High Speed Mobility (ERAN3.0 - 02)

High Speed Mobility
eRAN3.0
Feature Parameter Description
Issue 02
Date 2012-12-29
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 the 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
eRAN
High Speed Mobility Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 High Speed Mobility .................................................................................................................2-1

2.1 Doppler Shift .................................................................................................................................. 2-1
2.2 Automatic Frequency Control ........................................................................................................ 2-2
2.3 Random Access Preamble ............................................................................................................ 2-2
2.4 Scheduling ..................................................................................................................................... 2-3
3 Related Features .......................................................................................................................3-1

3.1 Required Features......................................................................................................................... 3-1
3.2 Mutually Exclusive Features ......................................................................................................... 3-1
3.3 Affected Features .......................................................................................................................... 3-1
4 Impact on the Network.............................................................................................................4-1

4.1 Impact on System Capacity........................................................................................................... 4-1
4.2 Impact on Network Performance................................................................................................... 4-1
5 Engineering Guidelines ...........................................................................................................5-1

5.1 When to Use High Speed Mobility................................................................................................. 5-1
5.2 Information to Be Collected ........................................................................................................... 5-1
5.3 Network Planning .......................................................................................................................... 5-1
5.3.1 RF Planning .......................................................................................................................... 5-1
5.3.2 Network Topology ................................................................................................................. 5-1
5.4 Deploying High Speed Mobility ..................................................................................................... 5-1
5.4.1 Deployment Requirements ................................................................................................... 5-1
5.4.2 Data Preparation................................................................................................................... 5-2
5.4.3 Initial Configuration ............................................................................................................... 5-5
5.4.4 Activation Observation .......................................................................................................... 5-6
5.4.5 Deactivation .......................................................................................................................... 5-7
5.5 Performance Optimization ............................................................................................................. 5-7
5.5.1 Monitoring ............................................................................................................................. 5-7
5.5.2 Parameter Optimization ........................................................................................................ 5-7
5.6 Troubleshooting ............................................................................................................................. 5-7
6 Parameters..................................................................................................................................6-1
7 Counters ......................................................................................................................................7-1
8 Glossary ......................................................................................................................................8-1
9 Reference Documents .............................................................................................................9-1
Issue 02 (2012-12-29) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
High Speed Mobility 1 Introduction
1 Introduction
1.1 Scope
This document describes the implementation of the high speed mobility feature in E-UTRAN NodeBs
(eNodeBs) and provides engineering guidelines for this feature.
High speed mobility refers to the mobile connections of UEs traveling at speeds of 120 km/h or higher.
UE refers to user equipment. In high speed scenarios, the eNodeB sustains the services on UEs and
ensures the service quality by using the automatic frequency control (AFC) function.
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.
1.2 Intended Audience

This document is intended for:
 Personnel who need to understand high speed mobility
 Personnel who work with Huawei Long Term Evolution (LTE) 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:
 Feature change: refers to a change in the high speed mobility 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:
 02 (2012-12-29)
 01 (2012-03-30)
 Draft A (2012-01-10)
02 (2012-12-29)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-12-29) of eRAN3.0 includes the
following changes.
Change Type Change Description Parameter Change

Feature change None None
Editorial change Added the frequency band supported in the ultra high None
speed mobility scenario in chapter 2 "High Speed
Mobility."
Revised chapter 4 "Impact on the Network."
Issue 02 (2012-12-29) Huawei Proprietary and Confidential 1-1

eRAN
High Speed Mobility 1 Introduction

Revised the application scenarios of high speed
mobility and ultra high speed mobility and the root
sequence index configurations in the two scenarios in
chapter 5 "Engineering Guidelines."
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.

Editorial change Revised chapter 5 "Engineering Guidelines." None
Draft A (2012-01-10)
This is a draft.
Compared with issue 02 (2011-09-30) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.

Editorial change Added chapter 3 "Related Features" and chapter 4 None
"Impact on the Network."

eRAN
High Speed Mobility 2 High Speed Mobility
2 High Speed Mobility

In the LTE system, subcarriers are closely spaced. Therefore, the LTE system is prone to Doppler shifts.
High speed movement of UEs causes great Doppler shifts, which affect the orthogonality between
subcarriers and therefore degrades system performance. To minimize the impact of Doppler shifts and
meet performance requirements in high speed scenarios, Huawei eNodeBs perform AFC in response to
frequency changes and adjust the scheduling mode.
Huawei eNodeBs support high speed mobility in two scenarios:
 High speed mobility. In this scenario, eNodeBs can provide satisfactory network performance for UEs
moving at 120 km/h.
 Ultra high speed mobility. In this scenario, eNodeBs can provide satisfactory network performance for
UEs working in 1 GHz or lower frequency band and moving at 350 km/h to 450 km/h. The performance
of ultra high speed mobility can be ensured only when there is no obstacle between UEs and
eNodeBs.
Throughout this document, the cells in the two scenarios are referred to as high speed cells and ultra
high speed cells.
This document describes the following optional features:
 LOFD-001007 High Speed Mobility
 LOFD-001008 Ultra High Speed Mobility
Unless otherwise specified, the descriptions in this document are for the two optional features.
2.1 Doppler Shift

When there is relative movement between a UE and an eNodeB, the frequency on which the UE
receives data is different from the frequency on which the eNodeB transmits data. Such a change is due
to Doppler shift. It can be calculated according to the following formula:
fd = f0/C x v x cosθ
where
 fd is the Doppler shift.
 f0 is the carrier frequency.
 C is the speed at which electromagnetic waves propagate.
 v is the velocity at which the UE moves.
 θ is the angle between the direction in which the UE moves relative to the eNodeB and the direction
in which the eNodeB transmits signals.
As indicated by the preceding formula, the amount of Doppler shift increases with the velocity of the UE
relative to the eNodeB. The Doppler shift may extend the receive frequency band or change the receive
frequency, and therefore causes interference within and between Orthogonal Frequency Division
Multiplexing (OFDM) symbols. A larger amount of Doppler shift causes severer interference. In severe
cases, the receiver fails to demodulate data even if the signal-to-noise ratio is high on channels. As a
result, the UE fails to access the network.
Figure 2-1 shows an example of Doppler shift. In this example, f0 is the center of the transmit frequency
of the eNodeB. If the UE moves away from the eNodeB, the receive frequency of the UE is f0 – fd. The
UE synchronizes its local oscillator with the receive frequency and transmits signals to the eNodeB at the
frequency of this local oscillator. Then, the eNodeB receives the signals from the UE at the frequency of

eRAN
f0 – 2fd. If the UE moves towards the eNodeB, the receive frequency of the UE is f0 + fd and that of the
eNodeB is f0 + 2fd.
Figure 2-1 Doppler shift
2.2 Automatic Frequency Control

To reduce the impact of Doppler shift, Huawei eNodeBs use AFC in ultra high speed (LOFD-001008)
scenarios. A cell can be set as an ultra high speed cell through the Cell.HighSpeedFlag parameter. The
functions of AFC are as follows:
 Initial frequency correction
During random access of UEs, an eNodeB detects frequency changes by using preambles and
performs initial frequency correction. After initial frequency correction completes, UEs can transmit
access signaling on the physical uplink shared channel (PUSCH).
 Continuous frequency correction
The eNodeB performs continuous frequency correction after UEs access the network. The eNodeB
estimates frequency changes based on pilot signals of the UEs and uses the results as the continuous
inputs to the frequency correction function.
Figure 2-2 shows how the AFC function works. Initial frequency correction is a coarse
adjustment whereas continuous frequency correction is fine-tuning. When a UE that has accessed the
network experiences a sudden change in channels, fine-tuning may fail to trace the frequency change.
This may result in consecutive failures to decode uplink data. In this case, a Huawei eNodeB searches
for the frequency change to ensure correct demodulation and decoding of uplink data.
Figure 2-2 Functionality of AFC
2.3 Random Access Preamble

A random access preamble sequence is defined by a root Zadoff-Chu (ZC) sequence and cyclic shift
sequences. The logical index to a root ZC sequence is specified by the Cell.RootSequenceIdx
parameter. For details about the Cell.RootSequenceIdx parameter, see Connection Management
Feature Parameter Description. High and low speed cells use different NCS values (NCS represents the
number of cyclic shifts), based on which limitations are applied to logical indexes. For details, see
section 5.7.2 in 3GPP TS 36.211.

eRAN
2.4 Scheduling
In high speed scenarios, both frequency-selective scheduling and semi-persistent scheduling are not
applied. The reasons are as follows:
 Frequency-selective scheduling requires better channel quality on one subcarrier than on others for a
period of time. When a UE moves at high speed, the quality of channels within the cell bandwidth
changes rapidly with time, and therefore no subcarrier has an outstanding channel quality for a period
of time.
 Semi-persistent scheduling requires that the scheduled resources be retained for a period of
time, which is not suitable in high speed scenarios.
Because frequency-selective scheduling is not applied, full-band channel quality indicator (CQI)
reporting rather than sub-band CQI reporting is used in high speed scenarios. The CQI reporting interval
depends on the channel variations of the UE with time. In high speed scenarios, however, shortening the
CQI reporting interval cannot help the eNodeB to trace channel variations faster. In addition, a short
interval may result in high occupancy of physical uplink control channel (PUCCH) resources. Therefore,
UEs in high speed mobility report CQIs at a fixed interval.
If a cell has more than one transmit antenna, the transmission mode on the radio interface can be set to
open- or closed-loop multiple-input multiple-output (MIMO). In closed-loop MIMO mode, the transmitter
performs precoding on signals based on the prior information about channels. If the prior information is
reliable and the associated precoding is valid, the closed-loop MIMO mode can provide much better
performance than the open-loop MIMO mode. However, the prior information is reliable and the
associated precoding is accurate only in low speed cells. If the prior information is insufficient, feedback
overhead is required in closed-loop MIMO mode. In addition, if the associated precoding does not
accurately reflect channel conditions, closed-loop MIMO may result in more costs than benefits.
Therefore, open-loop MIMO is recommended for Huawei eNodeBs in the high and ultra high speed
mobility scenarios. For details about MIMO, see MIMO Feature Parameter Description.

eRAN
High Speed Mobility 3 Related Features
3 Related Features
3.1 Required Features
None
3.2 Mutually Exclusive Features

In ultra high speed cells, semi-persistent scheduling and frequency selective scheduling are not
supported.
3.3 Affected Features

In high speed cells, it is recommended that semi-persistent scheduling and frequency selective
scheduling be disabled.
In ultra high speed cells, it is recommended that you disable physical downlink control channel (PDCCH)
symbol adaptation and that the PDCCH always occupy three symbols to improve PDCCH demodulation
performance. If more than one antenna is used in a cell, use transmission mode 2 in the cell to improve
the transmission reliability of the physical downlink shared channel (PDSCH). For details about PDCCH
symbol adaptation, see Physical Channel Resource Management Feature Parameter Description.

eRAN
High Speed Mobility 4 Impact on the Network
4 Impact on the Network

4.1 Impact on System Capacity
Compared with a low speed cell, a high speed cell or an ultra high speed cell has less measurement
accuracy and more inter-subcarrier interference caused by Doppler shift. This decreases system
capacity and even results in improper system operation. This feature is introduced to increase system
capacity and ensure proper system operation.
4.2 Impact on Network Performance

Compared with a low speed cell, a high speed cell or an ultra high speed cell has less measurement
accuracy and more inter-subcarrier interference caused by Doppler shift. This decreases the handover
success rate, increases the service drop rate, and even results in improper system operation. This
feature is introduced to increase network key performance indicators (KPIs) and ensure proper system
operation.

eRAN
High Speed Mobility 5 Engineering Guidelines
5 Engineering Guidelines
This chapter provides engineering guidelines for high speed mobility.
5.1 When to Use High Speed Mobility

The high speed mobility and ultra high speed mobility features are optional. The Cell.HighSpeedFlag
parameter specifies whether a cell is an ultra high speed, high speed, or low speed cell.
The recommended settings for a cell are as follows:
 If the cell covers high speed railways with UEs working in high frequency band (2.6 GHz) and moving
at 350 to 450 km/h, set it as an ultra high speed cell.
 If the cell covers high speed railways with UEs working in low frequency band (1 GHz or lower) and
moving at 350 to 450 km/h, set it as a high speed cell.
 If the cell covers highways and surrounding areas, set it as a high speed cell.
 In other scenarios, set it as a low speed cell.
NOTE
The value EXTRA_HIGH_SPEED(Extra high speed cell flag) of the Cell.HighSpeedFlag parameter is reserved for
future use. It is invalid in this version. The following sections do not describe this value.
5.2 Information to Be Collected

N/A
5.3 Network Planning

5.3.1 RF Planning
The relationship between the root sequence index and the cell radius for high speed cells and ultra high
speed cells involves limitations. Therefore, to ensure the use of different root sequence indexes for
cells whose coverage areas overlap, you must plan available root sequence indexes based on the cell
radius.
5.3.2 Network Topology

If the network covers high speed railways and highways, high speed mobility and ultra high speed
mobility features can be enabled to ensure satisfactory UE performance in the cells. During network
planning, ensure that the cells can directly cover high speed railways and highways. To ensure
satisfactory cell performance, very few deep-fading areas should exist that cannot be directly covered by
these cells.
5.4 Deploying High Speed Mobility

5.4.1 Deployment Requirements
Requirements for Other Functions
It is recommended that functions and parameters related to high speed mobility be set as follows:
 Frequency-selective scheduling is not supported by ultra high speed cells and not recommended for
high speed cells.
 Semi-persistent scheduling is not supported by ultra high speed cells and not recommended for high
speed cells.

eRAN
 Set the CellPdcchAlgo.PdcchSymNumSwitch parameter to OFF(Off) and the

CellPdcchAlgo.InitPdcchSymNum parameter to 3 for ultra high speed cells.
 Set the MimoAdaptiveParaCfg.MimoAdaptiveSwitch parameter to
NO_ADAPTIVE(NO_ADAPTIVE) and the MimoAdaptiveParaCfg.FixedMimoMode parameter to
TM2(TM2) by running the MOD MIMOADAPTIVEPARACFG command for high and ultra high speed
cells. For details about MIMO, see MIMO Feature Parameter Description.
Requirements for the Operating Environment

None
Requirements for Transmission Networking

None
Requirements for Licenses

Operators must purchase and activate the following licenses.
Feature License Control Item Name

LOFD-001007 High Speed Mobility High Speed Mobility(per Cell)(FDD)
LOFD-001008 Ultra High Speed Mobility Ultra High Speed Mobility(per Cell)(FDD)
5.4.2 Data Preparation

Generic Data
N/A
Scenario-specific Data
Scenario 1: High Speed Railways with High Frequency Band
The following table describes the parameters that must be set in a Cell managed object (MO) to
configure an ultra high speed cell.
Parameter Parameter ID Source Setting Description

Name
Local cell Cell.LocalCellId Network Set this parameter based on the network plan. This
identity plan parameter specifies the local ID of a cell.
(negotiation
not
required)
Root Cell.RootSequenc Network This parameter specifies the logical root sequence, which
sequence eIdx plan is used to generate the preamble sequence. Each logical
index (negotiation root sequence corresponds to a physical root sequence.
not For the mapping between logical root sequences and
required) physical root sequences, see 3GPP TS 36.211.
The following constraints are imposed on the parameter
(The following value ranges of root sequence index are
the maximum ones specified by the network plan. The
value range of root sequence index for each cell needs to

eRAN

Name
be planned manually or using a dedicated tool):
 If the Cell.FddTddInd parameter is set to
CELL_TDD(TDD) and the Cell.PreambleFmt
parameter is set to 4, this parameter must be set to a
value less than or equal to 137.
 If the value of the Cell.PreambleFmt parameter is less
than 4 and the Cell.HighSpeedFlag parameter is set to
HIGH_SPEED(High speed cell flag), the cell radius
cannot be greater than 32,800 m:
−1 m ≤ Cell radius ≤ 1000 m: The value of root
sequence index must be within the range of 24 to 815.
− 1000m < Cell radius ≤ 1500 m: The value of root
sequence index must be within the range of 116 to
731.
− 8600m < Cell radius ≤ 10,600 m: The value of root
706.
− 10,600
m < Cell radius ≤ 13,200 m: The value of root
676.
− 13,200
602.
− 17,200
566.
− 21,500
498.
− 27,800
450.

eRAN

Name
 If the value of the Cell.PreambleFmt parameter is less
than 4 and the Cell.HighSpeedFlag parameter is set to
ULTRA_HIGH_SPEED(Ultra high speed cell flag), the
cell radius cannot be greater than 17,200 m:
−1 m ≤ Cell radius ≤ 1000 m: The value of root
sequence index must be within the ranges of 24 to 332
and 548 to 800.
and 552 to 796.
and 552 to 790.
sequence index must be within the range of 42 to 310
and 552 to 784.
and 552 to 776.
and 558 to 770.
and 558 to 758.
and 598 to 746.
sequence index must be within the ranges of 116 to
254 and 624 to 732.
− 8600m < Cell radius ≤ 10,600 m: The value of root
254 and 624 to 710.
− 10,600
254 and 630 to 688.
− 13,200
246 and 630 to 640.
High speed Cell.HighSpeedFl Network This parameter specifies whether a cell is an ultra high
flag ag plan speed, high speed, or low speed cell. Set this parameter
(negotiation to ULTRA_HIGH_SPEED(Ultra high speed cell flag).
not
required)

eRAN
Scenario 2: High Speed Railways with Low Frequency Band, Highways and Surrounding Areas
The following table describes a parameter that must be set in a Cell MO to configure a high speed cell.
Other parameters in this MO required for this scenario are the same as those for scenario 1. The only
difference is the setting of the Cell.RootSequenceIdx and Cell.HighSpeedFlag parameters

Name
Root Cell.RootSequen Network plan Set this parameter according to the
sequence ceIdx (negotiation not Cell.HighSpeedFlag parameter value.
index required)
High speed Cell.HighSpeedFl Network plan Set this parameter to HIGH_SPEED(High speed
flag ag (negotiation not cell flag).
required)
5.4.3 Initial Configuration

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 5.4.2 "Data Preparation." For details,
see the procedure for configuring a single eNodeB on the CME GUI described in eNodeB Initial
Configuration Guide.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 5.4.2 "Data Preparation."
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
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.
MO Parameter Group Name Parameter

Cell Cell LocalCellID, HighSpeedFlag, *RootSequenceIdx
Same as in scenario 1.

eRAN
Configuring a Single eNodeB Using MML Commands

Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to
ULTRA_HIGH_SPEED(Ultra high speed cell flag).
Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to HIGH_SPEED(High
speed cell flag).
5.4.4 Activation Observation

The activation observation procedure is as follows:
Step 1 On the M2000 client, start a Uu interface tracing task for cells where high speed mobility is used.
Step 2 Check RRC_SYS_INFO messages, as shown in Figure 5-1.
If the value of highSpeedFlag in the information element (IE) prach-Config is TRUE shown in Figure
5-2, high speed mobility is successfully activated.
Figure 5-1 RRC_SYS_INFO messages
Figure 5-2 prach-Config IE
Step 3 Run the LST CELL command to query the value of the Cell.HighSpeedFlag parameter.
LOW_SPEED(Low speed cell flag) indicates a low speed cell, HIGH_SPEED(High speed cell
flag) indicates a high speed cell, and ULTRA_HIGH_SPEED(Ultra high speed cell flag)
indicates an ultra high speed cell.
---End

eRAN
5.4.5 Deactivation
Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to LOW_SPEED(Low
speed cell flag).
5.5 Performance Optimization

5.5.1 Monitoring
High speed mobility may affect the handover and access performance of cells due to a relatively large
frequency offset. To evaluate the impact of high speed mobility on cell performance, observe the
following key performance indicators (KPIs) and counters on the M2000 client:
 Inter-frequency Handover Success Rate
 Intra-frequency Handover Success Rate
 L.E-RAB.SuccEst
 L.E-RAB.AttEst
If the cell access success rate (calculated by dividing L.E-RAB.SuccEst by L.E-RAB.AttEst),
Intra-frequency Handover Success Rate, or Inter-frequency Handover Success Rate decreases after
high speed mobility is activated, the Cell.RootSequenceIdx parameter or handover parameters may be
set incorrectly. To solve this problem, modify the Cell.RootSequenceIdx parameter or handover
parameters. For details about how to modify handover parameters, see Connection Management
Feature Parameter Description.
5.5.2 Parameter Optimization

Preamble sequences are used for initial frequency correction in ultra high speed cells. Preamble
sequence generation depends on cell types and logical indexes to root ZC sequences. The logical index
to a root ZC sequence is specified by the Cell.RootSequenceIdx parameter. A smaller value of this
parameter indicates a higher probability of detecting a preamble sequence. If a cell is an ultra high speed
cell and uses AFC, set the Cell.RootSequenceIdx parameter to a small value. During network planning,
it is recommended that logical indexes be set in the following order: large high speed cell, medium high
speed cell, small high speed cell, large low speed cell, medium low speed cell, and small low speed cell.
The radius of a cell determines the cell size.
If two cells are far from each other, they can use the same logical index to a root ZC sequence.
5.6 Troubleshooting
Cells configured by referring to chapter 5 "Engineering Guidelines" can work properly in normal cases. If
they cannot work properly, perform the following steps to troubleshoot problems:
Step 1 Verify that the licenses are available and do not expire.
Step 2 Verify that the usage suggestion in section 5.1 "When to Use High Speed Mobility" has been
taken.
Step 3 Verify that the network planning suggestion in section 5.3 "Network Planning" has been taken,
such as the planning of root sequence indexes.
Step 4 Verify that the parameter setting suggestion in section 5.4 "Deploying High Speed Mobility" has
been taken.
Step 5 Verify that high speed mobility has been activated by referring to steps Step 1 and Step 2 in
section 5.4.4 "Activation Observation."

eRAN
Step 6 Verify that a high speed cell or an ultra high speed cell has been configured by referring to Step 3
in section 5.4.4 "Activation Observation."
Step 7 If there are other problems, contact Huawei technical support engineers.
----End

eRAN
High Speed Mobility 6 Parameters
6 Parameters
Table 6-1 Parameter description
MO Parameter ID MML Command Feature ID Feature Description
Name
Cell FddTddInd ADD CELL LBFD-0020 Broadcas Meaning:Indicates the

09 / t of duplex mode of the cell.
MOD CELL TDLBFD-00 system CELL_FDD indicates the
LST CELL 2009 informati FDD mode, and CELL_TDD
on indicates the TDD mode.
GUI Value
Range:CELL_FDD(FDD),
CELL_TDD(TDD)
Unit:None
Actual Value
Range:CELL_FDD,
CELL_TDD
Default Value:None
MimoAdaptiveP FixedMimoMod MOD LOFD-0010 DL 2x2 Meaning:Indicates the fixed

araCfg e MIMOADAPTIVEP 01 / MIMO MIMO transmission mode for
ARACFG TDLOFD-0 a multi-antenna eNodeB.
01001 DL 4x2 This parameter is valid
LST MIMO only when
MIMOADAPTIVEP LOFD-0010 MimoAdaptiveSwitch is set
ARACFG 03 / to NO_ADAPTIVE. There
TDLOFD-0 are four values.
01003
TM2: Transmission mode 2
is permanently applied to
UEs.
UEs.
UEs.
UEs.
GUI Value
Range:TM2(TM2),
TM3(TM3), TM4(TM4),
TM6(TM6)
Unit:None
Actual Value Range:TM2,

eRAN

Name
TM3, TM4, TM6
Default Value:TM3(TM3)
Cell HighSpeedFlag ADD CELL LOFD-0010 High Meaning:Indicates the speed

07 / Speed flag of the cell. Set this
MOD CELL TDLOFD-0 Mobility parameter to
LST CELL 01007 ULTRA_HIGH_SPEED if the
Ultra cell is used to provide
LOFD-0010 High coverage for an
08 / Speed ultra-high-speed railway. Set
TDLOFD-0 Mobility this parameter to
01008 HIGH_SPEED if the cell is
used to provide coverage for
a high way. Set this
parameter to LOW_SPEED
in other scenarios.
GUI Value
Range:LOW_SPEED(Low
speed cell flag),
HIGH_SPEED(High speed
cell flag),
ULTRA_HIGH_SPEED(Ultra
high speed cell flag),
EXTRA_HIGH_SPEED(Extr
a high speed cell flag)
Unit:None
Actual Value
Range:LOW_SPEED,
HIGH_SPEED,
ULTRA_HIGH_SPEED,
EXTRA_HIGH_SPEED
Default
Value:LOW_SPEED(Low
speed cell flag)
CellPdcchAlgo InitPdcchSymN MOD LBFD-0010 3GPP R8 Meaning:Indicates the

um CELLPDCCHALG 01 / Specificat number of OFDM symbols
O TDLBFD-00 ions initially occupied by the
1001 PDCCH.
LST Physical
CELLPDCCHALG LBFD-0020 Channel If the switch for dynamic
O 03 / Manage adjustment to the number of
TDLBFD-00 ment OFDM symbols occupied by
2003 the PDCCH is turned off, this
parameter indicates the
number of OFDM symbols
that are always occupied by
the PDCCH.

eRAN

Name
If the switch for dynamic
adjustment to the number of
OFDM symbols occupied by
the PDCCH is turned on, the
number of OFDM symbols
occupied by the PDCCH is
always 4 and 3 for the
bandwidths of 1.4 MHz and 3
MHz, respectively, and
therefore the parameter
setting is invalid. For the
bandwidth of 5 MHz,10 MHz,
15 MHz, or 20 MHz, this
parameter is set to 1 by
default and the number of
OFDM symbols occupied by
the PDCCH is adaptively
adjusted among 1, 2, and 3;
if this parameter is set to 2 or
3, the number of OFDM
symbols occupied by the
PDCCH is adaptively
adjusted between 2 and 3.
GUI Value Range:1~4
Unit:None
Actual Value Range:1~4
Default Value:1
Cell LocalCellId ACT CELL None None Meaning:Indicates the local

ID of the cell. It uniquely
ADD CELL identifies a cell within a BS.
BLK CELL GUI Value Range:0~17
DEA CELL Unit:None
DSP CELL Actual Value Range:0~17
LST CELL Default Value:None
MOD CELL
RMV CELL
STR
CELLRFLOOPBAC
K
STR
CELLSELFTEST
UBL CELL

eRAN

Name
MimoAdaptiveP MimoAdaptive MOD LOFD-0010 DL 2x2 Meaning:Indicates the type

araCfg Switch MIMOADAPTIVEP 01 / MIMO of adaptive MIMO for a
ARACFG TDLOFD-0 multi-antenna eNodeB. The
01001 DL 4x2 values are described as
LST MIMO follows:
MIMOADAPTIVEP LOFD-0010
ARACFG 03 / NO_ADAPTIVE: A fixed
TDLOFD-0 MIMO transmission mode is
01003 used. That is, transition
between MIMO transmission
modes is not supported.
OL_ADAPTIVE: open-loop
adaptive MIMO transmission
mode. UEs report RANK and
CQI values but do not report
PMI values to the eNodeB.
CL_ADAPTIVE: closed-loop
adaptive MIMO transmission
mode. UEs report RANK,
CQI, and PMI values to the
eNodeB.
OC_ADAPTIVE: UEs switch
between the open-loop and
closed-loop adaptive MIMO
transmission modes
automatically.
GUI Value
Range:NO_ADAPTIVE(NO_
ADAPTIVE),
OL_ADAPTIVE(OL_ADAPTI
VE),
CL_ADAPTIVE(CL_ADAPTI
VE),
OC_ADAPTIVE(OC_ADAPT
IVE)
Unit:None
Actual Value
Range:NO_ADAPTIVE,
OL_ADAPTIVE,
CL_ADAPTIVE,
OC_ADAPTIVE
Default
Value:OL_ADAPTIVE(OL_A
DAPTIVE)
CellPdcchAlgo PdcchSymNum MOD LBFD-0010 3GPP R8 Meaning:Indicates the switch

CELLPDCCHALG 01 / Specificat that is used to

eRAN

Name
Switch O TDLBFD-00 ions control whether to enable
1001 and disable dynamic
LST Physical adjustment on the number of
CELLPDCCHALG LBFD-0020 Channel OFDM symbols occupied by
O 03 / Manage PDCCH.
TDLBFD-00 ment
2003 GUI Value Range:OFF(Off),
ON(On)
Unit:None
Actual Value Range:OFF,
ON
Default Value:ON(On)
Cell PreambleFmt ADD CELL LBFD-0020 Random Meaning:Indicates the

10 / Access preamble format used in the
MOD CELL TDLBFD-00 Procedur cell. Cells set up on one
LST CELL 2010 e LBBP must use the same
preamble format. For details,
see 3GPP TS 36.211.
GUI Value Range:0~4
Unit:None
Default Value:0
Cell RootSequenceI ADD CELL LBFD-0020 Random Meaning:Indicates the first

dx 10 / Access logical root sequence, which
MOD CELL TDLBFD-00 Procedur is used to generate the
LST CELL 2010 e preamble sequence. Each
logical root sequence
corresponds to a physical
root sequence. For the
mapping between logical
root sequences and physical
root sequences, see 3GPP
TS 36.211.
GUI Value Range:0~837
Unit:None
Default Value:None

eRAN
High Speed Mobility 7 Counters
7 Counters
There are no specific counters associated with this feature.

eRAN
High Speed Mobility 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
High Speed Mobility 9 Reference Documents
9 Reference Documents
This chapter lists the reference documents related to high speed mobility.
[1] 3GPP TS 36.211, "Physical Channels and Modulation"
[2] eNodeB Performance Counter Reference
[3] eNodeB MO Reference
[4] MIMO Feature Parameter Description
[5] Connection Management Feature Parameter Description
[6] eNodeB Initial Configuration Guide
[7] Physical Channel Resource Management Feature Parameter Description


High Speed Mobility (ERAN3.0 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

High Speed Mobility (ERAN3.0 - 02)

Uploaded by

Copyright:

Available Formats

High Speed Mobility

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

2 High Speed Mobility .................................................................................................................2-1

3 Related Features .......................................................................................................................3-1

4 Impact on the Network.............................................................................................................4-1

5 Engineering Guidelines ...........................................................................................................5-1

Issue 02 (2012-12-29) Huawei Proprietary and Confidential i

1.2 Intended Audience

1.3 Change History

Change Type Change Description Parameter Change

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 1-2

2 High Speed Mobility

2.1 Doppler Shift

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 2-1

2.2 Automatic Frequency Control

2.3 Random Access Preamble

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 2-2

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 2-3

3.2 Mutually Exclusive Features

3.3 Affected Features

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 3-1

4 Impact on the Network

4.2 Impact on Network Performance

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 4-1

5.1 When to Use High Speed Mobility

5.2 Information to Be Collected

5.3 Network Planning

5.3.2 Network Topology

5.4 Deploying High Speed Mobility

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-1

 Set the CellPdcchAlgo.PdcchSymNumSwitch parameter to OFF(Off) and the

Requirements for the Operating Environment

Requirements for Transmission Networking

Requirements for Licenses

Feature License Control Item Name

5.4.2 Data Preparation

Parameter Parameter ID Source Setting Description

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-2

Parameter Parameter ID Source Setting Description

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-3

Parameter Parameter ID Source Setting Description

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-4

Parameter Parameter ID Source Setting Description

5.4.3 Initial Configuration

Configuring eNodeBs in Batches

MO Parameter Group Name Parameter

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-5

Configuring a Single eNodeB Using MML Commands

5.4.4 Activation Observation

Figure 5-2 prach-Config IE

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-6

5.5 Performance Optimization

5.5.2 Parameter Optimization

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-7

Issue 02 (2012-12-29) Huawei Proprietary and Confidential 5-8

Cell FddTddInd ADD CELL LBFD-0020 Broadcas Meaning:Indicates the

MimoAdaptiveP FixedMimoMod MOD LOFD-0010 DL 2x2 Meaning:Indicates the fixed