- This topic has 15 replies, 1 voice, and was last updated 12 years, 4 months ago by
.
-
Posts
-
In my bSC SOME Stand alon Site Having
Low TASR/RxQual
Please help to Improve this
suggest any parameter.Have you checked the reason for poor RX qual?
try finding which TRX is having bad quality BCCH, GSM hopping or DCS and then investigate for frequency clashes, Wrong inner zone settings, wrong MAL / MAIO settings, faulty Radio/ Issue with Path balance etc.
Tnaks for the help Mania
Can any one tell me cascading is also reason for Poor TASR.
Hi Mania,
Please help me again
here some cells are coming of ageing 2-3 days in TASR& TCR.
Then Its automatically disappear in bad KPI.Hi Saurabh,
Could you please explain, I am not familier with the terms TASR& TCR..
I can assume TASR to be TCH_Assign_Success_Rate but no idea of TCR. Also which vendor are you working on.TCR – TCH Comp rate
I am working for Huawei.TCR=100-TCH Drop Rate
Yes
Well not familiar with Huawei I think you should start with the usual checking. if the cells are of the same cluster check if IOI is on the increase with same trend. Check if the whole BSC gets effected then it might be some hardware level issue. however if these are random cells at random locations then analyse individually as mentioned below.
As to which TRX / set of hardware gets degraded for each site when the degradation occurs. Also it might be environmental issue so check if any specific band gets degraded. check if distance drops increase or RACH failures increase with the same trend.What the reason for delay handovers?
While attempting the handover Rxqual and Rx level degraded?why?any one can help me to explain rach failure
hi,
rach failure could be due to two main reasons:
1) the channel request contains an invalid “cause” field.
2) the timing advance is greater than the max timing advance allowed (“rach ta filter” or “max ta”)Reason 2 is quite straightforward. Maximum TA possible is 63, but it can be reduced by operator.
Reason 1 : mostly due to electromagnetic noise which sounds like a near-perfect channel request. Except the field “cause” contains an invalid value.
-> possibly HO ACCESS aimed at another cell (TCH, BSIC) where TCH(n)=BCCH(s) and BSIC(n)=BSIC(s).
-> possibly self-generated noise from the BTS itself
-> a crazy MS
-> an external device that sends bursts of signal, which actually sounds like a ch. req. (i think we’ve seen an army radar which was doing this, on this forum, a while ago)regrds
pixCascading will have impact on TASR….iF you configure more than 12 trx in a single E1 ,you are going to get issues.
- The forum ‘Telecom Design’ is closed to new topics and replies.
