Cell Management Feature Parameter Description: Eran TDD

eRAN TDD
Cell Management Feature Parameter

Description
Issue 04
Date 2015-10-30
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 04 (2015-10-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN TDD
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............................................................................................................................................................... 2
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
3 Technical Description...................................................................................................................5
3.1 Related Concepts............................................................................................................................................................ 5
3.1.1 Cell...............................................................................................................................................................................6
3.1.2 Sector........................................................................................................................................................................... 7
3.1.3 Sector Equipment........................................................................................................................................................ 7
3.1.4 RF Equipment..............................................................................................................................................................7
3.1.5 Baseband Equipment................................................................................................................................................... 8
3.1.6 Cell-specific Sector Equipment................................................................................................................................... 8
3.2 Typical Scenarios............................................................................................................................................................8
3.2.1 Establishing a Cell in a Common Sector..................................................................................................................... 8
3.2.2 Establishing Cells in Multiple Sectors with RRU Splitting........................................................................................ 9
3.2.3 Establishing a Cell in a Single Sector with RRU Combination.................................................................................. 9
3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs..........................................................................10
3.2.5 Establishing Multiple Cells in a Multi-Carrier Sector............................................................................................... 11
3.3 Cell-related Parameters.................................................................................................................................................12
3.3.1 Frequency Band......................................................................................................................................................... 12
3.3.2 Cell Bandwidth.......................................................................................................................................................... 13
3.3.3 Maximum Transmit Power of a Cell......................................................................................................................... 13
4 Related Features...........................................................................................................................18
5 Network Impact........................................................................................................................... 20
6 Engineering Guidelines............................................................................................................. 21
6.1 When to Use Cell Management....................................................................................................................................21
6.2 Required Information................................................................................................................................................... 21
6.3 Planning........................................................................................................................................................................ 21
Issue 04 (2015-10-30) Huawei Proprietary and Confidential ii

eRAN TDD
Cell Management Feature Parameter Description Contents
6.4 Deployment.................................................................................................................................................................. 21
6.4.1 Process....................................................................................................................................................................... 22
6.4.2 Requirements............................................................................................................................................................. 22
6.4.2.1 License....................................................................................................................................................................22
6.4.2.2 Hardware................................................................................................................................................................ 23
6.4.3 Data Preparation........................................................................................................................................................ 24
6.4.4 Precautions.................................................................................................................................................................34
6.4.5 Activation.................................................................................................................................................................. 36
6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................36
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 39
6.4.5.3 Using the CME to Perform Single Configuration.................................................................................................. 40
6.4.5.4 Using MML Commands......................................................................................................................................... 40
6.4.5.5 MML Command Examples.................................................................................................................................... 43
6.4.6 Activation Observation..............................................................................................................................................48
6.4.7 Reconfiguration......................................................................................................................................................... 48
6.4.8 Deactivation...............................................................................................................................................................48
6.5 Performance Monitoring...............................................................................................................................................49
6.6 Parameter Optimization................................................................................................................................................ 49
6.7 Troubleshooting............................................................................................................................................................ 49
7 Parameters..................................................................................................................................... 51
8 Counters........................................................................................................................................ 84
9 Glossary......................................................................................................................................... 85
10 Reference Documents............................................................................................................... 86
Issue 04 (2015-10-30) Huawei Proprietary and Confidential iii

eRAN TDD
Cell Management Feature Parameter Description 1 About This Document
1 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 the following features:
l TDLBFD-001003 Scalable Bandwidth
– TDLBFD-00100301 5MHz Bandwidth
– TDLBFD-00100302 10/20MHz Bandwidth
– TDLBFD-00100303 15MHz Bandwidth
l TDLBFD-002035 Multi Carrier
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 TDD. Any "LTE" in this document refers to LTE TDD,
and "eNodeB" refers to LTE TDD eNodeB.
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
LampSite DBS3900 LampSite TDD
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
Issue 04 (2015-10-30) Huawei Proprietary and Confidential 1

eRAN TDD
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN TDD 8.1 04 (2015-10-30)

This issue includes the following changes.
Change Type Change Description Parameter

Change
Feature change Added descriptions of the newly added pRRU3911, None

which is introduced in this version. For details, see
6.4.3 Data Preparation.
Added precautions for the configuration of an 8T8R None

cell and other cells on the same BBP. For details, see
6.4.4 Precautions.
Editorial None None

change
eRAN TDD 8.1 03 (2015-06-10)

Change Type Change Description Parameter

Change
Feature change None None
Editorial Optimized descriptions of baseband equipment. For None

change details, see 3.1.5 Baseband Equipment.
eRAN TDD 8.1 02 (2015-04-20)


eRAN TDD
Change Change Description Paramete Affected

Type r Change Entity
Feature Updated 6.4.4 Precautions. None Macro

change and
LampSite
eNodeBs
Editorial None None N/A

change
eRAN TDD 8.1 01 (2015-03-20)

This issue does not include any changes.
eRAN TDD 8.1 Draft A (2015-01-15)

Compared with Issue 01 (2014-09-30) of eRAN TDD 8.0, Draft A (2015-01-30) of eRAN
TDD 8.1 does not include any changes.

eRAN TDD
Cell Management Feature Parameter Description 2 Overview
2 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.

eRAN TDD
Cell Management Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 Related Concepts

Figure 3-1 shows the concepts related to cell management.

eRAN TDD
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.

eRAN TDD
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 Definition Benefits Applicati

Type on
Scenario
Omnidirec An omnidirectional sector uses In low-traffic areas, the Traffic is

tional an omnidirectional antenna to deployment of low.
sector provide 360 degrees of coverage omnidirectional sectors
from the center of a circular reduces the cost of antenna
area. equipment.
Directiona Directional sectors use In high-traffic areas, the Traffic is

l sector directional antennas for deployment of directional high.
coverage. Each directional sectors supports high traffic
antenna covers a sector area of volumes. In addition,
60 or 120 degrees when six or directional sectors support
three antennas, respectively, are more flexible area
configured on an eNodeB. When planning.
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.
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, pRRUs, and AAUs.
An RRU is added by running the ADD RRU and ADD RRUCHAIN commands.

eRAN TDD
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.
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
l Establishing cells in multiple sectors with RRU splitting
l Establishing a cell in a single sector with RRU combination
l Establishing a cell in multiple sectors served by different RRUs/RFUs
l Establishing multiple cells in a multi-carrier sector
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, as shown in the
following figure.
Figure 3-2 A cell established in a common sector

eRAN TDD
3.2.2 Establishing Cells in Multiple Sectors with RRU Splitting

An RRU can be logically split to establish multiple sectors when the RRU processing
capability does not match the antenna transmission and reception capability. The following
figure provides an example of this scenario.
Figure 3-3 RRU/RFU splitting for multiple sectors (using a 4T4R RRU as an example)
3.2.3 Establishing a Cell in a Single Sector with RRU

Combination
In RRU combination scenarios, RRUs working on the same frequency jointly provide a sector
to achieve greater RF capacity if the RRU processing capability does not match the antenna
transmission and reception capability.
Only RRUs working in 1T1R or 2T2R mode can be combined.
Micro eNodeBs do not support RRU combination.

eRAN TDD
Figure 3-4 RRU combination for a single sector (using a 2T2R RRU as an example)
3.2.4 Establishing a Cell in Multiple Sectors Served by Different

RRUs
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.
Multi-sector cells include SFN cells, and pRRU aggregation cells. Table 3-1 describes
different types of multi-sector cells.
Figure 3-5 Establishing a Cell in Multiple Sectors Served by Different RRUs

eRAN TDD
Table 3-1 Multi-sector cell types

Multi-sector Description Affected
Cell Type Entity
SFN cell Multiple RRUs/RFUs are combined to serve an SFN cell, Macro
where all the RRUs/RFUs use the same physical cell eNodeBs
identifier (PCI) and cell ID. This expands the cell center
area and reduces interference at the cell edge.
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 A pRRU aggregation cell is the smallest service area for Macro
aggregation cell providing indoor coverage in the LampSite solution. eNodeBs
NOTE
l For details about the LampSite solution, see LampSite
Solution Deployment and Reconfiguration Guide.
l For details about how to deploy pRRU aggregation cells, see
Reconfiguration Guide.
3.2.5 Establishing Multiple Cells in a Multi-Carrier Sector

In multi-carrier networking, cells working on different bands are set up in a sector, as shown
in Figure 3-6. Multi-carrier networking expands network capacity without deploying new
eNodeBs.
Figure 3-6 Establishing multiple cells in a multi-carrier sector
The multi-carrier technology applies to densely populated areas where traffic increases
rapidly, such as exhibition centers, waiting halls, shopping malls, central business districts,
and superior residential buildings.
In multi-carrier scenarios, macro eNodeBs support sectors working on a maximum of four
carriers.
Before establishing multiple cells in a multi-carrier sector, ensure that the concerned RRUs/
RFUs, CPRI ports, and baseband processing units have the required multi-carrier capabilities.
For details about how to reconfigure a single-carrier sector to a dual-carrier sector, see 6.4.2
Requirements. For details about how to reconfigure a single-carrier sector to a dual-carrier
sector, see 6.4.7 Reconfiguration or Reconfiguration Guide.

eRAN TDD
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 uplink-downlink subframe configuration, CPRI

compression, cycling prefix, preamble format, and cell radius, see Subframe Configuration
Feature Parameter Description, 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.7 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). The uplink
and downlink of a cell use the same frequency band.
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
Frequency Band Frequency Range (Lowest and Highest Supported by

(FreqBand) Frequencies) Huawei RRUs
33 1900 MHz 1920 MHz Yes
34 2010 MHz 2025 MHz No
35 1850 MHz 1910 MHz No
36 1930 MHz 1990 MHz No
37 1910 MHz 1930 MHz No
38 2570 MHz 2620 MHz Yes
39 1880 MHz 1920 MHz Yes
40 2300 MHz 2400 MHz Yes
41 2496 MHz 2690 MHz Yes
42 3400 MHz 3600 MHz Yes
43 3600 MHz 3800 MHz Yes
44 703 MHz 803 MHz Yes

eRAN TDD
3.3.2 Cell Bandwidth

This section describes the basic feature TDLBFD-001003 Scalable Bandwidth.
A cell in a macro eNodeB can be configured with different standardized bandwidths: 5 MHz,
10 MHz, 15 MHz, or 20 MHz. Micro eNodeBs support the cell bandwidths of 10 MHz and 20
MHz.
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
that provides the cell coverage.
NOTE
l If multiple cells are served by the same RRU, the sum of Pmax_out values of these cells must be less
than or equal to the maximum transmit power of the RRU.
l For details about the maximum transmit power of RRUs 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

eRAN TDD
NOTE
The value of the ReferenceSignalPwr parameter is determined by either of the following parameters:
l EuCellSectorEqm.ReferenceSignalPwr (EuSectorEqmGroup.ReferenceSignalPwr for
LampSite eNodeBs)
l PDSCHCfg.ReferenceSignalPwr
The value of the first parameter prevails if both the parameters are configured.
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.
l 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 Reference signal (RS) power of the physical downlink shared channel
nalPwr (PDSCH).
For details, see Pmax_out Configuration Parameters.

eRAN TDD
Variable Description
PowerFactor Power factor ratio of the energy per resource element (EPRE) on the
Ratio 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
PDSCHCfg.PB ρB/ρA (One ρB/ρA (Two or Four Antenna Ports)
Antenna Port)
0 1 5/4
1 4/5 1
2 3/5 3/4
3 2/5 1/2

eRAN TDD
Table 3-6 Mapping between cell bandwidths and the maximum number of available RBs
Cell Bandwidth 1.4 3 5 10 15 20
(MHz)
Maximum 6 15 25 50 75 100
Number of
Available RBs
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
l 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

eRAN TDD
The value of the ReferenceSignalPwr parameter cannot be greater than 18.24 dBm.

eRAN TDD
Cell Management Feature Parameter Description 4 Related Features
4 Related Features
TDLBFD-001003 Scalable Bandwidth

l Prerequisite features
None
l Mutually exclusive features
In macro eNodeBs, if the bandwidth of eNodeB is 5 MHz, the following features cannot
work:
– TDLOFD-001049 Single Streaming Beamforming
– TDLOFD-001061 Dual Streaming Beamforming
– TDLOFD-001077 MU-Beamforming
– TDLOFD-001007 High Speed Mobility
– TDLOFD-001075 SFN
– TDLOFD-002008 Adaptive SFN/SDMA
– TDLOFD-001098 Inter-BBP SFN
– TDLOFD-001080 Inter-BBU SFN
– TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
– TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
– TDLOFD-001005 UL 4-Antenna Receive Diversity
– TDLOFD-001062 UL 8-Antenna Receive Diversity
– TDLOFD-001031 Extended CP
– TDLOFD-001036 RAN Sharing with Common Carrier
– TDLOFD-001037 RAN Sharing with Dedicated Carrier
– TDLOFD-001066 Intra-eNodeB UL CoMP
– TDLOFD-001039 RF Channel Intelligent Shutdown
l Impacted features
None
TDLBFD-002035 Multi Carrier

l Prerequisite features
None

eRAN TDD
Cell Management Feature Parameter Description 4 Related Features
l Mutually exclusive features

None
l Impacted features
None

eRAN TDD
Cell Management Feature Parameter Description 5 Network Impact
5 Network Impact
TDLBFD-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.
l 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).
TDLBFD-002035 Multi Carrier

l System capacity
Multi-carrier improves the uplink and downlink system capacity, which theoretically
reaches two times of the original one.
l Network performance
No impact.

eRAN TDD
Cell Management Feature Parameter Description 6 Engineering Guidelines
6 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

eRAN TDD
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
6.4.2.1 License
The following table lists the license control items related to cell establishment. Operators
must purchase and activate the following licenses.
License Control Item Model NE Sales Unit
RF Output Power (TDD) LT1ST000PA00 eNodeB per 20W
Carrier Bandwidth - 0~5MHz(TDD) LT1ST05MHZ00 eNodeB per cell
eNodeB TDD Basic Software, V100R008 LT1STBASIC07 eNodeB per cell

(TDD)

eRAN TDD
RF Transmit Channel(TDD) LT1S0TRFTC00 eNodeB per Channel
RF Receive Channel(TDD) LT1S0TRFRC00 eNodeB per Channel
BB Transmit Channel(TDD) LT1S0TBBTC00 eNodeB per Channel
BB Receive Channel(per Channel)(TDD) LT1S0TBBRC00 eNodeB per Channel
RRC Connected User(TDD) LT1STACTUS00 eNodeB per RRC

Connected
User
Throughput Capacity(TDD) LT1STTHROU00 eNodeB per Mbps
Resource Block(TDD) LT1S000TRB00 eNodeB per RB
The following license control item is required for multi-carrier networking.
Multi Carrier(TDD) LT1ST00MCA00 eNodeB per Carrier
NOTE
Number of multi-carrier licenses required for an RF module = Number of carriers on the RF module -
Number of sectors on the RF module
If the RF module supports only one carrier, multi-carrier licenses are not required. For details, see
License Management Feature Parameter Description.
6.4.2.2 Hardware
The cell status is related to physical resources such as baseband resources, RF resources, and
CPRI resources. When the physical resources are insufficient, a cell cannot be successfully
established due to physical resource unavailability.
Before establishing a cell, ensure the following physical resources meet requirements:
l Cell Capability Supported by BBPs
l Cell Capability Supported by CPRI Ports
l Cell Capability Supported by RF Modules
Cell Capability Supported by BBPs

The number of cells supported by a BBP varies with the model of the BBP. For details, see
Product Specifications > Technical Specifications of the BBU > Baseband Specifications
in 3900 Series Base Station Technical Description.
Cell Capability Supported by CPRI Ports

The number of carriers supported by a single CPRI port depends on the CPRI port rate, carrier
bandwidth, number of RF channels, and whether CPRI compression or CPRI extension is

eRAN TDD
used. For details, see Product Specifications > Technical Specifications of the BBU >
CPRI Specifications in 3900 Series Base Station Technical Description.
NOTE
The CPRI compression function must be enabled and the CPRIEX parameter must be set to ON(On) by
running the MOD BBP command if both of the following conditions are met:
l The LBBPd is used.
l More than 10 20 Mbit/s channels (for example, in the scenario of two 20 Mbit/s 8T8R carriers) or
more than 16 10 Mbit/s channels are established over a single CPRI port.
In this case, only CPRI ports 0, 1, and 2 can be used.
Cell Capability Supported by RF Modules

Different RF modules support different cell bandwidths. For details, see Product
Specifications in 3900 Series Base Station Technical Description.
6.4.3 Data Preparation

The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.
Parameter Parameter ID Setting Notes Data

Name Source
Sector ID SECTOR.SECT Ensure that each sector number is Network

ORID unique. plan
(negotiation
not
required)
Sector Name SECTOR.SECN N/A Network

AME plan
(negotiation
not
required)
Location Name SECTOR.LOCA N/A Network

TIONNAME plan
(negotiation
not
required)
User Label SECTOR.USER N/A Network

LABEL plan
(negotiation
not
required)
Antenna SECTOR.ANTN N/A Network

Number UM plan
(negotiation
not
required)

eRAN TDD

Name Source
Cabinet No. of SECTOR.ANT1 N/A Network

Antenna 1 to CN to plan
Cabinet No. of SECTOR.ANT8 (negotiation
Antenna 8 CN not
required)
Subrack No. of SECTOR.ANT1 N/A Network

Antenna 1 to SRN to plan
Subrack No. of SECTOR.ANT8 (negotiation
Antenna 8 SRN not
required)
Slot No. of SECTOR.ANT1 For a LampSite eNodeB, Network

Antenna 1 to SN to l If the pRRU3901 is used, set this plan
Slot No. of SECTOR.ANT8 parameter to 255 to enable (negotiation
Antenna 8 SN automatic allocation of the slot not
number to an antenna. If the slot required)
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 SECTOR.ANT1 N/A Network

Antenna 1 to N to plan
Channel No. of SECTOR.ANT8 (negotiation
Antenna 8 N not
required)
Create Default SECTOR.CREA N/A Network

Sector TESECTOREQ plan
Equipment M (negotiation
not
required)
Default Sector SECTOR.SECT N/A Network

Equipment ID OREQMID 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.

eRAN TDD

Name Source
Sector SECTOREQM.sect N/A Network

equipment ID orEqmId plan
(negotiation
not
required)
Sector ID SECTOREQM.sect N/A Network

orId plan
(negotiation
not
required)
Antenna SECTOREQM.AN N/A Network

Number TNUM plan
(negotiation
not
required)
Cabinet No. of SECTOREQM.AN N/A Network

Antenna 1 to T1CNANT1CN to plan
Cabinet No. of SECTOREQM.AN (negotiation
Antenna 8 T8CN not
required)
Subrack No. SECTOREQM.AN N/A Network

of Antenna 1 T1SRN to plan
to Subrack No. SECTOREQM.AN (negotiation
of Antenna 8 T8SRN not
required)
Slot No. of SECTOREQM.AN For a LampSite eNodeB, Network

Antenna 1 to T1SN to l If the pRRU3901 is used, set plan
Slot No. of SECTOREQM.AN this parameter to 255 to enable (negotiation
Antenna 8 T8SN automatic allocation of the slot not
number to an antenna. If the required)
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.
Channel No. SECTOREQM.AN N/A Network

of Antenna 1 T1N to plan
to Channel SECTOREQM.AN (negotiation
No. of T8N not
Antenna 8 required)

eRAN TDD

Name Source
Antenna 1 SECTOREQM.AN N/A Network

RX/TX Mode TTYPE1 to plan
to Antenna 8 SECTOREQM.AN (negotiation
RX/TX Mode TTYPE8 not
required)
TX Antenna 1 SECTOREQM.TX Set the parameter value to Network

Master/Slave BKPMODE1 to MASTER(Master). plan
mode to TX SECTOREQM.TX This parameter cannot be set to (negotiation
Antenna 8 BKPMODE8 SLAVE(Slave) because the not
Master/Slave eNodeBs do not support antennas required)
mode working in active/standby mode.
The following table describes the parameters that must be set in a CnOperator MO to
configure an operator.
Parameter Parameter ID Setting Notes Data Source

Name
CN Operator CnOperator.Cn N/A Network plan

ID OperatorId (negotiation not
required)
CN Operator CnOperator.Cn N/A Network plan

name OperatorName (negotiation not
required)
CN Operator CnOperator.Cn This parameter specifies the Network plan

type OperatorType operator type: primary or (negotiation not
secondary. Each eNodeB can be required)
configured with only one
primary operator but multiple
secondary operators.
Mobile country CnOperator.Mcc N/A Network plan

code (negotiation not
required)
Mobile CnOperator.Mnc N/A Network plan

network code (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.

eRAN TDD

Name Source
Local tracking CnOperatorTa.Tr This parameter uniquely identifies a Network

area ID ackingAreaId tracking area. This parameter is used plan
only in the eNodeB and is different (negotiatio
from the tracking area identity (TAI) n not
configured in the tracking area list required)
(TAL) on the MME.
CN Operator CnOperatorTa.C N/A Network

ID nOperatorId plan
(negotiatio
n not
required)
Tracking area CnOperatorTa.Ta N/A Network

code c plan
(negotiatio
n not
required)
The following table describes the parameters that must be set in a Cell MO to configure a cell.

Name
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 Network plan
BOOLEAN_FALSE(FALSE). (negotiation
not required)
Uplink cyclic Cell.UlCyclicPr Retain the default value Network plan

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

cyclic prefix efix NORMAL_CP(Normal). (negotiation
length not required)
Frequency Cell.FreqBand N/A Network plan

band (negotiation
not required)

eRAN TDD

Name
Uplink earfcn Cell.UlEarfcnCf N/A Network plan

indication gInd (negotiation
not required)
Uplink earfcn Cell.UlEarfcn This parameter is optional, depending Network plan

on the value of the (negotiation
Cell.UlEarfcnCfgInd parameter. 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 Cell.DlEarfcn The downlink frequency identified by Network plan

EARFCN the EARFCN must be located in the (negotiation
band specified by the Cell.FreqBand not required)
parameter.
When establishing two cells in a
common sector without RRU/RFU
combination, the EARFCN range of
the two cells do not overlap.
Uplink Cell.UlBandWid N/A Network plan

bandwidth th (negotiation
not required)
Downlink Cell.DlBandWid N/A Network plan

bandwidth th (negotiation
not required)
Cell ID Cell.CellId N/A Network plan

(negotiation
not required)
Physical cell Cell.PhyCellId N/A Network plan

ID (negotiation
not required)
Additional Cell.AdditionalS N/A Network plan

spectrum pectrumEmissio (negotiation
emission n not required)
Cell FDD Cell.FddTddInd Set this parameter to Network plan

TDD CELL_TDD(TDD). (negotiation
indication not required)
Cell specific Cell.CellSpecific Set this parameter to 0. Network plan

offset Offset (negotiation
not required)

eRAN TDD

Name
Frequency Cell.QoffsetFre Set this parameter to 0. Network plan

offset q (negotiation
not required)
Root Cell.RootSeque For details about setting constraints, Network plan

sequence nceIdx see the MO reference for the eNodeB. (negotiation
index not required)
Preamble Cell.PreambleF N/A Network plan

format mt (negotiation
not required)
Cell radius Cell.CellRadius The value of this parameter must be Network plan
equal to or greater than the actual cell (negotiation
radius. Otherwise, UEs at the cell not required)
edge may fail to access the network.
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.
Customized Cell.Customized N/A Network plan

bandwidth BandWidthCfgI (negotiation
configure nd not required)
indicator
Customized Cell.Customized This parameter is required only when Network plan

uplink ULBandWidth the Cell.CustomizedBandWidthCf- (negotiation
bandwidth gInd parameter is set to not required)
CFG(Configure).
Customized Cell.Customized This parameter is required only when Network plan

downlink DLBandWidth the Cell.CustomizedBandWidthCf- (negotiation
bandwidth gInd parameter is set to not required)
CFG(Configure).
Ue max Cell.UePowerM N/A Network plan

power axCfgInd (negotiation
allowed not required)
configure
indicator
Max transmit Cell.UePowerM This parameter is required only when Network plan
power ax the Cell.UePowerMaxCfgInd (negotiation
allowed parameter is set to CFG(Configure). not required)
Flag of Multi- Cell.MultiRruC Set this parameter to Network plan

RRU Cell ellFlag CFG(Configure) while configuring (negotiation
multi-RRU cells. not required)

eRAN TDD

Name
Mode of Cell.MultiRruC This parameter is required only when Network plan

Multi-RRU ellMode the Cell.MultiRruCellFlag parameter (negotiation
Cell is set to CFG(Configure). not required)
Air Cell Flag Cell.AirCellFlag N/A Network plan

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

transmission the SECTOREQM.antNum (negotiation
and reception parameter in the Sector MO. not required)
mode
User Label Cell.UserLabel N/A Network plan

(negotiation
not required)
Work mode Cell.WorkMode N/A Network plan

(negotiation
not required)
Cell Slave Cell.CellSlaveB Set this parameter by running the Network plan
Band and ADD CELLBAND command. (negotiation
not required)
Cell Standby Cell.EuCellStan N/A Radio

Mode dbyMode 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.

Name
Local Cell ID EUCELLSECT N/A Network plan

OREQM.LocalC (negotiation
ellId not required)
Sector EUCELLSECT N/A Network plan

equipment ID OREQM.sectorE (negotiation
qmId not required)

eRAN TDD

Name
Reference EUCELLSECT If this parameter is set to 32767, it Network plan

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

equipment ID OREQM.BaseBa baseband equipment is specified (negotiation
ndEqmId for the cell. In this case, the cell not required)
can use any baseband equipment
of the eNodeB.
Sector CPRI EUCELLSECT This parameter specifies the CPRI Default/

Compression OREQM.SectorC compression mode of each piece recommende
priCompression of sector equipment. It is used d value:
only when the Mode of Multi-
RRU 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.
Auto Config EUCELLSECT N/A Radio

Flag OREQM.AutoCf planning
gFlag (Internal
planning)
The following table describes the parameters that must be set in a CellOp MO to configure a
cell operator.

Name
Local Cell ID CellOp.LocalCell N/A Network plan

Id (negotiation not
required)

eRAN TDD

Name
Local tracking CellOp.Tracking N/A Network plan

area ID AreaId (negotiation not
required)
Cell reserved CellOp.CellReser N/A Network plan

for operator vedForOp (negotiation not
required)
Operator uplink CellOp.OpUlRbU N/A Network plan

RB used ratio sedRatio (negotiation not
required)
Operator CellOp.OpDlRbU N/A Network plan

downlink RB sedRatio (negotiation not
used ratio required)
The following table describes the parameters that must be set in a BaseBandEqm MO to
configure baseband equipment information.

eRAN TDD

Name
Baseband BaseBandEqm.BASEBA Each BaseBandEqmId Network plan

equipment ID NDEQMID parameter value identifies (negotiation
a piece of baseband not required)
equipment.
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 BaseBandEqm.BASEBA N/A Radio

Equipment NDEQMTYPE planning
Type (Internal
planning)
6.4.4 Precautions
Table 6-1 Precautions
Nu If... Then...
mb
er
1 An LBBPd2 needs to These cells must be bound to the baseband equipment

support six 10 MHz corresponding to the LBBPd2.
common cells

eRAN TDD
Nu If... Then...
mb
er
2 Two cells with the The two cells must be configured on different BBPs.
bandwidths of 10 MHz In addition, the following requirements must be met:
and 20 MHz are
configured on the same l For a common cell, both Layer 1 and Layer 2 can
BBU be bound to a piece of baseband equipment that
contains multiple BBPs.
l For an SFN cell, Layer 1 must be bound to a piece
of baseband equipment containing only one BBP
while Layer 2 can be bound to a piece of baseband
equipment containing multiple BBPs.
3 Not all the cells of an The baseband equipment exclusive switch must be
eNodeB are bound to a turned on by running the following command:
piece of baseband MOD TDDRESMODESW: BbResExclusiveS-
equipment witch=ON;
In this way, cells that are not bound to a piece of
baseband equipment cannot be set up on this baseband
equipment
4 An RRU works in 10 The RRU must be connected to the BBP configured

MHz+20 MHz multi- with the 20 MHz carrier and then to the BBP
carrier scenarios configured with the 10 MHz carrier through the
backplane.
5 Cells under an eNodeB These cells must be bound to different BBPs. The
are configured with subframe configuration types must be the same for all
different subframe the cells configured on the same BBP.
configuration types
6 A cell is established on l When the CCNE parameter in the BBP MO is set

the UBBPd9 to ON(On), 8T8R RRUs can be installed at most 10
km away from the BBU. When the CCNE
parameter in the BBP MO is set to OFF(Off),
8T8R RRUs can be installed at most 20 km away
from the BBU. It is recommended that the CCNE
parameter in the BBP MO be set to OFF(Off).
l If a LampSite cell is established on the UBBPd9,
the CCNE parameter in the BBP MO must be set to
OFF(Off).
l If a 1T1R, 2T2R, or 4T4R cell is established on the
UBBPd9 and the RRU is installed 20 km or farther
away from the BBU, the CCNE parameter in the
BBP MO must be set to OFF(Off).
7 Seven or more sectors are The radius of the cell established on the sector must be
configured on the equal to or less than 9895 m.
UBBPd9.

eRAN TDD
Nu If... Then...
mb
er
8 In multi-carrier scenarios, Signals of other carriers will be interrupted

a carrier is removed from intermittently. Therefore, you are advised to add or
or added to an RRU remove a carrier in off-peak hours.
11 The UBBPd or LBBPd is A 8T8R cell cannot be configured on the same BBP as
used. 1T1R, 2T2R, or 4T4R cells.
12 2T2R and 4T4R cells Bind the 2T2R and 4T4R cells to the UBBPd.
must be set up on the
same UBBPd.
NOTE
l To bind baseband equipment to a cell (Layer 1), run the ADD EUCELLSECTOREQM command.
l To bind primary baseband equipment to a cell (Layer 2), run the ADD EUCELLPRIBBEQM
command.
6.4.5 Activation
6.4.5.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.
l Customizing a summary data file
Enter the values of the parameters listed in Table 6-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data

eRAN TDD
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:
– The MOs in Table 6-2 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-2 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.

eRAN TDD
Table 6-2 Cell management parameters (batch configuration for newly deployed eNodeBs)
MO Sheet in the Parameter Group Remarks
Summary Data
File
CELL LTE Cell *LocalCellID Parameters marked

*CellName with an asterisk (*) are
mandatory. Other
*CellId parameters are optional.
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

eRAN TDD
MO Sheet in the Parameter Group Remarks

Summary Data
File
CellSlaveBand
CnOper Common Data *Operator ID N/A

ator *Operator name
*Operator type
*Mcc
*Mnc
CnOper LTE Cell *TrackingAreaId N/A

atorTA *TAC
*CnOperatorId
CellOp LTE Cell *LocalCellID N/A

*TrackingAreaId
EUCE LTE Cell *LocalCellID N/A

LLSEC Sector equipment ID
TORE
QM Baseband equipment ID
6.4.5.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

eRAN TDD
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.5.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-2, select the eNodeB to which the MOs belong.
Figure 6-2 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.5.4 Using MML Commands

This section describes how to activate the cell management feature using MML commands in
the following scenarios:
l Scenario 1: Establishing a Cell in a Common Sector

eRAN TDD
– Establishing a 20 MHz 2T2R Cell in a Common Sector

l Scenario 2: Establishing a Cell in Multiple Sectors with RRU Splitting
l Scenario 3: Establishing a Cell in a Single Sector with RRU Combination
l Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs
l Scenario 5: Establishing Multiple Cells in a Multi-Carrier Sector
Universal Process to Establish a Cell

To establish a cell, perform the following steps:
Step 1 (Optional) If an RRU is added, add a sector and sector equipment.

1. Run the ADD SECTOR command to add a sector.
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
Scenario 1: Establishing a Cell in a Common Sector

l Establishing a 20 MHz 2T2R cell in a common sector
Perform steps described in Universal Process to Establish a Cell. In addition, pay
attention to the following details:
– When running the ADD SECTOR and ADD SECTOREQM commands to
configure a sector, set the antNum parameter to 2, and then configure the two
antenna channels to this sector.
– When running the ADD CELL command to establish a cell, set the
cell.UlBandWidth and cell.DlBandWidth parameter to CELL_BW_N100(20M).
l Establishing a 20 MHz 4T4R cell in a common sector

eRAN TDD

configure a sector, set the antNum parameter to 4, and then configure the four
cell.UlBandWidth and cell.DlBandWidth parameters to CELL_BW_N100(20M).
l Establishing a 20 MHz 8T8R Cell in a Common Sector
configure a sector, set the antNum parameter to 8, and then configure the eight
l Establishing a 5 MHz 2T2R Cell in a Common Sector
configure a sector, set the antNum parameter to 2, and then configure the two
Scenario 2: Establishing a Cell in Multiple Sectors with RRU Splitting

Establishing two 2T2R cells by splitting a 4T4R RRU is used as an example in this section.
Perform steps described in Universal Process to Establish a Cell. In addition, pay attention
to the following details:
l When running the ADD SECTOR and ADD SECTOREQM commands to configure
sectors, configure two sectors with the antNum parameter set to 2, and then configure
any two antenna channels to one sector and the other two antenna channels to the other
sector.
l When running the ADD EUCELLSECTOREQM command, bind the two cells with
two pieces of sector equipment.
Scenario 3: Establishing a Cell in a Single Sector with RRU Combination

Establishing a 4T4R cell by combining two 2T2R RRUs is used as an example in this section.
Perform steps described in Universal Process to Establish a Cell. 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.
l When running the ADD CELL command to establish a cell, set the
MULTIRRUCELLFLAG parameter to BOOLEAN_TRUE and the
cell.MULTIRRUCELLMODE parameter to SFN.

eRAN TDD
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs

Establishing a 3-sector SFN cell is used as an example in this section. Perform steps described
in Universal Process to Establish a Cell. 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.
l When running the ADD CELL command, establish only one cell with the
MULTIRRUCELLFLAG parameter set to BOOLEAN_TRUE and the
MULTIRRUCELLMODE parameter set to SFN.
l When running the ADD EUCELLSECTOREQM command, bind the three pieces of
sector equipment that have been established to one cell.
Scenario 5: Establishing Multiple Cells in a Multi-Carrier Sector

Establishing two cells in a dual-carrier sector is used as an example in this section. Perform
steps described in Universal Process to Establish a Cell. In addition, pay attention to the
following details:
NOTE
Before establishing multiple cells in a multi-carrier sector, ensure that the multi-carrier capabilities
supported by RRUs and CPRI ports meet the requirements described in 6.4.2 Requirements.
l When running the ADD CELL command, establish two cells with the cell.DlEarfcn
parameter set to different values for the two cells to ensure that the frequency bands do
not overlap.
l When running the ADD EUCELLSECTOREQM command, bind the established sector
equipment to the two cells.
6.4.5.5 MML Command Examples

This section provides the MML command examples in different scenarios.
l Scenario 1: Establishing a Cell in a Common Sector
l Scenario 2: Establishing a Cell in Multiple Sectors with RRU Splitting
l Scenario 3: Establishing a Cell in a Single Sector with RRU Combination
l Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs
l Scenario 5: Establishing Multiple Cells in a Multi-Carrier Sector
NOTE
The parameter settings in the following commands are used for reference only. Set the parameters based
on network requirements.
Scenario 1: Establishing a Cell in a Common Sector

1. Establishing a 20 MHz 2T2R cell in a common sector
//Adding a sector and sector equipment

eRAN TDD
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;
a. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
b. //Adding a tracking area for an operator

ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=1;
//Adding a 20 MHz cell

ADD CELL: LocalCellId=0, CellName="CELL1", FreqBand=38,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=37900, UlBandWidth=CELL_BW_N100,
DlBandWidth=CELL_BW_N100, CellId=0, PhyCellId=0, FddTddInd=CELL_TDD,
SubframeAssignment=SA2, SpecialSubframePatterns=SSP7,
EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, 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;

ADD SECTOR: SECTORID=0, SECNAME="0", LOCATIONNAME="0", USERLABEL="0",
ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60,
ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0C, ANT4CN=0,
ANT4SRN=60, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=0;


ADD CELL:LocalCellId=0, CellName="CELL1", FreqBand=38,
UePowerMaxCfgInd=NOT_CFG, TxRxMode=4T4R


//Activating a cell

ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, ANT5CN=0, ANT5SRN=60,
ANT5SN=0, ANT5N=R0E, ANT6CN=0, ANT6SRN=60, ANT6SN=0, ANT6N=R0F, ANT7CN=0,

eRAN TDD
ANT7SRN=60, ANT7SN=0, ANT7N=R0G, ANT8CN=0, ANT8SRN=60, ANT8SN=0, ANT8N=R0H,

CREATESECTOREQM=TRUE, SECTOREQMID=0;


ADD CELL:LocalCellId=0, CellName="CELL1", FreqBand=38,


//Activating a cell

ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE,
SECTOREQMID=0;


ADD CELL: LocalCellId=0, CellName="CELL1", FreqBand=38,


//Activating a cell
Scenario 2: Establishing a Cell in Multiple Sectors with RRU Splitting

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,

eRAN TDD
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;
//Adding an operator
//Adding a tracking area for an operator

//Adding two cells

ADD CELL: LocalCellId=0, CellName="CELL0", FreqBand=38, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=37900, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=1,
PhyCellId=1, FddTddInd=CELL_TDD, SubframeAssignment=SA2,
SpecialSubframePatterns=SSP7, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
ADD CELL: LocalCellId=1, CellName="CELL1", FreqBand=38, UlEarfcnCfgInd=NOT_CFG,
//Adding two 2T2R sector equipment groups

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

Activating two cells

Scenario 3: Establishing a Cell in a Single Sector with RRU Combination

//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;
1. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile",
2. //Adding a tracking area for an operator

//Adding a cell
ADD CELL: LocalCellId=0, CellName="cell0", FreqBand=38, UlEarfcnCfgInd=NOT_CFG,
HighSpeedFlag=HIGH_SPEED, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE=
SFN, TxRxMode=4T4R;

eRAN TDD
//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

Establishing a cell in 3 sectors is used as an example.
ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;

//Adding a SFN cell

ADD
CELL:LOCALCELLID=0,CELLNAME="0",FREQBAND=38,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=38000,
ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=0,PHYCELLID=0,FDDTDDIND=C
ELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,ROOTSEQUENCEIDX=0,CELL
RADIUS=9895,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWE
RMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE=SFN,TXRXMODE=2T2
R;
//Adding the mapping relationship between a cell and sector equipment


//Activating a cell
Scenario 5: Establishing Multiple Cells in a Multi-Carrier Sector

Establishing two cells in a dual-carrier sector is used as an example.

//Establishing two cells working at different frequencies and ensuring that the frequency
bands do not overlap

eRAN TDD

SpecialSubframePatterns=SSP7, RootSequenceIdx=0,
SpecialSubframePatterns=SSP7, RootSequenceIdx=0,
//Adding an operator for two cells

//Adding sector equipment for cells with the SectorEqmId parameter set to the same value for
each cell
//Activating two cells

6.4.6 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.7 Reconfiguration
For cell-related reconfiguration, see eRAN Reconfiguration Guide.
6.4.8 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.5.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 6-3.
Table 6-3 MO involved in feature deactivation

MO Sheet in the Summary Data Parameter Group
File
Cell LTE Cell Cell

eRAN TDD
Using the CME to Perform Single Configuration

On the CME, change the parameter according to Table 6-3. For detailed instructions, see
"6.4.5.3 Using the CME to Perform Single Configuration" described for feature activation.
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 Cell Outage Detection and Compensation Feature
Parameter Description.
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

eRAN TDD
Alarm ID Alarm Name
ALM-29242 No Traffic Volume in the Cell
----End

eRAN TDD
Cell Management Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
CellDlp PaPcOff MOD LBFD-0 Dynami Meaning: Indicates the PA to be used when PA
cPdschP CELLD 02016 / c adjustment for PDSCH power control is disabled, DL
a LPCPD TDLBF Downlin ICIC is disabled, and the even power distribution is
SCHPA D-00201 k Power used for the PDSCH.
LST 6 Allocati GUI Value Range: DB_6_P_A(-6 dB),
CELLD on DB_4DOT77_P_A(-4.77 dB), DB_3_P_A(-3 dB),
LPCPD DB_1DOT77_P_A(-1.77 dB), DB0_P_A(0 dB),
SCHPA DB1_P_A(1 dB), DB2_P_A(2 dB), DB3_P_A(3 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
Unit: dB
Default Value: DB_3_P_A(-3 dB)
PDSCH Pb MOD LBFD-0 Dynami Meaning: Indicates the scaling factor index of the
Cfg PDSCH 02016 / c Energy Per Resource Element (EPRE) on the PDSCH.
CFG TDLBF Downlin This scaling factor is determined by the value of this
LST D-00201 k Power parameter and the antenna port. For details, see 3GPP
PDSCH 6 Allocati TS 36.213.
CFG LBFD-0 on GUI Value Range: 0~3
02009 / Broadca Actual Value Range: 0~3
TDLBF st of
D-00200 system Unit: None
9 informat Default Value: 1
ion

eRAN TDD

nd
eUCellS Referen ADD None None Meaning: Indicates the reference signal power of the
ectorEq ceSignal EUCEL cell sector device. The value 32767 indicates that this
m Pwr LSECT reference signal power parameter is invalid. In this
OREQ case, the reference signal power of the cell equals the
M value of the PDSCHCFG parameter. For details, see
MOD 3GPP TS 36.213.This parameter is valid only when a
EUCEL multi-RRU cell works in
LSECT SFN,MPRU_AGGREGATION or cell combination
OREQ mode.
M GUI Value Range: -600~500,32767
LST Actual Value Range: -60~50,3276.7
EUCEL Unit: 0.1dBm
LSECT
OREQ Default Value: 32767
M
EuSecto Referen ADD None None Meaning: Indicates the reference signal power of a
rEqmGr ceSignal EUSEC sector equipment group for a cell (all sets of sector
oup Pwr TOREQ equipment in the sector equipment group have the
MGRO same reference signal power). If this parameter is set
UP to 32767, the parameter value is invalid, and the cell
MOD uses the reference signal power specified by the
EUSEC ReferenceSignalPwr parameter in the PDSCHCFG
TOREQ MO. For details, see 3GPP TS 36.213. This parameter
MGRO takes effect only when parameter MultiRruCellFlag is
UP set to BOOLEAN_TRUE and MultiRruCellMode is
set to MPRU_AGGREGATION or FDD SFN,
LST respectively.
EUSEC
TOREQ GUI Value Range: -600~500,32767
MGRO Actual Value Range: -60~50,3276.7
UP Unit: 0.1dBm
Default Value: 32767
PDSCH Referen MOD LBFD-0 Dynami Meaning: Indicates the cell reference signal power of
Cfg ceSignal PDSCH 02016 / c each physical antenna. However, the cell reference
Pwr CFG TDLBF Downlin signal power delivered in SIB2 is that of each logical
LST D-00201 k Power antenna.
PDSCH 6 Allocati GUI Value Range: -600~500
CFG LBFD-0 on
Actual Value Range: -60~50
02009 / Broadca
TDLBF st of Unit: 0.1dBm
D-00200 system Default Value: 182
9 informat
ion

eRAN TDD

nd
SECTO SECTO ADD None None Meaning: Indicates the number of the sector.
R RID SECTO GUI Value Range: 0~65535
R
Actual Value Range: 0~65535
DSP
SECTO Unit: None
R Default Value: None
LST
SECTO
R
MOD
SECTO
R
RMV
SECTO
R
SECTO SECNA ADD None None Meaning: Indicates the name of the sector.
R ME SECTO GUI Value Range: 0~99 characters
R
Actual Value Range: 0~99 characters
MOD
SECTO Unit: None
R Default Value: NULL(empty string)
LST
SECTO
R
SECTO LOCATI ADD None None Meaning: Indicates the location name of the base
R ONNA SECTO station.
ME R GUI Value Range: 0~64 characters
MOD Actual Value Range: 0~64 characters
SECTO
R Unit: None
LST Default Value: NULL(empty string)

SECTO
R
SECTO USERL ADD None None Meaning: Indicates the user-defined information of a
R ABEL SECTO sector. The value of this parameter consists of xx::yy
R and common character strings, which are separated by
MOD percentage signs (%), for example, %tel::
SECTO 88888888%owner::huawei%20130101. xx::yy
R indicates that the value of xx is yy.
LST GUI Value Range: 0~255 characters
SECTO Actual Value Range: 0~255 characters
R Unit: None
Default Value: NULL(empty string)

eRAN TDD

nd
SECTO SECTO ADD None None Meaning: Indicates the number of the sector
REQM REQMI SECTO equipment.
D REQM GUI Value Range: 0~65535
LST Actual Value Range: 0~65535
SECTO
REQM Unit: None
MOD Default Value: None

SECTO
REQM
RMV
SECTO
REQM
LST
SECTO
R
SECTO SECTO ADD None None Meaning: Indicates the number of the sector in which
REQM RID SECTO the sector equipment is located.
REQM GUI Value Range: 0~65535
SECTO
REQM Unit: None
Default Value: None

eRAN TDD

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator.
ator atorId CNOPE 01036 Sharing GUI Value Range: 0~5
RATOR LOFD-0 with
Commo Actual Value Range: 0~5
LST 01037
CNOPE n Unit: None
LOFD-0 Carrier
RATOR 01086 Default Value: None
MOD RAN
TDLOF Sharing
CNOPE D-00111
RATOR with
2 Dedicate
RMV LOFD-0 d
CNOPE 70206 Carrier
RATOR
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing

eRAN TDD

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the name of the operator.
ator atorNam CNOPE 01036 / Sharing GUI Value Range: 1~32 characters
e RATOR TDLOF with
D-00103 Commo Actual Value Range: 1~32 characters
MOD
CNOPE 6 n Unit: None
RATOR LOFD-0 Carrier Default Value: None
LST 01037 / RAN
CNOPE TDLOF Sharing
RATOR D-00103 with
7 Dedicate
LOFD-0 d
01086 / Carrier
TDLOF RAN
D-00108 Sharing
6 by More
TDLOF Operator
D-00111 s
2 MOCN
LOFD-0 Flexible
70206 Priority
Based
Campin
g
Hybrid
RAN
Sharing

eRAN TDD

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the type of the operator. The
ator atorType CNOPE 01036 / Sharing operator can be the primary operator or a secondary
RATOR TDLOF with operator. For each eNodeB, only one primary operator
MOD D-00103 Commo but more than one secondary operator can be
CNOPE 6 n configured.
RATOR LOFD-0 Carrier GUI Value Range:
LST 01037 / RAN CNOPERATOR_PRIMARY(Primary Operator),
CNOPE TDLOF Sharing CNOPERATOR_SECONDARY(Secondary Operator)
RATOR D-00103 with Actual Value Range: CNOPERATOR_PRIMARY,
7 Dedicate CNOPERATOR_SECONDARY
LOFD-0 d
Carrier Unit: None
01086 /
TDLOF RAN Default Value: None
D-00108 Sharing
6 by More
TDLOF Operator
D-00111 s
2 MOCN
LOFD-0 Flexible
70206 Priority
Based
Campin
g
Hybrid
RAN
Sharing

eRAN TDD

nd
CnOper Mcc ADD LOFD-0 RAN Meaning: Indicates the mobile country code (MCC) of
ator CNOPE 01036 / Sharing the operator.
RATOR TDLOF with GUI Value Range: 3 characters
MOD D-00103 Commo
6 n Actual Value Range: 000~999
CNOPE
RATOR LOFD-0 Carrier Unit: None
LST 01037 / RAN Default Value: None

CNOPE TDLOF Sharing
RATOR D-00103 with
7 Dedicate
LOFD-0 d
01086 / Carrier
TDLOF RAN
D-00108 Sharing
6 by More
TDLOF Operator
D-00111 s
2 MOCN
LOFD-0 Flexible
70206 Priority
Based
Campin
g
Hybrid
RAN
Sharing

eRAN TDD

nd
CnOper Mnc ADD LOFD-0 RAN Meaning: Indicates the mobile network code (MNC)
ator CNOPE 01036 / Sharing of the operator. The value of this parameter is a string
RATOR TDLOF with of two or three characters, each of which must be a
MOD D-00103 Commo digit in the range from 0 to 9.
CNOPE 6 n GUI Value Range: 2~3 characters
RATOR LOFD-0 Carrier
Actual Value Range: 00~99,000~999
LST 01037 / RAN
TDLOF Sharing Unit: None
CNOPE
RATOR D-00103 with Default Value: None
7 Dedicate
LOFD-0 d
01086 / Carrier
TDLOF RAN
D-00108 Sharing
6 by More
TDLOF Operator
D-00111 s
2 MOCN
LOFD-0 Flexible
70206 Priority
Based
Campin
g
Hybrid
RAN
Sharing
CnOper Trackin ADD LOFD-0 RAN Meaning: Indicates the tracking area ID, which
atorTa gAreaId CNOPE 01036 / Sharing uniquely identifies an entry of tracking area
RATOR TDLOF with information. This parameter is used only within the
TA D-00103 Commo eNodeB and is not used during the information
LST 6 n exchange with the EPC. This is different from the TAI
CNOPE LOFD-0 Carrier configured in the EPC TAL.
RATOR 01037 / RAN GUI Value Range: 0~65535
TA TDLOF Sharing Actual Value Range: 0~65535
MOD D-00103 with
7 Dedicate Unit: None
CNOPE
RATOR LOFD-0 d Default Value: None
TA 70206 Carrier
RMV Hybrid
CNOPE RAN
RATOR Sharing
TA

eRAN TDD

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator.
atorTa atorId CNOPE 01036 / Sharing GUI Value Range: 0~5
RATOR TDLOF with
TA D-00103 Commo Actual Value Range: 0~5
MOD 6 n Unit: None

CNOPE LOFD-0 Carrier Default Value: None
RATOR 01037 / RAN
TA TDLOF Sharing
LST D-00103 with
CNOPE 7 Dedicate
RATOR LOFD-0 d
TA 70206 Carrier
Hybrid
RAN
Sharing
CnOper Tac ADD LOFD-0 RAN Meaning: Indicates the tracking area code (TAC),
atorTa CNOPE 01036 / Sharing which is used by the EPC to determine the area within
RATOR TDLOF with which paging messages are sent. One tracking area is
TA D-00103 Commo comprised of one or more cells. Two TAC values
MOD 6 n 0x0000(0) and 0xFFFE(65534) are reserved according
CNOPE LOFD-0 Carrier to the protocol and will not be used in future versions.
RATOR 01037 / RAN Therefore, do not use 0 or 65534 as a TAC value in
TA TDLOF Sharing TAC planning or configuration.
LST D-00103 with GUI Value Range: 0~65535
CNOPE 7 Dedicate Actual Value Range: 0~65535
RATOR LOFD-0 d
Carrier Unit: None
TA 70206
Hybrid Default Value: None
RAN
Sharing

eRAN TDD

nd
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Actual Value Range: 0~255
ADD Unit: None
CELLB
AND 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

eRAN TDD

nd
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 ADD None None Meaning: Indicates the name of the cell.
me CELL GUI Value Range: 1~99 characters
MOD
Actual Value Range: 1~99 characters
CELL
Unit: None
LST
CELL Default Value: None

eRAN TDD

nd
Cell CsgInd ADD LBFD-0 Broadca Meaning: Indicates whether the cell is a closed
CELL 02009 / st of subscriber group (CSG) cell. A CSG cell has
MOD TDLBF system restrictions on UE access. It broadcasts a specific CSG
CELL D-00200 informat ID in the SIB and only those UEs of the group can
9 ion access the CSG cell. BOOLEAN_FALSE indicates
LST that the cell is not a CSG cell, and BOOLEAN_TRUE
CELL LBFD-0 Cell
0201803 Selectio indicates that the cell is a CSG cell. Currently, Huawei
/ n and eNodeBs do not support CSG cells.
TDLBF Re- GUI Value Range: BOOLEAN_FALSE(False),
D-00201 selection BOOLEAN_TRUE(True)
803 Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Unit: None
Default Value: BOOLEAN_FALSE(False)
Cell UlCycli ADD LBFD-0 Normal Meaning: Indicates the UL cyclic prefix length of a
cPrefix CELL 0100401 CP cell. A cyclic prefix can be a common or extended
MOD / Extende cyclic prefix. An extended cyclic prefix is generally
CELL TDLBF d CP used in a complex environment with a strong multi-
D-00100 path effect and long delay. In a cell, the UL cyclic
LST 401 Broadca prefix length can be different from the DL one. In
CELL st of addition, the UL or DL cyclic prefix length of a cell
LOFD-0 system
01031 / must be the same as that of the cell using the same
informat BBP. For details, see 3GPP TS 36.211.
TDLOF ion
D-00103 GUI Value Range: NORMAL_CP(Normal),
1 EXTENDED_CP(Extended)
LBFD-0 Actual Value Range: NORMAL_CP,
02009 / EXTENDED_CP
TDLBF
Unit: None
D-00200
9 Default Value: NORMAL_CP(Normal)

eRAN TDD

nd
Cell DlCycli ADD LBFD-0 Normal Meaning: Indicates the length of the DL cyclic prefix
cPrefix CELL 0100401 CP of a cell. A DL cyclic prefix can be a common or
MOD / Extende extended cyclic prefix. An extended cyclic prefix is
CELL TDLBF d CP generally used in a complex environment with a
D-00100 strong multi-path effect and long delay. In a cell, the
LST 401 UL cyclic prefix length can be different from the DL
CELL one. In addition, the UL or DL cyclic prefix length of
LOFD-0
01031 / a cell must be the same as that of the cell using the
TDLOF same BBP. For details, see 3GPP TS 36.211.
D-00103 GUI Value Range: NORMAL_CP(Normal),
1 EXTENDED_CP(Extended)
Actual Value Range: NORMAL_CP,
EXTENDED_CP
Unit: None
Default Value: NORMAL_CP(Normal)
Cell FreqBan ADD LBFD-0 Cell Meaning: Indicates the frequency band in which the
d CELL 0201803 Selectio cell operates. For details about this parameter, see
ADD / n and 3GPP TS 36.104.
CELLB TDLBF Re- GUI Value Range: 1~64
AND D-00201 selection
803 Actual Value Range: 1~64
LST Broadca
LBFD-0 st of Unit: None
CELLB
AND 02009 / system Default Value: None
TDLBF informat
MOD D-00200 ion
CELL 9 Multi-
RMV LBFD-0 Band
CELLB 70103 / Compati
AND TDLBF bility
LST D-00201 Enhance
CELL 806 ment
Cell UlEarfc ADD LBFD-0 Cell Meaning: Indicates whether to configure the uplink
nCfgInd CELL 0201803 Selectio EARFCN of the cell.
MOD / n and GUI Value Range: NOT_CFG(Not configure),
CELL TDLBF Re- CFG(Configure)
D-00201 selection
LST 803 Actual Value Range: NOT_CFG, CFG
CELL Broadca
LBFD-0 st of Unit: None
02009 / system Default Value: NOT_CFG(Not configure)
TDLBF informat
D-00200 ion
9

eRAN TDD

nd
Cell UlEarfc ADD LBFD-0 Coverag Meaning: Indicates the UL EARFCN of the cell. It is
n CELL 0201801 e Based optional, depending on the setting of the UL EARFCN
MOD / Intra- configuration indicator (UlEarfcnCfgInd). If the value
CELL TDLBF frequenc of this parameter is not specified, the default UL
D-00201 y EARFCN is used, which is calculated based on the
LST 801 Handov DL EARFCN. For details, see 3GPP TS 36.104.
CELL er
LBFD-0 GUI Value Range: 18000~46589,54436~65535
0201803 Cell Actual Value Range: 18000~46589,54436~65535
/ Selectio
TDLBF n and Unit: None
D-00201 Re- Default Value: 18000
803 selection
LBFD-0 Broadca
02009 / st of
TDLBF system
D-00200 informat
9 ion
Cell DlEarfc ADD LBFD-0 Broadca Meaning: Indicates the DL EARFCN of the cell. For
n CELL 02009 / st of details, see the 3GPP TS 36.104.
MOD TDLBF system GUI Value Range: 0~46589,54436~65535
CELL D-00200 informat
9 ion Actual Value Range: 0~46589,54436~65535
LST Unit: None
CELL LBFD-0 Coverag
0201801 e Based Default Value: None
/ Intra-
TDLBF frequenc
D-00201 y
801 Handov
LBFD-0 er
0201803 Cell
/ Selectio
TDLBF n and
D-00201 Re-
803 selection

eRAN TDD

nd
Cell UlBand ADD LOFD-0 Compac Meaning: Indicates the UL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009 / dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
LST between the parameter value and the actual cell
CELL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
informat deduced similarly. For details, see 3GPP TS 36.104.
TDLBF
D-00100 ion GUI Value Range: CELL_BW_N6(1.4M),
3 Scalable CELL_BW_N15(3M), CELL_BW_N25(5M),
Bandwi CELL_BW_N50(10M), CELL_BW_N75(15M),
dth CELL_BW_N100(20M)
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Unit: None
Default Value: None
Cell DlBand ADD LOFD-0 Compac Meaning: Indicates the DL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009 / dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
LST between the parameter value and the actual cell
CELL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
informat deduced similarly. For details, see 3GPP TS 36.104.
TDLBF
D-00100 ion GUI Value Range: CELL_BW_N6(1.4M),
3 Scalable CELL_BW_N15(3M), CELL_BW_N25(5M),
Bandwi CELL_BW_N50(10M), CELL_BW_N75(15M),
dth CELL_BW_N100(20M)
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Unit: None
Default Value: None
Cell CellId ADD LBFD-0 Broadca Meaning: Indicates the ID of the E-UTRAN cell. The
CELL 02009 / st of combination of this parameter and the eNodeB ID
MOD TDLBF system forms the E-UTRAN cell identity. The combination of
CELL D-00200 informat the E-UTRAN cell identity and the PLMN identity
9 ion forms the ECGI. For details, see 3GPP TS 36.413.
LST
CELL GUI Value Range: 0~255
Unit: None
Default Value: None

eRAN TDD

nd
Cell PhyCellI ADD LOFD-0 Compac Meaning: Indicates the physical cell ID. For details,
d CELL 01051 t see 3GPP TS 36.331.
MOD LBFD-0 Bandwi GUI Value Range: 0~503
CELL 02009 / dth
LST TDLBF Broadca
D-00200 st of Unit: None
CELL
9 system Default Value: None
informat
ion
Cell Addition ADD LBFD-0 Broadca Meaning: Indicates the additional spectrum emission,
alSpectr CELL 02009 / st of which restricts the emission power of the UEs in the
umEmis MOD TDLBF system cell. For details, see the 3GPP TS 36.101.
sion CELL D-00200 informat GUI Value Range: 1~32
9 ion
CELL Unit: None
Default Value: 1

eRAN TDD

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

eRAN TDD

nd
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5

eRAN TDD

nd
Cell CellSpe ADD LBFD-0 Coverag Meaning: Indicates the cell specific offset for the
cificOffs CELL 0201801 e Based serving cell. It affects the probability of triggering
et MOD / Intra- handovers from the serving cell to its neighboring
CELL TDLBF frequenc cells. A smaller value of this parameter leads to a
D-00201 y higher probability. For details, see 3GPP TS 36.331.
LST 801 Handov
CELL GUI Value Range: dB-24(-24dB), dB-22(-22dB),
TDLBF er dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
D-00201 Mobility dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
8 Manage dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
TDLBF ment dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
D-00201 Coverag dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
802 e Based dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
Inter- dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
TDLBF dB20(20dB), dB22(22dB), dB24(24dB)
D-00201 frequenc
804 y Actual Value Range: dB-24, dB-22, dB-20, dB-18,
Handov dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
TDLBF er dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,
D-00201 dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20,
805 Distance
Based dB22, dB24
TDLOF Inter- Unit: dB
D-00101 frequenc
9 Default Value: dB0(0dB)
y
TDLOF Handov
D-00104 er
3 Service
TDLOF Based
D-00107 Inter-
2 frequenc
TDLOF y
D-00102 Handov
0 er
TDLOF PS Inter-
D-00104 RAT
6 Mobility
between
TDLOF E-
D-00107 UTRAN
3 and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN

eRAN TDD

nd
Distance
based
Inter-
RAT
handove
r to
UTRAN
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
GERAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN

eRAN TDD

nd
Cell QoffsetF ADD LBFD-0 Coverag Meaning: Indicates the specific frequency offset of the
req CELL 0201801 e Based serving cell. This parameter is contained in the
MOD LBFD-0 Intra- measurement control information and is related to the
CELL 0201803 frequenc handover difficulty between the serving cell and the
y neighboring cell. For details, see 3GPP TS 36.331.
LST TDLBF Handov
CELL D-00201 GUI Value Range: dB-24(-24dB), dB-22(-22dB),
er dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
8
Cell dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
TDLBF Selectio dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
D-00201 n and dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
802 Re- dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
TDLBF selection dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
D-00201 Mobility dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
804 Manage dB20(20dB), dB22(22dB), dB24(24dB)
TDLBF ment Actual Value Range: dB-24, dB-22, dB-20, dB-18,
D-00201 Coverag dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
805 e Based dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,
TDLOF Inter- dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20,
D-00101 frequenc dB22, dB24
9 y Unit: dB
TDLOF Handov
Default Value: dB0(0dB)
D-00104 er
3 Distance
Based
TDLOF
Inter-
D-00107
frequenc
2
y
TDLOF Handov
D-00102 er
0
Service
TDLOF Based
D-00104 Inter-
6 frequenc
TDLOF y
D-00107 Handov
3 er
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
UTRAN
Service
based
Inter-

eRAN TDD

nd
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
GERAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN
Cell RootSeq ADD LBFD-0 Random Meaning: Indicates the first logical root sequence,
uenceId CELL 02010 / Access which is used to generate the preamble sequence.
x MOD TDLBF Procedu Each logical root sequence corresponds to a physical
CELL D-00201 re root sequence. For the mapping between logical root
0 sequences and physical root sequences, see 3GPP TS
LST 36.211.
CELL
GUI Value Range: 0~837
Unit: None
Default Value: None

eRAN TDD

nd
Cell Preambl ADD LBFD-0 Random Meaning: Indicates the preamble format used in the
eFmt CELL 02010 / Access cell. For details, see 3GPP TS 36.211.
MOD TDLBF Procedu GUI Value Range: 0~4
CELL D-00201 re
0 Actual Value Range: 0~4
LST Unit: None
CELL
Default Value: 0
Cell CellRadi ADD LBFD-0 Random Meaning: Indicates the radius of the cell, that is, the
us CELL 02010 / Access farthest distance that a cell can cover under the
MOD TDLBF Procedu condition of keeping certain network performance. If
CELL D-00201 re this parameter is set to a value greater than 100 km,
0 Random the Extended Cell Access Radius Beyond 100km
LST feature takes effect. Only FDD cells can be configured
CELL LBFD-0 Access
02010 / Procedu with a radius more than 100 km.
TDLBF re / GUI Value Range: 1~160000
D-00201 Extende Actual Value Range: 1~160000
0/ d Cell
LOFD-0 Access Unit: m
81223 Radius Default Value: 10000
beyond
100km
Cell Customi ADD LOFD-0 Compac Meaning: Indicates whether to configure a customized
zedBand CELL 01051 t bandwidth for a cell. A customized bandwidth can be
WidthCf MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
gInd CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured.
LST
CELL GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Actual Value Range: NOT_CFG, CFG
Unit: None
Default Value: NOT_CFG(Not configure)
Cell Customi ADD LOFD-0 Compac Meaning: Indicates a customized uplink bandwidth
zedULB CELL 01051 t configured for a cell. A customized bandwidth can be
andWidt MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
h CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured.
LST
CELL GUI Value Range:
12~14,44~50,89~100,139~150,183~200
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Unit: 0.1MHz
Default Value: 98

eRAN TDD

nd
Cell Customi ADD LOFD-0 Compac Meaning: Indicates a customized downlink bandwidth
zedDLB CELL 01051 t configured for a cell. A customized bandwidth can be
andWidt MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
h CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured.
LST
CELL GUI Value Range:
12~14,44~50,89~100,139~150,183~200
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Unit: 0.1MHz
Default Value: 98
Cell UePowe ADD LBFD-0 Uplink Meaning: Indicates whether to configure the
rMaxCf CELL 02026 / Power maximum TX power of the UE in the cell. If the value
gInd MOD TDLBF Control of this parameter is not specified, the maximum power
CELL D-00202 Broadca is subject to the UE capability.
6 st of GUI Value Range: NOT_CFG(Not configure),
LST
CELL LBFD-0 system CFG(Configure)
02009 / informat Actual Value Range: NOT_CFG, CFG
TDLBF ion
D-00200 Unit: None
9 Default Value: NOT_CFG(Not configure)
Cell UePowe ADD LBFD-0 Uplink Meaning: Indicates the maximum transmit power that
rMax CELL 02026 / Power a UE can apply to uplink transmission in the cell. It is
MOD TDLBF Control used in cell selection criterion S to calculate the
CELL D-00202 Broadca compensated power. If the value of this parameter is
6 st of not specified, the maximum power is subject to the
LST UE capability. For details, see 3GPP TS 36.304.
CELL LBFD-0 system
02009 / informat GUI Value Range: -30~36
TDLBF ion Actual Value Range: -30~36
D-00200
9 Unit: dBm
Default Value: 23

eRAN TDD

nd
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates whether to enable or disable the
uCellFla CELL 03029 / Adaptiv multi-RRU cell feature.
g MOD TDLOF e SFN/ GUI Value Range: BOOLEAN_FALSE(False),
CELL D-00107 SDMA BOOLEAN_TRUE(True)
5
LST Inter- Actual Value Range: BOOLEAN_FALSE,
CELL TDLOF BBP BOOLEAN_TRUE
D-00200 SFN
8 Unit: None
Inter- Default Value: BOOLEAN_FALSE(False)
TDLOF BBU
D-00109 SFN
8
Inter-
TDLOF BBP
D-00108 Adaptiv
0 e SFN/
TDLOF SDMA
D-00108 Inter-
1 BBU
TDLOF Adaptiv
D-00108 e SFN/
2 SDMA
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates the type of the multi-RRU cell.
uCellMo CELL 03029 / Adaptiv GUI Value Range: SFN(SFN),
de MOD TDLOF e SFN/ CELL_COMBINATION(Cell Combination),
CELL D-00107 SDMA TWO_RRU_COMBINATION(TWO RRU
5 Combination), DIGITAL_COMBINATION(Cell
LST Inter-
CELL LOFD-0 BBP Digital Combination),
70205 / SFN MPRU_AGGREGATION(MPRU_AGGREGATION)
TDLOF Actual Value Range: SFN, CELL_COMBINATION,
D-00200 Inter-
BBU TWO_RRU_COMBINATION,
8 DIGITAL_COMBINATION,
SFN
TDLOF MPRU_AGGREGATION
D-00109 Inter-
BBP Unit: None
8
Adaptiv Default Value: SFN(SFN)
TDLOF e SFN/
D-00108 SDMA
0
Inter-
TDLOF BBU
D-00108 Adaptiv
1 e SFN/
TDLOF SDMA
D-00108
2

eRAN TDD

nd
Cell AirCellF ADD None None Meaning: Indicates whether the cell is an air cell.
lag CELL GUI Value Range: BOOLEAN_FALSE(False),
MOD BOOLEAN_TRUE(True)
CELL Actual Value Range: BOOLEAN_FALSE,
LST BOOLEAN_TRUE
CELL Unit: None
Default Value: BOOLEAN_FALSE(False)
Cell CrsPort ADD LOFD-0 DL 2x2 Meaning: Indicates the number of ports for
Num CELL 01001 / MIMO transmitting cell-specific reference signal (CRS). As
MOD TDLOF DL 4x2 defined in 3GPP specifications, this parameter can be
CELL D-00100 MIMO set to CRS_PORT_1, CRS_PORT_2, or
1 CRS_PORT_4. The value CRS_PORT_1 indicates
LST DL 4x4 that one CRS port (port 0) is configured. The value
CELL LOFD-0 MIMO
01003 / CRS_PORT_2 indicates that two CRS ports (ports 0
TDLOF and 1) are configured. The value CRS_PORT_4
D-00100 indicates that four CRS ports (ports 0, 1, 2, and 3) are
3 configured.
LOFD-0 GUI Value Range: CRS_PORT_1(1 port),
01060 / CRS_PORT_2(2 ports), CRS_PORT_4(4 ports)
TDLOF Actual Value Range: CRS_PORT_1, CRS_PORT_2,
D-00106 CRS_PORT_4
0 Unit: None
Default Value: CRS_PORT_2(2 ports)
Cell TxRxM ADD None None Meaning: Indicates the transmission and reception
ode CELL mode of the cell.
MOD GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
CELL 8T8R, 2T8R, 4T8R
LST Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
CELL 4T4R, 8T8R, 2T8R, 4T8R
Unit: None
Default Value: None
Cell UserLab ADD None None Meaning: Indicates the user label of the cell.
el CELL GUI Value Range: 0~256 characters
MOD
CELL
Unit: None
LST
CELL Default Value: None

eRAN TDD

nd
Cell WorkM ADD LAOFD Intra- Meaning: Indicates the work mode of the cell. The
ode CELL -001001 Band DL_ONLY mode applies only to the carrier
MOD 01 Carrier aggregation scenario.
CELL LAOFD Aggrega GUI Value Range: UL_DL(Uplink and downlink),
-001001 tion for DL_ONLY(Downlink only)
LST Downlin
CELL 02 Actual Value Range: UL_DL, DL_ONLY
k 2CC
LAOFD Unit: None
-001002 Inter-
01 Band Default Value: UL_DL(Uplink and downlink)
Carrier
LAOFD Aggrega
-001002 tion for
02 Downlin
TDLAO k 2CC
FD-001 Carrier
003 Aggrega
TDLAO tion for
FD-001 Downlin
002 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

eRAN TDD

nd
Cell CellSlav ADD LBFD-0 Multi- Meaning: Indicates slave frequency bands of a cell. If
eBand CELLB 70103 / Band the operating frequency of a cell belongs to multiple
AND TDLBF Compati frequency bands, the frequency band with the highest
LST D-00201 bility priority is configured by the FreqBand parameter, and
CELLB 806 Enhance frequency bands with other priorities are configured
AND ment by the CellSlaveBand parameter and added in
descending order based on frequency band priorities.
RMV The frequency band priorities of a cell are determined
CELLB in network planning. It is recommended that the
AND 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.
GUI Value Range: 0~2
Unit: None
Default Value: None
eUCellS LocalCe ADD None None Meaning: Indicates the local cell identity. It uniquely
ectorEq llId EUCEL identifies a cell within an eNodeB.
m LSECT GUI Value Range: 0~255
OREQ
M Actual Value Range: 0~255
LST Unit: None

EUCEL Default Value: None
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
DSP
EURTW
P

eRAN TDD

nd
eUCellS SectorE ADD None None Meaning: Indicates the ID of the sector device that
ectorEq qmId EUCEL serves the cell,it uniquely identifies a sector device
m LSECT within an eNodeB.
OREQ GUI Value Range: 0~65535
M
DSP
EURTW Unit: None
P Default Value: None
LST
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
eUCellS BaseBan ADD None None Meaning:

ectorEq dEqmId EUCEL Indicates the ID of the baseband equipment serving a
m LSECT cell.
OREQ
M When this parameter is set to 255, the baseband
MOD equipment serving a cell is not specified. In this
EUCEL scenario, the LTE baseband processing units (LBBPs)
LSECT serving a cell are selected among all LBBPs in the
OREQ eNodeB, and the LBBPs to which the cell's serving
M RRU is connected are preferentially selected.
LST When this parameter is set to a value other than 255,

EUCEL the cell is served by LBBPs in the specified baseband
LSECT equipment, and the LBBPs to which the cell's serving
OREQ RRU is connected are preferentially selected.
M GUI Value Range: 0~23,255
Actual Value Range: 0~23,255
Unit: None
Default Value: 255

eRAN TDD

nd
CellOp LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELLO identifies a cell within a base station.
P GUI Value Range: 0~255
DSP Actual Value Range: 0~255
CELLB
ROADC Unit: None
ASTCN Default Value: None
OPERA
TOR
LST
CELLO
P
MOD
CELLO
P
RMV
CELLO
P
CellOp Trackin ADD LBFD-0 Broadca Meaning: Indicates the local tracking area identity of
gAreaId CELLO 02009 / st of the cell, which uniquely identifies an operator's record
P TDLBF system of tracking area information within a cell. This
LST D-00200 informat parameter is used only in the eNodeB and is different
CELLO 9 ion from the tracking area identity configured in the
P LBFD-0 Cell tracking area list on the MME.
MOD 0201803 Selectio GUI Value Range: 0~65535
CELLO / n and Actual Value Range: 0~65535
P TDLBF Re-
D-00201 selection Unit: None
RMV 803 Default Value: None
CELLO
P

eRAN TDD

nd
CellOp CellRes ADD LBFD-0 Broadca Meaning:

ervedFo CELLO 02009 / st of Indicates whether the cell is reserved for operator use.
rOp P TDLBF system
MOD D-00200 informat If this parameter is set to
CELLO 9 ion CELL_RESERVED_FOR_OP, the cell is reserved for
P operator use. UEs of AC11 or AC15 in their HPLMN
or EHPLMN can consider this cell as a candidate cell
LST for cell selection or reselection. UEs of AC11 or
CELLO AC15 outside their HPLMN/EHPLMN and UEs of
P 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)
Actual Value Range: CELL_RESERVED_FOR_OP,
CELL_NOT_RESERVED_FOR_OP
Unit: None
Default Value:
CELL_NOT_RESERVED_FOR_OP(Not Reserved)
CellOp OpUlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036 / Sharing (RBs) occupied by the operator on the physical uplink
io P TDLOF with shared channel (PUSCH) when radio access network
MOD D-00103 Commo (RAN) sharing is enabled on the eNodeB and the cell-
CELLO 6 n level RAN sharing switch is turned on. If the data
P LBFD-0 Carrier volume is sufficient, the percentage of RBs occupied
02009 / Broadca by each operator will reach the preset value.
LST Modifications on this parameter affect the percentage
CELLO TDLBF st of
D-00200 system of RBs occupied by operators on the PUSCH. This
P parameter takes effect only in RAN sharing with
9 informat
ion common carriers mode or in hybrid RAN sharing
LOFD-0 mode with more than one CellOp MO being
70206 Hybrid configured.
RAN
Sharing GUI Value Range: 1~100
Unit: %
Default Value: 16

eRAN TDD

nd
CellOp OpDlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036 / Sharing (RBs) occupied by the operator on the physical
io P TDLOF with downlink shared channel (PDSCH) when RAN
MOD D-00103 Commo sharing is enabled on the eNodeB and the cell-level
CELLO 6 n RAN sharing switch is turned on. If the data volume is
P LBFD-0 Carrier sufficient, the percentage of RBs occupied by each
02009 / Broadca operator will reach the preset value. Modifications on
LST this parameter affect the percentage of RBs occupied
CELLO TDLBF st of
D-00200 system by operators on the PDSCH. This parameter takes
P effect only in RAN sharing with common carriers
9 informat
ion mode or in hybrid RAN sharing mode with more than
LOFD-0 one CellOp MO being configured.
70206 Hybrid
RAN GUI Value Range: 1~100
Sharing Actual Value Range: 1~100
Unit: %
Default Value: 16
BASEB BASEB ADD None None Meaning: Indicates the number of the baseband
ANDEQ ANDEQ BASEB equipment.
M MID ANDEQ GUI Value Range: 0~23
M
LST
BASEB Unit: None
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M

eRAN TDD
Cell Management Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

eRAN TDD
Cell Management Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN TDD
Cell Management Feature Parameter Description 10 Reference Documents
10 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. Cell Outage Detection and Compensation Feature Parameter Description
5. SFN Feature Parameter Description


Cell Management Feature Parameter Description: Eran TDD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cell Management Feature Parameter Description: Eran TDD

Uploaded by

Copyright:

Available Formats

eRAN TDD

Cell Management Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2015-10-30) Huawei Proprietary and Confidential i

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

Issue 04 (2015-10-30) Huawei Proprietary and Confidential ii

Issue 04 (2015-10-30) Huawei Proprietary and Confidential iii

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeB

LampSite DBS3900 LampSite TDD

1.2 Intended Audience

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 1

1.3 Change History

eRAN TDD 8.1 04 (2015-10-30)

Change Type Change Description Parameter

Feature change Added descriptions of the newly added pRRU3911, None

Added precautions for the configuration of an 8T8R None

Editorial None None

eRAN TDD 8.1 03 (2015-06-10)

Change Type Change Description Parameter

Feature change None None

Editorial Optimized descriptions of baseband equipment. For None

eRAN TDD 8.1 02 (2015-04-20)

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 2

Change Change Description Paramete Affected

Feature Updated 6.4.4 Precautions. None Macro

Editorial None None N/A

eRAN TDD 8.1 01 (2015-03-20)

eRAN TDD 8.1 Draft A (2015-01-15)

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 3

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 4

3.1 Related Concepts

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 5

Figure 3-1 Cell-related concepts

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 6

Sector Definition Benefits Applicati

Omnidirec An omnidirectional sector uses In low-traffic areas, the Traffic is

Directiona Directional sectors use In high-traffic areas, the Traffic is

3.1.3 Sector Equipment

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 7

3.1.5 Baseband Equipment

3.1.6 Cell-specific Sector Equipment

3.2 Typical Scenarios

3.2.1 Establishing a Cell in a Common Sector

Figure 3-2 A cell established in a common sector

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 8

3.2.2 Establishing Cells in Multiple Sectors with RRU Splitting

3.2.3 Establishing a Cell in a Single Sector with RRU

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 9

3.2.4 Establishing a Cell in Multiple Sectors Served by Different

Figure 3-5 Establishing a Cell in Multiple Sectors Served by Different RRUs

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 10

Table 3-1 Multi-sector cell types

3.2.5 Establishing Multiple Cells in a Multi-Carrier Sector

Figure 3-6 Establishing multiple cells in a multi-carrier sector

Issue 04 (2015-10-30) Huawei Proprietary and Confidential 11

3.3 Cell-related Parameters

For other parameters of a cell, such as uplink-downlink subframe configuration, CPRI

For the steps of reconfiguring these parameters, see 6.4.7 Reconfiguration or

3.3.1 Frequency Band