Compact Bandwidth (FDD) (eRAN13.1 - 05)
Compact Bandwidth (FDD) (eRAN13.1 - 05)
Compact Bandwidth (FDD) (eRAN13.1 - 05)
Issue 05
Date 2019-01-21
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
1 Change History.............................................................................................................................. 1
1.1 eRAN13.1 05 (2019-01-21)............................................................................................................................................1
1.2 eRAN13.1 04 (2018-10-30)............................................................................................................................................2
1.3 eRAN13.1 03 (2018-08-27)............................................................................................................................................2
1.4 eRAN13.1 02 (2018-06-30)............................................................................................................................................3
1.5 eRAN13.1 01 (2018-04-10)............................................................................................................................................3
1.6 eRAN13.1 Draft B (2018-03-30)....................................................................................................................................4
1.7 eRAN13.1 Draft A (2018-01-15)................................................................................................................................... 4
3 General Principles......................................................................................................................... 9
3.1 Multi-RAT Scenarios.................................................................................................................................................... 11
3.2 LTE Only Scenario....................................................................................................................................................... 12
4 Compact Bandwidth................................................................................................................... 14
4.1 Principles...................................................................................................................................................................... 14
4.1.1 Reducing Guard Bandwidths.....................................................................................................................................14
4.1.2 Reducing Effective Bandwidths................................................................................................................................ 15
4.1.2.1 Physical Channel Resource Management...............................................................................................................16
4.1.2.2 CQI Adjustment......................................................................................................................................................19
4.1.3 Key Compact Bandwidth Technologies.................................................................................................................... 20
4.2 Network Analysis......................................................................................................................................................... 35
4.2.1 Benefits...................................................................................................................................................................... 35
4.2.2 Impacts.......................................................................................................................................................................35
4.3 Requirements................................................................................................................................................................ 38
4.3.1 Licenses..................................................................................................................................................................... 38
4.3.2 Software.....................................................................................................................................................................38
4.3.3 Hardware................................................................................................................................................................... 39
4.3.4 Networking................................................................................................................................................................ 40
4.3.4.1 Networking in Multi-RAT Scenarios......................................................................................................................40
4.3.4.2 Networking in LTE Only Scenarios........................................................................................................................41
4.4 Operation and Maintenance..........................................................................................................................................42
5 Parameters..................................................................................................................................... 57
6 Counters...................................................................................................................................... 114
7 Glossary....................................................................................................................................... 117
8 Reference Documents............................................................................................................... 118
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Added descriptions of impact of compact bandwidth on precise AMC. For details, see 4.2.2
Impacts.
Added descriptions of mutual exclusiveness with eMTC frequency hopping. For details, see
4.3.2 Software.
Optimized the network monitoring method. For details, see 4.4.3 Network Monitoring.
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station Model
Editorial Changes
Adjusted the display mode of punctured RBs in Table 4-3.
Added deactivation command examples. For details, see 4.4.1.2 Using MML Commands.
Technical Changes
Change Description Parameter Change Base Station
Model
Added support for LTE only Added parameters: l 3900 and 5900
scenarios. For details, see Cell.CompactBwCtrlIntrfMode series base
the following sections: stations
Cell.UlPuncturedRbNumOffset
l 3.2 LTE Only Scenario l DBS3900
l PUCCH Resource LampSite and
Allocation and Power DBS5900
Control LampSite
l PUSCH Resource
Allocation and Power
Control
Added support for the 1800 None 3900 and 5900 series
MHz AAU5972 which base stations
supports 11 non-
standardized bandwidths.
For details, see Table 4-3.
Added a parameter to Added the following parameter and l 3900 and 5900
support power compensation options: series base
and adaptive PUCCH and CellAlgoSwitch.NonStandardBwA stations
SRS resource allocation in lgoSw: l DBS3900
cells with non-standardized LampSite and
bandwidths. For details, see l PCFICH_POWER_OPT_SWI
TCH DBS5900
4.4.1.1 Data Preparation. LampSite
l PDCCH_POWER_OPT_SWI
TCH
l PUCCH_SRS_ADAPT_SWIT
CH
Editorial Changes
Reorganized this document using a new template.
3 General Principles
Compact bandwidth compresses LTE guard bands or LTE available resource blocks (RBs) in
cells with standardized LTE bandwidths of 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20
MHz by using radio frequency (RF) modules to obtain LTE non-standardized bandwidths. In
this document, standardized bandwidths before the compression refer to LTE original
bandwidths. For example, the original bandwidth of the non-standardized bandwidth 18.6
MHz is 20 MHz.
3GPP defines 450 MHz, 850 MHz, 900 MHz, and 1800 MHz as LTE operating frequency
bands. These frequency bands are currently used by CDMA, UMTS, and GSM networks. To
deploy an LTE network on these frequency bands, refarming is performed on some or all of
spectrum resources used by CDMA, UMTS, or GSM networks. During the refarming,
CDMA, UMTS, and GSM networks release spectrum resources as follows:
As a result, the released resources may not be standardized LTE operating bandwidths. The
Compact Bandwidth feature is designed for the preceding scenario. This feature applies to the
following scenarios:
l Multi-RAT scenarios
l LTE only scenarios
Table 3-1 lists all the non-standardized bandwidths supported by this feature.
Table 3-1 Non-standardized bandwidths, application scenarios, and base stations supported by
this feature.
1.2 MHz to 1.3 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
4.4 MHz to 4.7 MHz Multi-RAT and LTE only 3900 and 5900 series base
scenarios stations
4.8 MHz to 4.9 MHz Multi-RAT scenarios l 3900 and 5900 series
base stations
l DBS3900 LampSite and
DBS5900 LampSite
7.4 MHz to 7.5 MHz Multi-RAT and LTE only l 3900 and 5900 series
scenarios base stations
l DBS3900 LampSite and
DBS5900 LampSite
8.7 MHz Multi-RAT and LTE only 3900 and 5900 series base
scenarios stations
8.9 MHz to 9.1 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
9.2 MHz to 9.5 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
9.6 MHz to 9.9 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
13.9 MHz to 14.2 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
14.3 MHz to 14.5 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
14.6 MHz to 14.9 MHz Multi-RAT and LTE only l 3900 and 5900 series
scenarios base stations
l DBS3900 LampSite and
DBS5900 LampSite
17.5 MHz to 17.8 MHz Multi-RAT and LTE only 3900 and 5900 series base
scenarios stations
18.3 MHz to 18.5 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
18.6 MHz to 18.9 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
19 MHz to 19.2 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
19.3 MHz to 19.9 MHz Multi-RAT scenarios 3900 and 5900 series base
stations
For this type of operators, the LTE cell bandwidth must fall into the range of operators'
available spectrum.
NOTE
LTE cell bandwidth, the LTE original bandwidth Y in Figure 3-1 is specified by the Cell.UlBandWidth
and Cell.DlBandWidth parameters.
For example, if a multi-RAT operator has a total bandwidth of 20 MHz or more and plans to
deploy LTE networks with a bandwidth of 18.6 MHz, the rest of 1.4 MHz or more can be
allocated to other RATs.
For example, if the 1800 MHz band is used and compact bandwidth is enabled, the remaining
frequency resources can be used for GSM. These GSM frequencies are calculated by using
the following formulas:
Fu(n) = Fl(n) + 95
where
The GSM channel spacing is 200 kHz, and the difference between the uplink and downlink frequencies
is 95 MHz.
For example, in scenarios where the GSM and LTE cells do not share an RRU, if a compact
bandwidth of 18.3 MHz is deployed for LTE in the band from 1805 MHz to 1825 MHz, 200
kHz bandwidth is available for each GSM frequency and the following GSM ARFCNs can be
used for deploying GSM in the band:
Figure 3-3 Changes before and after compact bandwidth is enabled in LTE only scenarios
when the cell bandwidth is 7.5 MHz
4 Compact Bandwidth
4.1 Principles
Table 4-1 lists the number of available RBs under each standard bandwidth.
1.4 6
3 15
5 25
10 50
15 75
20 100
Under a compact bandwidth, the number of available RBs may be less than that under the
standard bandwidth. The following key techniques facilitate the deployment of LTE networks
under non-standard bandwidths:
l Guard bandwidth reduction through stringent filtering
l Effective bandwidth reduction
These techniques apply to all compact bandwidths in various scenarios.
1.4 MHz (compressed to 1.2 160 kHz at each end of the 60 kHz at each end of the
MHz to 1.3 MHz) band band
5 MHz (compressed to 4.4 250 kHz at each end of the 130 kHz at each end of the
MHz to 4.9 MHz) band band
10 MHz (compressed to 7.4 500 kHz at each end of the 435 kHz at each end of the
MHz to 7.5 MHz) band band
10 MHz (compressed to 8 500 kHz at each end of the 400 kHz at each end of the
MHz) band band
10 MHz (compressed to 8.7 500 kHz at each end of the 500 kHz at each end of the
MHz) band band
10 MHz (compressed to 8.8 500 kHz at each end of the 260 kHz at each end of the
MHz) band band
10 MHz (compressed to 8.9 500 kHz at each end of the 300 kHz at each end of the
MHz to 9.9 MHz) band band
15 MHz (compressed to 750 kHz at each end of the 550 kHz at each end of the
13.9 MHz to 14.9 MHz) band band
20 MHz (compressed to 1 MHz at each end of the 500 kHz at each end of the
17.5 MHz to 17.8 MHz) band band
20 MHz (compressed to 1 MHz at each end of the 650 kHz at each end of the
18.3 MHz to 19.9 MHz) band band
NOTE
Requirements for guard bandwidths are stipulated in section 5.6 of 3GPP TS 36.104 V9.3.0 (2010-03).
For details about resource allocation algorithms for physical channels under standardized
bandwidths, see Physical Channel Resource Management.
Figure 4-1 Example of PUCCH and PUSCH resource allocations in multi-RAT scenarios
In LTE only scenarios, UEs regard bandwidths standard. Therefore, the PUCCH must be
moved inwards to reduce the uplink out-of-band interference.
The Cell.CompactBwCtrlIntrfMode parameter can be set to REDUCED to move the
PUCCH inwards to reduce uplink out-of-band interference. If uplink out-of-band interference
is not reduced after the setting of the Cell.CompactBwCtrlIntrfMode parameter, configure the
Cell.UlPuncturedRbNumOffset parameter to specify the number of RBs to be moved at each
end.
l If the Cell.CompactBwCtrlIntrfMode parameter is set to REDUCED and the
Cell.UlPuncturedRbNumOffset parameter is set to 0, the PUCCH is moved one RB
inwards at each end and the uplink bandwidth remains unchanged, as shown in Figure
4-2.
Figure 4-2 Example of PUCCH and PUSCH resource allocations in LTE only scenarios
when GSM and LTE cells share the same RRU. For details, see 4.1.3 Key Compact
Bandwidth Technologies. The settings of the Cell.DlPuncturedRbNum parameter can
take effect when GSM and LTE cells do not share an RRU. However, these settings
increase downlink interference and degrade the cell performance.
– If the Cell.DlPuncturedRbNum parameter is set to 0, downlink RBs are not
punctured. In this case, the number of RBs occupied by the PDCCH equals to that
occupied by the PDSCH.
– If the Cell.DlPuncturedRbNum parameter is set to a non-zero value, the number of
RBs occupied by the PDCCH equals to the difference between the number of RBs
in the standardized bandwidth and Cell.DlPuncturedRbNum.
After the RB is punctured, the number of RBs occupied by the PDSCH equals to those
occupied by the PDCCH minus 2. For example, under the bandwidths of 4.4 MHz to 4.7
MHz, if the number of RBs occupied by the PDCCH is 23, the number of available downlink
PDSCH RBs is 21.
The number of RBs occupied by the PDSCH is two less than those occupied by the PDCCH.
This is because:
The test results prove that using these two PDSCH RBs decreases the throughput. Therefore,
these two PDSCH RBs are not used. To guarantee the performance, one more RB is punctured
at both ends of the frequency band for the downlink than that for the uplink.
The CQI adjustment algorithm applies to standardized and compact bandwidths as follows:
coding scheme (MCS) based on the combined wideband and subband CQIs and delivers
the MCS to the UE. As a result, the CQI adjustment algorithm provides lower accuracy,
which has little impact on performance and overall resource allocation fairness in
frequency selective scheduling mode.
For details about the CQI adjustment algorithm, see Channel State Management.
1 1.2 to 1.3 eNodeBs take all 6 0 0 The physical cell 450 MHz
values ranging from identifier (PCI) RRU3668
1.2 MHz to 1.3 value range in this
MHz as 1.2 MHz, solution is the same
and use special as that under the
stringent filters for standardized 1.4
1.4 MHz in their MHz bandwidth.
radio frequency
(RF) units to
minimize signal
spill-over from the
available
bandwidth. This
solution does not
require RB
puncturing from the
standardized
bandwidth.
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
3 4.8 to 4.9 eNodeBs take all 25 0 0 The PCI value MRFUd, 1800
values ranging from range in this MHz RRU3928,
4.8 MHz to 4.9 solution is the same 1800 MHz
MHz as 4.8 MHz. as that under the RRU3929, 1800
The eNodeBs use standardized 5 MHz MHz
special stringent bandwidth. RRU3962d,
filters for 5 MHz in AAU3940, 850
their RF units to MHz RRU3662
minimize signal V6, RRU3959,
spill-over from the RRU3959a, 1800
available MHz
bandwidth. This RRU3953w,
solution does not 1800 MHz
require RB MRFUdw V6,
puncturing from the 1800 MHz
standardized AAU5972 port
bandwidth. A, pRRU5913,
pRRU5918,
pRRU5920,
pRRU5922,
pRRU5923,
pRRU5921, 900
MHz RRU5909,
900 MHz
MRFUdv3, and
hRRU5901
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
4 7.4 to 7.5 eNodeBs take all 36 Sym 14 The PCI value 900 MHz
values ranging from metri range in this RRU3938, 850
7.4 MHz to 7.5 c solution is the same MHz RRU3652,
MHz as 7.35 MHz. comp as that under the 850 MHz
The eNodeBs ressio standardized 10 RRU3653, 850
puncture 14 RBs n MHz bandwidth. MHz RRU3662,
from the scena pRRU5913,
standardized 10 rios: pRRU5918,
MHz bandwidth 16 pRRU5920,
and use special Asym pRRU5922,
stringent filters for metri pRRU5923,
10 MHz in their RF c pRRU5921, and
units to minimize comp hRRU5901
signal spill-over ressio
from the available n
bandwidth. scena
rios:
15
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
6 8.7 eNodeBs take all 42 Sym 8 The PCI value 850 MHz
values ranging from metri range in this RRU3652, 850
8.7 MHz to 8.75 c solution is the same MHz RRU3653,
MHz. The eNodeBs comp as that under the and 850 MHz
puncture eight RBs ressio standardized 10 RRU3662
from the n MHz bandwidth.
standardized 10 scena
MHz bandwidth rios:
and use special 10
stringent filters for Asym
10 MHz in their RF metri
units to minimize c
signal spill-over comp
from the available ressio
bandwidth. n
scena
rios: 9
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
10 9.6 to 9.9 eNodeBs take all 50 0 0 The PCI value 900 MHz/1800
values ranging from range in this MHz MRFUd,
9.6 MHz to 9.9 solution is the same 900 MHz/1800
MHz as 9.6 MHz. as that under the MHz RRU3928,
The eNodeBs use standardized 10 900 MHz/1800
special stringent MHz bandwidth. MHz RRU3929,
filters for 10 MHz 900 MHz
in their RF units to RRU3938, 1800
minimize signal MHz RRU3953,
spill-over from the 900 MHz
available RRU3959, 900
bandwidth. This MHz
solution does not RRU3959a, 1800
require RB MHz
puncturing from the RRU3962d,
standardized 1800 MHz
bandwidth. RRU3971, 1800
MHz
RRU3971a, 1800
MHz AAU3940,
1800 MHz
AAU5972 port
A, 900 MHz
MRFUd V3, 900
MHz RRU3929
V3, 900 MHz
RRU3953 V6,
900 MHz
RRU3959 V6,
and 900 MHz
RRU3939
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
RRU5501, 2100
MHz RRU5502,
2100 MHz
RRU5507, 2100
MHz RRU3838,
and 2100 MHz
RRU3962
14 17.5 to eNodeBs take all 86 Sym 14 The PCI value 700 MHz
17.8 values ranging from metri range in this RRU3268
17.5 MHz to 17.8 c solution is the same
MHz as 17.5 MHz. comp as that under the
The eNodeBs ressio standardized 20
puncture 14 RBs n MHz bandwidth.
from the scena
standardized 20 rios:
MHz bandwidth 16
and use special Asym
stringent filters for metri
20 MHz in their RF c
units to minimize comp
signal spill-over ressio
from the available n
bandwidth. scena
rios:
15
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
No. Compac Compact Num Num Num PCI Value Range Supporting RF
t Bandwidth ber ber ber Module
Bandwi Solution of of of
dth Avail RBs Punct
Range able Punc ured
Support Upli tured Uplin
ed by nk by k
eNodeB RBs the RBs
s PDS
MHz CH
18 19.3 to eNodeBs take all 100 0 0 The PCI value 1800 MHz
19.9 values ranging from range in this MRFUd, 1800
19.3 MHz to 19.9 solution is the same MHz RRU3928,
MHz as 19.3 MHz. as that under the 1800 MHz
The eNodeBs use standardized 20 RRU3929, 1800
special stringent MHz bandwidth. MHz RRU3953,
filters for 20 MHz 1800 MHz
in their RF units to RRU3962d,
minimize signal 1800 MHz
spill-over from the RRU3971, 1800
available MHz
bandwidth. This RRU3971a,
solution does not AAU3940, and
require RB 1800 MHz
puncturing from the AAU5972 port A
standardized
bandwidth.
Solutions 4, 6, and 14 in Table 4-3 support both symmetric compression on both sides of a
bandwidth and asymmetric compression on only one side of a bandwidth. This function is
controlled by the Cell.CompactBwCtrlIntrfMode parameter and only applies to macro base
stations.
Table 4-4 Compact bandwidth range when GSM and LTE cells share an RRU
Cell.CustomizedDLBand- Cell.DlPuncturedRbNum Valid Bandwidth
Width Value Value
2 19 MHz
4 18.6 MHz
2 19 MHz
The settings of the Cell.DlPuncturedRbNum parameter in the preceding table can take effect
when GSM and LTE cells do not share an RRU, but these settings increase downlink
interference and degrade the cell performance.
On GSM+LTE 450/850/900/1800 MHz networks, if the Cell.CustomizedULBandWidth and
Cell.CustomizedDLBandWidth parameters are set using the Configuration Management
Express (CME) for the LTE network, the CME performs parameter checks based on the
configured values; however, the bandwidth settings take effect according to the Compact
Bandwidth solution. For example, if the two parameters are set to indicate a bandwidth of
19.9 MHz, the CME performs a parameter check based on 19.9 MHz, but the bandwidth that
takes effect is 19.3 MHz according to solution 18 described in Table 4-3.
If the Cell.CustomizedULBandWidth parameter is set to 8, it is recommended that
Cell.DlPuncturedRbNum be set to 255 rather than 8. Otherwise, downlink interference
increases, and spectral efficiency decreases.
4.2.1 Benefits
The compact bandwidth feature increases spectral efficiency, raises cell throughput, and
improves user experience. It is transparent to UEs and compatible with Third Generation
Partnership Project (3GPP) Release 8 and later. This function does not require any
modifications to algorithms in UEs.
4.2.2 Impacts
Network Impacts
For a given available bandwidth, this feature uses compact bandwidths to provide higher
spectrum efficiency and larger system capacity than standardized bandwidths.
The techniques for compact bandwidth are transparent to UEs. UEs behave in the same way
as in a cell with the corresponding standardized bandwidth when this feature is used. UEs in a
cell with a compact bandwidth experience higher inter-RAT interference (for example, GSM
interference in GSM/LTE refarming scenarios) than those in a cell with the corresponding
standardized bandwidth. The higher interference causes network performance deterioration in
terms of the access success rate, handover success rate, service drop rate, and BLER.
Function Impacts
Function Function Reference Description
Name Switch
PCI conflict ENodeBAlgoS PCI Conflict PCIs of cells affect the locations of
detection and witch.PciConfli Detection and RBs occupied by PHICHs and
self- ctDetectSwitch Self- PCFICHs. Under Compact
optimization Optimization Bandwidth, constraints are
imposed on PCI assignment to
prevent punctured RBs from being
occupied by PHICHs and
PCFICHs. When compact
bandwidth and PCI conflict
detection and self-optimization are
enabled, the range of available
PCIs for PCI conflict detection and
self-optimization must be set and
cannot exceed the range of
available PCIs for compact
bandwidth.
LTE guard band None NB-IoT Radio This function cannot be deployed
deployment and because the guard band is small in
Performance some compact bandwidths.
Basics (FDD)
4.3 Requirements
4.3.1 Licenses
The following are license requirements.
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
In multi-RAT scenarios, base stations of LTE and other RATs must share antennas, and the
ratio of LTE sites to sites of other RATs is 1:1. Base stations of all RATs must be provided by
Huawei.
Boards
Board Supported Scenario
RF Modules
For details about RF modules supporting different compact bandwidths, see the last column in
4.1.3 Key Compact Bandwidth Technologies.
4.3.4 Networking
Spectrum Requirements
LTE cell bandwidth, which is specified by the Cell.UlBandWidth and Cell.DlBandWidth
parameters, must fall into the range of operators' spectrum.
When planning frequency resources, ensure that the frequency bands for LTE services do not
overlap with the edge frequencies of the 450 MHz, 850 MHz, 900 MHz, and 1800 MHz
bands, or with the edge frequencies of the band supported by the RRU. The goal is to ensure
the successful deployment of the standardized bandwidths corresponding to the compact
bandwidths, which are implemented by puncturing RBs at the two ends of the standardized
bandwidths.
For example, an operator expects to release certain frequency resources in the 1800 MHz
GSM band for deploying an LTE network with a compact bandwidth of 19 MHz, which
corresponds to the standardized bandwidth of 20 MHz. 3GPP specifications specify that the
frequency range for the 1800 MHz band is 1805-1880 MHz. To achieve this expectation, the
operator can use 1805.5 MHz to 1824.5 MHz for LTE with the center frequency at 1815
MHz.
PSD Requirements
LTE and other RATs have the following requirements on the power spectrum density (PSD)
difference:
l If compact bandwidth is performed on the 5 MHz or 10 MHz bandwidth, the PSD
difference between LTE and other RATs cannot exceed 11 dB.
l If compact bandwidth is performed on the 15 MHz or 20 MHz bandwidth, the PSD
difference between LTE and other RATs cannot exceed 14 dB.
Co-antenna scenarios
In co-antenna and 1:1 site deployment scenarios, the PSD can be calculated based on the
configured power.
NOTE
1:1 site deployment refers to scenarios where an LTE cell and a GSM cell cover the same area.
For example, if the LTE bandwidth of 10 MHz (50 RBs with each of 0.18 MHz) is
compressed to 8.6 MHz and two transmit antennas are used, the following parameters are set
as follows:
PDSCHCfg.ReferenceSignalPwr= 212
PDSCHCfg.Pb = 1
CellDlpcPdschPa.PaPcOff= -3
In this case, the LTE cell power is 2 x 40 W. If the power of a neighboring GSM cell is 20 W
(a single carrier with a bandwidth of 0.2 MHz), the power difference between LTE and GSM
cells is –10.5 dB, which is calculated by the following formula:
10 x log([2 x 40/(50 x 0.18)]/(20/0.2)) = –10.5 dB
The absolute value of this difference is 10.5 dB, which is less than 11 dB.
Non-co-antenna scenarios
In non-co-antenna scenarios, the PSD difference between LTE and other RATs must be
measured through drive tests because such a difference cannot be calculated based on the
configured power spectrum density.
NOTE
Spectrum Requirements
LTE cell bandwidth, which is specified by the Cell.UlBandWidth and Cell.DlBandWidth
parameters, must fall into the range of operators' spectrum.
When planning frequency resources, ensure that the frequency bands for LTE services do not
overlap with the edge frequencies of the 450 MHz, 850 MHz, 900 MHz, and 1800 MHz
bands, or with the edge frequencies of the band supported by the RRU. The goal is to ensure
the successful deployment of the standardized bandwidths corresponding to the compact
bandwidths, which are implemented by puncturing RBs at the two ends of the standardized
bandwidths.
For example, an operator expects to release certain frequency resources in the 1800 MHz
GSM band for deploying an LTE network with a compact bandwidth of 19 MHz, which
corresponds to the standardized bandwidth of 20 MHz. 3GPP specifications specify that the
frequency range for the 1800 MHz band is 1805-1880 MHz. To achieve this expectation, the
operator can use 1805.5 MHz to 1824.5 MHz for LTE with the center frequency at 1815
MHz.
Interference caused by spectrum leakage exists in the uplink because UEs transmit signals in
the uplink using standardized bandwidths. Therefore, UEs on the live network need to be
tested. If the test results meet spectrum leakage requirements specified in 3GPP
specifications, this function can be deployed. Otherwise, this function cannot be deployed.
PSD Requirements
LTE and adjacent networks have the following requirements on the PSD difference:
l If compact bandwidth is performed on the 5 MHz or 10 MHz bandwidth, the PSD
difference between the local LTE cell and adjacent cells cannot exceed 11 dB.
l If compact bandwidth is performed on the 15 MHz or 20 MHz bandwidth, the PSD
difference between the local LTE cell and adjacent cells cannot exceed 14 dB.
In LTE only scenarios, the LTE cell cannot share the antenna system with adjacent cells.
Therefore, the PSD cannot be directly evaluated based on the power configuration. The PSD
difference between the local LTE cell and adjacent cells needs to be obtained through drive
tests. For details about how to calculate the PSD in co-antenna scenarios, see PSD
Requirements.
l The bandwidths acquired by an operator are within the ranges listed in 4.1.3 Key
Compact Bandwidth Technologies and meet bandwidth requirements listed in 4.3.3
Hardware.
l When both compact bandwidth and carrier aggregation are enabled, you are not advised
to configure cells with customized bandwidths as primary serving cells.
Step 1 Configure the standardized bandwidths of a cell and enable compact bandwidth in the cell.
For details, see Table 4-5.
Step 2 Configure operators' non-standardized cell bandwidths. Values of related parameters vary
according to scenarios. For details, see the following sections.
----End
Table 4-5 Parameters used for configuring the standardized bandwidths of a cell and enabling
compact bandwidth in the cell
Parameter Parameter ID Setting Notes
Name
The following table describes the parameters used for function optimization in scenario 1.
The following table describes the parameters used for function optimization in scenario 2.
The following table describes the parameters used for function activation in scenario 3.
The following table describes the parameters used for function optimization in scenario 3.
The following table describes the parameters used for function optimization in scenario 4.
The following table describes the parameters used for function activation in all scenarios.
CQI Set this Set this Set this Set this Set this Set this Set this Set this
RB parame parame parame parame parame parame parame parame
number ter to 1. ter to 2. ter to 1. ter to 2. ter to 1. ter to 2. ter to 1. ter to 2.
(PUCC
HCfg.
CqiRb
Num)
ACK/S Set this Set this Set this Set this Set this Set this Set this Set this
RI parame parame parame parame parame parame parame parame
Channe ter to ter to ter to ter to ter to ter to ter to ter to
l 20. 12. 47. 39. 58. 50. 52. 44.
Numbe
r
(PUCC
HCfg.
NaSriC
hNum)
Format Retain Set this Retain Set this Retain Set this Retain Set this
3 RB the parame the parame the parame the parame
Numbe default ter to 1. default ter to 1. default ter to 1. default ter to 1.
r value. value. value. value.
(PUCC
HCfg.
Format
3RbNu
m)
Scenario 3
ADD CELL: LocalCellId=0, CellName="0", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1300, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=0,
PhyCellId=8, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=CFG, CustomizedDLBandWidth=183,
CustomizedULBandWidth=183,DlPuncturedRbNum=0, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
Scenario 4
ADD CELL: LocalCellId=0, CellName="0", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1300, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0,
PhyCellId=8, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=CFG, CustomizedDLBandWidth=87,
CustomizedULBandWidth=87, DlPuncturedRbNum=255, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, DlPuncturedRbNum=255,
CompactBwCtrlIntrfMode=REDUCED, UlPuncturedRbNumOffset=0, TxRxMode=2T2R;
Scenario 4
//Turning on the non-standardized bandwidth algorithm switch
MOD
CELLALGOSWITCH:LOCALCELLID=0,NonStandardBwAlgoSw=PCFICH_POWER_OPT_SWITCH-1&PDCCH_P
OWER_OPT_SWITCH-1&PUCCH_SRS_ADAPT_SWITCH-1;
Scenario 4 (If the power difference between LTE and other RATs cannot be calculated,
perform the following operations based on the preceding optimization)
//Setting the RB Damage Cell Near Point User IBLER Thd parameter to its default
value 20
MOD CELLDLSCHALGO:LOCALCELLID=0,RBDamageNearPointIblerTh=20;
Scenario 4 (If the power difference between LTE and other RATs can be calculated,
perform the following operations based on the preceding optimization)
//Setting the RB Damage Cell Near Point User IBLER Thd parameter
MOD CELLDLSCHALGO:LOCALCELLID=0,RBDamageNearPointIblerTh=0;
Step 2 After this feature is activated in a cell, check whether the value of L.ChMeas.PRB.UL.Avail
is 98 and the value of L.ChMeas.PRB.DL.Avail is 96. If they are, compact bandwidth has
been activated.
----End
The following procedure takes activation observation for the compact bandwidth in scenario 3
with 9.2 MHz original bandwidth and 9.6 MHz valid bandwidth as an example:
Step 1 Set the Cell.UlBandWidth and Cell.DlBandWidth parameters both to 10 MHz, the
Cell.CustomizedULBandWidth and Cell.CustomizedDLBandWidth parameters both to 9.2
MHz, the Cell.CustomizedBandWidthCfgInd parameter to CFG, and the
Cell.DlPuncturedRbNum parameter to 0.
Step 2 After the cell is activated, check whether the value of L.ChMeas.PRB.UL.Avail is 48 and the
value of L.ChMeas.PRB.DL.Avail is 50. If they are, the valid bandwidth for compact
bandwidth has taken effect.
----End
NOTE
System Bandwidth in the result of the received signal strength indicator (RSSI) statistics monitoring
task on the U2000 indicates the standardized bandwidth before compression.
5 Parameters
Cell UlPunct ADD LOFD-0 Compac Meaning: Indicates the offset for the number of RBs
uredRb CELL 01051 t blocked in a cell in the uplink. This parameter applies
NumOff MOD Bandwi only to LTE FDD.
set CELL dth GUI Value Range: -5~8
LST Unit: None
CELL Actual Value Range: -5~8
Default Value: 0
Cell Compac ADD LOFD-0 Compac Meaning: Indicates the interference control mode for
tBwCtrlI CELL 01051 t scenarios where compact bandwidth is used. This
ntrfMod MOD Bandwi parameter applies only to LTE FDD.
e CELL dth GUI Value Range: NORMAL(NORMAL),
LST REDUCED(REDUCED),
CELL REDUCED_LEFT(REDUCED_LEFT),
REDUCED_RIGHT(REDUCED_RIGHT)
Unit: None
Actual Value Range: NORMAL, REDUCED,
REDUCED_LEFT, REDUCED_RIGHT
Default Value: NORMAL(NORMAL)
Cell UlBand ADD LOFD-0 Compac Meaning: Indicates the UL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009/ dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
LST between the parameter value and the actual cell
CELL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
informat deduced similarly. For details, see 3GPP TS 36.104.
TDLBF This parameter applies only to LTE FDD and LTE
D-00100 ion
TDD.
3 Scalable
Bandwi GUI Value Range: CELL_BW_N6(1.4M),
dth CELL_BW_N15(3M), CELL_BW_N25(5M),
CELL_BW_N50(10M), CELL_BW_N75(15M),
CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Default Value: None
Cell DlBand ADD LOFD-0 Compac Meaning: Indicates the DL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009/ dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
DSP between the parameter value and the actual cell
DDCEL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
LGROU deduced similarly. For details, see 3GPP TS 36.104.
P TDLBF informat
ion This parameter applies only to LTE FDD and LTE
LST D-00100 TDD.
CELL 3 Scalable
Bandwi GUI Value Range: CELL_BW_N6(1.4M),
dth CELL_BW_N15(3M), CELL_BW_N25(5M),
CELL_BW_N50(10M), CELL_BW_N75(15M),
CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Default Value: None
Cell 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 DlPunct ADD LOFD-0 Compac Meaning: Indicates the number of downlink RBs
uredRb CELL 01051 t blocked in a cell. This parameter applies only to LTE
Num MOD Bandwi FDD.
CELL dth GUI Value Range: 0~13,255
LST Unit: None
CELL Actual Value Range: 0~13,255
Default Value: 255
Cell Customi ADD LOFD-0 Compac Meaning: Indicates whether to configure a compact
zedBand CELL 01051 t bandwidth for a cell. A compact bandwidth can be
WidthCf MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
gInd CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured. This parameter applies only to LTE FDD
LST and LTE TDD.
CELL
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)
Cell Customi ADD LOFD-0 Compac Meaning: Indicates a customized uplink bandwidth
zedULB CELL 01051 t configured for a cell. A compact bandwidth can be
andWidt MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
h CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured. This parameter applies only to LTE FDD.
LST
CELL GUI Value Range:
12~14,44~50,74~75,80,87~100,139~150,175~178,18
3~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,7.4~7.5,8.0,8.7~10.0,13.9~15.0,17.5~
17.8,18.3~20.0
Default Value: 98
Cell Customi ADD LOFD-0 Compac Meaning: Indicates a customized downlink bandwidth
zedDLB CELL 01051 t configured for a cell. A compact bandwidth can be
andWidt MOD Bandwi configured only when a standard bandwidth 1.4 MHz,
h CELL dth 5 MHz, 10 MHz, 15 MHz, or 20 MHz has been
configured. This parameter applies only to LTE FDD.
LST
CELL GUI Value Range:
12~14,44~50,74~75,80,87~100,139~150,175~178,18
3~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,7.4~7.5,8.0,8.7~10.0,13.9~15.0,17.5~
17.8,18.3~20.0
Default Value: 98
witch, DlNonStandardBwMaxPwrSwitch,
PhichPwrRestrictSwitch
Default Value: PhichInnerLoopPcSwitch:Off,
PdcchPcSwitch:On, EDlMaxTXPwrSwitch:Off,
BFModeUserPwrSwitch:Off, SigPowerIncreaseS-
witch:Off, BFModeUserAdptPwrSwitch:Off,
BfEnhChnPwrFormSwitch:Off, DlNonStandardBw-
MaxPwrSwitch:Off, PhichPwrRestrictSwitch:Off
CqiFltOptSwitch(CqiFltOptSwitch),
PreciseMcsAdaptSwitch(PreciseMcsAdaptSwitch),
PilotOffCqiAdjOptSwitch(PilotOffCqiAdjOptSwitch)
Unit: None
Actual Value Range: CqiAdjAlgoSwitch,
StepVarySwitch, DlVarIBLERtargetSwitch,
TddBundlingCqiAdjOptSwitch, TddMultiplexingC-
qiAdjOptSwitch, AdaptiveStepVarySwitch,
DlCqiAdjDeltaOptSwitch, DlEnVarIblerTargetSwitch,
DlRetxTbsIndexAdjOptSwitch,
CfiConvertOptSwitch, BundlingOptThdSwitch,
DlSpsMcsIncreaseSwitch, CqiAdjTimeEffSwitch,
RptCqiFltInitSwitch, UeSigInitCqiModSwitch,
CqiFastCompstSwitch, CfiConvertWiDrsSwitch,
IblerCqiOffsetSwitch, CqiFltOptSwitch,
PreciseMcsAdaptSwitch, PilotOffCqiAdjOptSwitch
Default Value: CqiAdjAlgoSwitch:On,
StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off,
TddBundlingCqiAdjOptSwitch:Off,
TddMultiplexingCqiAdjOptSwitch:Off,
AdaptiveStepVarySwitch:Off, DlCqiAdjDeltaOptS-
witch:Off, DlEnVarIblerTargetSwitch:Off,
DlRetxTbsIndexAdjOptSwitch:On,
CfiConvertOptSwitch:Off,
BundlingOptThdSwitch:Off, DlSpsMcsIncreaseS-
witch:Off, CqiAdjTimeEffSwitch:Off,
RptCqiFltInitSwitch:On, UeSigInitCqiMod-
Switch:Off, CqiFastCompstSwitch:Off,
CfiConvertWiDrsSwitch:Off, IblerCqiOffsetS-
witch:Off, CqiFltOptSwitch:Off, PreciseMcsAdaptS-
witch:Off, PilotOffCqiAdjOptSwitch:Off
IDLE_EDRX_SWITCH(IDLE_EDRX_SWITCH),
G_VALUE_CFG_SWITCH(G_VALUE_CFG_SWIT
CH),
SI_UPDATE_REL_UE_SWITCH(SI_UPDATE_REL
_UE_SWITCH),
EMTC_ONLY_CELL_SWITCH(EMTC_ONLY_CE
LL_SWITCH),
MODE_A_UE_TA_SCHEDULING_SWITCH(MOD
E_A_UE_TA_SCHEDULING_SWITCH),
EMTC_UE_ACK_START_OFFSET_CFG(EMTC_U
E_ACK_START_OFFSET_CFG),
DL_PERFORMANCE_ENHANCE_SWITCH(DL_P
ERFORMANCE_ENHANCE_SWITCH),
UL_PERFORMANCE_ENHANCE_SWITCH(UL_P
ERFORMANCE_ENHANCE_SWITCH),
MPDCCH_MORE_AVAIL_NB_SWITCH(MPDCCH
_MORE_AVAIL_NB_SWITCH),
UL_MCS_SCHEDULING_OPT_SWITCH(UL_MCS
_SCHEDULING_OPT_SWITCH)
Unit: None
Actual Value Range: EMTC_SWITCH,
IDLE_EDRX_SWITCH, G_VALUE_CFG_SWITCH,
SI_UPDATE_REL_UE_SWITCH,
EMTC_ONLY_CELL_SWITCH,
MODE_A_UE_TA_SCHEDULING_SWITCH,
EMTC_UE_ACK_START_OFFSET_CFG,
DL_PERFORMANCE_ENHANCE_SWITCH,
UL_PERFORMANCE_ENHANCE_SWITCH,
MPDCCH_MORE_AVAIL_NB_SWITCH,
UL_MCS_SCHEDULING_OPT_SWITCH
Default Value: EMTC_SWITCH:Off,
IDLE_EDRX_SWITCH:Off,
G_VALUE_CFG_SWITCH:Off,
SI_UPDATE_REL_UE_SWITCH:Off,
EMTC_ONLY_CELL_SWITCH:Off,
MODE_A_UE_TA_SCHEDULING_SWITCH:On,
EMTC_UE_ACK_START_OFFSET_CFG:Off,
DL_PERFORMANCE_ENHANCE_SWITCH:Off,
UL_PERFORMANCE_ENHANCE_SWITCH:Off,
MPDCCH_MORE_AVAIL_NB_SWITCH:Off,
UL_MCS_SCHEDULING_OPT_SWITCH:Off
EmimoFbaSwitch:Off, New4TCodebookSwitch:Off,
4TxTM9MuMimoSwitch:Off, DrxSimulAckNack-
AndCqiSwitch:Off, PreciseAmcSwitch:Off,
EmimoCsiEnhanceSwitch:Off, PUSCH12Switch:Off
DdCell DdBand ADD LEOFD- Flexible Meaning: Indicates the bandwidth of a Double Deck
Group width DDCEL 111302 Bandwi cell group. This parameter applies only to FDD.
LGROU dth GUI Value Range: BW_2DOT6M(2.6M),
P based on BW_4M(4M), BW_5DOT7M(5.7M),
LST Overlap BW_7DOT3M(7.3M), BW_7DOT6M(7.6M),
DDCEL Carriers BW_10DOT8M(10.8M), BW_12DOT2M(12.2M),
LGROU BW_12DOT5M(12.5M), BW_17DOT1M(17.1M),
P BW_17DOT4M(17.4M), BW_27DOT6M(27.6M),
RMV BW_28DOT5M(28.5M), BW_23DOT9M(23.9M),
DDCEL BW_8DOT6M(8.6M), BW_8DOT9M(8.9M),
LGROU BW_14DOT1M(14.1M), BW_14DOT4M(14.4M),
P BW_18DOT7M(18.7M), BW_19M(19M)
DSP Unit: None
DDCEL Actual Value Range: BW_2DOT6M, BW_4M,
LGROU BW_5DOT7M, BW_7DOT3M, BW_7DOT6M,
P BW_10DOT8M, BW_12DOT2M, BW_12DOT5M,
BW_17DOT1M, BW_17DOT4M, BW_27DOT6M,
BW_28DOT5M, BW_23DOT9M, BW_8DOT6M,
BW_8DOT9M, BW_14DOT1M, BW_14DOT4M,
BW_18DOT7M, BW_19M
Default Value: None
Spectru Spectru ADD MRFD- GSM Meaning: Indicates whether to enable the spectrum
mCloud mCloud SPECT 130221 and LTE cloudification feature. When this parameter is set to
Switch RUMCL MRFD- Spectru OFF, spectrum cloudification is disabled. When this
OUD 130222 m parameter is set to
MOD Concurr GL_SPECTRUM_CONCURRENCY, GSM and LTE
SPECT ency spectrum concurrency is enabled. When this
RUMCL (LTE parameter is set to UL_SPECTRUM_SHARING,
OUD FDD) UMTS and LTE spectrum sharing is enabled. This
UMTS parameter applies only to LTE FDD.
LST
SPECT and LTE GUI Value Range: OFF(OFF),
RUMCL Spectru GL_SPECTRUM_CONCURRENCY(GL_SPECTRU
OUD m M_CONCURRENCY),
Sharing UL_SPECTRUM_SHARING(UL_SPECTRUM_SH
(LTE ARING)
FDD) Unit: None
Actual Value Range: OFF,
GL_SPECTRUM_CONCURRENCY,
UL_SPECTRUM_SHARING
Default Value: OFF(OFF)
MPDCCH_PDSCH_FREQ_HOPPING_SW(MPDCC
H_PDSCH_FREQ_HOPPING_SW)
Unit: None
Actual Value Range: PRACH_FREQ_HOPPING_SW,
PUSCH_FREQ_HOPPING_SW,
MPDCCH_PDSCH_FREQ_HOPPING_SW
Default Value: PRACH_FREQ_HOPPING_SW:Off,
PUSCH_FREQ_HOPPING_SW:Off,
MPDCCH_PDSCH_FREQ_HOPPING_SW:Off
PDSCH Referen MOD LBFD-0 Dynami Meaning: Indicates the cell reference signal power of
Cfg ceSignal PDSCH 02016/ c each physical antenna (the precision of converting
Pwr CFG TDLBF Downlin dBm to mW is 0.01 mW). However, the cell reference
LST D-00201 k Power signal power delivered in SIB2 is that of each logical
PDSCH 6 Allocati antenna. If the EMTC_SWITCH option of the
CFG LBFD-0 on EmtcAlgoSwitch parameter in a CellEmtcAlgo MO is
02009/ Broadca selected and the value of this parameter is changed,
TDLBF st of eMTC UEs that already accessed the cell will be
D-00200 system proactively released.
9 informat GUI Value Range: -600~500
MLBFD ion Unit: 0.1dBm
-120002 Broadca Actual Value Range: -60~50
29 st of
system Default Value: 182
informat
ion
PDSCH Pb MOD LBFD-0 Dynami Meaning: Indicates the scaling factor index of the
Cfg PDSCH 02016/ c Energy Per Resource Element (EPRE) on the PDSCH.
CFG TDLBF Downlin This scaling factor is determined by the value of this
LST D-00201 k Power parameter and the antenna port. For details, see 3GPP
PDSCH 6 Allocati TS 36.213. If the EMTC_SWITCH option of the
CFG LBFD-0 on EmtcAlgoSwitch parameter in a CellEmtcAlgo MO is
02009/ Broadca selected and the value of this parameter is changed,
TDLBF st of eMTC UEs that already accessed the cell will be
D-00200 system proactively released.
9 informat GUI Value Range: 0~3
ion Unit: None
Actual Value Range: 0~3
Default Value: 1
CellDlp PaPcOff MOD LBFD-0 Dynami Meaning: Indicates the PA to be used when DL ICIC
cPdschP CELLD 02016/ c is disabled, and the even power distribution is used for
a LPCPD TDLBF Downlin the PDSCH. This parameter applies only to LTE FDD
SCHPA D-00201 k Power and LTE TDD.
LST 6 Allocati GUI Value Range: DB_6_P_A(-6 dB),
CELLD LOFD-0 on DB_4DOT77_P_A(-4.77 dB), DB_3_P_A(-3 dB),
LPCPD 70208 Coordin DB_1DOT77_P_A(-1.77 dB), DB0_P_A(0 dB),
SCHPA ated DB1_P_A(1 dB), DB2_P_A(2 dB), DB3_P_A(3 dB)
Scheduli Unit: dB
ng based
Power Actual Value Range: DB_6_P_A, DB_4DOT77_P_A,
Control DB_3_P_A, DB_1DOT77_P_A, DB0_P_A,
DB1_P_A, DB2_P_A, DB3_P_A
Default Value: DB_3_P_A(-3 dB)
PHICH PhichDu MOD LBFD-0 Physical Meaning: Indicates the PHICH duration type. If this
Cfg ration PHICH 02003/ Channel parameter is set to NORMAL, the number of OFDM
CFG TDLBF Manage symbols occupied by the PDCCH is automatically
LST D-00200 ment adjusted. If this parameter is set to EXTENDED, the
PHICH 3 Compac number of OFDM symbols occupied by the PDCCH
CFG LOFD-0 t is fixed. Specifically, this number is fixed to 3 or 4 for
01051 Bandwi 1.4 MHz cells and 3 for cells with other bandwidths.
dth For the mapping between the type and the duration,
LBFD-0 see 3GPP TS 36.211. This parameter applies only to
02009/ Broadca LTE FDD and LTE TDD.
TDLBF st of
D-00200 system GUI Value Range: NORMAL, EXTENDED
9 informat Unit: None
ion Actual Value Range: NORMAL, EXTENDED
Default Value: NORMAL
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 Virtual configured for UEs in the cell. The value
G LEOFD- 4T4R BOOLEAN_FALSE indicates that no SRS resource is
111305 available in the cell, and therefore no UE in the cell is
DL 4- configured with SRS resources. This parameter does
TDLAO Layer not take effect on: (1) FDD cell that is established on
FD-081 MIMO an LBBPc and uses four or more RX antennas. (2)
409 Based FDD cell that is established on an LBBPc and uses
TDLEO on TM9 extended cyclic prefix (CP) in the uplink. (3) TDD
FD-121 DL cell established on an LBBPc. If this parameter does
615 Flexible not take effect on a cell but SRS resources are
TDLOF 3D- available in the cell, SRS resources can be configured
D-00104 Beamfor for UEs in the cell. This parameter applies only to
9 ming LTE FDD and LTE TDD.
Single GUI Value Range: BOOLEAN_FALSE(False),
Streami BOOLEAN_TRUE(True)
ng Unit: None
Beamfor
ming Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
RACHC PrachFr MOD LOFD-0 RACH Meaning: Indicates the policy of determining the
fg eqOffset RACHC 02015/ Optimiz PRACH frequency-domain offset. If this parameter is
Strategy FG TDLOF ation set to AUTOMATIC(AUTOMATIC) or
LST D-00201 Random FULLY_AUTOMATIC(FULLY_AUTOMATIC), the
RACHC 5 Access eNodeB determines the PRACH frequency-domain
FG TDLBF offset. If this parameter is set to
D-00201 MANUAL(MANUAL), the PRACH frequency-
0 domain offset is specified by the PrachFreqOffset
parameter. In an LTE FDD cell, the eNodeB
determines the PRACH frequency-domain offset only
if this parameter is set to
FULLY_AUTOMATIC(FULLY_AUTOMATIC)
when the PucchSwitch option of the
PucchAlgoSwitch parameter is deselected. In an LTE
TDD cell, the parameter value MANUAL(MANUAL)
does not take effect when preamble format 4 is used.
This parameter applies only to LTE FDD and LTE
TDD.
GUI Value Range: AUTOMATIC(AUTOMATIC),
MANUAL(MANUAL),
FULLY_AUTOMATIC(FULLY_AUTOMATIC)
Unit: None
Actual Value Range: AUTOMATIC, MANUAL,
FULLY_AUTOMATIC
Default Value: AUTOMATIC(AUTOMATIC)
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
3 Unit: None
CELLR
ACTHD Actual Value Range: 0~65535
Default Value: 65535
EpfEnhancedSwitch(EpfEnhancedSwitch),
AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS-
witch), VoipTbsBasedMcsSelS-
witch(VoipTbsBasedMcsSelSwitch),
PagingInterfRandSwitch(PagingInterfRandSwitch),
DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS-
witch), SubframeSchDiffSwitch(SubframeSchDiffS-
witch), TailPackagePriSchS-
witch(TailPackagePriSchSwitch),
UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch),
FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor-
DopplerSwitch),
SIB1InterfRandSwitch(SIB1InterfRandSwitch),
EnhExtQCISpsSchSwitch(EnhExtQCISpsSchSwitch),
DlVoipBundlingSwitch(DlVoipBundlingSwitch),
DlPacketLenAwareSchSw(DlPacketLenAwar-
eSchSw), RLCArqFeedbackEnhanced-
Switch(RLCArqFeedbackEnhancedSwitch),
PaReconfigOptSwitch(PaReconfigOptSwitch),
RankRapidRptSwitch(RankRapidRptSwitch),
DlRLCStateReportSchDe-
laySw(DlRLCStateReportSchDelaySw),
SmallPktMcsSelectAlgoSw(SmallPktMcsSelectAl-
goSw), SRB0SplitSchSw(SRB0SplitSchSw),
BfUserPairPriorSwitch(BfUserPairPriorSwitch),
HarqAllocOptSwitch(HarqAllocOptSwitch),
Pusch32Switch(Pusch32Switch),
DlPreciseAmbrCtrlSwitch(DlPreciseAmbrCtrlSwitch)
Unit: None
Actual Value Range: FreqSelSwitch, SpsSchSwitch,
MBSFNShutDownSwitch, NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,
MbrDlSchSwitch, UeAmbrDlSchSwitch,
EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch, PagingInterfRand-
Switch, DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch, TailPackagePriSchSwitch,
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-
plerSwitch, SIB1InterfRandSwitch,
EnhExtQCISpsSchSwitch, DlVoipBundlingSwitch,
DlPacketLenAwareSchSw, RLCArqFeedbackEnhan-
cedSwitch, PaReconfigOptSwitch,
RankRapidRptSwitch, DlRLCStateReportSchDe-
laySw, SmallPktMcsSelectAlgoSw, SRB0SplitSchSw,
BfUserPairPriorSwitch, HarqAllocOptSwitch,
Pusch32Switch, DlPreciseAmbrCtrlSwitch
Default Value: FreqSelSwitch:Off, SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off, NonGbrBundlingS-
CellDlsc FDUEE MOD LBFD-0 Enhance Meaning: Indicates the aperiodic channel quality
hAlgo nhAper CELLD 60103 d DL indicator (CQI) reporting period of a UE adopting
CQITrig LSCHA LBFD-0 Frequen frequency diversity (FD) scheduling. This parameter
Period LGO 0101502 cy can be set to 5ms, 10ms, 20ms, 40ms, 80ms, 160ms,
LST Selectiv and inf. The parameter value inf indicates that the
CELLD e aperiodic CQI reporting is not triggered. This
LSCHA Scheduli parameter applies only to LTE FDD.
LGO ng GUI Value Range: 5ms, 10ms, 20ms, 40ms, 80ms,
Dynami 160ms, inf
c Unit: None
Scheduli
ng Actual Value Range: 5ms, 10ms, 20ms, 40ms, 80ms,
160ms, inf
Default Value: 5ms
CellPdc PdcchPo MOD LBFD-0 Physical Meaning: Indicates whether to enable enhanced
chAlgo werEnha CELLP 02003/ Channel PDCCH power control. If this switch is turned on, the
ncedSwi DCCHA TDLBF Manage eNodeB selects appropriate PDCCH transmit power
tch LGO D-00200 ment based on channel quality to increase PDCCH capacity.
LST 3 ePDCC This parameter applies only to LTE FDD and LTE
CELLP LAOFD H TDD massive MIMO cells for which the policy of
DCCHA -110203 selecting the aggregation level based on capacity is
PDCCH adopted.
LGO LBFD-0 Utilizati
70107 on GUI Value Range: OFF(Off), ON(On)
Improve Unit: None
ment Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDlsc RBDam MOD LEOFD- Flexible Meaning: Indicates the IBLER threshold for
hAlgo ageNear CELLD 111302 Bandwi determining cell-center UEs when certain RBs are
PointIbl LSCHA LOFD-0 dth unavailable, or the IBLER threshold for 4R UEs to
erTh LGO 03029/ based on perform rank 3 or 4 measurement when CA and
LST TDLOF Overlap MIMO cooperation, the algorithm of 4x4 MIMO in
CELLD D-00107 Carriers the overlapping areas of an SFN cell, or the algorithm
LSCHA 5 SFN of adaptively entering TM4 and TM9 modes is used.
LGO This parameter applies only to LTE FDD and LTE
LOFD-0 Adaptiv
TDD.
70205/ e SFN/
TDLOF SDMA GUI Value Range: 0~1000
D-00200 Inter- Unit: None
8 eNodeB Actual Value Range: 0~1, step: 0.001
LOFD-0 SFN
Default Value: 20
81208 Based
on
LOFD-0
Coordin
81209
ated
LAOFD eNodeB
-001001 Inter-
01 eNodeB
LAOFD Adaptiv
-001002 e SFN/
LAOFD SDMA
-070201 Based
on
LAOFD
Coordin
-080202
ated
LAOFD eNodeB
-080207 Carrier
LAOFD Aggrega
-080208 tion for
LOFD-0 Downlin
01060 k 2CC
LOFD-0 Carrier
01051 Aggrega
tion for
Downlin
k 2CC
in
40MHz
Flexible
CA
from
Multiple
Carriers
Carrier
Aggrega
tion for
Uplink
2CC
Carrier
Aggrega
tion for
Downlin
k 3CC
in
40MHz
Carrier
Aggrega
tion for
Downlin
k 3CC
in
60MHz
DL 4x4
MIMO
Compac
t
BandWi
dth
EmtcAckModeSw(EmtcAckModeSw),
PucchMeasOptSwitch(PucchMeasOptSwitch)
Unit: None
Actual Value Range: PucchSwitch,
PucchFlexCfgSwitch, Dl2CCAckResShareSw,
SCCAckResourceCfgSw, EmtcAckModeSw,
PucchMeasOptSwitch
Default Value: PucchSwitch:On,
PucchFlexCfgSwitch:Off,
Dl2CCAckResShareSw:On,
SCCAckResourceCfgSw:Off, EmtcAckModeSw:Off,
PucchMeasOptSwitch:Off
CellCqi CqiPerio MOD LBFD-0 Basic Meaning: Indicates whether to enable CQI reporting
Adaptiv dAdapti CELLC 02025/ Scheduli period adaptation. If this parameter is set to ON(On),
eCfg ve QIADA TDLBF ng the CQI reporting period adaptively changes based on
PTIVEC D-00202 Dynami the air interface load of the cell. If this parameter is set
FG 5 c to OFF(Off), the CQI reporting period is specified by
LST LBFD-0 Scheduli the UserCqiPeriod parameter. This parameter applies
CELLC 0101502 ng only to LTE FDD and LTE TDD.
QIADA / Single GUI Value Range: OFF(Off), ON(On)
PTIVEC TDLBF Streami Unit: None
FG D-00101 ng
502 Actual Value Range: OFF, ON
Beamfor
TDLOF ming Default Value: ON(On)
D-00104 Dual
9 Streami
TDLOF ng
D-00106 Beamfor
1 ming
TDLBF Physical
D-00200 Channel
3 Manage
TDLBF ment
D-00203 Aperiodi
1 c CQI
LBFD-0 Reportin
60101 g
Optimiz
ation of
CQI
Reportin
g
CellCqi UserCqi MOD LBFD-0 Basic Meaning: Indicates the fixed CQI reporting period.
Adaptiv Period CELLC 02025/ Scheduli This parameter takes effect only if the
eCfg QIADA TDLBF ng CqiPeriodAdaptive parameter is set to OFF(Off). If
PTIVEC D-00202 Dynami the UserCqiPeriod parameter is set to ms2(2ms), the
FG 5 c period is automatically changed to 5ms for the TDD
LST LBFD-0 Scheduli cell. This parameter applies only to LTE FDD and
CELLC 0101502 ng LTE TDD.
QIADA / Physical GUI Value Range: ms2(2ms), ms5(5ms), ms10(10ms),
PTIVEC TDLBF Channel ms20(20ms), ms40(40ms), ms80(80ms),
FG D-00101 Manage ms160(160ms)
502 ment Unit: ms
TDLBF Actual Value Range: ms2, ms5, ms10, ms20, ms40,
D-00200 ms80, ms160
3
Default Value: ms40(40ms)
PUCCH SriPerio MOD LBFD-0 Physical Meaning: Indicates whether to enable scheduling
Cfg dAdapti PUCCH 02003/ Channel request indicator (SRI) period adaptation. If this
ve CFG TDLBF Manage parameter is set to QCIADAPTIVE(QCIADAPTIVE),
LST D-00200 ment the SRI period adaptively changes based on the cell
PUCCH 3 load and bearers with different QCIs. If this parameter
CFG is set to NOQCIADAPTIVE(NOQCIADAPTIVE),
the SRI period adaptively changes based only on the
cell load. If this parameter is set to OFF(OFF), the
SRI period is dependent on the value of the
FixedSriPeriod parameter in the PUCCHCfg MO: If
the FixedSriPeriod parameter value is
Disable(Disable), the SRI period is set to the value of
the SriPeriod parameter in the CellQciPara MO; if the
FixedSriPeriod parameter value is not
Disable(Disable), the SRI period is set to the value of
the FixedSriPeriod parameter. This parameter applies
only to LTE FDD and LTE TDD.
GUI Value Range: OFF(OFF),
QCIADAPTIVE(QCIADAPTIVE),
NOQCIADAPTIVE(NOQCIADAPTIVE)
Unit: None
Actual Value Range: OFF, QCIADAPTIVE,
NOQCIADAPTIVE
Default Value: QCIADAPTIVE(QCIADAPTIVE)
PUCCH DeltaShi MOD LBFD-0 Physical Meaning: Indicates the interval between cyclic shifts
Cfg ft PUCCH 02003/ Channel used for the PUCCH. The interval between cyclic
CFG TDLBF Manage shifts used for the PUCCH can be acquired based on
LST D-00200 ment the average delay spread in the cell, where the average
PUCCH 3 ePDCC delay spread is acquired based on the networking
CFG LAOFD H environment. The parameter value
-110203 DS1_DELTA_SHIFT is not supported by the LBBPc.
ePDCC If a cell is established on an LBBPc but this parameter
TDLAO H is set to DS1_DELTA_SHIFT, the value of this
FD-1114 Breathin parameter is automatically changed to
01 g Pilot DS2_DELTA_SHIFT when this parameter takes
LEOFD- effect. For details, see 3GPP TS 36.211. This
111306 parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: DS1_DELTA_SHIFT(ds1),
DS2_DELTA_SHIFT(ds2),
DS3_DELTA_SHIFT(ds3)
Unit: None
Actual Value Range: DS1_DELTA_SHIFT,
DS2_DELTA_SHIFT, DS3_DELTA_SHIFT
Default Value: DS1_DELTA_SHIFT(ds1)
PUCCH CqiRbN MOD LBFD-0 Physical Meaning: Indicates the number of RBs allocated to the
Cfg um PUCCH 02003/ Channel CQI at the RRC layer of cell. This parameter applies
CFG TDLBF Manage only to LTE FDD and LTE TDD.
LST D-00200 ment GUI Value Range: 0~20
PUCCH 3 Breathin Unit: None
CFG LEOFD- g Pilot
111306 Actual Value Range: 0~20
Default Value: 1
PUCCH NaSriCh MOD LBFD-0 Physical Meaning: Indicates the number of resource indexes
Cfg Num PUCCH 02003/ Channel allocated to SRI and semi-persistent ACK at the RRC
CFG TDLBF Manage layer for the cell. If this parameter is set to 0, UEs
LST D-00200 ment may fail to access the cell. This parameter applies
PUCCH 3 Breathin only to LTE FDD and LTE TDD.
CFG LEOFD- g Pilot GUI Value Range: 0~1000
111306 Unit: None
Actual Value Range: 0~1000
Default Value: 6
PUCCH Format3 MOD LBFD-0 Physical Meaning: Indicates the maximum number of RBs that
Cfg RbNum PUCCH 02003/ Channel can be used by PUCCH resources in Format 3. This
CFG TDLBF Manage parameter takes effect only when the
LST D-00200 ment SCCAckResourceCfgSw option of the
PUCCH 3 PucchAlgoSwitch parameter is selected. This
CFG parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: 0~2
Unit: None
Actual Value Range: 0~2
Default Value: 2
PUCCH Max2C MOD LBFD-0 Physical Meaning: Indicates the maximum number of code
Cfg CAckCh PUCCH 02003/ Channel channels that can be used by SCC ACKs in 2CC CA
Num CFG TDLBF Manage scenarios. This parameter takes effect only when
LST D-00200 ment options Dl2CCAckResShareSw and
PUCCH 3 SCCAckResourceCfgSw of the PucchAlgoSwitch
CFG parameter are selected. This parameter applies only to
LTE FDD and LTE TDD.
GUI Value Range: MAX_CH_NUM8(Ch8),
MAX_CH_NUM16(Ch16),
MAX_CH_NUM24(Ch24),
MAX_CH_NUM32(Ch32)
Unit: None
Actual Value Range: MAX_CH_NUM8,
MAX_CH_NUM16, MAX_CH_NUM24,
MAX_CH_NUM32
Default Value: MAX_CH_NUM32(Ch32)
CellQci SriPerio ADD LBFD-0 Physical Meaning: Indicates the interval at which scheduling
Para d CELLQ 02003/ Channel request indicators are sent. This parameter applies
CIPAR TDLBF Manage only to LTE FDD and LTE TDD.
A D-00200 ment GUI Value Range: ms5(SRI 5ms), ms10(SRI 10ms),
MOD 3 ms20(SRI 20ms), ms40(SRI 40ms), ms80(SRI 80ms)
CELLQ Unit: None
CIPAR
A Actual Value Range: ms5, ms10, ms20, ms40, ms80
6 Counters
7 Glossary
8 Reference Documents