GSM KPI and Measurements

8/12/2019 GSM KPI and Measurements

1/39RN20223EN14GLN0

KPI and Measurements

1

1 Nokia Siemens Networks RN20223EN14GLN0

RN2022-14NRANOP Radio Network Optimization Principles



2/39RN20223EN14GLN0


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


3/39RN20223EN14GLN0


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 MeasurementsKPIs and Measurements Measurement tables + KPIsMeasurement 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


4/39RN20223EN14GLN0


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


5/39RN20223EN14GLN0


5


PM TheoryDX Causes


6/39RN20223EN14GLN0


6


PM TheoryDX Causes

Performance

Reports

BSS

Measurements

Observations

KPI's

Counters

DXCauses


7/39RN20223EN14GLN0


7


MSC BSC BTS

NetAct

DX CAUSE DX CAUSE

GSM CAUSE

Successful

Unsuccessful = CLEAR CODES

COUNTERS 1N

1N

N1

PM TheoryGSM causes & DX Causes


8/39RN20223EN14GLN0


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 TheoryDX Causes Where are DX causes used?


9/39RN20223EN14GLN0


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 TCHASSIGN 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_CompleteRf_Channel_Release

Rf_Channel_Release_Ack

Alert

SDCCH signalling: MS moves on TCH, SDCCH released

MS on TCH

ConnectConnectConnect_Ack

Connect_Ack

Conversation

Alert

TCH DROPS AFTER

ASSIGNMENT

COMPLETE until

channel release

Channel release


10/39RN20223EN14GLN0


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


11/39RN20223EN14GLN0


11


BTS_

ID

RELEASE_

TIME

PHASE_

OUT

CAUSE_

OUT

TRX_

ID

PHASE_

IN

CAUSE_

IN

TIMING_

ADVANCE

DL_

RX_

LEVEL

UL_

RX_

LEVEL

DL_

RX_

QUALITY

UL_

RX_

QUALITY

DL_

LAST_

USED_

BITRATE

UL_

LAST_

USED_

BITRATE

SUDDEN_

DROP

ADJ_

CELL_

LAC_

1

ADJ_

CELL_

ID_

1

RX_

LEVEL_

ADJ_

1

ADJ_

CELL_

LAC_

2

ADJ_

CELL_

ID_

2

RX_

LEVEL_

ADJ_

2

ADJ_

CELL_

LAC_

3

ADJ_

CELL_

ID_

3

RX_

LEVEL_

ADJ_

3

ADJ_

CELL_

LAC_

4

ADJ_

CELL_

ID_

4

RX_

LEVEL_

ADJ_

4

4 4 2 .0 08 09 E+1 5 1 5 31 7 4 3 43 0 36 0 0 7 5 5 1 1 00 99 6 31 13 3 4 10 09 9 63 11 1 1 4 10 09 9 61 20 3 1 3 10 09 9 64 12 1 8

1 0 2 .0 08 09 E+ 15 2 3 17 1 3 4 2 1 2 20 0 2 7 1 5 9 1 1 00 99 6 15 13 2 1 1 00 99 6 31 92 1 0 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 0

3 4 2 .0 08 09 E+1 5 2 3 17 3 3 42 13 37 4 2 7 5 5 0 1 00 99 6 43 72 1 6 10 09 9 63 25 4 1 2 10 09 9 64 37 3 6 6 55 35 6 55 35 2 5

6 5 2 .0 08 09 E+1 5 15 3 17 4 3 4 2 4 3 7 0 0 7 5 5 1 1 00 99 6 34 86 3 3 10 09 9 60 26 6 2 5 10 09 9 61 52 3 2 2 65 53 5 65 53 5 2 2

2 4 2 .0 08 09 E+1 5 2 3 17 7 3 42 11 5 0 4 7 15 15 1 1 00 71 6 15 02 7 1 00 99 6 31 91 6 6 55 35 6 55 35 2 0 65 53 5 65 53 5 2 4

1 0 2 .0 08 09 E+1 5 2 31 7 1 3 42 0 15 0 4 7 5 5 1 10 09 9 6 15 13 2 7 1 00 66 60 08 7 9 10 09 9 6 30 81 9 10 09 9 6 31 92 8

1 9 2 .0 08 09 E+1 5 2 3 17 8 3 4 3 12 2 0 0 0 7 9 5 0 6 55 35 6 55 35 2 7 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 5

1 9 2 .0 08 09 E+1 5 2 3 17 7 3 4 3 13 3 7 0 0 7 5 5 0 1 00 99 6 02 26 2 1 10 09 9 63 08 3 2 0 10 09 9 60 26 8 1 7 10 09 9 64 37 3 1 4

4 4 2 .0 08 09 E+1 5 1 5 3 17 5 3 42 1 20 0 0 7 5 5 1 1 00 99 6 12 03 1 2 10 09 9 61 41 2 8 1 00 99 6 31 11 7 6 55 35 6 55 35 2 4

1 25 2 .0 08 09 E+ 15 1 5 31 7 6 1 2 89 1 3 20 0 0 7 9 9 1 6 5 53 5 6 55 35 2 5 6 55 35 6 5 53 5 2 0 6 55 35 6 5 53 5 2 0 6 55 35 6 5 53 5 3 0

Drop Call Breakdown Observation - Example

Phase out:

BSC internal phase value of the call release (the phase of the call where the drop occurred). SeeCallRelated 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 linkfailure.


12/39RN20223EN14GLN0


12



ExerciseHow this observation data can be used for networkoptimization?

BTS_

ID

RELEASE_

TIME

PHASE_

OUT

CAUSE_

OUT

TRX_

ID

PHASE_

IN

CAUSE_

IN

TIMING_

ADVANCE

DL_

RX_

LEVEL

UL_

RX_

LEVEL

DL_

RX_

QUALITY

UL_

RX_

QUALITY

DL_

LAST_

USED_

BITRATE

UL_

LAST_

USED_

BITRATE

SUDDEN_

DROP

ADJ_

CELL_

LAC_

1

ADJ_

CELL_

ID_

1

RX_

LEVEL_

ADJ_

1

ADJ_

CELL_

LAC_

2

ADJ_

CELL_

ID_

2

RX_

LEVEL_

ADJ_

2

ADJ_

CELL_

LAC_

3

ADJ_

CELL_

ID_

3

RX_

LEVEL_

ADJ_

3

ADJ_

CELL_

LAC_

4

ADJ_

CELL_

ID_

4

RX_

LEVEL_

ADJ_

4

4 4 2 .0 08 09 E+ 15 15 3 17 4 3 43 0 36 0 0 7 5 5 1 1 00 99 6 31 13 3 4 10 09 9 63 11 1 1 4 10 09 9 61 20 3 1 3 10 09 9 64 12 1 8

1 0 2 .0 08 09 E+ 15 2 3 17 1 3 4 2 12 2 0 0 2 7 1 5 9 1 1 00 99 6 15 13 2 1 10 09 9 63 19 2 1 0 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 0

3 4 2 .0 08 09 E+ 15 2 3 17 3 3 42 1 3 3 7 4 2 7 5 5 0 1 00 99 6 43 72 1 6 10 09 9 63 25 4 1 2 10 09 9 64 37 3 6 6 55 35 6 55 35 2 5

6 5 2 .0 08 09 E+ 15 1 5 31 7 4 3 4 2 4 3 7 0 0 7 5 5 1 1 00 99 6 34 86 3 3 10 09 9 60 26 6 2 5 10 09 9 61 52 3 2 2 65 53 5 65 53 5 2 2

2 4 2 .0 08 09 E+ 15 2 3 17 7 3 42 1 1 5 0 4 7 1 5 1 5 1 1 00 71 6 15 02 7 1 00 99 6 31 91 6 6 55 35 6 55 35 2 0 65 53 5 65 53 5 2 4

1 0 2 .00 80 9E +1 5 2 317 1 3 42 0 15 0 4 7 5 5 1 1 00 99 6 15 13 27 1 00 66 6 00 87 9 1 00 99 6 308 1 9 1 009 9 63 19 2 8

1 9 2 .0 08 09 E+ 15 2 3 17 8 3 4 3 12 2 0 0 0 7 9 5 0 6 55 35 6 55 35 2 7 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 0 65 53 5 65 53 5 2 5

1 9 2 .0 08 09 E+ 15 2 3 17 7 3 4 3 13 3 7 0 0 7 5 5 0 1 00 99 6 02 26 2 1 10 09 9 63 08 3 2 0 10 09 9 60 26 8 1 7 10 09 9 64 37 3 1 4

4 4 2 .0 08 09 E+ 15 15 3 17 5 3 42 1 20 0 0 7 5 5 1 1 00 99 6 12 03 1 2 10 09 9 61 41 2 8 1 00 99 6 31 11 7 6 55 35 6 55 35 2 4

1 25 2 .0 08 09 E+ 15 1 5 31 7 6 1 2 89 1 3 20 0 0 7 9 9 1 6 5 53 5 65 53 5 2 5 65 53 5 6 55 35 2 0 65 53 5 6 55 35 2 0 6 55 35 6 5 53 5 3 0


13/39RN20223EN14GLN0


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 TheoryDX Causes How to detect faults?


14/39RN20223EN14GLN0


14


Program block in BSC (e.g. ABIPRB)

Different checking e.g.

Acknowledgement

correct ?

rej_phantom_resGhost

CCCH Res

Establishment causevalid ?

SDCCH

act. failch_act_nack

Phase endedsuccessfully ?

cause code in = cause code out

DX cause code out counter

Channelrequest

Channelactivation

Channel activation

ackn.

PM TheoryDX Causes Counter triggering


15/39RN20223EN14GLN0


15


1003 1004 1005 1013

315 - conn_fail

1-8PHASE

CAUSE VALUE

NMS2000 Counter

TCHSDCCHCHANNEL TYPE

1014 1015

9-11 12-14 15

Note!! that there are no counters that are incremented by the same DXCause, so if you have the channel, phase and cause value you are able to knowwhich is the counter incremented!

DX Cause

PM TheoryDX Causes Counter pegging example


16/39RN20223EN14GLN0


16


PM TheoryBSS Tables Counters & KPIs


17/39RN20223EN14GLN0


17


PM TheoryBSS 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

LevelPI

KPI

Report


18/39RN20223EN14GLN0


18


PM TheoryNokia BSS Counters - Numbering

Counter = XXXYYY where

XXX = measurement tableYYY = 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


19/39RN20223EN14GLN0


19


PM TheoryBSS Counters: Measurement tables

Traffic Measurement Link Balance per MS Classmark Measurement Reversed Hunting Measurement

Re sour ce Ava ilab il ity Mea sur ement T iming Advance Stat ist ics Me as ure me nt Non-BCCH La ye r Offset Mea sur ement

Re sour ce Ac ces s Mea sure me nt Re sourc e Ava ilab il ity pe r BSC Mea sur ement UTRAN Ha ndover Adjac en t Cel l Me as ur ement

Handover Measurement BSC Level Clear Code (SERLEV) Measurement UTRAN Nei ghbouri ng 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 MeasurementHandover Adjacent Cel l Measurem ent MS Capabil ity Indi cation 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

Under lay-Over lay 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


20/39RN20223EN14GLN0


20



GPRS measuremenst Transmission measurementsPacket 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 MeasurementPBCCH 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

ObservationsSDCCH 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


21/39RN20223EN14GLN0


21



Performance measurements (S12)

Call control measurements (CSW) GPRS measurements (PSW)


Observations

Can be found here, see attached file

S12 Performance

Measurements


22/39RN20223EN14GLN0


22



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 ofeach 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:,:, ,:;

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


23/39RN20223EN14GLN0


23



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 managingscheduled jobs


24/39RN20223EN14GLN0


24



Measurement reporting interval to each measurement can be

unique. 15min, 30min, 1hour etc

During optimization these different measurement reportingintervals should be verified to support need of optimizationactivities.

Note!Any changes to measurement interval should beagreed with OSS administrator to avoid any overload situationin OSS.


25/39RN20223EN14GLN0


25



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


26/39RN20223EN14GLN0


26


PM TheoryKPIs

Measurements &

Observations

Measurement

Tables


Counters

Aggregation

LevelPI

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


27/39RN20223EN14GLN0


27


PM TheoryNED - 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 befound from here


28/39RN20223EN14GLN0


28


PM TheoryNED trigger point figure

Trigger point for counterc1001 can be found here

Note!C1001 is NOT the only counterwhich will be updated here.

All these counters will be updatedhere.


29/39RN20223EN14GLN0


29


Benchmarking KPIs


30/39RN20223EN14GLN0


30


Benchmarking KPIs - Introduction

Measurements &

Observations

Measurement

Tables


Counters

Aggregation

LevelPI

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


31/39RN20223EN14GLN0


31


Benchmarking KPIsDifferent 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 performanceanalysis / 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


32/39RN20223EN14GLN0


32


Benchmarking KPIsS14 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-es t. cons idered-> 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_11bDTM 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


33/39RN20223EN14GLN0


33


Benchmarking KPIsS14 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) l lc_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


34/39RN20223EN14GLN0


34


Benchmarking KPIsKPIs

Exercise

What can happen if BSS S14 KPIs are used but BSSRelease is S13?


35/39RN20223EN14GLN0


35


Benchmarking KPIs, CSTCH 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 andunsuccessful FACCH call setup.

Parts which are not visible to end user are excluded Directed retry (DR)

A-interface circuit type mismatch caused requests


36/39RN20223EN14GLN0


36


001204 DROP TCH ASSCOMPL TO RFCH REL[S11.5 counter]

Benchmarking KPIs, CS, Dropped call formulas

TCH DROPS AFT ER 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 STARTEDconn_ackto BTS

TCH ASSIGNED (alert followed)Assignment_completefrom BTS

TCH SEIZEDBSC allocates a TCH as a response toTCH 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 COMMANDfrom MSC

TCH D ROPS AFTER ASSIGNMENT

spare057044 /c57044-tch_re_est_assign /c57032

-----------------------------

TCH ASSIGNMENTS FOR NEW

CALL

tch_new_call_assign

/c57033

TCH DROPS AFTER ASSIGNMENT

drop_after_tch_assign /c1202-tch_re_est_assign /c57032

-----------------------------

TCH ASSIGNMENTS FOR NEW

CALL

tch_new_call_assign

/c57033

TCH RELEASEDisconnect from MS (A)Disconnect. from MSC (B)

S10.5 dcr_8g

S7 dcr_3j

S11 dcr_8h

S7 dcr_8b

RF CHN RELEASERf_channel_release_ackfrom BTS

S4 dcr_5a

Benchmarking KPIMore accurateoptimizing KPI

Different reasonscan seen


37/39RN20223EN14GLN0


37


Benchmarking KPIs, PSAverage 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 schemeselection

The lower the value the poorer the radio link quality causingretransmissions and use of lower coding schemes.

NOTE!

KPI is collectingcounter data from 2

different tables


38/39RN20223EN14GLN0


38


Benchmarking KPIs, PSTBF 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

ResponseFlush

CSW

TrafficSuspend

Normally

Ended

TBFs

TBF

Attempts

Establishment

Failures

No

ResponseFlush

CSW

TrafficSuspend

Normally

Ended

TBFs

TBF Failures


39/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

PriorizationWork ordersSolution

VerificationImplementations

Are CriteriasFulfilled

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

Documents