High Speed Mobility (eRAN7.0 - 01)

eRAN
High Speed Mobility Feature

Parameter Description
Issue 01
Date 2014-04-26
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. 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 01 (2014-04-26) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
High Speed Mobility Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................2
1.4 Differences Between eNodeB Types..............................................................................................................................3
2 Overview.........................................................................................................................................4
3 Technical Description...................................................................................................................5
3.1 Introduction....................................................................................................................................................................5
3.2 Doppler Shift..................................................................................................................................................................5
3.3 Automatic Frequency Control........................................................................................................................................6
3.4 Random Access Preamble..............................................................................................................................................7
3.5 Scheduling......................................................................................................................................................................7
4 Related Features.............................................................................................................................8
4.1 LOFD-001007 High Speed Mobility..............................................................................................................................8
4.2 LOFD-001008 Ultra High Speed Mobility....................................................................................................................8
5 Impact on the Network...............................................................................................................10

5.1 LOFD-001007 High Speed Mobility............................................................................................................................10
5.2 LOFD-001008 Ultra High Speed Mobility..................................................................................................................10
6 Engineering Guidelines.............................................................................................................11
6.1 When to Use High Speed Mobility...............................................................................................................................11
6.2 Required Information...................................................................................................................................................11
6.3 Planning........................................................................................................................................................................11
6.3.1 RF Planning...............................................................................................................................................................11
6.3.2 Network Planning......................................................................................................................................................12
6.4 Deployment..................................................................................................................................................................12
6.4.1 Requirements.............................................................................................................................................................12
6.4.2 Data Preparation........................................................................................................................................................13
6.4.3 Precautions.................................................................................................................................................................18
6.4.4 Activation..................................................................................................................................................................18
6.4.5 Activation Observation..............................................................................................................................................21
Issue 01 (2014-04-26) Huawei Proprietary and Confidential ii

eRAN
High Speed Mobility Feature Parameter Description Contents
6.4.6 Reconfiguration.........................................................................................................................................................21
6.4.7 Deactivation...............................................................................................................................................................21
6.5 Monitoring....................................................................................................................................................................22
6.6 Parameter Optimization................................................................................................................................................22
6.7 Troubleshooting............................................................................................................................................................22
7 Parameters.....................................................................................................................................24
8 Counters........................................................................................................................................31
9 Glossary.........................................................................................................................................32
Issue 01 (2014-04-26) Huawei Proprietary and Confidential iii

eRAN
High Speed Mobility Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the high speed mobility, including its technical principles, related
features, network impact, and engineering guidelines.
This document covers the following features:
l LOFD-001007 High Speed Mobility

l LOFD-001008 Ultra High Speed Mobility
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
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
Issue 01 (2014-04-26) Huawei Proprietary and Confidential 1

eRAN
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN7.0 01 (2014-04-26)
This issue does not include any changes.
eRAN7.0 Draft B (2014-03-07)

This issue includes the following changes.
Chang Change Description Parameter Affected Entity

e Type Change
Feature None None N/A

change
Editoria Added 1.4 Differences Between None N/A

l change eNodeB Types, which describes
differences in feature support
between eNodeB types.
eRAN7.0 Draft A (2014-01-20)

Compared with Issue 02 (2013-07-30) of eRAN6.0, Draft A (2014-01-20) of eRAN7.0 includes
the following changes.

eRAN
Change Type Change Description Parameter Change
Feature change l Added a new feature LOFD-070209 None

Coordinated Scheduling based Power
Control (ECO), which is not compatible
with the LOFD-001007 High Speed
Mobility feature. For details, see Mutually
Exclusive Features in 4.1 LOFD-001007
High Speed Mobility.
l Added a new feature LOFD-070209
Coordinated Scheduling based Power
Control (ECO), which is not compatible
with the LOFD-001008 Ultra High Speed
Mobility feature. For details, see Mutually
Exclusive Features in 4.2 LOFD-001008
Ultra High Speed Mobility.
Changed the name of Huawei mobile element None

management system from M2000 to U2000.
Editorial change None None
1.4 Differences Between eNodeB Types

The features described in this document apply only to macro eNodeBs.

eRAN
High Speed Mobility Feature Parameter Description 2 Overview
2 Overview
In the LTE system, subcarriers are closely spaced and sensitive to Doppler shift. Therefore, the
LTE system has high requirements for frequency synchronization to ensure orthogonality
between subcarriers.
High speed movement of UEs causes great Doppler shift that distorts the orthogonality between
subcarriers. Huawei eNodeBs use automatic frequency control (AFC) to correct Doppler shift.
The eNodeBs that support high speed mobility can sustain services and ensure user experience
for UEs moving at a maximum speed of 450 km/h.
Huawei eNodeBs support high speed mobility and ultra high speed mobility:
l With high speed mobility, eNodeBs provide satisfactory network performance for UEs
moving at the following maximum speeds when operating in different bands:
– 120 km/h in 2.6 GHz
– 160 km/h in 2.1 GHz
– 200 km/h in 1.8 GHz
– 450 km/h in 700 MHz and 800 MHz
NOTE
For example, 120 km/h in 2.6 GHz indicates that UEs can move at the maximum speed of 120 km/
h when operating in the 2.6 GHz band.
l With ultra high speed mobility, eNodeBs provide satisfactory network performance for
UEs moving at the maximum speed of 450 km/h when operating in a high band in the line
of sight (LOS) scenario.

eRAN
High Speed Mobility Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 Introduction
High speed movement of UEs causes great Doppler shift, which results in inter-subcarrier
interference and degrades system performance. Doppler shift can be corrected by using AFC
and system performance can be improved by properly setting the random access preamble and
applying appropriate scheduling. For details about how to configure related parameters, see 6
Engineering Guidelines.
3.2 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
l fd is the Doppler shift.
l f0 is the carrier frequency.
l C is the speed at which electromagnetic waves propagate.
l v is the velocity at which the UE moves.
l θ 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
severe 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 3-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

eRAN
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 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 3-1 Doppler shift
3.3 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:
l Initial frequency correction
During random access of UEs, an eNodeB detects frequency shifts by using preambles and
performs initial frequency correction. After initial frequency correction completes, UEs
can transmit access signaling messages on the physical uplink shared channel (PUSCH).
l Continuous frequency correction
The eNodeB performs continuous frequency correction after UEs access the network. The
eNodeB estimates frequency shifts based on pilot signals of the UEs and uses the results
as the continuous inputs to the frequency correction function.
Figure 3-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 shift to ensure correct demodulation and decoding of uplink
data.
Figure 3-2 Functionality of AFC

eRAN
3.4 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 and 6.4.2 Data
Preparation in this document.
3.5 Scheduling
In high speed scenarios, both frequency-selective scheduling and semi-persistent scheduling are
not applied. The reasons are as follows:
l 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.
l Semi-persistent scheduling requires that the scheduled resources be retained for a period
of time. Therefore, semi-persistent scheduling 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 accurate, 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, adaptive open-
loop MIMO is recommended for high speed cells and ultra high speed cells. For details about
MIMO, see MIMO Feature Parameter Description.

eRAN
High Speed Mobility Feature Parameter Description 4 Related Features
4 Related Features
4.1 LOFD-001007 High Speed Mobility

Prerequisite Features
None
Mutually Exclusive Features

In high speed cells, the LOFD-070209 Coordinated Scheduling based Power Control (ECO)
feature is not supported.
Impacted Features
In high speed cells, it is recommended that semi-persistent scheduling, frequency selective
scheduling, and physical downlink control channel (PDCCH) symbol adaptation be disabled,
and it is recommended that open-loop transmit diversity be enabled. For recommendation causes,
see 3.5 Scheduling.
4.2 LOFD-001008 Ultra High Speed Mobility

Prerequisite Features
None
Mutually Exclusive Features

In ultra high speed cells, the following features are not supported:
l LOFD-001016 VoIP Semi-persistent Scheduling

l Frequency selective scheduling
l LOFD-001066 Intra-eNodeB UL CoMP
l LOFD-070209 Coordinated Scheduling based Power Control (ECO)

eRAN
High Speed Mobility Feature Parameter Description 4 Related Features
Impacted Features
In ultra high speed cells, it is recommended that you disable 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 Feature Parameter Description 5 Impact on the Network
5 Impact on the Network
5.1 LOFD-001007 High Speed Mobility

System Capacity
Compared with low speed, high speed 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.
Network Performance
Compared with low speed, high speed 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.
5.2 LOFD-001008 Ultra High Speed Mobility

System Capacity
Compared with low speed, ultra high speed 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.
Network Performance
Compared with low speed, ultra high speed 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 KPIs and ensure proper system operation.

eRAN
High Speed Mobility Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.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:
l If the cell covers high speed railways (with UEs moving at the speed of up to 450 km/h
when operating in a high band in the LOS scenario), set it as an ultra high speed cell.
l If the cell covers high speed railways, and highways and surrounding areas (with UEs
moving at the speed of up to 120 km/h when operating in the 2.6 GHz band, 160 km/h in
2.1 GHz, 200 km/h in 1.8 GHz, and 450 km/h in 700 MHz and 800 MHz), set it as a high
speed cell.
l 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.
6.2 Required Information

N/A
6.3 Planning
6.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.

eRAN
6.3.2 Network Planning

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. In addition, the single frequency network (SFN) topology or
RRU cascading topology is recommended to reduce frequent handovers in high speed mobility
and ultra high speed mobility scenarios. In these topologies, 4-antenna receive diversity must
be supported in the uplink.
6.4 Deployment
6.4.1 Requirements
Other Functions
It is recommended that functions and parameters related to high speed mobility be set as follows:
l Frequency-selective scheduling is not supported by ultra high speed cells and not
recommended for high speed cells.
l Semi-persistent scheduling is not supported by ultra high speed cells and not recommended
for high speed cells.
l Set the CellPdcchAlgo.PdcchSymNumSwitch parameter to OFF(Off) and the
CellPdcchAlgo.InitPdcchSymNum parameter to 3 (4 for ultra high speed cells with the
bandwidth of 1.4 MHz) for ultra high speed cells.
l Set the MimoAdaptiveParaCfg.MimoAdaptiveSwitch parameter to OL_ADAPTIVE
(OL_ADAPTIVE) by running the MOD MIMOADAPTIVEPARACFG command for
high and ultra high speed cells. For details about MIMO, see MIMO Feature Parameter
Description.
Operating Environment
None
Transmission Networking
None
License
The operator has purchased and activated the following licenses.
Feature ID Feature Name License NE Sales Unit

Control Item
LOFD-001007 High Speed High Speed eNodeB per Cell

Mobility Mobility(FDD)

eRAN
Feature ID Feature Name License NE Sales Unit

Control Item
LOFD-001008 Ultra High Ultra High eNodeB per Cell

Speed Mobility Speed Mobility
(FDD)
6.4.2 Data Preparation
Required Data
N/A
Scenario-specific Data
NOTE
In high speed mobility scenarios, the maximum number of root sequences that can be configured is 20 for
the LBBPc, 10 for the LBBPd in preamble format 0 or 1, or 5 for the LBBPd in preamble format 2 or 3.
Scenario 1: High Speed Railways with High Frequency Band
The following table describes the parameters that must be set in a Cell MO to configure an ultra
high speed cell.
Paramete Parameter ID Data Setting Notes

r Name Source
Local cell Cell.LocalCellId Network Set this parameter based on the

identity plan network plan. This parameter specifies
(negotiation the local ID of a cell.
not
required)

eRAN

r Name Source
Root Cell. Network This parameter specifies the logical

sequence RootSequenceIdx plan root sequence numbers for preamble
index (negotiation generation. Each logical root sequence
not number maps a physical root sequence
required) number. For the mapping between
them, see 3GPP TS 36.211.
The following constraints are imposed
on this parameter (The following value
ranges are the maximum ones allowed
during network planning. The actual
value range for each cell needs to 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) or ULTRA_HIGH_SPEED
(Ultra high speed cell flag), the cell
radius cannot be greater than 32,800 m
and the value ranges of this parameter
are as follows:
l 1 m ≤ Cell radius ≤ 1000 m:
24-815
The value range 333-547 or
801-815 is not recommended if the
Cell.HighSpeedFlag parameter is
set to ULTRA_HIGH_SPEED
(Ultra high speed cell flag)
because the access performance
may deteriorate in this situation.
l 1000 m < Cell radius ≤ 1500 m:
30-811

eRAN

r Name Source

36-804
42-797
52-786
64-779
76-765
The value range 255~557 or
759~765 is not recommended if the

eRAN

r Name Source

90-747
The value range 255-597 or the
value 747 is not recommended if
the Cell.HighSpeedFlag
parameter is set to
ULTRA_HIGH_SPEED(Ultra
high speed cell flag) because the
access performance may
deteriorate in this situation.
116-731
The value range 255-623 is not
recommended if the
l 8600 m < Cell radius ≤ 10,600 m:
136-706
recommended if the
l 10,600 m < Cell radius ≤ 13,200
m: 168-676
recommended if the
l 13,200 m < Cell radius ≤ 17,200
m: 204-602
recommended if the

eRAN

r Name Source
l 17,200 m < Cell radius ≤ 21,500

m: 264-566
The value range for the cell radius
is not recommended if the
because the number of UEs that can
access the network decreases in this
situation.
l 21,500 m < Cell radius ≤ 27,800
m: 328- 498
situation.
l 27,800 m < Cell radius ≤ 32,800
m: 384-450
situation.
High speed Cell.HighSpeedFlag Network This parameter specifies whether a cell

flag plan is an ultra high speed, high speed, or
(negotiation low speed cell.
not Set this parameter to
required) ULTRA_HIGH_SPEED(Ultra high
speed cell flag).
Scenario 2: High Speed Railways, Highways and Surrounding Areas with Low Frequency
Band
The following table describes the parameters 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

eRAN
Parameter Name Parameter ID Source Setting

Description
Root sequence index Cell. Network plan Set this parameter

RootSequenceIdx (negotiation not according to the
required) Cell.HighSpeedFla
g parameter value.
High speed flag Cell. Network plan Set this parameter to

HighSpeedFlag (negotiation not HIGH_SPEED
required) (High speed cell
flag).
6.4.3 Precautions
None
6.4.4 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 6-1 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 MO in Table 6-1 is contained in a scenario-specific summary data file. In this situation,
set the parameters in the MO, and then verify and save the file.
l The MO in Table 6-1 is not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MO before you can set the
parameters.
Table 6-1 Parameters for activation
MO Sheet in the Parameter Group Remarks

Summary Data
File
Cell eNodeB Cell LocalCellID, -

HighSpeedFlag,
*RootSequenceIdx
Scenario 2: High Speed Railways with Low Frequency Band, Highways and Surrounding
Areas

eRAN
Same as in scenario 1.
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 After creating a planned data area, choose CME > Advanced > Customize Summary Data
File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client
mode), 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 (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), 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-1 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), 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 (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
Using MML Commands

Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to
ULTRA_HIGH_SPEED(Ultra high speed cell flag) and the Cell.RootSequenceIdx
parameter set to an appropriate value.
Scenario 2: High Speed Railways with Low Frequency Band, Highways and Surrounding
Areas
Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to HIGH_SPEED
(High speed cell flag) and the Cell.RootSequenceIdx parameter set to an appropriate value.
MML Command Examples

MOD CELL: LocalCellId=0, HighSpeedFlag=ULTRA_HIGH_SPEED, RootSequenceIdx=700;
MOD CELL: LocalCellId=0, HighSpeedFlag=HIGH_SPEED, RootSequenceIdx=700;

eRAN
6.4.5 Activation Observation

The activation observation procedure is as follows:
Step 1 On the U2000 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 6-2.
If the value of highSpeedFlag in the information element (IE) prach-Config is TRUE shown
in Figure 6-3, high speed mobility is successfully activated.
Figure 6-2 RRC_SYS_INFO messages
Figure 6-3 prach-Config IE
Step 3 Run the LST CELL command to query the value of the Cell.HighSpeedFlag parameter.
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
6.4.6 Reconfiguration
N/A
6.4.7 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
feature activation described in "Using the CME to Perform Batch Configuration for Existing
eNodeBs." In the procedure, modify the parameter according to Table 6-2.

eRAN
Table 6-2 Parameter for deactivation
MO Sheet in the Parameter Group Setting Notes

Summary Data
File
Cell eNodeB Cell HighSpeedFlag LOW_SPEED
Using the CME to Perform Single Configuration

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

Run the MOD CELL command with the Cell.HighSpeedFlag parameter set to LOW_SPEED
(Low speed cell flag).
MML Command Examples

MOD CELL: LocalCellId=0, HighSpeedFlag=LOW_SPEED;
6.5 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:
l Inter-frequency Handover Success Rate

l Intra-frequency Handover Success Rate
l L.E-RAB.SuccEst
l L.E-RAB.AttEst
If the cell access success rate (L.E-RAB.SuccEst/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
inappropriately. 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.
6.6 Parameter Optimization

N/A
6.7 Troubleshooting
Cells configured by referring to 6 Engineering Guidelines can work properly in normal cases.
If they cannot work properly, perform the following steps to troubleshoot problems:

eRAN
Step 1 Verify that the licenses are available and do not expire.
Step 2 Verify that the usage suggestion in 6.1 When to Use High Speed Mobility has been taken.
Step 3 Verify that the network planning suggestion in 6.3 Planning has been taken, such as the planning
of root sequence indexes.
Step 4 Verify that the parameter setting suggestion in 6.4 Deployment has been taken.
Step 5 Verify that high speed mobility has been activated by referring to steps Step 1 and Step 2 in
6.4.5 Activation Observation.
Step 6 Verify that a high speed cell or an ultra high speed cell has been configured by referring to Step
3 in 6.4.5 Activation Observation.
If there are other problems, contact Huawei technical support engineers.
----End

eRAN
High Speed Mobility Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameter description
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
Cell HighSpe ADD LOFD-0 High Meaning: Indicates the speed flag of the cell. Set this
edFlag CELL 01007 / Speed parameter to ULTRA_HIGH_SPEED if the cell is used
MOD TDLOF Mobility to provide coverage for an ultra-high-speed railway. Set
CELL D-00100 Ultra this parameter to HIGH_SPEED if the cell is used to
7 High provide coverage for a high way. Set this parameter to
LST LOW_SPEED in other scenarios.
CELL LOFD-0 Speed
01008 / Mobility GUI Value Range: LOW_SPEED(Low speed cell flag),
TDLOF HIGH_SPEED(High speed cell flag),
D-00100 ULTRA_HIGH_SPEED(Ultra high speed cell flag),
8 EXTRA_HIGH_SPEED(Extra 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)
Cell RootSeq ADD LBFD-0 Random Meaning: Indicates the first logical root sequence,
uenceId CELL 02010 / Access which is used to generate the preamble sequence. Each
x MOD TDLBF Procedu logical root sequence corresponds to a physical root
CELL D-00201 re sequence. For the mapping between logical root
0 sequences and physical root sequences, see 3GPP TS
LST 36.211.
CELL
GUI Value Range: 0~837
Unit: None
Actual Value Range: 0~837
Default Value: None

eRAN

nd
CellPdc PdcchSy MOD LBFD-0 Physical Meaning: Indicates the switch used to enable or disable
chAlgo mNumS CELLP 02003 / Channel dynamic adjustment on the number of orthogonal
witch DCCHA TDLBF Manage frequency division multiplexing (OFDM) symbols
LGO D-00200 ment occupied by the physical downlink control channel
LST 3 (PDCCH). If this parameter is set to OFF, the number
CELLP of OFDM symbols occupied by the PDCCH is fixed and
DCCHA cannot be dynamically adjusted. If this parameter is set
LGO to ON, the number of OFDM symbols occupied by the
PDCCH is dynamically adjusted based on the required
number of PDCCH control channel elements (CCEs).
If this parameter is set to ECFIADAPTIONON, the
number of OFDM symbols occupied by the PDCCH is
dynamically adjusted based on the cell downlink
throughput, and the adjustment performance is the best
among the three methods.
GUI Value Range: OFF(Off), ON(On),
ECFIADAPTIONON(Enhanced CFI Adaption On)
Unit: None
Actual Value Range: OFF, ON, ECFIADAPTIONON
Default Value: ON(On)
CellPdc InitPdcc MOD LBFD-0 Physical Meaning: Indicates the number of OFDM symbols
chAlgo hSymNu CELLP 02003 / Channel initially occupied by the PDCCH. If the switch for
m DCCHA TDLBF Manage dynamic adjustment of the number of OFDM symbols
LGO D-00200 ment occupied by the PDCCH is turned off, this parameter
LST 3 indicates the number of OFDM symbols that are always
CELLP occupied by the PDCCH. If the switch is turned on and
DCCHA the bandwidth is 1.4 MHz or 3 MHz, the PDCCH
LGO occupies 4 or 3 OFDM symbols, in this scenario, this
parameter cannot be manually set.. If the switch is
turned on and the bandwidth is 5 MHz, 10 MHz, 15
MHz, or 20 MHz, the eNodeB adjusts the number of
OFDM symbols in the range of 1, 2, and 3 when this
parameter is set to the default value 1, or in the range of
2 and 3 when this parameter is set to 2 or 3.
GUI Value Range: 1~4
Unit: None
Actual Value Range: 1~4
Default Value: 1

eRAN

nd
MimoA MimoA MOD LOFD-0 DL 2x2 Meaning: Indicates the type of adaptive MIMO for a
daptiveP daptiveS MIMOA 01001 MIMO multi-antenna eNodeB. The values are described as
araCfg witch DAPTI LOFD-0 DL 4x2 follows: NO_ADAPTIVE: A fixed MIMO transmission
VEPAR 01003 MIMO mode is used. That is, transition between MIMO
ACFG transmission modes is not supported. OL_ADAPTIVE:
LOFD-0 DL 4X4 The open-loop adaptive MIMO transmission mode is
LST 01060 / MIMO
MIMOA used. In this mode, UEs report RI and CQI values but
TDLOF DL 2x2 do not report PMI values to the eNodeB.
DAPTI D-00106
VEPAR MIMO CL_ADAPTIVE: The closed-loop adaptive MIMO
0 transmission mode is used. In this mode, UEs report RI,
ACFG
TDLOF CQI, and PMI values to the eNodeB. OC_ADAPTIVE:
D-00100 UEs switch between the open-loop and closed-loop
1 adaptive MIMO transmission modes automatically.
This parameter is unavailable in this version.
GUI Value Range: NO_ADAPTIVE
(NO_ADAPTIVE), OL_ADAPTIVE
(OL_ADAPTIVE), CL_ADAPTIVE
(CL_ADAPTIVE), OC_ADAPTIVE
(OC_ADAPTIVE)
Unit: None
Actual Value Range: NO_ADAPTIVE,
OL_ADAPTIVE, CL_ADAPTIVE, OC_ADAPTIVE
Default Value: OL_ADAPTIVE(OL_ADAPTIVE)

eRAN

nd
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Unit: None
ADD Actual Value Range: 0~255
CELLB
Default Value: None
AND
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND
STR
CELLR
FLOOP
BACK

eRAN

nd
STR
CELLS
ELFTES
T
STR
PRIBBP
ADJUS
T
UBL
CELL
DSP
PRIBBP
RESINF
O

eRAN

nd
Cell FddTddI ADD LBFD-0 Broadca Meaning: Indicates the duplex mode of the cell.
nd CELL 02009 st of CELL_FDD indicates the FDD mode, and CELL_TDD
MOD TDLBF system indicates the TDD mode.
CELL D-00100 informat GUI Value Range: CELL_FDD(FDD), CELL_TDD
7 ion (TDD)
LST
CELL TDLBF Basic Unit: None
D-00100 uplink-
Actual Value Range: CELL_FDD, CELL_TDD
701 downlin
k Default Value: None
TDLBF
subfram
D-00100
e
702
configur
TDLOF ation
D-00102
uplink-
6
downlin
TDLOF k
D-00102 subfram
601 e
TDLOF configur
D-00102 ation
602 type1&2
TDLOF uplink-
D-00102 downlin
603 k special
subfram
e
configur
ation
type 7
Optional
uplink-
downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0

eRAN

nd
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
Cell Preambl ADD LBFD-0 Random Meaning: Indicates the preamble format used in the cell.
eFmt CELL 02010 / Access For details, see 3GPP TS 36.211.
MOD TDLBF Procedu GUI Value Range: 0~4
CELL D-00201 re
0 Unit: None
LST Actual Value Range: 0~4
CELL
Default Value: 0

eRAN
High Speed Mobility Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

eRAN
High Speed Mobility Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.


High Speed Mobility (eRAN7.0 - 01)

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 (eRAN7.0 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

High Speed Mobility Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2014-04-26) Huawei Proprietary and Confidential i

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

5 Impact on the Network...............................................................................................................10

Issue 01 (2014-04-26) Huawei Proprietary and Confidential ii

Issue 01 (2014-04-26) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

l LOFD-001007 High Speed Mobility

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

1.2 Intended Audience

l Need to understand the features described herein

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 1

1.3 Change History

eRAN7.0 Draft B (2014-03-07)

Chang Change Description Parameter Affected Entity

Feature None None N/A

Editoria Added 1.4 Differences Between None N/A

eRAN7.0 Draft A (2014-01-20)

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 2

Change Type Change Description Parameter Change

Feature change l Added a new feature LOFD-070209 None

Changed the name of Huawei mobile element None

Editorial change None None

1.4 Differences Between eNodeB Types

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 3

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 4

3.2 Doppler Shift

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 5

Figure 3-1 Doppler shift

3.3 Automatic Frequency Control

Figure 3-2 Functionality of AFC

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 6

3.4 Random Access Preamble

l Frequency-selective scheduling requires better channel quality on one subcarrier than on

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 7

4.1 LOFD-001007 High Speed Mobility

Mutually Exclusive Features

4.2 LOFD-001008 Ultra High Speed Mobility

Mutually Exclusive Features

l LOFD-001016 VoIP Semi-persistent Scheduling

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 8

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 9

5 Impact on the Network

5.1 LOFD-001007 High Speed Mobility

5.2 LOFD-001008 Ultra High Speed Mobility

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 10

6.1 When to Use High Speed Mobility

The recommended settings for a cell are as follows:

6.2 Required Information

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 11

6.3.2 Network Planning

Feature ID Feature Name License NE Sales Unit

LOFD-001007 High Speed High Speed eNodeB per Cell

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 12

Feature ID Feature Name License NE Sales Unit

LOFD-001008 Ultra High Ultra High eNodeB per Cell