Beruflich Dokumente
Kultur Dokumente
Issue 06
Date 2015-12-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: support@huawei.com
Contents
2 Overview....................................................................................................................................... 18
2.1 Introduction.................................................................................................................................................................. 18
2.2 Benefits......................................................................................................................................................................... 19
2.3 Architecture.................................................................................................................................................................. 19
3 Technical Description.................................................................................................................21
3.1 Function Overview....................................................................................................................................................... 21
3.1.1 Related Concepts....................................................................................................................................................... 21
3.1.2 Usage Scenarios.........................................................................................................................................................22
3.1.2.1 Typical Scenarios....................................................................................................................................................22
3.1.2.2 Atypical Scenarios.................................................................................................................................................. 25
3.1.3 CA Features............................................................................................................................................................... 25
3.1.3.1 LAOFD-001001 LTE-A Introduction.....................................................................................................................27
3.1.3.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.................................................................... 28
3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers........................................................................................... 29
3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU........................................................................... 29
3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul........................................................................... 30
3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]...............................................................................32
3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz.................................................................... 32
3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz.................................................................... 33
3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]....................................................................... 34
3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]...................................................................35
3.1.4 Band Combinations................................................................................................................................................... 36
3.2 Carrier Management..................................................................................................................................................... 37
3.2.1 Overview................................................................................................................................................................... 37
3.2.2 PCC Anchoring (at Initial Access)............................................................................................................................ 40
3.2.2.1 CA-Group-based PCC Anchoring.......................................................................................................................... 40
3.2.2.2 Frequency-based or Adaptive PCC Anchoring...................................................................................................... 42
4 Related Features...........................................................................................................................84
4.1 Features Related to LAOFD-001001 LTE-A Introduction...........................................................................................84
4.2 Features Related to LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.......................................... 86
4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers..................................................................86
4.4 Features Related to LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU................................................. 87
4.5 Features Related to LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul..................................................87
4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]..................................................... 88
4.7 Features Related to LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz.......................................... 89
4.8 Features Related to LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz.......................................... 89
4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]............................................. 89
4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]......................................... 90
5 Network Impact........................................................................................................................... 94
5.1 LAOFD-001001 LTE-A Introduction...........................................................................................................................94
5.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.......................................................................... 95
5.3 LAOFD-070201 Flexible CA from Multiple Carriers................................................................................................. 95
5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU................................................................................. 95
5.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul................................................................................. 96
5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial].....................................................................................97
5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz.......................................................................... 97
5.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz.......................................................................... 97
5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]............................................................................. 97
5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial].........................................................................97
14 Parameters................................................................................................................................. 194
15 Counters.................................................................................................................................... 324
16 Glossary..................................................................................................................................... 547
17 Reference Documents............................................................................................................. 548
1.1 Scope
This document describes carrier aggregation (CA), including its technical principles, related
features, network impact, and engineering guidelines. This document covers the following
features:
l LAOFD-001001 LTE-A Introduction
LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100103 Support of UE Category 6
LAOFD-00100104 Support of UE Category 7
LAOFD-00100105 Support of UE Category 9
LAOFD-00100106 Support of UE Category 10
l LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
l LAOFD-070201 Flexible CA from Multiple Carriers
l LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
l LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
l LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
l LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
A trial feature is a feature that customers can use without paying for the license fee in the
current version. In a later version, a trial feature may be deleted or become an optional
feature. The license fee is required for optional features.
Before using a trial feature, customers need to sign a memorandum of understanding (MoU)
with Huawei.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
Micro BTS3202E
eRAN8.1 06 (2015-12-30)
This issue includes the following changes.
eRAN8.1 05 (2015-11-03)
This issue includes the following changes.
eRAN8.1 04 (2015-08-31)
This issue includes the following changes.
eRAN8.1 03 (2015-06-30)
This issue includes the following changes.
eRAN8.1 02 (2015-04-30)
This issue includes the following changes.
eRAN8.1 01 (2015-03-23)
This issue includes the following changes.
2 Overview
2.1 Introduction
3rd Generation Partnership Project (3GPP) requires LTE-Advanced networks to provide a
downlink peak data rate of 1 Gbit/s. However, radio spectrum resources are so scarce that in
most cases an operator owns only non-adjacent chunks of the spectrum. Due to the limited
bandwidth of a single chunk of the spectrum, the 1 Gbit/s data rate requirement is hard to
meet.
To deal with this situation, 3GPP specifications Release 10 introduced carrier aggregation
(CA) to LTE-Advanced networks, allowing aggregation of contiguous or non-contiguous
carriers. These carriers are called component carriers (CCs). CA achieves wider bandwidths
(a maximum of 100 MHz). Figure 2-1 shows CA for UEs.
During CA, upper-layer data streams are mapped to individual component carriers (CCs) at
the Media Access Control (MAC) layer in LTE-Advanced networks. An eNodeB constructs
one (two or more in the case of spatial multiplexing) transport block (TB) in each
transmission time interval (TTI) for each CC. Each CC uses its own hybrid automatic repeat
request (HARQ) entities and link adaptation mechanism. Therefore, the LTE-Advanced
system can inherit single-carrier-based physical layer designs from the LTE system.
2.2 Benefits
CA achieves wider bandwidth and allows a CA-capable UE (referred to as CA UE in this
document) to use idle resource blocks (RBs) on non-contiguous CCs. With CA enabled, a
single UE can reach higher uplink and downlink peak data rates. Figure 2-2 shows the
benefits of CA.
2.3 Architecture
Functional Architecture
The functional architecture for CA includes primary component carrier (PCC) anchoring,
SCell configuration, and transitions between SCell states. For details, see 3.2 Carrier
Management. This architecture also includes special implementation of other features under
CA, as described in 3.3 Other Key Techniques Under CA.
Huawei CA operates in accordance with the following constraints, which are stipulated in
3GPP TS 36.300 of Release 10:
l In the uplink or downlink, a CA UE supports the aggregation of up to five CCs, each
with a maximum bandwidth of 20 MHz. Currently, Huawei eNodeBs support the
aggregation of no more than three FDD CCs or a combination of four FDD and TDD
CCs, each with a maximum bandwidth of 20 MHz.
l CA UEs support asymmetric CA. A UE may use different numbers of CCs in the uplink
and downlink. However, the number of CCs in the downlink must always be greater than
or equal to the number of CCs in the uplink. In addition, the uplink CCs must be
included in the set of downlink CCs. Currently, Huawei eNodeBs support the
aggregation of two CCs in the uplink and the aggregation of two CCs, three CCs, or a
combination of four FDD and TDD CCs in the downlink.
l Each CC uses the same frame structure as 3GPP Release 8 carriers to support backward
compatibility.
l 3GPP Release 8 or 9 UEs are allowed to transmit and receive data on Release 10 CCs.
l A single radio bearer has only one Packet Data Convergence Protocol (PDCP) entity and
one Radio Link Control (RLC) entity. In addition, the number of CCs at the physical
layer is invisible to the RLC layer.
l User-plane data scheduling at the MAC layer is performed separately for individual CCs.
l Each CC has an independent set of transport channels and separate HARQ entities and
retransmission processes.
Figure 2-3 shows the uplink and downlink air-interface protocol stack with CA enabled.
Figure 2-3 Uplink and downlink air-interface protocol stack with CA enabled
3 Technical Description
PCell
A primary serving cell (PCell) is the cell on which a CA UE camps. In the PCell, the CA UE
works in the same way as it does in a 3GPP Release 8 or Release 9 cell. The physical uplink
control channel (PUCCH) of the UE exists only in the PCell.
For more details, see 3.3.1 Connection Management Under CA.
SCell
A secondary serving cell (SCell) is a cell that works at a different frequency from the PCell.
The eNodeB configures an SCell for a CA UE through an RRC Connection Reconfiguration
message. An SCell provides the CA UE with more radio resources. The CA UE can have only
downlink SCells or both downlink and uplink SCells.
CC
Component carriers (CCs) are the carriers that are aggregated for a CA UE.
PCC
The primary component carrier (PCC) is the carrier of the PCell.
SCC
A secondary component carrier (SCC) is the carrier of an SCell.
PCC Anchoring
During PCC anchoring, the eNodeB selects a high-priority cell as the PCell for the UE.
Related Events
l Event A2
Event A2 indicates that the signal quality of the serving cell becomes lower than a
specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A3
Event A3 indicates that the signal quality of the PCell's neighboring cell becomes higher
than that of the PCell. For details, see Intra-RAT Mobility Management in Connected
Mode.
l Event A4
Event A4 indicates that the signal quality of a neighboring cell becomes higher than a
specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A5
Event A5 indicates that the signal quality of the PCell becomes lower than a specific
threshold and the signal quality of a neighboring cell becomes higher than another
specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A6
Event A6 indicates that the signal quality of an SCell's intra-frequency neighboring cell
becomes higher than that of the SCell. If the eNodeB receives an event A6 report, it
changes the SCell while keeping the PCell unchanged.
The entering condition for event A6 is as follows: Mn + Ocn - Hys > Ms + Ocs + Off.
The following explains the variables involved:
Mn is the RSRP measurement result of a neighboring cell.
Ocn is the cell-specific offset for an intra-frequency neighboring cell. The offset is
specified by the EutranIntraFreqNCell.CellIndividualOffset parameter.
Hys is the hysteresis for event A6. The value of this variable is always 0.
Ms is the RSRP measurement result of the serving cell.
Ocs is the cell-specific offset for the serving cell. The offset is specified by the
Cell.CellSpecificOffset parameter.
Off is the offset for event A6. The offset is specified by the
CaMgtCfg.CarrAggrA6Offset parameter.
For details about this event, see section 5.5.4.6a "Event A6 (Neighbour becomes offset
better than SCell)" in 3GPP TS 36.331 V10.12.0.
NOTE
If the CellMcPara.TimetoTrigger parameter is set to a value greater than the value (3s) of the timer for
gap-assisted measurement, measurement results cannot be reported.
Table 3-1 Typical scenarios for using CA and Huawei eNodeBs' support
The following figures show the typical scenarios. In the figures, F1 and F2 denote two carrier
frequencies.
Figure 3-3 Intra-eNodeB carriers (one for macro coverage; another for edge coverage)
Figure 3-4 Intra-eNodeB carriers (one provided by the site; another provided by RRHs)
Figure 3-5 Intra-eNodeB carriers (one provided only by the site; another provided by the site
and a repeater)
3.1.3 CA Features
CA enables a UE to simultaneously access more than one carrier and transmit uplink (UL)
data and receive downlink (DL) data over all carriers, greatly increasing the data rate of the
UE.
Table 3-2 provides an overview of the CA features.
The time alignment error between two intra-band contiguous or non-contiguous CCs
must be less than 130 ns or 260 ns, respectively.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band
Combinations to a maximum of 20 MHz for a CA UE.
l LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
Inter-band CA aggregates two carriers from different frequency bands for downlink data
transmission to one CA UE, as shown in Figure 3-7.
The time alignment error between two inter-band CCs must be less than 260 ns.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band
Combinations to a maximum of 20 MHz for a CA UE.
l LAOFD-00100103 Support of UE Category 6
This sub-feature enables CA for UEs of category 6, which is defined in 3GPP TS 36.306
V10.0.0.
With this sub-feature, a UE of category 6 can reach a peak data rate of 300 Mbit/s in the
downlink and 50 Mbit/s in the uplink.
l LAOFD-00100104 Support of UE Category 7
This sub-feature enables CA for UEs of category 7, which is defined in 3GPP TS 36.306
V12.0.0.
With this sub-feature, a UE of category 7 can reach a peak data rate of 300 Mbit/s in the
downlink and 100 Mbit/s in the uplink.
l LAOFD-00100105 Support of UE Category 9
This sub-feature enables CA for UEs of category 9, which is defined in 3GPP TS 36.306
V12.0.0.
With this sub-feature, a UE of category 9 can reach a peak data rate of 450 Mbit/s in the
downlink and 50 Mbit/s in the uplink.
l LAOFD-00100106 Support of UE Category 10
This sub-feature enables CA for UEs of category 10, which is defined in 3GPP TS
36.306 V12.0.0.
With this sub-feature, a UE of category 10 can reach a peak data rate of 450 Mbit/s in the
downlink and 100 Mbit/s in the uplink.
This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to
a maximum of 40 MHz for a CA UE.
During initial access, during an incoming handover, or during an RRC connection re-
establishment, a CA UE reports its CA capability to the eNodeB after setting up an RRC
connection with the PCell. The eNodeB selects a suitable carrier as an SCC for the CA UE
based on the carrier deployment and the carrier management principles described in 3.2
Carrier Management.
From FDD carriers, an eNodeB can currently select either two or three carriers for CA. From
TDD carriers, an eNodeB can currently select two, three, or four carriers for FDD+TDD CA.
This feature maximizes carrier utilization. It uses mobility load balancing (MLB) to achieve
efficient multi-carrier management.
NOTE
Figure 3-10 shows inter-eNodeB CA based on coordinated BBUs. For details about
centralized multi-BBU interconnection, see USU3900-based multi-BBU interconnection. For
details about distributed multi-BBU interconnection, see USU3910-based multi-BBU
interconnection.
On live networks with relaxed backhaul requirements, if UEs and the EPC comply with 3GPP
Release 10, inter-eNodeB CA can be deployed without requiring network reconstruction.
During CA between macro cells, the cells exchange signaling messages and data through eX2
interfaces between the main control boards (LMPT or UMPT) of eNodeBs. During CA
between macro and micro cells, the cells exchange signaling messages and data through eX2
interfaces between the main control board (LMPT or UMPT) of the macro eNodeB and the
transport module of the micro eNodeB. When one-way delay and round trip time between
eNodeBs are not greater than 4 ms and 8 ms, respectively, downlink 2CC aggregation
increases the downlink average data rate of a CA UE by 40%80% and peak data rate by
more than 80%, compared with the data rates of a non-CA UE. The data rate reaches the peak
value when the CA UE is the only UE in the cell and is located in the cell center.
NOTE
l After CA is enabled, the transmission delay for CA-group-based configuration mode can be queried
by running the DSP CAGROUPCELL command, and that for frequency-based or adaptive
configuration mode can be queried by running the DSP PCCSCELLLIST command. Frequency-
based or adaptive configuration mode is recommended for inter-eNodeB CA based on relaxed
backhaul (also referred to as relaxed-backhaul-based inter-eNodeB CA in this document for clarity).
l For details about eX2 interfaces between eNodeBs, see eX2 Self-Management.
1. During initial access, during an incoming handover, or during an RRC connection re-
establishment, a CA UE reports its downlink CA capability to the eNodeB after setting
up an RRC connection with the PCell.
2. The eNodeB checks the related switch settings, the status of the eX2 interface to a peer
eNodeB, and inter-eNodeB transmission delay. If all the conditions meet certain
requirements, the local eNodeB selects a carrier of the peer eNodeB as an SCC for the
CA UE. The switch setting requirements depend on the types of eNodeBs:
If the pair of eNodeBs are both macro eNodeBs, RelaxedBackhaulCaSwitch under
the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs.
If the eNodeBs are a pair of macro and micro eNodeBs,
RelaxedBackhaulCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch
parameter must be on for both eNodeBs. In addition, HetNetCaSwitch under this
parameter must also be on for the micro eNodeB.
3. After activating the SCell, the eNodeB that serves the PCell will divert RLC traffic of the
CA UE from the PCell to the SCell. When inter-eNodeB transmission quality
deteriorates (for example, the transmission delay does not meet requirements or
transmission is interrupted), the eNodeB removes the SCells to exit inter-eNodeB CA.
The eNodeB may configure SCells again at UE access, an incoming handover, or an
RRC connection re-establishment after transmission quality recovers.
This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to
a maximum of 40 MHz for a CA UE in the uplink.
This feature is dependent on the uplink CA capabilities of UEs and the setting of
CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter. It requires
LAOFD-001001 LTE-A Introduction to be activated. Therefore, after LAOFD-080202 is
enabled, two carriers can be aggregated for both uplink and downlink transmission.
LAOFD-080202 works in typical scenarios and multi-BBU interconnection scenarios but
does not work between eNodeBs in relaxed backhaul scenarios.
This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to
a maximum of 40 MHz for a CA UE in the downlink.
This feature is dependent on the downlink CA capabilities of UEs and the setting of
CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of acknowledgments (ACKs) and negative ACKs
(NACKs) for three carriers, PUCCH format 3 is introduced. For details about PUCCH format
3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not
work between eNodeBs in relaxed backhaul scenarios.
This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to
a maximum of 60 MHz for a CA UE in the downlink.
This feature is dependent on the downlink CA capabilities of UEs and the setting of
CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of ACKs and NACKs for three carriers, PUCCH
format 3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH
format information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not
work between eNodeBs in relaxed backhaul scenarios.
3GPP Release 10 introduces TM9 into LTE. TM9 supports single-user MIMO with a maximum of
eight layers and multi-user MIMO with a maximum of four data blocks (at most two layers for
each UE). For details about TM9 and other MIMO-related concepts and principles, see MIMO.
This feature supports 2CC and 3CC aggregation in typical and multi-BBU interconnection
scenarios and supports only 2CC aggregation in relaxed-backhaul-based inter-eNodeB CA.
In this feature, only FDD carriers can be PCCs of CA UEs. TDD cells must use uplink-
downlink configuration 1 or 2. There is no subframe configuration requirement for FDD cells.
If a frame offset is configured for a TDD cell, the same frame offset must be specified for the
FDD cells involved in CA.
NOTE
For details about the principles and engineering guidelines for subframe configuration, see Subframe
Configuration for LTE TDD.
This feature is dependent on the downlink CA capabilities of UEs and the setting of
InterFddTddCaSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
This feature works in typical scenarios and between eNodeBs in relaxed backhaul scenarios.
In typical scenarios, downlink 2CC, 3CC, or 4CC aggregation works. However, in relaxed
backhaul scenarios, only downlink 2CC aggregation between macro cells works.
NOTE
3.2.1 Overview
Features Involved
Carrier management involves the following features:
l LAOFD-001001 LTE-A Introduction
l LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
l LAOFD-070201 Flexible CA from Multiple Carriers
l LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
l LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
l LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
l LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
Procedures Involved
Carrier management involves the following procedures for CA UEs:
l PCC anchoring
PCC anchoring, during which the PCell is selected, occurs when CA UEs initially access
networks or when their RRC connections are released. It does not occur during incoming
handovers or RRC connection re-establishments. During PCC anchoring, an eNodeB
selects a PCell for a CA UE based on PCell or PCC priorities. For details about PCC
anchoring at initial access, see 3.2.2 PCC Anchoring (at Initial Access). For details
about PCC anchoring at an RRC connection release, see 3.2.8 PCC Anchoring (at RRC
Connection Releases).
NOTE
NOTE
A gap-assisted measurement timer is used in PCC anchoring and SCell configuration for carrier
management. The timer has a fixed length of 3s.
Configuration Mode
There are three configuration modes for carrier management: CA-group-based, frequency-
based, and adaptive. The three modes are enabled as follows:
l CA-group-based configuration is enabled when FreqCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter is off. This mode requires that cells be
configured into a CA group, as shown in Figure 3-18. Only the cells in the group can be
aggregated.
Operators can select a configuration mode after considering the following differences between
these modes:
NOTE
In FDD+TDD CA, only an FDD carrier can serve as the PCC for a CA UE. To prioritize certain FDD
frequencies as PCCs, set high PCell or PCC priorities for cells on the frequencies or for the frequencies,
respectively.
When a CA UE initially accesses a network, the eNodeB skips PCC anchoring if a bearer for
an emergency call or with a QoS class identifier (QCI) of 1 has been established. The purpose
is to prevent gap-assisted measurements from affecting voice quality. (Bearers with a QCI of
1 are used to carry voice over LTE [VoLTE] services.)
NOTE
l Frequencies in band 29 work only for the downlink and therefore cannot work as PCCs.
l After PCC anchoring is enabled, the number of inter-frequency handovers increases.
1. The eNodeB checks whether cell 1 has the highest PCell priority among the cells in the
CA group.
If cell 1 has the highest PCell priority, the eNodeB retains cell 1 as the PCell for the
UE and does not perform further PCC anchoring.
If cell 1 does not have the highest PCell priority, the eNodeB treats the cells that
have higher PCell priorities than cell 1 in the CA group as candidate PCells. The
eNodeB then arranges the candidates in descending order of PCell priority and goes
to the next step.
2. If the UE is capable of working at the carrier frequency of the top-priority candidate
PCell (for example, cell 2), the eNodeB delivers the A4 measurement configuration,
instructing the UE to measure cell 2. The A4 measurement configuration varies
depending on the IntraRatHoComm.InterFreqHoA4TrigQuan parameter setting.
If the parameter value is RSRP, the A4 measurement configuration includes only a
reference signal received power (RSRP) configuration. The RSRP threshold for CA
is specified by the CaGroupCell.PCellA4RsrpThd parameter.
If the parameter value is RSRQ, the A4 measurement configuration includes only a
reference signal received quality (RSRQ) configuration. The RSRQ threshold for
CA is specified by the CaGroupCell.PCellA4RsrqThd parameter.
If the parameter value is BOTH, the A4 measurement configuration includes both
RSRP and RSRQ configurations. The UE sends an A4 measurement report to the
eNodeB when either the measured RSRP or RSRQ exceeds the specified threshold
for CA.
NOTE
If the UE is incapable of working at the carrier frequency of cell 2, the eNodeB skips to the next-
priority candidate PCell.
3. After receiving an A4 measurement report that contains cell 2, the eNodeB hands over
the UE to cell 2.
If the eNodeB does not receive such a report or if the handover to cell 2 fails, the eNodeB
deletes the A4 measurement configuration and evaluates the next-priority candidate PCell in
the same way. If no candidate PCell meets the conditions for triggering event A4, the eNodeB
terminates the PCC anchoring procedure and cell 1 eventually serves the UE as its PCell.
NOTE
l If multiple candidate PCells have the same PCell priority, the eNodeB instructs the UE to measure
all the carrier frequencies of these cells. The eNodeB then processes only the first A4 measurement
report from the UE and ignores the subsequent reports.
l After the CA UE is handed over to a new PCell, CA does not work if CA configurations are absent
or incorrect in the target eNodeB or if a data link fails to be set up between the new PCell and an
SCell.
1. The eNodeB checks whether carrier 1 has the highest PCC priority (specified by the
PccFreqCfg.PreferredPccPriority parameter) among the carriers identified by
PccDlEarfcn in PccFreqCfg managed objects (MOs).
If carrier 1 has the highest PCC priority, the eNodeB retains the cell on carrier 1 as
the PCell for the UE and does not perform further PCC anchoring.
If carrier 1 does not have the highest PCC priority, the eNodeB treats higher-priority
carriers as candidate PCCs for the UE, arranges them in descending order of PCC
priority, and goes to the next step.
2. If the UE is capable of working at the top-priority candidate PCC (for example, carrier
2), the eNodeB delivers the A4 measurement configuration, instructing the UE to
measure carrier 2. The A4 measurement configuration varies depending on the
IntraRatHoComm.InterFreqHoA4TrigQuan parameter setting.
If the parameter value is RSRP, the A4 measurement configuration includes only
an RSRP configuration. The RSRP threshold for CA is specified by the
PccFreqCfg.PccA4RsrpThd parameter.
If the parameter value is RSRQ, the A4 measurement configuration includes only
an RSRQ configuration. The RSRQ threshold for CA is specified by the
PccFreqCfg.PccA4RsrqThd parameter.
If the parameter value is BOTH, the A4 measurement configuration includes both
RSRP and RSRQ configurations. The UE sends an A4 measurement report to the
eNodeB when either the measured RSRP or RSRQ exceeds the specified threshold
for CA.
NOTE
If the UE is incapable of working at carrier 2, the eNodeB skips to the next-priority candidate
PCC.
3. After the eNodeB receives an A4 measurement report that contains a cell on carrier 2,
the eNodeB hands over the UE to the cell.
If the eNodeB does not receive such a report or if the handover to the cell fails, the eNodeB
deletes the A4 measurement configuration and evaluates the next-priority candidate PCC in
the same way. If no cells on the candidate PCCs meet the conditions for triggering event A4,
the eNodeB terminates the PCC anchoring procedure and the cell on carrier 1 eventually
serves the UE as its PCell.
NOTE
l If a candidate PCC is not accompanied by candidate SCCs, the eNodeB does not deliver A4
measurement configurations related to this candidate PCC.
l In an inter-eNodeB case, configuration checks on neighboring eNodeBs are not applicable. After the
CA UE is handed over to a new PCell, CA does not work if CA configurations are absent or
incorrect in the target eNodeB or if a data link fails to be set up between the new PCell and an SCell.
NOTE
An eNodeB starts SCell configuration for a CA UE if all the following conditions are met:
l The RRC connection of the UE has been set up in any of the following scenarios:
Initial access (when PCC anchoring has finished)
RRC connection re-establishment
An incoming handover
l Signaling radio bearer 2 (SRB2) and the default data radio bearer (DRB) have been set
up.
l The number of SCells for the UE has not reached the maximum allowed value.
l The UE is not running an emergency call.
The triggering of the SCell configuration procedure is also dependent on two factors:
l Setting of CaTrafficTriggerSwitch
This switch is an option of the ENodeBAlgoSwitch.CaAlgoSwitch parameter.
If this switch is off, which is the default setting, the eNodeB performs SCell
configuration when the CA UE initiates RRC connection setup (PCC anchoring has
finished) or when the traffic volume of the CA UE meets the SCell activation
conditions described in 3.2.5 SCell Activation.
If this switch is on, the eNodeB performs SCell configuration only when the traffic
volume of the CA UE meets the SCell activation conditions described in 3.2.5
SCell Activation.
l AMBR-based control over the number of UEs configured with SCells
This function is introduced in eRAN8.1. Figure 3-23 shows the procedure.
After a UE accesses a cell (during initial access, a handover, or an RRC connection re-
establishment) and reports its CA capability to the eNodeB, the eNodeB checks whether
the number of UEs that treat the cell as their PCell has reached the value of
CaMgtCfg.CellMaxPccNumber. If the number has reached the parameter value, the
eNodeB prohibits SCell configuration for this UE. If the number has not reached the
parameter value, the eNodeB then checks whether the downlink aggregate maximum bit
rate (AMBR) of the UE has exceeded the threshold specified by
CaMgtCfg.CaAmbrThd. The eNodeB allows SCell configuration for this UE only if the
AMBR exceeds the threshold.
In particular, if a CA UE reverts to the single carrier state after the number of UEs that
treat the cell as their PCell reaches the configured value, the eNodeB does not
immediately allow SCell configuration for another UE. The eNodeB allows SCell
configuration for other UEs only when the number of UEs that treat the cell as their
PCell falls below 90% of the configured value.
Figure 3-23 Procedure for AMBR-based control over the number of UEs configured
with SCells
NOTE
l When comparing the number of UEs with the value of CaMgtCfg.CellMaxPccNumber, the
eNodeB does not consider the number of UEs that treat the cell as their SCell.
l If the AMBR of a UE configured with an SCell is decreased to less than the previous AMBR
threshold, the eNodeB does not remove the SCell unless the conditions described in 3.2.7
SCell Removal are met.
l When the value of CaMgtCfg.CellMaxPccNumber is decreased to less than the number of
UEs that treat the cell as their PCell, the eNodeB does not remove the SCells for the UEs.
NOTE
The eNodeB treats a cell that meets all the following conditions as a candidate SCell for a CA
UE:
RRC Connection Reconfiguration message to configure the cell as an SCell for the UE.
If the SCell is configured successfully, the procedure ends. If the eNodeB does not
receive a report that contains a candidate SCell or the SCell fails to be configured, the
eNodeB continues to evaluate next-priority candidate SCells.
NOTE
NOTE
Among the carriers defined in SccFreqCfg MOs, the eNodeB treats those that have not been
configured as SCCs for the CA UE as candidate SCCs. The eNodeB then arranges all
candidate SCCs in descending order of SCC priority (specified by the
SccFreqCfg.SccPriority parameter) and attempts to select a cell on a candidate SCC as an
SCell for the UE. The configuration procedure is as follows:
for the UE, depending on the inter-frequency measurement capability reported by the
UE.
If the UE requires measurement gaps, the eNodeB considers the bearers of the UE.
If a bearer with a QCI of 1 has been established for the UE, the SCell configuration
procedure ends. If no such bearer has been established, the eNodeB sets up
measurement gaps in the measurement configuration. The configuration includes
the EARFCN, frequency-specific offset, measurement bandwidth, and other
measurement-related parameters. For details about the measurement parameters, see
the descriptions related to inter-frequency measurement in Intra-RAT Mobility
Management in Connected Mode.
NOTE
NOTE
l When a bearer for an emergency call or with a QCI of 1 is set up for a CA UE whose SCell
has been configured, the eNodeB does not automatically remove the SCell. The eNodeB
removes the SCell only when the conditions described in 3.2.7 SCell Removal are met.
l After delivering the A4 measurement configuration related to a candidate SCC to the UE, the
eNodeB may receive an A2 measurement report, indicating unsatisfactory signal quality of the
PCell, for an inter-frequency or inter-RAT handover. In such a case, the eNodeB will not
configure a candidate cell as an SCell for the UE, even if the eNodeB later receives an A4
measurement report that contains the candidate cell.
NOTE
Among the carriers defined in SccFreqCfg MOs, the eNodeB treats those that have not been
configured as SCCs for the CA UE as candidate SCCs. The eNodeB then arranges all
candidate SCCs in descending order of SCC priority (specified by the
SccFreqCfg.SccPriority parameter) and attempts to select a cell on a candidate SCC as an
SCell for the UE. The configuration procedure is as follows:
1. The eNodeB checks whether a blind-configurable candidate cell (with
CaGroupSCellCfg.SCellBlindCfgFlag set to TRUE(TRUE)) on the top-priority
candidate SCC has been specified for the PCell of the UE.
If such a cell has been specified, the eNodeB delivers an RRC Connection
Reconfiguration message to configure this cell as an SCell for the UE, without
delivering measurement configurations.
NOTE
If there are multiple blind-configurable candidate cells (either on the same candidate SCC or
on different candidate SCCs), the eNodeB selects the first cell that it finds.
If no such cell has been specified or the blind configuration fails, the eNodeB goes
to the next step.
NOTE
If multiple candidate SCCs have the same priority, the eNodeB will perform the subsequent
steps on all candidates.
2. The eNodeB delivers the A4 measurement configuration, instructing the UE to measure
the candidate SCC. In addition, the eNodeB may set up measurement gaps for the UE,
depending on the inter-frequency measurement capability reported by the UE.
If the UE requires measurement gaps, the eNodeB considers the bearers of the UE.
If a bearer with a QCI of 1 has been established for the UE, the SCell configuration
procedure ends. If no such bearer has been established, the eNodeB sets up
measurement gaps in the measurement configuration. The configuration includes
the EARFCN, frequency-specific offset, measurement bandwidth, and other
measurement-related parameters. For details about the measurement parameters, see
the descriptions related to inter-frequency measurement in Intra-RAT Mobility
Management in Connected Mode.
NOTE
NOTE
3. After receiving an A4 measurement report that contains cells on the candidate SCC, the
eNodeB selects the reported cells that belong to the serving PLMN of the UE or an
equivalent PLMN as candidate SCells. The eNodeB then arranges the candidate SCells
in descending order of RSRP and proceeds as follows:
If the PCell can set up a data link to the top-priority candidate SCell, the eNodeB
sends an RRC Connection Reconfiguration message to configure the candidate cell
as an SCell for the UE. If the SCell is configured successfully, the procedure ends.
If the SCell fails to be configured, the eNodeB tries the next-priority candidate
SCell.
If the PCell cannot set up a data link to the top-priority candidate SCell, the eNodeB
tries the next-priority candidate SCell.
If none of the candidate SCells can be configured as an SCell for the UE, the
eNodeB evaluates the next-priority candidate SCC.
NOTE
l When a bearer for an emergency call or with a QCI of 1 is set up for a CA UE whose SCell
has been configured, the eNodeB does not automatically remove the SCell. The eNodeB
removes the SCell only when the conditions described in 3.2.7 SCell Removal are met.
l After delivering the A4 measurement configuration related to a candidate SCC to the UE, the
eNodeB may receive an A2 measurement report, indicating unsatisfactory signal quality of the
PCell, for an inter-frequency or inter-RAT handover. In such a case, the eNodeB will not
configure a candidate cell as an SCell for the UE, even if the eNodeB later receives an A4
measurement report that contains the candidate cell.
NOTE
eNodeBs do not consider the load status of cells during A6-based SCell changes.
After receiving an A6 measurement report from the UE, the eNodeB arranges the reported
candidate SCells in descending order of RSRP and proceeds as follows:
l If the PCell can set up a data link to the top-priority candidate SCell (for example, cell
2), the eNodeB sends an RRC Connection Reconfiguration message to change the SCell
from cell 1 to cell 2 for the UE.
l If the PCell cannot set up a data link to cell 2, the eNodeB tries the next-priority
candidate SCell.
If the PCell cannot set up a data link to any candidate SCell, the eNodeB does not change the
SCell for the UE.
NOTE
l To maintain satisfactory SCell signal quality, it is recommended that SccModA6Switch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter should always be on after CA is enabled.
l When a CA UE supports downlink 3CC or FDD+TDD 4CC aggregation and is configured with two
or three SCells, the eNodeB delivers an A6 measurement configuration to each SCell if
SccModA6Switch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on. The SCell change
procedure occurs in the SCells separately.
NOTE
To ensure synchronization between the UE and the eNodeB, an SCell is activated on the UE
and eNodeB simultaneously in the xth subframe after the eNodeB sends a MAC CE for SCell
activation to the UE. The value of x is protocol-stipulated. For FDD eNodeBs, the value is 8.
Figure 3-35 shows the SCell activation. As shown in the figure, the eNodeB sends a MAC
CE in subframe n, and the SCell is activated on the UE and eNodeB in subframe (n+x).
NOTE
SCell deactivation does not require the CaMgtCfg.CarrierMgtSwitch parameter to be set for the
eNodeBs that serve SCells.
NOTE
NOTE
l After deactivating an SCell based on channel quality, the eNodeB that serves the PCell does not
remove the SCell, no matter whether CaTrafficTriggerSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter is on or off in the eNodeB.
l After an SCell is deactivated based on channel quality, the CA UE no longer reports the SCell's CQI
to the eNodeB. The eNodeB may subsequently activate the SCell based on traffic volume.
The eNodeB that serves the PCell of a CA UE removes SCells. The UE state changes as
follows:
l If the eNodeB removes the only SCell of a UE in the uplink or downlink 2CC
aggregation state, the UE falls back to the single carrier state.
l If the eNodeB removes an SCell of a UE in the downlink 3CC aggregation state, the UE
falls back to the downlink 2CC aggregation state. If the eNodeB removes both SCells,
the UE falls back to the single carrier state.
l If the eNodeB removes an SCell of a UE in the downlink FDD+TDD 4CC aggregation
state, the UE falls back to the downlink 3CC aggregation state. If the eNodeB removes
two SCells, the UE falls back to the downlink 2CC aggregation state. If the eNodeB
removes three SCells, the UE falls back to the single carrier state.
NOTE
l When a bearer for an emergency call or with a QCI of 1 is set up for a CA UE whose SCells have
been configured, the eNodeB does not automatically remove the SCells.
l In CA-group-based (with blind SCell configuration disabled), frequency-based, or adaptive
configuration mode, to maximize the probability of UEs being in the CA state, operators can set
SccA2RmvSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter off. Then, the eNodeB
will not deliver the A2 measurement configuration for SCell removal.
If SccA2RmvSwitch is off or the SCell was configured in a blind manner, the eNodeB does
not deliver the A2 measurement configuration.
NOTE
In CA-group-based configuration mode, the following setting constraint applies: The threshold for event
A4 must be higher than the threshold for event A2. In addition, only the values in the range of [-143,
-43] take effect for both thresholds.
If SccA2RmvSwitch is off, the eNodeB does not deliver the A2 measurement configuration.
NOTE
In frequency-based or adaptive configuration mode, no setting constraint takes effect on the thresholds
for events A2 and A4. When setting the parameters for these thresholds, ensure that the threshold for
event A4 is higher than the threshold for event A2. If the threshold for event A4 is not higher than the
threshold for event A2 and SccA2RmvSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter
is on, the eNodeB will remove an SCell based on event A2 immediately after configuring the SCell.
Then, if the traffic volume of the CA UE meets the SCell activation conditions throughout a certain
period of time, the eNodeB configures the SCell again. As a result, the SCell is configured and removed
repeatedly. The two thresholds are defined as follows:
l Threshold for event A4 = CaMgtCfg.CarrAggrA4ThdRsrp + SccFreqCfg.SccA4Offset. If the sum
is greater than 43 dBm or less than 140 dBm, the threshold takes the value 43 dBm or 140
dBm, respectively.
l Threshold for event A2 = CaMgtCfg.CarrAggrA2ThdRsrp + SccFreqCfg.SccA2Offset. If the sum
is greater than 43 dBm or less than 140 dBm, the threshold takes the value 43 dBm or 140
dBm, respectively.
l The PCell and SCell for a CA UE each have a complete set of channels with one
exception: physical uplink control channel (PUCCH). The PUCCH exists only in the
PCell. This channel carries layer 1 uplink control information, such as acknowledgments
(ACKs) or negative ACKs (NACKs) to downlink data, scheduling requests, and periodic
channel state information (CSI).
l The PCell is selected for a CA UE during initial access or an RRC connection re-
establishment. A handover is required to change the PCell for the UE. If a radio link
failure (RLF) occurs in the PCell, an RRC connection re-establishment procedure is
triggered.
l An SCell can be deactivated, but the PCell cannot. Only the eNodeB that serves the
PCell can deactivate and remove the SCell.
Handover Messages
The handover procedures for CA UEs have the following characteristics:
l The handover procedure for PCell changes is the same as a common handover
procedure, in which the eNodeB sends an RRC Connection Reconfiguration message
that contains the IE mobilityControlInfo to the UE.
l Unlike a common handover procedure, the handover procedure that involves SCell
configuration or removal has the following characteristics:
If SCell configuration is required, the eNodeB sends an RRC Connection
Reconfiguration message that contains the IE sCellToAddModList to the UE.
If SCell removal is required, the eNodeB sends an RRC Connection
Reconfiguration message that contains the IE sCellToReleaseList to the UE.
The number of CCs configured in source and target eNodeBs is irrelevant to the handover
procedure. If the target eNodeB is configured with a total of four downlink FDD and TDD
CCs, the SCell configuration procedures take place for 4CC aggregation. If the target eNodeB
is configured with three or two CCs, the procedures take place for 3CC or 2CC aggregation,
respectively.
The RRC Connection Reconfiguration and the preceding IEs can be traced as described in
6.4.6 Activation Observation.
Measurement Configuration
If an eNodeB performs CA for a CA UE whose signal quality is so poor that an inter-
frequency handover may occur, the spectral efficiency of the network decreases and the block
error rate (BLER) increases. To prevent this, set thresholds as follows:
l The threshold for CA event A4 (for SCell configuration) is greater than or equal to the
threshold for inter-frequency handover event A4 (specified by
InterFreqHoGroup.InterFreqHoA4ThdRsrp). The threshold for CA event A4 is equal
to CaMgtCfg.CarrAggrA4ThdRsrp plus CaGroupSCellCfg.SCellA4Offset in CA-
group-based configuration mode, or equal to CaMgtCfg.CarrAggrA4ThdRsrp plus
SccFreqCfg.SccA4Offset in frequency-based or adaptive configuration mode.
l The threshold for CA event A2 (for SCell removal) is greater than or equal to the
threshold for inter-frequency handover event A2 (specified by
Handover Events
CA UEs report events for eNodeBs to evaluate the following handovers:
l Intra-frequency handover (Related parameters are configured in the IntraFreqHoGroup
MO.)
An eNodeB performs an intra-frequency handover for a CA UE when it receives an A3
measurement report from the UE in the PCell.
l Inter-frequency handover (Related parameters are configured in the InterFreqHoGroup
MO.)
After receiving an A2 measurement report from a CA UE in the PCell, the eNodeB that
serves the PCell delivers the inter-frequency measurement configuration to the UE. The
measurement configuration varies depending on the SCell configuration:
When an SCell has been configured for the UE, the eNodeB delivers the A3
measurement configuration if EUTRANINTERNFREQ.InterFreqHoEventType
is set to EventA3. If this parameter is not set to EventA3, the eNodeB delivers the
A5 measurement configuration.
If no SCell has been configured for the UE, the eNodeB delivers the measurement
configuration related to the event specified by
EUTRANINTERNFREQ.InterFreqHoEventType.
The eNodeB performs an inter-frequency handover for the UE when it receives a
measurement report of the specified event from the UE.
NOTE
l For details about the triggering conditions for the preceding events, see Intra-RAT Mobility
Management in Connected Mode. Event A5 indicates that the signal quality in the PCell is
lower than the threshold for handover event A2 and the signal quality in at least one
neighboring cell is higher than the threshold for handover event A4.
l If threshold 1 of event A5 is lower than or equal to the threshold for triggering blind-handover
event A2, the eNodeB does not deliver an A5 measurement configuration. Therefore, it is
recommended that threshold 1 of event A5 be the same as the threshold for triggering inter-
frequency handover event A2.
Frequency-Priority-based Handover
If the operator-specified frequency with the highest priority for frequency-priority-based
handovers is different from the frequency with the highest priority for PCC anchoring, you are
advised to select the FreqPriBasedHoCaFiltSwitch option of the
If a frequency has both the highest priority for frequency-priority-based handovers and the
highest priority for PCC anchoring, you can deselect the FreqPriBasedHoCaFiltSwitch and
PccAnchorSwitch options of the ENodeBAlgoSwitch.CaAlgoSwitch parameter. In such a
case, mobility of both CA UEs and non-CA UEs is subject to the frequency priorities defined
for frequency-priority-based handovers.
l If HoWithSccCfgSwitch is on:
The source eNodeB includes the current SCell information in the IE sCellToAddModList
of the handover request message, which also contains the IE CandidateCellInfoList, sent
to the target eNodeB. The target eNodeB acquires measurement results from the IE
CandidateCellInfoList, determines the new SCell to be configured during the handover,
and updates the IE sCellToAddModList with the new SCell information. Then, the target
eNodeB sends the updated information in the handover command to the source eNodeB.
The source eNodeB sends an RRC Connection Reconfiguration message that contains
the IEs mobilityControlInfo, sCellToReleaseList, and sCellToAddModList to remove the
original SCell and configure the new SCell during the handover.
CaTrafficTriggerSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter does
not take effect in the preceding procedure. The source and target eNodeBs perform the
procedure without considering traffic volume for configuring the SCell even if
CaTrafficTriggerSwitch is on.
If the SCell configuration fails, no SCell is configured for the UE that has been handed
over to the target cell. In this case, the target eNodeB performs an SCell configuration
procedure. For details about the CA-group-based, frequency-based, and adaptive
configuration procedures, see 3.2.3.1 CA-Group-based SCell Configuration, 3.2.3.2
Frequency-based SCell Configuration, and 3.2.3.3 Adaptive SCell Configuration,
respectively.
NOTE
l This procedure results in a decrease in the number of blind or A4-based SCell configurations.
l SCell configuration during a handover requires that a routing relationship be set up between
the SCell and the target cell of the handover.
l If the function of SCell configuration during handovers is enabled, the eNodeB attempts to
configure SCells without considering the load status of candidate SCells, when PCC anchoring
is triggered. This shortens the SCell configuration delay.
l If HoWithSccCfgSwitch is off:
The source eNodeB delivers an RRC Connection Reconfiguration message to remove
the SCell and performs an intra- or inter-frequency handover for the UE. After the UE is
handed over to the target cell, the target eNodeB configures an SCell for the UE.
NOTE
In CA scenarios, handovers are executed in compliance with 3GPP Release 8. For details about
handover execution procedures, see Overview of Mobility Management in Connected Mode.
Admission Control
When compared with common admission control, admission control under CA has the
following characteristics:
l Admission control based on the number of UEs
When an eNodeB receives an access request from a CA UE (for an RRC connection
establishment or reestablishment, an incoming handover, or a transition from out-of-
synchronization to in-synchronization), the eNodeB performs admission control in both
the PCell and SCell based on the number of UEs. If the eNodeB accepts the access
request, it treats the UE as an RRC_CONNECTED UE in both the PCell and SCell.
However, only the RRC_CONNECTED UEs in the PCell consume UE count license
units. As a result, if all UEs on the entire network have their SCells activated, the
maximum number of UEs that can access the network decreases by half, and the number
of consumed UE count license units is equal to the actual number of UEs that have
accessed the network.
l Admission control based on QoS satisfaction rates
This type of admission control applies to GBR services of CA UEs only in the PCell. If a
CA UE is admitted to the PCell, the UE accesses the network. If the UE is not admitted
to the PCell and is incapable of preemption, the UE cannot access the network. If the UE
is not admitted to the PCell but is capable of preemption, the UE performs preemption
and, if preemption is successful, accesses the network.
NOTE
l When a preemption-capable UE attempts to access a cell configured on a BBP where the number of
UEs has reached the maximum, the eNodeB preferentially releases CA UEs that treat the cell as
their SCell. The release maximizes the total number of UEs on the entire network.
l For more details about admission control, see Admission and Congestion Control.
Congestion Control
Huawei eNodeBs relieve traffic congestion mainly by releasing GBR services. When a cell is
overloaded, GBR services in the cell do not meet their QoS requirements. If DlLdcSwitch
and UlLdcSwitch under the CellAlgoSwitch.RacAlgoSwitch parameter are on for the cell,
the eNodeB releases low-priority GBR services in the cell to ensure the satisfaction rates of
high-priority GBR services. This congestion control method applies in CA scenarios.
To relieve congestion due to radio resource insufficiency in a cell, the eNodeB releases GBR
services of non-CA UEs and GBR services of CA UEs that treat the cell as their PCell. When
the eNodeB selects the UEs whose services are to be released, it removes CA UEs that treat
the cell as their SCell from the list of prioritized candidates. If a service to be released is the
only GBR service of a UE that meets the redirection condition, the eNodeB redirects the UE.
If the service is not the only GBR service or the redirection condition is not met, the eNodeB
releases this GBR service of the UE.
NOTE
the CCs are close, UEs are evenly distributed on the CCs, and channel conditions are the
same between the CCs.
In differentiated scheduling, a CA UE is treated as a common UE on each CC. It is
scheduled separately in the CCs. Therefore, a CA UE can be assigned more PRBs and
have better user experience than a non-CA UE. However, radio resources for non-CA
UEs decrease.
UE scheduling on their PCCs and SCCs varies depending on CA scenarios:
l In inter-eNodeB CA based on centralized multi-BBU interconnection and intra-eNodeB
CA, when RLC unacknowledged mode (UM) is used, the eNodeB that serves the PCell
schedules the UE only on the PCC if the service type is VoLTE or emergency call. If the
service type is not VoLTE or emergency call, the eNodeB can schedule the UE on all the
CCs. For details about RLC UM, see section 4.2.1 "RLC entities" in 3GPP TS 36.322
V10.0.0.
l In inter-eNodeB CA based on relaxed backhaul, when RLC UM is used, the eNodeB that
serves the PCell schedules the UE only on the PCC regardless of service types (VoLTE,
emergency call, real-time video or voice streaming, or real-time gaming).
Currently, frequency-selective scheduling is not used in SCells by default. To enable
frequency-selective scheduling in an SCell, set CellDlschAlgo.CaSccDopMeas to
FROMPCC(FROMPCC).
NOTE
l After an SCell is configured for a CA UE in the uplink, uplink scheduling uses the method
configured for downlink scheduling: basic or differentiated scheduling.
l For more details about scheduling, see Scheduling.
According to section 5.7 "Discontinuous Reception (DRX)" in 3GPP TS 36.321 V11.2.0, the
same active time applies to all activated serving cells.
For this purpose, all the serving cells use the DRX parameters of the PCell, including On
Duration Timer, DRX Inactivity Timer, and DRX Short Cycle Timer. Figure 3-38 shows an
example of the DRX configuration under CA.
l If DRX is enabled in both the PCell and the SCell for a CA UE, the UE states in the cells
are handled as follows when the eNodeB that serves the PCell sends a MAC CE to
activate the SCell:
If the UE has entered the DRX state in the PCell, the UE now also enters the DRX
state in SCells, with the DRX parameters for the PCell applied to the SCells.
If the UE has not entered the DRX state in the PCell, the eNodeB determines
whether the UE should enter the DRX state in all the PCell and SCells based on the
traffic volume of the UE.
l If DRX is enabled in the PCell but disabled in an SCell, the UE exits and no longer
enters the DRX state after the SCell is configured for the UE.
l If DRX is disabled in the PCell, the UE will not enter the DRX state in either the PCell
or SCells, regardless of whether DRX is enabled in the SCells.
NOTE
For more details about DRX, see DRX and Signaling Control.
CA UEs can access only operator-specific carriers (either in PCells or in SCells). Assume that
there are three frequencies:
On this network, only the carriers of f1 and f2 can be aggregated for CA UEs of operator A,
and only the carriers of f1 and f3 can be aggregated for CA UEs of operator B. CA UEs of
operator A cannot access cells on f3 or have cells on f3 configured as their SCells. In addition,
CA UEs of operator B cannot access cells on f2 or have cells on f2 configured as their SCells.
NOTE
NOTE
For details about extended PHR, see section 6.1.3.6a "Extended Power Headroom MAC Control
Element" in 3GPP TS 36.321 V11.0.0.
After an SCell is configured and activated in both downlink and uplink for the UE, the
eNodeB sends a PDCCH order to the UE and, as instructed, the UE initiates a non-contention-
based random access procedure in the SCell. The eNodeB then sends the UE a random access
response to configure a secondary timing advance group (sTAG) for the UE. The network
maintains a TA for each serving cell of the UE.
If the number of preamble retransmissions in the SCell reaches the maximum, the random
access procedure fails. The UE stops random access without instructing the PCell to perform
RRC connection reestablishment. As a result, the UE is out-of-synchronization in the uplink,
and only downlink scheduling is allowed.
A noticeable difference (for example, a TA, which is equivalent to about 78 meters) in the
locations of reception antennas between the PCell and an SCell has a significant impact on
demodulation performance if a single TA is used. It is recommended that MTA be enabled to
improve uplink performance.
NOTE
For details about PDCCH order, see section 8.0 "UE procedure for transmitting the physical uplink
shared channel" in 3GPP TS 36.213 V11.4.0.
4 Related Features
Impacted Features
l LBFD-002028 Emergency Call
When a CA UE is running an emergency call service, the eNodeB terminates SCell
configuration procedures in which gap-assisted measurements are required. Gap-assisted
measurements negatively affect the service quality of emergency calls. After the
emergency call service is finished, the eNodeB re-attempts to configure SCells for the
UE if the UE traffic volume and SCell configuration interval conditions are fulfilled.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
In addition to the features described in 4.1 Features Related to LAOFD-001001 LTE-A
Introduction, the following features affect CA:
Impacted Features
In addition to the features described in 4.1 Features Related to LAOFD-001001 LTE-A
Introduction, CA affects the following features:
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
This feature is required if at least two TDD carriers are involved in FDD+TDD CA and
the total bandwidth of the TDD carriers is greater than 30 MHz but not greater than 40
MHz.
l (Optional) TDLAOFD-081405 Carrier Aggregation for Downlink 3CC
This feature is required if three TDD carriers are involved in FDD+TDD CA.
l (Optional) TDLAOFD-070201 Flexible CA from Multiple Carriers
This feature is required if the function of Flexible CA from Multiple Carriers is used for
the TDD carriers involved in the CA.
Impacted Features
l The impacted FDD eRAN features are as follows:
LBFD-070103 Multi-Band Compatibility Enhancement
Frequency-based CA and adaptive CA do not apply to multi-band cells. In either
configuration mode, when an eNodeB compares its band combination capability
with that of a CA UE, the eNodeB calculates band indicators based on the downlink
E-UTRA absolute radio frequency channel numbers (EARFCNs) of the PCC and
SCCs in SccFreqCfg MOs. However, currently the eNodeB does not consider
multi-band capabilities of cells. Therefore, the calculation produces only the
primary-band indicator.
LOFD-001016 VoIP Semi-persistent Scheduling
According to 3GPP TS 36.321, semi-persistent scheduling takes effect only on the
PCCs for CA UEs.
LOFD-001032 Intra-LTE Load Balancing and LOFD-070215 Intra-LTE User
Number Load Balancing
When selecting UEs for either type of load balancing defined in the two features,
the eNodeB filters out the CA UEs that treat the source cell as their PCells or
SCells.
LOFD-002001 Automatic Neighbour Relation (ANR) and LOFD-002002 Inter-
RAT ANR
During ANR, the eNodeB determines whether to select CA UEs to perform
measurements based on the ANR.CaUeChoseMode parameter setting. For details,
see ANR Management.
LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB)
This feature requires a centralized controller, which is a process deployed on a BBP
in the eNodeB. The centralized controller increases the average throughput of cells
on the affected frequency and the cell edge UE throughput in the network.
However, it has a negative impact on the high-throughput UEs that cause co-
channel interference to the cell edge UEs. If basic scheduling is used with CA, the
data rate of a CA UE is the total data rate of the UE on all the aggregated carriers
and therefore is typically higher than the data rate of a non-CA UE. As a result, CA
UEs have a lower probability of being scheduled and therefore a lower data rate in
CSPC scenarios.
LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture
When this feature is enabled, CA UEs can receive MBSFN subframes in their
PCells but not in their SCells. This feature works for CA UEs only in PCells.
LAOFD-002001 Static TDM eICIC and LAOFD-081233 Dynamic TDM eICIC
When one or both of these two features are enabled, the interference between macro
and micro cells cannot be mitigated as expected, because of subframe
synchronization between the PCell and SCells of each CA UE.
l The impacted TDD eRAN features are as follows:
TDLBFD-00201806 Multi-Band Compatibility Enhancement
If Multi-Band Compatibility Enhancement is enabled for a cell, the primary and
secondary operating bands of the cell are all compared with the CA band
combinations supported by CA UEs. The cell can be configured as an SCell for a
CA UE as long as an operating band of the cell is included in the CA band
combinations supported by the UE. If the CA UE can operate in the primary band
and a secondary band and only the secondary band supports CA, the eNodeB
transfers the UE to the secondary band through an intra-cell handover before
configuring the cell as an SCell for the UE.
TDLOFD-001016 VoIP Semi-persistent Scheduling
According to 3GPP TS 36.321, semi-persistent scheduling takes effect only on the
PCCs for CA UEs.
5 Network Impact
Network Performance
l PRB usage
In commercial networks, most services on CA UEs are burst services, and there is little
probability that PRBs in all CCs of a UE will be exhausted simultaneously. When CA is
enabled, cell load can be rapidly balanced through carrier management and scheduling,
utilizing idle resources and increasing the PRB usage of the network.
l Number of CQI reports
According to section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V10.10.0,
CA UEs cannot send CSI reports together with ACK/NACK over the PUCCH with
format 1b. Therefore, the UEs discard CSI reports according to 3GPP specifications. CSI
reports include periodic CQI reports. As a result, the number of CQI reports from CA
UEs decreases, as indicated by the values of the L.ChMeas.CQI.DL.0 to
L.ChMeas.CQI.DL.15 counters, after CA is enabled.
When the number of CQI reports from CA UEs decreases, the total number of CQI
reports in the entire network may decrease, increase, or remain unchanged, depending on
the radio conditions of the CA UEs and the ratio of CA UEs to all UEs. For example, if
CA UEs are located in cell centers and account for a high proportion of total UEs, the
total number of CQI reports may also decrease. If CA UEs are not located in cell centers
or they account for a low proportion, the total number of CQI reports may increase or
remain unchanged.
In a distributed multi-BBU interconnection scenario, if the round trip time for inter-eNodeB
transmission is between 32 s (including 32 s) and 260 s, the LAOFD-070202 feature
imposes the following impact on the UEs involved:
the CA UEs decrease. When the eNodeB detects that the congestion is relieved, it stops
the backpressure, and the data rates of the CA UEs return to the original levels.
addition, the FDD PCC provides better uplink coverage for the CA UE than a TDD carrier
does for a non-CA UE.
l If the live network is deployed in accordance with scenario 1 or 2, use any of the three
configuration modes: CA-group-based, frequency-based, and adaptive.
l If the live network is deployed in accordance with scenario 3 or 4, use frequency-based
or adaptive configuration.
In addition, considering the total bandwidth of the CCs, select features as follows:
l If the total bandwidth does not exceed 20 MHz, enable only LAOFD-001001 LTE-A
Introduction.
l If the total bandwidth is greater than 20 MHz but not greater than 40 MHz, enable both
LAOFD-001001 LTE-A Introduction and LAOFD-001002 Carrier Aggregation for
Downlink 2CC in 40MHz.
6.3 Planning
RF Planning
The coverage areas provided by the carriers to be aggregated must overlap. The areas where
CA takes effect are dependent on the overlapping ranges. Specifically:
l For CA-group-based configuration, the overlapping ranges must meet the requirements
of scenario 1 or 2 as described in 3.1.2.1 Typical Scenarios.
l For frequency-based or adaptive configuration, the overlapping ranges must meet the
requirements of scenario 1, 2, 3, or 4 as described in 3.1.2.1 Typical Scenarios.
Network Planning
l If the live network uses multiple frequency bands, the network plan does not need to be
changed.
l If the live network uses only one frequency, deploy at least one more frequency and
ensure that the frequencies meet the requirements described in RF Planning.
Hardware Planning
l RF modules
To meet the time alignment error requirements, use one dual-carrier RF module or two
RF modules of the same model for intra-band CA. Inter-band CA has no special
requirements for RF modules. For the time alignment error requirements, see 3.1.3.1
LAOFD-001001 LTE-A Introduction in 3.1.3 CA Features.
If a single-carrier RRU3201 has been deployed for an eNodeB of eRAN3.0 or an earlier
version, the RRU3201 supports two carriers after a software upgrade to eRAN6.0 or a
later version. In this case, common public radio interface (CPRI) modules must be
adjusted. For details, see "Reconfiguring a Single-Carrier Sector as a Dual-Carrier
Sector" in "Reconfiguration" of Cell Management.
l BBPs, including UMDU
CA works between either intra-BBP or inter-BBP cells. For intra-BBP CA, use a BBP
other than LBBPc. For inter-BBP CA, use any combination of LBBPc, LBBPd, and
UBBP boards, except a combination of two LBBPc boards. Antenna modes of cells
supported by common BBPs are listed in Table 6-1.
NOTE
LBBPd and UBBP perform better than LBBPc in terms of UE capacities and processing
capabilities. Therefore, it is recommended that cells on LBBPd and UBBP boards, rather than cells
on LBBPc boards, act as PCells for UEs.
LBBPd3 2T2R
UBBPd5 2T2R
UBBPd5 2T2R
UBBPda 2T2R
UMDUa3 2T2R
6.4 Deployment
6.4.1 Requirements
Operating Environment
None
NEs
Table 6-2 describes the network requirements for CA.
eNodeB l The eNodeB must support one RLC entity for the entire eNodeB and
independent MAC and HARQ entities for each CC and also support
communication between BBPs.
l Section 5.7.1A in 3GPP TR 36.101 requires that the nominal channel
spacing between the center frequencies of two intra-band contiguous
CCs be an integer multiple of 300 kHz.
For example, the nominal channel spacing for two contiguous 20 MHz
CCs is 19.8 MHz, and that for two contiguous CCs with a bandwidth
combination of 20 MHz and 10 MHz is 14.4 MHz. Nominal channel
spacing is calculated as follows:
NOTE
BWChannel(1) and BWChannel(2) are the bandwidths of two carriers.
l RF modules and BBPs must meet the requirements described in
Hardware Planning in 6.3 Planning.
UE UEs must comply with 3GPP Release 10 or later and support the frequency
bands of the carriers to be aggregated and their channel bandwidths.
NOTE
According to 3GPP TS 36.306, CA UEs must report the IE supportedBandCombina-
tion, based on which the eNodeB performs CA.
Transmission Networking
None
License
Deploying CA requires the following licenses:
l If the total bandwidth of the aggregated cells is less than or equal to 20 MHz, each cell
requires one sales unit of the license for LAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the aggregated cells is between 20 MHz and 40 MHz (including
40 MHz), each cell requires one sales unit of the license for LAOFD-001001 LTE-A
Introduction and one sales unit of the license for LAOFD-001002 Carrier Aggregation
for Downlink 2CC in 40MHz.
Others
l The prerequisite features for the CA features must have been enabled.
l Inter-BBP data exchange for CA is bandwidth-consuming. If CA is activated together
with the CoMP or SFN feature, the backplane bandwidth may be insufficient. To prevent
this, it is recommended that intra-frequency cells be configured in the same BBP.
l Cells in band 29 are DL_ONLY cells, which transmit only downlink data. UEs cannot
camp on the cells (in idle mode), access the cells, or be handed over to the cells. These
cells can serve only as SCells for CA UEs. In addition, cells and sector equipment in this
band must be configured as follows:
Cell.WorkMode is set to DL_ONLY(Downlink only), Cell.FreqBand is set to 29,
and Cell.UlEarfcn is not set. In addition, SECTOREQM.ANTTYPE1 and
SECTOREQM.ANTTYPE2 (if two antennas are configured) are set to
TX_MODE(TX).
EUTRANINTERNFREQ.AnrInd is set to
NOT_ALLOWED(NOT_ALLOWED) for frequencies in band 29 so that they
will not be managed by ANR. Therefore, for CA to take effect, you must manually
configure cells in band 29 as inter-frequency neighboring cells of intended
candidate PCells.
EUTRANINTERNFREQ.MlbTargetInd is set to
NOT_ALLOWED(NOT_ALLOWED) for frequencies in band 29 so that they
will not be treated as targets for mobility load balancing (MLB).
NOTE
l Each cell in band 29 can have a maximum of two transmit channels. It does not support 4T or
8T antenna modes.
l RRUs do not provide uplink resources for cells in band 29. Therefore,
SECTOREQM.AntTypeX (X = 1, 2, 3...8) cannot be set to RX_MODE(RX) or
RXTX_MODE(RX And TX).
l The Cell.WorkMode parameter can be set to DL_ONLY(Downlink only) only for cells in
band 29. If Cell.WorkMode is set to DL_ONLY(Downlink only) for cells in other bands, cell
activation fails.
l If the carriers to be aggregated are capable of multiple frequency band indicator (MFBI),
PccFreqCfg.PccDlEarfcn and SccFreqCfg.SccDlEarfcn must be set to the primary
frequency bands indicated by the MFBI.
NOTE
The parameters described in this section are mandatory for CA. You may set other optional parameters
as well based on the network plan. For the optional parameters, see 6.6 Parameter Optimization.
CA-Group-based Configuration
Parameter Parameter ID Setting Notes Data Source
Name
Local cell ID CaGroupSCell Set this parameter based on the Network plan
Cfg.LocalCellId network plan. (negotiation not
required)
Frequency-based Configuration
Parameter Parameter ID Setting Notes Data Source
Name
PCC Downlink PccFreqCfg.P Set this parameter based on the Network plan
EARFCN ccDlEarfcn network plan. (negotiation not
required)
PCC Downlink SccFreqCfg.P Set this parameter based on the Network plan
EARFCN ccDlEarfcn network plan. (negotiation not
required)
SCC Downlink SccFreqCfg.Sc Set this parameter based on the Network plan
EARFCN cDlEarfcn network plan. (negotiation not
required)
Adaptive Configuration
Parameter Parameter ID Setting Notes Data Source
Name
PCC Downlink PccFreqCfg.P Set this parameter based on the Network plan
EARFCN ccDlEarfcn network plan. (negotiation not
required)
PCC Downlink SccFreqCfg.P Set this parameter based on the Network plan
EARFCN ccDlEarfcn network plan. (negotiation not
required)
SCC Downlink SccFreqCfg.Sc Set this parameter based on the Network plan
EARFCN cDlEarfcn network plan. (negotiation not
required)
6.4.3 Precautions
l In RAN sharing scenarios, eNodeB ID collisions must be prevented. Otherwise, errors
occur in SCell configuration because target eNodeBs cannot be identified.
l Network planning must mitigate physical cell identifier (PCI) conflicts. If a PCI conflict
occurs on a cell, the eNodeB will not configure the cell as an SCell for any UE.
l In a CA group, cells in a pair must have the same cyclic prefix (CP) length: either normal
CP or extended CP.
l After CA groups (for CA-group-based configuration) or candidate PCCs and SCCs (for
frequency-based or adaptive configuration) are manually configured, the eNodeB can
configure SCells for CA UEs that newly access the network. However, this action does
not apply to CA UEs that have been staying in RRC_CONNECTED mode before the
CA groups or candidate PCCs and SCCs are configured. SCells can be configured for
these UEs only after they access the network again or are handed over.
l If CaMgtCfg.ActiveBufferLenThd is set to 0, a large amount of radio resources is
consumed. There are two reasons:
The eNodeB activates a configured SCell as long as the eNodeB intends to send
data to the CA UE. However, if the traffic volume of the CA UE is low, the eNodeB
deactivates the SCell (because the deactivation condition is met) immediately after
it activates the SCell for the UE.
If no SCell has been configured for the CA UE, the eNodeB repeatedly attempts to
configure an SCell without considering CaMgtCfg.SccCfgInterval when the
eNodeB intends to send data to the CA UE.
To reduce the radio resource consumption, it is recommended that
CaMgtCfg.DeactiveBufferLenThd be less than CaMgtCfg.ActiveBufferLenThd.
l When CA is enabled, a large number of scheduling request indicators (SRIs) collide with
measurement gaps, delaying the transmission of scheduling requests from CA UEs.
When the number of SRI retransmissions reaches its maximum, the values of the
following indicators increase: service drop rate, number of RRC connection re-
establishments, and number of random access attempts. To avoid these impacts, you are
advised to select the BasedSriGapOptSwitch option of the
ENodeBAlgoSwitch.HoCommOptSwitch parameter, which resolves the collision.
l For CA-group-based configuration, note the following:
If a higher-frequency cell that provides relatively small coverage works as the
PCell, you are advised to enable blind configuration for a lower-frequency cell that
provides relatively large coverage. This prevents an unnecessary inter-frequency
measurement of the lower-frequency cell, which always meets the triggering
condition for event A4, when a CA UE is in the higher-frequency cell.
If a lower-frequency cell that provides relatively large coverage works as the PCell,
you are advised to disable blind configuration for a higher-frequency cell that
provides relatively small coverage. If blind configuration is enabled, a CA UE that
has accessed the lower-frequency cell encounters low scheduling efficiency in the
higher-frequency cell. In this case, the data rate of the CA UE does not reach twice
that of a non-CA UE even in differentiated scheduling mode.
An eNodeB can be configured with a maximum of 72 CaGroupSCellCfg MOs,
which represent candidate SCells. Ensure that the candidate SCells are included in
the same CA group as the associated PCells. Otherwise, the candidate SCell
configurations do not take effect and therefore are regarded as invalid. Delete the
invalid CaGroupSCellCfg MOs, which account for a proportion of the MO
capacity.
CA takes effect for a maximum of five inter-frequency cells in a CA group. If more
than five cells are added to a CA group, CA takes effect only for at most five inter-
frequency cells no matter whether the cells added to the CA group are all inter-
frequency cells or some of them are intra-frequency cells. If some of them are intra-
frequency cells, CA takes effect only for one of the intra-frequency cells so that the
CA-effective cells in the CA group are all inter-frequency cells.
l For frequency-based configuration, note the following:
An LBBPd or UBBPd can work with a maximum of eight LBBPs or UBBPs for
CA. An LBBPc can work with a maximum of three LBBPs or UBBPs for CA.
Routes can be set up between a PCell and a maximum of eight cells for CA. If a cell
on an LBBPc is configured as the PCell for a UE, this cell can be accompanied by a
smaller number of SCells: four 20 MHz SCells, six 15 MHz SCells, or eight 10
MHz SCells.
This configuration mode uses intra- or inter-eNodeB dynamic routing and therefore
introduces certain delay in SCell configuration. In addition, this mode causes
overheads on the radio interface because inter-frequency measurements are required
for an eNodeB to select candidate SCells.
l For adaptive configuration, note the precautions taken for frequency-based configuration
and the following:
eNodeBs will not perform PCC anchoring or SCell configuration for the UEs. For
details about how to set parameters for identifying defective UEs and defining
differentiated handling policies, see Terminal Awareness Differentiation.
When an eNodeB is restarted, all served cells are reactivated and may be randomly distributed
on BBPs. It is possible that inter-frequency cells for CA are all re-established on LBBPc
boards. In this case, CA does not work between these cells. To prevent this, you are advised to
set a fixed mapping between cells and slots. The procedure is as follows:
6.4.5 Activation
6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 6-3 or Table 6-4 in a summary data file,
which also contains other data for the new eNodeBs to be deployed. Then, import the
summary data file into the Configuration Management Express (CME) for batch
configuration.
For detailed instructions, see section "Creating eNodeBs in Batches" in the initial
configuration guide for the eNodeB, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 6-3 or Table 6-4 are contained in a scenario-
specific summary data file. In this situation, set the parameters in the MOs, and then
verify and save the file.
l Some MOs in Table 6-3 or Table 6-4 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press
F1 when a CME window is active, and select Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary
Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or
choose Area Management > Planned Area > Export Incremental Scripts (CME client
mode), to export and activate the incremental scripts.
----End
Step 2 In the displayed Create Planned Area dialog box, specify Planned area name, select the
eNodeB (for which CA is to be activated) on the Base Station tab page under Available NEs,
and click so that it is added to Selected NEs. Then, click OK.
NOTE
Step 3 Choose CME > Advanced > Feature Operation and Maintenance > Export Feature
Commission Data.
Step 4 In the displayed dialog box, click LTE in the Category drop-down list, and select the CA
feature to be activated, for example, LAOFD-001001 LTE-A Introduction. Then, click
Next.
Step 5 Under Available Base Stations in the dialog box, select the eNodeB whose data is to be
exported. Click so that the eNodeB is added to Selected Base Stations. Then, click
Next.
Step 6 In the dialog box, set Export as to the format (.xls or .xlsm) in which the exported data is to
be saved. Click to the right of Export path to specify the save path. Then, click Next.
Step 7 Wait until the data is exported.
Step 8 Click the hyperlink to the save path. Alternatively, click Finish, and locate the exported file in
the save path.
Step 9 Set CA parameters in the CA data file (for example, LAOFD-001001.xls) in the save path. In
the CA data file, you can click an MO on the Home sheet and set the parameters on the
displayed sheet based on the network plan.
Step 10 After setting the parameters, choose CME > Advanced > Feature Operation and
Maintenance > Import Feature Commission Data on the U2000 client. In the displayed
dialog box, select the CA data file, and click Next.
Step 11 Wait until the file is imported. Leave the Export incremental script check box selected
(default setting). Click Finish.
Step 12 In the displayed dialog box, check that the eNodeB is displayed in the Selected NEs area. Set
Encrypt script and Script Executor Operation. You are advised to set Script Executor
Operation to Launch script executor and activate exported project so that the script will
be executed as soon as it is loaded. Then, click OK.
Step 13 In the displayed confirmation dialog box, click Yes. Data synchronization starts for the
eNodeB. When Success is displayed in the Result column, the CA feature has been activated.
----End
NOTE
After all the preceding steps are finished, you can run specific MML commands to verify that the
parameter settings take effect.
Configuration Procedure
CA-Group-based Configuration
The following actions are required to activate CA by using man-machine language (MML)
commands: (1) setting the CA algorithm switches; (2) adding a CA group; (3) adding cells
into the CA group.
If the local cells are active, CA is enabled after the local cells are added into the CA group. If
the local cells are inactive, activate them after adding them into the CA group. If the SCell
priority and blind SCell configuration flag are required, SCC configurations must be added to
the eNodeB involved in CA.
The activation procedure is as follows:
Step 1 Run the MOD ENODEBALGOSWITCH command to set the switches under CA
Algorithm Switch. Ensure that FreqCfgSwitch is off.
Step 2 Run the ADD CAGROUP command to add a CA group on the eNodeB and set the CA group
attribute.
Step 3 Run the ADD CAGROUPCELL command repeatedly to add at least two cells to the CA
group. In this step, set the PCell priority and the threshold for event A4 for each cell. You can
set either identical or different parameter values for the cells.
Step 4 (Optional. If you skip this step, the default parameter settings apply.) Run the ADD
CAGROUPSCELLCFG command to configure a candidate SCell for a cell that acts as the
PCell. In this step, set the SCell priority, blind SCell configuration flag, threshold for event
A4, and threshold for event A2 for the candidate SCell. You can set either identical or
different parameter values for the cells.
Step 5 (Optional; not required for a cell that has already been activated.) Run the ACT CELL
command to activate the cells.
----End
Frequency-based Configuration
The following actions are required to activate CA by using MML commands: (1) setting the
CA algorithm switches; (2) adding candidate PCCs; (3) adding candidate SCCs.
The activation procedure is as follows:
Step 1 Run the MOD ENODEBALGOSWITCH command to set the switches under CA
Algorithm Switch. Ensure that FreqCfgSwitch is on and AdpCaSwitch is off.
Step 2 Run the ADD PCCFREQCFG command to add candidate PCCs and set their attributes. You
can set either identical or different parameter values for the CCs.
Step 3 Run the ADD SCCFREQCFG command to add at least one candidate SCC and set its
attributes for each candidate PCC. You can set either identical or different parameter values
for the CCs.
Step 4 (Optional; not required for a cell that has already been activated.) Run the ACT CELL
command to activate the cells.
----End
Adaptive Configuration
The following actions are required to activate CA by using MML commands: (1) setting the
CA algorithm switches; (2) adding candidate PCCs; (3) adding candidate SCCs; (4) setting
blind-configurable candidate SCells.
The activation procedure is as follows:
Step 1 Run the MOD ENODEBALGOSWITCH command to set the switches under CA
Algorithm Switch. Ensure that FreqCfgSwitch and AdpCaSwitch are both on.
Step 2 Run the ADD PCCFREQCFG command to add candidate PCCs and set their attributes. You
can set either identical or different parameter values for the CCs.
Step 3 Run the ADD SCCFREQCFG command to add at least one candidate SCC and set its
attributes for each candidate PCC. You can set either identical or different parameter values
for the CCs.
Step 4 (Optional. If you skip this step, the default parameter settings apply.) Run the ADD
CAGROUPSCELLCFG command to configure a cell on a candidate SCC as a candidate
SCell for a cell (acting as a PCell) on a candidate PCC. In this step, set the SCell Blind
Configuration Flag parameter to TRUE(TRUE). You can repeat this step to set one blind-
configurable candidate SCell for one cell on each candidate PCC.
Step 5 (Optional; not required for a cell that has already been activated.) Run the ACT CELL
command to activate the cells.
----End
//Configuring SCells
ADD
CAGROUPSCELLCFG:LOCALCELLID=0,SCELLENODEBID=1234,SCELLLOCALCELLID=1,SCELLBLINDCFGF
LAG=TRUE,SCELLPRIORITY=2,SCELLA4OFFSET=10,SCELLA2OFFSET=-10;
ADD
CAGROUPSCELLCFG:LOCALCELLID=1,SCELLENODEBID=1234,SCELLLOCALCELLID=0,SCELLBLINDCFGF
LAG=TRUE,SCELLPRIORITY=3,SCELLA4OFFSET=20,SCELLA2OFFSET=-15;
//Activating cells
ACT CELL: LOCALCELLID=0;
ACT CELL: LOCALCELLID=1;
Frequency-based Configuration
//Adding a candidate SCC for each candidate PCC and setting SCC attributes
ADD
SCCFREQCFG:PCCDLEARFCN=123,SCCDLEARFCN=567,SCCPRIORITY=2,SCCA2OFFSET=-10,SCCA4OFFS
ET=-5;
ADD
SCCFREQCFG:PCCDLEARFCN=456,SCCDLEARFCN=789,SCCPRIORITY=3,SCCA2OFFSET=-20,SCCA4OFFS
ET=-10;
//Activating cells
ACT CELL: LOCALCELLID=0;
ACT CELL: LOCALCELLID=1;
Adaptive Configuration
//Adding a candidate SCC for each candidate PCC and setting SCC attributes
ADD
SCCFREQCFG:PCCDLEARFCN=123,SCCDLEARFCN=567,SCCPRIORITY=2,SCCA2OFFSET=-10,SCCA4OFFS
ET=-5;
ADD
SCCFREQCFG:PCCDLEARFCN=456,SCCDLEARFCN=789,SCCPRIORITY=3,SCCA2OFFSET=-20,SCCA4OFFS
ET=-10;
//Activating cells
ACT CELL: LOCALCELLID=0;
ACT CELL: LOCALCELLID=1;
Counter
After CA is enabled, the eNodeB configures SCells for CA UEs when the required conditions
are met. Observe the counters listed in the following table to obtain PCell and SCell statistics.
If both L.Traffic.User.SCell.DL.Avg and L.ChMeas.PRB.DL.SCell.Used.Avg produce non-
zero values, CA has been activated successfully. If the values of both counters remain at zero
and CA UEs exist in the network, CA has not been activated.
Message Tracing
After a CA UE accesses a cell, the eNodeB configures a cell that meets CA conditions as an
SCell for the UE. When traffic conditions are met, the eNodeB activates this SCell. The
U2000 client may be used or a drive test (for example, using Probe) may be conducted to
observe configuration and activation of this SCell. If an RRC_CONN_RECFG message for
configuring an SCell is observed on a network that serves CA UEs, CA has been activated
successfully.
Observing SCell Configuration on the U2000 Client
Step 1 Log in to the U2000 client, and then choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree on the left of the Signaling Trace Management tab
page, choose Trace Type > LTE > Application Layer > Uu Interface Trace.
Step 2 Select an NE, set tracing task parameters, and then click Finish to start signaling tracing.
Step 3 Check the tracing result for the RRC_CONN_RECFG message. The eNodeB configures or
removes an SCell for the CA UE by using an RRC_CONN_RECFG message that contains the
IE sCellToAddModList or sCellToReleaseList, as shown in Figure 6-2 or Figure 6-3,
respectively.
----End
Step 1 Log in to the U2000 client, and then choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree on the left of the Signaling Trace Management tab
page, choose Trace Type > LTE > User Performance Monitoring > Throughput
Monitoring.
Step 2 Select an NE, click Next, and then specify MMEc and mTMSI. Click Finish to start tracing.
Step 3 Observe the tracing result. If downlink MAC throughput is not 0 for both the PCell and the
SCell, as shown in Figure 6-4, the SCell has been activated.
----End
Start Probe and connect it to the CA UE, as shown in Figure 6-5, Figure 6-6 and Figure 6-7.
If the CA UE is allocated radio resources on both the PCC and the SCC and has MAC
throughput on the SCC, as shown in Figure 6-8 and Figure 6-9, the SCell has been
configured and activated for the UE. If the CA UE is not allocated radio resources on the
SCC, the feature activation has failed.
Figure 6-8 Successful SCell configuration and activation (radio resources allocated on both
the PCC and the SCC)
Figure 6-9 Successful SCell configuration and activation (MAC throughput on the SCC)
6.4.7 Deactivation
Configuration Procedure
CA-Group-based Configuration
To deactivate CA-group-based CA by using MML commands, perform the following steps:
----End
Frequency-based Configuration
To deactivate frequency-based CA by using MML commands, perform the following steps:
----End
Adaptive Configuration
To deactivate adaptive CA by using MML commands, perform the following steps:
Step 1 Turn off the subordinate switches of the CA algorithm switch, including the adaptive CA
switch.
Step 2 Remove SCC configurations.
----End
Frequency-based Configuration
//Turning off the subordinate switches of the CA algorithm switch
MOD
ENODEBALGOSWITCH:CAALGOSWITCH=PdcchOverlapSrchSpcSwitch-1&CaCapbFiltSwitch-0&PccAn
chorSwitch-0&SccBlindCfgSwitch-0&FreqCfgSwitch-0&SccA2RmvSwitch-1&CaTrafficTrigger
Switch-0&HoWithSccCfgSwitch-0&SccModA6Switch-0&GbrAmbrJudgeSwitch-0;
Adaptive Configuration
//Turning off the subordinate switches of the CA algorithm switch, including the adaptive CA
switch
MOD
ENODEBALGOSWITCH:CAALGOSWITCH=PdcchOverlapSrchSpcSwitch-1&CaCapbFiltSwitch-0&PccAn
chorSwitch-0&SccBlindCfgSwitch-0&FreqCfgSwitch-0&SccA2RmvSwitch-1&CaTrafficTrigger
Switch-0&HoWithSccCfgSwitch-0&SccModA6Switch-0&GbrAmbrJudgeSwitch-0&AdpCaSwitch-0;
Specifically:
1526728517 L.Traffic.User.SCell.DL.Max
1526728427 L.Traffic.User.SCell.DL.Avg
1526728425 L.ChMeas.PRB.DL.SCell.Used.
Avg
Common Parameters
The following table describes the parameters that are common to all CA configuration modes.
SCC CaMgtCfg. This parameter specifies the CQI threshold used User-
Disabl Scc to evaluate the deactivation of an SCell for a defined
e CQI DeactCqiThd CA UE based on channel quality. If the channel
Thresh quality of the CA UE is lower than the channel
old quality corresponding to the CQI threshold in
single-codeword transmission, the eNodeB
deactivates the SCell. If this parameter is set to
0, the eNodeB does not deactivate SCells based
on channel quality. The value 5 is
recommended.
l The higher the threshold, the higher the
probability of deactivating the SCell.
l The lower the threshold, the lower the
probability of deactivating the SCell.
To maintain active SCells only when channel
quality is high, increase the value of this
parameter.
FDD ENodeBFram This parameter specifies the offset of the frame User-
Frame eOffset. start time for all LTE FDD cells served by the defined
Offset Fdd eNodeB relative to the time of the reference
FrameOffset clock.
FDD CA and FDD+TDD CA require time
synchronization between the cells involved. An
identical frame offset must be set for all the
cells. Otherwise, FDD CA or FDD+TDD CA
does not work.
Set this parameter based on the network plan.
TDD ENodeBFram This parameter specifies the offset of the frame User-
Frame eOffset. start time for all LTE TDD cells served by the defined
Offset Tdd eNodeB relative to the time of the reference
FrameOffset clock.
If uplink and downlink timeslots are not aligned
between TDD systems, inter-system
interference may occur. You can adjust this
parameter to minimize the error in timeslot
alignment between the TDD systems.
Set this parameter based on the network plan.
Frame CellFrameOff This parameter specifies the type of the frame User-
Offset set. offset for the cell. There are three options: defined
Mode Fra l CustomFrameOffset(Cell Frame Offset):
meOffsetMode indicates a user-defined frame offset. This is
the only value of this parameter that applies
to FDD cells.
l TL_FrameOffset(T-L Dual Mode frame
offset): indicates the frame offset
automatically determined based on the
subframe configuration in a TD-SCDMA +
LTE TDD dual-RAT network.
l TL_FrameOffset_SA2_SSP5(T-L Dual
Mode SA2+SSP5 frame offset): indicates
the frame offset automatically determined
based on uplink-downlink configuration 2
and special subframe configuration 5 in a
TD-SCDMA + LTE TDD dual-RAT
network.
Set this parameter based on the network plan.
Frame CellFrameOff This parameter specifies the offset of the frame User-
Offset set. start time for the cell relative to the time of the defined
Fra reference clock.
meOffset Set this parameter based on the network plan.
CA-Group-based Configuration
The following table describes the parameters specific to CA-group-based configuration.
PCell CaGroupCell. This parameter specifies the RSRP threshold for User-
A4 PCellA4RsrpT CA event A4 during PCC anchoring. If the defined
RSRP hd measured RSRP of an inter-frequency
Thresh neighboring cell is greater than this parameter
old value, the CA UE reports event A4.
l The greater the value, the lower the
probability of an inter-frequency handover
for PCC anchoring.
l The smaller the value, the higher the
probability of an inter-frequency handover
for PCC anchoring. However, if the value is
too small, the handover may fail.
To shrink the area where the cell is the PCC
anchor, increase the value of this parameter.
SCell CaGroupSCel This parameter specifies the offset of the actual User-
A4 lCfg. threshold for CA event A4 relative to the defined
Offset SCe CaMgtCfg.CarrAggrA4ThdRsrp parameter
llA4Offset value. When the cell specified by the
LocalCellId parameter serves as the PCell,
event A4 is triggered if the candidate SCell
specified by the SCelleNodeBId and
SCellLocalCellId parameters meets the event
triggering condition.
l The greater the value, the higher the actual
threshold for CA event A4, and the lower
the probability of configuring an SCell.
l The smaller the value, the lower the actual
threshold for CA event A4, and the higher
the probability of configuring an SCell.
To adjust the CA event A4 threshold for
different SCells, set this parameter according to
operators' policies.
SCell CaGroupSCel This parameter specifies the offset of the actual User-
A2 lCfg. threshold for CA event A2 relative to the defined
Offset SCe CaMgtCfg.CarrAggrA2ThdRsrp parameter
llA2Offset value. When the cell specified by the
LocalCellId parameter serves as the PCell,
event A2 is triggered if the SCell specified by
the SCelleNodeBId and SCellLocalCellId
parameters meets the event triggering condition.
l The greater the value, the higher the actual
threshold for CA event A2, and the higher
the probability of removing an SCell.
l The smaller the value, the lower the actual
threshold for CA event A2, and the lower
the probability of removing an SCell.
To adjust the CA event A2 threshold for
different SCells, set this parameter according to
operators' policies.
PCC PccFreqCfg. This parameter specifies the RSRP threshold for User-
A4 Pcc CA event A4 during PCC anchoring. defined
RSRP A4RsrpThd l The greater the value, the lower the
Thresh probability of an inter-frequency handover
old for PCC anchoring.
l The smaller the value, the higher the
probability of an inter-frequency handover
for PCC anchoring. However, if the value is
too small, the handover may fail.
To shrink the area where the carrier is the PCC
anchor, increase the value of this parameter.
PCC PccFreqCfg. This parameter specifies the RSRQ threshold for User-
A4 Pcc CA event A4 during PCC anchoring. If the defined
RSRQ A4RsrqThd measured RSRQ of an inter-frequency
Thresh neighboring cell is greater than this parameter
old value, the CA UE reports event A4.
l The greater the value, the lower the
probability of an inter-frequency handover
for PCC anchoring.
l The smaller the value, the higher the
probability of an inter-frequency handover
for PCC anchoring. However, if the value is
too small, the handover may fail.
To shrink the area where the carrier is the PCC
anchor, increase the value of this parameter.
SCC SccFreqCfg. This parameter specifies the priority with which User-
Priority Scc the candidate SCC works as an SCC for the defined
Priority PCC.
l The smaller the value, the lower the priority
level.
l The greater the value, the higher the priority
level.
To raise the probability that CA UEs treat the
carrier as their SCC, increase the value of this
parameter.
SCC SccFreqCfg. This parameter specifies the offset of the actual User-
A2 Scc threshold for CA event A2 relative to the defined
Offset A2Offset CaMgtCfg.CarrAggrA2ThdRsrp parameter
value. If the sum of the offset and
CaMgtCfg.CarrAggrA2ThdRsrp is greater
than 43 dBm or less than 140 dBm, the
actual threshold for CA event A2 takes the value
43 dBm or 140 dBm, respectively.
l The greater the value, the higher the actual
threshold for CA event A2, and the higher
the probability of removing an SCell.
l The smaller the value, the lower the actual
threshold for CA event A2, and the lower the
probability of removing an SCell.
To adjust the CA event A2 threshold for
different SCCs, set this parameter according to
operators' policies.
SCC SccFreqCfg. This parameter specifies the offset of the actual User-
A4 Scc threshold for CA event A4 relative to the defined
Offset A4Offset CaMgtCfg.CarrAggrA4ThdRsrp parameter
value. If the sum of the offset and
CaMgtCfg.CarrAggrA4ThdRsrp is greater
than 43 dBm or less than 140 dBm, the
actual threshold for CA event A4 takes the value
43 dBm or 140 dBm, respectively.
l The greater the value, the higher the actual
threshold for CA event A4, and the lower the
probability of configuring an SCell.
l The smaller the value, the lower the actual
threshold for CA event A4, and the higher
the probability of configuring an SCell.
To adjust the CA event A4 threshold for
different SCCs, set this parameter according to
operators' policies.
SCell CaMgtCfg. This parameter specifies the length of the aging User-
Aging SC time for SCells that are dynamically configured defined
Time ellAgingTime for CA. If CA does not occur on a pair of cells
throughout the aging time, the eNodeB cancels
the CA relationship between the cells.
l The greater the value, the lower the
probability of canceling the CA relationship.
l The smaller the value, the higher the
probability of canceling the CA relationship.
To reduce the number of outdated SCells that
were dynamically configured, increase the value
of this parameter.
NOTE
If the value of this parameter is decreased, the SCells
whose aging time has exceeded the new value before
the change will be removed soon.
Carrier CaMgtCfg. This parameter specifies the offset for CA event User-
Aggreg Car A6, which is triggered when the signal quality defined
ation rAggrA6Offset of a neighboring cell is higher than that of an
A6 SCell.
Offset l The greater the value, the lower the
probability of changing the SCell based on
event A6.
l The smaller the value, the higher the
probability of changing the SCell based on
event A6.
To raise the signal quality requirement for SCell
changes, increase the value of this parameter.
6.7 Troubleshooting
Alarm-triggered eNodeB Operations
(1) Carrier or Cell Unavailable
If an alarm listed in the preceding table is reported as indicating a hardware fault or cell
unavailability, the eNodeB performs the following fallback operations:
l If the faulty cell has been configured as an SCell of a CA UE, the eNodeB sends an RRC
Connection Reconfiguration message to remove the SCell for the UE. If the faulty cell
has not been configured as an SCell of any CA UE, the eNodeB does not send an RRC
Connection Reconfiguration message to configure the cell as an SCell for any CA UE.
l If the faulty cell is the PCell of a CA UE, the CA UE may encounter service drops or
service unavailability.
(2) Clock Synchronization Capability Degraded
If the clock synchronization capability deteriorates because of a clock or hardware fault, the
eNodeB reports the alarm listed in the preceding table, and the following impact is generated:
l SCells cannot be configured for CA UEs that access the faulty eNodeB in scenarios of
initial access, handovers, or RRC connection re-establishments.
l Other eNodeBs cannot configure cells in the faulty eNodeB as SCells.
l SCells are removed for the CA UEs that treat cells served by the faulty eNodeB as their
PCells or SCells.
Handle the alarm according to the alarm reference. If the fault is rectified, CA services are
restored as follows:
l SCells can be configured for CA UEs that access the eNodeB in scenarios of initial
access, handovers, or RRC connection re-establishments.
l Functioning eNodeBs can configure cells in the originally faulty eNodeB as SCells.
Fault Description
After CA is enabled, the CA-related counters provided in 6.5 Performance Monitoring
retain the value of 0.
Fault Handling
If CA works in CA-group-based configuration mode, perform the following steps on the
U2000 client:
Step 1 Run the LST ENODEBALGOSWITCH command to check whether FreqCfgSwitch under
CA Algorithm Switch is off.
l If the switch is off, go to Step 3.
l If the switch is on, go to Step 2.
Step 3 Check whether ALM-26200 Board Hardware Fault or ALM-29240 Cell Unavailable is
reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values. If the counters
produce non-zero values, no further action is required. If the counters retain the value of
0, go to Step 4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the DSP CAGROUPCELL command to check the running status of all CA groups
configured on the eNodeB. The running status includes information such as whether the link
between cells in one CA group is normal, whether related licenses work normally, and
whether the CA configuration state is normal.
l If the running status is normal, go to Step 5.
l If any status is abnormal, rectify the fault. Then, check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values. If the counters
produce non-zero values, no further action is required. If the counters retain the value of
0, go to Step 5.
Step 5 Run the LST CAGROUPSCELLCFG command to check whether candidate SCells are
correctly configured in the eNodeB.
l If the configurations are correct, go to Step 6.
l If they are incorrectly configured, correct the configurations by following the
instructions described in 6.4 Deployment. Then, check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values. If the counters
produce non-zero values, no further action is required. If the counters retain the value of
0, go to Step 6.
Step 6 If CA-related hardware and data configurations are correct, check whether the fault is due to
no UE access to the network.
1. Start a Uu interface tracing task as follows: Choose Monitor > Signaling Trace >
Signaling Trace Management. In the navigation tree on the left of the Signaling Trace
Management tab page, choose LTE > Application Layer > Uu Interface Trace. Select
an NE, set tracing task parameters, and then click Finish to start signaling tracing.
2. Run the MOD ENODEBALGOSWITCH command with
SccBlindCfgSwitch(SccBlindCfgSwitch) under the CA Algorithm Switch parameter
selected, and run the ADD CAGROUPSCELLCFG command with SCell Blind
Configuration Flag set to TRUE(TRUE) for all candidate SCells associated with the
PCell. Enable a CA UE to access the network. Check the Uu interface tracing results for
an RRC_CONN_RECFG message.
If CA-related counters provided in 6.5 Performance Monitoring produce non-zero
values, these counters had the value of 0 because there was no CA UE on the
network. No further action is required.
If the RRC_CONN_RECFG message indicates that the eNodeB configures a
candidate cell as an SCell for the UE, but the CA-related counters in 6.5
Performance Monitoring still retain the value of 0, contact Huawei engineers.
If the eNodeB does not deliver an RRC_CONN_RECFG message to configure an
SCell for the UE, contact Huawei engineers.
----End
Step 1 Run the LST ENODEBALGOSWITCH command to check whether the required switch
(FreqCfgSwitch or AdpCaSwitch) under CA Algorithm Switch is on.
l If the switch is on, go to Step 3.
l If the switch is off, go to Step 2.
Step 3 Check whether ALM-26200 Board Hardware Fault or ALM-29240 Cell Unavailable is
reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values. If the counters
produce non-zero values, no further action is required. If the counters retain the value of
0, go to Step 4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the LST PCCFREQCFG and LST SCCFREQCFG commands to check whether PCC
and SCC configurations are correct.
l If the configurations are correct, go to Step 5.
l If the configurations are incorrect, correct them by following the instructions described
in 6.4 Deployment. Then, check whether the CA-related counters provided in 6.5
Performance Monitoring produce non-zero values. If the counters produce non-zero
values, no further action is required. If the counters retain the value of 0, go to Step 5.
Step 5 Run the LST EUTRANINTERNFREQ command and view Downlink EARFCN in the
command output to check whether candidate SCCs are correctly configured as neighboring
frequencies of each cell.
l If the configurations are correct, go to Step 6.
l If the configurations are incorrect, run the MOD EUTRANINTERNFREQ command
to correct them. Then, check whether the CA-related counters provided in 6.5
Performance Monitoring produce non-zero values. If the counters produce non-zero
values, no further action is required. If the counters retain the value of 0, go to Step 6.
Step 6 Run the DSP PCCSCELLLIST command and view PCC Downlink EARFCN and SCC
Downlink EARFCN in the command output to check whether the number of SCells
dynamically configured for each cell has reached eight.
l If the number has reached eight, wait 15 minutes and check again. If the check finds that
CA takes effect, no further action is required. If CA still does not work, contact Huawei
engineers.
l If the number is less than eight, go to Step 7.
Step 7 Run the MOD CAMGTCFG command with Carrier Aggregation A4 RSRP threshold set
to -140. Run the DSP PCCSCELLLIST command to check the SCells dynamically
configured for the PCell.
l If SCells are displayed in the command output, enable a CA UE to access the network in
the overlapping area of the PCell identified by PCC Local Cell ID and one of the SCells
identified by SCC Local Cell ID.
l If no SCell is displayed in the command output, enable a CA UE to access the network in
the overlapping area of the PCell and a potential SCell.
Step 8 Start Uu interface tracing. When the CA UE accesses the network, observe as follows:
l If CA-related counters provided in 6.5 Performance Monitoring produce non-zero
values, these counters had the value of 0 because there was no CA UE on the network.
No further action is required.
l If the RRC_CONN_RECFG message indicates that the eNodeB configures an SCell for
the UE, but the CA-related counters in 6.5 Performance Monitoring still retain the
value of 0, contact Huawei engineers.
l If the eNodeB does not deliver an RRC_CONN_RECFG message to configure an SCell
for the UE, contact Huawei engineers.
----End
7.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
l If the live network uses multiple frequency bands, no frequency needs to be added to the
network plan.
l If the live network uses only one or two frequencies, deploy more frequencies.
Hardware Planning
For details about hardware planning, see 6.3 Planning.
7.4 Deployment
Deploy this CA feature on a network with at least three operating frequencies. For details
about how to deploy a multi-carrier network, see Cell Management.
7.4.1 Requirements
Operating Environment, NEs, and Transmission Networking
The requirements described in 6.4.1 Requirements must be fulfilled. In addition, the EPC
must meet the following requirement:
To allow 2CC aggregation to reach a peak data rate of 300 Mbit/s in 2x2 MIMO scenarios, the
maximum bit rate that the UE subscribes to in the EPC must be greater than or equal to 300
Mbit/s.
License
Deploying LAOFD-070201 Flexible CA from Multiple Carriers requires the following
licenses:
l In CA-group-based configuration mode
In a CA group with more than two cells, each cell requires one sales unit of the license
for LAOFD-070201 Flexible CA from Multiple Carriers and one sales unit of the license
for LAOFD-001001 LTE-A Introduction.
If the total bandwidth of a cell and any other cell in the CA group is between 20 MHz
and 40 MHz (including 40 MHz), the cell requires one sales unit of the license for
LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.
NOTE
l If any license is insufficient, a CA group with cells added does not take effect. However, the
original CA group still works. In this case, the eNodeB reports ALM-26819 Data
Configuration Exceeding Licensed Limit.
l If the license for LAOFD-070201 Flexible CA from Multiple Carriers is insufficient in an
eNodeB and FreqCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is set
on and then off, none of the cells in a CA group that includes more than two cells takes effect.
In addition, the eNodeB reports ALM-26819 Data Configuration Exceeding Licensed Limit.
l In frequency-based or adaptive configuration mode
If a cell and its intra-BBU CA partners (either PCell or SCell) form a cell set that covers
three or more frequencies, the cell requires one sales unit of the license for
LAOFD-070201 Flexible CA from Multiple Carriers and one sales unit of the license for
LAOFD-001001 LTE-A Introduction.
If the total bandwidth of a cell and any other cell in the set is between 20 MHz and 40
MHz (including 40 MHz), the cell requires one sales unit of the license for
LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.
Others
The prerequisite features for LAOFD-070201 Flexible CA from Multiple Carriers must be
activated.
7.4.3 Precautions
For details, see 6.4.3 Precautions.
7.4.5 Activation
l In CA-group-based configuration mode, perform the MML-based procedure described in
6.4.5 Activation with the following exceptions: Add three cells to the CA group in step
3, and configure two candidate SCells for each PCell in step 4.
l In frequency-based or adaptive configuration mode, perform the MML-based procedure
described in 6.4.5 Activation with the following exception: Add at least two candidate
SCCs and set their attributes for each candidate PCC in step 3.
7.4.7 Deactivation
l In CA-group-based configuration mode, perform step 3 of the MML-based configuration
described in 6.4.7 Deactivation to delete one cell from a CA group so that the CA group
includes only two cells.
l In frequency-based configuration mode, perform step 1 of the MML-based configuration
described in 6.4.7 Deactivation to delete candidate SCCs so that each PCC is
accompanied by only one candidate SCC.
l In adaptive configuration mode, perform step 2 of the MML-based configuration
described in 6.4.7 Deactivation to delete candidate SCCs so that each PCC is
accompanied by only one candidate SCC.
7.7 Troubleshooting
For details, see 6.7 Troubleshooting.
8.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
Deploy multi-BBU interconnection, in addition to network planning described in 6.3
Planning.
Hardware Planning
Use LBBPd or UBBP as baseband processing units. Do not use LBBPc or UMDUa3. For the
antenna modes of cells supported by LBBPd and UBBP boards, see hardware planning
described in 6.3 Planning.
8.4 Deployment
CA works between two or three inter-frequency cells.
8.4.1 Requirements
Operating Environment
None
NEs
In addition to the requirements described in 6.4.1 Requirements, CA in centralized multi-
BBU interconnection scenarios has the following requirements:
l A USU is required for data exchange between BBUs.
l The same software version runs on the BBUs to be interconnected.
l LMPT and LBBPc cannot be used for USU-based multi-BBU interconnection.
Transmission Networking
The BBUs must be time-synchronized.
License
Deploying LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU requires the
following licenses:
l In CA-group-based configuration mode, each eNodeB on which any CA group includes
an inter-eNodeB cell requires one sales unit of the license for LAOFD-070202 Inter-
eNodeB CA based on Coordinated BBU.
l In frequency-based or adaptive configuration mode, if FreqCfgCaOverBBUsSwitch
under ENodeBAlgoSwitch.OverBBUsSwitch is on, each eNodeB on which any cell is
accompanied by an inter-BBU SCell requires one sales unit of the license for
LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.
In addition, each cell involved in CA requires one sales unit of the license for
LAOFD-001001 LTE-A Introduction and, if the total bandwidth of the cells is greater than 20
MHz and less than or equal to 40 MHz, one sales unit of the license for LAOFD-001002
Carrier Aggregation for Downlink 2CC in 40MHz.
Others
The prerequisite features for LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
must be activated.
NOTE
8.4.3 Precautions
In addition to the precautions described in 6.4.3 Precautions, a penalty mechanism applies to
eX2 route setups. If three consecutive attempts of an eNodeB to set up an eX2 route to an
inter-BBU cell fail, the eNodeB prohibits the subsequent 30 attempts on the route.
8.4.5 Activation
CA-Group-based Configuration
l If the network is deployed using the centralized multi-BBU interconnection architecture,
perform the operations described in 6.4.5 Activation on each BBU.
l If the network is deployed using the distributed multi-BBU interconnection architecture,
perform the operations described in 6.4.5 Activation on each BBU and run the following
command for the serving eNodeB of each candidate PCell to set
DistributeCloudbbCaSwitch on:
MOD ENODEBALGOSWITCH:CAALGOSWITCH=DistributeCloudbbCaSwitch-1;
Run the following command on the serving eNodeB of each candidate PCC to set
DistributeCloudbbCaSwitch on:
MOD ENODEBALGOSWITCH:CAALGOSWITCH=DistributeCloudbbCaSwitch-1;
8.4.7 Deactivation
CA-Group-based Configuration
l If the network is deployed using the centralized multi-BBU interconnection architecture,
delete inter-BBU cells from each CA group on a BBU. Inter-BBU cells have different
eNodeB IDs from the local BBU. The following is an example of the command:
RMV CAGROUPCELL:CAGROUPID=0,LOCALCELLID=0,ENODEBID=1234;
8.7 Troubleshooting
Troubleshooting described in 6.7 Troubleshooting applies to LAOFD-070202 Inter-eNodeB
CA based on Coordinated BBU with only an exception at step 4 in the fault handling
procedure for CA in CA-group-based configuration mode. In step 4, run the command on
each BBU to check whether the configurations are consistent between the eNodeBs.
l If the configurations are consistent, go to step 5.
l If the configurations are inconsistent, follow the instructions described in 6.4.5.5 Using
MML Commands to configure CaGroupCell MOs to be consistent between the BBUs.
Then, check whether the CA-related counters provided in 6.5 Performance Monitoring
produce non-zero values. If the counters produce non-zero values, no further action is
required. If the counters retain the value of 0, go to step 5.
9.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
In addition to network planning described in 6.3 Planning, make the network plan to ensure
that the inter-eNodeB cells are reachable through routes.
Hardware Planning
In addition to the hardware planning described in 6.3 Planning, select hardware with the
following requirements taken into consideration:
9.4 Deployment
Deploy this CA feature on inter-eNodeB inter-frequency cells.
9.4.1 Requirements
Operating Environment
None
NEs
For details, see 6.4.1 Requirements.
Transmission Networking
l The eNodeBs must be time-synchronized. Downlink CA requires a time synchronization
accuracy of 1.5 s, which can be achieved, for example, by deploying a GPS or
IEEE1588 V2 clock source.
l The eNodeBs must meet the following transmission requirements.
Scenario Average Average Jitter (ms) Packet Loss Rate
One-way Round (%)
Delay (ms) Trip Time
(ms)
Best 4 8 0 0.0001
Recommende 4 8 1 0.001
d
Tolerable 4 8 2 0.5
NOTE
l If the transmission delay, jitter, or packet loss rate deteriorates, the data rate of relaxed-
backhaul-based inter-eNodeB CA UEs decreases.
l In tolerable scenarios, services can be successfully set up but their QoS requirements are not
necessarily fulfilled.
l The bandwidth of the link between the eNodeBs must meet the bandwidth requirement.
The required link bandwidth is given by the following formula: Bandwidth of the SCC x
Spectral efficiency of the SCC x Percentage of CA UEs on the SCC x Number of SCells
to be associated.
Take a 20 MHz SCC as an example. Each time the eNodeB that serves the PCell
associates an inter-eNodeB SCell with the PCell, a link bandwidth of 35 Mbit/s is
required if the uplink and downlink resources are planned to reach average spectral
efficiency and a CA UE percentage of 50%. The required link bandwidth is calculated as
follows: 20 x 3.5 x 50% x 1. However, if the uplink and downlink resources are planned
to reach the maximum spectral efficiency of 7.5 and a CA UE percentage of 100%, a link
bandwidth of 150 Mbit/s is required.
The preceding examples are two common cases. Operators can calculate their required
link bandwidths based on site conditions. In addition, considering transport protocol
overheads, a bandwidth margin of about 12% must be reserved. As a result, in the
example of 35 Mbit/s link bandwidth, the bandwidth to be configured is calculated as
follows: 35 x (1 + 12%) = 39 Mbit/s.
NOTE
If an insufficient bandwidth is configured, packet loss will occur on the eX2 interface, affecting
the data rate of UEs in the relaxed-backhaul-based inter-eNodeB CA state.
Inter-eNodeB CA based on relaxed backhaul requires that the inter-eNodeB cells be
reachable through routes. eX2 interfaces must be set up between the eNodeBs. If the
eNodeBs belong to the same operator and are managed by the same U2000, eX2 self-
setup works. If the eNodeBs belong to different operators or are managed by different
U2000s, SCTP links and end-point groups must be manually configured for eX2
interfaces. For details about the configuration, see eX2 Self-Management.
License
Deploying LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul requires the
licenses listed in this section.
When RelaxedBackhaulCaSwitch under ENodeBAlgoSwitch.CaAlgoSwitch is on:
l In CA-group-based configuration mode, the serving eNodeB of each cell in a CA group
that includes relaxed-backhaul-based inter-eNodeB cells requires one sales unit of the
license for LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul. In addition,
each cell involved in CA requires one sales unit of the license for LAOFD-001001 LTE-
A Introduction and, if the total bandwidth of the cells is greater than 20 MHz and less
than or equal to 40 MHz, one sales unit of the license for LAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz.
l In frequency-based or adaptive configuration mode, if any cell served by an eNodeB acts
as a PCell and is accompanied by an inter-eNodeB SCell for relaxed-backhaul-based
CA, each of the eNodeBs requires one sales unit of the license for LAOFD-080201 Inter-
eNodeB CA based on Relaxed backhaul. In addition, each cell involved in CA requires
one sales unit of the license for LAOFD-001001 LTE-A Introduction and, if the total
bandwidth of the cells is greater than 20 MHz and less than or equal to 40 MHz, one
sales unit of the license for LAOFD-001002 Carrier Aggregation for Downlink 2CC in
40MHz.
Feature Feature Model License Control NE Sales
ID Name Item Unit
Others
The prerequisite features for the CA feature must have been enabled.
9.4.3 Precautions
In addition to the precautions described in 6.4.3 Precautions, note that:
9.4.5 Activation
In addition to the steps in 6.4.5 Activation, set the required switches on as described in this
section.
2. Run the MOD ENODEBALGOSWITCH command on the micro eNodeB with both
the RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) and
HetNetCaSwitch(HetNetCaSwitch) options of the CA Algorithm Switch parameter
selected.
MOD ENODEBALGOSWITCH:CAALGOSWITCH=RelaxedBackhaulCaSwitch-1&HetNetCaSwitch-1;
In addition to counters, you can evaluate the feature performance by tracing signaling
messages. For details, see "Message Tracing" in 6.4.6 Activation Observation.
9.4.7 Deactivation
l Deactivating CA between inter-eNodeB macro cells
Run the MOD ENODEBALGOSWITCH command with the
RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) option of the CA Algorithm
Switch parameter deselected.
MOD ENODEBALGOSWITCH:CAALGOSWITCH=RelaxedBackhaulCaSwitch-0;
1526732955 L.Traffic.User.SCell.DL.R
elaxedBackhaulCA.Avg
1526732954 L.Traffic.User.SCell.DL.R
elaxedBackhaulCA.Max
1526732912 L.ChMeas.PRB.DL.SCell.
RelaxedBackhaul-
CAUsed.Avg
9.7 Troubleshooting
In addition to the troubleshooting methods described in 6.7 Troubleshooting, the following
method is available for troubleshooting inter-eNodeB CA based on relaxed backhaul:
Step 1 On the U2000 client, check whether ALM-25888 SCTP Link Fault or ALM-25952 User
Plane Path Fault is reported.
l If either alarm is reported, handle the alarm and then check whether the CA-related
counters provided in 6.5 Performance Monitoring produce non-zero values.
If the counters produce non-zero values, no further action is required.
If the counters retain the value of 0, go to step 2.
l If neither alarm is reported, go to step 2.
----End
10.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
For details about network planning, see 6.3 Planning.
Hardware Planning
In addition to hardware planning described in 6.3 Planning, select BBPs as follows:
10.4 Deployment
Deploy this CA feature on two inter-frequency cells served by either the same eNodeB or
different eNodeBs that are interconnected in multi-BBU interconnection scenarios.
10.4.1 Requirements
Operating Environment
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. In addition, the EPC
and UEs must meet the following requirement:
l To allow uplink 2CC aggregation to reach a peak data rate of 100 Mbit/s in 2x2 MIMO
scenarios, the maximum uplink and downlink bit rates that the UE subscribes to in the
EPC must be greater than or equal to 100 Mbit/s and 300 Mbit/s, respectively.
l UEs must comply with 3GPP Release 12 or later and support the frequency bands of the
carriers to be aggregated and their channel bandwidths.
Transmission Networking
For details, see 6.4.1 Requirements.
License
If CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter is on for a cell, the
cell can be used for uplink CA. LAOFD-080202 Carrier Aggregation for Uplink 2CC is a trial
feature in eRAN8.1 and therefore is not under license control. However, for this uplink CA
feature to take effect, downlink CA must be licensed:
l If the total bandwidth of the downlink aggregated cells is less than or equal to 20 MHz,
each cell requires one sales unit of the license for LAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the downlink aggregated cells is between 20 MHz and 40 MHz
(including 40 MHz), each cell requires one sales unit of the license for LAOFD-001001
LTE-A Introduction and one sales unit of the license for LAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz.
Others
The prerequisite features for the CA feature must have been enabled.
10.4.3 Precautions
For details, see 6.4.3 Precautions.
10.4.5 Activation
In addition to the steps in 6.4.5 Activation, perform the following steps on the U2000 client:
Step 1 Run the MOD CELLALGOSWITCH command with the
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) option of the Uplink schedule
switch parameter selected.
MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=SchedulerCtrlPowerSwitch-1;
Step 2 Run the MOD CAMGTCFG command with the CaUl2CCSwitch(CaUl2CCSwitch) option
of the Cell Level CA Algorithm Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaUl2CCSwitch-1;
----End
10.4.7 Deactivation
Step 1 On the U2000 client, run the MOD CAMGTCFG command with the
CaUl2CCSwitch(CaUl2CCSwitch) option of the Cell Level CA Algorithm Switch
parameter deselected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaUl2CCSwitch-0;
Step 2 (Optional) If uplink scheduler-based power control is not required, run the MOD
CELLALGOSWITCH command with the
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) option of the Uplink schedule
switch parameter deselected.
MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=SchedulerCtrlPowerSwitch-0;
----End
1526732895 L.Traffic.User.SCell.UL.
Max
10.7 Troubleshooting
For details, see 6.7 Troubleshooting.
l If the total bandwidth is less than or equal to 40 MHz, enable only LAOFD-080207
Carrier Aggregation for Downlink 3CC in 40MHz.
l If the total bandwidth is greater than 40 MHz and less than or equal to 60 MHz, enable
both LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz and
LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz.
11.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
For details about network planning, see 6.3 Planning.
Hardware Planning
In addition to hardware planning described in 6.3 Planning, select BBPs as follows:
11.4 Deployment
Deploy this CA feature on three inter-frequency cells served by either the same eNodeB or
different eNodeBs that are interconnected in multi-BBU interconnection scenarios.
11.4.1 Requirements
Operating Environment
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. Specifically:
l To allow downlink 3CC aggregation to reach a peak data rate of 450 Mbit/s in 2x2
MIMO scenarios, the maximum bit rate that the UE subscribes to in the EPC must be
greater than or equal to 450 Mbit/s.
l UEs must comply with 3GPP Release 12 or later and support the frequency bands of the
carriers to be aggregated and their channel bandwidths.
Transmission Networking
For details, see 6.4.1 Requirements.
License
A cell can act as a PCell in downlink 3CC aggregation only if CaDl3CCSwitch under the
CaMgtCfg.CellCaAlgoSwitch parameter is on for the cell. LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz and LAOFD-080208 Carrier Aggregation for
Downlink 3CC in 60MHz are both under license control in eRAN8.1. Each cell involved in
3CC aggregation requires one sales unit of the license for LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz or LAOFD-080208 Carrier Aggregation for
Downlink 3CC in 60MHz. For the two features to take effect, their prerequisite features must
be licensed. See the following table.
Others
The prerequisite features for the CA feature must have been enabled.
11.4.3 Precautions
For details, see 6.4.3 Precautions.
11.4.5 Activation
Step 1 Configure cells or frequencies.
l In CA-group-based configuration mode, perform the MML-based procedure described in
6.4.5 Activation with the following exceptions: Add three cells to the CA group in step
3, and configure two candidate SCells for each PCell in step 4.
l In frequency-based or adaptive configuration mode, perform the MML-based procedure
described in 6.4.5 Activation with the following exception: Add at least two candidate
SCCs and set their attributes for each candidate PCC in step 3.
Step 2 On the U2000 client, run the MOD CAMGTCFG command with the
CaDl3CCSwitch(CaDl3CCSwitch) option of the Cell Level CA Algorithm Switch
parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1;
----End
1526732907 L.Traffic.User.PCell.D Average number of UEs that treat the local cell
L.3CC.Avg as their PCell and each have two SCells
configured
1526732915 L.Traffic.User.PCell.D Average number of UEs that treat the local cell
L.3CC.Active.Avg as their PCell and each have two SCells
activated
11.4.7 Deactivation
In addition to the steps in 6.4.7 Deactivation, perform the following step on the U2000 client:
11.7 Troubleshooting
For details, see 6.7 Troubleshooting.
12.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
For details about network planning, see 6.3 Planning.
Hardware Planning
For details about hardware planning, see 6.3 Planning.
12.4 Deployment
CA applies to two single-carrier cells or a dual-carrier sector. For details about how to deploy
a dual-carrier sector, see Cell Management.
12.4.1 Requirements
To allow downlink CA to reach a peak data rate of 300 Mbit/s or 450 Mbit/s in downlink 4x4
MIMO scenarios, the maximum bit rate that the UE subscribes to in the EPC cannot be less
than 300 Mbit/s or 450 Mbit/s, respectively.
License
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO is a trial feature in eRAN8.1 and
therefore is not under license control. However, for this feature to take effect, the features
listed in the following table must be licensed.
The license for LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz is
required only if the total bandwidth of aggregated cells is between 20 MHz and 40 MHz
(including 40 MHz).
Others
The prerequisite features for the CA feature must have been enabled.
12.4.3 Precautions
For details, see 6.4.3 Precautions.
12.4.5 Activation
For details, see 6.4.5 Activation.
12.4.7 Deactivation
For details, see 6.4.7 Deactivation.
12.7 Troubleshooting
For details, see 6.7 Troubleshooting.
13.3 Planning
RF Planning
For details about RF planning, see 6.3 Planning.
Network Planning
For details about network planning for FDD carriers, see 6.3 Planning. For details about
network planning for TDD carriers, see Carrier Aggregation in LTE TDD Feature
Documentation for eRAN TDD 8.1.
Hardware Planning
For details about hardware planning for FDD carriers, see 6.3 Planning. For details about
hardware planning for TDD carriers, see Carrier Aggregation in LTE TDD Feature
Documentation for eRAN TDD 8.1.
In addition, make the hardware plan for FDD+TDD CA with the following requirements
taken into consideration:
l If an FDD cell on an LBBPd4 board acts as the PCell for a CA UE, downlink FDD
+TDD 3CC or 4CC CA will not work.
l The PCell and SCells of a CA UE cannot be configured on a single BBP that works for
both FDD and TDD.
l The LTE TDD cells whose carriers are to be aggregated for a single CA UE must be
configured in the same BBU.
l FDD+TDD CA does not apply to cells on LBBPc boards.
13.4 Deployment
CA applies to two single-carrier cells or a dual-carrier sector. For details about how to deploy
a dual-carrier sector, see Cell Management.
13.4.1 Requirements
l To allow downlink 2FDD+2TDD aggregation to reach a peak data rate of 520 Mbit/s, the
maximum bit rate that the UE subscribes to in the EPC must be greater than or equal to
520 Mbit/s.
l UEs must comply with 3GPP Release 12 or later and support the frequency bands of the
carriers to be aggregated and their channel bandwidths.
License
FDD+TDD CA is a trial feature in eRAN8.1 and therefore is not under license control.
However, for this feature to take effect, its prerequisite features must be licensed:
l If at least two FDD carriers are involved in FDD+TDD CA and the total bandwidth of
the FDD carriers does not exceed 20 MHz, each of the cells requires one sales unit of the
license for LAOFD-001001 LTE-A Introduction.
l If at least two FDD carriers are involved in FDD+TDD CA and the total bandwidth of
the FDD carriers is between 20 MHz and 40 MHz (including 40 MHz), each of the cells
requires one sales unit of the license for LAOFD-001001 LTE-A Introduction and one
sales unit of the license for LAOFD-001002 Carrier Aggregation for Downlink 2CC in
40MHz.
l If three FDD carriers are involved in FDD+TDD CA and the total bandwidth of the FDD
carriers does not exceed 40 MHz, each of the cells requires one sales unit of the license
for LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz.
l If three FDD carriers are involved in FDD+TDD CA and the total bandwidth of the FDD
carriers is between 40 MHz and 60 MHz (including 60 MHz), each of the cells requires
one sales unit of the license for LAOFD-080207 Carrier Aggregation for Downlink 3CC
in 40MHz and one sales unit of the license for LAOFD-080208 Carrier Aggregation for
Downlink 3CC in 60MHz.
l If Flexible CA from Multiple Carriers is enabled for the FDD cells involved in the CA,
each of the cells requires one sales unit of the license for LAOFD-070201 Flexible CA
from Multiple Carriers.
l If at least two TDD carriers are involved in FDD+TDD CA and the total bandwidth of
the TDD carriers does not exceed 30 MHz, each of the cells requires one sales unit of the
license for TDLAOFD-001001 LTE-A Introduction.
l If at least two TDD carriers are involved in FDD+TDD CA and the total bandwidth of
the TDD carriers is between 30 MHz and 40 MHz (including 40 MHz), each of the cells
requires one sales unit of the license for TDLAOFD-001001 LTE-A Introduction and
one sales unit of the license for TDLAOFD-001002 Carrier Aggregation for Downlink
2CC in 40MHz.
l If three TDD carriers are involved in FDD+TDD CA, each of the cells requires one sales
unit of the license for TDLAOFD-081405 Carrier Aggregation for Downlink 3CC.
l If Flexible CA from Multiple Carriers is enabled for the TDD cells involved in the CA,
each of the cells requires one sales unit of the license for TDLAOFD-070201 Flexible
CA from Multiple Carriers.
Feature Feature Model License Control NE Sales
ID Name Item Unit
Others
The prerequisite features for the CA feature must have been enabled.
In addition:
l To enable downlink FDD+TDD 3CC aggregation, set the following switch in the
CaMgtCfg MO on.
Paramete Parameter Setting Notes Data Source
r Name ID
l To enable downlink FDD+TDD 4CC aggregation, set the following switches in the
CaMgtCfg MO on.
l To enable downlink FDD+TDD 2CC aggregation in relaxed backhaul scenarios, set the
following switch in the ENodeBAlgoSwitch MO on.
13.4.3 Precautions
For details, see 6.4.3 Precautions.
13.4.5 Activation
In addition to the steps in 6.4.5 Activation, perform the following steps on the U2000 client:
Step 1 For the eNodeB that serves the PCell, run the MOD CAMGTCFG command with the
InterFddTddCaSwitch(InterFddTddCaSwitch) option of the Cell Level CA Algorithm
Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=InterFddTddCaSwitch-1;
Step 2 (Optional) To enable downlink FDD+TDD 3CC aggregation, run the MOD CAMGTCFG
command with Local cell ID set to the ID of the intended PCell and with the
CaDl3CCSwitch(CaDl3CCSwitch) option of the Cell Level CA Algorithm Switch
parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1;
Step 3 (Optional) To enable downlink FDD+TDD 4CC aggregation, run the MOD CAMGTCFG
command with Local cell ID set to the ID of the intended PCell and with both the
CaDl3CCSwitch(CaDl3CCSwitch) and CaDl4CCSwitch(CaDl4CCSwitch) options of the
Cell Level CA Algorithm Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1&CaDl4CCSwitch-1;
Step 4 (Optional) To enable downlink FDD+TDD 2CC aggregation in relaxed backhaul scenarios,
run the MOD ENODEBALGOSWITCH command with the
RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) option of the CA Algorithm
Switch parameter selected.
MOD ENODEBALGOSWITCH:LOCALCELLID=0,CAALGOSWITCH=RelaxedBackhaulCaSwitch-1;
----End
After downlink FDD+TDD 3CC aggregation is enabled, the eNodeB configures two SCells at
a time for a CA UE when the required conditions are met. Observe the counters listed in the
following table to obtain PCell statistics related to FDD+TDD CA. If the
L.Traffic.User.FddTddCA.3CC.PCell.DL.Avg counter produces a non-zero value, downlink
FDD+TDD 3CC aggregation has been activated. If the value remains at zero, downlink FDD
+TDD 3CC aggregation may not be activated.
After downlink FDD+TDD 4CC aggregation is enabled, the eNodeB configures three SCells
at a time for a CA UE when the required conditions are met. Observe the counters listed in the
following table to obtain PCell statistics related to FDD+TDD CA. If the
L.Traffic.User.FddTddCA.4CC.PCell.DL.Avg counter produces a non-zero value, downlink
FDD+TDD 4CC aggregation has been activated. If the value remains at zero, downlink FDD
+TDD 4CC aggregation may not be activated.
13.4.7 Deactivation
In addition to the steps in 6.4.7 Deactivation, perform the following step on the U2000 client:
Run the MOD CAMGTCFG command with the
InterFddTddCaSwitch(InterFddTddCaSwitch) option of the Cell Level CA Algorithm
Switch parameter deselected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=InterFddTddCaSwitch-0;
To evaluate the performance of downlink FDD+TDD 3CC aggregation, monitor the following
counters in addition to those listed in Table 13-4.
To evaluate the performance of downlink FDD+TDD 3CC aggregation, monitor the following
counters in addition to those listed in 11.5 Performance Monitoring and Table 13-4.
To evaluate the performance of downlink FDD+TDD 4CC aggregation, monitor the following
counters in addition to those listed in Table 13-4.
To evaluate the performance of downlink FDD+TDD 4CC aggregation, monitor the following
counters in addition to those listed in Table 13-4 and Table 13-6.
13.7 Troubleshooting
For details, see 6.7 Troubleshooting.
14 Parameters
SccBlindCfgSwitch(SccBlindCfgSwitch),
FreqCfgSwitch(FreqCfgSwitch),
SccA2RmvSwitch(SccA2RmvSwitch),
CaTrafficTriggerSwitch(CaTrafficTriggerSwitch),
HoWithSccCfgSwitch(HoWithSccCfgSwitch),
SccModA6Switch(SccModA6Switch),
GbrAmbrJudgeSwitch(GbrAmbrJudgeSwitch),
MtaAlgSwitch(MtaAlgSwitch), RelaxedBackhaul-
CaSwitch(RelaxedBackhaulCaSwitch),
AdpCaSwitch(AdpCaSwitch),
CaHoControlSwitch(CaHoControlSwitch),
DistributeCloudbbCaSwitch(DistributeCloudbbCaS-
witch), SccSmartCfgSwitch(SccSmartCfgSwitch),
IdleModePccAnchorSwitch(IdleModePccAnchorS-
witch), FreqPriBasedHoCaFiltS-
witch(FreqPriBasedHoCaFiltSwitch),
CaSccSuspendSwitch(CaSccSuspendSwitch)
Unit: None
Actual Value Range: PdcchOverlapSrchSpcSwitch,
CaCapbFiltSwitch, PccAnchorSwitch,
SccBlindCfgSwitch, FreqCfgSwitch,
SccA2RmvSwitch, CaTrafficTriggerSwitch,
HoWithSccCfgSwitch, SccModA6Switch,
GbrAmbrJudgeSwitch, MtaAlgSwitch,
RelaxedBackhaulCaSwitch, AdpCaSwitch,
CaHoControlSwitch, DistributeCloudbbCaSwitch,
SccSmartCfgSwitch, IdleModePccAnchorSwitch,
FreqPriBasedHoCaFiltSwitch, CaSccSuspendSwitch
Default Value: PdcchOverlapSrchSpcSwitch:On,
CaCapbFiltSwitch:Off, PccAnchorSwitch:Off,
SccBlindCfgSwitch:Off, FreqCfgSwitch:Off,
SccA2RmvSwitch:On, CaTrafficTriggerSwitch:Off,
HoWithSccCfgSwitch:Off, SccModA6Switch:Off,
GbrAmbrJudgeSwitch:On, MtaAlgSwitch:Off,
RelaxedBackhaulCaSwitch:Off, AdpCaSwitch:Off,
CaHoControlSwitch:Off, DistributeCloudbbCaS-
witch:Off, SccSmartCfgSwitch:Off,
IdleModePccAnchorSwitch:Off, FreqPriBasedHoCa-
FiltSwitch:Off, CaSccSuspendSwitch:Off
CaMgtC CellMax MOD LAOFD Intra- Meaning: Indicates the maximum number of CA UEs
fg PccNum CAMG -001001 Band that are allowed to use the cell's carrier as the PCC. If
ber TCFG 01 Carrier the number of CA UEs using the cell's carrier as the
LST LAOFD Aggrega PCC has reached the parameter value, no more CA
CAMG -001001 tion for UEs can use the carrier as the PCC. A smaller
TCFG 02 Downlin parameter value leads to fewer CA UEs that are
k 2CC allowed to use the cell's carrier as the PCC. If this
LAOFD in parameter is set to 0, no CA UE is allowed to use the
-001002 20MHz cell's carrier as the PCC but CA UEs can use the
01 carrier as the SCC. If the total value of this parameter
Inter-
LAOFD Band for all cells on a baseband processing unit exceeds the
-001002 Carrier upper limit of such UEs served by the unit, the limit
02 Aggrega takes effect.
LAOFD tion for GUI Value Range: 0~65535
-070201 Downlin Unit: None
LAOFD k 2CC
in Actual Value Range: 0~65535
-070202
20MHz Default Value: 65535
LAOFD
-080201 Carrier
Aggrega
LAOFD
tion for
-080202
Downlin
LAOFD k 2CC
-080207 in
LAOFD 40MHz
-080208 Support
TDLAO of UE
FD-001 Categor
00111 y6
TDLAO Flexible
FD-001 CA
002 from
Multiple
TDLAO
Carriers
FD-070
201 Inter-
eNodeB
CA
based on
Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier
Aggrega
tion for
2CC
based on
inter
site)
Carrier
Aggrega
tion for
Uplink
2CC
Carrier
Aggrega
tion for
Downlin
k 3CC
in
40MHz
Carrier
Aggrega
tion for
Downlin
k 3CC
in
60MHz
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Flexible
CA
from
Multiple
Carriers
CaMgtC CaAmbr MOD LAOFD Intra- Meaning: Indicates the aggregate maximum bit rate
fg Thd CAMG -001001 Band (AMBR) threshold for aggregating carriers for UEs.
TCFG 01 Carrier Carriers can only be aggregated for UEs whose
LST LAOFD Aggrega AMBR values are greater than the threshold. A larger
CAMG -001001 tion for value of this parameter leads to fewer UEs for whom
TCFG 02 Downlin the carriers can be aggregated.
k 2CC GUI Value Range: 0~65535
LAOFD in
-001002 20MHz Unit: Mbps
01 Actual Value Range: 0~65535
Inter-
LAOFD Band Default Value: 0
-001001 Carrier
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
LAOFD
-080201 Carrier
Aggrega
LAOFD
tion for
-080202
Downlin
LAOFD k 2CC
-080207 in
LAOFD 40MHz
-080208 Support
TDLAO of UE
FD-001 Categor
00111 y6
TDLAO Flexible
FD-001 CA
002 from
Multiple
TDLAO
Carriers
FD-070
201 Inter-
eNodeB
CA
based on
Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier
Aggrega
tion for
2CC
based on
inter
site)
Carrier
Aggrega
tion for
Uplink
2CC
Carrier
Aggrega
tion for
Downlin
k 3CC
in
40MHz
Carrier
Aggrega
tion for
Downlin
k 3CC
in
60MHz
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Flexible
CA
from
Multiple
Carriers
ENodeB FddFra MOD MRFD- FDD Meaning: Indicates the offset of the start time of a cell
FrameO meOffse ENODE 101231 +TDD frame against a reference clock source. This offset
ffset t BFRAM MRFD- Carrier applies to all LTE FDD cells served by an eNodeB.
EOFFS 101222 Aggrega GUI Value Range: 0~261120,275943~307200
ET tion(LT
E TDD) Unit: Ts
LST
ENODE FDD Actual Value Range: 0~261120,275943~307200
BFRAM +TDD Default Value: 0
EOFFS Carrier
ET Aggrega
tion(LT
E FDD)
ENodeB TddFra MOD TDLBF Basic Meaning: Indicates the offset of the start time of a cell
FrameO meOffse ENODE D-00100 uplink- frame against a reference clock source. This offset
ffset t BFRAM 7 downlin applies to all LTE TDD cells served by an eNodeB.
EOFFS TDLBF k GUI Value Range: 0~261120,275943~307200
ET D-00100 subfram
e Unit: Ts
LST 701
ENODE configur Actual Value Range: 0~261120,275943~307200
TDLBF ation
BFRAM D-00100 Default Value: 0
EOFFS 702 uplink-
ET downlin
TDLOF k
D-00102 subfram
6 e
TDLOF configur
D-00102 ation
601 type1&2
TDLOF uplink-
D-00102 downlin
602 k special
TDLOF subfram
D-00102 e
603 configur
ation
MRFD- type 7
101231
Optional
MRFD- uplink-
101222 downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
FDD
+TDD
Carrier
Aggrega
tion(LT
E TDD)
FDD
+TDD
Carrier
Aggrega
tion(LT
E FDD)
CellFra LocalCe ADD None None Meaning: Indicates the local ID of a cell. It uniquely
meOffse llId CELLF identifies a cell within an eNodeB.
t RAME GUI Value Range: 0~255
OFFSE
T Unit: None
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
CaGrou CaGrou ADD LAOFD Intra- Meaning: Indicates the type of the CA group.
p pTypeIn CAGRO -001001 Band GUI Value Range: FDD(FDD), TDD(TDD),
d UP 01 Carrier FDDTDD(FDDTDD)
MOD LAOFD Aggrega
tion for Unit: None
CAGRO -001001
UP 02 Downlin Actual Value Range: FDD, TDD, FDDTDD
k 2CC Default Value: FDD(FDD)
LST LAOFD in
CAGRO -001002 20MHz
UP 01 /
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
LAOFD CA
-081236 from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
FDD
+TDD
Carrier
Aggrega
tion
EutranIn CellIndi ADD LBFD-0 Coverag Meaning: Indicates the cell individual offset for the
traFreq vidualOf EUTRA 0201801 e Based intra-frequency neighboring cell, which is used in
NCell fset NINTR / Intra- evaluation for handovers. It affects the probability of
AFREQ TDLBF frequenc triggering intra-frequency measurement reports. A
NCELL D-00201 y larger value of this parameter indicates a higher
MOD 801 Handov probability. For details, see 3GPP TS 36.331.
EUTRA TDLBF er GUI Value Range: dB-24(-24dB), dB-22(-22dB),
NINTR D-00201 Mobility dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
AFREQ 8 Manage dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
NCELL ment 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),
NINTR dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
AFREQ dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
NCELL 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)
Cell CellSpe ADD LBFD-0 Coverag Meaning: Indicates the cell specific offset for the
cificOffs CELL 0201801 e Based serving cell. It affects the probability of triggering
et MOD / Intra- handovers from the serving cell to its neighboring
CELL TDLBF frequenc cells. A smaller value of this parameter leads to a
D-00201 y higher probability. For details, see 3GPP TS 36.331.
LST 801 Handov
CELL GUI Value Range: dB-24(-24dB), dB-22(-22dB),
TDLBF er dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
D-00201 Mobility dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
8 Manage dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
TDLBF ment dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
D-00201 Coverag dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
802 e Based dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
Inter- dB12(12dB), dB14(14dB), dB16(16dB), dB18(18dB),
TDLBF dB20(20dB), dB22(22dB), dB24(24dB)
D-00201 frequenc
804 y Unit: dB
Handov Actual Value Range: dB-24, dB-22, dB-20, dB-18,
TDLBF er
D-00201 dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
805 Distance dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,
Based dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20,
TDLOF Inter- dB22, dB24
D-00101 frequenc
9 Default Value: dB0(0dB)
y
TDLOF Handov
D-00104 er
3 Service
TDLOF Based
D-00107 Inter-
2 frequenc
TDLOF y
D-00102 Handov
0 er
TDLOF PS Inter-
D-00104 RAT
6 Mobility
between
TDLOF E-
D-00107 UTRAN
3 and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
GERAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN
CaMgtC CarrAgg MOD TDLAO Intra- Meaning: Indicates the offset for secondary cell event
fg rA6Offs CAMG FD-001 band A6. This offset is the difference between the quality of
et TCFG 00111 Carrier a neighboring cell and that of the serving cell. A large
LST TDLAO Aggrega value indicates that a neighboring cell must have a
CAMG FD-001 tion for better quality than the serving cell for reporting the
TCFG 002 Downlin event A6.
k 2CC GUI Value Range: -30~30
TDLAO in
FD-001 30MHz Unit: 0.5dB
00102 Actual Value Range: -15~15
Carrier
TDLAO Aggrega Default Value: 2
FD-070 tion for
201 Downlin
LAOFD k 2CC
-001001 in
01 40MHz
LAOFD Support
-001001 for UE
02 Categor
LAOFD y6
-001002 Flexible
01 CA
LAOFD from
-001002 Multiple
02 Carriers
LAOFD Intra-
-070201 Band
Carrier
LAOFD
Aggrega
-070202
tion for
Downlin
k 2CC
in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
PrivateC PrivateC ADD LAOFD Intra- Meaning: Indicates the ID of the private CA band
aBandC aCombI PRIVAT -001001 Band combination. It uniquely identifies a private CA band
omb d ECABA 01 Carrier combination in an eNodeB.
NDCO LAOFD Aggrega GUI Value Range: 0~31
MB -001001 tion for
Downlin Unit: None
DSP 02
PRIVAT k 2CC Actual Value Range: 0~31
LAOFD in
ECABA -001002 Default Value: None
NDCO 20MHz
01 /
MB TDLAO Inter-
LST FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
MOD TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
RMV / Downlin
PRIVAT TDLAO k 2CC
ECABA FD-070 in
NDCO 201 40MHz
MB LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC MaxAgg ADD LAOFD Intra- Meaning: Indicates the maximum aggregated
aBandC regated PRIVAT -001001 Band bandwidth supported by the CA band combination.
omb Bw ECABA 01 Carrier GUI Value Range: 20~300
NDCO LAOFD Aggrega
MB tion for Unit: MHz
-001001
MOD 02 Downlin Actual Value Range: 20~300
PRIVAT k 2CC Default Value: None
LAOFD in
ECABA -001002
NDCO 20MHz
01 /
MB TDLAO Inter-
DSP FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
LST TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates combination band 1. For details,
aBandC nd1Id PRIVAT -001001 Band see 3GPP TS 36.101.
omb ECABA 01 Carrier GUI Value Range: 1~256
NDCO LAOFD Aggrega
MB tion for Unit: None
-001001
MOD 02 Downlin Actual Value Range: 1~256
PRIVAT k 2CC Default Value: 1
LAOFD in
ECABA -001002
NDCO 20MHz
01 /
MB TDLAO Inter-
DSP FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
LST TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates combination band 2. For details,
aBandC nd2Id PRIVAT -001001 Band see 3GPP TS 36.101.
omb ECABA 01 Carrier GUI Value Range: 1~256
NDCO LAOFD Aggrega
MB tion for Unit: None
-001001
MOD 02 Downlin Actual Value Range: 1~256
PRIVAT k 2CC Default Value: 1
LAOFD in
ECABA -001002
NDCO 20MHz
01 /
MB TDLAO Inter-
DSP FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
LST TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates combination band 3. For details,
aBandC nd3Id PRIVAT -001001 Band see 3GPP TS 36.101. If the value is 0, combination
omb ECABA 01 Carrier band 3 is invalid.
NDCO LAOFD Aggrega GUI Value Range: 0~256
MB -001001 tion for
Downlin Unit: None
MOD 02
PRIVAT k 2CC Actual Value Range: 0~256
LAOFD in
ECABA -001002 Default Value: 0
NDCO 20MHz
01 /
MB TDLAO Inter-
DSP FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
LST TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates combination band 4. For details,
aBandC nd4Id PRIVAT -001001 Band see 3GPP TS 36.101. If the value is 0, combination
omb ECABA 01 Carrier band 4 is invalid.
NDCO LAOFD Aggrega GUI Value Range: 0~256
MB -001001 tion for
Downlin Unit: None
MOD 02
PRIVAT k 2CC Actual Value Range: 0~256
LAOFD in
ECABA -001002 Default Value: 0
NDCO 20MHz
01 /
MB TDLAO Inter-
DSP FD-001 Band
PRIVAT 002 Carrier
ECABA Aggrega
LAOFD tion for
NDCO -001002
MB Downlin
02 / k 2CC
LST TDLAO in
PRIVAT FD-001 20MHz
ECABA 00202
NDCO Carrier
LAOFD Aggrega
MB -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates the bandwidth combination of
aBandC nd1Bw PRIVAT -001001 Band combination band 1. If a bandwidth is selected, the
omb ECABA 01 Carrier carrier with the corresponding bandwidth in
NDCO LAOFD Aggrega combination band 1 is supported in the private CA
MB -001001 tion for combination band. The selected bandwidths must be
MOD 02 Downlin consistent with the actual bandwidth configurations.
PRIVAT k 2CC Otherwise, the bandwidths that a UE does not support
LAOFD in are determined as supported by the eNodeB, causing
ECABA -001002
NDCO 20MHz CA configuration failures in the eNodeB.
01 /
MB TDLAO Inter- GUI Value Range: Bandwidth_1_4M(1.4M),
DSP FD-001 Band Bandwidth_3M(3M), Bandwidth_5M(5M),
PRIVAT 002 Carrier Bandwidth_10M(10M), Bandwidth_15M(15M),
ECABA Aggrega Bandwidth_20M(20M)
LAOFD tion for
NDCO -001002 Unit: None
MB Downlin
02 / k 2CC Actual Value Range: Bandwidth_1_4M,
LST TDLAO in Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVAT FD-001 20MHz Bandwidth_15M, Bandwidth_20M
ECABA 00202 Default Value: Bandwidth_1_4M:On,
NDCO Carrier
LAOFD Aggrega Bandwidth_3M:Off, Bandwidth_5M:Off,
MB -070201 Bandwidth_10M:Off, Bandwidth_15M:Off,
tion for
/ Downlin Bandwidth_20M:Off
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates the bandwidth combination of
aBandC nd2Bw PRIVAT -001001 Band combination band 2. If a bandwidth is selected, the
omb ECABA 01 Carrier carrier with the corresponding bandwidth in
NDCO LAOFD Aggrega combination band 2 is supported in the private CA
MB -001001 tion for combination band. The selected bandwidths must be
MOD 02 Downlin consistent with the actual bandwidth configurations.
PRIVAT k 2CC Otherwise, the bandwidths that a UE does not support
LAOFD in are determined as supported by the eNodeB, causing
ECABA -001002
NDCO 20MHz CA configuration failures in the eNodeB.
01 /
MB TDLAO Inter- GUI Value Range: Bandwidth_1_4M(1.4M),
DSP FD-001 Band Bandwidth_3M(3M), Bandwidth_5M(5M),
PRIVAT 002 Carrier Bandwidth_10M(10M), Bandwidth_15M(15M),
ECABA Aggrega Bandwidth_20M(20M)
LAOFD tion for
NDCO -001002 Unit: None
MB Downlin
02 / k 2CC Actual Value Range: Bandwidth_1_4M,
LST TDLAO in Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVAT FD-001 20MHz Bandwidth_15M, Bandwidth_20M
ECABA 00202 Default Value: Bandwidth_1_4M:On,
NDCO Carrier
LAOFD Aggrega Bandwidth_3M:Off, Bandwidth_5M:Off,
MB -070201 Bandwidth_10M:Off, Bandwidth_15M:Off,
tion for
/ Downlin Bandwidth_20M:Off
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates the bandwidth combination of
aBandC nd3Bw PRIVAT -001001 Band combination band 3. If a bandwidth is selected, the
omb ECABA 01 Carrier carrier with the corresponding bandwidth in
NDCO LAOFD Aggrega combination band 3 is supported in the private CA
MB -001001 tion for combination band. The selected bandwidths must be
MOD 02 Downlin consistent with the actual bandwidth configurations.
PRIVAT k 2CC Otherwise, the bandwidths that a UE does not support
LAOFD in are determined as supported by the eNodeB, causing
ECABA -001002
NDCO 20MHz CA configuration failures in the eNodeB.
01 /
MB TDLAO Inter- GUI Value Range: Bandwidth_1_4M(1.4M),
DSP FD-001 Band Bandwidth_3M(3M), Bandwidth_5M(5M),
PRIVAT 002 Carrier Bandwidth_10M(10M), Bandwidth_15M(15M),
ECABA Aggrega Bandwidth_20M(20M)
LAOFD tion for
NDCO -001002 Unit: None
MB Downlin
02 / k 2CC Actual Value Range: Bandwidth_1_4M,
LST TDLAO in Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVAT FD-001 20MHz Bandwidth_15M, Bandwidth_20M
ECABA 00202 Default Value: Bandwidth_1_4M:Off,
NDCO Carrier
LAOFD Aggrega Bandwidth_3M:Off, Bandwidth_5M:Off,
MB -070201 Bandwidth_10M:Off, Bandwidth_15M:Off,
tion for
/ Downlin Bandwidth_20M:Off
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates the bandwidth combination of
aBandC nd4Bw PRIVAT -001001 Band combination band 4. If a bandwidth is selected, the
omb ECABA 01 Carrier carrier with the corresponding bandwidth in
NDCO LAOFD Aggrega combination band 4 is supported in the private CA
MB -001001 tion for combination band. The selected bandwidths must be
MOD 02 Downlin consistent with the actual bandwidth configurations.
PRIVAT k 2CC Otherwise, the bandwidths that a UE does not support
LAOFD in are determined as supported by the eNodeB, causing
ECABA -001002
NDCO 20MHz CA configuration failures in the eNodeB.
01 /
MB TDLAO Inter- GUI Value Range: Bandwidth_1_4M(1.4M),
DSP FD-001 Band Bandwidth_3M(3M), Bandwidth_5M(5M),
PRIVAT 002 Carrier Bandwidth_10M(10M), Bandwidth_15M(15M),
ECABA Aggrega Bandwidth_20M(20M)
LAOFD tion for
NDCO -001002 Unit: None
MB Downlin
02 / k 2CC Actual Value Range: Bandwidth_1_4M,
LST TDLAO in Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVAT FD-001 20MHz Bandwidth_15M, Bandwidth_20M
ECABA 00202 Default Value: Bandwidth_1_4M:Off,
NDCO Carrier
LAOFD Aggrega Bandwidth_3M:Off, Bandwidth_5M:Off,
MB -070201 Bandwidth_10M:Off, Bandwidth_15M:Off,
tion for
/ Downlin Bandwidth_20M:Off
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
k 2CC
in
30MHz
CaGrou Preferre ADD LAOFD Intra- Meaning: Indicates the priority of the cell being
pCell dPCellP CAGRO -001001 Band treated as a primary serving cell (PCell). A larger
riority UPCEL 01 Carrier parameter value represents a higher priority level.
L LAOFD Aggrega This parameter takes effect only when
MOD -001001 tion for PccAnchorSwitch of the CaAlgoSwitch parameter is
CAGRO 02 Downlin on.
UPCEL k 2CC GUI Value Range: 0~7
LAOFD in
L -001002 Unit: None
20MHz
LST 01 / Actual Value Range: 0~7
CAGRO TDLAO Inter-
UPCEL FD-001 Band Default Value: 0
L 002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
IntraRat InterFre MOD LBFD-0 Coverag Meaning: Indicates the trigger quantity for event
HoCom qHoA4T INTRA 0201802 e Based A3/A4/A5 measurement reports of all inter-frequency
m rigQuan RATHO / Inter- handovers except coverage-based inter-frequency
COMM TDLBF frequenc handover.
LST D-00201 y GUI Value Range: RSRP, RSRQ, BOTH
INTRA 802 Handov
er Unit: None
RATHO LOFD-0
COMM 0109804 Carrier Actual Value Range: RSRP, RSRQ, BOTH
/ Manage Default Value: RSRP
TDLAO ment
FD-001
00306
CaGrou PCellA4 ADD LAOFD Intra- Meaning: Indicates the reference signal received
pCell RsrpThd CAGRO -001001 Band power (RSRP) threshold for triggering event A4
UPCEL 01 Carrier during higher-priority cell evaluation for PCell
L LAOFD Aggrega selection in scenarios where CA is configured based
MOD -001001 tion for on CA groups.
CAGRO 02 Downlin GUI Value Range: -140~-43
UPCEL k 2CC
LAOFD in Unit: dBm
L -001002 20MHz Actual Value Range: -140~-43
LST 01 /
CAGRO TDLAO Inter- Default Value: -105
UPCEL FD-001 Band
L 002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou PCellA4 ADD LAOFD Intra- Meaning: Indicates the reference signal received
pCell RsrqThd CAGRO -001001 Band quality (RSRQ) threshold for triggering event A4
UPCEL 01 Carrier during higher-priority cell evaluation for PCell
L LAOFD Aggrega selection in scenarios where CA is configured based
MOD -001001 tion for on CA groups. If the measured RSRQ of an inter-
CAGRO 02 Downlin frequency neighboring cell in the CA group is greater
UPCEL k 2CC than this parameter value, the CA UE reports event
LAOFD in A4.
L -001002 20MHz GUI Value Range: -40~-6
LST 01 /
CAGRO TDLAO Inter- Unit: 0.5dB
UPCEL FD-001 Band
Carrier Actual Value Range: -20~-3
L 002
Aggrega Default Value: -20
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
PccFreq Preferre ADD LAOFD Intra- Meaning: Indicates the priority with which the
Cfg dPccPri PCCFR -001001 Band candidate PCC is selected as the PCC. The priority
ority EQCFG 01 Carrier level has a positive correlation with the parameter
MOD LAOFD Aggrega value. This parameter is valid only if
PCCFR -001001 tion for IdleModePccAnchorSwitch or PccAnchorSwitch of
EQCFG 02 Downlin the CaAlgoSwitch parameter is set to 1.
k 2CC GUI Value Range: 0~7
LST LAOFD in
PCCFR -001002 20MHz Unit: None
EQCFG 01 Actual Value Range: 0~7
Inter-
LAOFD Band Default Value: 0
-001002 Carrier
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
PccFreq PccDlEa ADD LAOFD Intra- Meaning: Indicates the downlink E-UTRA absolute
Cfg rfcn PCCFR -001001 Band radio frequency channel number (EARFCN) of the
EQCFG 01 Carrier candidate PCC.
DSP LAOFD Aggrega GUI Value Range: 0~46589,54436~65535
PCCSC -001001 tion for
Downlin Unit: None
ELLLIS 02
T k 2CC Actual Value Range: 0~46589,54436~65535
LAOFD in
LST -001002 Default Value: None
20MHz
PCCFR 01
EQCFG Inter-
LAOFD Band
MOD -001002 Carrier
PCCFR 02 Aggrega
EQCFG LAOFD tion for
RMV -070201 Downlin
PCCFR LAOFD k 2CC
EQCFG -070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
PccFreq PccA4R ADD LAOFD Intra- Meaning: Indicates the reference signal received
Cfg srpThd PCCFR -001001 Band power (RSRP) threshold for triggering event A4
EQCFG 01 Carrier during higher-priority carrier evaluation for PCC
MOD LAOFD Aggrega selection.
PCCFR -001001 tion for GUI Value Range: -140~-43
EQCFG 02 Downlin
k 2CC Unit: dBm
LST LAOFD in Actual Value Range: -140~-43
PCCFR -001002 20MHz
EQCFG 01 Default Value: -105
Inter-
LAOFD Band
-001002 Carrier
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
PccFreq PccA4R ADD LAOFD Intra- Meaning: Indicates the reference signal received
Cfg srqThd PCCFR -001001 Band quality (RSRQ) threshold for triggering event A4
EQCFG 01 Carrier during higher-priority carrier evaluation for PCC
MOD LAOFD Aggrega selection in scenarios where CA is configured based
PCCFR -001001 tion for on frequencies. If the measured RSRQ of an inter-
EQCFG 02 Downlin frequency neighboring cell in the CA group is greater
k 2CC than this parameter value, the CA UE reports event
LST LAOFD in A4.
PCCFR -001002 20MHz
EQCFG 01 / GUI Value Range: -40~-6
TDLAO Inter- Unit: 0.5dB
FD-001 Band
Carrier Actual Value Range: -20~-3
002
Aggrega Default Value: -20
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CaGrou SCellPri ADD LAOFD Intra- Meaning: Indicates the priority of the candidate
pSCellC ority CAGRO -001001 Band secondary serving cell (SCell). A larger value of this
fg UPSCE 01 Carrier parameter indicates a higher priority and results in a
LLCFG LAOFD Aggrega higher probability of being configured as an SCell for
MOD -001001 tion for carrier aggregation (CA) UEs.The value 0 indicates
CAGRO 02 Downlin that this cell cannot be configured as an SCell for CA
UPSCE k 2CC UEs.
LAOFD in
LLCFG -001002 GUI Value Range: 0~7
20MHz
LST 01 / Unit: None
CAGRO TDLAO Inter-
Band Actual Value Range: 0~7
UPSCE FD-001
LLCFG 002 Carrier Default Value: 1
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
SccFreq SccPrior ADD LAOFD Intra- Meaning: Indicates the priority with which the
Cfg ity SCCFR -001001 Band candidate SCC works as an SCC for that PCC. A
EQCFG 01 Carrier smaller value of this parameter indicates a lower
MOD LAOFD Aggrega priority, and a larger value indicates a higher priority.
SCCFR -001001 tion for GUI Value Range: 1~7
EQCFG 02 Downlin
k 2CC Unit: None
LST LAOFD in Actual Value Range: 1~7
SCCFR -001002 20MHz
EQCFG 01 Default Value: 1
Inter-
LAOFD Band
-001002 Carrier
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CaMgtC SccCfgI MOD LAOFD Intra- Meaning: Indicates the minimum interval at which the
fg nterval CAMG -001001 Band eNodeB attempts to configure a secondary serving cell
TCFG 01 Carrier (SCell) again for a CA UE whose SCell failed to be
LST LAOFD Aggrega configured. The actual interval at which the eNodeB
CAMG -001001 tion for attempts to configure a secondary serving cell (SCell)
TCFG 02 Downlin again for a CA UE must be larger than this value. The
k 2CC eNodeB makes the attempt only if the traffic volume
LAOFD in of the UE always meets the SCell activation condition
-001002 20MHz throughout a certain time.
01
Inter- GUI Value Range: 5~60
LAOFD Band
-001001 Unit: s
Carrier
02 Aggrega Actual Value Range: 5~60
LAOFD tion for Default Value: 60
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
TDLAO
FD-001 Carrier
00111 Aggrega
tion for
TDLAO
Downlin
FD-001
k 2CC
002
in
TDLAO 40MHz
FD-001
Support
00102
of UE
TDLAO Categor
FD-070 y6
201
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
for UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
LcsSrvccSwitch, AutoGapSwitch,
UeVoipOnHspaCapSwitch, UtranFddB1CapSwitch,
CdmaHrpdNonOptMeaHoSwitch
Default Value: EutranVoipCapSwitch:On,
UtranVoipCapSwitch:Off, GeranVoipCapSwitch:Off,
Cdma1xRttVoipCapSwitch:Off,
UtranPsHoSwitch:Off, GeranPsHoSwitch:Off,
CdmaHrpdNonOptimisedHoSwitch:Off,
CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off, GeranCcoSwitch:Off,
UtranSrvccSwitch:Off, GeranSrvccSwitch:Off,
Cdma1xRttSrvccSwitch:Off,
UtranRedirectSwitch:Off, GeranRedirectSwitch:Off,
CdmaHrpdRedirectSwitch:Off,
Cdma1xRttRedirectSwitch:Off, BlindHoSwitch:Off,
LcsSrvccSwitch:Off, AutoGapSwitch:Off,
UeVoipOnHspaCapSwitch:Off,
UtranFddB1CapSwitch:Off, CdmaHrpdNonOptMea-
HoSwitch:Off
CaMgtC CarrAgg MOD LAOFD Intra- Meaning: Indicates the Reference Signal Received
fg rA4Thd CAMG -001001 Band Power (RSRP) threshold for a UE to report event A4
Rsrp TCFG 01 Carrier of a secondary cell. When the RSRP of the UE is
LST LAOFD Aggrega greater than the threshold, event A4 is reported.
CAMG -001001 tion for GUI Value Range: -140~-43
TCFG 02 Downlin
k 2CC Unit: dBm
LAOFD in Actual Value Range: -140~-43
-001002 20MHz
01 / Default Value: -105
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
SccFreq SccA4O ADD LAOFD Intra- Meaning: Indicates the offset of the actual threshold
Cfg ffset SCCFR -001001 Band for CA event A4 relative to the value of the
EQCFG 01 Carrier CarrAggrA4ThdRsrp parameter in the CaMgtCfg
MOD LAOFD Aggrega MO. If the actual threshold is greater than -43 dBm,
SCCFR -001001 tion for the value of -43 dBm takes effect. If the actual
EQCFG 02 Downlin threshold is less than -140 dBm, the value of -140
k 2CC dBm takes effect.
LST LAOFD in
SCCFR -001002 GUI Value Range: -35~62
20MHz
EQCFG 01 Unit: dBm
Inter-
LAOFD Band Actual Value Range: -35~62
-001002 Carrier Default Value: 0
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the threshold of the PRB usage for
B qMlbTh CELLM 01032 / LTE triggering inter-frequency load balancing. If the
d LB TDLOF Load MlbTriggerMode parameter is set to
LST D-00103 Balancin PRB_ONLY(PrbMode) or
CELLM 2 g PRB_OR_UE_NUMBER(PrbOrUeNumMode), inter-
LB frequency load balancing is triggered when the
number of synchronized UEs in the cell is greater than
or equal to the sum of the MlbMinUeNumThd and
MlbMinUeNumOffset parameter values and the PRB
usage of the cell is greater than or equal to the sum of
the InterFreqMlbThd and LoadOffset parameter
values. Load balancing stops when the PRB usage of
the cell or the number of synchronized UEs falls
below the value of the InterFreqMlbThd parameter or
the value of the MlbMinUeNumThd parameter,
respectively.
GUI Value Range: 1~100
Unit: %
Actual Value Range: 1~100
Default Value: 60
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the PRB usage threshold used for
B qOffloa CELLM 01032 / LTE transferring loads to neighboring cells with which the
dOffset LB TDLOF Load source cell does not exchange load information during
LST D-00103 Balancin inter-frequency load balancing. Consider that the
CELLM 2 g MlbTriggerMode parameter is set to
LB LOFD-0 Operator PRB_ONLY(PrbMode) or
70204 Load PRB_OR_UE_NUMBER(PrbOrUeNumMode). If the
Based PRB usage in the source cell is greater than or equal to
Intra- the sum of the InterFreqMlbThd parameter value and
LTE the InterFreqOffloadOffset parameter value,
MLB neighboring cells with which the source cell does not
exchange load information can be selected as the
target cells for load balancing, and the source cell
cannot be selected as a target cell for load balancing.
If the PRB usage in the source cell is less than the
value calculated by the InterFreqMlbThd parameter
value plus the InterFreqOffloadOffset parameter value
and then minus the LoadOffset parameter value, the
source cell can be selected as a target cell for load
balancing.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 0
CellML LoadOff MOD LOFD-0 Intra- Meaning: Indicates the offset of the PRB usage for
B set CELLM 01032 / LTE triggering inter-frequency load balancing. Inter-
LB TDLOF Load frequency load balancing is triggered if the number of
LST D-00103 Balancin synchronized UEs in the cell is greater than or equal
CELLM 2 g to the sum of the MlbMinUeNumThd and
LB LOFD-0 Inter- MlbMinUeNumOffset parameter values and the PRB
01044 / RAT usage of the cell is greater than or equal to the sum the
TDLOF Load InterFreqMlbThd and LoadOffset parameter values.
D-00104 Sharing Inter-frequency load balancing is triggered if the
4 to number of synchronized UEs in the cell is greater than
UTRAN or equal to the sum of the MlbMinUeNumThd and
LOFD-0 MlbMinUeNumOffset parameter values and the PRB
01045 / Inter- valuation in the cell is greater than or equal to the sum
TDLOF RAT of the PrbValMlbTrigThd and LoadOffset parameter
D-00104 Load values. Inter-RAT load sharing is triggered if the
5 Sharing number of synchronized UEs in the cell is greater than
to or equal to the sum of the InterRatMlbUeNumThd and
GERAN InterRatMlbUeNumOffset parameter values and the
PRB usage of the cell is greater than or equal to the
InterRatMlbThd and LoadOffset parameter values.
Inter-RAT load sharing to transfer to-be-released UEs
is triggered if the number of synchronized UEs is
greater than or equal to the sum of the
InterRATIdleMlbUeNumThd and InterRatMlbUeNu-
mOffset parameter values and the PRB usage of the
cell is greater than or equal to the sum of the
InterRatMlbThd and LoadOffset parameter values.
GUI Value Range: 0~50
Unit: %
Actual Value Range: 0~50
Default Value: 8
CellML InterFre MOD LOFD-0 Intra- Meaning: Indicates the threshold of the number of
B qMlbUe CELLM 70215 / LTE synchronized UEs for triggering inter-frequency load
NumTh LB TDLOF User balancing. When the MlbTriggerMode parameter is
d LST D-07021 Number set to UE_NUMBER_ONLY(UeNumMode) or
CELLM 5 Load PRB_OR_UE_NUMBER(PrbOrUeNumMode), inter-
LB Balancin frequency load balancing is triggered if the number of
g synchronized UEs in the cell is greater than or equal
to the sum of the InterFreqMlbUeNumThd and
MlbUeNumOffset parameter values. Inter-frequency
load balancing stops if the number of synchronized
UEs in the cell is less than the
InterFreqMlbUeNumThd parameter value.
GUI Value Range: 1~10000
Unit: None
Actual Value Range: 1~10000
Default Value: 100
CellML InterFrq MOD LOFD-0 Intra- Meaning: Indicates the UL-synchronized UE number
B UeNum CELLM 70215 / LTE threshold used for transferring loads to neighboring
Offload LB TDLOF User cells with which the source cell does not exchange
Offset LST D-07021 Number load information during inter-frequency load
CELLM 5 Load balancing. Consider that the MlbTriggerMode
LB LOFD-0 Balancin parameter is set to
70204 g UE_NUMBER_ONLY(UeNumMode) or
Operator PRB_OR_UE_NUMBER(PrbOrUeNumMode). If the
Load number of UL-synchronized UEs in the source cell is
Based greater than or equal to the sum of the
Intra- InterFreqMlbUeNumThd parameter value and the
LTE InterFrqUeNumOffloadOffset parameter value,
MLB neighboring cells with which the source cell does not
exchange load information can be selected as the
target cells for load balancing, and the source cell
cannot be selected as a target cell for load balancing.
If the number of UL-synchronized UEs in the source
cell is less than the value calculated by the
InterFreqMlbUeNumThd parameter value plus the
InterFrqUeNumOffloadOffset parameter value and
then minus the LoadOffset parameter value, the source
cell can be selected as a target cell for load balancing.
GUI Value Range: 0~10000
Unit: None
Actual Value Range: 0~10000
Default Value: 0
CellML MlbUeN MOD LOFD-0 Intra- Meaning: Indicates the offset of the number of
B umOffse CELLM 70215 / LTE synchronized UEs for triggering inter-frequency load
t LB TDLOF User balancing. User-number-based inter-frequency load
LST D-07021 Number balancing is triggered if the number of synchronized
CELLM 5 Load UEs in the cell is greater than or equal to the sum of
LB Balancin the InterFreqMlbUeNumThd and MlbUeNumOffset
g parameter values. User-number-based inter-frequency
load balancing to transfer to-be-released UEs is
triggered if the number of synchronized UEs in the
cell is greater than or equal to the sum of the
InterFreqIdleMlbUeNumThd and MlbUeNumOffset
parameter values.
GUI Value Range: 0~10000
Unit: None
Actual Value Range: 0~10000
Default Value: 20
CaMgtC Carrier MOD LAOFD Intra- Meaning: Indicates whether to enable carrier
fg MgtSwit CAMG -001001 Band management. If this parameter is set to ON(On), the
ch TCFG 01 Carrier eNodeB deactivates the secondary serving cell (SCell)
LST LAOFD Aggrega for a CA UE when the traffic volume of the CA UE is
CAMG -001001 tion for small or the channel quality of the SCell is poor. If
TCFG 02 Downlin this parameter is set to OFF(Off), the SCell is always
k 2CC active after being activated, unless a radio link failure
LAOFD in (RLF) is detected on the SCell.
-001002 20MHz
01 / GUI Value Range: OFF(Off), ON(On)
TDLAO Inter- Unit: None
FD-001 Band
Carrier Actual Value Range: OFF, ON
002
Aggrega Default Value: OFF(Off)
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaMgtC Deactive MOD LAOFD Intra- Meaning: Indicates the threshold for a CA UE to
fg Through CAMG -001001 Band deactivate an SCell. A CA UE can deactivate an SCell
putThd TCFG 01 Carrier only when its throughput is smaller than the value of
LST LAOFD Aggrega this parameter.
CAMG -001001 tion for GUI Value Range: 10~1000
TCFG 02 Downlin
k 2CC Unit: kbit/s
LAOFD in Actual Value Range: 10~1000
-001002 20MHz
01 / Default Value: 100
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaMgtC Deactive MOD LAOFD Intra- Meaning: Indicates the threshold for a CA UE to
fg BufferL CAMG -001001 Band deactivate an SCell. A CA UE can deactivate an SCell
enThd TCFG 01 Carrier only when its buffered data on the eNodeB is smaller
LST LAOFD Aggrega than this threshold.
CAMG -001001 tion for GUI Value Range: 1~10
TCFG 02 Downlin
k 2CC Unit: kB
LAOFD in Actual Value Range: 1~10
-001002 20MHz
01 / Default Value: 3
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
for UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for event A4
qHoGro qHoA4T INTERF 0201802 e Based related to coverage-based inter-frequency handover.
up hdRsrp REQHO / Inter- When the measured RSRP value exceeds this
GROUP TDLBF frequenc threshold, event A4 is reported. The value of this
MOD D-00201 y parameter is also used as the RSRP threshold for event
INTERF 802 Handov A4 related to distance-based, UL-power-based, or
REQHO LBFD-0 er SPID-based inter-frequency handover back to the
GROUP 0201804 Distance HPLMN.
LST / Based GUI Value Range: -140~-43
INTERF TDLBF Inter- Unit: dBm
REQHO D-00201 frequenc
804 y Actual Value Range: -140~-43
GROUP
Handov Default Value: -105
er
CaGrou SCellA4 ADD LAOFD Intra- Meaning: This parameter specifies the offset to
pSCellC Offset CAGRO -001001 Band CarrAggrA4ThdRsrp. When a CA UE treats the cell
fg UPSCE 01 Carrier specified by the LocalCellId parameter in the local
LLCFG LAOFD Aggrega eNodeB as its PCell, the UE reports event A4
MOD -001001 tion for pertaining to the candidate SCell specified by the
CAGRO 02 Downlin SCelleNodeBId and SCellLocalCellId parameters to
UPSCE k 2CC the eNodeB if the RSRP for the candidate SCell
LAOFD in exceeds the sum of the CarrAggrA4ThdRsrp and
LLCFG -001002 20MHz SCellA4Offset parameter values. If the sum is greater
LST 01 / than 43 dBm or less than 140 dBm, the threshold
CAGRO TDLAO Inter-
Band for event A4 takes the value 43 dBm or 140
UPSCE FD-001 dBm, respectively.
LLCFG 002 Carrier
Aggrega GUI Value Range: -35~62
LAOFD tion for
-001002 Unit: dBm
Downlin
02 / k 2CC Actual Value Range: -35~62
TDLAO in Default Value: 0
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaMgtC CarrAgg MOD LAOFD Intra- Meaning: Indicates the Reference Signal Received
fg rA2Thd CAMG -001001 Band Power (RSRP) threshold for reporting event A2 in a
Rsrp TCFG 01 Carrier secondary cell. When the RSRP of a UE is lower than
LST LAOFD Aggrega this threshold, event A2 is reported.
CAMG -001001 tion for GUI Value Range: -140~-43
TCFG 02 Downlin
k 2CC Unit: dBm
LAOFD in Actual Value Range: -140~-43
-001002 20MHz
01 / Default Value: -109
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou SCellA2 ADD LAOFD Intra- Meaning: Indicates the offset to CarrAggrA2ThdRsrp.
pSCellC Offset CAGRO -001001 Band When a CA UE treats the cell specified by the
fg UPSCE 01 Carrier LocalCellId parameter in the local eNodeB as its
LLCFG LAOFD Aggrega PCell, the UE reports event A2 pertaining to the
MOD -001001 tion for candidate SCell specified by the SCelleNodeBId and
CAGRO 02 Downlin SCellLocalCellId parameters to the eNodeB if the
UPSCE k 2CC RSRP for the candidate SCell exceeds the sum of the
LAOFD in CarrAggrA2ThdRsrp and SCellA2Offset parameter
LLCFG -001002 20MHz values. If the sum is greater than 43 dBm or less
LST 01 / than 140 dBm, the threshold for event A2 takes the
CAGRO TDLAO Inter-
Band value 43 dBm or 140 dBm, respectively.
UPSCE FD-001
LLCFG 002 Carrier GUI Value Range: -31~66
Aggrega Unit: dBm
LAOFD tion for
-001002 Downlin Actual Value Range: -31~66
02 / k 2CC Default Value: 0
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
SccFreq SccA2O ADD LAOFD Intra- Meaning: Indicates the offset of the actual threshold
Cfg ffset SCCFR -001001 Band for CA event A2relative to the value of the
EQCFG 01 Carrier CarrAggrA2ThdRsrp parameter in the CaMgtCfg
MOD LAOFD Aggrega MO. If the actual threshold is greater than -43 dBm,
SCCFR -001001 tion for the value of -43 dBm takes effect. If the actual
EQCFG 02 Downlin threshold is less than -140 dBm, the value of -140
k 2CC dBm takes effect.
LST LAOFD in
SCCFR -001002 GUI Value Range: -31~66
20MHz
EQCFG 01 Unit: dBm
Inter-
LAOFD Band Actual Value Range: -31~66
-001002 Carrier Default Value: 0
02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
EutranIn InterFre ADD LBFD-0 Coverag Meaning: Indicates the event to trigger coverage-
terNFre qHoEve EUTRA 0201802 e Based based inter-frequency handovers. This parameter can
q ntType NINTE / Inter- be set to EventA3, EventA4, or EventA5. If the
RNFRE TDLBF frequenc neighboring E-UTRAN frequency and the serving
Q D-00201 y frequency are in the same frequency band, event A3 is
MOD 802 Handov recommended as it provides better handover
EUTRA er performance in this situation. If the neighboring E-
NINTE UTRAN frequency and the serving frequency are in
RNFRE different frequency bands, event A4 or A5 is used.
Q GUI Value Range: EventA3(EventA3),
LST EventA4(EventA4), EventA5(EventA5)
EUTRA Unit: None
NINTE
Actual Value Range: EventA3, EventA4, EventA5
RNFRE
Q Default Value: EventA4(EventA4)
CellDlsc CaSchSt MOD LAOFD Intra- Meaning: Indicates the downlink scheduling policy
hAlgo rategy CELLD -001001 Band used when CA is applied, which can be basic
LSCHA 01 Carrier scheduling or differentiated scheduling. (If CA is
LGO LAOFD Aggrega applied in the uplink, this parameter also indicates the
LST -001001 tion for uplink scheduling polity.) If the CA basic scheduling
CELLD 02 Downlin policy is adopted, the eNodeB calculates the
LSCHA k 2CC proportional fair (PF) scheduling priority of each
LAOFD in component carrier (CC) for a CA UE using the total
LGO -001002 20MHz data rates on both CCs of this CA UE. In this way, CA
01 / UEs and non-CA UEs can be allocated similar number
TDLAO Inter-
Band of RBs. If the CA differentiated scheduling policy is
FD-001 adopted, the eNodeB calculates the PF scheduling
002 Carrier
Aggrega priority of each CC for a CA UE using the data rate
LAOFD tion for only on the primary component carrier (PCC) or
-001002 Downlin secondary component carrier (SCC) of this CA UE. In
02 / k 2CC this way, CA UEs can achieve better performance than
TDLAO in non-CA UEs.
FD-001 20MHz GUI Value Range: BASIC_SCHEDULE(Basic
00102 Schedule), DIFF_SCHEDULE(differentiation
Carrier
LAOFD Aggrega schedule)
-070201 tion for Unit: None
/ Downlin
TDLAO Actual Value Range: BASIC_SCHEDULE,
k 2CC DIFF_SCHEDULE
FD-070 in
201 40MHz Default Value: BASIC_SCHEDULE(Basic Schedule)
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
LOFD-0 CA
01015 / from
TDLOF Multiple
D-00101 Carriers
5 Inter-
LOFD-0 eNodeB
0101501 CA
/ based on
TDLOF Coordin
D-00101 ated
501 BBU
LOFD-0 Intra-
0101502 band
/ Carrier
TDLOF Aggrega
D-00101 tion for
502 Downlin
k 2CC
in
30MHz
Enhance
d
Scheduli
ng
CQI
Adjustm
ent
Dynami
c
Scheduli
ng
CellDlsc CaSccD MOD LAOFD Intra- Meaning: Indicates the method for measuring the
hAlgo opMeas CELLD -001001 Band Doppler frequency offset that is applied to frequency
LSCHA 01 / Carrier selective scheduling on the secondary component
LGO TDLAO Aggrega carrier (SCC) in carrier aggregation (CA). If this
LST FD-001 tion for parameter is set to FROMSCC, the Doppler frequency
CELLD 00101 Downlin offset on the SCC is measured. If this parameter is set
LSCHA LAOFD k 2CC to FROMPCC, the Doppler frequency offset on the
LGO -001001 in primary component carrier (PCC) is measured no
02 / 20MHz matter whether the SCC is configured with an uplink
TDLAO Inter- carrier, and then the Doppler frequency offset is
FD-001 Band applied to frequency selective scheduling on the SCC
00102 Carrier after converting downlink frequencies of the PCC and
Aggrega SCC.
LAOFD
-001002 tion for GUI Value Range: FROMSCC(FROMSCC),
01 / Downlin FROMPCC(FROMPCC)
TDLAO k 2CC Unit: None
FD-001 in
20MHz Actual Value Range: FROMSCC, FROMPCC
002
Carrier Default Value: FROMSCC(FROMSCC)
LAOFD
-001002 Aggrega
02 / tion for
TDLAO Downlin
FD-001 k 2CC
00102 in
40MHz
LAOFD
-070201 Support
/ of UE
TDLAO Categor
FD-070 y6
201 Flexible
LAOFD CA
-070202 from
Multiple
TDLAO Carriers
FD-001
00111 Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CellAlg EnhMI MOD LAOFD DL 2*2 Meaning: Indicates whether to enable enhanced
oSwitch MOSwit CELLA -080210 MIMO MIMO. This parameter now includes one switch.
ch LGOSW LAOFD based on TM9Switch: Indicates whether accessing UEs are
ITCH -080205 TM9 allowed to enter TM9 mode. Accessing UEs are
LST / DL 4*2 allowed to enter the TM9 mode only when this switch
CELLA TDLAO MIMO is on. This parameter does not apply to cells
LGOSW FD-001 based on established on the LBBPc.
ITCH 00113 TM9 GUI Value Range: TM9Switch(TM9Switch)
TDLAO DL 8x2 Unit: None
FD-001 MIMO Actual Value Range: TM9Switch
00114 based on
TM9 Default Value: TM9Switch:Off
TDLAO
FD-080 DL 4x4
406 MIMO
TDLAO based on
FD-080 TM9
407 DL 8x4
MIMO
based on
TM9
CellCsi CsiRsS MOD LOFD-0 DL 2*2 Meaning: Indicates whether to configure the CSI-RS.
RsParaC witch CELLC 01001 MIMO If this parameter is set to NOT_CFG, UEs are not
fg SIRSPA LOFD-0 DL 4*2 configured with CSI-RSs. If this parameter is set to
RACFG 01003 MIMO FIXD_CFG, UEs supporting CSI-RSs are configured
LST with a fixed CSI-RS. If this parameter is set to
LOFD-0 DL 4x4 ADAPTIVE_CFG, UEs supporting CSI-RSs are
CELLC 01060 MIMO
SIRSPA adaptively configured or not configured with the CSI-
RACFG TDLAO DL 2- RS based on the proportion of TM9-capable UEs. If
FD-001 Layer the SfnLoadBasedAdptSwitch parameter is set to
00114 MIMO OFF(Off) for an ASFN cell on an LTE TDD network,
TDLAO Based this parameter is invalid when it is set to
FD-081 on TM9 FIXED_CFG(Fixed configure) or
409 DL 4- ADAPTIVE_CFG(ADAPTIVE_CFG).
LAOFD Layer GUI Value Range: NOT_CFG(Not configure),
-080210 MIMO FIXED_CFG(Fixed configure),
Based ADAPTIVE_CFG(ADAPTIVE_CFG)
LAOFD on TM9
-080205 Unit: None
DL 2*2 Actual Value Range: NOT_CFG, FIXED_CFG,
MIMO ADAPTIVE_CFG
based on
TM9 Default Value: NOT_CFG(Not configure)
DL 4*2
MIMO
based on
TM9
Cell HighSpe ADD LOFD-0 High Meaning: Indicates the speed flag of the cell. Set this
edFlag CELL 01007 / Speed parameter to HIGH_SPEED if the cell is used to
MOD TDLOF Mobility provide coverage for an ultra-high-speed railway. Set
CELL D-00100 Ultra this parameter to LOW_SPEED in other scenarios.
7 High TDD cells with a bandwidth of 5 MHz or in 8T8R
LST mode can only be configured as low speed cells. TDD
CELL LOFD-0 Speed
01008 Mobility cells don't support ULTRA_HIGH_SPEED mode.
GUI Value Range: LOW_SPEED(Low speed cell
flag), HIGH_SPEED(High speed cell flag),
ULTRA_HIGH_SPEED(Ultra high speed cell flag),
EXTRA_HIGH_SPEED(Extra high speed cell flag)
Unit: None
Actual Value Range: LOW_SPEED, HIGH_SPEED,
ULTRA_HIGH_SPEED, EXTRA_HIGH_SPEED
Default Value: LOW_SPEED(Low speed cell flag)
EutranIn NoHoFl ADD LBFD-0 Coverag Meaning: Indicates whether handovers of UEs to the
terFreq ag EUTRA 0201802 e Based neighboring cell are prohibited.
NCell NINTE / Inter- GUI Value Range: PERMIT_HO_ENUM(Permit Ho),
RFREQ TDLBF frequenc FORBID_HO_ENUM(Forbid Ho)
NCELL D-00201 y
802 Handov Unit: None
MOD
EUTRA LBFD-0 er Actual Value Range: PERMIT_HO_ENUM,
NINTE 0201804 Distance FORBID_HO_ENUM
RFREQ / Based Default Value: PERMIT_HO_ENUM(Permit Ho)
NCELL TDLBF Inter-
LST D-00201 frequenc
EUTRA 804 y
NINTE LBFD-0 Handov
RFREQ 0201805 er
NCELL / Service
TDLBF Based
D-00201 Inter-
805 frequenc
LOFD-0 y
02012 / Handov
TDLOF er
D-00201 Cell
2 Outage
Detectio
n and
Compen
sation
Cell WorkM ADD LAOFD Intra- Meaning: Indicates the work mode of the cell. The
ode CELL -001001 Band DL_ONLY mode applies only to the carrier
MOD 01 Carrier aggregation scenario.
CELL LAOFD Aggrega GUI Value Range: UL_DL(Uplink and downlink),
-001001 tion for DL_ONLY(Downlink only)
LST Downlin
CELL 02 Unit: None
k 2CC
LAOFD Actual Value Range: UL_DL, DL_ONLY
-001002 Inter-
01 Band Default Value: UL_DL(Uplink and downlink)
Carrier
LAOFD Aggrega
-001002 tion for
02 Downlin
TDLAO k 2CC
FD-001 Carrier
003 Aggrega
TDLAO tion for
FD-001 Downlin
002 k 2CC
in
40MHz
Support
of UE
Categor
y6
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Cell FreqBan ADD LBFD-0 Cell Meaning: Indicates the frequency band in which the
d CELL 0201803 Selectio cell operates. For details about this parameter, see
ADD / n and 3GPP TS 36.104.
CELLB TDLBF Re- GUI Value Range: 1~64
AND D-00201 selection
803 Unit: None
LST Broadca
LBFD-0 st of Actual Value Range: 1~64
CELLB
AND 02009 / system Default Value: None
TDLBF informat
MOD D-00200 ion
CELL 9 Multi-
RMV LBFD-0 Band
CELLB 70103 / Compati
AND TDLBF bility
LST D-00201 Enhance
CELL 806 ment
Cell UlEarfc ADD LBFD-0 Coverag Meaning: Indicates the UL EARFCN of the cell. It is
n CELL 0201801 e Based optional, depending on the setting of the UL EARFCN
MOD / Intra- configuration indicator (UlEarfcnCfgInd). If the value
CELL TDLBF frequenc of this parameter is not specified, the default UL
D-00201 y EARFCN is used, which is calculated based on the
LST 801 Handov DL EARFCN. For details, see 3GPP TS 36.104.
CELL er
LBFD-0 GUI Value Range: 18000~46589,54436~65535
0201803 Cell Unit: None
/ Selectio
TDLBF n and Actual Value Range: 18000~46589,54436~65535
D-00201 Re- Default Value: 18000
803 selection
LBFD-0 Broadca
02009 / st of
TDLBF system
D-00200 informat
9 ion
EutranIn AnrInd ADD LOFD-0 Automat Meaning: Indicates whether information about inter-
terNFre EUTRA 02001 / ic frequency neighboring cells and external cells
q NINTE TDLOF Neighbo configured on the frequency associated with the
RNFRE D-00200 ur serving cell can be maintained by ANR. If this
Q 1 Relation parameter is set to ALLOWED, the information can
MOD (ANR) be maintained by ANR. If this parameter is set to
EUTRA NOT_ALLOWED, the information cannot be
NINTE maintained by ANR.
RNFRE GUI Value Range:
Q NOT_ALLOWED(NOT_ALLOWED),
LST ALLOWED(ALLOWED)
EUTRA Unit: None
NINTE
Actual Value Range: NOT_ALLOWED, ALLOWED
RNFRE
Q Default Value: ALLOWED(ALLOWED)
EutranIn MlbTarg ADD LOFD-0 Intra- Meaning: Indicates whether the neighboring
terNFre etInd EUTRA 01032 / LTE frequency of the serving frequency can be a target
q NINTE TDLOF Load frequency in load balancing. If this parameter is set to
RNFRE D-00103 Balancin ALLOWED, the neighboring frequency of the serving
Q 2 g frequency can be selected as a target frequency in load
MOD balancing. If this parameter is set to
EUTRA NOT_ALLOWED, the neighboring frequency of the
NINTE serving frequency cannot be selected as a target
RNFRE frequency in load balancing.
Q GUI Value Range:
LST NOT_ALLOWED(NOT_ALLOWED),
EUTRA ALLOWED(ALLOWED)
NINTE Unit: None
RNFRE Actual Value Range: NOT_ALLOWED, ALLOWED
Q
Default Value: ALLOWED(ALLOWED)
CaGrou CaGrou ADD LAOFD Intra- Meaning: Indicates the identity of the CA group. It
pCell pId CAGRO -001001 Band uniquely identifies a CA group within an eNodeB.
UPCEL 01 Carrier GUI Value Range: 0~35
L LAOFD Aggrega
tion for Unit: None
DSP -001001
CAGRO 02 Downlin Actual Value Range: 0~35
UPCEL k 2CC Default Value: None
LAOFD in
L -001002 20MHz
LST 01 /
CAGRO TDLAO Inter-
UPCEL FD-001 Band
L 002 Carrier
Aggrega
MOD LAOFD tion for
CAGRO -001002 Downlin
UPCEL 02 / k 2CC
L TDLAO in
RMV FD-001 20MHz
CAGRO 00102
Carrier
UPCEL LAOFD Aggrega
L -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou LocalCe ADD LAOFD Intra- Meaning: Indicates the local ID of the cell, which
pSCellC llId CAGRO -001001 Band uniquely identifies a cell within an eNodeB.
fg UPSCE 01 Carrier GUI Value Range: 0~255
LLCFG LAOFD Aggrega
tion for Unit: None
LST -001001
CAGRO 02 Downlin Actual Value Range: 0~255
UPSCE k 2CC Default Value: None
LAOFD in
LLCFG -001002 20MHz
MOD 01 /
CAGRO TDLAO Inter-
UPSCE FD-001 Band
LLCFG 002 Carrier
Aggrega
RMV LAOFD tion for
CAGRO -001002 Downlin
UPSCE 02 / k 2CC
LLCFG TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou eNodeB ADD LAOFD Intra- Meaning: Indicates the ID of the eNodeB serving the
pCell Id CAGRO -001001 Band cell.
UPCEL 01 Carrier GUI Value Range: 0~1048575
L LAOFD Aggrega
tion for Unit: None
LST -001001
CAGRO 02 Downlin Actual Value Range: 0~1048575
UPCEL k 2CC Default Value: None
LAOFD in
L -001002 20MHz
MOD 01 /
CAGRO TDLAO Inter-
UPCEL FD-001 Band
L 002 Carrier
Aggrega
RMV LAOFD tion for
CAGRO -001002 Downlin
UPCEL 02 / k 2CC
L TDLAO in
DSP FD-001 20MHz
CAGRO 00102
Carrier
UPCEL LAOFD Aggrega
L -070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
SccFreq PccDlEa ADD LAOFD Intra- Meaning: Indicates the downlink E-UTRA absolute
Cfg rfcn SCCFR -001001 Band radio frequency channel number (EARFCN) of the
EQCFG 01 Carrier PCC.
LST LAOFD Aggrega GUI Value Range: 0~46589,54436~65535
SCCFR -001001 tion for
Downlin Unit: None
EQCFG 02
k 2CC Actual Value Range: 0~46589,54436~65535
MOD LAOFD in
SCCFR -001002 Default Value: None
20MHz
EQCFG 01
Inter-
RMV LAOFD Band
SCCFR -001002 Carrier
EQCFG 02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
SccFreq SccDlEa ADD LAOFD Intra- Meaning: Indicates the downlink EARFCN of the
Cfg rfcn SCCFR -001001 Band candidate SCC.
EQCFG 01 Carrier GUI Value Range: 0~46589,54436~65535
LST LAOFD Aggrega
tion for Unit: None
SCCFR -001001
EQCFG 02 Downlin Actual Value Range: 0~46589,54436~65535
k 2CC Default Value: None
MOD LAOFD in
SCCFR -001002 20MHz
EQCFG 01
Inter-
RMV LAOFD Band
SCCFR -001002 Carrier
EQCFG 02 Aggrega
LAOFD tion for
-070201 Downlin
LAOFD k 2CC
-070202 in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CaMgtC ActiveB MOD LAOFD Intra- Meaning: Indicates the threshold for a CA UE to
fg ufferLen CAMG -001001 Band activate an SCell. A CA UE can active an SCell only
Thd TCFG 01 Carrier when its buffered data on the eNodeB exceeds this
LST LAOFD Aggrega threshold.
CAMG -001001 tion for GUI Value Range: 0~30
TCFG 02 Downlin
k 2CC Unit: kB
LAOFD in Actual Value Range: 0~30
-001002 20MHz
01 / Default Value: 9
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
D-00107 Distance
3 based
inter-
RAT
handove
r to
GERAN
Mobility
Manage
ment
CaMgtC ActiveB MOD LAOFD Intra- Meaning: Indicates the threshold for a CA UE to
fg ufferDel CAMG -001001 Band activate an SCell. A CA UE can activate an SCell only
ayThd TCFG 01 Carrier when its buffer delay on the eNodeB exceeds this
LST LAOFD Aggrega threshold.
CAMG -001001 tion for GUI Value Range: 0~300
TCFG 02 Downlin
k 2CC Unit: ms
LAOFD in Actual Value Range: 0~300
-001002 20MHz
01 / Default Value: 50
TDLAO Inter-
FD-001 Band
002 Carrier
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC
TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou SCellLo ADD LAOFD Intra- Meaning: Indicates the local cell ID of the candidate
pSCellC calCellI CAGRO -001001 Band secondary serving cell (SCell).
fg d UPSCE 01 Carrier GUI Value Range: 0~255
LLCFG LAOFD Aggrega
tion for Unit: None
LST -001001
CAGRO 02 Downlin Actual Value Range: 0~255
UPSCE k 2CC Default Value: None
LAOFD in
LLCFG -001002 20MHz
MOD 01 /
CAGRO TDLAO Inter-
UPSCE FD-001 Band
LLCFG 002 Carrier
Aggrega
RMV LAOFD tion for
CAGRO -001002 Downlin
UPSCE 02 / k 2CC
LLCFG TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaGrou SCelleN ADD LAOFD Intra- Meaning: Indicates the ID of the eNodeB to which the
pSCellC odeBId CAGRO -001001 Band candidate secondary serving cell (SCell) belongs.
fg UPSCE 01 Carrier GUI Value Range: 0~1048575
LLCFG LAOFD Aggrega
tion for Unit: None
LST -001001
CAGRO 02 Downlin Actual Value Range: 0~1048575
UPSCE k 2CC Default Value: None
LAOFD in
LLCFG -001002 20MHz
MOD 01 /
CAGRO TDLAO Inter-
UPSCE FD-001 Band
LLCFG 002 Carrier
Aggrega
RMV LAOFD tion for
CAGRO -001002 Downlin
UPSCE 02 / k 2CC
LLCFG TDLAO in
FD-001 20MHz
00102
Carrier
LAOFD Aggrega
-070201 tion for
/ Downlin
TDLAO k 2CC
FD-070 in
201 40MHz
LAOFD Support
-070202 of UE
TDLAO Categor
FD-001 y6
00111 Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
CaMgtC SCellAg MOD TDLAO Intra- Meaning: Indicates the length of aging time of the
fg ingTime CAMG FD-001 band SCells that are dynamically configured for CA UEs in
TCFG 00111 Carrier a cell in frequency-based CA configuration scenarios.
LST TDLAO Aggrega If no CA UE is performing carrier aggregation
CAMG FD-001 tion for between an SCell and the PCell within the aging time,
TCFG 002 Downlin the eNodeB cancels the association between the SCell
k 2CC and the PCell.
TDLAO in
FD-001 GUI Value Range: 1~65535
30MHz
00102 Unit: min
Carrier
TDLAO Aggrega Actual Value Range: 1~65535
FD-070 tion for Default Value: 15
201 Downlin
LAOFD k 2CC
-001001 in
01 40MHz
LAOFD Support
-001001 for UE
02 Categor
LAOFD y6
-001002 Flexible
01 CA
LAOFD from
-001002 Multiple
02 Carriers
LAOFD Intra-
-070201 Band
Carrier
LAOFD
Aggrega
-070202
tion for
Downlin
k 2CC
in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CaMgtC CaA6Re MOD TDLAO Intra- Meaning: Indicates the number of periodic
fg portAm CAMG FD-001 band measurement reports sent after CA event A6 is
ount TCFG 00111 Carrier triggered. For details, see 3GPP TS 36.331.
LST TDLAO Aggrega GUI Value Range: r1(1), r2(2), r4(4), r8(8), r16(16),
CAMG FD-001 tion for r32(32), r64(64), Infinity(Infinity)
TCFG 002 Downlin
k 2CC Unit: None
TDLAO in Actual Value Range: r1, r2, r4, r8, r16, r32, r64,
FD-001 30MHz Infinity
00102
Carrier Default Value: r8(8)
TDLAO Aggrega
FD-070 tion for
201 Downlin
LAOFD k 2CC
-001001 in
01 40MHz
LAOFD Support
-001001 for UE
02 Categor
LAOFD y6
-001002 Flexible
01 CA
LAOFD from
-001002 Multiple
02 Carriers
LAOFD Intra-
-070201 Band
Carrier
LAOFD
Aggrega
-070202
tion for
Downlin
k 2CC
in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
CaMgtC CaA6Re MOD TDLAO Intra- Meaning: Indicates the interval between periodic
fg portInter CAMG FD-001 band measurement reports that are sent after CA event A6
val TCFG 00111 Carrier is triggered. For details, see 3GPP TS 36.331.
LST TDLAO Aggrega GUI Value Range: 120ms, 240ms, 480ms, 640ms,
CAMG FD-001 tion for 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min,
TCFG 002 Downlin 12min, 30min, 60min
k 2CC
TDLAO in Unit: None
FD-001 30MHz Actual Value Range: 120ms, 240ms, 480ms, 640ms,
00102 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min,
Carrier
TDLAO Aggrega 12min, 30min, 60min
FD-070 tion for Default Value: 10240ms
201 Downlin
LAOFD k 2CC
-001001 in
01 40MHz
LAOFD Support
-001001 for UE
02 Categor
LAOFD y6
-001002 Flexible
01 CA
LAOFD from
-001002 Multiple
02 Carriers
LAOFD Intra-
-070201 Band
Carrier
LAOFD
Aggrega
-070202
tion for
Downlin
k 2CC
in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC
in
40MHz
Support
of UE
Categor
y6
Flexible
CA
from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch,
UlMbrCtrlSwitch, MbrUlSchSwitch,
UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,
UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,
UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,
ULFSSAlgoSwitch, PrachRbReuseSwitch,
SrSchDataAdptSw, UlFssUserThdStSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:Off,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On, UlEnhancedSrSchS-
witch:Off, SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off, UlEnhancedDopplerS-
witch:Off, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:Off,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off
15 Counters
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 4CC
Carrier Aggregation
for Downlink 4CC
Carrier Aggregation
for Downlink 4CC
Carrier Aggregation
for Downlink 4CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
Carrier Aggregation
for Downlink 3CC
16 Glossary
17 Reference Documents