RACH Optimization (ERAN6.0 04)

eRAN
RACH Optimization Feature

Parameter Description
Issue 04
Date 2013-10-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. 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
Issue 04 (2013-10-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
RACH Optimization Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Overview.........................................................................................................................................4
2.1 Introduction....................................................................................................................................................................4
2.2 Benefits...........................................................................................................................................................................4
2.3 Architecture....................................................................................................................................................................5
3 Key Technologies..........................................................................................................................6
4 Related Features.............................................................................................................................9
5 Network Impact...........................................................................................................................10
6 Engineering Guidelines.............................................................................................................13
6.1 When to Use RACH Optimization...............................................................................................................................13
6.2 Required Information...................................................................................................................................................13
6.3 Planning........................................................................................................................................................................14
6.4 Overall Deployment Procedure....................................................................................................................................14
6.5 Deployment..................................................................................................................................................................14
6.5.1 Process.......................................................................................................................................................................14
6.5.2 Requirements.............................................................................................................................................................14
6.5.3 Data Preparation........................................................................................................................................................15
6.5.4 Activation..................................................................................................................................................................18
6.5.5 Commissioning..........................................................................................................................................................20
6.5.6 Activation Observation..............................................................................................................................................21
6.5.7 Reconfiguration.........................................................................................................................................................21
6.5.8 Deactivation...............................................................................................................................................................21
6.6 Performance Monitoring...............................................................................................................................................22
6.7 Parameter Optimization................................................................................................................................................23
6.8 Troubleshooting............................................................................................................................................................23
6.8.1 Fault 1........................................................................................................................................................................23
6.8.2 Fault 2........................................................................................................................................................................24
Issue 04 (2013-10-30) Huawei Proprietary and Confidential ii

eRAN
RACH Optimization Feature Parameter Description Contents
7 Parameters.....................................................................................................................................25
8 Counters........................................................................................................................................28
9 Glossary.........................................................................................................................................29
10 Reference Documents...............................................................................................................30
Issue 04 (2013-10-30) Huawei Proprietary and Confidential iii

eRAN
RACH Optimization Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes LOFD-002015 RACH Optimization, including its technical principles,
related features, network impact, and engineering guidelines.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
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:
l Need to understand the features described herein

l 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, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
eRAN6.0 04 (2013-10-30)
This issue includes the following changes.
Issue 04 (2013-10-30) Huawei Proprietary and Confidential 1

eRAN
Change Type Change Description Parameter Change
Feature change None None
Editorial change Revised the following sections: None

l 6.1 When to Use RACH Optimization
l 6.5.2 Requirements
l 6.5.3 Data Preparation
l 6.5.6 Activation Observation
eRAN6.0 03 (2013-08-30)
Change Type Change Description Parameter

Change
Feature change Deleted the adaptive backoff function. None
Editorial change Added MML command examples. For details, see None
6.5.4 Activation and 6.5.8 Deactivation.
eRAN6.0 02 (2013-06-30)

Change
Editorial change Revised the description about when to use RACH None
optimization. For details, see 6.1 When to Use RACH
Optimization.
eRAN6.0 01 (2013-04-28)
This issue does not include any changes.
eRAN6.0 Draft A (2013-01-30)

Compared with Issue 02 (2012-12-29) of eRAN3.0, Draft A (2013-01-30) of eRAN6.0 includes
the following changes.

eRAN

Change
Editorial change Revised the descriptions of activation and None

deactivation. For details, see 6.5.4 Activation and
6.5.8 Deactivation.

eRAN
RACH Optimization Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
RACH optimization is implemented mainly through RACH resource adjustment. The
adjustment does not consider the maximum number of UEs that can be admitted per second.
RACH resources include a physical random access channel (PRACH) configuration index and
random access preambles:
l PRACH configuration index

The PRACH configuration index indicates the number of PRACHs in each frame and the
subframe number of each PRACH.
l Random access preambles
Random access preambles in a cell are divided into random preambles and dedicated
preambles, which are used for contention-based random access and non-contention-based
random access, respectively.
RACH resources are configured semi-statically. When the traffic model changes, RACH
resources may not be able to accommodate the RACH load. RACH resources need to be adjusted
in scenarios such as:
l When the number of handover attempts increases, dedicated preambles may be insufficient
and UEs need to initiate contention-based random access, which increases handover delays.
l When the number of random access attempts increases, random preambles or PRACHs
may be insufficient and preamble collisions increase on PRACHs, which increases access
delays.
2.2 Benefits
The RACH resource adjustment function adaptively adjusts the PRACH configuration index
and preamble groups based on the RACH load in a cell. This matches the number of each type
of preambles and the number of PRACHs per second with the traffic model. As a result, this
function decreases access delays if the RACH load is high while also improving the efficiency
of RACH resources.

eRAN
RACH Optimization Feature Parameter Description 2 Overview
2.3 Architecture
RACH resource adjustment is implemented using the following modules:
l Cell-level RACH resource configuration module

This module adjusts the cell-level RACH resources, including the PRACH configuration
index and preamble groups.
l Random access module

eRAN
RACH Optimization Feature Parameter Description 3 Key Technologies
3 Key Technologies
PRACH Configuration Index and Preamble Groups

The PRACH configuration index indicates the number of PRACHs in each frame and the
subframe number of each PRACH. The protocol parameter that specifies the PRACH
configuration index is prach-ConfigurationIndex. For details about this parameter in FDD mode
and TDD mode, see chapter 5 "Uplink" in 3GPP TS 36.211 V10.3.0 (2011-09).
A cell can use a maximum of 64 random access preambles, with indexes of 0 to 63. These
preambles are divided into dedicated preambles and random preambles:
l Dedicated preambles
Dedicated preambles are used for non-contention-based random access. The indexes of
dedicated preambles range from numberOfRA-Preambles to 63. The default value of
numberOfRA-Preambles is 52.
l Random preambles
Random preambles are used for contention-based random access. Random preambles, with
indexes of 0 to (numberOfRA-Preambles 1), are further divided into group A and group
B:
The indexes of random preambles in group A range from 0 to (sizeOfRA-
PreamblesGroupA 1). The default value of sizeOfRA-PreamblesGroupA is 28.
The indexes of random preambles in group B range from sizeOfRA-
PreamblesGroupA to (numberOfRA-Preambles 1). If sizeOfRA-PreamblesGroupA is
equal to numberOfRA-Preambles, there is no group B.
Figure 3-1 shows the preamble groups.

eRAN
Figure 3-1 Preamble groups
For details about preamble group selection, see Connection Management Feature Parameter
Description.
If group B exists, the following information must be provided to UEs for preamble group
selection:
l messagePowerOffsetGroupB and RACHCfg.messageSizeGroupA

messagePowerOffsetGroupB is a power offset used by a UE to calculate the path loss
when determining whether to select group B. This variable is 10 dB by default.
RACHCfg.messageSizeGroupAis a threshold used by a UE to estimate the size of
Msg3 when determining whether to select group A. This parameter is configurable.
l Cell.UePowerMax
Cell.UePowerMax is the UE transmit power configured for performing the random access
procedure in the serving cell. The actual UE transmit power is equal to the smaller value
between Cell.UePowerMax and the maximum transmit power that the UE supports.
l deltaPreambleMsg3
deltaPreambleMsg3 is the offset between the preamble and Msg3. The default value is 8
dB.
Resource Adjustment
RACH resource adjustment consists of PRACH configuration index adjustment and preamble
group adjustment. The resource adjustment principles are as follows:
l If both dedicated preambles and access preambles are in surplus, the eNodeB decreases the
PRACH configuration index.
Whether dedicated preambles are in surplus is measured based on the number of unused
dedicated preambles detected within a period of time.
Whether random preambles are in surplus is measured based on the number of random
preambles detected within a period of time.
l If random preambles are insufficient, the eNodeB increases the PRACH configuration
index.
Whether random preambles are insufficient is measured based on the number of random
preambles detected within a period of time.

eRAN
l If dedicated preambles are in surplus and random preambles are insufficient, the eNodeB
reduces the number of dedicated preambles.
l If dedicated preambles are insufficient, the eNodeB increases the number of dedicated
preambles.
Whether dedicated preambles are insufficient is measured based on the dedicated preamble
allocation failure rate, which is equal to one minus the ratio of the number of UEs that are
allocated dedicated preambles to the number of UEs that apply for dedicated preambles.
If the PRACH configuration index or preamble groups change, the eNodeB sends the new
configuration through system information block type 2 (SIB2) to UEs, and the UEs use the new
configuration.
The RACH resource adjustment function can be enabled or disabled by setting

RachAdjSwitch under the CellAlgoSwitch.RachAlgoSwitch parameter.

eRAN
RACH Optimization Feature Parameter Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

eRAN
RACH Optimization Feature Parameter Description 5 Network Impact
5 Network Impact
System Capacity
RACH resource adjustment reduces RACH resource consumption and increases the uplink cell
capacity when the RACH load is low.
Network Performance
RACH resource adjustment adjusts the RACH resource configuration based on the RACH load
in the cell. When the RACH load is high, RACH resource adjustment allocates more RACH
resources to increase access success rates, reduce the probability of preamble collisions, and
shorten access delays.
NOTE
In eRAN6.0 and earlier versions, the probability of preamble collisions cannot be observed on the eNodeB
side.
Table 5-1 describes the impact on network performance in typical scenarios. In this table:
l a: contention-based load, equal to the number of contention-based random access attempts

per second
l b: non-contention-based load, equal to the number of non-contention-based random access
attempts per second
l Load ranges: calculated on the assumption that the random access times follow a poisson
distribution. The calculated load ranges are different from the actual load ranges and
therefore serve as examples only.

eRAN
Table 5-1 Impact on network performance in typical scenarios
Scenari System Load RACH Resource Impact

o Bandwidth Ranges Adjustment
(MHz)
1 5 or 10 a > 50 and Allocates more RACH Reduces the

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

b > 30 resources. probability of
preamble
collisions and
shortens access
delays.
3 15 or 20 a < 50 and Allocates less RACH Increases uplink

b < 30 resources. capacity.
The following explains the RACH resource adjustment described in Figure 5-1:
l Allocates more RACH resources.
The eNodeB shortens the PRACH interval. For example, the eNodeB changes the value of
RACHCfg.PrachConfigIndex from 3 to 6, that is, from 10 ms to 5 ms.
l Allocates less RACH resources.
The eNodeB prolongs the PRACH interval. For example, the eNodeB changes the value
of RACHCfg.PrachConfigIndex from 6 to 3.
l Increases the number of access preambles.
The eNodeB increases the value of numberOfRA-Preambles.
The RACH resource adjustment described in Table 5-1 is the initial adjustment. After that, the
eNodeB readjusts RACH resources based on load changes, as shown in Figure 5-1 and Figure
5-2.
Figure 5-1 Initial and subsequent RACH resource adjustments (for 5 or 10 MHz)

eRAN
Figure 5-2 Initial and subsequent RACH resource adjustments (for 15 or 20 MHz)

eRAN
RACH Optimization Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 When to Use RACH Optimization

For a system bandwidth of 5 or 10 MHz, the default PRACH occurrence interval is 10 ms; that
is, there is only one PRACH in each radio frame. In this case, RACH resource adjustment is
recommended when the contention-based load is greater than 50.
For a system bandwidth of 15 or 20 MHz, the default PRACH occurrence interval is 5 ms, that
is, there are two PRACHs in each radio frame. In this case, RACH resource adjustment is
recommended only when the contention-based load and non-contention-based load are less than
50 and, 30 respectively.
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.
6.2 Required Information

Collect information of the counters listed in Table 6-1 before deploying RACH resource
adjustment.
The following formulas hold true:
l Contention access load = (L.RA.GrpA.Att + L.RA.GrpB.At)/CounterTime

l Probability of falsely detecting preambles = (L.RA.GrpA.Att + L.RA.GrpB.Att +
L.RA.Dedicate.HO.Att L.RA.GrpA.ContResolution L.RA.GrpB.ContResolution
L.RA.Dedicate.HO.Msg3Rcv)/(CounterTime/PRACHPeriod)
In the preceding formulas:
l CounterTime indicates the time (in seconds) during which the probability of falsely
detecting preambles is measured.
l PRACHPeriod indicates the PRACH occurrence interval (in seconds). For example, if
PRACH Configuration Index is set to 6, two PRACHs are allocated in each radio frame
and therefore the PRACH occurrence interval is 5 ms, that is, 0.005s.

eRAN
Table 6-1 Counters to be collected
Counter ID Counter Name
1526727215 L.RA.GrpA.Att
1526727217 L.RA.GrpA.ContResolution
1526727218 L.RA.GrpB.Att
1526727220 L.RA.GrpB.ContResolution
1526727221 L.RA.Dedicate.Att
1526727222 L.RA.Dedicate.HO.Att
1526727225 L.RA.Dedicate.HO.Msg3Rcv
6.3 Planning
N/A
6.4 Overall Deployment Procedure

N/A
6.5 Deployment
6.5.1 Process
None
6.5.2 Requirements
Operating Environment
None
Transmission Networking
None
License
The operator has purchased and activated the license for the feature listed in Table 6-2.

eRAN
Table 6-2 License information for RACH optimization
Feature ID Feature Name License NE Sales Unit

Control Item
LOFD-002015 RACH RACH eNodeB per cell

Optimization Optimization
(FDD)
Other Requirements
Before deploying this feature, trace the RRC-SYS-INFO message over the Uu interface and
record the values of the IEs prach-ConfigIndex and preamblesGroupAConfig.
6.5.3 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for a
specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the evolved packet core (EPC) or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator
l User-defined: parameter values set by users.
Required Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
configure RACH resource adjustment.
Parameter Parameter ID Data Source Setting Notes

Name
Local cell ID CellAlgoSwitch. Network plan This parameter specifies the local ID
LocalCellId (negotiation not of the cell. It uniquely identifies a cell
required) within an eNodeB.
RACH CellAlgoSwitch. Network plan For details about how to set the
algorithm RachAlgoSwitch (negotiation not RachAdjSwitch check box, see 6.1
switch required) When to Use RACH Optimization.

eRAN
Scenario-specific Data
Name
Indication RACHCfg. Network plan If this parameter is set to NOT_CFG

of PRACH PrachConfigIn- (negotiation not (Not configure), you do not need to
Configurati dexCfgInd required) set RACHCfg.PrachConfigIn-
on Index dexCfgInd. The eNodeB will
adaptively set the PRACH
configuration index.
If this parameter is set to CFG
(Configure), the eNodeB does not
adaptively adjust RACH resources
regardless of the setting of the
RachAdjSwitch check box under
CellAlgoSwitch.RachAlgoSwitch.
To activate RACH resource
adjustment, set this parameter to
NOT_CFG(Not configure).

eRAN

Name
PRACH RACHCfg. Network plan Set this parameter if

Configurati PrachConfigInd (negotiation not RACHCfg.PrachConfigIndexCf-
on Index ex required) gInd is set to CFG(Configure).
The following provides suggestions
on parameter setting.
For an FDD cell and LBBPd board:
l Set this parameter to 0-8 or 15 for
preamble format 0.
l Set this parameter to 16-24 or 31
for preamble format 1.
For an FDD cell and LBBPc board:

a low-speed cell with preamble
format 0 and system bandwidth 15
MHz or 20 MHz.
a low-speed cell with preamble
format 0 and system bandwidth
less than or equal to10 MHz.
for a low-speed cell with preamble
format 1, system bandwidth 15
MHz or 20 MHz, and cell radius
less than or equal to 15,960 m.
format 1, system bandwidth 15
MHz or 20 MHz, and cell radius
greater than 15,960 m.
format 1 and system bandwidth
less than or equal to10 MHz.
format 2.
format 3.

eRAN

Name

a non-low-speed cell with
preamble format 0.
for a non-low-speed cell with
preamble format 1.
preamble format 2.
preamble format 3.
6.5.4 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 6-3 in a summary data file, which also contains
other data for the new eNodeBs to be deployed. Then, import the summary data file into the
Configuration Management Express (CME) for batch configuration. For detailed instructions,
see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 6-3 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 6-3 are not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 6-3 Parameters related to RACH optimization
MO Sheet in the Parameter Group Remarks

Summary Data
File
CellAlgoSwitch CellAlgoSwitch, Local cell ID, None

user-defined sheet RACH algorithm
switch

eRAN
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File, or choose Advanced >
Customize Summary Data File, to customize a summary data file for batch reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data, or choose LTE Application > Export Data > Export Base Station Bulk Configuration
Data, to export the eNodeB data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 6-3 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data, or choose LTE Application > Import Data > Import Base Station Bulk Configuration
Data, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management
> Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.
----End
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.

eRAN
Figure 6-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management
> Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.
----End
Using MML Commands

l Activating RACH resource adjustment
Run the MOD CELLALGOSWITCH command with the RachAdjSwitch check box
selected under the RACH algorithm switch parameter.
MML Command Examples

l Activating RACH resource adjustment
MOD CELLALGOSWITCH: LocalCellId=0,RachAlgoSwitch=RachAdjSwitch-1;
6.5.5 Commissioning
N/A

eRAN
6.5.6 Activation Observation

To verify whether RACH resource adjustment is activated, perform the following steps:
Step 1 On the M2000 client, start a Uu interface tracing task.
Step 2 After a UE accesses the network, trace the RRC-SYS-INFO message and observe the values of
the IEs prach-ConfigIndex and preamblesGroupAConfig, as shown in Figure 6-2.
If the values of both IEs change after the RACH resource adjustment function is used, RACH
resource adjustment has been activated.
Figure 6-2 RRC-SYS-INFO
----End
6.5.7 Reconfiguration
None
6.5.8 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for

eRAN
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 6-4.
Table 6-4 Parameters related to RACH optimization
MO Sheet in the Summary Parameter Setting Notes

Data File Group
CellAlgoS User-defined sheet. RachAlgoS Turn off the RachAdjSwitch.

witch The sheet name can be witch
CellAlgoSwitch.
Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 6-4. For detailed instructions, see Using the
CME to Perform Single Configuration for feature activation.
Using MML Commands

To deactivate RACH resource adjustment, run the MOD CELLALGOSWITCH command
with the RachAdjSwitch check box cleared under the RACH algorithm switch parameter.
MML Command Examples

l Deactivating RACH resource adjustment
MOD CELLALGOSWITCH: LocalCellId=0, RachAlgoSwitch=RachAdjSwitch-0;
6.6 Performance Monitoring

Items that reflect random access loads and performance are summarized in Table 6-5.
Table 6-5 Items that reflect random access loads and performance
Load or Formula Expected

Performance Item Value Range
Contention-based (L.RA.GrpA.Att + L.RA.GrpB.Att)/ -

load CounterTime
Probability of falsely (L.RA.GrpA.Att + L.RA.GrpB.Att + 1%

detecting preambles L.RA.Dedicate.HO.Att - L.RA.GrpA.ContReso-
lution - L.RA.GrpB.ContResolution -
L.RA.Dedicate.HO.Msg3Rcv)/(CounterTime/
PRACHPeriod)

eRAN
NOTE
l CounterTime indicates the total time interval during which related counters are measured. It is in units
of second.
l 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 occurrence period is 5 ms (that is, 0.005s).
For all performance counters related to RACH optimization, see Table 6-6.
Table 6-6 Performance counters related to various random access attempts and results
Counter ID Counter Name
1526727215 L.RA.GrpA.Att
1526727217 L.RA.GrpA.ContResolution
1526727218 L.RA.GrpB.Att
1526727220 L.RA.GrpB.ContResolution
1526727222 L.RA.Dedicate.HO.Att
1526727225 L.RA.Dedicate.HO.Msg3Rcv
6.7 Parameter Optimization

N/A
6.8 Troubleshooting
6.8.1 Fault 1
Fault Description
After one or both of RACH resource adjustment and PRACH false alarm detection are activated,
there are failures such as UE access or handover failures.
Fault Handling
Step 1 Check whether the cell status is normal by checking alarms such as ALM-29240 Cell
Unavailable or ALM-29243 Cell Capability Degraded. For details, see Cell Management
Feature Parameter Description.
Step 2 If the fault persists, contact Huawei technical support.
----End

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

eRAN
RACH Optimization Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
CellAlg RachAlg MOD LOFD-0 RACH Meaning:

oSwitch oSwitch CELLA 02015 / Optimiz RachAdjSwitch: Indicates the switch used to enable or
LGOSW TDLOF ation disable random access channel (RACH) resource
ITCH D-00201 adjustment, which adaptively adjusts the RACH
LST 5 resources in the cell based on the access type and the
CELLA number of accesses. If the switch is turned off, RACH
LGOSW resource adjustment is disabled.
ITCH HoRaSwitch: Indicates the switch used to control the
random access mode applied during handovers.
If the switch is turned on, the eNodeB instructs UEs to
use the non-contention-based random access mode
during handovers.
If the switch is turned off, the eNodeB instructs UEs to
use the contention-based random access mode during
handovers.
UnsyncRaSwitch: Indicates the switch used to control
the random access mode applied when UEs are out of
synchronization in the uplink.
If the switch is turned on, the eNodeB instructs UEs to
use the non-contention-based random access mode
upon DL data arrivals in the case of out-of-
synchronization.
If the switch is turned off, the eNodeB instructs UEs to
use the contention-based random access mode upon DL
data arrivals in the case of out-of-synchronization.
MaksIdxSwitch: Indicates the switch used to control
reuse of dedicated preambles between UEs.

eRAN

nd
If the switch is turned on, the eNodeB enables reuse of

dedicated preambles among UEs based on the
MaskIndex parameter.
If the switch is turned off, the eNodeB allocates a
dedicated preamble to only one UE at a time.
BackOffSwitch: Indicates the switch for backoff
control.
If the switch is turned on, backoff control is enabled.
If the switch is turned off, backoff control is disabled.
GUI Value Range: RachAdjSwitch(RachAdjSwitch),
HoRaSwitch(HoRaSwitch), UnsyncRaSwitch
(UnsyncRaSwitch), MaksIdxSwitch(MaksIdxSwitch),
BackOffSwitch(BackOffSwitch)
Unit: None
Actual Value Range: RachAdjSwitch, HoRaSwitch,
UnsyncRaSwitch, MaksIdxSwitch, BackOffSwitch
Default Value: RachAdjSwitch:Off, HoRaSwitch:On,
UnsyncRaSwitch:On, MaksIdxSwitch:Off,
BackOffSwitch:Off
RACHC Message MOD LBFD-0 Broadca Meaning:

fg SizeGro RACHC 02009 / st of Indicates the threshold for determining the size of Msg3
upA FG TDLBF system when a UE selects a preamble from random access
LST D-00200 informat preamble group A during a random access procedure.
RACHC 9 ion
For details, see 3GPP TS 36.321.
FG LBFD-0 Random
02010 / Access GUI Value Range: B56_MSG_SIZE_GROUPA
TDLBF Procedu (56bits), B144_MSG_SIZE_GROUPA(144bits),
D-00201 re B208_MSG_SIZE_GROUPA(208bits),
0 B256_MSG_SIZE_GROUPA(256bits)
Unit: bit
Actual Value Range: B56_MSG_SIZE_GROUPA,
B144_MSG_SIZE_GROUPA,
B208_MSG_SIZE_GROUPA,
B256_MSG_SIZE_GROUPA
Default Value: B56_MSG_SIZE_GROUPA(56bits)

eRAN

nd
Cell UePowe ADD LBFD-0 Uplink Meaning: Indicates the maximum transmit power that a
rMax CELL 02026 / Power UE can apply to uplink transmission in the cell. It is used
MOD TDLBF Control in cell selection criterion S to calculate the compensated
CELL D-00202 Broadca power. If the value of this parameter is not specified, the
6 st of maximum power is subject to the UE capability. For
LST details, see 3GPP TS 36.304.
CELL LBFD-0 system
02009 / informat GUI Value Range: -30~36
TDLBF ion Unit: dBm
D-00200
9 Actual Value Range: -30~36
Default Value: 23
RACHC PrachCo MOD LBFD-0 Broadca Meaning: Indicates whether to configure the PRACH
fg nfigInde RACHC 02009 / st of configuration index of the cell.
xCfgInd FG TDLBF system GUI Value Range: NOT_CFG(Not configure), CFG
LST D-00200 informat (Configure)
RACHC 9 ion
Unit: None
FG LOFD-0 RACH
02015 / Optimiz Actual Value Range: NOT_CFG, CFG
TDLOF ation Default Value: NOT_CFG(Not configure)
D-00201
5
RACHC PrachCo MOD LBFD-0 Broadca Meaning: Indicates the PRACH configuration index of
fg nfigInde RACHC 02009 / st of the cell. If cells are established on an LBBPc in a 4T4R
x FG TDLBF system scenario, the PRACH configuration indexes of different
LST D-00200 informat cells must be separated in the time domain.
RACHC 9 ion GUI Value Range: 0~63
FG LBFD-0 Random Unit: None
02010 / Access
TDLBF Procedu Actual Value Range: 0~63
D-00201 re Default Value: 3
0 RACH
LOFD-0 Optimiz
02015 / ation
TDLOF
D-00201
5

eRAN
RACH Optimization Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

eRAN
RACH Optimization Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
RACH Optimization Feature Parameter Description 10 Reference Documents
10 Reference Documents
1. 3GPP 36.211, "Physical channels and modulation"

2. 3GPP 36.321, "Medium Access Control (MAC) protocol specification"
3. 3GPP TS 36.331, "Radio Resource Control (RRC)"
4. 3GPP TS 36.141, "Performance requirements for PRACH"
5. Connection Management Feature Parameter Description


RACH Optimization (ERAN6.0 04)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RACH Optimization (ERAN6.0 04)

Încărcat de

Drepturi de autor:

Formate disponibile

eRAN

RACH Optimization Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2013-10-30) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue 04 (2013-10-30) Huawei Proprietary and Confidential ii

Issue 04 (2013-10-30) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 1

Change Type Change Description Parameter Change

Feature change None None

Editorial change Revised the following sections: None

Change Type Change Description Parameter

Feature change Deleted the adaptive backoff function. None

Change Type Change Description Parameter

Feature change None None

eRAN6.0 Draft A (2013-01-30)

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 2

Change Type Change Description Parameter

Feature change None None

Editorial change Revised the descriptions of activation and None

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 3

l PRACH configuration index

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 4

l Cell-level RACH resource configuration module

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 5

PRACH Configuration Index and Preamble Groups

Figure 3-1 shows the preamble groups.

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 6

Figure 3-1 Preamble groups

l messagePowerOffsetGroupB and RACHCfg.messageSizeGroupA

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 7

The RACH resource adjustment function can be enabled or disabled by setting

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 8

Mutually Exclusive Features

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 9

l a: contention-based load, equal to the number of contention-based random access attempts

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 10

Table 5-1 Impact on network performance in typical scenarios

Scenari System Load RACH Resource Impact

1 5 or 10 a > 50 and Allocates more RACH Reduces the

2 5 or 10 a > 50 and Allocates more RACH Reduces the

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

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 11

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 12

6.1 When to Use RACH Optimization

6.2 Required Information

The following formulas hold true:

l Contention access load = (L.RA.GrpA.Att + L.RA.GrpB.At)/CounterTime

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 13

Table 6-1 Counters to be collected

Counter ID Counter Name

6.4 Overall Deployment Procedure

Issue 04 (2013-10-30) Huawei Proprietary and Confidential 14

Table 6-2 License information for RACH optimization

Feature ID Feature Name License NE Sales Unit

LOFD-002015 RACH RACH eNodeB per cell

6.5.3 Data Preparation