Decrease RRC NoReply Failure in LTE

[mounir34]

Dears
could you please share some Parameters to decrease RRC NoRply failure in Huawei Equipement based in your experience


Thanks

[sak2e]

Also faced the same issue,
I'm pretty sure there are no problem at coverage / interference / site to site distance is OK but somehow the NoReply failure come and leave without permission

[electron]

Also faced the same issue,
I'm pretty sure there are no problem at coverage / interference / site to site distance is OK but somehow the NoReply failure come and leave without permission

Hi,


RRC reconig time expiration could be the cause .


Cheers

[mounir34]

do you mean T300 ?

Hi,


RRC reconig time expiration could be the cause .


Cheers

[mounir34]

for your case to come and leave without permission,i think is related to 1 user ,did you check the trace or CHR to confirm if 1 or more user caused your problem ,

Also faced the same issue,
I'm pretty sure there are no problem at coverage / interference / site to site distance is OK but somehow the NoReply failure come and leave without permission

[babak1349]

do you mean T300 ?

Hello
T300 is good recommendation to be checked but it is UE timer which during UE waits for RRC connection setup message also there might be enodeB timer which during enodeB waits for RRC connection setup complete So you need to check this parameter too (it could be hidden or hard coded)
Anyway "no Reply" happens when EnodeB doesn't receive te RRC connection setup complete
it can happen due to poor quality or UE moved out of LTE coverage (it means reselects other RAT)
Different UE may have different firmware and some firmware allows reselect to another RAT during RRC establishment procedure so even the issue could be for specific UE type you can disable reselection to other RAT or making it very hard by setting the parameters appropriately for test purposes..
there are other points can help too:
1) does it happen in all cells ( if it does it mean a common issue like as timers ...)
2) what is the main RRC connection request cause of failed ones ? (registration ? might mean ping pong RAT reselection)
3) doing DT for worst cell and checking what happens on the field


cheers

cheers

[mounir34]

thanks freind,do you know some parameter for Power control can solve our issue ,
before for 3G we solved this problem by increase Constant value for Initial RACH Power (power control)

Hello
T300 is good recommendation to be checked but it is UE timer which during UE waits for RRC connection setup message also there might be enodeB timer which during enodeB waits for RRC connection setup complete So you need to check this parameter too (it could be hidden or hard coded)
Anyway "no Reply" happens when EnodeB doesn't receive te RRC connection setup complete
it can happen due to poor quality or UE moved out of LTE coverage (it means reselects other RAT)
Different UE may have different firmware and some firmware allows reselect to another RAT during RRC establishment procedure so even the issue could be for specific UE type you can disable reselection to other RAT or making it very hard by setting the parameters appropriately for test purposes..
there are other points can help too:
1) does it happen in all cells ( if it does it mean a common issue like as timers ...)
2) what is the main RRC connection request cause of failed ones ? (registration ? might mean ping pong RAT reselection)
3) doing DT for worst cell and checking what happens on the field


cheers

cheers

[oucht79]

Hi

Check contention resolution timer
change PDCCH CCE aggregation level
change PDCCH DCI1A power

Thx

[mounir34]

did you tried before,could you please share the report if you have ,thx

Hi

Check contention resolution timer
change PDCCH CCE aggregation level
change PDCCH DCI1A power

Thx

[sak2e]

From CHR i couldn't identify IMSI or MSISDN, can you help me how to figure out IMSI from CHR?
Only TMSI can be found there.

for your case to come and leave without permission,i think is related to 1 user ,did you check the trace or CHR to confirm if 1 or more user caused your problem ,