SDDCR- analysis, sdr_1a

Sum (a.sdcch_radio_fail + a.sdcch_rf_old_ho RF Reasons +(a.sdcch_abis_fail_call + a.sdcch_abis_fail_old Abis -interface +a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old A -interface +a.sdcch_lapd_fail + a.sdcch_bts_fail + a.sdcch_user_act Other Reason + a.sdcch_bcsu_reset +a.sdcch_netw_act ) Other reasons 100 * -------------------------------------------------------------------------------------------------------------------------------------------------Sum (a.sdcch_assign successful seizures of SDCCH for an immediate assignment + a.sdcch_ho_seiz) Number of successful SDCCH seizures for a handover

Counters from table(s): a = p_nbsc_traffic

Use: To follow up the performance of SDCCH from a technical point of view. Experiences on Use: 1) High SDCCH drop rates usually result from ghost accesses. A BTS decodes them from environmental or background noise and filters out most of them. However, all of them cannot be filtered out and the RACH request is passed on to the BSC for processing and for the allocation of a SDCCH channel. The counter GHOST CCCH RES (3030) is updated each time a CHANNEL REQUIRED is rejected because of an invalid establishment cause. In GSM ph.1 there exist altogether eight establishment causes, three of which are undefined as invalid, for example, resulting in that this counter shows only 3/8 of all the ghost accesses the BTS has decoded. For the rest, a SDCCH is allocated and this will result in SDCCH_ABIS_FAIL_CALL failure. Because of ghost attempts the SDCCH drop ratio is high with low traffic. As the amount of call attempts increases, the influence of ghosts becomes smaller and the drop ratio approaches its real value. 2) The rate of ghosts coming to SDCCH dropped when BTS B9 with improved ghost filtering was taken into use. NOTES: Known problems: In SDCCH failure counters it is not possible to separate LU and call seizures.

Soc Classification level 1 Nokia Siemens Networks

Presentation / Author / Date

SDDCR >2% and SDDCR_count > 10#

SDDCR > 2% & SDDCR_num >10

Yes

Drops due to RF reasons

No

Drops due to Abis

No

Drops due to A-interface

No

Drops due to Other reasons

No

Yes

Yes

Yes

Yes

No

RF

Abis

Other

Case Closed

Soc Classification level 2 Nokia Siemens Networks

Presentation / Author / Date

RF reasons (p_nbsc_traffic_sdcch_radio_fail, p_nbsc_traffic_sdcch_rf_old_ho)

Case closed
Check RX Statistic table or ND report 204, UL/DL level distribution. Any coverage problems = samples in bad signal leve <100dBm

No

RF

1*
YES Check TRX, Combiners, configuario ns, diversity and power parameters

1*

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

No

No
DCR still too high

Yes

All Alarms are checked and abis trace is done

Yes

No
DCR still too high

Yes
Any balance problems between UL and DL. Check ND 195, ND 191 or link balance table

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

no
Alarms are solved
Investigate alarms. If problems are not solved, activate abis trace

yes

2*

Yes
Any improvements,

No

No
Not Correct make Check that corrections power
control parameters UL / DL are correct

No
Change new frequency based on interference matrix

activate
Investigate log files. Check DX causes See doc Call related DX causes in BSC, If not long enough, activate another trace

Optimizer, Planner

PoC Correct
Coverage problems. Improve coverage Add LNA or new sites
Soc Classification level 3 Nokia Siemens Networks

Trace has been measured long enough. Any problems found

No

1* P_nbsc_rx_statistics 2* P_nbsc_link_balance

Make corrections

Yes

Presentation / Author / Date

Abis reasons (p_nbsc_traffic_sdcch_abis_fail_call,

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

Abis
YES No
Any improvements

Check abis No drops.Is the main reason sdcch_abis_fail_ call

No

1*

1*

YES

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

yes
No Yes
Has any parameter changes done Still abis drops and problems

Check t3101 expired, is the No value almost same as sdcch_abis_fail_ call

Yes
YES Check TRX, Combiners, configuario ns, diversity and power parameters
Any balance problems between ul and dl. Check ND 195, ND 191 or link balance table

No
Adjust rx_lev_access_min rx_lev_min_cell values little lower. Caution, This can increase TCH Drops.

Yes

No

c57020 YES

2*

YES is broken Change TRX (sample the TRX distribution is

somehow strange, for example only quality 4 samples)

Check Co BSIC YES, change + BCCH the bsic problems, any

No

site with same BSIC + BCCH is existing < 50km

No YES, unlock trxs

Not Correct Check that make power control corrections parameters UL /

DL are correct

No
Change new frequency based on interference matrix

Any availability problems. Check sdcch availability

PoC

ava_63a
No
Check if cells No are located near LA border more sdcch traffic

Coverage problems. Improve coverage Add LNA or new sites

Check ghost interference reservations, analysis c3030 values. Is this the main reason

YES, see

No Soc Classification level 4 Nokia Siemens Networks

YES, Try to reduce overlapping over borders, etc. tilting. Rehoming can sometimes helps, if areas not optimized. Presentation / Author / Date

1* P_nbsc_rx_statistics 2* P_nbsc_link_balance

Case closed

A- reasons (p_nbsc_traffic_sdcch_a_if_fail_call, p_nbsc_traffic_sdcch_a_if_fail_old)

yes No
DCR still too high

All Alarms are checked and A trace is done

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

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

yes

No

Yes
Any improvements,

No

Case closed

activate
Investigate log files.Check DX causes See doc Call related DX causes in BSC, If not long enough, activate another trace

Trace has been measured long enough. Any problems found

Make corrections Soc Classification level 5 Nokia Siemens Networks

Yes
Presentation / Author / Date

Other reasons p_nbsc_traffic_sdcch_lapd_fail, p_nbsc_traffic_ sdcch_bts_fail,

p_nbsc_traffic_sdcch_user_act, p_nbsc_traffic_sdcch_bcsu_reset, p_nbsc_traffic_sdcch_netw_act )

Case closed
No

Other

Check all the alarms

Lapd fails

No

bts fails

No

Netw act

No

User act, bcsu_reset

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 6 Nokia Siemens Networks

Presentation / Author / Date