- This topic has 11 replies, 1 voice, and was last updated 11 years, 6 months ago by Ian.
3rd June 2010 at 12:02 #62990VanGuest
after the IR(UL/Dl) activation in our network, we observed increase of TBF_Drop rate in DL. That is normal or there is something other ?
rb_bg3rd June 2010 at 14:13 #62991pixGuest
what are you new parameters settings related to IR & resegmentation ?
pix7th June 2010 at 08:37 #62992VanGuest
the changed parameter are
The TBF_Drop in UL also is increased but this is becomes after Extended_TBF_UL activation.
rb_bg9th June 2010 at 03:00 #62993PaulGuest
As I know in Alcatel PArameter, there is no EN_IR_DL, There are only EN_IR_UL and EN_RESEGMENTATION_UL.
Based on ALU Documentation, EN_IR_UL should be activated (ENABLE).The activation of both at the same time may reduce the gain
of the Incremental Redundancy
But why does the default value is 0 (it means DISABLE)?
If EN_IR_UL is ENABLE, supposedly it increase the accessibility and attainability of UL_Tbf_Establshment, but I don’t know why in your case it caused DL_TBF_DropRate.
Need your help 🙂
Paul21st June 2010 at 11:01 #62994VanGuest
Is there anybody to know?
…After the IR(UL/Dl) activation in our network, we observed increase of TBF_Drop rate in DL. That is normal or there is something other?…21st June 2010 at 13:20 #62995PixGuest
In the parameter definition :
“To allow the best throughput in DL, it is strongly recommended to set this parameter to 0 (DISABLE) i.e. to not forbid the resegmentation.”
When you enable this parameter, you actually force the system to stay in high MCS.
When you disable it, you actually allow it to use lower MCS.
In both caases, the IR is used whenever possible !
In case of network with good radio conditions all over, you can try to set it to “ENABLE”. But in typical networks, with sometimes bad conditions, it is safer to keep it at “DISABLE”.
(sorry for the late reply)4th July 2010 at 09:03 #62996sureshGuest
normalyy its combination of la/ir/bler but here if its disable then only la mode is availv\bale and if c/i is high it will go for low mcs and because of this throught will affect
while in ir it will do puncture within same mcs and after ms memory is full it will change ir to la but here user will get good throughput but i don’t knoe here if its enable then is it possible to go from ir to la like erc sys or will it remain in ir?
so which one is best?4th July 2010 at 13:20 #62997pixGuest
all answers are below…
pix5th July 2010 at 08:32 #62998RexGuest
Are EN_IR_UL and EN_RESEGMENTATION_UL optional parameters? Editing each BSC these params are empty, there’s no possibility to chose enable or disable.
Rex5th July 2010 at 08:55 #62999PixGuest
These parameters are now available per cell, not per BSC (it depends on your release).
Please check the cell level first, if it is not there, then we’ll dig further.
pix5th July 2010 at 09:44 #63000RexGuest
Yes, thanks. I didn’t know that, in B9 it was in BSC level. Except EN_IR_UL_per_cell there is EN_FULL_IR_DL_per_cell as well. Should we enable that too. And which is better, IR without Resegmentation or Resegmentation without IR?
Rex8th February 2011 at 03:00 #63001IanGuest
long time you have posted this but have you solved the problem below, we are facing the same here, should we activate IR_UL (according to Pix, this features is useless) or/and Resegmentation ?
we are in B10 and facing UL/DL tbf failures