Generic selectors
Exact matches only
Search in title
Search in content

N3105_Limit Optimization

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #56189 Reply

    Does anybody have experience on optimizing the N3105_Limit parameter on an Alcatel-Lucent network? Could it impact, in a positive way, the DL_TBF_DROP_RATE?

    #56190 Reply

    this parameter is useful to detect the drop, isn’t it ? could you write down the definition and the trigger condition here please ?

    it makes life easier.

    #56191 Reply

    Thanks Pix, this parameters works similar to RLTO counter for voice. There is the definition: For a DL EGPRS TBF this parameter defines the maximum number of expected Packet Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF.

    #56192 Reply

    Ok, thanks.
    Then, i’d say you just change the way you count the TBF drop. Even if it decreases the TBF drop %, from end user point of view, a drop is still a drop, even if it wasn’t counted by the MFS 🙂

    There is a defense mechanism though, so that the PDCH goes back to MCS1 or CS1 if packets are lost. Perhaps by increasing the N1305limit would give more time for this mechanism to work.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: N3105_Limit Optimization
Your information:

<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre class=""> <em> <strong> <del datetime="" cite=""> <ins datetime="" cite=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">