Professional Documents
Culture Documents
eRAN3.0
Issue
01
Date
2012-03-30
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
Issue 01 (2012-03-30)
eRAN
RACH Optimization
1 Introduction
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.
Feature change: refers to a change in the RACH optimization feature of a specific product version.
Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.
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.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
None
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.
Issue 01 (2012-03-30)
1-1
eRAN
RACH Optimization
1 Introduction
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
None
Issue 01 (2012-03-30)
1-2
eRAN
RACH Optimization
Adaptive backoff
If multiple UEs use the same preamble to quickly initiate contention-based random access, continual
preamble collisions may occur. After a preamble collision occurs, only one UE can access the network
as usual, and the remaining UEs that use the same preamble must initiate random access again on
the same PRACH, which may lead to another preamble collision. Continual preamble collisions cause
extra access delays for UEs. UE is short for user equipment.
To solve this problem, 3GPP specifications introduce the adaptive backoff function. A backoff time is
specified for each UE that has experienced a preamble collision and failed the random access
procedure. A UE can initiate random access again using the same preamble at a random time point
within the specified backoff period. Adaptive backoff enables the eNodeB to specify the backoff period
for UEs based on the contention-based random access load. This function reduces both the
probability of continual preamble collisions and the access delays for UEs.
This document describes the optional feature LOFD-002015 RACH Optimization. For details about
random access procedures and basic concepts related to random access preambles, see the
Connection Management Feature Parameter Description.
Issue 01 (2012-03-30)
2-1
eRAN
RACH Optimization
Issue 01 (2012-03-30)
3-1
eRAN
RACH Optimization
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.
Issue 01 (2012-03-30)
3-2
eRAN
RACH Optimization
If preamble groups or PRACH configurations change, the eNodeB sends the new PRACH configuration
to the UE through system information block type 2 (SIB2). Then, the UE uses the new PRACH
configuration to optimize random access performance.
RachAdjSwitch under the RachAlgoSwitch parameter controls RACH resource adjustment.
Adaptive backoff enables the eNodeB to measure the average number of random access preambles.
The policies are as follows:
If the number changes slightly, the eNodeB does not change the backoff time.
Issue 01 (2012-03-30)
3-3
eRAN
RACH Optimization
4 Related Features
4 Related Features
4.1 Required Features
None
Issue 01 (2012-03-30)
4-1
eRAN
RACH Optimization
Issue 01 (2012-03-30)
5-1
eRAN
RACH Optimization
6 Engineering Guidelines
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.
RACH Optimization(FDD)
LLT1RAOP01
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."
Issue 01 (2012-03-30)
6-1
eRAN
RACH Optimization
6 Engineering Guidelines
Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
Network plan (negotiation not required): Parameters are planned and set by operators.
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.
Parameter
Name
Parameter ID
Source
Setting Description
Local cell
ID
CellAlgoSwit
ch.LocalCellI
d
Network plan
(negotiation not
required)
RACH
algorithm
switch
RachAlgoSwi
tch
Network plan
(negotiation not
required)
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:
Issue 01 (2012-03-30)
6-2
eRAN
RACH Optimization
6 Engineering Guidelines
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.
Parameter
CellAlgoSwit
ch
CellAlgoSwitch
6.5.5 Commissioning
N/A
Issue 01 (2012-03-30)
6-3
eRAN
RACH Optimization
6 Engineering Guidelines
---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
Issue 01 (2012-03-30)
6-4
eRAN
RACH Optimization
7 Parameters
7 Parameters
Table 7-1 Parameter description
MO
Parameter ID
CellAlgoSwitch LocalCellId
Feature Name
Description
None
LST
CELLALGOSWI
TCH
None
Meaning:Indicat
es the local ID of
the cell. It
uniquely
identifies a cell
within a BS.
MOD
CELLALGOSWI
TCH
GUI Value
Range:0~17
Unit:None
Actual Value
Range:0~17
Default
Value:None
CellAlgoSwitch RachAlgoSwitch MOD
LBFD-001001 / 3GPP R8
CELLALGOSWI TDLBFD-001001 Specifications
TCH
LBFD-002010 / Random Access
LST
TDLBFD-002010 Procedure
CELLALGOSWI
LOFD-002015 / RACH
TCH
TDLOFD-00201 Optimization
5
Meaning:RachA
djSwitch:
Indicates the
switch used to
enable or disable
random access
channel (RACH)
resource
adjustment,
which adaptively
adjusts the
RACH resources
in the cell based
on the access
type and the
number of
accesses. If the
switch is turned
off, RACH
resource
adjustment is
disabled.
HoRaSwitch:
Indicates the
switch used to
control the
random access
mode applied
during
handovers.
Issue 01 (2012-03-30)
7-1
eRAN
RACH Optimization
MO
Parameter ID
7 Parameters
Feature Name
Description
If the switch is
turned on, the
eNodeB instructs
UEs to use the
non-contention-b
ased random
access mode
during
handovers.
If the switch is
turned off, the
eNodeB instructs
UEs to use the
contention-base
d 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-b
ased random
access mode
upon DL data
arrivals in the
case of
out-of-synchroni
zation.
If the switch is
turned off, the
eNodeB instructs
UEs to use the
contention-base
d random access
mode upon DL
data arrivals in
the case of
out-of-synchroni
zation.
Issue 01 (2012-03-30)
7-2
eRAN
RACH Optimization
MO
Parameter ID
7 Parameters
Feature Name
Description
MaksIdxSwitch:
Indicates the
switch used to
control reuse of
dedicated
preambles
between UEs.
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:RachAdj
Switch(RachAdj
Switch),
HoRaSwitch(Ho
RaSwitch),
UnsyncRaSwitch
(UnsyncRaSwitc
h),
MaksIdxSwitch(
MaksIdxSwitch),
BackOffSwitch(B
Issue 01 (2012-03-30)
7-3
eRAN
RACH Optimization
MO
Parameter ID
7 Parameters
Feature Name
Description
ackOffSwitch)
Unit:None
Actual Value
Range:RachAdj
Switch,
HoRaSwitch,
UnsyncRaSwitch
, MaksIdxSwitch,
BackOffSwitch
Default
Value:RachAdjS
witch:Off,
HoRaSwitch:On,
UnsyncRaSwitch
:On,
MaksIdxSwitch:
Off,
BackOffSwitch:O
ff
Issue 01 (2012-03-30)
7-4
eRAN
RACH Optimization
8 Counters
8 Counters
There are no specific counters associated with this feature.
Issue 01 (2012-03-30)
8-1
eRAN
RACH Optimization
9 Glossary
9 Glossary
For acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2012-03-30)
9-1
eRAN
RACH Optimization
10 Reference Documents
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
Issue 01 (2012-03-30)
10-1