Cell Management Feature Parameter Description: Eran TDD
Cell Management Feature Parameter Description: Eran TDD
Cell Management Feature Parameter Description: Eran TDD
Issue 04
Date 2015-10-30
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.
Website: http://www.huawei.com
Email: [email protected]
Contents
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
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
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.
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.
3 Technical Description
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.
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.
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.
Figure 3-3 RRU/RFU splitting for multiple sectors (using a 4T4R RRU as an example)
Figure 3-4 RRU combination for a single sector (using a 2T2R RRU as an example)
Multi-sector cells include SFN cells, and pRRU aggregation cells. Table 3-1 describes
different types of multi-sector cells.
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.
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.
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
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.
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.
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
– 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).
Variable Description
ReferenceSig Reference signal (RS) power of the physical downlink shared channel
nalPwr (PDSCH).
For details, see Pmax_out Configuration Parameters.
Variable Description
PowerFactor Power factor ratio of the energy per resource element (EPRE) on the
Ratio PDSCH.
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
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
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.
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
The value of the ReferenceSignalPwr parameter cannot be greater than 18.24 dBm.
4 Related Features
5 Network Impact
6 Engineering Guidelines
6.3 Planning
None
6.4 Deployment
6.4.1 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.
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
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.
The following table describes the parameters that must be set in a SECTOREQM MO to
configure a piece of sector equipment.
The following table describes the parameters that must be set in a CnOperator MO to
configure an operator.
The following table describes the parameters that must be set in a CnOperatorTa MO to
configure a tracking area for an operator.
The following table describes the parameters that must be set in a Cell MO to configure a cell.
Csg indicator Cell.CsgInd The default value for this parameter is Network plan
BOOLEAN_FALSE(FALSE). (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.
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)
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 Slave Cell.CellSlaveB Set this parameter by running the Network plan
Band and ADD CELLBAND command. (negotiation
not required)
The following table describes the parameters that must be set in an EUCELLSECTOREQM
MO to configure a piece of sector equipment for the cell.
The following table describes the parameters that must be set in a CellOp MO to configure a
cell operator.
The following table describes the parameters that must be set in a BaseBandEqm MO to
configure baseband equipment information.
6.4.4 Precautions
Table 6-1 Precautions
Nu If... Then...
mb
er
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
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
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.
Nu If... Then...
mb
er
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
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.
Table 6-2 Cell management parameters (batch configuration for newly deployed eNodeBs)
MO Sheet in the Parameter Group Remarks
Summary Data
File
CellSlaveBand
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
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
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.
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
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.
----End
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.
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.
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.
NOTE
The parameter settings in the following commands are used for reference only. Set the parameters based
on network requirements.
a. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Activating a cell
ACT CELL: LocalCellId=0;
a. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Activating a cell
ACT CELL: LocalCellId=0;
a. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Activating a cell
ACT CELL: LocalCellId=0;
a. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Activating a cell
ACT CELL: LocalCellId=0;
//Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
1. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01";
//Adding a cell
ADD CELL: LocalCellId=0, CellName="cell0", FreqBand=38, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=37900, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0,
PhyCellId=0, FddTddInd=CELL_TDD, SubframeAssignment=SA2,
SpecialSubframePatterns=SSP7, EuCellStandbyMode=ACTIVE, RootSequenceIdx=258,
HighSpeedFlag=HIGH_SPEED, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE=
SFN, TxRxMode=4T4R;
//Activating a cell
ACT CELL:LocalCellId=0;
1. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Activating a cell
ACT CELL: LocalCellId=0;
1. //Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CMCC",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
//Establishing two cells working at different frequencies and ensuring that the frequency
bands do not overlap
//Adding sector equipment for cells with the SectorEqmId parameter set to the same value for
each cell
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=0;
----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.
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.
----End
7 Parameters
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
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
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
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)
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
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
LST Actual Value Range: 0~65535
SECTO
REQM Unit: None
Default Value: None
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
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
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
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
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
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
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
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
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
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)
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
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
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
Actual Value Range: 0~255
Unit: None
Default Value: None
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
Actual Value Range: 0~503
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
LST Actual Value Range: 1~32
CELL Unit: None
Default Value: 1
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
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
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
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 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-
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
Actual Value Range: 0~837
Unit: None
Default Value: None
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
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
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
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
Actual Value Range: 0~256
CELL
Unit: None
LST
CELL Default Value: None
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
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
Actual 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
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
Actual Value Range: 0~65535
DSP
EURTW Unit: None
P Default Value: None
LST
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
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
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
Actual Value Range: 1~100
Unit: %
Default Value: 16
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
Actual Value Range: 0~23
LST
BASEB Unit: None
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
8 Counters
9 Glossary
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