GSM/EDGE BSS, Rel.
RG20(BSS), Operating
Documentation, Issue 07
KPI guidelines for BTSplus migration into
the Flexi BSC product family
DN0933284
Issue 01E
Approval Date 05-09-2011
Confidential
KPI guidelines for BTSplus migration into 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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.
2
Id:0900d805808c217b
Confidential
DN0933284
Issue 01E
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Table of contents
This document has 67 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
DN0933284
1
1.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Recommendations for KPI reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2
Employment of KPIs during migration . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3
3.1
3.2
3.3
3.4
3.4.1
3.4.2
3.5
3.6
3.7
3.8
KPI differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
General differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Measurement reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
LAPD multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Extended cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fine tuning of quality thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Power control indication due to link failure warning . . . . . . . . . . . . . . . . 18
AMR signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
4.1.11
4.1.12
4.1.13
4.1.14
4.1.15
4.1.16
4.2
4.2.1
4.2.2
4.2.3
4.3
4.3.1
4.3.2
4.3.3
4.3.4
Mapping of top level KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Voice call setup success rate BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SDCCH congestion time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SDCCH block rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SDCCH real blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Number of immediate assignment messages sent . . . . . . . . . . . . . . . . 24
Number of immediate assignment reject messages . . . . . . . . . . . . . . . 24
Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
TCH congestion time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
TCH call blocking, before directed retry. . . . . . . . . . . . . . . . . . . . . . . . . 24
TCH call lossing, before directed retry. . . . . . . . . . . . . . . . . . . . . . . . . . 25
Queuing time of queued call attempts . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Downlink multislot allocation blocking . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Downlink multislot soft blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Downlink temporary block flows per timeslot . . . . . . . . . . . . . . . . . . . . . 25
Combined timeslot availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
AGCH blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Retainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SDCCH drop rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
TCH drop rate per Erlanghour including TCH assignment failures . . . . 27
Call drop rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Handover success rate 2G to 2G (without intracell handover) . . . . . . . 27
Handover success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Handover success rate 2G to 3G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Handover drop (2G - 2G, intracell included) . . . . . . . . . . . . . . . . . . . . . 28
Id:0900d805808c217b
Confidential
3
KPI guidelines for BTSplus migration into the Flexi BSC
product family
4.3.5
4.3.6
4.3.7
4.4
4.4.1
4
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
4.4.7
4.4.8
4.4.9
4.4.10
4.4.11
4.4.12
4.4.13
4.4.14
4.4.15
4.4.16
4.4.17
4.4.18
4.4.19
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
Handover drop rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Outgoing network controlled cell reselection (NCCR) success ratio. . . . 28
Releases per minute TBF duration caused by flush-LL . . . . . . . . . . . . . 28
Network Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SDCCH traffic carried
(based on sampling - mean number of busy SDCCHs) . . . . . . . . . . . . . 29
SDCCH traffic utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
TCH traffic carried . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
TCH traffic share of half rate AMR calls . . . . . . . . . . . . . . . . . . . . . . . . . 30
TCH traffic share of full rate AMR calls. . . . . . . . . . . . . . . . . . . . . . . . . . 30
TCH traffic share of non AMR calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Network utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
User data volume on radio interface per cell uplink . . . . . . . . . . . . . . . . 31
User data volume on radio interface per cell downlink . . . . . . . . . . . . . . 31
Average number of busy packet channels uplink . . . . . . . . . . . . . . . . . . 32
Average number of busy packet channels downlink. . . . . . . . . . . . . . . . 32
PDCH utilization rate uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
PDCH utilization rate downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
PDCH utilization rate uplink, signaling excluded. . . . . . . . . . . . . . . . . . . 33
PDCH utilization rate downlink, signaling excluded . . . . . . . . . . . . . . . . 33
Coding scheme distribution EGPRS RLC downlink . . . . . . . . . . . . . . . . 33
Share of EGPRS requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Gb interface frame relay link utilization rate uplink . . . . . . . . . . . . . . . . . 34
Gb interface frame relay link utilization rate downlink. . . . . . . . . . . . . . . 34
Quality/Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cumulative quality in class x uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cumulative quality in class x downlink . . . . . . . . . . . . . . . . . . . . . . . . . . 35
GPRS RLC throughput per radio timeslot downlink . . . . . . . . . . . . . . . . 35
GPRS RLC throughput per radio timeslot uplink . . . . . . . . . . . . . . . . . . 35
EGPRS RLC throughput per radio timeslot downlink . . . . . . . . . . . . . . . 36
EGPRS RLC throughput per radio timeslot uplink . . . . . . . . . . . . . . . . . 36
5
Reference configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6
Verification of PS KPI comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
7.12
Definitions for non-benchmark KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_1a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_5a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
blck_21b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
cngt_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
cngt_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
cssr_7c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
trf_467 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
csf_43b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
csf_44b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Id:0900d805808c217b
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
DN0933284
7.13
7.14
7.15
7.16
7.17
7.18
7.19
7.20
7.21
7.22
7.23
7.24
7.25
7.26
7.27
7.28
7.29
7.30
7.31
7.32
7.33
7.34
dcr_26a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
dcr_29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
frl_7b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
hsr_30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
hsr_31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
hfr_68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
nccr_13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
que_10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
rlc_57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
sd_1b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
sdr_17a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
tbf_63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
trf_7b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
trf_238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
trf_239 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
trf_248a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
trf_249a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
trf_250a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
trf_249b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
trf_250b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
trf_536 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
trf_534 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.10
8.11
8.12
8.13
8.14
8.15
Definition of additional BR 9.0 product line KPIs . . . . . . . . . . . . . . . . . . 55
Assignment failure rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Timeslot utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Total TCH busy time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Combined channel availability rate for CS and PS traffic . . . . . . . . . . . 57
Handover unsuccess rate 2G to 2G. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Handover ratio, directed retries 2G to 2G . . . . . . . . . . . . . . . . . . . . . . . 58
Total handover rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
RXQUAL distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
TCH traffic share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
User throughput on radio interface per cell . . . . . . . . . . . . . . . . . . . . . . 61
Percent timeslot resources achieved . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
User data volume on radio interface per cell . . . . . . . . . . . . . . . . . . . . . 63
Share of EGPRS requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Coding scheme distribution on RLC data blocks . . . . . . . . . . . . . . . . . . 65
Frame relay link utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Id:0900d805808c217b
Confidential
5
KPI guidelines for BTSplus migration into the Flexi BSC
product family
List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
6
Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
LAPD multiplexing scenario (BSS product line) . . . . . . . . . . . . . . . . . . . 15
LAPD multiplexing scenario (after migration) . . . . . . . . . . . . . . . . . . . . . 16
Configuration with extended and superextended area (example) . . . . . 17
Measured (trf_234) and calculated UL EDGE Throughput per TSL curves
(x is a time axis given in GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Relative error in calculation of UL EDGE Throughput per TSL (x is a time
axis given in GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Measured (18.2.14b) and calculated UL EDGE Throughput per TSL curves
(x is a time axis given in GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Relative error in calculation of UL EDGE Throughput per TSL (x is a time
axis given in GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Dependence of the RLS throughput per TSL on SNR (C/I) for MCS-6 and
MCS-9 with and without IR feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Id:0900d805808c217b
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
List of tables
Table 1
DN0933284
KPI mapping (overview) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Id:0900d805808c217b
Confidential
7
Summary of changes
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Issue
Date
Summary
01
07/2009
First issue for release RG10(BSS)
01A
08/2009
New chapter “Definitions of BR9.0 product line KPIs” and editorial changes
01B
10/2009
•
•
•
•
Chapter “Mapping of top level KPIs” updated
Chapter “Reference configuration” added
Chapter “Verification of PS KPI comparison” added
Editorial changes
01C
03/2010
•
•
•
Chapter “ KPIdifferences” updated
Chapter “Mapping of top level KPIs” updated
Chapter “Definition of additional BR90 product line KPIs”
updated
01D
08/2010
•
•
•
•
•
•
•
•
4.1.1 Voice call setup success rate BSS updated
4.1.13 Downlink multislot soft blocking updated
7.9 cssr_7c updated
7.10 trf_467 updated
7.11 csf_43b new chapter
7.12 csf_44b updated
7.13 dcr_26a updated
7.14 dcr_29 updated
01E
09/2011
Chapter 4.2.1 SDDCH drop rate updated
sdr_17a replaced by sdr_17b
Issue 01E for release RG10(BSS)
8
Id:0900d805808c21ad
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Introduction
1 Introduction
This document describes the possible differences between network key performance
indicators (KPIs) of the Nokia Siemens Networks BR and BSS product lines, in the
context of migrating BTSplus base stations from BSCs of type eBSC/BSC1 to the Flexi
BSC product family.
The BTSplus is adapted to the Flexi BSC product family by means of the BSS Abis
implementation. This document shows the relationship of BR KPIs to BSS KPIs, and the
KPI substitution after migration.
Refer to “Migrating BTSplus to the Flexi BSC product family” for more information on the
migration procedures. Refer to the “BSS 21469: BS2xx@Flexi BSC product family”
feature description for more information on operating the BTSplus with the Flexi BSC
product family.
“Figure 1” displays the network architecture for operating the BTSplus with the
eBSC/BSC1 or with the Flexi BSC product family.
DN0933284
Id:0900d8058063e17e
Confidential
9
Introduction
KPI guidelines for BTSplus migration into the Flexi BSC
product family
BTSplus
Modified BSS Abis
BSS BTS
BTSplus
BTSplus
BSS BTS
BTSplus
BR LMT
BR Abis
BSS Abis
eBSC/
BSC1
Flexi
BSC
Q3
O-link
NetAct
RC
BR LMT
Figure 1
Network architecture
BTSplus, eBSC and BSC1 are products of the Nokia Siemens Networks GSM/EDGE
BR line. Flexi EDGE BTS and the Flexi BSC product family are products of the Nokia
Siemens Networks GSM/EDGE BSS line.
The referenced releases for the migration are:
•
•
BR10 for the BR product line
BSS14 for the BSS product line
In general, the rehosting of a BTSplus base station from the eBSC/BSC1 to the Flexi
BSC product family should not cause any performance degradation from the perspective of the end user (e.g. speech quality or data throughput) and from the perspective of
the network operator (e.g. radio capacity). This document describes the main
GSM/EDGE RAN KPIs which are recommended to be observed before and after rehosting of a BTSplus from an eBSC/BSC1 to the Flexi BSC product family. These KPI sets
should be comprehensive to avoid performance degradation caused by BTSplus rehost-
10
Id:0900d8058063e17e
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Introduction
ing. For a BTSplus connected to the Flexi BSC product family, the set of performance
measurement counters and KPIs from the Flexi BSC product family are used for performance monitoring. Thus, the main purpose for the present document is to provide the
mapping from PM counters and their KPIs for the BR product line (BTSplus,
eBSC/BSC1) to the best fitting KPIs for the BSS product line (Flexi BSC product family).
Comparison of tracing functions between BR and BSS product lines goes beyond the
scope of the present document.
1.1
Recommendations for KPI reporting
In general, the KPIs shall be observed before and after rehosting a BTSplus base station
from an eBSC/BSC1 to the Flexi BSC product family to avoid performance degradations.
Some KPIs need to be observed only after BTSplus rehosting. These are KPIs for critical
performance areas of the migration project which have no corresponding KPIs in the BR
product line due to different feature implementations.
A large number of KPIs is defined on the level of radio cells (or even on TRX level).
These KPIs shall be reported at least for the concerned radio cells served by the
rehosted BTSplus. Some of them should be reported additionally for the surrounding
cells of the concerned cells for the following reasons:
•
•
Verification that traffic balance between concerned cells and their neighbors is
roughly the same before and after BTSplus rehosting.
Verification that handover behavior in terms of handover cause distribution and
handover success rate has not degraded after BTSplus rehosting.
Rehosting of a single BTSplus from the eBSC/BSC1 to the Flexi BSC product family
might lead to a situation where a large number of handovers between neighboring cells
are treated as inter-BSC handovers between the eBSC/BSC1 and the Flexi BSC
product family (see “Figure 1”).
A precondition for acceptable inter-BSC handover behavior is having well aligned
handover parameters between the eBSC/BSC1 and Flexi BSC product family database.
KPIs which are defined on the level of the PCU or the Gb interface shall be reported for
the eBSC/BSC1 and the Flexi BSC product family.
DN0933284
Id:0900d8058063e17e
Confidential
11
Employment of KPIs during migration
KPI guidelines for BTSplus migration into the Flexi BSC
product family
2 Employment of KPIs during migration
The following performance areas are recommended to be observed:
1. Top level KPIs for the general observation of GSM/EDGE RAN performance.
These are sets of KPIs which an operator of both the BR and the BSS product lines
would normally observe continuously (usually on a daily basis).
They are not the main focus of the migration project, and should be observed at least
two weeks before and at least two weeks after BTSplus rehosting.
2. Enhanced set of KPIs for the observation of performance in GSM/EDGE RAN functional areas where technical concepts are different between the BR and the BSS
implementations. These standard KPIs for BSS product line should be employed for
a more detailed performance observation since technically different concepts cause
difficult mapping of BR line configuration parameters to corresponding BSS line configuration parameters.
Examples are:
• Detailed observation of Abis resource utilization, due to:
• EDAP (Enhanced Dynamic Abis Pool) handling as used in the Abis implementation between the BTSplus and the Flexi BTS product family, in
contrast with the Abis implementation used to connect the BTSplus with
eBSC/BSC1 (see “EDAP handling” for more information)
• Adaptations for LAPD multiplexing in the Flexi BSC product family (refer to
“LAPD multiplexing” for more information)
• Detailed observations of handover and power control, due to varying functional
mapping of handover and power control to BTS and BSC in the BR and BSS
product lines. Refer to “Handover and power control” for more information.
• Detailed observation of utilization of packet switched related resources (radio
channel, Abis and PCU) in the GSM/EDGE RAN. These KPI observations are
vital for proper resource dimensioning. The concepts for dynamic balancing of
contingents of radio resources between CS (TCH) and PS (PDCH) are different
for BR and BSS product line (BSS line: so called PS Territory concept), and
along with this also the concepts for assignment of Abis and PCU resources to
PDCHs depending on their current activity for data transmission.
• Observation of possible performance degradations after BTSplus rehosting due
to a different feature set in the BSS product line.
12
Id:0900d8058062da9e
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
KPI differences
3 KPI differences
This chapter deals with the main differences between the BSS line and the BR line KPIs.
The differences depend on the supported features and can be subdivided into the following groups:
•
•
•
•
•
•
General differences
Measurement reports
Handover
Abis interface
Extended cells
Fine tuning of quality thresholds
In order to monitor the differences some BSS KPI observations are recommended (see
chapter “Mapping of top level KPIs” to find the corresponding KPIs' partners on the BR
side). For non-benchmark BSS14 KPIs see chapter “Definitions for non-benchmark
KPIs”. The BR line KPIs are defined in the “PM: KPI Requirement Specification” and
related PM counters in the “Performance measurement counters” document for BR 10.
In addition to the above mentioned differences, there are some features with PM limitations and without corresponding counters within Flexi BSC product family:
•
•
•
•
3.1
Power control indication due to link failure warning
AMR signaling
BTS processor load counter (no counters of this type in BSS product line)
Correlated RX Lev, QUAL and TA per TRX counter (no counters of this type in BSS
product line)
General differences
The BR product line KPIs depend on BTS and BSC counters, while the BSS product line
counters are exclusively based on BSC counters. Due to this, the BSS product line
solution to implement counters within the BSC only is possible. The KPIs after migration
are based only on measurement counters reused from the BSS. All the counters can be
post-processed and handled as it is in today's BSS networks. BR counters are removed
and are no longer supported in the active configuration.
Therefore, the known post-processing tools for BR PM raw data cannot be used any
more and have to be exchanged at customer side to equivalent tools for BSS PM raw
data. Furthermore, the known KPIs and other results from BR PM data are no more
available in this configuration.
DN0933284
Id:0900d805806ff6b4
Confidential
13
KPI differences
KPI guidelines for BTSplus migration into the Flexi BSC
product family
3.2
Measurement reports
The measurement results of the BR product line (Abis counterpart of measurement
reports sent on the air interface) are normally not transmitted on Abis interface as for the
BR product line the pre-evaluation of measurement reports for handover and power
control decisions is done in the BTS.
The measurement results of the BSS product line (contain averaged results from measurement reports) are always sent on Abis as the BSC makes decision for handover and
power control. Additionally, the results are needed for channel allocation based on interference.
After migration the measurement reports are sent from the BTSplus to the Flexi BSC
product family in a certain configurable frequency (every N-th report will be sent from the
BTSplus to the Flexi BSC product family). Therefore, the measurement report based
KPIs and related Flexi BSC product family performance measurement counters will not
be evaluated using all measurement reports.
As the monitored quantity (RxQual, RXLEV, FER, ... etc.) is stochastical characterized
by a probability of function and statistical parameters random sampling (in this case
each N-th sample) can be used.
However, the previous statement is restricted to the event of large number of samples.
While for the most influenced KPIs the cumulative ratio is calculated it may happen that
before the swap it is calculated from 1000 samples while after the swap from
100 samples, and the relative error changes.
In some cases this may lead to customer complaints because KPI evaluation provides
values with a certain buffer range, although the system works very well. But the effect
of insufficient statistical reliability will only be visible for higher N (> 16).
3.3
Handover
The following handovers are not supported:
•
•
14
Compression/decompression handover for standard full rate/half rate (non AMR)
(intracell).
In the cells supported by the BR product line with non AMR but high GSM half rate
usage and compression/decompression (packing/unpacking) working under some
level of interference to observe unpacking due to poor quality it may happen that the
network quality degrades.
This may imply that call drop rate increases. Therefore, the following BSS KPIs shall
be monitored after migration:
• dcr_26a
• dcr_29
Additional quality may degrade. Therefore, the following BSS KPIs shall be monitored after migration:
• ulq_2a
• dlq_2a
• ulq_3
• dlq_3
Enhanced pairing (intracell)
Working under changing load conditions when two half rate calls are paired on different timeslots into one timeslot. In BR product line the cells with high half rate
Id:0900d805806ff6b4
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
•
3.4
KPI differences
usage (all timeslots configured as TCH DR) it may have impact on TCH blocking.
Therefore, the following BSS KPIs are recommended to be monitored after migration:
• blck_1a
• blck_8i
The better cell handover and imperative handover of UMTS may have impact on
TCH blocking. Therefore, the following KPIs are recommended to be monitored after
migration:
• blck_1a
• blck_8i
Abis interface
For Abis interface, LAPD multiplexing and traffic is considered.
3.4.1
LAPD multiplexing
LAPD multiplexing aims at optimizing usage of the LAPD channels by reduction of the
required signaling bandwidth. For the Abis interface controlled by the Flexi BSC product
family, a dedicated LAPD signaling channel is foreseen for each TRX (see “Figure 2”).
TRX3
TEI3
TRX1
TRX2 TEI1
TEI2
LAPD 1
Flexi
BTS
Figure 2
LAPD 2
LAPD 3
Dynamic Abis
Flexi
BSC
LAPD multiplexing scenario (BSS product line)
After migration, when the BSC of the Flexi BSC product family controls the BTSplus,
several TRXs can be multiplexed in the same LAPD, allowing all TRXs belonging to the
same site to be configured on one common physical LAPD link (see “Figure 3”).
DN0933284
Id:0900d805806ff6b4
Confidential
15
KPI differences
KPI guidelines for BTSplus migration into the Flexi BSC
product family
TRX3
TEI3
TRX1
TRX2 TEI1
TEI2
LAPD
BTS
Plus
Dynamic Abis
Figure 3
Flexi
BSC
LAPD multiplexing scenario (after migration)
After migration, the results cannot be provided on TRX basis as it is on the BSS side.
However, it is in accordance to the BR side where the measurement LAPD load provides
the results on LAPD link basis and not on TRX basis. The related KPI for the BR product
line is LAPDLOAD (LAPD load supervision). For BSS product line, the related KPI is
abi_6a.
3.4.2
Traffic
After migration, the Abis pool concept known from the BR product line consisting of one
common pool of Abis sub-timeslots for circuit switched and packet switched will not be
used.
Instead, the enhanced dynamic Abis pool (EDAP) will be used. Each radio timeslot has
a fixed assignment of one Abis sub-timeslot. The EDAP resources are only used for
packet switched activities when high coding schemes are assigned (e.g. CS4, MSC9)
when more than one sub-timeslot is needed.
After migration, the EDAP pool size has to be verified with the following BSS KPIs:
•
•
3.5
dap_1a (UL)
dap_2b (DL)
Extended cells
In the BR product line, the principle of extended cell (far area) is based on the double
timeslot technique where two consecutive timeslots are used for downlink. In the BSS
product line, it is based on a TRX basis where a specific radio propagation delay is considered for the extended and super extended area TRXs (see “Figure 4”).
After migration, the BSS approach is used.
16
Id:0900d805806ff6b4
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
KPI differences
N-TRX RX
f1
f1
f1
f1
f1
f1
f1
f1
TCH
TCH
TCH
TCH
TCH
f2
f2
TRX
BCCH/ Not TCH
RACH/ in use
SDCCH
Normal
E-TRX RX
f1
f2
f2
f2
f2
f2
E-TRX
E-RACH SDCCH TCH
TCH
TCH
TCH
TCH
TCH
f3
f3
40%
Delayed
receiver
S-TRX RX
f1
f3
f3
f3
f3
f3
TCH
TCH
S-TRX
E-RACH SDCCH TCH
TCH
TCH
TCH
80%
Delayed
receiver
Configuration with extended and superextended area (example)
Figure 4
After migration, a full rate channel consumes only one timeslot for both extended and
superextended areas in comparison to the BR product line where a full rate channel
always consumes two consecutive timeslots in downlink. Therefore, it may happen that
some TCH availability KPIs (like uav_14) provide higher values in relation to the available TRXs than expected based on experiences from the BR product line. For example,
a TRX with four timeslots for traffic enables to configure two full rate channels in the far
area on the BR side while four full rate channels can be configured in the extended area
on the BSS side (a TRX has to be of type E-TRX).
3.6
Fine tuning of quality thresholds
In the BR product line, quality thresholds for handover and power control are defined in
C/I (0..20dB). In the BSS product line, quality thresholds for handover and power control
are defined in RxQual (0..7).
During the migration process quality thresholds from BR (C/I thresholds) are converted
to the Flexi BSC product family RxQual parameters according to the following mapping
table:
C/l[dB] 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
RxQual 7
7
7
7
6
6
6
6
5
5
4
4
4
3
3
2
2
1
1
0
In the BSC, they are mapped back to C/I corresponding to the following mapping table:
RxQual
DN0933284
0
1
2
3
4
5
6
7
C/l[dB] 20
19
17
14
12
9
6
1
Id:0900d805806ff6b4
Confidential
17
KPI differences
KPI guidelines for BTSplus migration into the Flexi BSC
product family
A careful parameter control after migration is required. For instance C/I=4 dB is converted to RxQual 7 and mapped again to C/I=1 dB. This leads to mapping errors
between parameters, and as a consequence one procedure might be triggered erroneously before another.
The mapping might have the following impacts. Therefore the related KPIs shall be monitored:
•
•
•
•
Impact on handover and power control behavior.
The following BSS KPI related to handover performance shall be monitored:
– hsr_31
Impact on call drop rate increase.
The following BSS KPIs shall be monitored:
– dcr_26a
– dcr_29
Impact on interference level degradation which requires monitoring of the measurement type CI_RATIO.
The related BSS KPI shall be monitored:
– ci_1 - ci_8
In addition power control related BSS KPIs providing the mean strength level and
quality for uplink and downlink shall be monitored:
– c5012
– c5014
– c5016
– c5018
After migration power control is performed by the BTSplus and the BSC of the Flexi BSC
product family does not know when power control is supplied. Therefore, the following
counters cannot be used:
•
•
3.7
c5000 - 5003
providing the number of MS/BS power increase/decrease commands by signal
strength
c5008 - 5013
providing the number of MS/BS power increase/decrease commands by signal
quality
Power control indication due to link failure warning
For the counter “NCRLBRQU (2,10):normal call releases of calls with bad radio quality”
of BR product line the “Bad radio quality” means that the BTSplus
•
•
was not able to decode the last SACCH frames (uplink radio link counter decreased)
or the last uplink/downlink RxQual value is equal seven.
The counter is related to the feature “Power control indication due to link failure warning”
which is activated for the BTSplus. As there is no corresponding feature in the BSS
product line, no counter for monitoring within Flexi BSC product family exists.
3.8
AMR signaling
Concerning BR side the repeated SACCH/FACCH feature is available for non AMR and
AMR codecs. Therefore the related BSS measurement "AMR signalling measurements"
18
Id:0900d805806ff6b4
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
KPI differences
only counts AMR codecs as in GEMINI the BR approach is using it. An improvement
shall be done in next GEMINI release.
DN0933284
Id:0900d805806ff6b4
Confidential
19
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
4 Mapping of top level KPIs
This chapter defines a minimum set of corresponding so called top level KPIs between
the BR and the BSS product line, which should be monitored in the migration project.
•
•
BR product line KPIs see “PM:KPI Requirement Specification” (BR10)
BSS product line KPIs:
– for benchmark KPIs see “EDGE, GPRS, and GSM Voice Key Performance Indicators”
– for non-benchmark KPIs see chapter “Definitions for non-benchmark KPIs”
KPI deviations can be major or minor ones:
•
•
A major KPI deviation has a major effect in demonstrating to an operator the correct
functionality that can alter the prognosis or proposals provided by the network
planning and optimization department.
A minor KPI deviation has negligable impacts with regard to functionality demonstrations. Such an error might occur when BR product line KPI was used on the BSS
side and vice versa.
The following categories for top level KPIs are provided:
•
•
•
•
•
20
Accessibility
Retainability
Mobility
Network Usage
Quality/Integrity
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
BR KPI
BSS KPI
BR-BSS match
Accessibility
CSSuccRateBSS
cssr_5
Minor deviation
ASDCALTI[1] (PM counter)
cngt_2
Full match
SDCCHLossRate
blck_5
Full match
ImmAssLossRate
blck_5a
Minor deviation
TACCBPRO[2] - PM counter
C3001 - PM counter
Full match
TACCBPRO[3]- PM counter
C3002
Full match
ImmAssNoSize
sd_1b
Full match
AALTCHTI[1] (PM counter)
cngt_1
Full match
AssLossRate
blck_8i
Minor deviation
AssLossRateDRInc
blck_8
Full match
MDURTCRQ[1] FR
que_10
Minor deviation
TBFEstFailRateConDL
tbf_16b
Full match
PercentTSLAchievedDL
tbf_33b
Full match
MeanTBFMultiplPDCHDL
tbf_38d
Minor deviation
MeaAvChC
ava_1g
Full match
AGCHLossRate
blck_13 (CS)
Minor deviation
MDURTCRQ[2] HR
blck_21b (PS)
Retainability
SDCCHDropRatTCHAssFail
sdr_17b
Full match
TCHDropErlhAssFail
dcr_26a
Minor deviation
TCHDropErlhAssFail
dcr_29
Minor deviation
HOSuccRate2G2G
hsr_31
Full match
TotalHOSuccRate
hsr_28
Full match
HOSuccRate2G3G
hsr_30
Full match
HOUnSuccRate2G2G
hfr_2a
Full match
HODropRate2G2G
hfr_68
Full match
HODropRate
hfr_68c
Full match
NCIntrBSCCellSucRate
nccr_13
Minor deviation
TBFRelFlushMin
tbf_63 (uplink)
Minor deviation
Mobility
tbf_64 (downlink)
Network Usage
Table 1
DN0933284
KPI mapping (overview)
Id:0900d805808c2179
Confidential
21
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
BR KPI
BSS KPI
BR-BSS match
SDCCHTrafCarr
trf_11b
Full match
SDCCHTrafUtil
trf_7b
Minor deviation
TCHTrafCarrDR
trf_1d
Minor deviation
TCHShareHRAMR
trf_122a
Full match
TCHShareFRNBAMR
trf_121
Full match
TCHSharenonAMR
trf_120a
Full match
NTWUtilization
trf_248
Minor deviation
UserVolUmCellUL
trf_243
Minor deviation
UserVolUmCellDL
trf_244
Minor deviation
MeanPDCHBusyCellUL
trf_238
Full match
MeanPDCHBusyCellDL
trf_239
Full match
MeanBusyPdchUtilCellUL
trf_249a
Minor deviation
MeanBusyPdchUtilCellDL
trf_250a
Minor deviation
MeanBusyPdchUtilCellULSigExc
trf_249b
Minor deviation
MeanBusyPdchUtilCellDLSigExc
trf_250b
Minor deviation
CSDistrEGPRSDL
rlc_57
Full match
ShareEgprsRequ
tbf_65b
Full match
FRLUtilUL
frl_7b
Minor deviation
FRLUtilDL
frl_8b
Minor deviation
RxQuCumUL
ulq_2a, x=5
Full match
RxQuCumDL
dlq_2a, x=5
Full match
MeanPDCHThroughputGprsDL
trf_235b
Minor deviation
MeanPDCHThroughputGprsUL
trf_233c
Minor deviation
MeanPDCHThroughputEdgeDL
trf_236
Minor deviation
MeanPDCHThroughputEdgeUL
trf_234
Minor deviation
Quality/integrity
Table 1
22
KPI mapping (overview) (Cont.)
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
4.1
Accessibility
4.1.1
Voice call setup success rate BSS
BR KPI
BSS KPI
6.3.c
cssr_7c
BR-BSS match
Minor deviation
Comment:
Testing with reference configuration 1 and 2 showed some negligible deviations in NSN
lab testing (absolute error on the range about tenths of %). But it shall be noted that
neither interference nor AGCH blocking are introduced into the tests.
4.1.2
SDCCH congestion time
BR KPI
BSS KPI
ASDCALTI[1] (PM counter)
4.1.3
cngt_2
BR-BSS match
Full match
SDCCH block rate
BR KPI
BSS KPI
SDCCHLossRate
blck_5
BR-BSS match
Full match
Comment:
Testing in NSN lab with reference configuration 1 and 2 did not show any differences.
Both KPIs were equal to 0 but it should be note that no tests are done to introduce any
blocking.
4.1.4
SDCCH real blocking
BR KPI
ImmAssLossRate
BSS KPI
blck_5a
BR-BSS match
Minor deviation
The BR formula counts also Immediate Ass procedures for FACCH if direct TCH assignment feature is enabled. The BSS formula for counting the number of attempts to seize
an SDCCH means counting the channel request not only for new call but also for handover.
Comment:
Testing with reference configuration 1 and 2 in NSN lab showed negligible differences
between the KPIs due to the fact that attempted can arrive in one however evaluated in
the next GP. It should be note that no tests are done to introduce any blocking.
DN0933284
Id:0900d805808c2179
Confidential
23
Mapping of top level KPIs
4.1.5
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Number of immediate assignment messages sent
BR KPI
TACCBPRO[2] (PM counter)
4.1.6
BSS KPI
C3001 - PM counter
TACCBPRO[3] (PM counter)
BSS KPI
C3002
ImmAssNoSize
Full match
BSS KPI
sd_1b
BR-BSS match
Full match
TCH congestion time
BR KPI
AALTCHTI[1] (PM counter)
4.1.9
BR-BSS match
Phantom RACHs
BR KPI
4.1.8
Full match
Number of immediate assignment reject messages
BR KPI
4.1.7
BR-BSS match
BSS KPI
cngt_1
BR-BSS match
Full match
TCH call blocking, before directed retry
BR KPI
AssLossRate
BSS KPI
blck_8i
BR-BSS match
Minor deviation
The denominator of the formula (AssLossRate) deals with the total number of assignment procedures started by MSC. The denominator of the formula (blck_8i) is
decreased by the unsuccessful TCH assignments which were followed by directed retry.
Comment:
Testing with reference configuration 2 in NSN lab showed that in case of higher traffic
the BR KPI may be on the range about tenths of % while GEMINI KPI equal to 0. The
reason for the light blocking was a quite high number of intracell handovers with the
cause: "Forced handover due to multislot calls" to make some reorganization. For
example if there are two HR calls on two timeslots then to move them into one timeslot
and to free the second one for PS call. Detailed analysis showed it is due to different
PS policy in BSS and BR side. In BR side the dynamic channels shared between CS
and PS traffic (defined using the attribute GPDPDTCHA) are primarly for CS traffic
(those channels can be assigned to GPRS or EDGE only if it is possible, i.e. according
to current CS traffic situation). On the other hand in BSS side a PS territory is defined
(using the attribute CDEF) and those channels within the territory are only for PS traffic.
But the territory can be upgraded/downgraded according to the current CS traffic situation. Thanks to the fact that CS and PS territory are strictly separated the amount of
intracell HOs due to GPRS is negligible on BSS side.
24
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
4.1.10
Mapping of top level KPIs
TCH call lossing, before directed retry
BR KPI
BSS KPI
AssLossRateDRInc
blck_8
BR-BSS match
Full match
One TCH is considered as a lost one if the TCH request has been rejected due to lack
of resources or routed by directed retry to another cell.
4.1.11
Queuing time of queued call attempts
BR KPI
BSS KPI
MDURTCRQ[1] FR
que_10
BR-BSS match
Minor deviation
MDURTCRQ[2] HR
The BSS KPI (que_10) takes into account all successful and unsuccessful cases.
The BR KPI takes into account cases when TCH request
•
•
can be satisfied before expiry of T11 or TQHO
is discarded because the queue is already full and the queue place is allocated by
a new TCH request with a higher priority.
The expiration of the timers for maximum queuing duration (T11 or TQHO) is not considered.
In addition the BR measurement provides the results separately for full rate/half rate call
attempts and handover procedure.
4.1.12
Downlink multislot allocation blocking
BR KPI
BSS KPI
TBFEstFailRateConDL
4.1.13
tbf_16b
Full match
Downlink multislot soft blocking
BR KPI
BSS KPI
PercentTSLAchievedDL
4.1.14
BR-BSS match
blk_33b
BR-BSS match
Full match
Downlink temporary block flows per timeslot
BR KPI
BSS KPI
MeanTBFMultiplPDCHDL
tbf_38d
BR-BSS match
Minor deviation
Comment:
Testing with reference configuration 1 with higher CS traffic in NSN lab showed that
there can be quite big differences between BSS and BR KPI (BSS value twice higher
DN0933284
Id:0900d805808c2179
Confidential
25
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
than BR one) and GEMINI (BSC3i) side due to a different PS approach (on BR side horizontal and vertical algorithms while multislot TBF on BSS side are used).
4.1.15
Combined timeslot availability
BR KPI
MeaAvChC
4.1.16
BSS KPI
ava_1g
BR-BSS match
Full match
AGCH blocking
BR KPI
AGCHLossRate
BSS KPI
blck_13 (CS)
BR-BSS match
Minor deviation
blck_21b (PS)
26
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
4.2
Retainability
4.2.1
SDCCH drop rate
Mapping of top level KPIs
BR KPI
BSS KPI
SDCCHDropRatTCHAssFail
sdr_17b
BR-BSS match
Minor deviation
(BR KPI counts some
drops due to Abis and
TRAU problems which
cannot be counted in
BSS KPI.
Comment:
Testing in NSN lab with reference configuration 1 and 2 did not show any differences.
Both KPIs were equal to 0 but it should be note that no interference and fading are
included into the tests.
4.2.2
TCH drop rate per Erlanghour including TCH assignment failures
BR KPI
TCHDropErlhAssFaill
BSS KPI
dcr_26a
BR-BSS match
Minor deviation
BR KPI counts some
drops due to Abis and
TRAU problems which
cannot be counted in
BSS KPI.
The BR KPI counts some drops due to Abis and TRAU problems which cannot be
counted in BSS KPI.
4.2.3
Call drop rate
BR KPI
CallDropRate
BSS KPI
dcr_29
BR-BSS match
Minor deviation
The BR KPI counts some drops due to Abis and TRAU problems which cannot be
counted in BSS KPI.
4.3
Mobility
4.3.1
Handover success rate 2G to 2G (without intracell handover)
BR KPI
HOSuccRate2G2G
DN0933284
BSS KPI
hsr_31
Id:0900d805808c2179
Confidential
BR-BSS match
Full match
27
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Comment:
Testing in NSN lab with reference configuration 1 and 2 showed some differences
between the KPIs (see chap. 4.3.5, 4.3.6)
4.3.2
Handover success rate
BR KPI
HOSuccRate
4.3.3
BSS KPI
hsr_28
BR-BSS match
Full match
Handover success rate 2G to 3G
BR KPI
HOSuccRate2G3G
BSS KPI
hsr_30
BR-BSS match
Full match
Comment:
No 2G - 3G HO calls during the testing in NSN test lab.
4.3.4
Handover drop (2G - 2G, intracell included)
BR KPI
HODropRate2G2G
4.3.5
BSS KPI
hfr_68
HODropRate
BSS KPI
hfr_68c
BR-BSS match
Full match
Outgoing network controlled cell reselection (NCCR) success ratio
BR KPI
NCIntrBSCCellSucRate
4.3.7
Full match
Handover drop rate
BR KPI
4.3.6
BR-BSS match
BSS KPI
nccr_13
BR-BSS match
Minor deviation
Releases per minute TBF duration caused by flush-LL
BR KPI
TBFRelFlushMin
BSS KPI
tbf_63 (uplink)
BR-BSS match
Minor deviation
tbf_64 (downlink)
28
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
4.4
Network Usage
4.4.1
SDCCH traffic carried
(based on sampling - mean number of busy SDCCHs)
BR KPI
BSS KPI
SDCCHTrafCarr
trf_11b
BR-BSS match
Full match
Comment:
Testing with reference configuration 1 and 2 shows some deviations in NSN lab (slightly
lower value in Erlangs for BSS line in comparison to BR line, relative error on the range
about ones of %) due to the fact that different sampling period 20s on BSS while 500ms
on BR side are applied.
4.4.2
SDCCH traffic utilization
BR KPI
SDCCHTrafUtil
BSS KPI
trf_7b
BR-BSS match
Minor deviation
The BR KPI is based on sampling method.
The BSS KPI is based on mean SDCCH holding time in evaluation ot the number of
busy SDCCHs.
Comment:
Testing with reference configuration 1 and 2 confirmed the possible deviations in NSN
lab in such a way that slightly lower value for BSS line in comparison to BR line
observed, absolute shall not exceed 2 %).
4.4.3
TCH traffic carried
BR KPI
TCHTrafCarrDR
BSS KPI
trf_1d
BR-BSS match
Minor deviation
Minor deviation due to different sampling period. The sampling period for BSS KPI is
20 sec and for BR KPI 500 ms.
Comment:
Testing with reference configuration 1 and 2 shows some deviations in NSN lab (slightly
lower value in Erlangs for BSS line in comparison to BR line, relative error on the range
about tenths of %) due to fact that different sampling period 20s on BSS while 500ms
on BR side are applied.
DN0933284
Id:0900d805808c2179
Confidential
29
Mapping of top level KPIs
4.4.4
KPI guidelines for BTSplus migration into the Flexi BSC
product family
TCH traffic share of half rate AMR calls
BR KPI
TCHShareHRAMR
BSS KPI
trf_122a
BR-BSS match
Full match
Comment:
Testing with reference configuration 1 and 2 shows some deviations in NSN lab due to
fact that different algorithms used in BR and BSS side for HR usage.
4.4.5
TCH traffic share of full rate AMR calls
BR KPI
TCHShareFRNBAMR
4.4.6
BSS KPI
trf_121
Full match
TCH traffic share of non AMR calls
BR KPI
TCHSharenonAMR
4.4.7
BR-BSS match
BSS KPI
trf_120a
BR-BSS match
Full match
Network utilization
BR KPI
NTWUtilization
BSS KPI
trf_248a
BR-BSS match
Minor deviation
The BR KPI does not count the TCH/SD in TCHSD_pool (if any) as defined resources.
In the BSS implementation the TCH can be used as SDCCH in SDCCH congestion scenario. Compared to BR implementation they are not declared in the DB.
In addition it shall be considered different sampling period in mean SDCCH calculation
(see “4.4.3 TCH traffic carried”).
Comment:
Testing in NSN test lab with reference configuration 1 and 2 showed quite big differences between the KPI values. Detailed analysis showed, it is due to different using of
dynamic PS channels in BSS and BR side. In BR side the dynamic channels shared
between CS and PS traffic (defined using the attribute GPDPDTCHA) are primarly for
CS traffic (those channels can be assigned to GPRS or EDGE only if possible, i.e.
according to current CS traffic situation). Therefore all the channels are counted in the
BR formula. On the other hand in BSS side the dynamic channels (defined using the
attribute CDEF) are primarly for PS traffic (those channels can be assigned to CS only
if possible, i.e. according to current PS traffic situation). Therefore the channels are not
counted in the BSS formula.
Example: From a test for configuration 2 in NSN test lab resulted the following:
Busy TSsBR (numerator of 9.1.9)
= 16,21 TCHs
Busy TSs GEMINI (Numerator of trf_249a) = 16,267 TCHs
30
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
However
Network utilization BR (9.1.9)
= 27,01 %
Network utilization GEMINI (trf_248a)
= 57,48 %
The reason of such finding is that on BR side the total number of defined TSLs, i.e. 60
counted in the BR formula (9.1.9) [16,21/60 = 0,2701 (27,01 %)] while on BSS side
despite the total number of defined TSLs is the same only 30 of them counted within
trf_248a as the attribute CDEF set to 55 %. In addition the PS territory may be
upgraded/downgraded in dependence on CS traffic situation. The remaining 30 TSLs
belong to PS territory and therefore can only be used for PS calls.
4.4.8
User data volume on radio interface per cell uplink
BR KPI
UserVolUmCellUL
•
•
•
BSS KPI
trf_243
BR-BSS match
Minor deviation
The BSS KPI has to be multiplied with 1024•1024•1024•8/1000=8.6•106 for the unit
of the KPI is GB.
Preventive retransmissions by the MS are counted as data volume. This may cause
an increase in calculation of BR KPI in comparison to BSS KPI. For short duration
TBF (GMM/SM activities) the error is larger than for medium or long duration TBFs
(e.g. WAP session or ftp).
The BR KPI takes into account the length field in RLC data block. The BSS KPI does
not use the length field, i.e. blocks are counted as maximum length corresponding
to applied coding scheme. This may cause slight decrease in calculation of BR KPI
in comparison to BSS KPI.
Comment:
Testing in NSN test lab with reference configuration 1 and 2 showed quite big differences between the KPI values (the relative error about 30 % - BR KPI is always higher
than BSS one). Preventive retransmissions by the MS which are counted as data
volume on BR side are the reason.
4.4.9
User data volume on radio interface per cell downlink
BR KPI
UserVolUmCellDL
•
•
•
DN0933284
BSS KPI
trf_244
BR-BSS match
Minor deviation
The BSS KPI has to be multiplied with 1024•1024•1024•8/1000=8.6•106 for the unit
of the KPI is GB.
The BR KPI takes into account the length field in RLC data block. The BSS KPI does
not use the length field, i.e. blocks are counted as maximum length corresponding
to applied coding scheme. This may cause slight decrease in calculation of BR KPI
in comparison to BSS KPI.
Dummy blocks are counted as data volume. This may cause an increase in calculation of BR KPI in comparison to BSS KPI. For short duration TBF (GMM/SM activi-
Id:0900d805808c2179
Confidential
31
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
ties) the error is larger than for medium or long duration TBFs (e.g. WAP session or
ftp).
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed the KPIs providing
quite similar values (the relative error below 10 %).
4.4.10
Average number of busy packet channels uplink
BR KPI
MeanPDCHBusyCellUL
BSS KPI
trf_238
BR-BSS match
Full match
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to different PS
approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.11
Average number of busy packet channels downlink
BR KPI
MeanPDCHBusyCellDL
BSS KPI
trf_239
BR-BSS match
Full match
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to a different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.12
PDCH utilization rate uplink
BR KPI
MeanBusyPdchUtilCellUL
BSS KPI
trf_249a
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged mode.
Comment:
Comment: Testing in NSN test lab with reference configuration 2 and 3 showed that
these KPIs can not be evaluated separately but only in a combination to other ones due
to different PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.13
PDCH utilization rate downlink
BR KPI
MeanBusyPdchUtilCellDL
32
BSS KPI
trf_250a
Id:0900d805808c2179
Confidential
BR-BSS match
Minor deviation
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged mode.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to different PS
approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.14
PDCH utilization rate uplink, signaling excluded
BR KPI
BSS KPI
MeanBusyPdchUtilCellULSigExc
trf_249b
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged mode.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to a different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.15
PDCH utilization rate downlink, signaling excluded
BR KPI
BSS KPI
MeanBusyPdchUtilCellDLSigExc
trf_250b
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged mode.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to different PS
approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.4.16
Coding scheme distribution EGPRS RLC downlink
BR KPI
BSS KPI
CSDistrEGPRSDL
4.4.17
Full match
Share of EGPRS requests
BR KPI
ShareEgprsRequ
DN0933284
rlc_57
BR-BSS match
BSS KPI
tbf_65b
Id:0900d805808c2179
Confidential
BR-BSS match
Full match
33
Mapping of top level KPIs
4.4.18
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Gb interface frame relay link utilization rate uplink
BR KPI
FRLUtilUL
BSS KPI
frl_7b
BR-BSS match
Minor deviation
For BR KPI the NS signaling is included.
For BSS KPI the NS signaling is not included.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 confirmed some differences
between the KPIs. BR KPI provide slightly higher values but the relative error was below
3 %.
4.4.19
Gb interface frame relay link utilization rate downlink
BR KPI
FRLUtilDL
BSS KPI
frl_8b
BR-BSS match
Minor deviation
For BR KPI the NS signaling is included.
For BSS KPI the NS signaling is not included.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 confirmed some differences
between the KPIs. BR KPI provide slightly higher values but the relative error was below
3 %.
34
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
4.5
Quality/Integrity
4.5.1
Cumulative quality in class x uplink
BR KPI
BSS KPI
RxQuCumUL
ulq_2a, x=5
BR-BSS match
Full match
Comment:
Testing in NSN lab with reference configuration 1 and 2 did not show any significant differences between the KPIs.
4.5.2
Cumulative quality in class x downlink
BR KPI
BSS KPI
RxQuCumDL
dlq_2a, x=5
BR-BSS match
Full match
Comment:
Testing in NSN lab with reference configuration 1 and 2 did not show any significant differences between the KPIs.
4.5.3
GPRS RLC throughput per radio timeslot downlink
BR KPI
BSS KPI
MeanPDCHThroughputGprsDL
•
•
trf_235b
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged
mode.
On BR side preemptive retransmissions are considered like retransmissions due to
bad radio quality.
On BSS side they are not counted in the related retransmission counter.
This may cause an slight decrease in calculation of BR KPI in comparison to BSS
KPI.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to the different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.5.4
GPRS RLC throughput per radio timeslot uplink
BR KPI
BSS KPI
MeanPDCHThroughputGprsUL
DN0933284
trf_233c
Id:0900d805808c2179
Confidential
BR-BSS match
Minor deviation
35
Mapping of top level KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
•
•
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged
mode.
Preventive retransmissions by the MS are counted as data volume. This may cause
an increase in calculation of BR KPI in comparison to BSS KPI. For short duration
TBF (GMM/SM activities) the error is larger than for medium or long duration TBFs
(e.g. WAP session or ftp).
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to the different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.5.5
EGPRS RLC throughput per radio timeslot downlink
BR KPI
MeanPDCHThroughputEdgeDL
•
•
BSS KPI
trf_236
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged
mode.
On BR side preemptive retransmissions are considered like retransmissions due to
bad radio quality.
On BSS side they are not counted in the related retransmission counter.
This may cause an slight decrease in calculation of BR KPI in comparison to BSS
KPI.
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to the different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
4.5.6
EGPRS RLC throughput per radio timeslot uplink
BR KPI
MeanPDCHThroughputEdgeUL
•
•
36
BSS KPI
trf_234
BR-BSS match
Minor deviation
The BSS KPI takes into account RLC acknowledged mode only.
The BR KPI takes into account both RLC acknowledged and unacknowledged
mode.
Preventive retransmissions by the MS are counted as data volume. This may cause
an increase in calculation of BR KPI in comparison to BSS KPI. For short duration
TBF (GMM/SM activities) the error is larger than for medium or long duration TBFs
(e.g. WAP session or ftp).
Id:0900d805808c2179
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Mapping of top level KPIs
Comment:
Testing in NSN test lab with reference configuration 2 and 3 showed that these KPIs can
not be evaluated separately but only in a combination to other ones due to the different
PS approach used on BR and BSS side (see “Verification of PS KPI comparison”).
DN0933284
Id:0900d805808c2179
Confidential
37
Reference configuration
KPI guidelines for BTSplus migration into the Flexi BSC
product family
5 Reference configuration
The tests were done with the following configurations:
•
•
•
•
38
Configuration 1: CS only
see: Reference configuration CS only
Configuration 2: Mixed CS and PS
see: Reference configuration mixed CS PS
Configuration 3: PS only
see: Reference configuration PS only
BTS configuration for all the profiles was: 4+4 1900/800 : EGPRS enabled.
More detailed information about the attributes setting including also eBSC/BSC1
can be found in the attached documents for BR/BSS product line.
see: Reference configuration BR attributes and
see: Reference configuration BTSplus migration to FlexiBSC
Id:0900d80580702e54
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Verification of PS KPI comparison
6 Verification of PS KPI comparison
This chapter shows that even though some PS KPIs show different results before and
after the migration they are leading to the same overall result which is in this case RLC
payload.
In the BR and BSS product lines different PS approaches exist. Horizontal and vertical
algorithms on the BR side and multislot TBF on the BSS side are used. The KPI are
comparable apart from the different PS approach but there may be quite big differences
between them. There are differences before and after the migration in the following
KPIs:
•
•
•
•
Average number of busy PDCH UL/DL (4.4.10/4.4.11)
PDCH utilization rate UL/DL (4.4.12/4.4.13)
PDCH utilization rate, signaling excluded UL/DL (4.4.14/4.4.15)
Throughput per radio timeslot UL/DL (4.5.3 - 4.5.6)
Even though the "Downlink/Uplink TBFs per timeslot" and initial coding schemes are the
same for the BR and the BSS side, the above mentioned KPIs will not be the same for
both product lines. The reason is the different interface concept. For BR side flexible
Abis and for BSS side dynamic Abis is used. This leads to some differences in the frequency of using the coding schemes. It also has to be considered that algorithms for link
adaptation implemented within eBSC/BSC1 and Flexi BSC are different.Taking into
account the definitions of the above mentioned KPIs for the UL RLC payload on BSS
side we can write
UL_aver_busy_PS_channels(trf_238) ⋅
UL_RLC_Payload(trf_243) =
UL_PDCH_util_rate_sign_exc(trf_249b) ⋅
UL_EDGE_Throughput_TSL(trf_234) ⋅ GP ⋅ 60
(Eq. 1)
Where only EGPRS traffic considered as GPRS traffic was excluded from the tests.
From the (Eq. 1) we receive for UL_EDGE_Throughput_TSL that
UL_RLC_payload(trf_243)
UL_EDGE_Throughput_TSL(Cal) = ----------------------------------------------------------------------------------------------------------------------⎛ UL_aver_busy_PS_channels(trf_238) ⋅ ⎞
⎜ UL_PDCH_util_rate_sign_exc(trf_249b) ⋅ ⎟
⎜
⎟
⎝
⎠
GP ⋅ 60
(Eq. 2)
Where (Cal) means “calculated”
As an example in order to prove the stability of (Eq. 2) the measured (trf_234) and calculated UL EDGE Throughput per TSL curves can be seen in “Figure 5”.
DN0933284
Id:0900d80580700abc
Confidential
39
Verification of PS KPI comparison
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Figure 5
Measured (trf_234) and calculated UL EDGE Throughput per TSL curves
(x is a time axis given in GP)
Corresponding relative error [%] in calculation of UL EDGE Throughput per TSL is
shown in “Figure 6” which only confirms that the calculation is done with quite good precision (relative error less than approximately 3%). It should be noted that the above
results are related to tests where only ack traffic mode is used while in practice some
amount of unack mode traffic is also realistic which may lead to an error increase due
to fact that trf_243 counts both ack and unack while trf_249b and trf_234 only ack mode
traffic. But using only ack mode shall be a must.
40
Id:0900d80580700abc
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Figure 6
Verification of PS KPI comparison
Relative error in calculation of UL EDGE Throughput per TSL (x is a time
axis given in GP)
Similar equation we can be constructed for DL RLC payload on BR side where
UL_aver_busy_PS_channels(18.2.7e) ⋅
UL_RLC_payload(18.2.17a) =
UL_PDCH_util_rate_sign_exc(18.2.8c) ⋅
UL_EDGE_Throughput_TSL(18.2.14b) ⋅ GP ⋅ 60
(Eq. 3)
and only EGPRS is considered, as GPRS traffic was excluded from the tests.
Then from the (Eq. 3) we receive for UL EDGE Throughput per TSL that
UL_RLC_payload(18.2.17)
UL_EDGE_Throughput_TSL(Cal) = --------------------------------------------------------------------------------------------------------------UL_aver_busy_PS_channels(18.2.7e) ⋅
UL_PDCH_util_rate_sign_exc(18.2.8c) ⋅
GP ⋅ 60
(Eq. 4)
As an example in order to prove the stability of (Eq. 4) the measured (18.2.14b) and calculated UL EDGE Throughput per TSL curves can be seen in “Figure 7”.
DN0933284
Id:0900d80580700abc
Confidential
41
Verification of PS KPI comparison
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Figure 7
Measured (18.2.14b) and calculated UL EDGE Throughput per TSL curves
(x is a time axis given in GP)
The corresponding relative error [%] in the calculation of UL EDGE Throughput per TSL
is shown in “Figure 8”. The relative error is less than approximately 6 %. It has to be
taken into account that within UL RLC Payload (see “4.4.8 User data volume on radio
interface per cell uplink”), the length field in the RLC data block is considered while in
formula UL_PDCH_Util_rate_sign_exc in the (Eq. 4) blocks are counted as maximum
length corresponding to the applied coding scheme. This explains why on the BR side
the calculated UL RLC payload is equal to or less than the measured one
(UL_RLC_payload).
42
Id:0900d80580700abc
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Figure 8
Verification of PS KPI comparison
Relative error in calculation of UL EDGE Throughput per TSL (x is a time
axis given in GP)
From the above verification of the (Eq. 1) - (Eq. 4) it follows that the related KPIs
provide the correct results when evaluating them separately for BR and BSS and therefore shall be comparable. While when comparing them before and after the migration
quite big differences may be observed due to different PS approaches on the BR and
the BSS sides. Nevertheless, the overall results, e.g. for RLC payload, are similar at the
end. For the differences, see “4.4.8 User data volume on radio interface per cell uplink”.
For instance, throughput per TSL might be higher on the BSS side and the “Average
Busy of PDCH” can be similar on both sides, but the RLC throughput is similar, because
the PDCH utilization rat is significantly higher on the BR side (see table below). Reconfiguring the network during migration in order to obtain equal KPI values is not recommended, as the BTSplus on the BR side operates in an optimal way with the
eBSC/BSC1 setting before migration and with the Flexi BSC setting after migration. The
customer shall therefore be instructed when dealing the above mentioned KPIs before
and after the migration are comparable or not to evaluate always overall situation as
described in this part and not only to concentrate on one KPIs pair.
UL EGPRS
throughput per
TSL
UL PDCH utilization rate, signaling excluded
UL aver busy
PDCH
UL RLC payload
53.98 kbit/s
18.75%
23.83
858237 kbit/s
18.33 kbit/s
60.54%
22.403
884000 kbit/s
Notes
DN0933284
Id:0900d80580700abc
Confidential
43
Verification of PS KPI comparison
KPI guidelines for BTSplus migration into the Flexi BSC
product family
1. In order to get the correct results in the above (Eq. 2) and (Eq. 4), the unit of UL RLC
payload has to be kbit/s, the UL PDCH utilization rate has to be non-dimensional
value (not %), and the unit of the GP has to be minutes.
2. Similar analysis can be done for DL EDGE.
3. The described evidence using the above equations is only valid for the network with
GPRS or EGPRS traffic is more realistic. However, combined GPRS and EGPRS
traffic is more realistic. Therefore, instead of UL/DL GPRS/EGPRS throughput per
TSL, the UL/DL throughput per TSL KPI has to be used in this case.
4. On the BSS side, MCS-9 codec is mainly used while on BR side, the MCS-6 codec
is used (rf. 3GPP TS 04.60 Section 8.1.1).
Furthermore, the MCS codec scheme of additional transmissions might differ from the
MSC codec of the uplink TBF. This is allowed and typically occurs when the transmission only requires as many radio blocks as are available using an alternate MCS. For
example, if the commanded MCS is MCS-9 which sends 2 RLC data blocks, and the
mobile station only needs to send one RLC data block, it may choose to send it using
MCS-6, which sends only one data block and is also more robust.
But the difference can also be described using the incremental redundancy (IR) feature.
The next graph shows that the RLC throughput per TSL depends on SNR (C/I) for MCS6 and MCS-9 with and without the IR feature. The results for MCS-9 with IR shows that
the codec might have similar or sometimes better characteristics than MCS-6.
Figure 9
Dependence of the RLS throughput per TSL on SNR (C/I) for MCS-6 and
MCS-9 with and without IR feature
Therefore, significant differences of the throughput per TSL values before and after
migration does not necessarily indicate an error. As already shown, the characteristics
of MCS-9 and MCS-6 are similar.
44
Id:0900d80580700abc
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Definitions for non-benchmark KPIs
7 Definitions for non-benchmark KPIs
This chapter provides KPI formulas for non-benchmark BSS14 KPIs which are
employed in chapter “Mapping of top level KPIs”. For formula definitions the syntax of
NetAct is used.
The KPI formulas for benchmark KPIs are provided in “RG10(BSS) EDGE, GPRS, and
GSM Voice Key Performance Indicators”.
7.1
blck_1a
blck_1a =
sum ( tch_req_lack ( c001011 ) – tch_rej_due_req_ch_a_if_crc ( c001122 ) )
100 ⋅ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum ( tch_request ( c001010 ) – tch_rej_due_req_ch_a_if_crc ( c001122 ) )
Attribute unit: %
Counters from table(s): p_nbsc_traffic
7.2
blck_5
sum(sdcch_busy_att(c001001))
blck_5 = 100 ⋅ -----------------------------------------------------------------------------------sum(sdcch_seiz_att(c001000))
Attribute unit: %
7.3
blck_5a
blck_5a =
sum(sdcch_busy_att(c001001) – tch_seiz_due_sdcch_con(c01099))
100 ⋅ ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(sdcch_seiz_att(c001000))
Attribute unit: %
7.4
blck_8
blck_8 =
sum(tch_call_req(c001026) – tch_norm_seiz(c001009))
100 ⋅ -------------------------------------------------------------------------------------------------------------------------------------------------sum(tch_call_req(c001026))
Attribute unit: %
Counters from table(s): p_nbsc_traffic
7.5
blck_13
sum(del_ind_msg_rec(c003005))
blck_13 = 100 ⋅ ----------------------------------------------------------------------------------------------------------------------------------------------------------------sum(imm_assgn_rej(c003002) + imm_assgn_sent(c003001))
Attribute unit: %
DN0933284
Id:0900d805807d5fa0
Confidential
45
Definitions for non-benchmark KPIs
7.6
KPI guidelines for BTSplus migration into the Flexi BSC
product family
blck_21b
blck_21b = 100 ⋅
sum(packet_immed_ass_nack_msg(c072086))
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(packet_immed_ass_ack_msg(c072085)) + packet_immed_ass_nack_msg(c072086))
Attribute unit: %
7.7
cngt_1
sum(tch_cong_time(c002026))
cngt_1 = --------------------------------------------------------------------------------100
Attribute unit: second
Counters from table(s): p_nbsc_res_avail
7.8
cngt_2
sum(sdcch_cong_time(c002033))
cngt_2 = ----------------------------------------------------------------------------------------100
Attribute unit: second
Counters from table(s): p_nbsc_res_avail
7.9
cssr_7c
⋅ (1 – sdr_17a) ⋅ csf_44a
cssr_7c = trf_467b
--------------------------------------------------------------------------------------4
100
Attribute unit: %
see “RG10(BSS) EDGE, GPRS, and GSM Voice Key Performance Indicators”
7.10
trf_467
trf_467 =
sum(IMM_ASSGN_SENT(c003001) - DEL_IND_MSG_REC(c003005))
100 ⋅ -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(CH_REQ_MSG_REC(c003004)
Attribute unit: %
Counters from table(s): p_nbsc_res_access
46
Id:0900d805807d5fa0
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
7.11
Definitions for non-benchmark KPIs
csf_43b
⎞
⎛
⎟
⎜
⎟
⎜ sum(a.SDCCH_RADIO_FAIL + a.SDCCH_RF_OLD_HO + aSDCCH_USER_ACT +
⎜ a.sdcch_bcsu_reset + a. sdcch_netw_act + a.sdcch_abis_fail_old + a. sdcch_bts_fail + a.sdcch_lapd_fail ) ⎟
⎟
csf_43b = 100.⎜1 −
sum(b.SDCCH_ASSIGN)
⎟
⎜
⎟
⎜
⎟
⎜
⎟
⎜
⎠
⎝
Attribute unit: %
Counters from table(s):
p_nbsc_traffic
p_nbsc_service
7.12
csf_44b
sum(tch_new_call_assign(c057033) - served_facch_req(c057018) + msc_o_sdcch_tch(c004050) +
+ bsc_o_sdcch_tch(c004065) + cell_sdcch_tch(c004074) - msc_i_sdcch_tch(c004044) +
+ bsc_i_sdcch_tch(c004057)))
csf_44b = 100 ⋅
sum(tch_new_call_assign(c057033) - served_facch_req(c057018) + msc_o_sdcch_tch(c004050) +
+ bsc_o_sdcch_tch(c004065) + cell_sdcch_tch(c004074) - msc_i_sdcch_tch(c004044) +
+ bsc_i_sdcch_tch(c004057) + TCH_REQUESTS_CALL_ATTEMPT(c001192) -
- SUCC_TCH_SEIZ_CALL_ATTEMPT(c001193))
a
Attribute unit: %
Counters from table(s):
p_nbsc_traffic
p_nbsc_service
p_nbsc_ho
DN0933284
Id:0900d805807d5fa0
Confidential
47
Definitions for non-benchmark KPIs
7.13
KPI guidelines for BTSplus migration into the Flexi BSC
product family
dcr_26a
sum(a.tch_radio_fail(c001013)
- a.TCH_REL_DUE_RAD_FAIL_PH_2_3(c001205)
+ a.tch_rf_old_ho(c001014)
+ a.tch_lapd_fail(c001046)
+ a.tch_bts_fail(c001047)
dcr _ 26a =
A
+ a.tch_user_act(c001048)
+ a.tch_bcsu_reset(c001049)
+ a.tch_netw_act(c001050)
+ a.TCH_ABIS_FAIL_OLD(c001085)
+ a.TCH_TR_FAIL_OLD(c001030) )
trf_1d
* (60/avg(period_duration))
Counters from table(s):
a = p_nbsc_traffic
b = p_nbsc_ps_dtm
c = p_nbsc_res_avail
48
Id:0900d805807d5fa0
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
7.14
Definitions for non-benchmark KPIs
dcr_29
sum(a.tch_radio_fail(c001013)
- a.TCH_REL_DUE_RAD_FAIL_PH_2_3(c001205)
+ a.tch_rf_old_ho(c001014)
+ a.tch_lapd_fail(c001046)
+ a.tch_bts_fail(c001047)
+ a.tch_user_act(c001048)
+ a.tch_bcsu_reset(c001049)
a
+ a.tch_netw_act(c001050)
+ a.TCH_ABIS_FAIL_OLD(c001085)
+ a.TCH_TR_FAIL_OLD(c001030) )
dcr _ 29 = 100 *
sum(a.tch_radio_fail(c001013)
- a.TCH_REL_DUE_RAD_FAIL_PH_2_3(c001205)
+ a.tch_rf_old_ho(c001014)
+ a.tch_lapd_fail(c001046)
+ a.tch_bts_fail(c001047)
+ a.tch_user_act(c001048)
+ a.tch_bcsu_reset(c001049)
+ a.tch_netw_act(c001050)
+ a.TCH_ABIS_FAIL_OLD(c001085)
+ a.TCH_TR_FAIL_OLD(c001030)
+ TCH_NORM_R ELEASE(c057035) )
Counters from table(s):
a = p_nbsc_traffic
b = p_nbsc_service
7.15
frl_7b
frl_7b = 100 ⋅
sum ( 8 ⋅ ( dlci_1_bytes_sent + dlci_2_bytes_sent + ... + dlci_16_bytes_sent ) )/ ( period_duration ⋅ 60 )
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum per frbc over all unlocked child nsvc ( c_nsvc.commited_info_rate ⋅ 16 )
Attribute unit: %
frbc object_instance = bearer_id in p_nbsc_frame_relay
DN0933284
Id:0900d805807d5fa0
Confidential
49
Definitions for non-benchmark KPIs
7.16
KPI guidelines for BTSplus migration into the Flexi BSC
product family
hsr_30
sum(msc_to_wcdma_ran_succ_tch_ho(c004158))
hsr_30 = 100 ⋅ ------------------------------------------------------------------------------------------------------------------------------------sum(msc_tch_ho_wcdma_ran_att(c004150))
Attribute unit: %
7.17
hsr_31
hsr_31 =
sum(a.msc_o_succ_ho(c004004) + a.bsc_o_succ_ho(c004014))
100 ⋅ -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(b.msc_o_ho_cmd(c001195) + b.bsc_o_ho_cmd_assgn(c001196))
Attribute unit: %
Counters from table(s): a = p_nbsc_ho; b = p_nbsc_traffic
7.18
hfr_68
hfr_68 = 100 ⋅
all call drops
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------all ho attempts – ho fail due to blocking – ho fail due to not allowed – wrong A interf circuit type
Attribute unit: %
•
•
•
•
•
7.19
“all call drops”
Sum(bsc_o_drop_calls(c004084) + msc_o_call_drop_ho(c004107) +
cell_dropt_calls(c004085))
“all ho attempts”
Sum(msc_o_tch_tch_at(c 004052) + msc_o_sdcch_tch_at(c 004053) +
msc_o_sdcch_at(004054) + bsc_o_tch_tch_at(c 004067) +
bsc_o_sdcch_tch_at(c 004068) + bsc_o_sdcch_at(c 004069) +
cell_tch_tch_at(c 004076) + cell_sdcch_tch_at(c 004077) +
cell_sdcch_at(c 004078))
“ho fail due to blocking”
Sum(msc_o_fail_lack(c 004055) + bsc_o_fail_lack(c 004072) +
cell_fail_lack(c 004019))
“ho fail due to not allowed”
Sum(msc_o_not_allwd(c 004037) + bsc_o_not_allwd(c 004038) +
cell_not_allwd(c 004036))
“wrong A interf circuit type”
Sum(bsc_o_unsucc_a_int_circ_type(c 004096) +
msc_controlled_out_ho(c 004102) + ho_unsucc_a_int_circ_type(c 004098))
nccr_13
nccr_succ_flush_received(c095012)
nccr_13 = 100 ⋅ -----------------------------------------------------------------------------------------------nccr_1
Attribute unit: %
50
Id:0900d805807d5fa0
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
nccr_1 =
Definitions for non-benchmark KPIs
a.ncr_not_started_due_ac(c 095015) +
b.nccr_qc_trig_no_good_neig(c 072185) +
b.nccr_serv_isnccr_no_good_neig(c
072186) +a.pcco_to_gprs_ms_due_pwr_bdgt(c 095002) +
a.pcco_to_egprs_ms_due_pwr_bdgt(c 095003) +
a.pcco_sent_due_serv_isnccr (c095004) +
a.PCCO_sent_due_coverage_isnccr(c 095005) +
a.PCCO_SENT_DUE_QUAL_CTRL(c 095006)
7.20
que_10
sum(ave_q_tim_call_att(c001020))
que_1 = -------------------------------------------------------------------------------------------sum(queue_denom2(c001021))
Attribute unit: second
Counters from table(s): p_nbsc_traffic
7.21
rlc_57
Sum over MCS-n (DL_RLC_Blocks_In_Ack_Mode(c079000))
rlc_57 = 100 ⋅ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------Sum over MCS 1-9 (DL_RLC_Blocks_In_Ack_Mode(c079000))
Attribute unit: %
Counters from table(s): p_nbsc_coding_scheme
7.22
sd_1b
sd_1b =
sum(a.sdcch_assign(c001007)) – sum(b.succ_seiz_term(c003012)) +
b.succ_seiz_orig(c003013) + b.sdcch_loc_upd(c003019) +
b.sdcch_emerg_call(c003021) + b.sdcch_call_re_est(c003020) +
imsi_detach_sdcch(c003033) + b.succ_seiz_supplem_serv(c003044)
Attribute unit: none
Counters from table(s): a = p_nbsc_traffic; b = p_nbsc_res_access
7.23
sdr_17a
sdr_17a =
sum(a.sdcch_radio_fail(c001003)) + a.sdcch_rf_old_ho(c001004) + a.sdcch_user_act(c001037)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(b.succ_seiz_term(c003012)) + b.succ_seiz_orig(c003013) + b.sdcch_loc_upd(c003019) +
b.sdcch_emerg_call(c003021) + b.sdcch_call_re_est(c003020) + imsi_detach_sdcch(c003033) +
success_seizure_for_ho(c001006)
Attribute unit: none
DN0933284
Id:0900d805807d5fa0
Confidential
51
Definitions for non-benchmark KPIs
7.24
KPI guidelines for BTSplus migration into the Flexi BSC
product family
tbf_63
ul_tbf_rel_due_to_flush(c072058)
tbf_63 = 60 ⋅ 100 ⋅ ----------------------------------------------------------------------------------------ave_dur_ul_tbf_sum(c072003)
7.25
trf_7b
trf_7b =
•
•
•
•
SDCCH used time
100 ⋅ ----------------------------------------------------------- ⋅
SDCCH resource time
SDCCH seizures ⋅ avg SDCCH seizure length
100 ⋅ ----------------------------------------------------------------------------------------------------------------------------------------avg total nbr of SDCCH ⋅ period duration in seconds
“SDCCH seizures”
Sum(b.sdcch_assign(c001007) + b.sdcch_ho_seiz(c001006) +
b.tch_seiz_due_sdcch_con(c001099))
“avg SDCCH seizure length”
avg(a.ave_sdcch_hold_tim(c002034) / a.res_av_denom16(c002035)/100
“avg total nbr of SDCCH”
a.ave_sdcch_sub(c002004) / a.res_av_denom3(c002005) +
a.ave_non_avail_sdcch(c002038_1))
“period duration in seconds”
a.period_duration · 60
Attribute unit: %
Counters from table(s): a = p_nbsc_res_avail; b = p_nbsc_traffic
7.26
trf_238
sum(ave_busy_gprs_ch_ul(c072168)
trf_238 = -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------(avg(ave_busy_gprs_ch_den(c072170) ⋅ count(distinct_period_start_time))
Attribute unit: Erlang
7.27
trf_239
sum(ave_busy_gprs_ch_dl(c072169)
trf_239 = -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------(avg(ave_busy_gprs_ch_den(c072170) ⋅ count(distinct_period_start_time))
Attribute unit: Erlang
7.28
trf_248a
trf_248a = 100 ⋅
sum(ave_tch_busy_full(c002046_1) + ave_tch_busy_half(c002048_1)/2)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------sum(ave_avail_tch_timeslot_c(c002059) + ave_non_avail_tch_timeslot(c002069))
Counters from table(s): p_nbsc_res_avail
52
Id:0900d805807d5fa0
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
7.29
Definitions for non-benchmark KPIs
trf_249a
( trf_161i + trf_205d )
trf_249a = 100 ⋅ ----------------------------------------------------trf_238
trf_161i and trf_205d are benchmark KPIs
see “RG10(BSS) EDGE, GPRS, and GSM Voice Key Performance Indicators”
7.30
trf_250a
( trf_162g + trf_208c )
trf_250a = 100 ⋅ -----------------------------------------------------trf_239
trf_162g and trf_208c are benchmark KPIs
see “RG10(BSS) EDGE, GPRS, and GSM Voice Key Performance Indicators”
7.31
trf_249b
a.rlc_data_blocks_ul_cs1(c72062) + a.rlc_data_blocks_ul_cs2(c72064) +
⎛
⎞
⎜ a.retra_data_blocks_ul_cs1(c72173) + a.retra_data_blocks_ul_cs2(c72174) +
⎟
⎜
⎟
sum
over
MCS1..6
of
(yy)
+
sum
over
MCS11..12
of
(yy)
+
sum
over
MCS7..9
of
(yy)
⎜ -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------⎟
⎜
⎟
2
⎜
⎟
⎜
⎟
⎝
⎠
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------avg(period_duration
⋅
60
)
⋅
count(distinct
period_start_time)
⋅
50
trf_249b = ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------trf_238
where
yy = b.ul_rlc_blocks_in_ack_mode(c79002) + b.retrans_rlc_data_blocks_ul(c79008)
Counters from table(s): a = p_nbsc_packet_control_unit, b = p_nbsc_coding_scheme
7.32
trf_250b
a.rlc_data_blocks_dl_cs1(c72063) + a.rlc_data_blocks_dl_cs2(c72065) +
⎛
⎞
⎜ a.retra_data_blocks_dl_cs1(c72068) + a.retra_data_blocks_dl_cs2(c72069) +
⎟
⎜
⎟
sum over MCS1..6 of (yy) + sum over MCS11..12 of (yy) + sum over MCS7..9 of (yy)⎟
⎜ ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------⎜
⎟
2
⎜
⎟
⎜
⎟
⎝
⎠
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------avg(period_duration ⋅ 60 ) ⋅ count(distinct period_start_time) ⋅ 50
trf_250b = ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------trf_239
where
yy = b.dl_rlc_blocks_in_ack_mode(c79000) + b.retrans_rlc_data_blocks_dl(c79009)
Counters from table(s): a = p_nbsc_packet_control_unit, b = p_nbsc_coding_scheme
DN0933284
Id:0900d805807d5fa0
Confidential
53
Definitions for non-benchmark KPIs
7.33
KPI guidelines for BTSplus migration into the Flexi BSC
product family
trf_536
numerator(trf_236) + numerator(trf(235_b)
trf_536 = -------------------------------------------------------------------------------------------------------------------------------denominator(trf_236) + denominator(trf(235_b)
7.34
trf_534
numerator(trf_234) + numerator(trf(233_c)
trf_534 = ------------------------------------------------------------------------------------------------------------------------------denominator(trf_234) + denominator(trf(233_c)
54
Id:0900d805807d5fa0
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Definition of additional BR 9.0 product line KPIs
8 Definition of additional BR 9.0 product line
KPIs
The purpose of this chapter is the definition of additional BR 9.0 key performance indicators for operating the BTSplus with the Flexi BSC product family. Since an update of
“PM: SBS Key Performance Indicators” for BR 9.0 product line is not scheduled, the
additional BR 9.0 KPIs are defined within this chapter.
8.1
Assignment failure rate
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 5 “Assignment analysis”.
Formula a) to e) see section 5.4 “Assignment failure rate”.
Long name: (f) Assignment Loss Rate directed retries included
Short name: (f) AssLossRateDRInc
Description: These indicators provide the assignment failure rates. The assignment
procedure is unsuccessful if the BSC returns a assignment failure
message to the MSC or if the directed retry in the target cell was not successful.
Formula:
AssLoss + TASSFAIL [ 9 ,14 ]
AssLossRateDRInc = -------------------------------------------------------------------------AssAtt
Used param: AssAtt, AssLoss, AssFailbyMess, AssFailOther, QueFail, AssFail,
TASSFAIL[9,14]
8.2
Element
object:
Cell
Unit:
None
Remark:
Assignments of SDCCH are not considered
Timeslot utilization
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 9 “TCH load
related performance indicators”, section “TCH load for circuit switched traffic”, new
subsection 9.1.9.
Long name: (a) Timeslot Utilization
Short name: (a) TSUtilization
Description: This indicator provides the timeslot utilization. In comparison to the TCH
(Traffic Utilization) the KPI is independendent. Half rate is enabled or disabled.
DN0933284
Id:0900d80580703c1a
Confidential
55
Definition of additional BR 9.0 product line KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Formula:
MEBUSTCH [ 1,3 ] + MEBUSTCH [ 2, 4 ] ⁄ 2
TSUtilization = ---------------------------------------------------------------------------------------------------------------NRDEFTCH [ 6,12 ]
NRDEFTCH [ 3,9 ] + ------------------------------------------------2
Used param: MEBUSTCH[all], NRDEFTCH[all]
8.3
Element
object:
Cell
Unit:
None
Remark:
The KPI has ranges from 0 to 200%. Half rate calls are individually
counted at nominator, and contribute with 0.5 at denominator. If all
timeslots are busy by full rate calls it leads to 100% network utilization. If
all timeslots are busy by half rate calls it leads to 200% network utilization. In case of mixed configuration such as some TRXs with full rate TCH
and some others with directed retries, the 100% can be reached even if
not all full rate are busy in the network.
Total TCH busy time
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 9 “TCH load
related performance indicators”, section “TCH load for circuit switched traffic”, new
subsection 9.1.10.
Long name: (a) Total TCH busy time full rate
(b) Total TCH busy time half rate
Short name: (a) TotBusyTCHTimeFR
(b) TotBusyTCHTimeHR
Description: This indicator provides the total TCH busy time. Given indicators differentiate between full rate and half rate.
Formula:
(a)
TotBusyTCHTimeFR = MEBUSTCH [ 1,3 ] ⋅ GP ⋅ 60
(b)
TotBusyTCHTimeHR = MEBUSTCH [ 2,4 ] ⋅ GP ⋅ 60
Used param: MEBUSTCH[1..4]; MEBUSTCH[1,2] are defined for standard cell
56
Element
object:
Cell
Unit:
second
Remark:
---
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
8.4
Definition of additional BR 9.0 product line KPIs
Combined channel availability rate for CS and PS traffic
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 9 “TCH load
related performance indicators”, section “Combined time slot utilization for CS and PO
traffic”, new subsection 9.2.3.
Long name: (a) Mean overall channel availability rate for CS and PS traffic
Short name: (a) MeaAvChC
Description: This indicator provides the mean overall channel availability rate for CS
and PS traffic.
NAVTCH [ 3,6,9,12 ] +
Formula:
NAVPDCH [ 3 ] +
NAVTCHSD [ 3 ]
MeaAvCHC = ---------------------------------------------------------------------NRDEFTCH [ 3,6,9,12 ] +
NDFTCHSD [ 1 ] +
NDEFPDCH [ 3 ]
Used param: NAVTCH[3,6,9,12], NRDEFTCH[3,6,9,12], NDEFPDCH[3], NAVPDCH[3], NDFTCHSD[1], NAVTCHSD[3]
Element
object:
Cell
Unit:
None
Remark:
•
•
•
•
•
8.5
Due to feature 'Smooth Channel Modification' now all timeslots configured as TCH and or TCH/SD with pooltype 'TCH_Pool' are considered for measurement NRDEFTCH.
Due to feature 'Smooth Channel Modification' now all available
timeslots possible to use as TCH are considered for measurement
NAVTCH (timeslots configured as TCH or TCH/SD with pooltype
TCH_Pool' or TCH/SD with pooltype 'TCH_SD_Pool').
The number of defined TCH/SD with pooltype 'TCH_SD_Pool' is
counted by NDFTCHSD[1].
The measurements NDEFPDCH[3], NAVPDCH[3] provide the mean
number of defined, available reserved PDCHs. Reserved PDCHs are
those channels that can be used for GPRS only: PBCCH, PCCCH,
reserved timeslots (GMANPRESPRM, EMANPRESPRM, GMANPRESCOM, EMANPRESCOM).
Formula is based on mean values and all calculations are based on
TCH basis (not timeslot basis).
Handover unsuccess rate 2G to 2G
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 15 “Handover related performance indicators”, section “General handover performance”, new
subsection 15.1.4.
Long name: (a) Handover unsuccess rate 2G to 2G
Short name: (a) HOUnSuccRate2G2G
DN0933284
Id:0900d80580703c1a
Confidential
57
Definition of additional BR 9.0 product line KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Description: These indicators provide the general handover unsuccess rate as an
aggregation over all handover causes from 2G to 2G systems.
Formula:
HOUnSuccRate2G2G = 1 – HOSuccRate2G2G
Used param: HOSuccRate2G2G
8.6
Element
object:
Cell
Unit:
None
Remark:
---
Handover ratio, directed retries 2G to 2G
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 15 “Handover related performance indicators”, section “General handover performance”, new
subsection 15.1.5.
Long name: (a) Handover ratio, directed retries 2G to 2G
Short name: (a) HORatioDR2G2G
Description: These indicators provide the ratio of the attempted internal and external
handovers with the cause directed retry to the total number of attempted
handovers.
Formula:
ATINHIRC [ 7 ] + ∑ ATINBHDO [ 7 + j ⋅ 10 ]
31
j=0
HORatioDR2G2G = -----------------------------------------------------------------------------------------------------------------ATINHIRC [ all ] + ATINBHDO [ all ]
where j is the j-th neighbor cell
Used param: ATINHIRC[all], ATINBHDO[all]
8.7
Element
object:
Cell
Unit:
None
Remark:
---
Total handover rates
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 15 “Handover related performance indicators”, section “Other handover performance indicators”.
Formula a) to g) see section 15.6.8 “Total handover rates”.
Long name: (h) Total handover drop rate (2G-2G)
Short name: (h) HODropRate2G2G
Description: These indicators provide handover statistics related to (intra cell, inter
cell, inter BSC and inter system) handovers.
58
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Definition of additional BR 9.0 product line KPIs
Formula:
HODropRate2G2G =
UNIHIALC [ 1 ] + UNIHIRLC [ 1 ] +
( ATINBHDO [ all ] – SUINBHDO [ all ] – NRUNINHD [ all ] )
------------------------------------------------------------------------------------------------------------------------------------------------ATINHIAC [ all ] + ATINHIRC [ all ] + ATINBHDO [ all ]
Used param: ATINHIAC[all], SINTHITA[all], UNINHOIA[all], UNINHIALC[all], ATINHIRC[all], SINTHINT[all], UNINHOIE[all], UNIHIRLC[all], ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], ATOISHDO[all],
SUOISHDO[all], UNOISHDO[all]
8.8
Element
object:
Cell
Unit:
None
Remark:
During a running handover procedures the user is able to terminate the
call and the call will be released before completion of the handover procedure.Therefore the number of handover successes can be smaller
than the difference of handover attempts - handover failures - handover
drops. This will lead to a small systematic error for formula (d), (g) and
(h).
RXQUAL distribution
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 16 “Power
and quality measurements”, section “RXQUAL distribution”.
Formula a) to b) see section 16.8 “RXQUAL distribution”
Long name: (c) RXQUAL Cumulative downlink
(d) RXQUAL Cumulative uplink
Short name: (c) RxQuCumDL[n]
(d) RxQuCumUL[n]
Description: The indicators (a) and (b) provide the rate of received samples having the
received bit error rate in quality band equal to 'n' from uplink and downlink
directions, respectively. The indicators (c) and (d) provide the cumulative
rate of received samples having the received bit error rate in quality band
up to 'n' for uplink and downlink directions, respectively.
Formula:
(c)
∑
n
RxQuCumDL[n] =
RsQuDisDL[i]
i=0
(d)
∑ RxQuDisUL[i]
n
RsQuCumUL[n] =
i=0
Used param: CRXLVQUD[1..64], CRXLVQUU[1..64]
DN0933284
Id:0900d80580703c1a
Confidential
59
Definition of additional BR 9.0 product line KPIs
8.9
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Element
object:
TRX
Unit:
None
Remark:
The range of the used measurements (SCANCTRX measurements) can
be configured and is therefore relevant for the analysis of the results.
TCH traffic share
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 16 “Power
and quality measurements”, new section 16.21.
Long name: (a) TCH Traffic share of half rate AMR calls
(b) TCH Traffic share of full rate AMR calls
(c) TCH Traffic share of non AMR calls
Short name: (a) TCHShareHRAMR
(b) TCHShareFRAMR
(c) TCHSharenonAMR
Description: This indicator provides the ratio of the number of samples (related to one
SACCH period) coded by half rate, full rate and non AMR cadets and total
number of samples (non AMR and AMR).
Formula:
(a)
AMRFRMUL [ 9-13,22-26 ]
-------------------------------------------------------------------24
TCHShareHRAMR = 100 ⋅ -------------------------------------------------------------------CRXLVQUU [ all ]
(b)
AMRFRMUL [ 1-8,14-21 ]
----------------------------------------------------------------24
TCHShareFRAMR = 100 ⋅ ----------------------------------------------------------------CRXLVQUU [ all ]
(c)
TCHSharenonAMR =
[ 1 – 26 ]
CFERRXQU [ all ] – AMRFRMUL
------------------------------------------------------24
100 ⋅ ---------------------------------------------------------------------------------------------------------CRXLVQUU [ all ]
Used Purim: AMRFRMUL [all], CRXLVQUU[all]
60
Element
object:
Cell
Unit:
Percent
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Remark:
8.10
Definition of additional BR 9.0 product line KPIs
1. AMRFRMUL [9 - 13, 22 - 26] must be divided by 24 because AMRFRMUL[9-13,22-26] provides how many speech frames were coded
by half rate AMR codecs in uplink direction whereas the intention is
to provide for how many SACCH periods the half rate AMR codecs
were used (one SACCH period is equivalent to 24 speech frames).
2. AMRFRMUL [1 - 8, 14 - 21] must be divided by 24 because
AMRFRMUL [1 - 8, 14 - 21] provides how many speech frames were
coded by FR NB AMR codecs in uplink direction whereas the intention is to provide for how many SACCH periods the FR NB AMR
codecs were used (one SACCH period is equivalent to 24 speech
frames).
User throughput on radio interface per cell
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 18 “GPRS
related performance indicators”, section “Network planning (dimensioning)”.
Formula a) to b) see section 18.2.2 “User throughput on radio interface per cell”.
Long name: (c) User Data Throughput for GPRS per cell on radio interface uplink
(d) User Data Throughput for GPRS per cell on radio interface downlink
(e) User Data Throughput for EGPRS per cell on radio interface uplink
(f) User Data Throughput for EGPRS per cell on radio interface downlink
Short name: (c) UserThrGPRSUmCellUL
(d) UserThrGPRSUmCellDL
(e) UserThrEGPRSUmCellUL
(f) UserThrEGPRSUmCellDL
Description
This indicator provides the mean LLC throughput on the air interface per
cell. Retransmissions are excluded; therefore only the amount of data
transmitted on behalf of the application layer (here LLC) is considered.
The uplink/downlink directions are separated. GPRS and EGPRS are
separated.
The KPI does not indicate the packet throughput experienced by a single
subscriber. Instead the KPI refers to the mean user packet load of a
whole cell according to the following model: The user packet volume
transmitted for a cell is accumulated over the whole granularity period
and afterwards divided by the length of granularity period.
DN0933284
Id:0900d80580703c1a
Confidential
61
Definition of additional BR 9.0 product line KPIs
Formula:
KPI guidelines for BTSplus migration into the Flexi BSC
product family
(c)
8
UserThrGPRSUmCellUL = MUTHRF[1..4] ⋅ ------------1000
(d)
UserThrGPRSUmCellDL =
8
( MUTHRF[14..17] – REMUTHRF[14..17] ) ⋅ ------------1000
(e)
8
UserThrEGPRSUmCellUL = MUTHRF[5..13] ⋅ ------------1000
(f)
UserThrEGPRSUmCellDL =
8
( MUTHRF[18..26] – REMUTHRF[18..26] ) ⋅ ------------1000
Used param: MUTHRF[all], REMUTHRF[14 .. 26]
Element
object:
Cell
Unit:
kbit/sec
Remark:
Downlink throughput
The retransmitted throughput in downlink direction is included in the measurement MUTHRF(DL); therefore REMUTHRF(DL) has to be subtracted
Uplink throughput
•
•
8.11
Retransmissions due to bad radio link quality are not included in measurement MUTHRF(UL).
Systematic error in formula:
The MS may also retransmit a previously transmitted RLC/MAC
block when nothing else has to be transmitted in uplink direction. In
that case the BSC will receive certain RLC/MAC block more than
once. The counter MUTHRF(UL) registers each of these receipts.
Therefore UserThrUmCellUL contains a systematic error. For short
duration TBF (GMM/SM activities) the error is larger than for medium
or long duration TBFs (e.g. TBF for WAP session or ftp).
Percent timeslot resources achieved
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 18 “GPRS
related performance indicators”, section “Network planning (dimensioning)”.
Formula a) to d) see section 18.2.15 “Percent timeslot resources achieved”.
Long name: (e) Percent timeslot resources achieved for EDGE in downlink direction
(f) Percent timeslot resources achieved in uplink direction considering
GPRS and EDGE
62
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Definition of additional BR 9.0 product line KPIs
Short name: (e) PercentEdgeTSLAchievedDL
(f) PercentTSLAchievedDL
Description: This KPI provides the number of assigned timeslots to the number of
optimum CAA timeslots requested. The assigned timeslots are timeslots,
which are assigned by the RRM to a MS for a real TBF. The number of
optimum CAA timeslots requested is the highest prioritized timeslot configuration calculated by the minimum square method of the CAA MS configuration block.
Formula:
(e)
PercentEdgeTSLAchievedDL =
∑ MUTLLC [i+55] ⋅ MUTLLC [i+75]
5
i=1
-------------------------------------------------------------------------------------------------5
∑ MUTLLC [i+75]
i=1
(f)
PercentTSLAchievedDL =
∑ MUTLLC [i+50] ⋅ MUTLLC [i+70]
10
i=1
-------------------------------------------------------------------------------------------------10
∑ MUTLLC [i+70]
i=1
Used param: MUTLLC[41..80]
8.12
Element
object:
Cell
Unit:
%
Remark:
---
User data volume on radio interface per cell
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 18 “GPRS
related performance indicators”, section “Network planning (dimensioning)”, new
subsection 18.2.16.
Long name: (a) User Data Volume per cell on radio interface uplink
(b) User Data Volume per cell on radio interface downlink
(c) User Data Volume for GPRS per cell on radio interface uplink
(d) User Data Volume for GPRS per cell on radio interface downlink
(e) User Data Volume for EGPRS per cell on radio interface uplink
(f) User Data Volume for EGPRS per cell on radio interface downlink
DN0933284
Id:0900d80580703c1a
Confidential
63
Definition of additional BR 9.0 product line KPIs
KPI guidelines for BTSplus migration into the Flexi BSC
product family
Short name: (a) UserVolUmCellUL
(b) UserVolUmCellDL
(c) UserVolGPRSUmCellUL
(d) UserVolGPRSUmCellDL
(e) UserVolEGPRSUmCellUL
(f) UserVolEGPRSUmCellDL
Description: This indicator provides the mean LLC data volume on the air interface per
cell. Retransmissions are excluded; therefore only the amount of data
transmitted on behalf of the application layer (here LLC) is considered.
The uplink/downlink directions are separated. GPRS and EGPRS traffic
are separated. The KPI does not indicate the packet data volume experienced by a single subscriber. Instead the KPI refers to the mean user
packet load of a whole cell according to the following model: The user
packet volume transmitted for a cell is accumulated over the whole granularity period.
Formula:
(a)
UserVolUmCellUL = UserThrUmCellUL ⋅ gran ⋅ 60
(b)
UserVolUmCellDL = UserThrUmCellDL ⋅ gran ⋅ 60
(c)
UserVolGPRSUmCellUL = UserThrGPRSUmCellUL ⋅ gran ⋅ 60
(d)
UserVolGPRSUmCellDL = UserThrGPRSUmCellDL ⋅ gran ⋅ 60
(e)
UserVolEGPRSUmCellUL = UserThrEGPRSUmCellUL ⋅ gran ⋅ 60
(f)
UserVolEGPRSUmCellDL = UserThrEGPRSUmCellDL ⋅ gran ⋅ 60
Used param: UserThrUmCellUL (0 (a)), UserThrUmCellDL (0 (b)), UserThrGPRSUmCellUL (0 (c)), UserThrGPRSUmCellDL (0 (d)) , UserThrEGPRSUmCellUL (0 (e)), UserThrEGPRSUmCellDL (0 (f))
64
Element
object:
Cell
Unit:
kbit
Remark:
---
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
8.13
Definition of additional BR 9.0 product line KPIs
Share of EGPRS requests
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 18 “GPRS
related performance indicators”, section “Network planning (dimensioning)”, new
subsection 18.2.18.
Long name: (a) Share of EGPRS requests
Short name: (a) ShareEgprsRequ
Description: Share of EGPRS TBF establishment request from all TBF establishment
requests.
Formula:
(a)
CHALNHLY[28]
ShareEgprsRequ = ----------------------------------------------------------------------------------------CHALNHLY[27] + CHALNHLY[28]
Used param: CHALNHLY[27, 28]
8.14
Element
object:
Cell
Unit:
None
Remark:
---
Coding scheme distribution on RLC data blocks
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 18 “GPRS
related performance indicators”, section “Network optimization”, new subsection 18.3.5.
Long name: (a) Coding scheme distribution on uplink GPRS RLC data blocks
(b) Coding scheme distribution on downlink GPRS RLC data blocks
(c) Coding scheme distribution on uplink EGPRS RLC data blocks
(d) Coding scheme distribution on downlink EGPRS RLC data blocks
Short name: (a) CSDistrGPRSUL
(b) CSDistrGPRSDL
(c) CSDistrEGPRSUL
(d) CSDistrEGPRSDL
Description: This indicator provides the distribution of the amount of RLC datablocks
for the various coding schemes during the observed granularity period.
The uplink and downlink directions and the GPRS/EGPRS are considered separately.
Use Case:
DN0933284
During the planning phase of a radio network (i.e. before deployment) the
distribution of the user data transmission on coding schemes is predicted
by simulation results. By aid of the present KPIs these simulation results
may be replaced by the experiences of an operating network. This could
help e.g. for the planning of future network expansions (capacity
enhancements or expansion of the coverage area of the network).
Id:0900d80580703c1a
Confidential
65
Definition of additional BR 9.0 product line KPIs
Formula:
KPI guidelines for BTSplus migration into the Flexi BSC
product family
(a)
NTRAPDU[c]
CSDistrGPRSUL[c] = -----------------------------------------NTRAPDU[1..4]
for c = 1..4
(b)
NTRAPDU[c+13]
CSDistrGPRSDL[c] = ------------------------------------------------NTRAPDU[14..17]
for c = 1..4
(c)
NTRAPDU[c]
CSDistrEGPRSUL[c] = --------------------------------------------NTRAPDU[5..13]
for c = 5..13
(d)
NTRAPDU[c+13]
CSDistrEGPRSDL[c] = ------------------------------------------------NTRAPDU[18..26]
for c = 5..13
With parameter c for the observed coding scheme:
c = 1 coding scheme CS1
c = 2 coding scheme CS2
c = 3 coding scheme CS4
c = 4 coding scheme CS5
c = 5 coding scheme MCS1
c = 6 coding scheme MCS2
c = 7 coding scheme MCS3
c = 8 coding scheme MCS4
c = 9 coding scheme MCS5
c = 10 coding scheme MCS6
c = 11 coding scheme MCS7
c = 12 coding scheme MCS8
c = 13 coding scheme MCS9
Used param: NTRAPDU[all]
66
Element
object:
Cell
Unit:
None
Remark:
In downlink directions the retransmission is included in
NTRAPDU[14..26] but in uplink direction the retransmission is excluded
from NTRAPDU[1..13]. For simplicity it is assumed that the CS time distribution is mainly independent from the inclusion or exclusion of retransmissions.
Id:0900d80580703c1a
Confidential
DN0933284
KPI guidelines for BTSplus migration into the Flexi BSC
product family
8.15
Definition of additional BR 9.0 product line KPIs
Frame relay link utilization
Part of BR 9.0 product line “PM: SBS Key Performance Indicators”, chapter 19 “Miscellaneous performance indicators”.
Formula a) see section 19.8 “Frame relay link utilization”.
Long name: (b) Frame relay utilization uplink
(c) Frame relay utilization downlink
Short name: (b) FRLUtilUL
(c) FRLUtilDL
Description: This indicator provides the frame relay link utilization on the Gb interface
by meaning of the carried frame relay data per NSVC.
Formula:
(b)
MFRLDATA[1]
FRLUtilUL = --------------------------------------------Capacity FRL UL
(c)
MFRLDATA[2]
FRLUtilDL = -------------------------------------------Capacity FRL DL
Used param: Capacity FRL: The FRL is an n X 64 kbit/sec physical channel, created
over a PCM line, represented by PCMG/PCMA objects.
MFRLDATA [all]
DN0933284
Element
object:
NSVC
Unit:
kbit/sec
Remark:
---
Id:0900d80580703c1a
Confidential
67