Nokia Bss Formulas

Document Number/Issue

NTC f_bss_70

Copyright © Nokia Telecommunications Oy

STUDY OF BSS S11.5 ED COUNTER FORMULAS OF

NOKIA NETACT DATABASE

(NOKIA INTERNAL DOCUMENT)

v.80

STUDY OF BSS COUNTER FORMULAS OF NOKIA NMS2000 (PMWG working document)

Document Number/Issue NTC f_bss_70

Copyright Nokia Telecommunications Oy Page

2

The information in this document is subject to change without notice and describes only the software version defined in the introduction of this document. This document is intended for the use of Nokia Telecommunications customers only, and no part of it may be reproduced or transmitted in any form or means without the written permission of Nokia Telecommunications. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Telecommunications and the customer. Nokia Telecommunications will not be responsible in any event for errors in this document or for any damages, incidental or consequential (including monetary losses), that might arise from the use of this publication or the information in it. This material and the software described in this document are copyrighted according to the applicable laws. Trademarks The Nokia name and the Nokia logo are trademarks of Nokia Telecommunications Oy. Other product names mentioned in this document may be trademarks and they are mentioned for identification purposes only. This document was produced at Nokia Telecommunications, Network Operating Services, Hatanpäänkatu 3, 33100 Tampere, Finland. No. of pages Edited by Author Approved by Previous issue approved J. Neva J. Neva 27 Jun 02 27 Jun 02

STUDY OF BSS COUNTER FORMULAS OF NOKIA

NMS2000 (PMWG working document))



3





4

TABLE OF CONTENTS ABOUT THIS DOCUMENT.........................................................................................................................................6

RELATED DOCUMENTS.............................................................................................................................................7

BSS COUNTER FORMULAS .....................................................................................................................................9

ADDITIONAL GPRS CHANNELS (ACH)....................................................................................................................9 MULTISLOT (MSL) ................................................................................................................................................... 14 DYNAMIC ABIS POOL (DAP )...................................................................................................................................27 TBF (TBF) ..................................................................................................................................................................30 RLC (RLC) ..................................................................................................................................................................83 LLC (LLC).................................................................................................................................................................124 FRAME RELAY (FRL)..............................................................................................................................................125 RANDOM ACCESS (RACH)......................................................................................................................................134 SDCCH DROP FAILURES (SD)...............................................................................................................................138

SDCCH Drop Counters (xxx) ........................................................................................................................141 Problems with the SDCCH Drop Counters .................................................................................................145

SDCCH DROP RATIO (SDR) ..................................................................................................................................146 SETUP SUCCESS RATIO (CSSR) .............................................................................................................................150 TCH DROP FAILURES ............................................................................................................................................151

TCH Drop Call Counters................................................................................................................................151 Drop Call Ratio................................................................................................................................................157 Drop-out Ratio .................................................................................................................................................157 Problems with the Drop Call Counters .......................................................................................................157

DROP CALL FAILURES (DCF)................................................................................................................................157 TCH DROP CALL % (DCR)....................................................................................................................................162 HANDOVER (HO).....................................................................................................................................................210 HANDOVER FAILURE % (HFR)..............................................................................................................................234 HANDOVER SUCCESS % (HSR)...............................................................................................................................283 HO FAILURES (HOF)...............................................................................................................................................291 INTERFERENCE (ITF) .............................................................................................................................................297 CONGESTION (CNGT) .............................................................................................................................................300 QUEUING (QUE) ......................................................................................................................................................304 BLOCKING (BLCK) ..................................................................................................................................................309 TRAFFIC (TRF).........................................................................................................................................................336 TRAFFIC DIRECTIONS (XXX) ................................................................................................................................517

Mobile Originated Calls (moc).....................................................................................................................517 Mobile Terminated Calls (mtc) .....................................................................................................................519

PAGING (PGN )..........................................................................................................................................................522 SHORT MESSAGE SERVICE (SMS).........................................................................................................................528 DIRECTED RETRY (DR).........................................................................................................................................531 AVAILABILITY (AVA)............................................................................................................................................534 UNAVAILABILITY (UAV).......................................................................................................................................581 LOCATION UPDATES (LU).....................................................................................................................................591 LU SUCCESS % (LSR)..............................................................................................................................................593 LU FAILURE (LUF)..................................................................................................................................................595 EMERGENCY CALL (EC).........................................................................................................................................595 EMERCENCY CALL SUCCESS % (ECS)..................................................................................................................595 CALL RE-ESTABLISHMENT (RE)..........................................................................................................................596 CALL RE-ESTABLISHMENT SUCCESS % (RES)....................................................................................................597





5

DOWNLINK QUALITY (DLQ)................................................................................................................................597 UPLINK QUALITY (ULQ).......................................................................................................................................612 DL LEVEL, (DLL).....................................................................................................................................................627 UL LEVEL, (ULL).....................................................................................................................................................628 POWER (PWR).........................................................................................................................................................629 LEVEL (LEV) ............................................................................................................................................................630 DISTANCE ................................................................................................................................................................632 VOICE QUALITY (VQ) ............................................................................................................................................634 LINK BALANCE , POWER, LEVEL (LB)..................................................................................................................635 CALL SUCCESS (CSF)...............................................................................................................................................640 CONFIGURATION (CNF).........................................................................................................................................688 HSCSD (HSD)...........................................................................................................................................................689 ADAPTIVE MULTIRATE (AMR)............................................................................................................................691 POSITION BASED SERVICES (PBS).........................................................................................................................693 DFCA .......................................................................................................................................................................699 WPS..........................................................................................................................................................................706 TEMPLATE..............................................................................................................................................................708

MISSING COUNTERS.............................................................................................................................................709

XX1...........................................................................................................................................................................709 XX2...........................................................................................................................................................................710 XX3...........................................................................................................................................................................710 XX4...........................................................................................................................................................................710

ABBREVIATIONS ...................................................................................................................................................711

REFERENCES ............................................................................................................................................................712

REF.2.........................................................................................................................................................................712




6/712

ABOUT THIS DOCUMENT

This document defines the formulas used to calculating Key Performance Indicators based on the Nokia NetAct database. The document is a working document of Nokia Performance Management Working Group (PMWG) and should not be given to customers as such. Pieces of information from this document can be given to the customers if the customer situation requires. Note: The text meant for Nokia internal use only is written as hidden text so that it can be easily removed using Word features. Remember to read the document with hidden text shown. The title of the formula refers to the BSC release (S1 for example), indicating the first release since when the counters of the formula have been available. The use of the formulas backwards (for example, S5 formulas with S4) may give no results (measurement is not available) or false results (some counters which are new, for example, in S5 will be filled with value -1 by the NOKIA NETACT for S4 BSCs). Especially when there are two BSC software releases running in the network simultaneously be careful when running the reports with newer counters. This document contains also formulas which are no longer up to date and not used in any actual reports of the NOKIA NETACT post-processing tools. You can see the formulas used in post-processing from the actual reports of the tools.




7/712

Note: This document does not contain information on whether the formula is used or not.

Related Documents

Information about related documents is not updated anymore!! #1

#2 TAN 0422 dn98619454x3x0xen

Database Description for BSC Measurements

Describes the structure of PM tables in the NOKIA NETACT database and describes the records (including counters) in each table.

Producer: OSS

#3 DN9814277 Call related DX causes in BSC. Functional description.

Explanation of phases and list of causes in TCH and SDCCH observations for details on dropping calls.

Producer: RAS




8/712

#4 DN9813878 DX Causes Coding Mapping

Explains the relationship between DX cause codes and PM counters. You need this if you try to analyse TCH and SDCCH observations.

Producer: RAS




9/712

BSS COUNTER FORMULAS

Additional GPRS channels (ach)

Additional GPRS channel use, S9PS (ach_1)

Use: BTS level, especially BH values can be used for adjusting the CDEF parameter. Example: if the value equals to one, on average one additional timeslot has been used for GPRS. If the situation continues, it indicates the need to extend the default or dedicated territory.

Known problems: The numerator is incremented when the TBF is released. Therefore, if there is, for example, one long TBF but no other traffic, the value of this KPI can be totally incorrect because the whole TBF duration is counted on one measurement period.

Experiences on use: ach_1 is included in ava_16. Formula: total hold time of all additional GPRS ch. seizures (sec)




10/712

----------------------------------------------------------- = period duration sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 --------------------------------------- sum(period_duration*60) Counters from table(s): a= p_nbsc_res_avail

Unit: time slot

Average additional GPRS channel hold time, S9PS (ach_2)

Use: If the value is high, more default area is needed. Experiences on use: Formula: total hold time of all additional GPRS ch. seizures (sec) --------------------------------------------------------------- = total nbr of all additional GPRS channel. seizures sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 -------------------------------------------------------------------------- sum(decode(AVE_ADD_GPRS_CH_HOLD_TIME_SUM ,0,0,AVE_ADD_GPRS_CH_HOLD_TIME_DEN) Counters from table(s): a= p_nbsc_res_avail




11/712

Unit: sec

) Additional GPRS channels seized, S9PS (ach_3)

Use: How many times an additional channel has been released (a case of territory downgrade). Known problems: Shows slightly incorrect values in the case of an extended cell. Formula: sum(decode(AVE_ADD_GPRS_CH_HOLD_TIME_SUM ,0,0,AVE_ADD_GPRS_CH_HOLD_TIME_DEN) Counters from table(s): a= p_nbsc_res_avail

Additional GPRS channels seized, S9PS (ach_3a)

Use: How many times an additional channel has been released (a case of territory downgrade). Known problems: Shows slightly incorrect values in the case of an extended cell. Formula: sum(decode(decode(trx_type,0,AVE_ADD_GPRS_CH_HOLD_TIME_SUM) ,0,0,decode(trx_type,0,AVE_ADD_GPRS_CH_HOLD_TIME_DEN))) Counters from table(s): a= p_nbsc_res_avail

Total additional GPRS channel hold time, S9PS (ach_4)

Use: If the value is high, more default area is needed.




12/712

Experiences on use: Formula: sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 Counters from table(s): a= p_nbsc_res_avail Unit: sec

Additional GPRS channel use, PCU level, S9PS (ach_5)

Use: PCU level, see ach_1 Example: see ach_1.

Known problems: 1. Results will be incorrect if the "period duration" is different during reporting period. 2. The numerator is incremented when the TBF is released. Therefore, if there is, for example, one long TBF but no other traffic, the value of this KPI can be

totally incorrect because the whole TBF duration is counted on one measurement period. Experiences on use: ach_1 is included in ava_16. Formula: total hold time of all additional GPRS ch. seizures (sec) ----------------------------------------------------------- = period duration sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 ---------------------------------------




13/712

count(distinct period_start_time) * avg(period_duration*60) Counters from table(s): a= p_nbsc_res_avail

Unit: time slot

Ratio of used Additional GPRS channel, PCU level, S9PS (ach_6)

Description: Ratio of used additional GPRS channel Use: PCU level, see ach_5

Example: see ach_1. Known problems: 1. see ach_5 2. It is assumed that PCU handles 256 TSLs. Experiences on use: ach_1 is included in ava_16. Formula: Number of TSL used as additional GPRS channels ---------------------------------------------- TSL handling capacity of PCU (i.e. 256) ach_5 100 * ----- 256 Counters from table(s): a= p_nbsc_res_avail

Unit: %




14/712

Next free (ach_6)

Multislot (msl)

Distribution of UL multislot requests, S9PS (msl_1)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: req_X_TSL_UL 100 * -------------------------------------------------------------------------- % sum(req_1_TSL_UL+req_2_TSL_UL+req_1_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

req_X_TSL_UL = one of the components of the denominator. Counters from table(s): p_nbsc_packet_control_unit

Distribution of UL multislot requests, S9PS (msl_1a)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: req_X_TSL_UL 100 * -------------------------------------------------------------------------- %




15/712

sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)


Distribution of DL multislot requests, S9PS (msl_2)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: req_X_TSL_DL 100 * -------------------------------------------------------------------------- % sum(req_1_TSL_DL+req_2_TSL_DL+req_1_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)


Distribution of DL multislot requests, S9PS (msl_2a)

Use: Indicates the share of a multislot request type to all multislot requests. Formula:




16/712

req_X_TSL_DL 100 * -------------------------------------------------------------------------- % sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)


Distribution of UL multislot allocations, S9PS (msl_3)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: alloc_X_TSL_UL 100 * -------------------------------------------------------- % sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_1_TSL_UL +alloc_4_TSL_UL+ alloc_5_8_TSL_UL)





17/712

Distribution of UL multislot allocations, S9PS (msl_3a)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: alloc_X_TSL_UL 100 * -------------------------------------------------------- % sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL +alloc_4_TSL_UL+ alloc_5_8_TSL_UL)


Distribution of DL multislot allocations, S9PS (msl_4)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: alloc_X_TSL_DL 100 * ------------------------------------------------------ % sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_1_TSL_DL +alloc_4_TSL_DL+ alloc_5_8_TSL_DL)

req_X_TSL_DL = one of the components of the denominator.




18/712

Counters from table(s): p_nbsc_packet_control_unit

Distribution of DL multislot allocations, S9PS (msl_4a)

Use: Indicates the share of a multislot request type to all multislot requests. Formula: alloc_X_TSL_DL 100 * ------------------------------------------------------ % sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL +alloc_4_TSL_DL+ alloc_5_8_TSL_DL)

req_X_TSL_DL = one of the components of the denominator. Counters from table(s): p_nbsc_packet_control_unit

Ratio of reserved GPRS UL TSL requests, S9PS (msl_5)

Use: Indicates the ratio of multislot allocations to requests. Formula:




19/712

sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL) 100 * --------------------------------------------------------------------------------- % sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit

Ratio of reserved GPRS DL TSL requests, S9PS (msl_6)

Use: Indicates the ratio of multislot allocations to requests. Formula: sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL) 100 * --------------------------------------------------------------------------------- % sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit

UL multislot allocations, S9PS (msl_9)

Use: Total number of multislot allocations in UL. Formula: sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL +alloc_4_TSL_UL+ alloc_5_8_TSL_UL)




20/712

DL multislot allocations, S9PS (msl_10)

Use: Total number of multislot allocations in DL. Formula: sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL +alloc_4_TSL_DL+ alloc_5_8_TSL_DL)


Average number of allocated TSL, UL S9PS (msl_11)

Use: Formula: sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL) ------------------------------------------------------------------------ sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL+alloc_4_TSL_UL)


Average number of allocated TSL, UL S9PS (msl_11a)

Use: Formula:




21/712

sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL) ------------------------------------------------------------------------ sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL+alloc_4_TSL_UL+NO_RADIO_RES_AVA_UL_TBF)


Average number of allocated TSL, DL S9PS (msl_12)

Use: Formula: sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL) ------------------------------------------------------------------------ sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL)


Status: NOK (0 allocation not covered) Average number of allocated TSL, DL S9PS (msl_12a)

Use: Formula: sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL) ------------------------------------------------------------------------ sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL+NO_RADIO_RES_AVA_DL_TBF)




22/712

Counters from table(s): p_nbsc_packet_control_unit Status: OK Average number of requested UL TSL, S9PS (msl_13)

Use: Known problems: If one phase access is used (MS on CCCH) only the requested one single timeslot can be requested. Otherwise the MS class defines

how many timeslots are requested. This makes the meaning of the KPI less accurate. Formula: sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL) ------------------------------------------------------------------------ sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL+req_4_TSL_UL)


Average number of requested DL TSL, S9PS (msl_14)

Use: Known problems: If one phase access is used (MS on CCCH) only the requested one single timeslot can be requested. Otherwise the MS class defines

how many timeslots are requested. This makes the meaning of the KPI less accurate.




23/712

Formula: sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL) ------------------------------------------------------------------------ sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL+req_4_TSL_DL)


UL multislot allocation %, S9PS (msl_15)

Use: Indicates how well the requested multislots could be allocated. Known problems: 1) If there are no radio resources available, the allocation counters are not triggered and the ratio can get over 100%. E.g. a case

when a) 1 timeslot is requested (req_1_TSL_UL triggered) once but there are no resources, and therefore alloc_1_TSL_UL is not triggered.

b) 2 timeslots requested (req_2_TSL_UL triggered) and 2 timeslots allocated (alloc_2_TSL_UL) would give 100*(2*1+0)/(1) /(1+2*1) /(2) = 100* 4/3 =133.3%

2) Works until there are MSs with a multislot class greater than 4. Formula: 100* average allocated tsl / average requested tsl % = sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL) ------------------------------------------------------------------ sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL+alloc_4_TSL_UL) 100* ------------------------------------------------------------------------- %




24/712

sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL) ---------------------------------------------------------------- sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL+req_4_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit

UL multislot allocation %, S9PS (msl_15a)

Use: Indicates how well the requested multislots could be allocated. Known problems: 1) Works until there are MSs with a multislot class greater than 4. Formula: 100* average allocated tsl / average requested tsl % = sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL) ------------------------------------------------------------------ sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL+alloc_4_TSL_UL+ +NO_RADIO_RES_AVA_UL_TBF) 100* ------------------------------------------------------------------------- % sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL) ---------------------------------------------------------------- sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL+req_4_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit




25/712

DL multislot allocation %, S9PS (msl_16)

Use: Indicates how well the requested multislots could be allocated. Known problems: 1) If there are no radio resources available, the allocation counters are not triggered and the ratio can get over 100%. (See the

example in msl_15). 2) Works until there are MSs with a multislot class greater than 4. Formula: 100* average allocated tsl / average requested tsl % = sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL) ------------------------------------------------------------------ sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL) 100* ------------------------------------------------------------------------- % sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL) ---------------------------------------------------------------- sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL+req_4_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit

DL multislot allocation %, S9PS (msl_16a)

Use: Indicates how well the requested multislots could be allocated. Known problems: 1) Works until there are MSs with a multislot class greater than 4. Formula:




26/712

100* average allocated tsl / average requested tsl % = sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL) ------------------------------------------------------------------ sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL + NO_RADIO_RES_AVA_DL_TBF) 100* ----------------------------------------------------------------------- % sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL) ---------------------------------------------------------------- sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL+req_4_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit UL multislot requests, S9PS (msl_17)

Use: Total number of multislot requests in UL. Formula: sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

DL multislot requests, S9PS (msl_18)

Use: Total number of multislot requests in DL. Formula: sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)




27/712


Next free (msl_18)

Dynamic Abis Pool (dap)

Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1)

Description:. Percentage of Average usage of DL Dynamic Abis Pool from the total amount of subTSLs in DL EDAP. Use: Indicates the usage of pool resources. Formula: Sum(AVERAGE_DL_EDAP_USAGE_SUM) / Sum(AVERAGE_EDAP_USAGE_DEN) Counters from table(s): p_nbsc_dynamic_abis Unit: %




28/712

Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1a)

Description:. Percentage of Average usage of DL Dynamic Abis Pool from the total amount of subTSLs in DL EDAP. Use: Indicates the usage of pool resources. Known Problem: there may be EDAP allocations only in one direction at a time. This may lower the averages, and most probably the values in both directions

are smaller than actual percentage averages. Separate counters are needed for both 76000 and 76003 in DL and UL. This fix is in future plans.

Formula: Sum(AVERAGE_DL_EDAP_USAGE_SUM) 100 * ------------------------------ Sum(TOTAL_PCM_SUBTSLS_IN_EDAP) Counters from table(s): p_nbsc_dynamic_abis Unit: %

Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2)

Description:. Percentage of Average usage of UL Dynamic Abis Pool from the total amount of subTSLs in UL EDAP. Use: Indicates the usage of pool resources. Formula: Sum(AVERAGE_UL_EDAP_USAGE_SUM) / Sum(AVERAGE_EDAP_USAGE_DEN) Counters from table(s): p_nbsc_dynamic_abis




29/712

Unit: %

Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2a)

Description:. Percentage of Average usage of UL Dynamic Abis Pool from the total amount of subTSLs in UL EDAP. Use: Indicates the usage of pool resources. Known Problem: there may be EDAP allocations only in one direction at a time. This may lower the averages, and most probably the values in both directions

are smaller than actual percentage averages. Separate counters are needed for both 76000 and 76003 in DL and UL. This fix is in future plans.

Formula: Sum(AVERAGE_UL_EDAP_USAGE_SUM) 100 * -------------------------- Sum(TOTAL_PCM_SUBTSLS_IN_EDAP) Counters from table(s): p_nbsc_dynamic_abis Unit: %

Average Available PCM Sub-TSL, S10.5PS (dap_3)

Description: Average available amount of sub-TSLs in EDAP. Use: Indicates total sub-TSLs in EDAP. Formula: Sum(TOTAL_PCM_SUBTSLS_IN_EDAP) ------------------------------ Sum(AVERAGE_EDAP_USAGE_DEN)




30/712

Counters from table(s): p_nbsc_dynamic_abis Unit: sub-TSLs

Next free (dap_4)

TBF (tbf)

Average UL TBF data rate, S9PS (tbf_1)

Use: Indicates the average bit rate of TBF (throughput). Includes RLC/MAC header (3 octets) but not retransmissions. Formula: data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_UL_CS1 * (20+3)+RLC_data_blocks_UL_CS2 * (30+3))* 8/1000 ---------------------------------------------------------------------------- sum(Nbr_of_UL_TBF)* sum(Ave_dur_UL_TBF_sum/100) / sum(Ave_dur_UL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit




31/712

Unit: kbit/sec

Average UL TBF data rate, S9PS (tbf_1b)

Use: Indicates the average bit rate of TBF (throughput). Includes RLC/MAC header (3 octets) and retransmissions. Known problems: The denominator has been correct since BSC S9 CD 1.2. Formula: data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_UL_CS1*(20+3) +(RLC_data_blocks_UL_CS2 +retra_RLC_data_blocks_DL_CS1 +retra_RLC_data_blocks_DL_CS2)*(30+3))* 8/1000 ------------------------------------------------------------------------ sum(Nbr_of_UL_TBF)* sum(Ave_dur_UL_TBF_sum/100) / sum(Ave_dur_UL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec

Average UL TBF data rate, S9PS (tbf_1c)

Use: Indicates the average net bit rate of TBF (throughput). Does not include RLC header (2 byte), MAC header (1 byte) and retransmissions.




32/712

Known problems: The denominator has been correct since BSC S9 CD 1.2. Short TBFs affect strongly. The numerator contains also abnormally released TBFs whereas the denumerator only contains normally released TBFs. - The denominator counts also the time when the MS is not in transfer mode. Multislots are counted as one TBF. Therefore the formula is useful only if there is one class of MS and they get the requested number

of timeslots (i.e. in the test environment) Note that in S10 there will be total duration of TBFs per QoS class. Formula: data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_UL_CS1*20 +RLC_data_blocks_UL_CS2*30) *8/1000 ------------------------------------------------------------------------ sum(Nbr_of_UL_TBF)* sum(Ave_dur_UL_TBF_sum/100) / sum(Ave_dur_UL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec

Average DL TBF data rate, S9PS (tbf_2)

Use: Indicates the average bit rate of TBF (throughput). Includes RLC/MAC header (3 octets) but not retransmissions. Known problems: Formula tbf_1a is needed since BSC S9 CD 1.2. Formula:




33/712

data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_DL_CS1 * 23+RLC_data_blocks_DL_CS2 * 33 )* 8/1000 ---------------------------------------------------------------------- sum(Nbr_of_DL_TBF)* sum(Ave_dur_DL_TBF_sum) / sum(Ave_dur_DL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec

Average DL TBF data rate, S9PS (tbf_2a)

Use: Indicates the average bit rate of TBF (throughput). Includes RLC/MAC header (3 octets) but not retransmissions. Known problems: Formula tbf_1a is needed since BSC S9 CD 1.2. Formula: data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_DL_CS1 * 23+RLC_data_blocks_DL_CS2 * 33 )* 8/1000 ---------------------------------------------------------------------- sum(Nbr_of_DL_TBF)* sum(Ave_dur_DL_TBF_sum/100) / sum(Ave_dur_DL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec




34/712

Average DL TBF data rate, S9PS (tbf_2c)

Use: Indicates the average net bit rate of TBF (throughput). Does not include RLC header (2 byte), MAC header (1 byte) and retransmissions.

Known problems: 1) The denominator has been correct since BSC S9 CD 1.2. 2) Short TBFs affect strongly. There might be only one or a couple of actual blocks to be sent, but the duration of the tbf also contains signalling delays when the MS is not in transfer mode

3) The numerator also contains abnormally released TBFs whereas the denominator only contains normally released TBFs. - 4) Multislots are counted as one TBF. Therefore the formula is useful only if there is one class of MS and they get the requested

number of timeslots (i.e. in the test environment). Note that in S10 there will be the total duration of TBFs per QoS class. Formula: data in kilobits -------------------- = TBF total time sum(RLC_data_blocks_DL_CS1 * 20+RLC_data_blocks_DL_CS2 * 30 )* 8/1000 ---------------------------------------------------------------------- sum(Nbr_of_DL_TBF)* sum(Ave_dur_DL_TBF_sum/100) / sum(Ave_dur_DL_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec




35/712

Average number of LLC blocks per UL TBF, S9PS (tbf_3)

Use: Indicates the average number of LLC data blocks per normally released TBF. Formula: sum(Ave_UL_LLC_per_TBF_sum) ---------------------------- sum(Ave_UL_LLC_per_TBF_den) Counters from table(s): p_nbsc_packet_control_unit

Average number of LLC blocks per DL TBF, S9PS (tbf_4)

Use: Indicates the average number of LLC data blocks per normally released TBF. Formula: sum(Ave_DL_LLC_per_TBF_sum) ---------------------------- sum(Ave_DL_LLC_per_TBF_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds




36/712

Average UL TBF duration, S9PS (tbf_5)

Use: Known problems: The unit has changed to 10 ms in BSC CD 1.2. After that tbf_5a is needed. Formula: sum(ave_dur_ul_tbf_sum) ------------------------ sum(ave_dur_ul_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds

Average UL TBF duration, S9PS (tbf_5a)

Use: Counted from the normally released TBFs. Known problems: Contains part of TBF establishment delays. Formula: sum(ave_dur_ul_tbf_sum)/100 ---------------------------- sum(ave_dur_ul_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds




37/712

Average UL TBF duration, S9PS (tbf_5b)

Use: Counted from the normally released TBFs. Known problems: Contains part of TBF establishment delays. Formula: sum(ave_dur_ul_tbf_sum)/100 ---------------------------- sum(decode(ave_dur_ul_tbf_sum,1,0,ave_dur_ul_tbf_den)) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds

Average DL TBF duration, S9PS (tbf_6)

Use: Counted from the normally released TBFs. Known problems: The unit has changed to 10 ms in BSC CD 1.2. After that tbf_6a is needed. Formula: sum(ave_dur_dl_tbf_sum) ------------------------ sum(ave_dur_dl_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds




38/712

Average DL TBF duration, S9PS (tbf_6a)

Use: Counted from the normally released TBFs. Known problems: Contains part of TBF establishment delays. Formula: sum(ave_dur_dl_tbf_sum)/100 --------------------------- sum(ave_dur_dl_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds

Average DL TBF duration, S9PS (tbf_6b)

Use: Counted from the normally released TBFs. Known problems: Contains part of TBF establishment delays. Formula: sum(ave_dur_dl_tbf_sum)/100 --------------------------- sum(decode(ave_dur_dl_tbf_sum,1,0,ave_dur_dl_tbf_den)) Counters from table(s): p_nbsc_packet_control_unit

Unit: seconds




39/712

Average UL TBF duration, unack mode, S9PS (tbf_7)

Use: Formula: sum(ave_dur_ul_tbf_unack_mode_sum/100) ------------------------------------- sum(ave_dur_ul_tbf_ unack_mode_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds

Average DL TBF duration, unack mode, S9PS (tbf_8)

Use: Formula: sum(ave_dur_dl_tbf_unack_mode_sum/100) -------------------------------------- sum(ave_dur_dl_tbf_ unack_mode_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds




40/712

Dropped UL TBF %, S9PS (tbf_9)

Use: Formula: sum(UL_TBF_rel_due_CSW_traffic+UL_TBF_rel_due_no_resp_MS) 100 * ------------------------------------------------------- % sum(Nbr_of_UL_TBF)


Dropped DL TBF %, S9PS (tbf_10)

Use: Formula: sum(DL_TBF_rel_due_CSW_traffic+DL_TBF_rel_due_no_resp_MS) 100 * ------------------------------------------------------- % sum(Nbr_of_DL_TBF)





41/712

Requested UL TBF, S9PS (tbf_11)

Use: Known problems: Does not contain requests that are rejected due to lack of resources. Formula: sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit

Requested UL TBF, S9PS (tbf_11a)

Use: Formula: sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL + NO_RADIO_RES_AVA_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit




42/712

Requested DL TBF, S9PS (tbf_12)

Use: Known problems: Does not contain requests that are rejected due to lack of resources. Formula: sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit

Requested DL TBF, S9PS (tbf_12a)

Use: Known problems: Formula: sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) + NO_RADIO_RES_AVA_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit




43/712

UL TBF establishment success ratio, S9PS (tbf_13)

Use: Known problems: The numerator is updated when UL TBFs are established, while counters in the denominator are counting timeslot allocations.

Consecutive TBFs may use only one timeslot allocation and in reallocations only the timeslot allocation counters are updated. Formula: sum(nbr_of_UL_TBF) 100 * -------------------------------------------------------------------------% sum(req_1_TSL_UL+req_2_TSL_UL+req_1_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit

DL TBF establishment success ratio, S9PS (tbf_14)

Use: Known problems: The numerator is updated when DL TBFs are established, while counters in the denominator are counting timeslot allocations.

Consecutive TBFs may use only one timeslot allocation and in reallocations only the timeslot allocation counters are updated. Formula: sum(nbr_of_DL_TBF) 100 * -------------------------------------------------------------------------% sum(req_1_TSL_DL+req_2_TSL_DL+req_1_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit




44/712

UL mlslot allocation blocking, S9PS (tbf_15)

Use: If the blocking is met regularly, there is need either to expand the territory (CS traffic low) or TCH capacity (CS traffic high). Note: If the statistics show that there is blocking but no upgrade requests yet, the reason may be that the territory has been smaller than the

default setting defines (CS use). The PCU will not make an upgrade request. This is because the CS side will return the default channels back to the PS territory as soon as the CS load allows that.

Known problems: Formula: sum(NO_RADIO_RES_AVA_UL_TBF)

100 * -------------------------------------------------------------------------------------------------% sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit

DL mslot allocation blocking, S9PS (tbf_16)

Use: If the blocking is met regularly, there is need either to expand the territory (CS traffic low) or TCH capacity (CS traffic high). Note: If the statistics show that there is blocking but no upgrade requests yet, the reason may be that the territory has been smaller than the

default setting defines (CS use). The PCU will not make an upgrade request. This is because the CS side will return the default channels back to the PS territory as soon as the CS load allows that.

Formula: sum(NO_RADIO_RES_AVA_DL_TBF)

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




45/712

sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit

Dropped UL TBF %, MS lost, S9PS (tbf_17)

Use: Known problems: The amount of TBFs depends so much on the different factors that this KPI is not interpretable. Formula: sum(UL_TBF_rel_due_no_resp_MS) 100 * -------------------------------- % sum(Nbr_of_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit

Dropped DL TBF %, MS lost, S9PS (tbf_18)

Use: Known problems: The amount of TBFs depends so much on the different factors that this KPI is not interpretable. Formula: sum(DL_TBF_rel_due_no_resp_MS) 100 * ---------------------------------- % sum(Nbr_of_DL_TBF)




46/712


UL TBF re leases due to CS traffic %, S9PS (tbf_19)

Use: In GPRS the CS takes priority over the radio interface resources outside the dedicated territory. This KPI indicates the impact of CS traffic on PS (TBF drops) when radio interface capacity (TCH) is not sufficient and CS traffic takes the capacity from PS traffic by force.

Formula: sum(UL_TBF_rel_due_CSW_traffic) 100 * -------------------------------- % sum(Nbr_of_UL_TBF)


UL TBF releases due to CS traffic %, S9PS (tbf_19a)

Use: In GPRS the CS takes priority over the radio interface resources outside the dedicated territory. This KPI indicates the impact of CS traffic on PS (TBF drops) when radio interface capacity (TCH) is not sufficient and CS traffic takes the capacity from PS traffic by force.

Formula: sum(UL_TBF_rel_due_CSW_traffic)




47/712

100 * ----------------------------------------------------- % sum(Nbr_of_UL_TBF - UL_TBF_Establishment_Failed)


DL TBF releases due to CS traffic %, S9PS (tbf_20)

Use: In GPRS the CS takes priority over the radiointerface resources outside the dedicated territory. This KPI indicates the impact of CS traffic on PS (TBFs drops) when radio interface capacity (TCH) is not sufficient and CS traffic takes the capacity from PS traffic by force.

Formula: sum(DL_TBF_rel_due_CSW_traffic) 100 * ---------------------------------- % sum(Nbr_of_DL_TBF)


DL TBF releases due to CS traffic %, S9PS (tbf_20a)

Use: In GPRS the CS takes priority over the radiointerface resources outside the dedicated territory. This KPI indicates the impact of CS traffic on PS (TBFs drops) when radio interface capacity (TCH) is not sufficient and CS traffic takes the capacity from PS traffic by force.




48/712

Formula: sum(DL_TBF_rel_due_CSW_traffic) 100 * ------------------------------------------------------ % sum(Nbr_of_DL_TBF - DL_TBF_Establishment_Failed)


UL TBF drops per TBF hour, MS lost, S9PS (tbf_21)

Use: Formula: sum(UL_TBF_rel_due_no_resp_MS) 100 * --------------------------------------------------------------------------- % sum(Nbr_of_UL_TBF) *sum(ave_dur_UL_TBF_sum/100)/sum(ave_dur_UL_TBF_den)/3600

Counters from table(s): p_nbsc_packet_control_unit unit: drops / TBF hour

DL TBF drops per TBF hour, MS lost, S9PS (tbf_22)

Use:




49/712

Formula: sum(DL_TBF_rel_due_no_resp_MS) 100 * --------------------------------------------------------------------------- % sum(Nbr_of_DL_TBF) *sum(ave_dur_DL_TBF_sum/100)/sum(ave_dur_DL_TBF_den)/3600

Counters from table(s): p_nbsc_packet_control_unit unit: drops / TBF hour

Mean time between UL TBF drops due to MS lost, S9PS (tbf_23)

Use: Formula: sum(Nbr_of_UL_TBF) *sum(ave_dur_UL_TBF_sum/100)/sum(ave_dur_UL_TBF_den) ---------------------------------------------------------------------- sum(UL_TBF_rel_due_no_resp_MS) Counters from table(s): p_nbsc_packet_control_unit unit: TBF seconds

Mean time between DL TBF drops due to MS lost, S9PS (tbf_24)

Use: Formula:




50/712

sum(Nbr_of_DL_TBF) *sum(ave_dur_DL_TBF_sum/100)/sum(ave_dur_DL_TBF_den) ---------------------------------------------------------------------- sum(DL_TBF_rel_due_no_resp_MS) Counters from table(s): p_nbsc_packet_control_unit unit: TBF seconds

Normally released UL TBF ratio, S9PS (tbf_25)

Use: Known problems: If there is no normally released TBF, then AVE_DUR_UL_TBF_DEN = 1. instead of 0. Experiences on use: Cases when TBF is not released normally:

1) The PCU receives a Channel Request, allocates resources and sends an assignment but receives no blocks. These cases can occur if a MS sends more than one Channel Request before it receives an Immediate Assignment.

2) Ghost accesses. Formula: normally released UL TBFs 100*---------------------------- % = established UL TBFs sum(AVE_DUR_UL_TBF_DEN) 100*---------------------------% sum(NBR_OF_UL_TBF)




51/712


Normally released UL TBF ratio, S9PS (tbf_25a)

Use: Indicates the success of TBF. Some reasons for the abnormal releases can be seen from counters c72054, c72056, c72058, c72060. Known problems: 1) Counters of the numerator are triggered when the TBF is normally released whereas the counter of the denominator is triggered

when the TBF is established. This can cause inaccuracy especially on hourly level if the TBF lasts from one measurement period (hour) to another.

2) Some of the release types that are not included are still ‘normal’ for the end user. These types are flush and suspend. That is why this KPI alone is not useful.

Experiences on use: Cases when TBF is not released normally: 1) The PCU receives a Channel Request, allocates resources and sends an assignment but receives no blocks. These cases can occur if

a MS sends more than one Channel Request before it receives an Immediate Assignment. 2) Ghost accesses.

Formula: normally released UL TBFs 100*---------------------------- % = established UL TBFs sum(decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN)) 100*------------------------------------------------------% sum(NBR_OF_UL_TBF)




52/712


Normally released DL TBF ratio, S9PS (tbf_26)

Use: DL TBF establishment is not completed normally e.g. if the response from a MS is not received. If the TBF is already running and then the MS is not heard anymore, the counter DL_TBF_rel_due_no_resp_MS is triggered.

Known problems: If there is no normally released TBF, then AVE_DUR_UL_TBF_DEN = 1 instead of 0. Formula: normally released DL TBFs 100*---------------------------- % = established DL TBFs sum(AVE_DUR_DL_TBF_DEN) 100*--------------------------- % sum(NBR_OF_DL_TBF) Counters from table(s): p_nbsc_packet_control_unit

Normally released DL TBF ratio, S9PS (tbf_26a)

Use: Indicates the success of TBF. Some reasons for the abnormal releases can be seen from counters c72055, c72057, c72059, c72061. Known problems: 1) Counters of the numerator are triggered when the TBF is normally released whereas the counter of the denominator is triggered

when the TBF is established. This can cause inaccuracy especially on hourly level if the TBF lasts from one measurement period (hour) to another.




53/712

2) Some of the release types that are not included are still ‘normal’ for the end user. These types are flush and suspend. That is why this KPI alone is not useful.

Formula: normally released DL TBFs 100*---------------------------- % = established DL TBFs sum(decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN)) 100*-------------------------------------------------------- % sum(NBR_OF_DL_TBF) Counters from table(s): p_nbsc_packet_control_unit

UL Drops per 10 kbytes, MS lost, S9PS (tbf_27)

Use: This KPI tries to build something similar that we are used to seeing in the CS side to indicate the bad radio conditions that affect the connection, i.e. drops in ratio to volume.

Experiences on use: It has been found out that this KPI is problematic. One part of the problem is related to the counter used in the numerator. The second problem is related to the denominator (see below). Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of TBFs is quite independent of the RLC blocks (TBF length varies strongly). This KPI is suggested to be removed from the GPRS KPIs.

Known problems: - Slow cell reselections can affect the numerator. - 1000 used for 1 kbyte instead of 1024 Formula:




54/712

sum(UL_TBF_rel_due_no_resp_MS) -------------------------------- sum(rlc_data_blocks_ul_cs1*23 + rlc_data_blocks_ul_cs2*33 + rlc_mac_cntrl_blocks_ul*23 + BAD_FRAME_IND_UL_CS1*23 + BAD_FRAME_IND_UL_CS2*33)/ 10000 Counters from table(s): p_nbsc_packet_control_unit

UL Drops per 10 kbytes, MS lost, S9PS (tbf_27a)

Use: This KPI tries to build something similar that we are used to seeing in the CS side to indicate the bad radio conditions that affect the connection i.e. drops in ratio to volume.

Known problems: -Slow cell reselections (flushes) can increment the numerator. -Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of

TBFs is quite independent of the RLC blocks (TBF length varies strongly). -In S10 the EGPRS modulation coding scheme counters have to be added to the denominator. - 1000 used for 1 kbyte instead of 1024 Formula: sum(UL_TBF_rel_due_no_resp_MS) ------------------------------------------------------------------ sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 )/ 10000




55/712


UL Drops per 10 kbytes, MS lost, S9PS (tbf_27b)

Use: This KPI tries to build something similar that we are used to seeing in the CS side to indicate the bad radio conditions that affect the connection i.e. drops in ratio to volume.


TBFs is quite independent of the RLC blocks (TBF length varies strongly). -In S10 the EGPRS modulation coding scheme counters have to be added to the denominator. Formula: sum(UL_TBF_rel_due_no_resp_MS) ------------------------------------------------------------------ sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 )/ 10240 Counters from table(s): p_nbsc_packet_control_unit Unit: Drops per 10Kbytes

UL Drops per 10 kbytes, MS lost, S10.5PS (tbf_27c)

Description: UL TBF Drops per 10 kbytes Use: To indicate the bad radio conditions that affect the connection i.e. drops in ratio to volume.




56/712


TBFs is quite independent of the RLC blocks (TBF length varies strongly). Formula: sum(UL_TBF_rel_due_no_resp_MS) ---------------------------------------------------------------- (sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 ) + (sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148))/ 10240 Where xx=(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: Drops per 10 Kbytes

DL Drops per 10 kbytes, MS lost, S9PS (tbf_28)

Use: See tbf_27.




57/712

Experiences on use: See tbf_27. Known problems: -Slow cell reselections can affect the numerator. -Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of

TBFs is quite independent of the RLC blocks (TBF length varies strongly). -Dummy DL blocks make the ratio to show better -If there is UL TBF, it needs DL MAC blocks for ACK/NACK and therefore it is not correct to use MAC blocks in the same

formula with TBF, - 1000 used for 1 kbyte instead of 1024 Formula: sum(DL_TBF_rel_due_no_resp_MS) -------------------------------- sum(rlc_data_blocks_dl_cs1*23 + rlc_data_blocks_dl_cs2*33 + rlc_mac_cntrl_blocks_dl*23 + RETRA_RLC_DATA_BLOCKS_DL_CS1*23 + RETRA_RLC_DATA_BLOCKS_DL_CS2*33)/ 10000 Counters from table(s): p_nbsc_packet_control_unit

DL Drops per 10 kbytes, MS lost, S9PS (tbf_28a)

Use: See tbf_27a. Known problems: -Slow cell reselections (flushes) can increment the numerator.




58/712

-Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of TBFs is quite independent of the RLC blocks (TBF length varie s strongly).

-In S10 the EGPRS modulation coding scheme counters have to be added to the denominator. - 1000 used for 1 kbyte instead of 1024 Formula: sum(DL_TBF_rel_due_no_resp_MS) ------------------------------------------------------------------ sum(rlc_data_blocks_dl_cs1*20 + rlc_data_blocks_dl_cs2*30 )/ 10000 Counters from table(s): p_nbsc_packet_control_unit

DL Drops per 10 kbytes, MS lost, S9PS (tbf_28b)

Use: See tbf_27b. Known problems: -Slow cell reselections (flushes) can increment the numerator. -Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of

TBFs is quite independent of the RLC blocks (TBF length varies strongly). -In S10 the EGPRS modulation coding scheme counters have to be added to the denominator. Formula: sum(DL_TBF_rel_due_no_resp_MS) ------------------------------------------------------------------ sum(rlc_data_blocks_dl_cs1*20 + rlc_data_blocks_dl_cs2*30 )/ 10240




59/712


Unit: Drops per 10Kbytes DL Drops per 10 kbytes, MS lost, S10.5PS (tbf_28c)

Description: DL TBF Drops per 10kbytes Use: See tbf_27b. Known problems: -Slow cell reselections (flushes) can increment the numerator. -Combining TBF related information (numerator) to RLC block information (numerator) causes problems because the behaviour of

TBFs is quite independent of the RLC blocks (TBF length varies strongly). Formula: sum(DL_TBF_rel_due_no_resp_MS) ---------------------------------------- (sum(rlc_data_blocks_dl_cs1*20 + rlc_data_blocks_dl_cs2*30 + sum over MCS-1 (yy)* 22+ + sum over MCS-2 (yy)* 28+ + sum over MCS-3 (yy)* 37+ + sum over MCS-4 (yy)* 44+ + sum over MCS-5 (yy)* 56+ + sum over MCS-6 (yy)* 74+ + sum over MCS-7 (yy/2)*112+ + sum over MCS-8 (yy/2)*136+ + sum over MCS-9 (yy/2)*148)) / 10240




60/712

Where yy=(DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_schemes Unit: Drops per 10Kbytes

UL TBF reallocation failure ratio S9PS (tbf_29)

Use: Known problems: Formula: sum(UL_TBF_REALLOC_FAILS) 100 * ----------------------------------------------- % sum(UL_TBF_RE_ALLOCATIONS+ UL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit

DL TBF reallocation failure ratio S9PS (tbf_30)

Use: Known problems: Formula: sum(DL_TBF_REALLOC_FAILS)




61/712

100 * ----------------------------------------------- % sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit

Status: OK UL TBF reallocation attempts, S9PS (tbf_31)

Use: Known problems: Formula: sum(UL_TBF_RE_ALLOCATIONS+ UL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit

DL TBF reallocation attempts, S9PS (tbf_32)

Use: Known problems: Formula: sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS) Counters from table(s):




62/712

p_nbsc_packet_control_unit

UL TBF reallocation due to downgrade S10PS (tbf_33)

Use: Known problems: Formula: sum(REALLOC_DUE_TERR_DOWGR- DL_REALLOC_DUE_TERR_DOWNGR) Counters from table(s): p_nbsc_packet_control_unit

TBF success % S9PS (tbf_34)

Use: Also called ‘TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.

Known problems: Not usable on BTS level in S10 if common a BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100-TBF failure % = TBF establishments -Normal TBF releases - releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % =




63/712

TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_UL_TBF+ NBR_OF_DL_TBF ;TBF establishments -decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN) -decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN) -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_UL_TBF+NBR_OF_DL_TBF -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND) Counters from table(s): p_nbsc_packet_control_unit

TBF success % S9PS (tbf_34a)

Use: Also called ‘TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.

Known problems: Not usable on BTS level in S10 if common a BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100-TBF failure % = TBF establishments -Normal TBF releases - releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend




64/712

sum(NBR_OF_UL_TBF+ NBR_OF_DL_TBF - UL_TBF_Establishment_Failed - DL_TBF_Establishment_Failed ;TBF establishments -decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN) -decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN) -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_UL_TBF+NBR_OF_DL_TBF -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND) Counters from table(s): p_nbsc_packet_control_unit

UL TBF releases due to flush %, S9PS (tbf_35)

Use: This KPI indicates that there is mobility from this cell to other cells by cell reselection. Cell reselection affects the throughput. Formula: sum(UL_TBF_REL_DUE_TO_FLUSH) 100 * -------------------------------- % sum(Nbr_of_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit

UL TBF releases due to flush %, S9PS (tbf_35a)

Use: This KPI indicates that there is mobility from this cell to other cells by cell reselection. Cell reselection affects the throughput.




65/712

Formula: sum(UL_TBF_REL_DUE_TO_FLUSH) 100 * --------------------------------------------------------- % sum(Nbr_of_UL_TBF - UL_TBF_Establishment_Failed) Counters from table(s): p_nbsc_packet_control_unit

DL TBF releases due to flush %, S9PS (tbf_36)

Use: This KPI indicates that there is mobility from this cell to other cells by cell reselection. Cell reselection affects the throughput. Formula: sum (DL_TBF_REL_DUE_TO_FLUSH) 100 * ---------------------------------- % sum(Nbr_of_DL_TBF) Counters from table(s): p_nbsc_packet_control_unit

DL TBF releases due to flush %, S9PS (tbf_36a)

Use: This KPI indicates that there is mobility from this cell to other cells by cell reselection. Cell reselection affects the throughput. Formula: sum (DL_TBF_REL_DUE_TO_FLUSH)




66/712

100 * --------------------------------------------------------------- % sum(Nbr_of_DL_TBF- DL_TBF_Establishment_Failed) Counters from table(s): p_nbsc_packet_control_unit

Average UL TBF per timeslot, S9PS (tbf_37)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: 1) The numerator counts only the normally released TBF whereas the denominator also counts the abnormally released TBFs. Formula: sum(nbr_of_ul_tbf) ------------------------------------------------------ 12/13*(UL_RLC_blocks/50)/4.62 where UL_RLC_blocks = sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1 + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack + ignor_rlc_data_bl_ul_due_bsn) Counters from table(s): p_nbsc_packet_control_unit

Explanations




67/712

4.62 the length of TDMA frame is 4.62 ms 50 The Air interface can transmit 50 RLC blocks per second in a timeslot 12/13 The ratio of data transmission period to a multiframe period since there are 4 idle frames in between. Average UL TBF per timeslot, S9PS (tbf_37a)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: Formula: sum(req_1_tsl_ul+req_2_tsl_ul+req_3_tsl_ul+req_4_tsl_ul # all allocations - ul_tbf_re_allocations) # reallocations ------------------------------------------------------------------------- 12/13*(UL_RLC_blocks/50)/4.62 where UL_RLC_blocks = sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1 + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack + ignor_rlc_data_bl_ul_due_bsn) Counters from table(s): p_nbsc_packet_control_unit

Explanations




68/712

4.62 the length of TDMA frame is 4.62 ms 50 The Air interface can transmit 50 RLC blocks per second in a timeslot 12/13 The ratio of data transmission period to a multiframe period since there are 4 idle frames in between. Average UL TBF per timeslot, S9PS (tbf_37b)

Use: Indicates how many UL TBFs there are on average per timeslot. Known problems: 1) The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_ul_sum) -------------------------------------- sum(aver_tbfs_per_tsl_ul_den) Counters from table(s): p_nbsc_packet_control_unit

Average UL TBF per timeslot, S9PS (tbf_37c)

Use: Indicates how many UL TBFs there are on average per timeslot. Known problems: The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_ul_sum) -------------------------------------- sum(aver_tbfs_per_tsl_ul_den) * 100




69/712


Average UL TBF per timeslot, Area, S9PS (tbf_47)

Use: Indicates how many UL TBFs there are on average per timeslot. Known problems: The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_ul_sum) ----------------------------------------------------------------------- avg(aver_tbfs_per_tsl_ul_den) * 100 * count(distinct period_start_time) Counters from table(s): p_nbsc_packet_control_unit

Average DL TBF per timeslot, S9PS (tbf_38)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: 1) The numerator counts only the normally released TBF whereas then denominator also counts the abnormally released TBFs. 2) rlc_mac_cntrl_blocks_dl contains dummy blocks until S9 CD6.1. Formula: sum(nbr_of_dl_tbf)




70/712

------------------------------------------------------ 12/13*(DL_RLC_blocks/50)/4.62 where DL_RLC_blocks = sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs2) Counters from table(s): p_nbsc_packet_control_unit

Explanations 4.62 the length of TDMA frame is 4.62 ms 50 The Air interface can transmit 50 RLC blocks per second in a timeslot 12/13 The ratio of data transmission period to a multiframe period since there are 4 idle frames in between. Average DL TBF per timeslot, S9PS (tbf_38a)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: 1) rlc_mac_cntrl_blocks_dl contains dummy blocks until S9 CD6.1. Formula: sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL # all allocations - ul_tbf_re_allocations) # reallocations ------------------------------------------------------------------ 12/13*(DL_RLC_blocks/50)/4.62




71/712

where DL_RLC_blocks = sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs2) Counters from table(s): p_nbsc_packet_control_unit

Explanations 4.62 the length of TDMA frame is 4.62 ms 50 The Air interface can transmit 50 RLC blocks per second in a timeslot 12/13 The ratio of data transmission period to a multiframe period since there are 4 idle frames in between. Average DL TBF per timeslot, S9PS (tbf_38b)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: 1) The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_dl_sum) ------------------------------------- sum(aver_tbfs_per_tsl_dl_den) Counters from table(s): p_nbsc_packet_control_unit




72/712

Average DL TBF per timeslot, S9PS (tbf_38c)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_dl_sum) ------------------------------------- sum(aver_tbfs_per_tsl_dl_den) * 100 Counters from table(s): p_nbsc_packet_control_unit

Average DL TBF per timeslot, Area, S9PS (tbf_48)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: The implementation of the counters is wrong. Correction pending. Formula: sum(aver_tbfs_per_tsl_dl_sum) ----------------------------------------------------------------------- avg(aver_tbfs_per_tsl_dl_den) * 100 * count(distinct period_start_time) Counters from table(s): p_nbsc_packet_control_unit




73/712

Average number of timeslots used in UL TBF, S9PS (tbf_39)

Use: Indicates how many UL TBFs there are on average per timeslot. Known problems: 1) The denominator does not cover the abnormally released TBF. 2) ave_dur_ul_tbf_sum is triggered only in the end of a TBF whereas the numerator is updated more in real time. Thus in case of long

TBFs the reporting period may end up in the middle of a TBF and cause an error in the calculation. Formula: sum(UL_RLC_blocks/50) # UL timeslot time --------------------------- sum(ave_dur_ul_tbf_sum)/100 # UL TBF time where UL_RLC_blocks = sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1 + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack + ignor_rlc_data_bl_ul_due_bsn) Counters from table(s): p_nbsc_packet_control_unit




74/712

Average number of timeslots used in DL TBF, S9PS (tbf_40)

Use: Indicates how many DL TBFs there are on average per timeslot. Known problems: 1) The denominator does not cover the abnormally released TBF. 2) ave_dur_ul_tbf_sum is triggered only in the end of a TBF whereas the numerator is updated more in real time. Thus in case of long

TBFs the reporting period may end up in the middle of a TBF and cause an error in the calculation. 3) rlc_mac_cntrl_blocks_dl contains dummy blocks until S9 CD62.

Formula: sum(DL_RLC_blocks/50) # DL timeslot time -------------------------- sum(ave_dur_dl_tbf_sum)/100# DL TBF time where DL_RLC_blocks = sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL GPRS TBF establishments, S10.5PS (tbf_41)

Description: UL GPRS TBF establishments Use: Indicates only GPRS TBF establishments. EGPRS establishments are not counted.




75/712

Known problems: Formula: Sum (NBR_OF_UL_TBF - EGPRS_TBFS_UL) Counters from table(s): p_nbsc_packet_control_unit Unit: Numbers

DL GPRS TBF establishments, S10.5PS (tbf_42)

Description: DL GPRS TBF establishments Use: Indicates only GPRS TBF establishments. EGPRS establishments are not counted. Known problems: Formula: Sum (NBR_OF_DL_TBF - EGPRS_TBFS_DL) Counters from table(s): p_nbsc_packet_control_unit Unit: Numbers

TBF multichannel allocation success rate, cell and area level, S10.5PS (tbf_43)

Description: Success ratio of TBF multichannel requests. Use: This KPI gives an overview about the requested TSL and assigned TSL. The TBF is served but with fewer TSLs than requested.




76/712

For example, if the MS requests 3 channels, but only 2 can be assigned, the Multichannel Allocation Success indicator would be (2/3) * 100 = 66 % This indicator allows assessing the blocking. Applicable on Cell and area level.

Known problems: Formula: Sum (NBR_OF_DL_TBF - EGPRS_TBFS_DL) (ALLOC_1_TSL_UL + 2* ALLOC_2_TSL_UL + 3* ALLOC_3_TSL_UL + 4* ALLOC_4_TSL_UL + 6.5* ALLOC_5_8_TSL_UL + ALLOC_1_TSL_DL + 2* ALLOC_2_TSL_DL + 3* ALLOC_3_TSL_DL + 4* ALLOC_4_TSL_DL + 6.5* ALLOC_5_8_TSL_DL) 100* -------------------------------------------------- (%) (REQ_1_TSL_UL + 2* REQ_2_TSL_UL + 3* REQ_3_TSL_UL + 4* REQ_4_TSL_UL + 6.5* REQ_5_8_TSL_UL + REQ_1_TSL_DL + 2* REQ_2_TSL_DL + 3* REQ_3_TSL_DL + 4* REQ_4_TSL_DL + 6.5* REQ_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit Unit: %

Normal TBF release ratio, DL to UL, S10.5PS (tbf_44)

Description: Ratio of normally released TBFs in DL to UL Use: To detect the relative activity in DL compared to UL, used in finding sleeping GPRS cells. Known problems:




77/712

Formula: (100*(AVE_DUR_DL_TBF_DEN/AVE_DUR_UL_TBF_DEN)) Counters from table(s): p_nbsc_packet_control_unit Unit: %

UL TBF success % S9PS (tbf_45)

Use: Also called ‘UL TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.

Known problems: Not usable on BTS level in S10 if a common BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100 - UL TBF failure % = TBF establishments - Normal TBF releases - releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_UL_TBF+;TBF establishments - decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN) - UL_TBF_REL_DUE_TO_FLUSH - UL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_UL_TBF - UL_TBF_REL_DUE_TO_FLUSH - UL_TBF_REL_DUE_TO_SUSPEND)




78/712

UL TBF success % S9PS (tbf_45a)

Use: Also called ‘UL TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.

Known problems: Not usable on BTS level in S10 if a common BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100 - UL TBF failure % = TBF establishments - Normal TBF releases - releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_UL_TBF - UL_TBF_Establishment_Failed +;TBF establishments - decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN) - UL_TBF_REL_DUE_TO_FLUSH - UL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_UL_TBF - UL_TBF_REL_DUE_TO_FLUSH - UL_TBF_REL_DUE_TO_SUSPEND)

DL TBF success % S9PS (tbf_46)

Use: Also called ‘DL TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.




79/712

Known problems: Not usable on BTS level in S10 if a common BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100-DL TBF failure % = TBF establishments - Normal TBF releases - releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_DL_TBF+;TBF establishments - decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN) - DL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_DL_TBF - DL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_SUSPEND) Counters from table(s): p_nbsc_packet_control_unit

DL TBF success % S9PS (tbf_46a)

Use: Also called ‘DL TBF retainability’. This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS.

Known proble ms: Not usable on BTS level in S10 if a common BCCH is used because TBF can start in one BTS of a segment and end in another. Formula: 100-DL TBF failure % = TBF establishments - Normal TBF releases




80/712

- releases due to flush – releases due to suspend 100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_DL_TBF -DL_TBF_Establishment_Failed +;TBF establishments - decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN) - DL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_DL_TBF - DL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_SUSPEND) Counters from table(s): p_nbsc_packet_control_unit

(E)GPRS DL TBF Establishment Failure ratio, S10.5PS (tbf_49)

Use: Known problems: Formula: sum(DL_TBF_Establishment_Failed + DL_EGPRS_TBF_REL_DUE_NO_RESP) 100 * ----------------------------------------------------------- % sum(Nbr_Of_DL_TBF) Counters from table(s): p_nbsc_packet_control_unit




81/712

GPRS DL TBF Establishment Failure ratio, S10.5PS (tbf_50)

Use: Known problems: Formula: sum(DL_TBF_Establishment_Failed) 100 * ---------------------------------- % sum(Nbr_Of_DL_TBF - EGPRS_TBFs_DL) Counters from table(s): p_nbsc_packet_control_unit

EGPRS DL TBF Establishment Failure ratio, S10.5PS (tbf_51)

Use: Known problems: Formula: sum(DL_EGPRS_TBF_REL_DUE_NO_RESP) 100 * ---------------------------------- % sum(EGPRS_TBFs_DL) Counters from table(s): p_nbsc_packet_control_unit




82/712

(E)GPRS UL TBF Establishment Failure ratio, S10.5PS (tbf_52)

Use: Known problems: Formula: sum(UL_TBF_Establishment_Failed + UL_EGPRS_TBF_REL_DUE_NO_RESP) 100 * ----------------------------------------------------------- % sum(Nbr_Of_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit

GPRS DL TBF Establishment Failure ratio, S10.5PS (tbf_53)

Use: Known problems: Formula: sum(UL_TBF_Establishment_Failed) 100 * ---------------------------------- % sum(Nbr_Of_UL_TBF - EGPRS_TBFs_UL) Counters from table(s): p_nbsc_packet_control_unit




83/712

EGPRS DL TBF Establishment Failure ratio, S10.5PS (tbf_54)

Use: Known problems: Formula: sum(UL_EGPRS_TBF_REL_DUE_NO_RESP) 100 * ---------------------------------- % sum(EGPRS_TBFs_UL) Counters from table(s): p_nbsc_packet_control_unit

Next free (tbf_99)

RLC (rlc)

Ack. CS1 RLC blocks UL, S9PS (rlc_1)

Use: Number of UL blocks in RLC ack mode using CS1. Retransmission not included. Formula: sum(RLC_DATA_BLOCKS_UL_CS1 - RLC_DATA_BLOCKS_UL_UNACK)

Ack. CS1 RLC blocks DL, S9PS (rlc_2)

Use: Number of DL blocks in RLC ack mode using CS1. Retransmission not included. Formula:




84/712

sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK)

Ack. CS1 RLC DL block error rate, S9PS (rlc_3)

Use: Number of DL blocks in RLC ack mode using CS1. Formula: sum(BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK ) 100 * ------------------------------------------------% sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK)

Ack. CS1 RLC DL block error rate, S9PS (rlc_3a)

Use: Number of DL blocks in RLC ack mode using CS1. Formula: sum(BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK ) 100 * ------------------------------------------------------% sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK + BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK )

Unack. CS1 RLC UL block error rate, S9PS (rlc_4)

Use:




85/712

Formula: sum(BAD_FRAME_IND_UL_UNACK) 100 * ---------------------------% sum(RLC_DATA_BLOCKS_UL_UNACK)

Unack. CS1 RLC UL block error rate, S9PS (rlc_4a)

Use: Formula: sum(BAD_FRAME_IND_UL_UNACK) 100 * ----------------------------------------------------% sum(RLC_DATA_BLOCKS_UL_UNACK+ BAD_FRAME_IND_UL_UNACK)

xxxx (rlc_5)

UL CS1 RLC data share, S9PS (rlc_6)

Use: Formula: sum(RLC_data_blocks_UL_CS1*22 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32




86/712

+ RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: %

UL CS1 RLC data share, S9PS (rlc_6a)

Use: Indicates how big a share as a percentage UL CS1 data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_UL_CS1*20) 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

UL CS1 ack RLC data share, S9PS (rlc_6b)

Use: Indicates how big a share as a percentage UL CS1 ack data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_UL_CS1-RLC_data_blocks_UL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit




87/712

Unit: %

UL CS1 unack RLC data share, S9PS (rlc_6c)

Use: Indicates how big a share as a percentage UL CS1 unack data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_UL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

UL CS2 RLC data share, S9PS (rlc_7)

Use: Indicates how big a share as a percentage UL CS2 comprises out of all RLC data blocks. Formula: sum(RLC_data_blocks_UL_CS2*32 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: %




88/712

UL CS2 RLC data share, S9PS (rlc_7a)

Use: Indicates how big a share as a percentage UL CS2 data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_UL_CS2*30 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

DL CS1 RLC data share, S9PS (rlc_8)

Use: Formula: sum(RLC_data_blocks_DL_CS1*22 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: %




89/712

DL CS1 RLC data share, S9PS (rlc_8a)

Use: Indicates how big a share as a percentage DL CS1 data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_DL_CS1*20 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

DL CS1 ack RLC data share, S9PS (rlc_8b)

Use: Indicates how big a share as a percentage DL CS1 ack data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_DL_CS1-RLC_data_blocks_DL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

DL CS1 unack RLC data share, S9PS (rlc_8c)

Use: Indicates how big a share as a percentage DL CS1 unack data comprises out of all RLC payload data.




90/712

Formula: sum(RLC_data_blocks_DL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

DL CS2 RLC data share, S9PS (rlc_9)

Use: Formula: sum(RLC_data_blocks_DL_CS2*32 100 * ----------------------------------------------------------% (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: %

DL CS2 RLC data share, S9PS (rlc_9a)

Use: Indicates how big a share as a percentage DL CS2 data comprises out of all RLC payload data. Formula: sum(RLC_data_blocks_DL_CS2*30) 100 * ----------------------------------------------------------%




91/712

sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) Counters from table(s): p_nbsc_packet_control_unit Unit: %

UL CS1 RLC block error rate, S9PS (rlc_10)

Use: Known problems: 100% values met. 100% means that the MS has not responded to USF. The number of ignored RLC data blocks in uplink due to BSN being in acknowledged mode should be subtracted but there is no

counter for this specifically for CS1 (only one counter for CS1 and CS2). Marked as counter xx in the formula. Experiences on use: UL block error rate (BLER) is higher than DL BLER because there is no DL power control and full power is used in DL. Formula: sum(bad_frame_ind_UL_CS1) 100 * -------------------------------------------------% sum(rlc_data_blocks_UL_CS1+ bad_frame_ind_UL_CS1 +xx) ) Counters from table(s): p_nbsc_packet_control_unit

UL CS1 RLC block error rate, S9PS (rlc_10a)

Use: High BLER means worse radio interface conditions. Known problems: 1) The number of ignored RLC data blocks in uplink due to BSN being in acknowledged mode should be subtracted but there is no

counter for this specifically for CS1 There is only one counter for CS1 and CS2 which is marked as counter xx in the formula.




92/712

2) Does not show correctly if there is unack mode used. (rlc_data_blocks_ul_cs1 contains both ack and unack) Experiences on use: UL block error rate (BLER) is normally higher than DL BLER. There can be several reasons to this:

1) There is UL power control while full power is used in DL. The UL PC parameters may have been set too aggressively. 2) UL BLER includes uplink as well as downlink transmission problems (the MS needs to decode the USF correctly before transmitting). 3) When the MS stops responding during an UL TBF (e.g. due to a cell change), a number of 'bad frames' is received by the PCU before it detects that the radio contact has been lost. These bad frames increase the counters c072070 or c072071, and thus the UL BLER. 4) Also when resources are allocated for an UL TBF during one phase access, but the MS does not respond, bad frames are received. Such an allocation without any blocks may occur, for example, if the MS has sent the channel request more than once during the access, or if there is a collision, i.e. the network initiates DL TBF establishment at the same time, the MS reacts on that and ignores the UL TBF.

Formula: sum(bad_frame_ind_UL_CS1) 100 * -------------------------------------------------% sum(rlc_data_blocks_UL_CS1+ bad_frame_ind_UL_CS1 +xx) xx = RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) sum(rlc_data_blocks_ul_cs1) = ------------------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit




93/712

UL CS1 ACK RLC block error rate, S9PS (rlc_10b)

Use: High BLER means worse radio interface conditions. Known problems: 1) The number of ignored RLC data blocks in uplink due to BSN being in acknowledged mode should be subtracted but there is no

counter for this specifically for CS1 There is only one counter for CS1 and CS2 which is marked as counter xx in the formula. 2) Does not show correctly if there is unack mode used. (rlc_data_blocks_ul_cs1 contains both ack and unack) Experiences on use: UL block error rate (BLER) is normally higher than DL BLER. There can be several reasons to this:

1) There is UL power control while full power is used in DL. The UL PC parameters may have been set too aggressively. 2) UL BLER includes uplink as well as downlink transmission problems (the MS needs to decode the USF correctly before transmitting). 3) When the MS stops responding during an UL TBF (e.g. due to a cell change), a number of 'bad frames' is received by the PCU before it detects that the radio contact has been lost. These bad frames increase the counters c072070 or c072071, and thus the UL BLER. 4) Also when resources are allocated for an UL TBF during one phase access, but the MS does not respond, bad frames are received. Such an allocation without any blocks may occur, for example, if the MS has sent the channel request more than once during the access, or if there is a collision, i.e. the network initiates DL TBF establishment at the same time, the MS reacts on that and ignores the UL TBF.

Formula: sum(bad_frame_ind_UL_CS1) 100 * -------------------------------------------------% sum(rlc_data_blocks_UL_CS1- rlc_data_blocks_UL_unack !ack CS1 data blocks + bad_frame_ind_UL_CS1 ) + xx !RLC CS1 blocks ignored due to incorrect BSN (estimate)




94/712

where xx = sum(rlc_data_blocks_ul_cs1 - rlc_data_blocks_UL_unack) xx = --------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1 - rlc_data_blocks_UL_unack + rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL CS1 ACK RLC block error rate, S9PS (rlc_10c)

Description: Block Error Rate (BLER) for UL CS1 ACK RLC Blocks Use: High BLER means worse radio interface conditions. Known problems: 1.SPARE72107=RETRA_RLC_DATA_BLOCKS_UL_CS1. the spare counter will be replaced by an official counter later on.

2. Impact of "Ignore due to BSN" not considered. 3. See also rlc_10b.

Formula: sum(SPARE072107) 100 * -----------------------------------------% sum(rlc_data_blocks_UL_CS1) Counters from table(s): p_nbsc_packet_control_unit




95/712

UL CS2 ACK RLC block error rate, S9PS (rlc_11)

Use: Known problems: 1)100% means that there can be only failing accesses. 2) The number of ignored RLC data blocks in downlink due to BSN being in acknowledged mode should be subtracted but there is

no counter for this separately for CS2. There is only one counter for CS1 and CS2 which is marked as counter xx in the formula. Experiences on use: UL block error rate (BLER) is higher than DL BLER because there is no DL power control and full power is used in DL. Formula: sum(bad_frame_ind_ul_cs2) 100 * -------------------------------------------------% sum(rlc_data_blocks_ul_cs2+ bad_frame_ind_ul_cs2


UL CS2 ARLC block error rate, S9PS (rlc_11a)

Use: High BLER means worse radio interface conditions. Known problems: 1) The number of ignored RLC data blocks in downlink due to BSN being in acknowledged mode should be subtracted but there is

no counter for this separately for CS2. There is only one counter for CS1 and CS2, the estimated value of which is counted as xx below.

2) Does not work if unack mode is used, too. Experiences on use: See rlc_10a Formula:




96/712

sum(bad_frame_ind_ul_cs2) 100 * -------------------------------------------------% sum(rlc_data_blocks_ul_cs2+ bad_frame_ind_ul_cs2 + xx) xx = RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated) sum(rlc_data_blocks_ul_cs2) = ------------------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL CS2 ACK RLC block error rate, S9PS (rlc_11b)

Use: High BLER means worse radio interface conditions. Known problems: 1) The number of ignored RLC data blocks in downlink due to BSN being in acknowledged mode should be subtracted but there is

no counter for this separately for CS2. There is only one counter for CS1 and CS2, the estimated value of which is counted as xx below.

Experiences on use: See rlc_11a Formula: sum(bad_frame_ind_ul_cs2) 100 * -------------------------------------------------% sum(rlc_data_blocks_ul_cs2 - rlc_data_blocks_UL_unack ! CS2 ack blocks + bad_frame_ind_ul_cs2 + xx ! RLC CS2 blocks ignored due to incorrect BSN (estimated) )




97/712

where sum(rlc_data_blocks_ul_cs2) xx = -------------------------------------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1- -rlc_data_blocks_UL_unack + rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL CS2 ACK RLC block error rate, S9PS (rlc_11c)

rlc_data_blocks_UL_unack removed from the denominator)Use: High BLER means worse radio interface conditions. Known problems: 1) The number of ignored RLC data blocks in uplink due to BSN being in acknowledged mode should be subtracted but there is no

counter for this separately for CS2. There is only one counter for CS1 and CS2, the estimated value of which is counted as xx below. Experiences on use: See rlc_10b Formula: sum(bad_frame_ind_ul_cs2) 100 * -------------------------------------------------% sum(rlc_data_blocks_ul_cs2 + bad_frame_ind_ul_cs2) + xx ! RLC CS2 blocks ignored due to incorrect BSN estimated where sum(rlc_data_blocks_ul_cs2) xx = ---------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1 - rlc_data_blocks_UL_unack




98/712

+ rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL CS2 ACK RLC block error rate, S10.5PS (rlc_11d)

Description Use: High BLER means worse radio interface conditions. Known problems: 1. SPARE72108=RETRA_RLC_DATA_BLOCKS_UL_CS2. the spare counter will be replaced by an official counter later on.

2. Impact of blocks "Ignored due to BSN" not covered. Experiences on use: See rlc_10b. Formula: sum(SPARE072108) 100 * -------------------------------------------% sum(rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

UL CS2 ACK RLC block error rate, S10.5PS (rlc_11e)

Description Use: High BLER means worse radio interface conditions. Known problems: 1. SPARE72108=RETRA_RLC_DATA_BLOCKS_UL_CS2. the spare counter will be replaced by an official counter later on.

2. Impact of blocks "Ignored due to BSN" not covered. Experiences on use: See rlc_10b.




99/712

Formula: sum(SPARE072108) 100 * -------------------------------------------------% sum(SPARE072108 + rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

DL CS1 RLC block error rate, S9PS (rlc_12)

Use: High BLER means worse radio interface conditions. Known problems: 1) Does not work if the unack mode is used, too. Formula: sum(retra_rlc_data_blocks_dl_cs1) 100 * -------------------------------------------------% sum(rlc_data_blocks_dl_cs1+ retra_rlc_data_blocks_dl_cs1)


DL CS1 ACK RLC block error rate, S9PS (rlc_12a)

Use: High BLER means worse radio interface conditions. Formula: sum(retra_rlc_data_blocks_dl_cs1) 100 * ---------------------------------------------------------------- % sum(rlc_data_blocks_dl_cs1 - rlc_data_blocks_dl_unack ; ack CS1 + retra_rlc_data_blocks_dl_cs1)




100/712


DL CS2 ACK RLC block error rate, S9PS (rlc_13)

Use: High BLER means worse radio interface conditions. Formula: sum(retra_rlc_data_blocks_dl_cs2) 100 * -------------------------------------------------------- % sum(rlc_data_blocks_dl_cs2+ retra_rlc_data_blocks_dl_cs2)


UL RLC blocks, S9PS (rlc_14)

Use: Total UL data volume as the number of RLC blocks. Known problems: Formula: sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1 + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack + ignor_rlc_data_bl_ul_due_bsn) Counters from table(s): p_nbsc_packet_control_unit




101/712

DL RLC blocks, S9PS (rlc_15)

Use: Total DL data volume as the number of RLC blocks. Known problems: Formula: sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs2) Counters from table(s): p_nbsc_packet_control_unit

DL CS1 UNACK RLC block error rate, S9PS (rlc_16)

Use: Indicates radio interface problems. Formula: sum(bad_frame_ind_ul_unack) 100 * --------------------------------------------------- % sum(rlc_data_blocks_ul_unack+bad_frame_ind_ul_unack)


ACK RLC block error rate, S9PS (rlc_17)

Use: Indicates radio interface problems. Formula:




102/712

sum(bad_frame_ind_UL_CS1+bad_frame_ind_UL_CS1 +retra_rlc_data_blocks_dl_cs1+retra_rlc_data_blocks_dl_cs2) 100* ----------------------------------------------------------------------- % sum(rlc_data_blocks_DL_CS1-rlc_data_blocks_DL_unack+rlc_data_blocks_DL_CS2 +rlc_data_blocks_UL_CS1-rlc_data_blocks_UL_unack+rlc_data_blocks_ul_CS2 +bad_frame_ind_UL_CS1+bad_frame_ind_UL_CS1 +retra_rlc_data_blocks_DL_CS1+retra_rlc_data_blocks_DL_CS2) Counters from table(s): p_nbsc_packet_control_unit

UL ACK EGPRS Block Error Ratio S10.5PS (rlc_18)

Description: Ratio of retransmitted UL blocks to all blocks sent in EGPRS coding schemes Use: Known problems: Formula: Sum over MCS1 to 9 (RETRANS_RLC_DATA_BLOCKS_UL) 100 * ------------------------------------------------------------------------- Sum over MCS1 to 9 (UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL)

Counters from table(s): p_nbsc_coding_scheme Unit: %

DL ACK EGPRS Block Error Ratio S10.5PS (rlc_19)

Description: Ratio of retransmitted DL blocks to all blocks sent in EGPRS coding schemes




103/712

Use: Known problems: Formula: Sum over MCS1 to 9 (RETRANS_RLC_DATA_BLOCKS_DL) 100 * ------------------------------------------------------------------------- Sum over MCS1 to 9 (DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL)


UL ACK EGPRS Block Error Ratio MCS-n S10.5PS (rlc_20)

Description: UL ACK EGPRS Block Error Ratio MCSn. Use: For UL ACK EGPRS Block Error Ratio of any MCS from MCS 1 to 9. Known problems: Formula: Sum over MCS-n (RETRANS_RLC_DATA_BLOCKS_UL) 100 * ----------------------------------------------------------------------- Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL) where n can be from 1 to 9. Counters from table(s): p_nbsc_coding_scheme Unit: %




104/712

DL ACK EGPRS Block Error Ratio MCS-n S10.5PS (rlc_21)

Description: DL ACK EGPRS Block Error Ratio MCSn Use: For DL ACK EGPRS Block Error Ratio of any MCS from MCS 1 to 9 Known problems: Formula: Sum over MCS-n (RETRANS_RLC_DATA_BLOCKS_DL) 100 * ----------------------------------------------------------------------- Sum over MCS-n (DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL) where n can be from 1 to 9 Counters from table(s): p_nbsc_coding_scheme Unit: %

UL ACK RLC Data Share MCS-n S10.5PS (rlc_22)

Description: UL ACK RLC Data Share, MCS-n Use: Indicates how big share as a percentage UL ACK RLC Data comprises out of all RLC Payload data Known problems: Formula: Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE) 100 * ---------------------------------------------- Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE




105/712

+ DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9 Counters from table(s): p_nbsc_coding_scheme Unit: %

UL UNACK RLC Data Share MCS-n S10.5PS (rlc_23)

Description: UL UNACK RLC Data Share MCS-n Use: Indicates how big share as a percentage UL UNACK RLC Data comprises out of all RLC Payload data Known problems: Formula: Sum over MCS-n (UL_RLC_BLOCKS_IN_UNACK_MODE) 100 * --------------------------------------------- Sum over MCS-n(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9 Counters from table(s): p_nbsc_coding_scheme Unit: %




106/712

DL ACK RLC Data Share MCS-n S10.5PS (rlc_24)

Description: DL ACK RLC Data Share MCS-n Use: Indicates how big share as a percentage DL ACK RLC Data comprises out of all RLC Payload data Known problems: Formula: Sum over MCS-n (DL_RLC_BLOCKS_IN_ACK_MODE) 100* --------------------------------------------------- Sum over MCS-n(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE+ DL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9 Counters from table(s): p_nbsc_coding_scheme Unit: %

DL UNACK RLC Data Share MCS-n S10.5PS (rlc_25)

Description: DL UNACK RLC Data Share MCS-n Use: Indicates how big share as a percentage DL UNACK RLC Data comprises out of all RLC Payload data Known problems: Formula: Sum over MCS-n (DL_RLC_BLOCKS_IN_UNACK_MODE)




107/712

100* --------------------------------------------------- Sum over MCS-n(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE+ DL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9 Counters from table(s): p_nbsc_coding_scheme Unit: %

GMSK RLC Data Block Share, S10.5PS (rlc_39)

Use: Share of RLC blocks with MCS1..4 out of all used MCS Known problems: Formula: Sum over MCS 1..4 ( UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE ) ----------------------------- * 100 Sum over MCS 1..9 ( UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE +




108/712

RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE ) Counters from table(s): p_nbsc_coding_scheme Unit: %

8-PSK RLC Data Share, S10.5PS (rlc_40)

Use: Share of RLC/MAC blocks with MCS1..4 out of all used MCS Known problems: Formula: Sum over MCS 5...9 ( UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE ) ---------------------------- * 100 Sum over MCS 1..9 ( UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE )




109/712


GMSK RLC Data Share, S10.5PS (rlc_41)

Use: Share of RLC Data bytes with MCS1..4 out of all used MCSs Known problems: Formula: (sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44) ---------------------------- * 100 (sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148) where xx = UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL +




110/712

DL_RLC_BLOCKS_IN_UNACK_MODE Counters from table(s): p_nbsc_coding_scheme Unit: %

GPRS UL ACK RLC data share, S10.5PS (rlc_42)

Description: Share of GPRS UL ACK RLC data in data for total data Use: Known problems: Formula: sum(RLC_data_blocks_UL_CS1-RLC_data_blocks_UL_UNACK)*20 + sum(RLC_data_blocks_UL_CS2*30 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)




111/712

Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

GPRS UL UNACK RLC data share, S10.5PS (rlc_43)

Description: Share of GPRS UL UNACK RLC data in data for total data Use: Known problems: Formula: sum(RLC_data_blocks_UL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s):




112/712

p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

GPRS DL ACK RLC data share, S10.5PS (rlc_44)

Description: Share of GPRS DL ACK RLC data in data for total data Use: Known problems: Formula: sum(RLC_data_blocks_DL_CS1-RLC_data_blocks_DL_UNACK)*20 + sum(RLC_data_blocks_DL_CS2*30 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s):




113/712

p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

GPRS DL UNACK RLC data share, S10.5PS (rlc_45)

Description: Share of GPRS DL UNACK RLC data in data for total data Use: Known problems: Formula: sum(RLC_data_blocks_DL_UNACK)*20 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme




114/712

Unit: %

EGPRS UL ACK RLC data share, S10.5PS (rlc_46)

Description: Share of EGPRS UL ACK RLC data in total data Use: Known problems: Formula: ( sum over MCS-1 (yy)* 22 + sum over MCS-2 (yy)* 28 + sum over MCS-3 (yy)* 37 + sum over MCS-4 (yy)* 44 + sum over MCS-5 (yy)* 56 + sum over MCS-6 (yy)* 74 + sum over MCS-7 (yy/2)*112 + sum over MCS-8 (yy/2)*136 + sum over MCS-9 (yy/2)*148) 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx=




115/712

(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Where yy= UL_RLC_BLOCKS_IN_ACK_MODE Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

EGPRS UL UNACK RLC data share, S10.5PS (rlc_47)

Description: Share of EGPRS UL UNACK RLC data in total data Use: Known problems: Formula: ( sum over MCS-1 (yy)* 22 + sum over MCS-2 (yy)* 28 + sum over MCS-3 (yy)* 37 + sum over MCS-4 (yy)* 44 + sum over MCS-5 (yy)* 56 + sum over MCS-6 (yy)* 74 + sum over MCS-7 (yy/2)*112 + sum over MCS-8 (yy/2)*136 + sum over MCS-9 (yy/2)*148) 100 * ---------------------------------------------------------- % sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44




116/712

+ sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Where yy= UL_RLC_BLOCKS_IN_UNACK_MODE Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

EGPRS DL ACK RLC data share, S10.5PS (rlc_48)

Description: Share of EGPRS DL ACK RLC data in total data Use: Known problems: Formula: ( sum over MCS-1 (yy)* 22 + sum over MCS-2 (yy)* 28 + sum over MCS-3 (yy)* 37 + sum over MCS-4 (yy)* 44 + sum over MCS-5 (yy)* 56 + sum over MCS-6 (yy)* 74 + sum over MCS-7 (yy/2)*112 + sum over MCS-8 (yy/2)*136 + sum over MCS-9 (yy/2)*148)




117/712

100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Where yy= DL_RLC_BLOCKS_IN_ACK_MODE Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

EGPRS DL UNACK RLC data share, S10.5PS (rlc_49)

Description: Share of EGPRS DL UNACK RLC data in total data Use: Known problems: Formula:




118/712

( sum over MCS-1 (yy)* 22 + sum over MCS-2 (yy)* 28 + sum over MCS-3 (yy)* 37 + sum over MCS-4 (yy)* 44 + sum over MCS-5 (yy)* 56 + sum over MCS-6 (yy)* 74 + sum over MCS-7 (yy/2)*112 + sum over MCS-8 (yy/2)*136 + sum over MCS-9 (yy/2)*148) 100 * ----------------------------------------------------------% sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) +( sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE + DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE) Where yy= DL_RLC_BLOCKS_IN_UNACK_MODE Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %




119/712

UL GPRS RLC payload data share, S10.5PS (rlc_50)

Description: Share of GPRS UL RLC payload data in total payload data Use: Known problems: Formula: rlc_42 + rlc_43 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

DL GPRS RLC payload data share, S10.5PS (rlc_51)

Description: Share of GPRS DL RLC payload data in total payload data Use: Known problems: Formula: rlc_44 + rlc_45 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %




120/712

UL EGPRS RLC payload data share, S10.5PS (rlc_52)

Description: Share of EGPRS UL RLC payload data in total payload data Use: Known problems: Formula: rlc_46 + rlc_47 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %

DL EGPRS RLC payload data share, S10.5PS (rlc_53)

Description: Share of EGPRS UL RLC payload data in total payload data Use: Known problems: Formula: rlc_48 + rlc_49 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: %




121/712

Ratio of UL CS1 (GPRS,ack) %, S10.5PS (rlc_54)

Description: Use: Known problems: Formula: Sum(RLC_Data_Blocks_UL_CS1 - RLC_Data_Blocks_UL_Unack) 100 * --------------------------- Sum(RLC_Data_Blocks_UL_CS1 - RLC_Data_Blocks_UL_Unack + RLC_Data_Blocks_UL_CS2) Counters from table(s): p_nbsc_packet_control_unit Unit: %

Ratio of DL CS1 (GPRS,ack) %, S10.5PS (rlc_55)

Description: Use: Known problems: Formula: Sum(RLC_Data_Blocks_DL_CS1 - RLC_Data_Blocks_DL_Unack) 100 * --------------------------- Sum(RLC_Data_Blocks_DL_CS1 - RLC_Data_Blocks_DL_Unack + RLC_Data_Blocks_DL_CS2) Counters from table(s): p_nbsc_packet_control_unit Unit: %




122/712

Ratio of UL MCS-n (EGPRS,ack) %, S10.5PS (rlc_56)

Description: Use: Known problems: Formula: Sum over MCS-n(UL_RLC_Blocks_In_Ack_Mode) 100 * ----------------------------------------- Sum over MCS 1-9(UL_RLC_Blocks_In_Ack_Mode) Counters from table(s): p_nbsc_coding_scheme Unit: %

Ratio of DL MCS-n (EGPRS,ack) %, S10.5PS (rlc_57)

Description: Use: Known problems: Formula: Sum over MCS-n(DL_RLC_Blocks_In_Ack_Mode) 100 * ----------------------------------------- Sum over MCS 1-9(DL_RLC_Blocks_In_Ack_Mode) Counters from table(s): p_nbsc_coding_scheme Unit: %




123/712

Ratio of UL MCS-n (EGPRS,Unack) %, S10.5PS (rlc_58)

Description: Use: Known problems: Formula: Sum over MCS-n(UL_RLC_Blocks_In_Unack_Mode) 100 * ----------------------------------------- Sum over MCS 1-9(UL_RLC_Blocks_In_Unack_Mode) Counters from table(s): p_nbsc_coding_scheme Unit: %

Ratio of DL MCS-n (EGPRS,Unack) %, S10.5PS (rlc_59)

Description: Use: Known problems: Formula: Sum over MCS-n(DL_RLC_Blocks_In_Unack_Mode) 100 * ----------------------------------------- Sum over MCS 1-9(DL_RLC_Blocks_In_Unack_Mode) Counters from table(s): p_nbsc_coding_scheme Unit: %




124/712

Next free (rlc_22 to 38)

Use: Known problems: Formula:

LLC (llc)

Expired LLC frames % DL, S9PS (llc_1)

Use: Ratio of expired LLC frames to all frames. Indicates throughput problems in SGSN or in the network under it. The lifetime of the packets is set by SGSN and that may expire already in SGSN. If a packet is sent to PCU, the remaining lifetime is

the time when it should be sent further in PCU. If the lifetime expires, the packet is discarded. Formula: sum(disc_llc_blocks_due_to_exp) 100 * ------------------------------------------------ % sum(ave_dl_llc_per_tbf_sum+ disc_llc_blocks_due_to_exp) Counters from table(s): p_nbsc_packet_control_unit

Discarded UL LLC frames, NSE unavailability %, S9PS (llc_2)

Use: Ratio of discarded LLC bytes to UL RLC data bytes. Bytes discarded due to unavailable NSE which may mean problems in the Gb interface. Formula:




125/712

sum(disc_UL_LLC_data) 100 * -------------------------------------------------------- % sum(RLC_data_blocks_UL_CS1*20 +RLC_data_blocks_UL_CS2*30)


Next free (llc_3)

Frame relay (frl)

Kbytes in sent frames, S9PS (frl_1)

Use: Total data volume over all DLCI. Frame relay signalling is delivered in DLCI 0, so counters do not contain these messages. This KPI includes NS and BSSGP signalling, which means that the counters start to get pegged when these layers have been created.

Formula: sum(dlci_1_bytes_sent + dlci_2_bytes_sent + dlci_3_bytes_sent + dlci_4_bytes_sent + dlci_5_bytes_sent) Counters from table(s): p_nbsc_frame_relay Unit: Kbyte




126/712

Kbytes in received frames, S9PS (frl_2)

Use: Total data volume over all DLCI. Frame relay signalling is delivered in DLCI 0, so counters do not contain these messages. This KPI ncludes NS and BSSGP signalling, which means that the countiers start to get pegged when these layers have been created.

Formula: sum(DLCI_1_BYTES_REC + DLCI_2_BYTES_REC + DLCI_3_BYTES_REC + DLCI_4_BYTES_REC + DLCI_5_BYTES_REC) Counters from table(s): p_nbsc_frame_relay Unit: Kbyte

'Wrong check seq.' errors per Mbyte, S9PS (frl_3)

Use: Quality indicator of the HDLC layer. Known problems: Formula: sum(FRMS_WRONG_CHECK_SEQ_) 1000 * --------------------------------------------- sum(DLCI_1_BYTES_REC + DLCI_1_BYTES_DISC_REC + DLCI_2_BYTES_REC + DLCI_2_BYTES_DISC_REC + DLCI_3_BYTES_REC + DLCI_3_BYTES_DISC_REC + DLCI_4_BYTES_REC + DLCI_4_BYTES_DISC_REC + DLCI_5_BYTES_REC + DLCI_5_BYTES_DISC_REC)




127/712

Counters from table(s): p_nbsc_frame_relay Unit: errors per Mbyte

Other' errors per Mbyte, S9PS (frl_4)

Use: Quality indicator of the HDLC layer. Known problems: Formula: sum(OTHER_FRAME_ERROR) 1000 * --------------------------------------------- sum(DLCI_1_BYTES_REC + DLCI_1_BYTES_DISC_REC + DLCI_2_BYTES_REC + DLCI_2_BYTES_DISC_REC + DLCI_3_BYTES_REC + DLCI_3_BYTES_DISC_REC + DLCI_4_BYTES_REC + DLCI_4_BYTES_DISC_REC + DLCI_5_BYTES_REC + DLCI_5_BYTES_DISC_REC) Counters from table(s): p_nbsc_frame_relay Unit: errors per Mbyte

Bytes in discarded sent frames, S9PS (frl_5)

Use: Formula: sum(dlci_1_bytes_disc_sent + dlci_2_bytes_disc_sent + dlci_3_bytes_disc_sent + dlci_4_bytes_disc_sent




128/712

+ dlci_5_bytes_disc_sent)

Counters from table(s): p_nbsc_frame_relay

Bytes in discarded received frames, S9PS (frl_6)

Use: Formula: sum(dlci_1_bytes_disc_rec + dlci_2_bytes_disc_rec + dlci_3_bytes_disc_rec + dlci_4_bytes_disc_rec + dlci_5_bytes_disc_rec)

Counters from table(s): p_nbsc_frame_relay

Max. send load %, S9PS (frl_7)

Use: Indicates the load % of the frame relay bearer for outgoing data to SGSN. Known problems: The access rate is taken from configuration data and represents only the current setting. This may cause errors when used in historical

perspective if the settings have been changed. Formula: max per bearer_id




129/712

(8*(dlci_1_bytes_sent + dlci_2_bytes_sent + dlci_3_bytes_sent + dlci_4_bytes_sent + dlci_5_bytes_sent)/(period_duration*60)) 100 * ------------------------------------------------- % sum per frbc over all unlocked child nsvc (c_nsvc.committed_info_rate*16); frbc object_instance = bearer_id in p_nbsc_frame_relay Counters from table(s): p_nbsc_frame_relay

Max. received load %, S9PS (frl_8)

Use: Indicates the load % of the frame relay bearer for incoming data from SGSN. Known problems: The access rate is taken from configuration data and represents only the current setting. This may cause errors when used in historical

perspective if the settings have been changed. Formula: max per bearer_id (8*(dlci_1_bytes_rec + dlci_2_bytes_rec + dlci_3_bytes_rec + dlci_4_bytes_rec + dlci_5_bytes_rec)/(period_duration*60)) 100 * --------------------------------------------- % sum per frbc over all unlocked child nsvc (c_nsvc.committed_info_rate*16);




130/712

frbc object_instance = bearer_id in p_nbsc_frame_relay Counters from table(s): p_nbsc_frame_relay

Sent frames, S9PS (frl_9)

Use: Formula: sum(dlci_1_sent_frms + dlci_2_sent_frms + dlci_3_sent_frms + dlci_4_sent_frms + dlci_5_sent_frms) Counters from table(s): p_nbsc_frame_relay Unit: Kbyte

Received frames, S9PS (frl_10)

Use: Formula: sum(dlci_1_rec_frms + dlci_2_rec_frms + dlci_3_rec_frms + dlci_4_rec_frms




131/712

+ dlci_5_rec_frms) Counters from table(s): p_nbsc_frame_relay Unit: Kbyte

Discarded sent frames, S9PS (frl_11)

Use: Formula: sum(dlci_1_disc_sent_frms + dlci_2_disc_sent_frms + dlci_3_disc_sent_frms + dlci_4_disc_sent_frms + dlci_5_disc_sent_frms) Counters from table(s): p_nbsc_frame_relay Unit: Kbyte

Discarded received frames, S9PS (frl_12)

Use: Formula: sum(dlci_1_disc_rec_frms + dlci_2_disc_rec_frms




132/712

+ dlci_3_rec_frms + dlci_4_disc_rec_frms + dlci_5_disc_rec_frms) Counters from table(s):; p_nbsc_frame_relay Unit: Kbyte

Discarded bytes, UL NS-VC congestion S9PS (frl_13)

Use: Formula: sum(dlci_1_disc_ul_ns_udata + dlci_2_disc_ul_ns_udata + dlci_3_disc_ul_ns_udata + dlci_4_disc_ul_ns_udata) Counters from table(s): p_nbsc_frame_relay Unit: byte

Discarded bytes, UL NS-VC congestion S9PS (frl_13a)

Use: Formula: sum(dlci_1_disc_ul_ns_udata + dlci_2_disc_ul_ns_udata




133/712

+ dlci_3_disc_ul_ns_udata + dlci_4_disc_ul_ns_udata + dlci_5_disc_ul_ns_udata) Counters from table(s): p_nbsc_frame_relay Unit: byte

Committed Info Rate per FRBC, S9PS (frl_14)

Use: Indicates CIR. Known problems: The access rate is taken from configuration data and represents only the current setting. This may cause errors when used in historical

perspective if the settings have been changed. Formula: sum per frbc over all unlocked child nsvc (c_nsvc.committed_info_rate*16); frbc object_instance = bearer_id in p_nbsc_frame_relay Counters from table(s): p_nbsc_frame_relay




134/712

Next free (frl_14)

Random Access (rach)

Average RACH slot, S1 (rach_1)

Use: Indicates the capacity of BTS for RACH burst handling. Normally shows a constant value because it is dependent on the BTS configuration which does not change often.

Formula: avg(ave_rach_slot/res_acc_denom1) Counters from table(s): p_nbsc_res_access

Peak RACH load, average, S1 (rach_2)

Use: Indicates the absolute peak value during a measurement period. Correlates strongly with UL interference. Experiences on use: High values may suggest that MSs have problems in accessing the BTS. High values do not mean high load on SDCCH because

SDCCH is needed only if the RACH passes the detection in BTS. Known problems: The peak value does not indicate yet how many times there have been other peaks during the measurement period. Open questions: How serious the high values really are from MS point of view? Formula:




135/712

avg(peak_rach_load) Counters from table(s): p_nbsc_res_access

Peak RACH load %, S1 (rach_3)

Use: This PI indicates how close to full capacity the peak use of RACH has been during the measurement period. Experiences on use: It is quite normal that the momentary (peak) load can be high. Average RACH load is a more meaningful indicator. Formula: max(peak_rach_load) 100 * ----------------------------------- % max(ave_rach_busy/res_acc_denom1) Counters from table(s): p_nbsc_res_access

Average RACH load %, S1 (rach_4)

Use: This PI indicates how high the RACH load is on average. Experiences on use: If the value is to the order of tens of per cent there probably are access problems and MS users get, more often than usual, 3 beeps

when trying to start calls. A probable reason is UL interference. Formula: avg(ave_rach_busy/res_acc_denom3) 100 * --------------------------------- % avg(ave_rach_slot/res_acc_denom1)




136/712

Counters from table(s): p_nbsc_res_access

Average RACH busy, S1 (rach_5)

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

Formula: avg(ave_rach_busy/res_acc_denom3) Counters from table(s): p_nbsc_res_access

RACH rejected due to illegal establishment, S5 (rach_6)

Use: Most of the rejections are ghost accesses. Note that part of the ghosts have legal establishment cause and get further to SDCCH. Note that the actual ghost filtering is in BTS. Formula: sum(ghost_ccch_res - rej_seiz_att_due_dist) Counters from table(s): p_nbsc_res_access

Total RACH rejection ratio, S7 (rach_7)

Use: Ratio of all RACH rejections to total nbr of channel required messages received.




137/712

Note that counter ghost_ccch_res contains both ghosts and rejections due to distance checking. The latter one is optional feature of BSC.

Known problems: Since S9 (GPRS) the denominator should be modified to contain also the counter for PS channel required messages. Formula: sum(ghost_ccch_res - rej_seiz_att_due_dist; illegal establ. cause + bcsu_overload_lower_limit + bcsu_overload_upper_limit + bcsu_overload_deleted_rach) 100 * --------------------------------------------------------------------- % sum(ch_req_msg_rec) Counters from table(s): p_nbsc_res_access

Total RACH rejection ratio, S9 (rach_7a)

Use: Ratio of all RACH rejections to total nbr of channel required messages received. Note that counter ghost_ccch_res contains both ghosts and rejections due to distance checking. The latter one is optional feature of BSC.

Formula: sum(a.ghost_ccch_res - a.rej_seiz_att_due_dist; illegal establ. cause + a.bcsu_overload_lower_limit + a.bcsu_overload_upper_limit + a.bcsu_overload_deleted_rach) 100 * ---------------------------------------------------------------------- % sum(a.ch_req_msg_rec+b.packet_ch_req ) All counters are from the Counters from table(s):




138/712

a= p_nbsc_res_access b= p_nbsc_packet_control_unti

Total number of channel required messages, S9 (rach_8)

Use: All the RACH bursts that are passed by BTS to BSC. Formula: sum(b.ch_req_msg_rec + a.packet_ch_req) Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_res_access

Next free (rach_9)

SDCCH Drop Failures (sd)

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. These should comprise statistically 5/8 of all ghosts in GSM phase 1.

Another 3/8 of ghosts are detected already before SDCCH based on some invalid establishment cause. In GSM2 the ratio 5/8 and 3/8 is no longer valid.

- multiple seizures of SDCCH . Known problems: This counter includes also IMSI detaches which do not have a counter of their own. Formula:




139/712

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_traffic b = p_nbsc_res_access

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



- multiple seizures of SDCCH . Known problems: Includes also supplementary service request which do not have a counter of their own until S9. Formula: sum(a.sdcch_assign) - sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_loc_upd + b.sdcch_emerg_call + b.sdcch_call_re_est + imsi_detach_sdcch) Counters from table(s):




140/712

a = p_nbsc_traffic b = p_nbsc_res_access

Ghosts detected on SDCCH and other failures, S1 (sd_1b)



- multiple seizures of SDCCH . Known problems: Formula: sum(a.sdcch_assign) - sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_loc_upd + b.sdcch_emerg_call + b.sdcch_call_re_est + imsi_detach_sdcch +b.succ_seiz_supplem_serv) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access




141/712

Next free (sd_1b)

SDCCH Drop Counters (xxx)

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 coverage problems.

Triggered also if a MS user clears the call in the SDCCH phase.

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

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




142/712

1075 SDCCH_ABIS_FAIL_CALL Augmented when the BSC receives an Establish Indication the contents of which are corrupted, or more commonly when a timer (T3101, default 3 sec) expires while waiting for the Establish Indication. The Establish Indication is the first message sent from the BTS to the BSC after the MS has successfully accessed the SDCCH.

- Ghost seizures which accidentally have a valid establishment cause and are detected on SDCCH increment this counter.

- Multiple SDCCH seizures may cause these failures. If the MS has to send multiple random accesses for a call or location update, it is possible that there will be multiple reservations of SDCCH for one mobile – naturally the mobile can use only one of these and the rest will eventually time out and result in sdcch_abis_fail_call. One reason for multiple SDCCH seizures can be DL interference.

- Too short frequency&BSIC reuse distance may cause HO burst from one cell to be interpreted as RACH bursts in another cell causing false SDCCH seizures. This reason may be suspected if there are short, 2-3 second peaks with high blocking rate on SDCCH.

- A more rare yet possible reason are failing LUs.




143/712

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

1078 SDCCH_A_IF_FAIL_CALL Transactions have ended due to A interface problems. A high value can be related to IMSI detaches (in S3).

See #3 for all possible causes. SDCCH observation may be used to diagnose the cause on cell level. If this occurs in the entire network or BSS areas, use Clear Code measurement for cause analysis.

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

1035 SDCCH_LAPD_FAIL Transactions have ended due to LAPD problems (a call is lost when LAPD goes down).

TRX/TSL is blocked with cause lapd_fail due to a signalling link fault or a PCM fault.

Even if it occurs, the share is normally very low because the situation is transient.




144/712

1036 SDCCH_BT S_FAIL Transactions have ended due to BTS problems. A call is lost when TRX/TSL is blocked with cause bts_fail due to FU or CU or BCF fault or BTS or BCF reset.


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


1037 SDCCH_USER_ACT Transactions have ended due to user actions. A timeslot or TRX is locked by the user via the Top-level User Interface or BSC MML.





145/712

1039 SDCCH_NETW_ACT Transactions have ended due to a change in the radio network configuration (BCCH swap to another TRX) initiated by the BSC. The cause for the configuration change fails or locally blocked BCCH TRX.


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

Problems with the SDCCH Drop Counters

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 are counted as SDCCH_abis_fail_call and SDCCH_abis_fail_old . In practice, the latter case does not practically occur because SDCCH handovers are usually not used and particularly because phantoms do not perform handover. The percentage of SDCCH_abis_fail_call used to be very high in a low traffic network (even tens of per cent) whereas in a high traffic network the percentage settled down to around 18-20 per cent. In BTS B9, BTS RACH detection has been improved, and figures well under 10 per cent are now typical. A interface blocking not shown SDCCH failures do not include A interface blocking. In A interface blocking, an MSC clears the call without a request from a BSC. The failure is not in the BSC where the principle has been that MSC failures are not counted. Yet from an MS user’s point of view A interface blocking ends up to a failed call attempt. You can detect A interface blocking from the NSS statistics for circuit groups.




146/712

SDCCH Drop Ratio (sdr)

SDCCH Drop %, S3 (sdr_1a)

Use: To follow up the performance of SDCCH from a technical point of view. Experiences on use: 1) High SDCCH drop rates usually result from ghost accesses. A BTS decodes them from environmental or background noise and

filters out most of them. However, all of them cannot be filtered out and the RACH request is passed on to the BSC for processing and for the allocation of a SDCCH channel.

The counter GHOST CCCH RES (3030) is updated each time a CHANNEL REQUIRED is rejected because of an invalid establishment cause. In GSM ph.1 there exist altogether eight establishment causes, three of which are undefined as invalid, for example, resulting in that this counter shows only 3/8 of all the ghost accesses the BTS has decoded. For the rest, a SDCCH is allocated and this will result in SDCCH_ABIS_FAIL_CALL failure. Because of ghost attempts the SDCCH drop ratio is high with low traffic. As the amount of call attempts increases, the influence of ghosts becomes smaller and the drop ratio approaches its real value.

2) The rate of ghosts coming to SDCCH dropped when BTS B9 with improved ghost filtering was taken into use. Known problems: In SDCCH failure counters it is not possible to separate LU and call seizures. Formula: 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




147/712

SDCCH Drop %, abis fail excluded, S3 (sdr_2)

Known problems: SDCCH_ABIS_FAIL_CALL does not necessarily refer to ghosts but also, for example, to failing location updates. Formula: sum(sdcch_radio_fail+sdcch_rf_old_ho+sdcch_user_act+sdcch_bcsu_reset+ sdcch_netw_act +sdcch_bts_fail+ sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old) 100 * ------------------------------------------------------------------- % sum(sdcch_assign+sdcch_ho_seiz) - sum(sdcch_abis_fail_call+sdcch_abis_fail_old) Counters from table(s): p_nbsc_traffic

Illegal establishment cause %, (sdr_3)

Use: This PI gives you number of ghost accesses which try to seize SDCCH but are rejected before seizing SDCCH due to an illegal establishment cause.

Formula: 100* a.ghost_CCCH_res / b. sdcch_seiz_att % Counters from table(s): a = p_nbsc_res_access b = p_nbsc_traffic




148/712

Illegal establishment cause %, (sdr_3a)


Formula: 100 * (ghost_CCCH_res - rej_seiz_att_due_dist) / ch_req_msg_rec % Counters from table(s): p_nbsc_res_access

Illegal establishment cause %, (sdr_3b)


Formula: sum(a.ghost_CCCH_res - a.rej_seiz_att_due_dist) 100 * ------------------------------------------------- % sum(b.sdcch_assign + b.sdcch_ho_seiz)% Counters from table(s): a = p_nbsc_res_access b = p_nbsc_traffic

SDCCH drop ratio without timer T3101 expiry % (sdr_4)

Description: Ratio of dropped SDCCH without considering the drops caused by timer T3101.




149/712

Use: See sdr_1a. . Known Problems: See sdr_1a. Formula: sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act + a.sdcch_bcsu_reset+ + a.sdcch_netw_act + a.sdcch_abis_fail_call + a.sdcch_abis_fail_old + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old - b. T3101_EXPIRED) 100 * -------------------------------- % sum(sdcch_assign+sdcch_ho_seiz) a = p_nbsc_traffic b = p_nbsc_service Counters from table(s): p_nbsc_traffic p_nbsc_service




150/712

Next free (sdr_5)

Setup Success Ratio (cssr)

SDCCH, TCH setup success %, S4 (cssr_2)

Use: This PI shows the setup success ratio including SDCCH and TCH. Works also in the case of DR. Possible fault cases: - faulty DSP in BTS TRX Experiences on use: 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 TCH at all. This causes problems in special cases when there are many LUs but few

calls. The problems in calls are hidden by a great number of LUs which receive SDCCH successfully. Troubleshooting: You can use SDCCH and TCH observations to see which one is failing. However, note that this is a time-consuming task. Formula: sum(call_setup_failure) 100* ( 1 - ----------------------------------------) % sum(setup_succ+call_setup_failure) Counters from table(s): p_nbsc_service




151/712

Next free (cssr_3)

TCH Drop Failures

TCH Drop Call Counters

TCH drop calls after TCH seizuure are counted as the sum of the following counters: ID Name DESCRIPTION

1013 TCH_RADIO_FAIL • Radio link timeout

• Release indication from MS.

• MS moves out from timing advance

• TCH assignment failure where Establish Indication has been received but Assignment Complete has not been received

This counter is typical in connection with coverage problems. This failure type is usually the dominating one.

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




152/712

1084 TCH_ABIS_FAIL_CALL • missing ack of channel activation

• missing establishment indication

• reception of error indication

• corruption of messages

• measurement results no longer received from BTS

• excessive timing advance

• missing HO detection

• T3107 (assignment completely missing) expiry

• T3109 expiry As in this case the drop happens in the release phase, the MS user cannot see the situation as a drop call.

The BTS suffering from this failure can be faulty or their TCH TRX suffers from bad interference (TCH assignment fails).

See #3 for all possible causes that trigger this counter.

NOTE: If FACCH call setup is used, we may expect that we start to see ghost seizures incrementing this counter because the signalling tries to use SDCCH instead of TCH.




153/712

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

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

• abnormal clear received due to A interface (reset circuit, SCCP clear). For example BSU reset in MSC causes MSC to send 'reset circuit' message.

NOTE: there have been cases where the MSC of another vendor in inter-MSC handovers has caused high values even though the handovers have been successful.

See #3 for all possible causes that trigger this counter.

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

Note: Can be updated when GSM timer T8 expires in the source BSC during an external handover.




154/712

1029 TCH_TR_FAIL • Transcoder failure during a call attempt

This counter is updated only when BTS sends 'connection failure' with cause 'remote transcoder failure' and call is released due to this.

NOTE: If this failure is related to a transcoder, you can see its share to be high for one BSC. Another possibility is that the problem lies in a BTS. Also interruptions of the transmission may cause this failure (alarms may be filtered out in BSC or OMC to reduce the number of alarms due to disturbance).

In analysing the problem, you may find it helpful to check the pattern over a longer period of time.

NOTE: In S6 the portion of this failure has decreased due to improvements in transcoders.

NOTE: In S7 there will be a feature (parameter) to set how many 'connection failures' should be received before a call is released. Thus this failure becomes more rare in case of disturbances in transmission.




155/712

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

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

Even if it occurs, the share is very small because only ongoing calls are dropped when 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 it occurs, the share is very small because only ongoing calls are dropped when a BTS fails.

1049 TCH_BCSU_RESET TRX is blocked by BCSU reset.

Even if it occurs, the share is very small because only ongoing calls are dropped when BCSU resets.




156/712

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

Even if it occurs, the share is very small because only ongoing calls are dropped when the blocking command is given.

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

Even if it occurs, the share is very small because only ongoing calls are dropped when reconfiguration is executed.

1081 TCH_ACT_FAIL_CALL Channel activation nack received.

To see what DX causes can trigger the counters above, see #4. The problem especially with failure classes Abis and A interface is that they are triggered by many different causes. To analyse the case in question, TCH observations may be used. As there are limitations on how to set the observations, the analysis is more time-consuming. If the problem is not cell specific but related to the entire network or BSS areas, you could also use the Clear Code measurement. *_OLD counters are related to the HO situation when the return to old channel fails causing a call to drop. Thus, these counters reflect the amount of call drops in handovers.




157/712

Drop Call Ratio

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

Drop-out Ratio

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

Problems with the Drop Call Counters

See document about experiences.

Drop Call Failures (dcf)

TCH drop calls in HO, S2 (dcf_2)

Open questions: Claims of cases when the TCH_A_IF_OLD has not been a drop call have been made. Formula: sum(tch_rf_old_ho+ tch_abis_fail_old+tch_a_if_fail_old+tch_tr_fail_old) Counters from table(s): p_nbsc_traffic




158/712

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

Known problems: Accuracy is not good. Formula: sum(bsc_o_drop_calls) Counters from table(s): p_nbsc_ho

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

Known problems: Accuracy is not good. Formula: sum(cell_drop_calls) Counters from table(s): p_nbsc_ho

TCH drop calls in inter BSC HO, S4 (dcf_5a)

Formula: Drops in outgoing HO (all types including SDCCH-SDCCH) - failed outgoing SDCCH HO (always drops) - Drop Calls in BSC controlled outgoing HO - Drop Calls in intra-cell HO = sum(a.int_intra_ho_source_fail+a.int_inter_ho_source_fail+a.ext_ho_source_fail)




159/712

- sum(b.msc_o_sdcch_at - b.msc_o_sdcch + b.bsc_o_sdcch_at - b.bsc_o_sdcch) - sum(b.bsc_o_drop_calls) - sum(b.cell_drop_calls) Counters from table(s): a = p_nbsc_service b = p_nbsc_ho

TCH drop calls in inter BSC HO, S4 (dcf_5b)

Note: In S7/T11 there came a new counter msc_o_drop_call_ho (4107). Formula: Drops in outgoing HO (all types including SDCCH-SDCCH) - failed outgoing SDCCH HO (always drops) - failed DR - Drop Calls in BSC controlled outgoing HO - Drop Calls in intra-cell HO = sum(a.int_intra_ho_source_fail+a.int_inter_ho_source_fail+a.ext_ho_source_fail) - sum(b.msc_o_sdcch_at - b.msc_o_sdcch + b.bsc_o_sdcch_at - b.bsc_o_sdcch) -sum(b.msc_o_sdcch_tch_at - b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch_at - b.bsc_o_sdcch_tch+ b.cell_sdcch_tch_at - b.cell_sdcch_tch) - sum(b.bsc_o_drop_calls) - sum(b.cell_drop_calls) Counters from table(s): a = p_nbsc_service b = p_nbsc_ho




160/712

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

Known problems: Use on the BTS level. On the area level causes double counting. Accuracy is not good. Formula: sum(bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls) Counters from table(s): p_nbsc_ho

Drop calls in BSC incoming HO, S3 (dcf_7)

Known problems: Accuracy is not good. Formula: sum(bsc_i_drop_calls) Counters from table(s): p_nbsc_ho

xxxx (dcf_8)

Drop calls in MSC outgoing HO, S3 (dcf_9)

Known problems: The formula has given negative values. Formula:




161/712

All calls dropped in HOs [dcf_2] - calls dropped in BSC i HO [dcf_7] - calls dropped in BSC o HO [dcf_3] - calls dropped in intra-cell HO [dcf_4] = sum(a.tch_rf_old_ho+ a.tch_abis_fail_old+a.tch_a_if_fail_old+a.tch_tr_fail_old) - sum(b.bsc_i_drop_calls) - sum(b.bsc_o_drop_calls) - sum(b.cell_drop_calls) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

Drop calls in MSC outgoing HO, (dcf_10)

Formula: (Failed outgoing HO,drop call) - (BSC outgoing HO, drop call)

= (Outgoing HO attempts - successes - returns to old channel) - (BSC outgoing HO, drop call)

= 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) - sum(msc_o_fail_ret + bsc_o_fail_ret) - sum(bsc_o_drop_calls) Counters from table(s): p_nbsc_ho




162/712

TCH drop calls in HO, S7 (dcf_11)

Use: BTS level. Known problems: On the area level causes double counting. Accuracy is not good. Formula: sum(msc_o_call_drop_ho+bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls) Counters from table(s): p_nbsc_ho

Next free (dcf_12)

TCH Drop Call % (dcr)

TCH drop call %, area, S2 (dcr_1)

Known problems: Shows too pessimistic values since in the nominator the tch_bss_fail also includes non-call dropping failures. Formula: sum(tch_radio_fail + tch_bss_fail + tch_rf_old_ho + tch_tr_fail + tch_tr_fail_old + tch_act_fail) = 100 * ---------------------- % sum(tch_norm_seiz) Counters from table(s):




163/712

p_nbsc_traffic

TCH drop-out %, BTS level, S2 (dcr_2)

Known problems: Shows too pessimistic values since in the nominator the tch_bss_fail also includes non-call dropping failures. Formula: sum(tch_radio_fail + tch_bss_fail + tch_rf_old_ho + tch_tr_fail + tch_tr_fail_old + tch_act_fail) = 100 * -------------------------------- % sum(tch_norm_seiz + tch_ho_seiz) Counters from table(s): p_nbsc_traffic

TCH drop call %, area, S3 (dcr_3)

Experiences on use: In good networks where optimisation has been done already for two to three years, values have been around 2 to 3 per cent (and in networks in which no optimisation has been done yet the values remain above 10 per cent. A value of 5 per cent is achievable in many networks despite their bad initial coverage planning. Interference also raises the figure. Be careful when you give any promises concerning quality since the factors (whether caused by the customer or Nokia) can be time-consuming and expensive to prove.

If used on the cell level, the values can be even over 100 per cent if a cell takes HOs in but then drops them. Known problems: 1) Some failures in the release phase are included in this formula (tch_abis_fail_call) but are, in fact, not perceived as drop

calls by the MS user.




164/712

2) tch_norm_seiz does not mean that the MS is on TCH. It means that TCH has been successfully seized. Some mobiles never appear to the TCH because

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

2b) the mobile fails or 2c) something else goes wrong. 3) Call re-establishment is not taken into account Formula: 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(tch_norm_seiz) Counters from table(s): p_nbsc_traffic




165/712

TCH drop call %, area, S3 (dcr_3a)

Experiences on use: See dcr_3. Known problems: Does not count call re-establishments. Formula: 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(tch_norm_seiz) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

TCH drop call %, area, real, S3 (dcr_3b)

Use: On the area level. Call re-establishment considered.




166/712

Experiences on use: See dcr_3. Call re-establishments can markedly improve the drop call ratio (for example, from 2.5 to 2.0 %). Since this is an improvement from the MS user’s point of view, this figure suits well to be used in management reports.

Known problems: See dcr_3. Formula: 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) ;(call re-establishments) 100 * ---------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR) - sum(b.sdcch_call_re_est) ;(call re-establishments) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho




167/712

TCH drop call %, area, S3 (dcr_3c)

Use: On the area level. FACCH call setup considered. Experiences on use: See dcr_3. The best value reported for area: 2.3 %. Known problems: 1) Some failures in release phase are included in this formula (tch_abis_fail_call) but are, in fact, not perceived as drop calls

by the MS user. 2) tch_norm_seiz does not mean that the MS is on TCH. It means that TCH has been successfully seized. Some mobiles never

appear to the TCH because 2a) the call is cleared by user (probability is higher if call setup takes a long time, and thus DR and queuing can increase this share) or 2b) the mobile fails or 2c) something else goes wrong. 3) TCH failure counters are not triggered if call is cleared by pre-emption (1st priority call requested to be established, all TCH

seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered. Formula: 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




168/712

+ tch_act_fail_call) 100 * ------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR) + sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

TCH drop call %, area, real, S3 (dcr_3d)

Use: On the area level. Call re-establishment and FACCH call setup considered. Experiences on use: See dcr_3. Call re-establishments can markedly improve the drop call ratio (for, example, from 2.5 to 2.0 %). Since this is an

improvement from the MS user’s point of view, this figure suits better to management reports. Known problems: See dcr_3g. The assumption that all call re-establishments take place due to failures on TCH is probably not 100 % correct. However, there is no

counter to see which part of failures could have happened on SDCCH and therefore the formula cannot be improved (at least not with S6 counters).

Formula: 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




169/712

+ 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) ;(call re-establishments) 100 * --------------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup - sum(b.sdcch_call_re_est) ;(call re-establishments) Counters from table(s): a = p_nbsc_traffic, b = p_nbsc_res_access c = p_nbsc_ho

TCH drop call %, area, real, S3 (dcr_3e)

Latest modification: In the previous formula dcr_3d the impact of call re-establishments in FACCH call setup was not considered (b.tch_call_re_est)

Use: On the area level. Call re-establishment and FACCH call setup considered. Experiences on use: See dcr_3. Call re-establishments can markedly improve the drop call ratio (for example, from 2.5 to 2.0 %). Since this is an

improvement from the MS user’s point of view, this figure suits better to management reports. Known problems: See dcr_3g. It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH. Formula:




170/712

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) ;(calls started via DR) + 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

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

Use: On the area level. Experiences on use: See dcr_3. Call re-establishments can markedly improve the drop call ratio (for example, from 2.5 to 2.0 %). Since this is an

improvement from the MS user’s point of view, this figure suits better to management reports. Known problems: 1) See dcr_3g




171/712

2) It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH. 3) The counters used to compensate re-establishments are the ones that indicate re-establishment attempts, not the successful re-

establishments. In S7/T11 re-establishments can be considered accurately (see dcr_3j). 4) On the cell level it can happen that the call is re-established in a different cell than it was dropped, resulting in inaccuracy. Formula: 100 - csf_4p =

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ. 100 * ------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;calls started directly in the cell + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;DR calls + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls - sum(b.sdcch_call_re_est+b.tch_call_re_est) ;call re-establ.




172/712

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

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

Use: On the area level. Experiences on use: In good networks where optimisation has been done already for two to three years, values have been around 2 to 3 per cent (and in

networks in which no optimisation has been done yet the values remain even above 10 per cent. A value of 5 per cent is achievable in many networks despite their bad initial coverage planning. Interference also raises the figure. Be careful when setting the target values since the factors (whether caused by the customer or Nokia) can be time-consuming and expensive to prove.

If used on the cell level, the values can be even over 100 per cent if a cell takes HOs in but then drops them. Known problems: 1) Some failures in the release phase are included in this formula (tch_abis_fail_call) but are, in fact, not perceived as drop

calls by the MS user. 2) tch_norm_seiz does not mean that the MS is on TCH. It means that TCH has been successfully seized. Some mobiles never

appear to the TCH because 2a) the call is cleared by the user (the probability is higher if call setup takes a long time, and thus DR and queuing can increase this

share) or 2b) the mobile fails or 2c) something else goes wrong. 3) TCH failure counters are not triggered if a call is cleared by pre-emption (1st priority call requested to be established, all TCH

seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered. 4) It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH.




173/712

5) On the cell level it can happen that the call is re-established in a different cell than it was dropped, resulting in inaccuracy.

Formula: 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(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho




174/712

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

Use: On the area level. Experiences on use: See dcr_3. Call re-establishments can markedly improve the drop call ratio (for example, from 2.5 to 2.0 %). Since this is an

improvement from the MS user’s point of view, this figure suits better to management reports. Known problems: See dcr_3g.

- It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH. Formula: 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.tch_re_est_assign) ;(call re-establishments) 100 * ------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup - sum(b.tch_re_est_assign) ;(call re-establishments)




175/712

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service c = p_nbsc_ho

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

Use: On the area level. This KPI indicates how much calls are dropped after TCH seizure. Experiences on use: In good networks where optimisation has been done already for two to three years, values have been around 2 to 3 per cent (and in

networks in which no optimisation has been done yet the values remain even above 10 per cent. A value of 5 per cent is achievable in many networks despite their bad initial coverage planning. Interference also raises the figure. Be careful when setting the target values since the factors (whether caused by the customer or Nokia) can be time-consuming and expensive to prove.

If used on cell level, the values can be even over 100 per cent if a cell takes HOs in but then drops them. Known problems: 1) Some failures in the release phase are included in this formula (tch_abis_fail_call) but are, in fact, not perceived as drop

calls by the MS user. 2) tch_norm_seiz does not mean that the MS is on TCH. It means that TCH has been successfully seized. Some mobiles never

appear to the TCH because 2a) the call is cleared by the user (the probability is higher if call setup takes a long time, and thus DR and queuing can increase this

share) or 2b) the mobile fails or 2c) something else goes wrong. 3) TCH failure counters are not triggered if a call is cleared by pre-emption (1st priority call requested to be established, all TCH

seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered.




176/712

Formula: 100-csf_4u =

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call+ + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * ----------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Ref.1. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.




177/712

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

Use: On the area level. Experiences on use: In good networks where optimisation has been done already for two to three years, values are around 2 to 3 per cent. In networks in

which no optimisation has been done yet the values are even as high as 10 per cent. A value of 5 per cent is achievable in many networks despite their bad initial coverage planning. The values in the best networks are below 1.5%. Interference also raises the figure. Be careful when you give promises concerning quality since the factors (whether caused by the customer or Nokia) can be time-consuming and expensive to prove.

If used on the cell level, the values can be even over 100 per cent if a cell takes handovers in but then drops them. Call re-establishments can markedly improve the drop call ratio (for example, from 2.3 to 2.0 %). Since this is an improvement from the MS user’s point of view, this figure suits better to management reports. The biggest reason for having low figures usually is in basic network planning. If coverage is not adequate this KPI cannot show good values.

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

2) tch_norm_seiz does not mean that the MS is on TCH. It means that TCH has been successfully seized. Some mobiles never appear to the TCH because

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

2b) the mobile fails or 2c) something else goes wrong. 3) TCH failure counters are not triggered if call is cleared by pre-emption (1st priority call requested to be established, all TCH

seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered.




178/712

4) It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH. 5) On the cell level it can happen that the call is re-established in a different cell than it was dropped, resulting in inaccuracy. Formula: 100-csf_4v = sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.tch_re_est_assign) ;call re-establishments 100 * ----------------------------------------------------------- % sum(a.tch_norm_seiz) ;calls started directly in the cell + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;DR calls - sum(a.tch_succ_seiz_for_dir_acc) ;ref.1 + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls - sum(b.tch_re_est_assign) ;call re-establishments Counters from table(s): a = p_nbsc_traffic




179/712

b = p_nbsc_service c = p_nbsc_ho

Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch. TCH drop-out %, BTS level, S3 (dcr_4)

Known problems: The same as in dcr_3g. Formula: 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(tch_norm_seiz + tch_ho_seiz) Counters from table(s): p_nbsc_traffic




180/712

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

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

Known problems: See dcr_3g. Formula: sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * ------------------------------------------------------------------ % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch);(calls started via DR) + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(ext. TCH-TCH HO in) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho




181/712

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

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

Known problems: See dcr_3g. Formula: 100 - csf_4q = sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * --------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls + sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH HO in)




182/712

Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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


Known problems: See dcr_3g. Formula:

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * ----------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls)




183/712

+ sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls) + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO from other cells) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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

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

Known problems: See dcr_3g. Formula: 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)




184/712

100 * ------------------------------------------------------------ % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls) + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) - sum(c.msc_o_tch_tch + c.bsc_o_tch_tch) ;(TCH-TCH HO net in from other cells) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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


Known problems: See dcr_3g. Formula: 100 - csf_4y =

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




185/712

+ a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * ------------------------------------------------------ % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO from other cells) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch. TCH drop-out %, BTS level, before call re -establishment, S7 (dcr_4f)

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

Known problems: See dcr_3g. Formula: sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call




186/712

+ a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 * ------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls) + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) - sum(c.msc_o_tch_tch + c.bsc_o_tch_tch) ;(TCH-TCH HO net in from other cells) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5)

Use: On the area level. Tells the ratio of calls dropped while A and B are talking, that is after conn_ack. Theoretically should always be less than dcr_3 or dcr_3a. Results from networks 2 to 6 %.




187/712

Known problems: 1) Does not work on the BTS level (handovers). Accurate on the BSC and PLMN level after a bug was corrected 2) If call re-establishment is active and occurs, the conver_started is triggered once and dropped_ calls only once. After

the first call re-establishment the dropped_calls counter is no longer incremented in this call no matter if the call stays or drops. This means that in this case seen from counters, the call looks like a dropped call. In fact, from the MS user’s point of view it is impossible to know whether it was dropped or not (does call re-establishment save the call or not).

3) Subscriber clear during HO is counted as a dropped call. (correction at least in S6) 4) Due to an error in the mapping table also blocking in the case of an external HO has been counted as a dropped call (correction

planned in S6, possibly in S5) 5) External HOs (inter BSC handovers) trigger the conver_started counter in a target cell. Therefore on network level the ratio does

not correctly illustrate the dropped conversation ratio from the MS’s point of view. Formula: sum(dropped_calls) 100 * -------------------- % sum(conver_started) Counters from table(s): p_nbsc_service

TCH dropped conversation) %, area, S4-> (dcr_5a)

Use: On the area level. Tells the ratio of calls dropped while A and B are talking, that is after conn_ack. Inter-BSC handovers are subtracted in the denominator because they trigger conver_started. Compensation is 100% true only if the area has no inter-BSC HOs from outside the area.

Theoretically should always be less than dcr_3 or dcr_3a. Results from networks 2 to 6 %.




188/712

Known problems: See dcr_5. 1) conver_started is not triggered for call re-establishments. dropped_calls is triggered once for the first re-establishment. After that setup_failure is triggered if the call is a dropped call. If a call is ‘saved’ by re-establishment multiple times, setup_failure will be triggered several times accordingly. 2) Drop call by pre-emption (first priority call request to be established, all TCH seized, lower priority calls on) triggers dropped_calls.

Therefore this counter does not indicate only technical drops. Future: In S7 re-establishments can be compensated. Formula: 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

TCH dropped conversation %, area, re-est. considered, S7-> (dcr_5b)

Use: On the area level. Tells the ratio of calls dropped while A and B are talking, that is after conn_ack. Inter-BSC handovers are subtracted in the denominator because they trigger conver_started. Compensation is 100% true only if the area has no inter-BSC HOs from outside the area.

Theoretically should always be less than dcr_3 or dcr_3a. Known problems: See dcr_5.




189/712

1) conver_started is not triggered for call re-establishments. dropped_calls is triggered once for the first re-establishment. After that setup_failure is triggered if the call is a dropped call. If a call is ‘saved’ by re-establishment multiple times, setup_failure will be triggered several times accordingly. 2) Drop call by pre-emption (first priority call request to be established, all TCH seized, lower priority calls on) triggers dropped_calls.

Therefore this counter does not indicate only technical drops. Future: Formula: sum(b.dropped_calls) - sum(tch_re_est_release) 100 * -------------------------------------------------- % sum(b.conver_started) - sum(a.msc_i_tch_tch) Counters from table(s): a = p_nbsc_ho b = p_nbsc_service

TCH failure %, S4 (dcr_6)

Use: Includes TCH setup phase and conversation. Known problems: tch_fails is not necessarily a dropped call but can be, for example, a failure in the target cell of a handover when the call returns to

the old channel. It is also possible to have a TCH failure after a MS has released the call. Formula: sum(tch_fails) 100 * -------------------- %




190/712

sum(tch_seizures) Counters from table(s): p_nbsc_service

Total HO drop %, S4 (dcr_7)

Known problems: Includes any type of HO (also SDCCH-SDCCH) and failure does not necessarily mean a drop. Does not precisely indicate drop calls in handovers. Formula: sum(int_intra_ho_source_fail + int_inter_ho_source_fail + ext_ho_source_fail) 100 * (-------------------------------) % sum(int_intra_ho_source_fail + int_intra_ho_succ + int_inter_ho_source_fail + int_inter_ho_succ + ext_ho_source_fail + ext_ho_source_succ) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, without RE, area level, S7 (dcr_8)

Use: This formula has been developed to better match with the formulas of other vendors Known problems: 1) The formula is not reliable on hourly level because assigns and releases can happen in different measurement periods. In the worst

case this can cause a negative value.




191/712

2) Not good for BTS level because the denominator counts only started new calls (there can be a lot of handovers in, too). 3) The following bugs that affect the formula have been corrected in S9 CD6.0 3a) Counter TCH_NORM_RELEASE (c57035) is not updated if during the call there has been a MSC controlled HO with cause

‘pre-emption’ or ‘traffic’. 3b) TCH_NEW_CALL_ASSIGN (c57033) is not updated in the case of MSC controlled SDCCH-TCH HO with cause ‘pre-

emption’ or ‘traffic’. Formula: Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls sum(tch_new_call_assign + tch_ho_assign - tch_norm_release - tch_ho_release) 100 * -------------------------- % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S7 (dcr_8a)

Use: This formula has been developed to better match with the formulas of other vendors Known problems: The denominator is not correct. For example, with one call and one re-establishment it goes to 0! Formula dcr_8b has been defined to

fix this problem. Formula:




192/712

Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls sum(tch_new_call_assign + tch_ho_assign - tch_norm_release - tch_ho_release - tch_re_est_assign) 100 * ------------------------------------------- % sum(tch_new_call_assign - tch_re_est_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S7 (dcr_8b)

Use: This formula is developed to better match with the formulas of other vendors Known problems: see dcr_8 Formula: Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls sum(tch_new_call_assign + tch_ho_assign - tch_norm_release - tch_ho_release - tch_re_est_release) 100 * -------------------------- % sum(tch_new_call_assign)




193/712

Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, without RE, area level, S10.5 (dcr_8c)

Use: This formula is developed to better match with the formulas of other vendors Known problems: See dcr_8. Formula: Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls sum(spare057044) 100 * ------------------------ % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, without RE, area level, S11 (dcr_8d)

Use: This formula is developed to better match with the formulas of other vendors Known problems: See dcr_8. Formula: Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls




194/712

sum(drop_after_tch_assign) 100 * --------------------------- % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S10.5 (dcr_8e)

Origin: Based on dcr_8b Juhani Neva 1.7.2003 Description: TCH drop call %, after TCH assignment, considering re-establishments. Use: This formula is developed to better match with the formulas of other vendors Known problems: See dcr_8. Formula: Drops after TCH assignment considering re-establishments 100 * -------------------------------------------------------- % = TCH assignments for new calls sum(spare057044 - tch_re_est_release) 100 * ------------------------------------- % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S11 (dcr_8f)

Origin: Based on dcr_8b Juhani Neva 1.7.2003 Description: TCH drop call %, after TCH assignment, without considering re-establishments. Use: This formula is developed to better match with the formulas of other vendors




195/712

Known problems: See dcr_8. Formula: Drops after TCH assignment considering re-establishments 100 * -------------------------------------------------------- % = TCH assignments for new calls sum(drop_after_tch_assign - tch_re_est_release) 100 * ----------------------------------------------- % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S10.5 (dcr_8g)

Origin: Based on dcr_8b Juhani Neva 1.7.2003 Description: TCH drop call %, after TCH assignment, considering re-establishments. Use: This formula is developed to better match with the formulas of other vendors Known problems: See dcr_8. Formula: Drops after TCH assignment considering re-establishments 100 * -------------------------------------------------------- % = TCH assignments for new calls sum(spare057044 - TCH_RE_EST_ASSIGN) 100 * ------------------------------------- % sum(tch_new_call_assign) Counters from table(s):




196/712

p_nbsc_service

TCH drop call %, after TCH assignment, with RE, area level, S11 (dcr_8h)

Origin: Based on dcr_8b Juhani Neva 1.7.2003 Description: TCH drop call %, after TCH assignment, without considering re-establishments. Use: This formula is developed to better match with the formulas of other vendors Known problems: See dcr_8. Formula: Drops after TCH assignment considering re-establishments 100 * -------------------------------------------------------- % = TCH assignments for new calls sum(drop_after_tch_assign - TCH_RE_EST_ASSIGN) 100 * ----------------------------------------------- % sum(tch_new_call_assign) Counters from table(s): p_nbsc_service

Drop call ratio %, S4 (dcr_9)

Known problems: Difficult to implement in any tool. Comparison of different areas may not be sensible. Formula: Drops 100 * ------------------------------------------ Total call time / (Area Avg. Call length) sum(a.tch_radio_fail + a.tch_rf_old_ho




197/712

+ 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 * ---------------------------------------------------------------- % (avg(c.ave_busy_tch/c.res_av_denom14) * avg(period_duration)*60) /(Area Avg. Call length) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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

Use: On the area and BTS level. Known problems: The formula works for the 60 min period. Formula: Drops -------------------------- = Traffic (Erlang hours sum)

sum(a.tch_radio_fail + a.tch_rf_old_ho




198/712

+ a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) --------------------------------------------------------------- sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(period_duration)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_avail

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

Use: On the area and BTS level. Known problems: The formula works for the 60 min period. The counters used to compensate re-establishments are the ones that indicate re-establishment attempts, not the successful re-

establishments. Formula: Drops- re-establishments -------------------------- = Traffic (Erlang hours sum)

sum(a.tch_radio_fail




199/712

+ a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(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)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_avail c = p_nbsc_res_access

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

Use: On the area and BTS level. Known problems: The formula works for the 60 min period. Formula:

Drops - re-establishments -------------------------- = Traffic (Erlang hours sum)




200/712

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(c.tch_re_est_assign) ;call re-establishments -------------------------------------------------------------------- sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(b.period_duration)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_avail c = p_nbsc_service

Erlang minutes per drop, S4 (dcr_11)

Known problems: This formula cannot use the same report layout as those where drops are in the numerator. Use: On the area and BTS level. Formula: Call time in minutes ---------------------- =




201/712

Drops sum(b.period_duration * b.ave_busy_tch/b.res_av_denom14) -------------------------------------------------------- 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) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_avail

Dropped HO ratio, TCH (dcr_12)

Known problems: Use: On the area and BTS level. Formula: sum(a.tch_rf_old_ho + a.tch_abis_fail_old + a.tch_a_if_fail_old + a.tch_tr_fail_old) 100 * --------------------------------------------------------------- % sum(b.msc_o_tch_tch_at + b.bsc_o_tch_tch_at + b.cell_tch_tch_at)




202/712

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

TCH Rf loss ratio (dcr_13)

Known problems: Use: On the area and BTS level. Formula: sum(TCH_RADIO_FAIL + TCH_RF_OLD_HO) 100 * ---------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

TCH Rf loss in HO - ratio, IUO (dcr_14)

Known problems: Use: On the level of TRX, super/regular layer or BTS. Formula: sum(TCH_FAIL_CALL_HO) 100 * ---------------------- %




203/712

sum(tch_succ_seiz) Counters from table(s): p_nbsc_underlay

TCH Rf loss - ratio, IUO (dcr_15)

Known problems: Use: On the level of TRX, super/regular layer or BTS. Formula: sum(TCH_RADIO_FAIL) 100 * ---------------------- % sum(tch_succ_seiz) Counters from table(s): p_nbsc_underlay

Transcoder failure ratio, FR (dcr_16)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_FR_RATE1) 100 * ---------------------------------- % sum(TCH_FULL_SEIZ_SPEECH_VER1)




204/712

Counters from table(s): p_nbsc_traffic

Transcoder failure ratio, EFR (dcr_17)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_FR_RATE2) 100 * ---------------------------------- % sum(TCH_FULL_SEIZ_SPEECH_VER2) Counters from table(s): p_nbsc_traffic

Status: OK Transcoder failure ratio, HR (dcr_18)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_HR_RATE1) 100 * ---------------------------------- % sum(TCH_HALF_SEIZ_SPEECH_VER1) Counters from table(s):




205/712

p_nbsc_traffic

Transcoder failure ratio, AMR FR (dcr_19)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_FR_RATE3) 100 * ---------------------------------- % sum(TCH_FULL_SEIZ_SPEECH_VER3) Counters from table(s): p_nbsc_traffic

Transcoder failure ratio, AMR HR (dcr_20)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_HR_RATE3) 100 * ---------------------------------- % sum(TCH_HALF_SEIZ_SPEECH_VER3) Counters from table(s):




206/712

p_nbsc_traffic

Transcoder failure ratio, (dcr_21)

Known problems: Use: Formula: sum(TCH_ENDED_DUE_TRANSC_FR_RATE1 + TCH_ENDED_DUE_TRANSC_HR_RATE1 + TCH_ENDED_DUE_TRANSC_FR_RATE2 + TCH_ENDED_DUE_TRANSC_FR_RATE3 + TCH_ENDED_DUE_TRANSC_HR_RATE3") 100 * ------------------------------------------------------------------ % sum(TCH_FULL_SEIZ_SPEECH_VER1 + TCH_HALF_SEIZ_SPEECH_VER1 + TCH_FULL_SEIZ_SPEECH_VER2 + TCH_FULL_SEIZ_SPEECH_VER3 + TCH_HALF_SEIZ_SPEECH_VER3) Counters from table(s): p_nbsc_traffic

Call failures share of transcoder failures, (dcr_22)

Use: Indicates the share of transcoding failures that happen in TCH seizure for call as a percentage. These are call drops. Formula: Sum(TCH_TR_FAIL) 100 * ----------------------------------------------- % sum(TCH_TR_FAIL+TCH_TR_FAIL_OLD+TCH_TR_FAIL_NEW)




207/712


HO target share of transcoder failures, (dcr_23)

Use: Indicates the share of transcoding failures that happen in the target cell in TCH seizure for HO as a percentage. These are not call drops.

Formula: Sum(TCH_TR_FAIL_NEW) 100 * ---------------------------------------------------- % sum(TCH_TR_FAIL + TCH_TR_FAIL_OLD + TCH_TR_FAIL_NEW) Counters from table(s): p_nbsc_traffic

HO source share of transcoder failures, (dcr_24)

Use: Indicates as a percentage the share of transcoding failures that happen in the source cell in a HO when a MS fails to return to the old cell and a call drops.

Formula: Sum(TCH_TR_FAIL_OLD) 100 * --------------------------------------------------- % sum(TCH_TR_FAIL + TCH_TR_FAIL_OLD + TCH_TR_FAIL_NEW) Counters from table(s): p_nbsc_traffic




208/712

Transcoder failures, (dcr_25)

Use: Formula: sum(TCH_TR_FAIL + TCH_TR_FAIL_OLD + TCH_TR_FAIL_NEW) Counters from table(s): p_nbsc_traffic

Drops per erlang, before re-establishment, S7 (dcr_26)

Description: TCH drops per erlang, before re-establishment. Use: On the area and BTS level. Known problems: The formula works for the 60 min period. Formula: Drops - re-establishments -------------------------- = Traffic (Erlang hours sum)

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




209/712

+ a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) ------------------------------------------------------------------ sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(b.period_duration)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_avail c = p_nbsc_service

Erlang minutes per drop, S7 (dcr_27)

Known problems: see dcr_5a Use: On the area and BTS level. Formula: Call time in minutes ---------------------- = Drops sum(a.period_duration * a.ave_busy_tch/a.res_av_denom14) -------------------------------------------------------- sum(b.dropped_calls) Counters from table(s): b = p_nbsc_service a = p_nbsc_res_avail




210/712

Erlang minutes per drop after re-establishment, S7 (dcr_28)

Known problems: see dcr_5b Use: On the area and BTS level. Formula: Call time in minutes ---------------------- = Drops sum(a.period_duration * a.ave_busy_tch/a.res_av_denom14) -------------------------------------------------------- sum(b.dropped_calls - b.tch_re_est_release) Counters from table(s): b = p_nbsc_service a = p_nbsc_res_avail

Next free (dcr_29)

Handover (ho)

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

Formula: sum(ho_succ_to_reg_freq) 100 * -------------------------- % sum(ho_succ_from_reg_freq) Counters from table(s): p_nbsc_underlay




211/712

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

Formula: sum(ho_att_from_reg_freq) Counters from table(s): p_nbsc_underlay

HO attempts from super to regular, S4 (ho_3)

Formula: sum(ho_att_to_reg_freq) Counters from table(s): p_nbsc_underlay

Share of HO attempts from super to regular due to DL quality, S4 (ho_4)

Formula: sum(att_from_super_dl_qual) 100 * ------------------------------------------------------ % sum(att_from_super_dl_qual + att_from_super_dl_if + att_from_super_ul_if + att_from_super_bad_ci) Counters from table(s): p_nbsc_underlay




212/712

Share of HO attempts from super to regular due to DL interference, S4 (ho_5)

Formula: sum(att_from_super_dl_if) 100 * ------------------------------------------------------ % sum(att_from_super_dl_qual + att_from_super_dl_if + att_from_super_ul_if + att_from_super_bad_ci) Counters from table(s): p_nbsc_underlay

Share of HO attempts from super to regular due to UL interference, S4 (ho_6)

Description: Share of HO attempts from super to regular due to UL interference. Formula: sum(att_from_super_ul_if) 100 * ------------------------------------------------------ % sum(att_from_super_dl_qual + att_from_super_dl_if + att_from_super_ul_if + att_from_super_bad_ci) Counters from table(s): p_nbsc_underlay




213/712

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

Description: Share of HO attempts from super to regular due to bad C/I. Formula: sum(att_from_super_bad_ci) 100 * ------------------------------------------------------ % sum(att_from_super_dl_qual + att_from_super_dl_if + att_from_super_ul_if + att_from_super_bad_ci) Counters from table(s): p_nbsc_underlay

MSC incoming HO attempts, (ho_8)

Formula: sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

MSC outgoing HO attempts, (ho_9)

Formula: sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at) Counters from table(s):




214/712

p_nbsc_ho

BSC incoming HO attempts, (ho_10)

Formula: sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at) Counters from table(s): p_nbsc_ho

BSC outgoing HO attempts, (ho_11)

Formula: sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at) Counters from table(s): p_nbsc_ho

Intra-cell HO attempts, S2 (ho_12)

Formula: sum(cell_tch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho




215/712

Intra-cell HO attempts, S6 (ho_12a)

Formula: sum(cell_tch_tch_at + cell_sdcch_at + cell_sdcch_tch_at) Counters from table(s): p_nbsc_ho

HO attempts, outgoing and intra-cell S4, (ho_13)

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




216/712

Counters from table(s): p_nbsc_ho

HO attempts S3, (ho_13a)

Use: On the BTS level. If used on area level there will be double counting of inter-cell HOs. Formula: 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) Counters from table(s): p_nbsc_ho

HO attempts, outgoing and intra-cell, S5 (ho_13b)

Formula: sum(cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev + cause_distance + cause_msc_invoc + cause_intfer_up + cause_intfer_dwn + cause_umbr + cause_pbdgt + cause_omc




217/712

+ cause_ch_adm + cause_traffic + cause_dir_retry + cause_pre_emption + cause_field_drop + cause_low_distance + cause_bad_CI + cause_good_CI + ho_due_slow_mov_ms) Counters from table(s): p_nbsc_ho

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

Formula: sum(cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev + cause_distance + cause_msc_invoc + cause_intfer_up + cause_intfer_dwn + cause_umbr+cause_pbdgt + cause_omc + cause_dir_retry + cause_pre_emption + cause_field_drop + cause_low_distance + cause_bad_CI + cause_good_CI + cause_ho_due_slow_mov_ms




218/712

+ ho_att_due_switch_circ_pool ;S5 ) Counters from table(s): p_nbsc_ho

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

Formula: sum(cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev + cause_distance + cause_msc_invoc + cause_intfer_up + cause_intfer_dwn + cause_umbr + cause_pbdgt + cause_omc + cause_dir_retry + cause_pre_emption + cause_field_drop + cause_low_distance + cause_bad_CI + cause_good_CI + cause_ho_due_slow_mov_ms + ho_att_due_switch_circ_pool ;S5 + ho_due_ms_slow_speed + ho_due_ms_high_speed ; S6 ) Counters from table(s):




219/712

p_nbsc_ho

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

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

HO attempts, outgoing and intra-cell, S9, (ho_13f)

Use: Known problems: Formula: Sum(cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev + cause_distance + cause_msc_invoc + cause_intfer_up + cause_intfer_dwn + cause_umbr + cause_pbdgt + cause_omc + cause_ch_adm + cause_traffic + cause_dir_retry + cause_pre_emption + cause_field_drop + cause_low_distance




220/712

+ cause_bad_CI + cause_good_CI + ho_due_slow_mov_ms + ho_due_ms_slow_speed ; new S5,S6,S7 causes + ho_due_ms_high_speed + ho_att_due_switch_circ_pool + ho_att_due_erfd + ho_att_due_to_bsc_contr_trho.; new S8,S9 causes + ho_att_due_to_dadlb + ho_att_due_to_gprs + ho_att_due_to_hscsd) Counters from table(s): p_nbsc_ho Unit: Numbers

HO attempts, outgoing and intra-cell, S9, (ho_13g)

Use: Known problems: Formula: Sum(cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev + cause_distance + cause_msc_invoc + cause_intfer_up + cause_intfer_dwn + cause_umbr + cause_pbdgt




221/712

+ cause_omc + cause_traffic + cause_dir_retry + cause_pre_emption + cause_field_drop + cause_low_distance + cause_bad_CI + cause_good_CI + ho_due_slow_mov_ms + ho_due_ms_slow_speed ; new S5,S6,S7 causes + ho_due_ms_high_speed + ho_att_due_switch_circ_pool + ho_att_due_erfd + ho_att_due_to_bsc_contr_trho.; new S8,S9 causes + ho_att_due_to_dadlb + ho_att_due_to_gprs + ho_att_due_to_hscsd)

Counters from table(s): p_nbsc_ho Unit: Numbers

TCH requests for HO, (ho_14)

Known problems: Does not consider FACCH call setup. Formula: sum(tch_req - tch_call_req)




222/712


TCH requests for HO, (ho_14a)

Formula: sum(tch_req - tch_call_req - tch_fast_req) Counters from table(s): p_nbsc_traffic

TCH requests for HO, (ho_14b)

Note: When you are using IUO, you can see that the number of TCH requests due to HO attempts goes up (even tenfold). Formula: 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) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

TCH seizures for HO, (ho_15)

Formula: sum(tch_ho_seiz)




223/712


TCH-TCH HO attempts, (ho_16)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum(msc_o_tch_tch_at + msc_i_tch_tch_at + bsc_o_tch_tch_at + bsc_i_tch_tch_at + cell_tch_tch_at) Counters from table(s): p_nbsc_ho

SDCCH-TCH HO attempts, (ho_17)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum(msc_o_sdcch_tch_at + msc_i_sdcch_tch_at + bsc_o_sdcch_tch_at + bsc_i_sdcch_tch_at + cell_sdcch_tch_at) Counters from table(s): p_nbsc_ho

SDCCH-SDCCH HO attempts, (ho_18)

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




224/712

Formula: sum(msc_o_sdcch_at + msc_i_sdcch_at + bsc_o_sdcch_at + bsc_i_sdcch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

TCH-TCH HO successes, (ho_19)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum(msc_o_tch_tch + msc_i_tch_tch + bsc_o_tch_tch + bsc_i_tch_tch + cell_tch_tch) Counters from table(s): p_nbsc_ho

SDCCH-TCH HO successes, (ho_20)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum(msc_o_sdcch_tch + msc_i_sdcch_tch + bsc_o_sdcch_tch + bsc_i_sdcch_tch + cell_sdcch_tch) Counters from table(s):




225/712

p_nbsc_ho

SDCCH-SDCCH HO successes, (ho_21)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum(msc_o_sdcch + msc_i_sdcch + bsc_o_sdcch + bsc_i_sdcch + cell_sdcch) Counters from table(s): p_nbsc_ho

MSC controlled HO attempts, (ho_22)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum( msc_o_tch_tch_at + msc_i_tch_tch_at + msc_o_sdcch_tch_at + msc_i_sdcch_tch_at + msc_o_sdcch_at + msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

BSC controlled HO attempts, (ho_23)

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




226/712

sum( bsc_o_tch_tch_at + bsc_i_tch_tch_at + bsc_o_sdcch_tch_at + bsc_i_sdcch_tch_at + bsc_o_sdcch_at + bsc_i_sdcch_at) Counters from table(s): p_nbsc_ho

Intra-cell HO attempts, (ho_24)

Formula: sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

MSC controlled HO successes, (ho_25)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum( msc_o_tch_tch + msc_i_tch_tch + msc_o_sdcch_tch + msc_i_sdcch_tch + msc_o_sdcch_ + msc_i_sdcch) Counters from table(s): p_nbsc_ho




227/712

BSC controlled HO successes, (ho_26)

Use: On the BTS level. If used on the area level, it would result in double counting of inter-cell HOs. Formula: sum( bsc_o_tch_tch + bsc_i_tch_tch + bsc_o_sdcch_tch + bsc_i_sdcch_tch + bsc_o_sdcch + bsc_i_sdcch) Counters from table(s): p_nbsc_ho

Intra-cell HO successes, (ho_27)

Formula: sum(cell_tch_tch + cell_sdcch_tch + cell_sdcch) Counters from table(s): p_nbsc_ho

MSC incoming HO successes, (ho_28)

Formula: sum(msc_i_tch_tch + msc_i_sdcch_tch + msc_i_sdcch) Counters from table(s): p_nbsc_ho




228/712

MSC outgoing HO successes, (ho_29)

Formula: sum(msc_o_tch_tch + msc_o_sdcch_tch + msc_o_sdcch) Counters from table(s): p_nbsc_ho

BSC incoming HO successes, (ho_30)

Formula: sum(bsc_i_tch_tch + bsc_i_sdcch_tch + bsc_i_sdcch) Counters from table(s): p_nbsc_ho

BSC outgoing HO successes, (ho_31)

Formula: sum(bsc_o_tch_tch + bsc_o_sdcch_tch + bsc_o_sdcch) Counters from table(s): p_nbsc_ho

Incoming HO success, (ho_32)




229/712

sum(msc_i_succ_ho + bsc_i_succ_ho) Counters from table(s): p_nbsc_ho

Outgoing HO successes, (ho_33)

Formula: sum(msc_o_succ_ho + bsc_o_succ_ho) Counters from table(s): p_nbsc_ho

Outgoing HO attempts, (ho_34)

Formula: 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) Counters from table(s): p_nbsc_ho

Incoming HO attempts, (ho_35)

Formula: 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)




230/712


Outgoing SDCCH-SDCCH HO attempts, (ho_36)

Formula: sum(msc_o_sdcch_at + bsc_o_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming SDCCH-SDCCH HO attempts, (ho_37)

Formula: sum(msc_i_sdcch_at + bsc_i_sdcch_at) Counters from table(s): p_nbsc_ho

Outgoing SDCCH-TCH HO attempts, (ho_38)

Formula: sum(msc_o_sdcch_tch_at + bsc_o_sdcch_tch_at) Counters from table(s): p_nbsc_ho




231/712

Incoming SDCCH-TCH HO attempts, (ho_39)

Formula: sum(msc_i_sdcch_tch_at + bsc_i_sdcch_tch_at) Counters from table(s): p_nbsc_ho

Outgoing TCH-TCH HO attempts, (ho_40)

Formula: sum(msc_o_tch_tch_at + bsc_o_tch_tch_at) Counters from table(s): p_nbsc_ho

Incoming TCH-TCH HO attempts, (ho_41)

Formula: sum(msc_i_tch_tch_at + bsc_i_tch_tch_at) Counters from table(s): p_nbsc_ho

Outgoing SDCCH-SDCCH HO success, (ho_42)

Formula:




232/712

sum(msc_o_sdcch + bsc_o_sdcch) Counters from table(s): p_nbsc_ho

Incoming SDCCH-SDCCH HO success, (ho_43)

Formula: sum(msc_i_sdcch + bsc_i_sdcch) Counters from table(s): p_nbsc_ho

Outgoing SDCCH-TCH HO success, (ho_44)

Formula: sum(msc_o_sdcch_tch + bsc_o_sdcch_tch) Counters from table(s): p_nbsc_ho

Incoming SDCCH-TCH HO success, (ho_45)

Formula: sum(msc_i_sdcch tch + bsc_i_sdcch_tch) Counters from table(s):




233/712

p_nbsc_ho

Outgoing TCH-TCH HO success, (ho_46)

Formula: sum(msc_o_tch_tch + bsc_o_tch_tch) Counters from table(s): p_nbsc_ho

Incoming TCH-TCH HO success, (ho_47)

Formula: sum(msc_i_tch_tch + bsc_i_tch_tch) Counters from table(s): p_nbsc_ho

Intra-cell HO share, S1 (ho_48)

Formula: sum(cell_sdcch_tch_at + cell_tch_tch_at + cell_sdcch_at) 100 * ------------------------------------------------------------ % 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)




234/712

Unit: % Counters from table(s): p_nbsc_ho

MSC Controlled Incoming HO attempts, (ho_49)

Formula: sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

Next free (ho_50)

Handover Failure % (hfr)

Total HO failure %, S1 (hfr_1)

Use: Works best on the BTS level. On both the area level and the cell level. Experiences on use: In a good network the value can be less than 3 per cent, whereas in a very bad network values higher than 15 per cent may occur. When IUO is used, this formula shows high values due to highly failing intra-cell handovers between layers in congested cells. Known problems: This formula emphasises the non-intra-cell handovers since they are counted twice. This causes no problem on the cell level, whereas

on the area level problems may occur. Blocking is included. Blocking makes this indicator show high values especially in the case of IUO, but it does not necessarily mean

that there are some problems.




235/712

Formula: 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) Counters from table(s): p_nbsc_ho

Total HO failure %, S1 (hfr_2)

Use: On the area or network level. Experiences on use: In a network gave the result of 8 % instead of 7 % of hfr_1. In a good network the value can be less than 3 per cent, while in a very bad network values higher than 15 per cent may occur.




236/712

- If Directed Retry is enabled, the MS may, when congestion of the source cell SDCCH occurs, be moved from the best cell to a worse one. Then the MS tries to make a handover back but fails if the first cell is still congested. This leads to incrementation of the HO failure ratio.

Common reasons for a handover to fail: - incorrect parameter settings of adjacencies - badly defined neighbours (UL coverage becomes a problem) - UL coverage generally. Cell imbalanced. - TCH blocking in the target cell - UL interference (target BTS never gets the HO access) Known problems: 1) Blocking is included. Blocking makes this indicator show high values especially in the case of IUO, but it does not necessarily mean

that there are some technical problems. 2) Calls that are cleared by a MS user during the HO process increment the attempt counters but cannot be compensated in the

numerator. (XX2) 3) HO that is interrupted due to another procedure (e.g. assignment) increments attempt counters but cannot be compensated in the

numerator.(XX3) Formula: HO failures 100 * --------------- % HO attempts HO attempts - successful HOs = 100 * --------------------------------- % HO attempts successful HOs = 100 * (1- -------------- ) %




237/712

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) Counters from table(s): p_nbsc_ho

Intra-cell HO failure %, S1 (hfr_3)

Formula: Intra-cell HO successes 100 * (1- -------------------------) % Intra-cell HO attempts sum(cell_tch_tch + cell_sdcch) = 100* (1- ----------------------------------------) % sum(cell_tch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Intra-cell HO failure share, S1 (hfr_3a)

Use: On the BTS level. The results are equal to hfr_3c.




238/712

Formula: Intra-cell HO failures 100* (--------------------------------------) % All HO attempts sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch-at) -sum(cell_succ_ho) = 100* (--------------------------------------------------------------) % sum(msc_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) Counters from table(s): p_nbsc_ho

Intra-cell HO failure share, S1 (hfr_3b)

Use: On the area or network level. The results are equal to hfr_3d. Formula: Intra-cell HO failures 100 * (--------------------------------------) % All HO attempts sum(cell_tch_tch_at + cell_sdcch_tch_at +cell_sdcch-at) -sum(cell_succ_ho) = 100 * (--------------------------------------------------------------) % sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at) + 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) Counters from table(s):




239/712

p_nbsc_ho

Intra-cell HO failure share, S1 (hfr_3c)

Use: On the BTS level. The results are equal to hfr_3a. Formula: Intra-cell HO failures 100 * (--------------------------------------) % All HO attempts sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) - sum(cell_tch_tch + cell_sdcch_tch + cell_sdcch) = 100 * (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho

Intra-cell HO failure share, S1 (hfr_3d)

Use: On the area or network level. The results are equal to hfr_3b. Formula: Intra-cell HO failures 100* (--------------------------------------) % All HO attempts sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) - sum(cell_tch_tch + cell_sdcch_tch + cell_sdcch)




240/712

= 100 * (--------------------------------------------------------------) % sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at) + sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming MSC ctrl HO failure %, S1 (hfr_4)

Formula: MSC controlled incoming HO successes 100 * (1- --------------------------------------) % MSC controlled incoming HO attempts sum(msc_i_tch_tch + msc_i_sdcch_tch+msc_i_sdcch) = 100 * (1- --------------------------------------------------------------) % sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming MSC ctrl HO failure share, S1 (hfr_4a)

Use: On the BTS level. The results are equivalent to hfr_4c. Formula: MSC controlled incoming HO failures 100 * (--------------------------------------) % All HO attempts




241/712

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch-at) - sum(msc_i_succ_ho) = 100 * (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho

Incoming MSC ctrl HO failure share, S1 (hfr_4b)

Use: On the area or network level. The results are equivalent to hfr_4d. Formula: 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 * (--------------------------------------------------------------) % sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at+ msc_i_sdcch_at) + sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming MSC ctrl HO failure share, S1 (hfr_4c)

Use: On the BTS level. The results are equivalent to hfr_4a.




242/712

Formula: 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_tch_tch + msc_i_sdcch_tch + msc_i_sdcch) = 100 * (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho

Incoming MSC ctrl HO failure share, S1 (hfr_4d)

Use: On the area or network level. The results are equivalent to hfr_4b. Formula: 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_tch_tch + msc_i_sdcch_tch + msc_i_sdcch) = 100 * (--------------------------------------------------------------) % sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at) + sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s):




243/712

p_nbsc_ho

Outgoing MSC ctrl HO failure ratio %, S1 (hfr_5)

Use: On BTS Level. Formula: sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch) 100 - 100 * ------------------------------------------------------------ % sum(nvl(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at,0) Counters from table(s): p_nbsc_ho

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

Use: On the BTS level. The results are equivalent to hfr_5c. Formula: 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 * (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho




244/712

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

Use: On the area or network level. The results are equivalent to hfr_4d. Formula: 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* (--------------------------------------------------------------) % sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at) + sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

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

Use: On the BTS level. The results are equivalent to hfr_5a. Formula: 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_tch_tch+msc_o_sdcch_tch+msc_o_sdcch) = 100* (--------------------------------------------------------------) % 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)




245/712

+ 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) Counters from table(s): p_nbsc_ho

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

Use: On the area or network level. The results are equivalent to hfr_5b. Formula: 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_tch_tch + msc_o_sdcch_tch + msc_o_sdcch) = 100* (--------------------------------------------------------------) % sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at) + sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming BSC ctrl HO failure %, S1 (hfr_6)

Formula: BSC controlled incoming HO successes 100* (1- --------------------------------------) % BSC controlled incoming HO attempts




246/712

sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch) = 100* (1- --------------------------------------------------------------) % sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at) Counters from table(s): p_nbsc_ho

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

Use: On the BTS level. The results are equal to hfr_6c. Formula: 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* (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho

Incoming BSC ctrl HO failure %, S1 (hfr_6b)

Use: On the area or network level. The results are equal to hfr_6c. Formula:




247/712

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* (--------------------------------------------------------------) % sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at+ msc_i_sdcch_at) + sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

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

Use: On the BTS level. The results are to hfr_6a. Formula: 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_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch) = 100* (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho




248/712

Incoming BSC ctrl HO failure %, S1 (hfr_6d)

Use: On the area or network level. The results are equal to hfr_6b. Formula: 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_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch) = 100* (--------------------------------------------------------------) % sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at+ msc_i_sdcch_at) + sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Outgoing BSC ctrl HO failure %, S1 (hfr_7)

Formula: BSC controlled outgoing HO successes 100* (1- --------------------------------------) % BSC controlled outgoing HO attempts sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch) = 100* (1- --------------------------------------------------------------) % sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at) Counters from table(s):




249/712

p_nbsc_ho

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

Use: On the BTS level. The results are equal to hfr_7c. Formula: 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* (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho

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

Use: On the area or PLMN level. The results are equal to hfr_7d. Formula: BSC controlled outgoing HO failures 100* (--------------------------------------) % All HO attempts




250/712

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch-at) -sum(bsc_o_succ_ho) = 100* (--------------------------------------------------------------) % ........ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at) .......+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

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

Use: On the BTS level. The results are equal to hfr_7a. Formula: 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_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch) = 100* (--------------------------------------------------------------) % 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) Counters from table(s): p_nbsc_ho




251/712

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

Use: On the area or PLMN level. The results are equal to hfr_7b. Formula: 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_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch) = 100* (--------------------------------------------------------------) % ........ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at) .......+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at) + sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

Internal inter HO failure %, S4 (hfr_8)

Formula: sum(int_inter_ho_source_fail) 100* (-----------------------------------------------) % sum(int_inter_ho_source_fail+int_inter_ho_succ) Counters from table(s): p_nbsc_service

Internal intra HO failure %, S4 (hfr_9)

Formula:




252/712

sum(int_intra_ho_source_fail) 100* (-----------------------------------------------) % sum(int_intra_ho_source_fail+int_intra_ho_succ) Counters from table(s): p_nbsc_service

External source HO failure %, S4 (hfr_10)

Formula: sum(ext_ho_source_fail) 100* (-----------------------------------------------) % sum(ext_ho_source_fail+ ext_ho_source_succ) Counters from table(s): p_nbsc_service

External target HO failure %, S4 (hfr_11)

Known problems: ex_ho_target_fail is not augmented in S6 or later. HO counter based formula hfr_4 should be used instead. Formula: sum(ext_ho_target_fail) 100* (-----------------------------------------------) % sum(ext_ho_target_fail+ ext_ho_target_succ) Counters from table(s): p_nbsc_service

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

Use: Ratio of all other failures than ‘blocked’ to all HO attempts from super to regular.




253/712

Formula: 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) Counters from table(s): p_nbsc_underlay

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

Formula: 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) Counters from table(s): p_nbsc_underlay

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

Formula: sum(ho_fail_from_reg_due_ret) 100* (--------------------------------------------------------------------------) % sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ ho_fail_from_reg_freq) Counters from table(s): p_nbsc_underlay




254/712

Share of HO failures from regular to super due to MS lost, S4 (hfr_15)

Use: Ratio of ‘MS Lost’ failures to all HO attempts (blocked HOs excluded) in HOs from regular to super TRX. Formula: sum(ho_fail_from_reg_ms_lost) 100* (--------------------------------------------------------------------------) % sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ ho_fail_from_reg_freq) Counters from table(s): p_nbsc_underlay

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

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

Formula: sum(ho_fail_from_reg_freq) 100* (--------------------------------------------------------------------------) % sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ ho_fail_from_reg_freq) Counters from table(s): p_nbsc_underlay

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

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




255/712

Formula: sum(ho_fail_to_reg_due_ret) 100* (--------------------------------------------------------------------------) % sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq) Counters from table(s): p_nbsc_underlay

Share of HO failures from super to regular due to MS lost S4, (hfr_18)

Use: Ratio of ‘MS lost’ HO failures to all HO attempts (blocked HOs excluded) in HOs from super to regular TRX. Formula: sum(ho_fail_to_reg_ms_lost) 100* (--------------------------------------------------------------------------) % sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq) Counters from table(s): p_nbsc_underlay

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

Experiences on use: 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 regular TRX. Formula: sum(ho_fail_to_reg_freq) 100* (--------------------------------------------------------------------------) % sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq)




256/712

Counters from table(s): p_nbsc_underlay

SDCCH-SDCCH HO failure %, S2 (hfr_20)

Experiences on use: It is better to look at MSC and BSC controlled handover separately. Formula: 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) Counters from table(s): p_nbsc_ho

SDCCH-TCH HO failure %, S2 (hfr_21)

Use: These are Directed Retry. Formula: 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




257/712

+ 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) Counters from table(s): p_nbsc_ho

TCH-TCH HO failure %, S2 (hfr_22)

Formula: 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) Counters from table(s): p_nbsc_ho

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

Formula: 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)




258/712


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

Formula: 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) Counters from table(s): p_nbsc_ho

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

Formula: 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) Counters from table(s): p_nbsc_ho

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

Formula: sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at) -sum(msc_o_sdcch_tch + bsc_o_sdcch_tch) 100* ----------------------------------------------- %




259/712

sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: 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) Counters from table(s): p_nbsc_ho

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

Formula: 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) Counters from table(s): p_nbsc_ho

MSC ctrl HO failure %, blocking, (hfr_29)

Formula: msc_o_fail_lack 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at




260/712


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

Formula: msc_o_not_allwd 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: msc_o_fail_ret 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula:




261/712

msc_o_call_clr 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: msc_o_end_of_ho 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: msc_o_end_ho_bss 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho




262/712

MSC ctrl HO failure %, wrong air interface, (hfr_35)

Use: Relates to the congestion of A-interface pool resources detected by BSC. Formula: msc_controlled_out_ho 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: msc_o_adj_cell_id_err_c 100* ------------------------------------------------------ % msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at Counters from table(s): p_nbsc_ho

BSC ctrl HO failure %, blocking, (hfr_37)

Formula: bsc_o_fail_lack 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at




263/712


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

Formula: bsc_o_not_allwd 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: bsc_o_fail_ret 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: bsc_o_call_clr 100* ------------------------------------------------------ %




264/712

bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

bsc_o_end_of_ho 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: bsc_o_end_ho_bss 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

BSC ctrl HO failure %, wrong air interface, (hfr_43)

Use: Relates to the congestion of A-interface pool resources detected by BSC. Formula:




265/712

bsc_o_unsucc_a_int_circ_type 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

BSC ctrl HO drop call %, (hfr_44)

Formula: bsc_o_drop_calls 100* ------------------------------------------------------ % bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: cell_fail_lack 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho




266/712

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

Formula: cell_not_allwd 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: cell_fail_ret 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: cell_call_clr 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho




267/712

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

Formula: cell_fail_move 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: cell_fail_bss 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at Counters from table(s): p_nbsc_ho

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

Formula: cell_drop_calls 100* --------------------------------------------------- % cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at




268/712


HO failure % to adjacent cell, (hfr_52)

Formula: sum(ho_att_to_adj - ho_succ_to_adj) 100* ----------------------------------- % sum(ho_att_to_adj) Counters from table(s): p _nbsc_ho_adj

HO failure % from adjacent cell, (hfr_53)

Formula: sum(ho_att_from_adj - ho_succ_from_adj) 100* --------------------------------------- % sum(ho_att_from_adj) Counters from table(s): p _nbsc_ho_adj

HO failure %, blocking excluded, (hfr_54)

Use: On the area level. Formula:




269/712

/* all HO attempts */ 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_tc +cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at) /*successful handovers */ -sum(msc_i_succ_ho+msc_o_succ_ho +bsc_i_succ_ho+bsc_o_succ_ho+cell_succ_ho) /* handovers failing due to blocking */ -sum(msc_i_fail_lack+msc_o_fail_lack+bsc_i_fail_lack+ bsc_o_fail_lack+cell_fail_lack) 100 * ---------------------------------------------------------- % /* all HO attempts */ 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_tc +cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at) /*successful handovers */ -sum(msc_i_succ_ho+msc_o_succ_ho +bsc_i_succ_ho+bsc_o_succ_ho+cell_succ_ho) Counters from table(s): p_nbsc_ho

HO failure %, blocking excluded, (hfr_54a)

Use: On the area level. Formula: /* all HO attempts */




270/712

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 * ------------------------------------------------------% /* 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) /* handovers failing due to blocking */ -sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack) Counters from table(s): p_nbsc_ho

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

Use: On the area level. Formula: /* handovers failing due to blocking */ sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack) 100 * ------------------------------------------------------% /* 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)




271/712


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

Use: Relates to congestion of A-interface pool resources detected by BSC. sum(ho_unsucc_a_int_circ_type) 100 x -------------------------------------------------------- % sum(cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at) Counters from table(s): p_nbsc_ho

Intra-cell HO failure %, S1 (hfr_57)

Formula: Intra-cell HO successes 100 * (1- -------------------------) % Intra-cell HO attempts sum(cell_tch_tch + cell_sdcch_tch+ cell_sdcch) = 100 * (1- ---------------------------------------------------------------) % sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at) Counters from table(s): p_nbsc_ho

HO failures to target cell, S6 (hfr_58)

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




272/712

Known problems: Not accurate because 1) for calls that are cleared by MS user during the HO process the ho_att_to_adj counter is incremented and cannot be compensated

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

numerator. Formula: 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) Counters from table(s): p_nbsc_ho_adj

.20.8.98 OK HO failures from target cell, S6 (hfr_59)

Use: On the adjacency level. Gives the failure % of the real (non blocked) HO attempts. Known problems: Not accurate because 1) for calls that are cleared by MS user during the HO process the ho_att_to_adj-counter is incremented and cannot be compensated

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

numerator. Formula: 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)




273/712

Counters from table(s): p_nbsc_ho_adj

.20.8.98 OK HO attempted but not possible; no HO command, (hfr_60)

Note: HO command is not sent. Formula: sum(msc_o_fail_lack+ msc_o_not_allwd+ msc_controlled_out_ho +msc_o_adj_cell_id_err_c+bsc_o_fail_lack+bsc_o_not_allwd +bsc_o_unsucc_a_int_circ_type+cell_not_allwd+cell_fail_lack +ho_unsucc_a_int_crct_type) 100 * ----------------------------------------------------------% /* 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) Counters from table(s): p_nbsc_ho

HO attempted but not possible, wrong air interface circuit type, (hfr_61)

Note: HO command is not sent. Formula: sum(msc_controlled_out_ho+ bsc_o_unsucc_a_int_circ_type + ho_unsucc_a_int_crct_type) 100 * ------------------------------------------------------% sum(msc_o_fail_lack+ msc_o_not_allwd+ msc_controlled_out_ho + msc_o_adj_cell_id_err_c




274/712

+bsc_o_fail_lack+ bsc_o_not_allwd+ bsc_o_unsucc_a_int_circ_type +cell_not_allwd+ cell_fail_lack+ ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

HO attempted but not possible, HO not allowed, (hfr_62)

Note: HO command is not sent. Formula: sum(msc_o_not_allwd+bsc_o_not_allwd+cell_not_allwd) 100 * ------------------------------------------------------% sum(msc_o_fail_lack+ msc_o_not_allwd+ msc_controlled_out_ho + msc_o_adj_cell_id_err_c +bsc_o_fail_lack+ bsc_o_not_allwd+ bsc_o_unsucc_a_int_circ_type +cell_not_allwd+ cell_fail_lack+ ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

HO attempted but not possible, adjacent cell error, (hfr_63)

Note: HO command is not sent. Formula: sum(msc_o_adj_cell_id_err_c+bsc_o_unsucc_a_int_circ_type +ho_unsucc_a_int_crct_type) 100 * -------------------------------------------------------------------% sum(msc_o_fail_lack+ msc_o_not_allwd+ msc_controlled_out_ho + msc_o_adj_cell_id_err_c




275/712

+bsc_o_fail_lack+ bsc_o_not_allwd+bsc_o_unsucc_a_int_circ_type +cell_not_allwd+ cell_fail_lack+ ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

Call drops in HO, (hfr_64)

Note: Handovers that fail after the HO command is sent and cause a drop. Formula: sum(msc_o_call_drop_ho+bsc_o_drop_calls+cell_drop_calls) 100 * ------------------------------------------------------% /* 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) /* HO impossible, no HO command sent */ -sum(msc_o_fail_lack+msc_o_not_allwd+msc_controlled_out_ho +msc_o_adj_cell_id_err_c +bsc_o_fail_lack+bsc_o_not_allwd+bsc_o_unsucc_a_int_circ_type +cell_not_allwd+cell_fail_lack+ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

HO commanded, return to old channel, (hfr_65)

Note: Handovers that fail after the HO command is sent and cause a drop. Formula:




276/712

Sum(msc_o_fail_ret+bsc_o_fail_ret+cell_fail_ret) 100 * ------------------------------------------------------% /* 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) /* HO impossible, no HO command sent */ -sum(msc_o_fail_lack+msc_o_not_allwd+msc_controlled_out_ho +msc_o_adj_cell_id_err_c +bsc_o_fail_lack+bsc_o_not_allwd+bsc_o_unsucc_a_int_circ_type +cell_not_allwd+cell_fail_lack+ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

HO commanded, call clear, (hfr_66)

Note: Handovers that fail after the HO command is sent and cause a drop. Formula: Sum(msc_o_call_clear+bsc_o_call_clear+cell_call_clear) 100 * ------------------------------------------------------% /* 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) /* HO impossible, no HO command sent */ -sum(msc_o_fail_lack+msc_o_not_allwd+msc_controlled_out_ho +msc_o_adj_cell_id_err_c +bsc_o_fail_lack+bsc_o_not_allwd+bsc_o_unsucc_a_int_circ_type +cell_not_allwd+cell_fail_lack+ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho




277/712

HO failure % due to radio interface blocking, (hfr_67)

Note: HO command is not sent. Formula: /* handovers failing due to blocking */ sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack) 100 * ------------------------------------------------------% sum(msc_o_fail_lack+ msc_o_not_allwd+ msc_controlled_out_ho + msc_o_adj_cell_id_err_c +bsc_o_fail_lack+ bsc_o_not_allwd+ bsc_o_unsucc_a_int_circ_type +cell_not_allwd+ cell_fail_lack+ ho_unsucc_a_int_crct_type) Counters from table(s): p_nbsc_ho

HO drop ratio, (hfr_68)

Use: Defines how big a share of the started handovers is dropped. Indicates the quality of the handovers. Formula: Sum(bsc_o_drop_calls+msc_o_call_drop_ho +cell_drop_calls) 100* ------------------------------------------------------- % /* 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) /* handovers failing due to blocking */ -sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack) /* handovers failing due to not allowed */ -sum(msc_o_not_allwd+bsc_o_not_allwd+cell_not_allwd)




278/712

/* wrong Aif circuit type */ -sum(bsc_o_unsucc_a_int_circ_type+msc_controlled_out_ho +ho_unsucc_a_int_circ_type )


HO failures to target WCDMA cell, S10.5 (hfr_69)

Use: Gives the failure percentage of the non-blocked HO attempts. Formula: sum(ho_att_wcdma_ran_cell -ho_succ_wcdma_ran_cell -ho_fail_due_res_wcdma_ran) 100* -------------------------------------- % sum(ho_att_wcdma_ran_cell - ho_fail_due_res_wcdma_ran) Counters from table(s): p_nbsc_utran_ho_adj_cell

HO failures from target WCDMA cell, S10.5 (hfr_70)

Use: Gives the failure percentage of the non-blocked HO attempts. Formula:




279/712

sum(ho_att_from_wcdma_ran -ho_succ_from_wcdma_ran -ho_fail_due_res_wcdma_ran_cell) 100* -------------------------------------- % sum(ho_att_from_wcdma_ran -ho_fail_due_res_wcdma_ran_cell) Counters from table(s): p_nbsc_utran_ho_adj_cell

Intra-segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer, BSC level, S10.5 (hfr_71)

Description: Intra-segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer. Use: Gives intra-segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer. Known problems: Timing difference in two measurements. Formula: sum(b.INTRA_INTER_BAND_SDCCH_HANDOVER) 100 - 100* -------------------------------------- % sum(a.HO_ATT_INTER_BAND_SDCCH) a = p_nbsc_ho b = p_nbsc_cc_pm Counters from table(s): p_nbsc_ho p_nbsc_cc_pm Unit: %




280/712

Intra-segment SDCCH-SDCCH HO failure ratio between BTS types, BSC level, S10.5 (hfr_72)

Description: Intra-segment SDCCH-SDCCH HO failure ratio between BTS types. Use: Gives intra-segment SDCCH-SDCCH HO failure ratio between BTS types. Known problems: See hfr_71. Formula: sum(b.INTRA_INTER_BTS_TYPE_SDC) 100 - 100* -------------------------------------- % sum(a.HO_ATT_INTER_BTS_TYPE_SDCCH) a = p_nbsc_ho b = p_nbsc_cc_pm Counters from table(s): p_nbsc_ho p_nbsc_cc_pm Unit: %

Intra-segment TCH-TCH HO failure ratio between bands (due to load), BSC level, S10.5 (hfr_73)

Description: Intra-segment TCH-TCH HO failure ratio between bands (due to load reason). Use: Gives intra-segment TCH-TCH HO failure ratio between bands (due to lead reason) Known problems: See hfr_71.




281/712

Formula: sum(b.INTRA_INTER_BAND_TCH) 100 - 100* -------------------------------------- % sum(a.HO_ATT_INTER_BAND_TCH) a = p_nbsc_ho b = p_nbsc_cc_pm Counters from table(s): p_nbsc_ho p_nbsc_cc_pm Unit: %

Intra-segment TCH-TCH HO failure ratio between bands (due to downlink s ignal level), BSC level, S10.5 (hfr_74)

Description: Intra-segment TCH-TCH HO failure ratio between bands (due to downlink signal level). Use: Gives intra-segment TCH-TCH HO failure ratio between bands (due to downlink signal level). Known problems: See hfr_71. Formula: sum(b.INTRA_INTER_BAND_DUE_LEV) 100 - 100* -------------------------------------- % sum(a.HO_ATTEMPT_INTERBAND_DUE_LEVEL) a = p_nbsc_ho b = p_nbsc_cc_pm




282/712

Counters from table(s): p_nbsc_ho p_nbsc_cc_pm Unit: %

Intra-segment TCH-TCH HO failure ratio between BTS types (due to load), BSC level, S10.5 (hfr_75)

Description: Intra-segment TCH-TCH HO failure ratio between BTS types (due to load). Use: Gives intra-segment TCH-TCH HO failure ratio between BTS types (due to load). Known problems: See hfr_71. Formula: sum(b.INTRA_INTER_BTS_TYPE_TCH) 100 - 100* -------------------------------------- % sum(a.HO_ATT_INTER_BTS_TYPE_TCH) a = p_nbsc_ho b = p_nbsc_cc_pm Counters from table(s): p_nbsc_ho p_nbsc_cc_pm Unit: %




283/712

Next free (hfr_71)

Handover Success % (hsr)

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

Formula: sum(msc_o_sdcch) 100 * ------------------- % sum(msc_o_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(msc_o_sdcch_tch) 100 * ----------------------- % sum(msc_o_sdcch_tch_at) Counters from table(s): p_nbsc_ho




284/712

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

Formula: sum(msc_o_tch_tch) 100 * ----------------------- % sum(msc_o_tch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(bsc_o_sdcch) 100 * ------------------- % sum(bsc_o_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(bsc_o_sdcch_tch) 100 * ----------------------- % sum(bsc_o_sdcch_tch_at) Counters from table(s): p_nbsc_ho




285/712

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

Formula: sum(bsc_o_tch_tch) 100 * --------------------- % sum(bsc_o_tch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(cell_sdcch) 100 * ------------------- % sum(cell_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(cell_sdcch_tch) 100 * --------------------- % sum(cell_sdcch_tch_at)




286/712


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

Formula: sum(cell_tch_tch) 100 * --------------------- % sum(cell_tch_tch_at) Counters from table(s): p_nbsc_ho

MSC controlled incoming SDCCH-SDCCH HO success %, S1 (hsr_10)

Formula: sum(msc_i_sdcch) 100 * --------------------- % sum(msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(msc_i_sdcch_tch)




287/712

100 * --------------------- % sum(msc_i_sdcch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(msc_i_tch_tch) 100 * --------------------- % sum(msc_i_tch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(bsc_i_sdcch) 100 * --------------------- % sum(bsc_i_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula:




288/712

sum(bsc_i_sdcch_tch) 100 * ----------------------- % sum(bsc_i_sdcch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(bsc_i_tch_tch) 100 * --------------------- % sum(bsc_i_tch_tch_at) Counters from table(s): p_nbsc_ho

BSC controlled incoming HO success %, S1 (hsr_16)

Formula: sum(bsc_i_succ_ho) 100 * ------------------------------------------------------- % sum(bsc_i_sdcch_at+bsc_i_sdcch_tch_at+bsc_i_tch_tch_at) Counters from table(s): p_nbsc_ho




289/712

MSC controlled incoming HO success %, S1 (hsr_17)

Formula: sum(msc_i_succ_ho) 100 * ------------------------------------------------------- % sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at) Counters from table(s): p_nbsc_ho

Incoming HO success %, S1 (hsr_18)

Formula: sum(msc_i_tch_tch+bsc_i_tch_tch) 100 * --------------------------------------- % sum(msc_i_tch_tch_at +bsc_i_tch_tch_at) Counters from table(s): p_nbsc_ho

Outgoing HO success %, S1 (hsr_19)

Formula: sum(msc_o_tch_tch+bsc_o_tch_tch) 100 * --------------------------------------- % sum(msc_o_tch_tch_at +bsc_o_tch_tch_at) Counters from table(s): p_nbsc_ho




290/712

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

Formula: sum(cell_sdcch) 100 * ------------------ % sum(cell_sdcch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(cell_sdcch_tch) 100 * --------------------- % sum(cell_sdcch_tch_at) Counters from table(s): p_nbsc_ho

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

Formula: sum(cell_tch_tch) 100 * --------------------- % sum(cell_tch_tch_at) Counters from table(s): p_nbsc_ho




291/712

Next free (hsr_23)

HO Failures (hof)

Outgoing HO failures due to lack of resources, S2 (hof_1)

sum(BSC_o_fail_lack + MSC_o_fail_lack) Counters from table(s): p_nbsc_ho

Incoming HO failures due to lack of resources, S2 (hof_2)

Formula: sum(BSC_i_fail_lack + MSC_i_fail_lack) Counters from table(s): p_nbsc_ho

TCH HO failures when return to old channel was successful, (hof_3)

Known problems: Due to the mapping of different causes the accuracy may be poor. Formula: HOs failed in going to new channel - HOs 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)




292/712


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

Known problems: Due to the mapping of different causes the accuracy may be poor. Formula: HOs failed in going to new channel - HOs 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) Counters from table(s): p_nbsc_traffic

MSC incoming HO failures, (hof_5)

Formula: 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) Counters from table(s): p_nbsc_ho

MSC outgoing HO failures, (hof_6)

Formula: sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at) - sum(msc_o_tch_tch + msc_o_sdcch_tch + msc_o_sdcch) Counters from table(s):




293/712

p_nbsc_ho

MSC outgoing HO failures, (hof_6a)

Formula: sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at) - sum(msc_o_succ_ho) Counters from table(s): p_nbsc_ho

BSC incoming HO failures, (hof_7)

Formula: sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at) - sum(bsc_i_tch_tch + bsc_i_sdcch_tch + bsc_i_sdcch) Counters from table(s): p_nbsc_ho

BSC incoming HO failures, (hof_7a)

Formula: sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at - bsc_i_succ_ho) Counters from table(s): p_nbsc_ho




294/712

BSC outgoing HO failures, (hof_8)

Formula: sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at) - sum(bsc_o_tch_tch + bsc_o_sdcch_tch + bsc_o_sdcch) Counters from table(s): p_nbsc_ho

BSC outgoing HO failures, (hof_8a)

Formula: sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at - bsc_o_succ_ho) Counters from table(s): p_nbsc_ho

Intra-cell HO failures, (hof_9)

Formula: sum(cell_tch_tch_at + cell_sdcch_at - cell_tch_tch + cell_sdcch) Counters from table(s): p_nbsc_ho




295/712

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) Counters from table(s): p_nbsc_ho

Failed outgoing HO, return to old, (hof_10)

Formula: sum(msc_o_fail_ret + bsc_o_fail_ret) Counters from table(s): p_nbsc_ho

Failed outgoing HO, drop call, (hof_11)

Experiences on use: As handover failures also include blocking, this formula is not correct. Formula: (Outgoing HO failures) - (HO failures, return to old) = (Outgoing HO attempts) - (Outgong HO successes) - (HO failures, return to old) = 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) - sum(msc_o_fail_ret - bsc_o_fail_ret)




296/712


Outgoing HO failures, (hof_12)

Formula: Outgoing HO attempts - Outgoing HO successes = sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at + bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at) - sum(msc_o_succ_ho + bsc_o_succ_ho) Counters from table(s): p_nbsc_ho

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

Formula: sum(cell_fail_ret) Counters from table(s): p_nbsc_ho

Intra-cell HO fail, drop call, (hof_14)

Formula: sum(cell_drop_calls)




297/712


Incoming HO failures, (hof_15)

Formula: 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) Counters from table(s): p_nbsc_ho

Next free (hof_16)

Interference (itf)

UL interference, BTS level, S1 (itf_1)

Use: UL interference is measured as the time-out of the lowest band (band 0 in BSC terminology). Band 0 is defined by boundaries 0 and 1 which are BTS parameters. Boundary 0 is fixed, whereas boundary 1 can be set.

Experiences on use: UL interference alone is not a reliable quality factor if IUO is used. In IUO cells the UL interference can be high but the quality is still good.

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

2) If band 1 is defined unexceptionally wide, it becomes difficult to see the interference.




298/712

Formula: sum(ave_idle_f_TCH_1/res_av_denom4) 100 x (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

Idle timeslot time (%) in band X, TRX level, IUO, S4 (itf_2)

Experiences on use: In IUO cells the UL interference can show high values but the UL quality is still excellent. The bigger the values are in bands towards band 5, the worse the interference. Formula: sum(ave_full_tch_ifX) 100 x (----------------------- ) % sum(ave_full_tch_if1 + ave_full_tch_if2 + ave_full_tch_if3 + ave_full_tch_if4 + ave_full_tch_if5) Counters from table(s): p_nbsc_underlay




299/712

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

Experiences on use: UL interference alone is not a reliable quality factor if IUO is used. In IUO cells the UL interference can be high but the quality is still good.

Known problems: Formula: sum(ave_full_tch_if1) 100 x (1 - ------------------------------------------------------------ ) % sum(ave_full_tch_if1 + ave_full_tch_if2 + ave_full_tch_if3 + ave_full_tch_if4 + ave_full_tch_if5) Counters from table(s): p_nbsc_underlay

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

Use: BTS reports the interference of each TCH as a band number (0-4, where 0 is the lowest and band boundaries are defined as cell

parameters). BSC sums up the band numbers (ave_sum_idle_ch_interf) as well as the number of TCHs reported (ave_sum_idle_tch_per_trx) and from these figures an average interference band (0-4) can be calculated. Average interference is shifted by 1 (+1) to comply with band numbers 1-5.

Experiences on use: Shows null value on the TRX level if the TRX is completely in the GPRS territory, and on BTS level if all TRXs are completely in the GPRS territory, respectively.

Known problems:




300/712

Formula: sum(ave_sum_idle_ch_interf) -------------------------------- sum(ave_sum_idle_tch_per_trx)+1 Counters from table(s): p_nbsc_power

Next free (itf_4)

Congestion (cngt)

TCH congestion time, S1 (cngt_1)

Experiences on use: Useful to follow on the area level. Should give higher values than SDCCH congestion. Formula: sum(tch_cong_time/100) Counters from table(s): p_nbsc_res_avail Unit: seconds

SDCCH congestion time, S1 (cngt_2)

Experiences on use: Useful to follow on the area level. Should give smaller values than TCH congestion. Formula:




301/712

sum(sdcch_cong_time/100) Counters from table(s): p_nbsc_res_avail Unit: seconds

FTCH time congestion % (cngt_3)

Experiences on use: Formula: sum(tch_fr_radio_congestion_time) 100 * ----------------------------------------- % sum(period_duration*ave_tch_busy_full/60) Counters from table(s): p_nbsc_res_avail

FTCH time congestion % (cngt_3a)

Experiences on use: Formula: sum(tch_fr_radio_congestion_time/100) 100 * -------------------------------------------- % sum(period_duration * ave_tch_busy_full * 60) Counters from table(s): p_nbsc_res_avail




302/712

FTCH time congestion % (cngt_3b)

Experiences on use: Formula: sum(tch_fr_radio_congestion_time/100) 100 * ----------------------------------------- % sum(period_duration) Counters from table(s): p_nbsc_res_avail Unit: %

HTCH time congestion % (cngt_4)

Experiences on use: Formula: sum(tch_hr_radio_congestion_time) 100 * ------------------------------------------ % sum(period_duration * ave_tch_busy_half/60) Counters from table(s): p_nbsc_res_avail




303/712

HTCH time congestion % (cngt_4a)

Experiences on use: Formula: sum(tch_hr_radio_congestion_time/100) 100 * --------------------------------------------- % sum(period_duration * ave_tch_busy_half * 60) Counters from table(s): p_nbsc_res_avail

HTCH time congestion % (cngt_4b)

Experiences on use: Formula: sum(tch_hr_radio_congestion_time/100) 100 * ----------------------------------------- % sum(period_duration) Counters from table(s): p_nbsc_res_avail Unit: %




304/712

Next free (cngt_5)

Queuing (que)

Queued, served TCH call requests %, (que_1)

Use: Indicates the quota of TCH call requests seizing the TCH successfully after queuing. Known problems: tch_qd_call_att is triggered but unsrv_qd_call_att is not if: 1) The call attempt is in a queue and while waiting is taken by DR to another 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) before the queuing timer expires The impact of this depends on the queuing time and cell parameter Directed Retry Time Limit Min. The call is taken from the queue to DR as soon as the DR target cell list is ready. To get an accurate ratio, an additional counter XX1

would be needed (queued attempts taken to DR). Formula: sum( tch_qd_call_att - XX1 - unsrv_qd_call_att) 100 * ---------------------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic XX1 is the number of calls taken from queue to DR.

Queued, served TCH call requests %, S8 (que_1a)

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




305/712

Known problems: tch_qd_call_att is triggered but unsrv_qd_call_att is not if the call is lost for some reason (e.g. MS user hangs) before the queuing timer expires.

The impact of this depends on queuing time and cell parameter Directed Retry Time Limit Min . Formula: sum(tch_qd_call_att - removal_from_que_due_to_dr - unsrv_qd_call_att) 100 * --------------------------------------------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic

Queued, served TCH HO requests %, (que_2)


Formula: sum(tch_qd_ho_att - unsrv_qd_ho_att) 100 * ------------------------------------------------- % sum(tch_request - tch_call_req - tch_fast_req) Counters from table(s): p_nbsc_traffic




306/712

Queued, served TCH HO requests %, (que_2a)


Formula: sum(a.tch_qd_ho_att - a.unsrv_qd_ho_att) 100 * ------------------------------------------------------ % sum(a.tch_request - a.tch_call_req - a.tch_fast_req) - sum(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_hop_nbsc_ho

Successful queued TCH requests, (que_3)

Known problems: See que_1. Formula: sum(tch_qd_call_att - unsrv_qd_call_att) Counters from table(s): p_nbsc_traffic

Successful non-queued TCH requests, (que_4)

Known problems: See que_1. Formula:




307/712

sum(tch_norm_seiz) - sum(tch_qd_call_att - unsrv_qd_call_att) Counters from table(s): p_nbsc_traffic

Successful queued TCH HO requests, (que_5)

Known problems: See que_2. Formula: sum(tch_qd_ho_att - unsrv_qd_ho_att) Counters from table(s): p_nbsc_traffic

Successful non-queued TCH HO requests, (que_6)

Known problems: See que_2. Formula: sum(tch_ho_seiz) - sum(tch_qd_ho_att - unsrv_qd_ho_att) Counters from table(s): p_nbsc_traffic

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

Known problems: See que_1.




308/712

Use: Indicates the quota of TCH call requests seizing the TCH successfully straight without queuing. DR is excluded (its impac is seen in dr_3)

Formula: sum(tch_norm_seiz - (tch_qd_call_att - unsrv_qd_call_att)) 100 * --------------------------------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic

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

Known problems: See que_2. Formula: sum(tch_ho_seiz -(tch_qd_ho_att - unsrv_qd_ho_att)) 100 * --------------------------------------------------- % sum(tch_request - tch_call_req - tch_fast_req) Counters from table(s): p_nbsc_traffic

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

Known problems: See que_2. Formula: sum(a.tch_ho_seiz - (a.tch_qd_ho_att - a.unsrv_qd_ho_att)) 100 * ------------------------------------------------------------ % sum(a.tch_request - a.tch_call_req - a.tch_fast_req) - sum(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho




309/712

+ b.ho_unsucc_a_int_circ_type)


Next free (que_9)

Blocking (blck)

TCH Raw blocking, S1 (blck_1)

Experiences on use: Was earlier (before blck_8a) widely used on the cell and the area level. Known problems: This PI does not take Directed Retry into consideration. Rather, it shows only raw blocking including also HOs. Blocked HOs are

normally not so serious because there are alternatives to go to. Blocked new calls can be lost calls if Directed Retry is not in use. Formula: sum(tch_req_rej_lack) 100 * --------------------- % sum(tch_request) Counters from table(s): p_nbsc_traffic

SDCCH blocking %, before FCS, S1 (blck_5)

Known problems: See csf_1. Formula: 100 - csf_1 =




310/712

sum(SDCCH_busy_att) 100 * -------------------- % sum(SDCCH_seiz_att) Counters from table(s): p_nbsc_traffic

SDCCH real blocking %, S1 (blck_5a)

Known problems: See csf_1a Formula: 100-csf_1a = sum(SDCCH_busy_att - tch_seiz_due_sdcch_con) 100 * ------------------------------------------- % sum(SDCCH_seiz_att) Counters from table(s): p_nbsc_traffic

TCH Raw blocking % on super TRXs, S4 (blck_6)

Description: TCH blocking % on super TRXs Note: Cannot be calculated by a simple SQL*Plus statement. Formula: sum over super TRXs (tch_req_rej_lack) 100 * ----------------------------------------- % sum over super TRXs (tch_request)




311/712


TCH Raw blocking % on regular TRXs, S4 (blck_7)

Description: TCH Blocking % on regular layer. Note: Cannot be calculated by a simple SQL*Plus statement. Formula: sum over regular TRX (tch_req_rej_lack) 100 * ----------------------------------------- % sum over regular TRX (tch_request) Counters from table(s): p_nbsc_underlay

TCH call blocking, before DR, S2 (blck_8)

Experiences on use: Shows the blocking if DR is not used. Formula: TCH call req. rejected due to lack of res. or routed by DR to another cell 100 * ------------------------------------------------------------------------- % = all TCH call requests sum(tch_call_req - tch_norm_seiz) 100 * -------------------------------- % sum(tch_call_req)




312/712


TCH call blocking %, DR compensated, S2 (blck_8a)

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

It is the blocking rate that the customers will notice when they are driving in the mobile environment caused by the lack of radio resources. It is therefore one of the most critical KPIs.

Experiences on use: On the area level there is not yet a target value to give (except that 0% is the best). On the cell level, for example, 2% blocking on busy hour has been used as a criterion for design.

Known problems: This blocking shows also situations when blocking is caused by a fault in the BTS - not only pure blocking caused by high traffic. Formula: TCH call requests rejected due to lack of res. or routed by DR to another cell - successful outgoing DR 100 * ------------------------------------------------- % = all TCH call requests

sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch) 100 * -------------------------------------------- % sum(a.tch_call_req) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho




313/712

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 lost part of capacity due to a fault.

It is the blocking rate that the customer will notice when they are driving in the mobile environment caused by the lack of radio resources. It is therefore one of the most critical KPIs.

Experiences on use: On the area level there is not yet a target value to give (except that 0% is the best). On the cell level, for example, 2% blocking on Busy Hour has been used as a criterion for design.

Known problems: 1) This blocking also shows situations when it is caused by a fault in the BTS - not only pure blocking caused by high traffic. 2) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of

Trunk Reservation Invocation Refused) 3) The ratio can show too high values in the following case:

TCH assignment fails if the requested channel type is not found in A-interface circuit pool. In this case tch_norm_seiz is not triggered but tch_call_req was, i.e. in blck_8b this attempt is considered a blocked call. Anyhow BSC requests MSC to change the A-if circuit pool. The MSC can then decide if there is another request (assignment request) or call clear (clear_command). The second request may again fail or succeed. In BSC the TCH_REJ_DUE_REQ_CH_A_IF_CRC counter is triggered every time the channel request fails due to the above-mentioned reason. If Nokia MSC is used, there can be only one retry. With some other vendor’s MSC there can be multiple retries. The actual situation when this can be met is if EFR (enhanced full rate) codec is the primary choice but - the selected A-if circuit supports only Full Rate - there are free circuits supporting EFR in A-if

Formula:




314/712

TCH call requests rejected due to lack of res. or saved by DR - successful DR 100 * ---------------------------------------------------------------- % = all TCH call requests

sum(a.tch_call_req - a.tch_norm_seiz) - 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_traffic b = p_nbsc_ho

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

Use: It is the failed call attempts that the MS user will notice, caused by the lack of radio resources. It is therefore one of the most critical KPIs. On the cell level may appear in the busiest cells. The cell needs an urgent capacity extension or has lost part of its capacity due to a fault. A MS user usually hears three beep tones when a call is rejected due to blocking.

Experiences on use: On the area level there is not yet a target value to give (except that the trend should be to a smaller value and 0% is the best). On the cell level, for example, 2% blocking on Busy Hour has been used as a criterion for design. This KPI can be followed statistically, for example, as the number of cells in which the value exceeds the given threshold.

Known problems: 1) This blocking also shows situations when it is caused by a fault in the BTS - not only pure blocking caused by high traffic. 2) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of

Trunk Reservation Invocation Refused)

Formula:




315/712

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 (including retries due to mismatch) - (Aif circuit pool seizure rejections (blocking or mismatch) - Aif circuit pool handover failures) sum(a.tch_call_req - a.tch_norm_seiz) - 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) - 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)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho




316/712

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

Use: Applicable on area or BTS level. Queuing and Directed Retry are the BSS features that can reduce blocking.

It is the failed call attempts that the MS user will notice, caused by the lack of radio resources. It is therefore one of the most critical KPIs. On the cell level may appear in the busiest cells. The cell needs an urgent capacity extension or has lost part of its capacity due to a fault. A MS user usually hears three beep tones when a call is rejected due to blocking.

Experiences on use: On the cell level, for example, 2% blocking on Busy Hour has been used as a criterion for design. This KPI can be followed statistically, for example,as the number of cells in which the value exceeds the given threshold.

Known problems: 1) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of Trunk Reservation Invocation Refused)

2) If dadlb_start_due_exceeded_load is triggered and the dadlb handover fails the counter tch_call_req will be triggered twice. This problem will be corrected in S10.

3) The formula also counts the following case as a blocked call: a call is cleared from the other end between the call request and TCH seizure. Note that queuing prolongs this time and thus the probability of a call to be cleared.

100 - csf_3l = sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch + b.cell_sdcch_tch); DR calls + sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) 100 * -------------------------------------------------------------------------- % sum(a.tch_call_req)




317/712

- 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)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with the cell_sdcch_tch.

TCH call blocking %, DR compensated, EFR excluded S10.5 (blck_8e)

Use: Applicable on area or BTS level. Queuing and Directed Retry are the BSS features that can reduce blocking.

It is the failed call attempts that the MS user will notice, caused by the lack of radio resources. It is therefore one of the most critical KPIs. On the cell level may appear in the busiest cells. The cell needs an urgent capacity extension or has lost part of its capacity due to a fault. A MS user usually hears three beep tones when a call is rejected due to blocking.

Experiences on use: On the cell level, for example, 2% blocking on Busy Hour has been used as a criterion for design. This KPI can be followed statistically, for example,as the number of cells in which the value exceeds the given threshold.

Known problems: 1) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of Trunk Reservation Invocation Refused)

2) If dadlb_start_due_exceeded_load is triggered and the dadlb handover fails the counter tch_call_req will be triggered twice. This problem will be corrected in S10.




318/712

3) The formula also counts the following case as a blocked call: a call is cleared from the other end between the call request and TCH seizure. Note that queuing prolongs this time and thus the probability of a call to be cleared.

100 - csf_3n = sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch + b.cell_sdcch_tch); DR calls + sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 - sum(c.SPARE057046 ; Aif type mismatch or congestion) 100 * -------------------------------------------------------------------------- % sum(a.tch_call_req) - sum(c.SPARE057046) ; Aif type mismatch or congestion Counters from table(s): a = p_nbsc_traffic c = P_NBSC_SERVICE Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with the cell_sdcch_tch.

Blocked calls, S2 (blck_9)

Use: Shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. Formula: TCH call requests rejected due to lack of res. or routed by DR to another cell - successful outgoing DR

sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch)




319/712


Blocked calls, S2 (blck_9a)

Use: Shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. Known problems: TCH call seizures rejected due to Aif circuit pool mismatch get counted, too. Formula: TCH call requests rejected due to lack of res. or routed by DR to another cell - successful DR sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch); inter-cell DR - sum(b.cell_sdcch_tch); intra-cell DR in IUO Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

Blocked calls, S5 (blck_9b)

Use: Shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. Formula: TCH call requests rejected due to lack of res. or routed by DR to another cell - successful DR - Rejections due to Aif circuit mismatch




320/712

sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch); inter-cell DR - sum(b.cell_sdcch_tch); intra-cell DR in IUO

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

-(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)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

Blocked calls, S7 (blck_9c)

Use: Shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. Formula: TCH call requests rejected due to lack of res. or routed by DR to another cell - successful DR - Rejections due to Aif circuit mismatch sum(a.tch_call_req- a .tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch); inter-cell DR - sum(b.cell_sdcch_tch); intra-cell DR in IUO + sum(a.tch_succ_seiz_for_dir_acc ); ref.2 - sum(a.tch_rej_due_req_ch_a_if_crc; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures +b.msc_controlled_in_ho +b.ho_unsucc_a_int_circ_type))




321/712

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Blocked TCH HOs, S2 (blck_10)

Known problems: Shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. FACCH call setup not considered.

Formula: sum(tch_request - tch_call_req - tch_ho_seiz) Counters from table(s): p_nbsc_traffic

Blocked TCH HOs, S2 (blck_10a)

Use: Replaces blck_10. Formula: sum(tch_request-tch_call_req - tch_fast_req-tch_ho_seiz) Counters from table(s): p_nbsc_traffic




322/712

Blocked TCH HOs, S5 (blck_10b)

Use: Replaces blck_10a. Formula: 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) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

TCH HO blocking, S2 (blck_11)

Known problems: This PI shows also situations when blocking is caused by a fault in the BTS - not only blocking caused purely by high traffic. FACCH call setup not considered.

Formula: sum(tch_request - tch_call_req - tch_ho_seiz) 100 * -------------------------------------------- % sum(tch_request - tch_call_req) Counters from table(s): p_nbsc_traffic

TCH HO blocking, S2 (blck_11a)

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




323/712

2) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of Trunk Reservation Invocation Refused)

Formula: sum(tch_request - tch_call_req-tch_fast_req - tch_ho_seiz) 100 * ---------------------------------------------------------- % sum(tch_request - tch_call_req - tch_fast_req) Counters from table(s): p_nbsc_traffic

TCH HO blocking without Q, S2 (blck_11b)

Known problems: See que_2 (factor XX1)Use: Shows TCH HO blocking if queuing was not in use. Formula: sum(tch_request - tch_call_req - tch_fast_req - tch_ho_seiz) + sum(tch_qd_ho_att - XX1 - unserv_qd_ho_att) 100 * ------------------------------------------------------------ % sum(tch_request - tch_call_req - tch_fast_req) Counters from table(s): p_nbsc_traffic

TCH HO blocking, S5 (blck_11c)

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




324/712

2) NOTE: If Trunk Reservation is used, HO and Call blocking cannot be counted precisely (there is only one counter for the case of Trunk Reservation Invocation Refused)

Formula: 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) 100 * ------------------------------------------------------------- % sum(a.tch_request - a.tch_call_req - a.tch_fast_req) - sum(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho +b.ho_unsucc_a_int_circ_type)


Blocked incoming and internal HO, S2 (blck_12)

Use: Usable with S4 and earlier. Formula: sum(msc_i_fail_lack + bsc_i_fail_lack + cell_fail_lack) Counters from table(s): p_nbsc_ho

Blocked incoming and internal HO, S2 (blck_12a)

Use: On the area level with S5 and S6. Formula: sum(msc_i_fail_lack + bsc_i_fail_lack + cell_fail_lack




325/712

+ bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho + ho_unsucc_a_int_circ_type) Counters from table(s): p_nbsc_ho

AG blocking, S1 (blck_13)

Use: A BSC sends to a BTS an immediate assignment or immediate assignment rejected commands. When the AG buffer in the BTS is full, it will respond with a delete indication. Thus, the ratio of delete indications to the sum of immediate assignment and immediate assignment rejected describes the AG blocking. After receiving the delete indication message the BSC releases the SDCCH.

Formula: 100 * sum(del_ind_msg_rec)/ sum(imm_assgn_rej + imm_assgn_sent) Counters from table(s): p_nbsc_res_access

FCS blocking, S5 (blck_14)

Formula: sum(tch_seiz_att_due_sdcch_con - tch_seiz_due_sdcch_con) 100 * --------------------------------------------------- % sum(tch_seiz_att_due_sdcch_con %)




326/712


Blocked SDCCH seizure attempts, S5 (blck_15)

Formula: All blocked - seizures to FACCH setup sum(sdcch_busy_att - tch_seiz_due_sdcch_con) Counters from table(s): p_nbsc_traffic

HO blocking %, (blck_16)

Use: On the area level. Formula: /* handovers failing due to blocking */ - sum(msc_i_fail_lack + msc_o_fail_lack + bsc_i_fail_lack + bsc_o_fail_lack + cell_fail_lack) 100 * ---------------------------------------------------------- % /* all HO attempts */ 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_tc + cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)




327/712

HO blocking %, (blck_16a)

Use: On area level with S4 or earlier. Formula: /* handovers failing due to blocking */ - sum(msc_o_fail_lack + bsc_o_fail_lack + cell_fail_lack) 100 * ---------------------------------------------------------- % /* 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)

HO blocking %, (blck_16b)

Use: On the area level with S5 and S6. Known problems: If in intra-cell HO the required channel type (e.g. Full Rate) is not available, ho_unsucc_a_int_circ_type is triggered but the same

channel may be seized successfully after changing the HO to external (A-interface circuit changes). Formula: /* handovers failing due to blocking */ sum(msc_i_fail_lack + bsc_i_fail_lack + cell_fail_lack + bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho + ho_unsucc_a_int_circ_type) 100 * ---------------------------------------------------------- % /* 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)




328/712

Abis link blocking (blck_17)

There is no counter but an alarm: 2720 ‘Telecom Link overload’. Blocked FACCH call setup TCH requests, (blck_18)

Formula: sum(tch_seiz_att_due_sdcch_con - tch_seiz_due_sdcch_con) Counters from table(s): p_nbsc_traffic

Handover blocking to target cell, (blck_19)

Formula: sum(ho_fail_res_to_adj) 100 * ---------------------- % sum(ho_att_to_adj) Counters from table(s): p_nbsc_ho_adj

Handover blocking from target cell, (blck_20)

Formula: sum(ho_fail_res_from_adj) 100 * ------------------------- % sum(ho_att_from_adj)




329/712

Counters from table(s): p_nbsc_ho_adj

NACK ratio of p-immediate assignment, S9PS (blck_21)

Use: A negative acknowledgement (NACK) is sent from BTS to BSC after all AGCH messages which are deleted from TRX buffers due to - buffer overflow - maximum lead-time expiry - expired starting time, and which are ordered by BSC to be acknowledged. The negative acknowledgement is sent immediately after the message has been deleted.

Formula: sum(packet_immed_ass_nack_msg) 100 * --------------------------------------------------- % sum(packet_immed_ass_msg + packet_immed_ass_rej_msg) Counters from table(s): p_nbsc_packet_control_unit

Territory upgrade rejection %, S9PS (blck_22)

Use: Indicates the lack of resources to upgrade the GPRS territory. Formula:




330/712

sum(gprs_ter_ug_rej_due_csw_tr + gprs_ter_ug_rej_due_lack_psw + gprs_ter_ug_rej_due_lack_pcu) 100 * ------------------------------------------------------------- % sum(gprs_ter_upgrd_req) Counters from table(s): p_nbsc_traffic

FTCH blocking %, (blck_23)

Use: Formula: sum(TCH_REJ_REQ_DUE_LACK_FR) 100 * ----------------------------- % sum(TCH_FULL_REQ_SUCC_UNSUCC) Unit: %

HTCH blocking %, (blck_24)

Use: Formula: TCH_REJ_REQ_DUE_LACK_HR 100 * ---------------------------- % TCH_HALF_REQ_SUCC_UNSUCC Unit: %




331/712

FTCH blocking due to HR %, (blck_25)

Use: Formula: TCH_FULL_REJ_DUE_HR_TRAF 100 * ------------------------- % TCH_FULL_REQ_SUCC_UNSUCC Unit: %

HTCH blocking due to FR %, (blck_26)

Use: Formula: TCH_HALF_REJ_DUE_FR_TRAF 100 * -------------------------- % TCH_HALF_REQ_SUCC_UNSUCC Unit: %

Handover blocking to target WCDMA cell, S10.5 (blck_27)

Use: Formula: sum(ho_fail_due_res_wcdma_ran) 100 * ------------------------------- sum(ho_att_wcdma_ran_cell) Counters from table(s): p_nbsc_utran_ho_adj_cell




332/712

Unit: %

Handover blocking from target WCDMA cell, S10.5 (blck_28)

Use: Formula: sum(ho_fail_due_res_wcdma_ran_cell) 100 * ------------------------------------ sum(ho_att_from_wcdma_ran) Counters from table(s): p_nbsc_utran_ho_adj_cell Unit: %

TCH denied for call request ratio, S10 (blck_29)

Use: To indicate end user experience of TCH denied for new calls. Failures during call setup are not considered. Description: Attempts that fail to get TCH after the call setup phase. Known Problems: Formula: sum(a.tch_call_req + a.tch_fast_req) - sum(c.tch_re_est_assign + c.tch_new_call_assign) - 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.tch_fast_req) - sum (a.tch_rej_due_req_ch_a_if_crc; Aif type mismatch or congestion




333/712

-(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) ) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho c = p_nbsc_service Unit: % Territory upgrade rejection due to CSW %, S9PS (blck_30)

Use: Indicates the ratio of territory upgrade requests ending up in rejection due to CSW traffic. Formula: sum(gprs_ter_ug_rej_due_csw_tr) 100 * ------------------------------- % sum(gprs_ter_upgrd_req) Counters from table(s): p_nbsc_traffic

Territory upgrade rejection due to PSW %, S9PS (blck_31)

Use: Indicates the ratio of territory upgrade requests ending up in rejection due to PSW traffic. Formula: sum(gprs_ter_ug_rej_due_lack_psw)




334/712

100 * ------------------------------- % sum(gprs_ter_upgrd_req) Counters from table(s): p_nbsc_traffic

Territory upgrade rejection due to PCU capacity %, S9PS (blck_32)

Use: Indicates the ratio of territory upgrade requests ending up in rejection due to PCU capacity. Formula: sum(gprs_ter_ug_rej_due_lack_pcu) 100 * ------------------------------- % sum(gprs_ter_upgrd_req) Counters from table(s): p_nbsc_traffic

DL multislot Soft Blocking %, S10.5 PS (blck_33)

Use: Formula: 100 - msl_6 Counters from table(s): p_nbsc_packet_control_unit




335/712

UL multislot Soft Blocking %, S10.5 PS (blck_34)

Use: Formula: 100 - msl_5 Counters from table(s): p_nbsc_packet_control_unit

Ratio of Incompletely served Territory upgrade requests %, S10.5PS (blck_35)

Use: Indicates the ratio of territory upgrade requests that could not be completely served as requested. Formula: sum(incompl_serv_gprs_ter_upgr_req) 100 * ----------------------------------- % sum(gprs_ter_upgrd_req) Counters from table(s): p_nbsc_traffic




336/712

Next free (blck_30)

Traffic (trf)

TCH traffic sum, S1 (trf_1)

Experiences on use: If counted over one hour, Erlang is shown. Counting Erlangs over a longer period requires that the Erlang values per hour are first counted and then averaged.

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

- The sampling period is 20 s, which means that during the period of one hour the number of used TCHs checked 180 times. This method is not accurate if we think about short seizures and low traffic but statistically the results have been satisfactory.

- Does not show calls going to voice mail. Note: The result represents technical traffic, not charged traffic because counting is started when BSC seizes TCH. Includes some of

signalling, ringing and speech. Formula: sum(ave_busy_tch) ------------------- sum(res_av_denom14) Counters from table(s): p_nbsc_res_avail Unit: Erlang hours if the measurement period is 1 hour.




337/712

TCH traffic sum, S1 (trf_1a)

Note: See trf_1. Formula: sum_over_area ( sum_over_BTS(ave_busy_tch)/ sum_over_BTS(res_av_denom14) ) Counters from table(s): p_nbsc_res_avail

TCH traffic sum of normal TRXs, S1 (trf_1b)

Use: On the BTS and area level. Experiences on use: See trf_1. Known problems: See trf_1. Note: See trf_1.Formula: sum(decode(trx_type,0,ave_busy_tch) / decode(trx_type,0,res_av_denom14)) Counters from table(s): p_nbsc_res_avail Unit: Erlang hours if the measurement period is 1 hour.

TCHtraffic sum of extended TRXs, S1 (trf_1c)

Use: On the BTS and area level.




338/712

Experiences on use: See trf_1. Known problems: See trf_1. Note: See trf_1.Formula: sum(decode(trx_type,1,ave_busy_tch) / decode(trx_type,1,res_av_denom14)) Counters from table(s): p_nbsc_res_avail Unit: Erlang hours if the measurement period is 1 hour.

Average call length, S1 (trf_2)

Use: On the area level gives you an idea about the behaviour of the MS users. Known problems: This formula is sensitive to the used measurement period. If the period is 60 min, the result is correct. Directed retries and FACCH call setups are missing in the denominator. Note: In the numerator (a.ave_busy_tch / a.res_av_denom14) represents technical traffic, not charged traffic because counting is started

when BSC seizes TCH. Includes some of signalling, ringing and speech. In the denominator there are also calls that are not answered. Formula: Total TCH use time Nbr of seconds in meas. period * average busy TCH ------------------- = -------------------------------------------------- Number of calls Number of calls 3600 * sum(a.ave_busy_tch / a.res_av_denom14) = --------------------------------------------- sum(b.tch_norm_seiz) NOTE: The formula is valid if the measurement period is 1 hour (3600 s).




339/712

Counters from table(s): a = p_nbsc_res_avail b = n_bsc_traffic

Average call length, S1 (trf_2a)

Use: On the area level gives you an idea about the behaviour of the MS users. Note: See trf_2. Formula: Total TCH use time Nbr of seconds in meas.period * average busy TCH ------------------- = ------------------------------------------------- Number of calls Number of calls avg(period_duration) * 60 * sum(a.ave_busy_tch / a.res_av_denom14) = ------------------------------------------------------------------ sum(b.tch_norm_seiz) Counters from table(s): a = p_nbsc_res_avail b = n_bsc_traffic

Average call length, S1 (trf_2b)

Use: On the area level gives you an idea about the behaviour of the MS users. Note: In the numerator (a.ave_busy_tch / a.res_av_denom14) represents technical traffic, not charged traffic because counting is started

when BSC seizes TCH. Includes some of signalling, ringing and speech. In the denominator there are also calls that are not answered. Formula:




340/712

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(c.msc_o_sdcch_tch + c.bsc_o_sdcch_tch + c.cell_sdcch_tch) ;DR calls + sum(b.tch_seiz_due_sdcch_con) ;FACCH call setup calls Counters from table(s): a = p_nbsc_res_avail b = p_bsc_traffic c = p_nbsc_ho

Average call length, S1 (trf_2c)

Formula: (Nbr of TCH seizures per call) x (average TCH hold time) = (1 + (nbr of HOs)/ (nbr of calls)) x (average TCH hold time) sum(b.TCH_HO_seiz) = (1 + ------------------- ) x sum(a.ave_FTCH_hold_tim)/sum(a.res_av_denom17)x100 sum(b.TCH_norm_seiz) Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_traffic




341/712

Unit = seconds

Average call length, S1 (trf_2d)

Use: On the area level gives you an idea about the behaviour of the MS users. Note: In the numerator (a.ave_busy_tch / a.res_av_denom14) represents technical traffic, not charged traffic because counting is started

when BSC seizes TCH. Includes some of signalling, ringing and speech. In the denominator there are also calls that are not answered. The numerator counts both A and B-side in MS-MS calls, thus duplicating call time. Formula: 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 Counters from table(s): a = p_nbsc_res_avail b = p_bsc_traffic c = p_nbsc_ho




342/712

CS territory usage, S1 (trf_3)

Use: On the area level gives you an idea of how well the capacity is used. Usable after S4 if half rate is not used. The formula does not comprise the GPRS timeslots (PDTCH). Known problems: When GPRS is used, the CS territory size (denominator) can change according to the traffic needs and therefore the indicator is not

consistent. Formula: used TCH 100 * -------------------- % available TCH sum(ave_busy_tch/res_av_denom14) = 100 * --------------------------------------- % sum(ave_avail_full_TCH/res_av_denom2) Counters from table(s): p_nbsc_res_avail

FTCH usage, S1 (trf_3a)

Use: Use with S5 or earlier or later if half rate is not yet used. Known problems: 1) ave_non_avail_tsl does not separate FTCH and HTCH.

2) When GPRS is used, the CS territory size (denominator) can change according to the traffic needs and therefore the indicator is not consistent.

Formula:




343/712

TCH hold time 100 * ---------------------------------------- % average available TCH * period duration sum(ave_ftch_hold_tim/res_av_denom17/100) = 100 * ------------------------------------------------------------------------ % sum(ave_avail_full_TCH/res_av_denom2 + ave_non_avail_tsl/res_av_denom1) * period duration in seconds Counters from table(s): p_nbsc_res_avail

FTCH usage, S5 (trf_3b)

Use: On the area level gives you an idea of how well the capacity is used. Use with S5 or later. Known problems: When GPRS is used, the CS territory size (denominator) can change according to the traffic needs and therefore the indicator is not

consistent. Formula: sum(ave_tch_busy_full) 100 * ------------------------------------ % sum(ave_avail_full_TCH/res_av_denom2) Counters from table(s): p_nbsc_res_avail




344/712

Average SDCCH hold time, S1 (trf_4)

Description: Average SDCCH hold time Note: For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs, keeping in mind

the note above. Use: The holding time may change due to modification of the timers or perhaps software. This time is part of the call setup time. Experiences on use: The counters receive the value of zero if the BTS is locked. Typically the values range from 2 to 3 seconds but over 4 seconds with

satellite Abis. Formula: sum(ave_sdcch_hold_tim) -------------------------- sec sum(res_av_denom16) * 100 Counters from table(s): p_nbsc_res_avail

Average FTCH hold time, S1 (trf_5)

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

Experiences on use: The counters receive the value of zero if the BTS is locked. The value is highly dependent on the number of handovers that, again, are dependent on the network plan.

Formula: sum(ave_ftch_hold_tim)




345/712

------------------------- sec sum(res_av_denom17) * 100 Counters from table(s): p_nbsc_res_avail

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

Use: The seizures of TCH for a new call (i.e. not HO, not DR, not FCS). Formula: sum(p_nbsc_traffic.tch_norm_seiz) Counters from table(s): p_nbsc_traffic

SDCCH usage, S1 (trf_7)

test results Experiences on use:Formula: used SDCCH 100 * ------------------ % available SDCCH sum(ave_busy_sdcch/res_av_denom15) = 100 * ------------------------------------ % sum(ave_sdcch_sub/res_av_denom3)

SDCCH usage, S1 (trf_7a)

Formula:




346/712

SDCCH hold time 100 * ----------------------------------------- % average available SDCCH * period duration sum(sdcch_hold_tim/res_av_denom17/100) = 100 * ----------------------------------------------------- % average available SDCCH * period duration in seconds sum(ave_sdcch_hold_tim/res_av_denom16/100) = 100 * ---------------------------------------------------------- % sum(ave_sdcch_sub/res_av_denom3 + ave_non_avail_sdcch) * period duration in seconds Counters from table(s): p_nbsc_res_avail

SDCCH usage %, S1 (trf_7b)

Use: Experiences on use: Dynamic SDCCH allocation can add SDCCH capacity dynamically and therefore make the counting of SDCCH usage % obsolete. Formula: 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 * ------------------------------------------------------------------- %




347/712

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_avail b = p_nbsc_traffic

SDCCH usage %, S1 (trf_7c)

Known problems: SDCCH seizures are very short to be counted using 20 s sampling time. Formula: sum(period_duration * ave_busy_sdcch/res_av_denom15) 100 * ------------------------------------------------------ % sum((ave_sdcch_sub/res_av_denom3 + ave_non_avail_sdcch) * period_duration)

TCH traffic absorption on super, S4 (trf_8)

Note: Cannot be calculated by a simple SQL*Plus statement. First, count the traffic per a TRX: Then, label the TRXs to super or regular (TRX is a super TRX if HO related counters for this TRX show the value of zero). Sum up the traffic for super TRXs and for all TRXs and calculate their ratio. Formula: avg(ave_busy_tch)




348/712

traffic (super) 100 x --------------- % traffic (all)


TCH traffic absorption on super, S4 (trf_8a)

Use: IUO Note: Cannot be calculated by a simple SQL*Plus statement. Formula: sum over BTS (avg per each super TRX (ave_busy_tch)) 100 x ---------------------------------------------------- % sum over BTS (avg per each TRX (ave_busy_tch))


Average cell TCH traffic from IUO, S4 (trf_9)

Note: Cannot be calculated by a simple SQL*Plus statement. Formula: First, count the traffic per TRX and per hour:




349/712

avg(ave_busy_tch)

Then, sum up the traffic over the period and divide it by the number of hours in the period. sum traffic of all TRXs 100 x ------------------------ % hours


Cell TCH traffic from IUO, S4 (trf_9a)

Note: Cannot be calculated by a simple SQL*Plus statement. Formula: sum over BTS (avg per each TRX (ave_busy_tch)) Counters from table(s): p_nbsc_underlay

Average super TRX TCH traffic, S4 (trf_10)

Note: Cannot be calculated by a simple SQL*Plus statement. Formula: First, count the traffic per TRX and per hour: avg(ave_busy_tch)




350/712

Then, sum it up over the period for super TRXs and divide it by the number of hours in the period. traffic (super) 100 x --------------- 100% hours Counters from table(s): p_nbsc_underlay

Super TRX TCH traffic, S4 (trf_10a)

Note: Cannot be calculated by a simple SQL*Plus statement. Formula: sum over BTS (avg per each super TRX (ave_busy_tch))

Average SDCCH traffic, erlang, S2 (trf_11)

Known problems: SDCCH seizures are too short to be counted using 20s sampling time. Formula: sum of traffic sum(ave_busy_sdcch / res_av_denom15) --------------- = -------------------------------------- nbr of records count(*) Counters from table(s): p_nbsc_res_avail




351/712

Average SDCCH traffic, erlang, S2 (trf_11a)

Known problems: SDCCH seizures are too short to be counted using 20s sampling if traffic is low (less than 0.5 Erl). Note: Gives the same results as trf_11. Experiments showed that results match well with trf_45. Formula: avg(ave_busy_sdcch / res_av_denom15) Counters from table(s): p_nbsc_res_avail

Average SDCCH traffic, erlang, S2 (trf_11b)

Known problems: SDCCH seizures are too short to be counted using 20 s sampling if traffic is low (less than 0.5 Erl). Note: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Formula: sum(ave_busy_sdcch) / sum(res_av_denom15) Counters from table(s): p_nbsc_res_avail

Average TCH traffic, erlang, S2 (trf_12)

Formula: sum of traffic sum(ave_busy_tch / res_av_denom14) --------------- = -------------------------------------- nbr of records count(*) Counters from table(s): p_nbsc_res_avail




352/712

Average TCH traffic, erlang, S2 (trf_12a)

Note: Gives the same results as trf_12. On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Formula: avg(ave_busy_tch / res_av_denom14) Counters from table(s): p_nbsc_res_avail

Average CS traffic per BTS, erlang, S2 (trf_12b)

Use: This is a speech (circuit switched) traffic indicator. Speech traffic is a basic indicator needed to see how much TCH capacity is consumed. When the traffic increases without the increase of the capacity, the probability of blocking increases. The relationship between traffic, capacity and blocking is described for speech traffic in the formula known as Erlang B.

This KPI includes all types of CS traffic (single TCH, HSCSD). Known problems: If extended cells were used, the value is correct only if used on the BTS/trx_type level. Formula: sum(ave_busy_tch) / sum(res_av_denom14) Counters from table(s): p_nbsc_res_avail

Unit: erlang




353/712

Average CS traffic per BTS, erlang, S2 (trf_12c)


This KPI includes all types of CS traffic (single TCH, HSCSD). Known problems: Formula: trf_97 ; CS traffic on normal TRXs + trf_98 ; CS traffic on extended TRXs

Unit: erlang

Average CS traffic per BTS, erlang, S2 (trf_12d)


This KPI includes all types of CS traffic (single TCH, HSCSD). Known problems: this formula will not work at segment level. USe trf_12d Formula: trf_97a ; CS traffic on normal TRXs + trf_98a ; CS traffic on extended TRXs

Unit: erlang




354/712

HO / call %, S3 (trf_13)

Formula: 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_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_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) ------------------------------------------------------------- sum(tch_norm_seiz) Counters from table(s): p_nbsc_res_avail

HO / call %, S3 (trf_13a)

Formula: sum(tch_ho_seiz) 100 * ------------------ % sum(tch_norm_seiz) Counters from table(s): p_nbsc_traffic

HO / call %, (trf_13b)

Use: Indicates how stationary of mobile the traffic is. The bigger the number, the more mobile is the traffic. Using this KPI, cells with stationary traffic can be found. This is largely dependent on how much the coverage areas overlap.

Known problems: Includes also intra-cell HOs that are not so directly related to mobility.




355/712

Formula: sum(a.tch_ho_seiz) 100 * ----------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + 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) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Intra-cell HO / call %, (trf_13c)

Use: Usually illustrates the impact of interference in a non-IUO network. Known problems: See trf_13b. Formula: sum(c.cell_tch_tch) 100 * ------------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + 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) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho




356/712

HO / call %, (trf_13d)


Usable for non-IUO network. Depends on factors like the cell size and call length. Known problems: Includes also intra-cell HOs that are not so directly related to mobility. Formula: 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, opt. feature for S6) 100 * ------------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + 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, opt. feature for S6) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

HO / call %, (trf_13e)





357/712

Usable for non-IUO network. Intra-cell HOs are not included as they are not directly related to mobility. Known problems: Formula: 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, opt. feature for S6) - sum(c.cell_tch_tch) ;(Intra cell HOs) 100 * ------------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + 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, opt. feature for S6) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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

Formula: 3600 * sum_over_super_TRX(average_over_each_hour(ave_busy_tch)) --------------------------------------------------------------- sec sum_over_super_TRX(tch_succ_seiz) Counters from table(s): p_nbsc_underlay




358/712

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

Formula: call time/tch seizures = average period duration * average traffic / tch seizures. avg of BTS (avg. of TRX (period_duration))* 60 ! Avg.call time in seconds * sum of BTS (avg. of super TRX(ave_busy_tch)) = ------------------------------------------------------------------------- sec sum of BTS( sum of super TRX(tch_succ_seiz)) Counters from table(s): p_nbsc_underlay

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

call time/tch seizures = average period duration * average traffic / tch seizures. avg of BTS (avg of TRX (period_duration))* 60 ! Avg.call time in seconds * sum of BTS (sum of super TRX(ave_busy_tch)) = ------------------------------------------------------------------------ sec sum of BTS( sum of super TRX(tch_succ_seiz)) Counters from table(s): p_nbsc_underlay

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

Formula: 3600 * sum of regular TRX(average over each hour(ave_busy_tch)) --------------------------------------------------------------- sec sum of regular TRX(tch_succ_seiz)




359/712


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

Formula: call time/tch seizures = average period duration * average traffic / tch seizures. avg of BTS (avg of TRX (period_duration)) * 60 * sum of BTS (avg of regular TRX(avg_trx_traf)) = ------------------------------------------------------ sec sum of BTS( sum of regular TRX(tch_succ_seiz)) Counters from table(s): p_nbsc_underlay

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

Formula: call time/tch seizures = average period duration * average traffic / tch seizures. avg of BTS (avg of TRX (period_duration)) * 60 * sum of BTS (sum of regular TRX(avg_trx_traf)) = ------------------------------------------------------ sec sum of BTS( sum of regular TRX(tch_succ_seiz)) Counters from table(s): p_nbsc_underlay

Average TRX traffic, IUO, S4 (trf_16)

Formula: avg(ave_busy_tch)




360/712


Average TRX TCH seizure length, IUO, S4 (trf_17)

Formula: count(*) avg(ave_busy_tch) * 3600 --------------------------------- sum(tch_succ_seiz) Counters from table(s): p_nbsc_underlay

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

Formula: count(*) avg(ave_busy_tch) * period_duration * 60 ------------------------------------------------- sum(tch_succ_seiz) Counters from table(s): p_nbsc_underlay

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

Formula: sum(ave_busy_tch * period_duration * 60) ----------------------------------------------- sum(tch_succ_seiz)




361/712

Counters from table(s): p_nbsc_underlay Unit: second

TCH requests for a new call, S3 (trf_18)

Known problems: A interface pool circuit type mismatch related retries are included. Formula: sum(tch_call_req) Counters from table(s): p_nbsc_traffic

TCH requests for a new call, S3 (trf_18a)

Formula: 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) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho




362/712

Peak busy TCH, (trf_19)

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

Known problems: The formula is correct only if no data of extended TRXs is shown on BTS / TRX-type level. Formula: max(peak_busy_tch) Counters from table(s): p_nbsc_res_avail

Peak busy TCH, (trf_19a)

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

Known problems: Formula: trf_109 ; peak busy TCH on normal TRXs + trf_110 ; peak busy TCH on extended TRXs Counters from table(s): p_nbsc_res_avail

Average unit load, (trf_20)

Formula:




363/712

sum(load_rate)/sum(load_denom1) Counters from table(s): p_nbsc_load

Call time difference between TRXs, S4 (trf_21)

Use: Shows as a percentage how much bigger the traffic of the busiest TRX of a BTS is compared to the least busy TRX of the same BTS. Formula: 100 * (max_call_samples - min_call_samples)/min_call_samples where max_call_samples are the call samples of the busiest TRX of a BTS: max((ul_calls + dl_calls)/2) and min_call_samples are the call samples of the least busy TRX of a 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




364/712

+ 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

Call time difference between TRXs, S4 (trf_21a)

Use: Shows how many times bigger the traffic of the busiest TRX of a BTS is compared to the least busy TRX of the same BTS. Formula: max_call_samples/min_call_samples where max_call_samples are the call samples of the busiest TRX of a BTS: max((ul_calls + dl_calls)/2) and min_call_samples are the call samples of the least busy TRX of a 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)




365/712

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

Number of mobiles located in cell, BSC, (trf_23)

Formula: (sum of LU - sum of incom.HO from other LA) * LU period ------------------------------------------------------- nbr of measurement periods (sum(a.sdcch_loc_upd) - sum of incom.HO from other LA) * b.timer_periodic_update_ms ----------------------------------------------------------------------------------- count(*) Counters from table(s): a = p_nbsc_res_access b = c_bts

The sum of incoming handovers from other location areas has to be counted from p_nbsc_ho_adj using the LA info from the c_bts table.




366/712

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

Use: If counted over an area, it could be possible to derive a KPI called ’Call minutes per MS’ from this formula. If used over a cell, it can give you an idea about how potential the cell is, for example. Formula: 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 = number 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 - nbr of incom.HO from other LA) * 0.1*b.timer_periodic_update_ms ------------------------------------------------------------------------- count(*).a.period_duration/60 Counters from table(s):




367/712

a = p_nbsc_res_access b = c_bts

The sum of incoming handovers from other location areas has to be counted from p_nbsc_ho_adj using the LA info from the c_bts table. Note: * b.timer_periodic_update_ms and a.period_duration should be of the same unit, minutes, for example. Total TCH seizure time (call time, seconds), (trf_24b)

Note: The sampling takes place every 20 seconds. Ave_busy_tch counts cumulatively the number of busy TCHs. Res_av_denom14 counts the number of samples taken.

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

Formula: sum(period_duration * 60 * ave_busy_tch/res_av_denom14) Counters from table(s): p_nbsc_res_avail unit = seconds

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

Note: 1. See trf_24b. 2. On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Formula: sum(period_duration * ave_busy_tch / res_av_denom14/60)




368/712

Counters from table(s): p_nbsc_res_avail unit = hour (Erlang hour)

Total TCH seizure time (call time, hours), Area, (trf_196)

Note: 1. See trf_24b. Formula: ( sum(period_duration * ave_busy_tch ) ------------------------------------- avg(res_av_denom14) * count (distinct period_start_time) )/60 Counters from table(s): p_nbsc_res_avail unit = hour (Erlang hour)

SDCCH true seizures, (trf_25)

Known problems: There is no counter for IMSI detaches until in release S7. Formula: sum(succ_seiz_term + succ_seiz_orig + sdcch_call_re_est + sdcch_emerg_call + sdcch_loc_upd) Counters from table(s): p_nbsc_res_access




369/712

SDCCH true seizures S7, (trf_25a)

Known problems: There is no counter for supplementary service requests until in release S9. Formula: sum(succ_seiz_term + succ_seiz_orig + sdcch_call_re_est + sdcch_emerg_call + sdcch_loc_upd + imsi_detach_sdcch) Counters from table(s): p_nbsc_res_access

SDCCH true seizures for call and SS, (trf_26)

Known problems: Supplementary services cannot be separated currently on the cell level. Formula: sum(succ_seiz_term + succ_seiz_orig + sdcch_call_re_est + sdcch_emerg_call - succ_sdcch_sms_est - unsucc_sdcch_sms_est) Counters from table(s): p_nbsc_res_access




370/712

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

Known problems: Supplementary services cannot be separated. Formula: sum(succ_seiz_term + succ_seiz_orig + sdcch_call_re_est + sdcch_emerg_call) Counters from table(s): p_nbsc_res_access

Peak busy SDCCH seizures, BTS (trf_28)

Use: The peak value of SDCCH usage is needed for preventive capacity monitoring on the cell level. Known Problem: this can not be used on Area level. Peak of Area cannot be seen from this counter. Formula: max(peak_busy_sdcch) Counters from table(s): p_nbsc_res_avail




371/712

IUO layer usage %, (trf_29)

Formula: 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) Counters from table(s): p_nbsc_underlay

SDCCH seizures, (trf_30)

Use: This figure tells the number of all events that have seized SDCCH. Formula: sum(sdcch_assign + sdcch_ho_seiz) Counters from table(s): p_nbsc_traffic




372/712

Started calls, (trf_31)

Use: This figure tells the number of all new calls that have successfully seized TCH. It includes calls started directly in the cell or via Directed Retry.

Formula: sum(a.tch_norm_seiz) + sum(b.msc_i_sdcch_tch + b.bsc_i_sdcch_tch) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

Call time (minutes) from p_nbsc_res_avail, (trf_32)

Formula: sum(period_duration * ave_busy_tch/res_av_denom14) Counters from table(s): p_nbsc_res_avail unit = minutes

Non-AMR call time from p_nbsc_rx_qual, (trf_32a)

Use: TCH use time. Does not include AMR calls (S10). For S10 and later see trf_115, trf_116, trf_117, trf_118. Known problems: In a high load situation (OMU link) it is possible that all call time is not measured. In other words, call time can show a lower value

than it has in reality. Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality.




373/712

Formula: 0.48* sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 + freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7) /60 Counters from table(s): p_nbsc_rx_qual unit = minutes

Call time from p_nbsc_rx_statistics, (trf_32b)

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

0.48* sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 + freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7) /60




374/712

Counters from table(s): p_nbsc_rx_statistics unit = minutes

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

Formula: sum(sdcch_ho_seiz) 100 * -------------------- % sum(sdcch_seiz_att)


SDCCH assignment % out of SDCCH seizure attempts, (trf_34)

Formula: sum(sdcch_assign) 100 * -------------------- % sum(sdcch_seiz_att ) Counters from table(s): p_nbsc_traffic

TCH HO seizure % out of TCH HO seizure requests, (trf_35)

sum(tch_ho_seiz 100 * ---------------------------------------------- % sum(tch_request - tch_call_req - tch_fast_req)




375/712


TCH normal seizure % out of TCH call requests, (trf_36)

Formula: sum(tch_norm_seiz) 100 * -------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic

TCH normal seizure % out of TCH call requests, (trf_36a)

Formula: sum(tch_norm_seiz) - sum(tch_succ_seiz_for_dir_acc) ; ref.1 100 * -------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic

Ref.1 tch_norm_seiz is triggered also in case of DAC. TCH FCS seizure % out of TCH FCS attempts, (trf_37)

Formula: sum(tch_seiz_due_sdcch_con) 100 * ----------------------------------- %




376/712

sum(tch_seiz_att_due_sdcch_con) Counters from table(s): p_nbsc_traffic

TCH FCS (due to SDCCH congestion) seizure % out of SDCCH seizure attempts, (trf_38)

Use: Indicates the percentage how many SDCCH seizures are saved by FACCH call setup. Formula: sum(tch_seiz_due_sdcch_con) 100 * ----------------------------- % sum(sdcch_seiz_att) Counters from table(s): p_nbsc_traffic

TCH seizures for new calls (trf_39)

Formula: sum(a.tch_norm_seiz) ;(normal calls) + 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) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho




377/712

TCH seizures for new calls, S7 (trf_39a)

Formula: sum(a.tch_norm_seiz) ;(normal calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + 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) + sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Ref.2. Compensation is needed since in the case of Direct Access to super reuse TRX the counter tch_norm_seiz is triggered in parallel with cell_sdcch_tch. HTCH usage, S5 (trf_40)

Use: On the area level gives you an idea of how well the capacity is used. Use with S5 or a later version. Formula: sum(ave_tch_busy_halfl) 100 * -------------------------- % sum(ave_tch_avail_half) Counters from table(s): p_nbsc_res_avail




378/712

MOC rate, S6 (trf_41)

Known problems: Do not include SMS, SS ==> Better accuracy for speech calls than if 3012 and 3013 were used. If SDCCH were congested and FACCH used for SMS (SS?), also SMS and SS get included. Formula: tch_moc_seiz_att 100 * ------------------------------------ % tch_moc_seiz_att + tch_mtc_seiz_att Counters from table(s): p_nbsc_traffic

MTC rate, S6 (trf_42)

Known problems: Do not include SMS, SS ==> Better accuracy for speech calls than if 3012 and 3013 used. If SDCCH congested and FACCH used for SMS (SS?) then also SMS and SS get included. Formula: tch_moc_seiz_att 100 * ------------------------------------ % tch_moc_seiz_att + tch_mtc_seiz_att Counters from table(s): p_nbsc_traffic




379/712

TCH single band subscriber holding time, S6 (trf_43)

Formula: 0.48* sum(tch_single_band_hold_time) Counters from table(s): p_nbsc_dual_band Unit: seconds

TCH dual band subscriber holding time, S6 (trf_44)

Formula: 0.48* sum(tch_dual_band_hold_time) Unit: second Counters from table(s): p_nbsc_dual_band

Average SDCCH traffic, S1 (trf_45)

Description: Average SDCCH traffic Note: For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs, keeping in mind

the note above. Formula: SDCCH used time / period duration = (sum(a.ave_sdcch_hold_tim) / sum(a.res_av_denom16) * 100)




380/712

*sum(b.sdcch_assign + b.sdcch_ho_seiz + b.tch_seiz_due_sdcch_con) ----------------------------------------------------------------- sum(a.period_duration*60) Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_traffic Unit: Erlang

TCH data call seizures, (trf_46)

Formula: 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 csf_2b Counters from table(s): p_nbsc_traffic

Share of single band traffic (trf_47)

Formula:




381/712

sum(tch_single_band_hold_time) 100 * -------------------------------------------------------- % sum(tch_single_band_hold_time + tch_dual_band_hold_time) Counters from table(s): p_nbsc_dual_band.

Share of dual band traffic (trf_48)

Formula: sum(tch_dual_band_hold_time) 100 * -------------------------------------------------------- % sum(tch_single_band_hold_time + tch_dual_band_hold_time) Counters from table(s): p_nbsc_dual_band.

Call retries due to air interface pool mismatch (trf_49)

Use: Compensates the blocking caused by the A interface circuit pool mismatch. Formula: 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)




382/712


HO retries due to air interface pool mismatch (trf_50)

Use: Compensates the blocking caused by the A interface circuit pool mismatch. Formula: Sum(bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho + ho_unsucc_a_int_circ_type) Counters from table(s): p_nbsc_ho

TCH single band subscribers share of holding time, S6 (trf_51)

Formula: sum(tch_single_band_hold_time) 100 * -------------------------------------------------------- % sum(tch_single_band_hold_time + tch_dual_band_hold_time) Counters from table(s): p_nbsc_dual_band




383/712

TCH dual band subscribers share of holding time, S6 (trf_52)

Formula: sum(tch_dual_band_hold_time) 100 * -------------------------------------------------------- % sum(tch_single_band_hold_time + tch_dual_band_hold_time) Unit: second. Counters from table(s): p_nbsc_dual_band

Calls started as FACCH call setup (trf_53)

Use: If there is SDCCH congestion and dynamic SDCCH allocation is not capable of allocating more SDCCH, the signalling can take place on TCH if there is free capacity, and a call can be established.

Formula: sum(tch_seiz_att_due_sdcch_con) Unit: second Counters from table(s): p_nbsc_traffic

SDCCH seizures (trf_54)

Formula: sum(sdcch_assign + sdcch_ho_seiz)




384/712


TCH normal seizures, (trf_55)

Formula: sum(tch_norm_seiz) - sum(tch_succ_seiz_for_dir_acc) ; ref.1 Counters from table(s): p_nbsc_traffic

Ref.1 The counter tch_norm_seiz is triggered also in the case of DAC. Total FTCH seizure time (trf_56)

Formula: sum(period_duration * ave_tch_busy_full/60) Counters from table(s): p_nbsc_res_avail unit = hour

Total HTCH seizure time (trf_57)

Formula: sum(period_duration * ave_tch_busy_half/60)




385/712

Counters from table(s): p_nbsc_res_avail unit = hour

Average HSCSD traffic, S7HS (trf_58)

Use: The numerator counts the cumulative sum of the TCH holding times for HSCSD. The numerator is the number of HSCSD TCH releases.

Known problems: Incorrect if extended TRXs is used and not counted on BTS/trx_type level. Formula: sum(ave_tch_hold_time_hscsd_numer) ---------------------------------------- sec sum(ave_tch_hold_time_hscsd_denom) * 100 Counters from table(s): p_nbsc_res_avail

Average HSCSD traffic, S7HS (trf_58a)

Use: The numerator counts the cumulative sum of the TCH holding times for HSCSD. The numerator is the number of HSCSD TCH releases.

Known problems: Formula: trf_99 + trf_100




386/712

Average busy TCH for HSCSD, S7HS (trf_59)

Formula: sum(ave_busy_tch_hscsd_numer) ----------------------------- sum(ave_busy_tch_hscsd_denom) Counters from table(s): p_nbsc_res_avail

Average HSCSD main channel traffic, S7HS (trf_60)

Use: Formula: sum(ave_hscsd_users_numer) -------------------------- sum(ave_hscsd_users_denom) Counters from table(s): p_nbsc_res_avail Unit: erlang

Average HSCSD main channel traffic, S7HS (trf_60a)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Formula: trf_104 ; HSCSD main channel traffic, normal TRXs + trf_105 ; HSCSD main channel traffic, extended TRXs




387/712

Unit: erlang

Average HSCSD main channel traffic, Area S7HS (trf_194)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Formula: trf_177 ; HSCSD main channel traffic, normal TRXs + trf_178 ; HSCSD main channel traffic, extended TRXs Unit: erlang

Total HSCSD TCH seizure time (call time, hours), S7HS (trf_61)

Formula: sum(period_duration*ave_busy_tch_hscsd_numer/ave_busy_tch_hscsd_denom/60) Counters from table(s): p_nbsc_res_avail unit = hour

Average upgrade pending time, HSCSD, S7HS (trf_62)

Formula: sum(ave_pend_time_numer) ---------------------------- sum(ave_pend_time_denom)*100




388/712

Counters from table(s): p_nbsc_high_speed_data Unit: sec

Average upgrade pending time due to congestion HSCSD, S7HS (trf_63)

Formula: sum(ave_pend_time_due_cong_numer) --------------------------------------- sum(ave_pend_time_due_cong_denom) * 100 Counters from table(s): p_nbsc_high_speed_data Unit: second

Total reporting time of ph1 and ph2 mobiles, (trf_64)

Description: Total reporting time of ph1 and ph2 mobiles. Formula: sum(rep_time_by_ph_1_ms + rep_time_by_ph_2_ms) * 0,46/60 Counters from table(s): p_nbsc_ms_capability Unit: min

Total TCH seizures, (trf_65)

Formula: sum(tch_reserv_by_mslot_cl_1_ms + … + tch_reserv_by_mslot_cl_18_ms




389/712

+ tch_reserv_by_mslot_incap_ms) Counters from table(s): p_nbsc_ms_capability

UL GPRS capacity usage, S9PS (trf_66)

Known proble ms: The denominator also contains resources that are disabled. Therefore this KPI can show unrealistically small values.Formula: Data blocks transmitted in UL 100 * ------------------------------------------------------------ % = (available GPRS channel time in sec) * (nbr of blocks per sec) sum(b.rlc_data_blocks_ul_cs1 + b.rlc_data_blocks_ul_cs2 + b.rlc_mac_cntrl_blocks_ul) 100 * ---------------------------------------------------------- % sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

DL GPRS capacity usage, S9PS (trf_67)

Known problems: The denominator also contains resources that are disabled. Therefore this KPI can show unrealistically small values.Formula: Data blocks transmitted in DL




390/712

100 * ------------------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum(b.rlc_data_blocks_dl_cs1 + b.rlc_data_blocks_dl_cs2 + b.rlc_mac_cntrl_blocks_dl) 100 * ----------------------------------------------------------- % sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

Average single TCH CS traffic, erlang, S2 (trf_68)

Use: This KPI includes only single TCH CS traffic (HSCSD excluded). Known problems: For extended cells shows the correct value only if used on the BTS/trx_type level. sum(ave_busy_tch)/sum(res_av_denom14) ; all CS traffic - sum(ave_busy_tch_hscsd_numer)/sum(ave_busy_tch_hscsd_denom) ; HSCSD traffic

Counters from table(s): p_nbsc_res_avail

Unit: erlang

Average single TCH CS traffic, erlang, S2 (trf_68a)

Use: This KPI includes only single TCH CS traffic (HSCSD excluded). Formula: trf_97 ; all CS traffic, normal TRXs




391/712

+ trf_98 ; all CS traffic, extended TRXs - trf_99 ; all HSCSD traffic, normal TRXs - trf_100 ; all HSCSD traffic, extended TRXs Unit: erlang

Net UL data traffic per TSL, S9PS (trf_69)

Use: Gives feeling how effectively the GPRS time slots are used. Known problems: Formula: data in kilobits ------------------------------------------------------- = total time * average nbr of GPRS timeslots sum(a.RLC_data_blocks_UL_CS1 * (20+3) + a.RLC_data_blocks_UL_CS2 * (30+3))* 8/1000 ----------------------------------------------------------- sum(b.period_duration*60) * sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den) Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_res_avail Unit: kbit/sec/tsl

Net UL data traffic per TSL, S9PS (trf_69a)

Use: Gives feeling how effectively the GPRS time slots are used. Formula:




392/712

data in kilobits ------------------------------------------------------- = total time * average nbr of GPRS timeslots sum(a.RLC_data_blocks_UL_CS1 * 20 + a.RLC_data_blocks_UL_CS2 * 30)* 8/1000 ------------------------------------------------------------- sum(b.period_duration*60) * sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den) Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_res_avail Unit: kbit/sec/tsl

Net DL data traffic per TSL, S9PS (trf_70)

Use: Gives a feeling how effectively the GPRS timeslots are used. Formula: data in kilobits ------------------------------------------------------- = total time * average nbr of GPRS timeslots sum(a.RLC_data_blocks_DL_CS1 * (20+3) + a.RLC_data_blocks_DL_CS2 * (30+3))* 8/1000 ------------------------------------------------------------- sum(b.period_duration*60) * sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den) Counters from table(s): a = p_nbsc_packet_control_unit




393/712

b = p_nbsc_res_avail Unit: kbit/sec/tsl

Net DL data traffic per TSL, S9PS (trf_70a)

Use: Gives a feeling how effectively the GPRS timeslots are used. Formula: data in kilobits ------------------------------------------------------- = total time * average nbr of GPRS timeslots sum(a.RLC_data_blocks_DL_CS1 * 20 + a.RLC_data_blocks_DL_CS2 * 30)* 8/1000 ------------------------------------------------------------------------------- sum(b.period_duration*60) * sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den) Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_res_avail Unit: kbit/sec/tsl

spare (trf_71)

Use: Formula:




394/712

Average UL throughput per allocated TSL, S9PS (trf_72)

Use: Indicates the gross data rate per allocated channel. The lower the value, the more loaded is the GPRS territory and the less the MS users receive service.

The numerator does not contain the RLC header bytes (2) neither does the MAC header (1). Known problems: The formula works after S9 CD1.2, see ave_dur_UL_TBF_sum Formula: data in kilobits/ TBF total time ---------------------------------- = average allocated tsl (sum(RLC_data_blocks_UL_CS1 * (20+3) + RLC_data_blocks_UL_CS2 * (30+3))* 8/1000 ------------------------------------------------- sum(Nbr_of_UL_TBF) * sum(Ave_dur_UL_TBF_sum/100) / sum(Ave_dur_UL_TBF_den) ) ---------------------------------------------------------------- (sum(alloc_1_TSL_UL + 2*alloc_2_TSL_UL + 3*alloc_3_TSL_UL + 4*alloc_4_TSL_UL) ----------------------- sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_3_TSL_UL + alloc_4_TSL_UL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl




395/712

Average UL throughput per allocated TSL, S9PS (trf_72a)

Use: Indicates the net data rate per allocated channel. The lower the value, the more loaded is the GPRS territory and the less the MS users receive service.

The numerator does not contain the RLC header bytes (2) neither does the MAC header (1). Known problems: 1) The formula works after S9 CD1.2, see ave_dur_UL_TBF_sum. 2) The number of TBFs (MS) sharing the same timeslots varies. Formula: data in kilobits/ TBF total time ---------------------------------------- = average allocated tsl (sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30) * 8/1000 -------------------------------------------------------- sum(Nbr_of_UL_TBF) * sum(Ave_dur_UL_TBF_sum/100) / sum(Ave_dur_UL_TBF_den) ) ----------------------------------------------------------------- (sum(alloc_1_TSL_UL + 2*alloc_2_TSL_UL + 3*alloc_3_TSL_UL + 4*alloc_4_TSL_UL) ------------------------ sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_3_TSL_UL + alloc_4_TSL_UL)) Counters from table(s): p_nbsc_packet_control_unit




396/712

Unit: kbit/sec/tsl

Average UL throughput per allocated TSL, S9PS (trf_72b)

Use: Indicates the net data rate per allocated channel. The lower the value, the more loaded is the GPRS territory and the less service the MS users receive.

The numerator does not contain the RLC header bytes (2) neither does the MAC header (1) because the aim is to count data volume from the user’s point of view.

Known problems: 1) The formula works after S9 CD1.2, see ave_dur_UL_TBF_sum. 2) The number of TBFs (MS) sharing the same timeslots varies. 3) The data blocks of abnormally released TBFs and TBFs that are not yet released during the measurement period increase the

amount of data during the period, but are not taken into account in the duration counters, i.e. they do not increase the total duration of TBFs.

4) Another inaccuracy is the 'average allocated tsl'. Now each allocation in the formula is of equal weight. To be correct, each allocation should be weighted by its duration.

5) After S9 BSC CD 4.0, the 'Delayed TBF release' modification in PCU adds the TBF holding time and thus makes this KPI show smaller values.

Formula: data in kilobits/ TBF total time ----------------------------------- = average allocated tsl (sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30)* 8/1000 ------------------------------------------ sum(Ave_dur_UL_TBF_sum/100) -------------------------------------------------




397/712

(sum(alloc_1_TSL_UL + 2*alloc_2_TSL_UL + 3*alloc_3_TSL_UL + 4*alloc_4_TSL_UL) ----------------------- sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_3_TSL_UL + alloc_4_TSL_UL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl

Average UL throughput per allocated TSL, S9PS (trf_72c)









398/712

5) After S9 BSC CD 4.0, the 'Delayed TBF release' modification in PCU adds the TBF holding time and thus makes this KPI show smaller values. 6) Long TBFs cause an error because RLC counters are incremented for every measurement period but the TBF duration related counters are incremented only when the TBF is normally released.

Formula: data in kilobits/ TBF total time ----------------------------------- = average allocated tsl (sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30)* 8/1000 ----------------------------------------- sum(ave_dur_UL_TBF_sum/100 + sum(ave_dur_UL_TBF_unack_mode_sum/100))) ------------------------------------------------- (sum(alloc_1_TSL_UL + 2*alloc_2_TSL_UL + 3*alloc_3_TSL_UL + 4*alloc_4_TSL_UL) ------------------------ sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_3_TSL_UL + alloc_4_TSL_UL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl




399/712

Average effective UL throughput per used TSL, S9PS (trf_72d)

Use: Indicates the net data rate per used timeslot. The lower the value the more loaded is the GPRS territory and the less service the MS users receive.

The numerator does not contain the RLC header bytes neither does the MAC header because the aim is to count data volume from the user’s point of view as close as possible.

The denominator is built on the fact that one timeslot can carry 50 RLC blocks per second. Known problems: 1) The numerator is not yet pure user data but as close to that as we can see from BSC counters. 2) Note that this KPI has correlation with DL data because rlc_mac_cntrl_blocks_ul gets triggered for each Packet Downlink

ACK/NACK. If the DL retransmissions get more frequent (radio interface quality worse or polling parameters have been modified) the polling becomes more frequent and therefore rlc_mac_cntrl_blocks_ul gets triggered more often. This leads to a situation where the effective UL throughput seems to get worse even though nothing really has changed in UL.

Formula: UL payload data in (kilobit) --------------------------------- = UL time for data transfer (sec) sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30)*8 /1000 -------------------------------------------------------------------- sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2




400/712

+ BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50 Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl

Average effective UL throughput per used TSL, S9PS (trf_72e)

Use: Indicates the net data rate per used timeslot. The lower the value, the more loaded is the GPRS territory and the less service the MS users receive.


The denominator is built on the fact that one timeslot can carry 50 RLC blocks per second. Known problems: 1) The numerator is not yet pure user data but as close to that as we can see from BSC counters. 2) rlc_mac_cntrl_blocks_ul has not been included in UL time for data transfer because the counter is largely influenced by DL traffic.

This counter is updated for Packet DL ACK/NACK. For details on this, refer to the comments in trf_72d. IGNOR_RLC_DATA_BL_UL_DUE_BSN is not included in counting for UL time, because that data is discarded and doesn't represent user traffic.

Formula: UL payload data in (kilobit) ---------------------------------------- = UL time for data transfer (sec) sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30)*8 /1000




401/712

-------------------------------------------------------------------- sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK) /50 Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl

Use: Indicates the net data rate per used timeslot. The lower the value the more loaded is the GPRS territory and the less service the MS

users receive. The numerator does not contain the RLC header bytes neither does the MAC header because the aim is to count data volume from

the user’s point of view as close as possible. The denominator is built on the fact that one timeslot can carry 50 RLC blocks per second. Known problems: 1) The numerator is not yet pure user data but as close to that as we can see from BSC counters.

Formula: UL payload data in (kilobits) ---------------------------------------- = UL time for data transfer (sec) sum(a.RLC_data_blocks_UL_CS1*20+a.RLC_data_blocks_UL_CS2*30)*8 /1000 + (sum over MCS-1 (xx)*22 + sum over MCS-2 (xx)*28 + sum over MCS-3 (xx)*37




402/712

+ sum over MCS-4 (xx)*44 + sum over MCS-5 (xx)*56 + sum over MCS-6 (xx)*74 + sum over MCS-7 (xx)*56 + sum over MCS-8 (xx)*68 + sum over MCS-9 (xx)*74)*8/1000 -------------------------------------------------------------------- sum(a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 + a.rlc_mac_cntrl_blocks_ul + a.BAD_FRAME_IND_UL_CS1 + a.BAD_FRAME_IND_UL_CS2 + a.BAD_FRAME_IND_UL_UNACK + a.IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50 + sum over MSC1…6 of (yy)/50 + sum over MSC7…9 of (yy)/2 /50 where xx = b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode yy = b.ul_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_ul + b. bad_rlc_valid_hdr_ul_ack + b.bad_rlc_valid_hdr_ul_unack + b.ul_rlc_blocks_in_unack_mode Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_coding_scheme

Average effective UL throughput per used TSL, S10PS (trf_72g)

Origin: PMWG Based on trf_72f. 13.11.01




403/712


The numerator does not contain the RLC header bytes neither the does the MAC header because the aim is to count data volume from the user’s point of view as close as possible.

The denominator is built on the fact that one timeslot can carry 50 RLC blocks per second. Known problems: 1) The numerator is not yet pure user data but as close to that as we can see from BSC counters.

Formula: UL payload data in (kilobits) --------------------------------- = UL time for data transfer (sec) sum(a.RLC_data_blocks_UL_CS1*20+a.RLC_data_blocks_UL_CS2*30)*8 /1000 + (sum over MCS-1 (xx)*22 + sum over MCS-2 (xx)*28 + sum over MCS-3 (xx)*37 + sum over MCS-4 (xx)*44 + sum over MCS-5 (xx)*56 + sum over MCS-6 (xx)*74 + sum over MCS-7 (xx)*56 + sum over MCS-8 (xx)*68 + sum over MCS-9 (xx)*74)*8/1000 -------------------------------------------------------------------- sum(a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 + a.BAD_FRAME_IND_UL_CS1 + a.BAD_FRAME_IND_UL_CS2 + a.BAD_FRAME_IND_UL_UNACK + a.IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50 + sum over MSC1…6 of (yy)/50




404/712

+ sum over MSC7…9 of (yy)/2 /50 where xx = b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode yy = b.ul_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_ul + b.bad_rlc_valid_hdr_ul_ack + b.bad_rlc_valid_hdr_ul_unack + b.ul_rlc_blocks_in_unack_mode Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_coding_scheme

Average effective UL throughput per used TSL, S10PS (trf_72h)


The numerator does not contain the RLC header bytes neither the does the MAC header because the aim is to count data volume from the user’s point of view as close as possible.


Formula: UL payload data in (kilobits) ---------------------------------- = UL time for data transfer (sec)




405/712

sum(a.RLC_data_blocks_UL_CS1*20+a.RLC_data_blocks_UL_CS2*30)*8 /1000 + (sum over MCS-1 (xx)*22+ + sum over MCS-2 (xx)*28+ + sum over MCS-3 (xx)*37+ + sum over MCS-4 (xx)*44+ + sum over MCS-5 (xx)*56+ + sum over MCS-6 (xx)*74+ + sum over MCS-7 (xx)*56+ + sum over MCS-8 (xx)*68+ + sum over MCS-9 (xx)*74)*8/1000 -------------------------------------------------------------------- sum(a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 + a.BAD_FRAME_IND_UL_CS1 + a.BAD_FRAME_IND_UL_CS2 + a.BAD_FRAME_IND_UL_UNACK + a.IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50 + sum over MSC1…6 of (yy)/50 + sum over MSC7…9 of (yy)/2 /50 where xx = b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode yy = b.ul_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_ul + b.bad_rlc_valid_hdr_ul_unack + b.ul_rlc_blocks_in_unack_mode Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_coding_scheme




406/712

Average DL throughput per allocated TSL, S9PS (trf_73)

Use: Indicates the gross data rate per allocated channel. The lower the value, the more loaded is the GPRS territory and the less the MS users receive service.

The numerator does not contain the RLC header bytes (2) neither does the MAC header (1). Known problems: The formula works after S9 CD1.2, see ave_dur_UL_TBF_sum Formula: data in kilobits/ TBF total time ----------------------------------- = average allocated tsl (sum(RLC_data_blocks_DL_CS1 * (20+3) + RLC_data_blocks_DL_CS2 * (30+3))* 8/1000 ----------------------------------------------- sum(Nbr_of_DL_TBF) * sum(Ave_dur_DL_TBF_sum/100) / sum(Ave_dur_DL_TBF_den) ) ----------------------------------------------------------------- (sum(alloc_1_TSL_DL + 2*alloc_2_TSL_DL + 3*alloc_3_TSL_DL + 4*alloc_4_TSL_DL) ------------------------- sum(alloc_1_TSL_DL + alloc_2_TSL_DL + alloc_3_TSL_DL + alloc_4_TSL_DL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl




407/712

Average DL throughput per allocated TSL, S9PS (trf_73a)

Use: Indicates the net data rate per allocated channel. The lower the value, the more loaded is the GPRS territory and the less the MS users receive service.

The numerator does not contain the RLC header bytes (2) neither does the MAC header (1). Known problems: The formula works after S9 CD1.2, see ave_dur_UL_TBF_sum. Formula: data in kilobits/ TBF total time ---------------------------------------- = average allocated tsl (sum(RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)* 8/1000 ------------------------------------------- sum(Nbr_of_DL_TBF) * sum(Ave_dur_DL_TBF_sum/100) / sum(Ave_dur_DL_TBF_den) ) ---------------------------------------------------------------- (sum(alloc_1_TSL_DL + 2*alloc_2_TSL_DL + 3*alloc_3_TSL_DL + 4*alloc_4_TSL_DL) ------------------------- sum(alloc_1_TSL_DL + alloc_2_TSL_DL + alloc_3_TSL_DL + alloc_4_TSL_DL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl




408/712

Average DL throughput per allocated TSL, S9PS (trf_73b)




amount of data during the period, but are not taken into account in the duration counters, i.e. they do not increase the total duration of TBFs. This situation occurs when TBF completion ratio tbf_26a shows a low value.



Formula: data in kilobits/ TBF total time ----------------------------------- = average allocated tsl (sum(RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)* 8/1000 ------------------------------------------ sum(Ave_dur_DL_TBF_sum/100 ) -------------------------------------------------- (sum(alloc_1_TSL_DL




409/712

+ 2*alloc_2_TSL_DL + 3*alloc_3_TSL_DL + 4*alloc_4_TSL_DL) ------------------------ sum(alloc_1_TSL_DL + alloc_2_TSL_DL + alloc_3_TSL_DL + alloc_4_TSL_DL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl

Average DL throughput per allocated TSL, S9PS (trf_73c)










410/712

6) Long TBFs cause an error because RLC counters are incremented for every measurement period but the TBF duration related counters are incremented only when the TBF is normally released.

Formula: data in kilobits/ TBF total time ----------------------------------- = average allocated tsl (sum(RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)* 8/1000 ------------------------------------------ sum(Ave_dur_DL_TBF_sum/100 + sum(AVE_DUR_DL_TBF_UNACK_MODE_SUM/100)) --------------------------------------------------- (sum(alloc_1_TSL_DL + 2*alloc_2_TSL_DL + 3*alloc_3_TSL_DL + 4*alloc_4_TSL_DL) ---------------------------- sum(alloc_1_TSL_DL + alloc_2_TSL_DL + alloc_3_TSL_DL + alloc_4_TSL_DL)) Counters from table(s): p_nbsc_packet_control_unit Unit: kbit/sec/tsl




411/712

Average effective DL throughput per used TSL, S9PS (trf_73d)




2) Retransmitted blocks due to other reasons than NACK are not counted in any of the RLC counters. In DL direction these retransmissions occur when the TBF release is delayed. 3) If there is only one TBF on a timeslot, for example, some RLC blocks can be retransmitted before an ACK is received. These blocks are not counted in any of the RLC counters. 4) Counter rlc_mac_cntrl_blocks_dl also contains dummy blocks until CD.6.1.

Formula: DL ‘payload’ data in (kilobit) ---------------------------------------- = DL time for data transfer (sec) sum(RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)*8 /1000 ----------------------------------------------------------------------- sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) /50




412/712

Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl

Average effective DL throughput per used TSL, S9PS (trf_73e)

Use: Indicates the net data rate per used timeslot. The lower the value, the more loaded is the GPRS territory and the less service the MS users receive.



2) Retransmitted blocks due to other reasons than NACK are not counted in any of the RLC counters. In DL direction these retransmissions occur when the TBF release is delayed. 3) If there is only one TBF on a timeslot, for example, some RLC blocks can be retransmitted before an ACK is received. These blocks are not counted in any of the RLC counters. 4) rlc_mac_cntrl_blocks_dl is not considered in the denominator because it has impact from UL traffic. Packet UL ACK/NACK trigger this counter. Refer to comments in trf_73d and trf_72d for details.

Formula: DL ‘payload’ data in (kilobit) ---------------------------------------- = DL time for data transfer (sec)




413/712

sum(RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)*8 /1000 ----------------------------------------------------------------------- sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) /50 Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl

Status: OK. Mail review 3.6.2003. DL payload data in (kilobits) ---------------------------------- = DL time for data transfer (sec) sum(a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)*8 /1000 + (sum over MCS-1 (xx)*22 + sum over MCS-2 (xx)*28 + sum over MCS-3 (xx)*37 + sum over MCS-4 (xx)*44 + sum over MCS-5 (xx)*56 + sum over MCS-6 (xx)*74 + sum over MCS-7 (xx)*56 + sum over MCS-8 (xx)*68 + sum over MCS-9 (xx)*74)*8/1000 --------------------------------------------------------------- sum(a.rlc_data_blocks_dl_cs1 + a.rlc_data_blocks_dl_cs2 + a.rlc_mac_cntrl_blocks_dl – a.dummy_dl_mac_blocks_sent + a.RETRA_RLC_DATA_BLOCKS_DL_CS1




414/712

+ a.RETRA_RLC_DATA_BLOCKS_DL_CS2) /50 + sum over msc1…6 of (yy)/50 + sum over msc7…9 of (yy)/2/50 where xx = b.dl_rlc_blocks_in_ack_mode + b.dl_rlc_blocks_in_unack_mode yy = b.dl_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_dl + b.dl_rlc_blocks_in_unack_mode Counters from table(s): a = p_nbsc_packet_control_unit b= p_nbsc_coding_scheme Unit: kbit/sec/tsl

Average effective DL throughput per used TSL, S10PS (trf_73g)

Origin: PMWG based on trf_73f, 22.11.2003 Use: Indicates the net data rate per used timeslot. The lower the value the more loaded is the GPRS territory and the less service the MS

users receive. The numerator does not contain the RLC header bytes neither the does the MAC header because the aim is to count data volume

from the user’s point of view as close as possible. Known problems: 1) The numerator is not yet pure user data but as close to that as we can see from BSC counters.

2) Retransmitted blocks due to other reasons than NACK are not counted in any of the RLC-counters. In DL direction these retransmissions occur when the TBF release is delayed. 3) If there is only one TBF on a timeslot, for example, some RLC blocks can be retransmitted before an ACK is received. These blocks are not counted in any of the RLC counters.




415/712

Formula: DL payload data in (kilobits) ---------------------------------------- = DL time for data transfer (sec) sum(a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)*8 /1000 + (sum over MCS-1 (xx)*22+ + sum over MCS-2 (xx)*28+ + sum over MCS-3 (xx)*37+ + sum over MCS-4 (xx)*44+ + sum over MCS-5 (xx)*56+ + sum over MCS-6 (xx)*74+ + sum over MCS-7 (xx)*56+ + sum over MCS-8 (xx)*68+ + sum over MCS-9 (xx)*74)*8/1000 --------------------------------------------- sum(a.rlc_data_blocks_dl_cs1 + a.rlc_data_blocks_dl_cs2 + a.RETRA_RLC_DATA_BLOCKS_DL_CS1 + a.RETRA_RLC_DATA_BLOCKS_DL_CS2) /50 + sum over msc1…6 of (yy)/50 + sum over msc7…9 of (yy)/2/50 where xx = b.dl_rlc_blocks_in_ack_mode + b.dl_rlc_blocks_in_unack_mode yy = b.dl_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_dl + b.dl_rlc_blocks_in_unack_mode Counters from table(s): a = p_nbsc_packet_control_unit b = p_nbsc_coding_scheme




416/712

Unit: kbit/sec/tsl

Total RLC data, S9PS (trf_74)

Use: Indicates the total amount of data transmitted as CS1 or CS2 blocks, UL or DL. Formula: (sum(RLC_data_blocks_UL_CS1*23 + RLC_data_blocks_UL_CS2*33 + RLC_data_blocks_DL_CS1*23 + RLC_data_blocks_DL_CS2*33) /1000 Counters from table(s): p_nbsc_packet_control_unit Unit: kbyte

Total RLC data, S9PS (trf_74a)

Use: Indicates the total amount of data (both ack and unack modes) transmitted as CS1 or CS2 blocks. UL or DL. MAC blocks and RLC header bytes are excluded in order to get as close as possible to the payload data.

Known problems: The divisor should be 1024 for Kbytes. Formula: (sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30) /1000 Counters from table(s): p_nbsc_packet_control_unit Unit: kbyte




417/712

Total GPRS RLC data, S9PS (trf_74b)


Formula: (sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30 + RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30) /1024 Counters from table(s): p_nbsc_packet_control_unit Unit: kbyte

GPRS territory utilisation, S9PS (trf_75)

Known problems: Formula: Data blocks transmitted in DL and UL 100 * ----------------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( b.RLC_data_blocks_UL_CS1 + b.RLC_data_blocks_UL_CS2 + b.bad_frame_ind_UL_CS1 + b.bad_frame_ind_UL_CS2 + b.RLC_data_blocks_DL_CS1 + b.RLC_data_blocks_DL_CS2 + b.retra_RLC_data_blocks_DL_CS1 + b.retra_RLC_data_blocks_DL_CS2 )




418/712

100 * ---------------------------------------------------------------- % sum(a.ave_gprs_channels_sum / sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

GPRS territory UL utilisation, S9PS (trf_76)

Known problems: Formula: Data blocks transmitted in UL 100 * ------------------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( b.RLC_data_blocks_UL_CS1 + b.RLC_data_blocks_UL_CS2 + b.bad_frame_ind_UL_CS1 + b.bad_frame_ind_UL_CS2 ) 100 * ------------------------------------------------------------- % sum(a.ave_gprs_channels_sum / sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

GPRS territory UL utilisation, S9PS (trf_76a)

Known problems: Formula:




419/712

Data blocks transmitted in UL 100 * -------------------------------------------------------------- % = (available GPRS channel time in sec) * (nbr of blocks per sec) sum( b.RLC_data_blocks_UL_CS1 + b.RLC_data_blocks_UL_CS2 + b.RLC_MAC_cntrl_blocks_UL + b.bad_frame_ind_UL_CS1 + b.bad_frame_ind_UL_CS2 ) 100 * -------------------------------------------------------------- % sum(a.ave_gprs_channels_sum / sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

GPRS territory UL utilisation %, S9PS (trf_76b)

Use: Most useful on BTS level. Used as BH (CS+PS) trend together with CS traffic, total TCH capacity and PS territory size. Indicates how big a portion of the GPRS territory has been used. When the utilisation % increases, the throughput rate perceived by the user reduces. This KPI is the way to estimate the throughput rate reduction. If the utilisation % is high, increasing the CDEF parameter setting (when CS traffic is low) or adding a new TRX (when CS traffic is high) should be considered. UL and DL should be looked at the same time and the higher one of those used in dimensioning together with CS traffic trf_12b and PS territory ava_16.




420/712

Note: The denominator varies depending on the traffic situation (downgrade of territory) and therefore this KPI has no linear correlation with the traffic. See ava_15.

Target level: Thus choosing the acceptable level is a QoS issue. For example, 60% utilisation would give about 70% of the maximum rate achieved. Formula: Data blocks transmitted in UL 100 * ------------------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN) 100 * ------------------------------------------------------------- % sum(a.ave_gprs_channels_sum)/sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

GPRS territory DL utilisation, S9PS (trf_77)

Use: BTS level. Indicates how big a portion of the GPRS territory has been used in DL direction. If the utilisation % is high, increasing the CDEF parameter setting should be considered.

Known problems: The denominator varies depending on the traffic situation and therefore this KPI has no linear correlation with the traffic. See ava_15. Formula:




421/712

Data blocks transmitted in DL and UL 100 * -------------------------------------------------------------- % = (available GPRS channel time in sec) * (nbr of blocks per sec) sum( + b.RLC_data_blocks_DL_CS1 + b.RLC_data_blocks_DL_CS2 + b.retra_RLC_data_blocks_DL_CS1 + b.retra_RLC_data_blocks_DL_CS2 ) 100 * -------------------------------------------------------------- % sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den) * sum(a.period_duration*60)*50 Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit

GPRS territory DL utilisation, S9PS (trf_77a)

Use: Most useful on BTS level. Used as BH (CS+PS) trend together with CS traffic, total TCH capacity and PS territory size.

Indicates how big a portion of the GPRS territory has been used. When the utilisation % increases, the throughput rate perceived by the user reduces. This KPI is the way to estimate the throughput rate reduction. If the utilisation % is high, increasing the CDEF parameter setting (when CS traffic is low) or adding a new TRX (when CS traffic is high) should be considered. UL and DL should be looked at the same time and the higher one of those used in dimensioning together with CS traffic trf_12b and PS territory ava_16.




422/712


Target level: Thus choosing the acceptable level is a QoS issue. For example, 60% utilisation would give about 70% of the maximum rate achieved. Known problems: Dummy blocks on DL make this PI show too high a value (fixed in CD6.0: RLC_MAC_cntrl_blocks does not contain dummy blocks

anymore). Formula: Data blocks transmitted in DL and UL 100* --------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( + b.RLC_data_blocks_DL_CS1 + b.RLC_data_blocks_DL_CS2 + b.RLC_MAC_cntrl_blocks_DL + b.retra_RLC_data_blocks_DL_CS1 + b.retra_RLC_data_blocks_DL_CS2 ) 100* --------------------------------------------------------------- % sum(a.ave_gprs_channels_sum)/sum(a.ave_gprs_channels_den) *sum(a.period_duration*60)*50 Counters from table(s): a= p_nbsc_res_avail b= p_nbsc_packet_control_unit




423/712

UL GPRS traffic, S9PS (trf_78a)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes on average during the period. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: The value is optimistic because the time needed for TBF establishment and release is not included. The delayed TBF release that was taken into use in a CD of S9 also adds the actual usage of the TCH but cannot be considered in this formula. These make the value seem smaller.

Formula: Actual UL data troughput (blocks) ------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN) ----------------------------------- sum(period_duration*60)*50 ; 50 blocks /sec /tsl Counters from table(s): p_nbsc_packet_control_unit

Unit: tsl (or erlang)




424/712

UL PS traffic, S9PS (trf_78b)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. Known problems: See trf_79a. Formula: Actual data troughput (kbit/s) ------------------------- = Troughput per timeslot (kbit/s/tsl) sum(rlc_data_blocks_ul_cs1*23 + rlc_data_blocks_ul_cs2*33 + rlc_mac_cntrl_blocks_ul*23 + BAD_FRAME_IND_UL_CS1*23 + BAD_FRAME_IND_UL_CS2*33 + BAD_FRAME_IND_UL_UNACK*23 + IGNOR_RLC_DATA_BL_UL_DUE_BSN*23)*8/1000/sum(period_duration*60) -------------------------------------------------------------------------------- sum(RLC_data_blocks_UL_CS1 /(RLC_data_blocks_UL_CS1+RLC_data_blocks_UL_CS2)*9,05 + RLC_data_blocks_UL_CS2 /(RLC_data_blocks_UL_CS1+RLC_data_blocks_UL_CS2)*13,4) Counters from table(s): p_nbsc_packet_control_unit

Unit: tsl DL PS traffic, S9PS (trf_79)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. Known problems: Does not count the MAC blocks. With current S9 counters the actual MAC blocks cannot be counted because the counter also

counts the dummy blocks.




425/712

Formula: Actual data troughput (kbit/s) ------------------------- = Troughput per timeslot (kbit/s/tsl) sum(RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*33)*8/1000/sum(period_duration*60) -------------------------------------------------------------------------------- sum(RLC_data_blocks_DL_CS1 /(RLC_data_blocks_DL_CS1+RLC_data_blocks_DL_CS2)*9,05 + RLC_data_blocks_DL_CS2 /(RLC_data_blocks_DL_CS1+RLC_data_blocks_DL_CS2)*13,4) Counters from table(s): p_nbsc_packet_control_unit

Unit: tsl DL GPRS traffic, S9PS (trf_79a)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: 1) The MS can send an UL data block only if it has received its USF in the preceding DL block. If the network has nothing else to send, it will send a Packet DL Dummy Control Block to carry the USF. These dummy blocks are included in this KPI until CD6.1 and make it show bigger values. 2) Transferred DL blocks, whose corresponding element in the transmit window V(B) has the value PENDING ACK, are not counted to any of the counters. 3) The time needed for TBF establishment and release is not included. Also the delayed TBF release that was taken into use in a CD of S9 adds the actual usage of the TCH but cannot be considered in this formula. These make the value seem smaller.

Formula:




426/712

Actual DL data troughput (blocks) ------------------------------------------------------------ = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) ---------------------------------- sum(period_duration*60)*50 ;50 blocks /sec /tsl


Unit: time slot or erlang DL PS traffic, S9PS (trf_79b)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. Known problems: See trf_79a. Formula: Actual data troughput (kbit/s) ------------------------- = Troughput per timeslot (kbit/s/tsl) sum(rlc_data_blocks_dl_cs1*23 + rlc_data_blocks_dl_cs2*33




427/712

+ rlc_mac_cntrl_blocks_dl*23 + RETRA_RLC_DATA_BLOCKS_DL_CS1*23 + RETRA_RLC_DATA_BLOCKS_DL_CS2*33)*8/1000/sum(period_duration*60) -------------------------------------------------------------------------------- sum(RLC_data_blocks_DL_CS1 /(RLC_data_blocks_DL_CS1+RLC_data_blocks_DL_CS2)*9,05 + RLC_data_blocks_DL_CS2 /(RLC_data_blocks_DL_CS1+RLC_data_blocks_DL_CS2)*13,4) Counters from table(s): p_nbsc_packet_control_unit

Unit: tsl Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. This information is useful, for example, in forecasting

the need for capacity extension. Known problems: 1) The MS can send an UL data block only if it has received its USF in the preceding DL block. If the network has nothing else to

send it will send a Packet DL Dummy Control Block to carry the USF. These dummy blocks are included in this KPI and make it show bigger values. In S10 there is a new for the dummy blocks and it can be subtracted from the numerator. 2) Transferred DL blocks, whose corresponding element in the transmit window V(B) has the value PENDING ACK, are not counted to any of the counters 3) The time needed for TBF establishment and release is not included. Also the delayed TBF release that was taken into use in a CD of S9 adds the actual usage of the TCH but cannot be considered in this formula. These make the value seem smaller.

Formula: Actual DL data troughput (blocks) ------------------------------------------------------------ = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(a.rlc_data_blocks_dl_cs1




428/712

+ a.rlc_data_blocks_dl_cs2 + a.rlc_mac_cntrl_blocks_dl + a.RETRA_RLC_DATA_BLOCKS_DL_CS1 + a.RETRA_RLC_DATA_BLOCKS_DL_CS2)

+sum over MSC1…6 of (b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+ b.dl_rlc_blocks_in_unack_mode) +sum over msc7…9 of b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+ + b.dl_rlc_blocks_in_unack_mode)/2 --------------------------------------------------------- sum(period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s): A=p_nbsc_packet_control_unit

B=p_nsbc_coding_scheme GPRS TSL usage, UL and DL, S9PS (trf_80)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes. Known problems: Formula: Actual data troughput (blocks) ---------------------------------------------- = max. nbr of blocks during measurement period sum(UL_DL_RLC_MAC_BLOCKS ---------------------------- sum(period_duration*60)*50




429/712

Counters from table(s): p_nbsc_rlc_blocks_per_trx

Unit: tsl

TCH free margin, S9PS (trf_81)

Use: Indicates the average number of free TCH timeslots. Known problems: 1) DL MAC blocks contain dummy blocks.

2) Transferred DL blocks, whose corresponding element in the transmit window V(B) has the value PENDING ACK, are not counted to any of the counters.

Formula: Capacity available for CSW+ dedicated PSW capacity - CSW traffic - PSW DL traffic ava_15+ava_16-trf_12b-trf_79a Total RLC/MAC blocks DL, S9PS (trf_82)

Use: Gives the total number of RLC/MAC blocks in DL direction. Known problems: 1) MAC blocks contain dummy blocks.

2) Transferred DL blocks, whose corresponding element in the transmit window V(B) has the value PENDING ACK, are not counted to any of the counters.

Formula:




430/712

sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2)

Unit: time slot or erlang TCH usage % for CS, (trf_83)

Use: Indicates how many % of the total available TCH capacity has been used for CS traffic on average. For the peak value, c2029 is provided.

Formula: Capacity used by CS traffic / total TCH capacity

trf_12b = 100* --------------- % ava_15+ava_16 Normal TCH usage % for CS, (trf_83a)

Use: Indicates how many % of the total available normal TCH capacity has been used for CS traffic on average. Used for trend analysis. Formula: Capacity used by CS traffic / total normal TCH capacity




431/712

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

ava_28+ava_16a Normal TCH usage % for CS, (trf_83b)


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

ava_28a + ava_16bNormal TCH usage % for CS, Area, (trf_197)


trf_202 = 100 * ----------------- % ava_52 + ava_44 Normal TCH usage % for PS, S9PS (trf_84)

Use: Indicates how many % of the total available TCH capacity has been used for PS traffic on average. Known problems: 1) It is assumed that DL PS traffic is always greater than UL PS traffic and therefore DL PS traffic has been used in this calculation. In

some circumstances on BTS level this assumption may not be true. 2) See the problems of trf_79a.




432/712

3) For the absolute peak value there is no counter available unlike for CS traffic. Formula: Capacity used by PS traffic / total TCH capacity

trf_79a = 100* --------------- % ava_15+ava_16 TCH usage % for PS, S9PS (trf_84a)

Use: Indicates how many % of the total available TCH capacity has been used for PS traffic on average. Known problems: 1) See the problems of trf_79a. 2) For the absolute peak value there is no counter available unlike for CS traffic. Formula: Capacity used by PS traffic / total TCH capacity

trf_95 = 100* ----------------------- % ava_15+ava_16 Normal TCH usage % for PS, S9PS (trf_84b)

Use: Indicates how many % of the total available normal TCH capacity has been used for PS traffic on average. Used for trend analysis. Known problems: Formula:




433/712

Capacity used by PS traffic / total TCH normal capacity

trf_95 = 100* ------------- % ava_28+ava_16a Normal TCH usage % for GPRS, S9PS (trf_84c)

Description: Percentage of TCH usage for GPRS Use: Indicates how many % of the total available normal TCH capacity has been used for GPRS traffic on average. Used for trend analysis. Known problems: Formula: Capacity used by GPRS traffic / total TCH normal capacity

trf_95a = 100 * ---------------- % ava_28 + ava_16a Unit: % Normal TCH usage % for PS, S10.5PS (trf_84d)

Description: Percentage of TCH usage for GPRS and EGPRS. Use: Indicates how many % of the total available normal TCH capacity has been used for PS traffic on average. Used for trend analysis. Known problems: Formula:




434/712

Capacity used by GPRS traffic / total TCH normal capacity trf_159 = 100 * ---------------- % ava_28 + ava_16a Unit: %

Normal TCH usage % for PS, S10.5PS (trf_84e)

Description: Percentage of TCH usage for GPRS and EGPRS. Use: Indicates how many % of the total available normal TCH capacity has been used for PS traffic on average. Used for trend analysis. Known problems: Formula: Capacity used by EGPRS traffic / total TCH normal capacity trf_159 = 100 * ----------------- % ava_28a + ava_16b Unit: %

Normal TCH usage % for PS, Area, S10.5PS (trf_198)

Description: Percentage of TCH usage for GPRS and EGPRS. Use: Indicates how many % of the total available normal TCH capacity has been used for PS traffic on average. Used for trend analysis. Known problems:




435/712

Formula: Capacity used by (E)GPRS traffic / total TCH normal capacity trf_159 = 100 * ---------------- % ava_52 + ava_44 Unit: %

Total TCH usage % for CS and PS, S9PS (trf_85)

Use: Indicates how many % of the total TCH capacity has been used for PS traffic. Known problems: It is assumed that DL PS traffic is always greater than UL PS traffic. Formula: Capacity used by CS and PS traffic / total TCH capacity

trf_12b + trf_79a = 100 * ------------------ % ava_15 + ava_16 Total TCH usage % for CS and PS, S9PS (trf_85a)





436/712

trf_12b + trf_95 = 100 * ----------------- % ava_15 + ava_16 Total TCH usage % for CS and PS, S9PS (trf_85b)


trf_12b + trf_95 = 100 * ----------------- % ava_25a Total TCH usage % for CS and GPRS, S9PS (trf_85c)

Description: Indicates percentage of the TCH use of combined CS and PS traffic Use: Indicates how many % of the total TCH capacity has been used for PS traffic. Known problems: It is assumed that DL PS traffic is always greater than UL PS traffic. Formula: Capacity used by CS and PS traffic / total TCH capacity trf_12b + trf_95a = 100 * ------------------ % ava_25a Unit: %




437/712

Total TCH usage % for CS and PS, S10.5PS (trf_85d)

Description: Indicates percentage of the TCH use of combined CS and PS traffic Use: Indicates how many % of the total TCH capacity has been used for PS traffic. Known problems: It is assumed that DL PS traffic is always greater than UL PS traffic. Formula: Capacity used by CS and PS traffic / total TCH capacity trf_12b + trf_159 = 100 * ----------------- % ava_25a Unit: %

Free TCH %, S9PS (trf_86a)

Use: Most useful on BTS level in connection with trf_83 and trf_84a. The combined (PS+CS traffic) BH value trend can be used for dimensioning. Indicates how many % of the total available TCH capacity has not been used on average. If free TCH % approaches 0, the MS users start to experience call blocking and/or that GPRS throughput slows down.

Known problems: Because the measurement period is usually 60 minutes, the value cannot be used for spotting momentary problems rather the trend only.

Formula: 100- TCH usage % for CS - TCH usage % for PS = 100 - trf_83-trf_84a




438/712

Free TCH %, S9PS (trf_86b)

Use: Most useful on BTS level in connection with trf_83 and trf_84a. The combined (PS+CS traffic) BH value trend can be used for dimensioning. Indicates how many % of the total available TCH capacity has not been used on average. If free TCH % approaches 0 the MS users start to experience call blocking and/or that GPRS throughput slows down.


Formula: 100- TCH usage % for CS - TCH usage % for PS = 100 - trf_83a-trf_84b Free TCH %, S10.5PS (trf_86c)

Description: Percentage of free TCH capacity Use: Most useful on BTS level in connection with trf_83a, trf_84c.and trf_160 The combined (PS+CS traffic) BH value trend can be used

for dimensioning. Indicates how many % of the total available TCH capacity has not been used on average. If free TCH % approaches 0 the MS users start to experience call blocking and/or that (E)GPRS throughput slows down.


Formula:




439/712

100- TCH usage % for CS - TCH usage % for GPRS - TCH usage % for EGPRS = 100 - trf_83a-trf_84b-trf_160 Unit: % Free TCH %, S10.5PS (trf_200)

Description: Percentage of free TCH capacity Use: Most useful on BTS level in connection with trf_83 and trf_84a. The combined (PS+CS traffic) BH value trend can be used for

dimensioning. Indicates how many % of the total available TCH capacity has not been used on average. If free TCH % approaches 0 the MS users start to experience call blocking and/or that GPRS throughput slows down.


Formula: 100- TCH usage % for CS - TCH usage % for PS = 100 - trf_197-trf_198 Unit: % Total TCH % for PS, (trf_87)

Use: Indicates how many % of the total available TCH capacity has been allocated for the PS territory, including additional channels. If there are now upgrades or downgrades, this value should be quite close to the value of parameter CDEF. Some difference comes

from granularity when the CDEF value is converted to timeslots in BSC.




440/712

Formula: Known problems: See problems of ava_15 in the case of anextended cell. Capacity allocated for PS territory

------------------------------------------------------ total TCH capacity of normal TRXs

ava_16 = 100* --------------- % ava_15+ava_16 Total TCH % for PS, (trf_87a)

Use: Indicates how many % of the total available normal TRX TCH capacity has been allocated for the PS territory, includingadditional channels.

If there are now upgrades or downgrades, this value should be quite close to the value of parameter CDEF. Some difference comes from granularity when the CDEF value is converted to timeslots in BSC.

Known problems: Slightly incorrect values for extended cells. Formula: The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of

CDEF to timeslots. Capacity allocated for PS territory

------------------------------------------------------ total TCH capacity of normal TRXs

ava_16 = 100* --------------- % ava_28+ava_16




441/712

Total TCH % for PS, (trf_87b)

Use: Indicates how many % of the total available normal TRX TCH capacity has been allocated for the PS territory, including additional channels.

If there are now upgrades or downgrades, this value should be quite close to the value of parameter CDEF. Some difference comes from granularity when the CDEF value is converted to timeslots in BSC. The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of CDEF to timeslots.

Known problems: Formula: Capacity allocated for PS territory -------------------------------------- total TCH capacity of normal TRXs ava_16a = 100 * ---------------- % ava_28 + ava_16a Total TCH % for PS, (trf_87c)

Use: Indicates how many % of the total available normal TRX TCH capacity has been allocated for the PS territory, including additional channels.

If there are now upgrades or downgrades, this value should be quite close to the value of parameter CDEF. Some difference comes from granularity when the CDEF value is converted to timeslots in BSC.




442/712

The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of CDEF to timeslots.

Known problems: Formula: Capacity allocated for PS territory -------------------------------------- total TCH capacity of normal TRXs ava_16b = 100 * ----------------- % ava_28a + ava_16b

Total TCH % for dedicated PS, S9PS (trf_88)

Use: Indicates how many % of the total TCH capacity has been allocated for the dedicated PS territory. This value should be quite close to the value of CDED parameter. Some difference comes from granularity when the CDED value is converted to timeslots in BSC.

Known problems: See problems of ava_15 in the case of an extended cell. Formula: Capacity allocated for dedicated PS territory --------------------------------------------- Total TCH capacity of normal TRXs

ava_17 = 100 * --------------- % ava_15 + ava_16




443/712

Total TCH % for dedicated PS, S9PS (trf_88a)

Use: Indicates how many % of the total normal TRX TCH capacity has been allocated for the dedicated PS territory. This value should be quite close to the value of the CDED parameter. Some difference comes from granularity when the CDED value is converted to timeslots in BSC.

Known problems: Slightly incorrect values for extended cells. Formula: The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of

CDED to timeslots. Capacity allocated for dedicated PS territory --------------------------------------------- Total TCH capacity of normal TRXs

ava_17 = 100 * --------------- % ava_28 + ava_16 Total TCH % for dedicated PS, S9PS (trf_88b)

Use: Indicates how many % of the total normal TRX TCH capacity has been allocated for the dedicated PS territory. This value should be quite close to the value of the CDED parameter. Some difference comes from granularity when the CDED value is converted to timeslots in BSC. The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of CDED to timeslots.

Known problems: Formula: Capacity allocated for dedicated PS territory ---------------------------------------------




444/712

Total TCH capacity of normal TRXs

ava_17a = 100 * ---------------- % ava_28 + ava_16a Total TCH % for dedicated PS, S9PS (trf_88c)

Use: Indicates how many % of the total normal TRX TCH capacity has been allocated for the dedicated PS territory. This value should be quite close to the value of the CDED parameter. Some difference comes from granularity when the CDED value is converted to timeslots in BSC. The denominator does not contain extended TRXs because they are not GPRS capable and are not included in the conversion of CDED to timeslots.

Known problems: Formula: Capacity allocated for dedicated PS territory --------------------------------------------- Total TCH capacity of normal TRXs

ava_17a = 100 * ----------------- % ava_28a + ava_16b Average total UL throughput per used TSL, S9PS (trf_89)

Use: Indicates the total data rate per used timeslot. This figure is affected by the coding scheme selected by the link adaptation. Known problems: IGNOR_RLC_DATA_BL_UL_DUE_BSN is not only CS1 (23 octets) but can also be CS2 (33). The share between CS1 and

CS2 has to be approximated.




445/712

Formula: All UL data (kilobit) ------------------------------------ = time used for UL data transfer (sec) ( sum(rlc_data_blocks_ul_cs1 *23 + rlc_data_blocks_ul_cs2 *33 + rlc_mac_cntrl_blocks_ul *23 + BAD_FRAME_IND_UL_CS1*23 + BAD_FRAME_IND_UL_UNACK*23 + BAD_FRAME_IND_UL_CS2* 33 ) + ignor_rlc_data_bl_ul_due_bsn_CS1_aprx*23 + ignor_rlc_data_bl_ul_due_bsn_CS2_aprx *33 )*8/1000 ----------------------------------------------- sum(period_duration)*60* trf_78a where ignor_rlc_data_bl_ul_due_bsn_CS1_aprx = RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) = sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2) ignor_rlc_data_bl_ul_due_bsn_CS2_aprx = RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)= sum(rlc_data_blocks_ul_cs2) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn)




446/712

sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit unit: kbps / tsl

Average total UL throughput per used TSL, S10PS (trf_89a)

Use: Indicates the total data rate per used timeslot. This figure is affected by the coding scheme selected by the link adaptation Known problems: IGNOR_RLC_DATA_BL_UL_DUE_BSN is not only CS1 (23 octets) but can also be CS2 (33). The share between CS1 and

CS2 has to be approximated.

Formula: All UL data (kilobits) ---------------------------------- = time used for UL data transfer (sec)

sum(a.rlc_data_blocks_ul_cs1 *23 + a.rlc_data_blocks_ul_cs2 *33 + a.rlc_mac_cntrl_blocks_ul *23 + a.BAD_FRAME_IND_UL_CS1*23 + a.BAD_FRAME_IND_UL_UNACK*23 + a.BAD_FRAME_IND_UL_CS2* 33 + a.ignor_rlc_data_bl_ul_due_bsn_CS1_aprx*23 + a.ignor_rlc_data_bl_ul_due_bsn_CS2_aprx *33 ..+ )*8/1000 +8*(sum over MCS-1 (xx)*30+




447/712

sum over MCS-2 (xx)*36+ sum over MCS-3 (xx)*45+ sum over MCS-4 (xx)*52+ sum over MCS-5 (xx)*63+ sum over MCS-6 (xx)*81+ sum over MCS-7 (xx/2)*123+ sum over MCS-8 (xx/2)*147+ sum over MCS-9 (xx/2)*159)/1000 ----------------------------------------------- sum(period_duration)*60* trf_78c

where 1) ignor_rlc_data_bl_ul_due_bsn_CS1_aprx = RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) = sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2) Counters from table(s): p_nbsc_packet_control_unit

2) ignor_rlc_data_bl_ul_due_bsn_CS2_aprx = RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)= sum(rlc_data_blocks_ul_cs2) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2) Counters from table(s):




448/712

a=p_nbsc_packet_control_unit, b=p_nbsc_coding_scheme

3) xx= EGPRS UL RLC blocks = (b.ul_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_ul + b.bad_rlc_valid_hdr_ul_ack +b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode) Unit: kbps/tsl

Average total DL throughput per used TSL, S9PS (trf_90)

Use: Indicates the total data rate per used timeslot. Known problems: Counter rlc_mac_cntrl_blocks_dl also contains dummy blocks until CD6.1.

Formula: All DL data (kilobit) ---------------------------------- = time used for DL data transfer (sec) sum(rlc_data_blocks_dl_cs1 *23 + rlc_data_blocks_dl_cs2 *33 + rlc_mac_cntrl_blocks_dl *23 + RETRA_RLC_DATA_BLOCKS_DL_CS1*23 + RETRA_RLC_DATA_BLOCKS_DL_CS2* 33)*8/1000 ----------------------------------------------- sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl




449/712

+ RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2)/50 Counters from table(s): p_nbsc_packet_control_unit unit: kbps / tsl

Average total DL throughput per used TSL, S10PS (trf_90a)

Use: Indicates the total data rate per used timeslot. Known problems: Dummy blocks are included. They can be subtracted in S10. (not resolved yet)

Formula:

SDCCH true seizures for call, (trf_91)

Known problems: Formula: sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call - succ_sdcch_sms_est- unsucc_sdcch_sms_est-succ_seiz_supplem_serv) Counters from table(s): p_nbsc_res_access




450/712

Average HSCSD subchannel traffic, S7HS (trf_92)

Formula: HSCSD total traffic – HSCS main channel traffic = trf_59-trf-60 =

sum(ave_busy_tch_hscsd_numer)/sum(ave_busy_tch_hscsd_denom) -sum(ave_hscsd_users_numer)/sum(ave_hscsd_users_denom)

- Counters from table(s): p_nbsc_res_avail

Average HSCSD subchannel traffic, S7HS (trf_92a)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Note: HSCSD uses FR. Formula: trf_99 ; HSCSD total traffic, normal TRXs + trf_100 ; HSCSD total traffic, extended TRXs – trf_104 ; HSCS main channel traffic, normal TRXs – trf_105 ; HSCS main channel traffic, extended TRXs Unit: erlang Counters from table(s): p_nbsc_res_avail




451/712

Average HSCSD subchannel traffic, Area S7HS (trf_195)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Note: HSCSD uses FR. Formula: trf_188 ; HSCSD total traffic, normal TRXs + trf_191 ; HSCSD total traffic, extended TRXs – trf_177 ; HSCS main channel traffic, normal TRXs – trf_178 ; HSCS main channel traffic, extended TRXs Unit: erlang Counters from table(s): p_nbsc_res_avail

Voice calls on SDCCH, S1 (trf_93)

Formula: sum(sdcch_emerg_call+succ_seiz_term+succ_seiz_orig-succ_sdcch_sms_est-unsucc_sdcch_sms_est) Counters from table(s): p_nbsc_res_access

TCH traffic, S1 (trf_94)

Use: Possible to use on the TRX level. Formula:




452/712

Call time / period duration = sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 + freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7)/60 0.48 * ------------------------ sum(period_duration) Unit: Erlang Counters from table(s): p_nbsc_rx_qual

PS traffic, S9PS (trf_95)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes during the period on average. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: Timeslot use caused by DL TBF release delay is not included and this makes the value seem optimistic. Formula: Time used to transmit RLC blocks ---------------------------------- = time available




453/712

sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2)) /50 ----------------------------------- sum(period_duration*60) Counters from table(s): p_nbsc_packet_control_unit

Unit: tsl (or erlang) GPRS traffic sum, S9PS (trf_95a)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes during the period on average. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: Timeslot use caused by DL TBF release delay is not included and this makes the value seem optimistic. Formula:




454/712

Time used to transmit RLC blocks ---------------------------------- = time available sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2)) /50/3600 Counters from table(s): p_nbsc_packet_control_unit

Unit: erlang hours GPRS territory utilisation, S9PS (trf_96)

Use: BTS level. Indicates how big a portion of the GPRS territory has been used. If the utilisation % is high, increasing the CDEF parameter setting should be considered.




455/712


Target level: Choosing the acceptable level is a QoS issue. For example, 60% utilisation would give about 70% of the maximum rate achieved.Known problems: Dummy blocks on DL make this PI show too high a value (fixed in CD6.0: RLC_MAC_cntrl_blocks_DL does not contain dummy blocks anymore).

Known problems: 1) If there are very few timeslots in the GPRS territory, this KPI can show a high value even if there is only one active user. 2) The denominator is slightly incorrect if extended TRXs were used. Formula: Data blocks transmitted # greater one chosen, DL or UL 100* --------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) ) 100*------------------------------------------------------- % sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den) *sum(a.period_duration*60)*50




456/712

Counters from table(s): a= p_nbsc_res_avail b= p_nbsc_packet_control_unit

GPRS territory utilisation, S9PS (trf_96a)

Use: BTS level. Indicates how big a portion of the GPRS territory has been used. If the utilisation % is high, increasing the CDEF parameter setting should be considered.



Known problems: 1) If there are very few timeslots in the GPRS territory, this KPI can show a high value even if there is only one active user. 2) The denominator is slightly incorrect if extended TRXs were used. Formula: Data blocks transmitted # greater one chosen, DL or UL 100* --------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2




457/712

+ BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) ) 100*------------------------------------------------------- % ava_16a *sum(a.period_duration*60)*50 Counters from table(s): a= p_nbsc_res_avail b= p_nbsc_packet_control_unit

GPRS territory utilisation, Area, S9PS (trf_201)

Use: Area level. Indicates how big a portion of the GPRS territory has been used. If the utilisation % is high, increasing the CDEF parameter setting should be considered.



Known problems: 1) If there are very few timeslots in the GPRS territory, this KPI can show a high value even if there is only one active user. 2) The denominator is slightly incorrect if extended TRXs were used. Formula: Data blocks transmitted # greater one chosen, DL or UL




458/712

100* --------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( max of ( b.rlc_data_blocks_ul_cs1 + b.rlc_data_blocks_ul_cs2 + b.rlc_mac_cntrl_blocks_ul + b.BAD_FRAME_IND_UL_CS1 + b.BAD_FRAME_IND_UL_CS2 + b.BAD_FRAME_IND_UL_UNACK + b.IGNOR_RLC_DATA_BL_UL_DUE_BSN, b.rlc_data_blocks_dl_cs1 + b.rlc_data_blocks_dl_cs2 + b.rlc_mac_cntrl_blocks_dl + b.RETRA_RLC_DATA_BLOCKS_DL_CS1 + b.RETRA_RLC_DATA_BLOCKS_DL_CS2) ) 100*------------------------------------------------------- % a.ava_44 *sum(a.period_duration*60)*50 Counters from table(s): a= p_nbsc_res_avail b= p_nbsc_packet_control_unit

PS territory utilisation, S10.5PS (trf_96b)

Use: BTS level. Indicates how big a portion of the PS territory has been used. If the utilisation % is high, increasing the CDEF parameter setting should be considered.





459/712


Known problems: 1) If there are very few timeslots in the GPRS territory, this KPI can show a high value even if there is only one active user. 2) The denominator is slightly incorrect if extended TRXs were used. Formula: Data blocks transmitted # greater one chosen, DL or UL 100* --------------------------------------------------- % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, +( sum over MCS-1 (xx)+ sum over MCS-2 (xx)+ sum over MCS-3 (xx)+ sum over MCS-4 (xx)+ sum over MCS-5 (xx)+ sum over MCS-6 (xx)+ sum over MCS-7 (xx/2)+ sum over MCS-8 (xx/2)+ sum over MCS-9 (xx/2) ),




460/712

rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) +( sum over MCS-1 (yy)+ sum over MCS-2 (yy)+ sum over MCS-3 (yy)+ sum over MCS-4 (yy)+ sum over MCS-5 (yy)+ sum over MCS-6 (yy)+ sum over MCS-7 (yy/2)+ sum over MCS-8 (yy/2)+ sum over MCS-9 (yy/2) ) ) 100*------------------------------------------------------- % ava_16a *sum(a.period_duration*60)*50 Where xx= c.(UL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_UL+BAD_RLC_VALID_HDR_UL_UNACK+ UL_RLC_BLOCKS_IN_UNACK_MODE) yy= c.(DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): a= p_nbsc_res_avail b= p_nbsc_packet_control_unit c= p_nbsc_coding_scheme




461/712

PS territory utilisation, S10.5PS (trf_96c)

Use: BTS level. Indicates how big a portion of the PS territory has been used. If the utilisation % is high, increasing the CDEF parameter setting should be considered.



Known problems: 1) If there are very few timeslots in the GPRS territory, this KPI can show a high value even if there is only one active user. 2) The denominator is slightly incorrect if extended TRXs were used. Formula: Data blocks transmitted # greater one chosen, DL or UL 100 * ------------------------------------------------------------ % = (available GPRS channel time in sec)* (nbr of blocks per sec) sum( max of ( rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN, +( sum over MCS-1 (xx)+ sum over MCS-2 (xx)+




462/712

sum over MCS-3 (xx)+ sum over MCS-4 (xx)+ sum over MCS-5 (xx)+ sum over MCS-6 (xx)+ sum over MCS-7 (xx/2)+ sum over MCS-8 (xx/2)+ sum over MCS-9 (xx/2) ), rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) +( sum over MCS-1 (yy)+ sum over MCS-2 (yy)+ sum over MCS-3 (yy)+ sum over MCS-4 (yy)+ sum over MCS-5 (yy)+ sum over MCS-6 (yy)+ sum over MCS-7 (yy/2)+ sum over MCS-8 (yy/2)+ sum over MCS-9 (yy/2) ) ) 100 * ------------------------------------------------------- % ava_16b * sum(a.period_duration*60)*50 Where xx= c.(UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE) yy=




463/712

c.(DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL + DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_packet_control_unit c = p_nbsc_coding_scheme

Average CS traffic per BTS, normal TRXs, erlang, S2 (trf_97)

Use: This is a speech (circuit switched) traffic indicator. Speech traffic is a basic indicator needed to see how much TCH capacity is consumed. When the traffic increases without the increase of the capacity, the probability of blocking grows. The relationship between traffic, capacity and blocking is described for speech traffic in the formula known as Erlang B.

This KPI includes all types of CS traffic (single TCH, HSCSD) on normal TRXs. Known problems: this formula will not work at segment level. Use trf_97a Formula: sum(decode(trx_type,0,ave_busy_tch)) ----------------------------------- sum(decode(trx_type,0,res_av_denom14)) Counters from table(s): p_nbsc_res_avail

Unit: erlang




464/712

Average CS traffic per BTS, normal TRXs, erlang, S2 (trf_97a)


This KPI includes all types of CS traffic (single TCH, HSCSD) on normal TRXs. Known problems: Formula: sum(decode(trx_type,0,ave_busy_tch)) ----------------------------------- sum(decode(trx_type,0,decode(ave_busy_tch ,0,0,res_av_denom14))) Counters from table(s): p_nbsc_res_avail

Unit: erlang

Average CS traffic per BTS, extended TRXs, S2 (trf_98)


This KPI includes all types of CS traffic (single TCH, HSCSD) on extended TRXs. Known problems: this formula will not work at Segment level. Use trf_98a Formula: sum(decode(trx_type,1,ave_busy_tch)) ----------------------------------- sum(decode(trx_type,1,res_av_denom14)) Counters from table(s):




465/712

p_nbsc_res_avail

Unit: erlang

Average CS traffic per BTS, extended TRXs, S2 (trf_98a)


This KPI includes all types of CS traffic (single TCH, HSCSD) on extended TRXs. Known problems: Formula: sum(decode(trx_type,1,ave_busy_tch)) ----------------------------------- sum(decode(trx_type,1, decode(ave_busy_tch ,0,0,res_av_denom14))) Counters from table(s): p_nbsc_res_avail

Unit: erlang

Average HSCSD traffic, normal TRXs, S7HS (trf_99)

Note: HSCSD uses FR.Formula: sum(decode(trx_type,0,ave_busy_tch_hscsd_numer)) ------------------------------------------------ sum(decode(trx_type,0,ave_busy_tch_hscsd_denom))




466/712


Unit: erlang Average HSCSD traffic, normal TRXs, Area, S7HS (trf_188)

Note: HSCSD uses FR.Formula: sum(decode(trx_type,0,ave_busy_tch_hscsd_numer)) ------------------------------------------------ avg(decode(trx_type,0,ave_busy_tch_hscsd_denom)) * count(distinct period_start_time Counters from table(s): p_nbsc_res_avail

Unit: erlang Average HSCSD traffic, extended TRXs, S7HS (trf_100)

Note: HSCSD uses FR.Formula: sum(decode(trx_type,1,ave_busy_tch_hscsd_numer)) ------------------------------------------------ sum(decode(trx_type,1,ave_busy_tch_hscsd_denom)) Counters from table(s): p_nbsc_res_avail




467/712

Unit: erlang Average HSCSD traffic, extended TRXs, Area, S7HS (trf_191)

Note: HSCSD uses FR.Formula: sum(decode(trx_type,1,ave_busy_tch_hscsd_numer)) ------------------------------------------------ avg(decode(trx_type,1,ave_busy_tch_hscsd_denom)) * count(distinct period_start_time Counters from table(s): p_nbsc_res_avail

Unit: erlang Average HTCH traffic, S7HS (trf_101)

Use: Total of speech (circuit switched) single timeslot half rate traffic over normal and extended TRXs. Note: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Formula: trf_102 ; HTCH traffic, normal TRXs + trf_103 ; HTCH traffic, extended TRXs Unit: erlang




468/712

Average HTCH traffic, Area S7HS (trf_193)


Average HTCH traffic , normal TRXs, S7HS (trf_102)

Use: Total of speech (circuit switched) single timeslot half rate traffic over normal TRXs. Formula: Avg(decode,trx_type,0,ave_tch_busy_half)) Unit: erlang

Average HTCH traffic, extended TRXs, S7HS (trf_103)

Use: Total of speech (circuit switched) single timeslot half rate traffic over extended TRXs. Formula: nvl(Avg(decode,trx_type,1,ave_tch_busy_half)),0) Unit: erlang




469/712

Average HSCSD main channel traffic, normal TRXs, S7HS (trf_104)

Use: Note: HSCSD uses FR. Formula: sum(decode(trx_type,0,ave_hscsd_users_numer)) -------------------------------------------- sum(decode(trx_type,0,ave_hscsd_users_denom)) Counters from table(s): p_nbsc_res_avail Unit: erlang

Average HSCSD main channel traffic, extended TRXs, S7HS (trf_105)

.3.2002 Use: Note: HSCSD uses FR. Formula: sum(decode(trx_type,0,ave_hscsd_users_numer)) -------------------------------------------- sum(decode(trx_type,0,ave_hscsd_users_denom)) Counters from table(s): p_nbsc_res_avail Unit: erlang




470/712

Average FTCH single traffic, S7 (trf_106)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Note: Formula: trf_107 ; FTCH single traffic on normal TRXs + trf_108 ; FTCH single traffic on extended TRXs Unit: erlang

Average FTCH single traffic, S7 (trf_192)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Note: Formula: trf_189 ; FTCH single traffic on normal TRXs + trf_190 ; FTCH single traffic on extended TRXs Unit: erlang

Average FTCH single traffic, normal TRXs, S7 (trf_107)

Use: Note: Formula: trf_97 ; all CS traffic on normal TRXs




471/712

-trf_102 ; single HR traffic on normal TRXs -trf_99 ; al HSCSD (FR) traffic on normal TRXs Unit: erlang

Average FTCH single traffic, normal TRXs, Area S7 (trf_189)

Use: Note: Formula: trf_202 ; all CS traffic on normal TRXs -trf_175 ; single HR traffic on normal TRXs -trf_188 ; al HSCSD (FR) traffic on normal TRXs Unit: erlang

Average FTCH single traffic, extended TRXs, S7 (trf_108)

Use: Note: Formula: trf_98 ; all CS traffic on extended TRXs - trf_103 ; single HR traffic on extended TRXs - trf_100 ; all HSCSD (FR) traffic on extended TRXs Unit: erlang

Average FTCH single traffic, extended TRXs, Area S7 (trf_190)

Use: Note:




472/712

Formula: trf_170 ; all CS traffic on extended TRXs - trf_176 ; single HR traffic on extended TRXs - trf_191 ; all HSCSD (FR) traffic on extended TRXs Unit: erlang

Peak busy TCH on normal TRXs, (trf_109)

Use: This PI is an important traffic load indicator on the cell level. By following this and reacting proactively, blocking can be avoided in cells where the traffic growth is smooth.

Known problems: Formula: max(decode(trx_type,0,peak_busy_tch)) Counters from table(s): p_nbsc_res_avail

Peak busy TCH on normal TRXs, (trf_110)

Use: This PI is an important traffic load indicator on the cell level. By following this and reacting proactively, blocking can be avoided in cells where the traffic growth is smooth.

Known problems: Formula: max(decode(trx_type,1,peak_busy_tch))




473/712


Normal TCH usage % for CS, (trf_111)

Use: Indicates how many % of the total available TCH normal capacity has been used for CS traffic on average. Formula: trf_97 = 100 * -------------------------- % ava_28 + ava_16a - ava_17a Normal TCH usage % for CS, (trf_111a)

Use: Indicates how many % of the total available TCH normal capacity has been used for CS traffic on average. Formula: trf_97 = 100 * --------------------------- % ava_28a + ava_16b - ava_17a Normal TCH usage % for CS, (trf_112)

Use: Indicates how many % of the total available TCH normal capacity has been used for CS traffic on average. Formula:




474/712

trf_98 = 100* ------------ % ava_29 CS call samples, non-AMR call (trf_113)

Use: Indicates how many call samples (sampling interval 480 ms) of non-AMR calls have been detected. Formula: sum( nvl(FREQ_UL_QUAL0,0)+ + nvl(FREQ_UL_QUAL7,0) -sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0) nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0) ) ) CS call samples, AMR call (trf_114)

Use: Indicates TCH use (sampling interval 480ms) for AMR calls. Formula: sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0)




475/712

+ nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0) nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0) )

TCH traffic time , non-AMR calls (trf_115)

Use: Indicates TCH use (sampling interval 480 ms) for non-AMR calls.Known problems: In a high load situation (OMU link) it is possible that all call time is not measured. In other words, call time can show a lower value than it has in reality.

Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality. Formula: sum( nvl(FREQ_UL_QUAL0,0)+ + nvl(FREQ_UL_QUAL7,0) -sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0) nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0) )*0,48/3600 Unit: erlang hours TCH traffic time , AMR calls (trf_116)

Use: Indicates TCH use (sampling interval 480 ms) for AMR calls.




476/712

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

Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality. Formula: trf_114*0,48/36000 Unit: erlang hours TCH traffic time , FR AMR calls (trf_117)

Use: Indicates TCH use (sampling interval 480 ms) for full rate AMR. Known problems: In a high load situation (OMU link) it is possible that all call time is not measured. In other words, call time can show a lower value

than it has in reality. Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality. Formula: ,sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0) ) *0,48/3600 Unit: erlang hours TCH traffic time , HR AMR calls (trf_118)





477/712

Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality. Formula: Sum( nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0) ) *0,48/3600 Unit: erlang hours TCH traffic time , all calls (trf_119)


Also, in the beginning of a call and in handover, two samples are lost, showing a shorter time than in reality. Formula: sum(nvl(FREQ_UL_QUAL0,0)+ .. + nvl(FREQ_UL_QUAL7,0))*0,48/3600 Unit: erlang hours TCH traffic share of non-AMR calls (trf_120)

Use: Formula: 100*trf_115/trf_119 Unit: erlang hours TCH traffic share of FR AMR calls (trf_121)

Use: Formula:




478/712

100*trf_117/trf_119 Unit: erlang hours TCH traffic share of HR AMR calls (trf_122)

Use: Formula: 100*trf_118/trf_119 Unit: erlang hours Average effective UL TSL throughput per TBF, S10PS (trf_123)

Use: Indicates the net data rate per used timeslot and per TBF. The lower, the value the more loaded is the GPRS territory and the less service the MS users receive.


Known problems: 1) The numerator of trf_72d is not yet pure user data but as close to that as we can see from BSC counters. 2) See problems of the denominator.

Formula: UL payload data (kilobit) / UL time for data transfer (sec) ------------------------------------------------------------- = Avg UL TBF per tsl trf_72d = ---------- tbf_37b




479/712

Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl/TBF

Average effective DL TSL throughput per TBF, S10PS (trf_124)

Use: Indicates the net data rate per used timeslot and per TBF. The lower, the value the more loaded is the GPRS territory and the less

service the MS users receive. The numerator does not contain the RLC header bytes neither does the MAC header because the aim is to count data volume from

the user’s point of view as close as possible. Known problems: 1) The numerator of trf_73d is not yet pure user data but as close to that as we can see from BSC counters.

2) Retransmitted blocks due to other reasons than NACK are not counted in any of the RLC counters. In DL direction these retransmissions occur when the TBF release is delayed. 3) For example, if there is only one TBF on a timeslot, some RLC blocks can be retransmitted before an ACK is received. These blocks are not counted in any of the RLC counters. 4) Counter rlc_mac_cntrl_blocks_dl also contains dummy blocks until CD.6.1. 5) See problems of the denominator.

Formula: DL payload data (kilobit) / DL time for data transfer (sec) ------------------------------------------------------------- =




480/712

Avg DL TBF per tsl

trf_73d = -------- tbf_38b

Counters from table(s): p_nbsc_packet_control_unit unit: Kbps / tsl / TBF

MS specific flowrate (trf_125)

Origin: J.Neva 2.12.2002 Use: This is the flowrate of LLC PDUs. It can be counted per segment and priority class. 8/1000 * ave_ms_bssgp_flow_rate_sum ----------------------------------- ave_ms_bssgp_flow_rate_den Counters from table(s): p_nbsc_qos Unit: kbit/sec

Status: OK




481/712

GPRS UL Data (kbytes), S9PS (trf_127)

Use: Indicates all GPRS data on UL Known problems: IGNOR_RLC_DATA_BL_UL_DUE_BSN is not only CS1 (23 octets) but can also be CS2 (33). The share between CS1 and

CS2 has to be approximated. Formula: All GPRS UL data (kbytes) = sum(rlc_data_blocks_ul_cs1 *23 + rlc_data_blocks_ul_cs2 *33 + rlc_mac_cntrl_blocks_ul *23 + BAD_FRAME_IND_UL_CS1*23 + BAD_FRAME_IND_UL_UNACK*23 + BAD_FRAME_IND_UL_CS2* 33 + ignor_rlc_data_bl_ul_due_bsn_CS1_aprx*23 + ignor_rlc_data_bl_ul_due_bsn_CS2_aprx *33 ..+ )*/1024 where ignor_rlc_data_bl_ul_due_bsn_CS1_aprx = RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) = sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2) ignor_rlc_data_bl_ul_due_bsn_CS2_aprx = RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)=




482/712

sum(rlc_data_blocks_ul_cs2) ------------------------------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn) sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack +rlc_data_blocks_ul_cs2)


Unit: kbytes GPRS DL Data (kbytes), S9PS (trf_128)

Use: Indicates all GPRS data on DL Known problems: Counter rlc_mac_cntrl_blocks_dl also contains dummy blocks until CD6.1. Formula: All GPRS DL data (kbytes) = sum(rlc_data_blocks_dl_cs1 *23 + rlc_data_blocks_dl_cs2 *33 + rlc_mac_cntrl_blocks_dl *23 + RETRA_RLC_DATA_BLOCKS_DL_CS1*23 + RETRA_RLC_DATA_BLOCKS_DL_CS2* 33)*/1024


Unit: kbytes




483/712

EGPRS UL Data (kbytes), S10.5PS (trf_129)

Use: Indicates all EGPRS data on UL Known problems: Formula: (sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148)) ) / 1024 where xx = (UL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_UL+BAD_RLC_VALID_HDR_UL_UNACK+UL_RLC_BLOCKS_IN_UNACK_MODE)


p_nbsc_coding_scheme Unit: kbytes EGPRS DL Data (kbytes), S10.5PS (trf_130)

Use: Indicates all EGPRS data on DL Known problems: Formula: ( sum over MCS-1 (yy)* 22+




484/712

sum over MCS-2 (yy)* 28+ sum over MCS-3 (yy)* 37+ sum over MCS-4 (yy)* 44+ sum over MCS-5 (yy)* 56+ sum over MCS-6 (yy)* 74+ sum over MCS-7 (yy/2)*112+ sum over MCS-8 (yy/2)*136+ sum over MCS-9 (yy/2)*148 ) /1024 where yy=(dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+dl_rlc_blocks_in_unack_mode)


p_nbsc_coding_scheme Unit: % UL RLC Data MCS-n, S10.5PS (trf_140 )

Description: UL RLC Data, MCS-n Use: Known problems: Formula: sum over MCS-n (xx) *nn / 1024 (where xx = UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL + BAD_RLC_VALID_HDR_UL_UNACK + UL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9.




485/712

(where nn is multiplier for each Coding Scheme, i.e. RLC Data Block payload in bytes nn for each MCS: MCS-1 22 MCS-2 28 MCS-3 37 MCS-4 44 MCS-5 56 MCS-6 74 MCS-7 56 MCS-8 68 MCS-9 74) Counters from table(s):

p_nbsc_coding_scheme Unit: kbytes DL RLC Data MCS-n, S10.5PS (trf_141)

Description: DL RLC Data MCS-n Use: Known problems: Formula: sum over MCS-n (xx) * nn / 1024 where xx = (DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL +




486/712

DL_RLC_BLOCKS_IN_UNACK_MODE) where n can be from 1 to 9. (where nn is multiplier for each Coding Scheme, i.e. RLC Data Block payload in bytes nn for each MCS: MCS-1 22 MCS-2 28 MCS-3 37 MCS-4 44 MCS-5 56 MCS-6 74 MCS-7 56 MCS-8 68 MCS-9 74) Counters from table(s):

p_nbsc_coding_scheme Unit: kbytes EGPRS traffic sum, S9PS (trf_158)

Description: EGPRS traffic in Erlangs Use: Indicates the amount of resources (timeslots) the EGPRS traffic data consumes during the period on average. This information is

useful, for example, in forecasting the need for capacity extension. Known problems: Timeslot use caused by DL TBF release delay is not included and this makes the value seem optimistic. Ignored due to BSN counter

is triggered for GPRS and EGPRS . This information is not available separately for EGPRS.




487/712

Formula: Time used to transmit RLC blocks ---------------------------------- = time available sum( max of ( ( sum over MCS-1 (xx)+ sum over MCS-2 (xx)+ sum over MCS-3 (xx)+ sum over MCS-4 (xx)+ sum over MCS-5 (xx)+ sum over MCS-6 (xx)+ sum over MCS-7 (xx/2)+ sum over MCS-8 (xx/2)+ sum over MCS-9 (xx/2) ), ( sum over MCS-1 (yy)+ sum over MCS-2 (yy)+ sum over MCS-3 (yy)+ sum over MCS-4 (yy)+ sum over MCS-5 (yy)+ sum over MCS-6 (yy)+ sum over MCS-7 (yy/2)+ sum over MCS-8 (yy/2)+ sum over MCS-9 (yy/2) ) ) )/50 ----------------------------------- sum(period_duration*60)




488/712

Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE+ RETRANS_RLC_DATA_BLOCKS_UL+ BAD_RLC_VALID_HDR_UL_ACK+ BAD_RLC_VALID_HDR_UL_UNACK+ UL_RLC_BLOCKS_IN_UNACK_MODE) Where yy=(DL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_DL+DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): p_nbsc_coding_scheme

Unit: erlang PS traffic sum, S9PS (trf_159)

Description: PS Traffic in Erlangs Use: Indicates the amount of resources (timeslots) the (E)GPRS traffic data consumes during the period on average. This information is

useful, for example, in forecasting the need for capacity extension. Known problems: Timeslot use caused by DL TBF release delay is not included and this makes the value seem optimistic. Formula: Time used to transmit RLC blocks ---------------------------------- = time available sum( max of ( rlc_data_blocks_ul_cs1




489/712

+ rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + IGNOR_RLC_DATA_BL_UL_DUE_BSN + ( sum over MCS-1 (xx)+ sum over MCS-2 (xx)+ sum over MCS-3 (xx)+ sum over MCS-4 (xx)+ sum over MCS-5 (xx)+ sum over MCS-6 (xx)+ sum over MCS-7 (xx/2)+ sum over MCS-8 (xx/2)+ sum over MCS-9 (xx/2) ), , rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2 + ( sum over MCS-1 (yy)+ sum over MCS-2 (yy)+ sum over MCS-3 (yy)+ sum over MCS-4 (yy)+ sum over MCS-5 (yy)+ sum over MCS-6 (yy)+ sum over MCS-7 (yy/2)+ sum over MCS-8 (yy/2)+ sum over MCS-9 (yy/2) ) ))




490/712

/50 ----------------------------------- sum(period_duration*60) Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_UL+BAD_RLC_VALID_HDR_UL_UNACK+ UL_RLC_BLOCKS_IN_UNACK_MODE) Where yy=(DL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_DL+DL_RLC_BLOCKS_IN_UNACK_MODE) Counters from table(s): p_nbsc_coding_scheme p_nbsc_packet_control_unit

Unit: erlang Normal TCH usage % for EGPRS, S10.5PS (trf_160)

Use: Indicates how many % of the total available normal TCH capacity has been used for EGPRS traffic on average. Used for trend analysis.

Known problems: Formula: Capacity used by EGPRS traffic ------------------------------ Total TCH normal capacity trf_158 = 100 * ---------------- % ava_28 + ava_16a Unit: %




491/712

Normal TCH usage % for EGPRS, S10.5PS (trf_160a)


Known problems: Formula: Capacity used by EGPRS traffic ------------------------------ Total TCH normal capacity trf_158 = 100 * ----------------- % ava_28a + ava_16b Unit: %

Normal TCH usage % for EGPRS, Area, S10.5PS (trf_199)


Known problems: Formula: Capacity used by EGPRS traffic ------------------------------ Total TCH normal capacity trf_158




492/712

= 100 * ----------------- % ava_52 + ava_44 Unit: %

UL EGPRS traffic, S10.5PS (trf_161)

Description: UL EGPRS Traffic in Erlangs Use: Indicates the amount of resources (timeslots) the EGPRS traffic data consumes on average during the period. This information is

useful, for example, in forecasting the need for capacity extension. 50 blocks /sec /tsl is used to estimate timeslots. Known problems: check trf_78c Ignore due to BSN and MAC Control block counters are not available, making this formula show smaller value. Formula: Actual UL data troughput (blocks) ------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum over MSC1…6 of (ul_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_ul+ BAD_RLC_VALID_HDR_UL_ACK+bad_rlc_valid_hdr_ul_unack+ul_rlc_blocks_in_unack_mode) +sum over MSC7…9 of (ul_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_ul+ +BAD_RLC_VALID_HDR_UL_ACK+bad_rlc_valid_hdr_ul_ unack+ul_rlc_blocks_in_unack_mode)/2 --------------------------------------------------- sum(period_duration*60)*50 ; 50 blocks /sec /tsl Counters from table(s):




493/712

p_nbsc_coding_scheme Unit: tsl (or erlang) UL EGPRS traffic, S10.5PS, BTS level (trf_161a)


useful, for example, in forecasting the need for capacity extension. 50 blocks /sec /tsl is used to estimate timeslots. Known problems: check trf_78c Ignore due to BSN and MAC Control block counters are not available, making this formula show smaller value. Formula: Actual UL data troughput (blocks) ------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum over MSC1…6 of (a. ul_rlc_blocks_in_ack_mode+a.retrans_rlc_data_blocks_ul+ a.BAD_RLC_VALID_HDR_UL_ACK+a.bad_rlc_valid_hdr_ul_unack+a.ul_rlc_blocks_in_unack_mode) +sum over MSC7…9 of (a.ul_rlc_blocks_in_ack_mode+a.retrans_rlc_data_blocks_ul+ +a.BAD_RLC_VALID_HDR_UL_ACK+a.bad_rlc_valid_hdr_ul_unack+a.ul_rlc_blocks_in_unack_mode)/2 + ignor_rlc_data_bl_ul_due_bsn_egprs + rlc_mac_cntrl_blocks_ul_egprs ---------------------------------------------------




494/712

sum(period_duration*60)*50 ; 50 blocks /sec /tsl Counters from table(s): a = p_nbsc_coding_scheme b = p_nbsc_packet_control_unit ignor_rlc_data_bl_ul_due_bsn_egprs = trf_204 ignor_rlc_data_bl_ul_due_bsn * ================= trf_203 + trf_204 rlc_mac_cntrl_blocks_ul_egprs = trf_204 rlc_mac_cntrl_blocks_ul * ================= trf_203 + trf_204

Unit: tsl (or erlang) UL GPRS traffic in EGPRS BTS, S10.5PS, BTS level (trf_205)


useful, for example, in forecasting the need for capacity extension. 50 blocks /sec /tsl is used to estimate timeslots. Known problems: check trf_78c Ignore due to BSN and MAC Control block counters are not ava ilable, making this formula show smaller value. Formula: Actual UL data troughput (blocks)




495/712

------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + BAD_FRAME_IND_UL_CS1 + BAD_FRAME_IND_UL_CS2 + BAD_FRAME_IND_UL_UNACK + rlc_mac_cntrl_blocks_ul_gprs + IGNOR_RLC_DATA_BL_UL_DUE_BSN_gprs) ----------------------------------- sum(period_duration*60)*50 ; 50 blocks /sec /tsl ignor_rlc_data_bl_ul_due_bsn_gprs = trf_203 ignor_rlc_data_bl_ul_due_bsn * ================= trf_203 + trf_204 rlc_mac_cntrl_blocks_ul_gprs = trf_203 rlc_mac_cntrl_blocks_ul * ================= trf_203 + trf_204 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme

Unit: tsl (or erlang)




496/712

DL GPRS traffic in EGPRS BTS, S10.5PS, BTS level (trf_208)

Description: DL EGPRS Traffic in Erlangs Use: Indicates the amount of resources (timeslots) the GPRS traffic data in EGPRS capable BTS, consumes on average during the period.

This information is useful, for example, in forecasting the need for capacity extension. 50 blocks /sec /tsl is used to estimate timeslots. Known problems: check trf_78c Ignore due to BSN and MAC Control block counters are not available, making this formula show smaller value. Formula: Actual UL data troughput (blocks) ------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + RETRA_RLC_DATA_BLOCKS_DL_CS1 + RETRA_RLC_DATA_BLOCKS_DL_CS2) + rlc_mac_cntrl_blocks_dl_gprs -------------------------------------- sum(period_duration*60)*50; 50 blocks /sec /tsl rlc_mac_cntrl_blocks_dl_gprs = trf_206 rlc_mac_cntrl_blocks_dl * ================= trf_206 + trf_207 Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme




497/712

Unit: tsl (or erlang) DL EGPRS traffic, S10.5PS (trf_162)

Use: Indicates the amount of resources (timeslots) the DL EGPRS traffic data consumes. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: Formula: Actual DL data troughput (blocks) ------------------------------------------------------------ = nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum over msc1…6 (dl_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_dl+dl_rlc_blocks_in_unack_mode) +sum over msc7…9 of (dl_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_dl+ + dl_rlc_blocks_in_unack_mode)/2 --------------------------------------------------------- sum(period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):

p_nsbc_coding_scheme Unit: time slot or erlangDL EGPRS traffic, S10.5PS (trf_162a)




498/712

Use: Indicates the amount of resources (timeslots) the DL EGPRS traffic data consumes. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: Formula: Actual DL data troughput (blocks) ------------------------------------------------------------ = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum over msc1…6 of ( dl_rlc_blocks_in_ack_mode +retrans_rlc_data_blocks_dl +dl_rlc_blocks_in_unack_mode ) + sum over msc7…9 of ( dl_rlc_blocks_in_ack_mode +retrans_rlc_data_blocks_dl +dl_rlc_blocks_in_unack_mode )/2 + rlc_mac_cntrl_blocks_dl_egprs ----------------------------------------- sum(period_duration*60)*50 ;50 blocks /sec /tsl

rlc_mac_cntrl_blocks_dl_egprs = trf_207 rlc_mac_cntrl_blocks_dl * ================= trf_206 + trf_207

Counters from table(s): p_nsbc_coding_scheme




499/712

Unit: time slot or erlang

UL PS traffic, S10PS (trf_78c)

Use: Indicates the amount of resources (timeslots) the GPRS traffic data consumes on average during the period. This information is useful, for example, in forecasting the need for capacity extension.

Known problems: The value is optimistic because the time needed for TBF establishment and release is not included. The delayed TBF release that was taken into use in a CD of S9 also adds the actual usage of the TCH but cannot be considered in this formula. These make the value seem smaller.

Formula: Actual UL data troughput (blocks) ------------------------------------------------------------- = nbr of blocks equivalent to 1 tsl full use in each BTS of area sum(a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 + a.rlc_mac_cntrl_blocks_ul + a.bad_frame_ind_ul_cs1 + a.bad_frame_ind_ul_cs2 + a.bad_frame_ind_ul_unack + a.ignor_rlc_data_bl_ul_due_bsn) +sum over MSC1…6 of




500/712

(b.ul_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_ul+ b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode) +sum over MSC7…9 of (b.ul_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_ul+ b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode)/2 --------------------------------------------------- sum(period_duration*60)*50 ; 50 blocks /sec /tsl Counters from table(s): a=p_nbsc_packet_control_unit b= p_nbsc_coding_scheme Unit: tsl (or erlang) UL GPRS RLC Blocks, S10PS (trf_203)

Use: Known problems: Formula: Actual UL data blocks sum (a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 ) Counters from table(s): a=p_nbsc_packet_control_unit




501/712

Unit: number of blocks

UL EGPRS RLC Blocks, S10PS (trf_204)

Use: Known problems: Formula: Actual UL data blocks sum over MSC1…9 of (ul_rlc_blocks_in_ack_mode+ul_rlc_blocks_in_unack_mode) Counters from table(s): p_nbsc_coding_scheme

Unit: number of blocksDL GPRS RLC Blocks, S10PS (trf_206)

Use: Known problems: Formula: Actual DL data blocks sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2)




502/712

Counters from table(s): p_nbsc_packet_control_unit Unit: number of blocks

UL EGPRS RLC Blocks, S10PS (trf_207)

Use: Known problems: Formula: Actual DL data blocks sum over msc1…9 of ( dl_rlc_blocks_in_ack_mode +dl_rlc_blocks_in_unack_mode ) Counters from table(s): p_nbsc_coding_scheme

Unit: number of blocksTotal RLC Payload Data Blocks, S10PS (trf_210)

Use: Known problems: Formula: trf_203 + trf_204 + trf_206 + trf_207




503/712

Counters from table(s): p_nbsc_coding_scheme p_nbsc_packet_control_unit Unit: number of blocks UL call samples, AMR HR, S9CS (trf_163)

Description: Number of samples using AMR HR codecs Use: Indicates number of samples using AMR HR codecs for AMR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)

codec_type = 4..9

p_nbsc_ferStatus: Open DL call samples, AMR HR, S9CS (trf_164)

Description: Number of samples using AMR HR codecs Use: Indicates number of samples using AMR HR codecs for AMR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)

codec_type = 4..9




504/712

p_nbsc_fer UL call samples, AMR FR, S9CS (trf_165)

Description: Number of UL samples using AMR FR codecs Use: Indicates number of samples using AMR HR codecs for AMR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)

codec_type = 10..17

p_nbsc_ferStatus: Open DL call samples, AMR FR, S9CS (trf_166)

Description: Number of samples using AMR HR codecs Use: Indicates number of samples using AMR HR codecs for AMR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)

codec_type = 10..17

p_nbsc_ferUnit: Numbers




505/712

Status: Open Total EGPRS RLC Payload data, S9PS (trf_167)


Formula: ( (sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148)) )+ (sum over MCS-1 (yy)* 22+ sum over MCS-2 (yy)* 28+ sum over MCS-3 (yy)* 37+ sum over MCS-4 (yy)* 44+ sum over MCS-5 (yy)* 56+ sum over MCS-6 (yy)* 74+ sum over MCS-7 (yy/2)*112+ sum over MCS-8 (yy/2)*136+ sum over MCS-9 (yy/2)*148) ) /1024




506/712

Where xx= (UL_RLC_BLOCKS_IN_ACK_MODE+UL_RLC_BLOCKS_IN_UNACK_MODE) Where yy= DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE Counters from table(s): p_nbsc_coding_scheme Unit: kbyte

Total (E)GPRS RLC Payload data, S10.5PS (trf_209)


Formula: Total GPRS RLC Payload Data + Total EGPRS RLC Payload Data

trf_74b + trf_167

Counters from table(s): p_nbsc_packet_control_unit p_nbsc_coding_scheme Unit: kbyte

RLC Payload data for QoS Priority-n, S10.5PS (trf_211)

Use: Indicates the total amount of data (both ack and unack modes and UL and DL) transferred as QoS Priority-n.

Formula:




507/712

( ( xx* 23)+(yy *33) + ( sum over MCS-1 (zz) *22 +sum over MCS-2 (zz) *28 +sum over MCS-3 (zz) *37 +sum over MCS-4 (zz) *44 +sum over MCS-5 (zz) *56 +sum over MCS-6 (zz) *74 +sum over MCS-7 (zz/2)*112 +sum over MCS-8 (zz/2)*136 +sum over MCS-9 (zz/2)*148 ) ) * a.TOTAL_NBR_OF_RLC_BLOCKS ====================================== (trf_210 * 1024) xx = ( b.rlc_data_blocks_ul_cs1 + b.rlc_data_blocks_dl_cs1 yy = ( b.rlc_data_blocks_ul_cs2 + b.rlc_data_blocks_dl_cs2 ) zz = ( c.ul_rlc_blocks_in_ack_mode + c.ul_rlc_blocks_in_unack_mode + c.dl_rlc_blocks_in_ack_mode + c.dl_rlc_blocks_in_unack_mode ) Counters from table(s):




508/712

a = p_nbsc_qos b = p_nbsc_packet_control_unit c = p_nbsc_coding_scheme Unit: kbyte

Average SDCCH traffic, Area, S1 (trf_168)

Description: Average SDCCH traffic Formula: SDCCH used time / period duration = ( sum(a.ave_sdcch_hold_tim) / (avg(a.res_av_denom16) * 100 * count( distinct period_start_time)) ) *sum(b.sdcch_assign + b.sdcch_ho_seiz + b.tch_seiz_due_sdcch_con) ----------------------------------------------------------------- sum(a.period_duration*60) Counters from table(s): a = p_nbsc_res_avail b = p_nbsc_traffic Unit: Erlang

Average CS traffic, normal TRXs, erlang, Area, S2 (trf_202)





509/712

This KPI includes all types of CS traffic (single TCH, HSCSD) on normal TRXs. Known problems: Formula: sum(decode(trx_type,0,ave_busy_tch)) ---------------------------------------------------- avg(decode(trx_type,0, res_av_denom14)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Unit: erlang

Average CS traffic, extended TRXs, Area, S2 (trf_170)


This KPI includes all types of CS traffic (single TCH, HSCSD) on extended TRXs. Known problems: Formula: sum(decode(trx_type,1,ave_busy_tch)) ----------------------------------- avg(decode(trx_type,1,res_av_denom14)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Unit: erlang




510/712

Average CS traffic, erlang, Area, S2 (trf_171)


This KPI includes all types of CS traffic (single TCH, HSCSD). Known problems: Formula: trf_202 ; CS traffic on normal TRXs + trf_170 ; CS traffic on extended TRXs

Unit: erlang

Average HTCH traffic, S7HS Area, (trf_174)


Average HTCH traffic, normal TRXs, Area, S7HS (trf_175)

Use: Total of speech (circuit switched) single timeslot half rate traffic over normal TRXs. Formula:




511/712

sum(decode(trx_type,0, ave_tch_busy_half * RES_AV_DENOM1)) =================================================================== avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time) Unit: erlang

Average HTCH traffic, extended TRXs, Area, S7HS (trf_176)

Use: Total of speech (circuit switched) single timeslot half rate traffic over extended TRXs. Formula: sum(decode(trx_type,1, ave_tch_busy_half * RES_AV_DENOM1)) =================================================================== avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time) Unit: erlang

Average HSCSD main channel traffic, normal TRXs, Area, S7HS (trf_177)

Use: Note: HSCSD uses FR. Formula: sum(decode(trx_type,0,ave_hscsd_users_numer)) -------------------------------------------- avg(decode(trx_type,0,ave_hscsd_users_denom)) * count(distinct period_start_time)




512/712

Counters from table(s): p_nbsc_res_avail Unit: erlang

Average HSCSD main channel traffic, extended TRXs, Area, S7HS (trf_178)

.3.2002 Use: Note: HSCSD uses FR. Formula: sum(decode(trx_type,0,ave_hscsd_users_numer)) -------------------------------------------- avg(decode(trx_type,0,ave_hscsd_users_denom)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail Unit: erlang

Average busy TCH for HSCSD per BTS, normal TRX, S7HS (trf_179)

Formula: sum(decode(trx_type,0,ave_busy_tch_hscsd_numer)) ------------------------------------------------ sum(decode(trx_type,0,ave_busy_tch_hscsd_denom)) Counters from table(s): p_nbsc_res_avail




513/712

Average busy TCH for HSCSD per BTS, extended TRX, S7HS (trf_180)

Formula: sum(decode(trx_type,1,ave_busy_tch_hscsd_numer)) ------------------------------------------------ sum(decode(trx_type,1,ave_busy_tch_hscsd_denom)) Counters from table(s): p_nbsc_res_avail

Average busy TCH for HSCSD per BTS, extended TRX, S7HS (trf_181)

Formula: trf_179 + trf_180 Counters from table(s): p_nbsc_res_avail

Average HTCH traffic per BTS, S7HS (trf_182)





514/712

Average HTCH traffic per BTS, normal TRXs, S7HS (trf_183)

Use: Total of speech (circuit switched) single timeslot half rate traffic over normal TRXs. Formula: sum(decode(trx_type,0, ave_tch_busy_half * RES_AV_DENOM1)) ================================================================== sum(decode(trx_type,0,RES_AV_DENOM1)) Unit: erlang

Average HTCH traffic per BTS, extended TRXs, Area, S7HS (trf_184)

Use: Total of speech (circuit switched) single timeslot half rate traffic over extended TRXs. Formula: sum(decode(trx_type,1, ave_tch_busy_half * RES_AV_DENOM1)) =================================================================== sum(decode(trx_type,0,RES_AV_DENOM1)) Unit: erlang

Average number of MSs/users, S10.5 (trf_186)

Use: this is under work.:




515/712

Formula: AVE_MS_BSSGP_FLOW_RATE_DEN Unit: numbers Counters from table(s): p_nbsc_res_avail

Average busy TCH for HSCSD per BTS, normal TRX, S7HS (trf_187)

Formula: trf_177 + trf_178 Counters from table(s): p_nbsc_res_avail

new formula, SxxxS (xxx_yyy)

Description: Use: how does it help Known problems: if anything is known already Formula: formula




516/712

Counters from table(s): p_nbsc_

Unit: new formula, SxxxS (xxx_yyy)

Use: how does it help Known problems: if anything is known already Formula: formula

Counters from table(s): p_nbsc_

Unit: Next free, (trf_141 to trf_148 and trf_150 to trf_157)




517/712

Traffic Directions (xxx)

Mobile Originated Calls (moc)

SDCCH seizures for MO calls, S2 (moc_1)

Known problems: Includes supplementary services such as call divert. Includes SMS. Formula: sum(succ_seiz_orig) Counters from table(s): p_nbsc_res_access

Successful MO speech calls, S3 (moc_2)

Note: Triggered when a call is cleared. Excludes setup failures, TCH drops and TCH busy (congestion) cases. Known problems: The measurement is on the BSC level. Formula: sum(nbr_of_calls) where counter_id = 44 Counters from table(s): p_nbsc_cc_pm

Successful MO data calls, S3 (moc_3)

Known problems: See moc_2.




518/712

Formula: sum(nbr_of_calls) where counter_id = 45 Counters from table(s): p_nbsc_cc_pm

MO call success ratio, S6 (moc_4)

Known problems: See moc_2. Note: MO call attempts are counted when MOCs are found on SDCCH. The numerator excludes setup failures, TCH drops and TCH busy (congestion) cases. Formula: sum(nbr_of_calls) where counter_id = 44 /* MO call completed */ 100 * ----------------------------------------------------------------------- sum(nbr_of_calls) where counter_id = 38 /* MO call attempt */ Counters from table(s): p_nbsc_cc_pm

MO speech call attempts, S3 (moc_5)

Note: Triggered when a call is cleared. Excludes setup failures, TCH drops and TCH busy (congestion) cases. Known problems: See moc_2. Formula: sum(nbr_of_calls) where counter_id = 38 Counters from table(s): p_nbsc_cc_pm




519/712

MO call bids, S2 (moc_6)

Known problems: Includes supplementary services such as call divert. Includes SMS. Formula: sum(succ_seiz_orig+tch_moc) Counters from table(s): p_nbsc_res_access

Next free (moc_7)

Mobile Terminated Calls (mtc)

SDCCH seizures for MT calls, S2 (mtc_1)

Known problems: Includes SMS. See also moc_2. Formula: sum(succ_seiz_term) Counters from table(s): p_nbsc_res_access




520/712

Successful MT speech calls (mtc_2)

Note: See moc_2. Known problems: See moc_2. sum(nbr_of_calls) where counter_id = 43 Counters from table(s): p_nbsc_cc_pm

Successful MT data calls, S4 (mtc_3)

Note: See moc_2. Known problems: See moc_2. Formula: sum(nbr_of_calls) where counter_id = 47 Counters from table(s): p_nbsc_cc_pm

MT call success ratio, S (mtc_4)

Note: MT call attempts are counted when MTCs are found on SDCCH. The numerator excludes setup failures, TCH drops and TCH busy (congestion) cases. Known problems: See moc_2. Formula: sum(nbr_of_calls) where counter_id = 43 /* MT call completed */




521/712

100 * ----------------------------------------------------------------------- sum(nbr_of_calls) where counter_id = 37 /* MT call attempt */ Counters from table(s): p_nbsc_cc_pm

MT speech call attempts (mtc_5)

Note: See moc_2. Known problems: See moc_2. Formula: sum(nbr_of_calls) where counter_id = 43 Counters from table(s): p_nbsc_cc_pm

MT call attempts, S2 (mtc_6)

Use: Total number of calls bids with establishment cause ‘MT’. Known problems: Includes SMS. Formula: sum(succ_seiz_term+tch_mtc) Counters from table(s): p_nbsc_res_access




522/712

Next free (mtc_7)

Paging (pgn)

Number of paging messages sent, S2 (pgn_1)

Known problems: The number of repagings cannot be separated. Formula: sum(paging_msg_sent) Counters from table(s): p_nbsc_res_access

Paging buffer size average, S1 (pgn_2)

Use: To have an idea of how close to problems the BTS has been. Known problems: It is difficult to say when the problems start. Even if the counter 3018 does not yet show the 0 value, there may have been the situation

in one or some of the buffers that the capacity has run out. Formula: avg(min_paging_buf) Counters from table(s): p_nbsc_res_access Parameters related: Number of Blocks for AGCH (AG): e.g. = 2 Number of MultiFrames (MFR): e.g. = 6




523/712

Formulas related: Nbr of paging groups = (3-AG)*MFR ;if combined control channel Nbr of paging groups = (9-AG)*MFR ;if non-combined control channel Paging_Buffer_Size = free buffers (max 8) * Nbr of paging groups Min Paging Buffer (counter 3018) = min(Paging_Buffer_Space) . = min(Paging_Buffer_Size/2)

Paging Buffer Space is sent by BTS in the CCH_Load_Ind message to a BSC every 30 s. A BSC sends current paging load as Paging_Buffer_Size to a statistical unit. The minimum value of this is recorded as counter 3018. If Min Paging Buffer (counter 3018) equals to zero, paging blocking has occurred. Average free space of paging GSM buffer area, S1 (pgn_3)

Use: Average remaining free space for paging commands in GSM buffer area (part of GPRS buffer area). When there are no pagings, this PI shows the capacity of the buffer.

Known problems: Incorrect if CCCH load ind interval has changed during the observation period. Formula: avg(ave_pch_load/res_acc_denom2) Counters from table(s): p_nbsc_res_access

Average free space of paging GSM buffer area, S1 (pgn_3a)

Use: Average remaining free space for paging commands in GSM buffer area (part of GPRS buffer area). When there are no pagings, this PI shows the capacity of the buffer.

Formula:




524/712

sum(ave_pch_load)/sum(res_acc_denom2) Counters from table(s): p_nbsc_res_access

Paging success ratio, S1 (pgn_4)

Known problems: Due to the very dynamic behaviour it seems that this formula is not useful. Formula: sum over all BTS in LA (succ_seiz_term + tch_mtc) 100* ---------------------------------------------------- % sum over LA(paging_msg_sent) / sum over LA (count of BTS) Counters from table(s): p_nbsc_res_access

Average paging buffer air interface occupancy, S7 (pgn_5)

Known problems: Formula: sum (ave_paging_buffer_capa_numer) ---------------------------------- sum(ave_paging_buffer_capa_denom) Counters from table(s): p_nbsc_res_access




525/712

Average paging buffer Gb occupancy, S7PS (pgn_6)

Known problems: Formula: sum (ave_paging_gb_buf_sum) --------------------------- sum(ave_paging_gb_buf_den) Counters from table(s): p_nbsc_res_access

Average air interface DRX buffer load, due to paging, S7 (pgn_7)

Use: The DRX buffer handles messages that are sent in the DRX cycle, i.e. pagings and DRX access grants. This counter describes the DRX buffer load resulting from paging messages.

Known problems: Formula: sum (ave_paging_load_air_sum) --------------------------- sum(ave_paging_load_air_den) Counters from table(s): p_nbsc_res_access




526/712

Average air interface DRX buffer load, due to DRX AG, S7 (pgn_8)

Use: The DRX buffer handles messages that are sent in DRX cycle, i.e. pagings and DRX access grants. This counter describes DRX buffer load resulting from DRX AG messages (e.g. an Imm.Ass.for DL TBF establishment.)Known problems: Formula:

sum (ave_drx_agch_load_air_sum) ------------------------------- sum(ave_drx_agch_load_air_den) Counters from table(s): p_nbsc_res_access

Average air interface non-DRX buffer load due to AG, S7 (pgn_9)

Use: The non-DRX buffer handles messages that are sent immediately. This counter describes the non-DRX buffer load resulting from non-DRX (i.e. immediate) access grants such as CS Imm.Ass. and UL TBF (Imm.Ass. sent as an answer to RACH).Known problems: Formula:

sum (ave_non_drx_agch_load_air_sum) ----------------------------------- sum(ave_non_drx_agch_load_air_den) Counters from table(s): p_nbsc_res_access




527/712

Average free space of Paging GPRS buffer area, S9 (pgn_10)

Use: Average remaining free space for paging commands in the GSM buffer area. When there are no pagings, this PI shows the capacity of the GPRS buffer area.

Formula: sum(AVE_PCH_GB_LOAD_ON_CCCH_SUM) ---------------------------------- sum(AVE_PCH_GB_LOAD_ON_CCCH_DEN) Counters from table(s): p_nbsc_res_access

Average paging buffer Gb occupancy, S7PS (pgn_11)

Use: Area or BTS level Known problems: Formula: sum (ave_paging_gb_buf_sum) ------------------------------------------------------------- avg(ave_paging_gb_buf_den) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_access

Average free space of Paging GPRS buffer area, S9 Area (pgn_12)

Use: Average remaining free space for paging commands in the GSM buffer area. When there are no pagings, this PI shows the capacity of the GPRS buffer area.




528/712

Formula: sum(AVE_PCH_GB_LOAD_ON_CCCH_SUM) ---------------------------------- avg (AVE_PCH_GB_LOAD_ON_CCCH_DEN) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_access

Next free (pgn_11)

Short Message Service (sms)

SMS establishment failure %, (sms_1)

Formula: 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) Counters from table(s): p_nbsc_res_access

SMS TCH establishment failure %, (sms_2)

Formula:




529/712

sum(unsucc_TCH_sms_est) 100 * ------------------------------------------- % sum(succ_TCH_sms_est+unsucc_TCH_sms_est) Counters from table(s): p_nbsc_res_access

SMS SDCCH establishment failure %, (sms _3)

Use: MOC: Instead of sending the SETUP message, the MS starts SMS by sending SABM with SAPI 3 to BTS and a new establishment

indication is generated. MTC : Instead of sending the SETUP message, the MSC starts SMS by sending a CP DATA message to BSC and BSC sends an

ESTABLISH REQUEST to BTS, then MS answers by the UA message and the ESTABLISH CONFIRM message is generated. SMS fails if the message data is corrupted, timer expires when waiting for an establishment confirmation, or if an error indication or

release indication is received. Formula: sum(unsucc_sdcch_sms_est) 100 * -------------------------------------------- % sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est) Counters from table(s): p_nbsc_res_access

SMS establishment attempts, (sms_4)

Formula:




530/712

sum(succ_tch_sms_est+unsucc_tch_sms_est+succ_sdcch_sms_est+unsucc_sdcch_sms_est) Counters from table(s): p_nbsc_res_access

SMS SDCCH establishment attempts, (sms_5)

Formula: sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est) Counters from table(s): p_nbsc_res_access

SMS TCH establishment attempts, (sms_6)

Formula: sum(succ_tch_sms_est+unsucc_tch_sms_est) Counters from table(s): p_nbsc_res_access




531/712

Next free (sms_7)

Directed Retry (dr)

DR, outgoing to other cell attempts, S3 (dr_1)

Formula: sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at) Counters from table(s): p_nbsc_ho

DR, attempts, S3 (dr_1a)

Formula: sum(p_nbsc_ho.cause_dir_retry) Counters from table(s): p_nbsc_ho

DR, incoming from other cell attempts, S3 (dr_2)

Formula: sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at) Counters from table(s): p_nbsc_ho




532/712

DR, outgoing to other cell success, S3 (dr_3)

Formula: sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch) Counters from table(s): p_nbsc_ho

DR, incoming from other cell success, S3 (dr_4)

Formula: sum(msc_i_sdcch_tch+ bsc_i_sdcch_tch) Counters from table(s): p_nbsc_ho

DR, intra-cell s uccessful HO, S3 (dr_5)

Use: Triggered by - S6 feature ‘TCH assignment to super-reuse in IUO’ - S7 feature ‘Direct Access to super-reuse TRX’ Formula: sum(cell_sdcch_tch) Counters from table(s): p_nbsc_ho




533/712

% of new calls successfully handed over to another cell by DR, S3 (dr_6)

Formula: 100*sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch)/sum(tch_call_req) Counters from table(s): p_nbsc_ho

DR, outgoing to other cell, failed, S3 (dr_7)

Formula: sum(msc_o_sdcch_tch_at + bsc_o_sdcch_tch_at - msc_o_sdcch_tch + bsc_o_sdcch_tch) Counters from table(s): p_nbsc_ho

DR, intra-cell failed, S3 (dr_8)

Use: Triggered by - S6 feature ‘TCH assignment to super-reuse in IUO’ - S7 feature ‘Direct Access to super-reuse TRX’ Formula: sum(cell_sdcch_tch_at - cell_sdcch_tch) Counters from table(s): p_nbsc_ho




534/712

Next free (dr_9)

Availability (ava)

TCH availability percentage, S1 (ava_1)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. This PI is not, however, 100 per cent accurate for TCH since the timeslot also includes a signalling timeslot. New S4 counters allow

separating TCH and SDCCH (see ava_1a and ava_4). Formula: 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_tsl/res_av_denom1) Counters from table(s): p_nbsc_res_avail

TCH availability %, S4 (ava_1a)

Use: Failures (downtime) of TRXs cause loss of TCH and affect this KPI. Known problems: 1) If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. This means that both the system and the

user can affect this KPI and make it less useful. 2) This KPI is does not take HTCH into consideration.




535/712

Formula: 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) Counters from table(s): p_nbsc_res_avail

TCH availability %, S5 (ava_1b)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Does not work if TCHD (dual) channel type is used, because the same timeslot is seen as a resource available to both HTCH and

FTCH. Formula: available TCH 100 * ------------------ % all TCH

sum(ave_avail_full_TCH/res_av_denom2)+sum(ave_tch_avail_half)/2 =100 * -------------------------------------------------------------------------- % sum(ave_avail_full_TCH/res_av_denom2)+sum(ave_tch_avail_half)/2 +sum(ave_non_avail_TCH) Counters from table(s): p_nbsc_res_avail




536/712

TCH availability %, S9 (ava_1c)

Use: Failures (downtime) of TRXs cause loss of TCH and affect this KPI. Known problems: 1) If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. This means that both the system and the

user can affect this KPI and make it less useful. 2) The formula leaves out the timeslots reserved for GPRS. Formula: available TCH 100 * ------------------ % all TCH sum(ave_avail_TCH_sum/ave_avail_TCH_den) =100 * ------------------------------------------------------------------------ % sum(ave_avail_TCH_sum/ave_avail_TCH_den)+sum(ave_non_avail_TCH) Counters from table(s): p_nbsc_res_avail

TCH availability %, S9 (ava_1d)

Use: Failures (downtime) of TRXs cause loss of TCH and affect this KPI. Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. This means that both the system and the user

can affect this KPI and make it less useful. Note: The KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: available TCH 100 * ------------------------- % all TCH (traffic and GPRS)




537/712

sum(ave_avail_TCH_sum/ave_avail_TCH_den + ave_GPRS_channels_sum/ave_GPRS_channels_den) =100 * ------------------------------------------------------------------ % sum(ave_avail_TCH_sum/ave_avail_TCH_den + ave_GPRS_channels_sum/ave_GPRS_channels_den+ave_non_avail_TCH) Counters from table(s): p_nbsc_res_avail

TCH availability %, S9 (ava_1e)


can affect this KPI and make it less useful. Note: The KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: available TCH 100 * ------------------------- % all TCH (traffic and GPRS) ava_15 + ava_16b = 100 * --------------------------- % ava_15 + ava_16b + uav_11a Counters from table(s): p_nbsc_res_avail




538/712

TCH availability %, Area, S9 (ava_55)


can affect this KPI and make it less useful. Note: The KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: available TCH 100 * ------------------------- % all TCH (traffic and GPRS) ava_54 + ava_44 = 100 * --------------------------- % ava_54 + ava_44 + uav_17 Counters from table(s): p_nbsc_res_avail

Average defined FTCH, S1 (ava_2)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Note: 1. This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended).

2. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs, keeping in mind the note above.

Formula:




539/712

sum(ave_avail_full_TCH)/sum(res_av_denom2) Counters from table(s): p_nbsc_res_avail

Average defined FTCH, Area, S1 (ava_59)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: ava_60 + ava_61 Counters from table(s): p_nbsc_res_avail

Average defined FTCH,normal TRX, Area, S1 (ava_60)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: sum(decode(trx_type,0, ave_avail_full_TCH)) =================================================================== avg(decode(trx_type,0, res_av_denom2)) * count(distinct period_start_time)


Average defined FTCH,extended TRX, Area, S1 (ava_61)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula:




540/712

sum(decode(trx_type,1, ave_avail_full_TCH)) =================================================================== avg(decode(trx_type,1, res_av_denom2)) * count(distinct period_start_time)


Average available SDCCH, S1 (ava_3)

Note: 1. This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). 2. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs, keeping in mind the note above.

Formula: sum(ave_sdcch_sub)/sum(res_av_denom3) Counters from table(s): p_nbsc_res_avail

Average available SDCCH, BTS Level, S1 (ava_3a)

Note: 1. On object level higher than BTS, this formula gives the results "Avg avail SDCCH per BTS" Formula: ava_46 + ava_47 Counters from table(s): p_nbsc_res_avail




541/712

SDCCH availability %, S4 (ava_4)

Use: Indicates how big a share of all SDCCH resources has been available for traffic. Failures (downtime) of TRX containing SDCCH

affect this KPI. Known problems: Affected by locked TRX under unlocked BCF and BTS. Note: This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: sum(ave_sdcch_sub/res_av_denom3) 100 * --------------------------------------------------------- % sum(ave_sdcch_sub/res_av_denom3)+sum(ave_non_avail_sdcch) Counters from table(s): p_nbsc_res_avail

SDCCH availability %, BTS level S4 (ava_4a)


affect this KPI. Known problems: Affected by locked TRX under unlocked BCF and BTS. Note: This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula:




542/712

ava_3 100 * -------------- % ava_3 + uav_10 Counters from table(s): p_nbsc_res_avail

SDCCH availability %, BTS level S4 (ava_4b)


affect this KPI. Known problems: Affected by locked TRX under unlocked BCF and BTS. Note: This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: ava_3a 100 * -------------- % ava_3a + uav_10a Counters from table(s):

p_nbsc_res_avail SDCCH availability %, Area S4 (ava_63)


affect this KPI. Known problems: Affected by locked TRX under unlocked BCF and BTS. Note: This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula:




543/712

ava_45 100 * -------------- % ava_45 + uav_22

where ave_GPRS_channels_sum > 0


p_nbsc_res_avail SDCCH availability %, Area S4 (ava_63a)


affect this KPI. Known problems: Affected by locked TRX under unlocked BCF and BTS. Note: This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). Formula: ava_45a 100 * -------------- % ava_45a + uav_22



p_nbsc_res_avail




544/712

Average available FTCH in area, S1 (ava_5)

Formula: sum_over_area ( sum_over_BTS(ave_avail_full_TCH)/sum_over_BTS(res_av_denom2) ) Counters from table(s): p_nbsc_res_avail

DMR availability %, S6 (ava_6)

Formula: sum(avail_time) 100 * ---------------- % sum(total_time) Counters from table(s): p_nbsc_dmr.

DN2 availability %, S6 (ava_7)

Formula: sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_dn2.




545/712

TRU availability %, S6 (ava_8)

Formula: sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_tru_bie.

Average defined HTCH, S1 (ava_9)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: Avg(ave_tch_avail_half) Counters from table(s): p_nbsc_res_avail

Average defined HTCH, Area, S1 (ava_58)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: ava_56 + ava_57 Counters from table(s):




546/712

p_nbsc_res_avail

Average defined HTCH,normal TRX, Area, S1 (ava_56)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: sum(decode(trx_type,0, ave_tch_avail_half * RES_AV_DENOM1)) =================================================================== avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time)


Average defined HTCH,extended TRX, Area, S1 (ava_57)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: sum(decode(trx_type,1, ave_tch_avail_half * RES_AV_DENOM1)) =================================================================== avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time)


BSC ET availability %, S7 (ava_10)

Formula:




547/712

sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_et_bsc.

BSC ET availability %, S7 (ava_11)

Formula: sum(remote_avail_time) 100 * --------------------- % sum(remote_total_time) Counters from table(s): p_nbsc_et_bsc.

BSC TCSM availability %, S7 (ava_12)

Formula: sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_et_tcsm.




548/712

BSC TCSM availability %, S7 (ava_13)

Formula: sum(remote_avail_time) 100 * --------------------- % sum(remote_total_time) Counters from table(s): p_nbsc_et_tcsm.

TRE availability %, S6 (ava_14)

Formula: sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_tre.

Average CS territory, S9 (ava_15)

Use: Used on the BTS level. It indicates the average number of TCHs available for circuit switched traffic (CS). For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Note that this is not the same as the total capacity available for CS traffic, which is defined as ava_21. If CS traffic grows, the PS territory can diminish to what is defined as dedicated territory and give space for CS traffic. This figure is affected by:




549/712

1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: If extended cells are used, this KPI shows the correct value only on the BTS/trx_type level. Formula: sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) Counters from table(s): p_nbsc_res_avail

Unit: time slots

Average CS territory, Area S9 (ava_54)

Use: Known problems: If extended cells are used, this KPI shows the correct value only on the BTS/trx_type level. Formula: ava_52 + ava_53 Counters from table(s): p_nbsc_res_avail




550/712

Unit: time slots

Average PS territory, S9PS (ava_16)

Use: BTS level. Shows the actual average territory available for packet switched (PS) traffic. The value can be used for tuning the CDEF parameter. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: If extended TRXs are used, the values are correct only if the report is on BTS / TRX_type level. Formula: sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) Counters from table(s): p_nbsc_res_avail

Unit: time slots




551/712

Average PS territory, S9PS (ava_16a)

Use: BTS level. Shows the actual average territory available for packet switched (PS) traffic. The value can be used for tuning the CDEF parameter. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: GPRS timeslots can only be in normal TRXs. Formula: sum(decode(trx_type,0,ave_GPRS_channels_sum)) ---------------------------------------------- sum(decode(trx_type,0,ave_GPRS_channels_den)) Counters from table(s): p_nbsc_res_avail

Unit: time slots

Average PS territory, S9PS BTS level (ava_16b)

Description: Average available GPRS Channels (territory).




552/712

Use: BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Shows the actual average territory available for packet switched (PS) traffic. The value can be used for tuning the CDEF parameter. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: GPRS timeslots can only be in normal TRXs. Formula: sum(decode(trx_type,0,ave_GPRS_channels_sum)) -------------------------------------------------------------------------------- sum(decode(trx_type,0, decode(ave_GPRS_channels_sum,0,0,ave_GPRS_channels_den))) Counters from table(s): p_nbsc_res_avail

Unit: timeslots

Average PS territory, Area,S9PS (ava_44)

Description: Average available GPRS Channels (territory). Use:

Shows the actual average territory available for packet switched (PS) traffic.




553/712

The value can be used for tuning the CDEF parameter. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: GPRS timeslots can only be in normal TRXs. Formula: sum(decode(trx_type,0,ave_GPRS_channels_sum)) -------------------------------------------------------------------------------- (avg(decode(trx_type,0, decode(ave_GPRS_channels_sum,0,0,ave_GPRS_channels_den))) * count(distinct period_start_time)

where ave_GPRS_channels_sum > 0 Counters from table(s): p_nbsc_res_avail

Unit: timeslots

Ratio of Average used PCU TSL capacity, PCU,S9PS (ava_59)

Description: Ratio of used PCU TSL handling capacity Use:

Known problems: Formula:




554/712

Average TSLs in PS territory ------------------------------------ PCU TSL handling capacity ava_44 (100 * --------) 256


Unit: %

Ratio of Average "not in use" PCU TSL capacity, PCU,S9PS (ava_60)

Description: Ratio of used PCU TSL handling capacity which is not carrying traffic Use:

Known problems: Formula: ava_44 (100 *( 1- -------- )) 256


Unit: %




555/712

Average available dedicated GPRS channels, S9PS (ava_17)

Use: BTS level. Indicates the average number of channels available only for dedicated PS (GPRS) traffic. This capacity is allocated by setting the parameter CDED. In the case that there are no dedicated GPRS channels, throughput is not guaranteed, if CS traffic needs all the capacity.

Known problems: If extended TRXs are used, the values are correct only if the report is on the BTS/TRX type level. Formula: sum(ave_permanent_GPRS_ch_sum)/sum(ave_permanent_GPRS_ch_den) Counters from table(s): p_nbsc_res_avail

Average available dedicated GPRS channels, BTS levelS9PS (ava_17a)

Use: BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Indicates the average number of channels available only for dedicated PS (GPRS) traffic. This capacity is allocated by setting the parameter CDED. In the case that there are no dedicated GPRS channels, throughput is not guaranteed, if CS traffic needs all the capacity.

Known problems: GPRS timeslots can only be in normal TRXs. Formula: sum(decode(trx_type,0,ave_permanent_GPRS_ch_sum)) ------------------------------------------------- sum(decode(trx_type,0,ave_permanent_GPRS_ch_den))




556/712


Average available dedicated GPRS channels, Area S9PS (ava_51)

Use: Indicates the average number of channels available only for dedicated PS (GPRS) traffic. This capacity is allocated by setting the parameter CDED. In the case that there are no dedicated GPRS channels, throughput is not guaranteed, if CS traffic needs all the capacity.

Known problems: GPRS timeslots can only be in normal TRXs. Formula: sum(decode(trx_type,0,ave_permanent_GPRS_ch_sum)) ------------------------------------------------- (avg(decode(trx_type,0, decode(ave_permanent_GPRS_ch_sum,0,0,ave_permanent_GPRS_ch_den))) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

xxxx (ava_18)

ava_18 is replaced by ava_15. Share of TCH defined as PS territory, S9PS (ava_19)





557/712

sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) 100 * --------------------------------------------------- % sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den)+ sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) Counters from table(s): p_nbsc_res_avail

TRE-SEL availability %, S6 (ava_20)

Formula: sum(avail_time) 100 * --------------- % sum(total_time) Counters from table(s): p_nbsc_tre_sel.

Number of TSLs available for CS traffic, S9 (ava_21)

Use: BTS level. This KPI shows all the available timeslots that are not dedicated for PS (GPRS), i.e. that can be used by CS traffic. Note that this is not the same as CS territory, which is defined as ava_15.

Known problems: Incorrect if extended TRXs were used. Formula: sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den)




558/712

+ sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) - sum(ave_permanent_GPRS_ch_sum)/sum(ave_permanent_GPRS_ch_den) Counters from table(s): p_nbsc_res_avail

Number of TSLs available for CS traffic on normal TRXs, S9 (ava_21a)

Use: BTS level. This KPI shows all the available timeslots that are not dedicated for PS (GPRS), i.e. that can be used by CS traffic on normal TRXs.

Formula: ava_28 ; Pure CS TCHs on normal TRXs +ava_16a-ava_17a ; dynamic part of PS territory

Number of TSLs available for CS traffic on normal TRXs, S9 (ava_21b)

Use: BTS level. This KPI shows all the available timeslots that are not dedicated for PS (GPRS), i.e. that can be used by CS traffic on normal TRXs.

Formula: ava_28a ; Pure CS TCHs on normal TRXs + ava_16b - ava_17a ; dynamic part of PS territory

Number of TSLs available for CS traffic on normal TRXs, Area, S9 (ava_62)

Use: This KPI shows all the available timeslots that are not dedicated for PS (GPRS), i.e. that can be used by CS traffic on normal TRXs. Formula:




559/712

ava_52 ; Pure CS TCHs on normal TRXs

+ ava_44 - ava_51 ; dynamic part of PS territory Number of HR TSLs available, S9 (ava_22)

Use: Average number of timeslots available for half rate traffic only. Known problems: Incorrect values if extended TRXs were used. Formula: Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) -sum(ave_avail_full_TCH)/sum(res_av_denom2) Counters from table(s): p_nbsc_res_avail

Number of HR TSLs available, S9 (ava_22a)

Use: Average number of timeslots available for half rate traffic only. Known problems: Formula: ava_30+ava_31 Unit: tsls

Number of HR TSLs available, Area, S9 (ava_64)

Use: Average number of timeslots available for half rate traffic only.




560/712

Known problems: Formula: ava_42+ava_37 Unit: tsls

Number of FR TSLs available, S9 (ava_23)

Use: Average number of timeslots available for full rate traffic only. Known problems: Incorrect if extended TRXs were used. Formula: Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) – avg(ave_tch_avail_half)/2 Counters from table(s): p_nbsc_res_avail

Number of FR TSLs available, S9 (ava_23a)

Use: Average number of timeslots available for full rate traffic only. Known problems: Formula: ava_32 ; FR tsls on normal TRXs + ava_33; FR tsls on extended TRXs





561/712

Number of FR TSLs available, Area, S9 (ava_65)

Use: Average number of timeslots available for full rate traffic only. Known problems: Formula: ava_43 ; FR tsls on normal TRXs + ava_38; FR tsls on extended TRXs


Number of dual TSLs available, S9 (ava_24)

Use: Average number of timeslots available for dual (half rate or full rate) traffic. Known problems: Incorrect values if extended TRXs were used. Formula: sum(ave_avail_full_TCH)/sum(res_av_denom2) + avg(ave_tch_avail_half)/2 - Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) Counters from table(s): p_nbsc_res_avail

Number of dual TSLs available, S9 (ava_24a)

Use: Average number of timeslots available for dual (half rate or full rate) traffic Known problems: Formula:




562/712

ava_34 ; dual tsls on normal TRXs + ava_35 ; dual tsls on extended TRXs Counters from table(s): p_nbsc_res_avail

Number of dual TSLs available, Area, S9 (ava_66)

Use: Average number of timeslots available for dual (half rate or full rate) traffic Known problems: Formula: ava_41 ; dual tsls on normal TRXs + ava_40 ; dual tsls on extended TRXs Counters from table(s): p_nbsc_res_avail

Number of available TCH TSLs , S9 (ava_25)

Use: Average number of TCH timeslots (both CS and PS) available. Formula: Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) +sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) Counters from table(s): p_nbsc_res_avail




563/712

Average number of available TCH TSLs, S9 (ava_25a)

Use: BTS level. Average number of TCH timeslots (both CS and PS) available. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Formula: ava_31 ; HR timeslots on extended TRXs + ava_33 ; FR timeslots on extended TRXs + ava_35 ; dual timeslots on extended TRXs + ava_30 ; HR timeslots on normal TRXs + ava_32 ; FR timeslots on normal TRXs + ava_34; ; Dual timeslots on normal TRXs + ava_16a ; PS territory timeslots (always on normal TRXs) ) Counters from table(s): p_nbsc_res_avail

Average number of available TCH TSLs, S9 (ava_25b)

Use: BTS level. Average number of TCH timeslots (both CS and PS) available. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Formula: ava_31 ; HR timeslots on extended TRXs + ava_33 ; FR timeslots on extended TRXs + ava_35 ; dual timeslots on extended TRXs + ava_30 ; HR timeslots on normal TRXs + ava_32 ; FR timeslots on normal TRXs + ava_34; ; Dual timeslots on normal TRXs




564/712

+ ava_16b ; PS territory timeslots (always on normal TRXs) ) Counters from table(s): p_nbsc_res_avail

Number of available TCH TSLs, PS and CS common, S9 (ava_26)

Use: Average number of timeslots available for both CS and PS traffic. These are part of PS (GPRS) territory but if CS traffic needs, they can be taken to CS call use (territory downgrade) automatically by BSC.

Known problems: If extended TRXs were used, the values are correct only if the report is on the BTS/TRX_type level. Formula: ava_16 - ava_17

Number of available TCH TSLs, PS and CS common, S9 (ava_26a)

Use: Average number of timeslots available for both CS and PS traffic. These are part of PS (GPRS) territory but if CS traffic needs they can be taken to CS call use (territory downgrade) automatically by BSC. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Formula: ava_16a-ava_17a

Number of available TCH TSLs, PS and CS common, S9 (ava_26b)


Known problems:




565/712

Formula: ava_16b - ava_17a

Number of available TCH TSLs, PS and CS common, Area S9 (ava_50)


Known problems: Formula: ava_44 - ava_51

TCH total erlang capacity, S9 (ava_27)

Use: Dimensioning reference. Formula: FR timeslots + 2*(HR timeslots + dual timeslots) = ava_23 + 2* (ava_22 + ava_24 + ava_26) = Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) + avg(ave_tch_avail_half)/2 + 2* sum(ave_GPRS_channels_sum)/sum(ave_GPRS_channels_den) - 2* sum(ave_permanent_GPRS_ch_sum)/sum(ave_permanent_GPRS_ch_den) Counters from table(s): p_nbsc_res_avail




566/712

Average CS TCH in normal TRXs, S9 (ava_28)

Use: BTS level. Indicates the average number of TCHs available for circuit switched traffic (CS) in normal TRXs. This capacity can also be used for PS traffic if CS traffic is low. If CS traffic grows, the PS territory can diminish to what is defined as dedicated territory and give space for CS traffic. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: Formula: sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den)) Counters from table(s): p_nbsc_res_avail Unit: timeslots

Average CS TCH in normal TRXs, S9 (ava_28a)

Description: Average available TCHs for CS use in normal TRXs.




567/712

Use: BTS level. Indicates the average number of TCHs available for circuit switched traffic (CS) in normal TRXs. This capacity can also be used for PS traffic if CS traffic is low. If CS traffic grows, the PS territory can diminish to what is defined as dedicated territory and give space for CS traffic. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: Formula: sum(decode(trx_type,0,ave_avail_TCH_sum)) ------------------------------------------------------------------------- sum(decode(trx_type,0, decode(ave_avail_TCH_sum,0,0, ave_avail_TCH_den))) Counters from table(s): p_nbsc_res_avail Unit: timeslots

Average CS TCH in normal TRXs, Area S9 (ava_52)

Description: Average available TCHs for CS use in normal TRXs. Use: BTS level. Indicates the average number of TCHs available for circuit switched traffic (CS) in normal TRXs. This capacity can also

be used for PS traffic if CS traffic is low.




568/712

If CS traffic grows, the PS territory can diminish to what is defined as dedicated territory and give space for CS traffic. This figure is affected by 1) The settings of BTS parameters CDEF and CDED 2) Changes of capacity a) TRX locked or unlocked by the operator. If TRXs are locked and BTSs and BCFs are unlocked, the TCHs of that TRX appear as unavailable. b) TRX disabled by BSC due to fatal faults 3) Upgrades and downgrades of territory by BSC according to traffic needs

Known problems: Formula: sum(decode(trx_type,0,ave_avail_TCH_sum)) ------------------------------------------------------------------------- avg(decode(trx_type,0, decode(ave_avail_TCH_sum,0,0, ave_avail_TCH_den))) * count(dinstinct period_start_time)


Counters from table(s): p_nbsc_res_avail Unit: timeslots

Average available CS TCH in extended TRXs, S9 (ava_29)

Use: BTS level. Indicates the average number of TCHs available for circuit switched traffic (CS) in extended TRXs. This capacity cannot be used for PS traffic.

Known problems:




569/712

Formula: nvl(sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den)),1) Counters from table(s): p_nbsc_res_avail Unit: time slots

Average available CS TCH in extended TRXs, Area S9 (ava_53)

Use: BTS level. Indicates the average number of TCHs available for circuit switched traffic (CS) in extended TRXs. This capacity cannot be used for PS traffic.

Known problems: Formula: nvl(sum(decode(trx_type,1,ave_avail_TCH_sum))/(avg(decode(trx_type,1,ave_avail_TCH_den)) * count (distinct period_start_time),1) Counters from table(s): p_nbsc_res_avail Unit: time slots

Number of HR TSLs available, normal TRXs, S9 (ava_30)

Use: Average number of timeslots available for half rate traffic only. On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Formula: Sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den))




570/712

-sum(decode(trx_type,0,ave_avail_full_TCH))/sum(decode(trx_type,0,res_av_denom2)) Counters from table(s): p_nbsc_res_avail

Number of HR TSLs available, normal TRXs, Area,S9 (ava_42)

Use: On area level, Average number of timeslots available for half rate traffic only. Known problems: Formula: ( sum(decode(trx_type,0,ave_avail_TCH_sum)) / (avg(decode(trx_type,0,ave_avail_TCH_den))* count(distinct period_start_time)) ) - ( sum(decode(trx_type,0,ave_avail_full_TCH)) / ( avg(decode(trx_type,0,res_av_denom2)) * count(distinct period_start_time) ) ) Counters from table(s): p_nbsc_res_avail

Number of HR TSLs available, extended TRXs S9 (ava_31)

Use: Average number of timeslots available for half rate traffic only.




571/712

Used on the BTS level. If used on the area level, it shows the average over extended cells only. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Formula: nvl(Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den)) -sum(decode(trx_type,1,ave_avail_full_TCH))/sum(decode(trx_type,1,res_av_denom2)),0)


Number of HR TSLs available, extended TRXs , Area, S9 (ava_37)

Use: Average number of timeslots available for half rate traffic only. Known problems: Formula: nvl( ( sum(decode(trx_type,1,ave_avail_TCH_sum)) / ( avg(decode(trx_type,1,ave_avail_TCH_den)) * count(distinct period_start_time) ) ) - ( sum(decode(trx_type,1,ave_avail_full_TCH))




572/712

/ ( avg(decode(trx_type,1,res_av_denom2) * count(distinct period_start_time) ) ) ,0) Counters from table(s): p_nbsc_res_avail

Number of FR TSLs available, normal TRXs, S9 (ava_32)

Use: Average number of timeslots available on normal TRXs for full rate traffic only. On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Formula: Sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den)) - avg(decode(trx_type,0,ave_tch_avail_half))/2


Number of FR TSLs available, normal TRXs, Area,S9 (ava_43)

Use: Average number of timeslots available on normal TRXs for full rate traffic only. Known problems: Formula:




573/712

( sum(decode(trx_type,0,ave_avail_TCH_sum)) / ( avg(decode(trx_type,0,ave_avail_TCH_den)) * count(distinct period_start_time) ) ) - ( sum(decode(trx_type,0,ave_tch_avail_half * RES_AV_DENOM1)) / ( 2 * avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time) ) ) Counters from table(s): p_nbsc_res_avail

Number of FR TSLs available, extended TRXs, S9 (ava_33)

Use: Average number of timeslots available on extended TRXs for full rate traffic only. Used on the BTS level. If used on area level, shows the average over extended cells only. For area (or segment) level, first use the

formula for all the BTSs and then sum this formula over all underlying BTSs. Known problems: Formula: nvl(Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den)) - avg(decode(trx_type,1,ave_tch_avail_half))/2,0)




574/712


Number of FR TSLs available, extended TRXs, Area, S9 (ava_38)

Use: Average number of timeslots available on extended TRXs for full rate traffic only. Known problems: Formula: nvl( sum(decode(trx_type,1,ave_avail_TCH_sum))/(avg(decode(trx_type,1,ave_avail_TCH_den)) * count(distinct period_start_time) - sum(decode(trx_type,1,ave_tch_avail_half * RES_AV_DENOM1))/(2 * avg(decode(trx_type,1,ave_avail_TCH_den)) * count(distinct period_start_time)) ,0)


Number of dual TSLs available, normal TRXs, S9 (ava_34)

Use: Average number of timeslots available for dual (half rate or full rate) traffic. On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Formula: sum(decode(trx_type,0,ave_avail_full_TCH))/sum(decode(trx_type,0,res_av_denom2)) + avg(decode(trx_type,0,ave_tch_avail_half))/2 - Sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den)) +




575/712


Number of dual TSLs available, extended TRXs, S9 (ava_35)

Use: Average number of timeslots available for dual (half rate or full rate) traffic. Used on the BTS level. If used on the area level, it shows the average over extended cells only. For area (or segment) level, first use

the formula for all the BTSs and then sum this formula over all underlying BTSs. Known problems: Formula: nvl(sum(decode(trx_type,1,ave_avail_full_TCH))/sum(decode(trx_type,1,res_av_denom2)) + avg(decode(trx_type,1,ave_tch_avail_half))/2 - Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den))

,0) Counters from table(s): p_nbsc_res_avail

Number of dual TSLs available, extended TRXs, Area,S9 (ava_40)

Use: Average number of timeslots available for dual (half rate or full rate) traffic. Known problems: Formula: nvl( ( sum(decode(trx_type,1,ave_avail_full_TCH))




576/712

/ ( avg(decode(trx_type,1,res_av_denom2)) * count(distinct period_start_time) ) ) + ( sum(decode(trx_type,1,ave_tch_avail_half * RES_AV_DENOM1)) / ( 2 * avg(decode(trx_type,1, RES_AV_DENOM1)) * count(distinct period_start_time) ) ) - ( sum(decode(trx_type,1,ave_avail_TCH_sum)) / ( avg(decode(trx_type,1,ave_avail_TCH_den)) * count(distinct period_start_time) ) ) ,0) Counters from table(s): p_nbsc_res_avail

Number of dual TSLs available, normal TRXs, Area,S9 (ava_41)

Use: Average number of timeslots available for dual (half rate or full rate) traffic. Known problems: Formula: nvl( (




577/712

sum(decode(trx_type,0,ave_avail_full_TCH)) / ( avg(decode(trx_type,0,res_av_denom2)) * count(distinct period_start_time) ) ) + ( sum(decode(trx_type,0,ave_tch_avail_half * RES_AV_DENOM1)) / ( 2 * avg(decode(trx_type,0, RES_AV_DENOM1)) * count(distinct period_start_time) ) ) - ( sum(decode(trx_type,0,ave_avail_TCH_sum)) / ( avg(decode(trx_type,0,ave_avail_TCH_den)) * count(distinct period_start_time) ) ) ,0) Counters from table(s): p_nbsc_res_avail

GPRS enable time %, S10 (ava_36)

Description: Percentage of time, GPRS is enabled. Use: To indicate the GPRS availability in time. Known problems: Formula:




578/712

(100*(AVE_PCH_GB_LOAD_ON_CCCH_DEN / RES_ACC_DENOM1)) Counters from table(s): p_nbsc_res_access Unit: %

GPRS enable time %, S10 (ava_36a)

AVE_PCH_GB_LOAD_ON_CCCH_DENDescription: Percentage of time, GPRS is enabled. Use: To indicate the GPRS availability in time. Known problems: Formula: (100*(decode(AVE_PCH_GB_LOAD_ON_CCCH_DEN, 1, 0, AVE_PCH_GB_LOAD_ON_CCCH_DEN) / RES_ACC_DENOM1)) Counters from table(s): p_nbsc_res_access

Unit: % Average number of available TCH TSLs, Area, S9 (ava_39)

Use: Average number of TCH timeslots (both CS and PS) available. Formula: ava_37 ; HR timeslots on extended TRXs + ava_38 ; FR timeslots on extended TRXs + ava_40 ; dual timeslots on extended TRXs + ava_42 ; HR timeslots on normal TRXs + ava_43 ; FR timeslots on normal TRXs + ava_41; ; Dual timeslots on normal TRXs + ava_44 ; PS territory timeslots (always on normal TRXs) )




579/712


Average available SDCCH, Area,S1 (ava_45)

Use: Area level Average available SDCCH

Formula: sum(ave_sdcch_sub) / (avg(res_av_denom3) * count(distinct period_start_time)) Counters from table(s): p_nbsc_res_avail

Average available SDCCH, Area,S1 (ava_45a)

Use: Area level Average available SDCCH

Formula: ava_48 + ava_49 Counters from table(s): p_nbsc_res_avail




580/712

Average available SDCCH, normal TRX, BTS Level, S1 (ava_46)

Note: Formula: sum(decode(trx_type,0,ave_sdcch_sub)/ sum(decode(trx_type,0,res_av_denom3) Counters from table(s): p_nbsc_res_avail

Average available SDCCH, extended TRX, BTS Level, S1 (ava_47)

Note: Formula: sum(decode(trx_type,1,ave_sdcch_sub)/ sum(decode(trx_type,1,res_av_denom3) Counters from table(s): p_nbsc_res_avail

Average available SDCCH, normal TRX, Area, S1 (ava_48)

Note: Formula: sum(decode(trx_type,0,ave_sdcch_sub) -------------------------------------------------------------------- avg(decode(trx_type,0,res_av_denom3) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail




581/712

Average available SDCCH, extended TRX, Area, S1 (ava_49)

Note: Formula: sum(decode(trx_type,1,ave_sdcch_sub) -------------------------------------------------------------------- avg(decode(trx_type,1,res_av_denom3) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Next free (ava_61)

Unavailability (uav)

Average unavailable TSL per BTS, S1 (uav_1)

Use: For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: sum(ave_non_avail_tsl)/sum(res_av_denom1) Counters from table(s): p_nbsc_res_avail




582/712

Average unavailable TSL per BTS, S1 (uav_1a)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: avg(ave_non_avail_tsl/res_av_denom1) Counters from table(s): p_nbsc_res_avail

Average unavailable TSL per BTS, S1 (uav_1b)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. Formula: sum(ave_non_avail_tsl/res_av_denom1) ------------------------------------ count(*) Counters from table(s): p_nbsc_res_avail

Total outage time, (uav_2)

Known problems: It should be made possible to differentiate the reasons for outage. Note: Alarm number changed in S7 from 2567 to 7767. Formula: sum of BCCH missing alarm durations =




583/712

sum(cancel_time-alarm_time)*24*60 where probable_cause = 7767 /* BCCH missing alarm */ Counters from table(s): fx_alarm unit = minutes

Number of outages, (uav_3)

Note: Alarm number changed in S7 from 2567 to 7767. Formula: number of BCCH missing alarm starts = count(alarm_start_time) where probable_cause = 7767 /* BCCH missing alarm */ Counters from table(s): fx_alarm

Share of unavailability due to user, (uav_4)

Experiences on use: Locked TRXs can make this PI show high values. Known problems: The measurement is made on the BSC level. The BTS level cannot be seen. Formula: sum(ave_non_avail_user) 100 * -------------------------------------------------------------- % sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext)




584/712

Counters from table(s): p_nbsc_trx_avail

Share of unavailability due to internal reasons, (uav_5)

Known problems: The measurement is made on the BSC level. The BTS level cannot be seen. This KPI also includes, for example, an electricity break which, in fact, is not a BTS fault. Formula: sum(ave_non_avail_int) 100 * -------------------------------------------------------------- % sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext) Counters from table(s): p_nbsc_trx_avail

Share of unavailability due to external reasons, (uav_6)

Known problems: The measurement is made on the BSC level. The BTS level cannot be seen. Formula: sum(ave_non_avail_ext) 100 * -------------------------------------------------------------- % sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext) Counters from table(s): p_nbsc_trx_avail




585/712

TRX unavailability time due to user, (uav_7)

Experiences on use: Locked TRXs can make this PI show high values. Formula: sum(period_duration * ave_non_avail_user) Counters from table(s): p_nbsc_trx_avail

TRX unavailability time due to internal reasons, (uav_8)

Known problems: This KPI also includes, for example, an electricity break which, in fact, is not a BTS fault. Formula: sum(period_duration * ave_non_avail_int) Counters from table(s): p_nbsc_trx_avail

TRX unavailability time due to external reasons, (uav_9)

Formula: sum(period_duration * ave_non_avail_ext) Counters from table(s): p_nbsc_trx_avail




586/712

Average unavailable SDCCH, S5 (uav_10)

Note: 1. This KPI has to be counted separately for extended and normal area (trx_type: 0 = normal, 1 = extended). 2. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Formula: avg(ave_non_avail_sdcch) Counters from table(s): p_nbsc_res_avail

Average unavailable SDCCH, BTS level, S5 (uav_10a)

Note: Formula: uav_18 + uav_19 Counters from table(s): p_nbsc_res_avail

Average unavailable SDCCH, Area level, S5 (uav_22)

Note: Formula:




587/712

uav_20 + uav_21 Counters from table(s): p_nbsc_res_avail

Average unavailable TCH, S5 (uav_11)

Known problems: Locked TRXs are counted as unavailable TCH.Formula: avg(ave_non_avail_tch) Counters from table(s): p_nbsc_res_avail

Average unavailable TCH, S5 (uav_11a)

Use: On BTS level. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs. Known problems: Locked TRXs are counted as unavailable TCH.Formula: uav_13 + uav_14

Average bearer unavailability, S9PS (uav_12)

Known problems: Formula: 100*sum(time_bear_oper_unoper)/sum(period_duration*60) Counters from table(s):




588/712

p_nbsc_frame_relay

Average unavailable TCH on normal TRXs, BTS, S5 (uav_13)

Known problems: Locked TRXs are counted as unavailable TCH.Description: Average unavailable TCH on normal TRXs. On BTS Level. Formula: avg(decode(trx_type,0,ave_non_avail_tch)) Counters from table(s): p_nbsc_res_avail

Average unavailable TCH on normal TRXs, Area, S5 (uav_15)

Known problems: Locked TRXs are counted as unavailable TCH.Description: Average unavailable TCH on normal TRXs. On BTS Level. Formula: sum(decode(trx_type,0,ave_non_avail_tch * RES_AV_DENOM1)) =================================================================== avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail




589/712

Average unavailable TCH on extended TRXs, S5 (uav_14)

Use: On the BTS level. If used on the area level, it shows the average over extended cells only. For area (or segment) level, first use the formula for all the BTSs and then sum this formula over all underlying BTSs.

Known problems: Locked TRXs are counted as unavailable TCH.Formula: nvl(avg(decode(trx_type,1,ave_non_avail_tch)),0) Counters from table(s): p_nbsc_res_avail

Average unavailable TCH on extended TRXs, Area, S5 (uav_16)

Use: Known problems: Locked TRXs are counted as unavailable TCH.Formula: nvl(sum(decode(trx_type,1,ave_non_avail_tch * RES_AV_DENOM1)),0) ====================================================================== avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Average unavailable TCH, Area, S5 (uav_17)

Use: Average unavailable TCH on Area level Known problems: Locked TRXs are counted as unavailable TCH.Formula:




590/712

uav_15 + uav_16

Average unavailable SDCCH, normal TRX, BTS level S5 (uav_18)

Note: Formula: avg(decode(trx_type,0,ave_non_avail_sdcch)) Counters from table(s): p_nbsc_res_avail

Average unavailable SDCCH, extended TRX, BTS level S5 (uav_19)

Note: Formula: avg(decode(trx_type,1,ave_non_avail_sdcch)) Counters from table(s): p_nbsc_res_avail

Average unavailable SDCCH, normal TRX, Area level S5 (uav_20)

Note: Formula:




591/712

nvl(sum(decode(trx_type,0,ave_non_avail_sdcch * RES_AV_DENOM1)),0) ======================================================================

avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Average unavailable SDCCH, extended TRX, Area level S5 (uav_21)

Note: Formula: nvl(sum(decode(trx_type,1,ave_non_avail_sdcch * RES_AV_DENOM1)),0) ======================================================================

avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time) Counters from table(s): p_nbsc_res_avail

Next free (uav_13)

Location updates (lu)

Number of LU attempts, S1 (lu_1)

Formula:




592/712

sum(sdcch_loc_upd) Counters from table(s): p_nbsc_res_access

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

Formula: sum(sdcch_loc_upd) -------------------------------- avg(period_duration)*count(*)/60 Counters from table(s): p_nbsc_res_access

Number of LU attempts, S1 (lu_3)

Formula: sum(nbr_of_calls) where counter_id = 25 /* LU started */




593/712

Next free (lu_4)

LU Success % (lsr)

LU success %, (lsr_1)

Known problems: Emergency calls and re-establishment are included in the nominator but not in the denominator. This PI does not precisely tell the success ratio because sdcch_loc_upd indicates the SDCCH seizure but not the successful LU.

Formula: sum(b.sdcch_loc_upd) 100* (----------------------------------------)% sum(a.sdcch_seiz_att) -sum(b.succ_seiz_term+b.succ_seiz_orig) Counters from table(s): a = nbsc_traffic b = nbsc_res_access

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. LU started (51025) is triggered from establish.indication. Any problems prior to that cannot be seen. For example, interference

prevents a mobile station from making a location update. Values: Good: >99% Formula: sum(nbr_of_calls) where counter_id = 26 /* LU completed */ 100 * -------------------------------------------------------------- %




594/712

sum(nbr_of_calls) where counter_id = 25 /* LU started */ Counters from table(s): p_nbsc_cc_pm

LU success %, S4 (lsr_3)

Use: Known problems: The measurement is made on the BSC level and thus the selection of a BTS group or MR is not possible. If res_acc is running with the 60 min period and clear code with 24 h and period_stop is used, the result is not correct because

the data from p_nbsc_cc_pm would then come from a wrong day. Formula: sum(b.nbr_of_calls) where b.counter_id = 26 /* LU succeeded*/ 100 * -------------------------------------------------------------- % sum(a.sdcch_loc_upd) /* LU attempts*/ Counters from table(s): a = p_nbsc_res_access b = p_nbsc_cc_pm




595/712

Next free (lsr_4)

LU Failure (luf)

Emergency Call (ec)

Emergency calls, S6 (ec_1)

Formula: sum(nbr_of_calls) where counter_id = 35 /* Em.call started */ Counters from table(s): p_nbsc_cc_pm

Next free (ec_2)

Emercency Call Success % (ecs)

Emergency call success %, S6 (ecs_1)

Formula: sum(nbr_of_calls) where counter_id = 41 /* Em.call completed */ 100 * ----------------------------------------------------------------------- sum(nbr_of_calls) where counter_id = 35 /* Em.call started */ Counters from table(s):




596/712

p_nbsc_cc_pm

Next free (ecs_2)

Call Re-establishment (re)

Call re -establishment attempts, S6 (re_1)

Formula: sum(nbr_of_calls) where counter_id = 36 /* Call reest. started */ Counters from table(s): p_nbsc_cc_pm

Call re -establishment attempts, S6 (re_2)

Formula: sum(b.sdcch_call_re_est+b.tch_call_re_est) b = p_nbsc_res_access

Call re -establishments, S6 (re_3)

Formula: sum(tch_re_est_assign)




597/712


Next free (re_4)

Call Re-establishment Success % (res)

Call re -establishment success %, S6 (res_1)

Formula: sum(nbr_of_calls) where counter_id = 42 /* Call reest. completed */ 100 * ----------------------------------------------------------------------- sum(nbr_of_calls) where counter_id = 36 /* Call reest. started */ Counters from table(s): p_nbsc_cc_pm

Next free (res_2)

Downlink Quality (dlq)

DL BER, S1 (dlq_1)

Known problems: 1) BER % is not a very easy entity for a network planner. 2) Measurement periods that have no call on TCH, have power_denom5 = 0. Formula:




598/712

sum(ave_dl_sig_qual) ----------------------- % sum(power_denom5)*100 Counters from table(s): p_nbsc_power Unit = BER %

DL BER, S1 (dlq_1a)

Use: Downlink bit error ratio. Includes both SDCCH and TCH. Known problems: BER % is not a very easy entity for network planners. Formula: sum(ave_dl_sig_qual) ------------------------ % sum(decode(power_denom5+ ave_dl_sig_qual,1,0,power_denom5)*100) Counters from table(s): p_nbsc_power Unit = BER %

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

Use: This PI gives a cumulative percentage of call samples (AMR, non-AMR) in classes 0 to X. X = 5 is normally used as a quality indicator. If X = 5 and this figure is 100 %, then the MS users obviously have not perceived any quality problems.

Known problems: If DL DTX is used, there is a shift to a worse quality %, but a MS does not perceive this.




599/712

Formula: sum(freq_dl_qual0 + ... + freq_dl_qualX) 100 * ------------------------------------------ % sum(freq_dl_qual0 + ... + freq_dl_qual7) Counters from table(s): p_nbsc_rx_qual

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

Use: This PI gives a cumulative percentage of call samples (AMR, non-AMR) in classes 0 to X. X = 5 is normally used as a quality indicator. If X = 5 and this figure is 100 %, then the MS users obviously have not perceived any quality problems.

Known problems: If DL DTX is used, there is a shift to a worse quality %, but a MS does not perceive this. Formula: sum(freq_dl_qual0 + ... + freq_dl_qualX) 100 * ------------------------------------------ % sum(freq_dl_qual0 + ... + freq_dl_qual7) Counters from table(s): p_nbsc_rx_statistics

DL quality %, FER based, S10 (dlq_3)

Use: The share (as a percentage) of call samples in FEP classes 0 to 7.




600/712

Classes are defined by boundaries B0 to B8. Boundaries 1 to 7 can be set as a measurement parameter. Class 0 is between boundaries B0 (fixed 0%) and B1. Class 7 is between boundaries B7 and B8 (fixed 100%).

Note: In S10 all DL samples are estimated. Formula: sum(NBR_OF_DL_FER_CL_X) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) Counters from table(s): p_nbsc_fer

DL cumulative quality % in class X, HR AMR, S10 (dlq_4)

Use: This PI gives the cumulative percentage of call samples (downlink half rate AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator.

Formula: sum( nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_DL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_DL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_DL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_DL_RXQUAL_Z,0) ) 100* ------------------------------------------------------------------------- % sum( nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_DL_RXQUAL_7,0) +nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_DL_RXQUAL_7,0) +nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_DL_RXQUAL_7,0)




601/712

+nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_DL_RXQUAL_7,0) ) Counters from table(s): p_nbsc_rx_qual

DL cumulative quality % in class X, FR AMR, S10 (dlq_5)

Use: This PI gives the cumulative percentage of call samples (downlink full rate AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator.

Formula: sum( nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_DL_RXQUAL_Z,0 + nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_DL_RXQUAL_Z,0 + nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_DL_RXQUAL_Z,0 + nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_DL_RXQUAL_Z,0 ) 100 * ----------------------------------------------------------------------------- % sum( nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_DL_RXQUAL_7,0 + nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_DL_RXQUAL_7,0 + nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_DL_RXQUAL_7,0 + nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_DL_RXQUAL_7,0 ) Counters from table(s): p_nbsc_rx_qual




602/712

DL cumulative quality % in class X, S10 (dlq_6)

Use: This PI gives the cumulative percentage of all call samples (AMR and non-AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator. If Z = 5 and this figure is 100 %, the MS users obviously have not perceived any quality problems.

Formula: sum(freq_dl_qual0 + ... + freq_dl_qualZ) -sum( nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_DL_RXQUAL_Z,0) + nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_DL_RXQUAL_Z,0) + nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_DL_RXQUAL_Z,0) + nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_DL_RXQUAL_Z,0) ) -sum( nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_DL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_DL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_DL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_DL_RXQUAL_Z,0) ) 100 * ------------------------------------------------------------------------- % sum(freq_dl_qual0 + ... + freq_dl_qual7) -sum( nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_DL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_DL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_DL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_DL_RXQUAL_7,0) ) -sum( nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_DL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_DL_RXQUAL_7,0) + nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_DL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_DL_RXQUAL_7,0) )




603/712

Counters from table(s): p_nbsc_rx_qual

DL quality 0-5 %, HR, FER based, S10 (dlq_7)

Use: FER based quality benchmark for half rate speech traffic channel. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) codec_type = 1 Counters from table(s): p_nbsc_fer

DL quality 0-5 %, FR, FER based, S10 (dlq_8)

Use: FER based quality benchmark for FR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) codec_type = 2 Counters from table(s): p_nbsc_fer




604/712

DL quality 0-5 % EFR, FER based, S10 (dlq_9)

Use: FER based quality benchmark for EFR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) codec_type = 3 Counters from table(s): p_nbsc_fer

DL quality 0-5 % AMR HR, FER based, S10 (dlq_10)

Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) codec_type = 4..9 Counters from table(s): p_nbsc_fer




605/712

DL quality 0-5 % AMR FR, FER based, S10 (dlq_11)

Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7) codec_type = 10..17 Counters from table(s): p_nbsc_fer

DL quality % in Class 0 AMR HR, FER based, S10 (dlq_12)

Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_DL_FER_CL_0) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 4..9 Counters from table(s): p_nbsc_fer




606/712


Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_DL_FER_CL_0+NBR_OF_DL_FER_CL_1) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 4..9 Counters from table(s): p_nbsc_fer

Status: OK. DL quality 0-2 % AMR HR, FER based, S10 (dlq_14)

Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_2) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 4..9 Counters from table(s): p_nbsc_fer




607/712








608/712








609/712

DL quality % in Class 0 AMR FR, FER based, S10 (dlq_19)

Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_DL_FER_CL_0) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer


Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_DL_FER_CL_0+NBR_OF_DL_FER_CL_1) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer




610/712


Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_2) 100 * --------------------------------------------- % sum(NBR_OF_DL_FER_CL_0+…+NBR_OF_DL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer






611/712








612/712



Next free (dlq_26)

Uplink Quality (ulq)

UL BER, S1 (ulq_1)

Known problems: 1) BER % is not a very easy entity for a network planner. 2) Measurement periods that have no call on TCH, have power_denom6 = 0. sum(ave_ul_sig_qual) ------------------------ % sum(power_denom6)*100 Counters from table(s): p_nbsc_power




613/712

UL BER, S1 (ulq_1a)

Use: Uplink bit error ratio. Includes both SDCCH and TCH. Known problems: BER % is not very easy entity for a network planner. sum(ave_ul_sig_qual) ------------------------ % sum(decode(power_denom6+ ave_ul_sig_qual,1,0,power_denom6)*100) Counters from table(s): p_nbsc_power

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

Use: This PI gives the cumulative percentage of call samples (non AMR and AMR) in classes 0 to X. X = 5 is normally used as a quality indicator. If X = 5 and this figure is 100 %, the MS users obviously have not perceived any quality problems.

Known problems: Investigations in late 1997 showed that UL DTX makes UL quality seem worse than it actually is. The impact was about one 1% unit (1% of samples more in classes 6 and 7). When investigated with field tests, no real degradation of quality could be found.

Formula: sum(freq_ul_qual0 + ... + freq_ul_qualX) 100 * --------------------------------------------- % sum(freq_ul_qual0 + ... + freq_ul_qual7) Counters from table(s): p_nbsc_rx_qual




614/712

UL cumulative quality % in class X, S1 (ulq_2a)

Use: This PI gives the cumulative percentage of call samples in classes 0 to X. X = 5 is normally used as a quality indicator. If X = 5 and this figure is 100 %, the MS users obviously have not perceived any quality problems.

Formula: sum(freq_ul_qual0 + ... + freq_ul_qualX) 100 * -------------------------------------------------- % sum( freq_ul_qual0 + ... + freq_ul_qual7 ) Counters from table(s): p_nbsc_rx_statistics

UL quality %, FER based, S10 (ulq_3)

Use: The share (as a percentage) of call samples in FER classes 0 to 7. Classes are defined by boundaries B0 to B8. Boundaries 1 to 7 can be set as a measurement parameter. Class 0 is between

boundaries B0 (fixed 0%) and B1. Class 7 is between boundaries B7 and B8 (fixed 100%). Formula: sum(NBR_OF_UL_FER_CL_X) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7) Counters from table(s): p_nbsc_fer




615/712

UL cumulative quality % in class X, HR AMR, S10 (ulq_4)

Use: This PI gives the cumulative percentage of call samples (uplink half rate AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator.

Formula: sum( nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_Z,0) +nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_Z,0) ) 100* ------------------------------------------------------------------------ % sum( nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) +nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) +nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) +nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0) ) Counters from table(s): p_nbsc_rx_qual

UL cumulative quality % in class X, FR AMR, S10 (ulq_5)

Use: This PI gives the cumulative percentage of call samples (full rate AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator. Formula:




616/712

sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_Z,0 +nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_UL_RXQUAL_Z,0 +nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_UL_RXQUAL_Z,0 +nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_UL_RXQUAL_Z,0 ) 100* -------------------------------------------------------------------------- % sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0 +nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0 +nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0 +nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0 ) Counters from table(s): p_nbsc_rx_qual

UL cumulative quality % in class X, non-AMR S10 (ulq_6)

Use: This PI gives the cumulative percentage of all call samples (AMR and non AMR) in classes 0 to Z. Z = 5 is normally used as a quality indicator. If Z = 5 and this figure is 100 %, the MS users obviously have not perceived any quality problems.

Known problems: Investigations in late 1997 showed that UL DTX makes UL quality seem worse than it actually is. The impact was about one 1% unit (1% of samples more in classes 6 and 7). When investigated with field tests, no real degradation of quality could be found.

Formula: sum(freq_ul_qual0 + ... + freq_ul_qualZ) -sum( nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_UL_RXQUAL_Z,0)




617/712

+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_UL_RXQUAL_Z,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_UL_RXQUAL_Z,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_UL_RXQUAL_Z,0) ) -sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_UL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_UL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_UL_RXQUAL_Z,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_UL_RXQUAL_Z,0) ) 100 * ------------------------------------------------------------------------- % sum(freq_ul_qual0 + ... + freq_ul_qual7) -sum( nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0) ) -sum( nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0) + nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0) ) Counters from table(s): p_nbsc_rx_qual

UL quality 0-5 %, HR, FER based, S10 (ulq_7)

Use: FER based quality benchmark for HR calls. Formula:




618/712

sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7) codec_type = 1 Counters from table(s): p_nbsc_fer

UL quality 0-5 %, FR, FER based, S10 (ulq_8)

Use: FER based quality benchmark for FR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7) codec_type = 2 Counters from table(s): p_nbsc_fer

UL quality 0-5 % EFR, FER based, S10 (ulq_9)

Use: FER based quality benchmark for EFR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_5) 100 * --------------------------------------------- %




619/712

sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7) codec_type = 3 Counters from table(s): p_nbsc_fer

UL quality 0-5 % AMR HR, FER based, S10 (ulq_10)

Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7) codec_type = 4..9 Counters from table(s): p_nbsc_fer

UL quality 0-5 % AMR FR, FER based, S10 (ulq_11)

Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_5) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)




620/712

codec_type = 10..17 Counters from table(s): p_nbsc_fer

UL quality % in Class 0 AMR HR, FER based, S10 (ulq_12)

Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_UL_FER_CL_0) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 4..9 Counters from table(s): p_nbsc_fer


Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_UL_FER_CL_0 + NBR_OF_UL_FER_CL_1) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 4..9 Counters from table(s):




621/712

p_nbsc_fer


Use: FER based quality benchmark for AMR HR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_2) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 4..9 Counters from table(s): p_nbsc_fer






622/712








623/712



UL quality % in Class 0 AMR FR, FER based, S10 (ulq_19)

Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_UL_FER_CL_0) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer




624/712


Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_UL_FER_CL_0+NBR_OF_UL_FER_CL_1) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer


Use: FER based quality benchmark for AMR FR calls. Formula: sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_2) 100 * --------------------------------------------- % sum(NBR_OF_UL_FER_CL_0+…+NBR_OF_UL_FER_CL_7)) codec_type = 10..17 Counters from table(s): p_nbsc_fer




625/712








626/712








627/712

Next free (ulq_26)

DL level, (dll)

Share % per range, S4 (dll_1)

Formula: sum over a range (class_upper_range) (freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4 +freq_dl_qual5+freq_dl_qual6+freq_dl_qual7) 100 * ----------------------------------------------------------- % sum over all ranges (freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4 +freq_dl_qual5+freq_dl_qual6+freq_dl_qual7) Counters from table(s): p_nbsc_rx_statistics

Sorting factor for undefined adjacent cell, S4 (dll_2)

Use: Helps to sort the list of undefined adjacent cells. Formula: sum(ave_dl_sig_str)/1000




628/712

All counters are from the Counters from table(s): p_nbsc_undef_adj_cell table.

Next free (dll_3)

UL level, (ull)

Share % per range, S4 (ull_1)

Formula: sum over a range (class_upper_range) (freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4 +freq_ul_qual5+freq_ul_qual6+freq_ul_qual7) 100 * ----------------------------------------------------------- % sum over all ranges (freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4 +freq_ul_qual5+freq_ul_qual6+freq_ul_qual7) Counters from table(s): p_nbsc_rx_statistics




629/712

Next free (ull_2)

Power (pwr)

Average MS power, S2 (pwr_1)

Formula: max_power-2*sum(ave_ms_power)/sum(power_denom1) max_power = 43 (GSM900) or max_power = 30 (GSM1800, GSM1900) Counters from table(s): p_nbsc_power

Average MS power, S2 (pwr_1b)

Formula: decode(objects.frequency_band_in_use,0,43,30)-2*sum(ave_ms_power)/sum(power_denom1) Counters from table(s): p_nbsc_power Note: max_power = 43 (GSM900) or 30 (GSM1800, GSM1900)

Average BS power, S2 (pwr_2)

Formula: max_power - 2*sum(ave_BS_power)/sum(power_denom2)




630/712

max_power depends on the TRX used. Counters from table(s): p_nbsc_power

Next free (pwr_3)

Level (lev)

Average DL signal strength, S2 (lev_1)

Formula: -110+sum(ave_dl_sig_str)/sum(power_denom3) Counters from table(s): p_nbsc_power Unit: dBm

Average DL signal strength, S2 (lev_1a)

Formula: 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)) ) Counters from table(s): p_nbsc_power




631/712

Unit: dBm

Average UL signal strength, S2 (lev_2)

Formula: -110+sum(ave_ul_sig_str)/sum(power_denom4) Counters from table(s): p_nbsc_power Unit: dBm

Average UL signal strength, S2 (lev_2a)

Formula: 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)) ) Counters from table(s): p_nbsc_power Unit: dBm




632/712

Next free (lev_3)

Distance

Average MS-BS distance, (dis_1)

Formula: avg(ave_ms_bs_dist)*550 meter Counters from table(s): p_nbsc_power The condition below should be applied in order to filter out the hours that do not have traffic and for that reason show 0: peak_ms_bs_dist+ave_dl_sig_str +ave_ul_sig_str > 0

Average MS-BS distance, (dis_1a)

Formula: Counted per BTS/trx-type decode(trx_type, 0,ave_ms_bs_dist*550/1000, 1,ave_ms_bs_dist*550/1000+ c_bts.radius_extension )

Unit: km Counters from table(s): p_nbsc_power




633/712

If counted using average, the condition below should be applied in order to filter out the hours that do not have traffic and for that reason show 0: peak_ms_bs_dist+ave_dl_sig_str +ave_ul_sig_str > 0

Peak MS-BS distance, (dis_2a)

Formula: Counted per BTS/trx-type decode(trx_type, 0,peak_ms_bs_dist*550/1000, 1,peak_ms_bs_dist*550/1000+ c_bts.radius_extension)

Unit: km Counters from table(s): p_nbsc_power If counted using average, the condition below should be applied in order to filter out the hours that do not have traffic and for that reason show 0: peak_ms_bs_dist+ave_dl_sig_str +ave_ul_sig_str > 0

MS-BS distance class upper range, (dis_3a)

Formula: decode(trx_type, 0,class_upper_range*550/1000,




634/712

1, class_upper_range *550/1000+ c_bts.radius_extension)

Unit: km Counters from table(s): p_nbsc_power

Next free (dis_4)

Voice Quality (vq)

Voice quality, (vq_1)

This PI cannot be calculated from the NMS statistics. Formula: Voice echo, (vq_2)

This PI cannot be calculated from the NMS statistics. Formula: Voice delay, (vq_3)

This PI cannot be calculated from the NMS statistics. Formula:




635/712

Next free (vq_3)

Link Balance, Power, Level (lb)

Link balance, S1 (lb_1)

Formula: avg(ave_dl_sig_str/power_denom3) - avg(ave_ul_sig_str/power_denom4) Counters from table(s): p_nbsc_power

Share in acceptance range, S4 (lb_2)

Formula: sum(normal+ms_limited+bs_limited+max_power) {where class_sig_level <= upper threshold and class_sig_level >= lower threshold } 100 * ------------------------------------------------- % sum(normal+ms_limited+bs_limited+max_power) Counters from table(s): p_nbsc_link_balance

Share in normal, S4 (lb_3)

Formula: sum(normal) 100 * ------------------------------------------------- % sum(normal+ms_limited+bs_limited+max_power)




636/712

Counters from table(s): p_nbsc_link_balance

Share in MS limited, S4 (lb_4)

Formula: sum(ms_limited) 100 * ------------------------------------------------- % sum(normal+ms_limited+bs_limited+max_power) Counters from table(s): p_nbsc_link_balance

Share in BS limited, S4 (lb_5)

Formula: sum(bs_limited) 100 * ------------------------------------------------- % sum(normal+ms_limited+bs_limited+max_power) Counters from table(s): p_nbsc_link_balance

Share in Max power, S4 (lb_6)

sum(max_power) 100 * ------------------------------------------------- % sum(normal+ms_limited+bs_limited+max_power) Counters from table(s): p_nbsc_link_balance




637/712

Average MS power attenuation, S2 (lb_7)

Formula: 2*sum(ave_MS_power)/sum(power_denom1)

Unit= dB Counters from table(s): p_nbsc_power

Average MS power, S2 (lb_7b)

Formula: avg(decode(o_bts.freq_band_in_use,0,43,1,30)-2*ave_MS_power/power_denom1 Counters from table(s): p_nbsc_power Unit= dBm

Average BS power attenuation, S2 (lb_8)

Formula: sum(ave_BS_power)/sum(power_denom2) Counters from table(s): p_nbsc_power




638/712

Average BS power attenuation, S2 (lb_8b)

Formula: avg(ave_BS_power/power_denom2) Counters from table(s): p_nbsc_power

Average UL signal strength, S2 (lb_9)

Use: Values as defined by GSM 5.08. Values 0 to 63: 0 = less than –110 dBm

1 = -110 to -109 dBm 3 = -109 to –108 dBm 62 = -49 to –48 63 = greater than -48

Formula: sum(ave_ul_sig_str)/sum(power_denom4) Counters from table(s): p_nbsc_power

Average DL signal strength, S2 (lb_10)

Use: Values as defined by GSM 5.08. Values 0 to 63: 0 = less than –110 dBm




639/712

1 = -110 to -109 dBm 3 = -109 to –108 dBm 62 = -49 to –48 63 = greater than -48

sum(ave_dl_sig_str)/sum(power_denom3) Counters from table(s): p_nbsc_power

Average MS power attenuation, S2 (lb_11)

Formula: 2*sum(ave_MS_power)/sum(power_denom1) Counters from table(s): p_nbsc_power Unit = dB

Average BS power attenuation, S2 (lb_12)

Formula: 2*sum(ave_BS_power)/sum(power_denom2) Counters from table(s): p_nbsc_power Unit=dB




640/712

Average link imbalance, S2 (lb_13)

Formula: 2*sum(ave_BS_power)/sum(power_denom2)+sum(ave_dl_sig_str)/sum(power_denom3) -2*sum(ave_MS_power)/sum(power_denom1)-sum(ave_ul_sig_str)/sum(power_denom4) Counters from table(s): p_nbsc_power Unit=dB

Next free (lb_14)

Call Success (csf)

SDCCH access probability, before FCS (csf_1)

Use: Gives the probability to access SDCCH without the effect of FCS. Applicable for area and BTS level. Known problems: 1) The momentary SDCCH blocking phenomenon is met in some networks.

2) SDCCH_busy_att triggered also in the case of HO attempt if there are no free SDCCH.Formula:

sum(sdcch_busy_att) 100 * (1 - --------------------) % sum(sdcch_seiz_att) Counters from table(s):




641/712

p_nbsc_traffic

SDCCH access probability, (csf_1a)

Use: Gives the probability to access SDCCH. Applicable for area and BTS level. A low value means high traffic on SDCCH and lack of SDCCH resources, that is SDCCH blocking.

Experiences on use: The value should be kept very close to 100% in a network with traffic. -After S7 the Dynamic SDCCH Allocation can be used to prevent SDCCH congestion. -Before S7 the FACCH call setup could already be used to improve this KPI.

Known problems: 1) The momentary SDCCH blocking phenomenon is met in some networks and if the traffic is low, this KPI can show lower values that, however, do not mean bad access to the network perceived by the user.

2) SDCCH_busy_att triggered also in the case of HO attempt if there are no free SDCCH. 3) The formula does not separate calls from LU and other use. In some cases this would be needed (e.g. a train crossing LA boundary creates a high LU peak).

Formula: 100 - blck_5a = sum(sdcch_busy_att - tch_seiz_due_sdcch_con) 100 - (100 * -------------------------------------------) % sum(sdcch_seiz_att) Counters from table(s): p_nbsc_traffic




642/712

SDCCH success ratio, (csf_2a)

Experiences on use: The best values seen are around 98%. Known problems: 1) The formula does not separate the SDCCH call seizures from other seizures (such as LU). The failure rate in the case of a call or

LU can greatly differ from one another, wherefore you cannot use this formula for SDCCH call success ratio calculation. 2) It is not exactly known how big a portion of sum(sdcch_abis_fail_call + sdcch_abis_fail_old) really are setup failures. Formula: 100 - non abis SDCCH drop ratio = sum(sdcch_radio_fail + sdcch_rf_old_ho + sdcch_user_act + sdcch_bcsu_reset + sdcch_netw_act + sdcch_bts_fail + sdcch_lapd_fail + sdcch_a_if_fail_call + sdcch_a_if_fail_old) 100 - 100 * ------------------------------------------------------------ % sum(sdcch_assign + sdcch_ho_seiz) - sum(sdcch_abis_fail_call + sdcch_abis_fail_old) ; phantoms Counters from table(s): p_nbsc_traffic

SDCCH success ratio, (csf_2b)

Use: Indicates how well the SDCCH phase is completed. sdcch_abis_fail_call is not included in the numerator because they are mainly phantoms, neither are included in the denominator.




643/712

Experiences on use: The best values seen are around 98 %. Known problems: 1) The formula does not separate the SDCCH call seizures from other seizures (such as LU and SS). The failure rate in the case of a

call or e.g. LU can greatly differ from one another, wherefore you cannot use this formula for SDCCH call success ratio calculation. 2) This formula ignores all sdcch_abis_fail_call. However, not all of these are ghosts or double access. See csf_2c for a more accurate

formula. Formula: 100 - non abis SDCCH drop ratio = sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act + a.sdcch_bcsu_reset + a.sdcch_netw_act + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old + a.sdcch_abis_fail_old) 100 - 100 * ----------------------------------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) ;(calls, SS,SMS,emerg. calls,LUs,IMSI detach, succ. estab.) + sum(c.msc_i_sdcch + c.bsc_i_sdcch); ;(successful incoming SDCCH-SDCCH HOs,intracell excl.) Counters from table(s): a = p_nbsc_traffic




644/712

b = p_nbsc_res_access c = p_nbsc_ho

SDCCH success ratio, (csf_2c)

Use: Indicates how well the SDCCH phase is completed. Experiences on use: The best values seen are around 98 %.Known problems: The formula does not separate the SDCCH call seizures from other

seizures (such as LU and SS). The failure rate in the case of a call or e.g. LU can greatly differ from one another, wherefore you cannot use this formula for SDCCH call success ratio calculation.

Formula: 100 - SDCCH drop ratio = sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act + a.sdcch_bcsu_reset + a.sdcch_netw_act + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old + a.sdcch_abis_fail_old + (a.sdcch_abis_fail_call - C)) 100 - 100 * -------------------------------------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch




645/712

+ b.sdcch_emerg_call) ;(calls, SS,SMS,emerg. calls,LUs,IMSI detach, succ. estab.) + sum(c.msc_i_sdcch + c.bsc_i_sdcch); ;(successful incoming SDCCH-SDCCH HOs,intracell excl.) C = part of sdcch_abis_fail_call that occurs before establishment indication = a.sdcch_assign - (b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

SDCCH success ratio, (csf_2d)



Formula: 100 - SDCCH drop ratio = sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act




646/712

+ a.sdcch_bcsu_reset + a.sdcch_netw_act + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old + a.sdcch_abis_fail_old + (a.sdcch_abis_fail_call - C)) 100 - 100 * -------------------------------------------------- % sum(a.sdcch_assign) + sum(c.msc_i_sdcch + c.bsc_i_sdcch) ;(successful inc. intercell SDCCH-SDCCH HOs) C = part of sdcch_abis_fail_call that occurs before establishment indication = a.sdcch_assign - (b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

SDCCH success ratio, area (csf_2e)






647/712

Formula: 100 - SDCCH drop ratio = sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act + a.sdcch_bcsu_reset + a.sdcch_netw_act + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old + a.sdcch_abis_fail_old +(a.sdcch_abis_fail_call - C)) 100 - 100 * ----------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call C = part of sdcch_abis_fail_call that occurs before establishment indication = a.sdcch_assign - (b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho




648/712

SDCCH success ratio, area, (csf_2f)

Use: Area level Experiences on use: The best values seen are around 95%. Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time which, again, may depend on the use of

DR or queuing features. Other reasons can be authentication fails, identity check fails and MOC calls having wrong dialling, for example.

2) The number of supplementary service requests such as call forwarding is not available as a BTS level counter. 3) This formula does not count correctly the situation when the first call of 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 net

incoming amount of SDCCH handovers ends up in a successful case to 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

incoming amount of SDCCH-TCH (DR) handovers ends up in a successful case to TCH seizures but they are not seen in the nominator.

6) Problem found 3/99: The ratio shows over 100% values. Reason: The SMS counters (succ_sdcch_sms_est and unsucc_sdcch_sms_est) are triggered without triggering of SDCCH counters (succ_seiz_term, succ_seiz_orig) if in air interface interference causes repetition of the first message for SMS (SABM for SAPI3). Correction delivered to S7 and S8 in 1999 but afterwards still some cases reported. Investigations pending.

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




649/712

100 * ------------------------------------------------------- % (sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call) - call re-establ. (unknown factor) =100 * ------------------------------------------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_emerg_call + b.sdcch_call_re_est) ;(calls,sms, ss reqs) - sum(b.succ_sdcch_sms_est+ b.unsucc_sdcch_sms_est) ;(sms attempts) - sum(a.tch_call_req-a.tch_norm_seiz-bsc_o_sdcch_tch-msc_o_sdcch_tch) ;(blocked calls & Aif pool circuit type mismatch) - supplem.serv.requests (unknown factor ) - call clears before TCH (unknown factor) + net impact of SDCCH-SDCCH HO on area (unknown factor) + net incoming DR to area (unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

Note:

Includes also A interface blocking. Works for call re-establishment if the drop is on TCH.. If the drop is on SDCCH and the call is re-established, then there is double count in the divisor.

SDCCH success ratio, BTS, S6 (csf_2g)

Use: BTS level.




650/712

Experiences on use: Includes A interface blocking! Known problems: - As consistency is a critical property in measurements, the binding of three tables can lead into problems. See problems 1-3 from

csf_2d. - Unknown factors in the denominator make the values seem pessimistic (See problems 1-3 from csf_2d.).

Formula: 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_traffic b = p_nbsc_res_access c = p_nbsc_ho




651/712

Note:

Includes also A interface blocking.

If call re-establishment occurs already on SDCCH, the formula is not correct but if re-established on TCH, it is correct.

SDCCH success ratio, area, S8-9 (csf_2h)

Use: Area level. For T12/S9 see csf_2j. Experiences on use: The best values seen are around 95%. Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time which, again, may depend on the use of


2) The number of supplementary service requests such as call forwarding is not available as a BTS level counter. 3) This formula does not count correctly the situation when the first call of 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 net

incoming amount of SDCCH handovers ends up in a successful case to 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

incoming amount of SDCCH-TCH (DR) handovers ends up in a successful case to TCH seizures but they are not seen in the nominator.




652/712

6) Problem found 3/99: The ratio shows over 100% values. Reason: The SMS counters (succ_sdcch_sms_est and unsucc_sdcch_sms_est) are triggered without triggering of SDCCH counters (succ_seiz_term, succ_seiz_orig) if in air interface interference causes repetition of the first message for SMS (SABM for SAPI3). Correction pending (11.6.99)

Formula: (succ tch seiz) - (call re-establ.) 100 * ------------------------------------------------------- % (sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call) - call re-establ. (unknown factor) = 100 * ------------------------------------------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_emerg_call + b.sdcch_call_re_est) ;(calls,sms, ss reqs) - sum(b.succ_sdcch_sms_est + b.unsucc_sdcch_sms_est) ;(sms attempts) - (c.bsc_o_sdcch_tch - c.msc_o_sdcch_tch - c.cell_sdcch_tch + a.tch_succ_seiz_for_dir_acc ) - supplem.serv.requests (unknown factor ) - call clears before TCH (unknown factor) + net impact of SDCCH-SDCCH HO on area(unknown factor) + net incoming DR to area (unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho




653/712

Note:


SDCCH success ratio, BTS, (csf_2i)

Use: BTS level. Experiences on use: Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. See problems 1-3 from

csf_2d. Unknown factors in the denominator make the values seem pessimistic (See problems 1-3 from csf_2d.). Formula: 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(c.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc) ; direct access related correction - sum(a.tch_call_req - a.tch_norm_seiz);(DR and air itf blocking) - supplem.serv. requests ;(unknown factor) - call clears before TCH ;(unknown factor) - supplem.serv. requests ;(unknown factor)




654/712


Note:



SDCCH success ratio, area, S9 (csf_2j)

Use: Area level Experiences on use: The best values seen are around 95%. Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time which, again, may depend on the use of


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

3) For the BTS area there is no way knowing how much SDCCH-SDCCH handovers take place across the area border. The net incoming amount of SDCCH handovers ends up in a successful case to TCH seizures but they are not seen in the nominator.




655/712

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

5) Problem found 3/99: The ratio shows over 100% values. Reason: The SMS counters (succ_sdcch_sms_est and unsucc_sdcch_sms_est) are triggered without triggering of SDCCH counters (succ_seiz_term, succ_seiz_orig) if in air interface interference causes repetition of the first message for SMS (SABM for SAPI3). Correction available: For S8 CD the CD 1.0 is needed. For S7 the CD 4.00 is needed. 6) Problem with values over 100%: It is possible that when MS is on SDCCH with SMS and a call is started, this happens on the same SDCCH. This may result in the situation that only SMS counters are triggered. The problem can be corrected in S10.5 where a new counter is introduced. 7) LCS requests that are made on SDCCH (MS is idle) increment the denominator but not the numerator, thus making the ratio seem too pessimistic. A new counter is needed to fix the formula for this.


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) - (c.bsc_o_sdcch_tch - c.msc_o_sdcch_tch - c.cell_sdcch_tch + a.tch_succ_seiz_for_dir_acc )




656/712

- sum(b.succ_seiz_supplem_serv) ;(supplementary service requests, S9) - call clears before TCH (unknown factor) + net impact of SDCCH-SDCCH HO on area(unknown factor) + net incoming DR to area (unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

Note:

Includes also A interface blocking. Works for call re-establishment if the drop is on TCH. If the drop is on SDCCH and the call is re-established, then there is double count in the divisor.

SDCCH success ratio, BTS, S9 (csf_2k)

Use: BTS level. Experiences on use: Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. See problems from csf_2j. Formula: 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)




657/712

+ 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(c.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc) ; direct access related correction - sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking) - sum(b.succ_seiz_supplem_serv) ;supplem.serv. requests (S9) - call clears before TCH ;(unknown factor) - supplem.serv. requests ;(unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

Note:



SDCCH success ratio, BTS (csf_2l)

Use: Indicates how well the SDCCH phase is completed. Experiences on use: Known problems: The formula does not separate the SDCCH call seizures from other seizures (such as LU and SS). The failure

rate in the case of a call or LU, for example, can greatly differ from one another, wherefore you cannot use this formula for SDCCH call success ratio calculation.

Formula:




658/712

100 - SDCCH drop ratio = sum(a.sdcch_radio_fail + a.sdcch_rf_old_ho + a.sdcch_user_act + a.sdcch_bcsu_reset + a.sdcch_netw_act + a.sdcch_bts_fail + a.sdcch_lapd_fail + a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old + a.sdcch_abis_fail_old + (a.sdcch_abis_fail_call - C)) 100 - 100 * --------------- ------------------------------------------------------- % sum(b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) /* successful incoming intercell SDCCH-SDCCH HOs */ + sum(c.msc_i_sdcch + c.bsc_i_sdcch) C= part of sdcch_abis_fail_call that occurs before establishment indication = a.sdcch_assign - (b.succ_seiz_term + b.succ_seiz_orig + b.sdcch_call_re_est + b.sdcch_loc_upd + b.imsi_detach_sdcch + b.sdcch_emerg_call) Counters from table(s): a = p_nbsc_traffic




659/712

b = p_nbsc_res_access c = p_nbsc_ho

SDCCH success ratio, area, S10.5 (csf_2m)

Use: Area level. Experiences on use: The best values seen are around 95%. Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time which, again, may depend on the use of




4) For the BTS area there is no way knowing how much SDCCH-TCH (DR) handovers take place across the area border. The net incoming amount of SDCCH-TCH (DR) handovers ends up in a successful case to TCH seizures but they are not seen in the nominator. 5) LCS requests that are made on SDCCH (MS is idle) increment the denominator but not the numerator, thus making the ratio seem too pessimistic. A new counter is needed to fix the formula for this.





660/712

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 + b.call_assign_after_sms) ;(calls,sms, ss reqs) - sum(b.succ_sdcch_sms_est + b.unsucc_sdcch_sms_est);(sms attempts) - sum(c.bsc_o_sdcch_tch - c.msc_o_sdcch_tch - c.cell_sdcch_tch) ; (DR) + sum(a.tch_succ_seiz_for_dir_acc ) ; direct access - sum(b.succ_seiz_supplem_serv) ;(supplementary service requests, S9) - call clears before TCH (unknown factor) + net impact of SDCCH-SDCCH HO on area(unknown factor) + net incoming DR to area (unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

Note:


SDCCH success ratio, BTS, S10.5 (csf_2n)

Use: BTS level. Experiences on use: Includes A interface blocking!




661/712

Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time that, again, may depend on the use of



3) It is not known how much of SDCCH-SDCCH handovers are calls. 4) LCS requests that are made on SDCCH (MS is idle) increment the denominator but not the numerator, thus making the ratio seem

too pessimistic. A new counter is needed to fix the formula for this. Formula: 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 + b.call_assign_after_sms) ;(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(c.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc); direct access related correction - sum(a.tch_call_req - a.tch_norm_seiz);(DR and air itf blocking) - sum(b.succ_seiz_supplem_serv) ;supplem.serv. requests (S9) - call clears before TCH ;(unknown factor) - supplem.serv. requests ;(unknown factor)




662/712


Note:



SDCCH success ratio, area, S10.5 (csf_2o)

Use: Area level. Experiences on use: The best values seen are around 95%. Includes A interface blocking! Known problems: As consistency is a critical property in measurements, the binding of three tables can lead into problems. Unknown factors in the divisor make the values seem pessimistic. 1) The calls cleared before TCH can vary between networks depending on the call setup time which, again, may depend on the use of




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




663/712

5) LCS requests that are made on SDCCH (MS is idle) increment the denominator but not the numerator, thus making the ratio seem too pessimistic. A new counter is needed to fix the formula for this.


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 + b.call_assign_after_sms) ;(calls,sms, ss reqs) - sum(b.succ_sdcch_sms_est + b.unsucc_sdcch_sms_est);(sms attempts) - sum(c.bsc_o_sdcch_tch + c.msc_o_sdcch_tch) ; (DR) + sum(a.tch_succ_seiz_for_dir_acc ) ; direct access - sum(b.succ_seiz_supplem_serv) ;(supplementary service requests, S9) - call clears before TCH (unknown factor) + net impact of SDCCH-SDCCH HO on area(unknown factor) + net incoming DR to area (unknown factor) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho




664/712

Note:


TCH access probability without DR, (csf_3a)

Use: This PI indicates what would be the blocking if DR were not used. When compared to csf_3, you can see, assuming that DR is in use, the improvement that the DR has caused.

Formula: 100 - blck_8 = sum(tch_call_req - tch_norm_seiz) 100 - 100 * -------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic

TCH access probability without DR and Q, (csf_3b)

Use: This PI indicates what would be the blocking if DR and queuing were not used. When compared to csf_3 you can see, assuming that DR is in use, the improvement that the DR has caused.




665/712

Known problems: See XX1. Formula: sum(tch_call_req - tch_norm_seiz) + sum(tch_qd_call_att - XX1 - unsrv_qd_call_att) ; calls succeeded via queuing 100 - 100 * ------------------------------------------------- % sum(tch_call_req) Counters from table(s): p_nbsc_traffic XX1 = attempts taken from queue to DR (unknown)

TCH access probability without Q, (csf_3c)

Use: This PI indicates what would be the blocking if queuing were not used (but DR is used). Formula: 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) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho




666/712

TCH access probability, real, (csf_3d)

Use: this KPI is affected by the congestion on TCH. Formula: 100 - blck_8b = sum(a.tch_call_req - a.tch_norm_seiz) - 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_traffic b = p_nbsc_ho

TCH access probability without DR, S7 (csf_3e)

Use: This PI indicates what would be the blocking if DR were not used. DRs in this PI are represented by ‘TCH assignment to super reuse TRX in IUO (S6 feature)’ and normal DR.

sum(a.tch_call_req - a.tch_norm_seiz) - sum(a.tch_req_dir_acc_rej_due_lack) ; ref.1 100 - 100 * ------------------------------------------------- % sum(a.tch_call_req) - sum(a.tch_req_dir_acc_rej_due_lack) ; ref.1 Counters from table(s): p_nbsc_traffic




667/712

Ref.1. Needed as a compensation for S7 feature ‘Direct access to super reuse TRX’ that causes double triggering of the tch_call_req in the case of congestion in super reuse TRX. TCH access probability without DR S7, (csf_3i)

Use: This PI indicates what would be the TCH blocking if DR were not used. When compared to csf_3, you can see, assuming that DR is in use, the improvement that the DR has caused.

Does not include the congestion of A interface circuit pool. Formula: sum(a.tch_call_req - a.tch_norm_seiz) - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) 100 - 100 * ------------------------------------- % sum(a.tch_call_req) - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho




668/712

TCH access probability without DR and Q (csf_3j)

Use: This PI indicates what would be the THC blocking if DR and queuing were not used. When compared to csf_3, you can see, assuming that DR is in use, the improvement that the DR has caused. Does not include the congestion of A interface circuit pool.

Known problems: See XX1, . Formula: sum(tch_call_req - tch_norm_seiz) + sum(tch_qd_call_att - XX1-unsrv_qd_call_att) ;succ. calls via queuing - sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections 100 - 100 * --------------------------------------------------------- % sum(tch_call_req) - sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections Counters from table(s): p_nbsc_traffic XX1 = attempts taken from queue to DR (unknown)

TCH access probability, real, S6 (csf_3k)

Use: This KPI is affected by the blocking on TCH. Formula: 100 - blck_8c = sum(a.tch_call_req-a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch); DR calls - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type))




669/712

100 - 100 * ----------------------------------------------------------- % sum(a.tch_call_req) - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho

TCH access probability, real, S7 (csf_3l)

Use: See blck_8d.

Formula: 100 - blck_8d = sum(a.tch_call_req-a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch); DR calls + sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) 100 - 100 * ----------------------------------------------------------- % sum(a.tch_call_req) - sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion , -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type))




670/712


Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with the cell_sdcch_tch . TCH access probability without DR and Q (csf_3m)

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

Known problems: Inaccurate when the feature 'TCH assignment to super-reuse TRX in IUO' is applied. In this case tch_call_req and removal_from_que_due_to_dr are triggered multiple times if the target cell is congested and queuing is started but the call is removed to normal DR.

Formula: sum(tch_call_req - tch_norm_seiz) + sum(tch_qd_call_att - removal_from_que_due_to_dr - unsrv_qd_call_att) ;succ. calls via queuing - sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections 100 - 100 * --------------------------------------------------------- % sum(tch_call_req) - sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections Counters from table(s): p_nbsc_traffic




671/712

TCH access probability, real, S10.5 (csf_3n)

Use: See blck_8e. to fix negative results when HR is in use; using SPARE057046 which updates only in call setup phase.

Formula: 100 - blck_8e = sum(a.tch_call_req-a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch); DR calls + sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 - sum(c.SPARE057046 ; Aif type mismatch or congestion -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) 100 - 100 * ----------------------------------------------------------- % sum(a.tch_call_req) - sum(c.SPARE057046 ; Aif type mismatch or congestion , -(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)) Counters from table(s): a = p_nbsc_traffic b = p_nbsc_ho c = p_nbsc_service

Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with the cell_sdcch_tch .




672/712

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

Use: On the area level. The impact of call re-establishment is not yet taken into account. Known problems: See dcr_3g.

Formula: sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 – 100 * ------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho




673/712

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

Use: On the area level. Known problems: 1) See dcr_3g 2) It is assumed that call re-establishments happen on TCH. In fact they may happen also on SDCCH. 3) The counters used to compensate re-establishments are the ones that indicate re-establishment attempts, not the successful re-

establishments. In S7/T11 re-establishments can be considered accurately (see csf_4v). 4) On cell level it can happen that the call is re-established in a different cell than where it was dropped, resulting in inaccuracy.

Formula: 100 - dcr_3f =

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ. 100 – 100 * ------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;calls started directly in the cell + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch




674/712

+ c.cell_sdcch_tch) ;DR calls + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls - sum(b.sdcch_call_re_est+b.tch_call_re_est) ;call re-establ. Counters from table(s): a = p_nbsc_traffic b = p_nbsc_res_access c = p_nbsc_ho

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

Use: On the BTS level. Known problems: See dcr_4c. Formula: 100 - dcr_4b = sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 – 100 * -------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls)




675/712

+ sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls + sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH HO in) Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

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

Use: On the BTS level. Known problems: See dcr_3d. sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ. 100 – 100 * -------------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls)




676/712

+ sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in) - 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

TCH success ratio, area, after call re-establishment, S6 (csf_4s)

Use: On the area level. Known problems: See dcr_3g.

Formula: 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




677/712

+ a.tch_netw_act + a.tch_act_fail_call) - sum(b.tch_re_est_assign) ;call re-establishments 100 – 100 * ------------------------------------------------------------------ % sum(a.tch_norm_seiz) ;calls started directly in the cell + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;DR calls + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls - sum(b.tch_re_est_assign) ;call re-establishments Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service c = p_nbsc_ho

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

Use: On the BTS level. Known problems: See dcr_3d.

Formula: 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




678/712

+ a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.tch_re_est_assign) ;call re-establishments 100 – 100 * ----------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell sdcch_tch) ;(DR calls) + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in) - sum(b.tch_re_est_assign) ;call re-establ. Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service c = p_nbsc_ho

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

Use: See dcr_3i. Formula: 100 - dcr_3i = sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call+ + a.tch_abis_fail_old + a.tch_a_if_fail_call




679/712

+ a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 – 100 * ---------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch. TCH success ratio, area, after call re-establishment, S7 (csf_4v)

Use: On the area level. See dcr_3j. Formula: 100 - dcr_3j=

sum(a.tch_radio_fail + a.tch_rf_old_ho




680/712

+ a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.tch_re_est_assign) ;call re-establishments 100 – 100 * ----------------------------------------------------------- % sum(a.tch_norm_seiz) ;calls started directly in the cell + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;DR calls - sum(a.tch_succ_seiz_for_dir_acc) ;ref.1 + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls - sum(b.tch_re_est_assign) ;call re-establishments Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service

c = p_nbsc_ho Ref.1. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch . TCH success ratio, BTS, after call re-establishment, (csf_4x)

Use: On the BTS level.




681/712

Known problems: See dcr_3d. Formula: sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) - sum(b.tch_re_est_assign) ;call re-establishments 100 – 100 * ---------------------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in) - sum(b.tch_re_est_assign) ;call re-establishments Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service c = p_nbsc_ho

Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.




682/712

TCH success ratio, BTS, before call re-establishment, (csf_4y)

Use: On the BTS level. Known problems: See dcr_3d. Formula: 100 - dcr_4e= sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call + a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail + a.tch_tr_fail_old + a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act + a.tch_act_fail_call) 100 – 100 * --------------------------------------------------- % sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls + sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in) Counters from table(s):




683/712

a = p_nbsc_traffic c = p_nbsc_ho

Ref.2. Compensation needed since in the case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch . Congestion related SDCCH access probability, S7, (csf_11)

Use: On the area level. Known problems: Formula: sum(served_sdcch_req + served_facch_req) 100 * --------------------------------------------- % sum(sdcch_req) Counters from table(s): p_nbsc_service

Activation related SDCCH access probability, S7, (csf_12)

Use: On the area level. Known problems: Formula: sum(sdcch_assign + t3101_expired) 100 * --------------------------------------------- % sum(served_sdcch_req)




684/712


SDCCH call success probability, S7, (csf_13)

Use: On the area level. Known problems: The denominator misses those calls that are started after SMS. A new counter is available in S10.5. Formula: sum(a.tch_call_req) 100 * ---------------------------------- % sum(a.sdcch_new_call_assign + b.sdcch_ho_call_assign + a.sdcch_re_est_assign - a.sdcch_re_est_release - a.sdcch_sms_assign - a.sdcch_ho_release) Counters from table(s): p_nbsc_service, a = source, b = target

SDCCH call success probability, S10.5, (csf_13a)

Description: Ratio of calls successfully transferred to TCH from SDCCH. Use: On the area level. Indicates the probability of a call being successfully transferred from SDCCH to TCH. Known problems: Formula: sum(a.tch_call_req)




685/712

100 * ------------------------------- % sum(c.call_assign_after_sms + a.sdcch_new_call_assign + b.sdcch_ho_call_assign + a.sdcch_re_est_assign - a.sdcch_re_est_release - a.sdcch_sms_assign - a.sdcch_ho_release) Counters from table(s): p_nbsc_service, a = source, b = target c= p_nbsc_res_access

Congestion related TCH access probability, S7, (csf_14)

Use: On the area level. Known problems: Formula: sum(b.served_dr_req + a.served_tch_call_req) 100 * ----------------------------------------------- % sum(a.tch_call_req) Counters from table(s): p_nbsc_service, a = source, b = target

Activation related TCH access probability, S7, (csf_15)

Use: On the area level. Known problems: Formula:




686/712

sum(a.tch_new_call_assign) 100 * ------------------------------------------------------------------ % sum( b.served_dr_req + a.served_tch_call_req + a.served_facch_req) Counters from table(s): p_nbsc_service, a = source, b = target

TCH call success probability, S7, (csf_16a)

Use: On the area level. Known problems: Formula: sum(tch_norm_release) 100 * ------------------------- % sum( tch_new_call_assign) Counters from table(s): p_nbsc_service

TCH call success probability, S7, (csf_16b)

Use: On the area level. Known problems: Formula: sum(tch_norm_release + tch_ho_release + tch_re_est_release)




687/712

100 * --------------------------------------------------------------- % sum(tch_new_call_assign + b.tch_ho_assign + tch_re_est_assign)


TCH call success probability, after TCH assignment, with RE, area level, S7 (csf_16c)

Origin: Complement to dcr_8a. Use: This formula is developed to better match with the formulas of other vendors Known problems: Formula: 100-dcr_8a = Drops after TCH assignment 100 * ------------------------------ % = TCH assignments for new calls sum(tch_new_call_assign + tch_ho_assign - tch_norm_release - tch_ho_release - tch_re_est_assign) 100 – 100 * ------------------------------------------- % sum(tch_new_call_assign - tch_re_est_assign) Counters from table(s): p_nbsc_service




688/712

Next free (csf_17)

Configuration (cnf)

Reuse pattern, S1 (cnf_1)

Experiences on use: 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 Nokia NetAct only for the latest moment (no history). Formula: number of used frequencies -------------------------- average TRXs per cell

The used frequency means that the TRX and its parents (BTS and BCF) are unlocked. TRX Type, S1 (cnf_2)

Formula: Decode(Avg(trx_type),0,’normal’,1,’extended’,’mixed’)




689/712

Next free (cnf_2)

HSCSD (hsd)

Throughput ratio, S7HS (hsd_15)

Use: How many % of the offered data is put through. Known problems: Formula: Sum(96*(ONE_TCH_SEIZ_TIME_9600 + TWO_TCH_SEIZ_TIME_9600 + THREE_TCH_SEIZ_TIME_9600 + FOUR_TCH_SEIZ_TIME_9600) + 144*(ONE_TCH_SEIZ_TIME_14400 + TWO_TCH_SEIZ_TIME_14400 + THREE_TCH_SEIZ_TIME_14400 + FOUR_TCH_SEIZ_TIME_14400)) 100 * ------------------------------------------------------------------------ % Sum(96*(ONE_TCH_REQ_TIME_9600 + TWO_TCH_REQ_TIME_9600 + THREE_TCH_REQ_TIME_9600 + FOUR_TCH_REQ_TIME_9600) +144*(ONE_TCH_REQ_TIME_14400 + TWO_TCH_REQ_TIME_14400 + THREE_TCH_REQ_TIME_14400 + FOUR_TCH_REQ_TIME_14400)) Counters from table(s): p_nbsc_high_speed_data

9600 bps traffic share, S7HS (hsd_49)

Use: Gives the share of 9600 bps traffic out of all traffic.




690/712

Known problems: Formula: Sum(ONE_TCH_SEIZ_TIME_9600 + TWO_TCH_SEIZ_TIME_9600 + THREE_TCH_SEIZ_TIME_9600 + FOUR_TCH_SEIZ_TIME_9600) 100 * ---------------------------------------------------------- % Sum(ONE_TCH_SEIZ_TIME_9600 + TWO_TCH_SEIZ_TIME_9600 + THREE_TCH_SEIZ_TIME_9600 + FOUR_TCH_SEIZ_TIME_9600 + ONE_TCH_SEIZ_TIME_14400 + TWO_TCH_SEIZ_TIME_14400 + THREE_TCH_SEIZ_TIME_14400 + FOUR_TCH_SEIZ_TIME_14400) Counters from table(s): p_nbsc_high_speed_data

14400 bps traffic share, S7HS (hsd_50)

Use: Gives the share of 14400 bps traffic out of all traffic. Known problems: Formula: Sum(ONE_TCH_SEIZ_TIME_14400 + TWO_TCH_SEIZ_TIME_14400 + THREE_TCH_SEIZ_TIME_14400 + FOUR_TCH_SEIZ_TIME_14400) 100 * ---------------------------------------------------------- % Sum(ONE_TCH_SEIZ_TIME_9600 + TWO_TCH_SEIZ_TIME_9600 + THREE_TCH_SEIZ_TIME_9600 + FOUR_TCH_SEIZ_TIME_9600 + ONE_TCH_SEIZ_TIME_14400 + TWO_TCH_SEIZ_TIME_14400 + THREE_TCH_SEIZ_TIME_14400 + FOUR_TCH_SEIZ_TIME_14400) Counters from table(s):




691/712

p_nbsc_high_speed_data

Next free (hsd_51)

Adaptive multirate (amr)

Codec set upgrade attempts, S10 (amr_1)

Use: Known problems: Formula: Sum(SUCC_AMR_CODEC_SET_UPGR + UNSUCC_AMR_CODEC_SET_UPGR) Counters from table(s): p_nbsc_traffic

Codec set downgrade attempts, S10 (amr_2)

Use: Known problems: Formula: Sum(SUCC_AMR_CODEC_SET_DOWNGR + UNSUCC_AMR_CODEC_SET_DOWNGR) Counters from table(s): p_nbsc_traffic




692/712

Codec set upgrade failure ratio, S10 (amr_3)

Use: Known problems: Formula: Sum(UNSUCC_AMR_CODEC_SET_UPGR) 100 * -------------------------------------------------------- % Sum(SUCC_AMR_CODEC_SET_UPGR + UNSUCC_AMR_CODEC_SET_UPGR) Counters from table(s): p_nbsc_traffic

Codec set downgrade failure ratio, S10 (amr_4)

Use: Known problems: Formula: Sum(UNSUCC_AMR_CODEC_SET_DOWNGR) 100 * ----------------------------------------------------------- % Sum(SUCC_AMR_CODEC_SET_DOWNGR + UNSUCC_AMR_CODEC_SET_DOWNGR) Counters from table(s): p_nbsc_traffic




693/712

Next free (amr_5)

Position based servic es (pbs)

Failure ratio of location calculations for external LCS clients, S10 (pbs_1)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_BY_LCS_REQ) 100 - 100 * ------------------------------------------------------- % Sum(NBR_OF_LOC_REQ_FROM_LCS + SUCC_LOC_CALC_BY_LCS_REQ) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for external LCS clients, S10 (pbs_1a)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_BY_LCS_REQ) 100 - 100 * ------------------------------------ % Sum(NBR_OF_LOC_REQ_FROM_LCS)




694/712

Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for emergency calls, S10 (pbs_2)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_EMERGENCY) 100 - 100 * ------------------------------------------------------- % Sum(NBR_OF_LOC_REQ_EMERGENCY + SUCC_LOC_CALC_EMERGENCY) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for emergency calls, S10 (pbs_2a)

Use: Known problems: Incorrect denominator values cause problems. Pronto ID 2424316. Formula: Sum(SUCC_LOC_CALC_EMERGENCY) 100 - 100 * -------------------------------- % Sum(NBR_OF_LOC_REQ_EMERGENCY) Counters from table(s): p_nbsc_pbs




695/712

Failure ratio of E-OTD location calculations, S10 (pbs_3)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_E_OTD) 100 - 100 * ---------------------------------------------------- % Sum(NBR_OF_E_OTD_CALCULATIONS + SUCC_LOC_CALC_E_OTD) Counters from table(s): p_nbsc_pbs

Failure ratio of E-OTD location calculations, S10 (pbs_3a)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_E_OTD) 100 - 100 * ------------------------------- % Sum(NBR_OF_E_OTD_CALCULATIONS) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for MS, S10 (pbs_4)

Use:




696/712

Known problems: Formula: Sum(SUCC_LOC_CALC_BY_MS_REQ) 100 - 100 * ---------------------------------------------------- % Sum(NBR_OF_LOC_REQ_FROM_MS + SUCC_LOC_CALC_BY_MS_REQ) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for MS, S10 (pbs_4a)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_BY_MS_REQ) 100 - 100 * --------------------------------- % Sum(NBR_OF_LOC_REQ_FROM_MS) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for operator, S10 (pbs_5)





697/712

Sum(SUCC_LOC_CALC_BY_OPER_REQ) 100 - 100 * --------------------------------------------------------- % Sum(NBR_OF_LOC_REQ_FROM_OPER + SUCC_LOC_CALC_BY_OPER_REQ) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations for operator, S10 (pbs_5a)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_BY_OPER_REQ) 100 - 100 * -------------------------------- % Sum(NBR_OF_LOC_REQ_FROM_OPER) Counters from table(s): p_nbsc_pbs

Failure ratio of location calculations using standalone GPS, S10 (pbs_6)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_STAND_ALONE_GPS) 100 - 100 * ----------------------------------------------------------------- % Sum(NBR_LOC_CALC_STAND_ALONE_GPS + SUCC_LOC_CALC_STAND_ALONE_GPS) Counters from table(s):




698/712

p_nbsc_traffic

Failure ratio of location calculations using standalone GPS, S10 (pbs_6a)

Use: Known problems: Formula: Sum(SUCC_LOC_CALC_STAND_ALONE_GPS) 100 - 100 * -------------------------------------% Sum(NBR_LOC_CALC_STAND_ALONE_GPS) Counters from table(s): p_nbsc_traffic

SDCCH seizures due to PBS, S10 (pbs_7)

Use: Known problems: Formula: Sum(NBR_OF_LOC_REQ_FROM_LCS + FEATURE_NOT_SUPPORTED) Counters from table(s): p_nbsc_pbs




699/712

Unspecified LCS requests, S10 (pbs_8)

Use: Indicates the requests for which the client type is unspecified. Known problems: Formula: Sum(NBR_OF_LOC_REQ_FROM_LCS - NBR_OF_LOC_REQ_EMERGENCY - NBR_OF_LOC_REQ_FROM_MS - NBR_OF_LOC_REQ_FROM_OPER) Counters from table(s): p_nbsc_pbs

Next free (pbs_99)

DFCA

Average BSC - BSC delay, S11 (dfca_1)

Description: Average delay between Radio Resource Managers of the BSCs. Use: Indicates the transmission of BSC (BTS) measurements to neighbouring BSCs. Experiences on use: Known problems: Open questions: Formula:




700/712

avg(BSC_BSC_DELAY / BSC_BSC_DENOMINATOR1) Counters from table(s): p_nbsc_bsc_bsc

Unit:

Total DFCA assignment requests, S11 (dfca_2)

Description: Total DFCA assignment requests. Use: Indicates the total number of DFCA requests. Experiences on use: Known problems: Open questions: Formula: Sum(SUCC_DFCA_ASS + SOFT_BLOCKED_DFCA_ASS_DUETO_CI + SOFT_BLOCKED_DFCA_ASS_DUETO_CN) Counters from table(s): p_nbsc_dfca

DFCA assignment success ratio, S11 (dfca_3)

Description: Success ratio of DFCA assignments.




701/712

Use: Indicates the ratio of successful DFCA assignments to the DFCA assignment requests. Note that soft -blocked DFCA assignment requests are put to normal channel search procedure.

Experiences on use: Known problems: Open questions: Formula: Sum(SUCC_DFCA_ASS) ; total successful assignments 100 * ----------------------- ( dfca_2 ) ; total DFCA assignment requests Counters from table(s): p_nbsc_dfca Unit: %

Most optimal DFCA assignment success ratio, S11 (dfca_4)

Description: Success ratio of most optimal DFCA assignments. Use: Indicates the ratio of most optimal DFCA assignments to the DFCA assignment requests. Note that

1. Due to high MCMU load it may not be possible to continue finding the most optimal channel, and the best possible channel is assigned. 2. Soft-blocked DFCA assignment requests are put to normal channel search procedure.

Experiences on use: Known problems: Open questions: Formula:




702/712

Sum(SUCC_DFCA_ASS - SUCC_DFCA_ASS_HIGH_LOAD) ; most optimal assignments 100 * --------------------------------------------- ( dfca_2 ) ; total DFCA assignments Counters from table(s): p_nbsc_dfca Unit: %

Total soft-blocked DFCA assignments, S11 (dfca_5)

Description: Soft-blocked DFCA assignments Use: Indicates the DFCA assignment requests that could not be served through the DFCA channel assignment procedure and put to the

normal channel assignment procedure. Experiences on use: Known problems: Open questions: Formula: Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CI + SOFT_BLOCKED_DFCA_ASS_DUETO_CN) Counters from table(s): p_nbsc_dfca

DFCA soft-blocking ratio, S11 (dfca_6)

Description: Soft-blocking ratio of DFCA assignments. Experiences on use:




703/712

Known problems: Open questions: Formula: ( dfca_5 ) ; total soft-blocked DFCA assignment requests 100 * ----------- ( dfca_2 ) ; total DFCA assignment requests Counters from table(s): p_nbsc_dfca Unit: %

DFCA soft-blocking ratio for C/I reason, S11 (dfca_7)

Description: Soft-blocking ratio of DFCA assignments due to C/I reason alone. Use: Indicates the ratio of only C/I reason soft-blocked DFCA assignment requests to total DFCA assignment requests Experiences on use: Known problems: Open questions: Formula: Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CI) 100 * --------------------------------------------- ( dfca_2 ) ; total DFCA assignment requests Counters from table(s): p_nbsc_dfca




704/712

DFCA soft-blocking ratio for C/N reason, S11 (dfca_8)

Description: Soft-blocking ratio of DFCA assignments due to C/N reason alone. Use: Indicates the ratio of only C/N reason soft -blocked DFCA assignment requests to total DFCA assignment requests Experiences on use: Known problems: Open questions: Formula: Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CN) 100 * -------------------------------------------- ( dfca_2 ) ; total dfca assignment requests Counters from table(s): p_nbsc_dfca

Total number of DFCA channel assignments, S11 (dfca_9)

Description: Total number of DFCA assignments Use: A reference for indicating the share in each DFCA C/I estimate. Experiences on use: Known problems: Open questions: Formula: Sum(DFCA_C_I_TG_UL + DFCA_C_I_TG_1_UL + DFCA_C_I_TG_2_UL + DFCA_C_I_TG_3_UL




705/712

+ DFCA_C_I_TG_4_UL + DFCA_C_I_TG_5_UL + DFCA_C_I_TG_6_UL + DFCA_C_I_TG_7_UL + DFCA_C_I_TG_8_UL + DFCA_C_I_TG_9_UL + DFCA_C_I_TG_10_UL + DFCA_C_I_TG_11_UL + DFCA_C_I_TG_12_UL + DFCA_C_I_TG_13_UL + DFCA_C_I_TG_14_UL + DFCA_C_I_TG_15_UL + DFCA_C_I_TG_16_UL + DFCA_C_I_TG_17_UL + DFCA_C_I_TG_18_UL + DFCA_C_I_TG_19_UL + DFCA_C_I_TG_20_UL + DFCA_C_I_TG_ABOVE_20_UL + DFCA_C_I_TG_M_1_UL + DFCA_C_I_TG_M_2_UL + DFCA_C_I_TG_M_3_UL + DFCA_C_I_TG_M_4_UL + DFCA_C_I_TG_M_5_UL + DFCA_C_I_TG_M_6_UL + DFCA_C_I_TG_M_7_UL + DFCA_C_I_TG_M_8_UL + DFCA_C_I_TG_M_9_UL + DFCA_C_I_TG_M_10_UL + DFCA_C_I_TG_M_11_UL + DFCA_C_I_TG_M_12_UL + DFCA_C_I_TG_M_13_UL + DFCA_C_I_TG_M_14_UL + DFCA_C_I_TG_M_15_UL + DFCA_C_I_TG_BELOW_M_15_UL)




706/712

Counters from table(s): p_nbsc_dfca

WPS

Average successful queuing time for WPS user, S11 (wps_1)

Description: Average successful queuing time for a WPS user. Use: Indicates the average successful queuing time for a WPS user. Experiences on use: Known problems: Open questions: Formula: Avg(AVE_SUCC_WPS_QUEUE_TIME/WPS_DENOMINATOR_3)

Counters from table(s): p_nbsc_wps

Average occupied FTCHs for WPS user, S11 (wps_2)

Description: Average occupied FTCHs for a WPS user. Use: Indicates the average occupied FTCHs for a WPS user. Experiences on use: Known problems:




707/712

Open questions: Formula: Avg(WPS_AVE_OCCU_FTCH_COUNT/WPS_DENOMINATOR_1)


Average occupied HTCHs for WPS user, S11 (wps_3)

Description: Average occupied HTCHs for a WPS user. Use: Indicates the average occupied HTCHs for a WPS user. Experiences on use: Known problems: Open questions: Formula: Avg(WPS_AVE_OCCU_HTCH_COUNT/WPS_DENOMINATOR_2)





708/712

Template

Name of formula, S1 (xxx_0)

Origin: <The name of the person who has introduced the formula to the editor of the document> Use: <What could be the purpose of the formula> Experiences on use: <Any typical values, bad and good values> Known problems: <Problems found when using> Open questions: <Unknown aspects of the formula> Formula: < formula> avg(a.xxxxxxx/a.xxxxx_denom1) a = <table name>




709/712

MISSING COUNTERS

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

XX1

Meaning: How many calls were taken from queue to DR Related problem: If a call attempt is in a queue, it is taken to DR as soon as the DR target list is ready. In this case counters show as if the queuing took

place: tch_qd_call_att is triggered but unsrv_qd_call_att is not. How movement from a queue to DR takes place depends on queuing time and cell parameter Directed Retry Time Limit Min. Planned schedule: S8 (REMOVAL_FROM_QUE_DUE_TO_DR, counter id: 1173).




710/712

XX2

Meaning: Clear by MS user during HO procedure. Related problem: Affects counting of HO failure ratios. The ratio cannot be counted accurately (see hfr_2). Planned schedule: Open.

XX3

Meaning: Clear by another procedure during HO procedure, such as . assignment. Related problem: Affects counting of HO failure ratios. The ratio cannot be counted accurately (see hfr_2). Planned schedule: Open.

XX4

Meaning: Number of available timeslots for TCH (half or full rate). Related problem: Without this counter it is not possible to count the TCH availability in case HTCH is used. Planned schedule: S9: ave_avail_TCH_sum, ave_avail_TCH_den




711/712

ABBREVIATIONS

SS Supplementary Service SMS Short Message Service LU Location Update DR Directed Retry




712/712

REFERENCES

Ref.2

tch_norm_seiz is triggered in parallel with cell_sdcch_tch in case of DAC and with bsc_o_sdcch_tch or msc_o_sdcch_tch in case of DADLB.