Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

General Capture HO

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 27th August 2007 at 10:12 #49002
    FR
    Guest

    HI,

    I need some info regarding “general capture handovers” in Alcatel systems.

    EN_GENERAL_CAPTURE_HO and CAPTURE_TRAFFIC_CONDITION are two paremeters that i have found. As far my understanding till now it causes a HO to shift traffic from one cell to other. Does any other parameter affect such HO or any indicator other than traffic can be made its threshold?

    Regards,

    27th August 2007 at 14:08 #49003
    pix
    Guest

    hello FR,

    here is the algorithm for GENERAL CAPTURE HO :
    Traffic_load(0) = CAPTURE_TRAFFIC_CONDITION
    And Traffic_load(n) different than high
    And AV_RXLEV_NCELL(n) greater than L_RXLEV_CPT_HO(0,n) + max(0,[MS_TXPWR_MAX(n)-P])
    And EN_GENERAL_CAPTURE_HO = ENABLE

    27th August 2007 at 14:08 #49004
    Pix
    Guest

    Serving cell can be any type, any layer
    Target cell can be any type, any layer

    It is a VERY powerful HO, very dangerous in my opinion. You should rather use cause 14 (upper layer to lower layer), or cause 21 (from 900 cells to 1800 cells).

    This HO is used to force traffic to be pushed towards a specific cell, depending on the traffic load of the serving cell, and the traffic load of the target cell.

    When you activate this general capture HO on cell A, and you define a L RXLEV CPT HO(A,B) > -110dBm, what will happen is that you push traffic from cell A to cell B.

    Regarding QoS Indicators, you can check the HO causes split (CHO…) due to general capture (cause 24).
    It is based on QOS Counter MC1044.

    Regards,

    28th August 2007 at 04:29 #49005
    aso
    Guest

    dear
    this feature in ericsson and huawei called Load sharing .
    the congestion cell by this feature distribute traffic to the neighbor cells but as pix mention it depend on the traffic on neighbor cells which generally is two condtion one related to serving cell and other to neighbor cells

    28th August 2007 at 16:00 #49006
    pix
    Guest

    there are other “sweeter” load sharing features in alcatel… IMO, never use the general capture HO (unless all other solutions are dried out !)

    The general capture HO is as subtle as killing a mosquito with a bazooka.

    28th August 2007 at 17:35 #49007
    AD
    Guest

    Hi pix, what are other ways to shift traffic from one cell to another in alcatel system. besides that, general-capture-ho was enabled on only one cell in our network and there were many ping-pong handovers from this cell to another cell. what could be the reason possibly?

    28th August 2007 at 17:50 #49008
    pix
    Guest

    ad,

    1. traffic ho (cause 23), ho margin, forced directed retry, link factor, load factor, and the best for the end : FAST TRAFFIC HO !!! The BEST !!!

    2. yes, when you activate general capture on cell B, with l rxlev cpt ho (b, a) > -110dBm, you must disable PBGT HO (cause 12) on cell A. Otherwise, it will cause severe pingpong HO.
    To exit cell A, you cannot use PBGT HO, so you must use another HO cause, such as LOW LEVEL DOWNLINK (L_RXLEV_DL_H = -85dBm for instance)

    Regards,

    29th August 2007 at 07:25 #49009
    pix
    Guest

    to be more clear, you don’t disable the pbgt on cell A, you just set HO_MARGIN(A,B) = 127dB

    pbgt ho towards other cells can still be authorized, as long as it won’t lead to a triple ping-pong.

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • The forum ‘Telecom Design’ is closed to new topics and replies.