Random Access Control and RACH

Optimization
Contents
8.3.1.7 Random Access Control and RACH Optimization

eRAN
Random Access Control and RACH
Optimization Feature Parameter Description
Issue 05

Date 2017-10-23
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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: http://www.huawei.com/

Email: support@huawei.com

8.3.1.7 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types

2 Overview
 2.1 Introduction
2.1.1 Random Access
2.1.2 RACH Optimization
2.2 Benefits
2.2.1 RA
2.2.2 RACH Optimization

3 RA
3.1 Preambles
3.1.1 Overview
3.1.2 Preamble Sequence Generation
3.1.3 Preamble Sequence Grouping
3.2 Random Access Procedures
3.2.1 Contention-based Random Access Procedure
3.2.2 Non-Contention-based Random Access Procedure
3.3 RA Time-Frequency Resource Configuration
3.3.1 Preamble Transmission Time
3.3.2 Preamble Transmission Frequency-Domain Position
3.4 Random Access Backoff

4 RACH Optimization
4.1 RACH Resource Adjustment
4.2 UE Random Access Information Query
4.3 PRACH False Alarm Detection
4.4 PRACH Power Control Parameter Adjustment
4.5 UE Random Access Control Based on Cell Radius
4.6 PRACH Frequency-Domain Position Adjustment
4.7 PRACH Root Sequence Conflict Detection
4.8 Flow Control-based Backoff
4.9 Detection of Contention-based Random Access Beyond Cell Radius
4.10 Optimization of Non-Contention-based Random Access Beyond Cell Radius

5 Related Features
5.1 LBFD-002010 Random Access Procedure
5.2 LOFD-002015 RACH Optimization

6 Network Impact
6.1 LBFD-002010 Random Access Procedure
6.2 LOFD-002015 RACH Optimization

7 Engineering Guidelines
7.1 When to Use
7.2 Required Information
7.3 Requirements
7.4 Data Preparation and Feature Activation
7.4.1 Data Preparation
7.4.2 Using the CME
 7.4.3 Using MML Commands
7.4.4 MML Command Examples
7.5 Activation Observation
7.5.1 RA
7.5.2 RACH Optimization
7.6 Deactivation
7.6.1 Using the CME
7.6.2 Using MML Commands
7.6.3 MML Command Examples
7.7 Performance Monitoring
7.8 Parameter Optimization
7.9 Possible Issues

8 Parameters

9 Counters

10 Glossary

11 Reference Documents

1 About This Document

1.1 Scope

This document describes random access control and RACH optimization, including their
technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:
• LBFD-002010 Random Access Procedure
• LOFD-002015 RACH Optimization
This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series base stations

5900 series base stations

Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E

LampSite DBS3900 LampSite

DBS5900 LampSite
 Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience

This document is intended for personnel who:

• Need to understand the features described herein
• Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
• Feature change
Changes in features and parameters of a specified version as well as the affected entities
• Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.

eRAN12.1 05 (2017-10-23)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected

Entity

Feature Added support for 5900 series None Macro and

change base stations and DBS5900 LampSite
LampSite. eNodeBs

Editorial Revised some descriptions in None N/A

change 4.8 Flow Control-based Backoff.

eRAN12.1 04 (2017-08-30)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected

Entity

Feature None None N/A

change
 Change Type Change Description Parameter Change Affected
Entity

Editorial Revised some descriptions in None N/A

change 7.7 Performance Monitoring.

eRAN12.1 03 (2017-06-29)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected

Entity

Feature None None N/A

change

Editorial Revised some descriptions in None N/A

change 7.1 When to Use and 7.3
Requirements.

eRAN12.1 02 (2017-04-26)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected

Entity

Feature None None N/A

change

Editorial Revised some descriptions in None N/A

change 3.1.3 Preamble Sequence Grouping
and 7.5.2 RACH Optimization.

eRAN12.1 01 (2017-03-08)

This issue does not include any changes.

eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 01 (2016-03-

07) of eRAN11.1.

Change Type Change Description Parameter Change Affected

Entity

Feature Added the function of detecting Added the Macro,

change contention-based random ExceedRadiusRaDetectionSw micro, and
 Change Type Change Description Parameter Change Affected
Entity

access beyond cell radius. For check box to the LampSite

details, see the following CellAlgoSwitch.RachAlgoSwitch eNodeBs
sections: parameter.
• 4.9 Detection of Contention-
based Random Access Beyond
Cell Radius
• 5.2 LOFD-002015 RACH
Optimization
• 6.2 LOFD-002015 RACH
Optimization
• 7 Engineering Guidelines

Added the function of Added the Macro,

optimizing non-contention- NonContRaOptSwitch check micro, and
based random access beyond box to the LampSite
cell radius. For details, see the CellAlgoSwitch.RachAlgoSwitch eNodeBs
following sections: parameter.
• 4.10 Optimization of Non-
Contention-based Random
Access Beyond Cell Radius
• 5.2 LOFD-002015 RACH
Optimization
• 6.2 LOFD-002015 RACH
Optimization
• 7 Engineering Guidelines

Editorial Revised descriptions in this None N/A

change document.

1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs

None

Function Implementation in Macro, Micro, and LampSite eNodeBs

Function Difference

Preamble format Macro, micro, and LampSite eNodeBs support different

preamble formats. The Cell.PreambleFmt parameter
specifies the preamble format.

Cell radius-based UE random This function applies only to macro eNodeBs.

access control
2 Overview

2.1 Introduction

2.1.1 Random 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 RACHs 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.
2.1.2 RACH Optimization

RACH optimization helps decrease the network access delay of all UEs and mitigate uplink
interference caused by PRACHs. RACH optimization involves RACH resource adjustment,
PRACH false alarm detection, PRACH power control parameter adjustment, and other
functions.

RACH Resource Adjustment

RACH resources are configured semi-statically. When the traffic model changes, the
configured RACH resources may fail to accommodate the RACH load. In this situation,
RACH resources need to be adjusted as follows:
• 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.

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. For a
PRACH false alarm, the eNodeB does not send a Random Access Response message to the
UE or count it into the related counters.

PRACH Power Control Parameter Adjustment

 This function enables an eNodeB to adjust PRACH power control parameter settings based on
the random access information reported by the UEs. The parameters to be adjusted 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.

UE Random Access Control Based on Cell Radius

If the distance between a UE and the eNodeB is greater than the cell radius, the eNodeB
prohibits the UE from accessing the cell to control the coverage scope of the cell precisely.

PRACH Frequency-Domain Position Adjustment

This function enables the eNodeB to adjust the PRACH frequency-domain position based on
the number of RBs used by the PUCCH so that the PRACH is adjacent to the low-frequency
PUCCH.

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 2-1 and Figure 2-2.
Figure 2-1 Increase in the probability of false alarms

Figure 2-2 Increase in the probability of preamble collisions

This function enables the eNodeB to detect the root sequence conflict between the serving cell
and the neighboring cell at the peer end of an X2 link or between the serving cell and an intra-
eNodeB neighboring cell. In addition, the root sequence conflict information is displayed in
an alarm.

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 2-3 Msg3 flow control

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.

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.
2.2 Benefits

2.2.1 RA

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.
2.2.2 RACH Optimization

RACH Resource Adjustment

This function decreases the network access delay if the RACH load is heavy while improving
the RACH resource efficiency.

PRACH False Alarm Detection

 This function increases the random access success rate.

PRACH Power Control Parameter Adjustment

This function can control the number of preamble transmissions within the expected range
during random access.

UE Random Access Control Based on Cell Radius

This function enables an eNodeB to precisely control the coverage scope of a cell.

PRACH Frequency-Domain Position Adjustment

This function improves the uplink PRB usage.

PRACH Root Sequence Conflict Detection

This function can be used for detecting PRACH root sequence conflicts between cells in time.

Flow Control-based Backoff

• Positive gains: In heavy-load or Msg3 flow control scenarios, this function relieves
RACH congestion and increases the RRC connection setup success rate in both the user
plane and control plane.
• Negative gains: This function decreases the number of times that a UE transmits a
preamble, which may increase the service drop rate.

3 RA

This chapter describes LBFD-002010 Random Access Procedure.

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-triggering scenarios and random access
mechanisms.

Triggering Scenario Description Random Access

Mechanism

Initial RRC connection To switch from the RRC_IDLE state to the Contention-based
setup RRC_CONNECTED state, a UE initiates random access
random access.
 Triggering Scenario Description Random Access
Mechanism

RRC connection When a radio link failure (RLF) occurs, the

reestablishment UE needs to reestablish an RRC
connection. In this scenario, the UE initiates
random access.

Handover During a handover, a UE initiates random Non-contention-

access in the target cell. based random
access, and
Downlink data arrival When an eNodeB needs to send downlink contention-based
data to a UE in the RRC_CONNECTED random access
state and finds that the UE is out of uplink which applies when
synchronization, the eNodeB instructs the dedicated preambles
UE to initiate random access. are used up

Uplink data arrival When a UE in the RRC_CONNECTED Contention-based

state needs to send uplink data to an random access
eNodeB and finds that itself is out of uplink
synchronization, the UE initiates random
access.

Location service (LCS) For details, see LCS Feature Parameter Non-contention-
initiation Description. based random
access

Random access is categorized into the following types:

• Contention-based random access: 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: 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 triggering 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.
3.1 Preambles

3.1.1 Overview

During random access, the eNodeB sends the preamble configuration information to a UE.
Then 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 3-1. TCP denotes a cyclic prefix and TSEQ a preamble
sequence.
Figure 3-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 3-1 lists preamble formats corresponding to different TCP,
TSEQ, and cell radii.
Table 3-1 Preamble formats
Preamble Format Burst (µs) TCP (µs) TSEQ (µs) LTE FDD Cell
Radius (R) (km)

0 1,000 103.1 800 R ≤ 14.5

1 2,000 684.4 800 R ≤ 77.3

2 2,000 203.1 1,600 R ≤ 29.5

3 3,000 684.4 1,600 R ≤ 100

4 167.9 14.58 133.33 N/A

3.1.2 Preamble Sequence Generation

Preamble sequences are generated from cyclic shifts of Zadoff-Chu (ZC) root sequences.
• The logical ZC root sequence index is specified by the Cell.RootSequenceIdx parameter
and ranges from 0 to 837. The logical index of the ZC sequence is cyclic. 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. If 64 preamble
sequences cannot be generated from a single ZC sequence, they are obtained from subsequent
ZC sequences. For details about preamble sequence generation, see section 5.7.2 "Preamble
sequence generation" in 3GPP TS 36.211 V10.3.1. The logical index of a ZC sequence and
the value of a cyclic shift are indicated by the prach-ConfigIndex IE in SIB2.
3.1.3 Preamble Sequence Grouping

Based on the contention mechanism used during random access, preambles are grouped for
UE selection. Figure 3-2 shows the preamble sequence grouping principles.
 Figure 3-2 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
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.
3.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.
3.2.1 Contention-based Random Access Procedure

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

 Figure 3-3 Contention-based random access procedure

Random Preamble Transmission

shows the random preamble transmission procedure of the UE during contention-

Figure 3-4
based random access.
Figure 3-4 Random access preamble transmission procedure

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

• In step 3, the UE selects preamble group B only if all of the following conditions are
met:
▪ 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.

Random Access Response

Upon receiving the preamble, the eNodeB applies for a temporary cell RNTI (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 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.

Uplink 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.
Contention Resolution

After the UE sends Msg3 (indicated as scheduled transmission in Step 3 in Figure 3-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 information element
(IE) UE Contention Resolution Identity 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. Then, the UE performs random access again if the number of random
access attempts has not reached its upper limit. If the number of random access attempts has
reached its upper limit, the random access procedure fails.
3.2.2 Non-Contention-based Random Access Procedure

shows the non-contention-based random access procedure. Unlike contention-based

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

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

1. The eNodeB allocates a random access preamble to the UE by using a dedicated
signaling message.
• During a handover, a MobilityControlInfo message sent by the source eNodeB
carries the preamble.
 • Upon downlink data arrival, 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.
• During a handover, the response contains at least the timing alignment information
and initial uplink grant.
• Upon downlink data arrival, the 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.
3.3 RA Time-Frequency Resource Configuration

3.3.1 Preamble Transmission Time

During the contention-based random access, the UE reads the prach-ConfigIndex IE in system
information block 2 (SIB2) to obtain the PRACH start time in each radio frame. The value of
the prach-ConfigIndex IE ranges from 0 to 63. For details, see section 5.7.1 "Time and
frequency structure" in 3GPP TS 36.211 V10.3.1.
A prach-ConfigIndex IE is configured based on the factors such as the cell bandwidth and
average access delay. The prach-ConfigIndex IE is specified by the
RACHCfg.PrachConfigIndex parameter.
• The RACHCfg.PrachConfigIndex parameter takes effect when
RACHCfg.PrachConfigIndexCfgInd is set to CONFIG.
• The RACHCfg.PrachConfigIndex parameter does not take effect when
RACHCfg.PrachConfigIndexCfgInd is set to NOT_CONFIG. In this case, the prach-
ConfigIndex IE uses the typical default values listed in the following tables.
Table 3-2 Typical default values of the prach-ConfigIndex IE when the LBBPc is used

Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-

Format (MHz) ConfigIndex

LOW_SPEED(Low speed cell 0 15/20 6/7/8

flag)
5/10 3/4/5

1.4/3 Synchronized: 0/1/2

Non-synchronized: 3/4/5

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

22/24/23 (cell radius ≤ 16 km)

5/10 19/20/21

1.4/3 Synchronized: 16/17/18

Non-synchronized: 19/20/21

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

 Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-
Format (MHz) ConfigIndex

1.4/3 Synchronized: 32/33/34

Non-synchronized: 35/36/37

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

1.4/3 Synchronized: 48/49/50

Non-synchronized: 51/52/53

• HIGH_SPEED(High speed 0 15/20, 5/10 3/4/5

cell flag)
• ULTRA_HIGH_SPEED(Ultra 1.4/3 Synchronized: 0/1/2
high speed cell flag) Non-synchronized: 3/4/5

1 15/20, 5/10 19/20/21

1.4/3 Synchronized: 16/17/18

Non-synchronized: 19/20/21

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

1.4/3 Synchronized: 32/33/34

Non-synchronized: 35/36/37

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

1.4/3 Synchronized: 48/49/50

Non-synchronized: 51/52/53

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

Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-

Format (MHz) ConfigIndex

• LOW_SPEED(Low 0 15/20 6
speed cell flag)
• HIGH_SPEED(High 5/10 3
speed cell flag)
1.4/3 Synchronized: 0
Non-synchronized: 3

1 15/20, 5/10 19

1.4/3 Synchronized: 16
Non-synchronized: 19

2 15/20, 5/10 35

1.4/3 Synchronized: 32
Non-synchronized: 35

3 15/20, 5/10 51
 Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-
Format (MHz) ConfigIndex

1.4/3 Synchronized: 48
Non-synchronized: 51

ULTRA_HIGH_SPEED(Ultra 0 15/20, 5/10 3

high speed cell flag)
1.4/3 Synchronized: 0
Non-synchronized: 3

1 15/20, 5/10 19

1.4/3 Synchronized: 16
Non-synchronized: 19

2 15/20, 5/10 35

1.4/3 Synchronized: 32
Non-synchronized: 35

3 15/20, 5/10 51

1.4/3 Synchronized: 48
Non-synchronized: 51

PRACH subframes of different cells under an eNodeB can be separated in the time domain
and this function is controlled by the ENodeBAlgoSwitch.PrachTimeStagSwitch parameter.
• This function takes effect when RACHCfg.PrachConfigIndexCfgInd is set to
NOT_CONFIG.
• This function does not take effect when RACHCfg.PrachConfigIndexCfgInd is set to
CONFIG. It is recommended that this function be enabled in the scenario where the
LBBPd serves as the baseband processing board for six cells in 4R mode and the air
interface software synchronization function is enabled. The typical default values of the
prach-ConfigIndex IE are listed in the following table (the LBBPc is not used).
Table 3-4 Typical default values of the prach-ConfigIndex IE

Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-

Format (MHz) ConfigIndex

• LOW_SPEED(Low 0 15/20 6/7/8

speed cell flag)
• HIGH_SPEED(High 5/10 3/4/5
speed cell flag) 1.4/3 Synchronized: 0/1/2
Non-synchronized: 3/4/5

1 15/20, 5/10 19/20/21

1.4/3 Synchronized: 16/17/18

Non-synchronized: 19/20/21

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

 Cell Type (HighSpeedFlag) Preamble Bandwidth Typical Default Value of prach-
Format (MHz) ConfigIndex

1.4/3 Synchronized: 32/33/34

Non-synchronized: 35/36/37

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

1.4/3 Synchronized: 48/49/50

Non-synchronized: 51/52/53

ULTRA_HIGH_SPEED(Ultra 0 15/20, 5/10 3/4/5

high speed cell flag)
1.4/3 Synchronized: 0/1/2
Non-synchronized: 3/4/5

1 15/20, 5/10 19/20/21

1.4/3 Synchronized: 16/17/18

Non-synchronized: 19/20/21

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

1.4/3 Synchronized: 32/33/34

Non-synchronized: 35/36/37

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

1.4/3 Synchronized: 48/49/50

Non-synchronized: 51/52/53

NOTE:
• "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.

3.3.2 Preamble Transmission Frequency-Domain Position

For details, see 4.6 PRACH Frequency-Domain Position Adjustment.

3.4 Random Access Backoff

The RACH does not interfere with other uplink channels in LTE. Generally, the probability of
RACH collisions is low. If an excessively large number of UEs are admitted on a PRACH,
however, preamble collisions may occur, and some UEs may fail to access the network. To
solve this problem, random access backoff is introduced to control the time for preamble
retransmission by UEs.
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 its backoff time (corresponding to
the subframe position in the time domain). The UE can retransmit the preamble only after the
backoff time expires. Figure 3-6 shows the backoff mechanism.
 Figure 3-6 Backoff mechanism

Random access backoff is not performed in the following scenarios:

• Initial preamble transmission
• Preamble retransmission during non-contention-based random access

4 RACH Optimization

This chapter describes LOFD-002015 RACH Optimization.

4.1 RACH Resource Adjustment

Adjustment 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 4-1 and Table 4-1 describes the PRACH configuration index adjustment principles.
Figure 4-1 PRACH configuration index adjustment principles

Table 4-1 PRACH configuration index adjustment principles

Scenario Adjustment Principle

Both the dedicated preambles and random The eNodeB decreases the PRACH
preambles are redundant and the uplink PRB configuration index.
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 random preambles are insufficient based on the random access
information reported by the UE.
▪ When the UE random access information query function is disabled, the eNodeB
determines whether random preambles are insufficient based on the number of
random preambles detected within a period of time.
• The eNodeB determines whether the uplink PRB usage is high based on the actual PRB
usage in the uplink.

NOTE:
When the UlSwitch and UlLdcSwitch check boxes are both deselected under the
CellAlgoSwitch.RacAlgoSwitch parameter, 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 4-2 shows the preamble group adjustment principles.

 Figure 4-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 insufficient 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.

Parameters

The RachAdjSwitch check box under the CellAlgoSwitch.RachAlgoSwitch parameter

specifies whether to enable the RACH resource adjustment function. This function takes
effect only when the RachAdjSwitch check box under the RachAdjSwitch parameter is
selected and the RACHCfg.PrachConfigIndexCfgInd parameter is set to NOT_CONFIG.
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
check box 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.PrachConfigIndexCfgInd parameter
remains unchanged if the RACHCfg.PrachConfigIndex parameter is set to
CFG(Configure).
• The RACHCFG.PrachConfigIndex parameter returns to the default setting if the
RACHCfg.PrachConfigIndexCfgInd parameter is set to NOT_CFG(Not configure).
4.2 UE Random Access Information Query

The eNodeB can send UEInformationRequest messages to UEs to query the random access
information of the UEs. This function requires that the UEs comply with 3GPP Release 9 or
later. The random access information includes the number of preamble transmissions and the
contention-based random access conflict identification during the last random access.
 Using the reported information as an input to RACH resource adjustment, the eNodeB can
estimate the preamble collision probability with higher accuracy, thereby effectively limiting
the preamble collision probability to the target value.
UE random access information query is controlled by the UeRaInforInqSwitch option of the
CellAlgoSwitch.RachAlgoSwitch parameter.
4.3 PRACH False Alarm Detection

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. The PRACH false alarm detection function is controlled by the
PRACHFalseAlarmDetSwitch(PRACHFalseAlarmDetSwitch) check box under the
CellAlgoSwitch.RachAlgoSwitch parameter.
Figure 4-3 shows the PRACH false alarm detection decision mechanism.
Figure 4-3 PRACH false alarm detection decision mechanism

To ensure the gains offered by PRACH false alarm detection, it is recommended that the
CellRachAlgo.PrachFalseAlarmDetRadThd and CellRachAlgo.RachThdBoostRatio parameters be
set to desired values.
To support UEs with a 40 ms preamble retransmission period, the function of identifying
these preambles is added to the eNodeB and is controlled by the
PRACHFalseAlaDetRetxOptSwitch check box under 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
4.4 PRACH Power Control Parameter Adjustment

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 random access 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
powerRampingStep.
3. Broadcasts the adjusted parameters using a SIB.
The PRACH power control parameter adjustment function is controlled by the
RachPwrAdjSwitch check box under the CellAlgoSwitch.RachAlgoSwitch parameter and
requires the UE-reported random access information. Therefore, to make PRACH power
control parameter adjustment take effect, the UE random access information query function
must also be enabled by selecting the UeRaInforInqSwitch check box under the
CellAlgoSwitch.RachAlgoSwitch parameter.
It is recommended that the PRACH power control parameter adjustment function be disabled
if this function does not perform as expected or the network condition is not suitable for
implementing this function. After the selected RachPwrAdjSwitch check box is deselected,
the values of the RACHCfg.PreambInitRcvTargetPwr and RACHCfg.PwrRampingStep
parameters change as follows:
• If the RACHCfg.PreambInitRcvTargetPwr parameter has been modified by running the
MOD RACHCFG command, the value of this parameter changes accordingly.
Otherwise, the parameter returns to the default setting.
• If the RACHCfg.PwrRampingStep parameter has been modified by running the MOD
RACHCFG command, the value of this parameter changes accordingly. Otherwise, the
parameter returns to the default setting.
4.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 network
from the cell. This function is recommended only when the coverage scope of a cell needs to
be controlled accurately.
UE random access control based on cell radius is controlled by the
ForbidAcByRadiusSwitch option under the CellAlgoSwitch.RachAlgoSwitch parameter.
The implementation principles of this function are described as follows:
 1. After receiving a preamble from a UE, the eNodeB calculates the distance between the
UE and the eNodeB based on the timing advance (TA) of the preamble.

NOTE:
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.
4.6 PRACH Frequency-Domain Position Adjustment

shows three methods of determining the PRACH frequency-domain position:

Figure 4-4
determining the position based on the RACHCFG.PrachFreqOffset parameter; determining the
position based on the maximum number of RBs used by the PUCCH; adaptively adjusting the
position based on the number of RBs used by the PUCCH.
Figure 4-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 4-5. When a small number
of UEs exist 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. In this
 situation, the eNodeB adjusts the PRACH frequency-domain position based on the number of
RBs used by the PUCCH so that the PRACH is adjacent to the PUCCH located at the low
frequency, thereby preventing the waste of PUSCH RB resources.
Figure 4-5 PRACH frequency-domain position adjustment

PRACH frequency-domain position adjustment is controlled by the PrachFreqAdjSwitch

check box under the CellAlgoSwitch.RachAlgoSwitch parameter. This function takes effect
only when the PucchSwitch check box under the CellAlgoSwitch.PucchAlgoSwitch parameter
is selected and the RACHCFG.PrachFreqOffsetStrategy parameter is set to AUTOMATIC.
The eNodeB adaptively adjusts the PRACH frequency-domain position based on the number
of RBs used by the PUCCH.
4.7 PRACH Root Sequence Conflict Detection

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 ALM-26247 Configuration Failure is reported when
both of the following conditions are met:
▪ The PRACH time-frequency resources of the serving cell overlap with those of
neighboring cells.
▪ The serving cell uses completely the same or partially the same root sequence as
neighboring cells.
• When this function is disabled, the eNodeB determines that the root sequence conflict
disappears. Then, ALM-26247 Configuration Failure is cleared.

NOTE:
• 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.

4.8 Flow Control-based Backoff

The eNodeB adjusts the backoff index based on statistics on Msg3 flow control collected
every second, as shown in Table 4-2.
 Table 4-2 Flow control-based backoff index adjustment principles
Msg3 Flow Control Backoff Index
Adjustment

When both of the following conditions are met: The eNodeB increases
• The result of dividing the flow-control Msg3 quantity by the the value of the
received Msg3 quantity is greater than 5%. 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 40%.

When either of the following conditions is met: The eNodeB

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

Other conditions The eNodeB does not

change the value of
the backoff index.

Flow control-based backoff is controlled by the FlowCtrlTriBackoffSwitch check box under

the ENodeBAlgoSwitch.HighLoadNetOptSwitch parameter.
After this function is enabled, any adjustment to backoff indexes will be recorded in the SON
log. If the BackOffSwitch check box under the CellAlgoSwitch.RachAlgoSwitch
parameter is also selected, backoff indexes are more frequently adjusted and more SON logs
are created.
4.9 Detection of Contention-based Random Access Beyond Cell Radius

The detection procedure is as follows:

1. An eNodeB receives a random preamble that is a retransmission preamble, and detects
the preamble index of N but not the preamble index of 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 the 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.
This function is controlled by the ExceedRadiusRaDetectionSw check box under the
CellAlgoSwitch.RachAlgoSwitch parameter.
4.10 Optimization of Non-Contention-based Random Access Beyond Cell Radius

During the optimized procedure, if an eNodeB receives a dedicated preamble that is a

retransmission preamble, and the following conditions are met:
• The eNodeB detects that the index of the preamble is N but not N+1.
• The eNodeB allocates preamble N+1 to a UE but not preamble N.
 Then the eNodeB delivers the RAR message that carries the preamble index of N+1 to the
UE.
This function is controlled by the NonContRaOptSwitch check box under the
CellAlgoSwitch.RachAlgoSwitch parameter.

5 Related Features

5.1 LBFD-002010 Random Access Procedure

Prerequisite Features

Feature ID Feature Name Description

LBFD-002009 Broadcast of System None

Information

LBFD-00201803 Cell Selection and None

Re-selection

Mutually Exclusive Features

None

Impacted Features

None
5.2 LOFD-002015 RACH Optimization

Prerequisite Features

None

Mutually Exclusive Features

Feature ID Feature Name Description

LOFD-003029 SFN These functions are mutually exclusive with the

detection of contention-based random access beyond
LOFD-001007 High Speed cell radius and the optimization of non-contention-
Mobility based random access beyond cell radius.
LOFD-001008 Ultra High Speed
Mobility
Impacted Features

None

6 Network Impact

6.1 LBFD-002010 Random Access Procedure

System Capacity

No impact.

Network Performance

No impact.
6.2 LOFD-002015 RACH Optimization

System Capacity

• RACH resource adjustment

▪ For a cell bandwidth of 15 MHz or 20 MHz, the default PRACH occurrence interval
is 5 ms, RACH resource adjustment reduces the consumption of RACH resources
and increases the uplink system capacity when the RACH load is low.
▪ For a cell bandwidth of 10 MHz or less, the default PRACH occurrence interval is
10 ms, RACH resource adjustment increases the consumption of RACH resources
and decreases the uplink system capacity when the RACH load is high.
▪ RACH resource adjustment has little impact on uplink system capacity. This is
because the PRACH occupies only a small amount of resource.
• 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.
• Detection of contention-based random access beyond cell radius
This function increases the overheads of PDSCH, PUSCH, and PDCCH resources and
slightly decreases the uplink and downlink data rates.

Network Performance

• RACH resource adjustment

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 6-1describes the impact of RACH resource adjustment on network performance in
typical scenarios.
Table 6-1 Impact of RACH resource adjustment on network performance

Scenario System Load Range RACH Resource Impact

Bandwidth (MHz) Adjustment

1 5 or 10 a > 50 and b < Allocates more Reduces the probability of

30 RACH resources preamble collisions and
and increases shortens access delays.
the number of
random
preambles.

2 5 or 10 a > 50 and b > Allocates more Reduces the probability of

30 RACH preamble collisions and
resources. shortens access delays.

3 15 or 20 a < 50 and b < Allocates less Increases uplink cell

30 RACH capacity.
resources.

The following explains the RACH resource adjustment described in Table 6-1:
▪ Allocates more RACH resources. The eNodeB shortens the PRACH interval. 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 interval.
▪ Increases the number of contention-based access preambles. According to 3GPP
specifications, the numberOfRA-Preambles parameter indicates the number of
contention-based access preambles.
▪ a: contention-based load, equal to the number of contention-based random access
attempts per second
▪ b: non-contention-based load, equal to the number of dedicated random access
attempts per second
Load ranges in Table 6-1 are calculated on the assumption that the random access times
follow a poisson distribution. The calculated load ranges in Table 6-1 are different from
the actual load ranges and therefore serve as examples only.
Figure 6-1 Initial and subsequent RACH resource adjustments (for 5 MHz or 10 MHz)
 Figure 6-2 Initial and subsequent RACH resource adjustments (for 15 MHz or 20 MHz)

• PRACH false alarm detection

PRACH false alarm detection can reduce the probability of falsely detecting 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 call drop rate.
In the scenario where the PRACH false alarm detection function is enabled:
▪ When both the PRACHFalseAlarmDetSwitch and
PRACHFalseAlaDetRetxOptSwitch check boxes are selected, the random access
success rate slightly decreases compared with when only the
PRACHFalseAlarmDetSwitch check box is selected.
▪ The random access success rate of UEs with a preamble retransmission period of 40
ms increases.
• PRACH power control parameter adjustment
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 rate.
• PRACH root sequence conflict detection
PRACH root sequence conflict detection decreases the possibility of false alarm
reporting and preamble collisions.

NOTE:
Root sequence has no impact on cells when the cells barely affect each other or 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.

• Flow control-based backoff

In Msg3 flow control scenarios, this function mitigates the RACH congestion and
increases the RRC connection setup success rate in both the user plane and control plane.
However, the number of preambles retransmitted by UEs will significantly decrease,
which may increase the service drop rate.
 NOTE:
After the flow control-based backoff function is enabled, the number of received Msg1s and Msg2s will
decrease, reducing the BBP CPU resources occupied by the processing of Msg1s and Msg2s. In this case,
the eNodeB can process more Msg3s and therefore the CPU usage of the BBP increases by about 3%.

• Detection of contention-based random access beyond cell radius

This function increases the number of times that preamble messages are received in a
cell and decreases the random access success rate.
• Optimization of non-contention-based random access beyond cell radius
This function increases the non-contention-based random access success rate.

7 Engineering Guidelines

Random access is a basic function. It can be used as long as cells and IP paths are normal.
Therefore, this chapter describes only activation observation for random access and provides
detailed engineering guidelines for RACH optimization.
7.1 When to Use

RACH Resource Adjustment

• For a system bandwidth of 5 MHz or 10 MHz, the default PRACH occurrence interval is
10 ms and only one PRACH is transmitted in each radio frame. In this case, RACH
resource adjustment is recommended when contention-based random accesses are
performed for more than 50 times per second.
• For a system bandwidth of 15 MHz or 20 MHz, the default PRACH occurrence interval
is 5 ms and two PRACHs are transmitted in each radio frame. In this case, RACH
resource adjustment is recommended only when contention-based random accesses are
performed for less than 50 times per second and non-contention-based random accesses
are performed for less than 30 times per second.
The purpose of RACH resource adjustment is to match PRACHs with loads. Though loads
vary with time, RACH resource adjustment can be used as long as the loads within a period
meet the conditions.

UE Random Access Information Query

UE random access information query is recommended if UEs that support RACH information
reporting and comply with 3GPP Release 9 or later account for more than 80% of all UEs in a
cell.

PRACH False Alarm Detection

PRACH false alarm detection is recommended if the probability of falsely detecting

preambles in a cell is higher than expected.
 It is recommended that the switch for retransmission optimization of PRACH false alarm
detection be turned on when UEs with a 40 ms preamble retransmission period exist in a
network enabled with the PRACH false alarm detection algorithm.

PRACH Power Control Parameter Adjustment

PRACH power control parameter adjustment requires the UE-reported random access
information. A UE can report random access information only when the UE complies with
3GPP Release 9 or later and supports RACH information reporting. PRACH power control
parameter adjustment is recommended when both of the following conditions are met:
• A cell serves a great number of UEs that can report random access information.
• Contention-based and non-contention-based accesses are performed in the cell for more
than 10 times per second or the uplink PRB usage is greater than 50%.

UE Random Access Control Based on Cell Radius

UE random access control based on the cell radius is recommended if cell coverage areas
need to be controlled precisely.

PRACH Frequency-Domain Position Adjustment

The following principles are recommended for determining the PRACH frequency-domain
position:

• When both of the following conditions are met, manually configure the PRACH
frequency-domain position:
▪ 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 5 dB less than that on the PRACH.

NOTE:
▪ 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 less

than four activated UEs and the uplink PUSCH RB resources can be used up. When a
cell serves four or more activated UEs or the uplink PUSCH RB resources cannot be
used up, this function offers no gains in the uplink throughput.

NOTE:
▪ The number of activated UEs is measured by the L.Traffic.ActiveUser.Avg counter.
▪ If the following condition is met, it is considered that 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.Index3, L.ChMeas.PRB.PUSCH.Util.Samp.Index4,
 L.ChMeas.PRB.PUSCH.Util.Samp.Index5, L.ChMeas.PRB.PUSCH.Util.Samp.Index6,
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.

PRACH Root Sequence Conflict Detection

PRACH root sequence conflict detection is recommended when the possibility of false alarm
reporting is greater than expected and whether a root sequence conflict exists is not checked.

NOTE:
• 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.

Flow Control-based Backoff

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%.

Detection of Contention-based Random Access Beyond Cell Radius

• 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 so that the
number of random access failures of UEs beyond the cell radius can be measured. 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.
• This function does not take effect in the following cells:
▪ SFN cells
▪ High-speed cells

Optimization of Non-Contention-based Random Access Beyond Cell Radius

• It is recommended that this function be enabled to improve the non-contention-based

random access success rate 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.
 • This function does not take effect in the following cells:
▪ SFN cells
▪ High-speed cells
7.2 Required Information

Table 7-1 Information to be collected

Function Required Information Collection
Purpose

RACH resource Trace the RRC-SYS-INFO message over the Uu The information
adjustment interface and record the values of the IEs prach- is used later to
ConfigIndex and preamblesGroupAConfig. check whether
the feature has
• PRACH See Table 7-17. been activated
false alarm successfully.
detection
• PRACH root
sequence
conflict
detection

UE random Collect the values of the L.RA.GrpA.Disc.ByTA.Num,

access control L.RA.GrpB.Disc.ByTA.Num, and
based on cell L.RRC.SetupFail.Rej.ForbidAc counters.
radius

PRACH Collect the value of the prach-FreqOffset IE in SIB2. The information

frequency- is used later to
domain position check whether
adjustment the feature has
been activated
successfully.

Collect the values of the following counters: The information

• L.Traffic.ActiveUser.Avg
is used to
determine
• L.ChMeas.PRB.PUSCH.Util.Samp.Index0
whether to
• L.ChMeas.PRB.PUSCH.Util.Samp.Index1
enable the
• L.ChMeas.PRB.PUSCH.Util.Samp.Index2 involved function
• L.ChMeas.PRB.PUSCH.Util.Samp.Index3 in a certain
• L.ChMeas.PRB.PUSCH.Util.Samp.Index4 scenario.
• L.ChMeas.PRB.PUSCH.Util.Samp.Index5
• L.ChMeas.PRB.PUSCH.Util.Samp.Index6
• L.ChMeas.PRB.PUSCH.Util.Samp.Index7
• L.ChMeas.PRB.PUSCH.Util.Samp.Index8
• L.ChMeas.PRB.PUSCH.Util.Samp.Index9

• RACH See Table 7-17. The information

resource is used to
adjustment determine
• PRACH whether to
power enable the
 Function Required Information Collection
Purpose

control involved function

parameter in a certain
adjustment scenario.

Detection of Collect the values of the following counters:

contention-based • L.RA.GrpA.Att
random access • L.RA.GrpB.Att
beyond cell • L.RA.GrpA.ContResolution
radius
• L.RA.GrpB.ContResolution

Optimization of Collect the values of the L.RRC.ReEst.HoFail.Att and

non-contention- L.RRC.ConnReq.Msg counters.
based random
access beyond
cell radius

7.3 Requirements

Other Features

For details, see 5 Related Features.

Hardware

The detection of contention-based random access beyond cell radius and optimization of non-
contention-based random access beyond cell radius are not supported by the LBBPc board.

License

The operator has purchased and activated the license for the feature listed in Table 7-2.
Table 7-2 License information for RACH optimization

Feature ID Feature License Control License Control NE Sales Unit

Name Item ID Item

LOFD- RACH LT1S00RAOP00 RACH eNodeB per cell

002015 Optimization Optimization(FDD)

NOTE:
The preceding license controls the following functions:
• RACH resource adjustment
• PRACH power control parameter adjustment
• Detection of contention-based random access beyond cell radius
• Optimization of non-contention-based random access beyond cell radius

Other Requirements

None
7.4 Data Preparation and Feature Activation

7.4.1 Data Preparation

RACH Resource Adjustment

Table 7-3 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the RachAdjSwitch check box under

algorithm this parameter.
switch

Table 7-4 Parameter in the RACHCfg MO

Parameter Parameter ID Setting Notes

Name

Indication of RACHCfg.PrachConfigIndexCfgInd • If this parameter is set to

PRACH CFG(Configure), the eNodeB does
Configuration not adaptively adjust RACH resources
Index regardless of whether the
RachAdjSwitch(RachAdjSwitch)
check box is selected under the
CellAlgoSwitch.RachAlgoSwitch
parameter.
• If this parameter is set to
NOT_CFG(Not configure), the
eNodeB adaptively sets the PRACH
configuration index. You do not need
to set the RACHCfg.PrachConfigIndex
parameter.
Set this parameter to NOT_CFG(Not
configure).

UE Random Access Information Query

Table 7-5 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the UeRaInforInqSwitch check box

algorithm under this parameter.
switch

PRACH Frequency-Domain Position Adjustment

Table 7-6 Parameter in the CellAlgoSwitch MO

 Parameter Parameter ID Setting Notes
Name

PUCCH CellAlgoSwitch.PucchAlgoSwitch • In ultra-high-speed scenarios, deselect

algorithm the PucchSwitch check box under this
switch parameter.
• In other scenarios, select the
PucchSwitch check box under this
parameter.

PRACH RACHCfg.PrachFreqOffsetStrategy Set this parameter to

Frequency AUTOMATIC(AUTOMATIC).
Offset
Strategy

RACH CellAlgoSwitch.RachAlgoSwitch PRACH frequency-domain position

algorithm adjustment takes effect only when the
switch PucchSwitch check box is selected under
the CellAlgoSwitch.PucchAlgoSwitch
parameter.
Select the PrachFreqAdjSwitch check box
under this parameter.

PRACH False Alarm Detection

Table 7-7 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the PrachFalseAlarmDetSwitch check

algorithm box under this parameter.
switch Select the
PRACHFalseAlaDetRetxOptSwitch check
box when UEs with a 40 ms preamble
retransmission period exist on the live network.

Table 7-8 Parameters in the CellRachAlgo MO

Parameter Parameter ID Setting Notes

Name

PRACH CellRachAlgo.PrachFalseAlarmDetRadThd Set this parameter based on the

False calculation results of the following
Alarm formulas:
Detect • Urban areas: PRACH false alarm
Radius detection radius threshold =
Threshold Actual coverage radius + 1 km
• Suburban areas: PRACH false
alarm detection radius threshold =
Actual coverage radius + 2 km
 Parameter Parameter ID Setting Notes
Name

RACH CellRachAlgo.RachThdBoostRatio Set this parameter to 20. To further

Threshold reduce false alarms, increase the
Boosting value of this parameter with a step of
Ratio 5.

PRACH Power Control Parameter Adjustment

Table 7-9 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the RachPwrAdjSwitch and

algorithm UeRaInforInqSwitch check boxes under this
switch parameter.

Cell Radius-based UE Random Access Control

Table 7-10 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the ForbidAcByRadiusSwitch check

algorithm box under this parameter.
switch

Table 7-11 Parameter in the Cell MO

Parameter Name Parameter ID Setting Notes

Cell radius Cell.CellRadius Set this parameter based on the expected cell radius.

PRACH Root Sequence Conflict Detection

Table 7-12 Parameter in the ENodeBAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

Root ENodeBAlgoSwitch.RootSeqConflictDetSwitch Set this parameter to ON(On).

Sequence
Conflict
Detect
Switch
Flow Control-based Backoff

Table 7-13 Parameter in the ENodeBAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

High ENodeBAlgoSwitch.HighLoadNetOptSwitch Select the

Load FlowCtrlTriBackoffSwitch check
Network box under this parameter.
Optimized
Switch

Detection of Contention-based Random Access Beyond Cell Radius

Table 7-14 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the ExceedRadiusRaDetectionSw

algorithm check box under this parameter.
switch

Optimization of Non-Contention-based Random Access Beyond Cell Radius

Table 7-15 Parameter in the CellAlgoSwitch MO

Parameter Parameter ID Setting Notes

Name

RACH CellAlgoSwitch.RachAlgoSwitch Select the NonContRaOptSwitch check box

algorithm under this parameter.
switch

7.4.2 Using the CME

For detailed operations, see CME-based Feature Configuration.

7.4.3 Using MML Commands

• Activating RACH resource adjustment

Run the MOD CELLALGOSWITCH command with the
RachAdjSwitch(RachAdjSwitch) check box selected under the RachAlgoSwitch
parameter.
• Activating UE random access information query
Run the MOD CELLALGOSWITCH command with the
UeRaInforInqSwitch(UeRaInforInqSwitch) check box selected under the
RachAlgoSwitch parameter.
 • Activating PRACH false alarm detection
Run the MOD CELLALGOSWITCH command with the
PRACHFalseAlarmDetSwitch(PRACHFalseAlarmDetSwitch) check box selected
under the RachAlgoSwitch parameter and with the PrachFalseAlarmDetRadThd and
RachThdBoostRatio parameters set to appropriate values.
▪ Activating the function of identifying UEs with a 40 ms preamble retransmission
period
Run the MOD CELLALGOSWITCH command with the
PRACHFalseAlaDetRetxOptSwitch(PRACHFalseAlaDetRetxOptSwitch)
check box selected under the RachAlgoSwitch parameter.
• Activating PRACH power control parameter adjustment
1. Run the LST CELLALGOSWITCH command to check whether the
UeRaInforInqSwitch(UeRaInforInqSwitch) check box is selected under the
RachAlgoSwitch parameter. If not, run the MOD CELLALGOSWITCH
command with this check box selected.
2. Run the MOD CELLALGOSWITCH command with the
RachPwrAdjSwitch(RachPwrAdjSwitch) check box selected under the
RachAlgoSwitch parameter.
• Activating UE random access control based on cell radius
Run the MOD CELLALGOSWITCH command with the
ForbidAcByRadiusSwitch(ForbidAcByRadiusSwitch) check box selected under the
RachAlgoSwitch parameter.
• Activating PRACH frequency-domain position adjustment
Run the MOD CELLALGOSWITCH command with the
PrachFreqAdjSwitch(PrachFreqAdjSwitch) check box selected under the
RachAlgoSwitch parameter.

NOTE:
After the PrachFreqAdjSwitch(PrachFreqAdjSwitch) check box is selected under the RachAlgoSwitch
parameter, the PRACH frequency-domain position adjustment function takes effect only when the
PucchSwitch(PucchSwitch) check box under the CellAlgoSwitch.PucchAlgoSwitch parameter is selected and
the RACHCFG.PrachFreqOffsetStrategy parameter is set to AUTOMATIC(AUTOMATIC).

• Activating PRACH root sequence conflict detection

Run the MOD ENODEBALGOSWITCH command with the
ENodeBAlgoSwitch.RootSeqConflictDetSwitch parameter set to ON(On).
• Activating flow control-based backoff
Run the MOD ENODEBALGOSWITCH command with the
FlowCtrlTriBackoffSwitch(FlowCtrlTriBackoffSwitch) check box selected under the
HighLoadNetOptSwitch parameter.
• Activating detection of contention-based random access beyond cell radius
 Run the MOD CELLALGOSWITCH command with the
ExceedRadiusRaDetectionSw(ExceedRadiusRaDetectionSw) check box selected
under the RachAlgoSwitch parameter.
• Activating optimization of non-contention-based random access beyond cell radius
Run the MOD CELLALGOSWITCH command with the
NonContRaOptSwitch(NonContRaOptSwitch) check box selected under the
RachAlgoSwitch parameter.
7.4.4 MML Command Examples

• Activating RACH resource adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachAdjSwitch-1;

• Activating UE random access information query

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=UeRaInforInqSwitch-1;

• Activating PRACH false alarm detection

• MOD
CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFalseAlarmDetSwitch-
1;
MOD
CELLRACHALGO:LocalCellId=0,PrachFalseAlarmDetRadThd=3000,RachThdBoostR
atio=20;

▪ Turning on the switch for retransmission optimization of PRACH false alarm

detection
MOD CELLALGOSWITCH:LocalCellId=0,
RachAlgoSwitch=PRACHFalseAlaDetRetxOptSwitch-1;

• Activating PRACH power control parameter adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=RachPwrAdjSwitch-
1&UeRaInforInqSwitch-1;

• Activating UE random access control based on cell radius

MOD
CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=ForbidAcByRadiusSwitch-1;

• Activating PRACH frequency-domain position adjustment

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=PrachFreqAdjSwitch-1;

• Activating PRACH root sequence conflict detection

MOD ENODEBALGOSWITCH:RootSeqConflictDetSwitch=ON;

• Activating flow control-based backoff

MOD ENODEBALGOSWITCH:HighLoadNetOptSwitch=FlowCtrlTriBackoffSwitch-1;

• Activating detection of contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch=
ExceedRadiusRaDetectionSw-1;

• Activating optimization of non-contention-based random access beyond cell radius

MOD CELLALGOSWITCH:LocalCellId=0,RachAlgoSwitch= NonContRaOptSwitch-1;
7.5 Activation Observation

7.5.1 RA

1. On the U2000 client, start random access tracing, Uu interface tracing, and S1 interface
tracing.
2. Use a UE to access the network.
3. Check the counters of group A (including L.RA.GrpA.Att, L.RA.GrpA.ContResolution, and
L.RA.GrpA.Resp) or the counters of group B (including L.RA.GrpB.Att,
L.RA.GrpB.ContResolution, and L.RA.GrpB.Resp). If any counter value of group A or B
increases during a measurement period, random access has been activated.
7.5.2 RACH Optimization

RACH Resource Adjustment

Method 1
1. On the U2000 client, 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 7-1. If the
values of the two IEs change after this function is enabled, this function has taken
effect.
Figure 7-1 SIB2 message

Method 2
1. Use a UE to access the network.
 2. On the U2000 client, 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.

UE Random Access Information Query

1. On the U2000 client, start a Uu interface tracing task.

2. Use a UE to access the network.
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.

PRACH False Alarm Detection

1. On the U2000 client, start a counter measurement task.

2. Calculate the false alarm reporting probability by referring to Table 7-17. If the
probability decreases after this function is enabled, this function has taken effect.

PRACH Power Control Parameter Adjustment

Method 1
1. On the U2000 client, start a Uu interface tracing task.
2. Use a UE to access the network and then check the values of the IEs
preambleInitialReceivedTargetPower and powerRampingStep in SIB2. If the values
before and after the adjustment are different, this function has taken effect.
Method 2
1. Use a UE to access the network.
2. On the U2000 client, 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 PRACH Power
Parameters from the Custom drop-down list. Click Query. If any record about
PRACH power control parameter adjustment is displayed, this function has taken effect.

UE Random Access Control Based on Cell Radius

1. On the U2000 client, start a counter measurement task.

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

1. On the U2000 client, start a Uu interface tracing task.

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.

PRACH Root Sequence Conflict Detection

1. On the U2000, 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 will be 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.

Flow Control-based Backoff

1. On the U2000 client, choose SON > SON Log.

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.

Detection of Contention-based Random Access Beyond Cell Radius

1. On the U2000 client, start a counter measurement task.

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.

Optimization of Non-Contention-based Random Access Beyond Cell Radius

1. On the U2000 client, start a counter measurement task.

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.
7.6 Deactivation

7.6.1 Using the CME

For detailed operations, see CME-based Feature Configuration.

7.6.2 Using MML Commands

Table 7-16 Related MML commands

Function to Be MML Command Parameter to Be Setting Notes
Deactivated Configured

RACH MOD RACH Deselect the RachAdjSwitch

resource CELLALGOSWITCH algorithm check box.
adjustment switch

UE random Deselect the

access UeRaInforInqSwitch check box.
information
query

PRACH false Deselect the

alarm PrachFalseAlarmDetSwitch
detection check box.

UE random Deselect the

access control ForbidAcByRadiusSwitch
based on cell check box.
radius

PRACH Deselect the

frequency- PrachFreqAdjSwitch check box.
domain
position
adjustment

PRACH power Deselect the

control RachPwrAdjSwitch check box.
parameter
adjustment

Detection of Deselect the

contention- ExceedRadiusRaDetectionSw
based random check box.
access
beyond cell
radius

Optimization Deselect the

of non- NonContRaOptSwitch check
contention- box.
based random
access
beyond cell
radius

PRACH root MOD Root Set this parameter to OFF(off).

sequence ENODEBALGOSWITCH Sequence
conflict Conflict Detect
detection Switch

Flow control- High Load Deselect the

based backoff Network FlowCtrlTriBackoffSwitch
Optimized check box.
Switch
 7.6.3 MML 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;

7.7 Performance Monitoring

The following table lists the items for monitoring random access and RACH optimization.
Table 7-17 Monitoring items and their expected values
Feature/Function Monitored Calculation Formula
Item

RA Contention- (L.RA.GrpA.Att + L.RA.GrpB.Att)/CounterTime

based
access load

RA Non- L.RA.Dedicate.PreambleReq.Num/CounterTime
contention-
Feature/Function Monitored Calculation Formula
Item

based
access load

PRACH false Probability (L.RA.GrpA.Att + L.RA.GrpB.Att + L.RA.Dedicate.HO.Att - L.RA.GrpA.ContResolution -

alarm detection of falsely L.RA.GrpB.ContResolution - L.RA.Dedicate.HO.Msg3Rcv)/(CounterTime/PRACHPe
detecting
preambles

RACH resource Preamble L.RA.UeRaInfoRspWithCon.Num/L.RA.UeRaInfoRsp.Num

adjustment and collision
flow control- probability
based backoff

RACH resource Dedicated- L.RA.Dedicate.PreambleAssign.Num/L.RA.Dedicate.PreambleReq.Num

adjustment preamble
allocation
success rate

PRACH power Percentage L.RA.PreambleSentNum1/L.RA.UeRaInfoRsp.Num

control of random
parameter access
adjustment procedures
involving
only one
transmission
of the
preamble

PRACH Uplink PRB L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail

frequency- usage
domain position
adjustment

PRACH Uplink L.Thrp.bits.UL/L.Thrp.Time.UL

frequency- throughput
domain position
adjustment

PRACH false Random • Contention-based random access success rate

alarm access (L.RA.GrpA.ContResolution+L.RA.GrpB.ContResolution)/(L.RA.GrpA.Att+L.RA.G
detection, cell success rate • Non-contention-based random access success rate
radius-based
L.RA.Dedicate.Msg3Rcv/L.RA.Dedicate.Att*100%
UE random
access control,
and PRACH
root sequence
conflict
detection

Detection of Number of L.RA.ExceedRadiusContention.Access.Num

contention- contention-
based random based
exceeding-
Feature/Function Monitored Calculation Formula
Item

access beyond cell-radius

cell radius accesses

Optimization of Non- L.RA.Dedicate.Msg3Rcv/L.RA.Dedicate.Att

non-contention- contention-
based random based
access beyond random
cell radius access
success rate

NOTE:
CounterTime indicates the measurement period. It is in units of second.
PRACHPeriod indicates the PRACH occurrence period for a cell and is also in units of second. 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).

The following tables list all performance counters related to random access.
Table 7-18 Performance counters related to UE random access
Counter ID Counter Name Description

1526728913 to L.RA.PreambleSentNum1 to Number of random access

1526728914 L.RA.PreambleSentNum9or10 procedures with 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

NOTE:
The counters in Table 7-18 are valid only if the UeRaInforInqSwitch check box is selected under the
CellAlgoSwitch.RachAlgoSwitch parameter. If the UeRaInforInqSwitch check box is not selected, the values
of these counters are always 0.

Table 7-19 Performance counters related to random preambles

Counter ID Counter Name 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
 Counter ID Counter Name Description

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 Resolution message
after receiving a 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 messages that a cell
sends after receiving 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 messages that a cell
sends after receiving initially
transmitted non-contention-based
preambles

1526742179 L.RA.Dedicate.HO.Initial.Resp Number of Random Access

Response messages that a cell
sends after receiving handover-
induced initially transmitted non-
contention-based preambles

Table 7-20 Performance counters related to dedicated preambles

 Counter ID Counter Name Description

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 RA
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 RA procedure

7.8 Parameter Optimization

After PRACH false alarm detection is enabled and the

CellRachAlgo.PrachFalseAlarmDetRadThd parameter is set to an appropriate value, you can
adjust the value of the CellRachAlgo.RachThdBoostRatio parameter to further reduce the
probability of falsely detecting preambles:
• If the initial value of the CellRachAlgo.RachThdBoostRatio parameter is too small, the
effect of reducing the probability of falsely detecting preambles is not obvious. If the
initial value is too large, the probability of falsely regarding initially transmitted random
access preambles as false alarms is too high.
• If the CellRachAlgo.RachThdBoostRatio parameter is set with a small step, the effect of
reducing the probability of falsely detecting preambles is not obvious. If the parameter is
set with a large step, the probability of falsely regarding initially transmitted random
access preambles as false alarms is too high.
Therefore, it is recommended that the CellRachAlgo.RachThdBoostRatio parameter be set to 20
with the step of 5. Ensure that the setting of this parameter does not affect or negligibly
affects the contention-based access delay, success rate of handovers using contention-based
random access, and call drop rate.
7.9 Possible Issues

Table 7-21 Fault description and handling

Fault Description Fault Handling

After one or both of RACH 1. Check whether the cell status is normal by
resource adjustment and PRACH checking for alarms such as ALM-29240 Cell
false alarm detection are Unavailable or ALM-29243 Cell Capability
 Fault Description Fault Handling

activated, UE access failures or Degraded. For details, see Cell Management

handover failures occur. Feature Parameter Description.
2. If the fault persists, contact Huawei technical
support.

After RACH resource adjustment 1. Check whether the cell traffic model meets the
is activated, neither prach- requirements of RACH resource adjustment.
ConfigurationIndex nor 2. If the fault persists, contact Huawei technical
numberOfRA-Preambles is support.
adjusted.

After PRACH false alarm 1. Check whether the values of the

detection is activated, the CellRachAlgo.PrachFalseAlarmDetRadThd and
probability of falsely detecting CellRachAlgo.RachThdBoostRatio parameters are
preambles does not decrease. appropriate.
2. If the fault persists, contact Huawei technical
support.

After UE random access based Check whether the value of the Cell.CellRadius parameter
on cell radius is activated, UEs is appropriate.
outside the cell range access the • If the parameter value is inappropriate, change the
cell successfully. parameter setting.
• If the parameter value is appropriate or the fault
persists after the parameter setting change, contact
Huawei technical support.

After PRACH frequency domain Check whether the PucchSwitch(PucchSwitch) check

position adjustment is activated, box under the CellAlgoSwitch.PucchAlgoSwitch
the PRACH frequency domain parameter is selected.
position does not change when a • If the check box is not selected, confirm whether to
cell serves fewer than four UEs. select it. If the check box is not selected, select it. If
the PRACH frequency domain position remains
unchanged after the check box is selected, contact
Huawei technical support.
• If the check box is selected, contact Huawei
technical support.

No PRACH root sequence Contact Huawei technical support.

conflict occurs in a cell where
ALM-26247 Configuration Failure
is reported after PRACH root
sequence conflict detection is
enabled.

8 Parameters
Table 8-1 Parameters
MO Parameter ID MML Command Feature ID Feature Name

CellAlgoSwitch RachAlgoSwitch MOD LOFD- RACH Meaning:

CELLALGOSWITCH 002015 / Optimization RACHAdjSw
LST TDLOFD-
CELLALGOSWITCH Random (RACH) reso
002015 Access resources in
TDLBFD- Procedure access attem
002010 / is disabled. W
MLBFD- of PRACH pe
12000230 takes effect o
random prea
This option a
HoRaSwitch:
during hando
use the non-
If this option
contention-ba
applies only
UnsyncRaSw
when UEs ar
selected, the
random acce
synchronizat
to use the co
arrivals in the
LTE FDD an
MaksIdxSwit
between UEs
dedicated pre
this option is
only one UE
preamble reu
applies only
BackOffSwitc
is selected, b
backoff contr
for LTE UEs
UeRaInforInq
information is
access inform
UEInformatio
Release 9 an
information. T
for RACH res
UE random a
collected ran
This option a
PRACHFalse
alarm detecti
PrachFalseA
set to 0, PRA
considers the
MO Parameter ID MML Command Feature ID Feature Name

PRACH false
Access Resp
performance
belongs to gr
PrachFalseA
set to 0, PRA
deselected, P
function take
LTE UEs. Th
RachPwrAdjS
the RACH. If
eNodeB dyna
the RACH ba
probability of
successful ra
is deselected
eMTC functio
only on LTE
ForbidAcByR
access base
selected, onl
radius are all
eNodeB doe
eMTC functio
This option a
PrachFreqAd
domain posit
PucchAlgoSw
parameter is
selected, the
based on the
effect, this fu
only to LTE F
PRACHFalse
access from
40 ms when
is selected, a
interval of 40
preambles. W
preambles re
function take
option applie
PrachFreqAb
domain posit
the amount o
the PucchAlg
PrachFreqOf
AUTOMATIC
selects a freq
PRACH. This
 MO Parameter ID MML Command Feature ID Feature Name

ExceedRadiu
the access o
radius. The e
eNodeB is gr
This option d
eMTC functio
This option a
NonContRaO
for UEs whos
this option is
optimization
greater than
option is des
is disabled. T
LBBPc. Whe
only on LTE
GUI Value R
HoRaSwitch(
MaksIdxSwit
UeRaInforInq
PRACHFalse
RachPwrAdjS
ForbidAcByR
PrachFreqAd
PRACHFalse
PrachFreqAb
ExceedRadiu
NonContRaO
Unit: None
Actual Value
MaksIdxSwit
PRACHFalse
ForbidAcByR
PRACHFalse
ExceedRadiu
Default Value
UnsyncRaSw
UeRaInforInq
RachPwrAdjS
PrachFreqAd
PrachFreqAb
NonContRaO

Cell PreambleFmt ADD CELL LBFD- Random Meaning: Ind

MOD CELL 002010 / Access 3GPP TS 36
LST CELL TDLBFD- Procedure TDD.
002010 Extended Cell GUI Value R
LOFD- Access Radius Unit: None
001009 / Cell Access Actual Value
TDLOFD- Radius up to
001009 Default Value
15km
 MO Parameter ID MML Command Feature ID Feature Name

LBFD-
002012

Cell CellRadius ADD CELL LBFD- Random Meaning: Ind

MOD CELL 002010 / Access that a cell ca
LST CELL TDLBFD- Procedure performance
002010 Random Extended Ce
LBFD- Access FDD cells ca
002010 / Procedure / parameter ap
TDLBFD- Extended Cell GUI Value R
002010 / Access Radius Unit: m
LOFD- beyond 100km Actual Value
081223 Extended Cell Default Value
LOFD- Access Radius
001009 / Cell Access
TDLOFD- Radius up to
001009 15km
LBFD-
002012

Cell RootSequenceIdx ADD CELL LBFD- Random Meaning: Ind

MOD CELL 002010 / Access generate the
LST CELL TDLBFD- Procedure corresponds
002010 logical root s
36.211. This
GUI Value R
Unit: None
Actual Value
Default Value

RACHCfg RandomPreambleRatio MOD RACHCFG LBFD- Random Meaning: Ind

LST RACHCFG 002010 / Access in a cell to th
TDLBFD- Procedure preambles in
002010 the number o
classified as
used for cont
random acce
36.321. This
GUI Value R
Ratio16(16/6
Ratio32(32/6
Ratio48(48/6
Ratio64(64/6
Unit: None
Actual Value
Ratio28, Rat
Ratio60, Rat
Default Value
 MO Parameter ID MML Command Feature ID Feature Name

RACHCfg RaPreambleGrpARatio MOD RACHCFG LBFD- Random Meaning: Ind

LST RACHCFG 002010 / Access preambles in
TDLBFD- Procedure number of gr
002010 parameter va
cell. Preamb
dedicated pre
random prea
section 5.1.1
FDD and LTE
GUI Value R
Unit: %
Actual Value
Default Value

RACHCfg MessageSizeGroupA MOD RACHCFG LBFD- Broadcast of Meaning:

LST RACHCFG 002009 / system Indicates the
TDLBFD- information selects a pre
002009 Random random acce
LBFD- Access For details, s
002010 / Procedure FDD and LTE
TDLBFD- GUI Value R
002010 B144_MSG_
B208_MSG_
B256_MSG_
Unit: bit
Actual Value
B144_MSG_
B256_MSG_
Default Value

RACHCfg PreambleTransMax MOD RACHCFG LBFD- Broadcast of Meaning: Ind

LST RACHCFG 002009 / system times. For de
TDLBFD- information GUI Value R
002009 / Random N4_PREMB_
MLBFD- Access N5_PREMB_
12000229 Procedure N6_PREMB_
LBFD- N7_PREMB_
002010 / N8_PREMB_
TDLBFD- N10_PREMB
002010 / N20_PREMB
MLBFD- N50_PREMB
12000230 N100_PREM
N200_PREM
Unit: None
Actual Value
N4_PREMB_
N6_PREMB_
N8_PREMB_
N20_PREMB
N100_PREM
 MO Parameter ID MML Command Feature ID Feature Name

Default Value

RACHCfg ContentionResolutionTimer MOD RACHCFG LBFD- Broadcast of Meaning: Ind

LST RACHCFG 002009 / system during a rand
TDLBFD- information initially sends
002009 Random the NACK to
LBFD- Access does not rece
002010 / Procedure and the UE m
TDLBFD- parameter, s
002010 FDD and LTE
GUI Value R
SF48_MAC_
SF56_MAC_
SF64_MAC_
Unit: subfram
Actual Value
SF48_MAC_
SF56_MAC_
SF64_MAC_
Default Value

RACHCfg PrachConfigIndex MOD RACHCFG LBFD- Broadcast of Meaning: Ind

LST RACHCFG 002009 / system are establish
TDLBFD- information configuration
002009 Random domain. This
LBFD- Access GUI Value R
002010 / Procedure Unit: None
TDLBFD- RACH Actual Value
002010 Optimization Default Value
LOFD-
002015

RACHCfg PrachConfigIndexCfgInd MOD RACHCFG LBFD- Broadcast of Meaning: Ind

LST RACHCFG 002009 / system for a cell. If a
TDLBFD- information configuration
002009 RACH the eMTC fun
LOFD- Optimization regardless of
002015 Random configuration
LBFD- Access is preconfigu
002010 / Procedure FDD and LTE
TDLBFD- GUI Value R
002010 Unit: None
Actual Value
Default Value

ENodeBAlgoSwitch PrachTimeStagSwitch MOD LBFD- Random Meaning:

ENODEBALGOSWITCH 002010 Access Indicates wh
LST Procedure
ENODEBALGOSWITCH are separate
cells under a
parameter is
equipped wit
 MO Parameter ID MML Command Feature ID Feature Name

established o
time domain.
Note that the
both the defa
PrachConfigI
parameter is
specified by
PrachConfigI
PRACH subf
subframe con
parameter se
PrachConfigI
function take
effect on LTE
GUI Value R
Unit: None
Actual Value
Default Value

CellAlgoSwitch RacAlgoSwitch MOD LBFD- Admission Meaning:

CELLALGOSWITCH 002023 / Control Indicates wh
LST TDLBFD-
CELLALGOSWITCH Congestion DlSwitch: Ind
002023 Control admission co
LBFD- Radio/transport downlink adm
002024 / resource pre- satisfaction r
TDLBFD- emption the calculatio
002024 Enhanced satisfaction e
LOFD- extented QCI implemented
00102901 MCPTT QoS VoIP service
/ Management than the actu
TDLOFD- Therefore, if
00102901 Congestion recommende
Control for LTE FDD an
LOFD- Public Safety
081218 / UlSwitch: Ind
TDLOFD- Emergency call admission co
081215 RACH uplink admis
LTROFD- Optimization satisfaction r
111201 / Enhanced QoS calculation o
TDLOFD- for MCPTT satisfaction e
121103 (Trial) implemented
LTROFD- VoIP service
111202 / than the actu
TDLOFD- Therefore, if
121104 recommende
LTE FDD an
LBFD-
002028 / DlLdcSwitch:
TDLBFD- cell. If this op
002028 downlink for
performs loa
LOFD-
eNodeB doe
002015 downlink con
MO Parameter ID MML Command Feature ID Feature Name

TDLOFD- calculation o
110230 satisfaction e
implemented
VoIP service
than the actu
services with
option be des
TDD.
UlLdcSwitch:
cell. If this op
uplink for the
performs loa
eNodeB doe
uplink conge
calculation o
satisfaction e
implemented
VoIP service
than the actu
services with
option be des
TDD.
PreemptionS
this option is
preempt reso
If this option
resources ar
TDD.
PttAcSwitch:
control for PT
admission co
deselected, R
services. Thi
VoltePrefAdm
access of Vo
EutranVoipS
set to ON(On
preferentially
VoLTE servic
option applie
VoltePreemp
preempt reso
services. Thi
VoltePrefAdm
option is sele
this option is
UEs. This op
UeExpBased
the number o
signal quality
 MO Parameter ID MML Command Feature ID Feature Name

eNodeB take
only to LTE T
EmcAdmitCo
policies for e
services can
MCPTT QoS
features take
that of emerg
call services,
released dur
emergency c
preempted o
MCPTT QoS
features take
GUI Value R
DlLdcSwitch(
PreemptionS
VoltePrefAdm
VoltePreemp
UeExpBased
EmcAdmitCo
Unit: None
Actual Value
PreemptionS
VoltePreemp
EmcAdmitCo
Default Value
UlLdcSwitch:
VoltePrefAdm
UeExpBased

CellRachAlgo PrachFalseAlarmDetRadThd MOD CELLRACHALGO LBFD- Random Meaning: Ind

LST CELLRACHALGO 002010 / Access eNodeB for d
TDLBFD- Procedure the UE is a P
002010 RACH does not con
LOFD- Optimization this paramete
002015 the distance
considered a
timing advan
received for t
FDD and LTE
GUI Value R
Unit: m
Actual Value
Default Value

CellRachAlgo RachThdBoostRatio MOD CELLRACHALGO LBFD- Random Meaning: Ind

LST CELLRACHALGO 002010 / Access access chan
TDLBFD- Procedure example, the
002010 RACH alarm detecti
Optimization
 MO Parameter ID MML Command Feature ID Feature Name

LOFD- that the syste

002015 decreases by
GUI Value R
Unit: %
Actual Value
Default Value

RACHCfg PreambInitRcvTargetPwr MOD RACHCFG LBFD- Broadcast of Meaning:

LST RACHCFG 002009 / system Indicates the
TDLBFD- information eNodeB whe
002009 / Random requirements
MLBFD- Access For details, s
12000229 Procedure GUI Value R
LBFD- Uplink Power DBM_116(-1
002010 / Control DBM_110(-1
TDLBFD- RACH DBM_104(-1
002010 / Optimization DBM_98(-98
MLBFD- 92dBm), DBM
12000230
Unit: dBm
LBFD-
Actual Value
002026 /
TDLBFD- DBM_112, D
002026 / DBM_100, D
MLBFD- Default Value
12000235
LOFD-
002015

RACHCfg PwrRampingStep MOD RACHCFG LBFD- Broadcast of Meaning:

LST RACHCFG 002009 / system Indicates the
TDLBFD- information is increased
002009 Random to access the
LBFD- Access access pream
002010 / Procedure an access fa
TDLBFD- Uplink Power For details, s
002010 Control GUI Value R
LBFD- RACH DB2_PWR_R
002026 / Optimization DB4_PWR_R
TDLBFD- Unit: dB
002026
Actual Value
LOFD- DB2_PWR_R
002015 DB6_PWR_R
Default Value

RACHCfg PrachFreqOffset MOD RACHCFG LBFD- Broadcast of Meaning: Ind

LST RACHCFG 002009 / system the frequenc
TDLBFD- information when the Pra
002009 Random PucchSwitch
LBFD- Access an LTE FDD
002010 / Procedure TDD.
 MO Parameter ID MML Command Feature ID Feature Name

TDLBFD- RACH GUI Value R

002010 Optimization Unit: None
LOFD- Actual Value
002015 Default Value

CellAlgoSwitch PucchAlgoSwitch MOD LBFD- Physical Meaning:

CELLALGOSWITCH 002003 / Channel PucchSwitch
LST TDLBFD- Management
CELLALGOSWITCH If this option
002003 Breathing Pilot adjustment w
LEOFD- PUCCH option is des
111306 Flexible PucchFlexCf
LOFD- Configuration configuration
001093 RACH cell bandwidt
LOFD- Optimization enabled, freq
002015 scheduling d
of RBs (spec
PUCCHCfg M
allocated for
equals the P
the extension
deselected, f
applies only
Dl2CCAckRe
channel reso
ACK code ch
groups. If this
associated w
in only one g
SCC associa
any group. T
SCCAckRes
resource con
the maximum
the maximum
in 2CC CA sc
and Max2CC
respectively.
maximum nu
maximum nu
2CC CA scen
EmtcAckMod
this option is
mode. If this
multiplexing
NumRepetitio
NumRepetitio
sends any of
option is des
GUI Value R
PucchFlexCf
Dl2CCAckRe
 MO Parameter ID MML Command Feature ID Feature Name

SCCAckRes
EmtcAckMod
Unit: None
Actual Value
Dl2CCAckRe
Default Value
Dl2CCAckRe
EmtcAckMod

RACHCfg PrachFreqOffsetStrategy MOD RACHCFG LOFD- RACH Meaning: Ind

LST RACHCFG 002015 Optimization domain offse
TDLBFD- Random the eNodeB
002010 Access parameter is
Procedure offset is spec
cell, this para
PucchAlgoSw
parameter va
preamble for
LTE TDD.
GUI Value R
Unit: None
Actual Value
Default Value

ENodeBAlgoSwitch RootSeqConflictDetSwitch MOD LOFD- RACH Meaning: Ind

ENODEBALGOSWITCH 002015 Optimization If this parame
LST root sequenc
ENODEBALGOSWITCH
neighboring c
displayed in
eNodeB doe
about such c
conflict occur
GUI Value R
Unit: None
Actual Value
Default Value

ENodeBAlgoSwitch HighLoadNetOptSwitch MOD LOFD- PS Inter-RAT Meaning:

ENODEBALGOSWITCH 001020 / Mobility Indicates wh
LST TDLOFD- between E-
ENODEBALGOSWITCH network is he
001020 UTRAN and options:
LOFD- GERAN SPECSIGRE
001043 / Service based special signa
TDLOFD- Inter-RAT adaptively co
001043 handover to retransmissio
LOFD- UTRAN number of UE
001046 / Service based cannot adapt
TDLOFD- Inter-RAT retransmissio
001046 handover to number of UE
GERAN TDD.
 MO Parameter ID MML Command Feature ID Feature Name

LOFD- Distance FlowCtrlTriBa

001072 / based Inter- triggered bac
TDLOFD- RAT handover flow control s
001072 to UTRAN backoff is en
LOFD- Distance reinitiate rand
001073 / based Inter- If this option
TDLOFD- RAT handover During rando
001073 to GERAN required and
LOFD- E-UTRAN to number of in
001078 / UTRAN CS/PS rate decreas
TDLOFD- Steering recommende
001078 control-trigge
RACH take effect fo
LOFD- Optimization TDD.
002015
FlowCtrlForw
initial stage o
Msg3 flow co
smaller value
reducing sys
TDD.
FlowCtrlBase
control based
level MSG3 f
consumption
signaling tran
configuration
GUI Value R
SPECSIGRE
FlowCtrlTriBa
FlowCtrlForw
FlowCtrlBase
Unit: None
Actual Value
FlowCtrlTriBa
FlowCtrlBase
Default Value
FlowCtrlTriBa
FlowCtrlBase

9 Counters

Table 9-1 Counters

Counter ID Counter Name Counter Description Feature Feature Name
ID

1526726657 L.RRC.ConnReq.Msg Number of RRC Multi- RRC

connection setup mode: Connection
requests None Management
(retransmission GSM: RRC
included) None Connection
UMTS: Management
None
LTE:
LBFD-
002007
TDLBFD-
002007

1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of Multi- Basic

used uplink PRBs mode: Scheduling
None Basic
GSM: Scheduling
None Adaptive
UMTS: SFN/SDMA
None
LTE:
LBFD-
002025
TDLBFD-
002025
LOFD-
070205

1526727090 L.RRC.ReEst.HoFail.Att Number of RRC Multi- RRC

connection mode: Connection
reestablishment None Management
requests triggered by GSM: RRC
failed handovers None Connection
UMTS: Management
None
LTE:
LBFD-
002007
TDLBFD-
002007

1526727215 L.RA.GrpA.Att Number of times the Multi- Random

contention preamble in mode: Access
group A is received None Procedure
GSM: Random
None Access
UMTS: Procedure
None
Counter ID Counter Name Counter Description Feature Feature Name
ID

LTE:
LBFD-
002010
TDLBFD-
002010

1526727216 L.RA.GrpA.Resp Number of times a cell Multi- Random

sends a Random mode: Access
Access Response None Procedure
message after receiving GSM: Random
a preamble in group A None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727217 L.RA.GrpA.ContResolution Number of times a cell Multi- Random

sends a Contention mode: Access
Resolution message None Procedure
after receiving a GSM: Random
preamble in group A None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727218 L.RA.GrpB.Att Number of times the Multi- Random

contention preamble in mode: Access
group B is received None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727219 L.RA.GrpB.Resp Number of times a cell Multi- Random

sends a Random mode: Access
Access Response None Procedure
message after receiving
a preamble in group B
Counter ID Counter Name Counter Description Feature Feature Name
ID

GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727220 L.RA.GrpB.ContResolution Number of times a cell Multi- Random

sends a Contention mode: Access
Resolution message None Procedure
after receiving a GSM: Random
preamble in group B None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727221 L.RA.Dedicate.Att Number of times the Multi- Random

non-contention-based mode: Access
preamble is received None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727222 L.RA.Dedicate.HO.Att Number of times the Multi- Random

non-contention-based mode: Access
preamble is received None Procedure
(used in handover) GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526727223 L.RA.Dedicate.Resp Number of times the Multi- Random

Random Access mode: Access
Response message is None Procedure
sent after the non- GSM: Random
contention-based None Access
preamble is received UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727224 L.RA.Dedicate.HO.Resp Number of times the Multi- Random

Random Access mode: Access
Response message is None Procedure
sent after the non- GSM: Random
contention-based None Access
preamble is received UMTS: Procedure
(used in handover) None
LTE:
LBFD-
002010
TDLBFD-
002010

1526727225 L.RA.Dedicate.HO.Msg3Rcv Number of times the UE Multi- Random

Msg3 Response mode: Access
message is received in None Procedure
the handover-triggered GSM: Random
non-contention-based None Access
RA procedure UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728259 L.Thrp.bits.UL Total uplink traffic Multi- Radio

volume for PDCP PDUs mode: Bearer
in a cell None Management
GSM: Radio
None Bearer
UMTS: Management
None Basic
LTE: Scheduling
LBFD- Basic
002008 Scheduling
Counter ID Counter Name Counter Description Feature Feature Name
ID

TDLBFD-
002008
LBFD-
002025
TDLBFD-
002025

1526728260 L.Thrp.Time.UL Total receive duration of Multi- Radio

uplink PDCP PDUs in a mode: Bearer
cell None Management
GSM: Radio
None Bearer
UMTS: Management
None Basic
LTE: Scheduling
LBFD- Basic
002008 Scheduling
TDLBFD-
002008
LBFD-
002025
TDLBFD-
002025

1526728434 L.ChMeas.PRB.UL.Avail Number of available Multi- GSM and

uplink PRBs mode: LTE FDD
MRFD- Dynamic
090202 Spectrum
GSM: Sharing(LTE
None FDD)
UMTS: LTE-A
None Introduction
LTE: Carrier
LAOFD- Aggregation
001001 for Downlink
LAOFD- 2CC in
001002 40MHz
LOFD- Adaptive
070205 SFN/SDMA
TDLOFD- SFN
001075

1526728913 L.RA.PreambleSentNum1 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 1 None Procedure
time GSM: Random
None Access
UMTS: Procedure
None
Counter ID Counter Name Counter Description Feature Feature Name
ID

LTE:
LBFD-
002010
TDLBFD-
002010

1526728914 L.RA.PreambleSentNum2 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 2 None Procedure
times GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728915 L.RA.PreambleSentNum3 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 3 None Procedure
times GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728916 L.RA.PreambleSentNum4 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 4 None Procedure
times GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728917 L.RA.PreambleSentNum5or6 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 5 None Procedure
or 6 times
Counter ID Counter Name Counter Description Feature Feature Name
ID

GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728918 L.RA.PreambleSentNum7or8 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 7 None Procedure
or 8 times GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728919 L.RA.PreambleSentNum9or10 Number of random Multi- Random

access procedures with mode: Access
the preamble sent by 9 None Procedure
or 10 times GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728920 L.RA.UeRaInfoRsp.Num Number of received Multi- Random

UEInformationResponse mode: Access
messages containing None Procedure
RACH information GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526728921 L.RA.UeRaInfoRspWithCon.Num Number of received Multi- Random

UEInformationResponse mode: Access
messages whose None Procedure
"contentionDetected" is GSM: Random
TRUE None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728932 L.RA.GrpAandB.Att.Max Maximum number of Multi- Random

times a contention- mode: Access
based preamble is None Procedure
received GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728937 L.RA.Dedicate.PreambleReq.Num Number of times the Multi- Random

non-contention-based mode: Access
preamble is requested None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728938 L.RA.Dedicate.PreambleReq.Num.Max Maximum number of Multi- Random

times the non- mode: Access
contention-based None Procedure
preamble is requested GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

TDLBFD-
002010

1526728939 L.RA.Dedicate.PreambleAssign.Num Number of times the Multi- Random

non-contention-based mode: Access
preamble is assigned None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728954 L.RA.GrpA.ContResolution.PDCCH Number of times the Multi- Random

Contention Resolution mode: Access
message is sent on the None Procedure
PDCCH after the GSM: Random
contention-based None Access
preamble in group A is UMTS: Procedure
received None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728955 L.RA.GrpB.ContResolution.PDCCH Number of times the Multi- Random

Contention Resolution mode: Access
message is sent on the None Procedure
PDCCH after the GSM: Random
contention-based None Access
preamble in group B is UMTS: Procedure
received None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728956 L.RA.TA.UE.Index0 Number of times the TA Multi- Random

value is within index 0 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
Counter ID Counter Name Counter Description Feature Feature Name
ID

LTE:
LBFD-
002010
TDLBFD-
002010

1526728957 L.RA.TA.UE.Index1 Number of times the TA Multi- Random

value is within index 1 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728958 L.RA.TA.UE.Index2 Number of times the TA Multi- Random

value is within index 2 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728959 L.RA.TA.UE.Index3 Number of times the TA Multi- Random

value is within index 3 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728960 L.RA.TA.UE.Index4 Number of times the TA Multi- Random

value is within index 4 in mode: Access
a UE-initiated random None Procedure
access procedure
Counter ID Counter Name Counter Description Feature Feature Name
ID

GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728961 L.RA.TA.UE.Index5 Number of times the TA Multi- Random

value is within index 5 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728962 L.RA.TA.UE.Index6 Number of times the TA Multi- Random

value is within index 6 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728963 L.RA.TA.UE.Index7 Number of times the TA Multi- Random

value is within index 7 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526728964 L.RA.TA.UE.Index8 Number of times the TA Multi- Random

value is within index 8 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728965 L.RA.TA.UE.Index9 Number of times the TA Multi- Random

value is within index 9 in mode: Access
a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728966 L.RA.TA.UE.Index10 Number of times the TA Multi- Random

value is within index 10 mode: Access
in a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526728967 L.RA.TA.UE.Index11 Number of times the TA Multi- Random

value is within index 11 mode: Access
in a UE-initiated random None Procedure
access procedure GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

TDLBFD-
002010

1526728975 L.Traffic.ActiveUser.Avg Average number of Multi- RRC

activated UEs mode: Connection
None Management
GSM: RRC
None Connection
UMTS: Management
None
LTE:
LBFD-
002007
TDLBFD-
002007

1526730874 L.RA.GrpA.Disc.ByTA.Num Number of times that Multi- RACH

the contention-based mode: Optimization
preamble in group A is None
discarded based on the GSM:
TA None
UMTS:
None
LTE:
LOFD-
002015

1526730875 L.RA.GrpB.Disc.ByTA.Num Number of times that Multi- RACH

the contention-based mode: Optimization
preamble in group B is None
discarded based on the GSM:
TA None
UMTS:
None
LTE:
LOFD-
002015

1526732697 L.ChMeas.PRB.PUSCH.Util.Samp.Index0 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 0 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
Counter ID Counter Name Counter Description Feature Feature Name
ID

LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732698 L.ChMeas.PRB.PUSCH.Util.Samp.Index1 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 1 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732699 L.ChMeas.PRB.PUSCH.Util.Samp.Index2 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 2 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526732700 L.ChMeas.PRB.PUSCH.Util.Samp.Index3 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 3 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732701 L.ChMeas.PRB.PUSCH.Util.Samp.Index4 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 4 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732702 L.ChMeas.PRB.PUSCH.Util.Samp.Index5 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 5 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
Counter ID Counter Name Counter Description Feature Feature Name
ID

LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732703 L.ChMeas.PRB.PUSCH.Util.Samp.Index6 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 6 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732704 L.ChMeas.PRB.PUSCH.Util.Samp.Index7 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 7 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526732705 L.ChMeas.PRB.PUSCH.Util.Samp.Index8 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 8 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526732706 L.ChMeas.PRB.PUSCH.Util.Samp.Index9 Number of samples with Multi- LTE-A

the PUSCH PRB usage mode: Introduction
ranging within index 9 None Carrier
GSM: Aggregation
None for Downlink
UMTS: 2CC in
None 40MHz
LTE: SFN
LAOFD- Basic
001001 Scheduling
LAOFD- Basic
001002 Scheduling
TDLOFD-
001075
LBFD-
002025
TDLBFD-
002025

1526739722 L.RA.Dedicate.PreambleReq.HO.Num Number of times the Multi- Random

non-contention-based mode: Access
preamble is requested None Procedure
based on a handover GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

TDLBFD-
002010

1526739723 L.RA.Dedicate.PreambleAssign.HO.Num Number of times the Multi- Random

non-contention-based mode: Access
preamble is assigned None Procedure
based on a handover GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526739751 L.RA.Dedicate.Msg3Rcv Number of times the UE Multi- Random

Msg3 Response mode: Access
messages are received None Procedure
in non-contention-based GSM: Random
random access None Access
procedures UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742171 L.RRC.SetupFail.Rej.ForbidAc Number of times the Multi- RACH

eNodeB sends RRC mode: Optimization
Connection Reject None
messages because the GSM:
distance between UEs None
access the cell out of UMTS:
the coverage area None
LTE:
LOFD-
002015

1526742172 L.RA.GrpA.Initial Number of times initially Multi- Random

transmitted contention- mode: Access
based preambles in None Procedure
group A are received GSM: Random
None Access
UMTS: Procedure
None
Counter ID Counter Name Counter Description Feature Feature Name
ID

LTE:
LBFD-
002010
TDLBFD-
002010

1526742173 L.RA.GrpB.Initial Number of times initially Multi- Random

transmitted contention- mode: Access
based preambles in None Procedure
group B are received GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742174 L.RA.GrpA.Initial.Resp Number of Random Multi- Random

Access Response mode: Access
messages that a cell None Procedure
sends after receiving GSM: Random
initially transmitted None Access
contention-based UMTS: Procedure
preambles in group A None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742175 L.RA.GrpB.Initial.Resp Number of Random Multi- Random

Access Response mode: Access
messages that a cell None Procedure
sends after receiving GSM: Random
initially transmitted None Access
contention-based UMTS: Procedure
preambles in group B None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742176 L.RA.Dedicate.Initial Number of times initially Multi- Random

transmitted non- mode: Access
contention-based None Procedure
preambles are received
Counter ID Counter Name Counter Description Feature Feature Name
ID

GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742177 L.RA.Dedicate.HO.Initial Number of times initially Multi- Random

transmitted handover- mode: Access
induced non-contention- None Procedure
based preambles are GSM: Random
received None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742178 L.RA.Dedicate.Initial.Resp Number of Random Multi- Random

Access Response mode: Access
messages that a cell None Procedure
sends after receiving GSM: Random
initially transmitted non- None Access
contention-based UMTS: Procedure
preambles None
LTE:
LBFD-
002010
TDLBFD-
002010

1526742179 L.RA.Dedicate.HO.Initial.Resp Number of Random Multi- Random

Access Response mode: Access
messages that a cell None Procedure
sends after receiving GSM: Random
handover-induced None Access
initially transmitted non- UMTS: Procedure
contention-based None
preambles
LTE:
LBFD-
002010
TDLBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

1526745739 L.TA.UE.Index0 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 0 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745740 L.TA.UE.Index1 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 1 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745741 L.TA.UE.Index2 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 2 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745742 L.TA.UE.Index3 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 3 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
Counter ID Counter Name Counter Description Feature Feature Name
ID

TDLBFD-
002010

1526745743 L.TA.UE.Index4 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 4 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745744 L.TA.UE.Index5 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 5 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745745 L.TA.UE.Index6 Number of times UE TA Multi- Random

values fall into the range mode: Access
of index 6 None Procedure
GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745746 L.RA.ExceedRadiusContention.Access.Num Number of contention- Multi- Random

based exceeding-cell- mode: Access
radius accesses None Procedure
GSM: Random
None Access
UMTS: Procedure
None
 Counter ID Counter Name Counter Description Feature Feature Name
ID

LTE:
LBFD-
002010
TDLBFD-
002010

1526745747 L.RA.ExceedRadiusContention.Preamble.Num Number of contention- Multi- Random

based exceeding-cell- mode: Access
radius preamble None Procedure
receptions GSM: Random
None Access
UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

1526745748 L.RA.ExceedRadiusContention.Resp Number of times a cell Multi- Random

sends Random Access mode: Access
Response messages None Procedure
after contention-based GSM: Random
exceeding-cell-radius None Access
preamble receptions UMTS: Procedure
None
LTE:
LBFD-
002010
TDLBFD-
002010

10 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

11 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"