DCR- analysis, dcr_32a

(a.tch_radio_fail + a.tch_rf_old_ho RF Reasons +(a.tch_abis_fail_call - d.FACCH_CALL_SETUP_FAIL_PAGING) ;Ref 1 + a.tch_abis_fail_old Abis -interface A -interface +a.tch_a_if_fail_call + a.tch_a_if_fail_old +a.tch_tr_fail + a.tch_tr_fail_old Transcoder Other reasons +a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset +a.tch_netw_act + a.tch_act_fail_call) Other reasons sum(b.tch_re_est_assign) Call re-establishments 100 * ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Sum (a.tch_norm_seiz) Calls started directly in the cell DR calls +sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch + c.cell_sdcch_tch) - sum(a.tch_succ_seiz_for_dir_acc) ;ref.2 + sum(a.tch_seiz_due_sdcch_con) FACCH call setup calls - sum(b.tch_re_est_assign) Call re-establishments Sum

Counters from table(s): a = p_nbsc_traffic b = p_nbsc_service c = p_nbsc_ho d = p_nbsc_res_avail Ref 1; The counter002072 FACCH_SETUP_FAIL_DUR_PAGING used to compensate the counter
001084 TCH_ABIS_FAIL_CALL that is updated faultily after activation of FACCH Ref.2; Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Segment related problems: There might be some problems with tch_norm_size if used on BTS level and the BTS is part of the multisegment.

Soc Classification level 1 Nokia Siemens Networks

Presentation / Author / Date

DCR >2% and DCR_count > 10#

DCR > 2% & DCR_num >10

Yes

Drops due to RF reasons

No

Drops due to Abis

No

Drops due to A-interface

No

Drops due to Transcoder

No

Drops due to Other reasons

No

Yes

Yes

Yes

Yes

Yes

No

RF

Abis

TR

Other

Case Closed

Soc Classification level 2 Nokia Siemens Networks

Presentation / Author / Date

RF reasons (p_nbsc_traffic_tch_radio_fail, p_nbsc_traffic_tch_rf_old_ho)

Case closed
Check RX Statistic table or ND report 204, UL/DL quality/level distribution. Any Bad Quality problems = Lots of samples in good signal level and bad quality?

RF

1*

No

1*

Check RX Statistic table or ND report 204, UL/DL level distribution. Any Bad Level problems = Lots of samples in bad signal level?

No

2*

Check HOs to adjacent cells, Any bad HO problems to any adjacent cells? hfr_58, hfr_59

No

Check cell parameters, discrepancies? ND_parameters

No
Check all the alarms

No
DCR still too high

hfr_58, hfr_59

Yes
YES TRX is broken Change (sample the TRX distribution is
somehow strange, for example only quality 4 samples)

Yes
YES Change the TRX / combiner
TRX / combiner is broken, for example only <-100dBm level samples

Yes

3*

Check TA statistics and Check all Neighbors. If lots of long distance samples and only nearest cells are neighbors, may be some neighbor cells are missing ND 232

Yes
Make parameter corrections

yes

No No
Change new frequency based on interference matrix Coverage problems. Improve coverage Add LNA or new sites

YES Add neighbors

Neighbors are missing

No
YES make parameters, any corrections HOC parameter
problems? Check all HO

HOC

1* P_nbsc_rx_statistics 2* P_nbsc_ho_adj 3* P_nbsc_power

No
Capacity added Check blocking in target
cells. If blocking, add capacity to blocked cells

2*
Soc Classification level 3 Nokia Siemens Networks

blck_19, blck_20

TRX / combiner is broken

No blocking
Check if HO fails are due to MSC/ BSC border. If bad values, check borders. AreaND optimizing?

150

Presentation / Author / Date

Abis reasons (p_nbsc_traffic_tch_abis_fail_call, p_nbsc_traffic_tch_abis_fail_old,

p_nbsc_res_avail_spare002072 = p_nbsc_res_avail_facch_call_setup_fail_paging(S12))

Abis
All Alarms are checked and abis trace is done

Drops are checked and are not real abis problems

Case closed no
Still high drops in Abis interface

yes 1*

Check CC table, which phase drops are happening

Drops are happening in the release phase

no

1* yes

Check the parameters related to abis. BSC parameters

no
Alarms are solved
Investigate alarms. If problems are not solved, activate abis trace check the BTS release and the timer 3109 expired values. >BTS version 6.1 3109 expires in a BSC while waiting for the Release indication.These are seen as abis drops.These are not real drop not real abis problems

Yes

Yes

Any improvements,

No

activate
Investigate log files.

1* P_nbsc_CC

If not long enough, activate another trace

Trace has been measured long enough. Any problems found

No

Make corrections Soc Classification level 4 Nokia Siemens Networks

Yes
Presentation / Author / Date

A- reasons (p_nbsc_traffic_tch_a_if_fail_call, p_nbsc_traffic_tch_a_if_fail_old)

Case closed A
A interface problems. Alarms are checked and A interface trace is done

yes

No problems
Check ET lines in the BSC and transcoders /TCSM. Any problems

Checked
Are parameters and timers checked

no
Still A drops or problems

no
Alarms solved
Investigate alarms.If problems are not solved, activate A trace
Repair ET lines

no yes
Check that A parameter values are correct

yes

ZNRI:NA0; ZNNI:1,C;

Yes

Any improvements

No

activate
Investigate log files.

Check that A timer values are correct

ZNMI:C;

Check if there are errors, when MSC assign some pools Check that sccp counter values are correct

Any protocol error unspecified? Check bug possibility

ZOCI:1;

No
Make corrections Soc Classification level 5 Nokia Siemens Networks

Any problems found.

Yes
Presentation / Author / Date

Make corrections

Transcoder reasons (p_nbsc_traffic_tch_tr_fail, p_nbsc_traffic_tch_tr_fail_old)

Case closed TR
TR problems. Alarms are checked

yes

Check CC table, in which phase TR drops are happening

Not release phase

Check TR codec specific fails, run ND report 247,transcoder failure report

done

1* no
Alarms solved
Investigate alarms.If problems are not solved, activate abis trace (remote TR failures)

Check TCSM statistics, run done ND 523. Check also ICTF parameter

Check that TR parameters are correct. If not, correct these

Release phase
If release phase, not real drops

Not done
If drops are happening in some specific codec HR/FR issue investigate or is it more like individual TR problem

Not done
If there some problems with TCSM investigate. ICTF, how many fails are ignored

no
Still TR drops or problems

Yes
Any improvements

No

activate
Investigate log files.Check if failures are following some PCM either in Abis or A and fix accordingly. Before Implementing HR in the BSC & cells it is must to reconfigure the A interfacelinks to support Dual Rate. Otherwise it will give rise to high call failures mainly TCH_TR_fail due to mismatch of coding between TCH in Radio & "A" interface.

yes
1* P_nbsc_CC

No
Make corrections Soc Classification level 6 Nokia Siemens Networks

Any problems found

Yes
Presentation / Author / Date

Other reasons (p_nbsc_traffic_tch_lapd_fail, p_nbsc_traffic_tch_bts_fail,

p_nbsc_traffic_tch_user_act, p_nbsc_traffic_tch_bscu_act, p_nbsc_traffic_tch_netw_act, p_nbsc_traffic_tch_act_fail_call)

Case closed No Other

Check all the alarms

Lapd fails

No

bts fails

No

Netw act

No

User act, bscu, act fail

No

Still lots of other drops

Yes Yes
signalling fails or PCM fails. Check transmissio / parameters

Yes
TRX or BTS fails. Check that BTS/ TRX are working properly

Yes
Configuration problems, check configurations

Yes
Resets or act fail channel failures

Soc Classification level 7 Nokia Siemens Networks

Presentation / Author / Date