NB-IoT Radio and Performance Basics (ERAN12.1 - 05)
NB-IoT Radio and Performance Basics (ERAN12.1 - 05)
NB-IoT Radio and Performance Basics (ERAN12.1 - 05)
Issue 05
Date 2017-08-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....................................................................................................................................... 12
2.1 Background...................................................................................................................................................................12
2.2 Introduction.................................................................................................................................................................. 13
2.3 Benefits......................................................................................................................................................................... 13
2.4 Architecture.................................................................................................................................................................. 13
2.5 Feature Overview......................................................................................................................................................... 14
2.5.1 MLBFD-12000101 Standalone Deployment.............................................................................................................14
2.5.2 MLBFD-12000102 LTE Guardband Deployment.....................................................................................................14
2.5.3 MLBFD-12000103 LTE In-band Deployment.......................................................................................................... 14
2.5.4 MLBFD-12000202 Single-tone.................................................................................................................................15
2.5.5 MLBFD-12000203 Support of NB-IoT UE.............................................................................................................. 15
2.5.6 MLBFD-12000204 Data over NAS.......................................................................................................................... 16
2.5.7 MLBFD-12100205 Data over User Plane (Trial)......................................................................................................16
2.5.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK................................................................................ 17
2.5.9 MLBFD-12000227 AMC.......................................................................................................................................... 17
2.5.10 MLBFD-12000228 RRC Connection Management................................................................................................17
2.5.11 MLBFD-12000229 Broadcast of System Information............................................................................................ 18
2.5.12 MLBFD-12000223 Physical Channel Management............................................................................................... 18
2.5.13 MLBFD-12000224 DL Asynchronous HARQ....................................................................................................... 18
2.5.14 MLBFD-12000225 UL Asynchronous HARQ....................................................................................................... 18
2.5.15 MLBFD-12000230 Random Access Procedure...................................................................................................... 18
2.5.16 MLBFD-12000231 Paging...................................................................................................................................... 18
2.5.17 MLBFD-12000232 Cell Access Radius up to 35 km..............................................................................................19
2.5.18 MLBFD-12000233 Admission Control...................................................................................................................19
2.5.19 MLBFD-12000234 Basic Scheduling..................................................................................................................... 19
2.5.20 MLBFD-12000235 Uplink Power Control..............................................................................................................19
2.5.21 MLBFD-12000236 DRX.........................................................................................................................................19
3 Technical Description.................................................................................................................22
3.1 Basic Concepts............................................................................................................................................................. 22
3.1.1 Physical Channels......................................................................................................................................................22
3.1.2 Frequency-Domain Structure.................................................................................................................................... 23
3.1.3 Time-Domain Structure............................................................................................................................................. 24
3.1.4 Coverage Level..........................................................................................................................................................26
3.1.5 Aggregation Level..................................................................................................................................................... 26
3.2 Deployment Mode........................................................................................................................................................ 26
3.2.1 Standalone Deployment.............................................................................................................................................26
3.2.2 LTE Guardband Deployment.....................................................................................................................................27
3.2.3 LTE In-band Deployment.......................................................................................................................................... 29
3.3 Cell Management..........................................................................................................................................................31
3.3.1 Related Concepts....................................................................................................................................................... 31
3.3.1.1 Cell..........................................................................................................................................................................32
3.3.1.2 PRB.........................................................................................................................................................................32
3.3.1.3 Sector...................................................................................................................................................................... 35
3.3.1.4 Sector Equipment................................................................................................................................................... 35
3.3.1.5 RF Modules............................................................................................................................................................ 35
3.3.1.6 Baseband Equipment.............................................................................................................................................. 35
3.3.1.7 Cell-specific Sector Equipment.............................................................................................................................. 36
3.4 Idle Mode Management................................................................................................................................................36
3.4.1 Overview................................................................................................................................................................... 36
3.4.2 PLMN Selection........................................................................................................................................................ 37
3.4.3 Automatic PLMN Selection...................................................................................................................................... 38
3.4.4 Manual PLMN Selection........................................................................................................................................... 39
3.4.5 Roaming.....................................................................................................................................................................39
3.4.6 Cell Selection and Reselection.................................................................................................................................. 39
3.4.6.1 Cell Search..............................................................................................................................................................40
3.4.6.2 Cell Selection..........................................................................................................................................................40
3.4.6.3 Neighboring Cell Measurement for Cell Reselection.............................................................................................42
3.4.6.4 Cell Reselection...................................................................................................................................................... 42
3.4.6.5 TA Registration.......................................................................................................................................................44
3.4.6.6 TA Update...............................................................................................................................................................44
3.4.6.7 Attach/Detach......................................................................................................................................................... 44
3.4.7 Cell Reservation and Access Control........................................................................................................................ 44
3.4.7.1 Cell Reservation and Barring................................................................................................................................. 45
3.4.7.2 Access Control........................................................................................................................................................45
3.4.8 Paging........................................................................................................................................................................ 46
3.4.9 System Information Broadcast.................................................................................................................................. 50
3.5 Connection Management.............................................................................................................................................. 52
3.5.1 Random Access......................................................................................................................................................... 52
3.5.1.1 Overview................................................................................................................................................................ 52
3.5.1.2 Random Access Procedure..................................................................................................................................... 53
3.5.1.3 NPRACH Resource Configuration.........................................................................................................................55
3.5.1.4 NPRACH Detection Threshold.............................................................................................................................. 58
3.5.2 RRC Connection Setup..............................................................................................................................................58
3.5.3 RRC Connection Resume.......................................................................................................................................... 60
3.5.4 NB-IoT MME Selection............................................................................................................................................ 61
3.5.5 Data Transmission..................................................................................................................................................... 61
3.5.6 Signaling Connection Release................................................................................................................................... 64
3.6 Scheduling.................................................................................................................................................................... 65
3.6.1 Definition...................................................................................................................................................................65
3.6.2 Scheduler Working Principle..................................................................................................................................... 66
3.6.3 Uplink Scheduling..................................................................................................................................................... 68
3.6.3.1 Uplink Scheduling Procedure................................................................................................................................. 68
3.6.3.2 Uplink Scheduling Triggering................................................................................................................................ 69
3.6.3.3 Uplink Scheduling for Retransmissions................................................................................................................. 69
3.6.3.4 Uplink Scheduling for Initial Transmissions.......................................................................................................... 70
3.6.4 Downlink Scheduling................................................................................................................................................ 72
3.6.4.1 Downlink Scheduling Procedure............................................................................................................................ 72
3.6.4.2 Downlink Scheduling for Retransmissions............................................................................................................ 73
3.6.4.3 Downlink Scheduling for Initial Transmissions..................................................................................................... 73
3.7 Power Control...............................................................................................................................................................76
3.7.1 Downlink Power Control...........................................................................................................................................76
3.7.2 Uplink Power Control................................................................................................................................................81
3.7.2.1 NPRACH Power Control........................................................................................................................................81
3.7.2.2 NPUSCH Power Control........................................................................................................................................ 81
3.8 Admission Control, Congestion Control, and Overload Control................................................................................. 83
3.9 DRX..............................................................................................................................................................................87
3.9.1 DRX-related Concepts...............................................................................................................................................88
3.9.2 Startup of a DRX Cycle.............................................................................................................................................89
3.9.3 Operation in a DRX Cycle.........................................................................................................................................89
3.10 Idle Mode eDRX........................................................................................................................................................ 92
4 Related Features.........................................................................................................................106
4.1 MLBFD-12000101 Standalone Deployment..............................................................................................................107
4.2 MLBFD-12000102 LTE Guardband Deployment......................................................................................................107
4.3 MLBFD-12000103 LTE In-band Deployment........................................................................................................... 108
4.4 MLBFD-12000202 Single-tone.................................................................................................................................. 111
4.5 MLBFD-12000203 Support of NB-IoT UE............................................................................................................... 112
4.6 MLBFD-12000204 Data over NAS............................................................................................................................112
4.7 MLBFD-12100205 Data over User Plane (Trial).......................................................................................................112
4.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK................................................................................. 113
4.9 MLBFD-12000227 AMC........................................................................................................................................... 113
4.10 MLBFD-12000228 RRC Connection Management................................................................................................. 114
4.11 MLBFD-12000229 Broadcast of System Information............................................................................................. 114
4.12 MLBFD-12000223 Physical Channel Management.................................................................................................114
4.13 MLBFD-12000224 DL Asynchronous HARQ.........................................................................................................115
4.14 MLBFD-12000225 UL Asynchronous HARQ.........................................................................................................115
4.15 MLBFD-12000230 Random Access Procedure....................................................................................................... 116
4.16 MLBFD-12000231 Paging....................................................................................................................................... 116
4.17 MLBFD-12000232 Cell Access Radius up to 35 km............................................................................................... 116
4.18 MLBFD-12000233 Admission Control....................................................................................................................116
4.19 MLBFD-12000234 Basic Scheduling...................................................................................................................... 117
4.20 MLBFD-12000235 Uplink Power Control...............................................................................................................117
4.21 MLBFD-12000236 DRX..........................................................................................................................................118
4.22 MLBFD-12000237 Cell Selection and Re-selection................................................................................................ 118
4.23 MLBFD-12000238 UL 2-Antenna Receive Diversity............................................................................................. 119
4.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity............................................................................................119
4.25 MLBFD-12100243 Congestion Control...................................................................................................................119
4.26 MLOFD-120220 Idle Mode eDRX.......................................................................................................................... 120
4.27 MLOFD-120201 NB-IoT Coverage Extension........................................................................................................ 120
12 Parameters................................................................................................................................. 224
13 Counters.................................................................................................................................... 382
14 Glossary..................................................................................................................................... 423
15 Reference Documents............................................................................................................. 424
1.1 Scope
This document describes Narrowband Internet of Things (NB-IoT) features, including their
technical principles, related features, network impact, and engineering guidelines.
MLBFD-12000236 DRX
MLBFD-12000237 Cell Selection and Re-selection
MLBFD-12000238 UL 2-Antenna Receive Diversity
MLBFD-12100240 DL 4-Antenna Transmit Diversity
MLBFD-12100242 Active Queue Management (AQM)
MLBFD-12100243 Congestion Control
MLBFD-12100244 SCTP Congestion Control
l MLOFD-120201 NB-IoT Coverage Extension
l MLOFD-120220 Idle Mode eDRX
l MLOFD-120230 Multi-tone
l MLOFD-121202 UL 4-Antenna Receive Diversity
l MLOFD-121204 SFN
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
eRAN12.1 05 (2017-08-30)
This issue includes the following changes.
Change Change Description Parameter Change Affected
Type Entity
eRAN12.1 04 (2017-06-29)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity
eRAN12.1 03 (2017-05-29)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity
Enabled the backoff, access barring, and Added the Macro and
random access flow control functions PreambleSchEnh micro
and allowed the eNodeB to include the Switch option to eNodeBs
extendedWaitTime IE in RRC the
Connection Release messages when the CellAlgoSwitch.U
air interface is overloaded in a cell. lSchExtSwitch
For details, see 3.8 Admission Control, parameter.
Congestion Control, and Overload Added the
Control. UlRaUserSchOpt
Sw option to the
CellAlgoSwitch.U
lSchSwitch
parameter.
Added the
Extendedwaittime
Switch option to
the
CellAlgoSwitch.M
TCCongControlS
witch parameter.
eRAN12.1 02 (2017-04-26)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity
Feature Enabled the time for the eNodeB to wait Added the Macro and
change an RRC Connection Setup Complete NbCellDlSchCEAl micro
message to be configurable by the go.UuMessageWait eNodeBs
NbCellDlSchCEAl- ingTimer
go.UuMessageWaitingTimer parameter. parameter.
For details, see 3.5.2 RRC Connection
Setup.
Enabled the PRACH start time for each Added the Macro and
coverage level to be configurable by the following micro
CellRachCECfg.PrachStartTime parameters: eNodeBs
parameter. For details, see 3.5.1 l RACHCfg.Prac
Random Access. hStartTimeCfgI
nd
l CellRachCECf
g.PrachStartTi
me
eRAN12.1 01 (2017-03-08)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity
Feature Added the limitation on the number of LTE None Macro and
change FDD RBs that can be reserved for NB-IoT in micro
LTE in-band deployment. The recommended eNodeBs
maximum number is 9. For details, see 3.2.3
LTE In-band Deployment.
NOTE
2 Overview
2.1 Background
The Internet of Things (IoT) is an important part of the information technology of the future.
IoT is expected to enable people-thing and thing-thing interconnections by combining
communications technologies and networks. There are three types of IoT scenarios, each with
different bandwidth, power, and connectivity requirements, as shown in Figure 2-1.
l High rate
These are services such as video surveillance and electronic billboards, where there is
access to an external power supply and there are no special requirements regarding
power consumption.
l Moderate rate
These are services such as smart home appliances and Internet of Vehicles applications,
where there is access to an external power supply and there are still at least some
requirements regarding power consumption.
l Low rate
These are services such as wireless meter reading and industrial sensors, where there are
requirements for massive connections. Low rate services typically run on battery
powered devices, must be able to wait in standby mode for extremely long periods, and
run for extended periods on very little power. Low rate services must also be extremely
inexpensive.
Conventional wireless networks are not well designed for the huge number of low-rate
connections that IoT requires at such low costs and with very little power. Conventional
wireless networks are too expensive and too power hungry. 3GPP introduced Narrowband
Internet of Things (NB-IoT) to accommodate these scenarios.
2.2 Introduction
NB-IoT introduced a new radio interface technology for wireless IoT. It is mainly used for
low power, low rate scenarios that require deep coverage, and a massive volume of
connections.
2.3 Benefits
NB-IoT provides the following benefits:
l Maximum spectrum utilization
NB-IoT supports standalone deployment, LTE guardband deployment, and LTE in-band
deployment, fully utilizing spectrum resources and increasing spectral efficiency.
l Support for a large number of low-rate users
The low-rate, low-activity, machine-to-machine (M2M) application service model
supports a large number of users.
l Deep coverage
NB-IoT provides coverage enhancement with the help of repetitive data transmission and
power spectrum density (PSD) increase.
l Low power of UEs
The NB-IoT protocol stack is optimized for streamlined signaling processing and
signaling interaction, reducing UE power consumption.
2.4 Architecture
Figure 2-2 illustrates the end-to-end network architecture of NB-IoT.
l NB-IoT UE
Communicates with the eNodeB over the air interface.
l eNodeB
Performs functions such as air interface access processing and cell management. The
eNodeB communicates with the IoT evolved packet core (EPC) through an S1-lite
interface and sends non-access stratum (NAS) data to the IoT EPC for processing.
l IoT EPC
Interacts with the NAS of the UE and forwards IoT data to the IoT platform for
processing.
l IoT platform
Converges IoT data from access networks and forwards different types of data to their
corresponding application servers.
l Application server
Receives and processes IoT data.
Table 2-1 Downlink physical layer parameter values set by the field ue-Category-NB
UE Category Max. DL-SCH Max. Bits of a DL- Total Soft
Transport Block SCH Transport Channel Bits
Bits Received Block Received
Within a TTI Within a TTI
Table 2-2 Uplink physical layer parameter values set by the field ue-Category-NB
UE Category Max. UL-SCH Transport Max. Bits of a UL-SCH
Block Bits Transmitted Transport Block
Within a TTI Transmitted Within a
TTI
NB1 4000
Table 2-4 Half-duplex FDD operation type set by the field ue-Category-NB
UE Category Half-Duplex FDD Operation Type
NB1 Type B
NOTE
In this operation type, uplink and downlink
transmission are separated by a guard interval,
during which UEs neither monitor the
Narrowband Physical Downlink Control Channel
(NPDCCH) nor perform uplink transmission.
Figure 2-3 Protocol stack for the control plane CIoT EPS optimization function
Uplink data is carried by NAS messages in uplink RRC messages, and downlink data is
carried by NAS messages in downlink RRC messages.
Before using this feature, read 1.2 Disclaimer for Trial Features.
This feature implements the user plane CIoT EPS optimization function stipulated in 3GPP
TS. 36.300.
Unlike the control plane CIoT EPS optimization function, the user plane CIoT EPS
optimization function involves the PDCP layer between the RRC and RLC layers, as shown
in Figure 2-4. The PDCP layer supports data encryption and integrity protection for data
transmitted over the Uu interface. Service data is transmitted by the default bearer on the user
plane. Before data transmission, one or two DRBs are established between the UE and
eNodeB. To reduce signaling overhead of access procedures and meet the low power
consumption requirement for UEs, this function has simplified the access procedures with
support for suspension of RRC connections and UE context storage on the eNodeB and UE.
When the UE accesses the network again, the UE and eNodeB can quickly restore the UE
context, with no need for security activation and RRC reconfiguration procedures. Message
interactions over the Uu interface are reduced as a result. When the UE moves between the
coverage areas of different eNodeBs, the UE context is transmitted over the X2 interface to
recover the RRC connection. For details about this feature, see 3GPP TS 36.300.
Figure 2-4 Control plane protocol stack for the user plane CIoT EPS optimization function
NB-IoT UEs must support the control plane CIoT EPS optimization function and can
optionally support the user plane CIoT EPS optimization function.
This feature allows eNodeBs and UEs to select a modulation scheme based on the current
channel conditions, balancing the user data rate against the frame error rate (FER) during
transmission. For details about this feature, see 3GPP TS 36.211.
SI broadcast over the broadcast control channel (BCCH) can be read by UEs in RRC_IDLE
mode, without requiring RRC connection establishment. For details, see 3.4.9 System
Information Broadcast.
Power control for the NPUSCH decreases interference on neighboring cells and increases the
data rates of UEs at the local cell edge while ensuring cell throughput.
Power control for the NPRACH enables UEs to use the optimal low power to send preambles
while ensuring the random access success rate, thereby decreasing interference on
neighboring cells and decreasing UE power consumption.
For details about uplink power control, see 3.7.2 Uplink Power Control.
Figure 2-5 Paging procedure for UEs enabled with the eDRX and in RRC_IDLE mode
Idle Mode eDRX requires time synchronization in hyper system frame number (HSFN)
between the eNodeB and MME, as described in 3.10 Idle Mode eDRX.
For details about this feature, see 3.11 NB-IoT Coverage Extension.
3 Technical Description
(15 kHz each) or 48 subcarriers (3.75 kHz each). In the current version, the NPUSCH
supports multi-tone transmission and 15 kHz single-tone transmission, and the NPRACH
supports only 3.75 kHz single-tone transmission.
12 2 1
NOTE
The current version does not support 3.75 kHz single-tone transmission over the NPUSCH, including
the NPUSCH for uplink control information (UCI) transmission.
There are two options for standalone deployment, refarming or the use of idle spectrum.
l Refarming
Refarming enables part of the spectrum for a RAT to be used by NB-IoT, without
affecting the functionality of that RAT. Typically, GSM spectrum resources are refarmed
for NB-IoT, with guard bands used to set them apart. The GSM network is then
replanned to minimize the impact of the refarming on GSM services.
The following figure uses 1:1 co-site deployment as an example. In this example, two
GSM carriers are allocated to the NB-IoT network with a guard band of 100 kHz
reserved between NB-IoT and GSM. In refarming deployment, the GSM frequencies
across the entire buffer zone area need to be refarmed to reduce interference even if NB-
IoT is not deployed.
NOTE
If the adjacent GSM frequency is a BCCH frequency, a guard band of 300 kHz is reserved.
UMTS idle spectrums are used to deploy the NB-IoT network, as shown in Figure
3-7.
LTE idle spectrums are used to deploy the NB-IoT network, as shown in Figure
3-8.
The guard band between carriers is generally at least 180 kHz. NB-IoT is a narrowband
communication technology, requiring just 180 kHz of bandwidth for the uplink and another
180 kHz for the downlink. Services can be deployed on the guard bands of existing RATs,
eliminating the need for new spectrum resources and improving the utilization of old
spectrum.
In guard band deployment, NB-IoT services are now deployed on LTE FDD guard bands, as
shown in Figure 3-9. This deployment mode must meet the requirements specified in 3GPP
TS 36.101 (Release 13).
When LTE FDD cells use a bandwidth greater than or equal to 10 MHz, the guard bands
provide enough bandwidth to deploy NB-IoT. Figure 3-10 is an example of LTE guard band
deployment on 10 MHz of LTE FDD bandwidth. In accordance with 3GPP TS 36.802
(Release 13), LTE guard band deployment requires that the LTE FDD cell bandwidth be at
least 5 MHz. When LTE FDD cells use a 5 MHz bandwidth, LTE guard band deployment
makes the guard band become insufficient, causing interference to adjacent frequency bands.
Therefore, an LTE FDD cell bandwidth of at least 10 MHz is required for LTE guard band
deployment in this version.
Figure 3-10 LTE guard band deployment on 10 MHz of LTE FDD bandwidth
NOTE
For details about the LTE spectrum template, see 3GPP TS 36.104 V10.11.0.
Whether to use LTE guard band deployment is specified by the PRB.DeployMode parameter.
In LTE guard band deployment, the LTE FDD system bandwidth and center frequency must
be specified for NB-IoT deployment position verification. That is, the PRB.LteBandWidth
and PRB.LteDlEarfcn parameters must be configured.
NOTE
LTE guard band deployment must comply with the local laws and regulations. The uplink and downlink
E-UTRA absolute radio frequency channel numbers (EARFCNs) and frequency offsets for NB-IoT must
be planned with the assistance of Huawei technical support.
5 MHz 2, 7, 17, 22 7, 17
15 MHz 2, 7, 12, 17, 22, 27, 32, 42, 47, 52, 57, 32, 42
62, 67, 72
20 MHz 4, 9, 14, 19, 24, 29, 34, 39, 44, 55, 60, 44, 55
65, 70, 75, 80, 85, 90, 95
Uplink RB positions recommended for NB-IoT are at band edges excluding the positions
for the LTE FDD PRACH and static PUCCH. If the PUCCH is dynamically configured
(that is, if the PucchSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter
is selected), uplink RB positions recommended are at the first or last RB of the available
resources of LTE FDD.
If NB-IoT resources conflict with LTE FDD PRACH resources, NB-IoT cells
cannot work properly.
If NB-IoT positions conflict with static LTE FDD PUCCH positions, less PUCCH
resources will be available.
l LTE FDD RB reservation for NB-IoT
LTE FDD RB reservation policies for NB-IoT are controlled by the
CellRbReserve.RbRsvType and CellRbReserve.RbRsvMode parameters. The first
parameter specifies whether uplink or downlink RBs are reserved. The second parameter
specifies whether the reserved RBs are used for NB-IoT deployment.
It is recommended that no more than nine RBs be reserved for NB-IoT in an LTE FDD
cell. If more than nine RBs are reserved, only nine RBs can take effect as follows:
a. RBs reserved for NB-IoT deployment take effect preferentially.
b. RBs take effect in ascending order of the CellRbReserve.Index parameter value.
In downlink, NB-IoT subcarriers are orthogonal to LTE FDD subcarriers and therefore
no guardbands are required between them.
In uplink, NB-IoT NPRACH subcarriers are not orthogonal to LTE FDD subcarriers
because an NPRACH can use only a 3.75 kHz subcarrier for single-tone transmission.
RBs adjacent to NB-IoT RBs can be used as guardbands for interference mitigation. In
practice, however, RBs are not reserved for this purpose because the impact of
interference is not greater than the impact of reservation of one or two RBs.
l NB-IoT's conflict avoidance for LTE FDD
[Uplink]
If uplink NB-IoT RBs conflict with LTE FDD SRS resources, there will be interference
between them. To enable NB-IoT's conflict avoidance for LTE FDD, the
PRB.UlAllSymbolSendFlag parameter can be set to FALSE. Under this setting,
however, uplink NB-IoT capacity may decrease by 8% to 20%.
To determine whether an LTE FDD cell has SRS resources, you can check the
SRSCFG.SrsCfgInd parameter. If it is set to BOOLEAN_TRUE, the LTE FDD cell has
SRS resources.
If uplink NB-IoT RBs are more closer to the band edge while LTE FDD PUCCH
resources are more closer to the band center, there will be no conflict between uplink
NB-IoT RBs and LTE FDD SRS resources.
[Downlink]
Downlink NB-IoT RB resources must be punctured (reserved) for LTE FDD PDCCH
and cell-specific reference signal (CRS) according to 3GPP TS 36.211 (Release 13).
Currently, three symbols are reserved for PDCCH, as shown in the following figure.
In addition, the PCIs of NB-IoT and LTE FDD cells must leave the same remainder after
being divided by a number so that the NB-IoT cell can use LTE FDD CRS measurement
results. To simplify network planning, the current version requires that NB-IoT and LTE
FDD cells use the same PCI. The PCI is specified by the Cell.PhyCellId parameter.
3.3.1.1 Cell
A cell is an area where wireless communications services are provided. It is a fundamental
unit of a radio network. An NB-IoT cell is added by running the ADD CELL command with
the Cell.NbCellFlag parameter set to TRUE(TRUE). All the cells together jointly cover the
entire radio network. In the current version, an NB-IoT cell can only be a normal cell.
3.3.1.2 PRB
As a carrier in an NB-IoT cell, the physical resource block (PRB) configuration consists of
the identity of the NB-IoT cell served by the carrier, the deployment mode, and EARFCN-
related information. A PRB can be added by running the ADD PRB command and is
configured as required.
NOTE
In the current version, each NB-IoT cell corresponds to a single PRB. In later versions, one NB-IoT cell
can correspond to multiple PRBs.
Cell Bandwidth
NB-IoT cells have a fixed bandwidth of 180 kHz.
The uplink center frequency of the PRB for a cell can be calculated using the following
formula:
In LTE in-band deployment, operators deploy NB-IoT using existing LTE FDD in-band RBs,
and therefore the PRB center frequency of an NB-IoT cell must be consistent with the RB
center frequency of the corresponding LTE FDD cell. The NB-IoT frequency offset and
frequency are calculated using the following method:
In the downlink:
Obtain the downlink frequency offset. The specific offset relates to the LTE FDD cell
bandwidth and RB position, as described in Table 3-3, which complies with 3GPP TS 36.213
(Release 13).
5 MHz 2 and 7 2
17 and 22 1
In the uplink:
First use the following formula to calculate the uplink frequency, and rounds the calculated
value to an integer:
Then use the following formula to calculate the uplink frequency offset based on the
calculated uplink frequency:
3.3.1.3 Sector
A sector is the radio coverage area of an antenna. Sectors are added by running the ADD
SECTOR command. Each sector uses one or more radio carriers to provide coverage. Sectors
are combined with carriers to form cells.
NOTE
For a co-MPT base station, if services of different RATs are carried on the same transmit channel,
configure the same SECTOR MO for these RATs.
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 RATs are carried on the same transmit channel,
configure the SECTOREQM MO by RAT.
3.3.1.5 RF Modules
RF modules include RRUs and RFUs. An RF module is added by running the ADD RRU
command. After execution of this command, the ADD RRUCHAIN command must be
executed to specify the CPRI ports on baseband processing units (BBPs) for connecting the
added RF module.
In NB-IoT eNodeBs, a piece of baseband equipment must support both uplink and downlink
transmissions. It is recommended that each piece of baseband equipment include 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.4.1 Overview
The main activities of UEs in RRC_IDLE mode are public land mobile network (PLMN)
selection, cell selection and reselection, and tracking area (TA) registration. Figure 3-14
shows the relationships among them.
Figure 3-14 Relationships among PLMN selection, cell selection and reselection, and TA
registration
If the UE finds a suitable cell in a PLMN during this PLMN selection procedure, the UE
attempts to register on that PLMN. If the registration is successful, the UE camps on the
suitable cell; otherwise, the UE tries the next PLMN.
NOTE
Normal service and operator service are two types of services provided to UEs in RRC_IDLE mode in
the suitable cell and reserved cell, respectively. For details about the suitable cell and reserved cell, see
section 4.3 in 3GPP TS 36.304.
NB-IoT does not support limited service.
3.4.5 Roaming
When roaming, the UE obtains services from the visited PLMN (VPLMN), a PLMN other
than its HPLMN. For example, the UE may obtain services from a PLMN in another country
(an international roaming area). When a UE with the roaming service moves out of the
coverage area of its HPLMN, the UE can obtain services from another PLMN according to
the PLMN data stored in its USIM. The operator determines whether roaming is allowed for
the UE.
After the UE registers with a VPLMN, it periodically searches for its HPLMN and attempts to
return to there. The time interval between consecutive searches for the HPLMN is defined by
the operator and stored in the USIM. The time interval between consecutive searches by NB-
IoT UEs for the HPLMN ranges from 2 to 240 hours. If the time interval is not stored in the
USIM, the default value of 72 hours is used.
In the NB-IoT system, synchronization signals are specially used for cell search. There are
two types of synchronization signals: the narrowband primary synchronization signal (NPSS)
and the narrowband secondary synchronization signal (NSSS). More information about these
two types of signals can be found in 3GPP TS 36.211 (Release 13). The cell search procedure
is as follows:
1. The UE monitors the NPSS and NSSS to achieve frame synchronization, that is, time
synchronization with the cell, and to obtain the PCI.
2. The UE monitors the downlink reference signal to determine the signal quality of the
cell.
3. The UE monitors the NPBCH to acquire other information about the cell.
Triggering
When a UE switches from RRC_CONNECTED mode to RRC_IDLE mode or after it selects
a PLMN, the UE must select a cell to camp on.
When the UE switches from RRC_CONNECTED mode to RRC_IDLE mode, it first attempts
to select the last cell that it camped on in RRC_CONNECTED mode or it selects a suitable
cell on the frequency that is allocated through the RRC Connection Release message. If such
a cell is not available, the UE attempts to find a suitable cell by performing a Stored
Information Cell Selection procedure. If the UE fails to find a suitable cell, the UE performs
an Initial Cell Selection procedure.
NOTE
In the current version, the RRC Connection Release message does not contain the frequency allocated to
the UE.
l Stored information cell selection
The Stored Information Cell Selection procedure requires stored information related to
carrier frequencies and cell parameters. The information is obtained from previously
detected SI messages of cells. This information can help speed up cell selection.
l Initial cell selection
In this procedure, the UE scans all carrier frequencies in the evolved universal terrestrial
radio access network (E-UTRAN) according to its capabilities to find a suitable cell. On
each carrier frequency, the UE searches only for the cell with strongest signal. If the UE
finds a suitable cell, it selects that cell to camp on.
l Qrxlevmin is the lowest cell RX signal level. It is broadcast in SIB3 and specified by the
CellResel.QRxLevMin parameter.
l PMax is the maximum transmit power that the UE can apply to uplink transmission in
the neighboring cell. It is broadcast in SIB3 and specified by the CellResel.PMax
parameter.
The following parameters broadcast in SIB5 are used for calculating the Srxlev values of
inter-frequency neighboring cells:
l Qrxlevmin is the lowest cell RX signal level. It is broadcast in SIB5 and specified by the
EutranInterNFreq.QRxLevMin parameter.
l PMax is the maximum transmit power that the UE can apply to uplink transmission in
neighboring cells. It is broadcast in SIB5 and specified by the EutranInterNFreq.PMax
parameter.
The cell-ranking criteria R_s for the serving cell and R_n for neighboring cells are defined as
follows:
R_s = Qmeas,s + Qhyst Qoffsettemp
3.4.6.5 TA Registration
A UE informs the EPC of its TA by TA registration. The TA is a concept introduced to the
LTE/System Architecture Evolution (SAE) system for location management of UEs. A TA is
identified by a tracking area identity (TAI), which consists of the mobile country code
(MCC), mobile network code (MNC), and tracking area code (TAC). According to 3GPP
specifications, the TAIs of NB-IoT networks need to be independently configured and cannot
be the same as those of the E-UTRAN. In addition, interoperations between NB-IoT and E-
UTRAN are not allowed.
TA registration can be performed in two ways: TA update and Attach/Detach.
3.4.6.6 TA Update
UEs perform TA updates by sending TA update requests when any of the following conditions
are met (For details, see section 5.3.3.0 in 3GPP TS 23.401):
l The UE detects that it has entered a new TA when it finds that the TAI in the system
information is different from any TAI stored in its USIM.
l The periodic TA update timer expires. This timer length is delivered to the UE through a
non-access stratum (NAS) message.
l The RRC connection is released for load balancing.
l The UE receives an NAS level RRC connection setup failure message from the RRC
layer of the UE.
l The preferred network behavior information about or eDRX parameters for the UE
change and become inconsistent with the information stored on the MME.
The UE informs the EPC of its TA by TA update. The EPC will send paging messages to all
eNodeBs in the TA.
3.4.6.7 Attach/Detach
When a UE needs to obtain services from a network but is not registered to that network, the
UE performs an Attach procedure for TA registration. For the detailed Attach procedure, see
section 5.3.2.1 in 3GPP TS 23.401 (Release 13).
After a successful Attach procedure, the UE is allocated an IP address. The mobile equipment
identity (MEI) of the UE will be sent to the MME for authentication.
If the UE fails to connect to the EPC or the EPC does not allow UE access, a Detach
procedure is initiated. After the Detach procedure is finished, the EPC no longer pages the
UE.
3.4.8 Paging
Triggering of Paging
Paging is a procedure that can be initiated either by an MME to transmit paging messages to a
UE in RRC_IDLE mode, or by an eNodeB to inform all UEs in RRC_IDLE mode of an SI
message change.
l Transmitting paging messages to a UE in RRC_IDLE mode
The paging messages contain a tracking area list (TAL) for the concerned cell or UE. In
the cell or in all the cells within the TAs on the list, the eNodeBs transmit paging
messages over the paging control channel (PCCH) to page the UE. The paging messages
also contain the UE identity, which can be the SAE-temporary mobile subscriber identity
(S-TMSI) or international mobile subscriber identity (IMSI) of the UE.
l Informing all UEs in RRC_IDLE mode of an SI message change
The eNodeB transmits paging messages or NPDCCH messages (DCI format N2) to
notify all UEs in RRC_IDLE mode in the cell when the SI message changes. In the next
SI message modification period, it transmits the updated SI message. To ensure that all
of these UEs receive the system information, the eNodeB transmits the paging messages
or NPDCCH messages on all possible occasions in discontinuous reception (DRX)
cycles.
Though paging can be triggered by different NEs, the paging mechanism on the Uu interface
is the same.
NOTE
When the repetition count of NPDCCH information in a paging message is set to 1 and the signal quality
is good, a paging message occupies only one valid subframe. Under other circumstances, a paging
message can occupy multiple valid subframes.
The PF number and PO subframe number can be calculated based on the IMSI of the UE,
DRX cycle, and number of PO subframes in a DRX cycle. Frame numbers are stored in the SI
that contains the DRX parameters of the UE. When the DRX parameters change, PF number
and PO subframe number change accordingly.
The SFN of a PF is derived from the following formula: SFN mod T = (T div N) x (UE_ID
mod N)
Table 3-4 lists the subframe number i_s of a PO, which is derived from the following
formula: i_s = floor (UE_ID/N) mod Ns, where floor (UE_ID/N) represents rounding
(UE_ID/N) down to the nearest integer.
2 4 9 N/A N/A
4 0 4 5 9
NOTE
l In accordance with 3GPP TS 36.304, the NB-IoT UE does not support a specific paging cycle.
l In the S1 setup process, the eNodeB sends the MME the information about the eNodeB-
specific default NB-IoT paging DRX cycle. Based on the default paging DRX cycle, the MME
determines whether paging response times out. The default paging DRX cycle is specified by
the GlobalProcSwitch.S1DefaultPagingDrxForNb parameter. It is recommended that the
length of the default paging DRX cycle be greater than or equal to the "defaultPagingCycle"
IE value for all NB-IoT cells.
l N equals min(T, nB). The PCCHCfg.NbForNbIoT parameter specifies nB.
l Ns is max(1, nB/T).
l UE_ID equals IMSI mod 4096.
If the paging is triggered by the MME, the UE_ID value is the UE Identity Index
Value contained in the paging message sent over the S1 interface.
If the paging is triggered by the eNodeB, the UE_ID is unavailable, and the UE uses
the default UE_ID value of 0.
In addition to DRX, the paging procedure can also work with eDRX. For details, see 3.10 Idle
Mode eDRX.
earlier in a paging occasion and sends the paging messages for other UEs in the next
paging cycle.
l Priority differentiation
If PCCHCfg.PagingStrategy is set to PAGING_STRATEGY_DIFFPRI(Priority
Differentiation Strategy), the eNodeB preferentially selects paging messages that have
paging priorities and then selects PS paging messages that do not have paging priorities.
The eNodeB then sends the paging messages that have paging priorities in a paging
occasion and sends the remaining paging messages in the next paging cycle.
The paging message priorities are carried in the paging message sent by the MME to the
eNodeB. PS paging messages are indicated by value PS of the CN Domain field in
paging messages sent by the MME to the eNodeB.
Extended Paging
Most NB-IoT UEs are not very mobile. Therefore, an NB-IoT UE is preferentially paged in
the last cell it camped on and then paged in an extended area only if the previous paging fails,
which saves Uu interface resources and reduce UE power consumption. Figure 3-18 shows
an extended paging procedure.
1. When a UE's connection is released, the eNodeB includes the following information in a
UE Context Release Complete message sent to the MME:
UE's current cell and coverage level
Recommended cell list and eNodeB list. The recommended cell list includes the
intra-frequency neighboring cells of the current cell, and the eNodeB list includes
the eNodeBs serving the cells in the recommended cell list.
2. The MME stores the information received in the UE Context Release Complete message.
When paging the UE, the MME includes the coverage level and recommended cell list in
the paging message to the eNodeB.
NOTE
The MME determines the paging scope based on the recommended eNodeB list.
3. When the eNodeB receives the paging message from the MME, it determines the
extended paging policy based on the number of the current paging times and the total
number of planned paging times:
The eNodeB preferentially pages the UE in the last cell it camped on, and if the paging
fails, proceeds to page the UE in the recommended cells, and pages the UE in the entire
TA if the previous two paging attempts fail.
l The MIB is transmitted over the BCCH through an independent RRC message. The
BCCH has a predefined transport format. The UE receives the MIB on the BCCH
without obtaining other information from the network.
l The SIB1 is transmitted over the DL-SCH through an independent RRC message.
l Other SIBs are transmitted over the downlink shared channel (DL-SCH) through SI
messages, and the scheduling periods can be set separately. SIBs with the same
scheduling period can be transmitted through the same SI message, whereas the SIBs
with different scheduling periods must be transmitted through different SI messages.
SIB1 carries the scheduling periods of all SI messages and mapping information from
SIBs to SI messages.
The different types of content contained in the MIB, and in each SIB, are described in the
following table.
SI Block Content
SIB1 Parameters related to cell access and cell selection, and scheduling
information of SI messages
SI Block Content
SIB3 Common cell reselection parameters for all cells and intra-frequency
cell reselection parameters
SIB14 Access control information, which is used to bar the access of UEs
belonging to certain classes
NOTE
NB-IoT does not support intra-frequency and inter-frequency cell reselection blacklists in the current
version.
When SI messages (excluding the SIB14 and SIB16) are updated, the eNodeB changes the
value of "systemInfoValueTag" in the MIB and the value of "systemInfoValueTagSI" in the
SIB1. The UE reads the values and compares them with the values that it read last time. If the
values change, it is an indication that SI messages change. If the values do not change, it is an
indication that SI messages do not change.
The UE reads the SI message again 24 hours after receiving an SI message. In this case, the
UE reads all SI messages regardless of whether the values of "systemInfoValueTag" and
"systemInfoValueTagSI" change.
3.5.1.1 Overview
Random access must be performed before a UE can establish communication with the
network. During random access, the UE sends an access request to the eNodeB and then the
eNodeB responds to the request and allocates a RACH. Through random access, the UE
obtains uplink synchronization signals from the network and requests dedicated resources for
data transmission.
NB-IoT UEs initiate a random access procedure when one of the following conditions is met:
l The UE initiates a random access procedure while in RRC_IDLE mode or after being
paged.
l The eNodeB needs to send downlink data to a UE in RRC_CONNECTED mode and
finds that the UE is out-of-synchronization in the uplink.
l The UE is in RRC_CONNECTED mode when data for the UE arrives, but the UE has
not received a UL Grant message from the eNodeB. Under this condition:
If the NbCellUlSchCEAlgo.NbLogicChSrProhibitTimer parameter is set to
NOT_CFG, the UE immediately initiates a random access procedure but the
probability of successful pre-scheduling for the UE decreases.
If the NbCellUlSchCEAlgo.NbLogicChSrProhibitTimer parameter is set to a
value other than NOT_CFG (PP2 is recommended), the UE starts this timer and
initiates a random access procedure until the timer expires. The timer configuration
increases the probability of successful pre-scheduling for the UE. However, if this
timer is set to a too large value, the UE's access delay increases.
1. The UE reads RACH configuration information from SIB2, selects a coverage level
based on the RSRP threshold contained in SIB2 and the measured RSRP, and sends a
random access request to the eNodeB in the selected coverage level. The RSRP threshold
is specified by the RACHCfg.NbRsrpFirstThreshold and
RACHCfg.NbRsrpSecondThreshold parameters.
The UE sends the random access request to the eNodeB with the transmit power
specified by PPRACH. Detailed information about PPRACH can be found in 3.7.2 Uplink
Power Control.
2. Upon receiving the preamble, the eNodeB applies for a temporary cell RNTI (C-RNTI)
and applies for uplink and downlink resources for scheduling. Then, the eNodeB sends a
random access response over the DL-SCH to each UE. The response contains the RA-
preamble identifier, timing alignment information, initial UL grant, and temporary C-
RNTI. One DL-SCH can carry random access responses to multiple UEs.
After sending the preamble, the UE monitors the NPDCCH and waits for a random
access response within a random access response window:
If the UE receives a response containing an RA-preamble identifier which is the
same as the identifier contained in the transmitted random access preamble, the
response was successful, and the RA-preamble identifier is used for uplink
transmission.
If the UE does not receive a response within the random access window or fails to
verify the response, the response fails. In this case, if the number of random access
attempts is smaller than the upper limit, the UE retries random access. Otherwise,
random access fails. The maximum allowable number of random access attempts is
contained in SIB2 and specified by the RACHCfg.preambleTransMax parameter.
The maximum allowable number of random access attempts in a specific coverage
level is specified by the CellRachCECfg.MaxNumPreambleAttempt parameter.
3. The UE sends Msg3 using the resources contained in the random access response. The
UE transmits uplink scheduled data over the uplink shared channel (UL-SCH). The size
of the transport block, which is fixed at 88 bits, is specified in the random access
response. The information in the transport block sent by the UE varies in different
random access scenarios:
Initial RRC connection setup
The RRC Connection Request message is sent by the UE over the CCCH and
contains the cause of RRC connection setup, for example, mt-Access, mo-
Signalling, mo-Data, mo-Exception-Data, or delayTolerantAccess-v1330. This
message also contains the MAC CE consisting of DVI and PHR for requesting
uplink transmission resources and contains the NAS UE_ID.
Other scenarios
At least the C-RNTI of the UE is transmitted.
4. After the UE sends Msg3, a contention resolution timer starts. The contention resolution
timer is specified by the CellRachCECfg.ContentionResolutionTimer parameter and its
length can be obtained from SIB2. Within the timer length, the eNodeB performs
contention resolution at the MAC layer and informs the UE of the resolution through the
C-RNTI on the NPDCCH or through the UE Contention Resolution Identity IE on the
DL-SCH.
The UE monitors the NPDCCH before the timer expires. The UE considers the
contention resolution as successful, notifies upper layers, and stops the timer if both of
the following conditions are met:
The UE obtains the C-RNTI from the NPDCCH.
The UE obtains the temporary C-RNTI over the NPDCCH, the MAC packet data
unit (PDU) is successfully decoded, and the MAC PDU contains information
matching the CCCH service data unit (SDU) transmitted in Msg3.
Once the contention resolution completes, the entire contention-based random access
procedure is complete. If the contention resolution timer expires, the UE considers the
contention resolution to have failed. The UE then performs the entire procedure again, as
long as the number of random access attempts has not reached the maximum allowed. If
the number of random access attempts has reached this maximum, the random access
procedure fails.
For example, if three coverage levels, CL0, CL1, and CL2 are configured, the
CellRachCECfg.PrachRepetitionCount parameter for these three coverage levels is set to
REP_2(REP_2), REP_8(REP_8), and REP_32(REP_32), respectively, and the
RACHCfg.NbCyclicPrefixLength parameter is set to 66DOT7(66DOT7), the PRACH
occupation duration for CL0, CL1, and CL2 is 5.6 x 2 ms, 5.6 x 8 ms, and 5.6 x 32 ms,
respectively. The PRACH start time for CL0 is 8 ms. Accordingly:
l The PRACH start time for CL1 must be at least 48 ms (the sum of the PRACH start time
for CL0 (8 ms) and MAX {40 ms, 5.6 x 2 ms}). The smallest value in the value range
that meets this condition is 64 ms, which is then used as the PRACH start time for CL1.
l The PRACH start time for CL2 must be at least 108.8 ms (the sum of the PRACH start
time for CL1 (64 ms) and MAX {40 ms, 5.6 x 8 ms}). The smallest value in the value
range that meets this condition is 128 ms, which is then used as the PRACH start time
for CL2.
l The PRACH transmission period must be at least the sum of the PRACH occupation
duration and PRACH start time for the highest coverage level. The PRACH occupation
duration is 5.6 x 32 ms, and the PRACH start time is 128 ms, so the PRACH
transmission period must be at least 307.2 ms.
There must be at least a 40 ms difference between the PRACH start time for any
two coverage levels.
The PRACH transmission period must be at least equal to the sum of the PRACH
start time and PRACH occupation duration of any coverage level.
The configurations of the PRACH start time, PRACH transmission period, and
PRACH occupation duration must meet the requirement that the PRACH resources
of all coverage levels do not overlap in a super frame. Specifically, the PRACH
resources allocated to a coverage level cannot overlap with all PRACH resources
allocated to other coverage levels.
Figure 3-23 presents an example of how to determine whether the PRACH resources for
transmission period i of coverage level 0 (CL0i) overlap with those for transmission period j
of coverage level 1 (CL1j).
Calculate the center points of CL0i and CL1j, and the spacing between these two center points
as follows:
Center point of CL0i = PRACH transmission period for CL0 x i + PRACH start time for CL0
+ PRACH occupation duration for CL0/2
Center point of CL1j = PRACH transmission period for CL1 x j + PRACH start time for CL1
+ PRACH occupation duration for CL1/2
Spacing between these center points (L) = Center point of CL1j Center point of CL0i. If
the calculated result of the spacing is a negative value, the absolute value is used for PRACH
resource overlap determination.
l If the spacing is at least half of the sum of PRACH occupation durations for CL0 and
CL1, the PRACH resources for CL0i do not overlap with those for CL1j.
l If the spacing is less than half of the sum of PRACH occupation durations for CL0 and
CL1, the PRACH resources for CL0i overlap with those for CL1j.
Table 3-5 presents an example of how to plan the PRACH start time for different coverage
levels in three co-sited cells. To reduce the interference between NPRACH signals for
coverage level 2 in these three cells, the NPRACH resource overlap time for coverage level 2
must be minimized.
Table 3-5 An example of how to plan the PRACH start time for different coverage levels in
three co-sited cells
Cell PRACH Start Time PRACH Start Time PRACH Start Time for
for Coverage Level 0 for Coverage Level 1 Coverage Level 2
1. The UE sends the eNodeB an RRC Connection Request message containing the cause of
RRC connection setup.
NOTE
l The cause of RRC connection setup is related to NAS procedures and NAS session types. For
details, see 3GPP TS 24.301. When the UE needs to report exception conditions, the cause of
RRC connection setup is "mo-ExceptionData."
l The RRC Connection Request message contains the UE_ID field. If the upper layer provides
the S-TMSI, the UE signals the S-TMSI to the eNodeB. If no S-TMSI is available, the UE
signals a random value ranging from 0 to 240-1 to the eNodeB. In NB-IoT, the international
mobile subscriber identity (IMSI) of the UE is unknown to the eNodeB.
2. The eNodeB sets up the context for the UE.
If the eNodeB receives multiple RRC Connection Request messages from a UE within
an amount of time specified by the RrcConnStateTimer.FilterReptRrcConnReqTimer
parameter, the eNodeB handles only the one that was received last.
Within the window specified by both the UeTimerConst.T300ForNb parameter and the
RrcConnStateTimer.FilterReptRrcConnReqTimer parameter, the eNodeB calculates
the number of RRC Connection Request messages sent by a UE, not including abnormal
transmission scenarios. If the number of RRC Connection Request messages sent by a
UE is greater than the value of the GlobalProcSwitch.RrcConnPunishThd parameter,
the eNodeB responds to the UE with an RRC Connection Reject message containing the
extended wait time IE, the value of which is determined by the
RrcConnStateTimer.ExtendedWaitTime parameter. Upon receiving the message, the
UE sends another RRC Connection Request message only after the extended waiting
time expires.
3. When the control plane CIoT EPS optimization function is enabled, the eNodeB
performs admission and allocates SRB1bis resources to the UE. When the user plane
CIoT EPS optimization function is enabled, the eNodeB performs admission and
allocates SRB1bis and SRB1 resources to the UE.
The eNodeB admits signaling connections.
If the resource allocation is successful, the subsequent steps proceed. If the resource
allocation fails, the eNodeB responds to the UE with an RRC Connection Reject
message.
In the case of overload, the eNodeB responds to the UE with an RRC Connection
Reject message. Upon receiving the RRC Connection Reject message, the UE must
wait a period of time before resending a request. The wait time is specified by the
RrcConnStateTimer.ExtendedWaitTime parameter.
4. The eNodeB sends an RRC Connection Setup message containing SRB1bis resource
configurations to the UE.
5. The UE configures radio resources based on the SRB1bis resource information indicated
by the RRC Connection Setup message, and then sends an RRC Connection Setup
Complete message to the eNodeB. After the eNodeB receives the RRC Connection
Setup Complete message, the RRC connection is set up.
The timer for the eNodeB to wait an RRC Connection Setup Complete message is as
follows:
When the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is set to 0,
ENodeBConnStateTimer.UuMessageWaitingTimer is used.
When the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is set to a
non-zero value, the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is
used.
l The cause of RRC connection resume is related to NAS procedures and NAS session types.
For details, see 3GPP TS 24.301. When the UE needs to report exception conditions, the cause
value is "mo-ExceptionData."
l The RRC Connection Resume Request message contains the ResumeIdentity assigned by the
eNodeB upon RRC connection suspension.
2. The eNodeB searches for the UE context based on the ResumeIdentity.
If the eNodeB receives multiple RRC Connection Resume Request messages from a UE
within the time specified by the RrcConnStateTimer.FilterReptRrcConnReqTimer
parameter, the eNodeB handles only the latest received one.
Within the window specified by both the UeTimerConst.T300ForNb parameter and the
RrcConnStateTimer.FilterReptRrcConnReqTimer parameter, the eNodeB calculates
the number of RRC Connection Resume Request messages received from the same UE,
except in abnormal data transmission scenarios. If the number of RRC Connection
Resume Request messages received from the same UE is greater than the value of the
GlobalProcSwitch.RrcConnPunishThd parameter, the eNodeB responds to the UE
with an RRC Connection Reject message containing the extended wait time IE, the value
of which is determined by the RrcConnStateTimer.ExtendedWaitTime parameter.
Upon receiving the message, the UE sends another RRC Connection Resume Request
message only after the extended waiting time expires.
3. The eNodeB performs admission, and allocates SRB1bis and SRB1 resources to the UE.
The eNodeB admits signaling connections without any judgment.
If the resource allocation is successful, the subsequent steps proceed. If the resource
allocation fails, the eNodeB responds to the UE with an RRC Connection Reject
message.
In the case of overload, the eNodeB responds to the UE with an RRC Connection
Reject message. Upon receiving the RRC Connection Reject message, the UE must
wait a period before resending a request. The wait time is specified by the
RrcConnStateTimer.ExtendedWaitTime parameter.
4. If the eNodeB successfully finds the UE context, the eNodeB sends the UE an RRC
Connection Resume message over SRB1, which contains radio resource configurations
and NextHopChainingCount for the UE to configure radio resources and activate
security configurations.
5. After the configuration is complete, the UE sends an RRC Connection Resume Complete
message with PLMN to the eNodeB. The reception of the RRC Connection Resume
Complete message by the eNodeB indicates that the RRC connection resume procedure
is complete. The timer for the eNodeB to wait for an RRC Connection Resume Complete
message is specified by the ENodeBConnStateTimer.WaitRrcConnSetupCmpTimer
parameter.
For NB-IoT UEs supporting the user plane CIoT EPS optimization function, the eNodeB
preferentially selects an MME supporting this function to process their services. If no such an
MME is available, the eNodeB selects an MME supporting the control plane CIoT EPS
optimization function for service processing. For LTE FDD and LTE TDD UEs, the eNodeB
can select an MME with the MmeCapInfo.NbLteSupportCap parameter set to
SUPPORT(SUPPORT) for service processing.
NB-IoT eNodeBs can select the MME based on the NAS node selection function (NNSF),
configured policy (priority-, capacity-, or load-based), or on cell configurations. For details,
see S1-flex Feature Parameter Description.
Figure 3-26 Data transmission between the UE and EPC after the control plane CIoT EPS
optimization function is enabled
Figure 3-27 Data transmission between the UE and EPC after the user plane CIoT EPS
optimization function is enabled
Data of UEs with CSS1 > Data of UEs with CSS2 > Data of UEs with UE specific search
space (USS)
CSS is short for common search space. For details about the search space, see 3.6
Scheduling.
A signaling connection release procedure can be triggered by the MME or by the eNodeB:
l Triggered by the MME
The MME sends a UE Context Release Command message to the eNodeB when a
service process is complete on the NAS set up between the UE and MME or when the
MME aborts a service.
l Triggered by the eNodeB
The eNodeB sends a UE Context Release Request message to the MME after having
detected an exception, such as the expiry of the UE inactivity timer, a lack of data
transmission or reception on the UE side, or expiry of the Uu message waiting timer or
S1 message waiting timer. The eNodeB then waits for a UE Context Release Command
message from the MME.
The eNodeB performs the following operations during a signaling connection release
procedure:
1. Releases transport resources and initiates RRC connection release over the Uu interface.
2. Sends an RRC Connection Release message to the UE, instructing the UE to release
radio resources.
3. Releases radio resources.
4. Sends a UE Context Release Complete message to the MME, indicating that the
resources have been released.
5. Releases the UE context. Then, the UE switches from the RRC_CONNECTED mode to
the RRC_IDLE mode.
3.6 Scheduling
3.6.1 Definition
Scheduling
NB-IoT uses shared-channel transmissions in which time-frequency resources are
dynamically shared among UEs. eNodeBs perform scheduling to allocate time-frequency
resources for uplink and downlink transmissions.
Schedulers
NB-IoT schedulers are located above the physical layer. The basic function of schedulers is to
allocate system resources to UEs for uplink and downlink transmissions.
The schedulers allow an optimal balance between single-user performance and overall
network capacity.
RU
Uplink resources are measured in resource units (RUs). The durations of RUs with different
subcarrier spacing in multiple scenarios are described in Table 3-1.
MCS
The MCS includes BPSK and QPSK.
l BPSK modulates one bit into a modulation symbol.
l QPSK modulates two bits into a modulation symbol.
High-order modulation modes are used in scenarios with high channel quality. A higher
modulation order (more bits per modulation symbol) helps improve transmission efficiency.
Search Space
The search space for the NPDCCH is classified into the CSS and USS. The CSS is further
classified into CSS1 (CSS for paging) and CSS2 (CSS for RAR/Msg3 retransmission/Msg4).
For details, see section 16.6 of 3GPP TS 36.213 (Release 13).
Data buffer status (DL) The amount of to-be-scheduled data in the Radio Link
Control (RLC) buffer.
Buffer status report (UL) A report to the eNodeB to indicate the amount of data in the
UL buffer of the UE.
Channel state inputs indicate that an uplink scheduler schedules resources for UEs and
allocates resources to UEs based on signal to interference plus noise ratios (SINRs), which
indicate uplink channel conditions. The eNodeB obtains SINRs by measuring demodulation
reference signals (DMRSs).
MCS/Repetition selection The scheduler determines the MCS for each UE and
repetition counts based on the inputs.
The MCS selection, repetition count selection, and resource allocation apply to the NPUSCH,
UCI, and Msg3.
UE Selection
The UEs to be scheduled are queued in descending order of service priority as follows:
UEs with CSS1 > UEs with CSS2 > UEs with the USS
SINR Adjustment
SINR indicates uplink channel quality, based on which NB-IoT selects MCSs and repetition
counts for uplink scheduling. Due to the impact of channel fading on signals, the SINR at the
reporting time is significantly different from that at the scheduling time. Therefore, the SINR
needs to be adjusted based on the HARQ-ACK/HARQ-NACK feedback to uplink data.
l If the current channel quality is lower than that required by the MCS the scheduler
selects, the block error rate (BLER) of data packets increases. The eNodeB then
decreases the SINR based on the HARQ-NACK feedback.
l If the current channel quality is higher than that required by the MCS the scheduler
selects, the BLER of data packets decreases. The eNodeB then increases the SINR based
on the HARQ-ACK feedback.
l When the eNodeB cannot acquire the measured SINR, MCSs and repetition counts are
specified by NbCellUlSchCEAlgo.UlInitialMcs and
NbCellUlSchCEAlgo.UlInitialTransRptCount, respectively.
l When the eNodeB has acquired the measured SINR, the eNodeB selects appropriate
MCSs and repetition counts based on the SINR.
NOTE
If a UE supports only single-tone transmission and the MCS index is set to or reselected as 11 or 12, the
MCS index actually selected will be 10.
Resource Allocation
If a cell serves more than one UE, the amount of available NPUSCH/UCI resources is equal
to the amount of uplink resources across the entire channel bandwidth minus the amount of
resources occupied by the NPRACH and guard bandwidth.
The amount of time available for uplink scheduling is determined by the duration of the
NPUSCH, UCI, and Msg3 scheduling, as described in the following table.
NPUSCH Determined by the buffer status and SINR (including adjusted SINR)
scheduling after filtering.
Msg3 scheduling Determined by the coverage level, MCS, and repetition count.
Resource allocation involves allocating resources for NPUSCH scheduling, UCI scheduling,
and Msg3 scheduling.
NPUSCH Scheduling
The eNodeB uses the NPDCCH pre-allocation results, defined uplink timing constraints, start
position constraints, and uplink DTX constraints to determine the available NPUSCH start
position and duration, and allocates NPUSCH resources to UEs for scheduling.
UCI Scheduling
Based on the NPDSCH pre-allocation results, defined downlink timing constraints, start
position constraints, and uplink DTX constraints, the eNodeB determines the available UCI
start position and UCI duration, and allocates NPUSCH resources to UEs for downlink
scheduling.
Msg3 Scheduling
Based on the NPDCCH scheduling results, defined uplink timing constraints, start position
constraints, and uplink DTX constraints, the eNodeB determines the available Msg3 start
position and NPUSCH duration, and allocates NPUSCH resources to UEs for scheduling.
l Timing constraints
In accordance with 3GPP TS 36.213 (Release 13), the interval between the Msg3 start
position and Random Access Response (RAR) end position is greater than or equal to 12
ms.
l Start position constraints
In accordance with 3GPP TS 36.212 (Release 13), the relationship between the
NPUSCH start position and end position for Msg3 scheduling in the RAR message (Sn)
meets one of the following formulas:
Start position = Sn + 1 + 12
Start position = Sn + 1 + 16
Start position = Sn + 1 + 32
Start position = Sn + 1 + 64
l Uplink DTX constraints
In accordance with section 10.1.3.6 in 3GPP TS 36.211 (Release 13), the Msg3
transmission stops for 40 ms after each data transmission of 256 ms. During the 40 ms,
uplink and downlink scheduling for this UE is not allowed, but uplink data for other UEs
can be transmitted.
l In asynchronous HARQ retransmissions, a UE sends HARQ feedback four TTIs after the
initial transmission of the eNodeB, and the eNodeB retransmits the data at least four
TTIs after receiving a NACK.
l In adaptive HARQ retransmissions, the retransmitted TBS is the same as the initially
assigned TBS.
UE Selection
The UEs to be scheduled are queued in descending order by procedure priority as follows:
UEs with CSS1 > UEs with CSS2 > UEs with the USS
l In LTE in-band deployment mode, if the MCS index is set or adjusted to 11 or 12, the MCS
index actually selected will be 10. Therefore, it is recommended that the MCS index be not set
to 11 or 12 in LTE in-band deployment mode.
l When COVERAGE_EXTENSION_SWITCH under the CellDlschAlgo.NbCellAlgoSwitch
parameter is set to Off, the MCS index will be 0 and the repetition count will be 1.
Resource Allocation
The amount of time allowed for downlink scheduling is determined by the expected allocated
number of RUs based on the UE's buffer status, coverage level, and repetition count.
NPDCCH scheduling protocol constraints
To determine the available NPDSCH start position and NPDSCH duration, and to allocate
NPDSCH resources to UEs, the eNodeB uses the NPDCCH scheduling results and the
following:
l Downlink timing constraints: In accordance with 3GPP TS 36.213 (Release 13), the
interval between the NPDSCH start position and DCI end position must be greater than
or equal to 4 ms.
l Start position constraints: In accordance with section 6.4.3.1 of 3GPP TS 36.212
(Release 13), the relationship between the NPDSCH start position and the DCI end
position (Sn) must be relative to the maximum repetition count, as described in the
following table.
The start position for a paged UE cannot be occupied so that the UE can receive paging
messages. To ensure successful paging, the following configuration requirements must be
met:
l When the PCCHCfg.MaxNumRepetitionForPaging parameter is set to
NULL(Invalid), the number of the enumerated value of the PCCHCfg.NbForNbIoT
parameter must be greater than or equal to that of the
CellPdcchCECfg.PdcchMaxRepetitionCnt parameter. For example, when the
PCCHCfg.NbForNbIoT parameter is set to HALF_T~3, 3 is the number of this
enumerated value.
l When the PCCHCfg.MaxNumRepetitionForPaging parameter is not set to
NULL(Invalid), the number of the enumerated value of the PCCHCfg.NbForNbIoT
parameter must be greater than or equal to that of the
PCCHCfg.MaxNumRepetitionForPaging parameter.
The NRS power is indicated by the energy per resource element (EPRE) and specified as
follows:
l If this option is selected, calculate the pilot power broadcast in SIB2 as follows:
a. Set the wideband transmit power at each antenna port by using the
CellChPwrCfg.AntOutputPwr parameter.
b. Set the proportion of NB-IoT cell output power (OutputPowerRate) by using the
eNBCellRsvdPara.RsvdU16Para8 parameter.
c. Calculate the gain (, dB) of amplified power relative to un-amplified power at the
antenna port:
= 10lg(CellChPwrCfg.AntOutputPwr x OutputPowerRate) - RruOutputPwr
where
CellChPwrCfg.AntOutputPwr's unit is W, which needs to be converted into mW.
RruOutputPwr (dBm) is the maximum transmit power at the antenna port calculated
based on NRSs.
OutputPowerRate:
If the eNBCellRsvdPara.RsvdU16Para8 parameter value is not 0, it is used in the
preceding formula.
If the eNBCellRsvdPara.RsvdU16Para8 parameter value is 0, then:
n In LTE in-band deployment scenarios, the proportion of NB-IoT cell output
power is used in the preceding formula. The eNodeB automatically calculates
this proportion and the proportion of LTE FDD cell output power when the
LTE FDD cell meets the following conditions:
The AntRsPwrSwitch option of the CellAlgoSwitch.RepeaterSwitch
parameter of the LTE FDD cell is selected.
The eNBCellRsvdPara.RsvdU16Para8 parameter of the LTE FDD cell is set
to 0.
n In other scenarios, the value 1000 is used in the preceding formula.
d. Calculate the pilot power broadcast in SIB2.
AntReferenceSignalPwr (dBm) = PDSCHCfg.ReferenceSignalPwr +
1 0, 1, 2, 3, and 4 5 and 6 2
2 0, 1, 2, 3, and 4 5 and 6 4
l When there are two cell antenna ports, the RE power is half of the NRS power.
In standalone and LTE guard band deployment modes, the following formulas are true:
l When there is one cell antenna port:
In LTE in-band deployment mode, the first three symbols of each subframe must be punctured
for LTE FDD PDCCH, and do not consume power in NB-IoT cells.
Four REs of certain OFDM symbols in each subframe must be punctured due to its
coexistence with the CRS in an LTE FDD cell. They do not consume NB-IoT cell power. The
symbols occupied by the CRS, with different LTE FDD antenna configurations, are described
in the following table.
1 and 2 0, 4, 7, and 11
4 0, 1, 4, 7, 8, and 11
The actual transmit power of symbols punctured by the CRS in NB-IoT cells is as follows:
The transmit power of other symbols is calculated in the same way as that in standalone and
LTE guard band deployment modes.
NOTE
l In LTE in-band deployment mode, the transmit power including that of LTE FDD CRS is
described in the following table.
No NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg9) dBm
2 Yes NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg8 3) dBm
No NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg7 3) dBm
No NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg9) dBm
2 Yes NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg8 3) dBm
No NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg7 3) dBm
where
and
where
PO_PRE is the target power expected by the NPRACH and is specified by the
RACHCfg.PreambInitRcvTargetPwr parameter.
For details about the maximum allowable number of RRC_CONNECTED UEs in a cell and that
supported by main control boards and baseband boards, see 3900 Series Base Station Technical
Description.
3. If the admission fails, the involved UE attempts to preempt resources allocated to other
UEs. High-priority UEs are allowed to preempt the resources allocated to low-priority
UEs when NbUeNumPreemptSwitch under the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is turned on. UE priorities are
determined based on the RRC connection setup cause. The following lists the RRC
connection setup causes in the descending order of priority:
a. Mobile Originated Exception Data (mo-Exception-Data)
b. Paging
c. Mobile Terminated Access (mt-Access)
d. Mobile Originated Signaling (mo-Signaling)
e. Mobile Originated Data (mo-Data)
f. delayTolerantAccess-v1330
For services whose value of "Pre-emption Vulnerability" in the ARP is "not pre-
emptable", the allocated resources cannot be preempted.
4. When NB-IoT and LTE FDD cells are co-sited, NB-IoT and LTE FDD cells share RRC
resources. When no idle RRC resources are available, LTE FDD UEs initiating RRC
connection requests can preempt the RRC resources occupied by NB-IoT UEs if
ENODEBALGOSWITCH.LTEPreemptNbSwitch is turned on.
LTE FDD UEs preferentially preempt the resources occupied by low-priority NB-
IoT UEs. NB-IoT UEs with the RRC connection setup cause of
delayTolerantAccess-v1330 are considered to have the lowest priority, and their
resources are preempted prior to other UEs. NB-IoT UEs whose value of "Pre-
emption Vulnerability" is "not pre-emptable" are the last choice for resource
preemption.
To prevent excessive RRC resource preemption from affecting NB-IoT UE access,
a minimum number of RRC_CONNECTED UEs is reserved for NB-IoT. This
minimum number equals the product of
ENodeBNbPara.NbRsvMinUserNumRatio and the maximum number of
RRC_CONNECTED UEs supported by the eNodeB. When the number of
RRC_CONNECTED UEs in NB-IoT is less than or equal to this minimum number,
LTE FDD UEs are not allowed to preempt the RRC resources occupied by NB-IoT
UEs.
Congestion Control
Congestion control consists of backoff and access barring.
l Backoff
A large number of random access requests lead to a high load or even a reset of the
eNodeB. Random access flow is limited by controlling the number of preambles to be
processed. The eNodeB sends different backoff time indications to UEs based on the
NPRACH congestion status. The UE initiates a new network access request at a random
time based on the backoff time indication in the received message, so as to avoid
conflicts. The backoff function is controlled by BackOffSwitch under the
CellAlgoSwitch.RachAlgoSwitch parameter.
If some UEs on the live network do not support the maximum backoff index 12 defined
in 3GPP TS 36.321 (Release 13), operators must also turn on PreambleSchEnhSwitch
under the CellAlgoSwitch.UlSchExtSwitch parameter.
l Access barring
To protect the existing system and UEs from the possible impact of a sudden spike in UE
access, the eNodeB implements access barring based on dynamic load.
Access barring is defined in 3GPP TS 36.331 (Release 13). When a cell or all the MMEs
connected to an eNodeB are congested, the eNodeB broadcasts access class control
parameters in SIB14. UEs then determine whether to initiate access requests in the
current cell based on the received parameters. The EABAlgoSwitch option of the
CellAlgoSwitch.MTCCongControlSwitch parameter specifies whether to enable this
function.
The eNodeB can use the CellEABAlgoPara.ABForExceptionData parameter to control
whether NB-IoT UEs with the access cause of mo-ExceptionData can access the
network, and can use the ABForSpecialAC parameter to indicate NB-IoT UEs with
access classes 11 to 15 can initiate the access.
The cell congestion status is determined based on flow control status or CPU load,
depending on the value of the eNodeBFlowCtrlPara.DynAcBarPolicyMode parameter.
The access barring type is specified by the CellEABAlgoPara.EABCategory parameter.
UE access to the network in a given measurement period is allowed or barred based on
the following conditions:
The measurement period starts when the access barring algorithm switch is turned on.
The length of the measurement period is specified by
CellEABAlgoPara.EABStatPeriod parameter.
The triggering condition for access barring is as follows:
Proportion of cell congestion duration CellEABAlgoPara.EABTriggerThd
If this triggering condition is met, UEs belonging to certain access classes are
barred from accessing the network for a duration specified by the
CellEABAlgoPara.EABStatPeriod parameter.
The leaving condition for access barring is as follows:
Proportion of cell congestion duration CellEABAlgoPara.EABCancelThd
If the leaving condition is met for a number (N) of consecutive measurement
periods, UEs belonging to certain access classes are allowed to access the network.
N is specified by the CellEABAlgoPara.EABCancelCondSatiPeriod parameter.
UEs read the AB messages in the SIB14 period. The SIB14 period is specified by
the CellSiMap.NbSib14Period parameter.
In Figure 3-33 (parameter values from Table 3-6 are used as examples):
a. When the proportion of cell congestion within 20s is greater than 90%, or if all the
MMEs connected to the eNodeB deliver overload messages, the eNodeB will send
an SIB14 message to the UE.
b. To ensure that the UE can receive the SIB14 message, the eNodeB must send
paging messages or NPDCCH messages to notify the UE of system message
changes. After the reception of a change notice, the UE obtains ab_Enabled from
the MIB message. If access barring is enabled, the UE obtains a new AB message in
the SIB14 period.
c. UEs belong to access class 0, based on the bit information in the AB message, are
barred from accessing the network for a period of time equal to the measurement
period.
d. If the leaving condition is met for two consecutive periods (the proportion of cell
congestion within 20s is smaller than 70%), the eNodeB will not send the SIB14
message and stop access barring on UEs.
Overload Control
Overload control is implemented when there is a sudden spike in external services. NEs
control input and output flows to prevent overload and improve equipment stability. Overload
control improves NE stability by reducing the possibility of NE resets. It can also reduce the
risk of a decreased access success rate and provide a more stable user experience.
l MME-overload-triggered overload control
The objective of MME-overload-triggered overload control is to relieve the impact of
MME overload caused by a large number of UEs accessing the network.
When an MME is overloaded, it sends an OVERLOAD START message to the eNodeB,
indicating that the eNodeB needs to start flow control. The eNodeB then limits UE
access based on their RRC connection setup causes. When MME overload is relieved, it
sends an OVERLOAD STOP message to the eNodeB indicating that the eNodeB should
stop flow control. For details, see 3GPP TS 36.413.
l Random access flow control
A large number of random access requests lead to a high load or even a reset of the
eNodeB. Random access flow is limited by controlling the number of preambles to be
processed. The eNodeB adaptively adjusts the number of preambles to be processed
based on the CPU usage of the BBP control plane or the congestion status of air interface
resources. If the air interface is congested in a cell, the random access flow control is
controlled by UlRaUserSchOptSw under the CellAlgoSwitch.UlSchSwitch parameter.
Application Description
A sudden spike in UE access leads to cell air interface resource congestion, causes difficulty
in UE access, and degrades network performance. Under these circumstances, operators are
advised to:
l Enable the backoff function.
l Enable the access barring function.
l Enable the random access flow control function.
l Turn on ExtendedwaittimeSwitch under the CellAlgoSwitch.MTCCongControlSwitch
parameter to allow the eNodeB to include the extendedWaitTime IE in RRC Connection
Release messages. This IE delays UE access and thereby relieves the resource
congestion over the air interface.
3.9 DRX
DRX is a technology in which a UE can switch between active and sleep states to save power.
When the UE needs to receive downlink data, the UE turns on its receiver and enters the
active state. When there is no need to receive downlink data, the UE turns off its receiver and
enters the sleep state.
On Duration
When the UE is in DRX connected mode, it does not always keep its receiver off. It
periodically turns on its receiver and monitors the NPDCCH for incoming signaling for a
consecutive period. This consecutive period is called On Duration, which is defined by the
CellDrxPara.NbOnDurationTimer parameter.
DRX Cycle
A DRX cycle is the interval between two On Durations. A DRX cycle consists of an On
Duration and a possible period of sleep time, as shown in Figure 3-34.
NOTE
The On Duration Timer will stop after certain conditions are met.
The DRX period can be divided into active time and sleep time based on UE behavior. NB-
IoT supports only the long DRX cycles. The long NB-IoT DRX cycle is specified by the
CELLDRXPARA.NbLongDrxCycle parameter, which is set as follows:
l This parameter is set to SF256 in versions earlier than V100R012C10SPC210.
l This parameter is set based on the network plan in V100R012C10SPC210 and later
versions.
Active Time
In active time, the UE turns on its receiver and monitors the NPDCCH. Active time is equal
to On Duration plus other possible periods during which the UE needs to turn on its receiver,
for example, when other DRX timers are running. DRX timers include the DRX Inactivity
Timer, DRX Retransmission Timer, and DRX UL Retransmission Timer.
Sleep Time
During a DRX cycle, if a UE is not active, it is in sleep mode. A UE in sleep mode does not
monitor the NPDCCH, but it can still transmit and receive NPUSCH/NPDSCH messages
scheduled during active time. When no data is transmitted, the UE can turn off its receiver.
NOTE
HARQ RTT N/A Functio This timer specifies the interval between
Timer n the initial downlink data transmission and
the first downlink HARQ retransmission.
This timer is used to determine when to
start the timer related to a prolonged DRX
active time.
eDRX UEs monitor the paging channel in the PTW indicated by the PF and PO. The
monitoring mechanism is the same as that for DRX UEs described in 3.4.8 Paging.
1. The eNodeB includes the HSFN in the MIB and in SIB1. An HSFN lasts 10.24s, which
is the unit of an eDRX cycle.
2. The UE obtains the HSFN and determines whether to use DRX or eDRX based on its
own capabilities. If a UE uses eDRX, it includes the eDRX cycle length in an Attach
Request/TAU Request message sent to the MME.
3. If the MME accepts the eDRX request, it configures a different eDRX cycle and the size
of the PTW for the UE according to the predefined policy, and includes the information
in an Attach Accept/TAU Accept message to the UE. If the MME rejects the eDRX
request, the UE uses the DRX paging mechanism.
4. The UE and MME stores the "Extended DRX Parameters" after negotiation, and uses the
stored parameter values as the eDRX cycle later.
5. When an MME has a paging message for the UE, it calculates the HSFN and paging
hyperframe (PH) for the UE based on the negotiated eDRX cycle.
6. The MME sends the paging message to the eNodeB before the PH time for the UE
arrives.
7. On receiving the paging message, the eNodeB uses the eDRX cycle carried in the
message to calculate the time of the HSFN and PH. The eNodeB also calculates the PO
for the UE based on the configured paging cycle, and sends the paging message to the
UE at the calculated time.
The UE calculates the paging message delivery time the same way the eNodeB does, and
monitors and receives the paging message during this time.
When Idle Mode eDRX is enabled, the UE periodically monitors the paging channel and can
receive MT services. In traditional power saving mode, however, the UE cannot receive MT
services unless it proactively accesses the network. It will take a long time generally for a UE
to proactively access the network, depending on the mobile-originated (MO) data reporting
period and TAU period. Therefore, Idle Mode eDRX is suitable for machine-to-machine
(M2M) services that require short delays for downlink MT services (for example, tracking the
locations of children and elderly people).
parameter. When this feature is enabled, uplink and downlink scheduling selects the repetition
count based on the UE signal quality and coverage level. In this way, UEs in coverage
enhancement areas can access the network normally. It is recommended that the
Cell.CoverageLevelType parameter be adjusted when this feature is enabled. More
information about parameter adjustment can be found in 8.6 Parameter Optimization.
In LTE in-band deployment or LTE guard band deployment, UEs in an area of coverage level
2 may fail to camp on a cell even when the minimum receive level of the cell is set to a very
small value. To enable such UEs to camp on the cell, operators can reduce the actual
minimum receive level of the cell by configuring the delta-RxLevMin, which is specified by
the ENBCELLRSVDPARA.RsvdU8Para17 parameter.
3.12 Multi-tone
This section describes the optional feature MLOFD-120230 Multi-tone.
According to 3GPP TS 36.211 (Release 13), NB-IoT supports single-tone and multi-tone
transmissions in the uplink. Single-tone transmission is mandatory for UEs, while multi-tone
transmission is optional. There are three types of multi-tone transmission: 3-tone, 6-tone, and
12-tone. This means that an eNodeB can allocate 3, 6, or 12 subcarriers (15 kHz each),
respectively, at a time for uplink data transmission. In areas with favorable coverage, multi-
tone transmission increases data rates and reduces the transmission delay and power
consumption for uplink data transmission.
Multi-tone is controlled by MULTITONE_SWITCH under the
CellAlgoSwitch.NbCellAlgoSwitch parameter. Figure 3-39 shows the multi-tone triggering
procedure.
1. When multi-tone is enabled, the eNodeB sends SIB2 carrying the "nprach-
SubcarrierMSG3-RangeStart-r13" field to a multi-tone-capable UE, notifying the UE of
the start position of NPRACH resources.
2. The multi-tone-capable UE uses the allocated NPRACH resources to initiate a random
access request.
3. The eNodeB allocates multi-tone Msg3 resources to the UE if the number of repetitions
of NPRACH information is less than or equal to 32 times. Otherwise, the eNodeB
allocates single-tone Msg3 resources to the UE.
4. If the UE supports multi-tone transmission, it uses the allocated Msg3 resources to send
the eNodeB an RRC Connection Request message carrying the "multiToneSupport"
field.
5. The eNodeB determines whether the UE supports multi-tone transmission based on the
received information, and allocates multiple subcarriers to the multi-tone-capable UE for
uplink data transmission. The eNodeB determines the number of subcarriers to be
allocated based on factors such as the power headroom report (PHR), initial offset of the
resources to be allocated, and whether the resources to be allocated conflict with
NPRACH resources.
6. The UE uses the allocated uplink resources for uplink data transmission and uplink
scheduling.
NOTE
l The length of Msg3 is always 88 bits, and the scheduling delay of Msg3 is almost the same,
regardless of whether single-tone transmission or multi-tone transmission is used.
l NPRACH resources consist of two parts: One is used by multi-tone-capable UEs to send random
access requests and the other used by single-tone-capable UEs to send random access requests. The
access capability of single-tone-capable UEs is decreased. Therefore, in the current version "nprach-
SubcarrierMSG3-RangeStart-r13" is fixed at value 1, which means that Msg3 always uses single-
tone transmission.
l The eNodeB uses only Msg3 to determine whether a UE supports multi-tone transmission and to
notify the UE of resources for uplink data transmission.
3.13.1 Overview
Multiple-antenna reception is a technique in which signals received by multiple antennas are
combined using a special algorithm. Multiple-antenna reception must be supported by both
the eNodeB and UEs. The sub-sections that follow describe how multiple-antenna reception
works on the eNodeB side.
The radio channel from the transmitter to the receiver may experience time-varying deep
fading of 10 dB to 20 dB due to its fading characteristics, which will lead to SINR
fluctuations at the receiver. If the receiver uses multiple antennas for data reception, the
combined signals experience a lower probability of deep fading than the signals received by a
single antenna, because deep fading is not likely to occur on the signals received by all of the
antennas at once. The white noise received by the different antennas is random, and therefore
the power of the combined noise remains unchanged. However, the energy of the combined
signal increases several-fold.
Diversity Gains
Diversity gains are subject to the diversity orders of spatial channels. If the TX and RX
antenna channels are mutually orthogonal, and signals from all TX antennas are the same, an
MxN (M TX antennas, and N RX antennas) system delivers theoretical diversity gains of MxN
compared with the 1x1 system. The diversity order (MxN) theoretically represents the fault
tolerance capability of a spatial channel. Theoretically, the fault tolerance capability of an
MxN system is MxN times that of a 1x1 system.
Diversity gains indicate improved SINR stability and signal reliability at the receiver end.
Array Gains
Compared with a 1x1 system, a 1xN system and an Mx1 system bring array gains of 10 lg(N)
dB and 10 lg(M) dB, respectively.
Array gains indicate higher SINR and better signal quality at the receiver end, as shown in
Figure 3-41.
y = W (Hx + N)
Signal combining, especially the calculation of the weights to be applied to each antenna, is
key to receive diversity.
MRC must meet certain equalization criterion, for example, a minimum mean square error
(MMSE) or maximum signal to interference noise ratio (MSINR). In the current version,
MMSE MRC is used.
Both MMSE and MSINR require the calculation of Ruu, a covariance matrix of interference
and noise power. For MRC, Ruu is a diagonal matrix and only the entries on the main
diagonal need to be calculated. For IRC, Ruu is not a diagonal matrix and all the entries in the
matrix need to be calculated.
Concepts
l MMSE
MMSE is the minimum mean square error between the actual and estimated values of a
TX signal. The estimated value is obtained based on RX signals.
l White noise
White noise is noise whose PSD is evenly distributed over the entire frequency domain.
l Colored interference
Colored interference is interference whose PSD is not evenly distributed over the entire
frequency domain.
Figure 3-43 uses MMSE as an example to show the general working principles of a receiver.
TX signal x0 and interference Ik are transmitted through their radio channels hk(p),
superimposed at the RX antennas, added to white noises np, and converted into RX signals rp.
The combined signal is calculated as follows:
y=WxR
Different receivers generate different weights (W) and perform equalization and combination
in different ways depending on these weights.
An MMSE MRC receiver can generate the weights (w(p)) that minimize the mean square error
between the combined signal (y) and the original signal (x0) when interference is similar to
white noise.
Assume that the original signal's power is Es, and the original signal, noise, and interference
are independent of each other. Then, the RX antenna weights (W) are calculated as follows,
where Ruu is a diagonal matrix of the interference and noise power measured by the eNodeB:
For MRC, assume that a covariance matrix of total estimated white noise and interference on
RU i is equal to Ruu. If the entries not on the diagonal are set to zero for MRC, Ruu can be
expressed as follows:
Then, the output signals after MRC processing can be expressed as follows:
where
R(i) indicates the RX signal vector.
H(i) indicates the channel vector.
3.14.1 Overview
Multiple-antenna transmission is a technique in which signals transmitted using multiple
antennas are processed using a special algorithm. Multiple-antenna transmission must be
supported by the eNodeB, but that is not necessary for UEs. This section describes multiple-
antenna transmission on the eNodeB side.
NOTE
Antenna ports mentioned in this document are logical ports used for transmission. They do not have
one-to-one relationship with physical antennas. Signals on one antenna port can be transmitted over one
or more physical antennas.
The following figure shows signal processing at the transmitter when SFBC is enabled.
By transmitting the copies of signals x1 and x2 over different antenna ports and subcarriers,
SFBC brings diversity gains.
4 Related Features
This chapter describes the relationships between NB-IoT features and other features.
Impacted Features
Feature ID Feature Description
Name
LOFD-001070 Symbol When NB-IoT and LTE FDD cells share the same power
Power amplifier (PA), Symbol Power Saving provides fewer
Saving gains in LTE FDD cells. This is because the NB-IoT and
LTE FDD pilot symbols are staggered from each in the
time-domain and the PSS, SSS, MIB, and SIBs of NB-
IoT cells occupy more symbols in the time domain than
those of LTE FDD cells, reducing the chances of basic
symbol power saving.
Impacted Features
Feature ID Feature Name Description
LBFD-001003 Scalable Bandwidth LTE guard band deployment requires that the
LTE FDD cell bandwidth be at least 10
MHz.
LOFD-001070 Symbol Power When NB-IoT and LTE FDD cells share the
Saving same power amplifier (PA), Symbol Power
Saving provides fewer gains in LTE FDD
cells. This is because the NB-IoT and LTE
FDD pilot symbols are staggered from each
in the time-domain and the PSS, SSS, MIB,
and SIBs of NB-IoT cells occupy more
symbols in the time domain than those of
LTE FDD cells, reducing the chances of
basic symbol power saving.
Impacted Features
Feature ID Feature Name Description
LOFD-003029 SFN
LOFD-001070 Symbol Power Saving When NB-IoT and LTE FDD cells share
the same power amplifier (PA), Symbol
Power Saving provides fewer gains in LTE
FDD cells. This is because the NB-IoT and
LTE FDD pilot symbols are staggered
from each in the time-domain and the PSS,
SSS, MIB, and SIBs of NB-IoT cells
occupy more symbols in the time domain
than those of LTE FDD cells, which then
reduce the chances of basic symbol power
saving.
Impacted Features
None
Impacted Features
None
Impacted Features
None
Before using this feature, read 1.2 Disclaimer for Trial Features.
Prerequisite Features
Feature ID Feature Name Description
MLBFD-12000228 RRC Connection The Data over User Plane feature allows NB-
Management IoT service data to be carried on DRBs
established for it. It also enables the eNodeB
to preferentially select an MME supporting
the user plane CIoT EPS optimization
function for NB-IoT UEs.
MLBFD-12000203 Support of NB-IoT The Data over User Plane feature allows NB-
UE IoT service data to be carried on DRBs
established for it. This feature requires that
UEs support the user plane CIoT EPS
optimization function.
Impacted Features
None
Impacted Features
None
Impacted Features
None
MLBFD-12000237 Cell Selection and Re- UEs in the RRC_IDLE mode can
selection initiate services after camping on a
cell.
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
Impacted Features
Feature ID Feature Name Description
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
Impacted Features
Function Name Description
Impacted Features
None
Impacted Features
None
Impacted Features
Feature ID Feature Description
Name
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
5 Network Impact
This chapter describes the impact of NB-IoT features on network capacity and performance.
Network Performance
None
Network Performance
In LTE guard band deployment, if the NB-IoT cell shares the same RF modules with the LTE
FDD cell, the power allocation for LTE FDD and NB-IoT cells changes because the PSD of
NB-IoT is high. Specifically, after the NB-IoT cell is activated, the average throughput and
average MCS index may decrease for UEs at the center of the LTE FDD cell, and the residual
block error rate (RBLER) may increase. If DL 256QAM is enabled, the peak throughput of
UEs using the 256QAM modulation scheme at the center of the LTE FDD cell is 1.5 times
that of UEs using the 64QAM modulation scheme at the center of the LTE FDD cell.
NB-IoT deployment on LTE FDD in-band RBs reduces the RBs available to an LTE FDD cell
because RBs need to be reserved for NB-IoT deployment and for guard bandwidth.
l If NB-IoT uplink and downlink are deployed on RBs recommended in 3.2.3 LTE In-
band Deployment, the theoretical LTE FDD RBs and single-UE peak data rate are
decreased, as described in Table 5-1.
l If NB-IoT uplink and downlink are not deployed on recommended RBs, fragmented RBs
exist, and consequently more RBs may be affected in an LTE FDD cell. This is because
the protocol-defined uplink and downlink RB allocation principles (allocation of
continuous uplink carrier resources, uplink 2/3/5 allocation principles, symmetrical
PUCCH resource allocation, and downlink RBG allocation principles) do not support the
allocation of some fragmented RBs. For details on LTE FDD uplink and downlink RB
allocation, see Scheduling Feature Parameter Description.
l If NB-IoT uplink is not deployed on an edge RB, LTE FDD cell uplink RB resources
become discontinuous, and consequently the single-UE peak throughput decreases (the
single UE scheduling requirements for the PUSCH stipulated in 3GPP TS 36.211 are
met). The throughput decrease is related to the position of the RB reserved for NB-IoT
uplink deployment. The minimum single-UE peak throughput decrease equals the
proportion of the RBs reserved to the total cell bandwidth. The maximum single-UE
peak throughput decrease can reach 50%.
Table 5-1 Decreases in theoretical LTE FDD RBs and single-UE peak data rate each
time an RB is reserved
System Theoretical Downlink Theoretical Uplink Single-
Bandwidt Downlink Single-UE Uplink RB UE Peak Data
h RB Loss Peak Data Loss Rate Loss
Rate Loss
If there are multiple online UEs in an LTE FDD cell, the average uplink and downlink
experienced rates are affected each time an RB is reserved. Table 5-2 describes the detailed
impact.
Table 5-2 Impact on average uplink and downlink experienced rates each time an RB is
reserved
System Bandwidth Average UE Experienced Rate Loss
10 MHz 8% to 20%
15 MHz 5% to 15%
20 MHz 3% to 10%
Table 5-1 and Table 5-2 describe the impact of RB reservation on LTE FDD cell capacity and
average uplink and downlink experienced rates in a typical scenario, that is, in a scenario
where the following conditions are met:
l The inter-site distance is 500 meters.
l Each cell has 10 online UEs.
l The network load is about 20%.
l The ratio of large-sized packets to small-sized packets is 1:4.
In any of the following scenarios, the impact on LTE FDD cell capacity and average uplink
and downlink experienced rates is greater than that described in the tables above:
Different configurations of scheduling parameters for LTE FDD common messages such as
system messages and RAR messages result in different proportions of common message
overhead in the downlink and different impacts on resource allocation. A shorter scheduling
period for LTE FDD system messages or PRACH resources leads to a greater downlink
common message overhead and a lower peak throughput. A smaller LTE FDD system
bandwidth results in a greater impact on the downlink peak throughput.
Network Performance
l Impact of LTE FDD on NB-IoT
In LTE in-band deployment, the RB carrying NB-IoT is interfered with by the adjacent
channel leakage of LTE FDD uplink signals. Consequently, the overall noise floor
increases, and the NB-IoT coverage shrinks. The interference is related to the uplink
signal reception strength in the LTE FDD cell, and the adjacent channel leakage ratio
(ACLR) of LTE FDD UEs.
l Impact of NB-IoT on LTE FDD
Each NB-IoT cell occupies one LTE FDD PRB, and an extra uplink PRB may be
reserved as the guard band. Consequently, all existing LTE FDD KPIs are affected. The
impact on KPIs is less than the proportion of the PRBs reserved for NB-IoT deployment
to the entire LTE FDD cell bandwidth.
The 3.75 kHz subcarrier used by the NPRACH causes interference on adjacent LTE
FDD RBs, leading to an increase in the LTE BLER. The influence depends on the uplink
signal strength and ACLR of NB-IoT UEs.
NB-IoT deployment on LTE FDD in-band RBs results in fragmented allocable resources
because RBs need to be reserved for NB-IoT deployment and for the guard band. When
there are multiple online UEs in the LTE FDD cell, the average number of UEs
scheduled at a time may increase. Consequently, the average interference level in the
LTE FDD cell and average uplink and downlink MCS indexes fluctuate, and the CCE
usage improves. The interference and MCS index fluctuation or CCU usage
improvement is related to the position of the reserved RB and locations of UEs to be
scheduled. In addition, the BLER, throughput, and MCS index may vary depending on
different scenarios. The related non-KPI indexes may also change.
In addition, in LTE in-band deployment, certain symbols of the downlink RB allocated to
NB-IoT must be reserved for LTE FDD PDCCH, and therefore, if time synchronization
is not achieved, NB-IoT creates interference on the PDCCH. When the NB-IoT network
load reaches 100%, the PDCCH receives interference signals 6 dB stronger than before,
and the BLER/CFI/CCE level of the PDCCH is affected. The 6 dB interference increase
in a single RB has only very little impact on the PDCCH that is included in all RBs. In
heavy load scenarios, the theoretical impact (relative value) of the interference increase
is estimated to be 10 x log (1 + (4 x Number of reserved RBs/Total number of RBs)) dB.
The impact of the interference increase on the BLER varies depending on the scenario.
Specifically, the BLER may be increased by 1% to 5%.
As NB-IoT shares the same RF modules with LTE FDD, the power allocation for LTE
FDD and NB-IoT changes because the PSD of NB-IoT is high. Specifically, after an NB-
IoT cell is deployed on the same RF module with the corresponding LTE FDD cell, the
average throughput and average MCS index may decrease for UEs at the center of the
LTE FDD cell, and the RBLER may increase. If the DL 256QAM feature is enabled, the
impact on the peak throughput of UEs using the 256QAM modulation scheme at the
center of the LTE FDD cell is 1.5 times that on the peak throughput of UEs using the
64QAM modulation scheme at the LTE FDD cell center.
When the uplink PSD of an NB-IoT cell is greater than the PSD of neighboring uplink
RBs in an LTE FDD cell, the NB-IoT cell causes interference to the neighboring RBs in
the LTE FDD cell if the NB-IoT cell load is high. The interference level depends on the
difference in the PSD.
NB-IoT generally provides a continuous coverage area. In 1:1 deployment mode, a
certain amount of transmit power for neighboring LTE FDD cells is reclaimed and
allocated to NB-IoT, which reduces interference. The impact of transmit power
reclamation on SINR/channel quality indicator (CQI)/RANK2 proportion/MCS is less
than that on RSRP.
Network Performance
None
Network Performance
None
Network Performance
None
Before using this feature, read 1.2 Disclaimer for Trial Features.
System Capacity
None
Network Performance
None
Network Performance
None
Network Performance
None
Network Performance
None
Network Performance
When the SI_OFFSET_ADAPTIVE_CFG_SWITCH option under the
CellAlgoSwitch.NbCellAlgoSwitch parameter is selected for a cell, the system information
frame offset of the cell is adaptively configured using different values of PCI mod 3. This
reduces the inter-cell interference caused by system information broadcast and increases the
probability of successfully demodulating system information by UEs.
Network Performance
None
Network Performance
When HARQ retransmission scheduling uses a lowered MCS or bit rate, the downlink
RBLER and service drop rate are improved but downlink throughput is decreased. When the
maximum number of downlink HARQ retransmissions retains the default value, downlink
throughput decreases slightly. The smaller the maximum number of downlink HARQ
retransmissions, the greater the downlink throughput loss.
Network Performance
When HARQ retransmission scheduling uses a lowered MCS or bit rate, the uplink RBLER
and service drop rate are improved, the voice packet loss rate is decreased, but uplink
throughput is decreased. When the maximum number of uplink HARQ retransmissions
retains the default value, uplink throughput decreases slightly. The smaller the maximum
number of uplink HARQ retransmissions, the greater the uplink throughput loss.
Network Performance
None
Network Performance
None
Network Performance
None
Network Performance
If network congestion is reducing system capacity, the use of an admission control algorithm
decreases the access success rate.
Network Performance
Appropriately planned basic scheduling algorithm parameters can improve network
performance counters for the entire process from the initial UE access to data transmission.
Network Performance
The purpose of power control for the NPRACH is to ensure the random access success rate,
minimize transmit power, reduce interference with neighboring cells, and to reduce UE power
consumption.
Power control for the NPUSCH decreases interference with neighboring cells and increases
the data rates for UEs in the local cell edge while ensuring cell throughput.
Network Performance
The sleep state introduced by DRX helps reduce UE power consumption but increases the
service delay. The uplink and downlink single-UE peak data rates decrease as a result.
Network Performance
Cell selection and reselection ensure sufficient network coverage so that UEs in RRC_IDLE
mode will not become out of service when moving between cells.
Network Performance
None
Network Performance
If DL 4-Antenna Transmit Diversity doubles the total transmit power for a given number of
antenna ports, DL 4-Antenna Transmit Diversity provides coverage that is 1 dB to 3 dB
stronger than DL 2-Antenna Transmit Diversity. In addition, DL 4-Antenna Transmit
Diversity occupies fewer downlink subcarriers and thereby reduces their utilization.
Other network KPIs, such as the RRC connection setup success rate and the call drop rate
remain the same after DL 4-Antenna Transmit Diversity is deployed.
In LTE in-band deployment, when channel calibration is enabled for LTE FDD combined
RRUs:
l If an NB-IoT cell is activated during the LTE FDD channel calibration, channel
calibration affects NB-IoT services. Specifically, the bit error rate (BER) increases on the
NPDCCH and NPDSCH by up to 10%.
l If no NB-IoT cell is activated during LTE FDD channel calibration, channel calibration
does not affect NB-IoT services.
Network Performance
When the RRC connection setup success rate decreases due to the flow control implemented
on the main control board or BBP board, access control helps gradually bar UE access so as to
relieve the cell congestion. The RRC connection setup success rate increases as a result, but
the access experience is affected.
If RACH is congested, backoff is triggered to relieve the congestion and thereby improve the
RRC connection setup success rate. Backoff also reduces the number of times UEs transmit a
preamble, causing a possible increase in the call drop rate.
Network Performance
This feature prongs the UE paging cycle, which saves power.
Network Performance
This feature enables the NB-IoT to have a wide coverage area, improves the access success
rate in the coverage enhancement area, and reduces the service drop rate.
Network Performance
Multi-tone transmission significantly increases the single-UE peak uplink data rate, and
reduces the transmission delay and power consumption for uplink data transmission.
Network Performance
UL 4-Antenna Receive Diversity improves the coverage by 1 dB to 3 dB due to its large
diversity gains and array gains, compared with UL 2-Antenna Receive Diversity. UL 4-
Antenna Receive Diversity also occupies fewer uplink subcarriers and thereby reduces their
utilization.
However, UL 4-Antenna Receive Diversity also increases the scope where call drops may
occur and increases interference for cell edge users (CEUs). This increase can be avoided by
preventing overshoot coverage during network planning.
Other network KPIs, such as the RRC connection setup success rate and the call drop rate are
not affected by UL 4-Antenna Receive Diversity.
In LTE in-band deployment, when channel calibration is enabled for LTE FDD combined
RRUs:
l If an NB-IoT cell is activated during the LTE FDD channel calibration, channel
calibration affects NB-IoT services. Specifically, the BER increases on the NPDCCH
and NPDSCH by up to 10%.
l If no NB-IoT cell is activated during LTE FDD channel calibration, channel calibration
does not affect NB-IoT services.
l Standalone
l LTE guard band
l LTE in-band
Collect the information about protocols supported by NB-IoT UEs on the live network. The
collected protocol information is used to plan the settings of 3GPP incompatibility switches.
For details, see 6.4.2 Precautions.
If neighboring cells need to be configured, collect the following information about the intra-
frequency neighboring cells, inter-frequency EARFCNs, and inter-frequency neighboring
cells:
6.3 Planning
6.3.1 RF Planning
If NB-IoT shares RF units with other modes, the current power usage of RF must be taken
into consideration for RF planning.
l If RF units have power headroom, NB-IoT can be deployed directly.
l In refarming deployment scenarios where some GSM spectrums are allocated to NB-IoT,
NB-IoT can be deployed directly.
l If RF units do not have any power headroom, power back-off must be performed for NB-
IoT deployment. The power back-off does not have much impact on the coverage of the
existing network.
In LTE in-band scenarios, an NB-IoT cell and its corresponding LTE FDD cell share the same
RF channel power and the following requirements must be met:
1. The total power of an NB-IoT cell and its corresponding LTE FDD cell cannot exceed
the upper power threshold of the RF channel. For details about the power specifications
of RF modules, see 3900 Series Base Station Technical Description.
2. The PSD of an NB-IoT cell must be no more than 6 dB higher than that of an LTE FDD
cell.
The 1:N (N > 1) deployment is not supported in LTE in-band deployment. This is because
downlink signals in NB-IoT cells are severely interfered with due to the near-far effect when
the 1:N deployment is used, and NB-IoT UEs cannot normally process services. In addition,
the severe interference from LTE FDD to NB-IoT cannot be avoided by reserving extra RBs
as LTE FDD PDCCH signals and pilot signals are transmitted on all RBs.
6.4 Deployment
6.4.1 Requirements
Other Features
For details, see 4 Related Features.
Hardware
l The main control board must be an LMPT or UMPT.
l The baseband board must be an LBBPd1/LBBPd2/LBBPd3/LBBPd5, a UBBPd3/
UBBPd4/UBBPd5/UBBPd6, or a UBBPe1/UBBPe2/UBBPe3/UBBPe4.
l The RF modules supporting NB-IoT are described in 3900 Series Base Station Technical
Description of 3900 Series Base Station Product Documentation.
l LTE in-band deployment requires that NB-IoT cells share main control boards, RF
modules, and antenna systems with LTE FDD cells.
l NB-IoT does not support separate-MPT with LTE FDD.
License
To establish an NB-IoT cell, you need to apply for a capacity license. For details, see License
Control Item Lists (CIoT). Purchase hardware and board licenses as required.
Others
l UEs must support the NB-IoT functions stipulated in 3GPP specifications (Release 13).
l The EPC must support the control plane CIoT EPS optimization function stipulated in
3GPP specifications (Release 13) when this function is implemented between the
eNodeB and EPC.
l The EPC must support the user plane CIoT EPS optimization function stipulated in
3GPP specifications (Release 13) when this function is implemented between the
eNodeB and EPC.
l If NB-IoT and LTE FDD/TDD share the same RF module or baseband board, NB-IoT
must meet the following requirements:
The value of the ENodeBFrameOffset.FddFrameOffset parameter must be the
same as that of the corresponding eNodeB-level parameter of LTE FDD/TDD.
The value of the CellFrameOffset.FrameOffset parameter must be the same as that
of the corresponding cell-level parameter of LTE FDD/TDD.
6.4.2 Precautions
If some NB-IoT UEs in a cell comply with 3GPP TS 36.213 V13.3.0 (2016-09), select
DCI_SF_REP_NUM_COMP_SWITCH under the CellAlgoSwitch.NbCellAlgoSwitch
parameter. If this switch is not selected, these UEs cannot access NB-IoT networks.
When this switch is selected, the NB-IoT UEs that do not comply with 3GPP TS 36.213
V13.3.0 (2016-09) must be upgraded. If they are not upgraded, these NB-IoT UEs cannot
access NB-IoT networks.
The 3GPP Release 13 (2017-03) changed the compatibility policy for NB-IoT UEs.
NbR13CompatSw is introduced to the GlobalProcSwitch.UeCompatSwitch parameter to
determine whether to adopt the new compatibility policy.
l When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03),
NbR13CompatSw must be selected. Otherwise, these NB-IoT UEs cannot access NB-
IoT networks.
l When this option is selected, the NB-IoT UEs that do not comply with 3GPP Release 13
(2017-03) must be upgraded. If they are not upgraded, these NB-IoT UEs cannot access
NB-IoT networks.
Required Data
The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.
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 BASEBANDEQM MO to
configure baseband equipment information.
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 an MmeCapInfo MO to
configure the MME capability information for NB-IoT.
S1 ID S1Id N/A
MME Support LTE NbLteSupportCap If the MME supports LTE FDD and
Capability LTE TDD, set this parameter to
SUPPORT(SUPPORT).
When user plane CIoT EPS optimization is enabled, parameters in the RlcPdcpParaGroup
MO must be set.
When user plane CIoT EPS optimization is enabled, parameters in the QciPara MO must be
set.
The following table describes the parameters that must be set in a Cell MO to configure a cell.
Cell transmission and TxRxMode Set this parameter to the same value
reception mode as the number of antennas in the
sector where the cell is located.
The following table describes the parameters that must be set in a Prb MO to configure
physical resource blocks (PRBs).
The following table describes the parameters that must be set in an eUCellSectorEqm MO to
configure a piece of sector equipment for a cell.
Reference signal power ReferenceSignalPwr Set this parameter to the invalid value
32767 in non-SFN scenarios, where
cells use the reference signal power
specified in the PDSCHCfg MO.
The following table describes the parameters that must be set in a CellOp MO to configure a
cell operator.
The following table describes parameters that must be set in a PDSCHCfg MO to set the
narrowband referential signal (NRS) power.
The following table describes the parameters that must be set in a RACHCfg MO to
configure the random access channel (RACH) power.
The following table describes the parameters that must be set in a CellRachCECfg MO
configure the cell-level physical random access channel (PRACH) that differs according to
coverage levels.
The following table describes the parameters that must be set in a PCCHCfg MO to configure
air interface paging.
The following table describes the parameters that must be set in a GlobalProcSwitch MO to
configure the S1 default paging DRX value and UE compatibility switch.
The following table describes the parameters that must be set in an RrcConnStateTimer MO
to configure the eNodeB timer information.
The following table describes the parameters that must be set in an ENodeBConnStateTimer
MO to configure the eNodeB timer information. These parameters are shared by LTE FDD.
The following table describes the parameters that must be set in a CellPdcchCECfg MO to
configure the PDCCH resource allocation for NB-IoT cells with different coverage levels.
NOTE
The following table describes the parameters that must be set in an NbCellUlSchCEAlgo MO
to configure uplink scheduling parameters for a coverage level. The coverage level-related
parameters in this MO are valid only when MLOFD-120201 NB-IoT Coverage Extension is
activated.
The following table describes the parameters that must be set in an NbCellDlSchCEAlgo MO
to configure downlink scheduling parameters for a coverage level. The coverage level-related
parameters in this MO are valid only when MLOFD-120201 NB-IoT Coverage Extension is
activated.
The following table describes the parameters that must be set in a CellUlpcComm MO to
configure cell uplink power control information.
The following table describes the parameters that must be set in a CellUlpcDedic MO to
configure NPUSCH power control settings.
The following table describes the parameters that must be set in a CellSiMap MO to
configure the message mapping relationships of the system.
The following table describes the parameters that must be set in a CellDrxPara MO to
configure cell-level DRX settings.
The following table describes the parameters that must be set in a CellSel MO to configure
cell selection information.
The following table describes the parameters that must be set in a CellResel MO to configure
common cell reselection information.
Threshold for intra freq SIntraSearchCfgInd Set this parameter to its default
measurements value.
configure indicator
In the cell coverage area, if a UE is stable (for instance a meter reader) and is not in cell edge,
it is recommended that neighboring cells not be configured so as to save overhead over the air
interface.
The following table describes the parameters that must be set in a EutranExternalCell MO
to configure an external E-UTRAN cell.
NB-IoT Cell Flag NbCellFlag The cell must be a NB-IoT cell. Set
this parameter to TRUE(TRUE).
The following table describes the parameter that must be set in a EutranIntraFreqNCell MO
to configure intra-frequency neighboring cell information.
The following table describes the parameter that must be set in a EutranInterFreqNCell MO
to configure inter-frequency neighboring cell information.
The following table describes the parameters that must be set in a EutranInterNFreq MO to
configure a neighboring inter-frequency EARFCN.
The following table describes the parameters that must be set in a CellAlgoSwitch MO to
configure the SIB16 switch, extended access barring (EAB) switch, RACH backoff switch,
and NB-IoT cell algorithm switch.
If the eNodeB or its connected MMEs are overloaded, it is recommended that the EAB switch
be turned on for the cell and the related parameters be configured as required.
The following table describes the parameter that must be set in an eNodeBFlowCtrlPara MO
to configure dynamic access barring.
Parameter Name Parameter ID Setting Notes
The following table describes the parameters that must be set in a CellEABAlgoPara MO to
configure access control.
The following table describes the parameter that must be set in a CellRacThd MO to control
the maximum number of UEs that can be admitted to a cell.
The following table describes the parameters that must be set in a CellChPwrCfg MO to
configure cell channel power if repeaters are used to amplify RRU output power.
Parameter Name Parameter ID Setting Notes
The following table describes the parameters that must be set in an ENBCELLRSVDPARA
MO to configure the proportion of cell output power when repeaters are used to amplify RRU
output power.
Parameter Name Parameter ID Setting Notes
Scenario-specific Data
In LTE in-band deployment mode, RBs need to be reserved in LTE FDD cells for NB-IoT
deployment. The following table describes the parameters that must be set in a
CellRbReserve MO to configure the reserved RBs. The RB reservation will cause
reestablishment of the LTE FDD cell, and consequently ongoing services in the cell will be
interrupted.
RB Reserve End RbRsvEndIndex Set this parameter to a value that is the same
Index as that of RB Reserve Start Index.
The following table describes the parameters that must be set in an ENodeBAlgoSwitch MO
to allow FDD UEs to preempt the RRC resources occupied by NB-IoT UEs in NB-IoT and
LTE FDD co-site deployment scenarios.
The following table describes the parameter that must be set in an ENodeBNbPara MO to
configure the minimum proportion of UEs in RRC_CONNECTED mode reserved for NB-IoT
in NB-IoT and LTE FDD co-site deployment scenarios.
In LTE in-band deployment, ensure that the LTE FDD cell has been activated before
activating an NB-IoT cell.
Step 1 (Optional) If an RRU is added, configure a sector and a set of sector equipment.
1. Run the ADD SECTOR command to add a sector.
NOTE
Cells can work in 1T2R or 2T2R mode. Accordingly, the sector serving the cell must be
configured with the required number of antennas (specified by ANTNUM). For example, to add a
1T2R sector, run the ADD SECTOR command with ANTNUM set to 2.
2. Run the ADD SECTOREQM command to add a set of sector equipment.
NOTE
Step 2 (Optional) To bind baseband equipment to the cell, run the ADD BASEBANDEQM
command.
Step 3 (Optional) To configure the operator and tracking area information, 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 MOD MMECAPINFO command to configure the MME's capability of supporting
NB-IoT.
Step 5 (Optional) When user plane CIoT EPS optimization is enabled, run the ADD
RLCPDCPPARAGROUP command to add an RLC PDCP parameter group.
Step 6 (Optional) When user plane CIoT EPS optimization is enabled, run the MOD QCIPARA
command to add the mapping between the QCIs of non-GBR services and the RLC PDCP
parameter groups.
NOTE
The parameter settings in the QciPara MO take effect only when the
GlobalProcSwitch.QciParaEffectFlag parameter is set to ON(On).
Step 8 (Optional) To reserve LTE FDD in-band RBs for NB-IoT deployment, run the ADD
CELLRBRESERVE command. The RB reservation will cause reestablishment of the LTE
FDD cell, and consequently ongoing services in the cell will be interrupted.
Step 10 Run the ADD EUCELLSECTOREQM command to bind the sector equipment and
baseband equipment (which is optional) to the cell.
Step 11 Run the ADD PRBTOEUCELLSECTOREQM command to associate the PRB to the sector
equipment.
Step 12 Run the ADD CELLOP command to add an operator for the cell.
Step 13 Run the MOD PDSCHCFG command to configure the power of the cell reference signal.
Step 14 Run the MOD RACHCFG command to configure the parameters related to RACH.
Step 15 Run the MOD CELLRACHCECFG command to configure the parameters related to the
PRACH for all coverage levels.
Step 16 (Optional) To optimize the parameters related to the paging over the Uu interface, run the
MOD PCCHCFG command.
Step 17 (Optional) To optimize the S1 default paging DRX value for NB-IoT, run the MOD
GLOBALPROCSWITCH command.
Step 18 (Optional) When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03), run
the MOD GLOBALPROCSWITCH command to turn on the switches controlling UE
compatibility with NB-IoT specified in 3GPP Release 13. When these switches are turned on,
NB-IoT UEs that do not comply with 3GPP Release 13 (2017-03) cannot access the network.
Step 19 (Optional) To optimize the values of timers related to RRC connection control, run the MOD
RRCCONNSTATETIMER command.
Step 20 (Optional) To optimize the value of the Uu message waiting timer, run the MOD
ENODEBCONNSTATETIMER command.
Step 21 (Optional) To optimize the PDCCH resource allocation for different coverage levels in an
NB-IoT cell, run the MOD CELLPDCCHCECFG command.
Step 22 (Optional) To optimize the uplink scheduling algorithm parameters for different coverage
levels in an NB-IoT cell, run the MOD NBCELLULSCHCEALGO command.
Step 23 (Optional) To optimize the downlink scheduling algorithm parameters for different coverage
levels, run the MOD NBCELLDLSCHCEALGO command.
Step 24 Run the MOD CELLULPCCOMM command to modify the NB-IoT cell uplink power
control parameters.
Step 25 (Optional) To optimize dedicated parameters related to power control on the NPUSCH, run
the MOD CELLULPCDEDIC command.
Step 26 (Optional) To modify the SIB-to-SI mapping, run the MOD CELLSIMAP command.
Step 27 (Optional) To activate DRX in RRC_CONNECTED mode, run the MOD CELLDRXPARA
command.
Step 28 Run the MOD CELLSEL command to configure the cell selection information.
Step 29 (Optional) To configure cell reselection information, run the MOD CELLRESEL command.
Step 31 Run the MOD CELLALGOSWITCH command to enable the backoff function, and if
required, the access barring function.
1. (Optional) To modify the dynamic access barring policy mode, run the MOD
ENODEBFLOWCTRLPARA command.
2. Run the MOD CELLEABALGOPARA command to set the access barring-related
parameters.
Step 32 (Optional) When the air interface is congested in a cell, run the MOD
CELLALGOSWITCH command to enable random access flow control and to allow the
eNodeB to include the extendedWaitTime IE in RRC Connection Release messages.
Step 33 (Optional) If some UEs on the live network do not support the maximum backoff index 12
defined in 3GPP TS 36.321 (Release 13), run the MOD CELLEABALGOPARA command
to select the PreambleSchEnhSwitch option.
Step 34 (Optional) When the maximum number of UEs that can be admitted to an NB-IoT cell needs
to be controlled, run the MOD CELLRACTHD command to set Admission Control User
Number.
Step 35 (Optional) To enable UTC broadcast or adaptive configuration of system information frame
offset, run the MOD CELLALGOSWITCH command.
Step 36 (Optional) If repeaters are used to amplify RRU output power in LTE in-band deployment,
perform the following operations:
1. Run the MOD CELLALGOSWITCH command to turn on AntRsPwrSwitch in both
NB-IoT and LTE FDD cells.
2. Run the MOD CELLCHPWRCFG command to set the antenna transmit power of both
NB-IoT and LTE FDD cells.
3. Run the MOD ENBCELLRSVDPARA command to set the proportion of NB-IoT cell
output power and the proportion of LTE FDD cell output power.
Step 37 (Optional) If repeaters are used to amplify RRU output power in guardband or standalone
deployment, perform the following operations:
1. Run the MOD CELLALGOSWITCH command to turn on AntRsPwrSwitch in the
NB-IoT cell.
2. Run the MOD CELLCHPWRCFG command to configure the antenna output power of
the NB-IoT cell.
3. Run the MOD ENBCELLRSVDPARA command to set the proportion of NB-IoT cell
output power.
Step 38 (Optional) When some NB-IoT UEs in a cell comply with 3GPP TS 36.213 V13.3.0
(2016-09), run the MOD CELLALGOSWITCH command to turn on the related switches
under the NB-IoT Cell Algorithm Switch. When these switches are turned on, NB-IoT UEs
that do not comply with 3GPP TS 36.213 V13.3.0 (2016-09) cannot access the network.
Step 39 Run the ACT CELL command to activate the cell.
----End
----End
//Configuring the MME to support the user plane CIoT EPS optimization function
and LTE FDD/LTE TDD services
ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType= S1_CFG, S1Id=0, NbCiotEpsOptCap=CP_UP,
NbLteSupportCap=SUPPORT;
//(Optional) Configuring the RLC PDCP parameter groups for user plane CIoT EPS
optimization
ADD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=130, CatType=NBIOT, RlcMode=RlcMode_AM,
UlDlDiscardtimerSwitch=OFF;
//(Optional) Configuring the QCIs of non-GBR services using user plane CIoT EPS
optimization
MOD GLOBALPROCSWITCH: QciParaEffectFlag=ON;
MOD QCIPARA: Qci=5, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=6, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=7, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=8, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=9, NbRlcPdcpParaGroupId=130;
//Adding an NB-IoT cell (cell 0)
ADD CELL: LocalCellId=0, CellName="NBCell0", NbCellFlag=TRUE,
CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
CellId=0, PhyCellId=0, FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=1T1R,
UserLabel="NBCell0";
//(Optional) Reserving LTE FDD RBs for NB-IoT deployment in LTE in-band mode
(Assume that the LTE FDD cell bandwidth is 20 MHz, and downlink RB 44 and uplink
RB 0 are reserved for NB-IoT.)
ADD CELLRBRESERVE: LocalCellId=0, Index=0, RbRsvMode=NB_DEPLOYMENT,
RbRsvType=DOWNLINK_MODE, RbRsvStartIndex=44, RbRsvEndIndex=44;
ADD CELLRBRESERVE: LocalCellId=0, Index=1, RbRsvMode=NB_DEPLOYMENT,
RbRsvType=UPLINK_MODE, RbRsvStartIndex=0, RbRsvEndIndex=0;
//Configuring the PRB for NB-IoT in LTE in-band deployment (Assume that the
frequency band is band 8, the uplink EARFCN is 21511, and the downlink EARFCN is
3590.)
ADD PRB: LocalCellId=0, PrbId=0, DeployMode=IN_BAND, FreqBand=8,
UlEarfcnCfgInd=CFG, UlEarfcn=21511, UlFreqOffset=NEG_2, DlEarfcn=3590,
DlFreqOffset=POS_0, LteCellId=1;
//Configuring the PRB for an NB-IoT cell in standalone deployment
ADD PRB: LocalCellId=0,PrbId=0,DeployMode=STAND_ALONE,FreqBand=8,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3600,DlFreqOffset=NEG_0DOT5;
//Configuring the PRB for an NB-IoT cell in LTE guardband deployment
ADD PRB: LocalCellId=0,PrbId=0,DeployMode=GUARD_BAND,FreqBand=8,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3552,DlFreqOffset=NEG_2, LteBandWidth=
LTE_SYSTEM_BW_10M,LteDlEarfcn=3600;
//Adding sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BaseBandEqmId=0;
//Adding the mapping relationship between a PRB and sector equipment
ADD PRBTOEUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, PrbId=0;
//Adding an operator for the cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
//Configuring NRS power allocation
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=272;
//Configuring RACH information
MOD RACHCFG: LocalCellId=0,
PreambInitRcvTargetPwr=DBM_112,NbCyclicPrefixLength=66DOT7,
NbRsrpFirstThreshold=-128, NbRsrpSecondThreshold=-137,
PrachStartTimeCfgInd=NOT_CFG;
//Configuring the cell-level PRACH for three coverage levels
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=0,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_2,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_3;
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=1,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_8,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_2;
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=2,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_32,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_0;
//(Optional) Setting the default paging cycle and number of paging groups for NB-
IoT
MOD PCCHCFG: LocalCellId=0, PagingStrategy=PAGING_STRATEGY_DIFFPRI,
DefaultPagingCycleForNb=rf512, NbForNbIoT=ONE_64TH_T,
MaxNumRepetitionForPaging=REP_32;
//(Optional) Setting the S1 default paging DRX value for NB-IoT
MOD GLOBALPROCSWITCH: S1DefaultPagingDrxForNb=512;
// (Optional) Turning on NbR13CompatSw
MOD GLOBALPROCSWITCH: UeCompatSwitch=NbR13CompatSw-1;
//(Optional) Setting the NB-IoT UE inactivity timer
MOD RRCCONNSTATETIMER: NbUeInactiveTimer=30;
//Setting the S1 message waiting timer and Uu message waiting timer
MOD ENODEBCONNSTATETIMER: S1MessageWaitingTimer=20, UuMessageWaitingTimer=35;
//(Optional) Configuring the cell-level PDCCH configurations for three coverage
levels
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=0,
PdcchMaxRepetitionCnt=REP_8,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=ONER_EIGH
TR;
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=1,
PdcchMaxRepetitionCnt=REP_16,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=ONER_EIG
HTR;
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=2,
PdcchMaxRepetitionCnt=REP_32,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=QUARTERR
;
//(Optional) Configuring the cell uplink scheduling information for three
coverage levels
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=0,
UlInitialMcs=MCS_9,UlInitialTransRptCount=REP_1,AckNackTransRptCount=REP_2,AckNack
TransRptCountMsg4=REP_4;
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=1,
UlInitialMcs=MCS_0,UlInitialTransRptCount=REP_2,AckNackTransRptCount=REP_4,AckNack
TransRptCountMsg4=REP_8;
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=2,
UlInitialMcs=MCS_0,UlInitialTransRptCount=REP_32,AckNackTransRptCount=REP_32,AckNa
ckTransRptCountMsg4=REP_64;
//(Optional) Configuring the cell downlink scheduling information and Uu message
waiting timers for three coverage levels
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=0,
DlInitialTransRptCount=REP_1, DlInitialMcs=MCS_10, UuMessageWaitingTimer=35;
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=1,
DlInitialTransRptCount=REP_1, DlInitialMcs=MCS_1, UuMessageWaitingTimer=45;
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=2,
DlInitialTransRptCount=REP_16, DlInitialMcs=MCS_0, UuMessageWaitingTimer=65;
//Modifying the NB-IoT cell uplink power control parameters
MOD CELLULPCCOMM: LocalCellId=0, PassLossCoeff=AL1, P0NominalPUSCH=-105;
//(Optional) Setting the NPUSCH power control dedicated information
MOD CELLULPCDEDIC: LocalCellId=0, FilterRsrp=UU_FC6_FILTER_COEFF;
//(Optional) Setting cell SIB-to-SI mapping
MOD CELLSIMAP: LocalCellId=0, NbSib1RepetitionNum=16, NbSib2Period=RF512,
NbSib3Period=RF2048;
//(Optional) Configuring DRX
MOD CELLDRXPARA:LOCALCELLID=0, DrxAlgSwitch=ON;
//(Optional) Configuring DRX parameters
MOD CELLDRXPARA: LocalCellId=0, NbDrxInactivityTimer=PP3, NbDrxReTxTimer=PP4,
NbDrxUlReTxTimer=PP4, NbLongDrxCycle=SF2048, NbOnDurationTimer=PP3;
//Configuring cell selection information
MOD CELLSEL: LocalCellId=0, QRxLevMin=-70, QQualMin=-23;
//(Optional) Configuring cell reselection information
MOD CELLRESEL: LocalCellId=0, Qhyst=DB2_Q_HYST, SNonIntraSearchCfgInd=CFG,
SNonIntraSearch=9, QRxLevMin=-65, PMaxCfgInd=CFG, PMax=-27,
SIntraSearchCfgInd=CFG, SIntraSearch=29, TReselForNb=5, TReselInterFreqForNb=6;
//(Optional) Configuring E-UTRAN external cell information
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=255, CellId=1, NbCellFlag
=TRUE, DlEarfcn=3000, DlFreqOffset=NEG_0DOT5, UlEarfcnCfgInd=CFG, UlEarfcn=21000,
UlFreqOffset=POS_0, PhyCellId=1, Tac=1;
//(Optional) Configuring intra-frequency neighboring cell information
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=255,
CellId=1, CellIndividualOffset=dB1, CellQoffset=dB1;
//(Optional) Adding inter-frequency neighboring frequencies
If the value of the Cell instance state parameter is Normal, the cell has been activated.
Step 2 Use a UE to access the cell. If the UE successfully accesses the cell, the cell is working
properly.
----End
6.4.6 Deactivation
1526744783 L.NB.Traffic.User.Avg
1526744784 L.NB.Traffic.User.Avg.CoverageLevel0
1526744785 L.NB.Traffic.User.Avg.CoverageLevel1
1526744786 L.NB.Traffic.User.Max
1526744787 L.NB.Traffic.User.Max.CoverageLevel0
1526744788 L.NB.Traffic.User.Max.CoverageLevel1
1526744789 L.NB.Traffic.User.Max.CoverageLevel2
l RBLER
Uplink RBLER
Uplink RBLER = {100} x (L.NB.Traffic.UL.SCH.ErrTB.Rbler) /
(L.NB.Traffic.UL.SCH.TB)
Downlink RBLER
Downlink RBLER = {100} x (L.NB.Traffic.DL.SCH.ErrTB.Rbler) /
(L.NB.Traffic.DL.SCH.TB)
l Throughput
Uplink UE throughput
Formula: L.NB.Thrp.bits.UL/L.NB.Thrp.Time.UL
Downlink UE throughput
Formula: L.NB.Thrp.bits.DL/L.NB.Thrp.Time.DL
l Counters related to paging
Counter ID Counter Name Counter Description
1526745767 L.NB.AB.Trigger.Num
1526745768 L.NB.AB.Cancel.Num
1526745769 L.NB.AB.Adjust.Num
1526745770 L.NB.AB.Control.Dur
The following table provides suggestions on optimizing uplink scheduling parameter settings
for NB-IoT in the NbCellUlSchCEAlgo MO.
The following table provides suggestions on optimizing parameters related to the NB-IoT
downlink NPDCCH scheduling algorithm, which are in the CellPdcchCECfg MO.
The following table provides suggestions on optimizing parameters related to NB-IoT paging,
which are in the PCCHCFG MO.
Fault Handling
Step 1 Start cell status monitoring on the U2000 client to check the cell status. For detailed handling
methods when a cell outage occurs, refer to Cell Outage Detection and Recovery Feature
Parameter Description.
Step 2 View 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.
----End
l UEs stay in the RRC_IDLE state and support this feature. The power consumption of
these UEs needs to be reduced.
l The EPC supports this feature.
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
7.4 Deployment
7.4.1 Requirements
Other Features
See 4.26 MLOFD-120220 Idle Mode eDRX for details.
Hardware
None
License
Feature ID Feature Name Model License Sales Unit
Control Item
Others
l The EPC must support Idle Mode eDRX.
l UEs must support Idle Mode eDRX.
l When the eNodeB uses frequency synchronization, the eNodeB must be configured with
an IEEE1588 V2 clock to achieve time synchronization with the MME, if the MME does
not support the premature sending of paging messages to the eNodeB.
l When the eNodeB uses frequency synchronization and the MME supports the premature
sending of paging messages to the eNodeB, the eNodeB can also be configured with an
NTP clock source to achieve time synchronization with the MME.
7.4.2 Precautions
According to 3GPP TS 23.682 Release 13 (September 2016), if the eNodeB and MME use
different time standards, they must both use the GPS time to calculate the H-SFN. Currently,
the eNodeB supports only GPS time conversion. If the MME supports only the UTC, it is
recommended that the MME convert the UTC to GPS time.
3GPP TS 36.304 Release 13 (2017-03) changed the method Hash ID is calculated for UEs
using Idle Mode eDRX. HashedIdCompatSw is introduced to the
GlobalProcSwitch.UeCompatSwitch parameter to determine whether to use the new Hash ID
calculation method.
l When some NB-IoT UEs in a cell support Idle Mode eDRX specified in 3GPP Release
13 (2017-03), HashedIdCompatSw must be selected. If this option is not selected, these
NB-IoT UEs cannot normally receive paging messages when using Idle Mode eDRX.
l When this option is selected, the NB-IoT UEs that do not support Idle Mode eDRX
specified in 3GPP Release 13 (2017-03) must be upgraded. If they are not upgraded,
these NB-IoT UEs cannot normally receive paging messages when using Idle Mode
eDRX.
The following table describes the parameter that must be set in a GlobalProcSwitch MO to
set the UE compatibility switch.
The following table describes the parameter that must be set in a TASM MO to configure
HSFN synchronization parameters.
Low Precision Frame LPFNSYNCSW Turn on this switch when the eNodeB
No. Synchronization uses frequency synchronization and is
Switch configured with an IEEE1588 V2 clock
to achieve time synchronization with
the MME.
CIoT Frame No. FNSYNCSW Turn on this switch when the eNodeB
Synchronization uses frequency synchronization and is
Switch configured with an NTP clock source
to achieve time synchronization with
the MME, and when Idle Mode eDRX
is required.
Step 1 (Optional) When the eNodeB is configured to use frequency synchronization, configure an
IEEE1588 V2 clock for the eNodeB to achieve time synchronization with the MME, and at
the same time run the MML command SET CLKSYNCMODE to turn on Low Precision
Frame No. Synchronization Switch.
Step 2 (Optional) When the eNodeB is configured to use frequency synchronization and is
configured with an NTP clock source to achieve time synchronization with the MME, run the
MML command SET FNSYNCTIME to set the eDRX synchronization start time and start
the eDRX frame synchronization function.
Step 3 (Optional) When the eNodeB is configured to use frequency synchronization and is
configured with an NTP clock source to achieve time synchronization with the MME, and
when its connected MME uses GPS time, run the MML command SET
LEAPSECONDSINFO to set the leap second offset between the UTC and GPS.
Step 5 (Optional) When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03), run
the MOD GLOBALPROCSWITCH command to select HashedIdCompatSw under the Ue
Compatibility Switch parameter.
----End
----End
7.4.6 Deactivation
This feature can be deactivated by using the CME or MML commands.
----End
8.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
8.4 Deployment
8.4.1 Requirements
Other Features
For details, see 4.27 MLOFD-120201 NB-IoT Coverage Extension.
Hardware
None
License
Feature ID Feature Name Model License Sales Unit
Description
Others
None
8.4.2 Precautions
None
The following table describes the parameter that must be set in a eNBCellRsvdPara MO to
configure the delta-RxLevMin.
Step 2 (Optional) If some UEs in an area of coverage level 2 cannot camp on a cell, run the MOD
ENBCELLRSVDPARA command to modify with the Reserved U8 Parameter 17
parameter specified to set the delta-RxLevMin.
----End
1526744763 L.NB.ChMeas.NPUSCH.Repetition.16
1526744764 L.NB.ChMeas.NPUSCH.Repetition.32
1526744765 L.NB.ChMeas.NPUSCH.Repetition.64
1526744766 L.NB.ChMeas.NPUSCH.Repetition.128
1526744680 L.NB.ChMeas.NPDSCH.Repetition.16
1526744681 L.NB.ChMeas.NPDSCH.Repetition.32
1526744682 L.NB.ChMeas.NPDSCH.Repetition.64
1526744683 L.NB.ChMeas.NPDSCH.Repetition.128to256
8.4.6 Deactivation
----End
1526744783 L.NB.Traffic.User.Avg
1526744785 L.NB.Traffic.User.Avg.CoverageLevel1
1526744786 L.NB.Traffic.User.Max
1526744788 L.NB.Traffic.User.Max.CoverageLevel1
1526744789 L.NB.Traffic.User.Max.CoverageLevel2
l The values of the counters related to RRC connection setup will increase.
Counter ID Counter Name
1526744790 L.NB.RRC.ConnReq.Att
1526744792 L.NB.RRC.ConnReq.Att.CoverageLevel1
1526744798 L.NB.RRC.ConnReq.Succ
1526744800 L.NB.RRC.ConnReq.Succ.CoverageLevel1
1526744805 L.NB.RRC.ConnSetup
1526744807 L.NB.RRC.ConnSetup.CoverageLevel1
9.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
9.4 Deployment
9.4.1 Requirements
Other Features
For details, see 4.28 MLOFD-120230 Multi-tone.
Hardware
The baseband board must be an LBBPd1/LBBPd2/LBBPd3/LBBPd5, a UBBPd3/UBBPd4/
UBBPd5/UBBPd6, or a UBBPe1/UBBPe2/UBBPe3/UBBPe4.
License
Feature ID Feature Name Model License Sales Unit
Control Item
Others
UEs must be multi-tone-capable UEs.
9.4.2 Precautions
None
The following table lists the parameters that must be set in a CellDmrsCfg MO to configure
the demodulation reference signal (DMRS) of the cell.
DMRS Six Tone Base SixToneBaseSeq Set this parameter to a value different
Sequence from that of the neighboring cells to
ensure that the DMRS sequence
generated is different. Otherwise,
interference occurs.
Step 2 Run the ADD CELLDMRSCFG command to ensure that the values of all parameters are
different from those of the neighboring cells. Otherwise, the DMRS sequence generated by
multi-tone-capable UEs is the same and interference occurs.
----End
Step 2 Choose Monitor > Signaling Trace > Signaling Trace Management.
Step 3 In the navigation tree on the left of the Signaling Trace Management window, choose LTE
> User Performance Monitoring > NB Throughput Monitoring. The NB Throughput
Monitoring dialog box is displayed.
Step 5 Set tracing parameters, and click Finish. Then, the tracing task starts.
Step 6 On the right pane of the Signaling Trace Management window, right-click the
corresponding monitoring task and select Query Result from the shortcut menu to view the
results of the Uplink MAC Throughput item.
----End
Expected result:
If the value of the uplink MAC throughput is significantly greater than that before Multi-tone
is deployed, Multi-tone has taken effect.
NOTE
The uplink MAC throughput can also be measured on the UE side. The method used to measure the
uplink MAC throughput on the UE side may differ from that on the U2000 side. Consequently, the
uplink MAC throughput measured on the UE side may slightly differ from that measured on the U2000
side. It is recommended that the uplink MAC throughput measured on the UE side be used.
Step 2 Choose Monitor > Signaling Trace > Signaling Trace Management.
Step 3 In the navigation tree on the left of the Signaling Trace Management window, choose LTE
> User Performance Monitoring > NB Scheduling Monitoring. The NB Scheduling
Monitoring dialog box is displayed.
Step 5 Set tracing parameters, and click Finish. Then, the tracing task starts.
Step 6 On the right pane of the Signaling Trace Management window, right-click the
corresponding monitoring task and select Query Result from the shortcut menu to view the
values of items ThreeTone ULSCH Num, SixTone ULSCH Num, and TwelveTone
ULSCH Num.
----End
Expected result:
If the value of any previous item is not zero, Multi-tone has taken effect.
9.4.6 Deactivation
This chapter describes the engineering guidelines for the MLOFD-121202 UL 4-Antenna
Receive Diversity feature.
Coverage Area
l Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or
highways
l Service types and their coverage requirements
l User quantity and user distribution
l KPI requirements
Frequency Band
l Frequency band owned by the operator
l Adjacent frequency bands and frequency band distribution of other wireless
communications systems in the area, which are used to analyze interference from other
frequencies or frequency bands
Map
Whether a digital map of the coverage area is available for system performance simulation
needs to be verified.
Antenna
The following information needs to be collected:
l Antenna model
l Number of ports
l Manufacturer
l Electrical specifications, including the operating frequency band, polarization, and gains
l Mechanical specifications, including the antenna size, weight, and connector
l Antenna directivity diagram
If a new antenna is to be added, check whether space is sufficient and whether the space
meets the requirements for installing the antenna. If an old antenna is to be replaced with a
new one, check whether the installation conditions are fulfilled for the new antenna.
Feeder
Information about the feeder type and loss needs to be collected.
Coupler
When couplers are used, information about the coupler type and specifications such as delay
and insertion loss needs to be collected.
10.3 Planning
RF Planning
Estimate the uplink budget and capacity based on the information collected by referring to
10.2 Required Information and then complete RF planning.
Network Planning
N/A
Hardware Planning
4T4R includes multiple-antenna reception and transmission. It is recommended that hardware
for multiple-antenna reception and transmission be planned together. For details about
hardware planning, see 10.4.3 Hardware Adjustment.
10.4 Deployment
10.4.1 Requirements
Other Features
See 4.29 MLOFD-121202 UL 4-Antenna Receive Diversity.
Hardware
The eNodeB must be configured with a minimum of four receive channels and four physical
antennas.
The baseband board must be a UBBPd4/UBBPd5/UBBPd6 or a UBBPe2/UBBPe4.
License
The operator has purchased the feature license and hardware license.
l Feature license
Feature ID Feature Name Model License Sales Unit
Control Item
l Hardware license
In uplink reception, each baseband board is equipped with two baseband receive
channels for a cell, and each RF module is equipped with two RF receive channels for a
cell. Since UL 4-Antenna Receive Diversity requires four receive channels, the operator
needs to purchase the licenses for additional two baseband receive channels and two RF
receive channels for each cell. Otherwise, cell activation fails.
10.4.2 Precautions
If two antennas are combined to serve a cell, MLOFD-121202 UL 4-Antenna Receive
Diversity requires that all of the following conditions be met:
In addition to a 2T4R RRU, a 4T4R RRU can be used to serve a 2T4R cell. When a 4T4R
RRU is used, channels A and B must work in TX/RX mode while channels C and D must
work in RX mode. The TX/RX mode can be set using the ADD SECTOREQM or MOD
SECTOREQM command.
Figure 10-1 Topology for a 2T4R cell with an integrated antenna (integrated RRU)
Figure 10-2 Topology for a 2T4R cell with combined antennas (integrated RRU)
NOTE
l If a 2T4R RRU and an integrated antenna are used, the feeder connection mode shown in Figure
10-2 can also be used. As the antenna arrays of an integrated antenna are spaced about one
wavelength apart, the difference in performance between the two modes shown in Figure 10-1 and
Figure 10-2 can be ignored. However, the non-cross-connection mode shown in Figure 10-1 is
recommended to facilitate the installation.
l If a 4T4R RRU is used to serve a 2T4R cell, the topologies shown in Figure 10-7 and Figure 10-8
are recommended. The reason is to facilitate upgrade from a 2T4R cell to a 4T4R cell, avoiding a
second installation.
Figure 10-3 Topology for a 2T4R cell with an integrated antenna (1T2R+1T2R; 1T2R RRUs)
Figure 10-4 Topology for a 2T4R cell with combined antennas (1T2R+1T2R; 1T2R RRUs)
NOTE
If any TX channel is faulty, roll back the TX/RX mode of the cell from 2T4R to 1T2R.
NOTE
Figure 10-5 Topology for a 2T4R cell with an integrated antenna (2T2R+0T2R, 2T2R RRUs)
Figure 10-6 Topology for a 2T4R cell with combined antennas (2T2R+0T2R, 2T2R RRUs)
Figure 10-7 Topology for a 4T4R cell with an integrated antenna (integrated RRU)
Figure 10-8 Topology for a 4T4R cell with combined antennas (integrated RRU)
Figure 10-9 Topology for a 4T4R cell with an integrated antenna (2T2R+2T2R; 2T2R RRUs)
Figure 10-10 Topology for a 4T4R cell with combined antennas (2T2R+2T2R; 2T2R RRUs)
NOTE
If any transmit channel is faulty, roll back the TX/RX mode of the cell from 4T4R to 2T2R and then to
1T1R. That is, the TX/RX mode cannot be rolled back to 2T4R or 1T2R if the antennas are not adjusted.
Figure 10-11 Topology for a 4T4R cell with an integrated antenna (2T2R+2T2R; 2T4R
RRUs)
Figure 10-12 Topology for a 4T4R cell with combined antennas (2T2R+2T2R; 2T4R RRUs)
Required Data
The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.
Cabinet No. of ANT1CN Set the cabinet No. of all antennas based on
Antenna 1 the network plan.
Subrack No. of ANT1SRN Set the subrack No. of all antennas based on
Antenna 1 the network plan.
Slot No. of Antenna ANT1SN Set the slot No. of all antennas based on the
1 network plan.
Channel No. of ANT1N Set the channel No. of all antennas based on
Antenna 1 the network plan.
The following table describes the parameters that must be set in a SECTOREQM MO to
configure a set of sector equipment.
Slot No. of Antenna ANT1SN Set this parameter based on the network
1 plan.
The following table describes the parameters that must be set in an eUCellSectorEqm MO to
bind a set of sector equipment to a cell.
Scenario-specific Data
The following table describes the parameters that must be set in a Cell MO to configure a cell
and NB-RS port mapping.
CRS Port Number CrsPortNum Set this parameter based on the number of
downlink channels. Set this parameter to
CRS_PORT_2(2 ports) in 2T or 4T mode
and to CRS_PORT_1(1 port) in 1T mode.
Cell transmission TxRxMode Set this parameter to the same value as that
and reception mode of the SECTOR.ANTNUM parameter. For
NB-IoT cells, this parameter can only be set
to 1T1R, 1T2R, 2T2R, 2T4R, or 4T4R.
For MLOFD-121202 UL 4-Antenna Receive Diversity, set the TX/RX mode of a cell to 2T4R
or 4T4R by referring to 10.4.4.4 MML Command Examples:
l 2T4R Cell (Integrated RRU)
l 2T4R Cell (1T2R+1T2R; 1T2R RRUs)
l 2T4R Cell (2T2R+0T2R; 2T2R RRUs)
l 4T4R Cell (Integrated RRU)
l 4T4R Cell (2T2R+2T2R; 2T2R RRUs)
l 4T4R Cell (2T2R+2T2R; 2T4R RRUs)
Step 2 Run the ACT CELL command to activate the cell.
----End
Example:
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=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=FALSE;
ADD SECTOREQM:
SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=
RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3S
RN=61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RXTX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B
,ANTTYPE4=RXTX_MODE;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,ULBANDWIDTH=CELL_BW_N50,DLBANDWID
TH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZE
DBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MU
LTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_2,TXRXMODE=4T4R,
CRSPORTMAP=4T2P_0101;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
Step 2 On the Signaling Trace Management tab page, double-click the tracing task to view the NB-
IoT RSSI tracing result. Four receive antennas have been configured and UL 4-Antenna
Receive Diversity has been activated if none of the following values are N/A:
l antenna 0 RSSI(dBm)
l antenna 1 RSSI(dBm)
l antenna 2 RSSI(dBm)
l antenna 3 RSSI(dBm)
----End
Step 2 View the NB-IoT RSSI monitoring results in the displayed dialog box. Four receive antennas
have been configured and UL 4-antenna receive diversity has been activated if none of the
following values are N/A:
l antenna 0 RSSI(dBm)
l antenna 1 RSSI(dBm)
l antenna 2 RSSI(dBm)
l antenna 3 RSSI(dBm)
----End
10.4.6 Deactivation
Step 2 Modify a sector, a set of sector equipment (including antennas), and a cell (including its
TX/RX mode) by running the MML commands listed in 10.4.6.3 MML Command
Examples:
l Using Integrated RRUs
l Using Combined RRUs
----End
Check the RSSI values of the four antennas in the cell performance tracing result by referring
to 10.4.5 Activation Observation. If none of the values are N/A, UL 4-Antenna Receive
Diversity has been activated.
Method 2
Condition: Separately enable the UL 2-Antenna Receive Diversity and UL 4-Antenna Receive
Diversity features in the same cell, and ensure that the cell bandwidth and other parameters
such as the UE transmit power remain unchanged.
Method: Calculate the distribution of uplink MCS indexes and average uplink throughput
when UL 4-Antenna Receive Diversity and UL 2-Antenna Receive Diversity are enabled.
Result: You can find that the uplink MCS index and average uplink throughput increase after
UL 4-Antenna Receive Diversity is enabled. In addition, check the uplink throughput by
performing drive tests; you can find that the uplink throughput increases.
NOTE
In uplink 4-antenna receive diversity, if the receive power for some antennas is imbalanced due to
interference or feeder length difference, the gains of 4-antenna receive diversity are negatively affected
compared with 2-antenna receive diversity.
Handling
If a TX antenna and an RX antenna are faulty, the cell using the faulty antennas falls back to
the maximum TX/RX mode supported by the number of available TX and RX antennas. The
cell falls back in the sequence of 4T4R -> 2T4R -> 2T2R -> 1T2R -> 1T1R.
The eNodeB automatically adjusts the Cell.CrsPortMap parameter to the default value to
ensure normal running. After the antennas for 4T4R become available, the eNodeB
automatically restores this parameter to its original value.
This chapter describes the engineering guidelines for the MLBFD-12100240 DL 4-Antenna
Transmit Diversity feature.
Coverage Area
l Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or
highways
l Service types and their coverage requirements
l User quantity and user distribution
l KPI requirements
Frequency Band
l Frequency band owned by the operator
l Adjacent frequency bands and frequency band distribution of other wireless
communications systems in the area, which are used to analyze interference from other
frequencies
Map
Whether a digital map of the coverage area is available for system performance simulation
needs to be verified.
Antenna
The following information needs to be collected:
l Antenna model
l Number of ports
l Manufacturer
l Electrical specifications, including the operating frequency band, polarization, and gains
l Mechanical specifications, including the antenna size, weight, and connector
l Antenna directivity diagram
If a new antenna is to be added, check whether space is sufficient and whether the space
meets the requirements for installing the antenna. If an old antenna is to be replaced with a
new one, check whether the installation conditions are fulfilled for the new antenna.
Feeder
Information about the feeder type and loss
Coupler
When couplers are used, information about the coupler type and specifications such as delay
and insertion loss must be collected.
11.3 Planning
RF Planning
Estimate the downlink budget and capacity based on the information collected by referring to
11.2 Required Information and then complete RF planning.
Network Planning
N/A
Hardware Planning
See 11.4.3 Hardware Adjustment for details.
11.4 Deployment
11.4.1 Requirements
Other Features
See 4.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity for details.
Hardware
The eNodeB must be configured with a minimum of four transmit channels and four physical
antennas.
License
MLBFD-12100240 DL 4-Antenna Transmit Diversity is a basic feature, and therefore is not
under license control.
In downlink transmission, since the NB-RS can be transmitted over a maximum of two
antenna ports and each baseband board is equipped with two baseband transmit channels for a
cell, operators do not need to purchase licenses for additional baseband transmit channels. DL
4-Antenna Transmit Diversity requires four RF transmit channels, and each RF module is
equipped with two RF transmit channels by default. Therefore, operators need to purchase the
licenses for two additional RF transmit channels. Otherwise, cell activation fails.
Others
None
11.4.2 Precautions
If two antennas are combined to serve a cell, MLBFD-12100240 DL 4-Antenna Transmit
Diversity requires that all of the following conditions be met:
l The antennas have the same azimuth and downtilt.
l The spacing between the antennas meets the isolation requirement.
l The feeders between the antennas and RF modules have the same length and loss.
The TX/RX mode of a cell using DL 4-Antenna Transmit Diversity is 4T4R, and DL 4-
Antenna Transmit Diversity is configured together with UL 4-Antenna Receive Diversity. For
details, see 10.4.4.4 MML Command Examples.
----End
Step 2 In the navigation tree of the Signaling Trace Management tab page, choose Base Station
Device and Transport > RRU/RFU/BRU Output Power Monitoring. The
RRU/RFU/BRU Output Power Monitoring dialog box is displayed.
----End
----End
11.4.6 Deactivation
Step 2 Modify a sector, a set of sector equipment (including antennas), and a cell (including its
TX/RX mode). The configurations of DL 4-Antenna Transmit Diversity is modified together
with those of UL 4-Antenna Receive Diversity. For details about the involved commands, see
the following sub-sections in 10.4.6.3 MML Command Examples:
l Using Integrated RRUs
l Using Combined RRUs
Step 3 Run the ACT CELL command to activate the cell again.
----End
Method: Calculate the distribution of downlink MCS indexes and average downlink
throughput when DL 2-Antenna Transmit Diversity and DL 4-Antenna Transmit Diversity are
enabled.
Result: You can find that the downlink MCS index and average downlink throughput increase
after DL 4-Antenna Transmit Diversity is enabled. In addition, check the downlink throughput
by performing drive tests; you can find that the downlink throughput increases.
Handling
If a TX antenna and an RX antenna are faulty, the cell using the faulty antennas falls back to
the maximum TX/RX mode supported by the number of available TX and RX antennas. The
cell falls back in the sequence of 4T4R -> 2T4R -> 2T2R -> 1T2R -> 1T1R.
The eNodeB automatically adjusts the Cell.CrsPortMap parameter to the default value to
ensure normal running. After the antennas for 4T4R become available, the eNodeB
automatically restores this parameter to its original value.
12 Parameters
CellChP AntOutp MOD LBFD-0 Dynami Meaning: Indicates the transmit power for the entire
wrCfg utPwr CELLC 02016 / c channel bandwidth at each antenna connector. If the
HPWRC TDLBF Downlin AntRsPwrSwitch option of the RepeaterSwitch
FG D-00201 k Power parameter is selected, this parameter value is used to
LST 6 Allocati calculate the reference signal (RS) power to be
CELLC on delivered in system information block type 2 (SIB2).
HPWRC GUI Value Range: 20~40
FG Unit: W
Actual Value Range: 20~40
Default Value: 20
CellAlg Repeater MOD LBFD-0 Dynami Meaning: Indicates the type of reference signal (RS)
oSwitch Switch CELLA 02016 c power to be delivered in system information block
LGOSW Downlin type 2 (SIB2). If the AntRsPwrSwitch option is
ITCH k Power selected, the RS power calculated based on the
LST Allocati transmit power of the antenna port and output power
CELLA on rate is delivered in SIB2. If the AntRsPwrSwitch
LGOSW option is deselected, the RS power specified by the
ITCH ReferenceSignalPwr parameter is delivered in SIB2.
This parameter applies only to LTE FDD and NB-IoT.
GUI Value Range:
AntRsPwrSwitch(AntRsPwrSwitch)
Unit: None
Actual Value Range: AntRsPwrSwitch
Default Value: AntRsPwrSwitch:Off
TIMES AUTOS SET None None Meaning: Indicates whether to enable automatic time
RC WITCH TIMES source switchover. When the switch is turned on, the
RC system switches over the time source when time
DSP synchronization fails. When the switch is turned off,
TIMES the system does not switch over the time source.
RC GUI Value Range: OFF(Off), ON(On)
LST Unit: None
TIMES Actual Value Range: OFF, ON
RC
Default Value: ON(On)
ENodeB FddFra MOD MRFD- FDD Meaning: Indicates the offset of the start time of a cell
FrameO meOffse ENODE 101231 and frame against a reference clock source. This offset
ffset t BFRAM MRFD- TDD applies to all LTE FDD cells served by an eNodeB.
EOFFS 101222 Carrier This parameter applies only to LTE FDD and NB-IoT.
ET Aggrega GUI Value Range: 0~261120,275943~307200
LST tion(TD
D) Unit: Ts
ENODE
BFRAM FDD Actual Value Range: 0~261120,275943~307200
EOFFS and Default Value: 0
ET TDD
Carrier
Aggrega
tion(FD
D)
CellFra FrameO ADD None None Meaning: Indicates the offset of the start time of a cell
meOffse ffset CELLF frame against a reference clock source.
t RAME GUI Value Range: 0~261120,275943~307200
OFFSE
T Unit: Ts
lingSwitch), EnhExtQCISpsSchS-
witch(EnhExtQCISpsSchSwitch),
UlVoipRbRsvSwitch(UlVoipRbRsvSwitch),
UlThpEnhSwitch(UlThpEnhSwitch),
UlDataFitterRbCalcSwitch(UlDataFitterRbCalcS-
witch), UlFssOptForAttach(UlFssOptForAttach),
SrbProbeSchSwitch(SrbProbeSchSwitch),
UlSchCtrlPwrUserSetOptSw(UlSchCtrlPwrUserSe-
tOptSw), UlPttSchOptSwitch(UlPttSchOptSwitch),
UlPttDataSizeEstSwitch(UlPttDataSizeEstSwitch),
EnhancedSchForSparseSwitch(EnhancedSchForSpar-
seSwitch), UlSigSrSchDateLenA-
dapt(UlSigSrSchDateLenAdapt), UlFssWindSearch-
DirRandSw(UlFssWindSearchDirRandSw),
UlCellCenterMCSOptSwitch(UlCellCenterMCSOptS-
witch), PuschSchEscPucchS-
witch(PuschSchEscPucchSwitch),
HarqMcsOptSwitch(HarqMcsOptSwitch),
PreambleSchEnhSwitch(PreambleSchEnhSwitch),
UlPAMCSwitch(UlPAMCSwitch), UlMultiClusterS-
witch(UlMultiClusterSwitch)
Unit: None
Actual Value Range: UlPacketLenAwareSchSw,
EnhExtQCITtiBundlingSwitch, EnhExtQCISpsSchS-
witch, UlVoipRbRsvSwitch, UlThpEnhSwitch,
UlDataFitterRbCalcSwitch, UlFssOptForAttach,
SrbProbeSchSwitch, UlSchCtrlPwrUserSetOptSw,
UlPttSchOptSwitch, UlPttDataSizeEstSwitch,
EnhancedSchForSparseSwitch, UlSigSrSchDateLe-
nAdapt, UlFssWindSearchDirRandSw,
UlCellCenterMCSOptSwitch, PuschSchEscPucchS-
witch, HarqMcsOptSwitch, PreambleSchEnhSwitch,
UlPAMCSwitch, UlMultiClusterSwitch
Default Value: UlPacketLenAwareSchSw:Off,
EnhExtQCITtiBundlingSwitch:Off,
EnhExtQCISpsSchSwitch:Off,
UlVoipRbRsvSwitch:Off, UlThpEnhSwitch:Off,
UlDataFitterRbCalcSwitch:On,
UlFssOptForAttach:Off, SrbProbeSchSwitch:Off,
UlSchCtrlPwrUserSetOptSw:Off,
UlPttSchOptSwitch:Off, UlPttDataSizeEstSwitch:Off,
EnhancedSchForSparseSwitch:Off,
UlSigSrSchDateLenAdapt:Off, UlFssWindSearchDir-
RandSw:Off, UlCellCenterMCSOptSwitch:Off,
PuschSchEscPucchSwitch:Off,
HarqMcsOptSwitch:Off, PreambleSchEnhSwitch:Off,
UlPAMCSwitch:Off, UlMultiClusterSwitch:Off
NbCell UuMess MOD MLBFD RRC Meaning: Indicates the timer governing the period the
DlSchC ageWaiti NBCEL -120002 Connect eNodeB waits for a Uu response message from a UE.
EAlgo ngTimer LDLSC 28 ion If the timer expires, the eNodeB initiates to release the
HCEAL Manage UE. If this parameter is set to 0, the
GO ment UuMessageWaitingTimer parameter in the
LST ENodeBConnStateTimer MO, rather than this
NBCEL parameter, takes effect. If this parameter is set to 1 to
LDLSC 200, this parameter takes effect. This parameter
HCEAL applies only to NB-IoT.
GO GUI Value Range: 0~200
Unit: s
Actual Value Range: 0~200
Default Value: 0
PCCHC MaxNu MOD MLBFD Paging Meaning: Indicates the maximum number of
fg mRepeti PCCHC -120002 repetitions in the NPDCCH common search space for
tionForP FG 31 NB-IoT paging. For details about this parameter, see
aging LST descriptions of the npdcch-NumRepetitionPaging IE
PCCHC in 3GPP TS 36.331. When this parameter is set to
FG NULL, npdcch-NumRepetitionPaging uses the
CellPdcchCECfg.PdcchMaxRepetitionCnt parameter
value corresponding to the maximum coverage level
by default. When this parameter is not set to NULL,
npdcch-NumRepetitionPaging uses the
MaxNumRepetitionForPaging parameter value. This
parameter applies only to NB-IoT.
GUI Value Range: REP_1(REP_1), REP_2(REP_2),
REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
REP_32(REP_32), REP_64(REP_64),
REP_128(REP_128), REP_256(REP_256),
REP_512(REP_512), REP_1024(REP_1024),
REP_2048(REP_2048), NULL(Invalid)
Unit: None
Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128, REP_256,
REP_512, REP_1024, REP_2048, NULL
Default Value: NULL(Invalid)
CellRac PrachSta MOD MLBFD Random Meaning: Indicates the PRACH start time. When
hCECfg rtTime CELLR -120002 Access PrachStartTimeCfgInd is set to CFG, this parameter
ACHCE 30 Procedu can be set to different values for different coverage
CFG re levels of a cell. However, the PRACH start time
LST interval between coverage levels must not be less than
CELLR 40 ms. Otherwise, cells fail to be activated. This
ACHCE parameter applies only to NB-IoT.
CFG GUI Value Range: SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128),
SF256(SF256), SF512(SF512), SF1024(SF1024)
Unit: None
Actual Value Range: SF8, SF16, SF32, SF64, SF128,
SF256, SF512, SF1024
Default Value: SF8(SF8)
RACHC PrachSta MOD MLBFD Random Meaning: Indicates whether PRACH start time is
fg rtTimeC RACHC -120002 Access configurable. When this parameter is set to
fgInd FG 30 NOT_CFG, PRACH start time is not configurable.
LST The PRACH start time for coverage level 0 is always
RACHC 8 ms. The PRACH start time for coverage level 1 and
FG that for coverage level 2 are determined based on the
following factors: the sum of the PRACH start time
and PRACH time length for the previous coverage
level, and the restriction that the PRACH start time
interval between coverage levels is not less than 40
ms. When this parameter is set to CFG, the PRACH
start time for each coverage level is configurable. The
PRACH start time interval between coverage levels
must not be less than 40 ms. Otherwise, cells fail to be
activated. This parameter applies only to NB-IoT.
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)
CellRac PrachDe MOD MLBFD Random Meaning: Indicates the PRACH detection threshold.
hCECfg tectionT CELLR -120002 Access LEVEL_0 indicates the lower detection threshold and
hld ACHCE 30 LEVEL_3 indicates the upper detection
CFG threshold.When PrachRepetitionCount is set to
LST REP_1(REP_1), REP_2(REP_2), REP_4(REP_4), or
CELLR REP_128(REP_128), this parameter takes effect as it
ACHCE is set to LEVEL_3. This parameter applies only to
CFG NB-IoT.
GUI Value Range: LEVEL_0(LEVEL_0),
LEVEL_1(LEVEL_1), LEVEL_2(LEVEL_2),
LEVEL_3(LEVEL_3)
Unit: None
Actual Value Range: LEVEL_0, LEVEL_1,
LEVEL_2, LEVEL_3
Default Value: LEVEL_3(LEVEL_3)
MULTITONE_SWITCH(MULTITONE_SWITCH),
DCI_SF_REP_NUM_COMP_SWITCH(DCI_SF_RE
P_NUM_COMP_SWITCH),
SI_OFFSET_ADAPTIVE_CFG_SWITCH(SI_OFFS
ET_ADAPTIVE_CFG_SWITCH)
Unit: None
Actual Value Range: IDLE_EDRX_SWITCH,
COVERAGE_EXTENSION_SWITCH,
MULTITONE_SWITCH,
DCI_SF_REP_NUM_COMP_SWITCH,
SI_OFFSET_ADAPTIVE_CFG_SWITCH
Default Value: IDLE_EDRX_SWITCH:Off,
COVERAGE_EXTENSION_SWITCH:Off,
MULTITONE_SWITCH:Off,
DCI_SF_REP_NUM_COMP_SWITCH:Off,
SI_OFFSET_ADAPTIVE_CFG_SWITCH:Off
TASM CLKSY SET MRFD- BTS Meaning: Indicates the clock synchronization mode of
NCMO CLKSY 210501 Clock a BS, which can be frequency synchronization or time
DE NCMO synchronization.
DE GUI Value Range: FREQ(FREQ), TIME(TIME),
DSP HYBRID(HYBRID)
CLKST Unit: None
AT
Actual Value Range: FREQ, TIME, HYBRID
LST
CLKSY Default Value: FREQ(FREQ)
NCMO
DE
TASM LPFNS SET None None Meaning: Indicates the switch of low-precision frame
YNCS CLKSY No. synchronization. When this switch is turned on,
W NCMO the frame No. synchronization function is enabled,
DE and the SFN and HSFN are automatically aligned
DSP after the system clock is locked. When this switch is
CLKST turned off, the frame No. synchronization function is
AT disabled. This switch applies to NB-IoT and eDRX.
LST GUI Value Range: OFF(OFF), ON(ON)
CLKSY Unit: None
NCMO Actual Value Range: OFF, ON
DE
Default Value: OFF(OFF)
Prb Deploy ADD MLBFD Standalo Meaning: Indicates the NB-IoT PRB deployment
Mode PRB -120001 ne mode. STAND_ALONE indicates that out-of-band
MOD 01 Deploy LTE spectrum resources are used to deploy NB-IoT
PRB MLBFD ment PRB. GUARD_BAND indicates that NB-IoT PRB is
-120001 LTE deployed on the LTE guardband. IN_BAND indicates
LST that PRB is deployed on the LTE RB resources, which
PRB 02 Guardba
nd means that less RBs are available for LTE. This
MLBFD parameter applies only to NB-IoT.
-120001 Deploy
03 ment GUI Value Range:
LTE In- STAND_ALONE(STAND_ALONE),
band GUARD_BAND(GUARD_BAND),
Deploy IN_BAND(IN_BAND)
ment Unit: None
Actual Value Range: STAND_ALONE,
GUARD_BAND, IN_BAND
Default Value: STAND_ALONE(STAND_ALONE)
Prb DlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
ffset PRB -120001 ne downlink central frequency to the downlink
MOD 01 Deploy frequency. For details, see 3GPP TS 36.101. This
PRB MLBFD ment parameter applies only to NB-IoT.
LST -120001 LTE GUI Value Range: NEG_2(NEG_2),
PRB 02 Guardba NEG_1(NEG_1), NEG_0DOT5(NEG_0DOT5),
MLBFD nd POS_0(POS_0), POS_1(POS_1)
-120001 Deploy Unit: None
03 ment
Actual Value Range: NEG_2, NEG_1, NEG_0DOT5,
LTE In- POS_0, POS_1
band
Deploy Default Value: NEG_0DOT5(NEG_0DOT5)
ment
Prb LteBand ADD MLBFD LTE Meaning: Indicates the LTE cell bandwidth. This
Width PRB -120001 Guardba parameter takes effect only when DeployMode is set
MOD 02 nd to GUARD_BAND. This parameter applies only to
PRB Deploy NB-IoT.
ment GUI Value Range:
LST
PRB LTE_SYSTEM_BW_10M(LTE_SYSTEM_BW_10M
),
LTE_SYSTEM_BW_15M(LTE_SYSTEM_BW_15M
),
LTE_SYSTEM_BW_20M(LTE_SYSTEM_BW_20M
)
Unit: None
Actual Value Range: LTE_SYSTEM_BW_10M,
LTE_SYSTEM_BW_15M, LTE_SYSTEM_BW_20M
Default Value: None
Prb LteDlEa ADD MLBFD LTE Meaning: Indicates the downlink EARFCN of an LTE
rfcn PRB -120001 Guardba cell. This parameter takes effect only when
MOD 02 nd DeployMode is set to GUARD_BAND. This
PRB Deploy parameter applies only to NB-IoT.
ment GUI Value Range:
LST
PRB 0~68485,255144~256143,260894~262143
Unit: None
Actual Value Range:
0~68485,255144~256143,260894~262143
Default Value: None
Prb LteCellI ADD MLBFD LTE In- Meaning: Indicates the LTE cell ID. This parameter
d PRB -120001 band takes effect only when DeployMode is set to
MOD 03 Deploy IN_BAND. This parameter applies only to NB-IoT.
PRB ment GUI Value Range: 0~255
LST Unit: None
PRB Actual Value Range: 0~255
Default Value: None
CellRbR RbRsvT ADD MLBFD LTE In- Meaning: Indicates whether the PRBs to be reserved
eserve ype CELLR -120001 band at the physical layer are uplink or downlink ones. This
BRESE 03 Deploy parameter applies only to LTE FDD and NB-IoT.
RVE ment GUI Value Range:
MOD UPLINK_MODE(UPLINK_MODE),
CELLR DOWNLINK_MODE(DOWNLINK_MODE)
BRESE Unit: None
RVE
Actual Value Range: UPLINK_MODE,
LST DOWNLINK_MODE
CELLR
BRESE Default Value: None
RVE
CellRbR RbRsv ADD MLBFD LTE In- Meaning: Indicates the purpose for reserving RBs.
eserve Mode CELLR -120001 band The value NB_RESERVED indicates that the
BRESE 03 Deploy specified RBs are reserved as a guardband in the
RVE ment uplink or to reduce the interference between LTE and
MOD NB-IoT cells in the downlink. The value
CELLR NB_DEPLOYMENT indicates that the specified RBs
BRESE are to be used for deploying NB-IoT. The value
RVE RB_MASKING indicates that the specified RBs are to
be used for manual RB masking. The value
LST RB_MASKING_WITH_SRS indicates that the
CELLR specified RBs are to be used for manual RB and SRS
BRESE masking. This parameter applies only to LTE FDD
RVE and NB-IoT.
GUI Value Range:
NB_RESERVED(NB_RESERVED),
NB_DEPLOYMENT(NB_DEPLOYMENT),
RB_MASKING(RB_MASKING),
RB_MASKING_WITH_SRS(RB_MASKING_WITH
_SRS)
Unit: None
Actual Value Range: NB_RESERVED,
NB_DEPLOYMENT, RB_MASKING,
RB_MASKING_WITH_SRS
Default Value: None
CellRbR Index ADD MLBFD LTE In- Meaning: Indicates the index of a reserved RB
eserve CELLR -120001 band configuration for the cell. This parameter applies only
BRESE 03 Deploy to LTE FDD and NB-IoT.
RVE ment GUI Value Range: 0~99
MOD Unit: None
CELLR
BRESE Actual Value Range: 0~99
RVE Default Value: None
RMV
CELLR
BRESE
RVE
LST
CELLR
BRESE
RVE
Prb UlAllSy ADD MLBFD LTE In- Meaning: Indicates whether all PRB uplink symbols
mbolSen PRB -120001 band are used for sending. When this parameter is set to
dFlag MOD 03 Deploy TRUE, all NB-IoT PRB uplink symbols are sent.
PRB ment When this parameter is set to FALSE, not all NB-IoT
PRB uplink symbols are sent. In in-band scenarios,
LST NB-IoT PRB symbols do not conflict with LTE SRS
PRB symbols to avoid interference. This parameter applies
only to NB-IoT.
GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: TRUE(TRUE)
SRSCfg SrsCfgI MOD LBFD-0 Physical Meaning: Indicates whether to configure sounding
nd SRSCF 02003 / Channel reference signal (SRS) resources for UEs in a cell.
G TDLBF Manage The value BOOLEAN_TRUE indicates that SRS
LST D-00200 ment resources are available in the cell and can be
SRSCF 3 DL 4- configured for UEs in the cell. The value
G TDLAO Layer BOOLEAN_FALSE indicates that no SRS resource is
FD-081 MIMO available in the cell, and therefore no UE in the cell is
409 Based configured with SRS resources. This parameter does
on TM9 not take effect on: (1) FDD cell that is established on
TDLEO an LBBPc and uses four or more RX antennas. (2)
FD-121 DL FDD cell that is established on an LBBPc and uses
615 Flexible extended cyclic prefix (CP) in the uplink. (3) TDD
TDLOF 3D- cell established on an LBBPc. If this parameter does
D-00104 Beamfor not take effect on a cell but SRS resources are
9 ming available in the cell, SRS resources can be configured
Single for UEs in the cell. This parameter applies only to
Streami LTE FDD and LTE TDD.
ng GUI Value Range: BOOLEAN_FALSE(False),
Beamfor BOOLEAN_TRUE(True)
ming
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
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
Unit: None
LST TDLBF Broadca
D-00200 st of Actual Value Range: 0~503
CELL
9/ system Default Value: None
MLBFD informat
-120002 ion
29
Cell NbCellF ADD None None Meaning: Indicates whether a local cell is an NB-IoT
lag CELL cell. When this parameter is set to TRUE, the local
MOD cell is an NB-IoT cell. When this parameter is set to
CELL FALSE, the local cell is not an NB-IoT cell. This
parameter applies only to NB-IoT.
LST
CELL GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(FALSE)
Prb FreqBan ADD MLBFD Standalo Meaning: Indicates the frequency band to which the
d PRB -120001 ne PRB belongs. For details, see 3GPP TS 36.104. This
MOD 01 Deploy parameter applies only to NB-IoT.
PRB MLBFD ment GUI Value Range: 1~256
LST -120001 LTE Unit: None
PRB 02 Guardba
nd Actual Value Range: 1~256
MLBFD
-120001 Deploy Default Value: None
03 ment
LTE In-
band
Deploy
ment
Prb DlEarfc ADD MLBFD Standalo Meaning: Indicates the PRB DL EARFCN. For
n PRB -120001 ne details, see 3GPP TS 36.104. This parameter applies
MOD 01 Deploy only to NB-IoT.
PRB MLBFD ment GUI Value Range:
LST -120001 LTE 0~68485,255144~256143,260894~262143
PRB 02 Guardba Unit: None
MLBFD nd
Deploy Actual Value Range:
-120001 0~68485,255144~256143,260894~262143
03 ment
LTE In- Default Value: None
band
Deploy
ment
Prb UlEarfc ADD MLBFD Standalo Meaning: Indicates the PRB uplink EARFCN, which
n PRB -120001 ne is optional. This parameter takes effect only when
MOD 01 Deploy UlEarfcnCfgInd is set to CFG(Configure). Otherwise,
PRB MLBFD ment the eNodeB calculates this parameter value based on
-120001 LTE the rule that RB positions in the uplink and downlink
LST are consistent. This parameter applies only to NB-IoT.
PRB 02 Guardba
MLBFD nd GUI Value Range: 18000~65535,131072~133221
-120001 Deploy Unit: None
03 ment
Actual Value Range: 18000~65535,131072~133221
LTE In-
band Default Value: None
Deploy
ment
Prb UlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
ffset PRB -120001 ne uplink central frequency to the uplink frequency. This
MOD 01 Deploy parameter takes effect only when UlEarfcnCfgInd is
PRB MLBFD ment set to CFG(Configure). Otherwise, the eNodeB
-120001 LTE calculates this parameter value based on the rule that
LST RB positions in the uplink and downlink are
PRB 02 Guardba
nd consistent. For details, see 3GPP TS 36.101. This
MLBFD parameter applies only to NB-IoT.
-120001 Deploy
03 ment GUI Value Range: NEG_10(NEG_10),
LTE In- NEG_9(NEG_9), NEG_8(NEG_8), NEG_7(NEG_7),
band NEG_6(NEG_6), NEG_5(NEG_5), NEG_4(NEG_4),
Deploy NEG_3(NEG_3), NEG_2(NEG_2), NEG_1(NEG_1),
ment POS_0(POS_0), POS_1(POS_1), POS_2(POS_2),
POS_3(POS_3), POS_4(POS_4), POS_5(POS_5),
POS_6(POS_6), POS_7(POS_7), POS_8(POS_8),
POS_9(POS_9)
Unit: None
Actual Value Range: NEG_10, NEG_9, NEG_8,
NEG_7, NEG_6, NEG_5, NEG_4, NEG_3, NEG_2,
NEG_1, POS_0, POS_1, POS_2, POS_3, POS_4,
POS_5, POS_6, POS_7, POS_8, POS_9
Default Value: POS_0(POS_0)
Prb UlEarfc ADD MLBFD Standalo Meaning: Indicates whether to configure information
nCfgInd PRB -120001 ne about the PRB uplink EARFCN. This parameter
MOD 01 Deploy applies only to NB-IoT.
PRB MLBFD ment GUI Value Range: NOT_CFG(Not configure),
LST -120001 LTE CFG(Configure)
PRB 02 Guardba Unit: None
MLBFD nd
Deploy Actual Value Range: NOT_CFG, CFG
-120001
03 ment Default Value: NOT_CFG(Not configure)
LTE In-
band
Deploy
ment
CellSel QRxLev MOD LBFD-0 Broadca Meaning: Indicates the minimum required RX level
Min CELLS 02009 / st of for the cell to become a candidate for cell selection.
EL TDLBF system This value is included in criteria S and used in the
LST D-00200 informat evaluation of cell selection. For details, see 3GPP TS
CELLS 9/ ion 36.304.
EL MLBFD Cell GUI Value Range: -70~-22
-120002 Selectio
29 Unit: 2dBm
n and
LBFD-0 Re- Actual Value Range: -140~-44
0201803 selection Default Value: -64
/
TDLBF
D-00201
803 /
MLBFD
-120002
37
CellRes PMaxCf MOD LBFD-0 Cell Meaning: Indicates whether to configure the
el gInd CELLR 0201803 Selectio maximum TX power of the UE in the intra-frequency
ESEL / n and neighboring cell. If the value of this parameter is not
LST TDLBF Re- specified, the maximum power is subject to the UE
CELLR D-00201 selection capability.
ESEL 803 / Broadca GUI Value Range: NOT_CFG(Not configure),
MLBFD st of CFG(Configure)
-120002 system
37 Unit: None
informat
LBFD-0 ion Actual Value Range: NOT_CFG, CFG
02009 / Default Value: NOT_CFG(Not configure)
TDLBF
D-00200
9/
MLBFD
-120002
29
CellSel QQualM MOD LBFD-0 Broadca Meaning: Indicates the minimum required received
in CELLS 02009 / st of signal quality, which corresponds to the q-QualMin IE
EL TDLBF system in system information block type 1 (SIB1) and is used
LST D-00200 informat to calculate the Squal value for the serving cell
CELLS 9/ ion involved in cell selection and reselection. If this
EL MLBFD Cell parameter is set to 0, SIB1 does not contain the q-
-120002 Selectio QualMin IE. If this parameter is set to a value other
29 n and than 0, SIB1 contains the q-QualMin IE with the same
LBFD-0 Re- value as the parameter value. For details about this
0201803 selection parameter, see 3GPP TS 36.304.
/ GUI Value Range: -34~-3,0
TDLBF Unit: dB
D-00201
803 / Actual Value Range: -34~-3,0
MLBFD Default Value: 0
-120002
37
CellRes SNonInt MOD LBFD-0 Cell Meaning: Indicates the measurement triggering
el raSearch CELLR 0201803 Selectio threshold for reselection to inter-frequency or inter-
ESEL / n and RAT cells. If the cell reselection priority of a
LST TDLBF Re- frequency or RAT is higher than that of the serving
CELLR D-00201 selection frequency, the UEs always start inter-frequency or
ESEL 803 / Broadca inter-RAT measurements. If the cell reselection
MLBFD st of priority of a frequency is lower than or equal to that of
-120002 system the serving frequency or if the cell reselection priority
37 informat of an RAT is lower than that of the serving frequency,
LBFD-0 ion the UEs start inter-frequency or inter-RAT
02009 / measurements only when the value of Cell selection
PS Inter- RX level value (dB) is lower than or equal to the value
TDLBF RAT
D-00200 of this parameter.
Mobility
9/ between GUI Value Range: 0~31
MLBFD E- Unit: 2dB
-120002 UTRAN
29 Actual Value Range: 0~62
and
LOFD-0 CDMA2 Default Value: 9
01021 / 000
TDLOF PS
D-00102 Mobility
1 from E-
LOFD-0 UTRAN
01111 to
CDMA2
000
HRPD
Based
on
Frequen
cy-
specific
Factors
CellRes QRxLev MOD LBFD-0 Cell Meaning: Indicates the minimum required RX level
el Min CELLR 0201803 Selectio used in intra-frequency E-UTRAN cell reselection,
ESEL / n and which corresponds to the IE q-RxLevMin in SIB3.
LST TDLBF Re- This value is included in the cell reselection criteria
CELLR D-00201 selection and used in the evaluation of cell reselection. For
ESEL 803 / Broadca details, see 3GPP TS 36.304.
MLBFD st of GUI Value Range: -70~-22
-120002 system
37 Unit: 2dBm
informat
LBFD-0 ion Actual Value Range: -140~-44
02009 / PS Inter- Default Value: -64
TDLBF RAT
D-00200 Mobility
9/ between
MLBFD E-
-120002 UTRAN
29 and
LOFD-0 CDMA2
01021 / 000
TDLOF PS
D-00102 Mobility
1 from E-
LOFD-0 UTRAN
01111 to
CDMA2
000
HRPD
Based
on
Frequen
cy-
specific
Factors
CellRes PMax MOD LBFD-0 Cell Meaning: Indicates the maximum power that the UE
el CELLR 0201803 Selectio can apply to transmission in the intra-frequency
ESEL / n and neighboring cell. It is used in cell reselection criteria
LST TDLBF Re- to calculate the compensated power. If the value of
CELLR D-00201 selection this parameter is not specified, the maximum power is
ESEL 803 / Broadca subject to the UE capability. For details, see 3GPP TS
MLBFD st of 36.304.
-120002 system GUI Value Range: -30~33
37 informat Unit: dBm
LBFD-0 ion
02009 / Actual Value Range: -30~33
TDLBF Default Value: 23
D-00200
9/
MLBFD
-120002
29
EutranIn QRxLev ADD LBFD-0 Cell Meaning: Indicates the RX level required for a
terNFre Min EUTRA 0201803 Selectio neighboring cell on the frequency to become a
q NINTE / n and suitable cell for selection. It is included in criteria S
RNFRE TDLBF Reselect and used in the evaluation for cell selection. During
Q D-00201 ion the evaluation for cell reselection, the UE performs
MOD 803 / the following calculation: Srxlev = Measured RSRP
EUTRA MLBFD value of a neighboring cell on the frequency - Value of
NINTE -120002 this parameter - Compensated power. If Srxlev for a
RNFRE 37 cell is better than a threshold for a time-to-trigger,
Q reselection to the cell is started. For details, see 3GPP
TS 36.304.
LST
EUTRA GUI Value Range: -70~-22
NINTE Unit: 2dBm
RNFRE Actual Value Range: -140~-44
Q
Default Value: -64
EutranIn Pmax ADD LBFD-0 Cell Meaning: Indicates the maximum power that the UE
terNFre EUTRA 0201803 Selectio can apply to transmission on the neighboring E-
q NINTE / n and UTRAN frequency. It is used in cell reselection
RNFRE TDLBF Reselect criteria to calculate the compensated power. If the
Q D-00201 ion value of this parameter is not specified, the maximum
MOD 803 / power is subject to the UE capability. For details, see
EUTRA MLBFD 3GPP TS 36.304.
NINTE -120002 GUI Value Range: -30~33
RNFRE 37
Unit: dBm
Q
Actual Value Range: -30~33
LST
EUTRA Default Value: 23
NINTE
RNFRE
Q
CellRes Qhyst MOD LBFD-0 Cell Meaning: Indicates the hysteresis for cell reselection
el CELLR 0201803 Selectio when RSRP values are used in the evaluation. This
ESEL / n and parameter must be set based on the slow fading
LST TDLBF Re- characteristic of the area covered by the cell. The
CELLR D-00201 selection greater the slow fading variance is, the larger the value
ESEL 803 / Broadca of this parameter must be set to. A larger value of the
MLBFD st of hysteresis results in a larger boundary of the serving
-120002 system cell and a lower probability of cell reselection to
37 informat neighboring cells.
LBFD-0 ion GUI Value Range: DB0_Q_HYST(0dB),
02009 / DB1_Q_HYST(1dB), DB2_Q_HYST(2dB),
TDLBF DB3_Q_HYST(3dB), DB4_Q_HYST(4dB),
D-00200 DB5_Q_HYST(5dB), DB6_Q_HYST(6dB),
9/ DB8_Q_HYST(8dB), DB10_Q_HYST(10dB),
MLBFD DB12_Q_HYST(12dB), DB14_Q_HYST(14dB),
-120002 DB16_Q_HYST(16dB), DB18_Q_HYST(18dB),
29 DB20_Q_HYST(20dB), DB22_Q_HYST(22dB),
DB24_Q_HYST(24dB)
Unit: dB
Actual Value Range: DB0_Q_HYST, DB1_Q_HYST,
DB2_Q_HYST, DB3_Q_HYST, DB4_Q_HYST,
DB5_Q_HYST, DB6_Q_HYST, DB8_Q_HYST,
DB10_Q_HYST, DB12_Q_HYST, DB14_Q_HYST,
DB16_Q_HYST, DB18_Q_HYST, DB20_Q_HYST,
DB22_Q_HYST, DB24_Q_HYST
Default Value: DB4_Q_HYST(4dB)
EutranIn CellQoff ADD LBFD-0 Coverag Meaning: Indicates the offset for the intra-frequency
traFreq set EUTRA 0201801 e Based neighboring cell, which is used in evaluation for cell
NCell NINTR / Intra- reselections. A larger value of this parameter results in
AFREQ TDLBF frequenc a lower probability of cell reselections to this
NCELL D-00201 y neighboring cell. If this parameter is not set to dB0, it
MOD 801 Handov is delivered in SIB4. For details, see 3GPP TS 36.331.
EUTRA LBFD-0 er If this parameter is set to dB0, it is not delivered in
NINTR 0201803 Cell SIB4. In this situation, UEs use 0 dB as the offset for
AFREQ Selectio cell reselections. For details, see 3GPP TS 36.304.
NCELL n and GUI Value Range: dB-24(-24dB), dB-22(-22dB),
LST Re- dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
EUTRA selection dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
NINTR dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
AFREQ dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
NCELL dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
dB20(20dB), dB22(22dB), dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-20, dB-18,
dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,
dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20,
dB22, dB24
Default Value: dB0(0dB)
EutranIn QoffsetF ADD LBFD-0 Cell Meaning: Indicates the frequency-specific offset for
terNFre req EUTRA 0201803 Selectio the neighboring E-UTRAN frequency that applies to
q NINTE / n and UEs in idle mode. It is contained in system
RNFRE TDLBF Re- information block type 5 (SIB5) and delivered to UEs
Q D-00201 selection in idle mode for cell reselection. For details, see 3GPP
MOD 803 / TS 36.331.
EUTRA MLBFD GUI Value Range: dB-24(-24dB), dB-22(-22dB),
NINTE -120002 dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
RNFRE 37 dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
Q dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
LST dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
EUTRA dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
NINTE dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
RNFRE dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
Q dB20(20dB), dB22(22dB), dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-20, dB-18,
dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,
dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20,
dB22, dB24
Default Value: dB0(0dB)
CellRes TReselF MOD LBFD-0 Cell Meaning: Indicates the evaluation period for a UE to
el orNb CELLR 0201803 Selectio determine whether to perform cell reselections to an
ESEL / n and NB-IoT cell. If the signal quality of a new cell is
LST TDLBF Re- better than that of the serving cell within the period
CELLR D-00201 selection specified by this parameter and a UE camps on the
ESEL 803 / Broadca serving cell for more than 1s, the UE initiates cell
MLBFD st of reselections to the new cell. For details, see 3GPP TS
-120002 system 36.304. This parameter applies only to NB-IoT.
37 informat GUI Value Range: 0_SECOND(0_SECOND),
LBFD-0 ion 3_SECOND(3_SECOND),
02009 / 6_SECOND(6_SECOND),
TDLBF 9_SECOND(9_SECOND),
D-00200 12_SECOND(12_SECOND),
9/ 15_SECOND(15_SECOND),
MLBFD 18_SECOND(18_SECOND),
-120002 21_SECOND(21_SECOND)
29 Unit: None
Actual Value Range: 0_SECOND, 3_SECOND,
6_SECOND, 9_SECOND, 12_SECOND,
15_SECOND, 18_SECOND, 21_SECOND
Default Value: 6_SECOND(6_SECOND)
CellRes TReselI MOD MLBFD Cell Meaning: Indicates the evaluation period for a UE to
el nterFreq CELLR -002018 Selectio determine whether to perform cell reselections to an
ForNb ESEL 03 n and NB-IoT cell. If the signal quality of the inter-
LST Reselect frequency neighboring cell meets the threshold within
CELLR ion the period specified by this parameter and a UE camps
ESEL on the serving cell for more than 1s, the UE initiates
cell reselections to the inter-frequency neighboring
cell. The period is sent in SIB5. For details, see 3GPP
TS 36.331. This parameter applies only to NB-IoT.
GUI Value Range: 0_SECOND(0_SECOND),
3_SECOND(3_SECOND),
6_SECOND(6_SECOND),
9_SECOND(9_SECOND),
12_SECOND(12_SECOND),
15_SECOND(15_SECOND),
18_SECOND(18_SECOND),
21_SECOND(21_SECOND)
Unit: s
Actual Value Range: 0_SECOND, 3_SECOND,
6_SECOND, 9_SECOND, 12_SECOND,
15_SECOND, 18_SECOND, 21_SECOND
Default Value: 6_SECOND(6_SECOND)
CellAcc CellBarr MOD LBFD-0 Cell Meaning: Indicates whether the cell is barred. If the
ess ed CELLA 02013 / Outage cell is barred, the UE cannot camp on the serving cell.
CCESS TDLBF Detectio During cell reselection, the serving cell is not selected
LST D-00203 n and as a candidate cell.
CELLA 7 Compen GUI Value Range: CELL_BARRED(Barred),
CCESS LBFD-0 sation CELL_NOT_BARRED(Not Barred)
02009 / Broadca Unit: None
TDLBF st of
D-00200 system Actual Value Range: CELL_BARRED,
9/ informat CELL_NOT_BARRED
MLBFD ion Default Value: CELL_NOT_BARRED(Not Barred)
-120002 RAN
29 Sharing
LOFD-0 with
01036 / Commo
TDLOF n
D-00103 Carrier
6
PCCHC DefaultP MOD MLBFD Paging Meaning: Indicates the default paging period for the
fg agingCy PCCHC -120002 cell. It is also called the default discontinuous
cleForN FG 31 reception (DRX) period. For details, see 3GPP TS
b LST 36.304. This parameter applies only to NB-IoT.
PCCHC GUI Value Range: rf128(rf128), rf256(rf256),
FG rf512(rf512), rf1024(rf1024)
Unit: None
Actual Value Range: rf128, rf256, rf512, rf1024
Default Value: rf256(rf256)
GlobalP S1Defau MOD MLBFD NB-IoT Meaning: Indicates the value of the IE NB-IoT
rocSwitc ltPaging GLOBA -120002 Protocol Default Paging DRX contained in the S1 SETUP
h DrxFor LPROC Complia REQUEST and ENB CONFIGURATION UPDATE
Nb SWITC nce messages that the eNodeB sends over the S1 interface.
H For details, see 3GPP TS 36.413. This parameter
LST applies only to NB-IoT.
GLOBA GUI Value Range: 128(128), 256(256), 512(512),
LPROC 1024(1024)
SWITC Unit: None
H
Actual Value Range: 128, 256, 512, 1024
Default Value: 256(256)
PCCHC NbForN MOD MLBFD Paging Meaning: Indicates the number of paging occasions (a
fg bIoT PCCHC -120002 type of subframe) of NB-IoT cell within a paging
FG 31 period. This parameter value also indicates the
LST number of paging groups within a paging period. For
PCCHC details, see 3GPP TS 36.304. The values of this
FG parameter are correlated with PdcchInitialTransRpt-
Num. This parameter applies only to NB-IoT.
GUI Value Range: FOUR_T(FOUR_T),
TWO_T(TWO_T), ONE_T(ONE_T),
HALF_T(HALF_T), QUARTER_T(QUARTER_T),
ONE_8TH_T(ONE_8TH_T),
ONE_16TH_T(ONE_16TH_T),
ONE_32TH_T(ONE_32TH_T),
ONE_64TH_T(ONE_64TH_T),
ONE_128TH_T(ONE_128TH_T),
ONE_256TH_T(ONE_256TH_T),
ONE_512TH_T(ONE_512TH_T),
ONE_1024TH_T(ONE_1024TH_T)
Unit: None
Actual Value Range: FOUR_T, TWO_T, ONE_T,
HALF_T, QUARTER_T, ONE_8TH_T,
ONE_16TH_T, ONE_32TH_T, ONE_64TH_T,
ONE_128TH_T, ONE_256TH_T, ONE_512TH_T,
ONE_1024TH_T
Default Value: ONE_64TH_T(ONE_64TH_T)
PCCHC PagingS MOD TDLBF Paging Meaning: Indicates a paging message sending policy.
fg trategy PCCHC D-00201 There are two policies: first in first out (FIFO) and
FG 1/ priority differentiation. FIFO means that paging
LST LBFD-0 messages that arrive earlier are preferentially sent in a
PCCHC 02011 / paging occasion. Priority differentiation means higher-
FG MLBFD priority paging messages are preferentially sent in a
-120002 paging occasion.
31 GUI Value Range:
PAGING_STRATEGY_FIFO(First-in First-out
Strategy), PAGING_STRATEGY_DIFFPRI(Priority
Differentiation Strategy)
Unit: None
Actual Value Range: PAGING_STRATEGY_FIFO,
PAGING_STRATEGY_DIFFPRI
Default Value: PAGING_STRATEGY_FIFO(First-in
First-out Strategy)
CellSiM NbSib1 MOD MLBFD Broadca Meaning: Indicates the number of current cell's NB-
ap Repetiti CELLSI -120002 st of IoT SIB1 repetition times within the period. This
onNum MAP 29 System parameter applies only to NB-IoT.
LST Informat GUI Value Range: 4(4), 8(8), 16(16)
CELLSI ion
Unit: None
MAP
Actual Value Range: 4, 8, 16
Default Value: 16(16)
CellSiM NbSib2 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB2
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF512(RF512)
CellSiM NbSib3 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB3
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF2048(RF2048)
CellSiM NbSib4 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB4
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF2048(RF2048)
CellSiM NbSib5 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB5
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF2048(RF2048)
CellSiM NbSib14 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB14
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF512(RF512)
CellSiM NbSib16 MOD MLBFD Broadca Meaning: Indicates the current cell's NB-IoT SIB16
ap Period CELLSI -120002 st of transmission period. This parameter applies only to
MAP 29 System NB-IoT.
LST Informat GUI Value Range: RF64(RF64), RF128(RF128),
CELLSI ion RF256(RF256), RF512(RF512), RF1024(RF1024),
MAP RF2048(RF2048), RF4096(RF4096)
Unit: None
Actual Value Range: RF64, RF128, RF256, RF512,
RF1024, RF2048, RF4096
Default Value: RF2048(RF2048)
BcchCfg ModifyP MOD MLBFD Broadca Meaning: Indicates the BCCH modification period
eriodCo BCCHC -002009 st of coefficient of an NB-IoT cell. The actual modification
effForN FG System period (ModifyPeriod) equals the value of
b LST Informat ModifyPeriodCoeff multiplied by DefaultPagingCy-
BCCHC ion cle, where ModifyPeriod indicates the BCCH
FG modification period (in the unit of radio frame),
ModifyPeriodCoeff indicates the BCCH modification
period coefficient, and DefaultPagingCycle indicates
the default paging cycle (in the unit of radio frame).
This parameter applies only to NB-IoT.
GUI Value Range:
MOD_PERIOD_COEFF_N16(MOD_PERIOD_COE
FF_N16),
MOD_PERIOD_COEFF_N32(MOD_PERIOD_COE
FF_N32),
MOD_PERIOD_COEFF_N64(MOD_PERIOD_COE
FF_N64),
MOD_PERIOD_COEFF_N128(MOD_PERIOD_CO
EFF_N128)
Unit: None
Actual Value Range: MOD_PERIOD_COEFF_N16,
MOD_PERIOD_COEFF_N32,
MOD_PERIOD_COEFF_N64,
MOD_PERIOD_COEFF_N128
Default Value:
MOD_PERIOD_COEFF_N32(MOD_PERIOD_COE
FF_N32)
NbCell NbLogic MOD MLBFD Basic Meaning: Indicates the length of the logical channel
UlSchC ChSrPro NBCEL -120002 Scheduli prohibition timer for UEs. When a UE configured
EAlgo hibitTim LULSC 34 ng with the timer needs to send a service request, the
er HCEAL timer starts. The UE can send the service request only
GO when the timer expires. This timer can be delivered to
LST the UE through the RRCConnectionSetup message.
NBCEL For details about this parameter, see 3GPP TS 36.331.
LULSC This parameter applies only to NB-IoT.
HCEAL GUI Value Range: NOT_CFG(NOT_CFG),
GO PP2(PP2), PP8(PP8), PP32(PP32), PP128(PP128),
PP512(PP512), PP1024(PP1024), PP2048(PP2048)
Unit: None
Actual Value Range: NOT_CFG, PP2, PP8, PP32,
PP128, PP512, PP1024, PP2048
Default Value: NOT_CFG(NOT_CFG)
RACHC NbRsrp MOD MLBFD Random Meaning: Indicates the RSRP level-1 threshold. When
fg FirstThr RACHC -120002 Access the measured RSRP value is higher than the RSRP
eshold FG 30 Procedu level-1 threshold, cells of coverage level 0 are selected
LST re for random access. When the measured RSRP value is
RACHC between the RSRP level-1 threshold and RSRP level-2
FG threshold, cells of coverage level 1 are selected for
random access. When the measured RSRP value is
lower than the RSRP level-2 threshold, cells of
coverage level 2 are selected for random access. This
parameter applies only to NB-IoT.
GUI Value Range: -141~-44
Unit: dBm
Actual Value Range: -141~-44
Default Value: -110
RACHC NbRsrp MOD MLBFD Random Meaning: Indicates the RSRP level-2 threshold. When
fg SecondT RACHC -120002 Access the measured RSRP value is higher than the RSRP
hreshold FG 30 Procedu level-1 threshold, cells of coverage level 0 are selected
LST re for random access. When the measured RSRP value is
RACHC between the RSRP level-1 threshold and RSRP level-2
FG threshold, cells of coverage level 1 are selected for
random access. When the measured RSRP value is
lower than the RSRP level-2 threshold, cells of
coverage level 2 are selected for random access. This
parameter applies only to NB-IoT.
GUI Value Range: -141~-44
Unit: dBm
Actual Value Range: -141~-44
Default Value: -120
RACHC Preambl MOD LBFD-0 Broadca Meaning: Indicates the maximum number of preamble
fg eTrans RACHC 02009 / st of transmission times. For details about this parameter,
Max FG TDLBF system see 3GPP TS 36.321.
LST D-00200 informat GUI Value Range:
RACHC 9/ ion N3_PREMB_TRANS_MAX(3times),
FG MLBFD Random N4_PREMB_TRANS_MAX(4times),
-120002 Access N5_PREMB_TRANS_MAX(5times),
29 Procedu N6_PREMB_TRANS_MAX(6times),
LBFD-0 re N7_PREMB_TRANS_MAX(7times),
02010 / N8_PREMB_TRANS_MAX(8times),
TDLBF N10_PREMB_TRANS_MAX(10times),
D-00201 N20_PREMB_TRANS_MAX(20times),
0/ N50_PREMB_TRANS_MAX(50times),
MLBFD N100_PREMB_TRANS_MAX(100times),
-120002 N200_PREMB_TRANS_MAX(200times)
30 Unit: None
Actual Value Range: N3_PREMB_TRANS_MAX,
N4_PREMB_TRANS_MAX,
N5_PREMB_TRANS_MAX,
N6_PREMB_TRANS_MAX,
N7_PREMB_TRANS_MAX,
N8_PREMB_TRANS_MAX,
N10_PREMB_TRANS_MAX,
N20_PREMB_TRANS_MAX,
N50_PREMB_TRANS_MAX,
N100_PREMB_TRANS_MAX,
N200_PREMB_TRANS_MAX
Default Value:
N10_PREMB_TRANS_MAX(10times)
CellRac MaxNu MOD MLBFD Random Meaning: Indicates the maximum number of preamble
hCECfg mPream CELLR -120002 Access transmissions for random access attempts at the
bleAtte ACHCE 30 corresponding cell coverage level. This parameter
mpt CFG applies only to NB-IoT.
LST GUI Value Range: REP_3(REP_3), REP_4(REP_4),
CELLR REP_5(REP_5), REP_6(REP_6), REP_7(REP_7),
ACHCE REP_8(REP_8), REP_10(REP_10)
CFG Unit: None
Actual Value Range: REP_3, REP_4, REP_5, REP_6,
REP_7, REP_8, REP_10
Default Value: REP_4(REP_4)
CellRac Contenti MOD MLBFD Random Meaning: Indicates the period that a UE waits for
hCECfg onResol CELLR -120002 Access message 4 (Msg4) during a random access (RA)
utionTi ACHCE 30 Procedu procedure. This timer starts when a UE initially sends
mer CFG re or resends message 3 (Msg3). If the UE receives
LST Msg4 or NACK to Msg3 before the timer expires, the
CELLR timer stops. If the UE does not receive either message
ACHCE until the timer expires, the RA fails, and the UE must
CFG reinitiate an RA procedure. It is recommended that
this parameter be set to a relatively large value (such
as PP_16) when a large number of UEs are initiating
random access simultaneously or there is a large
number of high-coverage-level UEs (the average
number of high-coverage-level UEs performing
random access per second is 0.5 or more or the uplink
or downlink subcarrier resource usage reaches 65% or
more.) The unit is the PDCCH period of the
corresponding coverage level. This parameter applies
only to NB-IoT.
GUI Value Range: PP_1(PP_1), PP_2(PP_2),
PP_3(PP_3), PP_4(PP_4), PP_8(PP_8),
PP_16(PP_16), PP_32(PP_32), PP_64(PP_64)
Unit: None
Actual Value Range: PP_1, PP_2, PP_3, PP_4, PP_8,
PP_16, PP_32, PP_64
Default Value: PP_8(PP_8)
CellRac PrachSu MOD MLBFD Random Meaning: Indicates the frequency-domain subcarrier
hCECfg bcarrier CELLR -120002 Access offset position of PRACH resources. In this version,
Offset ACHCE 30 Procedu the PRACH subcarrier offset position configurations
CFG re must be the same for different coverage levels under
LST the same cell. Otherwise, NB-IoT cells fail to work.
CELLR This parameter applies only to NB-IoT.
ACHCE GUI Value Range: SC0(SC0), SC12(SC12),
CFG SC24(SC24), SC36(SC36), SC2(SC2), SC18(SC18),
SC34(SC34)
Unit: None
Actual Value Range: SC0, SC12, SC24, SC36, SC2,
SC18, SC34
Default Value: SC36(SC36)
RACHC NbCycli MOD MLBFD Random Meaning: Indicates the PRACH cyclic prefix length,
fg cPrefixL RACHC -120002 Access which can be 66.7 us and 266.7 us. This parameter
ength FG 30 Procedu applies only to NB-IoT.
LST re GUI Value Range: 66DOT7(66DOT7),
RACHC 266DOT7(266DOT7)
FG Unit: None
Actual Value Range: 66DOT7, 266DOT7
Default Value: 66DOT7(66DOT7)
CellRac PrachRe MOD MLBFD Random Meaning: Indicates the number of repeated preamble
hCECfg petition CELLR -120002 Access transmissions for the corresponding coverage level. If
Count ACHCE 30 Procedu this parameter is not set to a proper value, PRACH
CFG re resources overlap at different coverage levels or there
LST are identical RA-RNTIs. In this situation, cells fail to
CELLR be activated. This parameter must be configured in
ACHCE association with the PrachDetectionThld parameter so
CFG that the number of PRACH repetitions corresponds to
a proper PRACH signal detection threshold. This
parameter applies only to NB-IoT.
GUI Value Range: REP_1(REP_1), REP_2(REP_2),
REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
REP_32(REP_32), REP_64(REP_64),
REP_128(REP_128)
Unit: None
Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128
Default Value: REP_2(REP_2)
CellRac PrachTr MOD MLBFD Random Meaning: Indicates the PRACH transmission period.
hCECfg ansmissi CELLR -120002 Access It is recommended that this parameter be set to the
onPerio ACHCE 30 Procedu same value for each coverage level under the same
d CFG re cell. Otherwise, PRACH resources may overlap at
LST different coverage levels, which decreases the
CELLR PRACH reception success rate. If this parameter is set
ACHCE to a too small value, NPRACH resources overlap at
CFG different coverage levels. In this situation, cells fail to
be activated. This parameter applies only to NB-IoT.
GUI Value Range: SF40(SF40), SF80(SF80),
SF160(SF160), SF240(SF240), SF320(SF320),
SF640(SF640), SF1280(SF1280), SF2560(SF2560)
Unit: subframe
Actual Value Range: SF40, SF80, SF160, SF240,
SF320, SF640, SF1280, SF2560
Default Value: SF640(SF640)
RrcCon FilterRe MOD LBFD-0 RRC Meaning: Indicates the length of the timer for the
nStateTi ptRrcCo RRCCO 02007 / Connect eNodeB to filter repeated RRC Connection Request
mer nnReqTi NNSTA TDLBF ion messages. The actually used timer length is the sum of
mer TETIM D-00200 Manage T300 length and the value of this parameter.
ER 7 ment GUI Value Range: 0~15
LST Unit: s
RRCCO
NNSTA Actual Value Range: 0~15
TETIM Default Value: 15
ER
GlobalP RrcCon MOD LBFD-0 RRC Meaning: Indicates the threshold for an RRC
rocSwitc nPunish GLOBA 02007 / Connect connection penalty. Certain UEs may repeatedly fail
h Thd LPROC TDLBF ion to access networks because of incompatibility issues.
SWITC D-00200 Manage If the number of RRC connection setup requests that
H 7 ment the eNodeB receives from a UE within the period
LST specified by T300+FilterReptRrcConnReqTimer
GLOBA exceeds the threshold (a non-zero value), the eNodeB
LPROC imposes a penalty on the UE, rejecting RRC
SWITC connection setup requests from the UE. If this
H parameter is set to 0, the penalty does not take effect.
GUI Value Range: 0~3600
Unit: None
Actual Value Range: 0~3600
Default Value: 0
ENodeB UuMess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period the
ConnSta ageWaiti ENODE 02007 / Connect eNodeB waits for a response message from a UE
teTimer ngTimer BCONN TDLBF ion when the UE is running non-QCI1 services. If the
STATET D-00200 Manage timer expires, the eNodeB initiates a UE context
IMER 7 ment release over the S1 interface.
LST GUI Value Range: 1~200
ENODE Unit: s
BCONN
STATET Actual Value Range: 1~200
IMER Default Value: 35
ENodeB WaitRrc MOD LBFD-0 RRC Meaning: Indicates the timer for the eNodeB to wait
ConnSta ConnSet ENODE 02007/ Connect for a RRC Connection Setup Complete message.
teTimer upCmpT BCONN TDLBF ion GUI Value Range: 3~15
imer STATET D-00200 Manage
IMER 7 ment Unit: s
MmeCa NbCiotE ADD MLBFD Data Meaning: Indicates the MME's capability of
pInfo psOptCa MMEC -120002 over supporting CIoT EPS optimized transmission for NB-
p APINF 04 NAS IoT. If this parameter is set to NOT_SUPPORT, the
O MLBFD S1-flex MME does not support CIoT EPS optimized
MOD -120003 transmission for NB-IoT. If this parameter is set to CP,
Data the MME supports control-plane CIoT EPS optimized
MMEC 10 \ over
APINF LBFD-0 transmission for NB-IoT. If this parameter is set to
User CP_UP, the MME supports control-plane and user-
O 01018 Plane plane CIoT EPS optimized transmission for NB-IoT.
LST MLBFD For details about this parameter, see 3GPP TS 36.331.
MMEC -121002 This parameter applies only to NB-IoT.
APINF 05
O GUI Value Range:
NOT_SUPPORT(NOT_SUPPORT), CP(CP),
CP_UP(CP_UP)
Unit: None
Actual Value Range: NOT_SUPPORT, CP, CP_UP
Default Value: None
MmeCa NbLteS ADD MLBFD Data Meaning: Indicates the MME's capability of
pInfo upportC MMEC -120002 over supporting LTE FDD and LTE TDD. If this parameter
ap APINF 04 NAS is set to NOT_SUPPORT, the MME does not support
O MLBFD S1-flex LTE FDD or LTE TDD. If this parameter is set to
MOD -120003 SUPPORT, the MME supports LTE FDD and LTE
Data TDD.
MMEC 10 / over
APINF LBFD-0 User GUI Value Range:
O 01018 Plane NOT_SUPPORT(NOT_SUPPORT),
LST MLBFD SUPPORT(SUPPORT)
MMEC -121002 Unit: None
APINF 05 Actual Value Range: NOT_SUPPORT, SUPPORT
O
Default Value: None
S1 MmeRel ADD S1 LBFD-0 Star Meaning: Indicates the compliance protocol release of
ease MOD 0300101 Topolog the MMEs to which the eNodeB is connected through
S1 / y the S1 interfaces under this S1 object. This parameter
TDLBF Chain applies only to LTE FDD and LTE TDD.
LST S1 D-00300 Topolog GUI Value Range: Release_R8(Release 8),
101 y Release_R9(Release 9), Release_R10(Release 10),
LBFD-0 Tree Release_R11(Release 11), Release_R12(Release 12),
0300102 Topolog Release_R13(Release 13)
/ y Unit: None
TDLBF
D-00300 3GPP Actual Value Range: Release_R8, Release_R9,
102 R11 Release_R10, Release_R11, Release_R12,
Specific Release_R13
LBFD-0 ations
0300103 Default Value: Release_R8(Release 8)
/
TDLBF
D-00300
103
LBFD-0
01008 /
TDLBF
D-07011
1
S1Interf MmeRel ADD LBFD-0 Star Meaning: Indicates the compliance protocol release of
ace ease S1INTE 0300101 Topolog the MME to which the eNodeB is connected through
RFACE / y the S1 interface. The eNodeB sends S1 messages
MOD TDLBF Chain complying with the protocol release specified by this
S1INTE D-00300 Topolog parameter. The value of this parameter must be the
RFACE 101 y same as the MME-complied protocol release. If the
LBFD-0 parameter value is different from the MME-complied
DSP Tree protocol release, the way in which the MME handles
S1INTE 0300102 Topolog
/ these message is subject to the MME implementation.
RFACE y
TDLBF GUI Value Range: Release_R8(Release 8),
D-00300 3GPP Release_R9(Release 9), Release_R10(Release 10),
102 R11 Release_R11(Release 11), Release_R12(Release 12),
Specific Release_R13(Release 13)
LBFD-0 ations
0300103 Unit: None
/ Actual Value Range: Release_R8, Release_R9,
TDLBF Release_R10, Release_R11, Release_R12,
D-00300 Release_R13
103
Default Value: Release_R8(Release 8)
LBFD-0
01008 /
TDLBF
D-07011
1
RrcCon NBUeIn MOD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
nStateTi activeTi RRCCO 02007 / Connect timer for NB-IoT UEs. If the eNodeB detects that an
mer mer NNSTA TDLBF ion NB-IoT UE has neither received nor sent data for a
TETIM D-00200 Manage duration exceeding the value of this parameter, the
ER 7 ment eNodeB releases the RRC connection for the NB-IoT
LST UE. This parameter takes effect only for UEs that will
RRCCO access the network after the parameter is set. This
NNSTA parameter applies only to NB-IoT.
TETIM GUI Value Range: 1~3600
ER Unit: s
Actual Value Range: 1~3600
Default Value: 20
ENodeB S1Mess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period that
ConnSta ageWaiti ENODE 02007 / Connect the eNodeB waits for a response message from the
teTimer ngTimer BCONN TDLBF ion MME when the eNodeB performs an S1-based
STATET D-00200 Manage handover for a UE running non-QCI1 services. If the
IMER 7 ment timer expires, the eNodeB initiates a UE context
LST release over the S1 interface. If the eNodeB performs
ENODE an S1-based handover for a UE running services with
BCONN a QCI of 1, the S1MsgWaitingTimerQci1 parameter
STATET controls the period that the eNodeB waits for a
IMER response message from the MME.
GUI Value Range: 1~200
Unit: s
Actual Value Range: 1~200
Default Value: 20
CellUlsc NbUlHa MOD MLBFD Basic Meaning: Indicates the maximum number of uplink
hAlgo rqMaxT CELLU -120002 Scheduli HARQ transmissions. This parameter applies only to
xCount LSCHA 34 ng NB-IoT.
LGO GUI Value Range: 1~8
LST Unit: None
CELLU
LSCHA Actual Value Range: 1~8
LGO Default Value: 5
NbCell UlInitial MOD MLBFD Basic Meaning: Indicates the initial uplink MCS index of
UlSchC Mcs NBCEL -120002 Scheduli UEs of a coverage level. For details, see 3GPP TS
EAlgo LULSC 34 ng 36.211. This parameter applies only to NB-IoT.
HCEAL GUI Value Range: MCS_0(MCS_0),
GO MCS_1(MCS_1), MCS_2(MCS_2), MCS_3(MCS_3),
LST MCS_4(MCS_4), MCS_5(MCS_5), MCS_6(MCS_6),
NBCEL MCS_7(MCS_7), MCS_8(MCS_8), MCS_9(MCS_9),
LULSC MCS_10(MCS_10), MCS_11(MCS_11),
HCEAL MCS_12(MCS_12)
GO Unit: None
Actual Value Range: MCS_0, MCS_1, MCS_2,
MCS_3, MCS_4, MCS_5, MCS_6, MCS_7, MCS_8,
MCS_9, MCS_10, MCS_11, MCS_12
Default Value: MCS_9(MCS_9)
NbCell UlInitial MOD MLBFD Basic Meaning: Indicates the uplink initial transmission
UlSchC TransRp NBCEL -120002 Scheduli repetition times of UEs corresponding to a certain
EAlgo tCount LULSC 34 ng coverage level. This parameter applies only to NB-
HCEAL IoT.
GO GUI Value Range: REP_1(REP_1), REP_2(REP_2),
LST REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
NBCEL REP_32(REP_32), REP_64(REP_64),
LULSC REP_128(REP_128)
HCEAL Unit: None
GO
Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128
Default Value: REP_1(REP_1)
NbCell AckNac MOD MLBFD Basic Meaning: Indicates the uplink ACK/NACK repetition
UlSchC kTransR NBCEL -120002 Scheduli times for Msg4 of UEs of a coverage level. This
EAlgo ptCount LULSC 34 ng parameter applies only to NB-IoT.
Msg4 HCEAL GUI Value Range: REP_1(REP_1), REP_2(REP_2),
GO REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
LST REP_32(REP_32), REP_64(REP_64),
NBCEL REP_128(REP_128)
LULSC Unit: None
HCEAL
GO Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128
Default Value: REP_4(REP_4)
NbCell AckNac MOD MLBFD Basic Meaning: Indicates the uplink ACK/NACK repetition
UlSchC kTransR NBCEL -120002 Scheduli times for downlink scheduling of UEs of a coverage
EAlgo ptCount LULSC 34 ng level. This parameter applies only to NB-IoT.
HCEAL GUI Value Range: REP_1(REP_1), REP_2(REP_2),
GO REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
LST REP_32(REP_32), REP_64(REP_64),
NBCEL REP_128(REP_128)
LULSC Unit: None
HCEAL
GO Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128
Default Value: REP_2(REP_2)
CellDlsc NbDlHa MOD MLBFD Basic Meaning: Indicates the maximum number of downlink
hAlgo rqMaxT CELLD -120002 Scheduli HARQ transmissions. This parameter applies only to
xCount LSCHA 34 ng NB-IoT.
LGO GUI Value Range: 1~8
LST Unit: None
CELLD
LSCHA Actual Value Range: 1~8
LGO Default Value: 5
PDSCH Referen MOD LBFD-0 Dynami Meaning: Indicates the cell reference signal power of
Cfg ceSignal PDSCH 02016 / c each physical antenna. The cell reference signal power
Pwr CFG TDLBF Downlin delivered in SIB2 is that of each logical antenna. If the
LST D-00201 k Power EMTC_SWITCH option of the EmtcAlgoSwitch
PDSCH 6 Allocati parameter in a CellEmtcAlgo MO is selected and the
CFG LBFD-0 on value of this parameter is changed, eMTC UEs that
02009 / Broadca already accessed the cell will be proactively released.
TDLBF st of GUI Value Range: -600~500
D-00200 system Unit: 0.1dBm
9/ informat
MLBFD ion Actual Value Range: -60~50
-120002 Default Value: 182
29
eUCellS Referen ADD LBFD-0 Dynami Meaning: Indicates the reference signal power of the
ectorEq ceSignal EUCEL 02016 c cell sector equipment. The value 32767 indicates that
m Pwr LSECT LOFD-0 Downlin this reference signal power parameter is invalid. In
OREQ 03029 / k Power this case, the cell uses the reference signal power
M MLOFD Allocati specified in the PDSCHCfg MO. For details, see
MOD -121204 on 3GPP TS 36.213.This parameter is valid only when
EUCEL SFN the MultiRruCellFlag parameter of the Cell MO is set
LSECT to BOOLEAN_TRUE(True) and the
OREQ MultiRruCellMode parameter in the Cell MO is set to
M SFN(SFN), CELL_COMBINATION(Cell
Combination), or
LST MPRU_AGGREGATION(MPRU_AGGREGATION).
EUCEL
LSECT GUI Value Range: -600~500,32767
OREQ Unit: 0.1dBm
M Actual Value Range: -60~50,32767
Default Value: 32767
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 Unit: dBm
D-00200 Cell
9/ Actual Value Range: -30~36
Selectio
MLBFD n and Default Value: 23
-120002 Re-
29 selection
LBFD-0
0201803
/
TDLBF
D-00201
803
LOFD-0
02015
CellUlp FilterRsr MOD LBFD-0 Uplink Meaning: Indicates the alpha filtering coefficient used
cDedic p CELLU 02026 / Power by the UE during RSRP measurement for path loss
LPCDE TDLBF Control estimation. This parameter applies only to LTE FDD
DIC D-00202 and LTE TDD.
LST 6 GUI Value Range:
CELLU UU_FC0_FILTER_COEFF(UU_FC0_FILTER_COE
LPCDE FF),
DIC UU_FC1_FILTER_COEFF(UU_FC1_FILTER_COE
FF),
UU_FC2_FILTER_COEFF(UU_FC2_FILTER_COE
FF),
UU_FC3_FILTER_COEFF(UU_FC3_FILTER_COE
FF),
UU_FC4_FILTER_COEFF(UU_FC4_FILTER_COE
FF),
UU_FC5_FILTER_COEFF(UU_FC5_FILTER_COE
FF),
UU_FC6_FILTER_COEFF(UU_FC6_FILTER_COE
FF),
UU_FC7_FILTER_COEFF(UU_FC7_FILTER_COE
FF),
UU_FC8_FILTER_COEFF(UU_FC8_FILTER_COE
FF),
UU_FC9_FILTER_COEFF(UU_FC9_FILTER_COE
FF),
UU_FC11_FILTER_COEFF(UU_FC11_FILTER_CO
EFF),
UU_FC13_FILTER_COEFF(UU_FC13_FILTER_CO
EFF),
UU_FC15_FILTER_COEFF(UU_FC15_FILTER_CO
EFF),
UU_FC17_FILTER_COEFF(UU_FC17_FILTER_CO
EFF),
UU_FC19_FILTER_COEFF(UU_FC19_FILTER_CO
EFF)
Unit: None
Actual Value Range: UU_FC0_FILTER_COEFF,
UU_FC1_FILTER_COEFF,
UU_FC2_FILTER_COEFF,
UU_FC3_FILTER_COEFF,
UU_FC4_FILTER_COEFF,
UU_FC5_FILTER_COEFF,
UU_FC6_FILTER_COEFF,
UU_FC7_FILTER_COEFF,
UU_FC8_FILTER_COEFF,
UU_FC9_FILTER_COEFF,
UU_FC11_FILTER_COEFF,
UU_FC13_FILTER_COEFF,
UU_FC15_FILTER_COEFF,
UU_FC17_FILTER_COEFF,
UU_FC19_FILTER_COEFF
Default Value:
UU_FC6_FILTER_COEFF(UU_FC6_FILTER_COE
FF)
CellUlp DeltaPre MOD LBFD-0 Uplink Meaning: Indicates the power offset (delta value) of
cComm ambleM CELLU 02026 / Power message 3 relative to the preamble. This power offset
sg3 LPCCO TDLBF Control has a step size of 2. For details, see 3GPP TS 36.213.
MM D-00202 Broadca GUI Value Range: -1~6
LST 6 st of Unit: 2dB
CELLU LBFD-0 system
LPCCO 02009 / informat Actual Value Range: -2~12
MM TDLBF ion Default Value: 4
D-00200
9/
MLBFD
-120002
29
CellUlp P0Nomi MOD LBFD-0 Uplink Meaning: Indicates the nominal P0 value of the
cComm nalPUS CELLU 02026 / Power PUSCH. It is used in UL power control. For details,
CH LPCCO TDLBF Control see 3GPP TS 36.213.
MM D-00202 Broadca GUI Value Range: -126~24
LST 6 st of Unit: dBm
CELLU LBFD-0 system
LPCCO 02009 / informat Actual Value Range: -126~24
MM TDLBF ion Default Value: -67
D-00200
9/
MLBFD
-120002
29
CellUlp PassLos MOD LBFD-0 Uplink Meaning: Indicates the compensation factor for path
cComm sCoeff CELLU 02026 / Power loss. It is used in UL power control. For details, see
LPCCO TDLBF Control 3GPP TS 36.213.
MM D-00202 Broadca GUI Value Range: AL0(0), AL04(0.4), AL05(0.5),
LST 6 st of AL06(0.6), AL07(0.7), AL08(0.8), AL09(0.9),
CELLU LBFD-0 system AL1(1)
LPCCO 02009 / informat Unit: None
MM TDLBF ion
D-00200 Actual Value Range: AL0, AL04, AL05, AL06,
9/ AL07, AL08, AL09, AL1
MLBFD Default Value: AL07(0.7)
-120002
29
CellRac AcUser MOD LBFD-0 Admissi Meaning: Indicates the maximum number of UEs that
Thd Number CELLR 02023/ on can be admitted to the cell.
ACTHD TDLBF Control GUI Value Range: 0~65535
LST D-00202 System
3 Unit: None
CELLR Capabili
ACTHD PLBFD- ty Actual Value Range: 0~65535
001001 Default Value: 65535
ENodeB LTEPree MOD MLBFD 3GPP Meaning: Indicates whether to allow LTE UEs to
AlgoSwi mptNbS ENODE -120002 NB-IoT preempt the RRC connections of NB-IoT UEs during
tch witch BALGO Specific admission. When this parameter is set to ON, LTE
SWITC ations UEs can preempt the RRC connections of NB-IoT
H Complia UEs during admission. However, the number of
LST nt preempted RRC connections must not exceed the
ENODE minimum number of RRC connected UEs reserved for
BALGO NB-IoT. When this parameter is set to OFF, LTE UEs
SWITC cannot preempt the RRC connections of NB-IoT UEs
H during admission. This parameter applies only to LTE
FDD and NB-IoT.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
ENodeB NbRsv MOD MLBFD 3GPP Meaning: Indicates the minimum proportion of UEs in
NbPara MinUser ENODE -120002 NB-IoT RRC_CONNECTED mode reserved for NB-IoT. This
NumRat BNBPA Specific parameter applies only to LTE FDD and NB-IoT.
io RA ations GUI Value Range: 0~100
LST Complia
nt Unit: %
ENODE
BNBPA Actual Value Range: 0~100
RA Default Value: 0
only for LTE UEs and does not take effect for eMTC
UEs.
UeRaInforInqSwitch: Indicates whether the query of
UE random access information is enabled. If this
option is selected, the query of UE random access
information is enabled, and the eNodeB sends the
UEInformationRequest message to the UE complying
with 3GPP Release 9 and later and requires the UE to
report random access information. The eNodeB uses
the reported random access information for RACH
resource adjustment. If this option is deselected, the
query of UE random access information is disabled.
The eNodeB uses the self-collected random access
information for RACH resource adjustment. This
option applies only to LTE FDD and LTE TDD.
PRACHFalseAlarmDetSwitch: Indicates whether to
enable PRACH false alarm detection. If this option is
selected and the PrachFalseAlarmDetRadThd or
RachThdBoostRatio parameter is not set to 0, PRACH
false alarm detection is enabled. If the eNodeB
considers the initial contention-based preamble sent
by a UE as a PRACH false alarm, the eNodeB does
not send the UE a Random Access Response message,
nor records the preamble on the performance counter
L.RA.GrpA.Att or L.RA.GrpB.Att if the preamble
belongs to group A or B, respectively. If this option is
selected and the PrachFalseAlarmDetRadThd and
RachThdBoostRatio parameters are set to 0, PRACH
false alarm detection is disabled. If this option is
deselected, PRACH false alarm detection is disabled.
When the eMTC function takes effect, PRACH false
alarm detection takes effect only on LTE UEs. This
option applies only to LTE FDD and LTE TDD.
RachPwrAdjSwitch: Indicates whether to enable
power adjustment for the RACH. If both this option
and UeRaInforInqSwitch are selected, the eNodeB
dynamically adjusts the parameters related to power
control for the RACH based on the number of random
access preambles, probability of successful random
accesses, and target probability of successful random
accesses. If either this option or UeRaInforInqSwitch
is deselected, power adjustment for the RACH is
disabled. When the eMTC function takes effect,
power adjustment for the RACH takes effect only on
LTE UEs.
ForbidAcByRadiusSwitch: Indicates whether the
eNodeB controls UE access based on the distance
PRACHFalseAlaDetRetxOptSwitch:Off,
PrachFreqAbsAdjSwitch:Off, ExceedRadiusRaDetec-
tionSw:Off, NonContRaOptSwitch:Off
CellEA ABForE MOD MLOFD Broadca Meaning: Indicates the access barring status of
BAlgoP xception CELLE -120002 st of abnormal data. This parameter specifies whether NB-
ara Data ABALG 29 System IoT UEs can initiate access with the cause value being
OPARA MLBFD Informat mo-ExceptionData. When this parameter is set to
LST -121002 ion BOOLEAN_TRUE, NB-IoT UEs are not allowed to
CELLE 43 Congesti initiate access with the cause value being mo-
ABALG on ExceptionData. When this parameter is set to
OPARA Control BOOLEAN_FALSE, NB-IoT UEs can initiate access
with the cause value being mo-ExceptionData. This
parameter applies only to NB-IoT.
GUI Value Range:
BOOLEAN_FALSE(BOOLEAN_FALSE),
BOOLEAN_TRUE(BOOLEAN_TRUE)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value:
BOOLEAN_FALSE(BOOLEAN_FALSE)
CellEA EABCat MOD LEOFD- eNodeB Meaning: Indicates the category of UEs to which EAB
BAlgoP egory CELLE 120303 Supporti information is applied. If this parameter is set to
ara ABALG MLBFD ng MTC CATEGORY_A, EAB information is applied to all
OPARA -121002 Congesti EAB-applicable UEs. If this parameter to
LST 43 on CATEGORY_B, EAB information is applied to EAB-
CELLE Control applicable UEs that are not in the HPLMN and
ABALG EHPLMN. If this parameter is set to CATEGORY_C,
OPARA EAB information is applied to EAB-applicable UEs
that are not in the HPLMN, EHPLMN, and preferred
PLMN.
GUI Value Range: CATEGORY_A(Category_a),
CATEGORY_B(Category_b),
CATEGORY_C(Category_c)
Unit: None
Actual Value Range: CATEGORY_A,
CATEGORY_B, CATEGORY_C
Default Value: CATEGORY_A(Category_a)
CellEA EABStat MOD LEOFD- eNodeB Meaning: Indicates the period for measuring the
BAlgoP Period CELLE 120303 Supporti percentage of cell congestion duration for extended
ara ABALG MLBFD ng MTC access barring (EAB). An eNodeB periodically
OPARA -121002 Congesti determines the cell status based on the setting of this
LST 43 on parameter.
CELLE Control GUI Value Range: 10~60
ABALG Unit: s
OPARA
Actual Value Range: 10~60
Default Value: 20
CellEA EABTri MOD LEOFD- eNodeB Meaning: Indicates the threshold for triggering
BAlgoP ggerThd CELLE 120303 Supporti extended access barring (EAB). The threshold is
ara ABALG MLBFD ng MTC denoted by a percentage of cell congestion duration. If
OPARA -121002 Congesti the percentage of time when the cell is in a congestion
LST 43 on state is greater than or equal to the value of this
CELLE Control parameter within a statistics collection period
ABALG (specified by the EABStatPeriod parameter), the
OPARA conditions for triggering EAB are met.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 90
CellEA EABCa MOD LEOFD- eNodeB Meaning: Indicates the threshold for canceling
BAlgoP ncelThd CELLE 120303 Supporti extended access barring (EAB). The threshold is
ara ABALG MLBFD ng MTC denoted by a percentage of cell congestion duration. If
OPARA -121002 Congesti the percentage of time when the cell is in a congestion
LST 43 on state is less than or equal to the value of this parameter
CELLE Control within a statistics collection period (specified by the
ABALG EABStatPeriod parameter), the conditions for
OPARA canceling EAB are met.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 70
CellEA EABCa MOD LEOFD- eNodeB Meaning: Indicates the number of consecutive periods
BAlgoP ncelCon CELLE 120303 Supporti in which the conditions for canceling extended access
ara dSatiPer ABALG MLBFD ng MTC barring (EAB) are met. EAB can be canceled only
iod OPARA -121002 Congesti when the number of consecutive periods in which the
LST 43 on conditions for canceling EAB are met reaches the
CELLE Control value of this parameter.
ABALG GUI Value Range: 1~9
OPARA Unit: None
Actual Value Range: 1~9
Default Value: 2
CellDrx NbOnD MOD MLBFD DRX Meaning: Indicates the length of the On Duration
Para urationT CELLD -120002 Timer in an NB-IoT cell. The unit is the PDCCH
imer RXPAR 36 period of the coverage level corresponding to a UE.
A This parameter applies only to NB-IoT.
LST GUI Value Range: PP1(1 PDCCH period), PP2(2
CELLD PDCCH periods), PP3(3 PDCCH periods), PP4(4
RXPAR PDCCH periods), PP8(8 PDCCH periods), PP16(16
A PDCCH periods), PP32(32 PDCCH periods)
Unit: None
Actual Value Range: PP1, PP2, PP3, PP4, PP8, PP16,
PP32
Default Value: PP3(3 PDCCH periods)
CellDrx NbLong MOD MLBFD DRX Meaning: Indicates the length of the long DRX cycle
Para DrxCycl CELLD -120002 in an NB-IoT cell. This parameter applies only to NB-
e RXPAR 36 IoT.
A GUI Value Range: SF256(256 subframes), SF512(512
LST subframes), SF1024(1024 subframes), SF1536(1536
CELLD subframes), SF2048(2048 subframes), SF3072(3072
RXPAR subframes), SF4096(4096 subframes), SF4608(4608
A subframes), SF6144(6144 subframes), SF7680(7680
subframes), SF8192(8192 subframes), SF9216(9216
subframes)
Unit: None
Actual Value Range: SF256, SF512, SF1024, SF1536,
SF2048, SF3072, SF4096, SF4608, SF6144, SF7680,
SF8192, SF9216
Default Value: SF2048(2048 subframes)
CellDrx NbDrxI MOD MLBFD DRX Meaning: Indicates the length of the DRX Inactivity
Para nactivity CELLD -120002 Timer in an NB-IoT cell. The unit is the PDCCH
Timer RXPAR 36 period of the coverage level corresponding to a UE.
A This parameter applies only to NB-IoT.
LST GUI Value Range: PP0(0 PDCCH period), PP1(1
CELLD PDCCH period), PP2(2 PDCCH periods), PP3(3
RXPAR PDCCH periods), PP4(4 PDCCH periods), PP8(8
A PDCCH periods), PP16(16 PDCCH periods), PP32(32
PDCCH periods)
Unit: None
Actual Value Range: PP0, PP1, PP2, PP3, PP4, PP8,
PP16, PP32
Default Value: PP3(3 PDCCH periods)
CellDrx NbDrxR MOD MLBFD DRX Meaning: Indicates the length of the DRX
Para eTxTim CELLD -120002 Retransmission Timer in an NB-IoT cell. The unit is
er RXPAR 36 the PDCCH period of the coverage level
A corresponding to a UE. This parameter applies only to
LST NB-IoT.
CELLD GUI Value Range: PP0(0 PDCCH period), PP1(1
RXPAR PDCCH period), PP2(2 PDCCH periods), PP4(4
A PDCCH periods), PP6(6 PDCCH periods), PP8(8
PDCCH periods), PP16(16 PDCCH periods), PP24(24
PDCCH periods), PP33(33 PDCCH periods)
Unit: None
Actual Value Range: PP0, PP1, PP2, PP4, PP6, PP8,
PP16, PP24, PP33
Default Value: PP6(6 PDCCH periods)
CellDrx NbDrxU MOD MLBFD DRX Meaning: Indicates the length of the DRX uplink
Para lReTxTi CELLD -120002 retransmission timer in an NB-IoT cell. The unit is the
mer RXPAR 36 PDCCH period of the coverage level corresponding to
A a UE. This parameter applies only to NB-IoT.
LST GUI Value Range: PP0(0 PDCCH period), PP1(1
CELLD PDCCH period), PP2(2 PDCCH periods), PP4(4
RXPAR PDCCH periods), PP6(6 PDCCH periods), PP8(8
A PDCCH periods), PP16(16 PDCCH periods), PP24(24
PDCCH periods), PP33(33 PDCCH periods), PP40(40
PDCCH periods), PP64(64 PDCCH periods), PP80(80
PDCCH periods), PP96(96 PDCCH periods),
PP112(112 PDCCH periods), PP128(128 PDCCH
periods), PP160(160 PDCCH periods), PP320(320
PDCCH periods)
Unit: None
Actual Value Range: PP0, PP1, PP2, PP4, PP6, PP8,
PP16, PP24, PP33, PP40, PP64, PP80, PP96, PP112,
PP128, PP160, PP320
Default Value: PP24(24 PDCCH periods)
TIMES TIMES SET None None Meaning: Indicates the external reference time source
RC RC TIMES of the NE.
RC GUI Value Range: NTP(NTP), GPS(GPS),
DSP NONE(None), SYSCLK(SYSCLK)
TIMES Unit: None
RC
Actual Value Range: NTP, GPS, NONE, SYSCLK
LST
LATES Default Value: NTP(NTP)
TSUCC
DATE
LST
TIMES
RC
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 DL 4x4 and 1) are configured. The value CRS_PORT_4
D-00100 MIMO indicates that four CRS ports (ports 0, 1, 2, and 3) are
3 Based configured.
on TM3 GUI Value Range: CRS_PORT_1(1 port),
LOFD-0 and
01060 CRS_PORT_2(2 ports), CRS_PORT_4(4 ports)
TM4
TDLOF Unit: None
DL 64-
D-00106 Antenna Actual Value Range: CRS_PORT_1, CRS_PORT_2,
0 3D- CRS_PORT_4
TDLEO Beamfor Default Value: CRS_PORT_2(2 ports)
FD-121 ming
603
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, 64T64R
LST Unit: None
CELL Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
4T4R, 8T8R, 2T8R, 4T8R, 64T64R
Default Value: None
Cell CrsPort ADD LOFD-0 DL 2x2 Meaning: Indicates the mapping between a cell-
Map CELL 01001 / MIMO specific reference signal (CRS) port and a transmit
MOD TDLOF DL 4x2 (TX) channel in an RRU. In cells with one or two TX
CELL D-00100 MIMO channels, this parameter cannot be set. In cells with
1 four or eight TX channels, this parameter can be set.
LST DL 4x4 As defined in 3GPP specifications, the CrsPortNum
CELL LOFD-0 MIMO
01003 / parameter can be set to CRS_PORT_1,
TDLOF DL 4x4 CRS_PORT_2, or CRS_PORT_4. The value
D-00100 MIMO CRS_PORT_1 indicates that one CRS port (port 0) is
3 Based configured. The value CRS_PORT_2 indicates that
on TM3 two CRS ports (ports 0 and 1) are configured. The
LOFD-0 and value CRS_PORT_4 indicates that four CRS ports
01060 TM4 (ports 0, 1, 2 and 3). In values of this parameter,
TDLOF DL 4- mTnP indicates that the number of TX channels
D-00106 Antenna configured for a cell is "m" and the number of CRS
0 Transmi ports is "n". The parameter value 4TnP_abcd indicates
MLBFD t that reference signals transmitted over CRS ports a, b,
-121002 Diversit c, and d are mapped to TX channels 1, 2, 3, and 4 in
40 y an RRU, respectively (The TX channel number here is
for reference only, and is determined based on the
R0A to R0D, or others). The parameter value
8TnP_abcdefgh indicates that reference signals
transmitted over CRS ports a to h are mapped to TX
channels 1 to 8 in an RRU, respectively. Duplicate
numbers of abcd or abcdefgh indicates that virtual
antenna mapping (VAM) is applied, that is, the
reference signals transmitted over the CRS port are
mapped to corresponding TX channels. The parameter
value NOT_CFG indicates that the mapping between
a CRS port and a TX channel in an RRU is not
configured, and CRS ports are mapped to TX channels
in an RRU in a default manner. In TDD cells, "n" in
mTnP must be equal to the CrsPortNum parameter
value. For cells established on LBBPc boards, the
parameter value NOT_CFG takes effect regardless of
the actual parameter setting. This parameter applies
only to LTE FDD and LTE TDD.
GUI Value Range: NOT_CFG(Not configure),
4T4P_0213(4T4P_0213), 4T4P_0231(4T4P_0231),
4T4P_0123(4T4P_0123), 4T4P_0132(4T4P_0132),
4T4P_0312(4T4P_0312), 4T4P_0321(4T4P_0321),
4T2P_0011(4T2P_0011), 4T2P_0101(4T2P_0101),
4T2P_0110(4T2P_0110),
8T2P_00001111(8T2P_00001111),
8T2P_00110011(8T2P_00110011),
8T2P_01010101(8T2P_01010101),
8T4P_00112233(8T4P_00112233),
8T4P_01230123(8T4P_01230123)
Unit: None
Actual Value Range: NOT_CFG, 4T4P_0213,
4T4P_0231, 4T4P_0123, 4T4P_0132, 4T4P_0312,
4T4P_0321, 4T2P_0011, 4T2P_0101, 4T2P_0110,
8T2P_00001111, 8T2P_00110011, 8T2P_01010101,
8T4P_00112233, 8T4P_01230123
Default Value: NOT_CFG(Not configure)
CellPdc PdcchSy MOD LBFD-0 Physical Meaning: Indicates whether to enable dynamic
chAlgo mNumS CELLP 02003 / Channel adjustment on the number of orthogonal frequency
witch DCCHA TDLBF Manage division multiplexing (OFDM) symbols occupied by
LGO D-00200 ment the physical downlink control channel (PDCCH). If
LST 3 Enhance this parameter is set to OFF(Off), the number of
CELLP LBFD-0 d DL OFDM symbols occupied by the PDCCH is fixed and
DCCHA 60103 / Frequen cannot be dynamically adjusted. If this parameter is
LGO TDLBF cy set to ON(On), the number of OFDM symbols
D-08010 Selectiv occupied by the PDCCH is dynamically adjusted
2 e based on the required number of PDCCH control
Scheduli channel elements (CCEs). The OFDM symbol number
ng adjustment range can be determined by referring to
the MML reference of the InitPdcchSymNum
parameter. If this parameter is set to
ECFIADAPTIONON(Enhanced CFI Adaption On),
the number of OFDM symbols occupied by the
PDCCH is dynamically adjusted based on the cell
downlink throughput, and the adjustment performance
is the best among the three methods. The OFDM
symbol number adjustment range can be determined
by referring to the MML reference of the
InitPdcchSymNum parameter. If the EMTC_SWITCH
option of the EmtcAlgoSwitch parameter in a
CellEmtcAlgo MO is selected and the value of this
parameter is changed, the value of the startSymbolBR
IE is changed, and eMTC UEs that already accessed
the cell will be proactively released. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: OFF(Off), ON(On),
ECFIADAPTIONON(Enhanced CFI Adaption On)
Unit: None
Actual Value Range: OFF, ON, ECFIADAPTIONON
Default Value: ECFIADAPTIONON(Enhanced CFI
Adaption On)
eNodeB CpuLoa MOD LOFD-0 Intellige Meaning: Indicates the CPU load threshold of a board.
FlowCtr dThd ENODE 70207 / nt If the CPU load of a main control board or baseband
lPara BFLOW TDLOF Access processing unit serving the cells is greater than or
CTRLP D-07020 Class equal to this parameter value, the cells are congested.
ARA 7 Control If the CPU load is less than this parameter value, the
LST LOFD-0 Dynami cells are not congested. This parameter takes effect
ENODE 08002 / c only when the DynAcBarPolicyMode parameter is set
BFLOW TDLOF Service to CPULOAD(CPULOAD).
CTRLP D-00800 Specific GUI Value Range: 50~100
ARA 2 Access Unit: %
LEOFD- Control
Actual Value Range: 50~100
120303 MTC
Default Value: 80
SECTO SECTO ADD None None Meaning: Indicates the number of the sector.
R RID SECTO GUI Value Range: 0~65535
R
Unit: None
DSP
SECTO Actual Value Range: 0~65535
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
Unit: None
MOD
SECTO Actual Value Range: 0~99 characters
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. Generally, the LocationName parameter is set
ME R to the same value for all sectors in an RF site, and
MOD base station can acquire the location information of
SECTO RF modules through this parameter. However, if the
R LocationName parameter of the RF module is set in
the RRU or AAS MO, the base station will acquire the
LST location information of RF modules through the RRU
SECTO or AAS MO.
R
GUI Value Range: 0~64 characters
Unit: None
Actual Value Range: 0~64 characters
Default Value: NULL(empty string)
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 Unit: None
R Actual Value Range: 0~255 characters
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 Unit: None
SECTO
REQM Actual Value Range: 0~65535
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 Unit: None
SECTO
REQM Actual Value Range: 0~65535
Default Value: None
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
Unit: None
LST
BASEB Actual Value Range: 0~23
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
BASEB BASEB ADD None None Meaning: Indicates the type of baseband equipment.
ANDEQ ANDEQ BASEB GUI Value Range: UL(UL), DL(DL),
M MTYPE ANDEQ ULDL(Combined UL and DL)
M
Unit: None
LST
BASEB Actual Value Range: UL, DL, ULDL
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator.
ator atorId CNOPE 01036 / Sharing GUI Value Range: 0~5
RATOR TDLOF with
D-00103 Commo Unit: None
LST
CNOPE 6 n Actual Value Range: 0~5
RATOR MLOFD Carrier Default Value: None
MOD -121251 NB-IoT
CNOPE LOFD-0 RAN
RATOR 01037 / Sharing
TDLOF with
RMV Commo
CNOPE D-00103
7 n
RATOR Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
01086 / Dedicate
TDLOF d
D-00108 Carrier
6
NB-IoT
LOFD-0 RAN
70206 / Sharing
TDLOF with
D-08122 Dedicate
4 d
Carrier
RAN
Sharing
by More
Operator
s
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 Unit: None
MOD
CNOPE 6 n Actual Value Range: 1~32 characters
RATOR MLOFD Carrier Default Value: None
LST -121251 NB-IoT
CNOPE LOFD-0 RAN
RATOR 01037 / Sharing
TDLOF with
D-00103 Commo
7 n
Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
01086 / Dedicate
TDLOF d
D-00108 Carrier
6
NB-IoT
LOFD-0 RAN
70206 / Sharing
TDLOF with
D-08122 Dedicate
4 d
Carrier
RAN
Sharing
by More
Operator
s
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 MLOFD Carrier GUI Value Range:
LST -121251 NB-IoT CNOPERATOR_PRIMARY(Primary Operator),
CNOPE LOFD-0 RAN CNOPERATOR_SECONDARY(Secondary Operator)
RATOR 01037 / Sharing Unit: None
TDLOF with
Commo Actual Value Range: CNOPERATOR_PRIMARY,
D-00103 CNOPERATOR_SECONDARY
7 n
Carrier Default Value: None
MLOFD
-121252 RAN
Sharing
LOFD-0 with
01086 / Dedicate
TDLOF d
D-00108 Carrier
6
NB-IoT
LOFD-0 RAN
70206 / Sharing
TDLOF with
D-08122 Dedicate
4 d
Carrier
RAN
Sharing
by More
Operator
s
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 Unit: None
CNOPE
RATOR MLOFD Carrier Actual Value Range: 000~999
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 decimal digits.
MOD D-00103 Commo GUI Value Range: 2~3 characters
CNOPE 6 n
Carrier Unit: None
RATOR MLOFD
-121251 NB-IoT Actual Value Range: 00~99,000~999
LST
CNOPE LOFD-0 RAN Default Value: None
RATOR 01037 / Sharing
TDLOF with
D-00103 Commo
7 n
Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
01086 / Dedicate
TDLOF d
D-00108 Carrier
6
NB-IoT
LOFD-0 RAN
70206 / Sharing
TDLOF with
D-08122 Dedicate
4 d
Carrier
RAN
Sharing
by More
Operator
s
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 MLOFD Carrier configured in the EPC TAL.
RATOR -121251 NB-IoT GUI Value Range: 0~65535
TA LOFD-0 RAN Unit: None
MOD 01037 / Sharing
with Actual Value Range: 0~65535
CNOPE TDLOF
RATOR D-00103 Commo Default Value: None
TA 7 n
Carrier
RMV MLOFD
CNOPE -121252 RAN
RATOR Sharing
LOFD-0 with
TA 70206 / Dedicate
TDLOF d
D-08122 Carrier
4
NB-IoT
MLBFD RAN
-120002 Sharing
29 with
MLBFD Dedicate
-120002 d
37 Carrier
Hybrid
RAN
Sharing
Broadca
st of
system
informat
ion
Cell
Selectio
n and
Re-
selection
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 Unit: None
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.
MOD 6 n GUI Value Range: 1~65533,65535
CNOPE MLOFD Carrier
Unit: None
RATOR -121251 NB-IoT
TA RAN Actual Value Range: 1~65533,65535
LOFD-0
LST 01037 / Sharing Default Value: None
CNOPE TDLOF with
RATOR D-00103 Commo
TA 7 n
Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
70206 / Dedicate
TDLOF d
D-08122 Carrier
4
NB-IoT
RAN
Sharing
with
Dedicate
d
Carrier
Hybrid
RAN
Sharing
CnOper NbIotTa ADD MLBFD S1-flex Meaning: Indicates whether the current TAI applies
atorTa Flag CNOPE -120003 only to NB-IoT. If this parameter is set to
RATOR 10 BOOLEAN_TRUE, the current TAI applies only to
TA NB-IoT. If this parameter is set to
MOD BOOLEAN_FALSE, the current TAI does not apply
CNOPE to NB-IoT. In accordance with 3GPP specifications,
RATOR NB-IoT does not support inter-RAT mobility.
TA Therefore, the TAIs of NB-IoT must be different from
those of LTE FDD and LTE TDD. For details, see
LST section 5.3.3 in 3GPP TS 23.401 V13.7.0. This
CNOPE parameter applies only to NB-IoT.
RATOR
TA GUI Value Range:
BOOLEAN_FALSE(BOOLEAN_FALSE),
BOOLEAN_TRUE(BOOLEAN_TRUE)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value:
BOOLEAN_FALSE(BOOLEAN_FALSE)
MmeCa MmeCa ADD MLBFD Data Meaning: Indicates the MME capability configuration
pInfo pCfgId MMEC -120002 over index.
APINF 04 NAS GUI Value Range: 0~63
O MLBFD S1-flex Unit: None
LST -120003 Data
MMEC 10 Actual Value Range: 0~63
over
APINF MLBFD User Default Value: None
O -121002 Plane
MOD 05 eMTC
MMEC MLOFD Introduc
APINF -121280 tion
O
RMV
MMEC
APINF
O
MmeCa S1CfgT ADD MLBFD Data Meaning: Indicates the configuration type of the S1
pInfo ype MMEC -120002 over interface. Set this parameter to S1_CFG if operators
APINF 04 NAS want to configure the MME capability according to
O MLBFD S1-flex the S1 MO. Set this parameter to
LST -120003 S1INTERFACE_CFG if operators want to configure
Data the MME capability according to the S1Interface MO.
MMEC 10 over
APINF MLBFD User GUI Value Range: S1_CFG(S1_CFG),
O -121002 Plane S1INTERFACE_CFG(S1INTERFACE_CFG)
05 eMTC Unit: None
MLOFD Introduc Actual Value Range: S1_CFG, S1INTERFACE_CFG
-121280 tion Default Value: None
/
TDLEO
FD-121
611
MmeCa S1Id ADD MLBFD Data Meaning: Indicates the S1 object ID.
pInfo MMEC -120002 over GUI Value Range: 0~31
APINF 04 NAS
O Unit: None
MLBFD S1-flex
LST -120003 Actual Value Range: 0~31
eMTC
MMEC 10 Introduc Default Value: None
APINF MLOFD tion
O -121280
MmeCa S1Interf ADD MLBFD Data Meaning: Indicates the S1 interface ID.
pInfo aceId MMEC -120002 over GUI Value Range: 0~65534
APINF 04 NAS
O Unit: None
MLBFD S1-flex
LST -120003 Actual Value Range: 0~65534
Data
MMEC 10 over Default Value: None
APINF MLBFD User
O -121002 Plane
05 eMTC
MLOFD Introduc
-121280 tion
RlcPdcp RlcPdcp ADD LBFD-0 Radio Meaning: Indicates the ID of the RLC/PDCP
ParaGro ParaGro RLCPD 02008 / Bearer parameter group.
up upId CPPAR TDLBF Manage GUI Value Range: 0~159
AGROU D-00200 ment
P 8 Data Unit: None
RlcPdcp CatType ADD LBFD-0 Radio Meaning: Indicates the UE category type. Other
ParaGro RLCPD 02008 / Bearer parameters in this MO apply to LTE UEs, eMTC UEs
up CPPAR TDLBF Manage in mode A, eMTC UEs in mode B, and NB-IoT UEs if
AGROU D-00200 ment this parameter is set to LTE, EMTC_MODE_A,
P 8/ Data EMTC_MODE_B, and NBIOT, respectively.
MOD MLBFD over GUI Value Range: LTE(LTE),
RLCPD -121002 User EMTC_MODE_A(EMTC_MODE_A),
CPPAR 05 Plane EMTC_MODE_B(EMTC_MODE_B), NBIOT(NB-
AGROU MLOFD eMTC IoT)
P -121280 Introduc Unit: None
LST / tion
TDLEO Actual Value Range: LTE, EMTC_MODE_A,
RLCPD EMTC_MODE_B, NBIOT
CPPAR FD-121
AGROU 611 Default Value: LTE(LTE)
P
RlcPdcp NbPdcp ADD MLBFD Data Meaning: Indicates the length of the PDCP discard
ParaGro Discard RLCPD -121002 over timer. For details about this parameter, see 3GPP TS
up Timer CPPAR 05 User 36.323. This parameter applies only to NB-IoT.
AGROU Plane GUI Value Range: DiscardTimer_5120(5120),
P DiscardTimer_10240(10240),
MOD DiscardTimer_20480(20480),
RLCPD DiscardTimer_40960(40960),
CPPAR DiscardTimer_81920(81920),
AGROU DiscardTimer_Infinity(Infinity)
P Unit: None
LST Actual Value Range: DiscardTimer_5120,
RLCPD DiscardTimer_10240, DiscardTimer_20480,
CPPAR DiscardTimer_40960, DiscardTimer_81920,
AGROU DiscardTimer_Infinity
P
Default Value: DiscardTimer_Infinity(Infinity)
RlcPdcp NbDlPd ADD MLBFD Data Meaning: Indicates the length of the downlink PDCP
ParaGro cpDiscar RLCPD -121002 over discard timer in the eNodeB. If PDCP PDUs have
up dTimer CPPAR 05 User been buffered for a period longer than the timer
AGROU Plane length, the eNodeB discards the PDUs. This timer is
P valid only on DRBs. For details about this parameter,
MOD see 3GPP TS 36.323. This parameter applies only to
RLCPD NB-IoT.
CPPAR GUI Value Range: DiscardTimer_5120(5120),
AGROU DiscardTimer_10240(10240),
P DiscardTimer_20480(20480),
LST DiscardTimer_40960(40960),
RLCPD DiscardTimer_81920(81920),
CPPAR DiscardTimer_Infinity(Infinity)
AGROU Unit: None
P Actual Value Range: DiscardTimer_5120,
DiscardTimer_10240, DiscardTimer_20480,
DiscardTimer_40960, DiscardTimer_81920,
DiscardTimer_Infinity
Default Value: DiscardTimer_Infinity(Infinity)
RlcPdcp RlcMod ADD LBFD-0 Radio Meaning: Indicates the RLC transmission mode. Only
ParaGro e RLCPD 02008 / Bearer the AM and UM modes are available. This parameter
up CPPAR TDLBF Manage applies only to LTE FDD and LTE TDD.
AGROU D-00200 ment GUI Value Range: RlcMode_AM(Acknowledge
P 8 Mode), RlcMode_UM(Un-acknowledge Mode)
MOD Unit: None
RLCPD
CPPAR Actual Value Range: RlcMode_AM, RlcMode_UM
AGROU Default Value: RlcMode_AM(Acknowledge Mode)
P
LST
RLCPD
CPPAR
AGROU
P
RlcPdcp UeMax ADD LBFD-0 Radio Meaning: Indicates the UE-specific maximum number
ParaGro RetxThr RLCPD 02008 / Bearer of RLC ARQ retransmissions, namely the maximum
up eshold CPPAR TDLBF Manage number of AM PDU retransmissions. When the
AGROU D-00200 ment number of retransmissions reaches the value of this
P 8 Data parameter, RRC connection re-establishment is
MOD MLBFD over initiated.
RLCPD -121002 User GUI Value Range: Maxretx_Threshold_t1(1),
CPPAR 05 Plane Maxretx_Threshold_t2(2), Maxretx_Threshold_t3(3),
AGROU Maxretx_Threshold_t4(4), Maxretx_Threshold_t6(6),
P Maxretx_Threshold_t8(8),
LST Maxretx_Threshold_t16(16),
RLCPD Maxretx_Threshold_t32(32)
CPPAR Unit: None
AGROU Actual Value Range: Maxretx_Threshold_t1,
P Maxretx_Threshold_t2, Maxretx_Threshold_t3,
Maxretx_Threshold_t4, Maxretx_Threshold_t6,
Maxretx_Threshold_t8, Maxretx_Threshold_t16,
Maxretx_Threshold_t32
Default Value: Maxretx_Threshold_t32(32)
RlcPdcp ENodeB ADD LBFD-0 Radio Meaning: Indicates the eNodeB-specific maximum
ParaGro MaxRet RLCPD 02008 / Bearer number of RLC ARQ retransmissions, which limits
up xThresh CPPAR TDLBF Manage the maximum number of acknowledged mode (AM)
old AGROU D-00200 ment PDU retransmissions. When the number of RLC ARQ
P 8 Data retransmissions reaches the value of this parameter,
MOD MLBFD over eNodeB releases the UE.
RLCPD -121002 User GUI Value Range: Maxretx_Threshold_t1(1),
CPPAR 05 Plane Maxretx_Threshold_t2(2), Maxretx_Threshold_t3(3),
AGROU Maxretx_Threshold_t4(4), Maxretx_Threshold_t6(6),
P Maxretx_Threshold_t8(8),
LST Maxretx_Threshold_t16(16),
RLCPD Maxretx_Threshold_t32(32)
CPPAR Unit: None
AGROU Actual Value Range: Maxretx_Threshold_t1,
P Maxretx_Threshold_t2, Maxretx_Threshold_t3,
Maxretx_Threshold_t4, Maxretx_Threshold_t6,
Maxretx_Threshold_t8, Maxretx_Threshold_t16,
Maxretx_Threshold_t32
Default Value: Maxretx_Threshold_t32(32)
RlcPdcp NbUePo ADD MLBFD Data Meaning: Indicates the length of the Polling PDU
ParaGro llRetxTi RLCPD -121002 over retransmission timer for the UE. For details about this
up mer CPPAR 05 User parameter, see 3GPP TS 36.322. This parameter
AGROU Plane applies only to NB-IoT.
P GUI Value Range: Tpollretrans_m250(250),
MOD Tpollretrans_m500(500), Tpollretrans_m1000(1000),
RLCPD Tpollretrans_m2000(2000),
CPPAR Tpollretrans_m3000(3000),
AGROU Tpollretrans_m4000(4000),
P Tpollretrans_m6000(6000),
LST Tpollretrans_m10000(10000),
RLCPD Tpollretrans_m15000(15000),
CPPAR Tpollretrans_m25000(25000),
AGROU Tpollretrans_m40000(40000),
P Tpollretrans_m60000(60000),
Tpollretrans_m90000(90000),
Tpollretrans_m120000(120000),
Tpollretrans_m180000(180000)
Unit: None
Actual Value Range: Tpollretrans_m250,
Tpollretrans_m500, Tpollretrans_m1000,
Tpollretrans_m2000, Tpollretrans_m3000,
Tpollretrans_m4000, Tpollretrans_m6000,
Tpollretrans_m10000, Tpollretrans_m15000,
Tpollretrans_m25000, Tpollretrans_m40000,
Tpollretrans_m60000, Tpollretrans_m90000,
Tpollretrans_m120000, Tpollretrans_m180000
Default Value: Tpollretrans_m25000(25000)
RlcPdcp NbEnod ADD MLBFD Data Meaning: Indicates the length of the Polling PDU
ParaGro ebPollR RLCPD -121002 over retransmission timer for the eNodeB. For details about
up etxTime CPPAR 05 User this parameter, see 3GPP TS 36.322. This parameter
r AGROU Plane applies only to NB-IoT.
P GUI Value Range: Tpollretrans_m250(250),
MOD Tpollretrans_m500(500), Tpollretrans_m1000(1000),
RLCPD Tpollretrans_m2000(2000),
CPPAR Tpollretrans_m3000(3000),
AGROU Tpollretrans_m4000(4000),
P Tpollretrans_m6000(6000),
LST Tpollretrans_m10000(10000),
RLCPD Tpollretrans_m15000(15000),
CPPAR Tpollretrans_m25000(25000),
AGROU Tpollretrans_m40000(40000),
P Tpollretrans_m60000(60000),
Tpollretrans_m90000(90000),
Tpollretrans_m120000(120000),
Tpollretrans_m180000(180000)
Unit: None
Actual Value Range: Tpollretrans_m250,
Tpollretrans_m500, Tpollretrans_m1000,
Tpollretrans_m2000, Tpollretrans_m3000,
Tpollretrans_m4000, Tpollretrans_m6000,
Tpollretrans_m10000, Tpollretrans_m15000,
Tpollretrans_m25000, Tpollretrans_m40000,
Tpollretrans_m60000, Tpollretrans_m90000,
Tpollretrans_m120000, Tpollretrans_m180000
Default Value: Tpollretrans_m25000(25000)
RlcPdcp UlDlDis ADD LBFD-0 Radio Meaning: Indicates whether to enable separate
ParaGro cardtime RLCPD 02008 / Bearer configuration of the PDCP discard timer for the uplink
up rSwitch CPPAR TDLBF Manage and downlink.
AGROU D-00200 ment GUI Value Range: OFF(Off), ON(On)
P 8 Data
MLBFD over Unit: None
MOD
RLCPD -121002 User Actual Value Range: OFF, ON
CPPAR 05 Plane Default Value: OFF(Off)
AGROU
P
LST
RLCPD
CPPAR
AGROU
P
QciPara Qci ADD LBFD-0 Dynami Meaning: Indicates the QCI, which is an attribute of
QCIPA 0101502 c EPS bearers. Different QCIs represent different QoS
RA / Scheduli specifications such as the packet delay budget, packet
LST TDLBF ng loss rate (PLR) and packet error rate (PER), and
QCIPA D-00101 Basic resource type (whether the service is a GBR service or
RA 502 Scheduli not). For details, see Table 6.1.7 in 3GPP TS 23.203.
MOD LBFD-0 ng GUI Value Range:
QCIPA 02025 / Enhance 1,2,3,4,5,6,7,8,9,10~64,65,66,67~68,69,70,71~254
RA TDLBF d Unit: None
D-00202 Scheduli
RMV 5 Actual Value Range:
QCIPA ng 1,2,3,4,5,6,7,8,9,10~64,65,66,67~68,69,70,71~254
RA LBFD-0 Data
01015 / Default Value: None
over
TDLBF User
D-00101 Plane
5
MLBFD
-121002
05
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Unit: None
ADD Actual Value Range: 0~255
CELLB
Default Value: None
AND
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLC
ALIBR
ATION
DSP
CELLC
AMCST
ATUS
DSP
CELLH
LHCHK
DSP
CELLL
AA
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
CELLU
LICCL
USTER
DSP
DDCEL
LGROU
P
DSP
LIOPTR
ULE
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND
RMV
CELLN
RT
RST
EUCEL
LRES
STR
CELLH
LHCHK
STR
CELLR
FLOOP
BACK
STR
CELLS
ELFTES
T
STR
LRTWP
RTTST
STR
PRIBBP
ADJUS
T
UBL
CELL
DSP
CELLB
YLOCA
TION
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 Unit: None
CELL
Actual Value Range: 1~99 characters
DSP
CELL Default Value: None
LST
CELL
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 set up on 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 Unit: None
02009 / Actual Value Range: NORMAL_CP,
TDLBF EXTENDED_CP
D-00200
9/ Default Value: NORMAL_CP(Normal)
MLBFD
-120002
29
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 eMTC UL cyclic prefix length can be different from the DL
CELL Introduc one. In addition, the UL or DL cyclic prefix length of
LOFD-0 tion
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)
TDLEO Unit: None
FD-121 Actual Value Range: NORMAL_CP,
611 EXTENDED_CP
Default Value: NORMAL_CP(Normal)
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.
DSP MLBFD
CELLB GUI Value Range: 0~255
-120002
YLOCA 29 Unit: None
TION Actual Value Range: 0~255
DSP Default Value: None
CELLC
AMCST
ATUS
LST
CELL
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-00200 informat GUI Value Range: CELL_FDD(FDD),
9 ion CELL_TDD(TDD)
LST
CELL TDLBF Basic Unit: None
D-00100 uplink-
7 downlin Actual Value Range: CELL_FDD, CELL_TDD
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
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- Unit: None
CELL TDLOF BBP
D-00200 Actual Value Range: BOOLEAN_FALSE,
SFN BOOLEAN_TRUE
8
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 Unit: None
D-00200 Inter-
8 BBU Actual Value Range: SFN, CELL_COMBINATION,
SFN TWO_RRU_COMBINATION,
TDLOF DIGITAL_COMBINATION,
D-00109 Inter-
BBP MPRU_AGGREGATION
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 UserLab ADD None None Meaning: Indicates the user label of the cell.
el CELL GUI Value Range: 0~256 characters
MOD
Unit: None
CELL
Actual Value Range: 0~256
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), LAA(License Assisted
LST Downlin
CELL 02 Access)
k 2CC
LAOFD Unit: None
-001002 Inter-
Band Actual Value Range: UL_DL, DL_ONLY, LAA
01
Carrier Default Value: UL_DL(Uplink and downlink)
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
Prb LocalCe ADD None None Meaning: Indicates the local ID of a cell, which
llId PRB uniquely identifies a cell within an eNodeB.
LST GUI Value Range: 0~255
PRB Unit: None
MOD Actual Value Range: 0~255
PRB
Default Value: None
RMV
PRB
Prb PrbId ADD MLBFD 3GPP Meaning: Indicates the NB-IoT PRB identity. It
PRB -120002 R13 uniquely identifies a PRB within a cell. This
LST 01 NB-IoT parameter applies only to NB-IoT.
PRB Specific GUI Value Range: 0~255
ations
MOD Unit: None
PRB Actual Value Range: 0~255
RMV Default Value: None
PRB
Cell FreqBan ADD LBFD-0 Cell Meaning: Indicates the frequency band in which a cell
d CELL 0201803 Selectio operates. For details about this parameter, see 3GPP
ADD / n and TS 36.104. For details about the usage of 252 to 255,
CELLB TDLBF Re- see the following LTE-U forum document: eNodeB
AND D-00201 selection Minimum Requirements for LTE-U SDL V1.0. This
803 Broadca parameter applies only to LTE FDD and LTE TDD.
LST
CELLB LBFD-0 st of GUI Value Range: 1~256
AND 02009 / system Unit: None
TDLBF informat
MOD D-00200 ion Actual Value Range: 1~256
CELL 9 Default Value: None
Multi-
RMV LBFD-0 Band
CELLB 70103 / Compati
AND TDLBF bility
LST D-00201 Enhance
CELL 806 ment
LEOFD- License
111301 d
Assisted
Access
(LAA)
for CA
eUCellS LocalCe ADD LOFD-0 Intra- Meaning: Indicates the local ID of a cell. It uniquely
ectorEq llId EUCEL 03032 BBU identifies a cell within an eNodeB.
m LSECT Baseban GUI Value Range: 0~255
OREQ d
M Sharing Unit: None
eUCellS SectorE ADD LOFD-0 Intra- Meaning: Indicates the ID of the sector equipment
ectorEq qmId EUCEL 03032 BBU serving a cell. It uniquely identifies a piece of sector
m LSECT Baseban equipment within an eNodeB.
OREQ d GUI Value Range: 0~65535
M Sharing
(2T) Unit: None
ADD
PRBTO Actual Value Range: 0~65535
EUCEL Default Value: None
LSECT
OREQ
M
DSP
EURTW
P
LST
EUCEL
LSECT
OREQ
M
LST
PRBTO
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
RMV
PRBTO
EUCEL
LSECT
OREQ
M
RST
EUCEL
LRES
DSP
INREC
eUCellS SectorC ADD LOFD-0 CPRI Meaning: Indicates the common public radio interface
ectorEq priComp EUCEL 01076 / Compre (CPRI) compression type for the sector equipment.
m ression LSECT TDLOF ssion CPRI compression is used in RRU cascading
OREQ D-00107 Enhance scenarios to enable more RRUs to be cascaded
M 6 d CPRI without changing the data rate of CPRI ports. The
MOD TDLOF Compre parameter can be set to NO_COMPRESSION,
EUCEL D-08121 ssion NORMAL_COMPRESSION,
LSECT 4 ENHANCED_COMPRESSION,
OREQ TRIPLEX_COMPRESSION_10M, or NULL. The
M parameter value NO_COMPRESSION indicates that
CPRI compression is not used. The parameter value
LST NORMAL_COMPRESSION indicates that normal
EUCEL CPRI compression is used. The parameter value
LSECT ENHANCED_COMPRESSION indicates that
OREQ enhanced CPRI compression is used. The parameter
M value TRIPLEX_COMPRESSION_10M indicates
triple CPRI compression for a 10 MHz cell, which
applies only to LTE FDD. The parameter value NULL
indicates that this parameter is invalid. The
performance of enhanced CPRI compression is better
than the performance of normal CPRI compression. If
the eNodeB is equipped with LBBPd boards and the
CPRI data rate is 9.8 Gbit/s for LTE FDD cells or the
CPRI data rate is greater than 4.9 Gbit/s for LTE TDD
cells, the CPRI compression type of cells served by
RRUs in the same RRU chain or ring must be the
same. If this parameter value is changed, the cell
served by the sector equipment automatically resets.
This parameter is used only when MultiRruCellMode
is set to SFN or CELL_COMBINATION. This
parameter can be set based on the sector equipment
group. When this parameter is set to NULL, the CPRI
compression type of carriers depends on the value of
the CPRICompression parameter in the Cell MO.
When this parameter is set to any other value, the
CPRI compression type of carriers for the sector
equipment depends on the value of the
SectorCpriCompression parameter in the
eUCellSectorEqm MO. Before changing the value of
this parameter for cells served by RRUs in the same
RRU chain or ring, ensure that all cells served by the
RRU chain or ring are deactivated. Activate the cells
after you change the parameter value. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: NO_COMPRESSION(No
Compression), NORMAL_COMPRESSION(Normal
Compression),
ENHANCED_COMPRESSION(Enhanced
Compression),
TRIPLEX_COMPRESSION_10M(Triplex
Compression for 10M), NULL(Invalid)
Unit: None
Actual Value Range: NO_COMPRESSION,
NORMAL_COMPRESSION,
ENHANCED_COMPRESSION,
TRIPLEX_COMPRESSION_10M, NULL
Default Value: NULL(Invalid)
CellOp LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELLO identifies a cell within an eNodeB.
P GUI Value Range: 0~255
DSP Unit: None
CELLB
ROADC Actual Value Range: 0~255
ASTCN Default Value: None
OPERA
TOR
LST
CELLO
P
MOD
CELLO
P
RMV
CELLO
P
PDSCH LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
Cfg llId PDSCH identifies a cell within an eNodeB.
CFG GUI Value Range: 0~255
MOD Unit: None
PDSCH
CFG Actual Value Range: 0~255
Default Value: None
RACHC LocalCe DSP None None Meaning: Indicates the local ID of the cell. It uniquely
fg llId RACHC identifies a cell within a BS.
FG GUI Value Range: 0~255
LST Unit: None
RACHC
FG Actual Value Range: 0~255
CellRac LocalCe LST None None Meaning: Indicates the local ID of a cell, which
hCECfg llId CELLR uniquely identifies a cell within an eNodeB.
ACHCE GUI Value Range: 0~255
CFG
Unit: None
MOD
CELLR Actual Value Range: 0~255
ACHCE Default Value: None
CFG
CellRac Coverag LST MLOFD NB-IoT Meaning: Indicates the cell coverage level
hCECfg eLevel CELLR -120201 Coverag corresponding to RACH parameter configurations.
ACHCE e The value COVERAGE_LEVEL_0 indicates
CFG Extensio coverage level 0. The value COVERAGE_LEVEL_1
MOD n indicates coverage level 1. The value
CELLR COVERAGE_LEVEL_2 indicates coverage level 2.
ACHCE This parameter applies only to NB-IoT.
CFG GUI Value Range:
COVERAGE_LEVEL_0(COVERAGE_LEVEL_0),
COVERAGE_LEVEL_1(COVERAGE_LEVEL_1),
COVERAGE_LEVEL_2(COVERAGE_LEVEL_2)
Unit: None
Actual Value Range: COVERAGE_LEVEL_0,
COVERAGE_LEVEL_1, COVERAGE_LEVEL_2
Default Value: None
PCCHC LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
fg llId PCCHC identifies a cell within an eNodeB.
FG GUI Value Range: 0~255
MOD Unit: None
PCCHC
FG Actual Value Range: 0~255
Default Value: None
RrcCon RrcCon MOD LBFD-0 RRC Meaning: Indicates the duration that the eNodeB waits
nStateTi nRelTim RRCCO 02007 / Connect after sending an RRC Connection Release message to
mer er NNSTA TDLBF ion the UE.
TETIM D-00200 Manage GUI Value Range: 450~10000
ER 7 ment
Unit: ms
LST
RRCCO Actual Value Range: 450~10000
NNSTA Default Value: 450
TETIM
ER
CellPdc LocalCe LST None None Meaning: Indicates the local ID of a cell, which
chCECf llId CELLP uniquely identifies a cell within an eNodeB.
g DCCHC GUI Value Range: 0~255
ECFG
Unit: None
MOD
CELLP Actual Value Range: 0~255
DCCHC Default Value: None
ECFG
CellPdc Coverag LST MLOFD NB-IoT Meaning: Indicates the cell coverage level
chCECf eLevel CELLP -120201 Coverag corresponding to PDCCH parameter configurations.
g DCCHC e The value COVERAGE_LEVEL_0 indicates
ECFG Extensio coverage level 0. The value COVERAGE_LEVEL_1
MOD n indicates coverage level 1. The value
CELLP COVERAGE_LEVEL_2 indicates coverage level 2.
DCCHC This parameter applies only to NB-IoT.
ECFG GUI Value Range:
COVERAGE_LEVEL_0(COVERAGE_LEVEL_0),
COVERAGE_LEVEL_1(COVERAGE_LEVEL_1),
COVERAGE_LEVEL_2(COVERAGE_LEVEL_2)
Unit: None
Actual Value Range: COVERAGE_LEVEL_0,
COVERAGE_LEVEL_1, COVERAGE_LEVEL_2
Default Value: None
CellPdc PdcchTr MOD MLBFD Basic Meaning: Indicates the PDCCH initial transmission
chCECf ansRptC CELLP -120002 Scheduli repetition time factor. The number of PDCCH initial
g ntFactor DCCHC 34 ng transmission repetition times can be obtained by the
ECFG PDCCH initial transmission repetition time factor
LST multiplied by the maximum number of PDCCH
CELLP repetitions. This parameter applies only to NB-IoT.
DCCHC GUI Value Range: ONER_EIGHTR(ONE_EIGHTR),
ECFG QUARTERR(QUARTERR), HALFR(HALFR),
ONER(ONER)
Unit: None
Actual Value Range: ONER_EIGHTR, QUARTERR,
HALFR, ONER
Default Value: ONER_EIGHTR(ONE_EIGHTR)
NbCell LocalCe LST None None Meaning: Indicates the local ID of a cell, which
UlSchC llId NBCEL uniquely identifies a cell within an eNodeB.
EAlgo LULSC GUI Value Range: 0~255
HCEAL
GO Unit: None
NbCell Coverag LST MLBFD NB-IoT Meaning: Indicates the cell coverage level
UlSchC eLevel NBCEL -120002 Coverag corresponding to NPUSCH parameter configurations.
EAlgo LULSC 01 e The value COVERAGE_LEVEL_0 indicates
HCEAL Extensio coverage level 0. The value COVERAGE_LEVEL_1
GO n indicates coverage level 1. The value
MOD COVERAGE_LEVEL_2 indicates coverage level 2.
NBCEL This parameter applies only to NB-IoT.
LULSC GUI Value Range:
HCEAL COVERAGE_LEVEL_0(COVERAGE_LEVEL_0),
GO COVERAGE_LEVEL_1(COVERAGE_LEVEL_1),
COVERAGE_LEVEL_2(COVERAGE_LEVEL_2)
Unit: None
Actual Value Range: COVERAGE_LEVEL_0,
COVERAGE_LEVEL_1, COVERAGE_LEVEL_2
Default Value: None
NbCell LocalCe LST None None Meaning: Indicates the local ID of a cell, which
DlSchC llId NBCEL uniquely identifies a cell within an eNodeB.
EAlgo LDLSC GUI Value Range: 0~255
HCEAL
GO Unit: None
NbCell Coverag LST MLBFD NB-IoT Meaning: Indicates the cell coverage level
DlSchC eLevel NBCEL -120002 Coverag corresponding to NPDSCH parameter configurations.
EAlgo LDLSC 01 e The value COVERAGE_LEVEL_0 indicates
HCEAL Extensio coverage level 0. The value COVERAGE_LEVEL_1
GO n indicates coverage level 1. The value
MOD COVERAGE_LEVEL_2 indicates coverage level 2.
NBCEL This parameter applies only to NB-IoT.
LDLSC GUI Value Range:
HCEAL COVERAGE_LEVEL_0(COVERAGE_LEVEL_0),
GO COVERAGE_LEVEL_1(COVERAGE_LEVEL_1),
COVERAGE_LEVEL_2(COVERAGE_LEVEL_2)
Unit: None
Actual Value Range: COVERAGE_LEVEL_0,
COVERAGE_LEVEL_1, COVERAGE_LEVEL_2
Default Value: None
CellUlp LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
cComm llId CELLU identifies a cell within a BS.
LPCCO GUI Value Range: 0~255
MM
Unit: None
MOD
CELLU Actual Value Range: 0~255
LPCCO Default Value: None
MM
CellUlp LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
cDedic llId CELLU identifies a cell within a BS. This parameter applies
LPCDE only to LTE FDD and LTE TDD.
DIC GUI Value Range: 0~255
MOD Unit: None
CELLU
LPCDE Actual Value Range: 0~255
DIC Default Value: None
CellSiM LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
ap llId CELLSI identifies a cell within an eNodeB.
MAP GUI Value Range: 0~255
MOD Unit: None
CELLSI
MAP Actual Value Range: 0~255
Default Value: None
CellDrx LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
Para llId CELLD identifies a cell within a BS.
RXPAR GUI Value Range: 0~255
A
Unit: None
MOD
CELLD Actual Value Range: 0~255
RXPAR Default Value: None
A
CellDrx DrxAlg MOD LBFD-0 DRX Meaning: Indicates whether to enable DRX. This
Para Switch CELLD 02017 / Breathin parameter does not control dynamic DRX, and
RXPAR TDLBF g Pilot dynamic DRX applies only to LTE networks. DRX is
A D-00201 allowed to use for a CA UE only if this parameter is
LST 7/ set to ON on the eNodeBs serving the PCell and
CELLD MLBFD SCells of the CA UE. For LTE FDD and LTE TDD
RXPAR -120002 cells, the DrxAlgSwitch parameter in the CellDrxPara
A 36 MO takes effect only if the DrxAlgSwitch parameter
LEOFD- in the Drx MO is set to OFF. For NB-IoT cells, DRX
111306 / is allowed to use only when the DrxAlgSwitch
TDLOF parameter in the CellDrxPara MO is set to ON.
D-12020 GUI Value Range: OFF(Off), ON(On)
5 Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellSel LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELLS identifies a cell within an eNodeB.
EL GUI Value Range: 0~255
MOD Unit: None
CELLS
EL Actual Value Range: 0~255
Default Value: None
CellRes LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
el llId CELLR identifies a cell within a BS.
ESEL GUI Value Range: 0~255
MOD Unit: None
CELLR
ESEL Actual Value Range: 0~255
Default Value: None
CellRes SIntraSe MOD LBFD-0 Cell Meaning: Indicates whether to set the measurement
el archCfgI CELLR 0201803 Selectio triggering threshold for reselection to intra-frequency
nd ESEL / n and cells.
LST TDLBF Re- GUI Value Range: NOT_CFG(Not configure),
CELLR D-00201 selection CFG(Configure)
ESEL 803 / Broadca
MLBFD Unit: None
st of
-120002 system Actual Value Range: NOT_CFG, CFG
37 informat Default Value: CFG(Configure)
LBFD-0 ion
02009 /
TDLBF
D-00200
9/
MLBFD
-120002
29
CellRes SNonInt MOD LBFD-0 Cell Meaning: Indicates whether to configure the
el raSearch CELLR 0201803 Selectio measurement triggering threshold for cell reselection
CfgInd ESEL / n and to inter-frequency or inter-RAT cells. If this parameter
LST TDLBF Re- is set to NOT_CFG and the QQualMinCfgInd
CELLR D-00201 selection parameter is set to NOT_CFG, the UE continuously
ESEL 803 / Broadca measures intra-frequency and inter-RAT cells,
MLBFD st of regardless of the signal quality of the serving cell.
-120002 system GUI Value Range: NOT_CFG(Not configure),
37 informat CFG(Configure)
LBFD-0 ion Unit: None
02009 / PS Inter-
TDLBF Actual Value Range: NOT_CFG, CFG
RAT
D-00200 Mobility Default Value: CFG(Configure)
9/ between
MLBFD E-
-120002 UTRAN
29 and
LOFD-0 CDMA2
01021 / 000
TDLOF PS
D-00102 Mobility
1 from E-
LOFD-0 UTRAN
01111 to
CDMA2
000
HRPD
Based
on
Frequen
cy-
specific
Factors
Hybrid
RAN
Sharing
Hybrid
RAN
Sharing
EutranE eNodeB ADD None None Meaning: Indicates the eNodeB ID of the external E-
xternalC Id EUTRA UTRAN cell. It uniquely identifies an eNodeB within
ell NEXTE a PLMN. The 28-bit E-UTRAN cell ID is comprised
RNALC of the cell ID and the eNodeB ID (represented by the
ELL most significant 20 bits). The cell global identity
ADD (CGI) of an E-UTRAN cell is comprised of the E-
EUTRA UTRAN cell ID and the PLMN ID. For details, see
NEXTE 3GPP TS 36.413.
RNALC GUI Value Range: 0~1048575
ELLBA Unit: None
ND
Actual Value Range: 0~1048575
LST
EUTRA Default Value: None
NEXTE
RNALC
ELL
LST
EUTRA
NEXTE
RNALC
ELLBA
ND
MOD
EUTRA
NEXTE
RNALC
ELL
RMV
EUTRA
NEXTE
RNALC
ELL
RMV
EUTRA
NEXTE
RNALC
ELLBA
ND
EutranE CellId ADD LBFD-0 Coverag Meaning: Indicates the cell ID of the external E-
xternalC EUTRA 0201801 e Based UTRAN cell. It uniquely identifies a cell within an
ell NEXTE / Intra- eNodeB. The 28-bit E-UTRAN cell ID is comprised
RNALC TDLBF frequenc of the cell ID (represented by the least significant
ELL D-00201 y eight bits) and the eNodeB ID. An E-UTRAN cell ID
ADD 801 Handov and a PLMN ID compose an E-UTRAN CGI (ECGI).
EUTRA LBFD-0 er For details, see 3GPP TS 36.413.
NEXTE 0201802 Coverag GUI Value Range: 0~255
RNALC / e Based Unit: None
ELLBA TDLBF Inter-
ND D-00201 frequenc Actual Value Range: 0~255
EutranE DlEarfc ADD LOFD-0 RAN Meaning: Indicates the DL EARFCN of the external
xternalC n EUTRA 01036 / Sharing E-UTRAN cell. For details, see 3GPP TS 36.104.
ell NEXTE TDLOF with GUI Value Range: 0~68485
RNALC D-00103 Commo
ELL 6 n Unit: None
Hybrid
RAN
Sharing
EutranE PhyCellI ADD LBFD-0 Coverag Meaning: Indicates the physical cell identifier (PCI) of
xternalC d EUTRA 0201801 e Based the external E-UTRAN cell. For details, see 3GPP TS
ell NEXTE / Intra- 36.331.
RNALC TDLBF frequenc GUI Value Range: 0~503
ELL D-00201 y
801 Handov Unit: None
MOD
EUTRA LBFD-0 er Actual Value Range: 0~503
NEXTE 0201802 Coverag Default Value: None
RNALC / e Based
ELL TDLBF Inter-
LST D-00201 frequenc
EUTRA 802 y
NEXTE LBFD-0 Handov
RNALC 0201803 er
ELL / Cell
TDLBF Selectio
D-00201 n and
803 Reselect
TDLBF ion /
D-00201 Cell
801 Selectio
n and
Re-
selection
Coverag
e Based
Intra-
frequenc
y
Handov
er
EutranE Tac ADD LBFD-0 Coverag Meaning: Indicates the tracking area code (TAC) of
xternalC EUTRA 0201801 e Based the external E-UTRAN cell. Two TAC values
ell NEXTE / Intra- 0x0000(0) and 0xFFFE(65534) are reserved according
RNALC TDLBF frequenc to the protocol and will not be used in future versions.
ELL D-00201 y Therefore, do not use 0 or 65534 as a TAC value in
MOD 801 Handov TAC planning or configuration.
EUTRA LBFD-0 er GUI Value Range: 0~65535
NEXTE 0201802 Coverag Unit: None
RNALC / e Based
ELL TDLBF Inter- Actual Value Range: 0~65535
EutranE CellNa ADD LBFD-0 Coverag Meaning: Indicates the name of the external E-
xternalC me EUTRA 0201801 e Based UTRAN cell.
ell NEXTE / Intra- GUI Value Range: 0~99 characters
RNALC TDLBF frequenc
ELL D-00201 y Unit: None
EutranE UlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
xternalC ffset EUTRA -120001 ne uplink central frequency to the uplink frequency. This
ell NEXTE 01 Deploy parameter takes effect only when UlEarfcnCfgInd is
RNALC MLBFD ment set to CFG(Configure). Otherwise, the offset is
ELL -120001 LTE calculated based on the uplink/downlink symmetric
MOD 02 Guardba system. For details, see 3GPP TS 36.101. This
EUTRA nd parameter applies only to NB-IoT.
MLBFD
NEXTE -120001 Deploy GUI Value Range: NEG_10(NEG_10),
RNALC 03 ment NEG_9(NEG_9), NEG_8(NEG_8), NEG_7(NEG_7),
ELL LTE In- NEG_6(NEG_6), NEG_5(NEG_5), NEG_4(NEG_4),
LST band NEG_3(NEG_3), NEG_2(NEG_2), NEG_1(NEG_1),
EUTRA Deploy POS_0(POS_0), POS_1(POS_1), POS_2(POS_2),
NEXTE ment POS_3(POS_3), POS_4(POS_4), POS_5(POS_5),
RNALC POS_6(POS_6), POS_7(POS_7), POS_8(POS_8),
ELL POS_9(POS_9)
Unit: None
Actual Value Range: NEG_10, NEG_9, NEG_8,
NEG_7, NEG_6, NEG_5, NEG_4, NEG_3, NEG_2,
NEG_1, POS_0, POS_1, POS_2, POS_3, POS_4,
POS_5, POS_6, POS_7, POS_8, POS_9
Default Value: POS_0(POS_0)
EutranE DlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
xternalC ffset EUTRA -120001 ne downlink central frequency to the downlink
ell NEXTE 01 Deploy frequency. For details, see 3GPP TS 36.101. This
RNALC MLBFD ment parameter applies only to NB-IoT.
ELL -120001 LTE GUI Value Range: NEG_2(NEG_2),
MOD 02 Guardba NEG_1(NEG_1), NEG_0DOT5(NEG_0DOT5),
EUTRA MLBFD nd POS_0(POS_0), POS_1(POS_1)
NEXTE -120001 Deploy Unit: None
RNALC 03 ment
ELL Actual Value Range: NEG_2, NEG_1, NEG_0DOT5,
LTE In- POS_0, POS_1
LST band
EUTRA Deploy Default Value: NEG_0DOT5(NEG_0DOT5)
NEXTE ment
RNALC
ELL
EutranE NbCellF ADD MLBFD Cell Meaning: Indicates whether a local cell is an NB-IoT
xternalC lag EUTRA -120002 Selectio cell. When this parameter is set to TRUE, the local
ell NEXTE 37 n and cell is an NB-IoT cell. When this parameter is set to
RNALC Re- FALSE, the local cell is not an NB-IoT cell. This
ELL selection parameter applies only to NB-IoT.
MOD GUI Value Range: FALSE(FALSE), TRUE(TRUE)
EUTRA Unit: None
NEXTE
RNALC Actual Value Range: FALSE, TRUE
ELL Default Value: FALSE(FALSE)
LST
EUTRA
NEXTE
RNALC
ELL
EutranIn eNodeB ADD None None Meaning: Indicates the eNodeB ID of the intra-
traFreq Id EUTRA frequency neighboring cell. It uniquely identifies an
NCell NINTR eNodeB within a PLMN. The 28-bit E-UTRAN cell
AFREQ ID is comprised of the cell ID and the eNodeB ID
NCELL (represented by the most significant 20 bits). The cell
DSP global identity (CGI) of an E-UTRAN cell is
EUTRA comprised of the E-UTRAN cell ID and the PLMN
NEXTE ID. For details, see 3GPP TS 36.413.
NDEDN GUI Value Range: 0~1048575
CELL Unit: None
DSP Actual Value Range: 0~1048575
EUTRA
NINTR Default Value: None
AFREQ
NCELL
LST
EUTRA
NINTR
AFREQ
NCELL
MOD
EUTRA
NINTR
AFREQ
NCELL
RMV
EUTRA
NEXTE
NDEDN
CELL
RMV
EUTRA
NINTR
AFREQ
NCELL
EutranIn CellId ADD LBFD-0 Coverag Meaning: Indicates the ID of the intra-frequency
traFreq EUTRA 0201801 e Based neighboring cell. It uniquely identifies a cell within an
NCell NINTR / Intra- eNodeB. The 28-bit E-UTRAN cell ID is comprised
AFREQ TDLBF frequenc of the cell ID (represented by the least significant
NCELL D-00201 y eight bits) and the eNodeB ID. The cell global identity
DSP 801 Handov (CGI) of an E-UTRAN cell is comprised of the E-
EUTRA er UTRAN cell ID and the PLMN ID. For details, see
NEXTE 3GPP TS 36.413.
NDEDN GUI Value Range: 0~255
CELL Unit: None
DSP Actual Value Range: 0~255
EUTRA
NINTR Default Value: None
AFREQ
NCELL
LST
EUTRA
NINTR
AFREQ
NCELL
MOD
EUTRA
NINTR
AFREQ
NCELL
RMV
EUTRA
NEXTE
NDEDN
CELL
RMV
EUTRA
NINTR
AFREQ
NCELL
EutranIn LocalCe ADD LBFD-0 Coverag Meaning: Indicates the name of the local cell.
traFreq llName EUTRA 0201801 e Based GUI Value Range: 0~99 characters
NCell NINTR / Intra-
AFREQ TDLBF frequenc Unit: None
NCELL D-00201 y Actual Value Range: 0~99 characters
MOD 801 Handov Default Value: NULL(empty string)
EUTRA LOFD-0 er
NINTR 02001 / Automat
AFREQ TDLOF ic
NCELL D-00200 Neighbo
LST 1 ur
EUTRA Relation
NINTR (ANR)
AFREQ
NCELL
EutranIn Neighbo ADD LBFD-0 Coverag Meaning: Indicates the name of the intra-frequency
traFreq urCellN EUTRA 0201801 e Based neighboring E-UTRAN cell.
NCell ame NINTR / Intra- GUI Value Range: 0~99 characters
AFREQ TDLBF frequenc
NCELL D-00201 y Unit: None
EutranIn PhyCellI DSP LBFD-0 Coverag Meaning: Indicates the physical cell identifier (PCI) of
traFreq d EUTRA 0201801 e Based the neighboring E-UTRAN cell. For details about this
NCell NEXTE / Intra- parameter, see 3GPP TS 36.331.
NDEDN TDLBF frequenc GUI Value Range: 0~503
CELL D-00201 y
801 Handov Unit: None
DSP
EUTRA LBFD-0 er Actual Value Range: 0~503
NINTR 0201802 Coverag Default Value: None
AFREQ / e Based
NCELL TDLBF Inter-
D-00201 frequenc
802 y
LBFD-0 Handov
0201803 er
/ Cell
TDLBF Selectio
D-00201 n and
803 / Reselect
MLBFD ion
-120002
37
EutranIn eNodeB ADD None None Meaning: Indicates the eNodeB ID of the inter-
terFreq Id EUTRA frequency neighboring cell. It uniquely identifies an
NCell NINTE eNodeB within a PLMN. The 28-bit E-UTRAN cell
RFREQ ID is comprised of the cell ID and the eNodeB ID
NCELL (represented by the most significant 20 bits). The cell
DSP global identity (CGI) of an E-UTRAN cell is
EUTRA comprised of the E-UTRAN cell ID and the PLMN
NINTE ID. For details, see 3GPP TS 36.413.
RFREQ GUI Value Range: 0~1048575
NCELL Unit: None
LST Actual Value Range: 0~1048575
EUTRA
NINTE Default Value: None
RFREQ
NCELL
MOD
EUTRA
NINTE
RFREQ
NCELL
RMV
EUTRA
NINTE
RFREQ
NCELL
EutranIn CellId ADD LBFD-0 Coverag Meaning: Indicates the ID of the inter-frequency
terFreq EUTRA 0201802 e Based neighboring cell. It uniquely identifies a cell within an
NCell NINTE Inter- eNodeB. The 28-bit E-UTRAN cell ID is comprised
RFREQ frequenc of the cell ID (represented by the least significant
NCELL y eight bits) and the eNodeB ID. The cell global identity
DSP Handov (CGI) of an E-UTRAN cell is comprised of the E-
EUTRA er UTRAN cell ID and the PLMN ID. For details, see
NINTE 3GPP TS 36.413.
RFREQ GUI Value Range: 0~255
NCELL Unit: None
LST Actual Value Range: 0~255
EUTRA
NINTE Default Value: None
RFREQ
NCELL
MOD
EUTRA
NINTE
RFREQ
NCELL
RMV
EUTRA
NINTE
RFREQ
NCELL
EutranIn LocalCe ADD LBFD-0 Coverag Meaning: Indicates the name of the local cell.
terFreq llName EUTRA 0201802 e Based GUI Value Range: 0~99 characters
NCell NINTE / Inter-
RFREQ TDLBF frequenc Unit: None
NCELL D-00201 y Actual Value Range: 0~99 characters
MOD 802 Handov Default Value: NULL(empty string)
EUTRA LOFD-0 er
NINTE 02001 / Automat
RFREQ TDLOF ic
NCELL D-00200 Neighbo
LST 1 r
EUTRA Relation
NINTE (ANR)
RFREQ
NCELL
EutranIn Neighbo ADD LBFD-0 Coverag Meaning: Indicates the name of the inter-frequency
terFreq urCellN EUTRA 0201802 e Based neighboring cell.
NCell ame NINTE / Inter- GUI Value Range: 0~99 characters
RFREQ TDLBF frequenc
NCELL D-00201 y Unit: None
EutranIn PmaxCf ADD LBFD-0 Cell Meaning: Indicates whether to set the maximum
terNFre gInd EUTRA 0201803 Selectio power that the UE can apply to transmission on the
q NINTE / n and neighboring E-UTRAN frequency. If the value of this
RNFRE TDLBF Reselect parameter is not specified, the maximum power is
Q D-00201 ion subject to the UE capability.
MOD 803 / GUI Value Range: NOT_CFG(Not configure),
EUTRA MLBFD CFG(Configure)
NINTE -120002
37 Unit: None
RNFRE
Q Actual Value Range: NOT_CFG, CFG
EutranIn DlEarfc ADD LBFD-0 Coverag Meaning: Indicates the DL EARFCN of the
terNFre n EUTRA 0201802 e Based neighboring cell on the neighboring E-UTRAN
q NINTE / Inter- frequency. For details, see the 3GPP TS 36.104.
RNFRE TDLBF frequenc GUI Value Range: 0~68485
Q D-00201 y
802 Handov Unit: None
LST
EUTRA LBFD-0 er Actual Value Range: 0~68485
NINTE 0201803 Cell Default Value: None
RNFRE / Selectio
Q TDLBF n and
MOD D-00201 Re-
EUTRA 803 selection
NINTE LBFD-0 Distance
RNFRE 0201804 Based
Q / Inter-
RMV TDLBF frequenc
CELLE D-00201 y
UTRAN 804 Handov
INTER LBFD-0 er
NFREQ 0201805 Service
RMV / Based
EUTRA TDLBF Inter-
NINTE D-00201 frequenc
RNFRE 805 y
Q TDLOF Handov
D-00105 er
0 Mobility
MLBFD between
-120002 LTE
37 TDD
and LTE
FDD
Cell
Selectio
n and
Reselect
ion
EutranIn UlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
terNFre ffset EUTRA -120001 ne uplink central frequency to the uplink frequency. This
q NINTE 01 Deploy parameter takes effect only when UlEarfcnCfgInd is
RNFRE MLBFD ment set to CFG(Configure). Otherwise, the offset is
Q -120001 LTE calculated based on the uplink/downlink symmetric
MOD 02 Guardba system. For details, see 3GPP TS 36.101. This
EUTRA nd parameter applies only to NB-IoT.
MLBFD
NINTE -120001 Deploy GUI Value Range: NEG_10(NEG_10),
RNFRE 03 ment NEG_9(NEG_9), NEG_8(NEG_8), NEG_7(NEG_7),
Q LTE In- NEG_6(NEG_6), NEG_5(NEG_5), NEG_4(NEG_4),
LST band NEG_3(NEG_3), NEG_2(NEG_2), NEG_1(NEG_1),
EUTRA Deploy POS_0(POS_0), POS_1(POS_1), POS_2(POS_2),
NINTE ment POS_3(POS_3), POS_4(POS_4), POS_5(POS_5),
RNFRE POS_6(POS_6), POS_7(POS_7), POS_8(POS_8),
Q POS_9(POS_9)
Unit: None
Actual Value Range: NEG_10, NEG_9, NEG_8,
NEG_7, NEG_6, NEG_5, NEG_4, NEG_3, NEG_2,
NEG_1, POS_0, POS_1, POS_2, POS_3, POS_4,
POS_5, POS_6, POS_7, POS_8, POS_9
Default Value: POS_0(POS_0)
EutranIn DlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
terNFre ffset EUTRA -120001 ne downlink central frequency to the downlink
q NINTE 01 Deploy frequency. For details, see 3GPP TS 36.101. This
RNFRE MLBFD ment parameter applies only to NB-IoT.
Q -120001 LTE GUI Value Range: NEG_2(NEG_2),
MOD 02 Guardba NEG_1(NEG_1), NEG_0DOT5(NEG_0DOT5),
EUTRA MLBFD nd POS_0(POS_0), POS_1(POS_1)
NINTE -120001 Deploy Unit: None
RNFRE 03 ment
Q Actual Value Range: NEG_2, NEG_1, NEG_0DOT5,
LTE In- POS_0, POS_1
LST band
EUTRA Deploy Default Value: NEG_0DOT5(NEG_0DOT5)
NINTE ment
RNFRE
Q
CellAlg LteUtcB MOD LOFD-0 eMBMS Meaning: Indicates whether the eNodeB broadcasts
oSwitch roadcast CELLA 80215 / Service the coordinated universal time (UTC) in the LTE
Switch LGOSW TDLOF Continui system over the air interface. If this parameter is set to
ITCH D-08021 ty 1, the eNodeB broadcasts the UTC in the LTE system
LST 0 eMBMS using system information block type 16 (SIB16). If
CELLA LOFD-0 Phase 1 this parameter is set to 0, the eNodeB does not
LGOSW 70220 / based on broadcast the UTC in the LTE system.
ITCH TDLOF Centrali GUI Value Range: OFF(Off), ON(On)
D-07022 zed Unit: None
0 MCE
Architec Actual Value Range: OFF, ON
ture Default Value: OFF(Off)
CellChP LocalCe LST None None Meaning: Indicates the local ID of a cell, which
wrCfg llId CELLC uniquely identifies a cell within an eNodeB. This
HPWRC parameter applies only to LTE FDD and LTE TDD.
FG GUI Value Range: 0~255
MOD Unit: None
CELLC
HPWRC Actual Value Range: 0~255
FG Default Value: None
eNBCell LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
RsvdPar llId ENBCE identifies a cell within a BS. This parameter applies
a LLRSV only to LTE FDD and LTE TDD.
DPARA GUI Value Range: 0~255
MOD Unit: None
ENBCE
LLRSV Actual Value Range: 0~255
DPARA Default Value: None
CellRbR LocalCe ADD None None Meaning: Indicates the local ID of a cell, which
eserve llId CELLR uniquely identifies a cell within an eNodeB. This
BRESE parameter applies only to LTE FDD and NB-IoT.
RVE GUI Value Range: 0~255
LST Unit: None
CELLR
BRESE Actual Value Range: 0~255
RVE Default Value: None
MOD
CELLR
BRESE
RVE
RMV
CELLR
BRESE
RVE
CellRbR RbRsvSt ADD MLBFD LTE In- Meaning: Indicates the start of the physical-layer
eserve artIndex CELLR -120001 band reserved PRB range. The PRBs are numbered starting
BRESE 03 Deploy from 0 from low to high frequencies. For details, see
RVE ment 3GPP TS 36.211. This parameter applies only to LTE
MOD FDD and NB-IoT.
CELLR GUI Value Range: 0~99
BRESE Unit: None
RVE
Actual Value Range: 0~99
LST
CELLR Default Value: None
BRESE
RVE
CellRbR RbRsvE ADD MLBFD LTE In- Meaning: Indicates the end of the physical-layer
eserve ndIndex CELLR -120001 band reserved PRB range. This parameter applies only to
BRESE 03 Deploy LTE FDD and NB-IoT.
RVE ment GUI Value Range: 0~99
MOD Unit: None
CELLR
BRESE Actual Value Range: 0~99
RVE Default Value: None
LST
CELLR
BRESE
RVE
GlobalP QciPara MOD LBFD-0 Radio Meaning: Indicates whether parameters in QciPara,
rocSwitc EffectFl GLOBA 02008 Bearer CellQciPara, and CnOperatorQciPara MOs take
h ag LPROC TDLBF Manage effect. The parameters take effect by default. If this
SWITC D-00201 ment parameter is set to OFF, parameters in StandardQci,
H 7 DRX ExtendedQci, CellStandardQci, CellExtendedQci,
LST CnOperatorStandardQci, and CnOperatorExtendedQci
LBFD-0 Mobility MOs take effect and parameters in QciPara,
GLOBA 02018 / Manage
LPROC CellQciPara, and CnOperatorQciPara MOs do not
TDLBF ment take effect. If this parameter is set to ON, parameters
SWITC D-00201
H Coverag in QciPara, CellQciPara, and CnOperatorQciPara
8 e Based MOs take effect and parameters in StandardQci,
TDLBF Intra- ExtendedQci, CellStandardQci, CellExtendedQci,
D-00201 frequenc CnOperatorStandardQci, and CnOperatorExtendedQci
801 y MOs do not take effect. This parameter applies only to
LBFD-0 Handov LTE FDD and LTE TDD.
0201802 er GUI Value Range: OFF(Off), ON(On)
/ Coverag Unit: None
TDLBF e Based
D-00201 Inter- Actual Value Range: OFF, ON
802 frequenc Default Value: ON(On)
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
0301101 y
/ Handov
TDLOF er
D-00301 Transpo
101 rt
LOFD-0 Overboo
0301102 king
/ Transpo
TDLOF rt
D-00301 Differen
102 tiated
LOFD-0 Flow
0301103 Control
/ Transpo
TDLOF rt
D-00301 Resourc
103 e
Overloa
d
Control
TASM FNSYN SET None None Meaning: Indicates whether to enable the CIoT frame
CSW FNSYN No. synchronization function. The value ON indicates
CTIME that this function is enabled. The value OFF indicates
DSP that this function is disabled. This parameter takes
FNSYN effect only when frequency synchronization is used.
CTIME GUI Value Range: OFF(Off), ON(On)
LST Unit: None
FNSYN Actual Value Range: OFF, ON
CTIME
Default Value: OFF(Off)
TASM DATE SET None None Meaning: Indicates the date to be set for the CIoT
FNSYN Frame No. This parameter is set in compliance with
CTIME the GPS. The format is as follows: YYYY-MM-DD.
DSP For example, 2006-09-08 indicates September 8th of
FNSYN 2006.
CTIME GUI Value Range: 1900-01-01~2099-12-31
LST Unit: None
FNSYN Actual Value Range: 1900-01-01~2099-12-31
CTIME
Default Value: 1980-01-06
TASM TIME SET None None Meaning: Indicates the time to be set for the CIoT
FNSYN Frame No. This parameter is set in compliance with
CTIME the GPS. The format is as follows: HH:MM:SS. For
DSP example, 10:20:05.
FNSYN GUI Value Range: 00:00:00~23:59:59
CTIME
Unit: None
LST
Actual Value Range: 00:00:00~23:59:59
FNSYN
CTIME Default Value: 00:00:00
TASM LEAPS SET None None Meaning: Indicates the date when the leap seconds
ECOND LEAPS changed. This parameter is set in compliance with the
SCHGD ECOND UTC. The format is as follows: YYYY-MM-DD. For
ATE SINFO example, 2006-09-08 indicates September 8th of
LST 2006.
LEAPS GUI Value Range: 1900-01-01~2099-12-31
ECOND Unit: None
SINFO
Actual Value Range: 1900-01-01~2099-12-31
Default Value: 2017-01-01
TASM LEAPS SET None None Meaning: Indicates the time when the leap seconds
ECOND LEAPS changed. This parameter is set in compliance with the
SCHGT ECOND UTC. The format is as follows: HH:MM:SS. For
IME SINFO example, 10:20:05.
LST GUI Value Range: 00:00:00~23:59:59
LEAPS Unit: None
ECOND
SINFO Actual Value Range: 00:00:00~23:59:59
Default Value: 07:59:59
TASM CRTGP SET None None Meaning: Indicates the current leap second offset
STOUT LEAPS between the UTC and the GPS.
CLEAP ECOND GUI Value Range: -1000~1000
SECON SINFO
DS Unit: None
LST
LEAPS Actual Value Range: -1000~1000
ECOND Default Value: 17
SINFO
TASM NEXTG SET None None Meaning: Indicates the next leap second offset
PSTOU LEAPS between the UTC and the GPS.
TCLEA ECOND GUI Value Range: -1000~1000
PSECO SINFO
NDS Unit: None
LST
LEAPS Actual Value Range: -1000~1000
ECOND Default Value: 18
SINFO
CellDmr LocalCe ADD None None Meaning: Indicates the local ID of a cell, which
sCfg llId CELLD uniquely identifies a cell within an eNodeB. This
MRSCF parameter applies to LTE FDD, LTE TDD, and NB-
G IoT.
LST GUI Value Range: 0~255
CELLD Unit: None
MRSCF
G Actual Value Range: 0~255
CellDmr ThreeTo ADD MLOFD Multi- Meaning: Indicates the DMRS three tone base
sCfg neBaseS CELLD -120230 tone sequence of a cell, which is used to generate the
eq MRSCF DMRS sequence for the NPUSCH when three tone
G transmission is used. This parameter applies only to
MOD NB-IoT.
CELLD GUI Value Range: 0~11
MRSCF Unit: None
G
Actual Value Range: 0~11
LST
CELLD Default Value: None
MRSCF
G
CellDmr SixTone ADD MLOFD Multi- Meaning: Indicates the DMRS six tone base sequence
sCfg BaseSeq CELLD -120230 tone of a cell, which is used to generate the DMRS
MRSCF sequence for the NPUSCH when six tone transmission
G is used. This parameter applies only to NB-IoT.
MOD GUI Value Range: 0~13
CELLD Unit: None
MRSCF
G Actual Value Range: 0~13
CellDmr TwelveT ADD MLOFD Multi- Meaning: Indicates the DMRS twelve tone base
sCfg oneBase CELLD -120230 tone sequence of a cell, which is used to generate the
Seq MRSCF DMRS sequence for the NPUSCH when twelve tone
G transmission is used. This parameter applies only to
MOD NB-IoT.
CELLD GUI Value Range: 0~29
MRSCF Unit: None
G
Actual Value Range: 0~29
LST
CELLD Default Value: None
MRSCF
G
13 Counters
1526746040 L.NB.Thrp.Time.Ce Total duration with Multi-mode: None Data over User
ll.DL data transmission in GSM: None Plane
the downlink in an
NB-IoT cell UMTS: None
LTE:
MLBFD-12100205
1526746041 L.NB.Thrp.Time.Ce Total duration with Multi-mode: None Data over User
ll.UL data transmission in GSM: None Plane
the uplink in an
NB-IoT cell UMTS: None
LTE:
MLBFD-12100205
14 Glossary
15 Reference Documents