huawei parameter

  • View
    140

  • Download
    4

Embed Size (px)

DESCRIPTION

parameters defined by huawei

Text of huawei parameter

Handover Control Data TableHO algorithm Range: Huawei handover algorithm Unit Default: Huawei handover algorithm Recommended: Huawei handover algorithm Description: To select handover algorithm. Note: At present, only Huawei handover algorithm is available. Min interval for TCH HOs Range: 1~60 Unit Second Default: 2 Recommended: 2 When a new TCH is assigned, a timer should be started. Only when this timer times out will handover be allowed. This parameter is the duration for this timer. This parameter is used to avoid incorrect handover due to Description: inaccurate MRs at the early stage of call establishment. The value of this parameter when MR is pre-processed by BTS should be smaller than that when MR is not pre-processed by BTS. Min interval for SD HOs Range: 1~60 Unit second Default: 2 Recommended: 2 When a new SDCCH is assigned, a timer should be started. Only when this timer times out will handover be allowed. This parameter is the duration for this timer. This parameter is used to avoid incorrect Description: handover due to inaccurate MRs at the early stage of call establishment. The value of this parameter when MR is pre-processed by BTS should be smaller than that when MR is not pre-processed by BTS. Min interval for consecutive HOs Range: 1~60 Unit second Default: 4 Recommended: 6 Description: This parameter is used to prevent consecutive handovers that can result

in bad network performance. After BSC sends a handover command, it will start a timer. BSC will not perform any handover before this timer times out. This parameter is the duration for this timer. Min interval for Emerg. HOs Range: 1~60 Unit second Default: 4 Recommended: 6 When BSC completes or fails to perform an emergency handover, it will Description: start a timer. BSC will not perform any emergency handover before this timer times out. This parameter is the duration for this timer. Co-BSC/MSC Adj Range: Yes/ No Unit Default: No Recommended: No Indicates whether to adjust a candidate cell sorting so as that handover in Description: the same BSC/MSC is in priority. SD HO allowed Range: Yes/ No Unit Default: No Recommended: No Description: Determines whether to allow the handover between signaling channels. Penalty allowed Range: Yes/ No Unit Default: Yes Recommended: Yes Indicates whether penalty is given to certain candidate cells, including Description: the target cell that has handover failure history and the cell that has emergency handover history due to too large value of TA or bad quality. Intra-cell HO allowed Range: Yes/ No

Unit Default: No Recommended: No Determines whether intra-cell handover is allowed. Intra-cell handover includes timeslot and TRX change. Intra-cell handover can reduce the impact of "Rayleigh" fading or interference. Description: When initiating an intra cell HO, select as priority the channels with different TRXs from the TRXs occupied before HO. During the intra-cell handover, the channels on the TXR different from the previously occupied TRX are preferred to ensure the service quality. Note: For the version G3BSC32.10102.06.1120A and later, the TXR different from the the previously occupied TRX are preferred. Load HO allowed Range: Yes/ No Unit Default: Yes Recommended: Yes Indicates whether Traffic load-sharing handover is allowed. Loadsharing can reduce the cell congestion and balance the traffic load for Description: each cell so as to improve network performance. It works only in the same BSC or in cells of the same layer. It is used only for TCH. Note: Extra interference might be resulted from tight frequency reuse. MS fast moving HO allowed Range: Yes/ No Unit Default: No Recommended: No The fast moving algorithm is a special algorithm to process fast moving Description: MS. This parameter is used to decide whether to use this algorithm. Rx_Level_Drop HO allowed Range: Yes/ No Unit Default: No Recommended: No Description: The parameter decides whether to use the emergency handover algorithm

when receiving level drops fast. Generally, this parameter is set to No. This algorithm requires that BTS send the original MR to BSC. 1. Normally, the BSC determines whether to initiate handovers according to the priorities of of HO types. But the treatment of the BSC for the Rx_Level_Drop HO is some special. When the BSC determines whether to initiate the Rx_Level_Drop HO, there are two cases:

Note:

When the MR pre-processing function is disabled, the BSC determines whether to initiate the Rx_Level_Drop HO according to the MR sent by the BTS. When the MR pre-processing function is enabled, the BTS determines whether to initiate the Rx_Level_Drop HO and send the judgment to the BSC in two bits. The BSC initiates the Rx_Level_Drop HO according to the judgment of the BTS and selects the proper candidate cell for the handover.

2. For abnormal cases: When the MR pre-processing function is enabled, the BTS does not send the judgment of whether to initiate the Rx_Level_Drop HO to the BSC. Therefore, the BSC determines whether to initiate the Rx_Level_Drop HO by itself. For the original MR is not sent to the BSC, the BSC does not determine whether to initiate the handover. PBGT HO allowed Range: Yes/ No Unit Default: Yes Recommended: Yes Indicates whether to use the PBGT (POWER BUDGET) handover algorithm. PBGT is a handover algorithm based on path loss. It searches a cell in real time which can meet a certain requirements and has smaller Description: path loss, and judge whether to hand over it or not. To avoid Ping-Pong handover, PBGT handover occurs only between cells of the same layer and triggered only in TCH channel. Proper use of PBGT can reduces the over-cell coverage and co-channel interference. MS power prediction after HO Range: Yes/ No Unit -

Default: No Recommended: No Indicates whether MS is allowed to use optimized power instead of the maximum power to access new channel during handover. If this Description: parameter is set to "Yes", this can reduce system interference and improve service quality. MR. Pre-process Range: Yes/ No Unit Default: No Recommended: No Indicates whether BTS pre-processes MR. If this parameter is set to "No", it means that MR is processed by BSC. In this case, the parameter Transfer original MR. and Transfer BS/MS Power Class are invalid. If this parameter is set to "Yes", this will reduces the load of Abis interface signaling and also the load of BSC. It also improves response time and Description: network performance. Meanwhile, this parameter determines the place where to perform power control. If this parameter is set to "Yes", then the power control will be performed by BTS. Otherwise, the power control will be performed by BSC. 1) MR Pre-process aims to reduce load of BSC MPU. For versions before BTS01.1130, MR Pre-process will be enabled unless busy hour traffic exceeds the theoretic value. For versions after BTS01.1130 (including BTS01.1130), MR Pre-process is advised to be enabled if no encryption is used, but not if otherwise. 2) For BTS22C, this parameter must be set as "No.". Note: 3) BTS2X (including BTS23 and BTS22C) supports G-I power control instead of G-II power control shift-to BTS. When setting this parameter, it should be noted that whether BTS supports power control. 4) In 16K mode, if some TRX configured 2 or more SDCCH, or enabled dynamic SDCCH, it is recommended to enable MR. Pre-process, and the frequency of report configured as 1 time per second. Transfer original MR. Range: Yes/ No Unit Default: No

Recommended: No Description: Indicates whether to transfer the original MR to BSC after Description: BTS pre-processes MR. When the parameter is set to "Yes", BTS transfer to BSC not only the processed MRs, but also the original MRs. In the case of 15:1 function, if the number of SDCCH/8s should be Note: greater than or equal to 2, this parameter should be set to "No". Transfer BS/MS power class Range: Yes/ No Unit Default: Yes Recommended: Yes Indicates whether to transfer the original BS/MS power class to BSC. If the parameter is set to "No", BTS will not report BS/MS power class to Description: BSC. This will affect the result of uplink and downlink balance measurement. When MR Pre-process is enabled, the result of uplink and downlink balance measurement will be affected if "Transfer BS/MS power class" Note: is set as "No". Besides, such power compensation handovers as PBGT handover, load handover and concentric handover are abnormal. Cell Asynchronism HO Range: Yes/ No Unit Default: No Recommended: No The synchronous handover between synchronous cells in a BTS to which a fiber repeater is attached is easy to fail due to different TAs for the two cells. This parameter is specially set to control the handover type of synchronous cells. Description: If you select No, the type of handovers in and between synchronous cells is synchronous. If you select Yes, the type of handovers in and between synchronous cells is asynchronous. Sent Freq.of preprocessed MR. Do not report, Twice every second, Once every second, Once every 2 Range: seconds, Once every 4 seconds. Unit -

Twice every second Default: Once a second (in a trunk networking mode of 15:1) Twice every second Recommended: Description: Note: Once a second (in a trunk networking mode of 15:1) Indicates the period of BTS to transfer preprocessed MR to BSC. In the case of 15:1 function, it is recommended to set this parameter to "Once every second".

Multi-MNC HO allowed Range: Yes/ No Unit Default: No For areas that have only one MNC, this parameter is suggested to be Recommended: configured as No. For areas that have multiple MNCs, this parameter is suggested to be configured as Yes. Controlling whether the multi-MNC handover decision is allowed. If "N" is selected, the multi-MNC handover decision will not be performed. The handover processing for the cell of the same MNC will be the same as that for the cell of a differen