GSM KPI and Measurements

RN20223EN14GLN0
KPI and Measurements

1
1 Nokia Siemens Networks RN20223EN14GLN0
RN2022-14N
RANOP Radio Network Optimization Principles
RN20223EN14GLN0
2
Objectives
At the end of the this chapter participants will be able to
understand what are DX causes
understand how network data is collected to tables
work with OSS tables
which KPIs to use for optimizing
know the basic benchmarking KPIs
RN20223EN14GLN0
3
Contents of RANOP
Introduction
What is network optimization
What should be taken into account when starting Network
Optimization?
Assessment
Situation at the moment
KPIs and Measurements KPIs and Measurements
Measurement tables + KPIs Measurement tables + KPIs
Solution findings (optimization) and verification
Maximum gain in limited time
Bottlenecks
Features to be considered
NSN recommended features to be used in optimization
RN20223EN14GLN0
4
KPI and Measurement table of contents
PM Theory
DX Causes
GSM causes and DX causes
Drop Call Breakdown Observation
BSS Tables Counters & KPIs
Performance measurement
Measurement tables
NED
Benchmarking KPIs
Introduction
Different KPIs
S14 CS & PS Benchmarking KPIs
RN20223EN14GLN0
5
PM Theory
DX Causes
RN20223EN14GLN0
6
PM Theory
DX Causes
Performance
Reports
BSS
Measurements
Observations
KPI's
Counters
DXCauses
RN20223EN14GLN0
7
MSC BSC
BTS
NetAct
DX CAUSE
DX CAUSE
GSM CAUSE
Successful
Unsuccessful = CLEAR CODES
COUNTERS 1
N
1
N
N
1
PM Theory
GSM causes & DX Causes
RN20223EN14GLN0
8
Program
block
A
Program
block
B
Service Block controlling the Program Blocks A, B, .
DX Cause In (Phase, Channel, Cause In)
DX Cause Out (Phase, Channel, Cause Out)
DX Cause In (Phase, Channel, Cause In)
DX Cause Out (Phase, Channel, Cause Out)
In Observation Report
PM Theory
DX Causes Where are DX causes used?
RN20223EN14GLN0
9
Drop Call Breakdown observation collects statistics on the dropped calls.
After ASSIGNMENT_COMPLETE until channel will be released
The focus of the observation can be either the breakdown of counter DROP AFTER TCH
ASSIGN or the breakdown of counter CLEAR REQUEST SENT BY BSC ON TCH.
MS BTS BSC MSC
SABM (FACCH)
Establish_Indication
UA (FACCH)
Assignment_Complete (FACCH)
Assignment_Complete
Assignment_Complete
Rf_Channel_Release
Rf_Channel_Release_Ack
Alert
SDCCH signalling: MS moves on TCH, SDCCH released
MS on TCH
Connect Connect
Connect_Ack
Connect_Ack
Conversation
Alert
TCH DROPS AFTER
ASSIGNMENT
COMPLETE until
channel release
Channel release
RN20223EN14GLN0
10
Drop Call Breakdown Observation Report is included:
Network Element information, BSC, BTS, TRX IDs
Time information
KPI data
Drop causes included call phase
Timing Advance information
RX level + Quality information (UL and DL)
Adjacent information
Last used bitrate information
RN20223EN14GLN0
11
B
T
S
_
I
D
R
E
L
E
A
S
E
_
T
I
M
E
P
H
A
S
E
_
O
U
T
C
A
U
S
E
_
O
U
T
T
R
X
_
I
D
P
H
A
S
E
_
I
N
C
A
U
S
E
_
I
N
T
I
M
I
N
G
_
A
D
V
A
N
C
E
D
L
_
R
X
_
L
E
V
E
L
U
L
_
R
X
_
L
E
V
E
L
D
L
_
R
X
_
Q
U
A
L
I
T
Y
U
L
_
R
X
_
Q
U
A
L
I
T
Y
D
L
_
L
A
S
T
_
U
S
E
D
_
B
I
T
R
A
T
E
U
L
_
L
A
S
T
_
U
S
E
D
_
B
I
T
R
A
T
E
S
U
D
D
E
N
_
D
R
O
P
A
D
J
_
C
E
L
L
_
L
A
C
_
1
A
D
J
_
C
E
L
L
_
I
D
_
1
R
X
_
L
E
V
E
L
_
A
D
J
_
1
A
D
J
_
C
E
L
L
_
L
A
C
_
2
A
D
J
_
C
E
L
L
_
I
D
_
2
R
X
_
L
E
V
E
L
_
A
D
J
_
2
A
D
J
_
C
E
L
L
_
L
A
C
_
3
A
D
J
_
C
E
L
L
_
I
D
_
3
R
X
_
L
E
V
E
L
_
A
D
J
_
3
A
D
J
_
C
E
L
L
_
L
A
C
_
4
A
D
J
_
C
E
L
L
_
I
D
_
4
R
X
_
L
E
V
E
L
_
A
D
J
_
4
44 2.00809E+15 15 317 4 3 43 0 36 0 0 7 5 5 1 10099 63113 34 10099 63111 14 10099 61203 13 10099 64121 8
10 2.00809E+15 2 317 1 3 42 12 20 0 2 7 15 9 1 10099 61513 21 10099 63192 10 65535 65535 20 65535 65535 20
34 2.00809E+15 2 317 3 3 42 13 37 4 2 7 5 5 0 10099 64372 16 10099 63254 12 10099 64373 6 65535 65535 25
65 2.00809E+15 15 317 4 3 42 4 37 0 0 7 5 5 1 10099 63486 33 10099 60266 25 10099 61523 22 65535 65535 22
24 2.00809E+15 2 317 7 3 42 11 5 0 4 7 15 15 1 10071 61502 7 10099 63191 6 65535 65535 20 65535 65535 24
10 2.00809E+15 2 317 1 3 42 0 15 0 4 7 5 5 1 10099 61513 27 10066 60087 9 10099 63081 9 10099 63192 8
19 2.00809E+15 2 317 8 3 43 12 20 0 0 7 9 5 0 65535 65535 27 65535 65535 20 65535 65535 20 65535 65535 25
19 2.00809E+15 2 317 7 3 43 13 37 0 0 7 5 5 0 10099 60226 21 10099 63083 20 10099 60268 17 10099 64373 14
44 2.00809E+15 15 317 5 3 42 1 20 0 0 7 5 5 1 10099 61203 12 10099 61412 8 10099 63111 7 65535 65535 24
125 2.00809E+15 15 317 6 12 89 13 20 0 0 7 9 9 1 65535 65535 25 65535 65535 20 65535 65535 20 65535 65535 30
Drop Call Breakdown Observation - Example
Phase out:
BSC internal phase value of the call release (the phase of the call where the drop occurred). See Call
Related DX Causes in BSC.
Phase out
15 = Conversation,
2 = MM signaling
Cause out
BSC internal cause value of the call release (the drop cause). See Call Related DX Causes in BSC.
Cause out 317 = conn_fail_rad_link_fail_c
The Abis interface receives a CONNECTION FAILURE message and its cause is radio link
failure.
RN20223EN14GLN0
12
Exercise
How this observation data can be used for network
optimization?
B
T
S
_
I
D
R
E
L
E
A
S
E
_
T
I
M
E
P
H
A
S
E
_
O
U
T
C
A
U
S
E
_
O
U
T
T
R
X
_
I
D
P
H
A
S
E
_
I
N
C
A
U
S
E
_
I
N
T
I
M
I
N
G
_
A
D
V
A
N
C
E
D
L
_
R
X
_
L
E
V
E
L
U
L
_
R
X
_
L
E
V
E
L
D
L
_
R
X
_
Q
U
A
L
I
T
Y
U
L
_
R
X
_
Q
U
A
L
I
T
Y
D
L
_
L
A
S
T
_
U
S
E
D
_
B
I
T
R
A
T
E
U
L
_
L
A
S
T
_
U
S
E
D
_
B
I
T
R
A
T
E
S
U
D
D
E
N
_
D
R
O
P
A
D
J
_
C
E
L
L
_
L
A
C
_
1
A
D
J
_
C
E
L
L
_
I
D
_
1
R
X
_
L
E
V
E
L
_
A
D
J
_
1
A
D
J
_
C
E
L
L
_
L
A
C
_
2
A
D
J
_
C
E
L
L
_
I
D
_
2
R
X
_
L
E
V
E
L
_
A
D
J
_
2
A
D
J
_
C
E
L
L
_
L
A
C
_
3
A
D
J
_
C
E
L
L
_
I
D
_
3
R
X
_
L
E
V
E
L
_
A
D
J
_
3
A
D
J
_
C
E
L
L
_
L
A
C
_
4
A
D
J
_
C
E
L
L
_
I
D
_
4
R
X
_
L
E
V
E
L
_
A
D
J
_
4
44 2.00809E+15 15 317 4 3 43 0 36 0 0 7 5 5 1 10099 63113 34 10099 63111 14 10099 61203 13 10099 64121 8
10 2.00809E+15 2 317 1 3 42 12 20 0 2 7 15 9 1 10099 61513 21 10099 63192 10 65535 65535 20 65535 65535 20
34 2.00809E+15 2 317 3 3 42 13 37 4 2 7 5 5 0 10099 64372 16 10099 63254 12 10099 64373 6 65535 65535 25
65 2.00809E+15 15 317 4 3 42 4 37 0 0 7 5 5 1 10099 63486 33 10099 60266 25 10099 61523 22 65535 65535 22
24 2.00809E+15 2 317 7 3 42 11 5 0 4 7 15 15 1 10071 61502 7 10099 63191 6 65535 65535 20 65535 65535 24
10 2.00809E+15 2 317 1 3 42 0 15 0 4 7 5 5 1 10099 61513 27 10066 60087 9 10099 63081 9 10099 63192 8
19 2.00809E+15 2 317 8 3 43 12 20 0 0 7 9 5 0 65535 65535 27 65535 65535 20 65535 65535 20 65535 65535 25
19 2.00809E+15 2 317 7 3 43 13 37 0 0 7 5 5 0 10099 60226 21 10099 63083 20 10099 60268 17 10099 64373 14
44 2.00809E+15 15 317 5 3 42 1 20 0 0 7 5 5 1 10099 61203 12 10099 61412 8 10099 63111 7 65535 65535 24
125 2.00809E+15 15 317 6 12 89 13 20 0 0 7 9 9 1 65535 65535 25 65535 65535 20 65535 65535 20 65535 65535 30
RN20223EN14GLN0
13
Program
block
A
DX Cause In (Phase, Channel, Cause In) DX Cause Out (Phase, Channel, Cause Out)
Cause In <> Cause Out ?
NO Successful Event
YES Unsuccessful Event (CLEAR CODE)
PM Theory
DX Causes How to detect faults?
RN20223EN14GLN0
14
Program block in BSC (e.g. ABIPRB)
Different checking e.g.
Acknowledgement
correct ?
rej_phantom_res
Ghost
CCCH Res
Establishment cause
valid ?
SDCCH
act. fail
ch_act_nack
Phase ended
successfully ?
cause code in = cause code out
DX cause code out counter
Channel
request
Channel
activation
Channel activation
ackn.
PM Theory
DX Causes Counter triggering
RN20223EN14GLN0
15
1003 1004 1005 1013
315 - conn_fail
1-8
PHASE
CAUSE VALUE
NMS2000 Counter
TCH SDCCH
CHANNEL TYPE
1014 1015
9-11 12-14 15
Note!! that there are no counters that are incremented by the same DX
Cause, so if you have the channel, phase and cause value you are able to know
which is the counter incremented!
DX Cause
PM Theory
DX Causes Counter pegging example
RN20223EN14GLN0
16
PM Theory
BSS Tables Counters & KPIs
RN20223EN14GLN0
17
PM Theory
BSS Counters: Performance Measurements
Performance measurements and observations are divided
into the following groups according to their function:
Call control measurements (CSW)
GPRS measurements (PSW)
Transmission measurements
Observations
Measurements &
Observations
Measurement
Tables
Performance Measurements Hierarchy
Counters
Aggregation
Level
PI
KPI
Report
RN20223EN14GLN0
18
PM Theory
Nokia BSS Counters - Numbering
Counter = XXXYYY where
XXX = measurement table
YYY = counter number in measurement table
Example: counter 001001 or c1001
XXX = 001 = c1 = traffic measurement
YYY = 001 = SEIZURE ATTEMPTS WITH BUSY SDCCH
Description in NED
RN20223EN14GLN0
19
PM Theory
BSS Counters: Measurement tables
Traffic Measurement Link Balance per MS Classmark Measurement Reversed Hunting Measurement
Resource Availability Measurement Timing Advance Statistics Measurement Non-BCCH Layer Offset Measurement
Resource Access Measurement Resource Availability per BSC Measurement UTRAN Handover Adjacent Cell Measurement
Handover Measurement BSC Level Clear Code (SERLEV) Measurement UTRAN Neighbouring Cell Signal Level Measurement
Power Control Measurement MS Speed Detection Measurement Total FEP Measurement
Load Measurement Dual Band Measurement DFCA Measurement
Availability Measurement C/I Ratio Measurement DFCA Assignment Measurement
OSI/X.25 Measurement Hot Spot Measurement BSC-BSC Measurement
Undefined Adjacent Cell Measurement High Speed Data Measurement WPS Measurement
RX Quality Statistics Measurement Channel Finder Measurement IMSI-Based Handover Measurement
Handover Adjacent Cell Measurement MS Capability Indication Measurement CS DTM Measurement
BSC Level Clear Code Measurement Defined Adjacent Cell Measurement AMR RX Quality Measurement
BSC Level Clear Code (PM) Measurement FER Measurement DFCA SAIC Measurement
Underlay-Overlay Statistics Measurement Position Based Services Measurement Soft Channel Capacity Measurement
RX Level Statistics Measurement
Call Control measurements
Measurements & Observations
Measurement Tables
Measurement Counters
(Aggregation level)
Measurement tables of the Call Control measurements can be seen below
RN20223EN14GLN0
20
PM Theory
GPRS measuremenst Transmission measurements
Packet Control Unit Measurement DMR Measurement
RLC Blocks per TRX Measurement DN2 Measurement
Frame Relay Measurement TRU/BIE Measurement
Dynamic Abis Measurement ET BSC Measurement
Coding Scheme Measurement ET TCSM Measurement
Quality of Service Measurement TRE Measurement
PBCCH Availability Measurement Selective TRE Measurement
GPRS Cell Re-selection Measurement
GPRS RX Level and Quality Measurement
Enhanced Quality of Service Measurement
Gb Over IP Measurement
PS DTM Measurement
Observations
SDCCH Observation
TCH Observation
Handover Observation
Radio Measurement Report
Clear Code Observation
Dropped Call Observation
TBF Observation for GPRS Trace
GPRS Cell Re-selection Report
GPRS RX Level and Quality Report
Position Based Services Observation
Measurement tables of the
Observations
GPRS Measurements
Can be seen here
RN20223EN14GLN0
21
PM Theory
Performance measurements (S12)
Call control measurements (CSW)
GPRS measurements (PSW)
Observations
Can be found here, see attached file
S12 Performance
Measurements
RN20223EN14GLN0
22
PM Theory
How to activate tables?
These can be activated at BSC level or can be activated at NetAct level.
If they are part of optional feature, the feature needs to be present on the PRFILE of
each BSC. The parameter related to the feature needs to be activated.
Start date and End date needs to be defined.
Start time and End time of each day of the week needs to be defined
Period needs to be defined
Set parameter in PR_FILE (WOC):
ZWOC:10,65,FF;
Set measurement (TPM):
ZTPM:<measurement group>,<measurement type>:<measurement
day>, <measurement interval>,<output interval>:;
ZTPM:MEASUR,CHAN_FIN:ALL,00240,60:DB1=0,DB2=8;
Start measurement (TPS):
ZTPS:MEASUR,CHAN_FIN;
Note! Can be activated also in OSS, since 3.1
RN20223EN14GLN0
23
PM Theory
Connect to NetAct
Reporting
Reporting Suite Scheduler
Manage Scheduled Jobs
List Scheduled Jobs
Edit Scheduled Jobs
Job Data Map Details
Scheduling A Job Request
User Interface Guide can be used for more
detailed information
(admin rights needed)
How to activate tables in NetAct?
Scheduler can be used for managing
scheduled jobs
RN20223EN14GLN0
24
PM Theory
Measurement reporting interval to each measurement can be
unique.
15min, 30min, 1hour etc
During optimization these different measurement reporting
intervals should be verified to support need of optimization
activities.
Note! Any changes to measurement interval should be
agreed with OSS administrator to avoid any overload situation
in OSS.
RN20223EN14GLN0
25
PM Theory
How to check that all data is available in OSS
Can be checked running Reporting Suite reports
Some KPIs are using several tables, so if all data is not available,
results might be strange.
If you want to check all data, all tables should be run (troublesome)
Can be checked with SQL (Optional)
Can be seen, that there are some data
Difficult to see if hourly data in some counter is missing
RN20223EN14GLN0
26
PM Theory
KPIs
Measurements &
Observations
Measurement
Tables
Counters
Aggregation
Level
PI
KPI
Report
Performance Indicators (PIs) and Key Performance
Indicators (KPIs) are created based on data in counters.
Tables must be activated and data must be available in OSS
Performance Reports are created based on KPI analysis
RN20223EN14GLN0
27
PM Theory
NED - Introduction
From NED all the tables and counters with description can
be found
Tables can be found from here
Counter data descriptions
can be found from here
Trigger point figures can be
found from here
RN20223EN14GLN0
28
PM Theory
NED trigger point figure
Trigger point for counter
c1001 can be found here
Note!
C1001 is NOT the only counter
which will be updated here.
All these counters will be updated
here.
RN20223EN14GLN0
29
Benchmarking KPIs
RN20223EN14GLN0
30
Benchmarking KPIs - Introduction
Measurements &
Observations
Measurement
Tables
Counters
Aggregation
Level
PI
KPI
Report
In Optimizing project many KPIs can be used
Depends on the purpose
Depends on the customer
KPI
Benchmarking KPIs
Planning &
Optimizing KPIs
Operator
Specific KPIs
Other
KPIs
RN20223EN14GLN0
31
Benchmarking KPIs
Different KPIs
Which KPIs to use for optimizing?
Benchmarking KPIs recommended for reporting
Standard list of KPI that in the world wide experience of all projects
CDR, HO, Quality etc
Optimization KPIs can be used for deeper performance
analysis / monitoring
Almost all KPIs can be used for optimization (SW release specific)
KPIs used depends on the use case (for example drops)
Drops after TCH seized (dcr_3j)
Drops after TCH assigned(dcr_8h)
Drops after TCH conversation started(dcr_5a)
KPIs used depends on the available tool
RN20223EN14GLN0
32
Benchmarking KPIs
S14 CS KPIs
CS KPIs
KPI group Description S13
TCH call blocking, before DR blck_8i
SDCCH access probability, before FCS csf_1
SDCCH real blocking blck_5a
HO failure % due to radio interface blocking hfr_55a
SDCCH drop ratio without timer T3101 expiry % sdr_4
TCH drop call (dropped conversation) % dcr_5a
TCH dropped conversation % re-est. considered-> dcr_5b
Total HO failure % hfr_2a
Ho drop hfr_68a
UL cumulative quality % in class X, ulq_2a, X=5
DL cumulative quality % in class X, dlq_2a, X=5
TCH traffic sum trf_1d
Average SDCCH traffic trf_11b
DTM CS traffic ratio dtm_2
TCH traffic share of non-AMR calls % trf_120a
TCH traffic share of FR AMR calls % trf_121
TCH traffic share of HR AMR calls % trf_122a
Quality
Traffic
Accessibility
Retainability
S14 CS benchmarking KPIs can be seen here
RN20223EN14GLN0
33
Benchmarking KPIs
S14 PS KPIs
PS KPIs
KPI group Description S13
Downlink GPRS RLC payload n/a
Uplink GPRS RLC payload n/a
Uplink RLC Payload trf_243
Downlink EGPRS RLC payload n/a
Uplink EGPRS RLC payload n/a
Downlink RLC Payload trf_244
DTM PS payload ratio dtm_3
PS Erlangs trf_237d
Relative share of PS Erlangs trf_242a
Downlink GPRS Erlangs trf_208c
Uplink GPRS Erlangs trf_205d
Downlink EGPRS Erlangs trf_162f
Uplink EGPRS Erlangs tbf_161i
UL signaling TBFs usage ratio tbf_61
Share of EDGE requests tbf_65
LLC throughput for 4-tsl EDGE MSs llc_3a
LLC throughput for GPRS MSs (for each QoS class) llc_4a
Availability Data service availability ratio ava_68
DL multislot allocation blocking tbf_16a
DL multislot soft blocking blck_33a
Downlink TBFs pr timeslot tbf_38d
Downlink GPRS RLC throughput trf_235b
Uplink GPRS RLC throughput trf_233c
Downlink EGPRS RLC throughput trf_236
Uplink EGPRS RLC throughput trf_234
TBF establishment failure ratio tbf_66
TBF success ratio tbf_67
DL flush pr minute tbf_64
NCCR success ratio n/a
Abis congestion Inadequate EDAP resources in downlink (Note 1) dap_7a
Territory upgrade rejections due to lack of PCU capacity n/a
DL MCS selection limited by PCU dap_9
Gb congestion Downlink Gb load frl_8a
Mobility
PCU congestion
Network Usage
User Experience
PDTCH congestion
PDTCH quality
S14 PS benchmarking KPIs can be seen here
RN20223EN14GLN0
34
Benchmarking KPIs
KPIs
Exercise
What can happen if BSS S14 KPIs are used but BSS
Release is S13?
RN20223EN14GLN0
35
Benchmarking KPIs, CS
TCH Call Blocking,blck_8i
This formula counts the impact of lacking TCH resources on
call setup after the SDCCH phase.
Soft blocking increases the value.
TCH_REQUESTS_CALL_ATTEMPT updating corrected in unsuccessful FACCH
call setup due to lack of resources. Counter will be updated both in successful and
unsuccessful FACCH call setup.
Parts which are not visible to end user are excluded
Directed retry (DR)
A-interface circuit type mismatch caused requests
RN20223EN14GLN0
36
001204 DROP TCH ASSCOMPL TO RFCH REL [S11.5 counter]
Benchmarking KPIs, CS, Dropped call formulas
TCH DROPS AFTER SEIZURE
TCH_RADIO_FAIL /c1013
+TCH_RF_OLD_HO /c1014
+TCH_ABIS_FAIL_CALL /c1084
+TCH_ABIS_FAIL_OLD /c1085
+TCH_A_IF_FAIL_CALL /c1087
+TCH_A_IF_FAIL_OLD /c1088
+TCH_TR_FAIL /c1029
+TCH_TR_FAIL_OLD /c1030
+TCH_LAPD_FAIL /c1046
+TCH_BTS_FAIL /c1047
+TCH_USER_ACT /c1048
+TCH_BCSU_RESET /c1049
+TCH_NETW_ACT /c1050
+TCH_ACT_FAIL_CALL /c1081
-tch_re_est_assign /c57032
---------------------------------
---
CONVERSATION DROPS
dropped_calls /c57007
----------------------------------------------
TCH DROPS AFTER ASSIGNMENT
tch_new_call_assign /c57033
+tch_ho_assign /c57034
-tch_norm_release /c57035
-tch_ho_release /c57036
-----------------------------
TCH ASSIGNMENTS FOR NEW
CALL
tch_new_call_assign
/c57033
CONVERSATION STARTED
conn_ack to BTS
TCH ASSIGNED (alert followed)
Assignment_complete from BTS
TCH SEIZED
BSC allocates a TCH as a response to
TCH request (Channel Activation)
TCH SEIZURES FOR NEW CALL
tch_norm_seiz /c1009
+tch_seiz_due_sdcch_con /c1099
+msc_i_sdcch_tch /c4044
+bsc_i_sdcch_tch /c4057
+cell_sdcch_tch /c4074
-tch_succ_seiz_for_dir_acc /c1165
S11 dcr_8h:
STARTED CONVERSATIONS
conver_started /c57015
- msc_i_tch_tch /c4043
CLEAR COMMAND
from MSC
spare057044 /c57044
-----------------------------
CALL
tch_new_call_assign
/c57033
drop_after_tch_assign /c1202
-----------------------------
CALL
tch_new_call_assign
/c57033
TCH RELEASE
Disconnect from MS (A)
Disconnect. from MSC (B)
S10.5 dcr_8g
S7 dcr_3j
S11 dcr_8h
S7 dcr_8b
RF CHN RELEASE
Rf_channel_release_ack
from BTS
S4 dcr_5a
Benchmarking KPI
More accurate
optimizing KPI
Different reasons
can seen
RN20223EN14GLN0
37
Benchmarking KPIs, PS
Average effective ACK GPRS DL throughput per used TSL ,trf_235b
Indicates the impact of radio link quality on net data rate per
used timeslot considering retransmissions and coding scheme
selection
The lower the value the poorer the radio link quality causing
retransmissions and use of lower coding schemes.
NOTE!
KPI is collecting
counter data from 2
different tables
RN20223EN14GLN0
38
Benchmarking KPIs, PS
TBF Success ratio, tbf_67 (1-TBF drops)
TBF drop vs TCH drop
Connection during TBF drop is not lost
Connection during TCH drop is lost
TBF
Attempts
Establishment
Failures
No
Response
Flush
CSW
Traffic
Suspend
Normally
Ended
TBFs
TBF
Attempts
Establishment
Failures
No
Response
Flush
CSW
Traffic
Suspend
Normally
Ended
TBFs
TBF Failures
RN20223EN14GLN0
39
Benchmarking KPIs
Based on assessment report (including KPIs)
Preliminary optimization solutions will be done
Priorization will be done
Lets optimize
Project
Starts
INPUTS
Assessments Solutions
Priorization Work orders
Solution
Verification
Implementations
Are Criterias
Fulfilled
Project
Ends
Monitoring /
Data collection
Analysis Solutions
More detailed inputs
(if necessary) based
on assessment
Yes
No
Project
report
Performance
Problems

GSM KPI and Measurements

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSM KPI and Measurements

Uploaded by

Copyright:

Available Formats

RN20223EN14GLN0

KPI and Measurements

You might also like