PRACH

3/1/23, 2:00 PM HedEx Startpage
eRAN FDD Feature Documentation

Product Version: eRAN16.1
Library Version: 02
Date: 2020-05-21
For any question, please contact us.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
Random Access Control

Contents
4.2.2 Random Access Control
eRAN
Random Access Control Feature
Parameter Description
Issue 01
Date 2020-03-30
127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 1/41

HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei
Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the
products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise
specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to
ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any
kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
2.2 Contents
1 Change History
1.1 eRAN16.1 01 (2020-03-30)
1.2 eRAN16.1 Draft A (2020-01-20)
2 About This Document

2.1 General Statements
2.2 Applicable RAT
2.3 Features in This Document
3 Overview
4 Random Access
4.1 Principles
4.1.1 Preambles
4.1.1.1 Overview
4.1.1.2 Preamble Sequence Generation
4.1.1.3 Preamble Sequence Grouping
4.1.2 Random Access Procedures
4.1.2.1 Contention-based Random Access Procedure
4.1.2.2 Non-Contention-based Random Access Procedure
4.1.3 Random Access Time-Frequency Resource Configuration
4.1.3.1 Preamble Transmission Time
4.1.3.2 Preamble Transmission Frequency-Domain Position
4.1.4 Random Access Backoff
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Others
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the MAE-Deployment
4.4.2 Activation Verification

4.4.3 Network Monitoring
5 RACH Optimization
5.1 Principles
5.1.1 RACH Resource Adjustment
5.1.2 UE Random Access Information Query
5.1.3 PRACH False Alarm Detection
5.1.4 PRACH Power Control Parameter Adjustment
5.1.5 UE Random Access Control Based on Cell Radius
5.1.6 PRACH Frequency-Domain Position Adjustment
5.1.7 PRACH Root Sequence Conflict Detection
5.1.8 Flow Control-based Backoff
5.1.9 Detection of Contention-based Random Access Beyond Cell Radius
5.1.10 Optimization of Non-Contention-based Random Access Beyond Cell Radius
5.2 Network Analysis
5.2.1 Benefits
5.2.2 Impacts
5.3 Requirements
5.3.1 Licenses
5.3.2 Software
5.3.3 Hardware
5.3.4 Others
5.4 Operation and Maintenance
6 Parameters
7 Counters
8 Glossary
9 Reference Documents
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and "Reference Documents" chapters.
These changes include:
Technical changes
Changes in functions and their corresponding parameters
Editorial changes
Improvements or revisions to the documentation
eRAN16.1 01 (2020-03-30)
This issue does not include any changes.
eRAN16.1 Draft A (2020-01-20)

This issue introduces the following changes to eRAN15.1 02 (2019-07-20).
chnical Changes
Change Description Parameter Change RAT Base Station Model
Changed the name of U2020 to None FDD 3900 and 5900

MAE-Access and that of CME to series base
MAE-Deployment. stations
DBS3900
LampSite and
DBS5900
LampSite
itorial Changes
Revised descriptions in this document.
2 About This Document
General Statements
rpose
This document is intended to acquaint readers with:
The technical principles of features and their related parameters

The scenarios where these features are used, the benefits they provide, and the impact they have on networks and
functions
Requirements of the operating environment that must be met before feature activation
Parameter configuration required for feature activation, verification of feature activation, and monitoring of feature
performance
This document only provides guidance for feature activation. Feature deployment and feature gains depend on the specifics
of the network scenario where the feature is deployed. To achieve the desired gains, contact Huawei professional service
engineers.
ftware Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product documentation.
Applicable RAT
This document applies to FDD.
Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LBFD-002010 Random Access 4 Random Access
LOFD-002015 RACH Optimization 5 RACH Optimization

3 Overview
ndom Access
Random access is crucial for LTE systems. During random access, uplink synchronization is set up or restored between eNodeBs
and UEs.
Random access is classified into contention-based and non-contention-based random access.
In contention-based random access, UEs may fail to access the network.

In non-contention-based random access, the eNodeB allocates dedicated random access channel (RACH) resources to
UEs for network access. If the dedicated RACH resources are insufficient for a UE, the eNodeB instructs the UE to initiate
contention-based random access.
ACH Optimization
RACH optimization helps decrease the network access delay of all UEs and mitigate uplink interference caused by physical random
access channels (PRACHs). RACH optimization includes the following functions:
RACH resource adjustment

UE random access information query
PRACH false alarm detection
PRACH power control parameter adjustment
UE random access control based on cell radius
PRACH frequency-domain position adjustment
PRACH root sequence conflict detection
Flow control-based backoff
Detection of contention-based random access beyond cell radius
Optimization of non-contention-based random access beyond cell radius
4 Random Access
Principles
Random access is performed before a UE begins to communicate with the network. During random access, the UE sends an
access request to the eNodeB, and then the eNodeB responds to the request and allocates a RACH. During the process, the UE
obtains uplink synchronization signals from the network and requests dedicated resources for data transmissions.
The following table describes the random access trigger scenarios and random access mechanisms.
Trigger Scenario Description Random Access

Mechanism
Initial RRC connection A UE initiates random access if it wants to switch from the RRC_IDLE Contention-based
setup state to the RRC_CONNECTED state. random access
RRC connection When a radio link failure (RLF) occurs, the UE needs to reestablish an
reestablishment RRC connection. In this scenario, the UE initiates random access.
Uplink data arrival When a UE that is in the RRC_CONNECTED state but has lost uplink Contention-based
synchronization needs to send uplink data to an eNodeB, the UE random access
initiates random access.

Trigger Scenario Description Random Access

Mechanism
Handover During a handover, a UE initiates random access in the target cell. Non-contention-based
random access, and
Downlink data arrival When an eNodeB needs to send downlink data to a UE in the contention-based
RRC_CONNECTED state and finds that the UE is out of uplink random access which
synchronization, the eNodeB instructs the UE to initiate random applies when
access. dedicated preambles
are used up
Location service For details, see LCS. Non-contention-based

(LCS) initiation random access
Random access is categorized into the following types:
Contention-based random access: Preambles are generated by UEs, and conflicts may exist among these preambles. The
eNodeB uses a contention resolution mechanism to handle such conflicts.
Non-contention-based random access: Preambles are allocated by the eNodeB, and each preamble is dedicated to only
one UE. Therefore, there is no preamble conflict.
For details about the random access trigger scenarios, contention-based random access, and non-contention-based random
access, see section 10.1.5 "Random Access Procedure" in 3GPP TS 36.300 V10.3.1.
4.1.1 Preambles
4.1.1.1 Overview
During system information delivery, the eNodeB sends the preamble configuration information to a UE. Based on the received
preamble configuration, the UE initiates random access by sending a preamble to the eNodeB. The preamble is a burst, which
consists of a TCP and a TSEQ in the time domain and six resource blocks in the frequency domain, as shown in Figure 4-1. TCP
indicates the time length of the cyclic prefix, TSEQ indicates the time length of the preamble sequence, and TGT indicates the guard
interval.
Figure 4-1 Preamble format
There are five preamble formats corresponding to different cell radii. The preamble format is specified by the Cell.PreambleFmt
parameter, and the cell radius is specified by the Cell.CellRadius parameter.
Table 4-1 describes the relationship between preamble formats and TCP, TSEQ, and recommended cell radius ranges. If the
configured cell radius exceeds the maximum cell radius supported by the preamble format, the eNodeB may fail to accurately
detect the preambles sent by a UE when the UE initiates a random access request beyond the maximum cell radius.
Table 4-1 Preamble formats
Preamble Format Burst (µs) TCP (µs) TSEQ (µs) Cell Radius (km)
0 1000 103.1 800 R ≤ 14.5
1 2000 684.4 800 R ≤ 77.3
2 2000 203.1 1600 R ≤ 29.5
3 3000 684.4 1600 R ≤ 100
4.1.1.2 Preamble Sequence Generation

Preamble sequences are generated through cyclic shifts of Zadoff-Chu (ZC) root sequences.
The logical ZC root sequence index is specified by the Cell.RootSequenceIdx parameter and cyclically ranges from 0 to 837.
That is, logical index 0 is consecutive to index 837.
The number of cyclic shifts is determined by the eNodeB based on the cell type and cell radius.
Each cell can be configured with a maximum of 64 preamble sequences. The number of preamble sequences generated from a
single ZC sequence depends on the cell radius and cell type. For details, see section 5.7.2 in 3GPP TS 36.211 V10.3.1. If fewer
than 64 preamble sequences are generated from a single ZC sequence, subsequent ZC sequences are used until 64 preamble
sequences are generated.
The logical ZC sequence index and the number of cyclic shifts are signaled by the prach-ConfigIndex IE in SIB2.
For details about preamble sequence generation, see section 5.7.2 "Preamble sequence generation" in 3GPP TS 36.211 V10.3.1.
4.1.1.3 Preamble Sequence Grouping

Based on the contention mechanism used during random access, preambles are grouped for UE selection. Figure 4-2 shows the
preamble sequence grouping principles.
Figure 4-2 Example of preamble sequence grouping
The total number of random preamble sequences and the number of random preamble sequences in group A are calculated using
the RACHCfg.RandomPreambleRatio and RACHCfg.RaPreambleGrpARatio parameters.
Number of random preamble sequences = 4 x ROUNDDOWN(Total number of preamble sequences in a cell x Value of
RandomPreambleRatio/4)
Number of random preamble sequences in group A = 4 x ROUNDUP(Total number of random preamble sequences x Value
of RaPreambleGrpARatio/4)
For example: ROUNDDOWN(3.6) = 3, ROUNDUP(3.1) = 4

All the PRACH time-frequency resources in a cell use the same group configuration mode. Grouping information is delivered in
broadcast messages.
The eNodeB periodically collects statistics on the allocation of dedicated preamble sequences to UEs during non-contention-based
random access and checks for random preamble collisions during contention-based random access. Based on the statistics, the
eNodeB adjusts the dedicated preamble group and random preamble group.
When the next system information update interval arrives, the number of random preamble sequences and the number of random
preamble sequences in group A are updated using broadcast messages if the number of preamble sequences changes.
4.1.2 Random Access Procedures

The contention-based random access procedure slightly differs from the non-contention-based random access procedure. For
details about random access procedures, see section 5.1 "Random Access procedure" in 3GPP TS 36.321 V10.3.1.
4.1.2.1 Contention-based Random Access Procedure

Figure 4-3 shows the contention-based random access procedure.

Figure 4-3 Contention-based random access procedure
ndom Preamble Transmission
Figure 4-4 shows the random preamble transmission procedure of the UE during contention-based random access.
Figure 4-4 Random access preamble transmission procedure
Steps 3 and 5 in the preceding figure are described as follows:
In step 3, the UE selects random preamble group B only if all of the following conditions are met:
Random preamble group B exists.
The size of Msg3 is larger than the threshold specified by the RACHCfg.MessageSizeGroupA parameter.
The path loss of the UE is less than the threshold defined in 3GPP specifications. For details about the threshold,
see section 5.1.2 "Random Access Resource selection" in 3GPP TS 36.321 V10.3.1.
For details about how to calculate PPRACH in step 5, see Power Control.
ndom Access Response
Upon receiving the preamble, the eNodeB applies for a temporary cell radio network temporary identifier (C-RNTI) and uplink and
downlink scheduling resources. Then, the eNodeB sends a random access response over the downlink shared channel (DL-SCH)
for each UE. The response contains the RA-preamble identifier, timing alignment information, initial uplink grant, and temporary C-
RNTI. One DL-SCH can carry random access responses to multiple UEs.

After the UE sends the preamble, it monitors the physical dedicated control channel (PDCCH) and waits for a random access
response within a random access response window:
If the UE receives a response containing an RA-preamble identifier which is the same as the identifier contained in the
transmitted random access preamble, the response is successful. The UE then transmits uplink scheduling information.
If the UE does not receive a response within the random access response window or fails to verify the response, the
response fails. In this case, if the number of random access attempts is smaller than the upper limit, the UE retries random
access. Otherwise, random access fails. The maximum number of random access attempts of the UE is specified by the
RACHCfg.preambleTransMax parameter and can be obtained from SIB2.
plink Scheduling Information Transmission
After receiving a successful response, the UE sends scheduled uplink transport blocks over the uplink shared channel (UL-SCH).
The size of each transport block is specified in the preamble and is not smaller than 80 bits. The information in the transport block
sent by the UE varies in different random access scenarios:
Initial RRC connection setup

The RRC Connection Request message (including NAS UE_ID) is transmitted over the CCCH in TM at the RLC layer. The
message is not segmented.
RRC connection reestablishment
The RRC Connection Reestablishment Request message (excluding NAS information) is transmitted in TM at the RLC layer.
The message is not segmented.
Handover
Contention-based random access is triggered if the UE accesses the network from the target cell and no dedicated
preambles are available during a handover.
The RRC Handover Confirm message and C-RNTI are transmitted over the DCCH. If required, a buffer status report (BSR)
is also carried.
Other scenarios
At least the C-RNTI of the UE is transmitted.
ontention Resolution
After the UE sends Msg3 (indicated as scheduled transmission in step 3 in Figure 4-3), a contention resolution timer starts. The
contention resolution timer is specified by the RACHCfg.ContentionResolutionTimer parameter and can be obtained from SIB2.
Within the timer length, the eNodeB performs contention resolution at the MAC layer and informs the UE of the resolution through
the C-RNTI on the PDCCH or through the UE Contention Resolution Identity IE on the DL-SCH.
The UE monitors the PDCCH before the timer expires. The UE considers the contention resolution as successful, notifies upper
layers, and stops the timer if both of the following conditions are met:
The UE obtains the C-RNTI from the PDCCH.

The UE obtains the temporary C-RNTI over the PDCCH, the MAC packet data unit (PDU) is successfully decoded, and the
MAC PDU contains information matching the CCCH service data unit (SDU) transmitted in Msg3.
If the contention resolution is successful, the contention-based random access procedure is complete. If the contention resolution
timer expires, the UE considers the contention resolution as failed. In this case, if the number of random access attempts is smaller
than the upper limit, the UE retries random access. Otherwise, random access fails.
4.1.2.2 Non-Contention-based Random Access Procedure

Figure 4-5 shows the non-contention-based random access procedure. Unlike contention-based random access, non-contention-
based random access does not involve contention and conflict resolution because random access preambles are allocated by the
eNodeB. Other operations in non-contention-based random access are similar to those in contention-based random access.

Figure 4-5 Non-contention-based random access procedure
The non-contention-based random access procedure is as follows:
1. The eNodeB allocates dedicated preambles to UEs through dedicated signaling.

In handover scenarios, a MobilityControlInfo message sent by the source eNodeB carries the preamble.
In downlink data arrival scenarios, a signaling message at the MAC layer carries the preamble.
2. The UE sends the preamble over the PRACH.

3. The eNodeB sends a random access response over the DL-SCH.
In handover scenarios, the random access response contains at least the timing alignment information and initial
uplink grant.
In downlink data arrival or LCS scenarios, the random access response contains at least the timing alignment
information and RA-preamble identifier.
When the response is successful, the non-contention-based random access procedure is complete.
4.1.3 Random Access Time-Frequency Resource Configuration
4.1.3.1 Preamble Transmission Time

During contention-based random access, the UE reads the prach-ConfigIndex IE in SIB2 to obtain the PRACH start time in each
radio frame. In this way, the UE determines the PRACH resource period. For details, see section 5.7.1 in 3GPP TS 36.211 V10.3.1.
In FDD, the default PRACH resource period is 5 ms when the cell bandwidth is 15 MHz or 20 MHz. The default PRACH
resource period is 10 ms when the cell bandwidth is less than or equal to 10 MHz.
The prach-ConfigIndex IE is specified by the RACHCfg.PrachConfigIndex parameter and needs to be configured based on factors
such as the cell bandwidth and average access delay.
The prach-ConfigIndex IE equals the value of the RACHCfg.PrachConfigIndex parameter when the
RACHCfg.PrachConfigIndexCfgInd parameter is set to CFG.
The RACHCfg.PrachConfigIndex parameter does not take effect when the RACHCfg.PrachConfigIndexCfgInd parameter is
set to NOT_CFG. For FDD, the eNodeB specifies the prach-ConfigIndex IE based on the principles described in Table 4-2
and Table 4-3.
Table 4-2 Typical default values of the prach-ConfigIndex IE when the LBBPc board is used

Value of the HighSpeedFlag Preamble Format Bandwidth (MHz) Typical Default Value of the prach-
Parameter ConfigIndex IE
LOW_SPEED 0 15 or 20 6, 7, or 8
0 5 or 10 3, 4, or 5
0 1.4 or 3 Synchronized: 0, 1, or 2
Non-synchronized: 3, 4, or 5
1 15 or 20 19, 20, or 21 (cell radius > 16 km)

22, 24, or 23 (cell radius ≤ 16 km)
1 5 or 10 19, 20, or 21

2 5, 10, 15, or 20 35, 36, or 37

3 5, 10, 15, or 20 51, 52, or 53

HIGH_SPEED 0 5, 10, 15, or 20 3, 4, or 5

ULTRA_HIGH_SPEED
1 5, 10, 15, or 20 19, 20, or 21

2 5, 10, 15, or 20 35, 36, or 37

3 5, 10, 15, or 20 51, 52, or 53

Table 4-3 Typical default values of the prach-ConfigIndex IE when a baseband processing unit (BBP) other than
the LBBPc board is used

LOW_SPEED 0 15 or 20 6
HIGH_SPEED
0 5 or 10 3
0 1.4 or 3 Synchronized: 0
Non-synchronized: 3
1 5, 10, 15, or 20 19
Non-synchronized: 19
2 5, 10, 15, or 20 35
3 5, 10, 15, or 20 51
ULTRA_HIGH_SPEED 0 5, 10, 15, or 20 3
Non-synchronized: 3
1 5, 10, 15, or 20 19
2 5, 10, 15, or 20 35
3 5, 10, 15, or 20 51
When an LBBPc board is used for FDD, PRACH positions are staggered between the cells set up on the eNodeB in the time
domain by default. When a BBP other than the LBBPc board is used, the time-domain PRACH position staggering function is
controlled by the ENodeBAlgoSwitch.PrachTimeStagSwitch parameter. When this parameter is set to ON:
The prach-ConfigIndex IE equals the value of the RACHCfg.PrachConfigIndex parameter when the
RACHCfg.PrachConfigIndexCfgInd parameter is set to CFG.
When the RACHCfg.PrachConfigIndexCfgInd parameter is set to NOT_CFG, the prach-ConfigIndex IE uses the typical
default values listed in Table 4-4.
Table 4-4 Typical default values of the prach-ConfigIndex IE

LOW_SPEED 0 15 or 20 6, 7, or 8
HIGH_SPEED
0 5 or 10 3, 4, or 5
1 5, 10, 15, or 20 19, 20, or 21

2 5, 10, 15, or 20 35, 36, or 37

3 5, 10, 15, or 20 51, 52, or 53

ULTRA_HIGH_SPEED 0 5, 10, 15, or 20 3, 4, or 5
1 5, 10, 15, or 20 19, 20, or 21

2 5, 10, 15, or 20 35, 36, or 37

3 5, 10, 15, or 20 51, 52, or 53

"Synchronized" in the preceding tables indicates that the absolute time difference between frames with the same system
frame number (SFN) of adjacent cells is less than 5 ms. "Non-synchronized" indicates that the absolute time difference is
greater than or equal to 5 ms.
The prach-ConfigurationIndex IE has only three recommended initial values. These values are cyclically used when there
are more than three cells.
It is recommended that the PrachTimeStagSwitch parameter be set to ON when six 4R cells are set up on an LBBPd and the Uu-
based soft synchronization function is enabled.
4.1.3.2 Preamble Transmission Frequency-Domain Position

The PRACH frequency-domain position is determined using any of the following methods:
Based on the setting of the RACHCfg.PrachFreqOffset parameter. This method will reactivate the cell to make the
configuration take effect.
If the manually configured PRACH frequency-domain position conflicts with the PUCCH frequency-domain position, the cell
reactivation will fail. Considering the PUCCH resource expansion in different scenarios, the proper value range of the
PrachFreqOffset parameter is listed in Table 4-5. "MaxRbNum" indicates the maximum number of RBs for the
corresponding bandwidth. Preamble format 4 is suitable only for LTE TDD, and the PRACH frequency-domain position is
non-configurable.
Table 4-5 Proper value range of the PrachFreqOffset parameter
Board Type Bandwidth (MHz) Value Range
LBBPd or UBBP 10, 15, or 20 15 to (MaxRbNum – 20)
5 8 to 12
LBBPc 10, 15, or 20 14 to (MaxRbNum – 19)
5 5 to 15
Based on the maximum number of RBs used for PUCCH transmission

Through adaptation of the number of RBs used by the PUCCH. For details, see 5.1.6 PRACH Frequency-Domain Position
Adjustment.
4.1.4 Random Access Backoff

The RACH does not interfere with other uplink channels in LTE. In most cases, preamble collisions occur at a low probability. If
there are excessively many UEs on a PRACH, preamble collisions may occur, leading to random access failures. To minimize the
probability of preamble collisions, random access backoff is introduced to control the time for preamble retransmission.
If random access backoff is enabled, the eNodeB notifies a UE of a backoff index using a random access response message.
When the UE needs to retransmit a preamble, it randomly selects a value between 0 and the received backoff index as the backoff
time (corresponding to the subframe position in the time domain). The UE can retransmit the preamble only after the backoff time
expires. Figure 4-6 shows the backoff mechanism.
Figure 4-6 Backoff mechanism
Random access backoff is not performed in either of the following scenarios:
Initial preamble transmission

Preamble retransmission during non-contention-based random access
Network Analysis
4.2.1 Benefits
Random access is a basic function and plays an important role in an LTE system. Random access is the only way for a UE to
establish and restore uplink synchronization with the eNodeB. It is also the basis for a UE to access the network and set up service
bearers.
4.2.2 Impacts
twork Impacts
None
nction Impacts
RAT Function Function Switch Reference Description

Name
FDD Static shared None Massive MIMO It is recommended that the

beam (SSB) (FDD) Cell.PreambleFmt parameter be set
to 0 in massive MIMO scenarios.

RAT Function Function Switch Reference Description

Name
FDD Dynamic None Massive MIMO It is recommended that the

dedicated (FDD) Cell.PreambleFmt parameter be set
beam (DDB) to 0 in massive MIMO scenarios.
FDD Intelligent The Massive MIMO It is recommended that the

beam MM_INTELLIGENT_BEAM_SHAPING_SW (FDD) Cell.PreambleFmt parameter be set
shaping option of the to 0 in massive MIMO scenarios.
SectorSplitGroup.SectorSplitSwitch
parameter
FDD In-band relay InBandRelayDeNbSwitch and Relay The PRACH subframes may
InBandRelayReNbSwitch options of the conflict with backhaul subframes,
CellAlgoSwitch.RelaySwitch parameter affecting UE access. For ReBTS
cells, only some subframes are
used for UE access and only a
few subframes are available for
PRACH configuration.
For FDD, the recommended
values of the PRACH
configuration index are as follows:
Preamble format 0: 1, 4, 8, or 15
Preamble format 1: 17, 20, 24, or
31
47
63
Requirements
4.3.1 Licenses
There are no FDD license requirements.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and mutually exclusive functions have
been deactivated. For detailed operations, see the relevant feature documents.
erequisite Functions
RAT Function Name Function Switch Reference
FDD System information Sib6Switch and Idle Mode Management

broadcast Sib7Switch options of
the
CellSiMap.SiSwitch
parameter
FDD Cell selection and None Idle Mode Management

reselection
utually Exclusive Functions
None
4.3.3 Hardware
se Station Models
No requirements
oards

No requirements
F Modules
No requirements
4.3.4 Others
None
Operation and Maintenance

Random access is a basic feature for LTE and is activated without requiring any specific parameter setting. Table 4-6 describes the
parameters used for optimization.
Table 4-6 Parameters used for optimization
Parameter Name Parameter ID Option Setting Notes
Maximum number RACHCfg.PreambleTransMax None The value N10_PREMB_TRANS_MAX

of preamble is recommended. Set this parameter
transmission based on the network plan.
Maximum number RACHCfg.MaxHarqMsg3Tx None The value 5 is recommended. Set this

of Msg3 HARQ parameter based on the network plan.
transmissions
Timer for RACHCfg.ContentionResolutionTimer None Set this parameter based on the

contention network plan.
resolution
Indication of RACHCfg.PrachConfigIndexCfgInd None Set this parameter to NOT_CFG.

PRACH
Configuration
Index
PRACH Frequency RACHCfg.PrachFreqOffsetStrategy None Set this parameter to AUTOMATIC.

Offset Strategy
PUCCH algorithm CellAlgoSwitch.PucchAlgoSwitch PucchSwitch Deselect this option in ultra-high-

switch speed scenarios.
Select this option in other
scenarios.
//Configuring the maximum number of preamble transmissions, timer for contenstion resolution, and
maximum number of Msg3 HARQ transmissions based on the network plan
MOD RACHCFG: LocalCellId=0, PreambleTransMax=N10_PREMB_TRANS_MAX,
ContentionResolutionTimer=SF64_MAC_RESOLUTION_TIMER, MaxHarqMsg3Tx=5;

For detailed operations, see Feature Configuration Using the MAE-Deployment.
1. Start a performance counter tracing task on the MAE-Access.

2. Use a UE to access the network.
3. Check the measured values of the counters related to preamble group A or B after a measurement period expires.
Random access is enabled if any of them increases.
Counters related to preamble group A
L.RA.GrpA.Att
L.RA.GrpA.ContResolution
L.RA.GrpA.Resp
Counters related to preamble group B
L.RA.GrpB.Att
L.RA.GrpB.ContResolution
L.RA.GrpB.Resp

The random access load and performance can be monitored using counters.
Table 4-7 Monitoring items and their expected values
Feature/Function Monitored Item Calculation Formula
Random access Contention-based (L.RA.GrpA.Att + L.RA.GrpB.Att)/Monitoring time (s)

access loada
Random access Non-contention-based L.RA.Dedicate.PreambleReq.Num/Monitoring time (s)

access loadb
a: The contention-based access load denotes the number of contention-based random access attempts per second.
b: The non-contention-based load denotes the number of dedicated random access attempts per second.
Table 4-8 Performance counters related to random preambles
Counter ID Counter Name Counter Description
1526727215 L.RA.GrpA.Att Number of times the contention preamble in

group A is received
1526727217 L.RA.GrpA.ContResolution Number of times a cell sends a Contention

Resolution message after receiving a
preamble in group A
1526727218 L.RA.GrpB.Att Number of times the contention preamble in

group B is received
1526727220 L.RA.GrpB.ContResolution Number of times a cell sends a Contention

preamble in group B
1526727216 L.RA.GrpA.Resp Number of times a cell sends a Random

Access Response message after receiving a
preamble in group A
1526727219 L.RA.GrpB.Resp Number of times a cell sends a Random

Access Response message after receiving a
preamble in group B
Table 4-9 Performance counter related to dedicated preambles
1526728937 L.RA.Dedicate.PreambleReq.Num Number of times the non-contention-based

preamble is requested
5 RACH Optimization

Principles
5.1.1 RACH Resource Adjustment

RACH resources are configured semi-statically. When the traffic model changes, RACH resources may fail to accommodate the
RACH load. In this situation, RACH resources need to be adjusted. RACH resource adjustment is also required in the following
situations:
When the number of handover attempts increases, dedicated preambles may be insufficient and UEs can initiate only
contention-based random access, which increases the handover delay.
When the number of random access attempts increases, random preambles or PRACH resources may be insufficient and
the probability of preamble collisions increases on PRACHs, which increases the network access delay.
The eNodeB adaptively adjusts the PRACH configuration index and preamble groups based on the RACH load in a cell so that the
number of each type of preambles and the number of PRACHs per second adapt to the traffic model.
justment Principles
RACH resource adjustment includes the following:
PRACH configuration index (specified by the RACHCfg.PrachConfigIndex parameter) adjustment: preamble format, and the
frame and subframe numbers of each PRACH are involved, which are used to adjust the PRACH period.
Preamble grouping: Proportions of random access preamble sequences and dedicated preamble sequences are
determined.
Figure 5-1 and Table 5-1 describe the PRACH configuration index adjustment principles.
Figure 5-1 PRACH configuration index adjustment principles
Table 5-1 PRACH configuration index adjustment principles
Scenario Adjustment Principle
Both the dedicated preambles and random preambles are The eNodeB decreases the PRACH configuration index.
redundant and the uplink PRB usage is high.
Random preambles are insufficient. The eNodeB increases the PRACH configuration index.
The eNodeB determines whether dedicated preambles are redundant based on the number of unused dedicated preambles
detected within a period of time.
The eNodeB determines whether random preambles are redundant or insufficient based on the following principles:
When the UE random access information query function is enabled, the eNodeB determines whether preambles are
redundant based on the random access information reported by the UE. For details about the UE random access
information query function, see 5.1.2 UE Random Access Information Query.
When the function is disabled, the eNodeB determines whether preambles are insufficient based on the number of
preambles detected within a specified period of time.
The eNodeB determines whether the uplink PRB usage is high based on the actual PRB usage in the uplink.

When both of the UlSwitch and UlLdcSwitch options of the CellAlgoSwitch.RacAlgoSwitch parameter are deselected, the
eNodeB decreases the PRACH configuration index if both dedicated preambles and random preambles are redundant,
regardless of whether the uplink PRB usage is high.
Figure 5-2 shows the preamble group adjustment principles.
Figure 5-2 Preamble group adjustment principles
The eNodeB adjusts the number of preambles based on the following principles:
If dedicated preambles are redundant and random preambles are insufficient, the eNodeB reduces the number of
dedicated preambles.
If dedicated preambles are insufficient, the eNodeB increases the number of dedicated preambles.
The eNodeB determines whether dedicated preambles are sufficient based on the dedicated-preamble allocation failure
rate. The dedicated-preamble allocation failure rate is calculated using the following formula:
Dedicated-preamble allocation failure rate = 1 – Number of UEs that are allocated dedicated preambles/Number of UEs that
apply for dedicated preambles
If PRACH configuration indexes or preamble groups change, the eNodeB broadcasts the new configuration to UEs using SIB2 and
then the UEs use the new configuration.
tting Notes
The RachAdjSwitch option of the CellAlgoSwitch.RachAlgoSwitch parameter specifies whether to enable the RACH resource
adjustment function. The RACH resource adjustment function takes effect only when this option is selected and the
RACHCfg.PrachConfigIndexCfgInd parameter is set to NOT_CFG.
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:
The RACH resource adjustment function does not take effect and the PRACH configuration index specified by the
RACHCfg.PrachConfigIndex parameter remains unchanged if the RACHCfg.PrachConfigIndexCfgInd parameter is set to
CFG.
The RACHCFG.PrachConfigIndex parameter returns to the default setting if the RACHCfg.PrachConfigIndexCfgInd
parameter is set to NOT_CFG.
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.
5.1.2 UE Random Access Information Query

UE 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.
5.1.3 PRACH False Alarm Detection

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.
This function is controlled by the PrachFalseAlarmDetSwitch option of the CellAlgoSwitch.RachAlgoSwitch parameter, and is
recommended when the probability of PRACH false alarms is greater than expected.
Figure 5-3 shows the PRACH false alarm detection decision mechanism.
Figure 5-3 PRACH false alarm detection decision mechanism
It is recommended that this function be used with the CellRachAlgo.PrachFalseAlarmDetRadThd and

CellRachAlgo.RachThdBoostRatio parameters.
To support UEs with a 40 ms preamble retransmission period, the function of identifying preambles that support 40 ms
retransmission is added to the eNodeB and is controlled by the PRACHFalseAlaDetRetxOptSwitch option of the
CellAlgoSwitch.RachAlgoSwitch parameter.
Huawei eNodeBs detect the following false alarms:
False alarms defined in section 8.4.1.1 "Definition and applicability" of 3GPP TS 36.141 V10.4.0
Preambles transmitted after UEs fail to receive Msg2
Preambles transmitted after eNodeBs fail to receive Msg3
Preambles transmitted after eNodeBs receive Msg3 but do not send Msg4 during flow control
5.1.4 PRACH Power Control Parameter Adjustment

This function enables an eNodeB to adjust PRACH power control field settings based on the random access information reported
by the UEs. These fields include preambleInitialReceivedTargetPower and powerRampingStep. For details, see "RACH-
ConfigCommon" in section 6.3.2 "Radio resource control information elements" in 3GPP TS 36.331 V10.3.0.
The eNodeB adjusts PRACH power control parameters as follows:
1. Calculates the access probability AP(m) based on the UE-reported random access information, including the number of
preamble transmissions and contention-based random access conflict identification.
AP(m) = M/N
m: number of preamble transmissions
M: number of random accesses for m preamble transmissions
N: number of times that the UE reports RACH information
2. Adjusts PRACH power control parameters based on the target value and expected range of AP(m). The parameters to be
adjusted include RACHCfg.PreambInitRcvTargetPwr and RACHCfg.PwrRampingStep.
3. Broadcasts the adjusted parameters using a SIB.
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.
5.1.5 UE Random Access Control Based on Cell Radius

This 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
This function is implemented as follows:
1. After receiving a random access preamble from a UE, the eNodeB calculates the distance between the UE and the
eNodeB based on the timing advance (TA) of the preamble.
The eNodeB measures the TA of a preamble after detecting the preamble.
2. When the distance from the eNodeB to the UE sending a preamble is greater than the cell radius specified by the
Cell.CellRadius parameter:
With this function, the eNodeB responds with an RRC connection reject message upon receiving an RRC
connection setup request from the UE, preventing the UE from accessing the network.
Without this function, the eNodeB does not respond with an RRC connection reject message upon receiving an
RRC connection setup request from the UE.
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:
For FDD cells, after an upgrade to eRAN15.1 SPC150 or later, the RrcSetupSuccRateByRadiusOptSw option is
deselected by default.
5.1.6 PRACH Frequency-Domain Position Adjustment

The PRACH frequency-domain position is determined using any of the following methods:
Based on the setting of the RACHCfg.PrachFreqOffset parameter

Based on the maximum number of RBs used for PUCCH transmission
Through adaptive adjustment based on the number of RBs used for PUCCH transmission
Figure 5-4 shows the principles for determining the PRACH frequency-domain position.

Figure 5-4 Methods of determining the PRACH frequency-domain position
When the PRACH frequency-domain position is determined based on the maximum number of RBs used by the PUCCH, the
PRACH frequency-domain position equals half of the maximum number of RBs used by the PUCCH, as shown in Figure 5-5. When
there are a small number of UEs and the number of RBs used by the PUCCH is less than the upper limit, PUSCH resources are
divided into two parts and cannot be used as a whole by a single UE.
With PRACH frequency-domain position adjustment, the eNodeB adjusts the PRACH frequency-domain position based on the
number of RBs used for PUCCH transmission so that the PRACH is adjacent to the PUCCH located at the low frequency band, as
shown in Figure 5-5, improving the PUSCH RB resource efficiency.
Figure 5-5 PRACH frequency-domain position adjustment
PRACH frequency-domain position adjustment is controlled by the PrachFreqAdjSwitch option of the

CellAlgoSwitch.RachAlgoSwitch parameter. This function takes effect only when the PucchSwitch option of the
CellAlgoSwitch.PucchAlgoSwitch parameter is selected and the RACHCfg.PrachFreqOffsetStrategy parameter is set to
AUTOMATIC or FULLY_AUTOMATIC.
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.
Interference on each PRB of the PRACH and PUSCH is measured using the ChMeas.Pwr1.Cell counter.
It is recommended that interference greater than –110 dBm on each PRB be considered strong interference.
PRACH frequency-domain position adjustment is recommended when a cell serves fewer than four activated UEs and the
PUSCH RB resources can be used up. When a cell serves four or more activated UEs or the PUSCH RB resources cannot
be used up, this function offers no gains in the uplink throughput.

The number of activated UEs is measured by the L.Traffic.ActiveUser.Avg counter.

If the following condition is met, activated UEs can use up PUSCH RB resources:
L.ChMeas.PRB.PUSCH.Util.Samp.Index9 > Max{L.ChMeas.PRB.PUSCH.Util.Samp.Index0,
L.ChMeas.PRB.PUSCH.Util.Samp.Index1, L.ChMeas.PRB.PUSCH.Util.Samp.Index2,
L.ChMeas.PRB.PUSCH.Util.Samp.Index7, L.ChMeas.PRB.PUSCH.Util.Samp.Index8}
In other cases, the system determines the PRACH frequency-domain position based on the maximum number of RBs used
by the PUCCH.
5.1.7 PRACH Root Sequence Conflict Detection

When two cells use the same PRACH root sequence, the probability of false alarms or preamble collisions increases, as shown in
Figure 5-6 and Figure 5-7.
Figure 5-6 Increase in the probability of false alarms
Figure 5-7 Increase in the probability of preamble collisions
The 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.
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, this alarm
can be ignored.
ALM-26247 Configuration Failure only indicates whether there is a root sequence conflict. To query the detailed information
about the root sequence conflict, run the DSP ROOTSEQCONFLICT command.

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.
5.1.8 Flow Control-based Backoff

This function enables the eNodeB to adjust the backoff index based on the Msg3 flow control result and the number of UEs in a cell
so that UEs retransmit preambles after a delay during contention-based random access. In this way, RACH congestion is relieved.
Msg3 flow control is implemented based on the following principles:
After receiving an RRC Connection Request message from a UE, the eNodeB sends an RRC Connection Reject message
to the UE or does not respond to the request.
After receiving an RRC Connection Reestablishment Request message from a UE, the eNodeB sends an RRC Connection
Reestablishment Reject message to the UE or does not respond to the request.
Figure 5-8 Msg3 flow control
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
Msg3 Flow Control Backoff Index

Adjustment
When both of the following conditions are met: The eNodeB

The result of dividing the flow-control Msg3 quantity by the received Msg3 quantity is increases the value of
greater than 5%. the backoff index.
The result of dividing the number of UEs in a cell by the maximum number of UEs in
the cell is greater than about 40%.
When either of the following conditions is met: The eNodeB

The flow-control Msg3 quantity is 0. decreases the value
of the backoff index.
The result of dividing the number of UEs in a cell by the maximum number of UEs in
the cell is less than or equal to about 40%.
Other conditions The eNodeB does not

change the value of
the backoff index.
This function is controlled by the FlowCtrlTriBackoffSwitch option of the ENodeBAlgoSwitch.HighLoadNetOptSwitch parameter.

After this function is enabled, any adjustment to backoff indexes will be recorded in the SON log.

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%.
5.1.9 Detection of Contention-based Random Access Beyond Cell Radius

This function can determine whether a UE that initiates contention-based access is located beyond the cell radius and allows its
access.
The detection procedure is as follows:
1. An eNodeB receives a random preamble that is a retransmission preamble, and detects preamble index N but not
preamble index N + 1.
2. The eNodeB delivers two RAR messages, which carry preamble indexes N and N + 1, respectively, to a UE.
3. The eNodeB receives an RRC connection establishment request from the UE. If the RAR message for this request carries
preamble index of N + 1, the eNodeB determines that the UE is beyond the cell radius.
4. The eNodeB stops the random access procedure and measures the access-related performance counters.
Detection of contention-based random access beyond cell radius is controlled by the ExceedRadiusRaDetectionSw option of the
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.
5.1.10 Optimization of Non-Contention-based Random Access Beyond Cell Radius

This function can optimize the procedure of non-contention-based random access initiated by a UE beyond the cell radius to ensure
the successful access.
The optimized procedure is as follows:
An eNodeB receives a dedicated preamble that is a retransmission preamble, and both of the following conditions are met:
The eNodeB detects that preamble index N but not preamble index N + 1.
The eNodeB allocates preamble index N + 1 to a UE but not preamble index N.
Then the eNodeB delivers the RAR message that carries preamble index N + 1 to the UE.
Optimization of non-contention-based random access beyond cell radius is controlled by the NonContRaOptSwitch option of the
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.
Network Analysis
5.2.1 Benefits
ACH Resource Adjustment
This function decreases the network access delay if the RACH load is heavy while improving the RACH resource efficiency.
E Random Access Information Query
This function enables the eNodeB to accurately measure the preamble collision probability.
RACH False Alarm Detection
This function improves the random access success rate. It is recommended when the false alarm probability is greater than
expected.
RACH Power Control Parameter Adjustment
This function can control the number of preamble transmissions within the expected range during random access.

E Random Access Control Based on Cell Radius
This function enables an eNodeB to precisely control the coverage scope of a cell.
RACH Frequency-Domain Position Adjustment
This function improves the uplink PRB usage.
RACH Root Sequence Conflict Detection
This function can be used for detecting PRACH root sequence conflicts between cells in time.
ow Control-based Backoff
Positive gains: In heavy-load or Msg3 flow control scenarios, this function relieves RACH congestion and increases the
values of the KPIs RRC Setup Success Rate (Service) and RRC Setup Success Rate (Signaling). The network load is deemed
heavy when the CPU of the main control board or BBP is greater than 75%.
Negative gains: This function decreases the number of times a UE transmits a preamble, increasing the service drop rate.
After the flow control-based backoff function is enabled, the number of received Msg1 and Msg2 messages will decrease,
reducing the BBP CPU resources used to process Msg1 and Msg2 messages. In this case, the eNodeB can process more
Msg3 messages. Therefore, flow control-triggered backoff increases the CPU usage of the BBP by approximately 3%.
tection of Contention-based Random Access Beyond Cell Radius
None
ptimization of Non-Contention-based Random Access Beyond Cell Radius
This function increases the non-contention-based random access success rate.
5.2.2 Impacts
twork Impacts

Impact on uplink capacity
RACH resource adjustment has little impact on uplink system capacity. This is because the PRACH occupies only a
small amount of resources.
RACH resource adjustment reduces the system resources occupied by the RACH and increases the uplink
system capacity when the RACH load is low.
RACH resource adjustment increases the system resources occupied by the RACH and reduces the uplink
system capacity when the RACH load is high.
Impact on access delay

When the RACH load is high, RACH resource adjustment allocates more RACH resources to reduce the probability
of preamble collisions and shorten access delays.
Table 5-3 describes the impact of RACH resource adjustment on network performance in typical scenarios.
Table 5-3 Impact of RACH resource adjustment on network performance
System Bandwidth Contention-based RACH Resource Impact on Network Performance

(MHz) Access Load (a) Adjustment
Non-Contention-based
Access Load (b)
5 or 10 a > 50 and b < 30 Allocates more RACH Reduces the probability of

resources and preamble collisions and shortens
increases the number access delays.
of random preambles.
5 or 10 a > 50 and b > 30 Allocates more RACH Reduces the probability of

resources. preamble collisions and shortens

System Bandwidth Contention-based RACH Resource Impact on Network Performance

(MHz) Access Load (a) Adjustment
Non-Contention-based
Access Load (b)
access delays.
15 or 20 a < 50 and b < 30 Allocates less RACH Increases uplink system capacity.
resources.
The following explains the RACH resource adjustment described in Table 5-3:
Allocates more RACH resources. The eNodeB shortens the PRACH period. For example, the eNodeB
changes the value of prach-ConfigurationIndex from 3 to 6, that is, from 10 ms to 5 ms.
Allocates less RACH resources. The eNodeB prolongs the PRACH period.
Increases the number of contention-based access preambles. According to 3GPP specifications, the
numberOfRA-Preambles field indicates the number of contention-based access preambles.
Load ranges in Table 5-3 are calculated based on the assumption that the random access times follow a poisson
distribution. The calculated load ranges are different from the actual load ranges and therefore the load ranges in
Table 5-3 serve as examples only.
Figure 5-9 RACH resource adjustment when the initial state is 10 ms
Figure 5-10 RACH resource adjustment when the initial state is 5 ms
PRACH false alarm detection

PRACH false alarm detection can reduce the probability of falsely detected preambles. However, a contention-based
preamble initially transmitted by a UE may be incorrectly considered as a PRACH false alarm. This prolongs the handover
delay, decreases the handover success rate, and increases the service drop rate.
In the scenario where the PRACH false alarm detection function is enabled:
When both the PRACHFalseAlarmDetSwitch and PRACHFalseAlaDetRetxOptSwitch options are selected, the
random access success rate is slightly lower than that achieved when only the PRACHFalseAlarmDetSwitch option
is selected.
The random access success rate of UEs with a preamble retransmission period of 40 ms increases.

PRACH power control parameter adjustment can control the number of preamble transmissions within the expected range.
UE random access control based on cell radius
UE random access control based on cell radius enables an eNodeB to control its cell coverage area precisely. However,
allowing UEs beyond the cell radius to perform RACH access and RRC connection setup may decrease the RACH access
success rate and RRC connection setup success rate.
If the RrcSetupSuccRateByRadiusOptSw option of the CellCounterParaGroup.CellCounterAlgoSwitch parameter is
selected, the RRC connection setup success rate increases and the overheads of PDSCH, PUSCH, and PDCCH resources
slightly decrease. This increases the uplink and downlink data rates.
PRACH frequency-domain position adjustment
When a cell serves fewer than four UEs, PRACH frequency-domain position adjustment increases the uplink PRB usage
and uplink capacity of the cell. However, this function increases the uplink capacity by only about 1% because few PUSCH
resources are wasted when the PRACH is not adjacent to the PUCCH.
PRACH root sequence conflict detection
PRACH root sequence conflict detection decreases the possibility of false alarm reporting and preamble collisions.

Root sequence conflicts have no impact on the involved cells when the cells barely affect each other or when the cells affect
each other but the access load in the cells is low. In this case, clearing root sequence conflicts does not necessarily reduce
the possibility of false alarm reporting and preamble collisions.

This function increases the overheads of PDSCH, PUSCH, and PDCCH resources and slightly decreases the uplink and
downlink data rates. This function increases the number of received preamble messages in a cell and decreases the random
access success rate.
None
nction Impacts
RAT Function Name Function Switch Reference Description
FDD In-band relay InBandRelayDeNbSwitch Relay The PRACH subframes may conflict with
and backhaul subframes, affecting UE access.
InBandRelayReNbSwitch For ReBTS cells, only some subframes are
options of the used for UE access and only a few
CellAlgoSwitch.RelaySwitch subframes are available for PRACH
parameter configuration.
For FDD, the recommended values of the
PRACH configuration index are as follows:
Requirements
5.3.1 Licenses
Table 5-4 License information for RACH optimization
Feature ID Feature Name Model Sales Unit
LOFD-002015 RACH Optimization LT1S00RAOP00 per cell
The preceding license controls the following functions:

Flow control-based backoff
5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and mutually exclusive functions have
been deactivated. For detailed operations, see the relevant feature documents.
erequisite Functions
None
utually Exclusive Functions

RAT Function Name Function Switch Reference Description
FDD SFN cell Cell.MultiRruCellMode SFN This function is not compatible

with the following functions:
Detection of contention-
based random access
FDD High speed mobility Cell.HighSpeedFlag High Speed Mobility beyond cell radius
Optimization of non-
contention-based random
access beyond cell radius
FDD Ultra-high speed Cell.HighSpeedFlag High Speed Mobility This function is not compatible
mobility with the following functions:
Detection of contention-
based random access
beyond cell radius
Optimization of non-
contention-based random
access beyond cell radius
5.3.3 Hardware
se Station Models
Only the following functions have requirements for base station models.
Function Base Station Model
UE random access control based on cell radius 3900 and 5900 series base stations
Detection of contention-based random access beyond cell For FDD, the following base stations are compatible with
radius this function:
3900 and 5900 series base stations
Optimization of non-contention-based random access DBS3900 LampSite and DBS5900 LampSite
beyond cell radius BTS3911E
oards
Detection of contention-based random access beyond cell radius and optimization of non-contention-based random access
beyond cell radius are supported by all board models except for the LBBPc.
Other functions: no requirements
F Modules
No requirements
5.3.4 Others
UE random access information query requires that the UEs comply with 3GPP Release 9 or later and support RACH
information reporting.
PRACH power control parameter adjustment requires that the UEs comply with 3GPP Release 9 or later and support RACH
information reporting.
Operation and Maintenance
rameters Used for Activation
Table 5-5 Parameters for RACH resource adjustment

RACH algorithm CellAlgoSwitch.RachAlgoSwitch RachAdjSwitch Select this option.

switch
Indication of RACHCfg.PrachConfigIndexCfgInd None Set this parameter to NOT_CFG.

PRACH
Configuration If this parameter is set to CFG, the
Index eNodeB does not adaptively adjust
RACH resources regardless of
whether the RachAdjSwitch option
is selected under the
CellAlgoSwitch.RachAlgoSwitch
parameter.
If this parameter is set to
NOT_CFG, the eNodeB adaptively
allocates PRACH configuration
indexes regardless of the
RACHCfg.PrachConfigIndex
parameter setting.
Table 5-6 Parameters for UE random access information query
RACH algorithm CellAlgoSwitch.RachAlgoSwitch UeRaInforInqSwitch Select this option.

switch
Table 5-7 Parameters for PRACH false alarm detection
RACH CellAlgoSwitch.RachAlgoSwitch PRACHFalseAlarmDetSwitch Select this option.

algorithm
switch CellAlgoSwitch.RachAlgoSwitch PRACHFalseAlaDetRetxOptSwitch Select this option when there
are UEs configured with the 40
ms preamble retransmission
period and the PRACH false
alarm detection function has
been enabled.
Table 5-8 Parameters for PRACH power control parameter adjustment
RACH algorithm CellAlgoSwitch.RachAlgoSwitch RachPwrAdjSwitch Select this option.

switch UeRaInforInqSwitch
Table 5-9 Parameters for UE random access control based on cell radius
Parameter Parameter ID Option Setting Notes

Name
RACH CellAlgoSwitch.RachAlgoSwitch ForbidAcByRadiusSwitch Select this option if

algorithm the cell coverage
switch areas need to be
controlled
accurately.
Cell radius Cell.CellRadius None Set this parameter

based on the
expected cell radius.
PUCCH CellAlgoSwitch.PucchAlgoSwitch PucchSwitch Deselect this

algorithm option in
Parameter Parameter ID Option Setting Notes

Name
switch ultra-high-
speed
scenarios.
Select this
option in
other
scenarios.
PRACH RACHCfg.PrachFreqOffsetStrategy None Set this parameter

Frequency to AUTOMATIC.
Offset
Strategy
Cell CellCounterParaGroup.CellCounterAlgoSwitch RrcSetupSuccRateByRadiusOptSw It is recommended

Counter that this option be
Algorithm selected if the RRC
Switch connection setup
success rate needs
to be increased.
Table 5-10 Parameters for PRACH frequency-domain position adjustment
RACH algorithm CellAlgoSwitch.RachAlgoSwitch PrachFreqAdjSwitch PRACH frequency-domain position

switch adjustment takes effect only when the
PucchSwitch option is selected under
the CellAlgoSwitch.PucchAlgoSwitch
parameter.
It is recommended that this option be
selected.
Table 5-11 Parameters for PRACH root sequence conflict detection
Parameter Name Parameter ID Setting Notes
Root Sequence ENodeBAlgoSwitch.RootSeqConflictDetSwitch Set this parameter to ON.

Conflict Detect
Switch
Table 5-12 Parameters for flow control-based backoff
High Load ENodeBAlgoSwitch.HighLoadNetOptSwitch FlowCtrlTriBackoffSwitch Select this option.

Network
Optimized
Switch
Table 5-13 Parameters for detection of contention-based random access beyond cell radius
RACH algorithm CellAlgoSwitch.RachAlgoSwitch ExceedRadiusRaDetectionSw Select this option.

switch
Table 5-14 Parameters for optimization of non-contention-based random access beyond cell radius

RACH algorithm CellAlgoSwitch.RachAlgoSwitch NonContRaOptSwitch Select this option.

switch
rameters Used for Optimization
Table 5-15 Parameters for PRACH false alarm detection
PRACH False CellRachAlgo.PrachFalseAlarmDetRadThd Set this parameter based on the calculation results of
Alarm Detect the following formulas:
Radius Threshold Urban areas: PRACH false alarm detection
radius threshold = Actual coverage radius + 1
km
Suburban areas: PRACH false alarm detection
radius threshold = Actual coverage radius + 2
km
RACH Threshold CellRachAlgo.RachThdBoostRatio Set this parameter to 20. To further reduce false alarms,
Boosting Ratio increase the value of this parameter with a step of 5.
Table 5-16 Parameters for PRACH power control parameter adjustment
Preamble Initial RACHCfg.PreambInitRcvTargetPwr Retain the default value.

Received Target
Power
Power ramping step RACHCfg.PwrRampingStep Retain the default value.
Table 5-17 Parameters for UE random access control based on cell radius
Cell radius Cell.CellRadius Set this parameter based on the expected cell radius.
tivation Command Examples
//Enabling RACH resource adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachAdjSwitch-1;
MOD RACHCFG:LocalCellId=0,PrachConfigIndexCfgInd=NOT_CFG;
//Enabling UE random access information query

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=UeRaInforInqSwitch-1;
//Enabling PRACH false alarm detection

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFalseAlarmDetSwitch-1;
MOD CELLRACHALGO:LocalCellId=0,PrachFalseAlarmDetRadThd=3000,RachThdBoostRatio=20;
//Turning on the switch for retransmission optimization of PRACH false alarm detection
MOD CELLALGOSWITCH:LocalCellId=0, RachAlgoSwitch=PRACHFalseAlaDetRetxOptSwitch-1;
//Enabling PRACH power control parameter adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachPwrAdjSwitch-1&UeRaInforInqSwitch-1;
//Enabling UE random access control based on the cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=ForbidAcByRadiusSwitch-1;
//(Optional) Selecting the RrcSetupSuccRateByRadiusOptSw option if the RRC connection setup
success rate needs to be increased
MOD CELLCOUNTERPARAGROUP: LocalCellId=0, CellCounterAlgoSwitch=RrcSetupSuccRateByRadiusOptSw-1;
//Enabling PRACH frequency-domain position adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFreqAdjSwitch-1;
//Enabling PRACH root sequence conflict detection

MOD ENODEBALGOSWITCH:RootSeqConflictDetSwitch=ON;
//Enabling flow control-based backoff

MOD ENODEBALGOSWITCH:HighLoadNetOptSwitch=FlowCtrlTriBackoffSwitch-1;
//Enabling detection of contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch= ExceedRadiusRaDetectionSw-1;
//Enabling optimization of non-contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch= NonContRaOptSwitch-1;
ptimization Command Examples
//Changing the PRACH false alarm detection radius threshold and the RACH threshold boosting ratio
MOD CELLRACHALGO: LocalCellId=0, PrachFalseAlarmDetRadThd=10000, RachThdBoostRatio=20;
//Configuring PRACH power control parameter adjustment

MOD RACHCFG: LocalCellId=0, PwrRampingStep=DB2_PWR_RAMPING_STEP, PreambInitRcvTargetPwr=DBM_104;
//Changing the cell radius

MOD CELL: LocalCellId=0, CellRadius=10000;
activation Command Examples
//Deactivating RACH resource adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachAdjSwitch-0;
//Deactivating UE random access information query

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=UeRaInforInqSwitch-0;
//Deactivating PRACH false alarm detection

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFalseAlarmDetSwitch-0;
//Turning off the switch for retransmission optimization of PRACH false alarm detection
MOD CELLALGOSWITCH:LocalCellId=0, RachAlgoSwitch=PRACHFalseAlaDetRetxOptSwitch-0;
//Deactivating PRACH power control parameter adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachPwrAdjSwitch-0;
//Deactivating UE random access control based on the cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=ForbidAcByRadiusSwitch-0;
//Deactivating PRACH frequency-domain position adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFreqAdjSwitch-0;
//Deactivating PRACH root sequence conflict detection

MOD ENODEBALGOSWITCH:RootSeqConflictDetSwitch=OFF;
//Deactivating flow control-based backoff

MOD ENODEBALGOSWITCH:HighLoadNetOptSwitch=FlowCtrlTriBackoffSwitch-0;
//Deactivating detection of contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch= ExceedRadiusRaDetectionSw-0;
//Deactivating optimization of non-contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch= NonContRaOptSwitch-0;

For detailed operations, see Feature Configuration Using the MAE-Deployment.

ACH Resource Adjustment
Method 1
1. On the MAE-Access, start a Uu interface tracing task.

2. Use a UE to access the network. Trace the SIB2 message and observe the values of the IEs prach-ConfigIndex and
preamblesGroupAConfig, as shown in Figure 5-11. If the values of the two IEs change after this function is enabled, this
function has taken effect.
Figure 5-11 SIB2 message
Method 2

2. On the MAE-Access, choose SON > SON Log.
In the displayed Query SON Log window, select LTE RACH Optimization Log under Log Category. In the Event Name
pane, select Adjust RACH Resource Parameters from the Custom drop-down list. Click Query. If any record about
RACH resource optimization is displayed, this function has taken effect.
E Random Access Information Query

3. After the tracing is complete, select the task on the Signaling Trace Management tab page. Check all the traced
messages with Standard Interface Message Type set to RRC_UE_INFO_REQ.
4. If a UEInformationRequest message with the IE rach-ReportReq set to true is displayed among all DL-DCCH-Message
messages in the tracing result, this function has taken effect.
RACH False Alarm Detection
1. On the MAE-Access, start a performance counter tracing task.

2. Calculate the false alarm reporting probability by referring to Table 5-18. If the probability decreases after this function is
enabled, this function has taken effect.
RACH Power Control Parameter Adjustment
Method 1

2. Use a UE to access the network and then check the values of the IEs preambleInitialReceivedTargetPower and
powerRampingStep in SIB2. If the values change after the adjustment, this function has taken effect.
Method 2

In the displayed Query SON Log window, select LTE RACH Optimization Log under Log Category. In the Event Name
pane, select Adjust PRACH Power Parameters from the Custom drop-down list. Click Query. If any record about
PRACH power optimization is displayed, this function has taken effect.
E Random Access Control Based on Cell Radius

2. Use a UE beyond the cell radius to access the cell and check the values of the L.RA.GrpA.Disc.ByTA.Num,
L.RA.GrpB.Disc.ByTA.Num, and L.RRC.SetupFail.Rej.ForbidAc counters. If the values measured before the function is
enabled are different from those obtained after this function is enabled, this function has taken effect.
RACH Frequency-Domain Position Adjustment

2. Use a UE to access the cell and check the value of prach-FreqOffset in SIB2. If the value obtained before the adjustment
is different from that obtained after the adjustment, this function has taken effect.
RACH Root Sequence Conflict Detection
1. On the MAE-Access, query current alarms.

2. Check whether ALM-26247 Configuration Failure is reported. If the alarm is reported and the cause value is PRACH root
sequence conflict, this function has taken effect. ALM-26247 Configuration Failure is reported only when root sequence
conflicts exist on the network. Therefore, if this alarm is not reported, you cannot determine whether this function has
taken effect.
ow Control-based Backoff

2. In the displayed Query SON Log window, select LTE RACH Optimization Log under Log Category. In the Event Name
pane, select Adjust Backoff Parameters from the Custom drop-down list. Click Query. If any record about backoff
optimization is found, this function has taken effect.
tection of Contention-based Random Access Beyond Cell Radius

2. Observe the values of the L.RA.ExceedRadiusContention.Access.Num, L.RA.ExceedRadiusContention.Preamble.Num, and
L.RA.ExceedRadiusContention.Resp counters. If any of their values is not 0 after this function is enabled, this function has
taken effect.
ptimization of Non-Contention-based Random Access Beyond Cell Radius

2. Observe the non-contention-based random access success rate (indicated by L.RA.Dedicate.Msg3Rcv/L.RA.Dedicate.Att).
If the calculated value increases after this function is enabled, this function has taken effect.

The following table lists the monitoring items related to RACH optimization.
Table 5-18 Monitoring items and their expected values
Feature/Function Monitored Item Calculation Formula Expected Value
RACH resource Dedicated- L.RA.Dedicate.PreambleAssign.Num/L.RA.Dedicate.PreambleReq.Num ≥ 99%

adjustment preamble
allocation
success rate
RACH resource Preamble L.RA.UeRaInfoRspWithCon.Num/L.RA.UeRaInfoRsp.Num ≤ 5%

adjustment and collision
probability
Feature/Function Monitored Item Calculation Formula Expected Value

flow control-based
backoff
PRACH false Probability of (L.RA.GrpA.Att + L.RA.GrpB.Att + L.RA.Dedicate.HO.Att – ≤ 1%

alarm detection false alarm L.RA.GrpA.ContResolution – L.RA.GrpB.ContResolution –
reporting L.RA.Dedicate.HO.Msg3Rcv)/(Measurement duration
(s)/Measurement period (s))
NOTE:
The measurement period denotes the PRACH period. For example, if the
PRACH configuration index of a cell is 6, two PRACHs exist in each
frame and therefore the PRACH period is 5 ms (that is, 0.005s).
PRACH power Percentage of L.RA.PreambleSentNum1/L.RA.UeRaInfoRsp.Num ≥ 90%

control parameter random access
adjustment procedures
involving only
one transmission
of the preamble
PRACH Uplink PRB L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail None

frequency-domain usage
position
adjustment
PRACH Uplink L.Thrp.bits.UL/L.Thrp.Time.UL None

frequency-domain throughput
position
adjustment
PRACH false Random access Contention-based random access success rate None
alarm detection, success rate (L.RA.GrpA.ContResolution +
UE random L.RA.GrpB.ContResolution)/(L.RA.GrpA.Att + L.RA.GrpB.Att)
access control x 100%
based on cell
radius, and Non-contention-based random access success rate
PRACH root L.RA.Dedicate.Msg3Rcv/L.RA.Dedicate.Att x 100%
sequence conflict
detection
Detection of Number of L.RA.ExceedRadiusContention.Access.Num None

contention-based contention-based
random access exceeding-cell-
beyond cell radius radius accesses
Number of times L.RA.ExceedRadiusContention.Resp None

a cell sends
Random Access
Response
messages after
contention-based
exceeding-cell-
radius preamble
receptions
Optimization of Non-contention- L.RA.Dedicate.Msg3Rcv/L.RA.Dedicate.Att None

non-contention- based random
based random access success
access beyond rate
cell radius
The following tables list all performance counters related to random access.
Table 5-19 Performance counters related to UE random access

1526728913 through L.RA.PreambleSentNum1 through Number of random access procedures with

1526728914 L.RA.PreambleSentNum9or10 the preamble sent once to the number of
random access procedures with the preamble
sent by 9 or 10 times
1526728920 L.RA.UeRaInfoRsp.Num Number of received UEInformationResponse

messages containing RACH information
1526728921 L.RA.UeRaInfoRspWithCon.Num Number of received UEInformationResponse

messages whose contentionDetected is
TRUE
The counters in Table 5-19 are valid only if the UeRaInforInqSwitch option of the CellAlgoSwitch.RachAlgoSwitch parameter is
selected. If the option is not selected, the values of these counters are always 0.
Table 5-20 Performance counters related to random preambles
1526727215 L.RA.GrpA.Att Number of times the preamble in group A is

received
1526727218 L.RA.GrpB.Att Number of times the contention preamble in

group B is received
1526727217 L.RA.GrpA.ContResolution Number of times a cell sends a Contention

preamble in group A
1526727220 L.RA.GrpB.ContResolution Number of times a cell sends a Contention

preamble in group B
1526742172 L.RA.GrpA.Initial Number of times initially transmitted

contention-based preambles in group A are
received
1526742173 L.RA.GrpB.Initial Number of times initially transmitted

contention-based preambles in group B are
received
1526742174 L.RA.GrpA.Initial.Resp Number of Random Access Response

messages that a cell sends after receiving
initially transmitted contention-based
preambles in group A
1526742175 L.RA.GrpB.Initial.Resp Number of Random Access Response

initially transmitted contention-based
preambles in group B
1526742176 L.RA.Dedicate.Initial Number of times initially transmitted non-

contention-based preambles are received
1526742177 L.RA.Dedicate.HO.Initial Number of times initially transmitted

handover-induced non-contention-based
preambles are received
1526742178 L.RA.Dedicate.Initial.Resp Number of Random Access Response



initially transmitted non-contention-based
preambles
1526742179 L.RA.Dedicate.HO.Initial.Resp Number of Random Access Response

handover-induced initially transmitted non-
contention-based preambles
Table 5-21 Performance counters related to dedicated preambles
1526728937 L.RA.Dedicate.PreambleReq.Num Number of times the non-contention-based

preamble is requested
1526728939 L.RA.Dedicate.PreambleAssign.Num Number of times the non-contention-based

preambles are assigned
1526739751 L.RA.Dedicate.Msg3Rcv Number of times Msg3 is received in the non-

contention-based random access procedure
1526727221 L.RA.Dedicate.Att Number of times the dedicated preamble is

received
1526727222 L.RA.Dedicate.HO.Att Number of times the non-contention-based

preamble is received (used in handover)
1526727225 L.RA.Dedicate.HO.Msg3Rcv Number of times the UE Msg3 Response

message is received in the handover-
triggered non-contention-based random
access procedure
6 Parameters
The following hyperlinked EXCEL files of parameter documents match the software version with which this document is released.
Node Parameter Reference: contains device and transport parameters.

eNodeBFunction Parameter Reference: contains all parameters related to radio access functions, including air interface
management, access control, mobility control, and radio resource management.
eNodeBFunction Used Reserved Parameter List: contains the reserved parameters that are in use and those that have been
disused.
You can find the EXCEL files of parameter reference and used reserved parameter list for the software version used on the live
network from the product documentation delivered with that version.
FAQ 1: How do I find the parameters related to a certain feature from parameter reference?
1. Open the EXCEL file of parameter reference.

2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose Contains. Enter the feature ID,
for example, LOFD-001016 or TDLOFD-001016.
3. Click OK. All parameters related to the feature are displayed.
FAQ 2: How do I find the information about a certain reserved parameter from the used reserved parameter list?
1. Open the EXCEL file of the used reserved parameter list.

2. On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT columns to locate the reserved
parameter, which may be only a bit of a parameter. View its information, including the meaning, values, impacts, and
product version in which it is activated for use.
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the software version with which this document is
released.
Node Performance Counter Summary: contains device and transport counters.

eNodeBFunction Performance Counter Summary: contains all counters related to radio access functions, including air interface
management, access control, mobility control, and radio resource management.
You can find the EXCEL files of performance counter reference for the software version used on the live network from the product
documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter reference?
1. Open the EXCEL file of performance counter reference.

2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and choose Contains. Enter the
feature ID, for example, LOFD-001016 or TDLOFD-001016.
3. Click OK. All counters related to the feature are displayed.
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
9 Reference Documents
1. 3GPP TS 36.211: "Physical channels and modulation"

2. 3GPP TS 36.321: "Medium Access Control (MAC) protocol specification"
3. 3GPP TS 36.331: "Radio Resource Control (RRC)"
4. 3GPP TS 36.141: "Performance requirements for PRACH"
5. LCS
6. Massive MIMO (FDD)
7. Relay
8. SFN
9. Idle Mode Management
10. High Speed Mobility
11. Power Control


PRACH

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PRACH

Uploaded by

Copyright:

Available Formats

3/1/23, 2:00 PM HedEx Startpage

eRAN FDD Feature Documentation

For any question, please contact us.

Random Access Control

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 1/41

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 2/41

Huawei Technologies Co., Ltd.

2 About This Document

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 3/41

eRAN16.1 Draft A (2020-01-20)

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 4/41

Change Description Parameter Change RAT Base Station Model

Changed the name of U2020 to None FDD 3900 and 5900

Revised descriptions in this document.

2 About This Document

This document is intended to acquaint readers with:

The technical principles of features and their related parameters

Features in This Document

Feature ID Feature Name Section

LBFD-002010 Random Access 4 Random Access

LOFD-002015 RACH Optimization 5 RACH Optimization

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 5/41

In contention-based random access, UEs may fail to access the network.

RACH resource adjustment

Trigger Scenario Description Random Access

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 6/41

Trigger Scenario Description Random Access

Location service For details, see LCS. Non-contention-based

Random access is categorized into the following types:

Table 4-1 Preamble formats

0 1000 103.1 800 R ≤ 14.5

1 2000 684.4 800 R ≤ 77.3

2 2000 203.1 1600 R ≤ 29.5

3 3000 684.4 1600 R ≤ 100

4.1.1.2 Preamble Sequence Generation

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 7/41

4.1.1.3 Preamble Sequence Grouping

For example: ROUNDDOWN(3.6) = 3, ROUNDUP(3.1) = 4

4.1.2 Random Access Procedures

4.1.2.1 Contention-based Random Access Procedure

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 8/41

ndom Preamble Transmission

Figure 4-4 Random access preamble transmission procedure

Steps 3 and 5 in the preceding figure are described as follows:

ndom Access Response

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 9/41

plink Scheduling Information Transmission

Initial RRC connection setup

The UE obtains the C-RNTI from the PDCCH.

4.1.2.2 Non-Contention-based Random Access Procedure

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 10/41

The non-contention-based random access procedure is as follows:

1. The eNodeB allocates dedicated preambles to UEs through dedicated signaling.

2. The UE sends the preamble over the PRACH.

4.1.3 Random Access Time-Frequency Resource Configuration

4.1.3.1 Preamble Transmission Time

127.0.0.1:7890/printtopics.html?time=Wed Mar 01 2023 13:58:56 GMT+0200 (Central Africa Time) 11/41

1 15 or 20 19, 20, or 21 (cell radius > 16 km)

1 1.4 or 3 Synchronized: 16, 17, or 18

2 5, 10, 15, or 20 35, 36, or 37

2 1.4 or 3 Synchronized: 32, 33, or 34

3 5, 10, 15, or 20 51, 52, or 53