Horizon Kpi Guide Migr dn0983176 01A en

GSM/EDGE BSS, Rel.
RG10(BSS), Operating
Documentation, Issue 08, Doc.
Change Delivery 1
KPI guidelines for Horizon BTS migration

to the Flexi BSC product family
DN0983176
Issue 01A
Approval Date 2011-06-13
KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2011. All rights reserved
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the “Legal, Safety
and Environmental Information” part of this document or documentation set.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.
2 Id:0900d80580874610 DN0983176
Issue 01A
BSC product family
Table of contents
This document has 89 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Horizon BTS migration and related KPI measurements . . . . . . . . . . . . . 9
2 Employment of KPIs during migration . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 Performance verification KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Main field KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Summary of KPI differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Performance verification KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Main field KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Performance verification KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.1 TCH availability ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.1.1 GSR: BSS_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.1.2 BSS: ava_1g TCH availability ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Traffic volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2.1 Average CS traffic per BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2.1.1 GSR: TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2.1.2 BSS: trf_1d Average CS traffic per BTS . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Call Setup Success Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.1 Immediate Assignment Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.1.1 GSR: IMMEDIATE_ASSIGNMENT_ACCESS_RATE . . . . . . . . . . . . . . 16
4.3.1.2 BSS: trf_467a Immediate assignment success rate . . . . . . . . . . . . . . . 16
4.3.2 SDCCH Usage Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.2.1 GSR: SDCCH_USAGE_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . 16
4.3.2.2 BSS: csf_43b SDCCH usage success rate . . . . . . . . . . . . . . . . . . . . . . 17
4.3.3 TCH Allocation Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3.3.1 GSR: TCH_ALLOCATION_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . 17
4.3.3.2 BSS: csf_44b TCH allocation success rate . . . . . . . . . . . . . . . . . . . . . . 17
4.4 TCH drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.1 TCH drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.1.1 GSR: TCH_DROP_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.1.2 BSS: dcr_29 TCH drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2 TCH drops / Erlang . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2.1 GSR: TCH DROPS / ERLANG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2.2 BSS: dcr_26a TCH drop / Erlang (before re-establishment) . . . . . . . . . 18
4.5 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1 Handover success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1.1 GSR: HANDOVER_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1.2 BSS: hsr_28 Total handover success ratio . . . . . . . . . . . . . . . . . . . . . . 20
4.5.2 Handover drop rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.2.1 GSR: HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 20
DN0983176 Id:0900d80580874610 3
Issue 01A
BSC product family
4.5.2.2 BSS: hfr_68c handover drop ratio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.6 PS traffic volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1 (E)GPRS UL/DL Payload data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1.1 GSR: UL_USER_TRAFFIC_GPRS, DL_USER_TRAFFIC_GPRS . . . . 22
4.6.1.2 GSR: UL_USER_TRAFFIC_EGPRS, DL_USER_TRAFFIC_EGPRS . . 22
4.6.1.3 BSS: trf_213c, trf_212c GPRS DL/UL Payload Data . . . . . . . . . . . . . . . 23
4.6.1.4 BSS: trf_215a, trf_214a EGPRS DL/UL Payload Data . . . . . . . . . . . . . . 24
4.6.2 TBF multiplexing (RTSL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6.2.1 GSR: None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6.2.2 BSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslot . . . . . . . . . . . . 24
5 Main field KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.1 Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.1 Call Set-Up Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.1.1 GSR: CALL_SET-UP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.1.2 BSS: cssr_8a Call setup success rate . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.2 SDCCH Blocking Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.2.1 GSR: SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.2.2 BSS: blck_5, SDCCH blocking, before FCS . . . . . . . . . . . . . . . . . . . . . . 27
5.1.3 TCH Blocking Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.3.1 GSR: TCH_BLOCKING_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.3.2 BSS: blck_1a, TCH call blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.4 Call Set-Up Blocking Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.4.1 GSR: CALL_SET-UP_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.4.2 BSS: blck_8i, Call Set-Up Blocking Rate . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.5 Assignment Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.5.1 GSR: ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.5.2 BSS: trf_485a Assignment success rate. . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.6 Immediate Assign Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.6.1 GSR: IMMEDIATE_ASSIGN_SUCCESS_RATE . . . . . . . . . . . . . . . . . . 29
5.1.6.2 BSS: trf_486a Immediate assignment success rate% . . . . . . . . . . . . . . 29
5.1.7 Immediate Assign Access Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1.7.1 GSR: IMMEDIATE_ASSIGN_ACCESS_RATE . . . . . . . . . . . . . . . . . . . 29
5.1.7.2 BSS: trf_467a Immediate assignment access rate . . . . . . . . . . . . . . . . . 30
5.1.8 Circuit Switched System Accesses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.8.1 GSR: CIRCUIT_SWITCHED_SYSTEM_ACCESSES . . . . . . . . . . . . . . 30
5.1.8.2 BSS: trf_487 Circuit switched system access. . . . . . . . . . . . . . . . . . . . . 30
5.2 Retain ability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.1 Call Drop Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.1.1 GSR: DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.1.2 BSS: dcr_54b Call Drop Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2 SDCCH RF Loss Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2.1 GSR: SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2.2 BSS: sdr_18a SDCCH RF Loss Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.3 Mean Time Between Drops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.3.1 GSR: MEAN_TIME_BETWEEN_DROPS. . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.3.2 BSS: dcr_55a Mean Time Between Drops . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.4 Intra Cell HO Success Rate & Intra Cell HO Attempts . . . . . . . . . . . . . . 32
4 Id:0900d80580874610 DN0983176
Issue 01A
BSC product family
5.2.4.1 GSR: INTRA_CELL_ HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . 32

5.2.4.2 BSS: hsr_32a Intra cell HO Success Rate. . . . . . . . . . . . . . . . . . . . . . . 33
5.2.5 Intra BSS HO Success Rate & Intra BSS HO Attempts. . . . . . . . . . . . . 33
5.2.5.1 GSR: INTRA_BSS_HO_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . 33
5.2.5.2 BSS: hsr_33a Intra BSS HO Success Rate. . . . . . . . . . . . . . . . . . . . . . 33
5.2.6 Inter BSS HO Success Rate & Inter BSS HO Attempts. . . . . . . . . . . . . 33
5.2.6.1 GSR: INTER_BSS_HO_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . 33
5.2.6.2 BSS: hsr_34a Inter BSS HO Success Rate. . . . . . . . . . . . . . . . . . . . . . 34
5.2.7 HO Cause Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2.7.1 GSR: HO_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2.7.2 BSS: HO Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.3 Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.1 Call Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.1.1 GSR: CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.1.2 BSS: trf_488 Call Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.2 TCH Traffic Carried . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.2.1 GSR: TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.2.2 BSS: trf_489 TCH traffic carried . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.3 SDCCH Traffic Carried . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.3.3.1 GSR KPI: SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . 37
5.3.3.2 BSS: trf_490 SDCCH Traffic Carried . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4 PS traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.1 UL TBF Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.1.1 GSR: UL_TBF_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.1.2 BSS: tbf_74a, TBF establishment success rate UL . . . . . . . . . . . . . . . . 38
5.4.2 DL TBF Success Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.2.1 GSR: DL_TBF_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.2.2 BSS: tbf_145 (E)GPRS DL TBF establishment failure ratio . . . . . . . . . 39
5.4.3 UL TBF Failure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.3.1 GSR: UL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.3.2 BSS: tbf_142 UL TBF Failure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.4 DL TBF Failure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.4.1 GSR: DL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.4.2 BSS: tbf_143 DL TBF Failure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4.5 UL & DL GPRS Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4.5.1 GSR: UL & DL_USER_TRAFFIC_GPRS . . . . . . . . . . . . . . . . . . . . . . . 40
5.4.5.2 BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data 40
5.4.6 GPRS Access Per Rach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4.6.1 GSR: GPRS_ACCESS_PER_RACH. . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.4.6.2 BSS: 072082 PACKET_CH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6 Counter group mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
7 Counter list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1 GSR counter list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.2 BSS counter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
DN0983176 Id:0900d80580874610 5
Issue 01A
BSC product family
List of tables
Table 1 Summary of performance verification KPI differences . . . . . . . . . . . . . . 11
Table 2 Summary of main field KPI differences . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 3 Paging method for UL_RLC_ACK_BLKS/UL_RLC_UNACK_BLKS . . . 23
Table 4 Paging method for DL_RLC_ACK_BLKS/DL_RLC_UNACK_BLKS . . . 23
Table 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 6 GSR counter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 7 BSS counter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6 Id:0900d80580874610 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Summary of changes
BSC product family
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 01 (2011-01-24) and 01A (2011-06-13)
• Counter descriptions have been moved to chapters 7.1 GSR counter list and
7.2 BSS counter list.
Introduction (1)
• Figure 1 Reference network architecture has been removed.
• The introduction chapter has been rephrased and two new sections 1.1 Terminology
and 1.2 Horizon BTS migration and related KPI measurements have been added.
Summary of KPI differences (3)

• New KPIs form the chapter UL & DL GPRS Traffic have been added to 3.2 Main field
KPIs.
Call Setup Success Ratio (4.3)

• The following KPI formulas have been updated: trf_467a, csf_43b, csf_44b.
TCH drop (4.4)

• The dcr_29 KPI formula has been updated.
Handover (4.5)
• The following KPI formulas have been updated: hsr_28 and hsr_68c.
PS traffic volume (4.6)

• Following KPI formulas have been simplified: trf_212c, trf_213c and trf_215a
Accessibility (5.1)
• The following KPI formulas have been changed: cssr_8a and trf_467a.
• The naming of the following KPIs have been changed: cssr_8 onto cssr_8a, trf_485
onto trf_485a, and trf_486 onto trf_486a.
• KPI formula has been updated in 5.1.3 TCH Blocking Rate chapter.
Retain ability (5.2)

• The following KPI formulas have been changed: dcr_54b, sdr_18a, hsr_32a,
hsr_33a and hsr_34a.
• The naming of the following KPIs have been changed: dcr_54 onto dcr_54b, sdr_18
onto sdr_18a, dcr_55 onto dcr_55a, hsr_32 onto hsr_32a, hsr_33 onto hsr_33a, and
hsr_34 onto hsr_34a.
PS traffic (5.4)
• The tbf_49 has been replaced by the tbf_145.
• Description for the 072121 UL_TBF_ESTABL_STARTED couner has been
updated.
• The new chapter 5.4.5 UL & DL GPRS Traffic has been added.
DN0983176 Id:0900d8058087521f 7
Issue 01A
Summary of changes KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
Counter group mapping (6)

• 6 Counter group mapping chapter has been added.
BSS counter list (7.2)

• Counter list has been updated with new and updated KPIs.
8 Id:0900d8058087521f DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Introduction
BSC product family
1 Introduction
This document describes the possible differences between network key performance
indicators (KPIs) of the GSR and BSS product lines, in the context of Horizon BTS
migrating to the Flexi BSC product family.
1.1 Terminology
The term Flexi BSC is used to refer to all BSCs of the Flexi BSC product family, namely
the BSC3i 660, 1000 and 2000, as well as the Flexi BSC.
The BSS Abis interface implementation used in the product line to connect the Horizon
BTS with the BSC is referred to as the BSS Abis. It is also the Abis interface implemen-
tation used in the BSS product line to connect the Flexi EDGE BTS with the Flexi BSC.
There are two kinds of software releases paired with the BSC Horizon BTS, GSM
Software Release (GSR) and RAN Software Release (RSR). This document describes
only GSR KPIs.
1.2 Horizon BTS migration and related KPI measurements

The KPIs are measured before the migration of Horizon BTS to the FlexiBSC. These
values are used for comparing service quality before and after the migration. There
should be no degradation of Performance Monitoring KPIs post migration procedure.
The detailed migration procedure description can be found in the Migrating Horizon BTS
to the Flexi BSC Product Family.
This document shows the relationship between GSR KPIs and BSS KPIs and the KPI
substitution after migration. The comparison of BSS KPIs accuracy to GSR KPIs results
in creating new KPIs to support GSR KPIs without relevant substitute in BSS.
This document also describes the similarities and main differences between GSR and
BSS counters and measurements.
After the migration of Horizon BTSs. BTSs are controlled by Flexi BSC/BSC3i. The
network architecture details are to be found in the Horizon BTS at Flexi BSC Product
Family document.
The KPIs are divided into two categories 2.1 Performance verification KPIs and
2.2 Main field KPIs.
DN0983176 Id:0900d80580895c8d 9
Issue 01A
Employment of KPIs during migration KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
2 Employment of KPIs during migration

The Key Performance Indicators during the preparation phase compare the service
quality before and after the Horizon BTS migration to Flexi BSC.
The last phase of migration is optimization phase where the measured KPIs before
migration allow to compare results from after the migration. This KPI measurements are
the base for the network quality verification.
KPIs after the migration are rather based on the BSS BSC counters and KPIs than GSR.
After the migration process GSR counters and KPIs are no longer supported.
The migration of Horizon BTS from the GSR to the BSS BSC results in execution of mul-
tiplant and multilayer traffic management algorithms as well as the handover and power
control. This affects related to traffic, handover and the power control KPIs. The KPI
results before and after the migration might differ.
The GSR supports a functionality which allows a second attempt to assign the mobile
station onto a TCH if the first TCH assignment fails and the mobile successfully recovers
to the SDCCH (or signaling TCH) and a functionality to move the User Equipment to the
full power mode in order to continue the call when there is a risk of call drop. The Flexi
BSC does not support the BSS triggered second assignment and ‘Link about to fail’
functionality. That causes a small reduction in related KPIs.
The BSS BSC contains functionality, that ensures that the BSS abnormal release is not
triggered if the associated connection is already undergoing DTAP call clearing, which
GSR does not support. The Clear Request Suppression functionality should be disabled
in GSR BSC until the migration is completed.
2.1 Performance verification KPIs

Performance Verification KPIs are used to validate the consistency of network perfor-
mance before and after a Horizon BTS migration to a new Flexi BSC, both from the per-
spective of the end user and the network operator. In general, there should be no be no
increase or decrease in performance verification KPI values through a BTS migration.
The network capacity before and after migration is identical in terms of features enabled
and parameter settings. Any differences in KPI values require analysis for root cause of
the performance change.The network capacity, configuration, parameters and features
are mapped properly to be able to achieve the same performance before and after
migration, so the migrated network can be verified based on KPIs.
2.2 Main field KPIs

GSR Field KPIs are used to validate consistency of network performance before and
after a Horizon BTS migration to a new Flexi BSC, both from the perspective of the end
user and the network operator. In general, there should be no be no increase or
decrease in KPI values through a BTS migration, assuming the system configuration
and capacity before and after migration is identical in terms of features enabled and
parameter settings. Any differences in KPI values require analysis for root cause of the
performance change. The GSR Field KPIs section of this document defines a set of KPIs
based on BSS counters that matches as closely as possible to existing GSR field KPIs.
10 Id:0900d80580895bff DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Summary of KPI differences
BSC product family
3 Summary of KPI differences
3.1 Performance verification KPIs
KPI category GSR KPI BSS KPI New Match

BSS KPI
Availability
TCH avaliability ratio BSS_AVAILABILITY ava_1g - Minor deviation
Traffic volume
Average CS traffic per BTS TCH_TRAFFIC_CARRIED trf_1d - Minor deviation
Call Setup Success Ratio
Immediate Assignment IMMEDIATE_ASSIGNMENT_AC trf_467a - Minor deviation
Success Rate CESS_RATE
SDCCH Usage Success SDCCH_USAGE_SUCCESS_R csf_43b - Minor deviation
Rate ATE
TCH Allocation Success TCH_ALLOCATION_SUCCESS csf_44b - Major deviation
Rate _RATE
TCH drop
TCH drop TCH_DROP_RATE dcr_29 - Full match
TCH drops / Erlang TCH_DROPS / ERLANG dcr_26a - Full match
Handover
HO success rate HANDOVER_SUCCESS_RATE hsr_28 - Full match
HO drop rate HANDOVER_FAILURE_RATE hfr_68c - Full match
PS traffic volume
(E)GPRS UL/DL Payload UL_USER_TRAFFIC_GPRS, trf_213c, - Minor deviation
data DL_USER_TRAFFIC_GPRS trf_212c
(E)GPRS UL/DL Payload UL_USER_TRAFFIC_EGPRS, trf_215a, - Minor deviation
data DL_USER_TRAFFIC_EGPRS trf_214a
TBF multiplexing (RTSL) - tbf_38d, - No match
tbf_37d
Table 1 Summary of performance verification KPI differences
DN0983176 Id:0900d80580875145 11
Issue 01A
Summary of KPI differences KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
3.2 Main field KPIs

BSS KPI
Accessibility
Call Set-Up Success Rate CALL_SET- cssr_8a New Minor deviation
UP_SUCCESS_RATE
SDCCH Blocking Rate SDCCH_BLOCKING_RATE blck_5 - Full match
TCH Blocking Rate TCH_BLOCKING_RATE blck_1a - Full match
Call Set-Up Blocking Rate CALL_SET- blck_8i - Full match
UP_BLOCKING_RATE
Assignment Success Rate ASSIGNMEN_SUCCESS_RATE trf_485a New Full match
Immediate Assign Success IMMEDIATE_ASSIGN_SUCCE_ trf_486a New Minor deviation
Rate SRATE
Immediate Assign Access IMMEDIATE_ASSIGN_ACCESS trf_467a - Minor deviation
Rate _RATE
Circuit Switched System CIRCUIT_SWITCHED_SYSTEM trf_487 New Full match
Accesses _ACCESSES
Retain ability
Call Drop Rate DROP_CALL_RATE dcr_54b New Full match
SDCCH RF Loss Rate SDCCH_RF_LOSS RATE sdr_18a New Full match
Mean Time Between Drops MEAN_TIME_BETWEEN_DRO dcr_55a New Full match
PS
Intra Cell HO Success Rate INTRA hsr_32a New Full match
& Intra Cell HO Attempts _CELL_HO_SUCCESS_RATE
Intra BSS HO Success INTRA_BSS_HO_SUCCESS_R hsr_33a New Minor deviation
Rate & Intra BSS HO ATE
Attempts
Inter BSS HO Success INTER_BSS_HO_SUCCESS_R hsr_34a New Minor deviation
Rate & Inter BSS HO ATE
Attempts
HO Cause Distribution HO_CAUSE HO - Minor deviation
Distribution
Traffic
Call Volume CALL_VOLUME trf_488 New Minor deviation
TCH Traffic Carried TCH_TRAFFIC_CARRIED trf_489 New Full match
SDCCH Traffic Carried SDCCH_TRAFFIC_CARRIED trf_490 New Full match
PS traffic
UL TBF Success Rate UL_TBF_SUCCESS_RATE tbf_74a - Full match
Table 2 Summary of main field KPI differences
12 Id:0900d80580875145 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Summary of KPI differences
BSC product family

BSS KPI
DL TBF Success Rate DL_TBF_SUCCESS_RATE tbf_145 - Full match
UL TBF Failure Rate UL_TBF_FAILURE_RATE tbf_142 New Full match
DL TBF Failure Rate DL_TBF_FAILURE_RATE tbf_143 New Full match
GPRS Access Per Rach UL & trf_212c, - Minor deviation
DL_USER_TRAFFIC_GPRS trf_213c
(E)GPRS UL/DL Payload UL_USER_TRAFFIC_EGPRS trf_215a, - Minor deviation
data trf_214a
UL & DL GPRS Traffic UL & trf_494, New Full match
DL_USER_TRAFFIC_GPRS trf_495
GPRS Access Per Rach GPRS_ACCESS_PER_RACH 072082 - Full match
PACKET
CH REQ
Table 2 Summary of main field KPI differences (Cont.)
DN0983176 Id:0900d80580875145 13
Issue 01A
Performance verification KPI KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
4 Performance verification KPI
4.1 Availability
4.1.1 TCH availability ratio

The calculation of GSR BSS_AVAILABILITY and BSC BSS
TCH_AVAILABILITY_RATIO are generally matched. There might be some deviation in
generated values since the GSR resource manager measures precisely the number of
available channels to the accuracy of one millisecond whereas the BSS BSC only
samples the number of available channels every 20 seconds.
4.1.1.1 GSR: BSS_AVAILABILITY

Measurement target: Cell
BSS_AVAILABILITY - statistic provides the percentage of all radio timeslots capable of
carrying TCH or PDTCH traffic that are available to be allocated in response to a mobile
request for a circuit switched or packet switched connection.
The statistic is updated every time the number of TCH or PDTCHs in service changes.
There is a change to the availability statistics AVAILABLE_TCH, GPRS_AVAIL_PDTCH
or EGPRS_AVAIL_PDTC. The values produced are accurate to 1ms.
4.1.1.2 BSS: ava_1g TCH availability ratio

Measurement target: BTS
The ava_1g is calculated by the formula:
ava_1g = (ave_avail_tch_sum / ave_avail_tch_den + ave_gprs_channels_sum /

ave_gprs_channels_den) / (ave_avail_tch_sum / ave_avail_tch_den +
ave_gprs_channels_sum / ave_gprs_channels_den + ave_non_avail_tch_timeslot /
non_avail_tch_denom)
14 Id:0900d80580874616 DN0983176
Issue 01A
BSC product family
4.2 Traffic volume
4.2.1 Average CS traffic per BTS

The GSR and BSS measurements for CS TRAFFIC are well matched although there
may be some deviation in the values generated since the GSR resource manager
measures the number of busy TCHs to an accuracy of one millisecond whereas the BSS
BSC samples the number of busy TCHs every 20 seconds. The GSR and BSS calcula-
tions both include the 3PP guard timers T3109 and T3111.
It should be noted that the GSR BSS release currently deployed in the field does not
support DTM, however the field deployment goal for a consistent configuration pre and
post migration will ensure that DTM is disabled post migration and thus the DTM factor
in the BSS calculation should be zero.
4.2.1.1 GSR: TCH_TRAFFIC_CARRIED

The average CS traffic carried per cell is calculated by the formula:
tch_traffic_carried = busy_tch_mean
4.2.1.2 BSS: trf_1d Average CS traffic per BTS

The trf_1d is calculated by the formula:
trf_1d = (ave_busy_tch / res_av_denom14) + [((0.5 * dtm_duration_sum_HR +

dtm_duration_sum_FR) / 100) / (period_duration * 60)]
DN0983176 Id:0900d80580895c03 15
Issue 01A
BSC product family
4.3 Call Setup Success Ratio
4.3.1 Immediate Assignment Success Rate

The GSR KPI IMMEDIATE ASSIGN ACCESS rate provides a measurement that is com-
parable with the BSS KPI IMMEDIATE ASSIGNMENT SUCCESS RATE with one
exception. The GSR calculation does not take into account AGCH overload but the BSS
calculation does take into account AGCH overload. If AGCH overload exists and IMME-
DIATE ASSIGN or IMMEDIATE ASSIGNMENT REJECT messages are dropped at the
BTS then the value produced by the BSS KPI is degraded, however the value produced
by the GSR KPI is not degraded. Assuming there is no AGCH overload then the values
produced by the GSR and BSS KPIs are matched.
4.3.1.1 GSR: IMMEDIATE_ASSIGNMENT_ACCESS_RATE

Immediate IMMEDIATE_ASSIGNMENT_ACCESS_RATE is calculated by the formula:
immediate_assignement_access_rate = [(imm_assgn_cause[orig_call] +
imm_assgn_cause[emer_call] + imm_assgn_cause[call_re_estb] +
imm_assgn_cause[loc_upd] + imm_assgn_cause[page_resp] +
imm_assgn_cause[other_procedures_SDCCH] +
imm_assgn_cause[LMU_establishment]) / ok_acc_proc_suc_rach] * 100%
4.3.1.2 BSS: trf_467a Immediate assignment success rate

The trf_467a is calculated by the formula:
trf_467a = [(imm_assgn_sent - del_ind_msg_rec) / (imm_assgn_sent +

imm_assgn_rej)] * 100
4.3.2 SDCCH Usage Success Rate

The calculation for SDCCH USAGE SUCCESS RATE provided a match for BSS KPI
SDCCH USAGE SUCCESS RATE. The GSR calculation only includes RF related fail-
ures. Therefore the values produced by the GSR and BSS calculations diverge if the
number of failures, user interaction or BTS failures is greater than zero. It is expected
that these type of failures are rare and hence the GSR and BSS calculations are essen-
tially matched.
4.3.2.1 GSR: SDCCH_USAGE_SUCCESS_RATE

The SDCCH_USAGE_SUCCESS_RATE is calculated by the formula:
16 Id:0900d805808745f2 DN0983176
Issue 01A
BSC product family
sdcch_usage_success_rate = [1 - ((rf_loss_sd + (ma_fail_from_ms -

intra_cell_ho_return) - second_assign_atmpt) / ok_acc_proc)] * 100%
4.3.2.2 BSS: csf_43b SDCCH usage success rate

The csf_43b is calculated by the formula:
csf_43b = [1 - [(sdcch_radion_fail + sdcch_rf_old_ho + sdcch_user_act +

sdcch_bcsu_reset + sdcch_netw_act + sdcch_abis_fail_odl + sdcch_bts_fail +
sdcch_lapd_fail) / sdcch_assign]] * 100
4.3.3 TCH Allocation Success Rate

The GSRcalculation TCH ALLOCATION SUCCESS RATE does not provide a full match
for BSS KPI TCH ALLOCATION SUCCESS RATE. The counters requires to exclude
Assignment Failures received by the BTS from the mobile station which are not currently
available in the BSS BSC.
4.3.3.1 GSR: TCH_ALLOCATION_SUCCESS_RATE

The TCH_ALLOCATION_SUCCESS_RATEis calculated by the formula:
tch_allocation_success_rate = (total_calls + assgn_redirect) / (ma_req_from_msc -

(ma_fail_from_ms - intra_cell_ho_return - second_assign_atmpt))
4.3.3.2 BSS: csf_44b TCH allocation success rate

The csf_44b is calculated by the formula:
csf_44b = [(tch_net_call_assign - served_facch_req +(msc_o_sdcch_tch +

bsc_o_sdcch_tch) + cell_sdcch_tch - (msc_i_sdcch_tch + bsc_i_sdcch_tch)) /
(tch_net_call_assign - served_facch_req +(msc_o_sdcch_tch + bsc_o_sdcch_tch) +
cell_sdcch_tch - (msc_i_sdcch_tch + bsc_i_sdcch_tch) + tch_requests_call_attempt -
succ_seiz_call_attempt)] * 100
DN0983176 Id:0900d805808745f2 17
Issue 01A
BSC product family
4.4 TCH drop
4.4.1 TCH drop

The calculation for TCH DROP RATE provides a match for BSS KPI TCH DROP.
4.4.1.1 GSR: TCH_DROP_RATE

The custom GSR calculation for TCH_DROP_RATE is calculated by the formula:
drop_call_rate = [(clr_req_to_msc_fr + clr_req_to_msc_hr) / (clr_cmd_from_msc_fr +

clr_cmd_from_msc_hr)] * 100%
4.4.1.2 BSS: dcr_29 TCH drop

The dcr_29 is calculated by the formula:
dcr_29 = [(tch_radion_fail - tch_rel_due_rad_fail_pch_2_3 + tch_rf_old_ho +

tch_lapd_fail + tch_bts_fail + tch_user_act +tch_bcsu_reset + tch_netw_act +
tch_act_fail_call + tch_abis_fail_old + tch_tr_fail_old) / (tch_radio_fail +
tch_rel_due_rad_fail_ph_2_3 + tch_lapd_fail + tch_bts_fail + tch_user_act
+tch_bcsu_reset + tch_netw_act + tch_act_fail_call + tch_abis_fail_old + tch_tr_fail_old
+ tch_norm_release)] * 100
4.4.2 TCH drops / Erlang

The GSR calculation for TCH DROPS / ERLANG provides a match for BSS KPI TCH
DROPS / ERLANG with one minor exception.
The GSR calculation only includes RF related failures. Therefore, the values produced
by the GSR and BSS calculations diverge as the number of failures, user interaction or
BTS failures becomes more significant. It is expected that these type of failures are rare
and hence the GSR and BSS calculations are essentially matched.
4.4.2.1 GSR: TCH DROPS / ERLANG

The custom GSR calculation TCH DROPS / ERLANG is calculated by the formula:
tch_drops/erl = ((rf_loss_tch + intra_cell_ho_lostms - sig_intra_cell_ho_lostms +

out_intra_bss_ho_lostms - sig_out_intra_cell_ho_lostms + out_inter_bss_ho_fail -
sig_out_inter_bss_ho_fail + out_inter_bss_ho_euip_fail - sig_out_inter_bss_ho_equip-
fail) / (busy_tch_mean))* (60 / length_of_measurement_period)
4.4.2.2 BSS: dcr_26a TCH drop / Erlang (before re-establishment)

18 Id:0900d805808745fa DN0983176
Issue 01A
BSC product family
The dcr_26a is calculated by the formula:
dcr_26a = [(tch_radio_fail - tch_rel_due_rad_fail_ph_2_3 + tch_rf_old_ho +

tch_abis_fail_old + tch_tr_fail_old + tch_ldap_fail + tch_bts_fail + tch_bcsu_reset +
tch_newt_act) /((((0,5 * dtm_duration_sum_hr + dtm_duration_sum_fr)/ 100) /
perion_duration * 60) + (ave_busy_tch / res_av_denom14))] * (60 /
avg(period_duration))
DN0983176 Id:0900d805808745fa 19
Issue 01A
BSC product family
4.5 Handover
4.5.1 Handover success rate

The GSR KPI HANDOVER SUCCESS RATE is an exact match for the BSS KPI
handover SUCCESS RATIO. The counters in the GSR and BSS calculation increment
for exactly the same scenarios, and both formulae cover intra cell handovers, BSC con-
trolled handovers and MSC controlled handovers, both 2G to 2G handovers and 2G to
3G inter system handovers.
4.5.1.1 GSR: HANDOVER_SUCCESS_RATE

The custom GSR calculation for HANDOVER_SUCCESS_RATE is calculated by the
formula:
handover_success_rate = (intra_cell_ho_suc + out_intra_bss_ho_suc +

out_inter_bss_ho_suc) / (intra_cell_ho_atmpt_fr_fr + intra_cell_ho_atmpt_fr_hr +
intra_cell_ho_atmpt_hr_fr + intra_cell_ho_atmpt_hr_hr +
intra_cell_ho_atmpt_sd_to_sd + out_intra_bss_ho_atmpt + out_inter_bss_ho_atmpt)
4.5.1.2 BSS: hsr_28 Total handover success ratio

The hsr_28 is calculated by the formula:
hsr_28 = [(msc_o_succ_ho + bsc_o_succ_ho +cell_succ_ho +

msc_gen_sys_wcdma_ran_ho_com) / (msc_o_ho_cmd + bsc_o_ho_cmd_assgn +
bts_ho_assgn + msc_gen_sys_wcdma_ran_ho_com)] * 100
4.5.2 Handover drop rate

The custom GSR calculation for TCH DROP RATE provides a match for BSS KPI TCH
DROP.
4.5.2.1 GSR: HANDOVER_FAILURE_RATE

The custom GSR calculation for HANDOVER_FAILURE_RATE is calculated by the
formula:
The GSR KPI HANDOVER_FAILURE_RATE measures the percentage of all han-
dovers that are dropped.
ho_drop_rate = (intra_cell_ho_lostms + out_intra_bss_ho_lostms +

out_inter_bss_ho_fail + out_inter_bss_ho_equip_fail) / (intra_cell_ho_atmpt_fr_fr +
intra_cell_ho_atmpt_fr_hr + intra_cell_ho_atmpt_hr_fr + intra_cell_ho_atmpt_hr_hr +
intra_cell_ho_atmpt_sd_to_sd + out_intra_bss_ho_atmpt + out_inter_bss_ho_atmpt)
20 Id:0900d805808745f4 DN0983176
Issue 01A
BSC product family
4.5.2.2 BSS: hfr_68c handover drop ratio

The hfr_68c is calculated by the formula:
hfr_68c = [(bsc_o_drop_calls + msc_o_call_drop_ho + cell_drop_calls +

msc_call_drop_ho_wcdma_ran) / (msc_o_ho_cmd + bsc_o_ho_cmd_assgn +
bts_ho_assgn + msc_gen_sys_wcdma_ran_ho_com)] * 100
DN0983176 Id:0900d805808745f4 21
Issue 01A
BSC product family
4.6 PS traffic volume
4.6.1 (E)GPRS UL/DL Payload data

The GRPR counters both BSS and GSR KPIs are based on sent and transferred RLC
blocks and consider the same blocks, excluding retransmissions. Both formulas assume
that whole data size of the block is used for traffic. However, block sizes used by GSR
formulas contain also RLC header, which causes about 10% difference in the results. A
fully matching custom KPI can be created by using the same block sizes.
The EGPRS counters both BSS and GSR formulas use same block sizes. GSR
counters are counting RLC radio blocks and BSS counters count RLC data blocks. This
causes small inaccuracy to GSR KPI with such MCS-7..9 blocks which contain both new
and some other blocks. Impact of the DL blocks to KPI results is probably low. Impact
on UL payload is slightly higher than on DL payload. KPIs are almost a full match.
4.6.1.1 GSR: UL_USER_TRAFFIC_GPRS, DL_USER_TRAFFIC_GPRS

The UL & DL_USER_TRAFFIC_GPRS are calculated by the formulas:
ul_user_traffic_gprs = ((ul_rlc_ack_new_blks_cs_1 + ul_rlc_unack_new_blks_cs_1) *

22 + (ul_rlc_ack_new_blks_cs_2 + ul_rlc_unack_new_blks_cs_2) * 33 +
(ul_rlc_ack_new_blks_cs_3 + ul_rlc_unack_new_blks_cs_3) * 39 +
(ul_rlc_ack_new_blks_cs_4 + ul_rlc_unack_new_blks_cs_4) * 53) / 1024
dl_user_traffic_gprs = ((dl_rlc_ack_new_blks_cs_1 + dl_rlc_unack_new_blks_cs_1) *

22 + (dl_rlc_ack_new_blks_cs_2 + dl_rlc_unack_new_blks_cs_2) * 33 +
(dl_rlc_ack_new_blks_cs_3 + dl_rlc_unack_new_blks_cs_3) * 39 +
(dl_rlc_ack_new_blks_cs_4 + dl_rlc_unack_new_blks_cs_4) * 53) / 1024
4.6.1.2 GSR: UL_USER_TRAFFIC_EGPRS, DL_USER_TRAFFIC_EGPRS

The UL_USER_TRAFFIC_EGPRS is calculated by the formula:
ul_user_traffic_egprs = ((ul_rlc_ack_new_blks_mcs_1 +
ul_rlc_unack_new_blks_mcs_1) * 22 + (ul_rlc_ack_new_blks_mcs_2 +
ul_rlc_unack_new_blks_mcs_6) * 74 +(ul_rlc_ack_new_blks_mcs_7 +
ul_rlc_unack_new_blks_mcs_9) * 148) / 1024
The DL_USER_TRAFFIC_EGPRS is calculated by the formula:
22 Id:0900d8058088f7a3 DN0983176
Issue 01A
BSC product family
dl_user_traffic_egprs = ((dl_rlc_ack_new_blks_mcs_1 +
dl_rlc_unack_new_blks_mcs_1) * 22 + (dl_rlc_ack_new_blks_mcs_2 +
dl_rlc_unack_new_blks_mcs_6) * 74 +(dl_rlc_ack_new_blks_mcs_7 +
dl_rlc_unack_new_blks_mcs_9) * 148) / 1024
The data shown in Table 3 Paging method for

UL_RLC_ACK_BLKS/UL_RLC_UNACK_BLKS is used to determine which statistic
must be pegged for possible combinations of NEW, NACK, ACK_PEND, and STALL
when transmitting MCS-7, MCS-8, or MCS-9.
Pegging method for UL_RLC_ACK_NEW_BLKS(or UL_RLC_UNACK_NEW_BLKS)
statistic:
(RLC block 1, RLC block 2) UL radio block status

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
(RETRANS, RETRANS) RETRANS
Table 3 Paging method for UL_RLC_ACK_BLKS/UL_RLC_UNACK_BLKS
Pegging method for DL_RLC_ACK_NEW_BLKS(or DL_RLC_UNACK_NEW_BLKS)

statistic:
(RLC block 1, RLC block 2) DL radio block status

(NACK NACK) NACK
(NACK NEW) NACK
(NACK ACK_PEND) NACK
(NEW NEW) NEW
(NEW ACK_PEND) NEW
(ACK_PEND ACK_PEND) ACK_PEND
(NACK STALL) STALL
(NEW STALL) STALL
(STALL STALL) STALL
Table 4 Paging method for DL_RLC_ACK_BLKS/DL_RLC_UNACK_BLKS
4.6.1.3 BSS: trf_213c, trf_212c GPRS DL/UL Payload Data

DN0983176 Id:0900d8058088f7a3 23
Issue 01A
BSC product family
The trf_213c is calculated by the formula:
trf_213c = (rlc_data_blocks_dl_cs1 * 20 + rlc_data_blocks_dl_cs2 * 30 +

coding_scheme11(dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode) * 36 +
coding_scheme12(dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode) * 50) /
1024
The trf_212cis calculated by the formula:
trf_212c = (rlc_data_blocks_ul_cs1 * 20 + rlc_data_blocks_ul_cs2 * 30 +

coding_scheme11(ul_rlc_blocks_in_ack_mode + ul_rlc_blocks_in_unack_mode) * 36 +
coding_scheme12(ul_rlc_blocks_in_ack_mode + ul_rlc_blocks_in_unack_mode) * 50) /
1024
4.6.1.4 BSS: trf_215a, trf_214a EGPRS DL/UL Payload Data

The trf_215a and trf_214a is calculated by the formula:
trf_215a = (coding_scheme1(x) * 22 + coding_scheme2(x) * 28 +coding_scheme3(x) *

37 + coding_scheme4(x) * 44 + coding_scheme5(x) * 56 + coding_scheme6(x) * 74 +
coding_scheme7(x) * 112 + coding_scheme8(x) * 136 + coding_scheme9(x) * 148) /
1024
The x value for trf_215a is given by the formula:
x = dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode
The x value for trf_214a is given by the formula:
x = ul_rlc_blocks_in_ack_mode + ul_rlc_blocks_in_unack_mode
4.6.2 TBF multiplexing (RTSL)

GSR BSC does not support Average TBF per TSL statistics. Not possible to create
matching custom KPI based on existing counters.
4.6.2.1 GSR: None

GSR does not support the necessary counters to create a KPI to calculate the
AVERAGE DL/UL TBF per time slot.
4.6.2.2 BSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslot

24 Id:0900d8058088f7a3 DN0983176
Issue 01A
BSC product family
The tbf_38d is calculated by the formula:
tbf_38d = (ave_dl_tbfs_per_used_tsl) / (aver_tbfs_per_tsl_dl_den * 100)
The tbf_37d is calculated by the formula:
tbf_37d = (ave_ul_tbfs_per_used_tsl) / (aver_tbfs_per_tsl_ul_den * 100)
DN0983176 Id:0900d8058088f7a3 25
Issue 01A
Main field KPI KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
5 Main field KPI
5.1 Accessibility
5.1.1 Call Set-Up Success Rate

The difference between the GSR and BSS CSSR KPIs is a slight difference in case of
FACCH calls. If there is no SDCCH overload on BSS side then the above difference in
case of FACCH call is irrelevant. Next difference is external SDCCH handovers made
after a re-establishment. This difference is negligible in comparison to remaining
SDCCH seizures, in addition, a lot of operators could have the SDCCH-SDCCH
handover feature disabled. Incoming and outgoing SDCCH or TCH signalling handovers
during call set up in the denominator of GSR KPI are not counted in BSS KPI. Despite
the above differences there is a full match or only minor deviations between the new
proposed BSS and GSR CSSR KPI as in normal network without the SDCCH blocking
the differences can be omitted.
5.1.1.1 GSR: CALL_SET-UP_SUCCESS_RATE

The CALL_SET-UP_SUCCESS_RATE is given by formula:
cssr = [(total_calls + assign_redirect) / (cm_serv_req_call + cm_serv_req_emerg +

cm_serv_req_sms + cm_reestablishment + page_response + loc_flw_on_req_norm +
loc_flw_on_req_sms - sms_init_on_sdcch - sms_init_on_sdcch_req -
sms_init_on_tch_fcs - sms_init_on_tch_fcs_req +sms_init_on_sdcch_ho_in +
sms_init_on_sig_ho_in _req - mt_lcs_on_sdcch + in_intra_css_sig_ho_during_ setup +
in_inter_css_sig_ho_during_ setu - out_intra_css_sig_ho_during_ setu)] * 100%
5.1.1.2 BSS: cssr_8a Call setup success rate

The cssr_8a is given by formula:
cssr_8a = [[(tch_new_call_assign + (msc_o_sdcch_tch + bsc_o_sdcch_tch)) - (

msc_i_sdcch_tch + bsc_i_sdcch_tch)] / [(succ_seiz_term +succ_seiz_orig
+sdcch_emerg_call + sdcch_call_re_est + call_assign_after_sms +
tch_succ_seiz_for_dir_acc + served_facch_req) - (succ_sdcch_sms_est +
unsucc_sdcch_sms_est) - (succ_seiz_supplem_serv)]] * 100
5.1.2 SDCCH Blocking Rate

GSR SDCCH Blocking Rate measures the proportion of all SDCCH resource requests
that are rejected by the radio resource manger due to no available SDCCH resource.
The GSR SDCCH blocking rate covers all requests for SDCCH resource as well as the
BSS SDCCH Blocking Rate.Therefore GSR and BSS KPIs give full match.
26 Id:0900d80580874614 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Main field KPI
BSC product family
5.1.2.1 GSR: SDCCH_BLOCKING_RATE

SDCCH_BLOCKING_RATE is calculated by the formula:
sdcch_blocking_rate = [alloc_sdcch_fail / ( alloc_sdcch + alocc_sdcch_fail)] * 100%
The SDCCH blocking rate covers all requests for SDCCH resource as the immediate
assignment procedure, BSSMAP assignment procedure and incoming intra cell/intra
BSS/inter BSS handovers.
5.1.2.2 BSS: blck_5, SDCCH blocking, before FCS

The blck_5 is given by formula:
blck_5 = 100 * (sdcch_busy_att / sdcch_seiz_att)
5.1.3 TCH Blocking Rate

GSR KPI provides the total TCH blocking also includes all kinds of incoming handovers.
The BSS KPI includes all kinds of procedures used to request a TCH. Therefore these
KPIs provide full match. However, in high load scenario these KPIs might show unreal-
istic values as they are impacted by handover.
5.1.3.1 GSR: TCH_BLOCKING_RATE

TCH_BLOCKING_RATE is calculated by the formula:
tch_blocking_rate = [(alloc_tch_fail - tch_q_removed - tch_preempt_no_q_alloc_all) /

(alloc_tch+ alloc_tch_fail - tch_q_removed - tch_preempt_no_q_alloc_all)] * 100%
TCH Blocking Rate measures the proportion of all TCH resource requests that are
rejected by the radio resource manger due to no available TCH resource. The TCH
blocking rate covers all requests for TCH resource.
5.1.3.2 BSS: blck_1a, TCH call blocking

The blck_1a is given by formula:
blck_1a = 100 * [(tch_req_rej_lack - tch_rej_due_req_ch_a_if_crc) / (tch_request -

tch_rej_due_req_ch_a_if_crc)]
DN0983176 Id:0900d80580874614 27
Issue 01A
BSC product family
5.1.4 Call Set-Up Blocking Rate

Both KPIs are updated only once for every call attempt and both KPIs covers blocking
due to BTS failures. GSR and BSS formulas provide full match.
5.1.4.1 GSR: CALL_SET-UP_BLOCKING_RATE

CALL_SET-UP_BLOCKING_RATE is calculated by the formula:
call_set-up__blocking_rate = (ma_cmd_to_ms_blkd / ma_req_from_msc) *100%
5.1.4.2 BSS: blck_8i, Call Set-Up Blocking Rate

The blck_8i is given by formula:
blck_8i = 100 * [(tch_requests_call_attempt - succ_tch_seiz_call_attempt) /

tch_requests_call_attempt]
5.1.5 Assignment Success Rate

BSS and GSR KPI are full match.
5.1.5.1 GSR: ASSIGNMENT_SUCCESS_RATE

ASSIGNEMENT_SUCCESS_RATE is calculated by the formula:
assignement_success_rate = (ma_complete_to_msc / ma_req_from_msc) * 100%
Assignment Success Rate calculates the percentage of BSSMAP assignment proce-

dures that are successfully completed.
5.1.5.2 BSS: trf_485a Assignment success rate

BSS formula trf_485a is:
trf_485a = 100 * (tch_new_call_assign / tch_call_req)
5.1.6 Immediate Assign Success Rate

BSS and GSR KPIs not fully match because of Served_facch_req is updated only when
a TCH channel is successfully reserved.
28 Id:0900d80580874614 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Main field KPI
BSC product family
5.1.6.1 GSR: IMMEDIATE_ASSIGN_SUCCESS_RATE

IMMEDIATE_ASSIGN_SUCCESS_RATE is calculated by the formula:
immediate_assign_success_rate = ((ok_acc_proc[cm_serv_req_call] +
ok_acc_proc[cm_serv_req_sms] + ok_acc_proc[cm_serv_req_supp] +
ok_acc_proc[cm_serv_req_emerg] + ok_acc_proc[page_response] +
ok_acc_proc[cm_reestablishment] + ok_acc_proc[location_update] +
ok_acc_proc[imsi_detach] + ok_acc_proc[location_services]) /
(im_assgn_cause[orig_call] + im_assgn_cause[emer_call] +
im_assgn_cause[call_re_estb] + im_assgn_cause[loc_upd] +
im_assgn_cause[page_resp] + im_assgn_cause[other_procedures_sdcch] +
im_assgn_cause[lmu_establishment])) * 100%
The Immediate Assign Success Rate calculates the success rate of a mobile success-
fully accessing a dedicated channel (SDCCH or TCH) after the BSS has signaled the
dedicated resource to the mobile via Immediate Assignment.
5.1.6.2 BSS: trf_486a Immediate assignment success rate%

BSS formula trf_486a iis calculated by the formula:
trf_486a = 100% * [(sdcch_assign + served_facch_req) / imm_assgn_sent]
5.1.7 Immediate Assign Access Rate

The GSR KPI IMMEDIATE ASSIGN ACCESS rate provides a measurement that is com-
parable with the BSS KPI IMMEDIATE ASSIGNMENT SUCCESS RATE with one
exception. The GSR calculation does not take into account AGCH overload but the BSS
calculation does take into account AGCH overload. If AGCH overload exists and IMME-
DIATE ASSIGN or IMMEDIATE ASSIGNMENT REJECT messages are dropped at the
BTS then the value produced by the BSS KPI degrades, however, the value produced
by the GSR KPI do not. If there is no AGCH overload then the values produced by the
GSR and BSS KPIs are match.
5.1.7.1 GSR: IMMEDIATE_ASSIGN_ACCESS_RATE

The IMMEDIATE_ASSIGN_ACCESS_RATE is calculated by the formula
immediate_assgn_access_rate = [(imm_assgn_cause[orig_call] +
im_assgn_cause[emer_call] + im_assgn_cause[call_re_estb] +
im_assgn_cause[loc_upd] + im_assgn_cause[page_resp] +
im_assgn_cause[other_procedures_sdcch] + im_assgn_cause[lmu_establishment) /
ok_acc_proc_suc_rach] * 100%
DN0983176 Id:0900d80580874614 29
Issue 01A
BSC product family
5.1.7.2 BSS: trf_467a Immediate assignment access rate

The trf_467a Immediate assignment success rate is calculated by the formula:
trf_467a = [(imm_assgn_sent - del_ind_msg_rec) / (imm_assgn_sent +

imm_assgn_rej)] * 100
5.1.8 Circuit Switched System Accesses

The GSR and BSS KPIs are full match.
5.1.8.1 GSR: CIRCUIT_SWITCHED_SYSTEM_ACCESSES

The CIRCUIT_SWITCHED_SYSTEM_ACCESSES is calculated by the formula:
circuit_switched_system_accesses = ok_acc_proc_suc_rach
This is the volume measurement of CHANNEL REQUESTS received on the RACH with
circuit switched establishment causes.
5.1.8.2 BSS: trf_487 Circuit switched system access

The created trf_487 KPI is calculated by the formula:
trf_487 = imm_assgn_sent + imm_assgn_rej
30 Id:0900d80580874614 DN0983176
Issue 01A
BSC product family
5.2 Retain ability
5.2.1 Call Drop Rate

There can be some small differences between the GSR and BSS KPIs. The sum of
TCH_ABIS_FAIL_CALL and TCH_TR_FAIL do not count only drops during call release
but also some other drops due to Abis and transcoder failures. For both KPIs the numer-
ator counts all drops suffered on the cell being measured.
5.2.1.1 GSR: DROP_CALL_RATE

The DROP_CALL_RATE is calculated by the formula:
drop_call_rate = (rf_loss_tch + intra_cell_ho_lostms - sig_intra_cell_ho_lostms +

out_intra_bss_ho_lostms - sig_out_intra_cell_ho_lostms + out_ inter_bss_ho_fail -
sig_out_inter_bss_ho_fail + out_inter_bss_ho_equip_fail -
sig_out_inter_bss_ho_equip_fail) / (total_calls + in_inter_bss_ho_suc -
sig_in_inter_bss_ho_suc + in_intra_bss_ho_suc - sig_in_intra_bss_ho_suc)
The DROP_CALL_RATE measures the percentage of calls having successfully estab-

lished on a TCH in a cell subsequently suffer a BSS initiated abnormal release due to
RF reasons.
5.2.1.2 BSS: dcr_54b Call Drop Rate

The dcr_54b is calculated by the formula:
dcr_54b = [(tch_radio_fail - tch_rel_due_rad_fail_ph_2_3 + tch_rf_old_ho +

tch_abis_fail_call + tch_tr_fail) / (tch_new_call_assign + msc_i_tch_tch + bsc_i_tch_tch
+ msc_ho_wcdma_ran_succ)] * 100
5.2.2 SDCCH RF Loss Rate

The KPIs give full match because both of the formulas do not considered TCH assign-
ment failures where the MS has returned to SDCCH.
5.2.2.1 GSR: SDCCH_RF_LOSS_RATE

SDCCH_RF_LOSS_RATE is calculated by the formula:
sdcch_rf_loss_rate = [rf_losses_sd / (alloc_sdcch - chan_req_ms_fail)] * 100%
DN0983176 Id:0900d805808745f8 31
Issue 01A
BSC product family
The SDCCH RF Loss Rate calculates the percentage of SDCCH activations that suffer
a BSS initiated abnormal release for RF related reasons after the mobile has success-
fully established on the channel.
5.2.2.2 BSS: sdr_18a SDCCH RF Loss Rate

The sdr_18a is calculated by the formula:
sdr_18a = [(sdcch_radio_fail - spare001229) / (sdcch_assign - T3101_expired)] * 100
5.2.3 Mean Time Between Drops

BSS KPI provides a match for the GSR. The GSR calculation only includes radio related
failures. The values produced by the GSR and BSS calculations diverges as the number
of failures due to LAPD Abis and user interaction or BTS failures. It is expected that
these type of failures are rare and the GSR and BSS calculations are essentially
matched.
5.2.3.1 GSR: MEAN_TIME_BETWEEN_DROPS

The MEAN_TIME_BETWEEN_DROPS measures the mean time between BSS initi-
ated abnormal releases is calculated by the formula:
mtbd = (bust_tch_mean * start_interval_duration(1800 or 3600 seconds)) / (rf_loss_tch

+ intra_cell_ho_lostms - sig_intra_cell_ho_lostms + out_intra_bss_ho_lostms -
sig_out_intra_cell_ho_lostms + out_ inter_bss_ho_fail - sig_out_inter_bss_ho_fail +
out_inter_bss_ho_equip_fail - sig_out_inter_bss_ho_equip_fail)
5.2.3.2 BSS: dcr_55a Mean Time Between Drops

The dcr_55a is calculated by the formula:
dcr_55a = (ave_ftch_hold_tim / 100) / (tch_radio_fail - tch_rel_due_rad_fail_ph_2_3 +

tch_rf_old_ho + tch_abis_fail_call + tch_tr_fail)
5.2.4 Intra Cell HO Success Rate & Intra Cell HO Attempts

The GSR and BSS KPIs are match.
5.2.4.1 GSR: INTRA_CELL_ HO_SUCCESS_RATE

INTRA_CELL_ HO_SUCCESS_RATE is calculated by the formula:
32 Id:0900d805808745f8 DN0983176
Issue 01A
BSC product family
intra_cell_ho_success_rate = intra_call_ho[intra_cell_ho_suc] /
(intra_call_ho[intra_cell_ho_atmpt_fr_fr] + intra_call_ho[intra_cell_ho_atmpt_hr_hr] +
intra_call_ho[intra_cell_ho_atmpt_hr_fr] + intra_call_ho[[intra_cell_ho_atmpt_fr_hr] +
intra_call_ho[intra_cell_ho_atmpt_sd_to_sd])
INTRA_CELL_ HO_SUCCESS_RATE calculates the proportion of attempted intra cell

handovers that result in the mobile success access of the target channel.
5.2.4.2 BSS: hsr_32a Intra cell HO Success Rate

Created hsr_32a is calculated by the formula:
hsr_32a = (cell_succ_ho / bts_ho_assgn) * 100
5.2.5 Intra BSS HO Success Rate & Intra BSS HO Attempts

When analyzing KPI matching the amount of handovers should be equal.
5.2.5.1 GSR: INTRA_BSS_HO_SUCCESS_RATE

INTRA_BSS_HO_SUCCESS_RATE is calculated by the formula:
out_intra_bss_ho_success_rate = (out_intra_bss_ho_suc / out_intra_bss_ho_atmpt) *

100%
INTRA_BSS_HO_SUCCESS_RATE calculates the proportion of attempted intra BSS

handovers that result in the mobile successful access to the target channel.
5.2.5.2 BSS: hsr_33a Intra BSS HO Success Rate

Created hsr_33a is calculated by the formula:
hsr_33a = (bsc_o_succ_ho / bsc_o_ho_cmd_assgn) * 100
5.2.6 Inter BSS HO Success Rate & Inter BSS HO Attempts

GSR KPI and BSS KPI are match with minor deviation. The amount of handovers for
GSR and BSS KPIS should be on the same level to achieve similar results.
5.2.6.1 GSR: INTER_BSS_HO_SUCCESS_RATE

INTER_BSS_HO_SUCCESS_RATE is calculated by the formula:
DN0983176 Id:0900d805808745f8 33
Issue 01A
BSC product family
out_inter_bss_ho_success_rate = (out_inter_bss_ho_suc / out_inter_bss_ho_atmpt) *

100%
INTER_BSS_HO_SUCCESS_RATE calculates the proportion of attempted inter BSS

handovers that result in the mobile successfully accessing the target channel.
5.2.6.2 BSS: hsr_34a Inter BSS HO Success Rate

Created hsr_34a KPI is calculated by the formula:
hsr_34a = [(msc_o_succ_ho + msc_to_wcdma_ran_succ_tch_ho) / (msc_o_ho_cmd +

msc_gen_sys_wcdma_ran_ho_com)] * 100
5.2.7 HO Cause Distribution

The handover KPIs are match with minor deviation.The amount of handovers should be
analyzed while GSR and BSS KPI matching.
5.2.7.1 GSR: HO_CAUSE

The HO_CAUSE is calculated by the formula:
ho_cause_’X’ = out_ho_cause_atmpt (cause’X’) / out_ho_cause_atmpt
The HO_CAUSE is set of identical formula for each of the 12 handover causes gener-
ated by the handover process.
Handover causes:
• DL RxLev,
• DL RxQual,
• UL RxLev,
• UL RxQual,
• DL Interference,
• UL Interference,
• Power Budget,
• Distance,
• Congestion,
• Adjacent Channel Interference,
• Band Reassignment,
• Band Handover.
5.2.7.2 BSS: HO Distribution

There is no KPI formula, only separate counters:
34 Id:0900d805808745f8 DN0983176
Issue 01A
BSC product family
ho_cause_distribution = out_ho_cause / ∑(out_ho_cause)
OUT_HO_CAUSES:
004023 HO CAUSE_UP_QUAL, where the cause is UPLINK QUALITY.
004024 HO CAUSE_UP_LEVEL, where the cause is UPLINK LEVEL.
004025 HO CAUSE_DOWN_QUAL, where the cause is DOWNLINK QUALITY.
004026 HO CAUSE_DOWN_LEV, where the cause is DOWNLINK LEVEL.
004027 HO CAUSE_DISTANCE, where the cause is DISTANCE.
004029 HO CAUSE_INTFER_UP, where the cause is HIGH INT ON UPLINK.
004030 HO CAUSE_INTFER_DWN, where the cause sighs INT ON DOWNLINK.
004031 HO CAUSE_UMBR, where the cause is UMBRELLA.
004032 HO CAUSE_PBDG, where the cause is POWER BUDGET.
DN0983176 Id:0900d805808745f8 35
Issue 01A
BSC product family
5.3 Traffic
5.3.1 Call Volume

KPIs are almost full match with following minor deviations: BSS
TCH_NEW_CALL_ASSIGN is updated right after the ASSIGNMENT COMPLETE
message is received from BTS while GSR TOTAL_CALLS is updated after ASSIGN-
MENT COMPLETE message is sent to MSC. The difference is minor. GSR
ASSIGN_REDIRECT counter counts directed retry of handover during setup and multi-
band reassignments but handover during assignment is not supported in BSS. These
difference, however, is minor. The directed retry is supported in both of GSR and BSS.
5.3.1.1 GSR: CALL_VOLUME

The CALL_VOLUME is calculated by the formula:
call_volume = total_calls + assgn_redirect
5.3.1.2 BSS: trf_488 Call Volume

Created trf_488 KPI is calculated by the formula:
trf_488 = (tch_new_call_assign + (msc_o_sdcch_tch + bsc_o_sdcch_tch)) -

msc_i_sdcch_tch + bsc_i_sdcch_tch
5.3.2 TCH Traffic Carried

The new BSS KPI is proposed so both GSR and BSS TCH holding times are started
when TCH is seized. Both BSS and GSR KPIs include the guard time defined by 3GPP
radio resource timers T3109 and T3111. The only difference is in accuracy. BSS
monitors time with accuracy of 10 ms when GSR with 1 ms. It is almost full match with
new KPI.
5.3.2.1 GSR: TCH_TRAFFIC_CARRIED

The TCH_TRAFFIC_CARRIED is calculated by the formula:
tch_traffic_carried = busy_tch_mean
The TCH_TRAFFIC_CARRIED provides the mean number of busy TCHs measured in

Erlangs.
5.3.2.2 BSS: trf_489 TCH traffic carried

36 Id:0900d80580895c01 DN0983176
Issue 01A
BSC product family
trf_489 = (ave_ftch_hold_tim / 100) / (60 * period_duration)
5.3.3 SDCCH Traffic Carried

There is no existing BSS KPI calculating the mean busy SDCCHs based on the holding
time. Both GSR and BSS SDCCH holding times are started when SDCCH is seized. The
only difference is in accuracy. BSS monitors time with accuracy of 10 ms when GSR with
1 ms. It is almost full match.
5.3.3.1 GSR KPI: SDCCH_TRAFFIC_CARRIED

The SDCCH_TRAFFIC_CARRIED is calculated by the formula:
sdcch_traffic_carried = busy_sdcch_mean
The SDCCH Traffic Carried provides the mean number of busy SDCCHs measured in
Erlangs.
5.3.3.2 BSS: trf_490 SDCCH Traffic Carried

trf_490 = (ave_sdcch_hold_tim / 100) / (60 * period_duration)
DN0983176 Id:0900d80580895c01 37
Issue 01A
BSC product family
5.4 PS traffic
5.4.1 UL TBF Success Rate

GSR UL_TBF_SUCCESS_RATE and BSS tbf_74a are the full match.
5.4.1.1 GSR: UL_TBF_SUCCESS_RATE

Measurement target: ALL
The UL_TBF_SUCCESS_RATE is calculated by the formula:
ul_tbf_success_rate = (ul_pdtch_seizure * 100) / (channel_reqs_rec_p_c +

channel_reqs_rec_p_p + channel_reqs_rec_p_r + channel_reqs_rec_cp_a +
channel_reqs_rec_e_c + channel_reqs_rec_egprs_1ph_cc +
channel_reqs_rec_egprs_1ph_pcc + channel_reqs_rec_egprs_pkrs_rq +
channel_reqs_rec_egprs_crqpdak)
The UL_TBF_SUCCESS_RATE key statistic measures the success of uplink TBF

establishment by providing the percentage of MSs that have requested an uplink TBF
resource and successfully send data using this TBF.
5.4.1.2 BSS: tbf_74a, TBF establishment success rate UL

The tbf_74a is calculated by the formula:
tbf_74a = 100 * [(nbr_of_ul_tbf - ul_tbf_establishment_failed -

ul_egprs_tbf_rel_due_no_resp) / (ul_tbf_establ_started)]
5.4.2 DL TBF Success Rate

The main difference between BSS KIP and GSR KPI is that BSS formula provides failure
ratio and GSR formula success ratio. It is easily solved by using equation success% =
100% - failure%. Based on counter descriptions the triggering points of GSR and BSS
counters are same.
5.4.2.1 GSR: DL_TBF_SUCCESS_RATE

The DL_TBF_SUCCESS_RATE is calculated by the formula:
dl_tbf_success_rate = (dl_pdtch_seizure * 100) / (tbf_dl_asgn_pacch +

gprs_dl_asgn_pccch + egprs_dl_asgn_pccch)
The DL_TBF_SUCCESS_RATE key statistic monitors downlink TBF success.
38 Id:0900d805808745f6 DN0983176
Issue 01A
BSC product family
5.4.2.2 BSS: tbf_145 (E)GPRS DL TBF establishment failure ratio

The tbf_145 is calculated by the formula:
tbf_145 = 100 - [100 * [(dl_tbf_establishment_failed + dl_egprs_tbf_rel_due_no_resp) /

nbr_of_dl_tbf]]
5.4.3 UL TBF Failure Rate

Numerator of GSR KPI considers all TBF phases from establishment to release and
denominator is counting all assignments. Fully matching BSS KPIs does not exist. The
new BSS KPI is introduced.
5.4.3.1 GSR: UL_TBF_FAILURE_RATE

The UL_TBF_FAILURE_RATE is calculated by the formula:
ul_tbf_failure_rate = (air_ul_tbf_failures * 100) / (channel_reqs_success_p_c +

channel_reqs_success_p_p + channel_reqs_success_p_r +
channel_reqs_success_pkts + channel_reqs_success_e_c +
channel_reqs_success_cp_a + channel_reqs_success_e_1p_ccc +
channel_reqs_success_e_1p_pccc + channel_reqs_success_e_puaprr +
channel_reqs_success_e_ptr + channel_reqs_success_e_puapdak)
The UL_TBF_FAILURE_RATE key statistic calculates the rate of faulty uplink TBFs.
5.4.3.2 BSS: tbf_142 UL TBF Failure Rate

tbf_142 = 100 * [(ul_tbf_rel_due_no_resp_ms + ul_tbf_establishment_failed +

ul_egprs_tbf_rel_due_no_resp) / nbr_of_ul_tbf]
5.4.4 DL TBF Failure Rate

The closest existing matching for GSR KPI is tbf_18 BSS KPI. It in not full match
because denominator of tbf_18 counts sent assignments for DL TBF and GSR KPI
denominator counts successfully started DL.
5.4.4.1 GSR: DL_TBF_FAILURE_RATE

The DL_TBF_FAILURE_RATE is calculated by the formula:
DN0983176 Id:0900d805808745f6 39
Issue 01A
BSC product family
dl_tbf_failure_rate = ((air_dl_tbf_failures - air_dl_tbf_failures_et) * 100) /

dl_pdtch_seizure
The DL_TBF_FAILURE_RATE key statistics calculates the rate of abnormally released

downlink TBFs.
5.4.4.2 BSS: tbf_143 DL TBF Failure Rate

tbf_143 = 100 * [dl_tbf_rel_due_no_resp_ms / (nbr_of_dl_tbf -

dl_tbf_establishment_failed - ul_egprs_tbf_rel_due_no_resp)]
5.4.5 UL & DL GPRS Traffic

GSR KPI and BSS KPI are fully matching.
5.4.5.1 GSR: UL & DL_USER_TRAFFIC_GPRS

GSR KPI formulas can be found in chapters 4.6.1.1 GSR: UL_USER_TRAFFIC_GPRS,
DL_USER_TRAFFIC_GPRS and 1.1.2 GSR: UL_USER_TRAFFIC_EGPRS,
DL_USER_TRAFFIC_EGPRS.
5.4.5.2 BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data
The trf_494 is calculated by the formula:
trf_494 = (rlc_data_blocks_ul_cs1 * 22 + rlc_data_blocks_ul_cs2 * 33 +

coding_scheme11(ul_rlc_blocks_in_ack_mode + ul_rlc_blocks_in_unack_mode) * 39 +
coding_scheme12(ul_rlc_blocks_in_ack_mode + ul_rlc_blocks_in_unack_mode) * 53) /
1024
The trf_495 is calculated by the formula:
trf_495 = (rlc_data_blocks_dl_cs1 * 22 + rlc_data_blocks_dl_cs2 * 33 +

coding_scheme11(dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode) * 39 +
coding_scheme12(dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode) * 53) /
1024
5.4.6 GPRS Access Per Rach

Full match.
40 Id:0900d805808745f6 DN0983176
Issue 01A
BSC product family
5.4.6.1 GSR: GPRS_ACCESS_PER_RACH

GPRS_ACCESS_PER_RACH - tracks the number of packet switched Channel
Request messages successfully received on the Random Access CHannel (RACH) for
GPRS purposes. This statistic pegs when a packet switched Channel Request message
is sent on the Random Access CHannel (RACH) of a cell.This statistic is pegged for both
GPRS and EGPRS events.
5.4.6.2 BSS: 072082 PACKET_CH_REQ

072082 PACKET_CH_REQ - number of packet channel requests on CCCH. Updated
when a packet channel request is received on common control channel (CHANNEL
REQUEST or EGPRS PACKET CHANNEL REQUEST).
DN0983176 Id:0900d805808745f6 41
Issue 01A
Counter group mapping KPI guidelines for Horizon BTS migration to the Flexi
BSC product family
6 Counter group mapping

This chapter provides mapping of GSR counter groups to BSS counter groups.
Detailed description of BSS counter groups can be found in the Counters/Performance
indicators chapter of the GSM/EDGE BSS, rel.RG10(BSS), operating documentation.
g Note
There are no BSS couners connected to the features that are not supported, as counters
for L3 message validation failures, second assignment and setup signalling handover,
and Cocentric Cell.
GSR counter group Description of the GSR Equivalent BSS counter

counter group group
AMR STATISTICS This group of per cell AMR sta- 14 RX Quality Statistics
tistics provides information on Measurement,
the number of times a change is 107 AMR RX Quality Mea-
made to the AMR codec in use, surement
the relative usage of each AMR
codec and the number of times g BSS counters for
the BSS adjusts the AMR adap- mode adaptations and
tation thresholds for changing thresholds are
codecs. missing.
ATER STATISTICS This group of counters -
measures the performance of
the allocation of ATER channels
on the BSC to Remote
Transcoder interface, including
pre-emption aspects.
BSSMAP ASSIGN- This group of predominantly per 1 Traffic Measurement
MENT STATISTICS cell statistics measures signal-
ing related to the BSSMAP
assignment procedure. The sta-
tistics measure the volume of
Assignment Request and
Assignment Complete
messages on the A interface and
Assignment Command, Assign-
ment Complete and Assignment
Failure messages on the air
interface. Further statistics cover
second assignment, blocking,
queuing and pre-emption
aspects.
Table 5
42 Id:0900d805808934b3 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Counter group mapping
BSC product family

counter group group
BSS-PCU This group of statistics provides -
ETHERNET STATIS- counters related to the perfor-
TICS mance of the Ethernet link
between the BSC and PCU.
BSS-SMLC STATIS- This group of statistics provides Supported locally by the
TICS counters to measurement the following MML commands:
performance of the MTP and OI,OL,OM,ON,OO,OS,OT
SCCP layers of C7 interface
between the BSC and BSS
based Serving Mobile Location
Centre (SMLC).
CALL RELEASE This group of per cell statistics 1 Traffic Measurement,
STATISTICS provides a measure of normal 50 BSC Level Clear Code
and abnormal call releases Measurement,
thorough counts of BSSMAP
51 BSC Level Clear Code
Clear Commands and Clear
Requests. Other counters (PM) Measurement,
measure RF related drops for 57 BSC Level Clear Code
specific radio channel types. (SERLEV) Measurement
CCCH AND PAGING This group of per cell statistics 1 Traffic Measurement,
STATISTICS measures signaling volume on 3 Resource Access Mea-
the Random Access Channel surement,
(RACH), Access Grant Channel
(AGCH) and Paging Channel 57 BSC Level Clear Code
(SERLEV) Measurement
(PCH) for both circuit switched
and packet switched functional-
ity. The main statistics included
in this group peg for Channel
Request, Paging Request,
Immediate Assignment, Immedi-
ate Assignment Reject mes-
sages, including counts per
establishment cause. Other sta-
tistics covered by this group peg
for AGCH / PCH queuing and
messages discarded due to
AGCH or PCH overload.
Table 5 (Cont.)
DN0983176 Id:0900d805808934b3 43
Issue 01A
BSC product family

counter group group
CIRCUIT SWITCHED This group of predominantly per 1 Traffic Measurement,
TRAFFIC STATIS- cell statistics provide circuit 2 Resource Availability
TICS switched traffic related measure- Measurement,
ments, including Erlang mea-
71 MS Capability Indica-
surements per radio channel
tion Measurement,
type, congestion time per radio
channel type and volume of suc- 78 Position-based
cessful call establishments. Services Measurement
There are also specific statistics
that measure on a per zone, per
g BSS counters for
some MS types are
frequency band (PGSM, EGSM
missing
and DCS1800), per codec (e.g.
AMR and HR) and per TRX
basis rather than the more
general per cell basis.
CONNECTION This group of per cell statistics 1 Traffic Measurement,
ESTABLISHMENT provides a variety of different 3 Resource Access Mea-
STATISTICS measurements related to con- surement,
nection establishment e.g.
57 BSC Level Clear Code
access onto SDCCH per estab-
(SERLEV) Measurement,
lishment cause, failure to access
SDCCH (T3101 expiry), cipher- 71 MS Capability Indica-
ing failures, classmark update tion Measurement,
failures, volume of SAPI3 estab- 78 Position-based
lishments for SMS and volume Services Measurement
system accesses by multi-RAT
mobiles.
EMERGENCY CALL This group of per cell statistics 1 Traffic Measurement
STATISTICS measures the volume of emer-
gency call attempts, related
channel pre-emptions and emer-
gency call failures.
Table 5 (Cont.)
44 Id:0900d805808934b3 DN0983176
Issue 01A
BSC product family

counter group group
GPRS/EDGE PCU This large group of statistics 57 BSC Level Clear Code
STATISTICS provides measurement of (SERLEV) Measurement,
GPRS/EDGE packet switched 72 Packet Control Unit
performance, mainly pegging at Measurement,
the PCU.
74 Frame Relay Measure-
ment,
79 Coding Scheme Mea-
surement,
90 Quality of Service Mea-
surement,
98 Gb Over IP Measure-
ment
g BSS counters for PFC

procedures, Packet
system informations,
DL TBF time per TS,
and idle PDTCH per
interference band are
missing. There are no
corresponding
counters for and versal
TRAUbecause of
feature difference.
HANDOVER STATIS- This group of predominantly per 1 Traffic Measurement,
TICS cell statistics measures 4 Handover Measurement
handover attempts, handover
successes and handover g
There are no corre-
failures for intra cell handovers, sponding counters for
BSC controlled handovers and extended cell due to
MSC controlled handovers. Sta- feature difference.
tistics cover both incoming and
outgoing handovers. Other sta-
tistics cover signaling han-
dovers, zone handovers,
extended range handovers con-
gestion relief, directed retry and
handover causes.
LOCATION This group of statistics provides 78 Position-based
SERVICES BSS STA- counters related to the BSSLAP Services Measurement
TISTICS layer 3 protocol between the
BSS and SMLC and also
location services aspects of the
BSSAP protocol.
Table 5 (Cont.)
DN0983176 Id:0900d805808934b3 45
Issue 01A
BSC product family

counter group group
LOCATION This group of statistics provides Supported locally by the
SERVICES MTP a wide variety of counters mea- following MML commands:
STATISTICS suring the performance of the OI,OL,OM,ON,OO,OS,OT
Location Services Message
Transfer Part (LMTP) of the ITU-
TSS No.7 protocol on the BSC to
MSC interface.
MTP STATISTICS This group of statistics provides Supported locally by the
a wide variety of counters mea- following MML commands:
suring the performance of the OI,OL,OM,ON,OO,OS,OT
Message Transfer Part (MTP) of
the ITU-TSS No.7 protocol on
the BSC to MSC interface.
PER NEIGHBOUR This group of statistics 4 Handover Measurement,
HANDOVER STATIS- measures handover attempts 13 Undefined Adjacent
TICS and handover successes on a Cell Measurement,
per neighbour relationship,
15 Handover Adjacent Cell
included counts per handover
Measurement
cause.
g There are small differ-
ences between
counters due to
handover algorithm
implementation differ-
ences.
PER TRX RF STA- This group of per TRX statistics 5 Power Control Measure-
TISTICS provides distributions, mean, ment,
minimum and maximum values 60 C/I Ratio Measurement,
for the different contents of Mea-
77 FER Measurement,
surement Results for both
downlink and uplink paths e.g. 137 Precise Power Level
RxQual, path loss, transmit Measurement,
power, timing advance. Further 139 Air Path Loss Mea-
statistics cover FER and interfer- surement,
ence on idle measurements.
(70 Channel Finder Mea-
surement, 75 Defined
Adjacent Cell Measure-
ment, 99 Total FEP Mea-
surement)
Table 5 (Cont.)
46 Id:0900d805808934b3 DN0983176
Issue 01A
BSC product family

counter group group
PROCESSOR STA- This group of per processor sta- 6 Load Measurement
TISTICS tistics provides minimum and
maximum processor utilization g
Corresponding BSS
counters for processor
figures for BSC, PCU and BTS
load are available but
processors. Further statistics the
dfferent due to archi-
duration the GSR master BSC
tecture differences.
processor (BSP) is in safe and
critical overload situation and
the volume of BSSMAP
Overload messages exchanged
between the BSC and MSC on
the A-interface.
RADIO RESOURCE This group of predominantly per 1 Traffic Measurement,
AVAILABILITY & cell statistics is related to radio 2 Resource Availability
ALLOCATION STA- resource manager functionality, Measurement,
TISTICS principally for circuit switched
3 Resource Access Mea-
operation but also some limited
surement,
packet switched operation. The
statistics measure the availabil- 57 BSC Level Clear Code
ity of different radio channel (SERLEV) Measurement
types (SDCCH, Full Rate TCH,
Half Rate TCH, PDTCH) for allo-
cation, the number of successful
and unsuccessful activations of
different radio channel types and
the amount of traffic (measure in
Erlangs) carried by the different
radio channel types. There are
also specific statistics that
measure on a per zone, per fre-
quency band and per TRX basis
rather than the more general per
cell basis.
SCCP STATISTICS This group of statistics provides Supported locally by the
a mixture of per link and per cell following MML commands:
counters for SCCP messages OI,OL,OM,ON,OO,OS,OT
sent/received on the A interface
e.g. Connection Request, Con-
nection Refused, DT1, RLSD
and RLC SCCP messages.
Table 5 (Cont.)
DN0983176 Id:0900d805808934b3 47
Issue 01A
BSC product family

counter group group
X25 / LAPD STATIS- This group of statistics provides 226 Abis D-Channel Mea-
TICS a performance measurement for surement
a variety of signaling links
between the BTS, BSC and
other network elements. The
statistics are provided on a per
signaling link basis.
Table 5 (Cont.)
48 Id:0900d805808934b3 DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Counter list
BSC product family
7 Counter list
7.1 GSR counter list
GSR counter name Description Presence in KPI

formulas
AIR_DL_TBF_FAILU Tracks the total number of downlink GSR:
RES Temporary Block Flow (TBF) that are DL_TBF_FAILURE_
abnormally released in the different RATE
phases due to radio failures in a cell.
This statistic pegs each time a
downlink TBF is established and later
abnormally released due to radio
failures in a cell during a statistical
measurement interval. The statistic
pegs the appropriate bin depending
on the phase where the TBF was
abnormally released.
AIR_UL_TBF_FAILU Statistic tracks the total number of GSR:
RES uplink Temporary Block Flow that are UL_TBF_FAILURE_
abnormally released in the different RATE
phases due to radio failures in a cell.
This statistic pegs each time an uplink
TBF is established and later abnor-
mally released due to radio failures in
a cell during a statistical measurement
interval. The statistic pegs the appro-
priate bin depending on the phase
where the TBF was abnormally
released.
ALLOC_SDCCH_FAI The counter is pegged when the radio GSR:
L resource manager fails to service a SDCCH_BLOCKING
request to allocate an SDCCH _RATE
resource.
ALLOC_SDCCH The counter is pegged when the radio GSR:
resource manager successfully SDCCH_BLOCKING
services a request to allocate an _RATE
SDCCH resource.
ALLOC_TCH The counter is pegged when the radio GSR:
resource manager successfully TCH_BLOCKING_R
services a request to allocate an TCH ATE
resource.
ALLOC_TCH_FAIL The counter is pegged when the radio GSR:
resource manager fails to service a TCH_BLOCKING_R
request to allocate an TCH resource. ATE
Table 6 GSR counter list
DN0983176 Id:0900d80580874612 49
Issue 01A
Counter list KPI guidelines for Horizon BTS migration to the Flexi
BSC product family

formulas
ASSGN_REDIRECT This statistic tracks the number of GSR:
times the call assignment is redirected TCH_ALLOCATION
to another cell. _SUCCESS_RATE,
• 0 DIRECTED_RETRY - tracks the GSR:
handovers that were executed as CALL_VOLUME
the result of standard directed
retry.
• 1 DURING_ASSIGNMENTS -
tracks the handovers that
occurred during the assignment
for normal radio reasons.
• 2 MULTIBAND_BAND - tracks the
handovers that were executed as
the result of multiband reassign
procedure.
BSS_AVAILABILITY The statistic provides the percentage GSR:
of all radio timeslots capable of BSS_AVAILABILITY
carrying TCH or PDTCH traffic that
are available to be allocated in
response to a mobile request for a
circuit switched or packet switched
connection.The statistic is updated
every time the number of TCH or
PDTCHs in service changes. There is
a change to the availability statistics
AVAILABLE_TCH,
GPRS_AVAIL_PDTCH or
EGPRS_AVAIL_PDTC. The values
produced are accurate to 1ms.
BUSY_TCH_MEAN Average number of TCHs in use GSR: TCH DROPS /
during a statistics interval measured in ERLANG,
Erlangs. The radio resource manager GSR:
updates the running calculation of MEAN_TIME_BETW
busy TCHs during a statistics interval EEN_DROPS,
every time a TCH is allocated or deal-
GSR:
located. The calculation includes the
TCH_TRAFFIC_CA
guard time defined by 3GPP radio
RRIED
resource timers T3109 and T3111.
CHAN_REQ_MS_FA The counter is pegged on expiry of GSR:
IL 3GPP defined radio resource T3101. SDCCH_RF_LOSS_
Example case is when the BSS has RATE
sent an IMMEDIATE ASSIGNMENT
to the mobile station but no SABM was
received from the mobile station.
Table 6 GSR counter list (Cont.)
50 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
CHANNEL_REQS_R GPRS Channel Request in Packet GSR:
EC_CP_A Downlink ACK/NACK (PDAK) UL_TBF_SUCCESS
message is received. _RATE
CHANNEL_REQS_R Enhanced One-Phase (EOP) access GSR:
EC_E_C indication is received UL_TBF_SUCCESS
_RATE
CHANNEL_REQS_R EGPRS One-Phase access on CCCH GSR:
EC_EGPRS_1PH_C is received. UL_TBF_SUCCESS
C _RATE
CHANNEL_REQS_R EGPRS One-Phase access on GSR:
EC_EGPRS_1PH_P PCCCH is received. UL_TBF_SUCCESS
CC _RATE
CHANNEL_REQS_R EGPRS Channel Request in Packet GSR:
EC_EGPRS_CRQP Downlink ACK/NACK (PDAK) UL_TBF_SUCCESS
DAK message is received. _RATE
CHANNEL_REQS_R EGPRS Packet Resource Request is GSR:
EC_EGPRS_PKRS_ received UL_TBF_SUCCESS
RQ _RATE
CHANNEL_REQS_R GPRS One-Phase Access Channel GSR:
EC_P_C request is received. UL_TBF_SUCCESS
_RATE
CHANNEL_REQS_R GPRS One-Phase access packet GSR:
EC_P_P channel request on PCCCH is UL_TBF_SUCCESS
received. _RATE
CHANNEL_REQS_R GPRS Packet Resource Request GSR:
EC_P_R (PRR) message is received (second UL_TBF_SUCCESS
phase of two phase access). _RATE
CHANNEL_REQS_R Statistic tracks the number of channel GSR:
EC or resource request messages UL_TBF_SUCCESS
received by the PCU. This statistic _RATE
pegs for each channel request
message received. The bin that is
incremented is determined by the
channel request message type.
CHANNEL_REQS_S GPRS PUA in response to a channel GSR:
UCCESS_CP_A request received in a Packet Downlink UL_TBF_FAILURE_
ACK. RATE
CHANNEL_REQS_S EGPRS One-Phase Access Immedi- GSR:
UCCESS_E_1P_CC ate Assignment (IA) is sent on CCCH. UL_TBF_FAILURE_
C RATE
DN0983176 Id:0900d80580874612 51
Issue 01A
BSC product family

formulas
CHANNEL_REQS_S EGPRS One-Phase Access Packet GSR:
UCCESS_E_1P_PC Uplink Assignment (PUA) is sent on UL_TBF_FAILURE_
CC PCCCH. RATE
CHANNEL_REQS_S Enhanced One-Phase (EOP) Access GSR:
UCCESS_E_C indication is received on CCCH. UL_TBF_FAILURE_
RATE
CHANNEL_REQS_S EGPRS PTR is sent to establish a GSR:
UCCESS_E_PTR new TBF or to re-assign the downlink UL_TBF_FAILURE_
TBF (only the first PTR is counted). RATE
CHANNEL_REQS_S EGPRS PUA in response to a channel GSR:
UCCESS_E_PUAPD request in a PDAK. UL_TBF_FAILURE_
AK RATE
CHANNEL_REQS_S EGPRS PUA (in response to Packet GSR:
UCCESS_E_PUAPR Resource Request (PRR)) is sent to UL_TBF_FAILURE_
R establish a TBF (only the first PUA is RATE
counted).
CHANNEL_REQS_S PRS One-Phase Access Packet GSR:
UCCESS_P_C Immediate Assignment (PIA) is sent UL_TBF_FAILURE_
on CCCH. RATE
CHANNEL_REQS_S GPRS One-Phase Access Packet GSR:
UCCESS_P_P Uplink Assignment (PUA) is sent on UL_TBF_FAILURE_
PCCCH. RATE
CHANNEL_REQS_S GPRS PUA (in response to Packet GSR:
UCCESS_P_R Resource Request) is sent to estab- UL_TBF_FAILURE_
lish a TBF (only the first PUA is RATE
counted).
CHANNEL_REQS_S GPRS Packet Timeslot Reconfigura- GSR:
UCCESS_PKTS tion (PTR) is sent to establish a new UL_TBF_FAILURE_
TBF or to re-assign the downlink TBF RATE
(only the first PTR is counted)
CHANNEL_REQS_S The statistic counts the number of GSR:
UCCESS channel or resource requests that UL_TBF_FAILURE_
allocates a TBF resource success- RATE
fully. This statistic specifically counts
the number of ASSIGNMENT
messages sent to the MS. This statis-
tic pegs for each channel request
message granted on the downlink.
The bin that is incremented is deter-
mined by the channel request
message type
52 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
CLR_CMD_FROM_ Provides number of CLEAR GSR:
MSC_FR COMMANDs received from the MSC TCH_DROP_RATE
to release a full rate TCH. Counter
covers both normal and abnormal
releases.
CLR_CMD_FROM_ Provides number of CLEAR GSR:
MSC_HR COMMANDs received from the MSC TCH_DROP_RATE
to release a half rate TCH. Counters
covers both normal and abnormal
releases.
CLR_REQ_TO_MSC Provides number of CLEAR GSR:
_FR REQUESTs sent to the MSC for an TCH_DROP_RATE
abnormal release of a full rate TCH.
CLR_REQ_TO_MSC Provides number of CLEAR GSR:
_HR REQUESTs sent to the MSC for an TCH_DROP_RATE
abnormal release of a half rate TCH
DL_PDTCH_SEIZUR The statistics measures the success- GSR:
E ful Packet Data Traffic Channel DL_TBF_SUCCESS
(PDTCH) seizure on the downlink. _RATE
This statistic counts the number of
TBFs on the downlink. The statistic is
obtained by measuring the receipt of
the first RLC block on the PDTCH
from the network. This statistic is
pegged each time a DL TBF is suc-
cessfully established and the MS is
listening on the PDTCH.
DL_RLC_ACK_NEW The statistic measures the total GSR:
_BLKS number of new RLC acknowledge UL_USER_TRAFFIC
mode blocks received sent for the first _GPRS,
time) by the PCU over the cell. One DL_USER_TRAFFIC
unit represents 100 RLC radio blocks. _GPRS
The maximum statistical interval is 60
minutes. The translation of actual
radio blocks counted to units is per-
formed at the end of the interval. The
RLC radio blocks are split into the four
GPRS channel coding schemes and
the nine EGPRS.
DN0983176 Id:0900d80580874612 53
Issue 01A
BSC product family

formulas
DL_RLC_UNACK_N The statistic measures the total GSR:
EW_BLKS number of new RLC unacknowledge UL_USER_TRAFFIC
the nine EGPRS.
EGPRS_DL_ASGN_ The statistics counts the total number GSR:
PCCCH of EGPRS packet downlink assign- DL_TBF_SUCCESS
ments sent on the PCCCH. This sta- _RATE
tistic pegs whenever an EGPRS
packet downlink assignment is sent
on PCCCH.
GPRS_ACCESS_PE The counter tracks the number of GSR:
R_RACH packet switched Channel Request GPRS_ACCESS_PE
messages successfully received on R_RACH
the Random Access CHannel (RACH)
for GPRS purposes. This statistic
pegs when a packet switched
Channel Request message is sent on
the Random Access CHannel (RACH)
of a cell.This statistic is pegged for
both GPRS and EGPRS events.
GPRS_DL_ASGN_P The statistics counts the total number GSR:
CCCH of GPRS packet downlink assign- DL_TBF_SUCCESS
ments sent on the PCCCH. This sta- _RATE
tistic pegs whenever an GPRS packet
downlink assignment is sent on
PCCCH.
IMM_ASSGN_CAUS The counter is pegged when sending GSR:
E an IMMEDIATE ASSIGNMENT to the IMMEDIATE_ASSIG
mobile after dedicated resources are NMENT_ACCESS_
successfully allocated and activated RATE,
and the appropriate bin is pegged. GSR:
IMMEDIATE_ASSIG
N_SUCCESS_RATE
GSR:
IMMEDIATE_ASSIG
N_ACCESS_RATE
54 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
IN_INTER_BSS_HO Number of mobiles successfully GSR:
_SUC accessing a TCH via an incoming inter DROP_CALL_RATE
BSS handover.
IN_INTRA_BSS_HO Number of mobiles successfully GSR:
_SUC accessing a TCH via an incoming intra DROP_CALL_RATE
BSS handover.
INTRA_CELL_HO[int The counter is pegged when an GSR: INTRA_CELL_
ra_cell_ho_atmpt_fr_ ASSIGNMENT COMMAND is sent to HO_SUCCESS_RA
fr] the mobile station to move the mobile TE
station from a Full Rate traffic channel
to a new Full Rate traffic channel.
ra_cell_ho_atmpt_fr_ ASSIGNMENT COMMAND is sent to HO_SUCCESS_RA
hr] the mobile station to move the mobile TE
station from a Full Rate traffic channel
to a new Half Rate traffic channel.
ra_cell_ho_atmpt_hr ASSIGNMENT COMMAND is sent to HO_SUCCESS_RA
_fr] the mobile station to move the mobile TE
station from a Half Rate traffic channel
to a new Full Rate traffic channel
ra_cell_ho_atmpt_hr ASSIGNMENT COMMAND is sent to HO_SUCCESS_RA
_hr] the mobile station to move the mobile TE
station from a Half Rate traffic channel
to a new Half Rate traffic channel.
ra_cell_ho_atmpt_sd ASSIGNMENT COMMAND is sent to HO_SUCCESS_RA
_to_sd] the mobile station to move the mobile TE
station from an SDCCH to a new
SDCCH channel
INTRA_CELL_HO[int The counter is pegged when GSR: INTRA_CELL_
ra_cell_ho_suc] HANDOVER PERFORMED is sent to HO_SUCCESS_RA
the MSC after receipt of an ASSIGN- TE
MENT COMPLETE from the mobile
station
INTRA_CELL_HO_A Number of ASSIGNMENT GSR:
TMPT_FR_FR COMMANDS sent to a mobile station HANDOVER_SUCC
for an intra cell handover from a full ESS_RATE
rate TCH to a full rate TCH GSR:
HANDOVER_FAILU
RE_RATE
DN0983176 Id:0900d80580874612 55
Issue 01A
BSC product family

formulas
TMPT_FR_HR COMMANDS sent to a mobile station HANDOVER_SUCC
for an intra cell handover from a full ESS_RATE
rate TCH to a half rate TCH. GSR:
HANDOVER_FAILU
RE_RATE
TMPT_HR_FR COMMANDS sent to a mobile station HANDOVER_SUCC
for an intra cell handover from a half ESS_RATE
rate TCH to a full rate TCH. GSR:
HANDOVER_FAILU
RE_RATE
TMPT_HR_HR COMMANDS sent to a mobile station HANDOVER_SUCC
for an intra cell handover from a half ESS_RATE
rate TCH to a half rate TCH. GSR:
HANDOVER_FAILU
RE_RATE
TMPT_SD_TO_SD COMMANDS sent to a mobile station HANDOVER_SUCC
for an intra cell handover from an ESS_RATE
SDCCH to an SDCCH. GSR:
HANDOVER_FAILU
RE_RATE
INTRA_CELL_HO_L Number of intra cell handovers where GSR:
OSTMS the mobile station fails to establish on HANDOVER_FAILU
the target cell, fails to recover to the RE_RATE,
source cell and returns to idle mode. GSR: TCH DROPS /
ERLANG,
GSR:
MEAN_TIME_BETW
EEN_DROPS
GSR:
DROP_CALL_RATE
INTRA_CELL_HO_R The counter is pegged when an GSR:
ETURN ASSIGNMENT FAILURE is recieved SDCCH_USAGE_S
from the mobile station in relation to a UCCESS_RATE,
failed intra cell handover. GSR: TCH ALLOCA-
TION SUCCESS
RATE
56 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
INTRA_CELL_HO_S Number of ASSIGNMENT GSR:
UC COMPLETE received messages on HANDOVER_SUCC
successful completion of an intra cell ESS_RATE
handover.
MA_CMD_TO_MS_B The counter is pegged when the radio GSR: CALL_SET-
LKD resource manager fails to allocate a UP_BLOCKING_RA
radio resource in response to an TE
ASSIGNMENT REQUEST from the
MSC.
MA_COMPLETE_TO The counter is pegged when an GSR:
_MSC ASSIGNMENT COMPLETE is sent ASSIGNMENT_SUC
from the BSC to the MSC. CESS_RATE
MA_FAIL_FROM_M The counter is pegged when an GSR:
S ASSIGNMENT FAILURE is received SDCCH_USAGE_S
from the mobile station. This includes UCCESS_RATE,
ASSIGNMENT COMPLETE GSR: TCH ALLOCA-
messages related to call set-up, intra TION SUCCESS
cell handovers and any repeated RATE
assignment attempts.
MA_REQ_FROM_M The counter is pegged when the BSC GSR: TCH ALLOCA-
SC receives an ASSIGNMENT TION SUCCESS
REQUEST from the MSC. RATE,
GSR: CALL_SET-
UP_BLOCKING_RA
TE,
GSR:
ASSIGNMENT_SUC
CESS_RATE
OK_ACC_PROC_SU The counter is pegged on receipt of GSR:
C_RACH CHANNEL REQUEST with a circuit IMMEDIATE_ASSIG
switched establishment cause. NMENT_ACCESS_
RATE,
GSR:
CIRCUIT_SWITCHE
D_SYSTEM_ACCES
SES,
GSR:
IMMEDIATE_ASSIG
N_ACCESS_RATE
DN0983176 Id:0900d80580874612 57
Issue 01A
BSC product family

formulas
OK_ACC_PROC The counter is pegged when a mobile GSR:
station successfully allocates an SDCCH_USAGE_S
SDCCH or signaling TCH resource UCCESS_RATE,
allocated via IMMEDIATE ASSIGN- GSR:
MENT. CIRCUIT_SWITCHE
D_SYSTEM_ACCES
SES,
GSR:
IMMEDIATE_ASSIG
N_SUCCESS_RATE
OUT_HO_CAUSE_A Number of outgoing inter cell GSR: HO_CAUSE
TMPT[CAUSE 'X'] handover attempts for a particular
cause.
OUT_HO_CAUSE_A The counter is pegged for the appro- GSR: HO_CAUSE
TMPT priate cause when a HANDOVER
COMMAND is sent to the mobile
station for an inter cell handover. The
counter does not peg for intra cell han-
dovers. It represents the sum of
HANDOVER COMMANDS for all
causes
OUT_INTER_BSS_H Number of HANDOVER COMMANDS GSR:
O_ATMPT sent to a mobile station for an inter HANDOVER_SUCC
BSS handover. ESS_RATE
GSR:
HANDOVER_FAILU
RE_RATE,
GSR:
INTER_BSS_HO_S
UCCESS_RATE
OUT_INTER_BSS_H From the perspective of the source GSR: TCH DROPS /
O_EQUIP_FAIL cell, the number of mobiles dropped ERLANG,
due to BSS equipment failure during GSR:
an inter BSS handover. MEAN_TIME_BETW
EEN_DROPS,
GSR:
DROP_CALL_RATE
58 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
OUT_INTER_BSS_H From the perspective of the source GSR: TCH DROPS /
O_FAIL cell, the number of mobiles dropped ERLANG,
due to RF reasons during an inter BSS GSR:
handover. MEAN_TIME_BETW
EEN_DROPS,
GSR:
DROP_CALL_RATE
OUT_INTER_BSS_H Number of HANDOVER COMPLETE GSR:
O_SUC received messages on successful HANDOVER_SUCC
completion of an inter BSS handover. ESS_RATE,
GSR:
INTER_BSS_HO_S
UCCESS_RATE
OUT_INTRA_BSS_H Number of HANDOVER COMMANDS GSR:
O_ATMPT sent to a mobile station for an intra HANDOVER_SUCC
BSS handover. ESS_RATE,
GSR:
HANDOVER_FAILU
RE_RATE,
GSR:
INTRA_BSS_HO_S
UCCESS_RATE
OUT_INTRA_BSS_H Number of inter cell handovers where GSR:
O_EQUIP_FAIL the mobile is dropped due to an equip- HANDOVER_FAILU
ment failure. RE_RATE
OUT_INTRA_BSS_H Number of inter cell handovers where GSR:
O_FAIL the mobile station fails to establish on HANDOVER_FAILU
the target cell, fails to recover to the RE_RATE
source cell and returns to idle mode.
OUT_INTRA_BSS_H Number of intra BSS handovers GSR: TCH DROPS /
O_LOSTMS where the mobile station fails to estab- ERLANG,
lish on the target cell, fails to recover GSR:
to the source cell and returns to idle HANDOVER_FAILU
mode. RE_RATE,
GSR:
MEAN_TIME_BETW
EEN_DROPS
GSR:
DROP_CALL_RATE
DN0983176 Id:0900d80580874612 59
Issue 01A
BSC product family

formulas
OUT_INTRA_BSS_H Number of HANDOVER COMPLETE GSR:
O_SUC received messages on successful HANDOVER_SUCC
completion of an intra BSS handover. ESS_RATE,
GSR:
INTRA_BSS_HO_S
UCCESS_RATE
RF_LOSSES_SD The counter is pegged when an GSR:
SDCCH resource is released on SDCCH_USAGE_S
receipt of an RELEASE INDICATION UCCESS_RATE,
from the radio subsystem due to T200 GSR:
expiry N200 times or loss of uplink SDCCH_RF_LOSS_
SACCH. RATE
RF_LOSSES_TCH Number of mobiles dropped from a GSR: TCH DROPS /
TCH due to loss of uplink SACCH or ERLANG,
T200 timeout N00 times. Such drops GSR:
are experienced during any handover MEAN_TIME_BETW
procedures. EEN_DROPS,
GSR:
DROP_CALL_RATE
SECOND_ASSIGN_ The counter is pegged when a second GSR: TCH ALLOCA-
ATMPT ASSIGNMENT COMMAND is sent to TION SUCCESS
the mobile station in response to RATE,
receipt of an ASSIGNMENT FAILURE GSR:
from the mobile station for the initial SDCCH_USAGE_S
ASSIGNMENT COMMAND. UCCESS_RATE
SIG_IN_INTER_BSS Number of mobiles successfully GSR:
_HO_SUC accessing an SDCCH or signaling DROP_CALL_RATE
TCH via an incoming inter BSS han-
dover.
SIG_IN_INTRA_BSS Number of mobiles successfully GSR:
_HO_SUC accessing an SDCCH or signaling DROP_CALL_RATE
TCH via an incoming intra BSS han-
dover.
SIG_INTRA_CELL_ Number of mobiles dropped during an GSR: TCH DROPS /
HO_LOSTMS SDCCH or signaling TCH intra call ERLANG,
handover. GSR:
MEAN_TIME_BETW
EEN_DROPS,
GSR:
DROP_CALL_RATE
60 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
SIG_OUT_INTER_B From the perspective of the source GSR: TCH DROPS /
SS_HO_EQUIP_FAI cell, the number of mobiles dropped ERLANG,
L due to BSS equipment failure during GSR:
an SDCCH or signaling TCH inter MEAN_TIME_BETW
BSS handover EEN_DROPS,
GSR:
DROP_CALL_RATE
SIG_OUT_INTER_B From the perspective of the source GSR: TCH DROPS /
SS_HO_FAIL cell, the number of mobiles dropped ERLANG,
due to RF reasons during an SDCCH GSR:
or signaling TCH inter BSS handover. MEAN_TIME_BETW
EEN_DROPS,
GSR:
DROP_CALL_RATE
SIG_OUT_INTRA_C From the perspective of the source GSR: TCH DROPS /
ELL_HO_LOSTMS cell, the number of mobiles dropped ERLANG,
during an SDCCH or signaling TCH GSR:
intra BSS handover. MEAN_TIME_BETW
EEN_DROPS,
GSR:
DROP_CALL_RATE
TBF_DL_ASGN_PA Statistics represents the total number GSR:
CCH of Packet Downlink Assignments and DL_TBF_SUCCESS
Packet Timeslot Reconfigure sent by _RATE
the PCU using PACCH channel to
establish new downlink TBF. This sta-
tistic pegs whenever a PDA or PTR is
sent on PACCH to establish new
downlink TBF.
TCH_PREEMPT_TC Number of times a TCH resource is GSR:
H_NO_Q_ALLOC_A allocated within a cell after a TCH pre- TCH_BLOCKING_R
LL emption. ATE
TCH_Q_REMOVED Number of requests for TCH resource GSR:
that were initially blocked, queued and TCH_BLOCKING_R
then removed from the queue, and ATE
also serviced successfully with the
allocation of a TCH resource.
DN0983176 Id:0900d80580874612 61
Issue 01A
BSC product family

formulas
TOTAL_CALLS The statistic counts number of GSR:
mobiles that successfully complete TCH_ALLOCATION
TCH assignment at the call set-up _SUCCESS_RATE,
GSR: CALL_SET-
UP_SUCCESS_RAT
E,
GSR:
CALL_VOLUME
GSR:
DROP_CALL_RATE
UL_PDTCH_SEIZUR The statistic measures successful GSR:
E Packet Data Traffic Channel (PDTCH) UL_TBF_SUCCESS
seizure on the uplink. This statistic _RATE
counts the number of temporary block
flows on the uplink. The statistic is
obtained by measuring the receipt of
the first RLC block (PDU) on the
PDTCH from the MS. This statistic
pegs when the receipt of the first
uplink RLC block on the PDTCH from
the MS is obtained. This statistic is
updated when: the first uplink data
block is received during a two-phase
uplink TBF establishment and the first
uplink data block containing a valid
Temporary Logical Link Identity (TLLI)
is received during a one-phase uplink
TBF establishment.
UL_RLC_ACK_NEW The statistic measures the total GSR:
_BLKS number of new RLC acknowledge UL_USER_TRAFFIC
the nine EGPRS.
62 Id:0900d80580874612 DN0983176
Issue 01A
BSC product family

formulas
UL_RLC_UNACK_N The statistic measures the total GSR:
EW_BLKS number of new RLC unacknowledge UL_USER_TRAFFIC
the nine EGPRS.
DN0983176 Id:0900d80580874612 63
Issue 01A
BSC product family
7.2 BSS counter list
Counter BSS counter Description Presence in

number name KPI formulas
1029 TCH_TR_FAIL Number of TCH transactions that are BSS: dcr_54b
ended because of a transcoder failure. Call Drop Rate
Counter is updated when a TCH trans-
action ends because of a transcoder
failure during a call attempt. These
failures can also contain situations
when the timer T3109 expires in a BSC
in call release phase while waiting for
the Release Indication. The MS sub-
scriber does not see these failures
caused by the T3109 expiry as real
dropcalls.
1084 TCH_ABIS_FAI Number of TCH transactions ended BSS: dcr_54b
L_CALL because of a failure in the Abis inter- Call Drop Rate
face during a call in progress. The sig-
nalling problems might include missing
acknowledgement of channel activa-
tion, missing indication of call estab-
lishment, receipt of an error indication,
corrupted messages, missing mea-
surement results from the BTS, exces-
sive timing advance or some internal
reasons. These failures can also
contain situations when the timer
T3109 expires in a BSC in call release
phase while waiting for the Release
Indication. The MS subscriber does not
see these failures caused by the T3109
expiry as real drop calls
001000 SDCCH_SEIZ_ Number of times when an MS attempts BSS: blck_5,
ATT to seize an SDCCH. Updated when the SDCCH block-
RRM receives requests for SDCCH ing, before
from an MS as the MS needs a channel FCS
for either a call or a hondover
Table 7 BSS counter list
64 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

001001 SDCCH_BUSY Number of times when an MS attempts BSS: blck_5,
_ATT to seize an SDCCH but the attempt is SDCCH block-
unsuccessful because all SDCCHs are ing, before
busy. This counter does not necessar- FCS
ily mean that the call attempt is lost,
because the call might be established
as an FACCH call setup using TCH
instead of SDCCH. This counter is not
triggered when the TCH reconfigura-
tion is attempted because of dynamic
SDCCH allocation. If the attempt fails,
the SDCCH_BUSY_ATTEMPT is trig-
gered together with 1155
UNSUCC_IMM_ASS_SDCCH_ATTE
MPT. Counter is updated when the
RRM has no SDCCHs to allocate for a
call or handover attempts
001003 SDDCH_RADI Number of SDCCH transactions ended BSS: csf_43b
O_FAIL because of a radio failure. When the SDCCH usage
SDCCH transaction ends because of a success rate,
radio failure (radio link timeout) the BSS: sdr_18a
RRM releases the SDCCH. This SDCCH RF
counter is updated in call phases 1-8 Loss Rate
only
001004 SDCCH_RF_O Number of SDCCH transactions ended BSS: csf_43b
LD_HO because of a radio failure on the source SDCCH usage
channel during a handover between success rate
SDCCH-SDCCH or SDCCH-TCH. This
counter is updated in the source cell. If
the target cell lies within the same
BSC, also counter 001005 in the target
cell is updated along with this counter.
The counter is updated when an
SDCCH transaction ends because of a
radio failure (handover failure) on the
source channel during a handover
attempt and after releasing the SDCCH
by RRM. This counter is updated only
in call phases 9-11.
001007 SDCCH_ASSI Number of successful seizures of BSS: sdr_18a
GN SDCCH for an immediate assignment. SDCCH RF
Updated when the RRM allocates an Loss Rate
SDCCH for an immediate assignment
in a call attempt.
Table 7 BSS counter list (Cont.)
DN0983176 Id:0900d8058087523d 65
Issue 01A
BSC product family

001010 TCH_REQUES Total number of requests for a TCH BSS: blck_1a,
T (successful and unsuccessful). Takes TCH call
into account incoming HO from 3G. blocking
When the RRM receives a request for
a TCH either in a call or a handover
attempt.
001011 TCH_REQ_RE Number of requests for TCHs that are BSS: blck_1a,
J_LACK rejected because there are no radio TCH call
resources available for either call or blocking
handover attempts. This counter is also
updated when a request for TCH is
rejected because of a mismatch
between the types of the requested
channel and the A interface circuit.
Updated when the RRM has no TCHs
available for either call or HO attempt
requests, or the RRM changes the A
interface circuit pool before the TCH
allocation. This counter might be
updated immediately after a TCH
request or, in case of queuing, when
the queuing timer expires.
001013 TCH_RADIO_F Number of TCH transactions ended BSS: dcr_29
AIL because of a radio failure. The RRM TCH drop
releases the TCH when a TCH transac-
tion ends because of a radio failure.
This counter is typical in connection
with coverage problems. ERROR INDI-
CATION is sent by the BTS to the BSC
in the following cases:
• sequence error in a received
message (the case where retrans-
mission is not possible),
• timer T200 has expired N200 +1
times (MS does not respond any
more),
• unsolicited DM response when link
is established. This counter is
updated in call phases 1-8 or 15
only.
66 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

001014 TCH_RF_OLD Number of TCH transactions ended BSS: dcr_29
_HO because of a radio failure on the source TCH drop,
channel during a handover attempt. BSS: dcr_54b
When a TCH transaction ends because Call Drop Rate
of a radio failure (handover failure) on
the source channel during a handover
attempt to counter is registered. This
counter is updated in call phases 9 to
11 only.
001030 TCH_TR_FAIL Number of TCH transactions ended BSS: dcr_29
_OLD because of a transcoder failure on the TCH drop
source channel during a handover on a
TCH. When a TCH transaction ends
because of a transcoder failure on the
source channel during a handover
attempt and the RRM releases the
TCH the counter is updated. This
happens before the RRM receives a
message from the MS stating the
handover or the assignment is com-
pleted. This counter is updated only in
call phases 9 to 11.
001035 SDCCH_LAPD Number of SDCCH transactions ended BSS: csf_43b
_FAIL because of the LAPD failure. When an SDCCH usage
SDCCH transaction ends because of a success rate
TRX blocked by an LAPD failure, the
RRM releases the SDCCH.
001036 SDCCH_BTS_ Number of SDCCH transactions ended BSS: csf_43b
FAIL because of the BTS failure. The SDCCH usage
SDCCH is released when an SDCCH success rate
transaction ends because of a TRX
being blocked by a BTS failure.
001037 SDCCH_USER Number of SDCCH transactions ended BSS: csf_43b
_ACT because of user actions. When the SDCCH usage
user disconnects a busy SDCCH by success rate
blocking the TSL/TRX with an MML
command the transaction ends and the
SDCCH is released.
DN0983176 Id:0900d8058087523d 67
Issue 01A
BSC product family

001038 SDCCH_BCSU Number of SDCCH transactions ended BSS: csf_43b
_RESET because of a BCSU restart. The BCSU SDCCH usage
restarts trigger the SDCCH release. success rate
When an SDCCH transaction ends
because of a TRX blocked by a BCSU
restart the the SDCCH is released by
RRM
001039 SDCCH_NET Number of SDCCH transactions ended BSS: csf_43b
W_ACT because of the radio network reconfig- SDCCH usage
uration. The SDCCH transaction ends success rate
because of a TRX blocked by a failure
which leads to TRX reconfiguration.
The failure might occur both during call
and handover attempts.
001044 TCH_FAST_S Number of successful seizures of BSS: cssr_8a
EIZ TCHs in FACCH call setup. When the Call setup
RRM allocates a TCH as a response to success rate
an SDCCH request as part of the
FACCH call setup because of no
SDCCHs being idle the counter is
updated.
001046 TCH_LAPD_F Number of TCH transactions ended BSS: dcr_29
AIL because of an LAPD failure. When a TCH drop
TCH transaction ends because of a
TRX blocked by an LAPD failure and
the RRM releases the TCH the counter
is updated.
001047 TCH_BTS_FAI Number of TCH transactions ended BSS: dcr_29
L because of a BTS failure. Counter TCH drop
update is done after the RRM releases
the TCH because of the BTS failure.
001048 TCH_USER_A Number of TCH transactions ended BSS: dcr_29
CT because of user actions. Counter TCH drop
update is done a after the user discon-
nection form the busy TCH by blocking
the TSL/TRX with an MML command.
The transaction ends and the TCH is
released.
001049 TCH_BCSU_R Number of TCH transactions ended BSS: dcr_29
ESET because of a BCSU restart. TCH drop
68 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

001050 TCH_NETW_A Number of TCH transactions ended BSS: dcr_29
CT because of the radio network reconfig- TCH drop
uration. Counter is updated when a
TCH transaction ends because of a
TRX blocked by a failure which leads to
TRX reconfiguration.
001076 SDCCH_ABIS_ Number of SDCCH transactions ended BSS: csf_43b
FAIL_OLD because of a failure in the Abis inter- SDCCH usage
face on the source channel during success rate
SDCCH-SDCCH or SDCCH-TCH han-
dover. The SDCCH is released by
RRM when SDCCH transaction ends
because of a failure in the Abis inter-
face on the source channel during a
handover and. This counter is updated
only in call phases 9-11.
001081 TCH_ACT_FAI Number of TCH transactions ended BSS: dcr_29
L_CALL because of channel activation failure TCH drop
during a call attempt. After the TCH
transaction ends because of the
channel activation failure in the BTS
the RRM releases the TCH. This
counter is updated only in call phases 1
to 8.
001085 TCH_ABIS_FAI Number of TCH transactions ended BSS: dcr_29
L_OLD because of a failure in the Abis inter- TCH drop
face on the source channel during a
TCH handover. When a TCH transac-
tion ends because of a failure in the
Abis interface on the source channel
during a TCH handover the RRM
releases the TCH, then counter is
updated. This counter is updated only
in call phases 9 to 11.
001192 TCH_REQUES Number of TCH channel requests for a BSS: blck_8i,
TS_CALL_ATT call. Updated while a TCH is requested Call Set-Up
EMPT for a call. The counter is updated only Blocking Rate
once for every call attempt.
001193 SUCC_TCH_S Number of successful TCH channel BSS: blck_8i,
EIZ_CALL_AT seizures for a call. Updated when a Call Set-Up
TEMPT TCH is successfully allocated for a call. Blocking Rate
The counter is updated only once for
every call attempt.
DN0983176 Id:0900d8058087523d 69
Issue 01A
BSC product family

001099 TCH_SEIZ_DU Number of successful TCH seizures BSS: blck_1a,
E_SDCCH_CO because of congestion on the SDCCH. TCH call
N The RRM allocates a TCH as a blocking
response to a request for SDCCH
seizure during congestion on the
SDCCHs and then the counter is
updated.
001122 TCH_REJ_DU Number of requests for TCHs that are BSS: blck_1a,
E_REQ_CH_A rejected because of a mismatch TCH call
_IF_CRC between the types of the requested blocking
channel and the A interface circuit,
whether queuing occurred or not.
When the RRM changes the A inter-
face circuit pool before TCH allocation.
001165 TCH_SUCC_S Number of successful seizures for a BSS: cssr_8a
EIZ_FOR_DIR TCH in direct accesses to a super- Call setup
_ACC reuse TRX during the call setup phase. success rate
When the RRM allocates a TCH as a
response to a TCH request in a call
attempt using direct access to a super-
reuse TRX procedure the counter is
updated.
001192 TCH_REQUES Number of TCH channel requests for a BSS: csf_44b
TS_CALL_ATT call. Updated when a TCH is requested TCH allocation
EMPT for a call. The counter is updated only success rate
once for every call attempt. If the
seizure of TCH is successful, the
counter is updated to the BTS from
which the TCH was successfully sei-
zured. In case the seizure is unsuc-
cessful, the counter is updated to the
BCCH BTS.
001193 SUCC_TCH_S Number of succesful TCH channel BSS: csf_44b
EIZ_CALL_AT seizures for a call. The counter is TCH allocation
TEMPT updated only once for every call success rate
attempt and it is not updated for TCH-
TCH handover attempts.
001195 MSC_O_HO_C Number of handover commands sent BSS: hsr_28
MD by the BSC in an outgoing MSC-con- Total handover
trolled handover. success ratio,
BSS: hsr_34a
Inter BSS HO
Success Rate
70 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

001196 BSC_O_HO_C Number of all handover commands BSS: hsr_28
MD_ASSGN sent by the BSC in an outgoing BSC- Total handover
controlled handover. success ratio,
BSS: hsr_33a
Intra BSS HO
Success Rate
001197 BTS_HO_ASS Number of assignment commands BSS: hsr_28
GN sent in intra-BTS handovers. Total handover
success ratio,
BSS: hsr_32a
Intra cell HO
Success Rate
001205 TCH_REL_DU Number of the TCH releases because BSS: dcr_29
E_RAD_FAIL_ of the radio failures. Counter 001139 is TCH drop,
PH_2_3 updated together with this counter. BSS: dcr_54
When the TCH is released in call phase Call Drop Rate
2 (MM signalling) or 3 (Basic assign-
ment) because of a radio failure
counter is updated.
002027 AVE_BUSY_T Sum of the busy TCH timeslots BSS: dcr_26a
CH samples. The average value is calcu- TCH drop /
lated by dividing the value of this Erlang (before
counter by the value of counter 002028 re-establish-
RES AVAIL DENOMINATOR 14. The ment)
002028 counter is updated along with
this counter. The number of busy TCH
timeslots is sampled every 20 seconds.
When HR capable timeslot has both
channels occupied the number of busy
TCHs is updated for both TCHs individ-
ually.
002028 RES_AV_DEN Number of samples of busy TCH BSS: dcr_26a
OM14 timeslots. Denominator of counter TCH drop /
002027 AVE BUSY TCH is always Erlang (before
bigger than 0. The 002027 counter is re-establish-
updated along with this counter. The ment)
counter is incremented every 20
seconds when sample of number of
busy TCH timeslots is taken.
DN0983176 Id:0900d8058087523d 71
Issue 01A
BSC product family

002034 AVE_SDCCH_ Average time that SDCCHs are busy. BSS: trf_490
HOLD_TIM The average value is calculated by SDCCH Traffic
dividing the value of this counter by the Carried
value of the next counter. The mea-
surement period starts when an
SDCCH is allocated and ends when
the SDCCH is released and marked
free.
002036 AVE_FTCH_H Length of the reservation summed up BSS: trf_489
OLD_TIM into the counter at the release of TCH. TCH traffic
Unit of the counter is 10 ms. carried,
BSS: dcr_55a
Mean Time
Between Drops
002059 AVE_AVAIL_T Average number of available TCHs. BSS: ava_1g
CH_SUM The average value is calculated by TCH availabil-
dividing the value of this counter by the ity ratio
value of the next counter. Counter
002060 is updated along with this
counter. The counter is sampled every
20 seconds.
002060 AVE_AVAIL_T Denominator of the average number of BSS: ava_1g
CH_DEN available TCHs.The value is always TCH availabil-
bigger than 0. Counter 002059 is ity ratio
updated along with this counter.
002061 AVE_GPRS_C Average number of radio time slots BSS: ava_1g
HANNELS_SU delivered for GPRS use. The average TCH availabil-
M value is calculated by dividing the value ity ratio
of this counter by the value of the next
counter. The counter value does not
indicate how many time slots has
actually been used for GPRS traffic.
Counter 002062 is updated along with
this counter. Counter is updated when
the GPRS territory of the BTS is
upgraded or downgraded. The counter
is sampled every 20 seconds.
002062 AVE_GPRS_C Denominator of the average number of BSS: ava_1g
HANNELS_DE GPRS channels. The value is always TCH availabil-
N bigger than 0. Counter 002061 is ity ratio
72 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

002069 AVE_NON_AV Average number of the TCH timeslots BSS: ava_1g
AIL_TCH_TIM not available. Counter is updated when TCH availabil-
ESLOT TCH timeslot is not available, it is ity ratio
sampled every 20 seconds.
002070 NON_AVAIL_T Denominator of the average number of BSS: ava_1g
CH_DENOM the TCHs timeslots not available. The TCH availabil-
value is always bigger than 0. The ity ratio
counter is increased by every 20
seconds.
003001 IMM_ASSGN_ Number of BSS: trf_467a
SENT IMMEDIATE_ASSIGN_COMMAND Immediate
messages sent to the BTS. Counted assignment
when the success rate,
IMMEDIATE_ASSIGN_COMMAND BSS: trf_486a
message is sent to the BTS. Immediate
assignment
success rate%,
BSS: trf_467a
Immediate
assignment
access rate,
BSS: trf_487
Circuit
switched
system access
003002 IMM_ASSGN_ Number of BSS: trf_467a
REJ IMMEDIATE_ASSIGNMENT_REJEC Immediate
T messages sent to the BTS. This assignment
counter is updated when an success rate,
IMMEDIATE_ASSIGNMENT_REJEC BSS: trf_467a
T message is packed and sent to the Immediate
BTS. The message can include one to assignment
four immediate assignment rejects. access rate,
The
BSS: trf_487
IMMEDIATE_ASSIGNMENT_REJEC
T message is sent to MS in the follow- Circuit
switched
ing cases:
system access
• No free SDCCH.
• Abis interface process has no
internal resources to handle the
request.
DN0983176 Id:0900d8058087523d 73
Issue 01A
BSC product family

003005 DEL_IND_MS Number of DELETE_INDICATION BSS: trf_467a
G_REC messages received from the BTS. Immediate
BTS sends the DELETE INDICATION assignment
message each time when IMMEDIATE success rate,
ASSIGNMENT or IMMEDIATE BSS: trf_467a
ASSIGNMENT REJECT message is Immediate
lost, for example due to BTS buffer assignment
overflown. Counter is updated when access rate
the DELETE_INDICATION message is
received from the BTS.
003012 SUCC_SEIZ_T Number of successful seizures of BSS: cssr_8a
ERM SDCCHs for an MTC. When an Call setup
ESTABLISH_INDICATION message success rate
with paging response is received on
SDCCH from the BTS.
003013 SUCC_SEIZ_O Number of successful seizures for BSS: cssr_8a
RI SDCCH for an MOC. When an Call setup
ESTABLISH_INDICATION message success rate
with CM service request is received on
SDCCH from the BTS. This counter is
updated also in case of an SMS or
Supplementary Service Requests.
003020 SDCCH_CALL Number of successful SDCCH BSS: cssr_8a
_RE_EST seizures for call re-establishment Call setup
attempts. When an success rate
ESTABLISHMENT_INDICATION
message for a call re-establishment is
received on SDCCH from the BTS.
This counter counts only the number of
re-establisment attempts on SDCCH.
The counter 057022 gives the number
of SDCCH re-establishment assign-
ments.
003021 SDCCH_EMER Number of successful seizures of BSS: cssr_8a
G_CALL SDCCHs for an emergency call. Call setup
When an ESTABLISH_INDICATION success rate
message for an emergency call is
received on SDCCH from the BTS.
74 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

003028 SUCC_SDCCH Number of SMSs successfully estab- BSS: cssr_8a
_SMS_EST lished on an SDCCH. The counter is Call setup
updated when an success rate
ESTABLISH_INDICATION message
(mobile originating SMS) or an
ESTABLISH_CONFIRM message
(mobile terminating SMS) is received
on SDCCH from the BTS.
003029 UNSUCC_SDC Number of unsuccessful establish- BSS: cssr_8a
CH_SMS_EST ments of SMSs on an SDCCH. After Call setup
the establishment of an SMS fails on success rate
SDCCH the counter is updated.
003044 SUCC_SEIZ_S Number of successful seizures of BSS: cssr_8a
UPPLEM_SER SDCCHs for supplementary service. Call setup
V Counter update goes after an success rate
ESTABLISH_INDICATION message
with CM service request and service
type supplementary service is received
on SDCCH from the BTS.
003059 CALL_ASSIGN Number of calls started directly after an BSS: cssr_8a
_AFTER_SMS SMS on the already reserved SDCCH. Call setup
When an ASSIGNMENT REQUEST success rate
message is received directly after a
successful SMS on SDCCH from the
MSC.
004004 MSC_O_SUCC Number of successful outgoing han- BSS: hsr_28
_HO dovers controlled by the MSC. This Total handover
counter is updated when one of the success ratio,
counters 004049, 004050 or 004051 is BSS: hsr_34a
updated. This counter represents their Inter BSS HO
sum. Updated when the handover is Success Rate
completed.
004014 BSC_O_SUCC Number of successful outgoing han- BSS: hsr_28
_HO dovers controlled by the BSC. This Total handover
counter is updated when one of the success ratio,
counters 004064, 004065 or 004066 is BSS: hsr_33a
updated. This counter represents their Intra BSS HO
sum. Updated when the handover is Success Rate
completed.
DN0983176 Id:0900d8058087523d 75
Issue 01A
BSC product family

004018 CELL_SUCC_ Number of successful intra-cell han- BSS: hsr_28
HO dovers. This counter is updated when Total handover
one of the counters 004073, 004074 or success ratio,
004075 is updated. This counter repre- BSS: hsr_32a
sents their sum. Updated when the Intra cell HO
handover is completed. Success Rate
004023 HO The handover cause is UPLINK BSS: HO Distri-
CAUSE_UP_Q QUALITY. bution
UAL
004024 HO The handover cause is UPLINK BSS: HO Distri-
CAUSE_UP_L LEVEL. bution
EVEL
004025 HO The handover cause is DOWNLINK BSS: HO Distri-
CAUSE_DOW QUALITY. bution
N_QUAL
004026 HO The handover cause is DOWNLINK BSS: HO Distri-
CAUSE_DOW LEVEL. bution
N_LEV
004027 HO The handover cause is DISTANCE. BSS: HO Distri-
CAUSE_DISTA bution
NCE
004029 HO The handover cause is HIGH INT ON BSS: HO Distri-
CAUSE_INTFE UPLINK. bution
R_UP
004030 HO The cause sighs INT ON DOWNLINK. BSS: HO Distri-
CAUSE_INTFE bution
R_DWN
004031 HO The handover cause is UMBRELLA. BSS: HO Distri-
CAUSE_UMBR bution
004032 HO The handover cause is POWER BSS: HO Distri-
CAUSE_PBDG BUDGET. bution
004043 MSC_I_TCH_T Number of successful incoming TCH to BSS: dcr_54b
CH TCH handovers controlled by the MSC. Call Drop Rate
Updated when the handover is com-
pleted.
004044 MSC_I_SDCC Number of successful incoming BSS: csf_44b
H_TCH SDCCH to TCH handovers controlled TCH allocation
by the MSC. Counter 004000 is success rate,
updated along with this counter. When BSS: trf_488
a directed retry procedure is com- Call Volume
pleted.
76 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

004050 MSC_O_SDCC Number of successful outgoing BSS: csf_44b
H_TCH SDCCH to TCH handovers controlled TCH allocation
by the MSC. The directed retry proce- success rate,
dure is completed when the counter is BSS: trf_488
released Call Volume
004056 BSC_I_TCH_T Number of successful incoming TCH to BSS: dcr_54b
CH TCH handovers controlled by the BSC Call Drop Rate
(pegged only in 2G handovers.)
Updated when the HO is completed.
004057 BSC_I_SDCCH Number of successful incoming BSS: csf_44b
_TCH SDCCH to TCH handovers controlled TCH allocation
by the BSC. Counter 004010 is success rate,
updated along with this counter. When BSS: trf_488
a directed retry procedure is completed Call Volume
or when the direct access to the super-
reuse TRX is completed or when the
TCH assignment to the super-reuse
TRX is completed.
004065 BSC_O_SDCC Number of successful outgoing TCH BSS: csf_44b
H_TCH handoverhandovers controlled by the TCH allocation
BSC. Counter 004014 is updated along success rate,
with this counter. Updated when a BSS: trf_488
directed retry procedure is completed, Call Volume
when the direct access from the
SDCCH to TCH on a super-reuse TRX
is completed, when the intelligent
directed retry is completed or when the
TCH assignment to a super-reuse TRX
is completed.
004074 CELL_SDCCH Number of successful intra-cell BSS: csf_44b
_TCH (SDCCH to TCH) handovers. Counter TCH allocation
004018 is updated along with this success rate
counter. When a channel assignment
to a super-reuse TRX in an IUO DR is
completed or when the direct access to
a super-reuse TRX is completed.
004084 BSC_O_DROP Number of calls that are dropped BSS: hfr_68c
_CALLS during outgoing handovers controlled handover drop
by the BSC. Counters 004012, 004016 ratio
and 004083 are updated along with this
counter, or counters 004013, 004017
and 004083 are updated along with this
counter
DN0983176 Id:0900d8058087523d 77
Issue 01A
BSC product family

004085 CELL_DROP_ Number of calls dropped during intra- BSS: hfr_68c
CALLS cell handovers. Counter 004020 is handover drop
updated along with this counter when ratio
the MS is lost or counter 004021 is
updated along with this counter when
switching from a unidirectional to a bi-
directional speech path fails.
004107 MSC_O_CALL Number of calls that are dropped BSS: hfr_68c
_DROP_HO during external handovers after handover drop
HANDOVER_COMMAND is received ratio
from the MSC. Counter 004007 is
004149 MSC_HO_WC Number of successfully completed BSS: dcr_54b
DMA_RAN_SU incoming (UTRAN to GSM) handovers. Call Drop Rate
CC Updated when the inter-system
handover (UTRAN to GSM) is acknowl-
edged and completed.
004154 MSC_GEN_SY Number of the BSS: hsr_28
S_WCDMA_R INTER_SYSTEM_HANDOVER_TO_ Total handover
AN_HO_COM WCDMA_RAN_COMMAND success ratio,
messages generated by outgoing BSS: hsr_34a
(GSM to WCDMA RAN) inter-system Inter BSS HO
handovers controlled by the MSC. Success Rate,
When HANDOVER COMMAND is sent
to the MS the counter is updated.
004157 MSC_CALL_D Number of dropped calls during BSS: hfr_68c
ROP_HO_WC outgoing (GSM to WCDMA RAN) han- handover drop
DMA_RAN dovers after HANDOVER COMMAND ratio
is received from the MSC. When a call
is dropped during an external handover
after the BSC has received a
HANDOVER_COMMAND message.
The HANDOVER_COMMAND
message is received when either the
GSM timer T8 expires or when the
MSC sends a CLEAR_COMMAND
message to the BSC with other cause
than call control or handover success-
ful. The counter is updated for non-
transparent data calls, transparent
data calls or speech calls.
78 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

004158 MSC_TO_WC Number of successful outgoing (GSM BSS: hsr_28
DMA_RAN_SU to WCDMA RAN) handovers controlled Total handover
CC_TCH_HO by the MSC. When the inter-system success ratio,
handover is completed and BSC has BSS: hsr_34a
received CLEAR_COMMAND from the Inter BSS HO
MSC. The counter is updated for non- Success Rate
transparent data calls, transparent
data calls, speech calls.
057018 SERVED_FAC Number of the served FACCH call BSS: csf_44b
CH_REQ requests. When a TCH channel is suc- TCH allocation
cessfully reserved for an FACCH call success rate,
set-up. A TCH is reserved, because BSS: trf_486a
there is a congestion situation on the Immediate
SDCCH. assignment
success rate%,
BSS: cssr_8a
Call setup
success rate
057020 T3101_EXPIR Number of times when the GSM timer BSS: sdr_18a
ED T3101 expires. The SDCCH RF
IMMEDIATE_ASSIGN_COMMAND Loss Rate
message is sent but an
ESTABLISH_INDICATION message is
not received causing the GSM timer
T3101 to expire on the SDCCH then
the counter is updated.
057021 SDCCH_ASSI Number of the SDCCH assignments. BSS: csf_43b
GN Counter released when an SDCCH usage
ESTABLISH_INDICATION message is success rate,
received on the SDCCH from the BTS. BSS: trf_486a
This means that an MS is also moved Immediate
to the SDCCH channel. This counter is assignment
updated with all SDCCH assignments, success rate%
except handover.
057028 TCH_CALL_R Number of the TCH call requests BSS: trf_485a
EQ Updated when the TCH channel is Assignment
requested from the RRM. This counter success rate
includes all TCH requests, except TCH
to TCH handovers. This counter is not
updated in re-establishment case.
DN0983176 Id:0900d8058087523d 79
Issue 01A
BSC product family

057033 TCH_NEW_CA Number of the TCH new call assign- BSS: csf_44b
LL_ASSIGN ments. In case of a new callan TCH allocation
ASSIGNMENT_COMPLETE message success rate,
is received on TCH from the BTS. This BSS: trf_485a
counter is updated when an Assignment
ESTABLISH_INDICATION message is success rate,
received on the TCH from the BTS.
BSS: dcr_54b
While normal directed retry (inter-cell
directed retry) this counter is updated Call Drop Rate,
when a HANDOVER_COMPLETE BSS: trf_488
message is received on the TCH from Call Volume
the BTS. If external SDCCH to SDCCH
handover is made after a re-establish-
ment, this counter is also updated.
057035 TCH_NORM_R Number of the TCH normal releases. BSS: dcr_29
ELEASE When the TCH channel is released TCH drop
(after a CHANNEL_RELEASE
message) without any problems and
the channel is reserved for a normal
call the counter is updated. If an
external handover is made after a re-
establishment this counter is also
updated. In case the BSC receives a
Release Indication message from the
BTS withandoverut having started the
call release, the BSC does not consider
this as a dropped call and therefore it
triggers this counter.
80 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

072000 NBR_OF_UL_ Number of all UL TBF establishments, BSS: tbf_74a,
TBF including both acknowledged mode TBF establish-
and unacknowledged mode UL TBF ment success
establishments. Updated when an rate UL,
uplink TBF is established. The counter BSS: tbf_142
is triggered exactly after UL TBF Failure
IMMEDIATE_ASSIGNMENT, Rate
PACKET_UPLINK_ASSIGNMENT or
PACKET_TIMESLOT_RECONFIGUR
E messages. Consecutive TBFs from
the same MS to the same direction
might use only one TSL allocation. This
counter is not updated in reallocations,
whereas counters 072034 to 072038
and 072044 to 072048 are updated
both in allocations and reallocations.
This counter is updated separately for
normal, extended and super-extended
areas.
072005 NBR_OF_DL_ Number of all downlink TBF establish- BSS: tbf_145
TBF ments, including both acknowledged (E)GPRS DL
mode and unacknowledged mode TBF establish-
downlink TBF establishments. ment failure
Updated when a downlink TBF is ratio,
established. The counter is triggered BSS: tbf_143
after IMMEDIATE_ASSIGNMENT, DL TBF Failure
PACKET_DOWNLINK_ASSIGNMEN Rate
T messages. This counter is not
updated in reallocations. This counter
is updated separately for normal,
extended and super-extended areas.
DN0983176 Id:0900d8058087523d 81
Issue 01A
BSC product family

072056 UL_TBF_REL_ Number of uplink TBF releases due to BSS: tbf_142
DUE_NO_RES no response from MS. The BSC UL TBF Failure
P_MS increases N3101 for each USF when Rate
no data is received from the MS. When
N3101 reaches the maximum value
timer T3169 is started. When the timer
expires and neither a SUSPEND nor
FLUSH-LL message is received before
expiration this counter is updated. If
either of them is received before T3169
expiration, a corresponding counter
072058 UL TBF_REL_DU_
TO_FLUSH or 072060 UL_TBF_REL
DUE_TO_SUSPEND is updated
instead. This counter is updated sepa-
rately for normal, extended and super-
extended areas.
072057 DL_TBF_REL_ Number of downlink TBF releases due BSS: tbf_143
DUE_NO_RES to no response from MS. If the BSC DL TBF Failure
P_MS does not receive a Rate
PACKET_DOWNLINK_ACK/NACK
message after it has polled the MS, it
increases N3105. When the timer
expires, and neither a SUSPEND nor
FLUSH-LL message is received before
expiration, this counter is updated. If
either of them is received before T3195
expiration a corresponding counter
072059 DL TBF REL DUE TO FLUSH
or 072061 DL TBF REL DUE TO
SUSPEND is updated instead. This
counter is updated separately for
areas.
82 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

072062 RLC_DATA_BL Number of new RLC data blocks in BSS: trf_213c,
OCKS_DL_CS downlink with CS1. This counter does trf_212c GPRS
1 not count the retransmitted data DL/UL Payload
blocks. When a valid, new RLC data Data,
block is sent in downlink with CS1 BSS: trf_494
coding scheme the counter is updated. GPRS UL
This counter does not include retrans- Payload data,
missions, but is triggered both in trf_495 GPRS
acknowledged and unacknowledged DL Payload
modes. data
In downlink data transfer the PCU
selects the CS to be used, and the
code word for the selected CS is
included in each sent RLC data block.
If the CS is changed during one TBF
reservation, the new CS code word is
included in the blocks. In retransmis-
sions the same CS has to be used as in
the initial block transmission. The
unacknowledged RLC blocks always
use CS1 and trigger this counter. This
areas.
072063 RLC_DATA_BL Number of new RLC data blocks in BSS: trf_213c,
OCKS_DL_CS downlink with CS2. This counter does trf_212c GPRS
2 not count the retransmitted data DL/UL Payload
blocks. When a new, valid RLC data Data,
block is sent in downlink with CS2. This BSS: trf_494
counter does not include retransmis- GPRS UL
sions. In downlink packet transfer the Payload data,
PCU selects the CS to be used, and trf_495 GPRS
the code word for the selected CS is DL Payload
included in each sent RLC data block. data
If the CS is changed during one TBF
reservation, the new CS code word is
included in the blocks. In retransmis-
sion the same CS has to be used as in
the initial block transmission. This
areas.
DN0983176 Id:0900d8058087523d 83
Issue 01A
BSC product family

072064 RLC_DATA_BL Number of valid RLC data blocks in BSS: trf_213c,
OCKS_UL_CS uplink with CS1. When the RLC trf_212c GPRS
1 receives a valid, new uplink RLC data DL/UL Payload
block with CS1 coding scheme this Data,
counter is updated. This counter does BSS: trf_494
not include retransmissions, but it is GPRS UL
triggered both in acknowledged and Payload data,
unacknowledged modes. The MS is trf_495 GPRS
told with either the DL Payload
IMMEDIATE_ASSIGNMENT or the data
PACKET_UPLINK_ASSIGNMENT
message which CS to use initially in the
uplink data transfer. The PCU can
command the MS to change the CS by
sending a
PACKET_UPLINK_ACK/NACK
message that includes a Channel
Coding Command field. In retransmis-
sions the same CS has to be used as in
areas
072065 RLC_DATA_BL Number of valid RLC data blocks in BSS: trf_213c,
OCKS_UL_CS uplink with CS2. Counter is updated trf_212c GPRS
2 when the RLC receives a valid and new DL/UL Payload
uplink RLC data block with CS2. This Data,
counter does not include retransmis- BSS: trf_494
sions. CS2 is always acknowledged. GPRS UL
The MS is told with either the Payload data,
IMMEDIATE_ASSIGNMENT or trf_495 GPRS
PACKET_UPLINK_ASSIGNMENT DL Payload
message which CS to use initially in the data
uplink data transfer. The PCU can
command the MS to change the CS by
sending a
PACKET_UPLINK_ACK/NACK
message, which includes the Channel
Coding Command field. In retransmis-
sion the same CS has to be used as in
areas.
84 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

072082 PACKET_CH_ Number of packet channel requests on BSS: 072082
REQ CCCH. Updated when a packet PACKET_CH_
channel request is received on REQ
common control channel (CHANNEL
REQUEST or EGPRS PACKET
CHANNEL REQUEST).
072092 UL_TBF_ESTA Number of uplink GPRS TBF establish- BSS: tbf_74a,
BLISHMENT_F ments that have failed due to no TBF establish-
AILED response from MS. Updated when the ment success
TBF establishment is aborted. rate UL
072093 DL_TBF_ESTA Number of downlink GPRS TBF estab- BSS: tbf_145
BLISHMENT_F lishments that have failed due to no (E)GPRS DL
AILED response from MS. Updated when the TBF establish-
GPRS TBF establishment is aborted ment failure
due to no response from MS. ratio,
BSS: tbf_143
DL TBF Failure
Rate
072094 UL Number of uplink EGPRS TBF estab- BSS: tbf_74a,
EGPRS_TBF_ lishments that have failed due to no TBF establish-
RELEASE_DU response from MS. Updated when the ment success
E_NO_RESPO EGPRS TBF establishment is aborted rate UL,
NSE_FROM_M due to no response from MS. BSS: tbf_142
S UL TBF Failure
Rate
072095 DL_EGPRS_T Number of downlink EGPRS TBF BSS: tbf_145
BF_RELEASE_ establishments that have failed due to (E)GPRS DL
DUE_NO_RES no response from MS. Updated when TBF establish-
P the EGPRS TBF establishment is ment failure
aborted due to no response from MS. ratio
072100 AVER_TBFS_ Denominator for the sum of uplink BSS: tbf_38d,
PER_TSL_UL_ TBFs average values per timeslot. tbf_37d
DEN Incremented once per second. This Average DL/UL
counter is updated separately for TBF per
normal, extended and super-extended timeslot
areas.
072102 AVER_TBFS_ Denominator for the sum of downlink BSS: tbf_38d,
PER_TSL_DL_ TBFs average values per timeslot. tbf_37d
DEN Incremented once per second. This Average DL/UL
counter is updated separately for TBF per
normal, extended and super-extended timeslot
areas.
DN0983176 Id:0900d8058087523d 85
Issue 01A
BSC product family

072121 UL_TBF_ESTA Number of started UL TBF establish- BSS: tbf_74a,
BL_STARTED ments. Updated before radio resources TBF establish-
are allocated after the PCU has ment success
received a Channel Request for a new rate UL
TBF, or channel request in a Packet DL
Ack/Nack if there is an ongoing DL
TBF. Updated only once per TBF. This
areas.
072171 AVE_UL_TBF_ Sum of uplink TBFs average values per BSS: tbf_38d,
PER_USED_T timeslot. An average value is counted tbf_37d
SL once per second from the used Average DL/UL
timeslots of a GPRS/EDGE territory. TBF per
The obtained decimal value is then timeslot
multiplied by 100 and summed up to
this counter. This counter is updated
separately for normal, extended and
super-extended areas.
072172 AVE_DL_TBF_ Sum of downlink TBFs average values BSS: tbf_38d,
PER_USED_T per timeslot. An average value is tbf_37d
SL counted once per second from the Average DL/UL
used timeslots of a GPRS/EDGE terri- TBF per
tory. The obtained decimal value is timeslot
then multiplied by 100 and summed up
to this counter. This counter is updated
separately for normal, extended and
super-extended areas.
079000 DL_RLC_BLO Number of DL RLC data blocks sent to BSS: trf_213c,
CKS_IN_ACK_ an EGPRS MS in acknowledged mode trf_212c GPRS
MODE for the first time. Retransmitted blocks DL/UL Payload
are not included. The counter is Data,
updated after DL RLC data block is BSS: trf_494
sent. This counter is updated sepa- GPRS UL
rately for normal, extended and super- Payload data,
extended areas. trf_495 GPRS
DL Payload
data
86 Id:0900d8058087523d DN0983176
Issue 01A
BSC product family

079001 DL_RLC_BLO Number of DL RLC data blocks in BSS: trf_213c,
CKS_IN_UNAC unacknowledged mode sent to an trf_212c GPRS
K_MODE EGPRS MS. In unacknowledged mode DL/UL Payload
there are no retransmissions on RLC Data,
level. The PCU does not know how BSS: trf_494
many of these blocks get correctly GPRS UL
through to the MS. When a DL RLC Payload data,
data block is sent the counter is trf_495 GPRS
updated. This counter is updated sepa- DL Payload
rately for normal, extended and super- data
extended areas.
079002 UL_RLC_BLO Number of valid UL RLC data blocks BSS: trf_213c,
CKS_IN_ACK_ with a new BSN received in acknowl- trf_212c GPRS
MODE edged mode from an EGPRS MS DL/UL Payload
within a radio block having a valid Data,
header. The counter is updated after BSS: trf_494
valid UL RLC data block is received. GPRS UL
This counter is updated separately for Payload data,
normal, extended and super-extended trf_495 GPRS
areas. DL Payload
data
079003 UL_RLC_BLO Number of valid UL RLC data blocks BSS: trf_213c,
CKS_IN_UNAC with a new BSN received in unacknowl- trf_212c GPRS
K_MODE edged mode from an EGPRS MS DL/UL Payload
within a radio block having a valid Data,
header. When a valid UL RLC data BSS: trf_494
block is received the counter is GPRS UL
updated. This counter is updated sepa- Payload data,
rately for normal, extended and super- trf_495 GPRS
extended areas. DL Payload
data
105010 DTM_DURATI Not in use. BSS: dcr_26a
ON_SUM_HR TCH drop /
Erlang (before
re-establish-
ment)
105011 DTM_DURATI Sum of DTM allocation durations BSS: dcr_26a
ON_SUM_FR having a full rate speech connection. TCH drop /
The BSC measures for handover long Erlang (before
each DTM CS connection is kept in the re-establish-
PS territory with a full rate speech con- ment)
nection. The measured durations are
summed up to this counter.
DN0983176 Id:0900d8058087523d 87
Issue 01A
BSC product family

- SPARE001229 Number of TCH assignment failures BSS: sdr_18a
where the MS has returned to SDCCH. SDCCH RF
Updated when the BSC receives Loss Rate
ASSIGNMENT FAILURE message
from the MS via the BTS indicating that
the MS has returned to SDCCH.
88 Id:0900d8058087523d DN0983176
Issue 01A
KPI guidelines for Horizon BTS migration to the Flexi Abbreviations
BSC product family
8 Abbreviations
0-Z
Abis Interface which allows connection between base station controller

(BSC) and base transceiver station (BTS)
AGCH Access Grant Channel
BSC Base Station Controller
BSS GSM SW release
CCCH Common Control Channel
DTM Dual Transfer Mode
EGPRS Enhanced General Packet Radio Service
FACCH Fast Associated Control Channel
GPRS General Packet Radio Service
GSR GSM SW release based on BSC2
KPI Key Performance Indicator
LAPD Link Access Procedure on the D-channel
MSC Mobile Services Switching Center
PDTCH Packet Data Traffic Channel
SDCCH Stand-alone Dedicated Control Channel
TCH Traffic Channel
TLS Transport Layer Security Protocol
TRX Transceiver
DN0983176 Id:0900d805808934bd 89
Issue 01A

Horizon Kpi Guide Migr dn0983176 01A en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Horizon Kpi Guide Migr dn0983176 01A en

Загружено:

Авторское право:

Доступные форматы

GSM/EDGE BSS, Rel.

KPI guidelines for Horizon BTS migration

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

2 Employment of KPIs during migration . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Summary of KPI differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Performance verification KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.5.2.2 BSS: hfr_68c handover drop ratio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Main field KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.2.4.1 GSR: INTRA_CELL_ HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . 32

6 Counter group mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Summary of KPI differences (3)

Call Setup Success Ratio (4.3)

TCH drop (4.4)

PS traffic volume (4.6)

Retain ability (5.2)

Counter group mapping (6)

BSS counter list (7.2)

1.2 Horizon BTS migration and related KPI measurements

2 Employment of KPIs during migration

2.1 Performance verification KPIs

2.2 Main field KPIs

3 Summary of KPI differences

3.1 Performance verification KPIs

KPI category GSR KPI BSS KPI New Match

Table 1 Summary of performance verification KPI differences

3.2 Main field KPIs

KPI category GSR KPI BSS KPI New Match

Table 2 Summary of main field KPI differences

KPI category GSR KPI BSS KPI New Match

Table 2 Summary of main field KPI differences (Cont.)

4 Performance verification KPI

4.1.1 TCH availability ratio

4.1.1.1 GSR: BSS_AVAILABILITY

4.1.1.2 BSS: ava_1g TCH availability ratio

ava_1g = (ave_avail_tch_sum / ave_avail_tch_den + ave_gprs_channels_sum /

4.2 Traffic volume

4.2.1 Average CS traffic per BTS

4.2.1.1 GSR: TCH_TRAFFIC_CARRIED

4.2.1.2 BSS: trf_1d Average CS traffic per BTS

trf_1d = (ave_busy_tch / res_av_denom14) + [((0.5 * dtm_duration_sum_HR +

4.3 Call Setup Success Ratio

4.3.1 Immediate Assignment Success Rate

4.3.1.1 GSR: IMMEDIATE_ASSIGNMENT_ACCESS_RATE

4.3.1.2 BSS: trf_467a Immediate assignment success rate

trf_467a = [(imm_assgn_sent - del_ind_msg_rec) / (imm_assgn_sent +

4.3.2 SDCCH Usage Success Rate

4.3.2.1 GSR: SDCCH_USAGE_SUCCESS_RATE

sdcch_usage_success_rate = [1 - ((rf_loss_sd + (ma_fail_from_ms -

4.3.2.2 BSS: csf_43b SDCCH usage success rate

csf_43b = [1 - [(sdcch_radion_fail + sdcch_rf_old_ho + sdcch_user_act +

4.3.3 TCH Allocation Success Rate

4.3.3.1 GSR: TCH_ALLOCATION_SUCCESS_RATE

tch_allocation_success_rate = (total_calls + assgn_redirect) / (ma_req_from_msc -

4.3.3.2 BSS: csf_44b TCH allocation success rate

csf_44b = [(tch_net_call_assign - served_facch_req +(msc_o_sdcch_tch +

4.4 TCH drop

4.4.1 TCH drop

4.4.1.1 GSR: TCH_DROP_RATE

drop_call_rate = [(clr_req_to_msc_fr + clr_req_to_msc_hr) / (clr_cmd_from_msc_fr +

4.4.1.2 BSS: dcr_29 TCH drop

dcr_29 = [(tch_radion_fail - tch_rel_due_rad_fail_pch_2_3 + tch_rf_old_ho +