You are on page 1of 27

Nokia Process & Core Optimization

Nokia Siemens Networks

KPI Evaluation Process

Nokia Siemens Networks

HOW DO WE NEED TO START OPTIMIZATION

Firstly we need to check the KPI of Cluster Level & BSC level After that Check the KPI of which BSC is going down and then find the
cells due to which KPIs going worst

Now check the Cells KPI ( Preferably CSSR, DCR & HOSR ) why it is going
worst

If CSSR KPI is worst then we need to check all the components of the

CSSR ( TCH Blocking, SDCCH Blocking, SDCCH Drop, TCH Assignment success Rate) & if DCR KPI worst check all the Raw counters also according to the formula and same procedures for the HOSR.
We need no check all the counters also for the respective KPIs not just like high Blocking or high Drops as it is also plays the very important role in Core-optimization

Nokia Siemens Networks

CSSR KPI
As we know CSSR depends on the 4 Components (TCH Blocking,
SDCCH Blocking, SDCCH Drop, TCH Assignment success Rate ) and if any of the components KPIs going worst than CSSR will be the worst.

I will discuss these cases one by one For Hardware we will discuss later

Nokia Siemens Networks

CASE-1 CSSR BAD Due To High SDCCH Drop Rate


SDCCH Drop rate may be high due to many reasons as given below Hardware Problem in a Cell Overshooting Co-channel Interference Transmission issue Phantom RACH Extra SDCCH As the above KPI shows that CSSR is going worst due to high SDCCH Drop Rate and No we have to find out the reason for High SDCCH Drop Rate

Nokia Siemens Networks

MS accessing, noise (ghosts)

SDCCH requests
SDCCH FAILURES

RACH on CCCH /c3004 ch_req_msg_rec 3/8 of ghosts (ph.1)

SDCCH ACCESSES REJECTED IN BSC


REJECTED DUE TO ILLEGAL EST.CAUSE /c3030 ghost_ccch_res Distance checking BSS5280 (S5) TRUE SDCCH SEIZURES ASSIGNMENTS FOR CALLS,LU,SS /c1007 /TRF_25a (not updated in SDCCH HO) TRUE SDCCH SEIZURES FOR CALL,SMS,SS /TRF-27 sdcch_assign SEIZURES FOR HO /c1006 MOC (incl.SMS) /c3013 succ_seiz_orig sdcch_ho_seiz BLOCKED /blck_15 succ_seiz_term sdcch_busy_att tch_seiz_due_sdcc h_con sdcch_emerg_call MTC (incl.SMS) /c3012 CALL RE-EST. /c3020 sdcch_call_re_est EMERGENCY CALL /c3021 5/8 OF GHOSTS (ph.1) AND OTHER FAILURES BEFORE ESTABL. INDICATION (incl.IMSI detach): /SD_1a c1007- TRF_25

/c57020

(S7)

(Ghosts)
T3101 adjustable by MML ZEGT:T3101..

t3101_expired SDCCH FAILURES /c1075 sdcch_abis_fail_call

(blocked chan.,corrupted msgs, failed chan.act.)

REJECTED DUE TO DISTANCE /c3031 (S5)

small part of failures other than sdcch_abis_* failures

SDCCHSDCCH HO

rej_seiz_att_due_dist

SDCCH REQUESTS /c1000 sdcch_seiz_att

SDCCHTRUE SDCCH SEIZURES FOR CALL & SS /TRF-26 TRF-27 - succ_sdcch_sms_est - unsucc _sdcch_sms_est TRUE SDCCH SEIZURES FOR SMS SDCCH HO

TCH

SDCCH BLOCKING (blck_5a)

LOCATION UPDATE /c3019 sdcch_loc_upd Normal LU Periodic LU IMSI attach

IMSI DETACH /c3033 (S7) imsi_detach_sdcch

succ_sdcch_sms_est + unsucc _sdcch_sms_est

NOTE: Triggered also in case of HO attempt if there are no free SDCCH

FACCH call setups /c1099 tch_seiz_due_sdcc h_con

Supplementary service request (S9) /c3044 CALL RE-EST. ASSGN. /c57022 (S7) sdcch_re_est_assign

Nokia Siemens Networks

SDCCH Drop Call Rate (%)



Formula: 100 * (traffic.sdcch_radio_fail + traffic.sdcch_rf_old_ho + No. of SD transaction traffic.sdcch_user_act + traffic.sdcch_bcsu_reset + failures due to BTS failure. (1036) traffic.sdcch_netw_act + traffic.sdcch_bts_fail + sdcch_lapd_fail+ sdcch_a_if_fail_call+sdcch_a_if_fail_old) / Number of SDCCH transactions ended because of a failure in the A interface on (traffic.sdcch_assign + traffic.sdcch_ho_seiz) the source channel during an SDCCHSDCCH or SDCCH-TCH HO No. of SDCCH assignments. (57021) No. of successful SDCCH seizures for a handover. (1006) Number of SDCCH transactions ended because of a failure in the A interface during a call attempt. No. of SD transaction failures due to BCSU reset. (1038) No. of SD transaction failures due to the radio failure (1003) No. of SD transaction failures due to the radio failure of the former channel during SD-SD or SD-TCH HO. (1004)

No. of SD transaction failures due to radio N/W reconfiguration actions. (1039) No. of SD transaction failures due to user action. (1037)

Counter from table: p_nbsc_traffic (Traffic Measurements)


Nokia Siemens Networks

SDCCH Drop Rate KPI Analysis

Please make sure SDCCH_ABIS_FAIL_CALL counter we dont include in the KPIs formula of SDCCH Drop Rate as this is not the customer satisfactory.
Now in the above KPI we can see the SDCCH drop rate is high due to SDCCH A interface fail call is high as major drops are going only on this counter and it is suspected due to Transmission issue so for root cause we need to check the all counters.
8 Nokia Siemens Networks /

SDCCH Drop Rate Analysis Based on Several Reasons

If SDCCH_Radio_fail counter value is high it means drops going may be


due to Overshooting, interference , Phantom RACH etc.

If 7745 Channel Failure Rate Alarm persist on SDCCH then Shift the
SDCCH from that TRX to another TRX.

For Extra SDCCH we need to check the SD Configuration as per Nokia

system 1 SDCCH can take 5000 SDCCH attempts, for this dont consider the daily KPI, please see the next slide for better explanation of this

Nokia Siemens Networks

Extra SDCCH Analysis

According to KPI there should be only one SDCCH timeslot but if I check the Database configuration it has 4 SDCCH so we need to remove the extra SDCCH from the TRXs

10

Nokia Siemens Networks

CASE-2 CSSR BAD DUE TO BAD TASR

TASR Bad due to Several Reasons Hardware Faulty Timer T10 Expired ( BSC Level) Queuing not Allowed Queue Full Due to Radio Problem Due to Hardware Issue

11

Nokia Siemens Networks

TASR FORMULA

[sum(a.tch_radio_fail+ a.tch_abis_fail_call + a.tch_a_if_fail_call + a.tch_tr_fail + a. tch_user_act + a.tch_bcsu_reset + a.tch_netw_act+ a.tch_act_fail_call + a.tch_lapd_fail+ a. tch_bts_fail)] - [sum(a.spare057044) - sum(a.tch_rf_old_ho + a.tch_abis_fail_old + a.tch_a_if_fail_old + a. tch_tr_fail_old)] 100%( * ----------------------------------------------------------------------------------------------------) % Number of successful incoming SDCCH ; sum(a.tch_norm_seiz) to TCH HOs controlled by the MSC (normal calls) + sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) ;(DR calls) - sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup

Counters from table(s): a = p_nbsc_traffic c = p_nbsc_ho

12

Nokia Siemens Networks

TASR Analysis Counters

As in the above given counters shows that suddenly some the counters value ( ABIS interface fail, Radio fail etc) increased . Radio fail may be due to some Radio problems as interference, overshooting etc and if ABIS fail call increased it may be increased due to some Transmission alarm.

13

Nokia Siemens Networks

CASE-3 CSSR Bad Due TO Blocking

CSSR is worst due to high SDCCH & TCH blocking

14

Nokia Siemens Networks

What is TCH Blocking ?


BUSY BUSY BUSY BUSY BUSY BUSY BUSY BUSY

All Timeslots are busy

When all timeslots ( 8 TS) are busy then it is called congestion and when at the time of congestion any call come through that busy timeslot then it is called blocking.

15

Nokia Siemens Networks

TCH Blocking Formula (%)


Formula: 100 * [sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch +

b.bsc_o_sdcch_tch + b.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc) sum {a.tch_rej_due_req_ch_a_if_crc -(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)} ] ______________________________________________________ [sum(a.tch_call_req) sum {a.tch_rej_due_req_ch_a_if_crc (b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type) } ]

16

Nokia Siemens Networks

TCH Blocking (%)


Formula: (Nom) 100 * [sum(a.tch_call_req - a.tch_norm_seiz)

No. of TCH requests for normal assignment. (1026) No. of successful TCH requests for a normal assignment. (1009) No. successful SDTCH HO. (Intra-cell) (4074)

sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch + b.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc)

sum {a.tch_rej_due_req_ch_a_if_crc -(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)} ]

No. successful SDTCH HO. (BSC Controlled) (4065)

Number of unsuccessful handovers due to wrong Ainterface circuit type. (4101)

Number of unsuccessful handovers due to wrong Ainterface circuit type. (4097)

No. successful SD-TCH HO. (4050) Number of successful TCH seizures in direct accesses to a super-reuse TRX during the call set-up phase. (1165)

Number of rejected TCH requests due to mismatch between the requested channel type and the A-interface circuit type (1122)

Number of unsuccessful handover due to wrong Ainterface circuit type. (4098)

17

Nokia Siemens Networks

TCH Blocking (%)


Formula: (Denom)

No. of TCH requests for normal assignment. (1026)

Number of rejected TCH requests due to mismatch between the requested channel type and the A-interface circuit type (1122)

sum(a.tch_call_req) sum {a.tch_rej_due_req_ch_a_if_crc (b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type) }

Number of unsuccessful handovers due to wrong Ainterface circuit type. (4097)

Number of unsuccessful handover due to wrong Ainterface circuit type. (4098)

Number of unsuccessful handovers due to wrong Ainterface circuit type. (4101)

18

Nokia Siemens Networks

SDCCH Blocking (%)

Unsuccessful SDCCH seizure attempts, due to nonavailability of SDCCH (1001)

Formula: 100 * (traffic.sdcch_busy_att - traffic.tch_seiz_due_sdcch_con)/


traffic.sdcch_seiz_att
Successful seizures of TCH due to SDCCH congestion (1099) Total no. of SDCCH seizure attempt (1000)

19

Counter from table: p_nbsc_traffic (Traffic Measurements)


Nokia Siemens Networks

TCH Blocking Reasons

Hardware Problem ( May be TRX faulty or any other hardware issue) Overshooting ( due to this cell are taking calls from very large distances) Any event ( Match, Exhibition, Meeting etc) Handover is better Cell is not occurring High rate of assignment failure messages

20

Nokia Siemens Networks

Optimization TCH Blocking


If hardware problem exist then need to escalate to the concerned person Increase dual Rate for reduce the TCH Blocking ( TCHF TCHD,
TCHH TCHD) Check FRL & FRU setting ( BTS Level) Check HRL & HRU setting ( BSC Level) Check HRI ( TCH in handover) setting ( BSC Level) ( it should be 5 and it means TCH has to be primarily allocated from the best BTS of the handover candidate list) Directed Retry Enable Remove Extra SDCCH Channel and convert in to TCHD in case of high TCH Traffic to reduce the blocking In case of Overshooting check RXP setting In case of very high traffic in clusters then we can reduce the power Traffic Sharing Add Extra TRX Add New Site Optimize the cell boundaries to share the traffic with surrounding cells Traffic Reason Handover enable
21 Nokia Siemens Networks /

SDCCH BLOCKING REASONS

Too much SDCCH normal traffic for cell SDCCH design


- Logical cell design, extra TRX, new site

LA border at crowded area ( Check HYS Setting) Abnormal SDCCH traffic


phantom channel requests Inadequate LAC design, causing too much LU Redesign LAC Problem with neighbor cells belong to other LAC

22

Nokia Siemens Networks

SDCCH BLOCKING ANALYSIS

23

Nokia Siemens Networks

Channel Failure Rate Above Defined Threshold

Please see the given below core analysis for the 7745 Alarm 02 01 01 00 00 00 00 00 00 01 04 100d
01 means Faulty Timeslot 02 represents Alarm on SDCCH Channel 8 Time Slots

time slot with the highest failure rate

Shift the SDCCH channel from that TRX or remove SDCCH if there is extra SDCCH timeslots The same scenario start for TCH but at the starts there is 01 in place of 02 and for that is any timeslot is faulty then we can go for Locking Timeslot & Locking TRX and after Lock we can check the Performance in Hourly KPI

24

Nokia Siemens Networks

SCCP Disturbance

0B 08 0000188D FE 0000177B FE 0000

0B means Sending Message to MTP has Failed 08 Means National Network 0

25

Nokia Siemens Networks

SDCCH Drop Rate Affects By Transmission Alarm

26

Nokia Siemens Networks

THANKS

27

Nokia Siemens Networks