Thanks Thanks:  1
Showing results 1 to 5 of 5

Thread: F3 barred Cell Huawei

  1. #1
    Member Reputation: 50
    Join Date
    2011-02-03
    Posts
    375


    Default F3 barred Cell Huawei

    Hi all,

    We tryed the barred cell strategy on F3 to limit CS traffic on F3 and only PS traffic via blind HO from F1 and F2 will be carried on F3.

    We noticed that for F3 the CELLFACHUEs and CELLPCHUEs come to 0 !

    Also increase in PS drop for F3.

    Any could explain this.

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Junior Member Reputation: 12
    Join Date
    2012-04-01
    Posts
    1


    1 out of 1 members found this post helpful.

    Default Re: F3 barred Cell Huawei

    Hi Fahmi,
    This seems to be due to an issue in how a UE could decode messages in SIB3 and SIB4. Even though UE moving to CELL-FACH need to read SIB4 to get cell details, most of the UE's unable to correctly decode SIB4. When SIB4 is not correctly decoded, it uses SIB3 and according to SIB3 the F3 cell is idle barred. Therefore when a UE send a message to tranfer UE to CELL-FACH it will try to latch but after few seconds will latch to F1/F2 and send a Cell-Update updating from same sector F1/F2 cells. Therefore there will be no FACH/PCH UE in barred carrier cells.

    We had a similar issue and solution adopted was to change strategy as move to F1/F2 based on reselection parameters as below.
    For F3 cells add IDLESINTERSEARCH=9 and then,
    For F1/F2 cells add IDLEQOFFSET2SN=50 and for F3 cells add IDLEQOFFSET2SN=-50.

  4. Thanks fahmi thanked for this post
  5. #3
    Member Reputation: 156
    Join Date
    2010-03-26
    Posts
    74


    Default Re: F3 barred Cell Huawei

    Normally SIB4 is not configured and there is an indicator field in SIB3 mentioning that SIB4 is False so the UE shouldn't look for SIB4. This means the same cell selection and reselection settings are used in Idle and connected mode (PCH/FACH). So the SIB4 not being decoded explanation doesn't fit for me.

  6. #4
    Member Reputation: 119
    Join Date
    2009-02-09
    Location
    ISTANBUL
    Posts
    127


    Default Re: F3 barred Cell Huawei

    Hi Fahmi Kardesim

    If you remember we faced the same scenario in SA and we have used the same method which hasithamar recommended. I think it is still valid.

    take care and enjoy.
    kadir

  7. #5
    Member Reputation: 156
    Join Date
    2010-03-26
    Posts
    74


    Default Re: F3 barred Cell Huawei

    Hi,

    We use same strategy of IDLEQOFFSET2SN and I had to search old docs to find out why we chose it long time back, so here's the explanation:

    When the cell is barred, it can be barred for idle mode and connected mode independently. If it is barred for both, CELLFACHUEs and CELLPCHUEs will be 0. In this case when the state transition will happen from DCH to FACH, UE has to first reselect another cell (which is not barred) and then send the physical channel reconfiguration response. If this reselection takes longer, the response times out and can result in a drop!

    I hope it makes sense.

    BR,
    Faisal

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
  •