Professional Documents
Culture Documents
eRAN3.0
Feature Parameter Description
Issue 01
Date 2012-03-30
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 the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
eRAN
RACH Optimization Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
6 Engineering Guidelines...........................................................................................................6-1
6.1 When to Use RACH Optimization ................................................................................................. 6-1
6.2 Information to be Collected ........................................................................................................... 6-1
6.3 Network Planning .......................................................................................................................... 6-1
6.4 Overall Deployment Procedure ..................................................................................................... 6-1
6.5 Deploying RACH Optimization ...................................................................................................... 6-1
6.5.1 Deployment Procedure ......................................................................................................... 6-1
6.5.2 Deployment Requirements ................................................................................................... 6-1
6.5.3 Data Preparation................................................................................................................... 6-1
6.5.4 Activation .............................................................................................................................. 6-2
6.5.5 Commissioning ..................................................................................................................... 6-3
6.5.6 Activation Observation .......................................................................................................... 6-3
6.5.7 Reconfiguration .................................................................................................................... 6-4
6.5.8 Deactivation .......................................................................................................................... 6-4
6.6 Optimization .................................................................................................................................. 6-4
6.7 Troubleshooting ............................................................................................................................. 6-4
7 Parameters..................................................................................................................................7-1
8 Counters ......................................................................................................................................8-1
9 Glossary ......................................................................................................................................9-1
10 Reference Documents .........................................................................................................10-1
1 Introduction
1.1 Scope
This document describes the key techniques and engineering guidelines for random access channel
(RACH) optimization.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
Document Issues
The document issues are as follows:
01 (2012-03-30)
Draft A (2012-01-10)
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.
Draft A (2012-01-10)
This is the draft.
Compared with issue 02 (2011-11-30) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.
Table 3-1 Frame structure type 1 random access configuration for preamble formats 0-3
As listed in Table 3-1, the Subframe Number column specifies PRACH opportunities reserved for the
subframes of a radio frame in each PRACH configuration. For example, PRACH configuration index 7
specifies that random access preambles are transmitted at subframes 2 and 7 of each radio frame, and
PRACH configuration index 3 specifies that random access preambles are transmitted only at subframe
1 of each radio frame.
Based on the allocation of dedicated preambles, detection of random access preambles, and load on the
physical uplink shared channel (PUSCH), RACH optimization adaptively groups preambles and adjusts
PRACH configurations as follows:
Decreases the number of PRACH opportunities within each radio frame if the eNodeB receives a
small number of random access preambles and the PUSCH load is high. It will impact the uplink traffic
volume if
Increases the number of PRACH opportunities within each radio frame if the eNodeB receives a large
number of random access preambles and the PUSCH load is not high.
Decreases the number of dedicated preambles if there are sufficient dedicated preambles and the
eNodeB receives a large number of random access preambles.
Adaptive backoff enables the eNodeB to measure the average number of random access preambles.
The policies are as follows:
If the number is large, the eNodeB increases the backoff time.
If the number is small, the eNodeB decreases the backoff time.
If the number changes slightly, the eNodeB does not change the backoff time.
BackOffSwitch under the RachAlgoSwitch parameter controls adaptive backoff.
4 Related Features
4.1 Required Features
None
6 Engineering Guidelines
6.1 When to Use RACH Optimization
RACH optimization is recommended if operators require improvements in random access performance
in terms of the one-time random access success rate and access delay.
Other Requirements
Before deploying this feature, trace the SIB2 message over the Uu interface and record the values of the
IEs prach-ConfigIndex and preamblesGroupAConfig. For details about how to trace the message and
obtain the IE values, see section 6.5.6 "Activation Observation."
Generic Data
None
Scenario-specific Data
The following table describes the parameters that must be set in the CellAlgoSwitch managed object
(MO) to configure RACH resource adjustment and adaptive backoff.
6.5.4 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 6.5.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
6.5.5 Commissioning
N/A
---End
6.5.7 Reconfiguration
None
6.5.8 Deactivation
To deactivate RACH resource adjustment and adaptive backoff, run the MOD CELLALGOSWITCH
command with the RachAdjSwitch and BackOffSwitch check boxes cleared under the
RachAlgoSwitch parameter.
6.6 Optimization
None
6.7 Troubleshooting
None
7 Parameters
Table 7-1 Parameter description
MO Parameter ID MML Command Feature ID Feature Name Description
8 Counters
There are no specific counters associated with this feature.
9 Glossary
For acronyms, abbreviations, terms, and definitions, see the Glossary.
10 Reference Documents
This chapter lists the reference documents related to RACH optimization.
[1] 3GPP 36.211 "Physical channels and modulation"
[2] 3GPP 36.321 "Medium Access Control (MAC) protocol specification"
[3] eNodeB Performance Counter Reference
[4] eNodeB MO Reference
[5] Connection Management Feature Parameter Description
[6] eNodeB Initial Configuration Guide