Thanks Thanks:  6
Page 1 of 2 12 LastLast
Showing results 1 to 10 of 11

Thread: HSUPA Low Throughput

  1. #1
    Member Reputation: 25
    Join Date
    2012-05-17
    Posts
    14


    Default HSUPA Low Throughput

    Hi experts,

    What could be checked in our RNC to improve HSUPA Throughput? Any specific feature? Parameters? We use RAN 14.0. On DTs the rate is very low < 100kbps on most of the route. All Nodebs are IP with 4 carriers (mostly)!! RTWP is high! Lots of users per Cell. Lots of custumers complains!!

    Pls any help I give reputation

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Member Reputation: 172
    Join Date
    2010-11-01
    Posts
    515


    Default Re: HSUPA Low Throughput

    You already answered i.e RTWP is high . that's one of the main problems nowadays.

    br
    alex

    Quote Originally Posted by MaikonX View Post
    Hi experts,

    What could be checked in our RNC to improve HSUPA Throughput? Any specific feature? Parameters? We use RAN 14.0. On DTs the rate is very low < 100kbps on most of the route. All Nodebs are IP with 4 carriers (mostly)!! RTWP is high! Lots of users per Cell. Lots of custumers complains!!

    Pls any help I give reputation

  4. #3
    Member Reputation: 25
    Join Date
    2012-05-17
    Posts
    14


    Default Re: HSUPA Low Throughput

    Quote Originally Posted by agenov View Post
    You already answered i.e RTWP is high . that's one of the main problems nowadays.

    br
    alex
    We all know this.

    And what about changing the BACKGROUNDNOISE on UCELLCAC to something like 220 (-90dbm)! Field tests has shown improves on UL thr during busy hour. But what will be the "side effects" on this? Anyone can explain?
    Last edited by MaikonX; 2014-08-29 at 09:26 AM

  5. #4
    Member Reputation: 172
    Join Date
    2010-11-01
    Posts
    515


    Default Re: HSUPA Low Throughput

    never played with that parameter. Try and share



    Quote Originally Posted by MaikonX View Post
    We all know this.

    And what about changing the BACKGROUNDNOISE on UCELLCAC to something like 220 (-90dbm)! Field tests has shown improves on UL thr during busy hour. But what will be the "side effects" on this? Anyone can explain?

  6. #5
    Member Reputation: 27
    Join Date
    2011-08-23
    Posts
    24


    Default Re: HSUPA Low Throughput

    Hello,
    First you need to check transmission capacity and way for low HSUPA rates,
    If RTWP is high, you need to adjust attenuation parameter,
    Regards

  7. #6
    Member Reputation: 25
    Join Date
    2012-05-17
    Posts
    14


    Default Re: HSUPA Low Throughput

    Quote Originally Posted by gudubettin View Post
    Hello,
    First you need to check transmission capacity and way for low HSUPA rates,
    If RTWP is high, you need to adjust attenuation parameter,
    Regards
    IuB Capacity is ok, all nobes are IP, this is not the case. What is the name of this attenuation parameter?

    The changes in BNG Noise has improves a lot the UL throughput! Also you must turn OFF BNG Switch, if it is ON.

  8. #7
    Member Reputation: 295
    Join Date
    2009-06-04
    Posts
    270


    Default Re: HSUPA Low Throughput

    Hello,

    Could you mention the exact parameter names for background noise and bng switch?

    BR

    Quote Originally Posted by MaikonX View Post
    IuB Capacity is ok, all nobes are IP, this is not the case. What is the name of this attenuation parameter?

    The changes in BNG Noise has improves a lot the UL throughput! Also you must turn OFF BNG Switch, if it is ON.

  9. #8
    Member Reputation: 25
    Join Date
    2012-05-17
    Posts
    14


    Default Re: HSUPA Low Throughput

    Quote Originally Posted by Shakeel_15 View Post
    Hello,

    Could you mention the exact parameter names for background noise and bng switch?

    BR
    Yes, sure!

    MOD UCELLCAC: CELLID=XXX, BGNSWITCH=OFF, BACKGROUNDNOISE = 220 ( 220 => -90dBm, by default is 61 => -106dBm). The formula is -112dbm + BGN/10.

  10. Thanks justdream thanked for this post
  11. #9
    Member Reputation: 71
    Join Date
    2011-07-14
    Posts
    90


    Default Re: HSUPA Low Throughput

    If BGNSWITCH is set to OFF:
    -The background noise used by the HSUPA scheduling is set to a fixed value determined by BACKGROUNDNOISE, by default to -106dBm (typical value of background noise if the spectrum is clean),
    - The HSUPA scheduling algorithm will compare the value of BACKGROUNDNOISE + MaxTargetUlLoadFactor(e.g. 4dB) with the measured RTWP to decide if HSUPA resources can be allocated.

    So if the background noise is bad estimated, you have risk to be sooner limited and have bad HSUPA performances.

    If you put BGNSWITCH to ON, the Background noise value will be updated based on RTWP measurements and so you will have a value closer to real background noise in your network and you will not face the noise rise limitation as soon as in the previous case.

    However, having RTWP of -90dBm is not normal and you should look for the cause of the interference (other system interfering such as 900MHz or 2100MHz not licensed equipment, repeaters, radar,...). This investigation can take time.

  12. Thanks justdream thanked for this post
  13. #10
    Member Reputation: 25
    Join Date
    2012-05-17
    Posts
    14


    Default Re: HSUPA Low Throughput

    Quote Originally Posted by Philippe View Post
    If BGNSWITCH is set to OFF:
    -The background noise used by the HSUPA scheduling is set to a fixed value determined by BACKGROUNDNOISE, by default to -106dBm (typical value of background noise if the spectrum is clean),
    - The HSUPA scheduling algorithm will compare the value of BACKGROUNDNOISE + MaxTargetUlLoadFactor(e.g. 4dB) with the measured RTWP to decide if HSUPA resources can be allocated.

    So if the background noise is bad estimated, you have risk to be sooner limited and have bad HSUPA performances.

    If you put BGNSWITCH to ON, the Background noise value will be updated based on RTWP measurements and so you will have a value closer to real background noise in your network and you will not face the noise rise limitation as soon as in the previous case.

    However, having RTWP of -90dBm is not normal and you should look for the cause of the interference (other system interfering such as 900MHz or 2100MHz not licensed equipment, repeaters, radar,...). This investigation can take time.
    1o. OK that is the default parameter. But we can not always work with defaults.
    2o. Yes that is how HSUPA scheduling will work. Only that the value of Noise Rise (dB) will depend on the MaxTargetUlLoadFactor (Noise rise dB = 10*Log(1/(1-MaxTargetUlLoadFactor)). Só this will not always be 4 dB. The default value of 75% leads to 6 dB in noise rise. In our network this value is 85% (8.2 dB) and some sites is even more 90% (10dB)!
    3o. We agree the the best will be ON. But RTWP around -90dBm or even more can be easily reached by load on busy hour on our network. And this has tremendous impact on HSUPA.

    With all that, I am just saying the we had a great improvement on HSUPA logs from drive test after changing those parameters.

  14. Thanks justdream thanked for this post

Tags for this Thread

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •