eRAN Cell Management Guide

Cell Management
eRAN3.0
Feature Parameter Description
Issue 05
Date 2013-05-20
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
Cell Management Contents
Issue 05 (2013-05-20) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
i
Contents
1 Introduction................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
2.1 Introduction.................................................................................................................................... 2-1
2.2 Benefits ......................................................................................................................................... 2-1
3 Technical Description..............................................................................................................3-1
3.1 Sectors .......................................................................................................................................... 3-1
3.1.1 Mapping Between Sectors and RF Resources .................................................................... 3-1
3.1.2 Sector Types......................................................................................................................... 3-2
3.2 Cell ................................................................................................................................................ 3-5
4 Engineering Guidelines...........................................................................................................4-1
4.1 When to Use Cell Management .................................................................................................... 4-1
4.2 Information to Be Collected........................................................................................................... 4-1
4.3 Network Planning .......................................................................................................................... 4-1
4.4 Deploying Cell Management......................................................................................................... 4-1
4.4.1 Deployment Requirements................................................................................................... 4-1
4.4.2 Data Preparation................................................................................................................... 4-4
4.4.3 Hardware Installation.......................................................................................................... 4-13
4.4.4 Initial Configuration............................................................................................................. 4-15
4.4.5 Activation Verification.......................................................................................................... 4-19
4.4.6 Reconfiguration .................................................................................................................. 4-20
4.4.7 Deactivation........................................................................................................................ 4-22
4.5 Optimization ................................................................................................................................ 4-22
4.6 Troubleshooting........................................................................................................................... 4-22
4.6.1 Fault Description................................................................................................................. 4-22
4.6.2 Fault Handling .................................................................................................................... 4-22
5 Parameters..................................................................................................................................5-1
6 Counters......................................................................................................................................6-1
7 Glossary ......................................................................................................................................7-1
8 Reference Documents .............................................................................................................8-1

eRAN
Cell Management 1 Introduction
1-1
1 Introduction
1.1 Scope
This document describes the technical principles of cell management in the Long Term Evolution (LTE)
system. It also provides engineering guidelines for cell management. The cell management feature
relates to the feature LBFD-001003 Scalable Bandwidth.
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 the cell management feature
 Personnel who work with Huawei 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 cell management 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:
 05 (2013-05-20)
 04 (2012-09-20)
 03 (2012-06-30)
 02 (2012-05-11)
 01 (2012-03-30)
 Draft A (2012-01-10)
05 (2013-05-20)
Compared with issue 04 (2012-09-20) of eRAN3.0, 05 (2013-05-20) of eRAN3.0 includes the following
changes.
Change Type Change Description Parameter Change
Feature change None None
Editorial change Added the chapter 2 "Overview." None

eRAN
1-2
04 (2012-09-20)
Compared with issue 03 (2012-06-30) of eRAN3.0, 04 (2012-09-20) of eRAN3.0 includes the following
changes.
Editorial change Modified the description of hardware
installation. For details, see section 4.4.3
"Hardware Installation."
None
03 (2012-06-30)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-06-30) of eRAN3.0 includes the
following changes.
Editorial change  Added the scenario with multiple RRUs
combined and the requirements for RRU
installation. For details, see section 4.4.3
"Hardware Installation."
 Added the description of setting PA by the
CellDlpcPdschPa.PaPcOff parameter. For
details, see "Transmit Power" in section 3.2
"Cell."
Added the
CellDlpcPdschPa.PaPcOff
parameter.
02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the
following changes.
Feature change Modified the formulas for calculating the
cell-specific maximum transmit power. For
details, see "Transmit Power" in section 3.2
"Cell."
Added the PA parameter.
Editorial change None None
01 (2012-03-30)
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.

eRAN
1-3
Editorial change Revised the frequency band section. For details,
see section 3.2 "Cell."
None
Draft A (2012-01-10)
This is a draft.
Compared with issue 02 (2011-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.
Editorial change Revised chapter 4 "Engineering Guidelines." None

eRAN
Cell Management 2 Overview
2-1
2 Overview
2.1 Introduction
A cell is an area where radio communication services are provided. It is the fundamental unit of a radio
network. When joined, cells provide radio coverage over a wide area.
eNodeBs can manage radio communication resources, which include sectors, sector equipment, radio
frequency (RF) resources, baseband equipment, and carriers.
2.2 Benefits
LBFD-001003 Scalable Bandwidth provides the following benefits:
 Supports high bandwidths, which help increase cell throughput and improve user experience.
 Supports small bandwidths of 1.4 MHz and 3 MHz to increase spectral efficiency.
 Allows flexible bandwidth configurations to facilitate spectrum utilization.

eRAN
Cell Management 3 Technical Description
3-1
3 Technical Description
3.1 Sectors
A sector is the smallest radio coverage area. Each sector uses one or more radio carriers to achieve
coverage. Each radio carrier works at a frequency. A sector and a carrier compose a cell that user
equipment (UEs) can access.
Sectors are classified into the following types:
 Omnidirectional sectors
Omnidirectional sectors are used for low-traffic coverage. An omnidirectional sector covers a circle
area of 360 degrees with an omnidirectional antenna at the center.
 Directional sectors
Directional sectors are used for high-traffic coverage. Each directional sector uses directional
antennas for coverage. In three-sector scenarios, each directional antenna covers a sector area of
120 degrees. In six-sector scenarios, each directional antenna covers a sector area of 60 degrees.
The coverage areas of adjacent sectors overlap each other because the actual azimuth of each sector
is slightly larger than 60 or 120 degrees.
3.1.1 Mapping Between Sectors and RF Resources
Figure 3-1 shows the mapping between sectors and radio frequency (RF) resources of an eNodeB. A
sector uses antennas for coverage. To improve the receive quality, each antenna provides multiple
receive channels that work in receive diversity mode.

eRAN
3-2
Figure 3-1 Mapping between sectors and RF resources of an eNodeB
The antenna mode for 3900 series eNodeBs can be 1T1R, 1T2R, 2T2R, 2T4R, or 4T4R.
xTyR indicates that a cell uses x transmit channels and y receive channels.
3.1.2 Sector Types
Common Sectors
The antenna mode of a common sector can be 1T1R, 1T2R, 2T2R, 2T4R, or 4T4R. Each common
sector can use one remote radio unit (RRU) or RF unit (RFU). Two RRUs or RFUs can be combined for
capacity expansion, and they must be connected to the same LTE baseband processing unit (LBBP).
Two RRUs or RFUs can be combined only when the antenna mode is 2T2R, 2T4R, or 4T4R.
The two combined RRUs or RFUs work at the same frequency band and serve the same sector. For example, two 2T2R
RRUs or RFUs can serve a 4T4R cell, as shown below.

eRAN
3-3
Sectors with MIMO Mutual Aid Implemented
Multiple-input multiple-output (MIMO) mutual aid is implemented by cross-connecting RRU or RFU
antennas and exchanging data between sectors.
If MIMO mutual aid is implemented and an RRU or RFU in a sector is faulty, MIMO cells become
single-input single-output (SISO) cells. This ensures that each cell can still provide services.
Constraints on sectors with MIMO mutual aid implemented are described as follows:
 MIMO mutual aid can be implemented when the sectors work in 2T2R mode.
 MIMO mutual aid can be implemented when RRUs or RFUs are connected in star topology. Only three
RRUs or RFUs can be connected to an LBBP using common public radio interface (CPRI) ports 0 to 2.
Three antennas are connected to form three sectors.
 Assume that RRUs or RFUs 60, 61, and 62 are connected to CPRI ports 0 to 2. If the antenna mode is
2T2R, antenna ports used by sectors with MIMO mutual aid implemented must meet the following
combination requirements:
− Antenna port A of RRU or RFU 60 is combined with antenna port B of RRU or RFU 61.
Figure 3-2 shows antenna port connections for sectors with MIMO mutual aid implemented.

eRAN
3-4
Figure 3-2 Antenna port connections for sectors with MIMO mutual aid implemented
Sectors with Multiple RRUs Combined
Multiple RRUs can be combined to serve a cell. The transmitter combines downlink signals on each
RRU or selectively transmits them. The receiver combines the uplink signals from multiple RRUs or
selectively demodulates them. Multi-RRU combination is also called multi-carrier combination.
Multi-RRU combination has the following advantages:
 Increased cell coverage radius and less UE handovers
 Improved UE performance by reducing the number of cells, the area of cell boundaries, and
interference
 Reduced capacity expansion costs by splitting a cell into multiple cells
Table 3-1 illustrates the multi-RRU combination scenarios.
Table 3-1 Multi-RRU combination scenarios
Scenario Figure
Ultra-high-speed
railway

eRAN
3-5
Scenario Figure
Macro coverage
Wide coverage
3.2 Cell
A cell is a radio coverage area that provides services for users. All the joined cells provide coverage for
the entire radio network.
The number of cells supported by an eNodeB is calculated as follows:
Number of cells supported by an eNodeB = Number of sectors x Number of carriers
Figure 3-3 shows the mapping between sectors, carriers, and cells. This figure uses a typical 3 x 2
configuration as an example. Three sectors (sectors 0 to 2) cover a circle area. Each sector uses two
carriers, and each cell uses one carrier. There are a total of six cells.

eRAN
3-6
Figure 3-3 Mapping between sectors, carriers, and cells
Coverage is classified into overlapping coverage and separate coverage. Figure 3-4 shows the mapping
between cells and coverage areas.
Figure 3-4 Mapping between cells and coverage areas
Frequency Band
A cell can be configured with independent bandwidths in the uplink and downlink. The Cell.FreqBand
parameter can be set to a value from 1 to 14 or from 17 to 25. The uplink and downlink frequencies for a
cell must fall in the ranges listed in Table 3-2. For details, see 3GPP TS 36.104.

eRAN
3-7
Table 3-2 Mapping between the FreqBand parameter and frequencies
E-UTRA
Frequency Band
Number
Uplink Frequency Band
(FUL_low-FUL_high)
Downlink Frequency Band
(FDL_low-FDL_high)
1 1920 MHz 1980 MHz 2110 MHz 2170 MHz
2 1850 MHz 1910 MHz 1930 MHz 1990 MHz
3 1710 MHz 1785 MHz 1805 MHz 1880 MHz
4 1710 MHz 1755 MHz 2110 MHz 2155 MHz
5 824 MHz 849 MHz 869 MHz 894MHz
61
830 MHz 840 MHz 875 MHz 885 MHz
7 2500 MHz 2570 MHz 2620 MHz 2690 MHz
8 880 MHz 915 MHz 925 MHz 960 MHz
9 1749.9 MHz 1784.9 MHz 1844.9 MHz 1879.9 MHz
10 1710 MHz 1770 MHz 2110 MHz 2170 MHz
11 1427.9 MHz 1447.9 MHz 1475.9 MHz 1495.9 MHz
12 699 MHz 716 MHz 729 MHz 746 MHz
13 777 MHz 787 MHz 746 MHz 756 MHz
14 788 MHz 798 MHz 758 MHz 768 MHz
15 Reserved Reserved Reserved Reserved
16 Reserved Reserved Reserved Reserved
17 704 MHz 716 MHz 734 MHz 746 MHz
18 815 MHz 830 MHz 860 MHz 875 MHz
19 830 MHz 845 MHz 875 MHz 890 MHz
20 832 MHz 862 MHz 791 MHz 821 MHz
21 1447.9 MHz 1462.9 MHz 1495.9 MHz 1510.9 MHz
22 3410 MHz 3490 MHz 3510 MHz 3590 MHz
23 2000 MHz 2020 MHz 2180 MHz 2200 MHz
24 1626.5 MHz 1660.5 MHz 1525 MHz 1559 MHz
25 1850 MHz 1915 MHz 1930 MHz 1995 MHz
Note 1: Frequency band 6 is not applicable.

eRAN
3-8
Transmit Power
During cell setup, the maximum transmit power of an RF unit must be greater than its maximum
theoretical transmit power (Pmax_out). Pmax_out is determined by the following parameters:
 PDSCHCfg.ReferenceSignalPwr: the reference signal power.
 NRB: the maximum number of available RBs. For details, see 3GPP TS 36.211 V10.4.0 (2011-12).
 PA and PDSCHCfg.PB: the scaling factor indexes of the energy per resource element (EPRE) on the
physical downlink shared channel (PDSCH). PA is set by the CellDlpcPdschPa.PaPcOff parameter.
The formula for calculating Pmax_out is as follows:
Pmax_out = MAX{TypeA(Pmax_out), TypeB(Pmax_out)}
where
 TypeA(Pmax_out): the maximum transmit power configured for one TypeA symbol.
 TypeB(Pmax_out): the maximum transmit power configured for one TypeB symbol.
For definitions of TypeA and TypeB, see section 5.2 in 3GPP TS 36.213 V10.5.0 (2012-03).
The formulas for calculating TypeA(Pmax_out) and TypeB(Pmax_out) are as follows:
 TypeA(Pmax_out) = (PDSCHCfg.ReferenceSignalPwr x CellDlpcPdschPa.PaPcOff) x TypeA(NRE)
 TypeB(Pmax_out) = PDSCHCfg.ReferenceSignalPwr x TypeB(NRS) +
(PDSCHCfg.ReferenceSignalPwr x CellDlpcPdschPa.PaPcOff x AB  / ) x TypeB(NRE)
where
− TypeA(NRE): the number of resource elements (REs), excluding pilots, on one TypeA symbol, that is,
12 x NRB. For the mapping between cell bandwidths and NRB, see Table 3-3.
− TypeB(NRS): the number of pilots on one TypeB symbol. For details, see section 5.2 in 3GPP TS
36.213 V10.5.0 (2012-03).
− AB  /
: the cell-specific ratio obtained based on PDSCHCfg.PB. For the mapping between
PDSCHCfg.PB and AB  / , see Table 3-4. For details about AB  / , see section 5.2 in 3GPP TS
36.213 V10.5.0 (2012-03).
− TypeB(NRE): the number of REs, excluding pilots, on one TypeB symbol. For details, see section 5.2
in 3GPP TS 36.213 V10.5.0 (2012-03).
 If the TxBranch.TXMAXPWR parameter is configured, Pmax_out is the same as the value of
TxBranch.TXMAXPWR.
Table 3-3 Mapping between cell bandwidths and the maximum number of available RBs
Cell Bandwidth (MHz) 1.4 3 5 10 15 20
Maximum Number of
Available RBs
6 15 25 50 75 100

eRAN
3-9
Table 3-4 Mapping between the cell-specific ratio AB  / and PDSCHCfg.PB
PDSC
HCfg.
PB
AB  /
One Antenna
Port
Two or Four
Antenna Ports
0 1 5/4
1 4/5 1
2 3/5 3/4
3 2/5 1/2
Users must configure the reference signal power, bandwidth, CellDlpcPdschPa.PaPcOff,
PDSCHCfg.PB, and maximum actual transmit power of an RF unit according to the specifications for the
PDSCHCfg managed object (MO) in eNodeB Parameter Reference.

eRAN
Cell Management 4 Engineering Guidelines
4-1
4 Engineering Guidelines
This chapter provides engineering guidelines for cell management.
4.1 When to Use Cell Management
The major function of eNodeBs is to provide radio cell coverage for UEs. Cell management is mandatory
and must be enabled.
4.2 Information to Be Collected
Before deployment of this feature, data on network application scenarios and information about the
frequency band, bandwidth, network coverage, and power limit must be collected. For details about
information to be collected, see section 4.4.2 "Data Preparation."
4.3 Network Planning
None
4.4 Deploying Cell Management
4.4.1 Deployment Requirements
Generic Requirements
Requirements for Licenses
The following table lists the license control items related to cell establishment. Operators must purchase
and activate the licenses including the control items RF Output Power (per 20W)(FDD), Carrier
Bandwidth(per 5MHz)(FDD), Cell License(per Cell)(FDD), and Resource Block(per RB)(FDD).. Licenses
including other control items can also be purchased based on the network plan.
Feature License Control Item Name
NA RF Output Power (per 20W)(FDD)
NA Carrier Bandwidth(per 5MHz)(FDD)
LOFD-001001DL 2x2 MIMO DL 2x2 MIMO(per Cell)(FDD)
LOFD-001002UL 2x2 MU-MIMO UL 2x2 MU-MIMO(per Cell)(FDD)
LOFD-001003DL 4x2 MIMO DL 4x2 MIMO(per Cell)(FDD)
LOFD-001005UL 4-Antenna Receive UL 4-Antenna Receive Diversity(per Cell)(FDD)
LOFD-001007 High Speed Mobility High Speed Mobility(per Cell)(FDD)
LOFD-001008 Ultra High Speed Mobility Ultra High Speed Mobility(per Cell)(FDD)
LOFD-001009 Extended Cell Access Radius Extended Cell Access Radius(per Cell)(FDD)
NA Cell License(per Cell)(FDD)
LOFD-001058UL 2x4 MU-MIMO UL 2x4 MU-MIMO
LOFD-001060DL 4X4 MIMO DL 4X4 MIMO

eRAN
4-2
Feature License Control Item Name
N/A Resource Block(per RB)(FDD)
N/A RF Transmit Channel(per Channel)(FDD)
N/A RF Receive Channel(per Channel)(FDD)
N/A BB Transmit Channel(per Channel)(FDD)
N/A BB Receive Channel(per Channel)(FDD)
Requirements for Hardware
Unless otherwise specified, eNodeBs use optical modules that support the rate of 2.5 Gbit/s.
Other Requirements
Bandwidths of the cells provided by the RRUs or RFUs must fall in the frequency bands supported by the
RRUs or RFUs.
Scenario-specific Requirements
Scenario 1: Establishing a Cell in a Common Sector Without RRU or RFU Combination
For details about constraints on cell frequencies and bandwidths, see section 3.2 "Cell."
Scenario 2: Establishing a Cell in a Common Sector with RRU or RFU Combination
 The two RRUs or RFUs support the same frequency band.
 Two 2T2R RRUs or RFUs can be combined to provide a 4T4R cell.
 The optical fibers used to connect the two RRUs to the BBU must have similar lengths with a length
difference less than 100 m.
 For RRUs or RFUs working only in LTE mode:
− Two 1T2R RRUs or RFUs of the same type can be combined and configured to work in 2T mode.
− Two 2T2R RRUs or RFUs of the same type can be combined and configured to work in 4T mode.
 For RRUs or RFUs working in multiple modes: Two 1T2R RRUs or RFUs can be combined and
configured to work in 2T mode.
 To combine two RRUs or RFUs of different types, upgrade the eNodeB software version to the
corresponding version before the combination.
 The RRUs or RFUs are connected to the same LBBP in a star topology.
In multi-mode dual-star topology, the two RRUs must be connected to the same LBBP.
 For details about constraints on cell frequencies and bandwidths, see section 3.2 "Cell."

eRAN
4-3
Scenario 3: Establishing a Cell in a Sector with Multiple RRUs Combined
The implementation of Ultra-high-speed railway scenario has limitations and causes performance instability. Therefore,
this scenario is not recommended in eRAN3.0.
 The two RRUs or RFUs are 2T2R RRUs or 2T2R RFUs.
 The bandwidth supported by the RRUs or RFUs is 10 MHz or 20 MHz.
 The RRUs or RFUs are connected to the same LBBP in a star topology.
 If the RRUs are connected in a chain topology, a chain of a maximum of two levels is supported.
LRFUs do not support the cascading connection.
In multi-mode dual-star topology, the two RRUs must be connected to the same baseband board.
 If the RRUs or RFUs providing 20 MHz cells are connected in a two-level chain topology, optical
modules supporting the 4.9 Gbit/s rate are required and the RRUs or RFUs must support the
negotiated rate of 4.9 Gbit/s.
 Only the RRU3821E supports cascading connections (two to eight levels) to provide a multi-RRU cell
with digital combination and division and uses CPRI compression to save CPRI bandwidth resources.
A multi-RRU cell with digital combination and division provided by cascading RRU3821Es has the
following characteristics:
− Four or less levels of cascading connections of RRU3821Es are recommended. Otherwise, system
performance cannot be ensured.
− The cell can be a 2T2R or 1T1R cell, and supports the bandwidth of 5, 10, 15, or 20 MHz.
− The cell supports only normal CP.
− The cell can be established only on the LBBPd.
− The cell does not support UL CoMP.
− The cell does not support either cascading connections on different CPRI links or the ring topology.
Scenario 4: Establishing a Cell in a Sector with MIMO Mutual Aid Implemented
 The RRU or RFU models and frequency bands supported by the RRUs or RFUs must be the same.
 Three RRUs or RFUs are required.
 The cells are 2T2R cells.
 The optical fibers used to connect the three RRUs to the BBU must have similar lengths with a length
difference less than 100 m.
 If the RRUs or RFUs are connected in a star, ring, or load-sharing topology, the RRUs or RFUs must
be connected to the same baseband board.
In multi-mode dual-star topology, the two RRUs must be connected to the same baseband board.
 The antenna ports must be combined in the way described in section 3.1 "Sectors."
Scenario 5: Establishing a Four-Antenna Cell in a Common Sector Without RRU or RFU
Combination
 The RRUs or RFUs are 2T4R or 4T4R RRUs or RFUs. For details about RRU or RFU models, see
3900 Series LTE eNodeB Technical Description.

eRAN
4-4
 If the cell bandwidth is 15 MHz or 20 MHz, optical modules that support the 4.9 Gbit/s rate are
required.
In the load-sharing topology where RRUs or RFUs are connected to the same baseband board, optical modules that
support the 2.5 Gbit/s rate can be used but the load-sharing topology is not recommended.
Scenario 6: Establishing Two Dual-Carrier Cells in a Common Sector Without RRU or RFU
Combination
 The RRUs or RFUs support multiple carriers. For details about RRU or RFU models, see 3900 Series
LTE eNodeB Technical Description.
 A standard bandwidth and a customized bandwidth can be used for the two cells.
 The two cells use the same sector.
 The bandwidths configured for the two cells are within the frequency bands supported by the RRUs or
RFUs.
 The two cells are configured with non-overlapping frequencies.
 The network topology is star, chain, ring, or load sharing.
4.4.2 Data Preparation
This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
evolved packet core (EPC) or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.
Generic Data
The following table describes the parameters that must be set in a Sector MO to configure a sector.
Parameter Name Parameter ID Source Setting Description
Sector No. Sector.SECN Network plan
(negotiation
not required)
Set this parameter based on the network plan.
Ensure that each sector number is unique.
Geo-coordinate
data format
Sector.GCDF Network plan
(negotiation
not required)
This parameter can be set to DEG or SEC.
The LONGITUDE and LATITUDE parameters
are valid only when this parameter is set to
DEG. The ANTLATITUDESECFORMAT and
ANTLONGITUDESECFORMAT parameters
are valid only when this parameter is set to
SEC. The default value is DEG.
Antenna longitude
with second
Sector.ANTLO
NGITUDESECF
Network plan
(negotiation
This parameter is mandatory only when the
GCDF parameter is set to SEC. Set this

eRAN
4-5
format ORMAT not required) parameter as required.
Antenna latitude
with second
format
Sector.ANTLA
TITUDESECFO
RMAT
Network plan
(negotiation
not required)
GCDF parameter is set to SEC. Set this
parameter as required.
Longitude Sector.LONGIT
UDE
Network plan
(negotiation
not required)
Set this parameter as required. This
parameter is mandatory only when the GCDF
parameter is set to DEG.
Latitude Sector.LATITU
DE
Network plan
(negotiation
not required)
Set this parameter as required. This
parameter is mandatory only when the GCDF
parameter is set to DEG.
Sector mode Sector.SECM Network plan
(negotiation
not required)
This parameter can be set to
AIDMIMO(mutual-aid MIMO) or the default
value NormalMIMO(Normal MIMO).
For details about setting constraints, see
eNodeB Parameter Reference.
Antenna mode Sector.ANTM Network plan
(negotiation
not required)
For details about setting constraints, see
eNodeB Parameter Reference.
CombMode Sector.COMBM Network plan
(negotiation
not required)
This parameter specifies the RRU
combination mode for the sector.
Cabinet No. of the
RRU where
antenna port n is
located
CNn Network plan
(negotiation
not required)
n indicates the antenna port number. The
value of n can be from 1 to 16, depending on
the value of ANTM.
Subrack No. of
the RRU where
antenna port n is
located
SRNn Network plan
(negotiation
not required)
the value of ANTM.
Slot No. of the
RRU where
antenna port n is
located
SNn Network plan
(negotiation
not required)
the value of ANTM.
Port No. of
antenna
connector n
PNn Network plan
(negotiation
not required)
the value of ANTM.
Sector name Sector.SECTO
RNAME
Network plan
(negotiation
not required)
This parameter specifies the sector name,
which is a string of 30 characters or less.
Altitude Sector.ALTITU
DE
Network plan
(negotiation
This parameter specifies the altitude of the

eRAN
4-6
not required) sector in the WGS 84 coordinate system.
WGS stands for World Geodetic System.
UncertSemiMajor Sector.UNCER
TSEMIMAJOR
Network plan
(negotiation
not required)
This parameter specifies the length of the
semi-major axis of the sector location
uncertainty area. The positioning accuracy
has a negative correlation with the parameter
value.
UncertSemiMinor Sector.UNCER
TSEMIMINOR
Network plan
(negotiation
not required)
This parameter specifies the length of the
semi-minor axis of the sector location
uncertainty area. The positioning accuracy
value.
OrientOfMajorAxis Sector.ORIENT
OFMAJORAXI
S
Network plan
(negotiation
not required)
This parameter specifies the orientation of the
major axis of the sector location uncertainty
area, expressed by the counter-clockwise
angle in degrees between the major axis and
the north direction. The positioning accuracy
value.
UncertAltitude Sector.UNCER
TALTITUDE
Network plan
(negotiation
not required)
This parameter specifies the estimated
altitude of the sector location uncertainty area
in the WGS 84 coordinate system. The
positioning accuracy has a negative
correlation with the parameter value.
Confidence Sector.CONFID
ENCE
Network plan
(negotiation
not required)
This parameter specifies the confidence level
for the sector location uncertainty area. The
positioning accuracy has a negative
correlation with the parameter value.
Omni Mode Sector.OMNIFL
AG
Network plan
(negotiation
not required)
This parameter specifies whether cells in the
sector are omnidirectional cells.
The following table describes the parameters that must be set in a CnOperator MO to configure an
operator.
CN Operator ID
CnOperator.Cn
OperatorId
Network plan
(negotiation
not required)
This parameter specifies the index of the
operator. Its value range is 0 to 3.
CN Operator
name
CnOperator.Cn
OperatorName
Network plan
(negotiation
This parameter specifies the name of the

eRAN
4-7
required) operator.
CN Operator type
CnOperator.Cn
OperatorType
Network plan
(negotiation
required)
This parameter specifies the operator type:
primary or secondary. Each eNodeB can be
configured with only one primary operator, but
multiple secondary operators.
Mobile country
code
CnOperator.Mc
c
Network plan
(negotiation
required)
This parameter specifies the mobile country
code (MCC) of the operator. An MCC is a
string of three decimal digits.
Mobile network
code
CnOperator.Mn
c
Network plan
(negotiation
required)
This parameter specifies the mobile network
code (MNC) of the operator. An MNC is a
string of two or three decimal digits.
The following table describes the parameters that must be set in a CnOperatorTa MO to configure a
tracking area for an operator.
Tracking area ID
CnOperatorTa.
TrackingAreaId
Network plan
(negotiation
required)
This parameter uniquely identifies a tracking
area.
CN Operator ID
CnOperatorTa.
CnOperatorId
Network plan
(negotiation
not required)
operator.
Tracking area
code
CnOperatorTa.
Tac
Network plan
(negotiation
required)
This parameter is used by the EPC to
determine the area within which paging
messages are sent. One tracking area is
comprised of one or more cells.
The following table describes the parameters that must be set in a Cell MO to configure a cell.
Local cell ID Cell.LocalCellI
d
Network plan
(negotiation
not required)
This parameter specifies the local ID of a cell.
It uniquely identifies a cell within an eNodeB.
Cell name Cell.CellName Network plan
(negotiation
not required)
-
Sector No. Cell.SectorId Network plan
(negotiation
not required)
This parameter identifies the sector to which
the cell belongs.
Csg indicator Cell.CsgInd Network plan Huawei eNodeBs currently do not support

eRAN
4-8
(negotiation
not required)
CSG cells.
Uplink cyclic prefix
length
Cell.UlCyclicPr
efix
Network plan
(negotiation
not required)
This parameter specifies whether to use the
normal or extended cyclic prefix (CP) in the
uplink. The extended CP is used in a complex
environment, for example, with a strong
multipath effect or long delay. In a cell, the
uplink CP length can be either the same as or
different from the downlink CP length. In
addition, the uplink and downlink CP lengths
of a cell must be the same as those of the
other cells on the same LBBP.
Retain the default value
NORMAL_CP(Normal).
Downlink cyclic
prefix length
Cell.DlCyclicPr
efix
Network plan
(negotiation
not required)
This parameter specifies whether to use the
normal or extended CP in the downlink. The
extended CP is used in a complex
environment, for example, with a strong
multipath effect or long delay. In a cell, the
downlink CP length can be either the same as
or different from the uplink CP length. In
addition, the uplink and downlink CP lengths
of a cell must be the same as those of the
other cells on the same LBBP.
Retain the default value
NORMAL_CP(Normal).
Frequency band Cell.FreqBand Network plan
(negotiation
not required)
-
Uplink earfcn
indication
Cell.UlEarfcnCf
gInd
Network plan
(negotiation
not required)
The default value NOT_CFG(Not configure)
is recommended.
Uplink earfcn Cell.UlEarfcn Network plan
(negotiation
not required)
This parameter is optional, depending on the
value of the UlEarfcnCfgInd parameter:
 If UlEarfcnCfgInd is set to
CFG(Configure), UlEarfcn must be set.
 If UlEarfcnCfgInd is set to NOT_CFG(Not
configure), UlEarfcn does not need to be
set.
Downlink earfcn Cell.DlEarfcn Network plan
(negotiation
not required)
This parameter specifies the downlink
EARFCN of the cell. The downlink frequency
identified by the EARFCN must be located in
the band specified by the FreqBand
parameter. If the FddTddInd parameter is set
to CELL_TDD(TDD) and the UlEarfcnCfgInd
parameter is set to CFG(Configure), the

eRAN
4-9
DlEarfcn and UlEarfcn parameters must be
set to the same value.
Uplink bandwidth Cell.UlBandWi
dth
Network plan
(negotiation
not required)
-
Downlink
bandwidth
Cell.DlBandWi
dth
Network plan
(negotiation
not required)
-
Cell ID Cell.CellId Network plan
(negotiation
not required)
-
Physical cell ID Cell.PhyCellId Network plan
(negotiation
not required)
-
Additional
spectrum
emission
Cell.Additional
SpectrumEmis
sion
Network plan
(negotiation
not required)
Retain the default value during initial
configuration. This parameter restricts the
emission power of UEs in the cell.
Cell FDD TDD
indication
Cell.FddTddInd Network plan
(negotiation
not required)
This parameter specifies the duplex mode of
the cell, which must be consistent with the
model of the RRU or RFU serving the cell.
Cell specific offset Cell.CellSpecifi
cOffset
Network plan
(negotiation
not required)
This parameter specifies the cell-specific
offset for the cell. The probability of
measurement reporting for handovers from
the cell to its intra-frequency neighboring cells
value.
Retain the default value 0 during initial
configuration.
Intra frequency
offset
Cell.QoffsetFre
q
Network plan
(negotiation
not required)
This parameter specifies the
frequency-specific offset for the cell. It is
contained in the measurement configuration
delivered to UEs.
Retain the default value 0 during initial
configuration.
Root sequence
index
Cell.RootSequ
enceIdx
Network plan
(negotiation
not required)
logical root sequence, which is used to derive
the preamble sequence. Each logical root
sequence corresponds to a physical root
sequence. For details about setting
constraints, see eNodeB MO Reference.
High speed flag Cell.HighSpee
dFlag
Network plan
(negotiation
not required)
-
Preamble format Cell.PreambleF
mt
Network plan
(negotiation
-

eRAN
4-10
not required)
Cell radius Cell.CellRadius Network plan
(negotiation
not required)
-
Customized
bandwidth
configure indicator
Cell.Customize
dBandWidthCf
gInd
Network plan
(negotiation
not required)
This parameter specifies whether to configure
customized bandwidths for the cell. The
default value NOT_CFG(Not configure) is
recommended.
Customized uplink
bandwidth
Cell.Customize
dULBandWidth
Network plan
(negotiation
not required)
CustomizedBandWidthCfgInd parameter is
set to CFG(Configure).
Customized
downlink
bandwidth
Cell.Customize
dDLBandWidth
Network plan
(negotiation
not required)
CustomizedBandWidthCfgInd parameter is
set to CFG(Configure).
Emergency Area
Id indicator
Cell.Emergenc
yAreaIdCfgInd
Network plan
(negotiation
not required)
This parameter specifies whether to set an
emergency area ID. The default value is
NOT_CFG(Not configure). The default value
is recommended.
Emergency Area
ID
Cell.Emergenc
yAreaId
Network plan
(negotiation
not required)
This parameter is required only when the
EmergencyAreaIdCfgInd parameter is set to
CFG(Configure).
Ue max power
allowed configure
indicator
Cell.UePowerM
axCfgInd
Network plan
(negotiation
not required)
This parameter specifies whether to set the
maximum transmit power that a UE can apply
to uplink transmission in the cell. The default
value is NOT_CFG(Not configure). The
default value is recommended.
Max transmit
power allowed
Cell.UePowerM
ax
Network plan
(negotiation
not required)
UePowerMaxCfgInd parameter is set to
CFG(Configure).
Flag of Multi-RRU
Cell
Cell.MultiRruC
ellFlag
Network plan
(negotiation
not required)
The default value is
BOOLEAN_FALSE(False). The default value
is recommended.
Mode of
Multi-RRU Cell
Cell.MultiRruC
ellMode
Network plan
(negotiation
not required)
MultiRruCellFlag parameter is set to
BOOLEAN_TRUE(True).
CPRI
Compression
Cell.CPRICom
pression
Network plan
(negotiation
not required)
-
The following table describes the parameters that must be set in a CellOp MO to configure a cell
operator.

eRAN
4-11
Local cell ID
CellOp.LocalC
ellId
Network plan
(negotiation
not required)
This parameter specifies the local ID of a cell
and uniquely identifies a cell within an
eNodeB.
Tracking area ID
CellOp.Trackin
gAreaId
Network plan
(negotiation
not required)
This parameter specifies the tracking area ID
of the cell and uniquely identifies an operator
within the cell.
Cell reserved for
operator
CellOp.CellRes
ervedForOp
Network plan
(negotiation
not required)
-
Operator uplink
RB used ratio
CellOp.OpUlRb
UsedRatio
Network plan
(negotiation
not required)
This parameter specifies the percentage of
RBs occupied by the operator on the PUSCH
when RAN sharing is enabled at the eNodeB
and the cell-level switch of RAN sharing is
turned on. If the data volume is sufficient, the
percentage of RBs occupied by each operator
will reach the preset value. Modifications on
this parameter affect operators' percentages
of RBs.
Operator downlink
RB used ratio
CellOp.OpDlRb
UsedRatio
Network plan
(negotiation
not required)
This parameter specifies the percentage of
RBs occupied by the operator on the PDSCH
when RAN sharing is enabled at the eNodeB
and the cell-level switch of RAN sharing is
turned on. If the data volume is sufficient, the
percentage of RBs occupied by each operator
will reach the preset value. Modifications on
this parameter affect operators' percentages
of RBs.
Scenario-specific Data
Sector mode
Sector.SECM Network plan (negotiation
not required)
Set this parameter to
NormalMIMO(Normal
MIMO).
Antenna mode
Sector.ANTM Network plan (negotiation
not required)
Set this parameter to 2T2R.
CombMode
Sector.COMBM Network plan (negotiation
not required)
COMBTYPE_SINGLE_RRU.

eRAN
4-12
Scenario 2: Establishing a Cell in a Common Sector with Two RRUs or RFUs Combined
Sector mode
Sector.SECM Network plan
(negotiation not required)
NormalMIMO(Normal
MIMO).
Antenna mode
Sector.ANTM Network plan
CombMode
Sector.COMBM Network plan
Sector mode
NormalMIMO(Normal
MIMO).
Antenna mode
CombMode
COMBTYPE_TWO_RRU.
DIGITAL_COMBINATION
only for the RRU3821E.
Flag of Multi-RRU
Cell
Cell.MultiRruCellFlag Network plan
(negotiation not
required)
BOOLEAN_TRUE(True)
Mode of Multi-RRU
Cell
Cell.MultiRruCellMode Network plan
(negotiation not
required)
-

eRAN
4-13
Sector mode
(negotiation not
required)
AIDMIMO(mutual-aid MIMO).
Antenna mode
(negotiation not
required)
Combination
Sector mode
(negotiation not
required)
NormalMIMO(Normal MIMO).
Antenna mode
(negotiation not
required)
CombMode
(negotiation not
required)
Combination
Sector No. Cell.SectorId Network plan
(negotiation not
required)
The two cells provided by the two
carriers have the same sector.
Downlink earfcn Cell.DlEarfcn Network plan
(negotiation not
required)
The two cells provided by the two
carriers must be configured with
non-overlapping frequencies.
4.4.3 Hardware Installation
Hardware installation is required only for the following scenarios where a cell is established in a sector
with:

eRAN
4-14
 MIMO mutual aid implemented. For information about how to connect the RRUs/RFUs and the
antennas, see Figure 3-2.
 Multiple RRUs combined. Table 4-1 describes the installation requirements for RRUs serving the same
cell.
Table 4-1 Requirements and examples of installing multiple combined RRUs
Installation Requirement Example
If the RRUs are not installed in a straight
line, the spacing between any two RRUs
cannot be greater than 1000 m. As shown
in the figure, four RRUs are installed to
serve cell A. The spacing between RRU1
and RRU4 is the largest and cannot
exceed 1000 m.
If RRUs are installed in a straight line, the
spacing between each pair of neighboring
RRUs cannot be greater than 1000 m. As
shown in the figure, four RRUs are
installed to serve cell B. The spacing
between two neighboring RRUs (for
example, RRU1 and RRU2) cannot exceed
1000 m.
If RRUs are cascaded, the total length of
optical fibers connecting all of the RRUs in
a cell cannot exceed 5 km. As shown in the
figure, Ln represents the length of the
optical fiber between two neighboring
RRUs that serve cell C. The sum of L1, L2,
and L3 cannot be greater than 5 km.
If RRUs are cascaded to an LBBP board,
the total length of optical fibers connecting
all of the RRUs and the LBBP board
cannot exceed 20 km. As shown in the
figure, the sum of L1, L2, L3, and L4
cannot be greater than 20 km.

eRAN
4-15
4.4.4 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 4.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
Sectors
Use an internal template.
Cells
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 4.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 Basic Parameters
*LocalCellID, *CellName, *CellId, *SectorId,
*FrequencyBand, UlEarfcnCfgInd, *DlEarfcn,
UlEarfcn, CsgInd, UlCyclicPrefix,
DlCyclicPrefix, *DlBandwidth, *UlBandwidth,
*PCI, AdditionalSpectrumEmission,
CellSpecificOffset, QoffsetFreq,
HighSpeedFlag, PreambleFmt, CellRadius,
Customized bandwidth configure indicator,
Customized uplink bandwidth(0.1MHz),
Customized downlink bandwidth(0.1MHz),
Emergency Area Id indicator, Emergency Area
ID, Ue max power allowed configure indicator,
Max transmit power allowed(dBm), Flag of
Multi-RRU Cell, Mode of Multi-RRU Cell,
CPRICompression, ReferenceSignalPwr,
*RootSequenceIdx, SpecialSubframePatterns,
SubframeAssignment, CellReselPriority,
*FddTddInd,
CnOperator CnOperator
*Operator ID, *Operator name, *Operator type,
*Mcc, *Mnc

eRAN
4-16
MO Parameter Group Name Parameter
CnOperatorTA Cell Basic Parameters TrackingAreaId, *TAC, CnOperatorId
CellOp Cell Basic Parameters
*LocalCellID, *TrackingAreaId,
CellReservedForOp, OpUlRbUsedRatio,
OpDlRbUsedRatio
Configuring a Single eNodeB Using MML Commands
Step 1 Run the ADD SECTOR command to add a sector.
Step 2 Run the ADD CNOPERATOR command to add an operator.
Step 3 Run the ADD CNOPERATORTA command to add a tracking area for the eNodeB.
Step 4 Run the ADD CELL command to add a cell.
Step 5 Run the ADD CELLOP command to add a cell operator.
Step 6 Run the ACT CELL command to activate the cell.
----End
Scenario 2: Establishing a Cell in a Common Sector with RRU or RFU Combination
Example: To add a 2T4R sector, run the following command with SECTOR.ANTM set to 2T4R:
ADD SECTOR: SECN=0, GCDF=DEG, LONGITUDE=0, LATITUDE=0, ANTM=2T4R, CN1=0, SRN1=60, SN1=0, PN1=R0A,
CN2=0, SRN2=60, SN2=0, PN2=R0B, CN3=0, SRN3=61, SN3=0, PN3=R0A, CN4=0, SRN4=61, SN4=0, PN4=R0B,
ALTITUDE=3;
----End
Scenario 3: Establishing a Cell in a Sector with Multi-RRU Combination
Example: To add a sector with two antennas of each RRU providing a coverage area, run the
following command with SECTOR.ANTM set to 2T2R, SECTOR.SECM to NormalMIMO, and
SECTOR.COMBM to COMBTYPE_MULTI_RRU:
ADD SECTOR: GCDF=DEG, ANTM=2T2R, SECM=NormalMIMO, COMBM=COMBTYPE_MULTI_RRU, CN1=0, SRN1=60,
SN1=0, PN1=R0A, CN2=0, SRN2=60, SN2=0, PN2=R0B, CN3=0, SRN3=61, SN3=0, PN3=R0A, CN4=0, SRN4=61, SN4=0,
PN4=R0B, ALTITUDE=3;

eRAN
4-17
The COMBM parameter is set to DIGITAL_COMBINATION only for the RRU3821E.
Example: Run the following command with CELL.MultiRruCellFlag set to BOOLEAN_TRUE,
CELL.MultiRruCellMode to TWO_RRU_COMBINATION or DIGITAL_COMBINATION:
ADD CELL: LocalCellId=0, CellName="cell 0", SectorId=0, FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=2900,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0, PhyCellId=0, FddTddInd=CELL_FDD,
RootSequenceIdx=0, MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=TWO_RRU_COMBINATION;
----End
MIMO mutual aid requires that a group of sectors be added. Example: Run the following
commands with SECTOR.ANTM in each command set to 2T2R:
ADD SECTOR: SECN=0, GCDF=DEG, LONGITUDE=0, LATITUDE=0, ANTM=2T2R, SECM=AIDMIMO, CN1=0, SRN1=60,
SN1=0, PN1=R0A, CN2=0, SRN2=61, SN2=0, PN2=R0B, ALTITUDE=3;
Note that RET 1 and RET 2 for each sector must be correctly connected to antenna ports on
different RRUs.
----End
Combination
Example: To add a 2T4R sector, run the following command with SECTOR.ANTM set to 2T4R:
ADD SECTOR: SECN=0, GCDF=DEG, LONGITUDE=0, LATITUDE=0, ANTM=2T4R, CN1=0, SRN1=60, SN1=0, PN1=R0A,
CN2=0, SRN2=60, SN2=0, PN2=R0B, CN3=0, SRN3=60, SN3=0, PN3=R0C, CN4=0, SRN4=60, SN4=0, PN4=R0D,
ALTITUDE=3;

eRAN
4-18
----End
Combination
Example 1: To add two dual-carrier cells, run the following commands with CELL.SectorId in
each command set to the same value and CELL.DlEarfcn in the commands set to two
non-adjacent frequencies:
ADD CELL: LocalCellId=0, CellName="multi-carrier cell 0", SectorId=0, FreqBand=7, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=2900, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0, PhyCellId=0,
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG;
FddTddInd=CELL_FDD, RootSequenceIdx=1, CustomizedBandWidthCfgInd=NOT_CFG;
Example 2: Customized bandwidths can also be configured based on the frequency bands
operators applied for. Assume that the operator bandwidth is 19.8 MHz. run the following
command with CELL.CustomizedBandWidthCfgInd set to CFG,
CELL.CustomizedDLBandWidth and CELL.CustomizedULBandWidth set to 98:
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=CFG, CustomizedDLBandWidth=98,
CustomizedULBandWidth=98;
FddTddInd=CELL_FDD, RootSequenceIdx=1, CustomizedBandWidthCfgInd=CFG, CustomizedDLBandWidth=98,
CustomizedULBandWidth=98;
In this example, the value 98 indicates the customized uplink and downlink bandwidths are both
9.8 MHz, the frequency spacing between the uplink and downlink bandwidths is 0.2 MHz.
Operators need to be separately added for the two cells. Different operators can be added.
----End

eRAN
4-19
4.4.5 Activation Verification
Scenario 1: Establishing a Cell in a Common Sector Without RRU or RFU
Combination
The verification procedure is as follows:
Step 1 On the M2000 client or eNodeB local maintenance terminal (LMT), run the DSP CELL command
to query the status of the cell.
If Cell instance state is Normal, the cell is successfully activated.
The expected value of Cell topo type is Basic Type.
Step 2 Use a UE to access this cell.
If the UE successfully accesses the cell, the cell is working properly.
----End
Scenario 2: Establishing a Cell in a Common Sector with Two RRUs or RFUs
Combined
The activation verification for scenario 2 is the same as that for scenario 1 described earlier in this
section.
Step 1 On the M2000 client or eNodeB LMT, run the DSP CELL command to query the status of the
cell.
The expected value of Cell topo type is TWO RRU Combination.
----End
Step 1 On the M2000 client or eNodeB LMT, run the DSP CELL command to query the status of the
cell.
The expected value of Cell topo type is Mutual-Aid MIMO Type.
----End

eRAN
4-20
Scenario 5: Establishing a Four-Antenna Cell in a Common Sector Without
RRU or RFU Combination
section.
Scenario 6: Establishing Two Dual-Carrier Cells in a Common Sector Without
RRU or RFU Combination
section.
4.4.6 Reconfiguration
eNodeBs can be reconfigured in batches on the CME. Modify related parameters using one of the
following methods:
 Batch reconfiguration (which is recommended for reconfiguration)
 Reconfiguration using the batch modification center
 Reconfiguration using templates
 Reconfiguration using radio data planning files
For details, see eNodeB Reconfiguration Guide.
Scenario 1: Reconfiguring Bandwidths
Prerequisites:
 New cell bandwidths are planned.
 The baseband resources are sufficient, allowing the cell bandwidths to be modified without adding
baseband resources.
If the baseband resources are insufficient, add an LBBP to increase the capacity. Establish a new cell
meeting the bandwidth requirements on this added LBBP.
The following table describes the parameters that must be set in a Cell MO to reconfigure a cell.
Uplink bandwidth Cell.UlBandWidth
Network plan
Set this parameter based on
the network plan.
Downlink bandwidth Cell.DlBandWidth
Network plan
the network plan.
Scenario 2: Reconfiguring a Sector Without RRU or RFU Combination as a
Sector with two RRUs or RFUs Combined
Prerequisites:
 Hardware is planned and hardware capacity is expanded with another RRU or RFU connected to the
same LBBP.
 The baseband resources are sufficient. For details about the baseband resource specifications, see
DBS3900 Hardware Description.

eRAN
4-21
The following table describes the parameters that must be set in a Sector MO to reconfigure a sector.
Antenna mode Sector.ANTM
Network plan (negotiation
not required)
the network plan.
Scenario 3: Reconfiguring the Cell Radius, Preamble Format, High Speed Flag,
or Root Sequence Index
Prerequisite: The parameters Cell radius, Preamble format, High speed flag, and Root sequence
index are planned based on the parameter relationships. For details about the relationships, see
eNodeB MO Reference.
Cell radius Cell.CellRadius Network plan
(negotiation not
required)
Set this parameter based on the
network plan.
Root sequence index Cell.RootSequenceIdx Network plan
(negotiation not
required)
network plan.
High speed flag Cell.HighSpeedFlag Network plan
(negotiation not
required)
network plan.
Preamble format Cell.PreambleFmt Network plan
(negotiation not
required)
network plan.
Scenario 4: Reconfiguring Cell Frequencies
Prerequisites:
 The intra-frequency blacklist is blank.
 All configurations of intra-frequency neighboring cells are removed.
 The new frequency is different from any configured neighboring E-UTRA frequency.
Downlink earfcn
Cell.DlEarfcn Network plan
(negotiation not
required)
network plan.
Uplink earfcn
Cell.UlEarfcn Network plan
(negotiation not
required)
This parameter is optional.
network plan.

eRAN
4-22
Frequency band Cell.FreqBand Network plan
(negotiation not
required)
network plan. This parameter
specifies the frequency band where
the cell operates.
Scenario 5: Reconfiguring the Cell ID
Prerequisite: Neighboring relationship configurations for the cell are removed.
Parameter
Name
Parameter ID Source Setting Description
Cell ID CellId
Network plan (negotiation
not required)
network plan.
Scenario 6: Reconfiguring the PCI
Prerequisite: The new physical cell identifier (PCI) is different from the PCI of any intra-frequency
neighboring cell or the PCI of any blacklisted intra-frequency cell.
Physical cell ID Cell.PhyCellId
Network plan
(negotiation not
required)
network plan. Ensure that neighboring
relationships are planned.
4.4.7 Deactivation
None
4.5 Optimization
None
4.6 Troubleshooting
4.6.1 Fault Description
Cell status is abnormal.
4.6.2 Fault Handling
Step 1 Start cell status monitoring on the M2000 client to check the cell status.

eRAN
4-23
Step 2 If an alarm indicating problems such as cell unavailability and cell capability degradation is
generated, clear the alarm by following the alarm handling suggestions in eNodeB Alarm
Reference.
The following table lists the common alarms related to a cell.
Alarm ID Alarm Name Alarm
Type
Severity Network Management
Type
ALM-26816 Licensed Feature Unusable Fault Minor Operating system
ALM-26818 No License Running in System Fault Critical Operating system
ALM-29240 Cell Unavailable Fault Major Signaling system
ALM-29243 Cell Capability Degraded Fault Major Signaling system
ALM-29245 Cell Blocked Fault Major Signaling system
ALM-29247 Cell PCI Conflict Fault Warning Signaling system
Step 3 If the cell is in the outage or sleeping state, rectify the fault by referring to Cell Outage
Management Feature Parameter Description.
----End

eRAN
Cell Management 5 Parameters
5-1
5 Parameters
Table 5-1 Parameter description
MO Parameter ID MML Command Feature ID Feature
Name
Description
Cell AdditionalSpectrum
Emission
ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
Meaning:Indicates the
additional spectrum emission,
which restricts the emission
power of the UEs in the cell.
For details, see the 3GPP TS
36.101.
GUI Value Range:1~32
Unit:None
Actual Value Range:1~32
Default Value:1
Sector ALTITUDE ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the altitude
of the sector in the WGS-84
coordinate system. If the
value is greater than 0, the
sector is above the ellipsoid
surface in the WGS-84
coordinate system. If the
value is less than 0, the sector
is below the ellipsoid surface
in the WGS-84 coordinate
system. For details, see
3GPP TS 23.032 and 3GPP
TS 36.455.
GUI Value
Range:-32767~32767
Unit:m
Actual Value
Range:-32767~32767
Default Value:None
Sector ANTLATITUDESE
CFORMAT
ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the latitude
of the sector in the WGS-84
coordinate system.
characters
Unit:s
characters

eRAN
5-2
Name
Description
Default Value:0:0:0
Sector ANTLONGITUDES
ECFORMAT
ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the
longitude of the sector in the
WGS-84 coordinate system.
characters
Unit:s
characters
Default Value:0:0:0
Sector ANTM ADD SECTOR
MOD SECTOR
LST SECTOR
LOFD-0010
38
LOFD-0010
01
LOFD-0010
03
LOFD-0010
60
RRU
Channel
Cross
Connect
ion
Under
MIMO
DL 2x2
MIMO
DL 4x2
MIMO
DL 4x4
MIMO
antenna mode of the sector.
GUI Value Range:1T1R,
1T2R, 2T2R, 2T4R, 4T4R,
8T8R
Unit:None
Actual Value Range:1T1R,
1T2R, 2T2R, 2T4R, 4T4R,
8T8R
Default Value:None
Cell CellId ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
Meaning:Indicates the ID of
the E-UTRAN cell. The
combination of this parameter
and the eNodeB ID forms the
E-UTRAN cell identity. The
combination of the E-UTRAN
cell identity and the PLMN
identity forms the ECGI. For
details, see 3GPP TS 36.413.
Unit:None
Default Value:None
Cell CellName ADD CELL
MOD CELL
None None Meaning:Indicates the name
of the cell.

eRAN
5-3
Name
Description
LST CELL characters
Unit:None
characters
Default Value:None
Cell CellRadius ADD CELL
MOD CELL
LST CELL
LBFD-0020
10 /
TDLBFD-00
2010
Rando
m
Access
Procedu
re
Meaning:Indicates the radius
of the cell.
Unit:m
Actual Value
Range:1~100000
Default Value:10000
CellOp CellReservedForO
p
ADD CELLOP
MOD CELLOP
LST CELLOP
LBFD-0010
01 /
TDLBFD-00
1001
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0020
1803 /
TDLBFD-00
201803
3GPP
R8
Specific
ations
Broadca
st of
system
informat
ion
Cell
Selectio
n and
Re-sele
ction
Meaning:Indicates whether
the cell is reserved for
operator use.
If this parameter is set to
CELL_RESERVED_FOR_OP
, the cell is reserved for
operator use. UEs of AC11 or
AC15 in their HPLMN or
EHPLMN can consider this
cell as a candidate cell for cell
selection or reselection. UEs
of AC11 or AC15 outside their
HPLMN/EHPLMN and UEs of
AC0-9/AC12-14 consider this
cell as a barred cell during cell
selection or reselection.
CELL_NOT_RESERVED_FO
R_OP, the cell is not reserved
for operator use. All UEs can
consider this cell as a
candidate cell for cell
selection or reselection.
GUI Value
Range:CELL_RESERVED_F
OR_OP(Reserved),
R_OP(Not Reserved)
Unit:None
Actual Value

eRAN
5-4
Name
Description
Range:CELL_RESERVED_F
OR_OP,
R_OP
Default
Value:CELL_NOT_RESERVE
D_FOR_OP(Not Reserved)
Cell CellSpecificOffset ADD CELL
MOD CELL
LST CELL
None None Meaning:Indicates the cell
specific offset for the serving
cell. It affects the probability of
triggering handovers from the
serving cell to its
intra-frequency neighboring
cells. A smaller value of this
parameter leads to a higher
probability. For details, see
3GPP TS 36.331.
GUI Value
Range:dB-24(-24dB),
dB-22(-22dB), dB-20(-20dB),
dB-18(-18dB), dB-16(-16dB),
dB-14(-14dB), dB-12(-12dB),
dB-10(-10dB), dB-8(-8dB),
dB-6(-6dB), dB-5(-5dB),
dB-4(-4dB), dB-3(-3dB),
dB-2(-2dB), dB-1(-1dB),
dB0(0dB), dB1(1dB),
dB2(2dB), dB3(3dB),
dB4(4dB), dB5(5dB),
dB6(6dB), dB8(8dB),
dB10(10dB), dB12(12dB),
dB14(14dB), dB16(16dB),
dB18(18dB), dB20(20dB),
dB22(22dB), dB24(24dB)
Unit:dB
Actual Value Range:dB-24,
dB-22, dB-20, dB-18, dB-16,
dB-14, dB-12, dB-10, dB-8,
dB-6, dB-5, dB-4, dB-3, dB-2,
dB-1, dB0, dB1, dB2, dB3,
dB4, dB5, dB6, dB8, dB10,
dB12, dB14, dB16, dB18,
dB20, dB22, dB24
Default Value:dB0(0dB)
CnOperat
orTa
CnOperatorId ADD
CNOPERATORTA
LOFD-0010
36 /
RAN
Sharing
Meaning:Indicates the index
of the operator.

eRAN
5-5
Name
Description
MOD
CNOPERATORTA
LST
CNOPERATORTA
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
ed
Carrier
GUI Value Range:0~5
Unit:None
Default Value:None
CnOperat
or
CnOperatorId ADD CNOPERATOR
LST CNOPERATOR
MOD CNOPERATOR
RMV CNOPERATOR
LOFD-0010
36 /
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
ed
Carrier
Meaning:Indicates the index
of the operator.
GUI Value Range:0~5
Unit:None
Default Value:None
CnOperat
or
CnOperatorName ADD CNOPERATOR
MOD CNOPERATOR
LST CNOPERATOR
LOFD-0010
36 /
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
ed
Carrier
Meaning:Indicates the name
of the operator. The name is a
string of a maximum of 32
characters. The string cannot
be all null characters or
contain any of the following
characters: double quotation
marks ("), commas (,),
semicolons (;), equal signs
(=), single quotation marks ('),
three consecutive plus signs
(+++), two or more
consecutive spaces, and two
or more consecutive percent
signs (%).
characters
Unit:None
characters
Default Value:None

eRAN
5-6
Name
Description
CnOperat
or
CnOperatorType ADD CNOPERATOR
MOD CNOPERATOR
LST CNOPERATOR
LOFD-0010
36 /
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
ed
Carrier
Meaning:Indicates the type of
the operator. The operator
can be the primary operator or
a secondary operator. For
each eNodeB, only one
primary operator but more
than one secondary operator
can be configured.
GUI Value
Range:CNOPERATOR_PRIM
ARY(Primary Operator),
CNOPERATOR_SECONDAR
Y(Secondary Operator)
Unit:None
Actual Value
Range:CNOPERATOR_PRIM
ARY,
CNOPERATOR_SECONDAR
Y
Default Value:None
Sector COMBM ADD SECTOR
MOD SECTOR
LST SECTOR
LOFD-0010
38
LOFD-0010
01
LOFD-0010
03
LOFD-0010
60
TDLOFD-0
01075
RRU
Channel
Cross
Connect
ion
Under
MIMO
DL 2x2
MIMO
DL 4x2
MIMO
DL 4x4
MIMO
SFN
combination mode of the
sector.
GUI Value
Range:COMBTYPE_SINGLE
_RRU,
COMBTYPE_TWO_RRU,
COMBTYPE_THREE_RRU,
COMBTYPE_FOUR_RRU,
COMBTYPE_FIVE_RRU,
COMBTYPE_SIX_RRU,
COMBTYPE_SEVEN_RRU,
COMBTYPE_EIGHT_RRU
Unit:None
Actual Value
Range:COMBTYPE_SINGLE
_RRU,
COMBTYPE_TWO_RRU,
COMBTYPE_THREE_RRU,
COMBTYPE_FOUR_RRU,
COMBTYPE_FIVE_RRU,
COMBTYPE_SIX_RRU,
COMBTYPE_SEVEN_RRU,
COMBTYPE_EIGHT_RRU
Default

eRAN
5-7
Name
Description
Value:COMBTYPE_SINGLE_
RRU
Sector CONFIDENCE ADD SECTOR
MOD SECTOR
LST SECTOR
confidence level of an
uncertainty area by which the
geographical location of the
antennas in the sector is to be
included. The smaller the
parameter value is, the higher
the positioning accuracy is.
For details about the
uncertainty area, see 3GPP
TS 23.032.
Unit:%
Default Value:0
Cell CPRICompression ADD CELL
MOD CELL
LST CELL
None None Meaning:Indicates the CPRI
compression type of the cell.
CPRI compression is used in
RRU cascading scenarios to
improve the cascading
specifications without
changing the CPRI data rate.
This parameter can be set to
NO_COMPRESSION or
NORMAL_COMPRESSION.
The value
NO_COMPRESSION
indicates that CPRI
compression is not used, and
the value
NORMAL_COMPRESSION
indicates that CPRI
compression is used.
GUI Value
Range:NO_COMPRESSION(
No Compression),
NORMAL_COMPRESSION(
Normal Compression)
Unit:None
Actual Value
Range:NO_COMPRESSION,
NORMAL_COMPRESSION

eRAN
5-8
Name
Description
Default
Value:NO_COMPRESSION(
No Compression)
Cell CsgInd ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
Meaning:Indicates whether
the cell is a closed subscriber
group (CSG) cell. A CSG cell
has restrictions on UE access.
It broadcasts a specific CSG
ID in the SIB and only those
UEs of the group can access
the CSG cell.
BOOLEAN_FALSE indicates
that the cell is not a CSG cell,
and BOOLEAN_TRUE
indicates that the cell is a
CSG cell. Currently, Huawei
eNodeBs do not support CSG
cells.
GUI Value
Range:BOOLEAN_FALSE(Fa
lse), BOOLEAN_TRUE(True)
Unit:None
Actual Value
Range:BOOLEAN_FALSE,
BOOLEAN_TRUE
Default
Value:BOOLEAN_FALSE(Fal
se)
Cell CustomizedBandW
idthCfgInd
ADD CELL
MOD CELL
LST CELL
LOFD-0010
51
LBFD-0010
03 /
TDLBFD-00
1003
Compac
t
Bandwi
dth
Scalabl
e
Bandwi
dth
Meaning:Indicates whether to
configure bandwidth
customization for the cell.
Bandwidth customization is
available only when the
bandwidth is 5 MHz, 10 MHz,
15 MHz, or 20 MHz.
GUI Value
Range:NOT_CFG(Not
configure), CFG(Configure)
Unit:None
Actual Value
Range:NOT_CFG, CFG
Default Value:NOT_CFG(Not
configure)

eRAN
5-9
Name
Description
Cell CustomizedDLBan
dWidth
ADD CELL
MOD CELL
LST CELL
LOFD-0010
51
LBFD-0010
03 /
TDLBFD-00
1003
Compac
t
Bandwi
dth
Scalabl
e
Bandwi
dth
customized DL cell
bandwidth. Bandwidth
customization is available
only when the bandwidth is 5
MHz, 10 MHz, 15 MHz, or 20
MHz.
GUI Value
Range:48~50,96~100,146~15
0,183~200
Unit:0.1MHz
Actual Value
Range:4.8~5.0,9.6~10.0,14.6
~15.0,18.3~20.0, step:0.1
Default Value:98
Cell CustomizedULBan
dWidth
ADD CELL
MOD CELL
LST CELL
LOFD-0010
51
LBFD-0010
03 /
TDLBFD-00
1003
Compac
t
Bandwi
dth
Scalabl
e
Bandwi
dth
customized UL cell
bandwidth. Bandwidth
customization is available
only when the bandwidth is 5
MHz, 10 MHz, 15 MHz, or 20
MHz.
GUI Value
Range:48~50,96~100,146~15
0,183~200
Unit:0.1MHz
Actual Value
Range:4.8~5.0,9.6~10.0,14.6
~15.0,18.3~20.0, step:0.1
Default Value:98
Cell DlBandWidth ADD CELL
MOD CELL
LST CELL
LBFD-0010
03 /
TDLBFD-00
1003
LBFD-0020
09 /
TDLBFD-00
2009
Scalabl
e
Bandwi
dth
Broadca
st of
system
informat
ion
Meaning:Indicates the DL
bandwidth of the cell, which is
based on the number of
resource blocks (RBs). The
value CELL_BW_N25
indicates a cell bandwidth of
25 RBs. The value
CELL_BW_N50 indicates a
cell bandwidth of 50 RBs. The
mapping between the
parameter value and the
actual cell bandwidth (that is,
the number of RBs) can be
deduced similarly. For details,

eRAN
5-10
Name
Description
see 3GPP TS 36.104.
GUI Value
Range:CELL_BW_N6(1.4M),
CELL_BW_N15(3M),
CELL_BW_N25(5M),
CELL_BW_N50(10M),
CELL_BW_N75(15M),
CELL_BW_N100(20M)
Unit:None
Actual Value
Range:CELL_BW_N6,
CELL_BW_N15,
CELL_BW_N25,
CELL_BW_N50,
CELL_BW_N75,
CELL_BW_N100
Default Value:None
Cell DlCyclicPrefix ADD CELL
MOD CELL
LST CELL
LBFD-0010
04 /
TDLBFD-00
1004
LBFD-0010
0401 /
TDLBFD-00
100401
LOFD-0010
31
CP
length
Normal
CP
Extende
d CP
Meaning:Indicates the length
of the DL cyclic prefix of a cell.
A DL cyclic prefix can be a
common or extended cyclic
prefix. An extended cyclic
prefix is generally used in a
complex environment with a
strong multi-path effect and
long delay. In a cell, the UL
cyclic prefix length can be
different from the DL one. In
addition, the UL or DL cyclic
prefix length of a cell must be
the same as that of the cell
using the same LBBP. For
GUI Value
Range:NORMAL_CP(Normal)
, EXTENDED_CP(Extended)
Unit:None
Actual Value
Range:NORMAL_CP,
EXTENDED_CP
Default
Value:NORMAL_CP(Normal)
Cell DlEarfcn ADD CELL LBFD-0020
09 /
Broadca
st of
Meaning:Indicates the DL
EARFCN of the cell. For

eRAN
5-11
Name
Description
MOD CELL
LST CELL
TDLBFD-00
2009
LBFD-0010
07 /
TDLBFD-00
1008
LBFD-0010
08 /
TDLBFD-00
1009
system
informat
ion
3GPP
R9
Specific
ations
3GPP
R10
Specific
ations
details, see the 3GPP TS
36.104.
GUI Value
Range:0~45589,64436~6553
5
Unit:None
Actual Value
Range:0~45589,64436~6553
5
Default Value:None
Cell EmergencyAreaId ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
emergency area ID. For
GUI Value
Range:0~16777215
Unit:None
Actual Value
Range:0~16777215
Default Value:0
Cell EmergencyAreaId
CfgInd
ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
Meaning:Indicates whether to
set an emergency area ID.
GUI Value
Range:NOT_CFG(Not
configure), CFG(Configure)
Unit:None
Actual Value
Range:NOT_CFG, CFG
Default Value:NOT_CFG(Not
configure)
Cell FddTddInd ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
Meaning:Indicates the duplex
mode of the cell. CELL_FDD
indicates the FDD mode, and
CELL_TDD indicates the TDD
mode.
GUI Value
Range:CELL_FDD(FDD),
CELL_TDD(TDD)
Unit:None

eRAN
5-12
Name
Description
Actual Value
Range:CELL_FDD,
CELL_TDD
Default Value:None
Cell FreqBand ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0010
07 /
TDLBFD-00
1008
LBFD-0010
08 /
TDLBFD-00
1009
Broadca
st of
system
informat
ion
3GPP
R9
Specific
ations
3GPP
R10
Specific
ations
frequency band in which the
cell operates. For details
about this parameter, see
3GPP TS 36.104.
GUI Value Range:1~43,61~64
Unit:None
Actual Value
Range:1~43,61~64
Default Value:None
Sector GCDF ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the format
of geographical coordinates.
GUI Value Range:DEG, SEC
Unit:None
Actual Value Range:DEG,
SEC
Default Value:DEG
Cell HighSpeedFlag ADD CELL
MOD CELL
LST CELL
LOFD-0010
07 /
TDLOFD-0
01007
LOFD-0010
08 /
TDLOFD-0
01008
High
Speed
Mobility
Ultra
High
Speed
Mobility
Meaning:Indicates the speed
flag of the cell. Set this
parameter to
ULTRA_HIGH_SPEED if the
cell is used to provide
coverage for an
ultra-high-speed railway. Set
this parameter to
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

eRAN
5-13
Name
Description
high speed cell flag),
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)
Sector LATITUDE ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the latitude
of the sector. A negative value
indicates a south latitude, and
a positive value indicates a
north latitude.
GUI Value
Range:-90000000~90000000
Unit:1e-6 degree
Actual Value Range:-90~90,
step:1e-6
Default Value:None
CellOp LocalCellId ADD CELLOP
DSP
CELLBROADCASTC
NOPERATOR
LST CELLOP
MOD CELLOP
RMV CELLOP
LBFD-0010
01 /
TDLBFD-00
1001
3GPP
R8
Specific
ations
Meaning:Indicates the local ID
of the cell. It uniquely
identifies a cell within a BS.
Unit:None
Default Value:None
Cell LocalCellId ACT CELL
ADD CELL
BLK CELL
DEA CELL
DSP CELL
LST CELL
None None Meaning:Indicates the local ID
of the cell. It uniquely
identifies a cell within a BS.
Unit:None
Default Value:None

eRAN
5-14
Name
Description
MOD CELL
RMV CELL
STR
CELLRFLOOPBACK
STR
CELLSELFTEST
UBL CELL
Sector LONGITUDE ADD SECTOR
MOD SECTOR
LST SECTOR
longitude of the sector. A
negative value indicates a
west longitude, and a positive
value indicates an east
longitude.
GUI Value
Range:-180000000~1800000
00
Unit:1e-6 degree
Actual Value
Range:-180~180, step:1e-6
Default Value:None
CnOperat
or
Mcc ADD CNOPERATOR
MOD CNOPERATOR
LST CNOPERATOR
LOFD-0010
36 /
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
ed
Carrier
Meaning:Indicates the mobile
country code (MCC) of the
operator.
GUI Value Range:3
characters
Unit:None
Default Value:None
CnOperat
or
Mnc ADD CNOPERATOR
MOD CNOPERATOR
LST CNOPERATOR
LOFD-0010
36 /
TDLOFD-0
01036
LOFD-0010
37 /
TDLOFD-0
01037
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicat
Meaning:Indicates the mobile
network code (MNC) of the
operator. The value of this
parameter is a string of two or
three characters, each of
which must be a digit in the
range from 0 to 9.
GUI Value Range:2~3
characters

eRAN
5-15
Name
Description
ed
Carrier
Unit:None
Actual Value
Range:00~99,000~999
Default Value:None
Cell MultiRruCellFlag ADD CELL
MOD CELL
LST CELL
TDLOFD-0
01075
SFN Meaning:Indicates whether to
enable or disable the
multi-RRU cell feature.
GUI Value
Range:BOOLEAN_FALSE(Fa
lse), BOOLEAN_TRUE(True)
Unit:None
Actual Value
Range:BOOLEAN_FALSE,
BOOLEAN_TRUE
Default
Value:BOOLEAN_FALSE(Fal
se)
Cell MultiRruCellMode ADD CELL
MOD CELL
LST CELL
TDLOFD-0
01075
SFN Meaning:Indicates the type of
the multi-RRU cell.The value
TWO_RRU_COMBINATION(
TWO RRU Combination)
applies to ultra-high-speed
railway scenarios.
GUI Value Range:SFN(SFN),
CELL_COMBINATION(Cell
Combination),
TWO_RRU_COMBINATION(
TWO RRU Combination),
DIGITAL_COMBINATION(Cel
l Digital Combination)
Unit:None
Actual Value Range:SFN,
CELL_COMBINATION,
TWO_RRU_COMBINATION,
DIGITAL_COMBINATION
Default Value:SFN(SFN)
Sector OMNIFLAG ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the flag of
the omnidirectional cell. If this
parameter is set to TRUE, the
cell is an omnidirectional cell.
FALSE, the cell is not an

eRAN
5-16
Name
Description
omnidirectional cell.
GUI Value Range:FALSE,
TRUE
Unit:None
Actual Value Range:FALSE,
TRUE
Default Value:FALSE
CellOp OpDlRbUsedRatio ADD CELLOP
MOD CELLOP
LST CELLOP
LBFD-0010
01 /
TDLBFD-00
1001
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0020
1803 /
TDLBFD-00
201803
LOFD-0010
36 /
TDLOFD-0
01036
3GPP
R8
Specific
ations
Broadca
st of
system
informat
ion
Cell
Selectio
n and
Reselec
tion
RAN
Sharing
with
Commo
n
Carrier
percentage of RBs occupied
by the operator on the
PDSCH when RAN sharing is
enabled at the eNodeB and
the cell-level switch of RAN
sharing is turned on. When
the data volume is sufficiently
large, the percentage of RBs
occupied by each operator will
reach the preset value.
Modifications on this
parameter affect operators'
percentages of RBs.
Unit:%
Default Value:16
CellOp OpUlRbUsedRatio ADD CELLOP
MOD CELLOP
LST CELLOP
LBFD-0010
01 /
TDLBFD-00
1001
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0020
1803 /
TDLBFD-00
201803
LOFD-0010
36 /
TDLOFD-0
3GPP
R8
Specific
ations
Broadca
st of
system
informat
ion
Cell
Selectio
n and
Reselec
tion
RAN
Sharing
percentage of RBs occupied
by the operator on the
PUSCH when RAN sharing is
enabled at the eNodeB and
the cell-level switch of RAN
sharing is turned on. When
the data volume is sufficiently
large, the percentage of RBs
occupied by each operator will
reach the preset value.
Modifications on this
parameter affect operators'
percentages of RBs.
Unit:%

eRAN
5-17
Name
Description
01036 with
Commo
n
Carrier
Default Value:16
Sector ORIENTOFMAJOR
AXIS
ADD SECTOR
MOD SECTOR
LST SECTOR
None None Meaning:Indicates the major
axis orientation of an
uncertainty area by which the
geographical location of the
antennas in the sector is to be
included. (The orientation is
the counter-clockwise angle in
degrees between the major
axis and north). The smaller
the parameter value is, the
higher the positioning
accuracy is. For details about
the uncertainty area, see
3GPP TS 23.032.
Unit:degree
Default Value:0
CellDlpcP
dschPa
PaPcOff MOD
CELLDLPCPDSCHP
A
LST
CELLDLPCPDSCHP
A
LBFD-0020
16 /
TDLBFD-00
2016
Dynami
c
Downlin
k Power
Allocati
on
Meaning:Indicates the PA to
be used when PA adjustment
for PDSCH power control is
disabled, downlink ICIC is
disabled, and the even power
distribution is used for the
PDSCH.
GUI Value
Range:DB_6_P_A(-6 dB),
DB_4DOT77_P_A(-4.77 dB),
DB_3_P_A(-3 dB),
DB_1DOT77_P_A(-1.77 dB),
DB0_P_A(0 dB), DB1_P_A(1
dB), DB2_P_A(2 dB),
DB3_P_A(3 dB)
Unit:dB
Actual Value
Range:DB_6_P_A,
DB_4DOT77_P_A,
DB_3_P_A,
DB_1DOT77_P_A,
DB0_P_A, DB1_P_A,

eRAN
5-18
Name
Description
DB2_P_A, DB3_P_A
Default Value:DB_3_P_A(-3
dB)
PDSCHCf
g
Pb MOD PDSCHCFG
LST PDSCHCFG
LBFD-0020
03 /
TDLBFD-00
2003
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0020
16 /
TDLBFD-00
2016
Physical
Channel
Manage
ment
Broadca
st of
system
informat
ion
Dynami
c
Downlin
k Power
Allocati
on
Meaning:Indicates the scaling
factor index of the Energy Per
Resource Element (EPRE) on
the PDSCH. This scaling
factor is determined by the
value of this parameter and
the antenna port. For details,
see 3GPP TS 36.213.
GUI Value Range:0~3
Unit:None
Default Value:1
Cell PhyCellId ADD CELL
MOD CELL
LST CELL
LBFD-0020
09 /
TDLBFD-00
2009
Broadca
st of
system
informat
ion
physical cell ID. For details,
see 3GPP TS 36.331.
Unit:None
Default Value:None
Cell PreambleFmt ADD CELL
MOD CELL
LST CELL
LBFD-0020
10 /
TDLBFD-00
2010
Rando
m
Access
Procedu
re
preamble format used in the
cell. Cells set up on one 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 QoffsetFreq ADD CELL
MOD CELL
None None Meaning:Indicates the specific
frequency offset of the serving
cell. This parameter is
contained in the

eRAN
5-19
Name
Description
LST CELL intra-frequency measurement
control information and is
related to the handover
difficulty between the serving
cell and the neighboring cell.
For details, see 3GPP TS
36.331.
GUI Value
Range:dB-24(-24dB),
dB-22(-22dB), dB-20(-20dB),
dB-18(-18dB), dB-16(-16dB),
dB-14(-14dB), dB-12(-12dB),
dB-10(-10dB), dB-8(-8dB),
dB-6(-6dB), dB-5(-5dB),
dB-4(-4dB), dB-3(-3dB),
dB-2(-2dB), dB-1(-1dB),
dB0(0dB), dB1(1dB),
dB2(2dB), dB3(3dB),
dB4(4dB), dB5(5dB),
dB6(6dB), dB8(8dB),
dB10(10dB), dB12(12dB),
dB14(14dB), dB16(16dB),
dB18(18dB), dB20(20dB),
dB22(22dB), dB24(24dB)
Unit:dB
Actual Value Range:dB-24,
dB-22, dB-20, dB-18, dB-16,
dB-14, dB-12, dB-10, dB-8,
dB-6, dB-5, dB-4, dB-3, dB-2,
dB-1, dB0, dB1, dB2, dB3,
dB4, dB5, dB6, dB8, dB10,
dB12, dB14, dB16, dB18,
dB20, dB22, dB24
Default Value:dB0(0dB)
PDSCHCf
g
ReferenceSignalP
wr
MOD PDSCHCFG
LST PDSCHCFG
LBFD-0020
03 /
TDLBFD-00
2003
LBFD-0020
09 /
TDLBFD-00
2009
LBFD-0020
16 /
TDLBFD-00
2016
Physical
Channel
Manage
ment
Broadca
st of
system
informat
ion
Dynami
c
Downlin
k Power
Meaning:Indicates the cell
reference signal power of
each physical antenna.
However, the cell reference
signal power delivered in SIB2
is that of each logical
antenna. The cell reference
signal transmit (TX) power of
each logical antenna is
calculated by using the
formula: 10 x log(Number of
physical antennas/Number of
logical antennas) +
ReferenceSignalPwr. The

eRAN
5-20
Name
Description
Allocati
on
number of physical antennas
refers to the number of TX
channels specified by the
ANTM parameter in the
Sector MO. The number of
logical antennas refers to the
number of antenna ports for
transmitting cell-specific
reference signals in a cell as
defined in 3GPP
specifications. In FDD mode,
the number of logical
antennas equals the number
of physical antennas. In TDD
mode, there are permanently
two logical antennas if the
is greater than or equal to 2,
and one logical antenna if the
is 1.
GUI Value Range:-600~500
Unit:0.1dBm
Actual Value Range:-60~50,
step:0.1
Default Value:182
Cell RootSequenceIdx ADD CELL
MOD CELL
LST CELL
LBFD-0020
10 /
TDLBFD-00
2010
Rando
m
Access
Procedu
re
Meaning:Indicates the first
logical root sequence, which
is used to generate the
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.
Unit:None
Default Value:None
Sector SECM ADD SECTOR
MOD SECTOR
LOFD-0010
38
LOFD-0010
RRU
Channel
Cross
multiple-input multiple-output
(MIMO) mode of the sector,

eRAN Cell Management Guide

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to eRAN Cell Management Guide

Similar to eRAN Cell Management Guide (20)

Recently uploaded

Recently uploaded (20)

eRAN Cell Management Guide