Cell Management (ERAN8.1 02)

eRAN
Cell Management Feature Parameter

Description
Issue
02
Date
2015-06-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. 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 02 (2015-06-10)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eRAN
Cell Management Feature Parameter Description
Contents
Contents
1 About This Document.................................................................................................................. 1
1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between eNodeB Types.............................................................................................................................. 3
2 Overview......................................................................................................................................... 5
2.1 Introduction.................................................................................................................................................................... 5
2.2 Benefits........................................................................................................................................................................... 5
3 Technical Description...................................................................................................................6
3.1 Related Concepts............................................................................................................................................................ 6
3.1.1 Cell...............................................................................................................................................................................7
3.1.2 Sector........................................................................................................................................................................... 8
3.1.3 Sector Equipment........................................................................................................................................................ 8
3.1.4 RF Equipment..............................................................................................................................................................8
3.1.5 Baseband Equipment................................................................................................................................................... 9
3.1.6 Cell-specific Sector Equipment................................................................................................................................... 9
3.2 Typical Scenarios............................................................................................................................................................9
3.2.1 Establishing a Cell in a Common Sector..................................................................................................................... 9
3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU Splitting..............................................................................10
3.2.3 Establishing a Cell in a Single Sector with RRU/RFU Combination........................................................................11
3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs/RFUs................................................................11
3.3 Cell-related Parameters.................................................................................................................................................13
3.3.1 Frequency Band......................................................................................................................................................... 13
3.3.2 Cell Bandwidth.......................................................................................................................................................... 14
3.3.3 Maximum Transmit Power of a Cell......................................................................................................................... 15
4 Related Features...........................................................................................................................20
5 Network Impact........................................................................................................................... 21
6 Engineering Guidelines............................................................................................................. 22
6.1 When to Use Cell Management....................................................................................................................................22
6.2 Required Information................................................................................................................................................... 22
6.3 Planning........................................................................................................................................................................ 22
Issue 02 (2015-06-10)

ii
eRAN
Contents
6.4 Deployment.................................................................................................................................................................. 22
6.4.1 Process....................................................................................................................................................................... 23
6.4.2 Requirements............................................................................................................................................................. 23
6.4.3 Data Preparation........................................................................................................................................................ 26
6.4.4 Precautions.................................................................................................................................................................37
6.4.5 Hardware Adjustment................................................................................................................................................37
6.4.6 Activation.................................................................................................................................................................. 39
6.4.6.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................39
6.4.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 41
6.4.6.3 Using the CME to Perform Single Configuration.................................................................................................. 42
6.4.6.4 Using MML Commands......................................................................................................................................... 42
6.4.6.5 MML Command Examples.................................................................................................................................... 44
6.4.7 Activation Observation..............................................................................................................................................47
6.4.8 Reconfiguration......................................................................................................................................................... 47
6.4.9 Deactivation...............................................................................................................................................................47
6.5 Performance Monitoring...............................................................................................................................................48
6.6 Parameter Optimization................................................................................................................................................ 48
6.7 Troubleshooting............................................................................................................................................................ 48
7 Parameters..................................................................................................................................... 49
8 Counters........................................................................................................................................ 82
9 Glossary......................................................................................................................................... 83
10 Reference Documents............................................................................................................... 84
Issue 02 (2015-06-10)

iii
eRAN
1 About This Document
About This Document
1.1 Scope
This document describes cell management, including its technical principles, related features,
network impact, and engineering guidelines.
This document covers LBFD-001003 Scalable Bandwidth.
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.
This document applies to the following types of eNodeBs.
eNodeB Type
Model
Macro
3900 series eNodeB
Micro
BTS3202E
LampSite
DBS3900
1.2 Intended Audience

This document is intended for personnel who:
l
Need to understand the features described herein
Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
Issue 02 (2015-06-10)

eRAN
Feature change
Changes in features and parameters of a specified version as well as the affected entities
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.
eRAN8.1 02 (2015-06-10)
This issue includes the following changes.
Change
Type
Change Description
Paramet
er
Change
Affected
Entity
Feature
change
None
None
Macro,
micro, and
LampSite
eNodeBs
Editorial
change
Revised baseband equipment descriptions. For

details, see 3.1.5 Baseband Equipment.
None
eRAN8.1 01 (2015-03-23)
This issue does not include any changes.
eRAN8.1 Draft A (2015-01-15)

Compared with Issue 05 (2014-09-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1
includes the following changes.
Change
Type
Change Description
Paramete
r Change
Affected
Entity
Feature
change
Added the description of Band 28 and Band

29. For details, see 3.3.1 Frequency Band.
None
Macro,
micro, and
LampSite
eNodeBs
Added the support for 4T8R antenna mode.

For details, see 3.2.1 Establishing a Cell in
a Common Sector.
None
Macro,
micro, and
LampSite
eNodeBs
None
None
Editorial
change
Issue 02 (2015-06-10)

eRAN
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID
Feature
Name
Supported by
Macro
eNodeBs
Supported by
Micro
eNodeBs
Supported by
LampSite
eNodeBs
LBFD-001003
Scalable
Bandwidth
Yes
Yes
Yes
Function Implementation in Macro, Micro, and LampSite eNodeBs
Issue 02 (2015-06-10)
Functio
n
Difference
Establishi
ng a cell
in
multiple
sectors
with
RRU/RF
U
splitting
Implementation of this function varies based on eNodeB types:
Establishi
ng a cell
in a
single
sector
with
RRU/RF
U
combinat
ion
Establishi
ng a cell
in a
sector
with
RRU/RF
U
channel
crossconnectio
n under
MIMO
l Macro and micro eNodeBs support this function.

l LampSite eNodeBs do not support this function.
For details about establishing a cell in multiple sectors with RRU/RFU
splitting, see 3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU
Splitting.
l Macro eNodeBs support this function.

l Micro and LampSite eNodeBs do not support this function.
For details about establishing a cell in a single sector with RRU combination,
see 3.2.3 Establishing a Cell in a Single Sector with RRU/RFU
Combination.
l Macro eNodeBs support this function.

l Micro and LampSite eNodeBs do not support this function.
For details about establishing a cell in a sector with RRU/RFU channel crossconnection under MIMO, see Base Station Equipment Reliability Feature
Parameter Description.

eRAN
Functio
n
Difference
Establishi
ng a cell
in
multiple
sectors
served by
different
RRUs/
RFUs
Multi-sector cells include single-frequency-network (SFN) cells, pico RRU

(pRRU) aggregation cells, 2-RRU combination cells, and digital combination
cells. Implementation of this function varies based on eNodeB types:
Cell
bandwidt
h
Bandwidths supported by eNodeBs vary with eNodeB types.
l Macro eNodeBs support SFN cells, pRRU aggregation cells, 2-RRU

combination cells, and digital combination cells.
l LampSite eNodeBs support only pRRU aggregation cells.
l Micro eNodeBs do not support multi-sector cells.
For details about multi-sector cells, see 3.2.4 Establishing a Cell in Multiple
Sectors Served by Different RRUs/RFUs.
l Macro eNodeBs support the cell bandwidths of 1.4 MHz, 3 MHz, 5MHz,
10MHz, 15MHz and 20MHz.
l Micro and LampSite eNodeBs support the cell bandwidth of 5MHz,
10MHz, 15MHz and 20MHz.
For details about cell bandwidths, see 3.3.2 Cell Bandwidth.
Cell
transmiss
ion and
reception
mode
Transmission and reception modes supported by eNodeBs vary with eNodeB

types.
l Macro eNodeBs support 1T1R, 1T2R, 2T2R, 2T4R, 4T4R, 2T8R and
4T8R cells.
l LampSite eNodeBs support 1T1R, 1T2R, 2T2R, 2T4R and 4T4R cells.
l For micro eNodeBs,
The BTS3202E supports 1T1R, 1T2R and 2T2R cells.
Issue 02 (2015-06-10)

eRAN
2 Overview
Overview
2.1 Introduction
Cell management refers to management of wireless communications resources by cell setup
and parameter configuration for cells.
2.2 Benefits
Cell management is a basic function for eNodeBs to provide radio coverage.
Issue 02 (2015-06-10)

eRAN
3 Technical Description
Technical Description
3.1 Related Concepts

Figure 3-1 shows the concepts related to cell management.
Issue 02 (2015-06-10)

eRAN
Figure 3-1 Cell-related concepts
3.1.1 Cell
A cell is an area where wireless communications services are provided. It is the fundamental
unit of a radio network. Cells are joined to achieve contiguous coverage of the entire radio
network.
Issue 02 (2015-06-10)

eRAN
3.1.2 Sector
A sector is a radio coverage area. Each sector uses one or more radio carriers to provide
coverage. Sectors and carriers compose cells.
NOTE
For a co-MPT base station, if services of different modes are carried on the same transmit channel,
configure the same SECTOR MO for these modes.
A sector can be omnidirectional or directional, depending on the antenna type. The following
table describes the sector types.
Sector
Type
Definition
Benefits
Applicati
on
Scenario
Omnidirec
tional
sector
An omnidirectional sector uses

an omnidirectional antenna to
provide 360 degrees of coverage
from the center of a circular
area.
In low-traffic areas, the

deployment of
omnidirectional sectors
reduces the cost of antenna
equipment.
Traffic is
low.
Directiona
l sector
Directional sectors use

directional antennas for
coverage. Each directional
antenna covers a sector area of
60 or 120 degrees when six or
three antennas, respectively, are
configured on an eNodeB. When
six sectors are configured, each
directional antenna covers a
sector area of 60 degrees. The
azimuth of each sector is slightly
greater than 60 or 120 degrees.
This overlapping ensures
seamless coverage.
In high-traffic areas, the

deployment of directional
sectors supports high traffic
volumes. In addition,
directional sectors support
more flexible area
planning.
Traffic is
high.
3.1.3 Sector Equipment

Sector equipment is a piece of RF antennas specified for a sector.
One set of RF antennas must serve the same sector.
Sector equipment is added by running the ADD SECTOREQM command.
NOTE
For a co-MPT base station, if services of different modes are carried on the same transmit channel,
configure the SECTOREQM MO by mode.
3.1.4 RF Equipment
RF equipment includes RRUs, RFUs, pRRUs, and AAUs. For micro eNodeBs, RF equipment
refers to their RF processing units.
Issue 02 (2015-06-10)

eRAN
An RRU is added by running the ADD RRU and ADD RRUCHAIN commands. There is no
need to add RRUs for micro eNodeBs.
3.1.5 Baseband Equipment

A piece of baseband equipment consists of one or more baseband processing units (BBPs).
A BBP is added by running the ADD BRD command. It can be added to a piece of baseband
equipment by running the ADD BASEBANDEQM command. For micro eNodeBs, there is
no need to add BBPs or baseband equipment.
In LTE eNodeBs, the baseband equipment is used for both uplink and downlink
transmissions. It is recommended that each piece of baseband equipment includes only one
BBP. Each BBP can belong to only one piece of baseband equipment.
Baseband equipment is bound to cells by running the ADD EUCELLSECTOREQM
command.
3.1.6 Cell-specific Sector Equipment

When binding sector equipment to a cell, you can specify the baseband equipment for the cell
at the same time.
If baseband equipment is not configured for a cell, the baseband processing unit connected to
the RRU serving the cell is used by default.
The sector equipment of a cell is added by running the ADD EUCELLSECTOREQM
command. In LampSite scenarios, a sector equipment group is required for each cell. Sector
equipment groups are added by running the ADD EUSECTOREQMGROUP command.
3.2 Typical Scenarios

The following are typical scenarios of cell establishment:
l
Establishing a common cell
Establishing cells in multiple sectors with RRU/RFU splitting
Establishing a cell in a single sector with RRU/RFU combination
Establishing a cell in multiple sectors served by different RRUs/RFUs
Establishing a cell in a sector with RRU/RFU channel cross-connection under MIMO
For details about cell setup in a sector with RRU/RFU channel cross-connection under
MIMO, see Base Station Equipment Reliability Feature Parameter Description.
In the preceding scenarios, only cells setup in a common or multi-carrier sector apply to micro
eNodeBs.
3.2.1 Establishing a Cell in a Common Sector

A cell can be established in a common sector that is served by a single RRU or RFU, as
shown in the following figure.
The antenna mode of a cell in a common sector can be 1T1R, 1T2R, 2T2R, 2T4R, 2T8R,
4T4R or 4T8R. xTyR means x transmit channels and y receive channels.
Issue 02 (2015-06-10)

eRAN
NOTE
If the cell works in 4T4R mode, run the MOD RXBRANCH command to disable two receive channels.
The antenna mode of the cell changes to 4T2R. (This mode is used to temporarily prevent
intermodulation interference. The 4T2R mode is not recommended for normal use because in this mode
uplink coverage of the sector may reduce compared with the coverage in 4T4R mode.)
Macro and LampSite eNodeBs support 2T4R and 4T4R cells. For micro eNodeBs, the BTS3202E does
not support 2T4R or 4T4R cells while the BTS3203E supports 2T4R and 4T4R cells.
Figure 3-2 A cell established in a common sector
3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU

Splitting
An RRU/RFU can be logically split to establish multiple sectors when the RRU/RFU
processing capability does not match the antenna transmission and reception capability. The
following figure provides an example of this scenario.
The RU unit of a micro eNodeB works in 2T2R mode and can be split to provide two 1T1R
sectors.
Figure 3-3 RRU/RFU splitting for multiple sectors (using a 4T4R RRU as an example)
Issue 02 (2015-06-10)

10
eRAN
3.2.3 Establishing a Cell in a Single Sector with RRU/RFU

Combination
In RRU/RFU combination scenarios, RRUs/RFUs working on the same frequency jointly
provide a sector to achieve greater RF capacity if the RRU/RFU processing capability does
not match the antenna transmission and reception capability.
Only RRUs or RFUs working in 0T4R, 1T2R, 2T2R, 2T4R, or 4T4R mode can be combined.
Micro eNodeBs do not support RRU/RFU combination.
Figure 3-4 RRU combination for a single sector (using a 2T2R RRU/RFU as an example)
3.2.4 Establishing a Cell in Multiple Sectors Served by Different

RRUs/RFUs
The sectors served by multiple RRUs/RFUs can be combined to set up a single cell. The RF
channels, antenna mode, and transmit power can be configured separately for each sector to
implement precise control of services. The Cell.MultiRruCellFlag parameter specifies
whether a cell is a multi-sector cell. The Cell.MultiRruCellMode parameter specifies the type
of a multi-sector cell.
Micro eNodeBs do not support multi-sector cells.
Multi-sector cells include digital combination cells, SFN cells, and pRRU aggregation cells.
Table 3-1 describes different types of multi-sector cells.
Issue 02 (2015-06-10)

11
eRAN
Figure 3-5 Establishing a Cell in Multiple Sectors Served by Different RRUs/RFUs
Table 3-1 Multi-sector cell types

Multi-sector
Cell Type
Description
Affected
Entity
SFN cell
Multiple RRUs/RFUs are combined to serve an SFN cell,

where all the RRUs/RFUs use the same physical cell
identifier (PCI) and cell ID. This expands the cell center
area and reduces interference at the cell edge.
Macro
eNodeBs
SFN cells apply in densely populated outdoor scenarios

and in indoor scenarios where the distributed antenna
system (DAS) is used. For details about SFN cells, see
SFN Feature Parameter Description.
pRRU
aggregation cell
A pRRU aggregation cell is the smallest service area for

providing indoor coverage in the LampSite solution.
LampSite
For details about pRRU aggregation cells, see SFN

Feature Parameter Description.
2-RRUcombination cell
A 2-RRU-combination cell is set up using sectors

provided by two RRUs (each RRU serves one sector). In
the downlink, the two RRUs transmit the same data. In
the uplink, the baseband processing unit combines the
signals received by the two RRUs.
Macro
eNodeBs
2-RRU-combination cells mainly cover high-speed

railways and highways. They are not recommended
because of unstable performance.
Issue 02 (2015-06-10)

12
eRAN
Multi-sector
Cell Type
Description
Affected
Entity
Digital
combination cell
A digital combination cell is served by multiple pRRUs.

The pRRUs serve different sectors but use the same PCI.
In the downlink, the pRRUs transmit the same data. In
the uplink, the baseband processing unit combines the
signals received by the pRRUs.
Macro
eNodeBs
Digital combination cells mainly cover subways and

underground business areas.
For engineering guidelines for enabling digital
combination cells, see 6.4 Deployment.
3.3 Cell-related Parameters

This section describes three parameters: frequency band, cell bandwidth, and reference signal
power.
For other parameters of a cell, such as CPRI compression, cycling prefix, preamble format,
and cell radius, see CPRI Configuration Feature Parameter Description, Extended CP
Feature Parameter Description, and Extended Cell Range Feature Parameter Description.
For the steps of reconfiguring these parameters, see 6.4.8 Reconfiguration or
Reconfiguration Guide.
3.3.1 Frequency Band

The frequency band of a cell is specified by the FreqBand parameter. For details about
allowed frequency bands, see section 5.5 in 3GPP TS 36.104 V11.0 (2013-07).
If the operating frequencies of a cell belong to multiple frequency bands, the multiple
frequency band indicator can be used. For details, see Multiple Frequency Band Indicator
Feature Parameter Description.
Table 3-2 Mapping between the frequency band and frequency range
Issue 02 (2015-06-10)
Frequency
Band
(FreqBand)
Uplink Frequency Range

(Lowest and Highest
Frequencies)
Downlink Frequency Range

(Lowest and Highest
Frequencies)
1920 MHz
1980 MHz
2110 MHz
2170 MHz
1850 MHz
1910 MHz
1930 MHz
1990 MHz
1710 MHz
1785 MHz
1805 MHz
1880 MHz
1710 MHz
1755 MHz
2110 MHz
2155 MHz
824 MHz
849 MHz
869 MHz
894 MHz
61
830 MHz
840 MHz
875 MHz
885 MHz

13
eRAN
Frequency
Band
(FreqBand)
Uplink Frequency Range

(Lowest and Highest
Frequencies)
Downlink Frequency Range

(Lowest and Highest
Frequencies)
2500 MHz
2570 MHz
2620 MHz
2690 MHz
880 MHz
915 MHz
925 MHz
960 MHz
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
26
814 MHz
849 MHz
859 MHz
894 MHz
28
703 MHz
748 MHz
758 MHz
803 MHz
29
N/A
N/A
717 MHz
728 MHz
NOTE
l Band 6 is unavailable.
l Band 29 applies only to carrier aggregation scenarios. For details, see Carrier Aggregation Feature
Parameter Description.
3.3.2 Cell Bandwidth

This section describes the basic feature LBFD-001003 Scalable Bandwidth.
A cell can be configured with different standardized bandwidths: 1.4 MHz, 3 MHz, 5 MHz,
10 MHz, 15 MHz, or 20 MHz. Macro eNodeBs support the cell bandwidths of 1.4 MHz and 3
Issue 02 (2015-06-10)

14
eRAN
MHz while micro and LampSite eNodeBs do not support these two bandwidths. Cells also
support non-standardized bandwidths. For details about non-standardized bandwidths, see
Compact Bandwidth Feature Parameter Description.
Cell bandwidths are specified by the UlBandWidth and DlBandWidth parameters.
3.3.3 Maximum Transmit Power of a Cell

This section describes the method of configuring the maximum transmit power of a cell
(Pmax_out).
Pmax_out Configuration Principle

The value of Pmax_out must be less than or equal to the maximum transmit power of the RRU
or RFU that provides the cell coverage.
NOTE
l If multiple cells are served by the same RRU or RFU, the sum of Pmax_out values of these cells must
be less than or equal to the maximum transmit power of the RRU or RFU.
l For details about the maximum transmit power of RRUs or RFUs with different carrier
configurations, see section "Typical Power Configuration Reference for RF Modules" in 3900 Series
Base Station Technical Description.
Pmax_out Configuration Parameters

Pmax_out is not specified by a single parameter but adjusted by the parameters described in the
following table.
Table 3-3 Pmax_out configuration parameters
Parameter
Setting Notes
ReferenceSignalPwr
Its value must be calculated. For details, see

Pmax_out Calculation Example.
CellDlpcPdschPa.PaPcOff
Dual-antenna or four-antenna scenarios: DB_3_P_A

(-3 dB)
Single-antenna scenarios: DB0_P_A (0 dB)
PDSCHCfg.PB
Single-antenna scenarios: 0
Dual-antenna scenarios: 1
NOTE
The value of the ReferenceSignalPwr parameter is determined by either of the following parameters:
l
EuCellSectorEqm.ReferenceSignalPwr (EuSectorEqmGroup.ReferenceSignalPwr for

LampSite eNodeBs)
PDSCHCfg.ReferenceSignalPwr
The value of the first parameter prevails if both the parameters are configured.
Issue 02 (2015-06-10)

15
eRAN
Pmax_out Query Method

To query Pmax_out of a cell, perform the following steps:
Step 1 Run the DSP CELL command to query the value of Maximum transmit power(0.1dBm).
This parameter indicates the maximum transmit power of a single antenna channel of a cell.
Step 2 Multiply Maximum transmit power(0.1dBm) by the number of transmit channels of a cell
to obtain the value of Pmax_out.
----End
Pmax_out Calculation Formula

l
If the TxBranch.TXMAXPWR parameter is configured, Pmax_out equals the value of

TxBranch.TXMAXPWR.
If the TxBranch.TXMAXPWR parameter is not configured, Pmax_out is calculated using

the following formula:
Pmax_out = MAX {TypeA(Pmax_out),TypeB(Pmax_out)}
where
Type A(Pmax_out) is the maximum transmit power configured for one type A
symbol. The calculation formula is as follows:
Type B(Pmax_out) is the maximum transmit power configured for one type B symbol.
The calculation formula is as follows:
Table 3-4 describes the variables in the preceding formulas. For details about the preceding
formulas, see section 5.2 in 3GPP TS 36.213 V10.5.0 (2012-03).
Table 3-4 Variables in the formulas
Variable
Description
ReferenceSig
nalPwr
Reference signal (RS) power of the physical downlink shared channel

(PDSCH).
For details, see Pmax_out Configuration Parameters.
Issue 02 (2015-06-10)

16
eRAN
Variable
Description
PowerFactor
Ratio
Power factor ratio of the energy per resource element (EPRE) on the
PDSCH.
l For Type A(Pmax_out), PowerFactorRatio is
, where
PaPcOff is determined by the CellDlpcPdschPa.PaPcOff parameter.
For example, when the CellDlpcPdschPa.PaPcOff parameter is set to
-3 dB, the value of PowerFactorRatio is 10-3/10, that is, 0.5.
l For Type B(Pmax_out), PowerFactorRatio is
PaPcOff is determined by the CellDlpcPdschPa.PaPcOff

parameter.
B/A is related to the PDSCHCfg.PB parameter. Table 3-5 lists
the mappings between B/A and the PDSCHCfg.PB parameter.
For example, when the CellDlpcPdschPa.PaPcOff parameter is set
to -3 dB and the PDSCHCfg.PB parameter is set to 1, B/A is 1. In
this scenario, the value of PowerFactorRatio is 0.5.
Type A(NRE)
Number of non-RS resource elements (REs) in one type A symbol period.

The calculation formula is as follows:
Type A(NRE) = Number of REs per RB in the frequency domain x
Number of RBs x Number of antennas
Table 3-6 lists the mappings between the cell bandwidth and number of
RBs.
Type B(NRS)
Number of RSs in one type B symbol period. The calculation formula is as

follows:
Type B(NRS) = Number of RSs per RB in the frequency domain x
Number of RBs x Number of antennas
Type B(NRE)
Number of non-RS REs in one type B symbol period. The calculation

formula is as follows:
Type B(NRE) = Number of REs per RB in the frequency domain x Number
of RBs x Number of antennas
Table 3-5 Mapping between PDSCHCfg.PB and the cell-specific ratio (B/A) for one, two,
or four antenna ports
Issue 02 (2015-06-10)
PDSCHCfg.PB
B/A (One
Antenna Port)
B/A (Two or Four Antenna Ports)
5/4
4/5
3/5
3/4
2/5
1/2

17
eRAN
Table 3-6 Mapping between cell bandwidths and the maximum number of available RBs
Cell Bandwidth
(MHz)
1.4
10
15
20
Maximum
Number of
Available RBs
15
25
50
75
100
Pmax_out Calculation Example

Among the three parameters for configuring Pmax_out, PaPcOff and PB can be configured
according to Table 3-3. You only need to calculate the value of ReferenceSignalPwr.
The following is an example of calculating the value of ReferenceSignalPwr. In this
example, the RRU provides the maximum transmit power of 80 W and serves a 20 MHz cell
with two antennas.
Pmax_out = MAX {TypeA(Pmax_out),TypeB(Pmax_out)} 80 W
where
l
Type A(Pmax_out)
= ReferenceSignalPwr x PowerFactorRatio x TypeA(NRE)
= ReferenceSignalPwr x 0.5 x 2400
= 1200 x ReferenceSignalPwr
Type B(Pmax_out)
= ReferenceSignalPwr x TypeB(NRS) + ReferenceSignalPwr x PowerFactorRatio x
TypeB(NRE)
= ReferenceSignalPwr x 400 + ReferenceSignalPwr x 0.5 x 1600
= 1200 x ReferenceSignalPwr
NOTE
l Type A(NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of
antennas = 12 x 100 x 2 = 2400
l Type A(NRS) = Number of RSs per RB in the frequency domain x Number of RBs x Number of
antennas = 2 x 100 x 2 = 400
l According to Table 3-3, the PaPcOff parameter for a cell with two antennas is set to 3 dB.
Therefore, for type A symbols, PowerFactorRatio =
= 0.5.
l According to Table 3-3, the typical value of the PB parameter for a cell with two antennas is 1.
According to Table 3-5, for a cell with two antennas, B/A = 1. Therefore, for type B symbols,
PowerFactorRatio =
= 0.5.
l Type B(NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of
antennas = 8 x 100 x 2 = 1600
Based on the preceding calculation results, you can infer that:

Pmax_out = 1200 x ReferenceSignalPwr 80 W
ReferenceSignalPwr 66.67 mW = 18.24 dBm
Issue 02 (2015-06-10)

18
eRAN
The value of the ReferenceSignalPwr parameter cannot be greater than 18.24 dBm.
Issue 02 (2015-06-10)

19
eRAN
4 Related Features
Related Features
LBFD-001003 Scalable Bandwidth

l
Prerequisite features
None
Mutually exclusive features

None
Impacted features
None
Issue 02 (2015-06-10)

20
eRAN
5 Network Impact
Network Impact
LBFD-001003 Scalable Bandwidth

l
System capacity
System capacities vary with bandwidths. A higher bandwidth allows more UEs to access
the network and to be scheduled and therefore supports higher UE and cell throughput.
Network performance
Under the same CPU, digital signal processor (DSP), and memory configurations, a
higher cell bandwidth uses more hardware resources. However, a higher system
bandwidth helps produce better service key performance indicators (KPIs).
Issue 02 (2015-06-10)

21
eRAN
6 Engineering Guidelines
Engineering Guidelines
6.1 When to Use Cell Management

The major function of eNodeBs is to provide radio cell coverage for UEs. Cell management
functionality must be enabled.
6.2 Required Information

Before you deploy the cell management feature, determine the cell establishment scenario and
collect information about the frequency band, bandwidth, cell radius, and power.
6.3 Planning
None
6.4 Deployment
Issue 02 (2015-06-10)

22
eRAN
6.4.1 Process
Figure 6-1 Cell deployment process
For details about "Configure device data", see "Creating a Single eNodeB" in chapter
"Creating Base Stations" of the 3900 Series Base Station Initial Configuration Guide.
6.4.2 Requirements
License
The following table lists the license control items related to cell establishment. Operators
must purchase and activate the following licenses.
Issue 02 (2015-06-10)
License Control Item
Model
NE
Sales Unit
RF Output Power (FDD)
LT1S0000PA00
eNode
B
per 20W
Carrier Bandwidth - 0~5MHz(FDD)
LT1S005MHZ00
eNode
B
per cell
LT1S010MHZ00
eNode
B
per cell
LT1S015MHZ00
eNode
B
per cell

23
eRAN
Model
NE
Sales Unit
LT1S020MHZ00
eNode
B
per cell
eNodeB FDD Basic Software,

V100R008 (FDD)
LT1S0BASIC08
eNode
B
per cell
RF Transmit Channel(FDD)
LT1S00RFTC00
eNode
B
per Channel
RF Receive Channel(FDD)
LT1S00RFRC00
eNode
B
per Channel
BB Transmit Channel(FDD)
LT1S00BBTC00
eNode
B
per Channel
BB Receive Channel(per Channel)

(FDD)
LT1S00BBRC00
eNode
B
per Channel
RRC Connected User (FDD)
LT1S0ACTUS00
eNode
B
per RRC
Connected
User
Throughput Capacity (FDD)
LT1S0THROU00
eNode
B
per Mbps
Resource Block(FDD)
LT1S0000RB00
eNode
B
per RB
The following license control item is required for the multi-carrier technology.
Model
NE
Sales Unit
Multi Carrier(per Carrier)(FDD)
LT1S000MCA00
eNodeB
per Carrier
NOTE
Number of multi-carrier licenses required for an RF module = Number of carriers on the RF module - 1
If the RF module supports only one carrier, multi-carrier licenses are not required.
For details, see License Management Feature Parameter Description.
Hardware
l
When selecting optical modules for the baseband processing units, ensure that data rates
over common public radio interface (CPRI) ports match the bandwidths and transmission
and reception modes of cells. For the constraints between the data rates over CPRI ports
and the bandwidths and transmission and reception modes of cells, see the related section
in BBU3900 Hardware Description.
Only RRU3908, MRFUd, or MRFU V2 can be used for a 1T1R cell whose signal
transmission and reception functions are performed by different antenna channels.
Issue 02 (2015-06-10)

24
eRAN
Bandwidths of the cells provided by the RRUs/RFUs must fall within the frequency
bands supported by the RRUs/RFUs.
If different uplink and downlink bandwidths are configured for a cell served by a macro
eNodeB, the following requirements must be met:
The transmission and reception modes of the cell must be 1T1R, 1T2R, or 2T2R.
The uplink and downlink bandwidths must be set to one of the following
combinations: 5 MHz/10 MHz, 10 MHz/5 MHz, 10 MHz/15 MHz, 15 MHz/10
MHz, 20 MHz/15 MHz, and 15 MHz/20 MHz.
RF modules must work in the 1800 MHz (band 3) frequency band. pRRUs are not
allowed.
The baseband processing unit must be the LBBPd or UBBPd. The LBBPc is not
allowed.
NOTE
When different uplink and downlink bandwidths are configured for a cell, the cell does not
support the 141 test and RF loopback.
The LampSite cell (pRRU aggregation cell) and macro cell cannot be established on the
same baseband processing unit. When both a LampSite cell and a macro cell are to be
established in an eNodeB, you need to configure different baseband resources for the
cells if you want to manually configure the baseband resources for the cells. Relevant
MML commands are as follows:
ADD BASEBANDEQM: This command is used to configure a piece of baseband

equipment.
ADD EUCELLSECTOREQM: This command is used to bind a macro cell to a

piece of baseband equipment.
ADD EUSECTOREQMGROUP: This command is used to bind a LampSite cell

to a piece of baseband equipment.
Scenario-specific Requirements
Establishing a Cell in a Common Sector Without RRU/RFU Combination
l
To establish a four-antenna cell in a common sector without RRU/RFU combination, the

following conditions must be met:
The RRUs/RFUs must be 2T4R or 4T4R units. For details about RRU/RFU models,
see 3900 Series Base Station Technical Description.
NOTE
In the load-sharing topology where RRUs/RFUs are connected to the same baseband board, optical
modules that support the 2.5 Gbit/s rate can be used. The load-sharing topology is not recommended.
Issue 02 (2015-06-10)
To establish two cells in a common sector without RRU/RFU combination, the following
conditions must be met:
The RRUs/RFUs must support multiple carriers. For details about RRU/RFU
models, see 3900 Series Base Station Technical Description.
A standardized bandwidth and a non-standardized bandwidth can be used for the

two cells.
The EARFCN range of the two cells must be within the frequency bands supported
by the RRUs/RFUs.
The EARFCN range of the two cells cannot overlap.

25
eRAN
The network topology must be star, chain, ring, or load sharing. For details, see RF
Unit and Topology Management Feature Parameter Description.
Cell frequencies and bandwidths must meet the constraints described in 3.3 Cell-related
Parameters.
Establishing a Cell in a Common Sector with RRU/RFU Combination

l
The two RRUs/RFUs must support the same frequency band and have the same number
of transmit and receive antennas.
The length difference between optical fiber cables used to connect the two RRUs/RFUs
to the BBU cannot exceed 100 m.
RRUs/RFUs must be capable of being combined to serve one sector. The RRU/RFU
capabilities are as follows:
Two 1T2R RRUs/RFUs can be combined and configured to work in 2T4R mode.
A 2T4R and a 0T4R RRU/RFU can be combined and configured to work in 2T8R
mode.
A 4T4R and a 0T4R RRU/RFU can be combined and configured to work in 4T8R
mode.
The RRU/RFU topology must be a star topology. For details, see RF Unit and Topology
Management Feature Parameter Description.
Parameters.
Establishing a Digital Combination Cell

l
The cell can be established only on the LBBPd, UBBP or UMDU.
The sector must be provided by RRU3821Es.
The RRUs support two to eight levels of cascading connections. CPRI compression can
be deployed to save CPRI resources. A maximum of four levels of cascading
connections is recommended. If the cascading level is greater than four, cell performance
is not guaranteed. In this case, you are advised to configure more cells.
The RRUs must be cascaded to a CPRI port on a baseband processing unit in a chain
topology.
The cell does not support extended cyclic prefix (CP) or uplink coordinated multi-point
(UL CoMP).
The cell must work on a bandwidth of 5 MHz, 10 MHz, 15 MHz, or 20 MHz, and the
transmission and reception mode of the cell can be 2T2R or 1T1R.
Parameters.
6.4.3 Data Preparation

The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.
Issue 02 (2015-06-10)

26
eRAN
Issue 02 (2015-06-10)
Parameter
Name
Parameter ID
Setting Notes
Data
Source
Sector ID
SECTOR.SECT
ORID
Ensure that each sector number is

unique.
Network
plan
(negotiation
not
required)
Sector Name
SECTOR.SECN
AME
N/A
Network
plan
(negotiation
not
required)
Location Name
SECTOR.LOCA
TIONNAME
N/A
Network
plan
(negotiation
not
required)
User Label
SECTOR.USER
LABEL
N/A
Network
plan
(negotiation
not
required)
Antenna
Number
SECTOR.ANTN
UM
N/A
Network
plan
(negotiation
not
required)
Cabinet No. of
Antenna 1 to
Cabinet No. of
Antenna 8
SECTOR.ANT1
CN to
SECTOR.ANT8
CN
N/A
Network
plan
(negotiation
not
required)
Subrack No. of
Antenna 1 to
Subrack No. of
Antenna 8
SECTOR.ANT1
SRN to
SECTOR.ANT8
SRN
N/A
Network
plan
(negotiation
not
required)

27
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data
Source
Slot No. of
Antenna 1 to
Slot No. of
Antenna 8
SECTOR.ANT1
SN to
SECTOR.ANT8
SN
For a LampSite eNodeB,
Network
plan
(negotiation
not
required)
l If the pRRU3901 is used, set this

parameter to 255 to enable
automatic allocation of the slot
number to an antenna. If the slot
number is to be assigned
manually, set this parameter to a
value ranging from 1 to 3,
depending on the slot number of
the RF daughter board.
However, manual and automatic
configurations cannot be both
used for the same pRRU.
l If the pRRU3902 or pRRU3911
is used, set this parameter to 0.
Channel No. of
Antenna 1 to
Channel No. of
Antenna 8
SECTOR.ANT1
N to
SECTOR.ANT8
N
N/A
Network
plan
(negotiation
not
required)
Create Default
Sector
Equipment
SECTOR.CREA
TESECTOREQ
M
N/A
Network
plan
(negotiation
not
required)
Default Sector
Equipment ID
SECTOR.SECT
OREQMID
N/A
Network
plan
(negotiation
not
required)
The following table describes the parameters that must be set in a SECTOREQM MO to
configure a piece of sector equipment.
Issue 02 (2015-06-10)
Parameter
Name
Parameter ID
Setting Notes
Data
Source
Sector
equipment ID
SECTOREQM.sect
orEqmId
N/A
Network
plan
(negotiation
not
required)

28
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data
Source
Sector ID
SECTOREQM.sect
orId
N/A
Network
plan
(negotiation
not
required)
Antenna
Number
SECTOREQM.AN
TNUM
N/A
Network
plan
(negotiation
not
required)
Cabinet No. of
Antenna 1 to
Cabinet No. of
Antenna 8
SECTOREQM.AN
T1CNANT1CN to
SECTOREQM.AN
T8CN
N/A
Network
plan
(negotiation
not
required)
Subrack No.
of Antenna 1
to Subrack No.
of Antenna 8
SECTOREQM.AN
T1SRN to
SECTOREQM.AN
T8SRN
N/A
Network
plan
(negotiation
not
required)
Slot No. of
Antenna 1 to
Slot No. of
Antenna 8
SECTOREQM.AN
T1SN to
SECTOREQM.AN
T8SN
For a LampSite eNodeB,
Network
plan
(negotiation
not
required)
l If the pRRU3901 is used, set

this parameter to 255 to enable
automatic allocation of the slot
number to an antenna. If the
slot number is to be assigned
manually, set this parameter to a
value ranging from 1 to 3,
depending on the slot number
of the RF daughter board.
However, manual and automatic
configurations cannot be both
used for the same pRRU.
l If the pRRU3902 is used, set
this parameter to 0.
Issue 02 (2015-06-10)
Channel No.
of Antenna 1
to Channel
No. of
Antenna 8
SECTOREQM.AN
T1N to
SECTOREQM.AN
T8N
N/A
Network
plan
(negotiation
not
required)
Antenna 1
RX/TX Mode
to Antenna 8
RX/TX Mode
SECTOREQM.AN
TTYPE1 to
SECTOREQM.AN
TTYPE8
N/A
Network
plan
(negotiation
not
required)

29
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data
Source
TX Antenna 1
Master/Slave
mode to TX
Antenna 8
Master/Slave
mode
SECTOREQM.TX
BKPMODE1 to
SECTOREQM.TX
BKPMODE8
Set the parameter value to

MASTER(Master).
Network
plan
(negotiation
not
required)
This parameter cannot be set to

SLAVE(Slave) because the
eNodeBs do not support antennas
working in active/standby mode.
The following table describes the parameters that must be set in a CnOperator MO to
configure an operator.
Parameter
Name
Parameter ID
Setting Notes
Data Source
CN Operator
ID
CnOperator.Cn
OperatorId
N/A
Network plan
(negotiation not
required)
CN Operator
name
CnOperator.Cn
OperatorName
N/A
Network plan
(negotiation not
required)
CN Operator
type
CnOperator.Cn
OperatorType
This parameter specifies the

operator type: primary or
secondary. Each eNodeB can be
configured with only one
primary operator but multiple
secondary operators.
Network plan
(negotiation not
required)
Mobile country
code
CnOperator.Mcc
N/A
Network plan
(negotiation not
required)
Mobile
network code
CnOperator.Mnc
N/A
Network plan
(negotiation not
required)
The following table describes the parameters that must be set in a CnOperatorTa MO to
configure a tracking area for an operator.
Issue 02 (2015-06-10)

30
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data
Source
Local tracking
area ID
CnOperatorTa.Tr
ackingAreaId
This parameter uniquely identifies a

tracking area. This parameter is used
only in the eNodeB and is different
from the tracking area identity (TAI)
configured in the tracking area list
(TAL) on the MME.
Network
plan
(negotiatio
n not
required)
CN Operator
ID
CnOperatorTa.C
nOperatorId
N/A
Network
plan
(negotiatio
n not
required)
Tracking area
code
CnOperatorTa.Ta
c
N/A
Network
plan
(negotiatio
n not
required)
The following table describes the parameters that must be set in a Cell MO to configure a cell.
Issue 02 (2015-06-10)
Parameter
Name
Parameter ID
Setting Notes
Data Source
Local Cell ID
Cell.LocalCellId
N/A
Network plan
(negotiation
not required)
Cell Name
Cell.CellName
N/A
Network plan
(negotiation
not required)
Csg indicator
Cell.CsgInd
The default value for this parameter is

BOOLEAN_FALSE(FALSE).
Network plan
(negotiation
not required)
Uplink cyclic
prefix length
Cell.UlCyclicPr
efix
Retain the default value

NORMAL_CP(Normal).
Network plan
(negotiation
not required)
Downlink
cyclic prefix
length
Cell.DlCyclicPr
efix
Retain the default value

NORMAL_CP(Normal).
Network plan
(negotiation
not required)
Frequency
band
Cell.FreqBand
N/A
Network plan
(negotiation
not required)

31
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Uplink earfcn
indication
Cell.UlEarfcnCf
gInd
N/A
Network plan
(negotiation
not required)
Uplink earfcn
Cell.UlEarfcn
This parameter is optional, depending

on the value of the
Cell.UlEarfcnCfgInd parameter.
Network plan
(negotiation
not required)
l If Cell.UlEarfcnCfgInd is set to
CFG(Configure), set
Cell.UlEarfcn.
l If Cell.UlEarfcnCfgInd is set to
NOT_CFG(Not configure), do
not set Cell.UlEarfcn.
Downlink
EARFCN
Cell.DlEarfcn
The downlink frequency identified by

the EARFCN must be located in the
band specified by the Cell.FreqBand
parameter.
Network plan
(negotiation
not required)
When establishing two cells in a

common sector without RRU/RFU
combination, the EARFCN range of
the two cells do not overlap.
Issue 02 (2015-06-10)
Uplink
bandwidth
Cell.UlBandWid
th
N/A
Network plan
(negotiation
not required)
Downlink
bandwidth
Cell.DlBandWid
th
N/A
Network plan
(negotiation
not required)
Cell ID
Cell.CellId
N/A
Network plan
(negotiation
not required)
Physical cell
ID
Cell.PhyCellId
N/A
Network plan
(negotiation
not required)
Additional
spectrum
emission
Cell.AdditionalS
pectrumEmissio
n
N/A
Network plan
(negotiation
not required)
Cell FDD
TDD
indication
Cell.FddTddInd
Set this parameter to

CELL_FDD(FDD).
Network plan
(negotiation
not required)
Cell specific
offset
Cell.CellSpecific
Offset
Set this parameter to 0.
Network plan
(negotiation
not required)

32
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Frequency
offset
Cell.QoffsetFre
q
Set this parameter to 0.
Network plan
(negotiation
not required)
Root
sequence
index
Cell.RootSeque
nceIdx
For details about setting constraints,

see the MO reference for the eNodeB.
Network plan
(negotiation
not required)
Preamble
format
Cell.PreambleF
mt
N/A
Network plan
(negotiation
not required)
Cell radius
Cell.CellRadius
The value of this parameter must be

equal to or greater than the actual cell
radius. Otherwise, UEs at the cell
edge may fail to access the network.
Network plan
(negotiation
not required)
If more than three physical cells are

established on a UBBPd8 or more
than six physical cells are established
on a UBBPd9, set this parameter to a
value equal to or smaller than 9895.
Issue 02 (2015-06-10)
Customized
bandwidth
configure
indicator
Cell.Customized
BandWidthCfgI
nd
N/A
Network plan
(negotiation
not required)
Customized
uplink
bandwidth
Cell.Customized
ULBandWidth
This parameter is required only when

the Cell.CustomizedBandWidthCfgInd parameter is set to
CFG(Configure).
Network plan
(negotiation
not required)
Customized
downlink
bandwidth
Cell.Customized
DLBandWidth

the Cell.CustomizedBandWidthCfgInd parameter is set to
CFG(Configure).
Network plan
(negotiation
not required)
Ue max
power
allowed
configure
indicator
Cell.UePowerM
axCfgInd
N/A
Network plan
(negotiation
not required)
Max transmit
power
allowed
Cell.UePowerM
ax

the Cell.UePowerMaxCfgInd
parameter is set to CFG(Configure).
Network plan
(negotiation
not required)
Flag of MultiRRU Cell
Cell.MultiRruC
ellFlag
Set this parameter to

CFG(Configure) while configuring
multi-RRU cells.
Network plan
(negotiation
not required)

33
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Mode of
Multi-RRU
Cell
Cell.MultiRruC
ellMode

the Cell.MultiRruCellFlag parameter
is set to CFG(Configure).
Network plan
(negotiation
not required)
Air Cell Flag
Cell.AirCellFlag
N/A
Network plan
(negotiation
not required)
CRS Port
Number
CrsPortNum
Set this parameter based on the

number of downlink channels. For
example, set this parameter to 2 if a
cell works in 2T mode and to 1 if the
cell works in 1T1R mode.
Network plan
(negotiation
not required)
Cell
transmission
and reception
mode
Cell.TxRxMode
This parameter should be the same as

the SECTOREQM.antNum
parameter in the Sector MO.
Network plan
(negotiation
not required)
User Label
Cell.UserLabel
N/A
Network plan
(negotiation
not required)
Work mode
Cell.WorkMode
N/A
Network plan
(negotiation
not required)
Cell Slave
Band
Cell.CellSlaveB
and
Set this parameter by running the

ADD CELLBAND command.
Network plan
(negotiation
not required)
Cell Standby
Mode
Cell.EuCellStan
dbyMode
N/A
Radio
planning
(Internal
planning)
The following table describes the parameters that must be set in an EUCELLSECTOREQM
MO to configure a piece of sector equipment for the cell.
Issue 02 (2015-06-10)
Parameter
Name
Parameter ID
Setting Notes
Data Source
Local Cell ID
EUCELLSECT
OREQM.LocalC
ellId
N/A
Network plan
(negotiation
not required)
Sector
equipment ID
EUCELLSECT
OREQM.sectorE
qmId
N/A
Network plan
(negotiation
not required)

34
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Reference
signal power
EUCELLSECT
OREQM.Referen
ceSignalPwr
If this parameter is set to 32767, it

is invalid. In this case, the
reference signal power of the cell
is specified in the PDSCHCfg
MO.
Network plan
(negotiation
not required)
ReferenceSignalPwr parameter.
Baseband
equipment ID
EUCELLSECT
OREQM.BaseBa
ndEqmId
If this parameter is set to 255, no

baseband equipment is specified
for the cell. In this case, the cell
can use any baseband equipment
of the eNodeB.
Network plan
(negotiation
not required)
Sector CPRI
Compression
EUCELLSECT
OREQM.SectorC
priCompression
This parameter specifies the CPRI

compression mode of each piece
of sector equipment. It is used
only when the Mode of MultiRRU Cell parameter is set to
SFN(SFN) or
CELL_COMBINATION(Cell
Combination). When this
parameter is set to
NULL(Invalid), the CPRI
compression mode of carriers is
specified by the CPRI
Compression parameter in the
CELL MO. When this parameter
is set to another value, the CPRI
compression mode of carriers is
specified by this parameter.
Default/
recommende
d value:
Auto Config
Flag
EUCELLSECT
OREQM.AutoCf
gFlag
N/A
Radio
planning
(Internal
planning)
The following table describes the parameters that must be set in a CellOp MO to configure a
cell operator.
Issue 02 (2015-06-10)
Parameter
Name
Parameter ID
Setting Notes
Data Source
Local Cell ID
CellOp.LocalCell
Id
N/A
Network plan
(negotiation not
required)

35
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Local tracking
area ID
CellOp.Tracking
AreaId
N/A
Network plan
(negotiation not
required)
Cell reserved
for operator
CellOp.CellReser
vedForOp
N/A
Network plan
(negotiation not
required)
Operator uplink
RB used ratio
CellOp.OpUlRbU
sedRatio
N/A
Network plan
(negotiation not
required)
Operator
downlink RB
used ratio
CellOp.OpDlRbU
sedRatio
N/A
Network plan
(negotiation not
required)
The following table describes the parameters that must be set in a BaseBandEqm MO to
configure baseband equipment information.
Issue 02 (2015-06-10)

36
eRAN
Parameter
Name
Parameter ID
Setting Notes
Data Source
Baseband
equipment ID
BaseBandEqm.BASEBA
NDEQMID
Each BaseBandEqmId
parameter value identifies
a piece of baseband
equipment.
Network plan
(negotiation
not required)
One piece of baseband

equipment can include
multiple BBPs. For
example, the following
command specifies that
the baseband equipment
numbered 0 includes the
BBPs installed in slots 1
and 2:
ADD
BASEBANDEQM:BASE
BANDEQMID=0,BASEB
ANDEQMTYPE=ULDL,
UMTSDEMMODE=NUL
L,SN1=2,SN2=1;
However, it is
recommended that one
piece of baseband
equipment includes only
one BBP.
A BBP cannot belong to
multiple pieces of
baseband equipment.
Baseband
Equipment
Type
BaseBandEqm.BASEBA
NDEQMTYPE
N/A
Radio
planning
(Internal
planning)
6.4.4 Precautions
None
6.4.5 Hardware Adjustment

To establish a digital combination cell in multiple sectors, the RRUs serving this cell must be
installed as follows:
l
Issue 02 (2015-06-10)
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 Figure 6-2, four RRUs are installed to serve
a cell. The spacing between RRU1 and RRU4 is the largest and cannot exceed 1000 m.

37
eRAN
Figure 6-2 Example of RRUs not installed in a straight line
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 Figure 6-3, four RRUs are installed
to serve a cell. The spacing between two neighboring RRUs (for example, RRU1 and
RRU2) cannot exceed 1000 m.
Figure 6-3 Example of RRUs installed in a straight line
RRUs must be cascaded in a chain topology as shown in Figure 6-4. The requirement of
the length of optical fibers is as follows:
NOTE
Ln represents the length of the optical fiber between two neighboring RRUs or between a baseband
processing unit and a neighboring RRU.
The total length of optical fibers connecting all the RRUs serving a cell cannot exceed 5
km. That is, the sum of L2, L3, and L4 cannot be greater than 5 km.
The total length of optical fibers connecting all the RRUs and the baseband processing
unit cannot exceed 20 km. That is, the sum of L1, L2, L3, and L4 cannot be greater than
20 km.
Issue 02 (2015-06-10)

38
eRAN
Figure 6-4 Fiber optic length requirement
6.4.6 Activation
6.4.6.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Before configuring sectors and cells in batches using the Configuration Management Express
(CME), you have to prepare templates and then customize a summary data file.
l
Preparing templates
Sector configuration data is contained in the eNodeB template. Cell configuration data is
contained in the cell template.
If the eNodeB template or the cell template does not meet configuration requirements,
you can modify the configuration data in the template. For example, before establishing
a cell with the transmission and reception mode of 1T1R, you have to modify the
parameter configurations in the eNodeB template and the cell template as follows:
In the eNodeB template, set ANTNUM in the SECTOR and SECTOREQM MOs
to 1. In addition, set the parameters such as ANT1CN, ANT1SRN, ANT1SN, and
ANT1N for the RRU connected to the antenna.
In the cell template, set TXRXMODE in the Cell MO to 1T1R.

For details about how to modify the configuration data in the eNodeB template or
the cell template, see "Preparing Templates" in the initial configuration guide for
the eNodeB.
NOTE
On the Base Station Transport Data sheet in the summary data file, enter the eNodeB template name.
On the LTE Cell sheet in the summary data file, enter the cell template name.
Customizing a summary data file

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 "Creating eNodeBs in Batches" in the initial configuration
guide for the eNodeB, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a
customized file, depending on the following conditions:
Issue 02 (2015-06-10)
The MOs in Table 6-1 are contained in a scenario-specific summary data file. In
this situation, set the parameters in the MOs, and then verify and save the file.
Some MOs in Table 6-1 are not contained in a scenario-specific summary data file.
In this situation, customize a summary data file to include the MOs before you can
set the parameters.
39
eRAN
Table 6-1 Cell management parameters (batch configuration for newly deployed eNodeBs)
MO
Sheet in the
Summary Data
File
Parameter Group
Remarks
CELL
LTE Cell
*LocalCellID
Parameters marked
with an asterisk (*) are
mandatory. Other
parameters are optional.
*CellName
*CellId
CsgInd
UlCyclicPrefix
DlCyclicPrefix
*FrequencyBand
Uplink earfcn indication
UlEarfcn
*DlEarfcn
*DlBandwidth
*UlBandwidth
*PCI
AdditionalSpectrumEmission
CellActiveState
CellAdminState
CellMidBlkTimer
*FddTddInd
SubframeAssignment
SpecialSubframePatterns
CellSpecificOffset
QoffsetFreq
*RootSequenceIdx
PreambleFmt
CellRadius
Customized bandwidth
configure indicator
Customized uplink
bandwidth(0.1MHz)
Customized downlink
bandwidth(0.1MHz)
PowerMaxCfgInd
UePowerMax
MultiRruCellFlag
MultiRruCellMode
*Cell transmission and reception
mode
Issue 02 (2015-06-10)

40
eRAN
MO
Sheet in the
Summary Data
File
Parameter Group
Remarks
CellSlaveBand
CnOper
ator
Common Data
*Operator ID
N/A
*Operator name
*Operator type
*Mcc
*Mnc
CnOper
atorTA
LTE Cell
*TrackingAreaId
N/A
*TAC
*CnOperatorId
CellOp
LTE Cell
*LocalCellID
N/A
*TrackingAreaId
EUCE
LLSEC
TORE
QM
LTE Cell
*LocalCellID
N/A
Sector equipment ID
Baseband equipment ID
6.4.6.2 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 Customize a summary data file with the MOs and parameters listed in "Using the CME to
Perform Batch Configuration for Newly Deployed eNodeBs". For detailed operations, press
F1 in a CME window and navigate to Managing the CME > CME Guidelines > LTE
Application Management > eNodeB Related Operations > Customizing a Summary Data
File for Batch eNodeB Configuration in the CME online help.
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 according to the setting notes
provided in the "Data Preparation" section, 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. For
Issue 02 (2015-06-10)

41
eRAN
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End
6.4.6.3 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-5, select the eNodeB to which the MOs belong.
Figure 6-5 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
6.4.6.4 Using MML Commands

This section describes how to activate the cell management feature using MML commands in
the following scenarios:
Scenario 1: Establishing a Cell in a Common Sector
Issue 02 (2015-06-10)

42
eRAN
Scenario 2: Establishing a Cell in Multiple Sectors with RRU/RFU Splitting

Scenario 3: Establishing a Cell in a Single Sector with RRU/RFU Combination
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs

Step 1 (Optional) If an RRU is added, add a sector and sector equipment.
1.
Run the ADD SECTOR command to add a sector.

NOTE
A cell can work in 1T2R, 2T2R, 2T4R, or 4T4R mode, based on which the ANTNUM parameter
is configured. For example, if a cell works in 2T4R mode, the ANTNUM parameter must be set to
4.
2.
Run the ADD SECTOREQM command to add sector equipment.

NOTE
If the SECTOR.CREATESECTOREQM parameter in substep 1 is set to TRUE(TRUE), ADD

SECTOREQM is not required. The default value of this parameter is FALSE(FALSE).
Step 2 (Optional) If the baseband equipment needs to be bound to a cell, run the ADD
BASEBANDEQM command to add baseband equipment.
Step 3 (Optional) If the operator and tracking area information is not configured, perform the
following steps:
1.
Run the ADD CNOPERATOR command to add an operator.
2.
Run the ADD CNOPERATORTA command to add a tracking area.
Step 4 Run the ADD CELL command to add a cell.

Step 5 Run the ADD EUCELLSECTOREQM command to bind sector equipment and (or)
baseband equipment (if required) for the cell.
Step 6 Run the ADD CELLOP command to add an operator for the cell.
Step 7 Run the ACT CELL command to activate the cell.
----End

Establishing two 2T2R cells by splitting a 4T4R RRU is used as an example in this section.
Perform steps described in Scenario 1: Establishing a Cell in a Common Sector. In
addition, pay attention to the following details:
l
When running the ADD SECTOR and ADD SECTOREQM commands, configure two
sectors with the antNum parameter set to 2, and then configure two antenna channels to
one sector and the other two antenna channels to the other sector.
When running the ADD EUCELLSECTOREQM command, bind the two cells with
two pieces of sector equipment.
Issue 02 (2015-06-10)

43
eRAN

Establishing a 4T4R cell by combining two 2T2R RRUs is used as an example in this section.
Perform steps described in Scenario 1: Establishing a Cell in a Common Sector. In
addition, pay attention to the following details:
l
When running the ADD SECTOR and ADD SECTOREQM commands to configure a
sector, set the antNum parameter to 4. Then, divide the four antenna ports into two
groups and configure them to the two 2T2R RRUs, respectively.
When running the ADD CELL command to establish a cell, set the
MULTIRRUCELLFLAG parameter to BOOLEAN_TRUE and the
cell.MULTIRRUCELLMODE parameter to CELL_COMBINATION.
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs

Establishing a digital combination 3-sector cell is used as an example in this section. Perform
steps described in Scenario 1: Establishing a Cell in a Common Sector. In addition, pay
attention to the following details:
l
Run the ADD SECTOR and ADD SECTOREQM commands for three times,
respectively and establish a sector on each RRU.
When running the ADD CELL command, establish only one cell with the
MultiRruCellFlag parameter set to BOOLEAN_TRUE(True) and the
MultiRruCellMode parameter set to DIGITAL_COMBINATION(Cell Digital
Combination).
When running the ADD EUCELLSECTOREQM command, bind the three pieces of
sector equipment that have been established to one cell.
6.4.6.5 MML Command Examples

This section provides the MML command examples in different scenarios.
l
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs/RFUs

NOTE
The parameter settings in the following commands are used for reference only. Set the parameters
based on network requirements.

//(Optional) Adding a sector and sector equipment
ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;
//(Optional) Performing the following steps if no operator or tracking area information is

added
1.
Add an operator.
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01";
2.
Issue 02 (2015-06-10)
Add a tracking area.

44
eRAN
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33;
//Adding a cell
ADD CELL: LocalCellId=0, CellName="cell0", FreqBand=12, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=5020, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0,
PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R
//Adding sector equipment for a cell

ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
//Adding an operator for a cell

ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
//Activating a cell
ACT CELL: LocalCellId=0;

Establishing two 2T2R cells by splitting a 4T4R RRU is used as an example.
//Adding two 2T2R sectors with the sector number as 0 and 1 (sector 0 uses antenna ports A
and B, and sector 1 uses antenna ports C and D)
ADD SECTOR: SECTORID=0, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=2,
ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0,
ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;
ADD SECTOR: SECTORID=1, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=2,
ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0C, ANT2CN=0, ANT2SRN=60, ANT2SN=0,
ANT2N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=1;

added
1.
Add an operator.
2.

//Adding two cells

UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
//Adding two 2T2R sector equipment groups

ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
//Adding the operator information about two cells

Activating two cells

Issue 02 (2015-06-10)

45
eRAN

//Adding a sector and sector equipment (separating four antennas to two groups and
configuring them to the two 2T2R RRUs)
ADD SECTOR: SECTORID=0, SECNAME="Sector0", LOCATIONNAME="River", USERLABEL="0",
ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60,
ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0A, ANT4CN=0,
ANT4SRN=61, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;

added
1.
Add an operator.
2.

//Adding a cell
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=CELL_COMBINATION, TxRxMode=4T4R;

//Adding the mapping relationship between a cell and sector equipment

//Activating a cell
ACT CELL:LocalCellId=0;
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs/

RFUs
Establishing a digital combination cell in two sectors is used as an example.
//Adding a sector and sector equipment
ADD
SECTOR:SECTORID=0,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN
=60,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRUE,SECTOREQMID=0;
ADD
SECTOR:SECTORID=1,ANTNUM=2,ANT1CN=0,ANT1SRN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN
=61,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRUE,SECTOREQMID=1;

added
1.
Add an operator.
2.

Issue 02 (2015-06-10)

46
eRAN
//Adding a digital combination cell

ADD CELL: LocalCellId=0, CellName="Cell0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=DIGITAL_COMBINATION, TxRxMode=2T2R;
//Adding the mapping relationship between a cell and sector equipment


//Activating a cell
6.4.7 Activation Observation

Step 1 Run the DSP CELL command to check the cell status.
If the Cell instance state parameter is Normal, the cell has been activated.
Step 2 Use a UE to access this cell. If the UE successfully accesses the cell, the cell is working
properly.
----End
6.4.8 Reconfiguration
For cell-related reconfiguration, see eRAN Reconfiguration Guide.
6.4.9 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 6.4.6.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 6-2.
Table 6-2 MO involved in feature deactivation
MO
Sheet in the Summary Data

File
Parameter Group
Cell
LTE Cell
Cell
Using the CME to Perform Single Configuration

On the CME, change the parameter according to Table 6-2. For detailed instructions, see
"6.4.6.3 Using the CME to Perform Single Configuration" described for feature activation.
Issue 02 (2015-06-10)

47
eRAN
Using MML Commands

Run the DEA CELL command to deactivate the cell.
MML Command Examples

DEA CELL: LocalCellId=0;
6.5 Performance Monitoring

None
6.6 Parameter Optimization

None
6.7 Troubleshooting
Fault Description
Cell status is abnormal.
Fault Handling
Step 1 Start cell status monitoring on the U2000 client to check the cell status. If a cell outage
occurs, perform operations according to zh-cn_bookmap_0001792924.htmlFeature
Description About Cell Outage Detection and Recovery.
Step 2 View the alarms on the U2000 client. If any alarm has been reported, clear the alarm
according to 3900 Series Base Station Alarm Reference.
The following table lists the common alarms related to a cell.
Alarm ID
Alarm Name
ALM-26816
Licensed Feature Unusable
ALM-26818
No License Running in System
ALM-29240
Cell Unavailable
ALM-29243
Cell Capability Degraded
ALM-29245
Cell Blocked
ALM-29247
Cell PCI Conflict
ALM-29242
No Traffic Volume in the Cell
----End
Issue 02 (2015-06-10)

48
eRAN
7 Parameters
Parameters
Table 7-1 Parameters

MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CellDlp
cPdschP
a
PaPcOff
MOD
CELLD
LPCPD
SCHPA
LBFD-0
02016 /
TDLBF
D-00201
6
Dynami
c
Downlin
k Power
Allocati
on
Meaning: Indicates the PA to be used when PA

adjustment for PDSCH power control is disabled, DL
ICIC is disabled, and the even power distribution is
used for the PDSCH.
LST
CELLD
LPCPD
SCHPA
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, DB2_P_A, DB3_P_A
Default Value: DB_3_P_A(-3 dB)
PDSCH
Cfg
Pb
MOD
PDSCH
CFG
LST
PDSCH
CFG
Issue 02 (2015-06-10)
LBFD-0
02016 /
TDLBF
D-00201
6
LBFD-0
02009 /
TDLBF
D-00200
9
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.
Broadca
st of
system
informat
ion
Unit: None
GUI Value Range: 0~3

Actual Value Range: 0~3
Default Value: 1

49
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
eUCellS
ectorEq
m
Referen
ceSignal
Pwr
ADD
EUCEL
LSECT
OREQ
M
None
None
Meaning: Indicates the reference signal power of the

cell sector device. The value 32767 indicates that this
reference signal power parameter is invalid. In this
case, the reference signal power of the cell equals the
value of the PDSCHCFG parameter. For details, see
3GPP TS 36.213.This parameter is valid only when a
multi-RRU cell works in
SFN,MPRU_AGGREGATION or cell combination
mode.
MOD
EUCEL
LSECT
OREQ
M
GUI Value Range: -600~500,32767
LST
EUCEL
LSECT
OREQ
M
EuSecto
rEqmGr
oup
Referen
ceSignal
Pwr
ADD
EUSEC
TOREQ
MGRO
UP
Unit: 0.1dBm
Actual Value Range: -60~50,3276.7
Default Value: 32767
None
None
MOD
EUSEC
TOREQ
MGRO
UP
LST
EUSEC
TOREQ
MGRO
UP
Meaning: Indicates the reference signal power of a

sector equipment group for a cell (all sets of sector
equipment in the sector equipment group have the
same reference signal power). If this parameter is set
to 32767, the parameter value is invalid, and the cell
uses the reference signal power specified by the
ReferenceSignalPwr parameter in the PDSCHCFG
MO. For details, see 3GPP TS 36.213. This parameter
takes effect only when parameter MultiRruCellFlag is
set to BOOLEAN_TRUE and MultiRruCellMode is
set to MPRU_AGGREGATION or FDD SFN,
respectively.
GUI Value Range: -600~500,32767
Unit: 0.1dBm
Actual Value Range: -60~50,3276.7
PDSCH
Cfg
Referen
ceSignal
Pwr
MOD
PDSCH
CFG
LST
PDSCH
CFG
Issue 02 (2015-06-10)
LBFD-0
02016 /
TDLBF
D-00201
6
LBFD-0
02009 /
TDLBF
D-00200
9
Dynami
c
Downlin
k Power
Allocati
on
Broadca
st of
system
informat
ion
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.
GUI Value Range: -600~500
Unit: 0.1dBm
Actual Value Range: -60~50
Default Value: 182

50
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
SECTO
R
SECTO
RID
ADD
SECTO
R
None
None
Meaning: Indicates the number of the sector.

Unit: None
DSP
SECTO
R

Default Value: None
LST
SECTO
R
MOD
SECTO
R
RMV
SECTO
R
SECTO
R
SECNA
ME
ADD
SECTO
R
None
None
Meaning: Indicates the name of the sector.

GUI Value Range: 0~99 characters
Unit: None
MOD
SECTO
R
Actual Value Range: 0~99 characters

Default Value: NULL(empty string)
LST
SECTO
R
SECTO
R
SECTO
R
LOCATI
ONNA
ME
USERL
ABEL
ADD
SECTO
R
None
None
Meaning: Indicates the location name of the base

station.
MOD
SECTO
R
Unit: None
LST
SECTO
R
ADD
SECTO
R
MOD
SECTO
R
LST
SECTO
R
None
None
Meaning: Indicates the user-defined information of a

sector. The value of this parameter consists of xx::yy
and common character strings, which are separated by
percentage signs (%), for example, %tel::
88888888%owner::huawei%20130101. xx::yy
indicates that the value of xx is yy.
Unit: None
Issue 02 (2015-06-10)

51
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
SECTO
REQM
SECTO
REQMI
D
ADD
SECTO
REQM
None
None
Meaning: Indicates the number of the sector

equipment.
LST
SECTO
REQM
Unit: None
MOD
SECTO
REQM
Default Value: None
RMV
SECTO
REQM
LST
SECTO
R
SECTO
REQM
SECTO
RID
ADD
SECTO
REQM
LST
SECTO
REQM
None
None
Meaning: Indicates the number of the sector in which

the sector equipment is located.
Unit: None
Default Value: None
Issue 02 (2015-06-10)

52
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
ator
CnOper
atorId
ADD
CNOPE
RATOR
LOFD-0
01036
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the index of the operator.
LST
CNOPE
RATOR
LOFD-0
01037
LOFD-0
01086
MOD
CNOPE
RATOR
TDLOF
D-00111
2
RMV
CNOPE
RATOR
LOFD-0
70206

Unit: None
Default Value: None
RAN
Sharing
with
Dedicate
d
Carrier
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
Issue 02 (2015-06-10)

53
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
ator
CnOper
atorNam
e
ADD
CNOPE
RATOR
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the name of the operator.
MOD
CNOPE
RATOR
LST
CNOPE
RATOR
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
01086 /
TDLOF
D-00108
6
TDLOF
D-00111
2
LOFD-0
70206

Unit: None
Default Value: None
RAN
Sharing
with
Dedicate
d
Carrier
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
Issue 02 (2015-06-10)

54
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
ator
CnOper
atorType
ADD
CNOPE
RATOR
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
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.
MOD
CNOPE
RATOR
LST
CNOPE
RATOR
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
01086 /
TDLOF
D-00108
6
TDLOF
D-00111
2
LOFD-0
70206
RAN
Sharing
with
Dedicate
d
Carrier
RAN
Sharing
by More
Operator
s
GUI Value Range:

CNOPERATOR_PRIMARY(Primary Operator),
CNOPERATOR_SECONDARY(Secondary Operator)
Unit: None
Actual Value Range: CNOPERATOR_PRIMARY,
CNOPERATOR_SECONDARY
Default Value: None
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
Issue 02 (2015-06-10)

55
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
ator
Mcc
ADD
CNOPE
RATOR
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the mobile country code (MCC) of

the operator.
RAN
Sharing
with
Dedicate
d
Carrier
Default Value: None
MOD
CNOPE
RATOR
LST
CNOPE
RATOR
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
01086 /
TDLOF
D-00108
6
TDLOF
D-00111
2
LOFD-0
70206
GUI Value Range: 3 characters

Unit: None
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
Issue 02 (2015-06-10)

56
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
ator
Mnc
ADD
CNOPE
RATOR
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
Carrier
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.
MOD
CNOPE
RATOR
LST
CNOPE
RATOR
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
01086 /
TDLOF
D-00108
6
TDLOF
D-00111
2
LOFD-0
70206
RAN
Sharing
with
Dedicate
d
Carrier

Unit: None
Actual Value Range: 00~99,000~999
Default Value: None
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
CnOper
atorTa
Trackin
gAreaId
ADD
CNOPE
RATOR
TA
LST
CNOPE
RATOR
TA
MOD
CNOPE
RATOR
TA
RMV
CNOPE
RATOR
TA
Issue 02 (2015-06-10)
LOFD-0
01036 /
TDLOF
D-00103
6
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
70206
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the tracking area ID, which

uniquely identifies an entry of tracking area
information. This parameter is used only within the
eNodeB and is not used during the information
exchange with the EPC. This is different from the TAI
configured in the EPC TAL.
RAN
Sharing
with
Dedicate
d
Carrier

Unit: None
Default Value: None
Hybrid
RAN
Sharing

57
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CnOper
atorTa
CnOper
atorId
ADD
CNOPE
RATOR
TA
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the index of the operator.
MOD
CNOPE
RATOR
TA
LST
CNOPE
RATOR
TA
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
70206

Unit: None
Default Value: None
RAN
Sharing
with
Dedicate
d
Carrier
Hybrid
RAN
Sharing
CnOper
atorTa
Tac
ADD
CNOPE
RATOR
TA
MOD
CNOPE
RATOR
TA
LST
CNOPE
RATOR
TA
LOFD-0
01036 /
TDLOF
D-00103
6
LOFD-0
01037 /
TDLOF
D-00103
7
LOFD-0
70206
RAN
Sharing
with
Commo
n
Carrier
RAN
Sharing
with
Dedicate
d
Carrier
Hybrid
RAN
Sharing
Issue 02 (2015-06-10)
Meaning: Indicates the tracking area code (TAC),

which 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. Two TAC values
0x0000(0) and 0xFFFE(65534) are reserved according
to the protocol and will not be used in future versions.
Therefore, do not use 0 or 65534 as a TAC value in
TAC planning or configuration.
Unit: None
Default Value: None

58
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
LocalCe
llId
ACT
CELL
None
None
Meaning: Indicates the local ID of the cell. It uniquely

identifies a cell within a BS.
ADD
CELL
ADD
CELLB
AND
Unit: None
Default Value: None
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
LIOPTR
ULE
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND
RMV
CELLN
RT
Issue 02 (2015-06-10)

59
eRAN
MO
Parame
ter ID
MML
Comma
nd
7 Parameters
Feature
ID
Feature
Name
Description
None
None
Meaning: Indicates the name of the cell.
STR
CELLR
FLOOP
BACK
STR
CELLS
ELFTES
T
STR
LRTWP
RTTST
STR
PRIBBP
ADJUS
T
UBL
CELL
DSP
LRTWP
RTTST
DSP
PRIBBP
RESINF
O
Cell
CellNa
me
ADD
CELL
MOD
CELL
LST
CELL
Issue 02 (2015-06-10)

Unit: None
Default Value: None

60
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
CsgInd
ADD
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
LBFD-0
0201803
/
TDLBF
D-00201
803
Cell
Selectio
n and
Reselection
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.
MOD
CELL
LST
CELL
GUI Value Range: BOOLEAN_FALSE(False),

BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)
Cell
UlCycli
cPrefix
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
0100401
/
TDLBF
D-00100
401
LOFD-0
01031 /
TDLOF
D-00103
1
LBFD-0
02009 /
TDLBF
D-00200
9
Issue 02 (2015-06-10)
Normal
CP
Extende
d CP
Broadca
st of
system
informat
ion
Meaning: Indicates the UL cyclic prefix length of a

cell. A cyclic prefix can be a common or extended
cyclic prefix. An extended cyclic prefix is generally
used in a complex environment with a strong multipath 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
BBP. For details, see 3GPP TS 36.211.
GUI Value Range: NORMAL_CP(Normal),
EXTENDED_CP(Extended)
Unit: None
Actual Value Range: NORMAL_CP,
EXTENDED_CP
Default Value: NORMAL_CP(Normal)

61
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
DlCycli
cPrefix
ADD
CELL
LBFD-0
0100401
/
TDLBF
D-00100
401
Normal
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 BBP. For details, see 3GPP TS 36.211.
MOD
CELL
LST
CELL
Extende
d CP
LOFD-0
01031 /
TDLOF
D-00103
1
GUI Value Range: NORMAL_CP(Normal),

EXTENDED_CP(Extended)
Unit: None
Actual Value Range: NORMAL_CP,
EXTENDED_CP
Default Value: NORMAL_CP(Normal)
Cell
FreqBan
d
ADD
CELL
ADD
CELLB
AND
LST
CELLB
AND
MOD
CELL
RMV
CELLB
AND
LST
CELL
Cell
UlEarfc
nCfgInd
ADD
CELL
MOD
CELL
LST
CELL
Issue 02 (2015-06-10)
LBFD-0
0201803
/
TDLBF
D-00201
803
LBFD-0
02009 /
TDLBF
D-00200
9
LBFD-0
70103 /
TDLBF
D-00201
806
LBFD-0
0201803
/
TDLBF
D-00201
803
LBFD-0
02009 /
TDLBF
D-00200
9
Cell
Selectio
n and
Reselection
Broadca
st of
system
informat
ion
Meaning: Indicates the frequency band in which the

cell operates. For details about this parameter, see
3GPP TS 36.104.
Unit: None
Default Value: None
MultiBand
Compati
bility
Enhance
ment
Cell
Selectio
n and
Reselection
Broadca
st of
system
informat
ion
Meaning: Indicates whether to configure the uplink

EARFCN of the cell.
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

62
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
UlEarfc
n
ADD
CELL
LBFD-0
0201801
/
TDLBF
D-00201
801
Coverag
e Based
Intrafrequenc
y
Handov
er
Meaning: Indicates the UL EARFCN of the cell. It is

optional, depending on the setting of the UL EARFCN
configuration indicator (UlEarfcnCfgInd). If the value
of this parameter is not specified, the default UL
EARFCN is used, which is calculated based on the
DL EARFCN. For details, see 3GPP TS 36.104.
Cell
Selectio
n and
Reselection
Unit: None
MOD
CELL
LST
CELL
Cell
DlEarfc
n
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
0201803
/
TDLBF
D-00201
803

LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
Meaning: Indicates the DL EARFCN of the cell. For

details, see the 3GPP TS 36.104.
LBFD-0
0201801
/
TDLBF
D-00201
801
Coverag
e Based
Intrafrequenc
y
Handov
er
LBFD-0
0201803
/
TDLBF
D-00201
803
Issue 02 (2015-06-10)
GUI Value Range: 18000~46589,54436~65535
GUI Value Range: 0~46589,54436~65535

Unit: None
Default Value: None
Cell
Selectio
n and
Reselection

63
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
UlBand
Width
ADD
CELL
LOFD-0
01051
MOD
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
Compac
t
Bandwi
dth
Meaning: Indicates the UL 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, see 3GPP TS 36.104.
LST
CELL
TDLBF
D-00100
3
Broadca
st of
system
informat
ion
Scalable
Bandwi
dth
GUI Value Range: CELL_BW_N6(1.4M),

CELL_BW_N15(3M), CELL_BW_N25(5M),
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
DlBand
Width
ADD
CELL
LOFD-0
01051
MOD
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
LST
CELL
TDLBF
D-00100
3
Compac
t
Bandwi
dth
Broadca
st of
system
informat
ion
Scalable
Bandwi
dth
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, see 3GPP TS 36.104.
GUI Value Range: CELL_BW_N6(1.4M),
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
CellId
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
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
Issue 02 (2015-06-10)

64
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
PhyCellI
d
ADD
CELL
LOFD-0
01051
Meaning: Indicates the physical cell ID. For details,

see 3GPP TS 36.331.
MOD
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
Compac
t
Bandwi
dth
LST
CELL
Cell
Addition
alSpectr
umEmis
sion
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
Broadca
st of
system
informat
ion

Unit: None
Default Value: None
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.
Unit: None
Default Value: 1
Issue 02 (2015-06-10)

65
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
FddTddI
nd
ADD
CELL
LBFD-0
02009
MOD
CELL
TDLBF
D-00100
7
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.
Basic
uplinkdownlin
k
subfram
e
configur
ation
Unit: None
LST
CELL
TDLBF
D-00100
701
TDLBF
D-00100
702
TDLOF
D-00102
6
TDLOF
D-00102
601
TDLOF
D-00102
602
TDLOF
D-00102
603
GUI Value Range: CELL_FDD(FDD),

CELL_TDD(TDD)
Actual Value Range: CELL_FDD, CELL_TDD
Default Value: None
uplinkdownlin
k
subfram
e
configur
ation
type1&2
uplinkdownlin
k special
subfram
e
configur
ation
type 7
Optional
uplinkdownlin
k
subfram
e
configur
ation
uplinkdownlin
k
subfram
e
configur
ation
type 0
uplinkdownlin
Issue 02 (2015-06-10)

66
eRAN
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
7 Parameters
Feature
Name
Description
k special
subfram
e
configur
ation
type 4
uplinkdownlin
k special
subfram
e
configur
ation
type 5
Issue 02 (2015-06-10)

67
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
CellSpe
cificOffs
et
ADD
CELL
LBFD-0
0201801
/
TDLBF
D-00201
801
Coverag
e Based
Intrafrequenc
y
Handov
er
Meaning: Indicates the cell specific offset for the

serving cell. It affects the probability of triggering
handovers from the serving cell to its neighboring
cells. A smaller value of this parameter leads to a
higher probability. For details, see 3GPP TS 36.331.
MOD
CELL
LST
CELL
TDLBF
D-00201
8
TDLBF
D-00201
802
TDLBF
D-00201
804
TDLBF
D-00201
805
TDLOF
D-00101
9
TDLOF
D-00104
3
TDLOF
D-00107
2
TDLOF
D-00102
0
TDLOF
D-00104
6
TDLOF
D-00107
3
Mobility
Manage
ment
Coverag
e Based
Interfrequenc
y
Handov
er
Distance
Based
Interfrequenc
y
Handov
er
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),
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)
Service
Based
Interfrequenc
y
Handov
er
PS InterRAT
Mobility
between
EUTRAN
and
UTRAN
Service
based
InterRAT
handove
r to
UTRAN
Issue 02 (2015-06-10)

68
eRAN
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
7 Parameters
Feature
Name
Description
Distance
based
InterRAT
handove
r to
UTRAN
PS InterRAT
Mobility
between
EUTRAN
and
GERAN
Service
based
InterRAT
handove
r to
GERAN
Distance
based
InterRAT
handove
r to
GERAN
Issue 02 (2015-06-10)

69
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
QoffsetF
req
ADD
CELL
LBFD-0
0201801
MOD
CELL
LBFD-0
0201803
LST
CELL
TDLBF
D-00201
8
Coverag
e Based
Intrafrequenc
y
Handov
er
Meaning: Indicates the specific frequency offset of the

serving cell. This parameter is contained in the
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.
TDLBF
D-00201
802
TDLBF
D-00201
804
TDLBF
D-00201
805
TDLOF
D-00101
9
TDLOF
D-00104
3
TDLOF
D-00107
2
TDLOF
D-00102
0
TDLOF
D-00104
6
TDLOF
D-00107
3
Cell
Selectio
n and
Reselection
Mobility
Manage
ment
Coverag
e Based
Interfrequenc
y
Handov
er
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),
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)
Distance
Based
Interfrequenc
y
Handov
er
Service
Based
Interfrequenc
y
Handov
er
PS InterRAT
Mobility
between
EUTRAN
and
UTRAN
Service
based
Inter-
Issue 02 (2015-06-10)

70
eRAN
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
7 Parameters
Feature
Name
Description
RAT
handove
r to
UTRAN
Distance
based
InterRAT
handove
r to
UTRAN
PS InterRAT
Mobility
between
EUTRAN
and
GERAN
Service
based
InterRAT
handove
r to
GERAN
Distance
based
InterRAT
handove
r to
GERAN
Cell
RootSeq
uenceId
x
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
02010 /
TDLBF
D-00201
0
Random
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
Issue 02 (2015-06-10)

71
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
Preambl
eFmt
ADD
CELL
LBFD-0
02010 /
TDLBF
D-00201
0
Random
Access
Procedu
re
Meaning: Indicates the preamble format used in the

cell. For details, see 3GPP TS 36.211.
MOD
CELL
LST
CELL
Cell
CellRadi
us
ADD
CELL
MOD
CELL
LST
CELL
Cell
Customi
zedBand
WidthCf
gInd
ADD
CELL

Unit: None
Default Value: 0
LBFD-0
02010 /
TDLBF
D-00201
0
LBFD-0
02010 /
TDLBF
D-00201
0/
LOFD-0
81223
LOFD-0
01051
MOD
CELL
Random
Access
Procedu
re
Random
Access
Procedu
re /
Extende
d Cell
Access
Radius
beyond
100km
Compac
t
Bandwi
dth
LST
CELL
Meaning: Indicates the radius of the cell, that is, the

farthest distance that a cell can cover under the
condition of keeping certain network performance. If
this parameter is set to a value greater than 100 km,
the Extended Cell Access Radius Beyond 100km
feature takes effect. Only FDD cells can be configured
with a radius more than 100 km.
Unit: m
Meaning: Indicates whether to configure a customized

bandwidth for a cell. A customized bandwidth can be
configured only when a standard bandwidth 1.4 MHz,
5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured.
CFG(Configure)
Unit: None
Cell
Customi
zedULB
andWidt
h
ADD
CELL
MOD
CELL
LST
CELL
LOFD-0
01051
Compac
t
Bandwi
dth
Meaning: Indicates a customized uplink bandwidth

configured for a cell. A customized bandwidth can be
configured.
GUI Value Range:
12~14,44~50,89~100,139~150,183~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Default Value: 98
Issue 02 (2015-06-10)

72
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
Customi
zedDLB
andWidt
h
ADD
CELL
LOFD-0
01051
Compac
t
Bandwi
dth
Meaning: Indicates a customized downlink bandwidth

configured for a cell. A customized bandwidth can be
configured.
MOD
CELL
LST
CELL
GUI Value Range:

12~14,44~50,89~100,139~150,183~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Default Value: 98
Cell
UePowe
rMaxCf
gInd
ADD
CELL
MOD
CELL
LST
CELL
Cell
UePowe
rMax
ADD
CELL
MOD
CELL
LST
CELL
LBFD-0
02026 /
TDLBF
D-00202
6
LBFD-0
02009 /
TDLBF
D-00200
9
LBFD-0
02026 /
TDLBF
D-00202
6
LBFD-0
02009 /
TDLBF
D-00200
9
Uplink
Power
Control
Broadca
st of
system
informat
ion
Meaning: Indicates whether to configure the

maximum TX power of the UE in the cell. If the value
of this parameter is not specified, the maximum power
is subject to the UE capability.
CFG(Configure)
Unit: None
Uplink
Power
Control
Broadca
st of
system
informat
ion
Meaning: Indicates the maximum transmit power that

a UE can apply to uplink transmission in the cell. It is
used in cell selection criterion S to calculate the
compensated power. If the value of this parameter is
not specified, the maximum power is subject to the
UE capability. For details, see 3GPP TS 36.304.
GUI Value Range: -30~36
Unit: dBm
Actual Value Range: -30~36
Default Value: 23
Issue 02 (2015-06-10)

73
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
MultiRr
uCellFla
g
ADD
CELL
LOFD-0
03029 /
TDLOF
D-00107
5
SFN
Meaning: Indicates whether to enable or disable the

multi-RRU cell feature.
MOD
CELL
LST
CELL
TDLOF
D-00200
8
TDLOF
D-00109
8
TDLOF
D-00108
0
TDLOF
D-00108
1
TDLOF
D-00108
2
Cell
MultiRr
uCellMo
de
ADD
CELL
MOD
CELL
LST
CELL
LOFD-0
03029 /
TDLOF
D-00107
5
LOFD-0
70205 /
TDLOF
D-00200
8
TDLOF
D-00109
8
TDLOF
D-00108
0
TDLOF
D-00108
1
TDLOF
D-00108
2
Issue 02 (2015-06-10)
Adaptiv
e SFN/
SDMA

BOOLEAN_TRUE(True)
InterBBP
SFN
Unit: None
InterBBU
SFN

BOOLEAN_TRUE
InterBBP
Adaptiv
e SFN/
SDMA
InterBBU
Adaptiv
e SFN/
SDMA
SFN
Meaning: Indicates the type of the multi-RRU cell.
Adaptiv
e SFN/
SDMA
GUI Value Range: SFN(SFN),

CELL_COMBINATION(Cell Combination),
TWO_RRU_COMBINATION(TWO RRU
Combination), DIGITAL_COMBINATION(Cell
Digital Combination),
MPRU_AGGREGATION(MPRU_AGGREGATION)
InterBBP
SFN
InterBBU
SFN
InterBBP
Adaptiv
e SFN/
SDMA
Unit: None
Actual Value Range: SFN, CELL_COMBINATION,
TWO_RRU_COMBINATION,
DIGITAL_COMBINATION,
MPRU_AGGREGATION
Default Value: SFN(SFN)
InterBBU
Adaptiv
e SFN/
SDMA

74
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
AirCellF
lag
ADD
CELL
None
None
Meaning: Indicates whether the cell is an air cell.

BOOLEAN_TRUE(True)
MOD
CELL
Unit: None
LST
CELL

BOOLEAN_TRUE
Cell
TxRxM
ode
ADD
CELL
None
None
Meaning: Indicates the transmission and reception

mode of the cell.
MOD
CELL
GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,

8T8R, 2T8R, 4T8R
LST
CELL
Unit: None
Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
4T4R, 8T8R, 2T8R, 4T8R
Default Value: None
Cell
UserLab
el
ADD
CELL
MOD
CELL
LST
CELL
Issue 02 (2015-06-10)
None
None
Meaning: Indicates the user label of the cell.

Unit: None
Default Value: None

75
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
WorkM
ode
ADD
CELL
LAOFD
-001001
01
IntraBand
Carrier
Aggrega
tion for
Downlin
k 2CC
Meaning: Indicates the work mode of the cell. The

DL_ONLY mode applies only to the carrier
aggregation scenario.
InterBand
Carrier
Aggrega
tion for
Downlin
k 2CC
Actual Value Range: UL_DL, DL_ONLY
MOD
CELL
LST
CELL
LAOFD
-001001
02
LAOFD
-001002
01
LAOFD
-001002
02
TDLAO
FD-001
003
TDLAO
FD-001
002
GUI Value Range: UL_DL(Uplink and downlink),

DL_ONLY(Downlink only)
Unit: None
Default Value: UL_DL(Uplink and downlink)
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Issue 02 (2015-06-10)

76
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
Cell
CellSlav
eBand
ADD
CELLB
AND
LBFD-0
70103 /
TDLBF
D-00201
806
MultiBand
Compati
bility
Enhance
ment
Meaning: Indicates slave frequency bands of a cell. If

the operating frequency of a cell belongs to multiple
frequency bands, the frequency band with the highest
priority is configured by the FreqBand parameter, and
frequency bands with other priorities are configured
by the CellSlaveBand parameter and added in
descending order based on frequency band priorities.
The frequency band priorities of a cell are determined
in network planning. It is recommended that the
frequency bands supporting UEs that comply with
3GPP TS 36.331 V8.16.0, 3GPP TS 36.331 V9.1.0,
3GPP TS 36.331 V10.5.0, or a later vision be
configured as slave frequency bands.
LST
CELLB
AND
RMV
CELLB
AND

Unit: None
Default Value: None
eUCellS
ectorEq
m
LocalCe
llId
ADD
EUCEL
LSECT
OREQ
M
LST
EUCEL
LSECT
OREQ
M
None
None
Meaning: Indicates the local cell identity. It uniquely

identifies a cell within an eNodeB.
Unit: None
Default Value: None
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
DSP
EURTW
P
Issue 02 (2015-06-10)

77
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
eUCellS
ectorEq
m
SectorE
qmId
ADD
EUCEL
LSECT
OREQ
M
None
None
Meaning: Indicates the ID of the sector device that

serves the cell,it uniquely identifies a sector device
within an eNodeB.
Unit: None
DSP
EURTW
P

Default Value: None
LST
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
eUCellS
ectorEq
m
BaseBan
dEqmId
ADD
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
LST
EUCEL
LSECT
OREQ
M
None
None
Meaning:
Indicates the ID of the baseband equipment serving a
cell.
When this parameter is set to 255, the baseband
equipment serving a cell is not specified. In this
scenario, the LTE baseband processing units (LBBPs)
serving a cell are selected among all LBBPs in the
eNodeB, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.
When this parameter is set to a value other than 255,
the cell is served by LBBPs in the specified baseband
equipment, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.
GUI Value Range: 0~23,255
Unit: None
Actual Value Range: 0~23,255
Default Value: 255
Issue 02 (2015-06-10)

78
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CellOp
LocalCe
llId
ADD
CELLO
P
None
None
Meaning: Indicates the local ID of the cell. It uniquely

identifies a cell within a base station.
DSP
CELLB
ROADC
ASTCN
OPERA
TOR
Unit: None
Default Value: None
LST
CELLO
P
MOD
CELLO
P
RMV
CELLO
P
CellOp
Trackin
gAreaId
ADD
CELLO
P
LST
CELLO
P
MOD
CELLO
P
RMV
CELLO
P
Issue 02 (2015-06-10)
LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
LBFD-0
0201803
/
TDLBF
D-00201
803
Cell
Selectio
n and
Reselection
Meaning: Indicates the local tracking area identity of

the cell, which uniquely identifies an operator's record
of tracking area information within a cell. This
parameter is used only in the eNodeB and is different
from the tracking area identity configured in the
tracking area list on the MME.
Unit: None
Default Value: None

79
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CellOp
CellRes
ervedFo
rOp
ADD
CELLO
P
LBFD-0
02009 /
TDLBF
D-00200
9
Broadca
st of
system
informat
ion
Meaning:
MOD
CELLO
P
LST
CELLO
P
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.
If this parameter is set to
CELL_NOT_RESERVED_FOR_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_FOR_OP(Reserved),
CELL_NOT_RESERVED_FOR_OP(Not Reserved)
Unit: None
Actual Value Range: CELL_RESERVED_FOR_OP,
CELL_NOT_RESERVED_FOR_OP
Default Value:
CELL_NOT_RESERVED_FOR_OP(Not Reserved)
CellOp
OpUlRb
UsedRat
io
ADD
CELLO
P
MOD
CELLO
P
LST
CELLO
P
LOFD-0
01036 /
TDLOF
D-00103
6
LBFD-0
02009 /
TDLBF
D-00200
9
LOFD-0
70206
RAN
Sharing
with
Commo
n
Carrier
Broadca
st of
system
informat
ion
Hybrid
RAN
Sharing
Meaning: Indicates the percentage of resource blocks

(RBs) occupied by the operator on the physical uplink
shared channel (PUSCH) when radio access network
(RAN) sharing is enabled on the eNodeB and the celllevel RAN sharing switch 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 the percentage
of RBs occupied by operators on the PUSCH. This
parameter takes effect only in RAN sharing with
common carriers mode or in hybrid RAN sharing
mode with more than one CellOp MO being
configured.
Unit: %
Default Value: 16
Issue 02 (2015-06-10)

80
eRAN
7 Parameters
MO
Parame
ter ID
MML
Comma
nd
Feature
ID
Feature
Name
Description
CellOp
OpDlRb
UsedRat
io
ADD
CELLO
P
LOFD-0
01036 /
TDLOF
D-00103
6
RAN
Sharing
with
Commo
n
Carrier
Meaning: Indicates the percentage of resource blocks

(RBs) occupied by the operator on the physical
downlink shared channel (PDSCH) when RAN
sharing is enabled on the eNodeB and the cell-level
RAN sharing switch 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 the percentage of RBs occupied
by operators on the PDSCH. This parameter takes
effect only in RAN sharing with common carriers
mode or in hybrid RAN sharing mode with more than
one CellOp MO being configured.
MOD
CELLO
P
LST
CELLO
P
LBFD-0
02009 /
TDLBF
D-00200
9
LOFD-0
70206
Broadca
st of
system
informat
ion
Hybrid
RAN
Sharing

Unit: %
Default Value: 16
Issue 02 (2015-06-10)

81
eRAN
8 Counters
Counters
There are no specific counters associated with this feature.
Issue 02 (2015-06-10)

82
eRAN
9 Glossary
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 02 (2015-06-10)

83
eRAN
10
10 Reference Documents
Reference Documents
1.
3GPP TS 36.211, " Evolved Universal Terrestrial Radio Access (E-UTRA); Physical
channels and modulation "
2.
3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical

layer procedures"
3.
3GPP TS36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio

Resource Control (RRC) protocol specification"
4.
zh-cn_bookmap_0001792924.htmlFeature Description About Cell Outage Detection and

Recovery
5.
SFN Feature Parameter Description
Issue 02 (2015-06-10)

84

Cell Management (ERAN8.1 02)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cell Management (ERAN8.1 02)

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

Cell Management Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 About This Document

About This Document

3900 series eNodeB

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

Revised baseband equipment descriptions. For

eRAN8.1 Draft A (2015-01-15)

Added the description of Band 28 and Band

Added the support for 4T8R antenna mode.

Huawei Proprietary and Confidential

1 About This Document

1.4 Differences Between eNodeB Types

Function Implementation in Macro, Micro, and LampSite eNodeBs

Implementation of this function varies based on eNodeB types:

Implementation of this function varies based on eNodeB types:

Implementation of this function varies based on eNodeB types:

l Macro and micro eNodeBs support this function.

l Macro eNodeBs support this function.

l Macro eNodeBs support this function.

Huawei Proprietary and Confidential

1 About This Document

Multi-sector cells include single-frequency-network (SFN) cells, pico RRU

Bandwidths supported by eNodeBs vary with eNodeB types.

l Macro eNodeBs support SFN cells, pRRU aggregation cells, 2-RRU

Transmission and reception modes supported by eNodeBs vary with eNodeB

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

3.1 Related Concepts

Huawei Proprietary and Confidential

Figure 3-1 Cell-related concepts

Huawei Proprietary and Confidential

An omnidirectional sector uses

In low-traffic areas, the

Directional sectors use

In high-traffic areas, the

3.1.3 Sector Equipment

Huawei Proprietary and Confidential

3.1.5 Baseband Equipment

3.1.6 Cell-specific Sector Equipment

3.2 Typical Scenarios

Establishing a common cell

Establishing cells in multiple sectors with RRU/RFU splitting

Establishing a cell in a single sector with RRU/RFU combination

Establishing a cell in multiple sectors served by different RRUs/RFUs

Establishing a cell in a sector with RRU/RFU channel cross-connection under MIMO

3.2.1 Establishing a Cell in a Common Sector

Huawei Proprietary and Confidential

Figure 3-2 A cell established in a common sector

3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU