RACH OPTMIZATION HW-Lte
RACH OPTMIZATION HW-Lte
All attributes related to Msg (1) [preambles, power, retrans) are received by the UE in SIB2
Optimize POWER :
PreambleInitRcvTargetPwr
PreambleTransMax
PwrRampingStep
To Improve Power
CellChPwrCfg. RaRspPwr
PDSchCfg.ReferenceSignalPwr
T300
ContentionResolutionTimer
Re-Trans
MaxHarqMsg3TX ---- Msg for contention
UlHarqMaxT --- Msg for Handover
Power :
DeltaPreambleMsg3
DeltaPreambleMsg2
CellUlPcDedic. DeltaMcsEnabled
The purpose of RACH resource adjustment is to match the allocated PRACH resources with the access load. Though the access load varies with time, RACH resource adjustment can be
used as long as the network load within a specified period meets the trigger condition.
The PRACH resource period is 10 ms. Namely, each radio frame carries one PRACH. The default configured PRACH resources may be insufficient. Therefore, RACH resource adjustment is
recommended when the number of contention-based random access attempts is greater than 50 per second.
The PRACH resource period is 5 ms. Namely, each radio frame carries two PRACHs. The default configured PRACH resources are sufficient. RACH resource adjustment is recommended
only when the number of contention-based random access attempts is less than 50 per second and the number of non-contention-based random access attempts is less than 30 per
second.
When the performance of the RACH resource adjustment function is not as expected or the network condition does not meet the requirement for enabling the RACH resource
adjustment function, you are advised to disable this function. When the status of the RachAdjSwitch option of the RachAlgoSwitch parameter is changed from being selected to being
deselected, the PRACH configuration index and preamble group change based on the following principles:
RACH Optimization Feature :
UE random access RACH algorithm switch CellAlgoSwitch.RachAlgoSwitch UeRaInforInqSwitch Select this option.
information query
E random access information query enables the eNodeB to send UE Information Request messages to UEs, requesting the
UEs to report their random access information. This information includes the collision flag and the number of preambles
sent in the last successfully completed random access procedure. This function requires that the UEs comply with 3GPP
Release 9 or later and support RACH information reporting.
Using the reported information as an input to RACH resource adjustment, the eNodeB accurately estimates the preamble
collision probability and converges the probability to the target value.
The UE random access information query function is controlled by the UeRaInforInqSwitch option of the
CellAlgoSwitch.RachAlgoSwitch parameter. This function is recommended when more than 80% of the UEs in a cell comply
with 3GPP release 9 or later and support RACH information reporting.
RACH Optimization Feature :
Function Parameter Name Parameter ID Option Setting Notes
If a UE does not send a preamble but the eNodeB detects a preamble from the UE during a random access
procedure, this falsely detected preamble is called a PRACH false alarm. If a received preamble is considered as a
PRACH false alarm, the eNodeB does not respond with a Random Access Response message or count the preamble
into the preamble-related counters.
RachPwrAdjSwitch
PRACH power control RACH algorithm switch CellAlgoSwitch.RachAlgoSwitch Select this option.
parameter adjustment
UeRaInforInqSwitch
The PRACH power control parameter adjustment function is controlled by the RachPwrAdjSwitch option of the
CellAlgoSwitch.RachAlgoSwitch parameter and requires the UE-reported random access information. Therefore, PRACH power control
parameter adjustment requires the UE random access information query function to be enabled.
When the status of the RachPwrAdjSwitch option is changed from being selected to being deselected, the
preambleInitialReceivedTargetPower and powerRampingStep fields revert to their configured values if their values are changed when the
option is selected. Otherwise, the preambleInitialReceivedTargetPower and powerRampingStep fields revert to their default values.
This function is recommended when both of the following conditions are met:
Most UEs in a cell support RACH information reporting.
The contention-based access load and non-contention-based access load are greater than 10 or the uplink PRB usage is greater than 50%.
This function is not recommended if it does not perform as expected or the network condition is not suitable for implementing this
function.
RACH Optimization Feature :
his function enables the eNodeB to accurately control the coverage scope of a cell by forbidding certain UEs, such as those beyond a country's border, from
accessing the cell. This function is recommended only when the coverage scope of a cell needs to be accurately controlled.
UE random access control based on cell radius is controlled by the ForbidAcByRadiusSwitch option under the CellAlgoSwitch.RachAlgoSwitch parameter.
The RrcSetupSuccRateByRadiusOptSw option of the CellCounterParaGroup.CellCounterAlgoSwitch parameter can be configured to control the method for
measuring the RRC connection setup success rate when this function is enabled. If this option is selected, the number of rejected RRC connection setup
requests of UEs initiating access beyond the cell radius is not taken into account for RRC connection setup success rate measurements. If this option is
deselected, the number is taken into account for the measurements.
When the software version is upgraded, the RrcSetupSuccRateByRadiusOptSw option of the CellCounterParaGroup.CellCounterAlgoSwitch parameter is set as
follows:
RACH Optimization Feature :
The following principles are recommended for determining the PRACH frequency-domain position:
The RACHCfg.PrachFreqOffset parameter is recommended when both of the following conditions are met:
The PRACH experiences strong interference and the interference is steady during a certain period.
Within the system bandwidth, interference on at least six PRBs used by the PUSCH is at least 5 dB lower than that on the
PRACH.
RACH Optimization Feature :
PRACH root sequence Root Sequence Conflict Detect Switch ENodeBAlgoSwitch.RootSeqConflictDetSwitch Set this parameter to ON.
conflict detection
he PRACH root sequence conflict detection function enables the eNodeB to detect root sequence conflicts between the serving cell and inter-eNodeB or
intra-eNodeB neighboring cells over the X2 interface and notifies UEs of information about root sequence conflicts, if any.
The eNodeB detects PRACH root sequence conflicts based on the following principles:
When PRACH root sequence conflict detection is enabled, the eNodeB determines that a root sequence conflict occurs and reports ALM-26247
Configuration Failure if both of the following conditions are met:
The PRACH time-frequency resources of the serving cell overlap with those of neighboring cells.
Some or all root sequences used by the serving cell are the same as those used by neighboring cells.
When this function is disabled, the eNodeB determines that the root sequence conflict disappears. Then, ALM-26247 Configuration Failure is cleared.
This function is controlled by the ENodeBAlgoSwitch.RootSeqConflictDetSwitch parameter.
This function is enabled when the false alarm probability of a cell is greater than expected and no root sequence conflict check has been performed.
It is recommended that this function be disabled to decrease the eNodeB CPU usage after the root sequence conflict is eliminated.
When a UE sends a preamble in the serving cell in which the root sequence conflicts with that in a neighboring cell, ALM-26247 Configuration Failure is
reported even if the preamble has no impact on the neighboring cell. In this case, it is recommended that this function be disabled.
RACH Optimization Feature :
flow control-based High Load Network Optimized Switch ENodeBAlgoSwitch.HighLoadNetOpt FlowCtrlTriBackoffSwitch Select this option.
backoff Switch
The eNodeB adjusts the backoff index based on statistics on Msg3 flow control collected every second, as shown in
Table 5-2.
Table 5-2 Flow control-based backoff index adjustment principles
It is recommended that this function be enabled in heavy-load scenarios, for example, the CPU usage of the BBP or
main control board is greater than 75%.
RACH Optimization Feature :
Function Parameter Name Parameter ID Option Setting Notes
detection of
contention-based RACH algorithm switch CellAlgoSwitch.RachAlgoSwitc ExceedRadiusRaDetectionSw Select this option.
random access h
beyond cell radius
Detection of contention-based random access beyond cell radius is controlled by the ExceedRadiusRaDetectionSw option
of the CellAlgoSwitch.RachAlgoSwitch parameter.
It is recommended that this function be enabled during off-peak hours when the contention-based random access success
rate in a cell is lower than expected. This function takes effect only when all of the following conditions are met:
The cell is a normal low-speed cell.
The distance between the UE and the eNodeB is greater than the cell radius and is less than twice the cell radius.
The distance between the UE and the eNodeB is less than or equal to 100 km.
RACH Optimization Feature :
Function Parameter Name Parameter ID Option Setting Notes
optimization of non-
contention-based random RACH algorithm switch CellAlgoSwitch.RachAlgoSwitch NonContRaOptSwitch Select this option.
access beyond cell radius
Optimization of non-contention-based random access beyond cell radius is controlled by the NonContRaOptSwitch
option of the CellAlgoSwitch.RachAlgoSwitch parameter.
This function is recommended during off-peak hours when the non-contention-based random access success rate in a
cell is lower than expected. This function takes effect only when all of the following conditions are met:
The cell is a normal low-speed cell.
The distance between the UE and the eNodeB is greater than the cell radius and is less than twice the cell radius.
The distance between the UE and the eNodeB is less than or equal to 100 km.
RACH Optimization Feature :
OPT Parameters
Parameter Name Parameter ID Setting Notes
UE random access control based Set this parameter based on the For cell radius R ≤ 14.5, the
Cell radius Cell.CellRadius
on cell radius expected cell radius. Preamble format is (0)
KPI for Monitoring: