GSM KPI and Measurements PDF

KPI and Measurements
RN2022-14N
RANOP – Radio Network Optimization Principles
1 © Nokia Siemens Networks RN20223EN14GLN0
RN20223EN14GLN0 1
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 2
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
– 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 3
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 4
PM Theory
DX Causes
RN20223EN14GLN0 5
PM Theory
DX Causes
Performance KPI's
Reports
BSS Counters
Measurements
Observations DXCauses
RN20223EN14GLN0 6
PM Theory
GSM causes & DX Causes
Successful
N
DX CAUSE DX CAUSE
1←
Unsuccessful = CLEAR CODES
→
1
GSM CAUSE
MSC BSC BTS
N
1←
COUNTERS
NetAct
RN20223EN14GLN0 7
PM Theory
DX Causes – Where are DX causes used?
In Observation Report
DX Cause In (Phase, Channel, Cause In) DX Cause In (Phase, Channel, Cause In)
DX Cause Out (Phase, Channel, Cause Out) DX Cause Out (Phase, Channel, Cause Out)
Program Program
block block
A B
Service Block controlling the Program Blocks A, B, ….
RN20223EN14GLN0 8
Drop Call Breakdown Observation

• 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
SDCCH signalling: MS moves on TCH, SDCCH released

SABM (FACCH)
Establish_Indication TCH DROPS AFTER
UA (FACCH)
ASSIGNMENT
MS on TCH Assignment_Complete (FACCH) COMPLETE until
Assignment_Complete
channel release
Assignment_Complete
Rf_Channel_Release
Rf_Channel_Release_Ack
Alert Alert
Connect Connect
Connect_Ack
Connect_Ack
Conversation
Channel release
RN20223EN14GLN0 9
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 10
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.
DL_LAST_USED_BITRATE
UL_LAST_USED_BITRATE
TIMING_ADVANCE
RX_LEVEL_ADJ_1
RX_LEVEL_ADJ_2
RX_LEVEL_ADJ_3
RX_LEVEL_ADJ_4
ADJ_CELL_LAC_1
ADJ_CELL_LAC_2
ADJ_CELL_LAC_3
ADJ_CELL_LAC_4
DL_RX_QUALITY
UL_RX_QUALITY
ADJ_CELL_ID_1
ADJ_CELL_ID_2
ADJ_CELL_ID_3
ADJ_CELL_ID_4
SUDDEN_DROP
RELEASE_TIME
DL_RX_LEVEL
UL_RX_LEVEL
PHASE_OUT
CAUSE_OUT
PHASE_IN
CAUSE_IN
TRX_ID
BTS_ID
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 11
Exercise
How this observation data can be used for network
optimization?
DL_LAST_USED_BITRATE
UL_LAST_USED_BITRATE
TIMING_ADVANCE
RX_LEVEL_ADJ_1
RX_LEVEL_ADJ_2
RX_LEVEL_ADJ_3
RX_LEVEL_ADJ_4
ADJ_CELL_LAC_1
ADJ_CELL_LAC_2
ADJ_CELL_LAC_3
ADJ_CELL_LAC_4
DL_RX_QUALITY
UL_RX_QUALITY
ADJ_CELL_ID_1
ADJ_CELL_ID_2
ADJ_CELL_ID_3
ADJ_CELL_ID_4
SUDDEN_DROP
RELEASE_TIME
DL_RX_LEVEL
UL_RX_LEVEL
PHASE_OUT
CAUSE_OUT
PHASE_IN
CAUSE_IN
TRX_ID
BTS_ID
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 12
PM Theory
DX Causes – How to detect faults?
DX Cause In (Phase, Channel, Cause In) DX Cause Out (Phase, Channel, Cause Out)
Program
block
A
NO  Successful Event
Cause In <> Cause Out ?

YES  Unsuccessful Event (CLEAR CODE)
RN20223EN14GLN0 13
PM Theory
DX Causes – Counter triggering
Program block in BSC (e.g. ABIPRB)
Different checking e.g.
Channel Establishment cause Ghost

request valid ? rej_phantom_res
CCCH Res
Channel
activation
Channel activation Acknowledgement

ackn. SDCCH
correct ? ch_act_nack
act. fail
Phase ended
successfully ?
DX cause code out counter
cause code in = cause code out
RN20223EN14GLN0 14
PM Theory
DX Causes – Counter pegging example
NMS2000 Counter 1003 1004 1005 1013 1014 1015
CAUSE VALUE 315 - conn_fail
PHASE 1-8 9-11 12-14 15
CHANNEL TYPE SDCCH TCH

DX Cause
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!
RN20223EN14GLN0 15
PM Theory
BSS Tables – Counters & KPIs
RN20223EN14GLN0 16
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
Performance Measurements Hierarchy Report
Aggregation KPI
Level
PI
Counters
Measurement
Tables
Measurements &
Observations
RN20223EN14GLN0 17
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 18
PM Theory
BSS Counters: Measurement tables
• Measurements & Observations
•Measurement Tables
•Measurement Counters
•(Aggregation level)
Measurement tables of the Call Control measurements can be seen below

Call Control measurements
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
RN20223EN14GLN0 19
PM Theory
Observations
SDCCH Observation
Measurement tables of the TCH Observation
Handover Observation
• Observations Radio Measurement Report
• GPRS Measurements Clear Code Observation
Dropped Call Observation
• Transmission measurements TBF Observation for GPRS Trace
GPRS Cell Re-selection Report
Can be seen here GPRS RX Level and Quality Report
Position Based Services Observation
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
RN20223EN14GLN0 20
PM Theory
Performance measurements (S12)
• Call control measurements (CSW)
• GPRS measurements (PSW)
• Transmission measurements
• Observations
Can be found here, see attached file
S12 Performance
Measurements
RN20223EN14GLN0 21
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,0–0–24–0,60:DB1=0,DB2=8;
Start measurement (TPS):
ZTPS:MEASUR,CHAN_FIN;
Note! Can be activated also in OSS, since 3.1

RN20223EN14GLN0 22
PM Theory
How to activate tables in NetAct?

• Connect to NetAct
• Reporting
• Reporting Suite Scheduler
Scheduler can be used for managing

scheduled jobs
• (admin rights needed)
User Interface Guide can be used for more

detailed information
• Manage Scheduled Jobs
• List Scheduled Jobs
• Edit Scheduled Jobs
• Job Data Map Details
23 © Nokia Siemens Networks RN20223EN14GLN0 • Scheduling A Job Request
RN20223EN14GLN0 23
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 24
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 25
PM Theory
KPIs
Aggregation KPI
Level
PI
Counters
Measurement
Tables
Measurements &
Observations
• 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 26
PM Theory
NED - Introduction
From NED all the tables and counters with description can
be found
Trigger point figures can be

found from here
Counter data descriptions

can be found from here
Tables can be found from here

RN20223EN14GLN0 27
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 28
Benchmarking KPIs
RN20223EN14GLN0 29
Benchmarking KPIs - Introduction
Aggregation KPI
Benchmarking KPIs
Level
PI
Planning &
Counters Optimizing KPIs
Operator
Specific KPIs
Measurement
Tables Other
KPIs
Measurements &
Observations
• In Optimizing project many KPIs can be used

• Depends on the purpose
• Depends on the customer
RN20223EN14GLN0 30
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 31
Benchmarking KPIs
S14 CS KPIs
S14 CS benchmarking KPIs can be seen here

CS KPIs
KPI group Description S13
Accessibility 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
Retainability 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
Quality UL cumulative quality % in class X, ulq_2a, X=5

DL cumulative quality % in class X, dlq_2a, X=5
Traffic 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
RN20223EN14GLN0 32
Benchmarking KPIs
S14 PS KPIs
S14 PS benchmarking KPIs can be seen here
PS KPIs
KPI group Description S13
Network Usage 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
User Experience 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
PDTCH congestion DL multislot allocation blocking tbf_16a
DL multislot soft blocking blck_33a
Downlink TBFs pr timeslot tbf_38d
PDTCH quality 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
Mobility DL flush pr minute tbf_64
NCCR success ratio n/a
Abis congestion Inadequate EDAP resources in downlink (Note 1) dap_7a
PCU congestion Territory upgrade rejections due to lack of PCU capacity n/a
DL MCS selection limited by PCU dap_9
33 Gb congestion
© Nokia Siemens Networks Downlink Gb load
RN20223EN14GLN0 frl_8a
RN20223EN14GLN0 33
Benchmarking KPIs
KPIs
Exercise
What can happen if BSS S14 KPIs are used but BSS
Release is S13?
RN20223EN14GLN0 34
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 35
Benchmarking KPIs, CS, Dropped call formulas

Benchmarking KPI
More accurate CONVERSATION STARTED
conn_ack to BTS
optimizing KPI TCH ASSIGNED (alert followed)
Assignment_complete from BTS
S4 dcr_5a
CONVERSATION DROPS
S11 dcr_8h dropped_calls /c57007
• Different reasons ----------------------------------------------
TCH DROPS AFTER ASSIGNMENT
can seen STARTED CONVERSATIONS
drop_after_tch_assign /c1202 conver_started /c57015
- msc_i_tch_tch /c4043
S7 dcr_3j -tch_re_est_assign /c57032 S11 dcr_8h:
TCH DROPS AFTER SEIZURE
-----------------------------
TCH_RADIO_FAIL /c1013
+TCH_RF_OLD_HO /c1014 TCH ASSIGNMENTS FOR NEW
+TCH_ABIS_FAIL_CALL /c1084 CALL
+TCH_ABIS_FAIL_OLD /c1085 tch_new_call_assign
+TCH_A_IF_FAIL_CALL /c1087 /c57033
+TCH_A_IF_FAIL_OLD /c1088
+TCH_TR_FAIL /c1029 TCH DROPS AFTER ASSIGNMENT
+TCH_TR_FAIL_OLD /c1030 S10.5 dcr_8g
+TCH_LAPD_FAIL /c1046 spare057044 /c57044
+TCH_BTS_FAIL /c1047 -tch_re_est_assign /c57032
+TCH_USER_ACT /c1048 ----------------------------- TCH RELEASE
+TCH_BCSU_RESET /c1049 Disconnect from MS (A)
TCH ASSIGNMENTS FOR NEW
+TCH_NETW_ACT /c1050 Disconnect. from MSC (B)
CALL
+TCH_ACT_FAIL_CALL /c1081
tch_new_call_assign
/c57033
-tch_re_est_assign /c57032
---------------------------------
---
TCH SEIZURES FOR NEW CALL
TCH DROPS AFTER ASSIGNMENT S7 dcr_8b
tch_norm_seiz /c1009
+tch_seiz_due_sdcch_con /c1099
tch_new_call_assign /c57033
+msc_i_sdcch_tch /c4044
+tch_ho_assign /c57034
+bsc_i_sdcch_tch /c4057
-tch_norm_release /c57035
+cell_sdcch_tch /c4074 CLEAR COMMAND
-tch_ho_release /c57036 from MSC
-tch_succ_seiz_for_dir_acc /c1165
-----------------------------
TCH ASSIGNMENTS FOR NEW
CALL
tch_new_call_assign
/c57033
TCH SEIZED
BSC allocates a TCH as a response to
TCH request (Channel Activation) RF CHN RELEASE
‘001204 DROP TCH ASSCOMPL TO RFCH REL’ [S11.5 counter] Rf_channel_release_ack
from BTS
RN20223EN14GLN0 36
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 37
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 Failures
Establishment No CSW
Flush Suspend
Failures Response Traffic
Normally
TBF
Ended
Attempts
38 © Nokia Siemens Networks RN20223EN14GLN0 TBFs
RN20223EN14GLN0 38
Benchmarking KPIs
Based on assessment report (including KPIs)

• Preliminary optimization solutions will be done
• Priorization will be done
Let’s optimize INPUTS
More detailed inputs
(if necessary) based
on assessment
Performance Project Assessments Solutions

Problems Starts
Solution
Implementations Work orders Priorization
Verification
Are Criteria’s
No
Monitoring /
Fulfilled Analysis Solutions
Data collection
Yes Project
report
Project
Ends
RN20223EN14GLN0 39

GSM KPI and Measurements PDF

Uploaded by

Copyright:

Available Formats

You might also like

GSM KPI and Measurements PDF

Uploaded by

Document Information

Original Title

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 PDF

Uploaded by

Copyright:

Available Formats

KPI and Measurements

1 © Nokia Siemens Networks RN20223EN14GLN0

At the end of the this chapter participants will be able to

• understand what are DX causes

2 © Nokia Siemens Networks RN20223EN14GLN0

3 © Nokia Siemens Networks RN20223EN14GLN0

KPI and Measurement– table of contents

– BSS Tables – Counters & KPIs

4 © Nokia Siemens Networks RN20223EN14GLN0

5 © Nokia Siemens Networks RN20223EN14GLN0

6 © Nokia Siemens Networks RN20223EN14GLN0

MSC BSC BTS

Service Block controlling the Program Blocks A, B, ….

8 © Nokia Siemens Networks RN20223EN14GLN0

Drop Call Breakdown Observation

MS BTS BSC MSC

SDCCH signalling: MS moves on TCH, SDCCH released

Drop Call Breakdown Observation

Drop Call Breakdown Observation Report is included:

• Network Element information, BSC, BTS, TRX IDs

10 © Nokia Siemens Networks RN20223EN14GLN0

Drop Call Breakdown Observation - Example

Drop Call Breakdown Observation

12 © Nokia Siemens Networks RN20223EN14GLN0

Cause In <> Cause Out ?

13 © Nokia Siemens Networks RN20223EN14GLN0

Channel Establishment cause Ghost

Channel activation Acknowledgement

DX cause code out counter

cause code in = cause code out

14 © Nokia Siemens Networks RN20223EN14GLN0

CAUSE VALUE 315 - conn_fail

PHASE 1-8 9-11 12-14 15

CHANNEL TYPE SDCCH TCH

15 © Nokia Siemens Networks RN20223EN14GLN0

16 © Nokia Siemens Networks RN20223EN14GLN0

Performance Measurements Hierarchy Report

Example: counter 001001 or c1001

18 © Nokia Siemens Networks RN20223EN14GLN0

Measurement tables of the Call Control measurements can be seen below

19 © Nokia Siemens Networks RN20223EN14GLN0

GPRS measuremenst Transmission measurements

Can be found here, see attached file

21 © Nokia Siemens Networks RN20223EN14GLN0

Set parameter in PR_FILE (WOC):

Note! Can be activated also in OSS, since 3.1

How to activate tables in NetAct?

Scheduler can be used for managing

User Interface Guide can be used for more

24 © Nokia Siemens Networks RN20223EN14GLN0

25 © Nokia Siemens Networks RN20223EN14GLN0

• Performance Indicators (PIs) and Key Performance

Trigger point figures can be

Counter data descriptions

Tables can be found from here

Trigger point for counter

28 © Nokia Siemens Networks RN20223EN14GLN0

29 © Nokia Siemens Networks RN20223EN14GLN0