Carrier Aggregation (eRAN TDD 8.1 02) FPD PDF

eRAN TDD
Carrier Aggregation Feature

Parameter Description
Issue 02
Date 2015-05-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2015-05-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN TDD
Carrier Aggregation Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................2
1.3 Change History...............................................................................................................................................................2
2 Overview.......................................................................................................................................12
2.1 Introduction..................................................................................................................................................................12
2.2 Benefits.........................................................................................................................................................................12
2.3 Architecture..................................................................................................................................................................13
3 Technical Description.................................................................................................................15
3.1 Function Overview.......................................................................................................................................................15
3.1.1 Related Concepts.......................................................................................................................................................15
3.1.2 Usage Scenarios.........................................................................................................................................................16
3.1.2.1 Typical Scenarios...................................................................................................................................................16
3.1.2.2 Atypical Scenarios..................................................................................................................................................19
3.1.3 CA Features...............................................................................................................................................................19
3.1.3.1 TDLAOFD-001001 LTE-A Introduction...............................................................................................................20
3.1.3.2 TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz...............................................................21
3.1.3.3 TDLAOFD-070201 Flexible CA from Multiple Carriers......................................................................................22
3.1.3.4 TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]..........................................................22
3.1.3.5 TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial].........................................................................23
3.1.3.6 TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial].....................................................................24
3.1.3.7 TDLAOFD-081404 Carrier Aggregation for Downlink 4CC [Trial].....................................................................24
3.1.3.8 MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [Trial]....................................................................24
3.1.4 Band Combinations...................................................................................................................................................25
3.2 Carrier Management.....................................................................................................................................................31
3.2.1 Overview...................................................................................................................................................................32
3.2.2 PCC Anchoring (at Initial Access)............................................................................................................................34
3.2.2.1 CA-Group-based PCC Anchoring..........................................................................................................................34
3.2.2.2 Frequency-based or Adaptive PCC Anchoring......................................................................................................36
3.2.3 SCell Configuration...................................................................................................................................................38
3.2.3.1 CA-Group-based SCell Configuration...................................................................................................................40
3.2.3.2 Frequency-based SCell Configuration....................................................................................................................46
Issue 02 (2015-05-15) Huawei Proprietary and Confidential ii

eRAN TDD
3.2.3.3 Adaptive SCell Configuration................................................................................................................................52

3.2.3.4 Load-based SCell Configuration............................................................................................................................60
3.2.4 SCell Change.............................................................................................................................................................61
3.2.5 SCell Activation........................................................................................................................................................61
3.2.6 SCell Deactivation.....................................................................................................................................................62
3.2.7 SCell Removal...........................................................................................................................................................63
3.2.8 PCC Anchoring (at RRC Connection Releases)........................................................................................................65
3.3 Other Key Techniques Under CA................................................................................................................................65
3.3.1 Connection Management Under CA.........................................................................................................................66
3.3.2 Mobility Management Under CA..............................................................................................................................66
3.3.3 Admission and Congestion Control Under CA.........................................................................................................69
3.3.4 Scheduling Under CA................................................................................................................................................70
3.3.5 MIMO Under CA......................................................................................................................................................71
3.3.6 DRX Control Under CA............................................................................................................................................72
3.3.7 RAN Sharing Under CA............................................................................................................................................73
3.3.8 Power Backoff Under CA..........................................................................................................................................73
3.3.9 Load Balancing Under CA........................................................................................................................................74
4 Related Features...........................................................................................................................75
4.1 Features Related to TDLAOFD-001001 LTE-A Introduction.....................................................................................75
4.2 Features Related to TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.....................................76
4.3 Features Related to TDLAOFD-070201 Flexible CA from Multiple Carriers............................................................77
4.4 Features Related to TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]................................77
4.5 Features Related to TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial]................................................78
4.6 Features Related to TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial]...........................................79
4.7 Features Related to TDLAOFD-081404 Carrier Aggregation for Downlink 4CC [Trial]...........................................79
4.8 Features Related to MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [Trial]..........................................80
5 Network Impact...........................................................................................................................83
5.1 TDLAOFD-001001 LTE-A Introduction.....................................................................................................................83
5.2 TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.....................................................................84
5.3 TDLAOFD-070201 Flexible CA from Multiple Carriers............................................................................................85
5.4 TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]................................................................85
5.5 TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial]...............................................................................85
5.6 TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial]...........................................................................86
5.7 TDLAOFD-081404 Carrier Aggregation for Downlink 4CC [Trial]...........................................................................86
5.8 MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [Trial]..........................................................................86
6 Engineering Guidelines for TDLAOFD-001001 LTE-A Introduction and

TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz...............................87
6.1 When to Use TDLAOFD-001001 and TDLAOFD-001002.........................................................................................87
6.2 Required Information...................................................................................................................................................87
6.3 Planning........................................................................................................................................................................88
Issue 02 (2015-05-15) Huawei Proprietary and Confidential iii

eRAN TDD
6.4 Deployment..................................................................................................................................................................89
6.4.1 Requirements.............................................................................................................................................................89
6.4.2 Data Preparation........................................................................................................................................................90
6.4.3 Precautions.................................................................................................................................................................94
6.4.4 Hardware Adjustment................................................................................................................................................96
6.4.5 Activation..................................................................................................................................................................97
6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................97
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.............................................................100
6.4.5.3 Using the CME to Perform Single Configuration................................................................................................101
6.4.5.4 Using Feature Operation and Maintenance on the CME......................................................................................102
6.4.5.5 Using MML Commands.......................................................................................................................................103
6.4.6 Activation Observation............................................................................................................................................106
6.4.7 Deactivation.............................................................................................................................................................111
6.4.7.1 Using the CME to Perform Batch Configuration.................................................................................................111
6.4.7.2 Using the CME to Perform Single Configuration................................................................................................112
6.4.7.3 Using MML Commands.......................................................................................................................................112
6.5 Performance Monitoring.............................................................................................................................................114
6.6 Parameter Optimization..............................................................................................................................................116
6.7 Troubleshooting..........................................................................................................................................................135
7 Engineering Guidelines for TDLAOFD-070201 Flexible CA from Multiple Carriers

..........................................................................................................................................................139
7.1 When to Use TDLAOFD-070201..............................................................................................................................139
7.2 Required Information.................................................................................................................................................139
7.3 Planning......................................................................................................................................................................139
7.4 Deployment................................................................................................................................................................140
7.4.1 Requirements...........................................................................................................................................................140
7.4.2 Data Preparation......................................................................................................................................................141
7.4.3 Precautions...............................................................................................................................................................141
7.4.4 Hardware Adjustment..............................................................................................................................................141
7.4.5 Activation................................................................................................................................................................141
7.4.7 Deactivation.............................................................................................................................................................142
8 Engineering Guidelines for TDLAOFD-081402 Inter-eNodeB CA based on Relaxed

Backhaul [Trial]............................................................................................................................143
8.3 Planning......................................................................................................................................................................143
8.4 Deployment................................................................................................................................................................144
Issue 02 (2015-05-15) Huawei Proprietary and Confidential iv

eRAN TDD
8.4.1 Requirements...........................................................................................................................................................144
8.4.3 Precautions...............................................................................................................................................................147
8.4.5 Activation................................................................................................................................................................148
8.4.7 Deactivation.............................................................................................................................................................149
9 Engineering Guidelines for TDLAOFD-081407 Carrier Aggregation for Uplink 2CC

[Trial]...............................................................................................................................................152
9.3 Planning......................................................................................................................................................................152
9.4 Deployment................................................................................................................................................................152
9.4.1 Requirements...........................................................................................................................................................153
9.4.3 Precautions...............................................................................................................................................................154
9.4.5 Activation................................................................................................................................................................154
9.4.7 Deactivation.............................................................................................................................................................158
10 Engineering Guidelines for TDLAOFD-081405 Carrier Aggregation for Downlink 3CC

[Trial]...............................................................................................................................................161
10.1 When to Use TDLAOFD-081405............................................................................................................................161
10.2 Required Information...............................................................................................................................................161
10.3 Planning....................................................................................................................................................................161
10.4 Deployment..............................................................................................................................................................161
10.4.1 Requirements.........................................................................................................................................................162
10.4.2 Data Preparation....................................................................................................................................................163
10.4.3 Precautions.............................................................................................................................................................163
10.4.4 Hardware Adjustment............................................................................................................................................163
10.4.5 Activation..............................................................................................................................................................163
10.4.6 Activation Observation..........................................................................................................................................164
10.4.7 Deactivation...........................................................................................................................................................167
10.5 Performance Monitoring...........................................................................................................................................168
10.6 Parameter Optimization............................................................................................................................................168
Issue 02 (2015-05-15) Huawei Proprietary and Confidential v

eRAN TDD
10.7 Troubleshooting........................................................................................................................................................168
11 Engineering Guidelines for TDLAOFD-081404 Carrier Aggregation for Downlink 4CC

[Trial]...............................................................................................................................................169
11.1 When to Use TDLAOFD-081404............................................................................................................................169
11.3 Planning....................................................................................................................................................................169
11.4 Deployment..............................................................................................................................................................169
11.4.1 Requirements.........................................................................................................................................................170
11.4.3 Precautions.............................................................................................................................................................171
11.4.5 Activation..............................................................................................................................................................172
11.4.7 Deactivation...........................................................................................................................................................175
12 Engineering Guidelines for MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD)

[Trial]...............................................................................................................................................177
12.1 When to Use MRFD-101231....................................................................................................................................177
12.3 Planning....................................................................................................................................................................177
12.4 Deployment..............................................................................................................................................................178
12.4.1 Requirements.........................................................................................................................................................178
12.4.3 Precautions.............................................................................................................................................................181
12.4.5 Activation..............................................................................................................................................................182
12.4.7 Deactivation...........................................................................................................................................................184
13 Parameters.................................................................................................................................188
14 Counters....................................................................................................................................316
15 Glossary.....................................................................................................................................352
16 Reference Documents.............................................................................................................353
Issue 02 (2015-05-15) Huawei Proprietary and Confidential vi

eRAN TDD
Carrier Aggregation Feature Parameter Description 1 About This Document
1 About This Document
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 TDLAOFD-001001 LTE-A Introduction
– TDLAOFD-00100111 Intra-band Carrier Aggregation for Downlink 2CC in 30MHz
– TDLAOFD-00100102 Support for UE Category 6
l TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
l TDLAOFD-070201 Flexible CA from Multiple Carriers
l TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]
l TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial]
l TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial]
l MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [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 TDD. Any "LTE" in this document refers to LTE TDD, and
"eNodeB" refers to LTE TDD eNodeB.
Issue 02 (2015-05-15) Huawei Proprietary and Confidential 1

eRAN TDD
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro DBS3900 LTE TDD
LampSite DBS3900 LampSite TDD
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

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

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

Type Entity
Feature Added adaptive configuration mode, Added the option Macro, micro,
change and updated the entire document AdpCaSwitch to the and LampSite
accordingly. parameter eNodeBs
ENodeBAlgoSwitch.
CaAlgoSwitch.

eRAN TDD

Type Entity
Deleted enhanced DL ACK Removed the option Macro, micro,

demodulation for 2CC aggregation. Tdd2CCDlCaEnhan and LampSite
For details, see: ceSwitch from the eNodeBs
l 3.1.3.1 TDLAOFD-001001 LTE- parameter
A Introduction CaMgtCfg.CellCaAl
goSwitch.
l 3.1.3.2 TDLAOFD-001002
Carrier Aggregation for
Downlink 2CC in 40MHz
l 6.4.3 Precautions
l 6.6 Parameter Optimization
Editorial Revised event A6-related descriptions. None N/A

change For details, see 3.1.1 Related
Concepts.
Modified band combinations. For None N/A

details, see 3.1.4 Band
Combinations.
Revised the descriptions of None N/A

configuration modes. For details, see
3.2.1 Overview.
Revised the description of the None N/A

procedure for AMBR-based control
over the number of UEs configured
with SCells. For details, see 3.2.3
SCell Configuration.
Revised the description of impacted None N/A

features in 4.1 Features Related to
TDLAOFD-001001 LTE-A
Introduction and 4.8 Features
Related to MRFD-101231 FDD
+TDD Carrier Aggregation(LTE
TDD) [Trial].
Revised the description of network None N/A

planning. For details, see 6.3
Planning.
Revised precautions in 6.4.3 None N/A

Precautions.

eRAN TDD

Type Entity
Revised the description of CME-based None N/A

batch configuration for newly
deployed eNodeBs. For details, see
6.4.5.1 Using the CME to Perform
Batch Configuration for Newly
Deployed eNodeBs.
Revised descriptions in 6.7 None N/A

Troubleshooting.
Revised descriptions of the None N/A

transmission networking requirements
and deactivation of relaxed-backhaul-
based inter-eNodeB CA. For details,
see 8.4.1 Requirements and 8.4.7
Deactivation.
Revised descriptions of the activation, None N/A

activation observation, and
deactivation of uplink 2CC
aggregation. For details, see:
l 9.4.5 Activation
l 9.4.6 Activation Observation
l 9.4.7 Deactivation

deactivation of downlink 3CC
l 10.4.5 Activation

deactivation of downlink 4CC
l 11.4.5 Activation
Removed the requirements for EPC None N/A

versions from the engineering
guidelines for each feature.

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


Type Entity
Feature Added descriptions of frequency- Added the option Macro, micro,

change priority-based handovers. For details, FreqPriBasedHoCa- and LampSite
see 3.3.2 Mobility Management FiltSwitch to the eNodeBs
Under CA. parameter
ENodeBAlgoSwitch.
CaAlgoSwitch.
Modified the band combinations that None Macro and

support FDD+TDD CA. For details, LampSite
see 3.1.4 Band Combinations. eNodeBs
Canceled the license for FDD+TDD None Macro and

CA. For details, see 12.4.1 LampSite
Requirements. eNodeBs
Editorial Revised the description in 3.3.9 Load None N/A

change Balancing Under CA.
Revised the description of the None N/A

functional architecture in 2.3
Architecture.
Revised the description in 3.2.3.2 None N/A

Frequency-based SCell
Configuration.
Revised the description of impacted None N/A

features in 4.5 Features Related to
TDLAOFD-081407 Carrier
Aggregation for Uplink 2CC
[Trial].
Revised the description in 6.4.5.4 None N/A

Using Feature Operation and
Maintenance on the CME.
Revised the feature activation and None N/A

deactivation procedures in 6
Engineering Guidelines for
Introduction and
Aggregation for Downlink 2CC in
40MHz.
Modified the alarms in 6.7 None N/A

Troubleshooting.

eRAN TDD

Type Entity
Revised the description of hardware None N/A

planning for FDD+TDD CA in 12.3
Planning.
Revised the description of FDD+TDD None N/A

CA monitoring in 12.5 Performance
Monitoring.
eRAN TDD 8.1 Draft B (2015-02-10)


Type Entity
Feature Added the description of terminal Added the options Macro, micro,
change awareness differentiation in CA CaSwitchOff and and LampSite
scenarios. For details, see 6.4.3 Tdd2CCDlCaEnhan eNodeBs
Precautions. ceSwitchOff to the
parameter
UECOMPATOPT.B
lkLstCtrlSwitch.
Editorial Revised the priority description of None N/A

change intra-frequency cells in CA-group-
based PCC anchoring. For details, see
3.2.2.1 CA-Group-based PCC
Anchoring.
Revised the feature activation and None N/A

deactivation procedures in 6
Introduction and
40MHz.
eRAN TDD 8.1 Draft A (2015-01-15)

Compared with Issue 03 (2014-11-20) of eRAN TDD 8.0, Draft A (2015-01-15) of eRAN TDD
8.1 includes the following changes.

eRAN TDD
Chang Change Description Parameter Change Affected

e Type Entity
Feature Added relaxed-backhaul-based inter- Added the option Macro,

change eNodeB CA. For details, see: RelaxedBackhaul- micro, and
l 3.1.3.4 TDLAOFD-081402 Inter- CaSwitch to the LampSite
eNodeB CA based on Relaxed parameter eNodeBs
Backhaul [Trial] (feature ENodeBAlgoSwitch.
description) CaAlgoSwitch.
l 4.4 Features Related to

TDLAOFD-081402 Inter-eNodeB
CA based on Relaxed Backhaul
[Trial]
l 5.4 TDLAOFD-081402 Inter-
eNodeB CA based on Relaxed
Backhaul [Trial] (network impact)
l 8 Engineering Guidelines for
TDLAOFD-081402 Inter-eNodeB
CA based on Relaxed Backhaul
[Trial]
Added uplink 2CC aggregation. For Added the option Macro and
details, see: CaUl2CCSwitch to LampSite
l 3.1.3.5 TDLAOFD-081407 Carrier the parameter eNodeBs
Aggregation for Uplink 2CC CaMgtCfg.CellCaAl
[Trial] (feature description) goSwitch.

[Trial]
l 5.5 TDLAOFD-081407 Carrier
[Trial] (network impact)
[Trial]

eRAN TDD

e Type Entity
Added downlink 3CC aggregation. For Added the option Macro and
details, see: CaDl3CCSwitch to LampSite
Aggregation for Downlink 3CC CaMgtCfg.CellCaAl

Aggregation for Downlink 3CC
[Trial]
[Trial]
Added downlink 4CC aggregation. For Added the option Macro and
details, see: CaDl4CCSwitch to LampSite
Aggregation for Downlink 4CC CaMgtCfg.CellCaAl

[Trial]
[Trial]

eRAN TDD

e Type Entity
Added FDD+TDD CA. For details, see: l Added the option Macro and
l 3.1.3.8 MRFD-101231 FDD+TDD InterFddTddCa LampSite
Carrier Aggregation(LTE TDD) Switch to the eNodeBs
[Trial] (feature description) parameter
ENodeBAlgoSwi
l 4.8 Features Related to tch.CaAlgoSwitc
MRFD-101231 FDD+TDD h.
Carrier Aggregation(LTE TDD)
[Trial] l Added the
following
l 5.8 MRFD-101231 FDD+TDD parameters:
[Trial] (network impact) – ENodeBFram
eOffset.
l 12 Engineering Guidelines for FddFrameOff
MRFD-101231 FDD+TDD set
[Trial] – ENodeBFram
eOffset.
TddFrameOff
set
– CellFrameOff
set.
LocalCellId
– CellFrameOff
set.
FrameOffset
Mode
– CellFrameOff
set.
FrameOffset
l Added the option
FDDTDD to the
parameter
CaGroup.CaGro
upTypeInd.
Added AMBR-based control over the Added the following Macro,

number of UEs configured with SCells. parameters: micro, and
For details, see 3.2.3 SCell l CaMgtCfg. LampSite
Configuration. CellMaxPccNum eNodeBs
ber
l CaMgtCfg.
CaAmbrThd

eRAN TDD

e Type Entity
Changed the name of None Macro,

TDLAOFD-070201 from "CA for micro, and
Downlink 2CC From Multiple Carriers" LampSite
to "Flexible CA from Multiple Carriers". eNodeBs
For details, see:
l 3.1.3.3 TDLAOFD-070201
Flexible CA from Multiple
Carriers
TDLAOFD-070201 Flexible CA
from Multiple Carriers
l 5.3 TDLAOFD-070201 Flexible
CA from Multiple Carriers
TDLAOFD-070201 Flexible CA
from Multiple Carriers
Added implementation of features in CA None Macro,

scenarios. For details, see: micro, and
l 3.3.8 Power Backoff Under CA LampSite
eNodeBs
l 3.3.9 Load Balancing Under CA
Added the following sub-features to None Macro,

TDLAOFD-001001 LTE-A micro, and
Introduction, as described in 1.1 Scope LampSite
and 3.1.3 CA Features: eNodeBs
l TDLAOFD-00100102 Support for
UE Category 6
UE Category 7
UE Category 9
UE Category 10
Modified the feature None Macro,

TDLAOFD-001002 Carrier micro, and
Aggregation for Downlink 2CC in LampSite
40MHz by deleting its sub-feature eNodeBs
40MHz. For details, see 1.1 Scope and
3.1.3 CA Features.

eRAN TDD

e Type Entity
Added band combinations. For details, None Macro,

see 3.1.4 Band Combinations. micro, and
LampSite
eNodeBs
Added frequency-based configuration. None Macro,

For details, see descriptions throughout micro, and
this document. LampSite
eNodeBs
Added load-based SCell configuration. Added the option Macro,

For details, see 3.2.3.4 Load-based SccSmartCfgSwitch micro, and
SCell Configuration. to the parameter LampSite
ENodeBAlgoSwitch. eNodeBs
CaAlgoSwitch.
Added PCC anchoring at RRC Added the option Macro,

connection releases. For details, see IdleModePccAn- micro, and
3.2.8 PCC Anchoring (at RRC chorSwitch to the LampSite
Connection Releases). parameter eNodeBs
ENodeBAlgoSwitch.
CaAlgoSwitch.
Added load balancing under CA. For l Added the option Macro,
details, see 3.3.9 Load Balancing DlCaLbAlgoSwit micro, and
Under CA. ch to the LampSite
parameter eNodeBs
ENodeBAlgoSwi
tch.CaLbAlgoSwi
tch.
l Added the
following
parameters:
– eNodeBMlb.
DlCaLbMaxC
CNum
– eNodeBMlb.
CaUeMinData
VolRatio
Editoria Revised descriptions and modified the None N/A

l change organization throughout this document.

eRAN TDD
Carrier Aggregation Feature Parameter Description 2 Overview
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 TR 36.913 of Release 10 introduced carrier aggregation (CA)
to LTE-Advanced networks, allowing aggregation of contiguous or non-contiguous carriers. CA
achieves wider bandwidths (a maximum of 100 MHz) and higher spectral efficiency (especially
in spectrum refarming scenarios).
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 or
more (two or more in the case of spatial multiplexing) transport blocks (TBs) in each
transmission time interval (TTI) for each CC. Each individual 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 for the LTE system.
Huawei eNodeBs allow three configuration modes: CA-group-based, frequency-based, and

adaptive CA. Unless otherwise stated, the descriptions in this document apply to all three modes.
2.2 Benefits
Maximized Resource Utilization
A CA-capable UE (referred to as CA UE in this document) can use idle resource blocks (RBs)
on up to five CCs to minimize wasted resources.
Efficient Utilization of Non-contiguous Spectrum Chunks

With CA, an operator's non-contiguous spectrum chunks can be aggregated for efficient
utilization.

eRAN TDD
Better User Experience

With CA enabled, a single UE can reach higher uplink and downlink peak data rates. On a
network that serves a number of UEs, CA UEs with activated secondary serving cells (SCells)
can use idle resources in their SCells and have increased throughput if the network is not
overloaded.
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 four 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, three, or four CCs in the downlink. However,
the aggregation of two CCs in the uplink is not compatible with the aggregation with three
or four CCs in the downlink for a CA UE.
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 The TDD cells to be aggregated must use the same uplink-downlink configuration: either
configuration 1 or configuration 2.
Protocol Stack Architecture

The uplink and downlink air-interface protocol stack with CA enabled has the following
characteristics:
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-1 shows the uplink and downlink air-interface protocol stack with CA.

eRAN TDD
Figure 2-1 Uplink and downlink air-interface protocol stack with CA
ARQ: automatic repeat request
ROHC: robust header compression

eRAN TDD
Carrier Aggregation Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 Function Overview
3.1.1 Related Concepts

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.

eRAN TDD
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
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. 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.
3.1.2 Usage Scenarios
3.1.2.1 Typical Scenarios

Annex J in 3GPP TS 36.300 of Release 10 defines five typical scenarios for using CA. It
stipulates that the two carriers are intra-eNodeB carriers in these scenarios. Table 3-1 lists the
typical scenarios and whether Huawei eNodeBs support the scenarios. The following features
apply to the typical scenarios:


eRAN TDD
Table 3-1 Typical scenarios for using CA and Huawei eNodeBs' support
Typical Scenario Supported by Huawei Remarks

eNodeBs
Scenario 1: intra- Yes None

eNodeB co-coverage
carriers

eNodeB different-
coverage carriers

eNodeB carriers (one
for macro coverage;
another for edge
coverage)
Scenario 4: intra- Yes eNodeBs support this scenario when

eNodeB carriers (one the ratio of macro cells to RRHs is
provided by the site; 1:N (N ≥ 1).
another provided by
remote radio heads
[RRHs])
Scenario 5: intra- No Scenario 5 is a typical scenario of

eNodeB carriers (one repeater deployment and is not
provided only by the supported at present.
site; another provided
by the site and a
repeater)
The following figures show the typical scenarios. In the figures, F1 and F2 denote two carrier
frequencies.
Figure 3-1 Intra-eNodeB co-coverage carriers

eRAN TDD
Figure 3-2 Intra-eNodeB different-coverage carriers
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)

eRAN TDD
3.1.2.2 Atypical Scenarios

In addition to protocol-defined typical scenarios, Huawei CA applies to inter-eNodeB cells in
scenarios with relaxed backhaul requirements for delay. The CA feature involved is
TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]. This feature currently
implements only FDD+TDD CA in relaxed backhaul scenarios. For details, see 3.1.3.4
TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial].
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.
Table 3-2 CA features
Feature Max. Max. Min. BW Max. Total Description

No. of No. of per CC BW
UL CCs DL CCs
TDLAOFD-0 1 2 10 MHz 30 MHz This feature allows

01001 LTE-A (CA not (2CC aggregation of two
Introduction supporte aggregati downlink CCs
d) on (referred to as
supporte downlink 2CC
d) aggregation in this
document) to a
maximum
bandwidth of 30
MHz.

01002 Carrier downlink 2CC
Aggregation aggregation to a
for Downlink maximum
2CC in bandwidth of 40
40MHz MHz.
TDLAOFD-0 1 4 10 MHz 80 MHz This feature enables

70201 an eNodeB to select
Flexible CA the two, three, or four
from Multiple most suitable
Carriers downlink carriers for
CA.

eRAN TDD
Feature Max. Max. Min. BW Max. Total Description

No. of No. of per CC BW
UL CCs DL CCs

81402 Inter- downlink 2CC
eNodeB CA aggregation between
based on inter-eNodeB cells in
Relaxed scenarios with
Backhaul relaxed backhaul
[Trial] requirements. The
two CCs must be a
combination of FDD
and TDD carriers.

81407 Carrier aggregation of two
Aggregation uplink CCs (referred
for Uplink to as uplink 2CC
2CC [Trial] aggregation in this
document) to a
maximum
bandwidth of 40
MHz.

3CC [Trial] bandwidth of 60
MHz.

4CC [Trial] bandwidth of 80
MHz.
MRFD-10123 1 4 l FDD: 5 80 MHz This feature allows

1 FDD+TDD MHz aggregation of at
Carrier l TDD: 10 most four downlink
Aggregation MHz FDD and TDD CCs
(LTE TDD) to a maximum
[Trial] bandwidth of 80
MHz.
3.1.3.1 TDLAOFD-001001 LTE-A Introduction

This feature includes five sub-features:

eRAN TDD
l TDLAOFD-00100111 Intra-band Carrier Aggregation for Downlink 2CC in 30MHz

Intra-band CA aggregates two carriers in a single frequency band for downlink data
transmission to one CA UE. Intra-band CA is further classified into contiguous CA and
non-contiguous CA.
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 30 MHz for a CA UE.
l TDLAOFD-00100102 Support for UE Category 6
This sub-feature enables CA for UEs of category 6, which is defined in 3GPP TS 36.306
V10.0.0.
If two carriers are aggregated for a single category-6 UE in the downlink, the peak downlink
data rate of the UE is twice that of a non-CA UE. For example, when each aggregated cell
uses downlink 2x2 multiple-input multiple output (MIMO), uplink-downlink configuration
2, and special subframe configuration 7, the peak downlink data rate of a single category-6
UE can reach 220 Mbit/s.
V12.0.0.
If two carriers are aggregated for a single category-7 UE in both uplink and downlink, the
peak uplink and downlink data rates of the UE are twice those of a non-CA UE. For example,
when each aggregated cell uses downlink 2x2 MIMO, uplink 1x2 MIMO (with 16QAM),
uplink-downlink configuration 2 and special subframe configuration 7, the peak data rate
of a single category-7 UE can reach 220 Mbit/s in the downlink and 20 Mbit/s in the uplink.
V12.0.0.
If three carriers are aggregated for a single category-9 UE in the downlink, the peak
downlink data rate of the UE is three times that of a non-CA UE. For example, when each
aggregated cell uses downlink 2x2 MIMO, the peak downlink data rate of a single
category-9 UE can reach 330 Mbit/s.
V12.0.0.
If three carriers are aggregated for a single category-10 UE, the peak uplink and downlink
data rates of the UE are twice and three times those of a non-CA UE, respectively. For
example, when each aggregated cell uses downlink 2x2 MIMO and uplink 1x2 MIMO
(with 16QAM), the peak data rate of a single category-10 UE can reach 330 Mbit/s in the
downlink and 20 Mbit/s in the uplink.
3.1.3.2 TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz

This feature allows a maximum of 40 MHz downlink bandwidth for a CA UE. By aggregating
two contiguous or non-contiguous carriers, operators can provide higher bandwidths and
improve service quality for UEs.
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.

eRAN TDD
3.1.3.3 TDLAOFD-070201 Flexible CA from Multiple Carriers

This feature allows an eNodeB to select several of the most suitable carriers for CA. The
selections are based on the CA capability reported by the CA UE and carrier management
principles.
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 two or three carriers for FDD+TDD CA.
From TDD carriers, an eNodeB can currently select two, three, or four carriers for CA. This
feature maximizes carrier utilization. It uses mobility load balancing (MLB) to achieve efficient
multi-carrier management.
3.1.3.4 TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial]

In a TDD-only network, CA applies only to intra-BBU cells. On an FDD+TDD network, CA
now applies to inter-eNodeB cells in relaxed backhaul scenarios, as shown in Figure 3-6. In
these scenarios, eNodeBs are interconnected with a one-way delay less than or equal to 4 ms
and round trip time less than or equal to 8 ms.
Figure 3-6 Inter-eNodeB CA based on relaxed backhaul
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.

eRAN TDD
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 configuration mode
can be queried by running the DSP PCCSCELLLIST command. Frequency-based 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 Currently, this feature works only between macro or micro FDD cells and macro TDD cells for FDD
+TDD CA.
l For details about eX2 interfaces between eNodeBs, see eX2 Self-Management.
The CA procedure is as follows:

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:
l If the pair of eNodeBs are both macro eNodeBs, RelaxedBackhaulCaSwitch under
the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs.
l 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 SCell to exit CA. CA restarts when transmission
quality recovers.
3GPP Release 10 specifications stipulate that downlink-data demodulation results (ACK or
NACK) must be reported over the PCC of each CA UE. In a relaxed backhaul scenario, the
eNodeB that provides the SCC for a CA UE estimates the CQI, NACK, and scheduling priority
to determine the scheduling occasion and resources for the UE in advance without affecting the
scheduling priority policy and fairness among UEs. This prevents inter-eNodeB CA failures
caused by transmission delay.
Inter-eNodeB CA based on relaxed backhaul requires that a GPS or IEEE1588 V2 clock source
be deployed with a time synchronization accuracy of ±1.5 μs. It also requires that the jitter and
packet loss rate meet the requirements described in S1/X2 Self-Management.
Inter-eNodeB CA based on relaxed backhaul employs the same procedures as intra-eNodeB CA
for PCC anchoring, SCell activation, SCell change, and SCell deactivation, as described in 3.2
Carrier Management. This type of inter-eNodeB CA implements SCell configuration and
SCell removal as described in both the current section and 3.2 Carrier Management.
3.1.3.5 TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial]

This feature allows a maximum of 40 MHz uplink bandwidth for a CA UE. By aggregating two
intra- or inter-band carriers, operators can provide higher bandwidths and improve service
quality for UEs. 3.1.4 Band Combinations lists the combinations of bands that support carrier
aggregation.

eRAN TDD
This feature is dependent on the uplink CA capabilities of UEs and the setting of
CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter. It requires
TDLAOFD-001001 LTE-A Introduction to be activated. Therefore, after TDLAOFD-081407
is enabled, two carriers can be aggregated for both uplink and downlink transmission.
TDLAOFD-081407 works only between intra-eNodeB cells.
3.1.3.6 TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial]

This feature allows operators to aggregate three intra- or inter-band carriers so as to provide
higher bandwidths and improve service quality for UEs. 3.1.4 Band Combinations lists the
combinations of bands that support carrier aggregation.
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 only between intra-eNodeB cells.
3.1.3.7 TDLAOFD-081404 Carrier Aggregation for Downlink 4CC [Trial]

This feature allows operators to aggregate four intra- or inter-band carriers so as to provide higher
bandwidths and improve service quality for UEs. 3.1.4 Band Combinations lists the
combinations of bands that support carrier aggregation.
CaDl4CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of ACKs and NACKs for four 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 only between intra-eNodeB cells.
3.1.3.8 MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [Trial]

This feature allows aggregation of downlink FDD and TDD CCs. With this feature, up to four
CCs can be aggregated to a maximum bandwidth of 80 MHz. This feature deals with spectrum
shortages by utilizing both FDD and TDD spectral resources, addresses mobile broadband
service competitions, and improves service quality.
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.
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 works.

eRAN TDD
3.1.4 Band Combinations
3GPP-defined Band Combinations

eNodeBs support CA in the combinations of 3GPP-defined bands listed in Table 3-3. The
following are the rules for using CA features in different band combinations:
l If the total bandwidth is less than or equal to 30 MHz, the feature TDLAOFD-001001 LTE-
A Introduction must be activated. In addition, the following features can be activated when
required: TDLAOFD-070201 Flexible CA from Multiple Carriers, TDLAOFD-081402
Inter-eNodeB CA based on Relaxed Backhaul [Trial], TDLAOFD-081407 Carrier
Aggregation for Uplink 2CC [Trial], and MRFD-101231 FDD+TDD Carrier Aggregation
(LTE TDD) [Trial].
l If the total bandwidth is greater than 30 MHz but is less than or equal to 40 MHz, the
features TDLAOFD-001001 LTE-A Introduction and TDLAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz must be activated. In addition, the following
features can be activated when required: TDLAOFD-070201 Flexible CA from Multiple
Carriers, TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial],
TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial], TDLAOFD-081405
Carrier Aggregation for Downlink 3CC [Trial], TDLAOFD-081404 Carrier Aggregation
for Downlink 4CC [Trial], and MRFD-101231 FDD+TDD Carrier Aggregation(LTE
TDD) [Trial].
l To enable 3CC aggregation, the following features must be activated: TDLAOFD-001001
LTE-A Introduction, TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in
40MHz, and TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial]. In
addition, the following features can be activated when required: TDLAOFD-070201
Flexible CA from Multiple Carriers, TDLAOFD-081407 Carrier Aggregation for Uplink
2CC [Trial], and MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD) [Trial].
l To enable 4CC aggregation, the following features must be activated: TDLAOFD-001001
LTE-A Introduction, TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in
40MHz, TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial], and
TDLAOFD-081404 Carrier Aggregation for Downlink 4CC [Trial]. In addition, the
following features can be activated when required: TDLAOFD-070201 Flexible CA from
Multiple Carriers and TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial].
NOTE
l If carriers with the bandwidths listed in the BW (MHz) column of the following table are aggregated,
the total bandwidth cannot exceed the bandwidth listed in the Max. Total BW (MHz) column.
l Macro eNodeBs support all the band combinations listed in the table below, whereas micro eNodeBs
support only the 20+20 bandwidth combination in band 38 and the same combination in band 41 listed
in the table.
Table 3-3 CA band combinations supported by Huawei eNodeBs
Band BW (MHz) UL CA Version Max. Total

Combination Supported BW (MHz)
Band 38 (2.6 20+20 Yes eRAN6.0 or later 40

GHz),
contiguous 15+15 Yes eRAN8.0 or later

eRAN TDD

Band 38 (2.6 20+20 Yes eRAN6.0 or later 40

GHz), non-
contiguous l 20+15 Yes eRAN8.0 or later
l 15+15
l 15+10
l 10+10
Band 39 (1.9 l 20+20 Yes eRAN8.0 or later 40

GHz), l 20+10
contiguous
l 15+15

GHz), non- l 20+15
contiguous
l 20+10
l 15+15
l 15+10
l 10+10

GHz), l 20+10
contiguous
15+15 Yes eRAN8.0 or later

GHz), non- l 20+10
contiguous
l 20+15 Yes eRAN8.0 or later
l 15+15
l 15+10
l 10+10

GHz), l 20+10
contiguous
l 15+15

GHz), non- l 20+10
contiguous
l 15+15
l 15+10
l 10+10

eRAN TDD


GHz), l 20+10
contiguous
l 15+15

GHz), non- l 20+15
contiguous
l 20+10
l 15+15
l 15+10
l 10+10

GHz), l 20+10
contiguous
l 15+15

GHz), non- l 20+15
contiguous
l 20+10
l 15+15
l 15+10
l 10+10
Band 38 (2.6 l Band 38: {20} Yes eRAN8.0 or later 40

GHz) + band 39 l Band 39: {10,
(1.9 GHz) 20}
Band 39 (1.9 l Band 39: {10, Yes eRAN8.0 or later 40

GHz) + band 41 20}
(2.6 GHz) l Band 41: {20}
Band 40 (2.3 l 20+20+10 No eRAN8.1 or later 60

GHz) l 20+20+20
(3CC,
contiguous or
non-contiguous)
Band 40 (2.3 20+20+20+20 No eRAN8.1 or later 80

GHz)
(4CC)

eRAN TDD

Band 41 (2.6 l 20+20+20 No eRAN8.1 or later 60

GHz) l 20+10+10
(3CC, l 20+10+20
contiguous or
non-contiguous)
Band 38 (2.6 l Band 38: {20 No eRAN8.1 or later 60

GHz) + band 39 +20}
(1.9 GHz) l Band 39: {10,
(3CC) 20}
Band 39 (1.9 l Band 39: {10, No eRAN8.1 or later 60

GHz) + band 41 20}
(2.6 GHz) l Band 41: 20+20
(3CC) (Contiguous)
Band 39 (1.9 l Band 39: 10+20 No eRAN8.1 or later 60

GHz) + band 41 (Contiguous)
(2.6 GHz) l Band 41: {20}
(3CC)
Band 39 (1.9 l Band 39: {10, No eRAN8.1 or later 80

GHz) + band 41 20}
(2.6 GHz) l Band 41: {20+20
(4CC) +20}

GHz) + band 42 +10}
(3.5 GHz) l Band 42: {20}
(3CC)

GHz) + band 42 +10}
(3.5 GHz) l Band 42: {20
(4CC) +20}
Band 3 (1.8 l Band 3 (FDD): No eRAN8.1 or later 25

GHz) + band 40 {5}
(2.3 GHz) l Band 40 (TDD):
(FDD+TDD {20}
2CC)

eRAN TDD

Band 20 (800 l Band 20 (FDD): No eRAN8.1 or later 50

MHz) + band 38 {10}
(2.6 GHz) + l Band 38 (TDD):
band 38 (2.6 {20}
GHz)
l Band 38 (TDD):
(FDD+TDD {20}
3CC)

GHz) + band 7 {10, 15}
(2.6 GHz) + l Band 7 (FDD):
band 40 (2.3 {20}
GHz) + band 40
{10, 20}
(FDD+TDD
4CC) l Band 40 (TDD):
{20}

GHz) + band 7 {15}
band 38 (2.6 {20}
GHz) + band 38
{20}
(FDD+TDD
{20}

GHz) + {10, 15, 20}
band 8 (900 l Band 8 (FDD):
MHz) + band 41 {10, 15, 20}
(2.6 GHz) + l Band 41 (TDD):
band 41 (2.6 {20}
GHz)
l Band 41 (TDD):
(FDD+TDD {20}
4CC)

GHz) + band 20 {10}
(800 MHz) + l Band 20 (FDD):
band 38 (2.6 {10}
GHz) + band 38
{20}
(FDD+TDD
{20}

eRAN TDD


MHz) + band 39 {10, 15, 20}
(1.9 GHz) + l Band 39 (FDD):
band 41 (2.6 {20}
GHz) + band 41
{20}
(FDD+TDD
{20}

GHz) + band 5 {10}
(850 MHz)+ l Band 5 (FDD):
band 7 (2.6 {10}
GHz) + band 40
(2.3 GHz) l Band 7 (FDD):
{20}
(FDD+TDD
{20}

GHz) + band 7 {10}
band 20 (800 {20}
MHz) + band 38
(2.6 GHz) l Band 20 (FDD):
{5}
(FDD+TDD
{20}

GHz) + band 41 {10, 15, 20}
(2.6 GHz) + l Band 41 (TDD):
band 41 (2.6 {20}
GHz) + band 41
{20}
(FDD+TDD
{20}

MHz) + band 41 {10, 15, 20}
(2.6 GHz) + l Band 41 (TDD):
band 41 (2.6 {20}
GHz) + band 41
{20}
(FDD+TDD
{20}

eRAN TDD


GHz) + band 40 {20}
(2.3 GHz) + l Band 40 (TDD):
band 40 (2.3 {20}
GHz) + band 40
{20}
(FDD+TDD
{20}
Operator-defined Band Combinations

Operators may own frequency band combinations that have not been defined by 3GPP
specifications. Huawei eRAN8.1 supports operator-defined band combinations to meet operator
requirements for band combination customization.
The PrivateCaBandComb MO is used to define band combinations for 2CC, 3CC, or 4CC
aggregation. This MO contains the following parameters:
l PrivateCaBandComb.PrivateCaCombId: identifies an operator-defined CA band

combination. This ID is unique within an eNodeB.
l PrivateCaBandComb.MaxAggregatedBw: specifies the maximum aggregated
bandwidth that the band combination supports.
l PrivateCaBandComb.BwCombSetId: identifies a bandwidth combination set for the band
combination. A band combination may support multiple bandwidth combination sets.
l PrivateCaBandComb.CombBand1Id, PrivateCaBandComb.CombBand2Id,
PrivateCaBandComb.CombBand3Id, and PrivateCaBandComb.CombBand4Id:
identify the bands in the band combination. The parameter settings must meet the following
requirement: PrivateCaBandComb.CombBand1Id ≤
PrivateCaBandComb.CombBand2Id ≤ PrivateCaBandComb.CombBand3Id ≤
PrivateCaBandComb.CombBand4Id.
l PrivateCaBandComb.CombBand1Bw, PrivateCaBandComb.CombBand2Bw,
PrivateCaBandComb.CombBand3Bw, and PrivateCaBandComb.CombBand4Bw:
specify the bandwidth allowed in each band.
NOTE
If a 3GPP-defined band combination supported by eNodeBs conflicts with an operator-defined band

combination, the operator-defined one takes precedence. To avoid UE faults caused by conflicts between
3GPP-defined and operator-defined bandwidth combination sets, operators are advised to set
PrivateCaBandComb.BwCombSetId to be different from any 3GPP-defined set ID.
3.2 Carrier Management

eRAN TDD
3.2.1 Overview
Features Involved
Carrier management involves the following features:

Procedures Involved
Carrier management involves the following procedures for CA UEs:
l PCC anchoring
PCC anchoring 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
The PCell of a CA UE cannot be deactivated or removed. It changes only in handovers.

l SCell configuration, change, activation, deactivation, and removal
SCell configuration is triggered when a CA UE initiates RRC connection setup in any of
the following scenarios: initial access (when PCC anchoring has finished), an RRC
connection re-establishment, and an incoming handover. For details about SCell
configuration, see 3.2.3 SCell Configuration. After an SCell is configured, it may be
changed, activated, deactivated, and removed. For details about these procedures, see 3.2.4
SCell Change, 3.2.5 SCell Activation, 3.2.6 SCell Deactivation, and 3.2.7 SCell
Removal, respectively. CA works only when an SCell is configured and activated for a
CA UE.
Figure 3-7 shows the transitions between the SCell states.

eRAN TDD
Figure 3-7 SCell state transitions
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. Only the cells in the group can be aggregated.
l Frequency-based configuration is enabled when FreqCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter is on but AdpCaSwitch under the same
parameter is off. This mode requires that PCC and SCC attributes be set for E-UTRAN
frequencies. Only the cells on these frequencies can be aggregated.
l Adaptive configuration is enabled when both FreqCfgSwitch and AdpCaSwitch under
the ENodeBAlgoSwitch.CaAlgoSwitch parameter are on. Compared with frequency-
based configuration, adaptive configuration supports blind SCell configuration. In addition
to PCC and SCC attribute settings, the adaptive mode requires that
CaGroupSCellCfg.SCellBlindCfgFlag be set to TRUE(TRUE) for candidate SCells.
Operators can select a configuration mode after considering the following differences between
these modes:
l In CA-group-based or adaptive configuration mode, SCells can be configured in a blind

manner (without measurements). However, in frequency-based configuration mode, an
eNodeB can select a candidate SCell for a CA UE and set up a data link between the
candidate SCell and the PCell based only on measurements by the UE. Therefore,
frequency-based SCell configuration takes a longer time than CA-group-based and adaptive
SCell configuration.

eRAN TDD
l Frequency-based configuration mode, in which only frequencies and their attributes need
to be configured, is simpler than CA-group-based and adaptive configuration modes.
l Only frequency-based and adaptive configuration modes apply to scenarios 3 and 4
described in 3.1.2.1 Typical Scenarios. (In CA-group-based configuration mode, eNodeBs
support scenario 4 only when the ratio of macro cells to RRHs is 1:1.)
3.2.2 PCC Anchoring (at Initial Access)

During PCC anchoring, an eNodeB selects a PCell for a CA UE based on PCell or PCC priorities.
To prioritize certain frequencies as PCCs, an operator can set high PCell or PCC priorities so
that the eNodeB will select the highest-priority cell or carrier as the PCell or PCC for the UE.
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
After PCC anchoring is enabled, the number of inter-frequency handovers increases.
3.2.2.1 CA-Group-based PCC Anchoring

Candidate PCCs can be prioritized for CA UEs. If PccAnchorSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter is on, the eNodeB performs PCC anchoring to
select cells with high PCell priorities (specified by the CaGroupCell.PreferredPCellPriority
parameter) as PCells for CA UEs.
After a CA UE initially accesses a cell (for example, cell 1), if the UE supports inter-frequency
handovers and no bearer for an emergency call or with a QCI of 1 has been established for the
UE, the eNodeB performs PCC anchoring as shown in Figure 3-8.

eRAN TDD
Figure 3-8 CA-group-based PCC anchoring
The PCC anchoring procedure is as follows:
1. The eNodeB checks whether cell 1 has the highest PCell priority among the cells in the CA
group.
l 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.
l 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

eRAN TDD
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.
l 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.
l 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.
l 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.
l Operators are advised to set an identical PCell priority for intra-frequency cells in the same CA group.
If the intra-frequency cells are assigned different priorities, the eNodeB takes the highest one of the
priorities as the priority for all these cells during PCC anchoring.
3.2.2.2 Frequency-based or Adaptive PCC Anchoring

Compared with PCC anchoring in CA-group-based configuration mode, PCC anchoring in
frequency-based or adaptive configuration mode involves candidate PCCs for which only
frequency-level information is configured. Therefore, the eNodeB can determine the PCell only
after receiving A4 measurement reports from the CA UE.
PCC anchoring requires that PccAnchorSwitch under the

ENodeBAlgoSwitch.CaAlgoSwitch parameter be on and candidate PCC configurations
(including PCC priorities, specified by PccFreqCfg.PreferredPccPriority) have been added.
After a CA UE initially accesses a cell on a carrier (for example, carrier 1), if the UE supports
inter-frequency handovers and no bearer for an emergency call or with a QCI of 1 has been
established for the UE, the eNodeB performs PCC anchoring as shown in Figure 3-9.

eRAN TDD
Figure 3-9 Frequency-based PCC anchoring
The PCC anchoring procedure is as follows:
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).
l 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.

eRAN TDD
l 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.
l 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.
l 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.
l 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 In an intra-eNodeB case of TDD-only or FDD+TDD carriers, if a candidate PCC is not accompanied

by candidate SCCs, the eNodeB does not deliver A4 measurement configurations related to this
candidate PCC. In an inter-eNodeB case of FDD+TDD carriers, configuration checks 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.
3.2.3 SCell Configuration

To prioritize certain frequencies as SCCs, an operator can set high SCell or SCC priorities so
that the eNodeB will select the highest-priority cell or carrier as an SCell or SCC for the UE.
NOTE
For FDD+TDD CA, the eNodeB takes the following actions:

l When a UE is served only by FDD cells, the eNodeB must select a TDD cell as an SCell for the UE.
During the selection, the eNodeB considers TDD cells with uplink-downlink configuration 1 or 2 and
special subframe configuration 5, 6, or 7 as candidates. From the candidates, the eNodeB selects an
SCell based on carrier management principles.
l When a CA UE is served by an FDD PCell, the eNodeB follows the SCell configuration procedures
described in Carrier Aggregation of eRAN Feature Documentation for FDD eRAN8.1 to configure
either FDD or TDD SCells.
An eNodeB starts SCell configuration for a CA UE if all the following conditions are met:

eRAN TDD
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 SCells have not been configured for the UE.
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 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. Particularly, in adaptive configuration mode, the eNodeB performs
measurement-based SCell configuration, rather than blind SCell configuration.
l AMBR-based control over the number of UEs configured with SCells
This function is introduced in eRAN8.1. Figure 3-10 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.

eRAN TDD
Figure 3-10 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 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.
3.2.3.1 CA-Group-based SCell Configuration

This section describes the procedures of CA-group-based SCell configuration for uplink/
downlink 2CC aggregation, downlink 3CC aggregation, and downlink 4CC aggregation.
Uplink and Downlink 2CC Aggregation

Uplink 2CC aggregation and downlink 2CC aggregation use the same SCell configuration
procedure. With both uplink and downlink 2CC aggregation enabled, in a single procedure, an
eNodeB configures an SCell for a CA UE for both uplink and downlink transmission.

eRAN TDD
Figure 3-11 shows the SCell configuration procedure.
Figure 3-11 CA-group-based SCell configuration for uplink/downlink 2CC aggregation

eRAN TDD
The eNodeB treats a cell that meets all the following conditions as a candidate SCell for a CA
UE:
l The cell is in the same CA group as the PCell of the UE.
l The cell has not been configured as an SCell for the UE.
l The cell belongs to the public land mobile network (PLMN) that serves the UE or belongs
to an equivalent PLMN.
The eNodeB arranges all candidate SCells in descending order of SCell priority (specified by
the CaGroupSCellCfg.SCellPriority parameter) and attempts to select a candidate SCell as an
SCell for the UE. Cells with the priority value of 0 cannot be configured as SCells.
The SCell configuration procedure varies depending on the settings of the
CaGroupSCellCfg.SCellBlindCfgFlag parameter and SccBlindCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter.
l If SccBlindCfgSwitch is on and CaGroupSCellCfg.SCellBlindCfgFlag is set to TRUE
(TRUE) for a top-priority candidate SCell, the eNodeB does not send the A4 measurement
configuration. Instead, the eNodeB directly delivers an RRC Connection Reconfiguration
message to configure this candidate cell as an SCell for the UE.
If multiple candidate SCells have the same top SCell priority and have their
CaGroupSCellCfg.SCellBlindCfgFlag set to TRUE(TRUE), the eNodeB randomly
selects one cell from these candidate SCells and attempts to configure this cell as an SCell
for the UE in a blind manner (that is, without measurements).
If the SCell is configured successfully, the procedure ends. If the SCell fails to be
configured, the eNodeB evaluates next-priority candidate SCells in the same way.
l If SccBlindCfgSwitch is off or if SccBlindCfgSwitch is on but
CaGroupSCellCfg.SCellBlindCfgFlag is set to FALSE(FALSE) for a top-priority
candidate SCell, the eNodeB does not support blind SCell configuration. In this situation,
the eNodeB delivers the A4 measurement configuration related to the candidate SCell.
After receiving an A4 measurement report from the UE, the eNodeB determines whether
to configure the candidate cell as an SCell for the UE. The configuration procedure is as
follows:
The eNodeB delivers the A4 measurement configuration, instructing the UE to measure all
of the top-priority candidate SCells. In the measurement configuration, 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 E-UTRA
absolute radio frequency channel number (EARFCN), frequency-specific offset,
measurement bandwidth, and other measurement-related parameters.
– If the UE does not require measurement gaps, the eNodeB delivers the A4 measurement
configuration in which measurement gaps are not set up.
NOTE
AutoGapSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter affects the decision

process of the inter-frequency measurement gap setup. If this switch is on, the eNodeB determines
whether to set up the gaps based on the reported UE capabilities. If this switch is off, the eNodeB
sets up the gaps, without considering UE capabilities. It is recommended that this switch be off to
ensure that only cells with satisfactory signal quality can be configured as SCells.

eRAN TDD
After receiving an A4 measurement report from the UE, the eNodeB checks the cells
contained in the report. If the report contains a candidate SCell, the eNodeB sends an 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
l In CA-group-based configuration mode, it is recommended that blind configuration be enabled

to facilitate SCell configuration.
l After delivering the A4 measurement configuration related to a candidate SCell 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 the candidate cell as an SCell for the UE, even if the eNodeB later receives an A4
measurement report that contains the candidate cell.
l The threshold for event A4 used in the preceding procedure is equal to
CaMgtCfg.CarrAggrA4ThdRsrp plus CaGroupSCellCfg.SCellA4Offset.
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.
Downlink 3CC Aggregation

The SCell configuration procedure for downlink 3CC aggregation is similar to that for uplink/
downlink 2CC aggregation. The difference lies in the number of SCells to be configured and
the consequences that follow. For downlink 3CC aggregation, the eNodeB selects two candidate
SCells and attempts to configure them. The consequences are as follows:
l Both cells are configured as SCells, and the procedure ends.

l One cell is configured as an SCell. The CA UE stays in the 2CC aggregation state. When
the traffic volume of the CA UE meets the triggering condition again, the eNodeB performs
an SCell configuration procedure, in which the eNodeB selects only one candidate SCell
at a time. The procedure ends when a total of two SCells are configured for the UE.
l Neither cell is configured as an SCell. The CA UE stays in the single carrier state. When
an SCell configuration procedure, in which the eNodeB selects two candidate SCells. The
procedure ends when a total of two SCells are configured for the UE.
Figure 3-12 shows the SCell configuration procedure for downlink 3CC aggregation.

eRAN TDD
Figure 3-12 CA-group-based SCell configuration for downlink 3CC aggregation

eRAN TDD

the consequences that follow. For downlink 4CC aggregation, the eNodeB selects three
candidate SCells and attempts to configure them. The consequences are as follows:
l All the three cells are configured as SCells, and the procedure ends.
l Two of the cells are configured as SCells. The CA UE stays in the 3CC aggregation state.
When the traffic volume of the CA UE meets the triggering condition again, the eNodeB
performs an SCell configuration procedure, in which the eNodeB selects only one candidate
SCell at a time. The procedure ends when a total of three SCells are configured for the UE.
l Only one cell is configured as an SCell. The CA UE stays in the 2CC aggregation state.
performs an SCell configuration procedure, in which the eNodeB selects two candidate
SCells. The procedure ends when a total of three SCells are configured for the UE.
l None of the cells is configured as an SCell. The CA UE stays in the single carrier state.
performs an SCell configuration procedure, in which the eNodeB selects three candidate

eRAN TDD
Figure 3-13 CA-group-based SCell configuration for downlink 4CC aggregation
3.2.3.2 Frequency-based SCell Configuration

This section describes the procedures of frequency-based SCell configuration for uplink/
downlink 2CC aggregation, downlink 3CC aggregation, and downlink 4CC aggregation.

eRAN TDD

Figure 3-14 Frequency-based SCell configuration for uplink/downlink 2CC aggregation

eRAN TDD
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 delivers the A4 measurement configuration, instructing the UE to measure

the top-priority 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. (This
capability is indicated by the IE interFreqNeedForGaps in the UECapabilityInformation
message transmitted over the Uu interface.)
l If the UE requires measurement gaps, the eNodeB considers the bearers of the UE. If a
gaps in the measurement configuration. The configuration includes the EARFCN,
frequency-specific offset, measurement bandwidth, and other measurement-related
parameters.
NOTE
During initial frequency-based SCell configuration for relaxed-backhaul-based inter-eNodeB CA

for a UE, the control-plane link and user-plane path are set up and checked for the eX2 interface
between the eNodeBs and information is exchanged between the PCell and the candidate SCell.
This takes more time than intra-eNodeB CA. In addition, the SCell cannot be configured within
a single gap. Therefore, the eNodeB sets up two gaps in this case: one for eX2 setup and check
as well as information exchange and the other for SCell configuration. The interval between the
two gaps is determined by the CaMgtCfg.SccCfgInterval parameter.
After the eX2 interface is set up, the eNodeB sets up only one gap during subsequent SCell
configuration procedures.
l If the UE does not require measurement gaps, the eNodeB delivers the A4 measurement
NOTE
l AutoGapSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter affects the decision

sets up the gaps, without considering UE capabilities. It is recommended that this switch be off
to ensure that only cells with satisfactory signal quality can be configured as SCells.
CaMgtCfg.CarrAggrA4ThdRsrp plus SccFreqCfg.SccA4Offset.
l If multiple candidate SCCs have the same priority, the eNodeB performs this step on all
candidates.
2. 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:
l 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.
l If the PCell cannot set up a data link to the top-priority candidate SCell, the eNodeB
tries the next-priority candidate SCell.

eRAN TDD
l 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 After delivering the A4 measurement configuration related to a candidate SCC to the UE, the
configure a candidate cell as an SCell for the UE, even if the eNodeB later receives an A4


an SCell configuration procedure, in which the eNodeB selects only one candidate SCell
at a time. The procedure ends when a total of two SCells are configured for the UE.
an SCell configuration procedure, in which the eNodeB selects two candidate SCells. The
procedure ends when a total of two SCells are configured for the UE.

eRAN TDD
Figure 3-15 Frequency-based SCell configuration for downlink 3CC aggregation

eRAN TDD

performs an SCell configuration procedure, in which the eNodeB selects only one candidate
SCell at a time. The procedure ends when a total of three SCells are configured for the UE.
performs an SCell configuration procedure, in which the eNodeB selects two candidate
performs an SCell configuration procedure, in which the eNodeB selects three candidate

eRAN TDD
Figure 3-16 Frequency-based SCell configuration for downlink 4CC aggregation
3.2.3.3 Adaptive SCell Configuration

An eNodeB can configure an SCell in adaptive mode when both FreqCfgSwitch and
AdpCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter are on, candidate

eRAN TDD
PCells and their candidate SCells are configured, and the

CaGroupSCellCfg.SCellBlindCfgFlag parameter is set to TRUE(TRUE).
In this mode, the eNodeB attempts to configure an SCell in a blind manner for a UE only when
the UE accesses a cell during initial access, a handover, or an RRC connection re-establishment.
This section describes the procedures of adaptive SCell configuration for uplink/downlink 2CC
aggregation, downlink 3CC aggregation, and downlink 4CC aggregation.
NOTE
l A maximum of 72 CaGroupSCellCfg MOs can be configured for a single eNodeB.

l Each cell can work with no more than eight other cells (configured in CaGroupSCellCfg MOs) for
CA; routes can be set up between one cell and up to eight others. Any more CaGroupSCellCfg MOs
will not take effect. No new routes will be set up by A4 or A6 measurements. Therefore, no more SCells
can be configured or changed to accompany a PCell. The eight cells are not necessarily active SCells.
They may be SCells configured but not activated, cells to which routes are not set up, or invalid cells.
l Currently, downlink 4CC aggregation works only for FDD+TDD CA.


eRAN TDD
Figure 3-17 Adaptive SCell configuration for uplink/downlink 2CC aggregation

eRAN TDD
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.
l 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.
l 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.
l If the UE requires measurement gaps, the eNodeB considers the bearers of the UE. If a
gaps in the measurement configuration. The configuration includes the EARFCN,
frequency-specific offset, measurement bandwidth, and other measurement-related
parameters.
NOTE
During initial adaptive SCell configuration for relaxed-backhaul-based inter-eNodeB CA for a

UE, the control-plane link and user-plane path are set up and checked for the eX2 interface
between the eNodeBs and information is exchanged between the PCell and the candidate SCell.
This takes a longer time than intra-eNodeB CA. In addition, the SCell cannot be configured within
a single gap. Therefore, the eNodeB sets up two gaps in this case: one for eX2 setup and check
as well as information exchange and the other for SCell configuration. The interval between the
two gaps is determined by the CaMgtCfg.SccCfgInterval parameter.
After the eX2 interface is set up, the eNodeB sets up only one gap during subsequent SCell
configuration procedures.
l If the UE does not require measurement gaps, the eNodeB delivers the A4 measurement
NOTE
l AutoGapSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter affects the decision

sets up the gaps, without considering UE capabilities. It is recommended that this switch be off
to ensure that only cells with satisfactory signal quality can be configured as SCells.
CaMgtCfg.CarrAggrA4ThdRsrp plus SccFreqCfg.SccA4Offset.

eRAN TDD
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:
l 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.
l If the PCell cannot set up a data link to the top-priority candidate SCell, the eNodeB
tries the next-priority candidate SCell.
l 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 After delivering the A4 measurement configuration related to a candidate SCC to the UE, the
configure a candidate cell as an SCell for the UE, even if the eNodeB later receives an A4


a measurement-based SCell configuration procedure, in which the eNodeB selects only one
candidate SCell at a time. The procedure ends when a total of two SCells are configured
for the UE.
a measurement-based SCell configuration procedure, in which the eNodeB selects two
candidate SCells. The procedure ends when a total of two SCells are configured for the UE.

eRAN TDD
Figure 3-18 Adaptive SCell configuration for downlink 3CC aggregation

eRAN TDD

performs a measurement-based SCell configuration procedure, in which the eNodeB selects
only one candidate SCell at a time. The procedure ends when a total of three SCells are
configured for the UE.
two candidate SCells. The procedure ends when a total of three SCells are configured for
the UE.
three candidate SCells. The procedure ends when a total of three SCells are configured for
the UE.

eRAN TDD
Figure 3-19 Adaptive SCell configuration for downlink 4CC aggregation

eRAN TDD
3.2.3.4 Load-based SCell Configuration

In CA-group- or frequency-based SCell configuration mode, eNodeBs may consider the load
status of cells when configuring SCells. Load-based SCell configuration takes effect if
SccSmartCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on. After
load-based SCell configuration is enabled, inter- or intra-eNodeB cells with routes set up
between them exchange their load status. If no route is set up between them, the eNodeB
considers the candidate cells to be in the high load state.
When the number of operating frequencies on a network is greater than the number of frequencies
to be aggregated and at least two of those frequencies have the same SCC priority, the eNodeB
checks the load status of candidate cells and selects low-load cells as SCells. If all candidate
cells have the same load status (either low or high), the eNodeB selects cells with high RSRP
as SCells.
The load status definitions vary depending on the settings of CELLMLB.MlbTriggerMode and
CELLMLB.PrbLoadCalcMethod:
l When CELLMLB.MlbTriggerMode is set to PRB_ONLY(PrbMode) and

CELLMLB.PrbLoadCalcMethod is set to PRB_USAGE(PRB_USAGE), the eNodeB
considers a cell to be in the high load state if the cell meets both of the following conditions
continuously for 5s:
– PRB usage of the cell ≥ CellMLB.InterFreqMLBThd + CellMLB.LoadOffset +
CellMLB.InterFreqOffloadOffset
– Number of uplink-synchronized UEs in the cell ≥ CellMLB.MlbMinUeNumThd +
CellMLB.MlbMinUeNumOffset
The eNodeB considers a cell to be in the low load state if the cell does not meet both
conditions for 5s.
l When CELLMLB.MlbTriggerMode is set to PRB_ONLY(PrbMode) and
CELLMLB.PrbLoadCalcMethod is set to PRB_VALUATION_WITH_CTRL
(PRB_VALUATION_WITH_CTRL) or PRB_VALUATION_NO_CTRL
(PRB_VALUATION_NO_CTRL), the eNodeB considers a cell to be in the high load
state if the cell meets the following condition continuously for 5s:
PRB evaluation result of the cell ≥ CELLPRBVALMLB.PrbValMlbAdmitThd
The eNodeB considers a cell to be in the low load state if the cell does not meet the condition
for 5s.
l When CELLMLB.MlbTriggerMode is set to UE_NUMBER_ONLY(UeNumMode) or
PRB_OR_UE_NUMBER(PrbOrUeNumMode), the eNodeB considers a cell to be in the
high load state if the cell meets the following condition continuously for 5s:
Number of uplink-synchronized UEs in the cell ≥ CellMLB.InterFreqMlbUeNumThd +
CellMLB.MlbUeNumOffset + CellMLB.InterFrqUeNumOffloadOffset
The eNodeB considers a cell to be in the low load state if the cell does not meet the condition
for 5s.
NOTE
eNodeBs do not consider the load status of cells during A6-based SCell changes.

eRAN TDD
3.2.4 SCell Change

If a CA UE whose SCell has been configured receives better signal quality from an intra-
frequency neighboring cell of the SCell than from the SCell, the serving eNodeB of the PCell
can change the SCell while keeping the PCell unchanged.
CA-Group-based SCell Change

If SccModA6Switch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on and intra-
frequency cells of an SCell are included in the same CA group as the SCell, the eNodeB sends
the CA UE an RRC Connection Reconfiguration message after configuring the SCell. The
message contains the A6 measurement configuration for the SCC of the UE. The offset for event
A6 is equal to the CaMgtCfg.CarrAggrA6Offset parameter value specified for the PCell.
After receiving an A6 measurement report from the CA UE, the eNodeB selects the cell with
the highest RSRP value among all the reported cells, which are included in the CA group. Then,
the eNodeB sends an RRC Connection Reconfiguration message to change the SCell to the
selected cell. If the SCell change fails, the eNodeB selects the cell with the next highest RSRP
value among the reported cells and makes another SCell change attempt.
Frequency-based or Adaptive SCell Change

If SccModA6Switch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on, the
eNodeB sends an RRC Connection Reconfiguration message to a CA UE after configuring an
SCell (for example, cell 1) for the UE. The message contains the A6 measurement configuration
for the SCC of the UE. The offset for event A6 is equal to the CaMgtCfg.CarrAggrA6Offset
parameter value specified for the PCell.
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 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.
3.2.5 SCell Activation

When an SCell for a CA UE is configured but not activated, the eNodeB that serves the PCell
checks the setting of GbrAmbrJudgeSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch
parameter if both of the following downlink traffic volume conditions are met:

eRAN TDD
l Data volume buffered at the RLC layer > max (Uu data rate at the RLC layer x
CaMgtCfg.ActiveBufferDelayThd, CaMgtCfg.ActiveBufferLenThd)
l Delay of the first RLC protocol data unit (PDU) > CaMgtCfg.ActiveBufferDelayThd
If GbrAmbrJudgeSwitch is off, the eNodeB sends a MAC control element (CE) to quickly
activate the SCell.
If GbrAmbrJudgeSwitch is on, the eNodeB performs the following:
l If the UE has downlink guaranteed bit rate (GBR) bearers in the PCell, the eNodeB checks
the bit rates of the downlink GBR services. The eNodeB activates the SCell for the UE
only if the bit rates do not reach the GBR.
l If the UE has downlink non-GBR bearers in the PCell, the eNodeB checks whether the total
rate of downlink non-GBR services on the UE has reached the downlink aggregate
maximum bit rate (AMBR). The eNodeB activates the SCell for the UE only if the total
rate has not reached the AMBR.
l If the UE has multiple bearers, each bearer is independently evaluated based on the
preceding criteria. As long as at least one bearer meets the preceding criteria for SCell
activation, the eNodeB activates the SCell for the UE.
When a CA UE is configured with two, three, or four downlink CCs, the eNodeB delivers a
MAC CE to activate one, two, or three SCells, respectively.
When a CA UE is configured with two uplink CCs, the eNodeB evaluates uplink traffic volume
as follows, in addition to downlink traffic volume:
If transmission time interval (TTI) bundling does not take effect on the CA UE and the reported
uplink buffer status is greater than the CaMgtCfg.ActiveBufferLenThd parameter value
throughout the period specified by CaMgtCfg.UlCaActiveTimeToTrigger, the uplink SCell can
be activated.
The eNodeB delivers a MAC CE to activate the SCell for the uplink and downlink, as long as
either uplink or downlink traffic volume meets their respective activation conditions.
NOTE
l If CaMgtCfg.ActiveBufferLenThd is set to 0, the eNodeB activates a configured SCell as long as the

eNodeB intends to send data to the CA UE. In this situation, if no SCell has been configured for the
CA UE, the eNodeB repeatedly attempts to configure an SCell without considering
CaMgtCfg.SccCfgInterval. (CaMgtCfg.SccCfgInterval specifies the minimum interval after which
the eNodeB attempts to configure an SCell again for a CA UE whose SCell failed to be configured.)
l Section 6.1.3.8 "Activation/Deactivation MAC Control Element" in 3GPP TS 36.321 V11.1.0 provides
details about the MAC CE. SCell activation is not direction-specific. An eNodeB activates an SCell as
long as either uplink or downlink traffic volume meets the activation conditions.
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 determined by physical layer specifications. For TDD
eNodeBs, the value is greater than or equal to 8.
3.2.6 SCell Deactivation

SCell deactivation takes effect when CaMgtCfg.CarrierMgtSwitch is set to ON(On). The
eNodeB that serves the PCell of a CA UE deactivates the SCell. The deactivation can be based
on traffic volume or channel quality. The two methods can be enabled separately or
simultaneously.

eRAN TDD
Traffic Volume–triggered SCell Deactivation

To deactivate SCells when the traffic volume of CA UEs is low, activate the traffic volume–
triggered SCell deactivation function. It is recommended that, if CA is enabled, this function
always be activated.
If CaMgtCfg.CarrierMgtSwitch is set to ON(On) for the PCell, the eNodeB sends a MAC CE
to the UE to deactivate SCells when each E-UTRAN radio access bearer (E-RAB) of the UE
meets both of the following traffic volume conditions:
l Uu data rate at the RLC layer ≤ CaMgtCfg.DeactiveThroughputThd

l Data volume buffered at the RLC layer ≤ CaMgtCfg.DeactiveBufferLenThd
When two, three, or four downlink CCs are aggregated for a CA UE, the eNodeB delivers a
MAC CE to deactivate all SCells if the downlink traffic volume meets the preceding deactivation
conditions. When two uplink CCs are aggregated for a CA UE, the eNodeB evaluates both uplink
and downlink traffic volumes. It delivers a MAC CE to deactivate the SCell only if both the
uplink and downlink traffic volumes meet the preceding deactivation conditions.
NOTE
l If CaTrafficTriggerSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on in the

eNodeB that serves the PCell, the eNodeB sends an RRC Connection Reconfiguration message to
remove the SCell immediately after deactivating the SCell based on the traffic volume.
l For a CA UE with an SCell activated in the uplink, the eNodeB deactivates the SCell only when both
the uplink and downlink traffic volumes meet the deactivation conditions. For a CA UE with one, two,
or three SCells activated in the downlink, the eNodeB deactivates the SCells as long as the downlink
traffic volume meets the deactivation conditions.
Channel Quality–triggered SCell Deactivation

To deactivate SCells when the channel quality of CA UEs is low, activate the channel quality–
triggered SCell deactivation function. It is recommended that this function be activated,
especially when blind SCell configuration is enabled or A2 measurements are disabled. The
purpose is to prevent scheduling on the SCells where channel quality is low.
If CaMgtCfg.CarrierMgtSwitch is set to ON(On) for the PCell, the eNodeB sends a MAC CE
to deactivate an SCell for a CA UE when the spectral efficiency corresponding to the SCell's
channel quality indicator (CQI) reported by the UE falls below the spectral efficiency
corresponding to the CaMgtCfg.SccDeactCqiThd parameter value specified for the SCell in
single-codeword transmission. If CaMgtCfg.SccDeactCqiThd is set to 0 for the SCell, the
eNodeB that serves the PCell does not deactivate the SCell based on channel quality.
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.
3.2.7 SCell Removal

To have SCells removed when their signal quality is poor, set the SCell removal switch on.
The eNodeB that serves the PCell of a CA UE removes SCells. The UE state changes as follows:

eRAN TDD
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 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.
CA-Group-based SCell Removal

If SccA2RmvSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on, the
eNodeB delivers the A2 measurement configuration to a CA UE after configuring an SCell for
the UE based on A4 measurements. The threshold for event A2 is equal to
CaMgtCfg.CarrAggrA2ThdRsrp configured for the PCell plus
CaGroupSCellCfg.SCellA2Offset. After receiving an A2 measurement report that contains the
SCell, the eNodeB removes the SCell by delivering an RRC Connection Reconfiguration
message.
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.
Frequency-based or Adaptive SCell Removal

If SccA2RmvSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on, the
eNodeB delivers the A2 measurement configuration to a CA UE after configuring an SCell for
the UE based on A4 measurements or in a blind manner. The threshold for event A2 is equal to
CaMgtCfg.CarrAggrA2ThdRsrp configured for the PCell plus SccFreqCfg.SccA2Offset.
After receiving an A2 measurement report that contains the SCell, the eNodeB removes the
SCell by delivering an RRC Connection Reconfiguration message.
If SccA2RmvSwitch is off, the eNodeB does not deliver the A2 measurement configuration.

eRAN TDD
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.
3.2.8 PCC Anchoring (at RRC Connection Releases)

When IdleModePccAnchorSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter
is on:
l If subscriber profile IDs (SPIDs) or operator-specific cell-reselection priorities are not

configured on the eNodeB, the eNodeB performs PCC anchoring when the RRC
connections of CA UEs are normally released. This does not occur in abnormal RRC
connection releases, for example, due to S1 faults, eNodeB overload, or MME overload.
During PCC anchoring:
1. The eNodeB generates a PCC anchor frequency list for an RRC connection release,
based on the band combinations supported by the CA UE and PCC anchor
configurations. In the list, the frequencies that can be aggregated are arranged in
descending order of PCC priority.
2. The eNodeB includes the list in the information element (IE)
idleModeMobilityControlInfo of an RRC Connection Release message and, in that
message, sets the length of timer T320 to a fixed value of 180 minutes.
3. The eNodeB sends the message to the CA UE, instructing the UE to camp in the
specified frequency band.
l If SPID- or operator-specific cell-reselection priorities are configured on the eNodeB, the
eNodeB includes the configured priorities in the IE idleModeMobilityControlInfo of an
RRC Connection Release message.
3.3 Other Key Techniques Under CA

This section describes how other techniques work when the following CA features are enabled:


eRAN TDD

3.3.1 Connection Management Under CA

Connection management under CA has the following characteristics:
l After an RRC connection is set up between a CA UE and a cell, the cell acts as the PCell
of the UE. The PCell transmits non-access stratum (NAS) messages for the UE.
l An eNodeB configures an SCell for a CA UE by sending messages over the RRC
connection. After the SCell is configured, the CA UE still has only one RRC connection
with the network and is allocated only one cell radio network temporary identifier (C-
RNTI).
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.
3.3.2 Mobility Management Under CA

This section describes how mobility management works when CA is enabled.
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 four, three, or two CCs, the procedures take
place for 4CC, 3CC, or 2CC aggregation, respectively.
The RRC Connection Reconfiguration and the preceding IEs can be traced as described in 6.4.6
Activation Observation.

eRAN TDD
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 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
InterFreqHoGroup.InterFreqHoA2ThdRsrp). The threshold for CA event A2 is equal
to CaMgtCfg.CarrAggrA2ThdRsrp plus CaGroupSCellCfg.SCellA2Offset in CA-
group-based configuration mode, or equal to CaMgtCfg.CarrAggrA2ThdRsrp plus
SccFreqCfg.SccA2Offset in frequency-based configuration mode.
When CA is enabled, the setting of HoWithSccCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter has an impact on measurement configuration. If
this switch is on, the eNodeB includes the IE reportAddNeighMeas in the handover-related A3,
A4, and A5 measurement configuration delivered to CA UEs. The CA UEs report the
measurement result of the best cell on each serving frequency (in the IE
measResultBestNeighCell), in addition to the PCell and SCell measurement results (in the IEs
measResultPCell and measResultSCell), to the eNodeB. Then, the eNodeB includes the best cell
information in the IE CandidateCellInfoList in the handover request message sent to the target
eNodeB.
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.

eRAN TDD
NOTE
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.
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
ENodeBAlgoSwitch.CaAlgoSwitch parameter. In such a case, the eNodeB does not deliver the
measurement configuration related to frequency-priority-based handovers to CA UEs. If you do
not select this option, frequency-priority-based handovers may occur on CA UEs soon after the
UEs are handed over to a frequency with a high PCC anchoring priority.
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.
SCell Configuration During Handovers

The procedure for configuring SCells during handovers varies depending on the setting of
HoWithSccCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter. Setting this
switch on shortens the configuration delay. When an SCell has been configured for a CA UE,
the eNodeB performs the following special procedures for mobility management:
l If HoWithSccCfgSwitch is on:
1. 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.
2. The target eNodeB acquires measurement results from the IE CandidateCellInfoList,
determines the new SCell to be configured after 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.
3. 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.

eRAN TDD
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 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.
3.3.3 Admission and Congestion Control Under CA

This section describes how admission control and congestion control work when CA is enabled.
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 re-establishment, 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.
The eNodeB rejects access requests if the number of UEs in a cell has reached its maximum.
No switch is available to control this type of admission control.
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 RelDrbSwitch

eRAN TDD
under the CellAlgoSwitch.RacAlgoSwitch parameter is on in 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
l Non-CA UEs are UEs that do not support CA.

l For more details about congestion control, see Admission and Congestion Control.
3.3.4 Scheduling Under CA

This section describes how scheduling works when CA is enabled.
For GBR services, scheduling with CA enabled is almost the same as scheduling with CA
disabled. The goal of scheduling is still to meet the QoS requirements of GBR services.
For non-GBR services, Huawei designs two scheduling methods: basic scheduling and
differentiated scheduling. The scheduling method is specified by the
CELLDLSCHALGO.CaSchStrategy parameter. The default method is basic scheduling. The
scheduling method must be consistent between serving cells to prevent data transmission
exceptions. The following presents the characteristics of the two methods:
l Basic scheduling
In basic scheduling, the data rate of a CA UE (a variable used to calculate scheduling
priority) is defined as the total data rate on the CCs of the UE. Under the same channel
condition and sufficient bandwidth, the average data rate of a CA UE is almost the same
as the average data rate of a non-CA UE that runs services with the same QCI.
Due to inconsistent spectral efficiency for the CA UE between the PCC and SCCs, basic
scheduling fails to achieve an identical data rate for a CA UE and a non-CA UE when
planning to allocate the same number of physical resource blocks (PRBs) to the two UEs.
– If the difference in spectral efficiency between the PCC and SCCs is large (for example,
when the CA UE is located at the edge of a cell), there is a large difference in the number
of allocated PRBs between the CA UE and the non-CA UE.
– If the spectral efficiency is almost the same between the PCC and SCCs, the number of
PRBs allocated to the CA UE is close to that of PRBs allocated to the non-CA UE.
l Differentiated scheduling
In differentiated scheduling, the data rate of a CA UE for priority calculation is defined as
the data rate only on the current CC of the UE. On each CC, the CA UE is allocated the
same number of RBs as a non-CA UE on the same CC. Therefore, the number of RBs
allocated to the CA UE is the sum of the average number of RBs allocated to a non-CA UE
in each of the serving cells. The average data rate of the CA UE served by N CCs is almost
N times the average data rate of a non-CA UE, when the spectral efficiencies of the CCs
are close, UEs are evenly distributed on the CCs, and channel conditions are the same
between the CCs.

eRAN TDD
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.
3.3.5 MIMO Under CA
MIMO Schemes for PCells

An eNodeB takes MIMO schemes for the PCell of a CA UE as follows:
l If CellBfMimoParaCfg.BfMimoAdaptiveSwitch is set to NO_ADAPTIVE

(NO_ADAPTIVE), the value of CellBfMimoParaCfg.FixedBfMimoMode takes effect.
The value can be TM2(TM2), TM3(TM3), TM4(TM4), TM7(TM7), TM8(TM8),
TM9w/oPMI(TM9w/oPMI), or TM9wPMI(TM9wPMI).
l If CellBfMimoParaCfg.BfMimoAdaptiveSwitch is set to TxD_BF_ADAPTIVE
(TxD_BF_ADAPTIVE) or MIMO_BF_ADAPTIVE(MIMO_BF_ADAPTIVE),
adaptive selection from transmission modes for beamforming and MIMO takes effect.
For TM9 to take effect, the TM9Switch(TM9Switch) option of the

CellAlgoSwitch.EnhMIMOSwitch parameter must be selected, and the
CellCsiRsParaCfg.CsiRsSwitch parameter must be set to FIXED_CFG(Fixed configure) or
ADAPTIVE_CFG(ADAPTIVE_CFG). In such a case, TM9 works for TM9-capable CA UEs
in their PCell, and only TM3 or adaptive transmission works for other CA UEs.
MIMO Schemes for SCells

CellBfMimoParaCfg.SccBfMimoAdaptiveSwitch controls the transmission mode used in the
SCells of CA UEs.
l If this parameter is set to ON(On), the beamforming and MIMO configurations for the
SCells themselves take effect. Specifically:

eRAN TDD
– If CellBfMimoParaCfg.BfMimoAdaptiveSwitch is set to NO_ADAPTIVE

(NO_ADAPTIVE), the value of CellBfMimoParaCfg.FixedBfMimoMode takes
effect. The value can be TM2(TM2), TM3(TM3), TM4(TM4), TM7(TM7), TM8
(TM8), TM9w/oPMI(TM9w/oPMI), or TM9wPMI(TM9wPMI).
– If CellBfMimoParaCfg.BfMimoAdaptiveSwitch is set to TxD_BF_ADAPTIVE
(TxD_BF_ADAPTIVE) or MIMO_BF_ADAPTIVE(MIMO_BF_ADAPTIVE),
adaptive selection from transmission modes for beamforming and MIMO takes effect.
For TM9 to take effect, the TM9Switch(TM9Switch) option of the
CellAlgoSwitch.EnhMIMOSwitch parameter must be selected, and the
CellCsiRsParaCfg.CsiRsSwitch parameter must be set to FIXED_CFG(Fixed
configure) or ADAPTIVE_CFG(ADAPTIVE_CFG). In such a case, TM9 works for
TM9-capable CA UEs in their SCell, and only TM3 or adaptive transmission works for
other CA UEs.
l If this parameter is set to OFF(Off), the transmission mode for an SCell is dependent on
the cell type and the antenna mode of RRUs. If the SCell is not a multi-RRU cell, TM3 (or
TM1 in the case of single-antenna transmission) is always used in the cell. If the SCell is
a multi-RRU cell served only by 1T1R RRUs, TM1 or TM2 is used, depending on the
number of CRS ports configured for the cell. If the SCell is a multi-RRU cell of any other
type, TM3 is used in the cell.
NOTE
For more details about MIMO, see MIMO.
3.3.6 DRX Control Under CA

In discontinuous reception (DRX) mode, UEs do not monitor the PDCCH in some periods,
thereby reducing power consumption.
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-20 shows an example of
the DRX configuration under CA.
Figure 3-20 Common DRX configuration
When CA is enabled, DRX control works as follows:

eRAN TDD
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 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
l For more details about DRX, see DRX and Signaling Control.
l DRX does not work on UEs in the FDD+TDD CA state.
3.3.7 RAN Sharing Under CA

In RAN sharing scenarios, the operators involved allocate resources to their subscribers based
on the predefined proportions of resources. To enhance fairness in resource usage among the
operators that share a carrier, differentiated scheduling is recommended.
CA UEs can access only operator-specific carriers (either in PCells or in SCells). Assume that
there are three frequencies:
l f1, shared by operators A and B

l f2, dedicated to operator A
l f3, dedicated to operator B
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
For more details about RAN sharing, see RAN Sharing.
3.3.8 Power Backoff Under CA

After an SCell is configured for a CA UE in the uplink, uplink power control works separately
on the two CCs. The UE sends CC-specific extended power headroom reports (PHRs) to the
eNodeB. Based on the reports, the eNodeB calculates the total required power for the CCs. The
required power for the PCC or an SCC is equal to the maximum transmit power supported by
the UE minus the power headroom indicated in the PCC- or SCC-specific extended PHR,
respectively. If the total required power exceeds the maximum transmit power of the UE, Huawei
employs single-carrier scheduling. If the SCell is still active, the eNodeB estimates the spectral
efficiency of the PCell and SCell based on uplink channel quality and schedules the UE on the
better CC.

eRAN TDD
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.
3.3.9 Load Balancing Under CA

Each eNodeB measures and evaluates the load of each cell involved in CA (referred to as CA
cell in this section) among the served cells. If a CA cell enters the high load state, the serving
eNodeB triggers load balancing between CCs of UEs in the downlink CA state. With the load
balancing algorithm, the eNodeB selects high- and low-load CA cells and dynamically adjusts
the ratio of CA UE data volumes in the cells to achieve a load balance between the cells. This
algorithm helps reduce the number of handovers of non-CA UEs triggered for mobility load
balancing (MLB).
NOTE
l This load balancing function does not take effect on multi-RRU cells, such as SFN cells.
l If three CCs are aggregated in the downlink for a UE, the ratio adjustment works between the PCell
and an SCell, not between SCells.
Load balancing under CA is controlled by the DlCaLbAlgoSwitch option of the

ENodeBAlgoSwitch.CaLbAlgoSwitch parameter.
For this load balancing algorithm to take effect, operators must also set the following parameters:
l ENODEBMLB.DlCaLbMaxCCNum: specifies the maximum number of CCs aggregated

for each CA UE whose load is to be transferred for load balancing. If this parameter is set
to 2CC(2CC), the eNodeB transfers the load of CA UEs in the downlink 2CC aggregation
state. If this parameter is set to 3CC(3CC), the eNodeB transfers the load of CA UEs in
the downlink 2CC aggregation state and those in the downlink 3CC aggregation state.
Currently, this parameter does not provide an option for 4CC. The value 3CC(3CC) is
recommended.
l ENODEBMLB.CaUeMinDataVolRatio: specifies the minimum required ratio (expressed
in percentage) of the data volume on a high-load CC to that on a low-load CC for each CA
UE. For example, if this parameter is set to 20, the minimum ratio for a single CA UE is
1/5. If this parameter is set to 0, the minimum ratio is 0/1, which means that all data of the
CA UE on the high-load CC can be transferred to the low-load CC. The value 0 is
recommended.
NOTE
For more details about load balancing, see MLB.

eRAN TDD
Carrier Aggregation Feature Parameter Description 4 Related Features
4 Related Features
4.1 Features Related to TDLAOFD-001001 LTE-A

Introduction
Prerequisite Features
l TDLBFD-002007 RRC Connection Management
The RRC Connection Management feature manages signaling procedures such as random
access, RRC connection setup, and RRC connection reconfiguration for CA UEs.
l TDLBFD-002018 Mobility Management
The Mobility Management feature manages mobility-related procedures for CA UEs.
l TDLOFD-001015 Enhanced Scheduling
The enhanced scheduling algorithm performs scheduling for each CA UE in the UE's PCell
and SCells. In basic scheduling, the priority of CA UEs is the same as the priority of non-
CA UEs that run services with the same QCI on the PCC. In differentiated scheduling, the
priority of CA UEs is the same as the priority of non-CA UEs that run services with the
same QCI on each CC.
For services with a QCI of 1, the algorithm performs scheduling only in the PCell of each
UE.
Mutually Exclusive Features

None
Impacted Features
l 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

eRAN TDD
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.
l TDLOFD-001016 VoIP Semi-persistent Scheduling
According to 3GPP TS 36.321, semi-persistent scheduling takes effect only on the PCCs
for CA UEs.
l TDLOFD-001032 Intra-LTE Load Balancing and TDLOFD-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.
l TDLOFD-002001 Automatic Neighbour Relation (ANR) and TDLOFD-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.
l TDLOFD-002008 Adaptive SFN/SDMA
Adaptive SFN requires UEs to report SRS, based on which eNodeBs select remote radio
units (RRUs) for independent scheduling of the UEs. If an adaptive SFN cell is configured
as an SCell for a CA UE only in the downlink, only joint scheduling applies to the SCell.
If the SCell is also configured for the uplink, independent scheduling can be used in the
cell.
l TDLOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture
After this feature is enabled, CA UEs can receive Multimedia Broadcast multicast service
Single Frequency Network (MBSFN) subframes in their PCells but not in their SCells. This
feature works for CA UEs only in PCells.
l TDLOFD-001047 LoCation Services(LCS)
Reference signal time difference (RSTD) measurements for OTDOA-based positioning
increase the ACK/NACK loss rate. A higher ACK/NACK loss rate results in scheduling
performance deterioration, which may affect user experience of CA UEs.
l TDLAOFD-00100103 Intra-eNodeB DL CoMP in DCS Mode, TDLAOFD-003002 Intra-
eNodeB DL CoMP in Adaptive Mode, and TDLAOFD-081411 Inter-eNodeB DL CoMP
based on Relaxed backhaul
CA UEs support DL CoMP in their PCells, but not in their SCells.
4.2 Features Related to TDLAOFD-001002 Carrier

Aggregation for Downlink 2CC in 40MHz
TDLAOFD-001001 LTE-A Introduction

The mutually exclusive features are the same as those described in 4.1 Features Related to
TDLAOFD-001001 LTE-A Introduction.

eRAN TDD
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
4.3 Features Related to TDLAOFD-070201 Flexible CA from

Multiple Carriers
l (Optional) TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
This feature is required if the total bandwidth is greater than 30 MHz but not greater than
40 MHz.

Impacted Features
4.4 Features Related to TDLAOFD-081402 Inter-eNodeB CA

based on Relaxed Backhaul [Trial]
40 MHz.

Impacted Features
In addition to the features described in 4.1 Features Related to TDLAOFD-001001 LTE-A
Introduction, the following features affect CA:
l TDLBFD-002005 DL Asynchronous HARQ
Due to inter-eNodeB transmission delay, HARQ feedback is postponed, which has an
impact on the residual block error rate (RBLER) of CA UEs. Among HARQ retransmission

eRAN TDD
statistics, the RBLER-related counters produce larger values. In addition, CQI reports about
SCells of CA UEs are also delayed, which affects the initial block error rate (IBLER) of
the UEs. The IBLER-related counters produce larger values.
If a UE is located a medium or long distance from the center of its PCell or SCell, the data
rate of the UE fluctuates.
l TDLOFD-001015 Enhanced Scheduling
The impact applies only to the UEs on which inter-eNodeB CA based on relaxed backhaul
takes effect. To mitigate the impact of inter-eNodeB transmission delay, an eNodeB must
estimate the scheduling opportunities for CA UEs in advance. This may have a slight short-
term impact on fairness among UEs but no impact on scheduling-related performance
indicators.

Aggregation for Uplink 2CC [Trial]
40 MHz.

Impacted Features
In addition to the features described in 4.1 Features Related to TDLAOFD-001001 LTE-A
Introduction, CA affects the following features:
l TDLOFD-001048 TTI Bundling

Uplink CA does not work with TTI bundling. TTI bundling overrides uplink CA. When an
eNodeB determines to configure TTI bundling for a CA UE, the eNodeB sends an RRC
Connection Reconfiguration message to remove the uplink SCell and configure TTI
bundling.
l TDLOFD-001049 Single Streaming Beamforming, TDLOFD-001061 Dual Streaming

Beamforming, and TDLOFD-001077 MU-Beamforming
If uplink CA is disabled, CA UEs support beamforming only in their PCells. When uplink
CA is enabled, CA UEs support beamforming in all their serving cells, because they can
send SRS in all the cells.
l TDLOFD-001058 UL 2x4 MU-MIMO and UL 2x8 MU-MIMO
If uplink CA is disabled, the MIMO features work for CA UEs only in their PCells. When
uplink CA is enabled, the MIMO features work for CA UEs in all their serving cells, where
uplink transmission from the UEs is applicable.

eRAN TDD
l TDLOFD-001066 Intra-eNodeB UL CoMP

A CA UE takes a longer scheduling time than a non-CA UE. Currently, non-CA UEs
support UL CoMP, but CA UEs do not.

Aggregation for Downlink 3CC [Trial]

Impacted Features

Aggregation for Downlink 4CC [Trial]

Impacted Features

eRAN TDD
4.8 Features Related to MRFD-101231 FDD+TDD Carrier

Aggregation(LTE TDD) [Trial]
l (Optional) LAOFD-001001 LTE-A Introduction
This feature is required 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.
l (Optional) LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
This feature is required if at least two FDD carriers are involved in FDD+TDD CA and the
total bandwidth of the FDD carriers is greater than 20 MHz but not greater than 40 MHz.
This feature is required if three FDD carriers are involved in FDD+TDD CA and the total
bandwidth of the FDD carriers does not exceed 40 MHz.
This feature is required if three FDD carriers are involved in FDD+TDD CA and the total
bandwidth of the FDD carriers is greater than 40 MHz but not greater than 60 MHz.
l (Optional) TDLAOFD-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 does not exceed 30 MHz.
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 [Trial]
This feature is required if three TDD carriers are involved in FDD+TDD CA.

l FDD+TDD CA is not compatible with the following FDD eRAN features:
– LOFD-003029 SFN, LOFD-070205 Adaptive SFN/SDMA, LOFD-081208 Inter-
eNodeB SFN Based on Coordinated BBU, and LOFD-081209 Inter-eNodeB Adaptive
SFN/SDMA Based on Coordinated BBU
The PCell and SCells of a CA UE cannot be SFN cells.
– LOFD-001007 High Speed Mobility and LOFD-001008 Ultra High Speed Mobility
The PCell and SCells of a CA UE cannot be high-speed or ultra-high-speed cells.
– LBFD-002017 DRX and LOFD-001105 Dynamic DRX
DRX does not work on UEs in the FDD+TDD CA state.
– LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
Uplink 2CC aggregation does not work in FDD+TDD CA scenarios.
l FDD+TDD CA is not compatible with the following TDD eRAN features:
– TDLOFD-001075 SFN, TDLOFD-002008 Adaptive SFN/SDMA, TDLOFD-001098
Inter-BBP SFN, TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA,

eRAN TDD
TDLOFD-001080 Inter-BBU SFN, TDLOFD-001082 Inter-BBU Adaptive SFN/

SDMA, and TDLOFD-070227 PDCCH DCS in SFN
The PCell and SCells of a CA UE cannot be SFN cells.
– TDLBFD-002017 DRX and TDLOFD-001105 Dynamic DRX
DRX does not work on UEs in the FDD+TDD CA state.
– TDLAOFD-081407 Carrier Aggregation for Uplink 2CC [Trial]
Uplink 2CC aggregation does not work in FDD+TDD CA scenarios.
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
for CA UEs.
– LOFD-001032 Intra-LTE Load Balancing and LOFD-070215 Intra-LTE User Number
Load Balancing
– 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 applies to CA UEs only in PCells.
– LAOFD-002001 Static TDM eICIC and LAOFD-081233 Dynamic TDM eICIC

eRAN TDD
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
for CA UEs.
– TDLOFD-001032 Intra-LTE Load Balancing and TDLOFD-070215 Intra-LTE User
Number Load Balancing
– TDLOFD-002001 Automatic Neighbour Relation (ANR) and TDLOFD-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 Feature Parameter Description.
– TDLOFD-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 applies to CA UEs only in PCells.

eRAN TDD
Carrier Aggregation Feature Parameter Description 5 Network Impact
5 Network Impact
5.1 TDLAOFD-001001 LTE-A Introduction

System Capacity
l Number of RRC_CONNECTED UEs
An eNodeB treats a CA UE as an RRC_CONNECTED UE in each of its serving cells. In
an extreme case with 2CC aggregation for all UEs on the network, the maximum number
of UEs that can access the network decreases by half. The maximum number decreases
depending on the number of CCs aggregated. To maximize the number of UEs that can
access the network, the eNodeB preferentially releases the CA UEs that treat a cell as their
SCell.
l PUCCH and PUSCH overheads
Each CA UE sends the ACK/NACK and CSI related to its SCells in its PCell. When the
PUSCH is not scheduled, the UE sends the information over the PUCCH. When the PUSCH
is scheduled, the UE sends the information over the PUSCH. Therefore, PUCCH overhead
or PUSCH associated signaling overhead increases.
l Overall throughput in the entire network
CA does not directly affect network capacity. However, when spare resources are available
on a network, CA increases the resource usage and overall throughput in the network.
l Data rates of CA UEs
– When spare resources are available on a network, CA in the network increases the data
rates of CA UEs.
– When no spare resources are available, the data rates of CA UEs are dependent on
scheduling policies (described in 3.3.4 Scheduling Under CA) and UE locations.
Activating an SCell may result in a decrease in the overall SCell throughput if the UE
is located at the edge of the SCell. However, activating an SCell may cause an increase
in the overall SCell throughput if the UE is located in the cell center or at a place of a
medium distance to the center of the SCell.
Network Performance
l PRB usage

eRAN TDD
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.
l CA UE throughput
In accordance with section 9.1.1 "PDCCH Assignment Procedure" in 3GPP TS 36.213
V10.9.0, PdcchOverlapSrchSpcSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch
parameter is used to control whether CA UEs regard the overlapping PDCCH candidates
of the common search space and UE-specific search space, which are transmitted in the
PCell, as PDCCH candidates of the common or UE-specific search space.
– Setting PdcchOverlapSrchSpcSwitch on has a positive impact if most CA UEs on the
network comply with 3GPP TS 36.213 V10.9.0 or later specifications. It has a negative
impact if most CA UEs on the network do not comply with 3GPP TS 36.213 V10.9.0
or later specifications. The positive impact is that the success rate of aperiodic CSI
reporting on SCCs increases and the SCC throughput rises. The negative impact is that
blind decoding and demodulation of the PDCCH by CA UEs fail and the SCC
throughput decreases.
– Setting PdcchOverlapSrchSpcSwitch off has the preceding negative impact if most
CA UEs on the network comply with 3GPP TS 36.213 V10.9.0 or later specifications.
It has the preceding positive impact if most CA UEs on the network do not comply with
3GPP TS 36.213 V10.9.0 or later specifications.
It is recommended that PdcchOverlapSrchSpcSwitch be on only if most CA UEs on the
network comply with 3GPP TS 36.213 V10.9.0 or later specifications.
NOTE
If a large number of RRC connection reconfiguration failures occur on a network, it is an indication

that most CA UEs on the network do not comply with 3GPP TS 36.213 V10.9.0 or later specifications.
5.2 TDLAOFD-001002 Carrier Aggregation for Downlink

2CC in 40MHz
This feature itself does not have any network impacts. For the impacts of its prerequisite features,
see 5.1 TDLAOFD-001001 LTE-A Introduction.

eRAN TDD
5.3 TDLAOFD-070201 Flexible CA from Multiple Carriers

5.4 TDLAOFD-081402 Inter-eNodeB CA based on Relaxed

Backhaul [Trial]
The prerequisite features have the impacts described in 5.1 TDLAOFD-001001 LTE-A
Introduction. Due to inter-eNodeB transmission delay and limited bandwidth, the
TDLAOFD-081402 feature itself has the following impacts on the UEs involved:
l CQI reports are delayed, causing slight deterioration in frequency-selective scheduling

performance and an increase in IBLER.
l Reports of HARQ demodulation results are delayed, affecting the peak data rate of a single
UE and resulting in an increase in RBLER.
l CQI and IBLER feedback is delayed, causing a fluctuation in the data rate of UEs located
at places of medium or long distances to the center of their SCells.
l Due to the difference in RLC data arrival time between the aggregated carriers, a CA UE
has to combine the received data and arrange the order of the data. The data combining and
ordering consume UE CPU resources. If the CPU capacity is insufficient, the data rate of
the UE fluctuates.
l Due to possible errors in the estimated scheduling priority of a CA UE, the PRBs in an
SCell for the UE may not be fully utilized when the SCell serves a small number of non-
CA UEs and the non-CA UE traffic is light.
l To minimize the impact of inter-eNodeB transmission delay, RLC retransmissions occur
only in the PCell of each CA UE. If the Uu bandwidth of the PCell is used up by GBR
services, RLC retransmissions for a CA UE are often blocked and the data rate of the UE
fluctuates.
l Due to the limited inter-eNodeB transmission bandwidth, if an eNodeB detects congestion
in the transmission queues on an eX2 interface, it triggers backpressure on the inter-eNodeB
CA UEs on the interface, and the data rates of 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.
5.5 TDLAOFD-081407 Carrier Aggregation for Uplink 2CC

[Trial]

eRAN TDD

3CC [Trial]
Introduction. The TDLAOFD-081405 feature itself has the following impact on PUCCH
overheads:
When downlink 3CC aggregation is enabled, two RBs are used for PUCCH format-3 overhead.
If PucchSwitch under the CellAlgoSwitch.PucchAlgoSwitch parameter is on, these RBs are
additional RBs for the PUCCH. They were originally allocated for the physical uplink shared
channel (PUSCH). If PucchSwitch is off, these RBs are existing RBs for the PUCCH. They
were originally allocated for periodic CQI reporting. As a result, more UEs have to use aperiodic
CQI reporting.

4CC [Trial]
Introduction. The TDLAOFD-081404 feature itself has the following impact on PUCCH
overheads:
When downlink 4CC aggregation is enabled, two RBs are used for PUCCH format-3 overhead.
If PucchSwitch under the CellAlgoSwitch.PucchAlgoSwitch parameter is on, these RBs are
additional RBs for the PUCCH. They were originally allocated for the physical uplink shared
channel (PUSCH). If PucchSwitch is off, these RBs are existing RBs for the PUCCH. They
were originally allocated for periodic CQI reporting. As a result, more UEs have to use aperiodic
CQI reporting.
5.8 MRFD-101231 FDD+TDD Carrier Aggregation(LTE

TDD) [Trial]
Introduction. The MRFD-101231 feature itself has the following impact:
When an FDD carrier works as the PCC and TDD carriers as SCCs for a CA UE, the downlink
TDD spectral resources are fully utilized to increase downlink throughput. In addition, the FDD
PCC provides better uplink coverage for the CA UE than a TDD carrier does for a non-CA UE.

6 Engineering Guidelines for TDLAOFD-001001 LTE-A
eRAN TDD Introduction and TDLAOFD-001002 Carrier Aggregation
Carrier Aggregation Feature Parameter Description for Downlink 2CC in 40MHz
6
TDLAOFD-001001 LTE-A Introduction and
TDLAOFD-001002 Carrier Aggregation for

Downlink 2CC in 40MHz
6.1 When to Use TDLAOFD-001001 and TDLAOFD-001002

Enable TDLAOFD-001001 and TDLAOFD-001002 when operators require aggregation of two
downlink CCs on the live network that provide coverage areas from scenarios 1 to 4 described
in 3.1.2.1 Typical Scenarios. Specifically:
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 30 MHz, enable only TDLAOFD-001001 LTE-A
Introduction.
l If the total bandwidth is greater than 30 MHz but not greater than 40 MHz, enable both
TDLAOFD-001001 LTE-A Introduction and TDLAOFD-001002 Carrier Aggregation for
Downlink 2CC in 40MHz.
NOTE
CA can currently be used in high-speed mobility scenarios.
6.2 Required Information

Verify that:
l The cells to be aggregated have been configured as inter-frequency neighboring cells of

each other.

l The neighboring cell is not a blacklisted inter-frequency cell for the local cell. (Blacklisted
inter-frequency cells are identified by Downlink EARFCN and Start physical cell ID in
the LST INTERFREQBLKCELL command output.)
l For the neighboring cell, EutranInterFreqNCell.NoHoFlag is not set to
FORBID_HO_ENUM(Forbid Ho) on the local cell.
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.
l In contiguous carrier aggregations, the spacing between the center frequencies of the two
carriers must meet the following conditions:
– For two 20 MHz carriers, the spacing must be 19.8 MHz.
– For a 20 MHz carrier and a 10 MHz carrier, the spacing must be 14.4 MHz.
– For two 15 MHz carriers, the spacing must be 15 MHz.
– For a 20 MHz carrier and a 15 MHz carrier, the spacing must be 17.1 MHz.
l If the Multi-Band Compatibility Enhancement feature is enabled for cells on the network,
all these cells must have the same primary and secondary frequency band settings.
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 TDLAOFD-001001
LTE-A Introduction in 3.1.3 CA Features.
l BBPs
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.
NOTE
Currently, cells configured on LBBPc boards cannot act as PCells for CA UEs.

6.4 Deployment
6.4.1 Requirements
Operating Environment
None
NEs
Table 6-1 describes the network requirements for CA.
Table 6-1 Network requirements for CA
Element Requirements
Evolved To allow 2CC aggregation to reach the expected peak data rate in 2x2 MIMO
packet core scenarios, the maximum bit rate that the UE subscribes to in the EPC must
(EPC) be greater than or equal to 220 Mbit/s.
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 in 3GPP TR 36.808 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, that for two contiguous CCs with a bandwidth
combination of 20 MHz and 10 MHz is 14.4 MHz, and that for two
contiguous CCs with a bandwidth combination of 20 MHz and 15 MHz
is 17.1 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 supportedBandCombination,
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 30 MHz, each cell
requires one sales unit of the license for TDLAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the aggregated cells is between 30 MHz and 40 MHz (including
40 MHz), each cell 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.
Feature ID Feature Name Model License NE Sales Unit

Control Item
TDLAOFD- LTE-A LT1SLTE LTE-A eNodeB per cell

001001 Introduction AID01 Introduction
(per cell)
TDLAOFD- Carrier LT1SC2C4 Carrier eNodeB per cell

001002 Aggregation for 0M00 Aggregation
Downlink 2CC for Downlink
in 40MHz 2CC in 40MHz
(per cell)
CA-group-based CA is automatically enabled and the corresponding licenses are consumed for
cells after a CA group (identified by the CaGroup.CaGroupId parameter) is set up and these
cells (at least two; identified by the CaGroupCell.eNodeBId and CaGroupCell.LocalCellId
parameters) are added into the CA group and activated. When the eNodeB sets up a data link
from one cell to another cell for frequency-based or adaptive CA, the corresponding licenses are
consumed for the cells involved in CA.
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
a 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.
6.4.2 Data Preparation

There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users

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
The following table describes the parameters that must be set in a CaGroup MO to configure
a CA group.
Parameter Parameter ID Setting Notes Data Source

Name
CA Group CaGroup. Set this parameter based on the Network plan

Identity CaGroupId network plan. (negotiation not
required)
CA Group CaGroup. Set this parameter based on the Network plan

Type CaGroupTypeI network plan. (negotiation not
Indication nd l In a TDD-only network, set this required)
parameter to TDD(TDD).
l In an FDD+TDD network, set
this parameter to FDDTDD
(FDDTDD).
The following table describes the parameters that must be set in a CaGroupCell MO to add a
cell into a CA group.

Name
CA Group CaGroupCell. Set this parameter based on the Network plan

Identity CaGroupId network plan. (negotiation not
required)
Local cell ID CaGroupSCell Set this parameter based on the Network plan
Cfg.LocalCellId network plan. (negotiation not
required)
eNodeB ID CaGroupCell. Set this parameter based on the Network plan

eNodeBId network plan. (negotiation not
required)
CA Algorithm ENodeBAlgoS Set FreqCfgSwitch Network plan

Switch witch. (FreqCfgSwitch) under this (negotiation not
CaAlgoSwitch parameter off. required)
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
enable CA-group-based configuration.


Name

CaAlgoSwitch parameter off. required)
Frequency-based Configuration
The following table describes the parameter that must be set in a PccFreqCfg MO to configure
a candidate PCC.

Name
PCC Downlink PccFreqCfg. Set this parameter based on the Network plan
EARFCN PccDlEarfcn network plan. (negotiation not
required)
The following table describes the parameters that must be set in an SCCFreqCfg MO to
configure a candidate SCC.

Name
PCC Downlink SccFreqCfg. Set this parameter based on the Network plan
required)
SCC Downlink SccFreqCfg. Set this parameter based on the Network plan
EARFCN SccDlEarfcn network plan. (negotiation not
required)
enable frequency-based configuration.

Name

CaAlgoSwitch parameter on. required)

Adaptive Configuration
The following table describes the parameter that must be set in a PccFreqCfg MO to configure
a candidate PCC.

Name
PCC Downlink PccFreqCfg. Set this parameter based on the Network plan
required)
The following table describes the parameters that must be set in an SCCFreqCfg MO to
configure a candidate SCC.

Name
PCC Downlink SccFreqCfg. Set this parameter based on the Network plan
required)
SCC Downlink SccFreqCfg. Set this parameter based on the Network plan
EARFCN SccDlEarfcn network plan. (negotiation not
required)
enable adaptive configuration.

Name
CA Algorithm ENodeBAlgoS Set both FreqCfgSwitch Network plan

Switch witch. (FreqCfgSwitch) and (negotiation not
CaAlgoSwitch AdpCaSwitch(AdpCaSwitch) required)
under this parameter on.
The following table describes the parameter that must be set in a CaGroupSCellCfg MO to
specify the blind SCell configuration capability.


Name
SCell Blind CaGroupSCel This parameter specifies whether a User-defined

Configuration lCfg. candidate cell can be configured as
Flag SCellBlindCfg an SCell in a blind manner during
Flag adaptive CA.
In adaptive configuration mode,
this parameter takes effect
regardless of the SccBlindCfgS-
witch setting under the
ENodeBAlgoSwitch.CaAlgoSwit
ch parameter.
l If this parameter is set to
TRUE(TRUE), the eNodeB
can configure this candidate
cell as an SCell for CA UEs in
a blind manner, without
delivering A4 measurement
configurations to the UEs.
l If this parameter is set to
FALSE(FALSE), the eNodeB
delivers A4 measurement
configurations to CA UEs
before it can configure this
candidate cell as an SCell.
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 the PCI of a
candidate SCell conflicts with that of an intra-frequency neighboring cell, the eNodeB will
not configure the candidate cell as an SCell for any UE.
l For macro eNodeBs, to ensure normal CA operation in eNodeBs equipped with LBBPc
boards, enable PCC anchoring and set lower priorities for cells on LBBPc boards than those
for cells on LBBPd or UBBP boards. The reason is that cells on LBBPc boards cannot
function as PCells.
l CA does not work on some UEs due to their software or hardware defects. To prevent the
UE incompatibility issue from affecting network performance, enable TDLBFD-081103
Terminal Awareness Differentiation with the UEs blacklisted and the CaSwitchOff option
of the UECOMPATOPT.BlkLstCtrlSwitch parameter selected. eNodeBs will not perform
PCC anchoring or SCell configuration for the UEs. On live networks, certain UEs support
CA but do not support PUCCH format 3. To prevent this issue from affecting user
experience of the UEs, enable TDLBFD-081103 Terminal Awareness Differentiation with
the UEs blacklisted and the Tdd2CCDlCaEnhanceSwitchOff option of the
UECOMPATOPT.BlkLstCtrlSwitch parameter selected. CA works for these UEs, but
enhanced DL ACK demodulation does not. For details about how to set parameters for

identifying defective UEs and defining differentiated handling policies, see Terminal
Awareness Differentiation.
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. If a cell that has been
configured as an SCell for a CA UE in CA-group-based configuration mode is deactivated
and then activated again, the cell will not be configured as an SCell for the UE again. This
cell can be configured as an SCell for the UE only after the UE accesses the network again
or experiences a handover.
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 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.
– If the cells to be aggregated operate in the same band and cover the same areas (for
example, in high-speed mobility scenarios), you are advised to enable blind SCell
configuration.
– 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.
– A maximum of six cells, including five inter-frequency cells, can be configured into a
TDD CA group.

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 cell and a maximum of eight cells for CA.
– 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:
– A static route is set up when a CaGroupSCellCfg MO is configured. This prevents
delays introduced by dynamic routing during CA. A maximum of eight routes, including
static and dynamic routes, can be set up for a cell. To prevent a waste of inter-board
routing bandwidth due to excessive configurations, it is recommended that one static
route be configured for each cell in adaptive configuration mode. Currently, there is no
check on the destination cell status of a route when the route is set up.
– The CAGROUPSCELLCFG.SCellPriority parameter setting does not take effect in
adaptive configuration mode. Carrier priorities are still specified by the
SCCFREQCFG.SccPriority parameter.
– In adaptive configuration mode, the CaGroupSCellCfg.SCellBlindCfgFlag parameter
setting takes effect regardless of the SccBlindCfgSwitch setting under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter. Blind SCell configuration for adaptive
CA works so long as the CaGroupSCellCfg.SCellBlindCfgFlag parameter is set to
TRUE(TRUE).
l An eNodeB may configure an SCell for a CA UE in a blind manner when the UE is located
in a weak coverage area or experiences strong interference. As a result, the CQI for the
SCell will be low. This causes a decrease in the cell throughput and an increase in the
number of RRC connection re-establishments, uplink and downlink IBLER values, packet
loss rate, and service drop rate. To avoid these impacts, you are advised to enable channel-
quality-triggered SCell deactivation.
l The PCell and SCells of each CA UE may not have the same channel quality. Therefore,
the CQIs for the entire network vary slightly after SCells are configured for CA UEs. The
CQI variation leads to fluctuations in cell throughput, the number of RRC connection re-
establishments, uplink and downlink IBLER values, the packet loss rate, and the service
drop rate.
6.4.4 Hardware Adjustment

For macro eNodeBs, CA currently requires an LBBPd or UBBP to be installed in slot 2 or 3 of
a BBU3900, if configured, for capacity expansion or upgrades. This requirement does not apply
to a BBU3910.
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:
1. Run the LST EUCELLSECTOREQM command on a macro eNodeB or the LST

EUSECTOREQMGROUP command on a LampSite eNodeB to check the existing

mapping configuration. If the baseband equipment ID is in the range of 0 to 23 in the

command output, the specified cell has been mapped to the specified baseband equipment.
If the ID is 255, the cell has not been mapped to any baseband equipment, and then go to
the next step.
2. Run the ADD BASEBANDEQM command to add baseband equipment. Ensure that the
baseband equipment ID does not collide with any existing baseband equipment ID.
3. Run the MOD EUCELLSECTOREQM command on the macro eNodeB or the MOD
EUSECTOREQMGROUP command on the LampSite eNodeB to map the cell to the new
baseband equipment. After that, the cell will be re-established. Then, the mapping takes
effect.
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-2 or Table 6-3 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-2 or Table 6-3 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-2 or Table 6-3 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.
Table 6-2 Parameters related to CA-group-based CA
MO Sheet in the Parameter Group Remarks

Summary Data
File
CaGroup User-defined sheet CA Group Identity, None

CA Group Type
Indication
CaGroupCell User-defined sheet CA Group Identity, None

eNodeB Id, Local
Cell ID, Preferred
PCell Priority, PCell
A4 RSRP Threshold,
PCell A4 RSRQ
Threshold


Summary Data
File
CaMgtCfg User-defined sheet Local cell ID, Carrier None

Aggregation A2
RSRP threshold,
Carrier Aggregation
A4 RSRP threshold,
Carrier Management
Switch, CA Active
Buffer Length
Threshold, CA
Deactive Buffer
Length Threshold,
CA Active Buffer
Delay Threshold, CA
Deactive Throughput
Threshold, Carrier
Aggregation A6
Offset, SCell Aging
Time, CA A6 Report
Amount, CA A6
Report Interval, SCC
Disable CQI
Threshold, SCC
Configuration
Interval, Cell Level
CA Algorithm
Switch
CellDlschAlgo User-defined sheet Local cell ID, None

Downlink CA
Schedule Strategy,
Ca Scc Doppler
Measurement
InterFreqHoGroup User-defined sheet CoverageBased None

Interfreq RSRP
threshold, A4A5
Based Interfreq A2
RSRP Threshold
ENodeBAlgoSwitch User-defined sheet CA Algorithm None

Switch
GlobalProcSwitch User-defined sheet Protocol None

Compatibility
Switch


Summary Data
File
CaGroupSCellCfg User-defined sheet Local Cell ID, SCell None

eNodeB ID, SCell
Local Cell ID, SCell
Priority, SCell Blind
Configuration Flag,
SCell A4 Offset,
SCell A2 Offset
Table 6-3 Parameters related to frequency-based or adaptive CA

Summary Data
File
CaMgtCfg User-defined sheet Carrier Aggregation None

A2 RSRP threshold,
Carrier Aggregation
A4 RSRP threshold,
Local cell ID, CA
Active Buffer Delay
Threshold, CA
Active Buffer Length
Threshold, CA
Deactive Throughput
Threshold, CA
Deactive Buffer
Length Threshold,
CA A6 Report
Amount, CA A6
Report Interval, SCC
Deactive CQI
Threshold, SCC
Configuration
Interval, Cell Level
CA Algorithm
Switch
CellDlschAlgo User-defined sheet Local cell ID, None

Downlink CA
Schedule Strategy,
Ca Scc Doppler
Measurement


Summary Data
File
InterFreqHoGroup User-defined sheet CoverageBased None

Interfreq RSRP
threshold, A4A5
Based Interfreq A2
RSRP Threshold
ENodeBAlgoSwitch User-defined sheet CA Algorithm None

Switch,
OverBBUsSwitch
GlobalProcSwitch User-defined sheet Protocol None

Compatibility
Switch
PccFreqCfg User-defined sheet PCC Downlink None

EARFCN, Preferred
PCC Priority, PCC
A4 RSRP Threshold,
PCC A4 RSRQ
Threshold
SccFreqCfg User-defined sheet PCC Downlink None

EARFCN, SCC
Downlink EARFCN,
SCC Priority, SCC
A2 Offset, SCC A4
Offset
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure is as follows:
Step 1 Customize a summary data file with the MOs and parameters listed in 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
6.4.5.3 Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.
Figure 6-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.

Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
6.4.5.4 Using Feature Operation and Maintenance on the CME

Step 1 On the U2000 client, choose CME > Planned Area > Create Planned Area.
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
You can select one or more eNodeBs in this step.
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, TDLAOFD-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 Read the descriptions in the (eNodeB)comment.html file in the save path, and then set CA
parameters in the CA data file (for example, TDLAOFD-001001.xls). 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
l After all the preceding steps are finished, you can run specific MML commands to verify that the
parameter settings take effect.
l Currently, this procedure can be used to activate CA-group-based configuration for the following
features: TDLAOFD-001001 LTE-A Introduction, TDLAOFD-001002 Carrier Aggregation for
Downlink 2CC in 40MHz, and TDLAOFD-070201 Flexible CA from Multiple Carriers.
6.4.5.5 Using MML Commands
Configuration Procedure
The following actions are required to activate CA by using man-machine language (MML)
commands: (1) configuring intra- or inter-frequency neighboring cells; (2) setting the CA
algorithm switches; (3) adding a CA group; (4) 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 Determine the inter-frequency cells to be added to a CA group according to the network plan.
Run the ADD EUTRANINTERNFREQ command to configure the operating frequency of a
cell in each inter-frequency cell pair as a neighboring frequency of the other cell in the pair. Run
this command repeatedly to configure neighboring frequencies for each cell.
Step 2 Run the ADD EUTRANINTERFREQNCELL command to configure the cells as inter-
frequency neighboring cells of each other.
NOTE
In this step, set No remove indicator to FORBID_RMV_ENUM(Forbid ANR Remove). Otherwise,

ANR may automatically remove neighbor relationships, after which CA does not work.
Step 3 (Optional; required when intra-frequency cells are to be added to the CA group) Run the ADD
EUTRANINTRAFREQNCELL command to configure intra-frequency cells as intra-
frequency neighboring cells of each other.
Step 4 Run the MOD ENODEBALGOSWITCH command to set the switches under CA Algorithm
Switch based on the network plan (referring to 6.4.2 Data Preparation and 6.6 Parameter
Optimization). Ensure that FreqCfgSwitch is off.
Step 5 Run the ADD CAGROUP command to add a CA group on the eNodeB and set the CA group
attribute.
Step 6 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 7 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 8 (Optional; not required for a cell that has already been activated.) Run the ACT CELL command
to activate the cells.
----End
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:
Optimization). Ensure that FreqCfgSwitch is 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.
----End
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:
Optimization). Ensure that FreqCfgSwitch and AdpCaSwitch are 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.
----End
MML Command Examples


//Configuring neighboring E-UTRA frequencies

ADD EUTRANINTERNFREQ: LOCALCELLID=0, DLEARFCN=37900, ULEARFCNCFGIND=NOT_CFG,
CELLRESELPRIORITYCFGIND=NOT_CFG, SPEEDDEPENDSPCFGIND=NOT_CFG,
MEASBANDWIDTH=MBW100, PMAXCFGIND=NOT_CFG, QQUALMINCFGIND=NOT_CFG;
ADD EUTRANINTERNFREQ: LOCALCELLID=1, DLEARFCN=38098, ULEARFCNCFGIND=NOT_CFG,
CELLRESELPRIORITYCFGIND=NOT_CFG, SPEEDDEPENDSPCFGIND=NOT_CFG,
MEASBANDWIDTH=MBW100, PMAXCFGIND=NOT_CFG, QQUALMINCFGIND=NOT_CFG;
//Configuring inter-frequency neighboring cells

ADD
EUTRANINTERFREQNCELL:LOCALCELLID=0,MCC="460",MNC="20",ENODEBID=1234,CELLID=1,NORMV
FLAG=FORBID_RMV_ENUM;
ADD
EUTRANINTERFREQNCELL:LOCALCELLID=1,MCC="460",MNC="20",ENODEBID=1234,CELLID=0,NORMV
FLAG=FORBID_RMV_ENUM;
//(Optional) Configuring intra-frequency neighbor relationships if there are intra-frequency cells

in the CA group in addition to configuring neighboring E-UTRA frequencies and inter-frequency
neighboring cells
ADD EUTRANINTRAFREQNCELL:LOCALCELLID=0,MCC="460",MNC="20",ENODEBID=1234,CELLID=2;
ADD EUTRANINTRAFREQNCELL:LOCALCELLID=2,MCC="460",MNC="20",ENODEBID=1234,CELLID=0;
//Setting the options of the CA algorithm switch

MOD ENODEBALGOSWITCH: CAALGOSWITCH=FreqCfgSwitch-0;
//Adding a TDD CA group and setting its attribute

ADD CAGROUP: CAGROUPID=0, CAGROUPTYPEIND=TDD;
//Adding cells to the CA group and setting cell attributes

ADD CAGROUPCELL: CAGROUPID=0, LOCALCELLID=0, ENODEBID=1234;
ADD CAGROUPCELL: CAGROUPID=0, LOCALCELLID=1, ENODEBID=1234;
//Configuring SCells
ADD CAGROUPSCELLCFG: LOCALCELLID=0, SCELLENODEBID=1234, SCELLLOCALCELLID=1;
ADD CAGROUPSCELLCFG: LOCALCELLID=1, SCELLENODEBID=1234, SCELLLOCALCELLID=0;
//Activating cells
ACT CELL: LOCALCELLID=0;
MOD ENODEBALGOSWITCH: CAALGOSWITCH=FreqCfgSwitch-1;
//Adding candidate PCCs and setting their attributes

ADD PCCFREQCFG: PCCDLEARFCN=37900;
//Adding candidate SCCs and setting their attributes

ADD SCCFREQCFG: PCCDLEARFCN=37900, SCCDLEARFCN=38098;
//Activating cells


MOD ENODEBALGOSWITCH: CAALGOSWITCH=FreqCfgSwitch-1&AdpCaSwitch-1;
//Adding candidate PCCs and setting their attributes

//Adding candidate SCCs and setting their attributes

//Setting blind-configurable candidate SCells

ADD CAGROUPSCELLCFG: LOCALCELLID=0, SCELLENODEBID=1234, SCELLLOCALCELLID=1,
SCELLBLINDCFGFLAG=TRUE;
ADD CAGROUPSCELLCFG: LOCALCELLID=1, SCELLENODEBID=1234, SCELLLOCALCELLID=2,
SCELLBLINDCFGFLAG=TRUE;
//Activating cells
6.4.6 Activation Observation
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.
Table 6-4 CA-related counters
Counter ID Counter Name Description
1526728426 L.Traffic.User.PCell.DL.Avg Average number of downlink CA UEs

that treat the local cell as their PCell
1526728427 L.Traffic.User.SCell.DL.Avg Average number of downlink CA UEs

that treat the local cell as their SCell
1526728424 L.ChMeas.PRB.DL.PCell.Use Average number of downlink PRBs

d.Avg occupied by CA UEs that treat the local
cell as their PCell
1526728425 L.ChMeas.PRB.DL.SCell.Use Average number of downlink PRBs

d.Avg occupied by CA UEs that treat the local
cell as their SCell

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 or Probe may be used 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.
Figure 6-2 SCell configuration message

Figure 6-3 SCell removal message
----End
Observing SCell Activation 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 > 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.
Figure 6-4 Signaling tracing result for SCell activation
----End
Observing SCell Configuration and Activation on Probe
Start Probe and connect it to the CA UE, as shown in Figure 6-5, Figure 6-6, and Figure 6-7.

Figure 6-5 Opening the Device Configure window
Figure 6-6 Setting the UE IP address

Figure 6-7 Connecting to the UE
If there are downlink radio measurement values for both the PCC and the SCC and non-zero
MAC throughput on the SCC, as shown in Figure 6-8 andFigure 6-9, the SCell has been
successfully configured and activated for the UE. If there are no radio measurement values for
the SCC, the feature activation has failed.

Figure 6-8 Successful SCell configuration and activation (radio measurement values for both
the PCC and the SCC)
Figure 6-9 Successful SCell configuration and activation (MAC throughput on the SCC)
6.4.7 Deactivation
6.4.7.1 Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 6.4.5.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 6-5 or Table 6-6.

Table 6-5 Parameters related to deactivation of CA-group-based CA
MO Sheet in the Parameter Group Setting Notes

Summary
Data File
CaGroupCell User-defined CA Group Identity, Example: CaGroupId = 0,

sheet eNodeB ID, Local Cell ID eNodeBId = 1234,
LocalCellId = 0
CaGroup User-defined CA Group Identity Example: CaGroupId = 0

sheet
CaGroupSCe User-defined Local Cell ID, SCell Example: LocalCellId = 0,

llCfg sheet eNodeB ID, SCell Local SCelleNodeBId = 1234,
Cell ID SCellLocalCellId = 2
Table 6-6 Parameters related to deactivation of frequency-based or adaptive CA
MO Sheet in the Parameter Group Setting Notes

Summary
Data File
SccFreqCfg User-defined PCC Downlink EARFCN, Example: PccDlEarfcn =

sheet SCC Downlink EARFCN 12345, SccDlEarfcn =
56789
PccFreqCfg User-defined PCC Downlink EARFCN Example: PccDlEarfcn =

sheet 12345
6.4.7.2 Using the CME to Perform Single Configuration

On the CME, set parameters according to 6.4.7.1 Using the CME to Perform Batch
Configuration. For detailed instructions, see 6.4.5.3 Using the CME to Perform Single
Configuration described for feature activation.
6.4.7.3 Using MML Commands
Configuration Procedure
To deactivate CA-group-based CA by using MML commands, perform the following steps:
Step 1 Remove cells from each CA group.
Step 2 Remove the CA groups.
Step 3 Remove the SCell configuration from each CA group on eNodeBs involved in CA.
----End

To deactivate frequency-based CA by using MML commands, perform the following steps:
Step 1 Remove SCC configurations.
Step 2 Remove PCC configurations.
----End
To deactivate adaptive CA by using MML commands, perform the following steps:
Step 1 Remove SCC configurations.
Step 2 Remove PCC configurations.
----End
MML Command Examples

//Removing cells from a CA group

RMV CAGROUPCELL: CAGROUPID=0, LOCALCELLID=0, ENODEBID=1234;
RMV CAGROUPCELL: CAGROUPID=0, LOCALCELLID=1, ENODEBID=1234;
//Removing the CA group

RMV CAGROUP: CAGROUPID=0;
//Removing SCell configurations

RMV CAGROUPSCELLCFG: LOCALCELLID=0, SCELLENODEBID=1234, SCELLLOCALCELLID=1;
RMV CAGROUPSCELLCFG: LOCALCELLID=1, SCELLENODEBID=1234, SCELLLOCALCELLID=0;
//Removing SCC configurations

RMV SCCFREQCFG: PCCDLEARFCN=123, SCCDLEARFCN=456;
//Removing PCC configurations

RMV PCCFREQCFG:PCCDLEARFCN=123;
RMV PCCFREQCFG:PCCDLEARFCN=456;
//Removing SCC configurations

//Removing PCC configurations

RMV PCCFREQCFG: PCCDLEARFCN=12345;

6.5 Performance Monitoring

Counter-based Monitoring
Monitor the counters listed in the following table and compare them with the network plan to
evaluate feature performance.
Specifically:
l Monitor the L.ChMeas.PRB.DL.Used.Avg counter value before and after CA is enabled,

to evaluate the impact of CA on the overall resource usage.
l Calculate the result of L.Thrp.bits.DL.CAUser/L.Thrp.Time.DL.CAUser to monitor the
average data rate of CA UEs. Then, compare the data rate with that of non-CA UEs.
1526726740 L.ChMeas.PRB.DL.Used.Avg Observe the average number of

PUCCH PRBs used.
1526728516 L.Traffic.User.PCell.DL.Max Observe the number of UEs that

are using CA in a cell.
1526728426 L.Traffic.User.PCell.DL.Avg
1526728517 L.Traffic.User.SCell.DL.Max
1526728427 L.Traffic.User.SCell.DL.Avg
1526728424 L.ChMeas.PRB.DL.PCell.Used. Observe the number of PRBs

Avg occupied by CA UEs.
1526728425 L.ChMeas.PRB.DL.SCell.Used.
Avg
1526728564 L.Thrp.bits.DL.CAUser Observe the total volume of

traffic transmitted to CA UEs in
a cell.
1526728565 L.Thrp.Time.DL.CAUser Observe the total duration of

downlink transmission to CA
UEs in a cell.
1526728514 L.E-RAB.AbnormRel.CAUser Calculate the service drop rate of

CA UEs by using the following
1526728515 L.E-RAB.NormRel.CAUser formula: L.E-
RAB.AbnormRel.CAUser/
(L.E-RAB.AbnormRel.CAUser
+ L.E-RAB.NormRel.CAUser)
x 100%.
1526728520 L.HHO.ExecSuccOut.CAUser. Calculate the handover success

PCC rate of CA UEs by using the
following formula:
L.HHO.ExecSuccOut.CAUser.

1526728519 L.HHO.ExecAttOut.CAUser.P PCC/

CC L.HHO.ExecAttOut.CAUser.P
CC x 100%.
1526728518 L.HHO.PrepAttOut.CAUser.P Observe the number of outgoing

CC handover preparation attempts
for PCC anchoring of CA UEs.
1526729602 L.HHO.InterFddTdd.PrepAtt Observe the number of outgoing

Out.CAUser.PCC inter-duplex-mode handover
preparation attempts for PCC
anchoring of CA UEs.
1526729603 L.HHO.InterFddTdd.ExecAtt Calculate the success rate of

Out.CAUser.PCC handovers from LTE FDD to
LTE TDD for PCC anchoring of
1526729604 L.HHO.InterFddTdd.ExecSucc CA UEs by using the following
Out.CAUser.PCC formula:
L.HHO.InterFddTdd.ExecSucc
Out.CAUser.PCC/
L.HHO.InterFddTdd.ExecAttO
ut.CAUser.PCC x 100%.
1526729045 L.CA.DLSCell.Add.Att Observe the total number of

attempts to add or remove SCells
1526729046 L.CA.DLSCell.Add.Succ for CA UEs in a cell, and
1526729047 L.CA.DLSCell.Rmv.Att calculate the total success rate of
adding or removing SCells for
1526729048 L.CA.DLSCell.Rmv.Succ CA UEs in the cell.
1526730592 L.CA.DLSCell.Add.Meas.Att Observe the number of attempts

to add or remove SCells for CA
1526730593 L.CA.DLSCell.Add.Meas.Succ UEs based on A4 or A2
1526730594 L.CA.DLSCell.Rmv.Meas.Att measurements, respectively, in a
cell, and calculate the success
1526730595 L.CA.DLSCell.Rmv.Meas.Succ rate of such attempts in the cell.
1526730590 L.CA.DLSCell.Add.Blind.Att Observe the number of attempts

to add SCells for CA UEs in a
1526730591 L.CA.DLSCell.Add.Blind.Succ blind manner in a cell, and
calculate the success rate of such
attempts in the cell.
1526730596 L.CA.DLSCell.Mod.Att Observe the number of SCell

changes based on event A6 in a
1526730597 L.CA.DLSCell.Mod.Succ cell, and calculate the success
rate of the SCell changes in the
cell.
1526728999 L.CA.DLSCell.Act.Att Observe the number of attempts

to activate or deactivate SCells
1526729000 L.CA.DLSCell.Act.Succ

1526729001 L.CA.DLSCell.Deact.Att for CA UEs in a cell, and

calculate the success rate of
1526729002 L.CA.DLSCell.Deact.Succ activating or deactivating SCells
for CA UEs in the cell.
1526732658 L.CA.Traffic.bits.DL.PCell Observe the MAC-layer traffic

volume of the CA UEs that treat
1526729259 L.CA.Traffic.bits.DL.SCell a cell as their PCell or SCell. In
1526729003 L.CA.DL.PCell.Act.Dur addition, observe the total
duration of downlink data
1526729004 L.CA.DL.SCell.Act.Dur transmission to the CA UEs that
treat the cell as their PCell or
SCell.
1526732656 L.Traffic.User.SCell.Active.DL. Observe the average number and

Avg maximum number of CA UEs
that treat the cell as their SCell
1526732657 L.Traffic.User.SCell.Active.DL. and have the SCell activated.
Max
Real-Time UE-Level Performance Monitoring on the U2000

Start real-time monitoring tasks on CA cells on the U2000 to check the performance of CA UEs.
The U2000 provides the following UE-level monitoring items:
l BLER
l Power Headroom
l Quality of Channel
l Scheduling
l Throughput
l UL Power Control
l DL Power Control
l MCS Count
l ICIC (User)
6.6 Parameter Optimization

Adjust parameter settings as described in this section to improve network performance.
Common Parameters
This section describes the parameters that are common to all three CA configuration modes.
specify the CA algorithm switch settings.

Param Parameter ID Setting Notes Data

eter Source
Name
CA ENodeBAlgoS l PdcchOverlapSrchSpcSwitch User-

Algorit witch. You are advised to select this option only if defined
hm CaAlgoSwitch most CA UEs on the network comply with
Switch 3GPP TS 36.213 V10.9.0 or later
specifications. Selecting the option in this
situation helps increase the success rate of
aperiodic SCC CSI reporting and the SCC
throughput.
NOTE
If a large number of RRC connection
reconfiguration failures occur on a network, it is an
indication that most CA UEs on the network do not
comply with 3GPP TS 36.213 V10.9.0 or later
specifications.
l CaCapbFiltSwitch
You are advised to select this option only in
the following case to reduce service drops: A
large number of RRC connection
reconfiguration rejection messages appear in
the network because CA UEs reject SCC
configuration, and CA UEs experience
service drops. This occurs when the eNodeB
and the UE support the same band
combinations but different bandwidth
combinations, and the UE does not report the
IE supportedBandwidthCombinationSet to
the eNodeB. When this option is not selected,
CA does not work for a CA UE if the UE
reports the IE supportedBandwidthCombina-
tionSet but does not support the band
combinations configured in the network.
l PccAnchorSwitch
Select this option only if you intend to use
PCC anchoring.
l SccBlindCfgSwitch
Select this option only if you intend to use
blind SCell configuration for CA-group-
based CA.
l SccA2RmvSwitch
Select this option only if you intend to allow
the eNodeB to deliver the A2 measurement
configuration for SCells that have been
configured based on A4 measurements.
l CaTrafficTriggerSwitch


eter Source
Name
Select this option only if you intend to allow

the eNodeB to configure and remove SCells
based on traffic volume.
l HoWithSccCfgSwitch
Select this option if you intend to allow the
eNodeB to configure SCells for CA UEs
during their handovers. Do not select this
option if you intend to have SCells removed
after the CA UEs are handed over.
l SccModA6Switch
You are advised to select this option only if
you intend to have SCells changed to better
intra-frequency neighboring cells. If this
option is not selected, the eNodeB does not
support SCell changes based on event A6.
l GbrAmbrJudgeSwitch
When the bit rate of each GBR service reaches
the GBR or the total rate of non-GBR services
reaches the AMBR, the PRBs on the PCC may
be exhausted instantaneously. In this
situation, if GbrAmbrJudgeSwitch is on, the
eNodeB does not activate the SCell for the UE
even if the traffic conditions meet the SCell
activation criteria.
You are advised to set GbrAmbrJudgeS-
witch off so that the eNodeB activates the
SCell to improve PRB utilization in the
preceding situation.
l SccSmartCfgSwitch
This option specifies whether to enable smart
SCC selection. Select this option only if you
intend to allow the eNodeB to consider the
load status of candidate cells during SCell
configuration.
l IdleModePccAnchorSwitch
This option specifies whether to enable PCC
anchoring at RRC connection releases. Select
this option only if you intend to use PCC
anchoring at RRC connection releases.
l This parameter provides the
DlCaLbAlgoSwitch option.
This option specifies whether to enable MLB
under downlink CA. Select this option only if
you intend to use this type of MLB.

The following table describes the parameter that must be set in the GlobalProcSwitch MO to
configure the protocol compatibility switch.

eter Source
Name
Protoc GlobalProcSw This parameter specifies whether the eNodeB User-

ol itch. adopts compatibility procedures in protocol- defined
Compa ProtocolComp defined procedures. It provides the following
tibility atibilitySw options:
Switch l CaGapMeasPriOffSwitch: You are advised
to select this option only if there are a large
number of Samsung Galaxy S4 UEs on the
network in CA-group-based configuration
mode with blind SCell configuration disabled
or in frequency-based configuration mode.
l CaHoReqWithR9ConfigSwitch: You are
advised to select this option only if the
network equipment is provided by different
vendors.
The following table describes the parameters that must be set in the CellDlschAlgo MO to
specify downlink scheduling settings for a cell.

eter Source
Name
Downl CellDLSchAlg This parameter specifies the scheduling policy for User-
ink CA o. CA UEs. defined
Sched CaSchStrategy If CA UEs are treated as VIP users, set this
ule parameter to DIFF_SCHEDULE
Strateg (differentiation schedule). Otherwise, set this
y parameter to BASIC_SCHEDULE(Basic
Schedule).
The scheduling method must be consistent
between serving cells to prevent data
transmission exceptions.


eter Source
Name
Ca Scc CellDLSchAlg This parameter specifies the method for User-

Doppl o. measuring the Doppler frequency offset that is defined
er CaSccDopMea applied to frequency-selective scheduling in
Measu s SCells. To use frequency-selective scheduling in
rement SCells, set this parameter to FROMPCC
(FROMPCC). Otherwise, set this parameter to
FROMSCC(FROMSCC).
The following table describes the parameters that must be set in the ENodeBFrameOffset MO
to configure the eNodeB-specific frame offset.

eter Source
Name
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 FddFrameOffs eNodeB relative to the time of the reference
et 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 TddFrameOffs eNodeB relative to the time of the reference
et 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.
The following table describes the parameters that must be set in the CellFrameOffset MO to
configure the cell-specific frame offset.


eter Source
Name
Local CellFrameOff This parameter specifies the local ID of a cell. It User-

Cell ID set. uniquely identifies a cell served by an eNodeB. defined
LocalCellId 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 FrameOffsetM l CustomFrameOffset(Cell Frame Offset):
ode 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.
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
FrameOffset reference clock.
The following table describes the parameters that must be set in the CaMgtCfg MO to configure
carrier management.


eter Source
Name
Carrier CaMgtCfg. This parameter specifies the RSRP threshold used User-
Aggre CarrAggrA2T by a UE to determine whether to report event A2 defined
gation hdRsrp for removing an SCell.
A2 l The greater the value, the higher the
RSRP probability of removing the SCell.
thresh
old l The smaller the value, the lower the
probability of removing the SCell.
Set this parameter to a large value if you intend
to apply CA to UEs that are not located at the cell
edge.
Carrier CaMgtCfg. This parameter specifies the RSRP threshold used User-
Aggre CarrAggrA4T by a UE to determine whether to report event A4 defined
gation hdRsrp for configuring an SCell.
A4 l The greater the value, the lower the
RSRP probability of configuring the SCell.
thresh
old l The smaller the value, the higher the
probability of configuring the SCell.
Set this parameter to a large value if you intend
to apply CA to UEs that are not located at the cell
edge.
The value of this parameter must be greater than
that of CaMgtCfg.CarrAggrA2ThdRsrp.
Carrier CaMgtCfg. This parameter specifies the carrier management User-

Manag CarrierMgtSwi switch. If this parameter is set to ON(On), the defined
ement tch eNodeB deactivates an SCell for a CA UE when
Switch the traffic volume of the UE is low or the channel
quality of the SCell is unsatisfactory. If this
parameter is set to OFF(Off), the eNodeB does
not deactivate the SCell until a radio link failure
occurs in the SCell.
CA CaMgtCfg. This parameter specifies the buffer delay User-

Active ActiveBufferD threshold used to evaluate the activation of an defined
Buffer elayThd SCell.
Delay l The greater the value, the lower the
Thresh probability of activating the SCell.
old
l The smaller the value, the higher the
probability of activating the SCell.
To raise the probability of SCell activation,
reduce the value of this parameter.


eter Source
Name
CA CaMgtCfg. This parameter specifies the buffered data User-

Active ActiveBuffer- threshold used to evaluate the activation of an defined
Buffer LenThd SCell.
Length l The greater the value, the lower the
Thresh probability of activating the SCell.
old
probability of activating the SCell.
To raise the probability of SCell activation,
reduce the value of this parameter.
NOTE
You are not advised to set this parameter to 0. If it is
set to 0, the eNodeB activates a configured SCell as
long as the eNodeB intends to send data to the CA UE.
CA CaMgtCfg. This parameter specifies the data rate threshold User-

Deacti DeactiveThrou used to evaluate the deactivation of an SCell. defined
ve ghputThd l The higher the threshold, the higher the
Throu probability of deactivating the SCell.
ghput
Thresh l The lower the threshold, the lower the
old probability of deactivating the SCell.
To raise the probability of SCell deactivation,
increase the value of this parameter.
CA CaMgtCfg. This parameter specifies the buffered data User-

Deacti DeactiveBuffer threshold used to evaluate the deactivation of an defined
ve LenThd SCell.
Buffer l The higher the threshold, the higher the
Length probability of deactivating the SCell.
Thresh
old l The lower the threshold, the lower the
probability of deactivating the SCell.
To raise the probability of SCell deactivation,


eter Source
Name
SCC CaMgtCfg. This parameter specifies the CQI threshold used User-
Disabl SccDeactCqiT to evaluate the deactivation of an SCell for a CA defined
e CQI hd 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
l The lower the threshold, the lower the
To maintain active SCells only when channel
quality is high, increase the value of this
parameter.
SCC CaMgtCfg. This parameter specifies the minimum interval User-

Config SccCfgInterval after which the eNodeB attempts to configure an defined
uration SCell again for a CA UE whose SCell failed to be
Interva configured. The eNodeB makes the attempt only
l if the traffic volume of the UE always meets the
SCell activation condition throughout a period.
l A smaller value results in more frequent SCell
configurations and more RRC Connection
Reconfiguration messages transmitted to
configure SCells. In addition, it leads to a
greater decrease in cell throughput if the
eNodeB configures SCells based on A4
measurements and the UE requires inter-
frequency measurement gaps.
l A larger value results in less frequent SCell
configurations and fewer RRC Connection
Reconfiguration messages transmitted to
configure SCells. In addition, it leads to a
smaller decrease in cell throughput if the
eNodeB configures SCells based on A4
measurements and the UE requires inter-
frequency measurement gaps.
To accelerate SCell configuration, reduce the
value of this parameter.


eter Source
Name
Carrier CaMgtCfg. This parameter specifies the offset for CA event User-
Aggre CarrAggrA6Of A6, which is triggered when the signal quality of defined
gation fset a neighboring cell is higher than that of an SCell.
A6 l The greater the value, the lower the
Offset probability of changing the SCell based on
event A6.
probability of changing the SCell based on
event A6.
To raise the signal quality requirement for SCell
changes, increase the value of this parameter.
CA A6 CaMgtCfg. This parameter specifies the number of periodic User-

Report CaA6ReportA measurement reports sent after CA event A6 is defined
Amou mount triggered. For details, see 3GPP TS 36.331.
nt l The greater the value, the higher the UE power
consumption. However, if this parameter is
set to a large value, the eNodeB can monitor
the radio signal condition of the SCell's intra-
frequency neighboring cells. When the signal
quality in the SCell is poor, the eNodeB can
change the SCell in a timely manner to prevent
a decrease in the SCell transmission
efficiency.
l The smaller the value, the lower the UE power
consumption. However, if this parameter is
set to a small value, the eNodeB may not know
the radio signal condition of the SCell's intra-
frequency neighboring cells. When the signal
quality in the SCell is poor, the eNodeB may
not change the SCell in a timely manner,
which in turn lowers the SCell transmission
efficiencyCaUeMinDataVolRatio.
To raise the probability of changing the SCell,


eter Source
Name
CA A6 CaMgtCfg. This parameter specifies the interval between User-

Report CaA6ReportIn periodic measurement reports that are sent after defined
Interva terval CA event A6 is triggered. For details, see 3GPP
l TS 36.331.
l The greater the value is, the less frequently the
UE sends A6 measurement reports, and the
lower the UE power consumption is.
However, if this parameter is set to a large
value, the eNodeB may not know the radio
signal condition of the SCell's intra-frequency
neighboring cells. When the signal quality in
the SCell is poor, the eNodeB may not change
the SCell in a timely manner, so the SCell
transmission efficiency decreases.
l The smaller the value is, the more frequently
the UE sends A6 measurement reports, and
the higher the UE power consumption is.
However, if this parameter is set to a small
value, the eNodeB can monitor the radio
signal condition of the SCell's intra-frequency
neighboring cells. When the signal quality in
the SCell is poor, the eNodeB can change the
SCell in a timely manner to prevent a decrease
in the SCell transmission efficiency.
To accelerate SCell changes for CA UEs whose
PCell remains unchanged, reduce the value of this
parameter.


eter Source
Name
Cell CaMgtCfg. This parameter specifies the maximum User-

Maxim CellMaxPccN permissible number of UEs that treat the cell as defined
um umber their PCell. If the number of UEs that treat the cell
PCC as their PCell has reached the value of this
Numb parameter, the eNodeB prohibits SCell
er configuration for any other UEs in the cell.
l If this parameter is set to a larger value, more
UEs are allowed to treat the cell as their PCell.
l If this parameter is set to a smaller value,
fewer UEs are allowed to treat the cell as their
PCell. If this parameter is set to 0, no UEs are
allowed to treat the cell as their PCell, but UEs
can treat the cell as their SCell. If the sum of
the values of this parameter for all cells on a
board exceeds the board capacity, the number
of UEs that can treat a cell as their PCell is
preferentially subject to the board capacity.
To allow more UEs to treat a cell as their PCell,
increase the value of this parameter for the cell.
To allow fewer UEs to treat a cell as their PCell,
decrease the value of this parameter for the cell.
CA CaMgtCfg. This parameter specifies the AMBR threshold User-

user CaAmbrThd used for the evaluation of CA for UEs. CA is defined
AMB allowed for CA UEs whose AMBR exceeds this
R threshold.
Thresh l A larger value of this parameter results in a
old smaller number of UEs for which CA is
allowed.
l A smaller value of this parameter results in a
larger number of UEs for which CA is
allowed.
To allow CA for more UEs, decrease the value of
this parameter. To allow CA for fewer UEs,
The following table describes the eNodeB-level parameters that must be set in the
eNodeBMlb MO to configure mobility load balancing for CA.


eter Source
Name
DL CA eNodeBMlb. This parameter specifies the maximum number of User-

LB DlCaLbMaxC CCs aggregated for each CA UE whose load is to defined
Max CNum be transferred for MLB. If this parameter is set to
Comp 2CC(2CC), the eNodeB transfers the load of CA
onent UEs in the downlink 2CC aggregation state. If
Carrier this parameter is set to 3CC(3CC), the eNodeB
Numb transfers the load of CA UEs in the downlink 2CC
er aggregation state and those in the downlink 3CC
aggregation state.
CA UE eNodeBMlb. This parameter specifies the minimum required User-

Minim CaUeMinData ratio (expressed in percentage) of the data volume defined
um VolRatio on a high-load CC to that on a low-load CC for
Data each CA UE. For example, if this parameter is set
Volum to 20, the minimum ratio for a single CA UE is
e Ratio 1/5. If this parameter is set to 0, the minimum ratio
is 0/1, which means that all data of the CA UE on
the high-load CC can be transferred to the low-
load CC.
This section describes the parameters specific to CA-group-based configuration.
The following table describes the parameters that must be set in a CaGroupCell MO to configure
a candidate PCell in a CA group.

eter Source
Name
Preferr CaGroupCell. This parameter specifies the PCell priority of a User-

ed PreferredPCel cell. defined
PCell lPriority l The greater the value is, the more probable it
Priority is for CA UEs to treat the cell as their PCell.
l The smaller the value is, the less probable it
is for CA UEs to treat the cell as their PCell.
To raise the probability that CA UEs treat the cell
as their PCell, increase the value of this
parameter.


eter Source
Name
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.
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.
PCell CaGroupCell. This parameter specifies the RSRQ threshold for User-
A4 PCellA4RsrqT CA event A4 during PCC anchoring. If the defined
RSRQ hd measured RSRQ of an inter-frequency
l The greater the value, the lower the
PCC anchoring.
To shrink the area where the cell is the PCC
The following table describes the parameters that must be set in a CaGroupSCellCfg MO to
configure a candidate SCell.

eter Source
Name
SCell CaGroupSCel This parameter specifies the local ID of a User-

Local lCfg. candidate SCell. defined
Cell ID SCellLocalCel
lId


eter Source
Name
SCell CaGroupSCel This parameter specifies the eNodeB ID of the User-

eNode lCfg. candidate SCell. defined
B ID SCelleNodeBI
d
SCell CaGroupSCel This parameter specifies the priority of the User-

Priority lCfg. candidate SCell. The priority level has a positive defined
SCellPriority correlation with the parameter value. The value 0
indicates that the cell cannot be configured as an
SCell.
To raise the probability that CA UEs treat the cell
as their SCell, increase the value of this
parameter.
To prohibit the cell from being configured as an
SCell, set this parameter to 0.
SCell CaGroupSCel This parameter specifies whether the candidate User-

Blind lCfg. SCell can be configured as an SCell for CA UEs defined
Config SCellBlindCfg in a blind manner.
uration Flag This parameter takes effect only if
Flag SccBlindCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter
is on.
l If this parameter is set to TRUE(TRUE), the
eNodeB can configure this candidate cell as
an SCell for CA UEs in a blind manner,
without delivering A4 measurement
l If this parameter is set to FALSE(FALSE),
the eNodeB delivers A4 measurement
configurations to CA UEs before it can
configure this candidate cell as an SCell.


eter Source
Name
SCell CaGroupSCel This parameter specifies the offset of the actual User-
A4 lCfg. threshold for CA event A4 relative to the defined
Offset SCellA4Offset CaMgtCfg.CarrAggrA4ThdRsrp parameter
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
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 SCellA2Offset CaMgtCfg.CarrAggrA2ThdRsrp parameter
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.
probability of removing an SCell.
SCells, set this parameter according to operators'
policies.
Frequency-based or Adaptive Configuration

This section describes the parameters specific to frequency-based or adaptive configuration.
The following table describes the parameters that must be set in a PccFreqCfg MO to configure
a candidate PCC.


eter Source
Name
Preferr PccFreqCfg. This parameter specifies the priority of a User-

ed PCC PreferredPcc- candidate PCC. defined
Priority Priority l The greater the value is, the more probable it
is for CA UEs to treat the carrier as their PCC.
l The smaller the value is, the less probable it is
for CA UEs to treat the carrier as their PCC.
PCC PccFreqCfg. This parameter specifies the RSRP threshold for User-
A4 PccA4RsrpTh CA event A4 during PCC anchoring. defined
RSRP d l The greater the value, the lower the probability
Thresh of an inter-frequency handover for PCC
old anchoring.
To shrink the area where the carrier is the PCC
PCC PccFreqCfg. This parameter specifies the RSRQ threshold for User-
A4 PccA4RsrqTh CA event A4 during PCC anchoring. If the defined
RSRQ d measured RSRQ of an inter-frequency
l The greater the value, the lower the probability
of an inter-frequency handover for PCC
anchoring.
To shrink the area where the carrier is the PCC
The following table describes the parameters that must be set in an SccFreqCfg MO to configure
a candidate SCC.


eter Source
Name
PCC SccFreqCfg. This parameter specifies the downlink EARFCN User-

Downli PccDlEarfcn of a PCC. Set this parameter based on the network defined
nk plan.
EARF
CN
SCC SccFreqCfg. This parameter specifies the downlink EARFCN User-

Downli SccDlEarfcn of a candidate SCC. Set this parameter based on defined
nk the network plan.
EARF
CN
SCC SccFreqCfg. This parameter specifies the priority with which User-
Priority SccPriority the candidate SCC works as an SCC for the PCC. defined
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 SccA2Offset threshold for CA event A2 relative to the defined
Offset 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.
SCCs, set this parameter according to operators'
policies.


eter Source
Name
SCC SccFreqCfg. This parameter specifies the offset of the actual User-
A4 SccA4Offset threshold for CA event A4 relative to the defined
Offset 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.
SCCs, set this parameter according to operators'
policies.
The following table describes the parameter that must be set in the CaMgtCfg MO to specify
the SCell aging time.

eter Source
Name
SCell CaMgtCfg. This parameter specifies the length of the aging User-
Aging SCellAgingTi time for SCells that are dynamically configured defined
Time me 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.
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.

The following table describes the parameter that must be set in a CaGroupSCellCfg MO to
specify the blind SCell configuration capability.

eter Source
Name
SCell CaGroupSCel This parameter specifies whether a candidate cell User-

Blind lCfg. can be configured as an SCell in a blind manner defined
Config SCellBlindCfg during adaptive CA.
uration Flag l If this parameter is set to TRUE(TRUE), the
Flag eNodeB can configure this candidate cell as
an SCell for CA UEs in a blind manner,
without delivering A4 measurement
l If this parameter is set to FALSE(FALSE),
the eNodeB delivers A4 measurement
configurations to CA UEs before it can
configure this candidate cell as an SCell.
6.7 Troubleshooting
Alarm-triggered eNodeB Operations
Alarm ID Alarm NE Feature ID Feature Name
Name
ALM-26200 Board eNodeB l TDLAOFD-00100 l LTE-A Introduction

Hardware 1 l Carrier Aggregation for
Fault l TDLAOFD-00100 Downlink 2CC in
2 40MHz
ALM-26215 Inter- eNodeB
Board l TDLAOFD-07020 l Flexible CA from
Service 1 Multiple Carriers
Link l TDLAOFD-08140 l Inter-eNodeB CA
Failure 2 based on Relaxed
l TDLAOFD-08140 Backhaul [Trial]
ALM-29240 Cell eNodeB
Unavaila 7 l Carrier Aggregation for
ble l TDLAOFD-08140 Uplink 2CC [Trial]
5 l Carrier Aggregation for
ALM-29243 Cell eNodeB Downlink 3CC [Trial]
l TDLAOFD-08140
Capabilit
4 l Carrier Aggregation for
y
l MRFD-101231 Downlink 4CC [Trial]
Degraded
l FDD+TDD Carrier
Aggregation(LTE
TDD) [Trial]

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.
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 2 Run the MOD ENODEBALGOSWITCH command with the FreqCfgSwitch

(FreqCfgSwitch) option of the CA Algorithm Switch parameter deselected. Then, check
whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero
values.
l If the counters produce non-zero values, no further action is required.
l If the counters retain the value of 0, go to Step 3.
Step 3 Check whether ALM-26200 Board Hardware Fault, ALM-26215 Inter-Board Service Link
Failure, ALM-29240 Cell Unavailable, or ALM-29243 Cell Capability Degraded 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 none of the alarms 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
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 window, 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.
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 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.
l If the eNodeB does not deliver an RRC_CONN_RECFG message to configure an SCell
for the UE, contact Huawei engineers.
----End
If CA works in frequency-based or adaptive 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 on.
l If the switch is on, go to Step 3.
l If the switch is off, go to Step 2.
Step 2 Run the MOD ENODEBALGOSWITCH command with the FreqCfgSwitch

(FreqCfgSwitch) option of the CA Algorithm Switch parameter selected. Then, check whether
the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values.
l If the counters produce non-zero values, no further action is required.
l If the counters retain the value of 0, go to Step 3.
Step 3 Check whether ALM-26200 Board Hardware Fault, ALM-26215 Inter-Board Service Link
Failure, ALM-29240 Cell Unavailable, or ALM-29243 Cell Capability Degraded is reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters

4.
l If none of the alarms 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 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 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

eRAN TDD 7 Engineering Guidelines for TDLAOFD-070201 Flexible
Carrier Aggregation Feature Parameter Description CA from Multiple Carriers
7
TDLAOFD-070201 Flexible CA from Multiple
Carriers
7.1 When to Use TDLAOFD-070201

If several carriers are to be selected from multiple carriers for flexible aggregation, enable
TDLAOFD-070201 Flexible CA from Multiple Carriers.
In addition, TDLAOFD-070201 Flexible CA from Multiple Carriers requires that
TDLAOFD-001001 LTE-A Introduction and optionally TDLAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz be enabled. For the deployment scenarios for the two
prerequisite features, see 6.1 When to Use TDLAOFD-001001 and TDLAOFD-001002.

For details, see 6.2 Required Information.
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 220 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 220
Mbit/s.
License
Deploying TDLAOFD-070201 Flexible CA from Multiple Carriers requires the following
licenses:
l In CA-group-based configuration mode

In a CA group with cells on more than two frequencies, each cell requires one sales unit of
the license for TDLAOFD-070201 Flexible CA from Multiple Carriers and one sales unit
of the license for TDLAOFD-001001 LTE-A Introduction.
If the total bandwidth of a cell and any other cell in the CA group is between 30 MHz and
40 MHz (including 40 MHz), the cell requires one sales unit of the license for
TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.
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
TDLAOFD-070201 Flexible CA from Multiple Carriers and one sales unit of the license
for TDLAOFD-001001 LTE-A Introduction.
If the total bandwidth of a cell and any other cell in the set is between 30 MHz and 40 MHz
(including 40 MHz), the cell requires one sales unit of the license for TDLAOFD-001002
Carrier Aggregation for Downlink 2CC in 40MHz.
Feature Feature Model License NE Sales Unit

ID Name Control
Item
TDLAOF LTE-A LT1SLTE LTE-A eNodeB per cell

D-001001 Introduction AID01 Introduction
(per cell)


ID Name Control
Item
TDLAOF Carrier LT1SC2C Carrier eNodeB per cell

D-001002 Aggregation 40M00 Aggregation
for Downlink for Downlink
2CC in 40MHz 2CC in
40MHz (per
cell)
TDLAOF Flexible CA LT1SCA Flexible CA eNodeB per cell

D-070201 from Multiple DFMC00 from Multiple
Carriers Carriers (per
cell)
Others
The prerequisite features for TDLAOFD-070201 Flexible CA from Multiple Carriers must be
activated.

For details, see 6.4.2 Data Preparation.
7.4.3 Precautions
For details, see 6.4.3 Precautions.

l If BBU3900 is used, LBBPd or UBBP boards must be installed in slots 2 and 3. If CA is
performed on two boards in other slots, CA cell data still travels through slots 2 and 3. As
a result, more backplane bandwidth of slots 2 and 3 is required, and CA can take effect in
fewer cells.
l If BBU3910 is used, there is no requirement on the board positions.
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.

For details, see 6.4.6 Activation Observation.

7.4.7 Deactivation
l In CA-group-based configuration mode, perform step 3 described in 6.4.7.3 Using MML
Commands of 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 described in 6.4.7.3 Using MML
Commands of 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 described in 6.4.7.3 Using MML
Commands of 6.4.7 Deactivation to delete candidate SCCs so that each PCC is
accompanied by only one candidate SCC.

For details, see 6.5 Performance Monitoring.

For details, see 6.6 Parameter Optimization.
7.7 Troubleshooting
For details, see 6.7 Troubleshooting.

eRAN TDD 8 Engineering Guidelines for TDLAOFD-081402 Inter-
Carrier Aggregation Feature Parameter Description eNodeB CA based on Relaxed Backhaul [Trial]
8
TDLAOFD-081402 Inter-eNodeB CA based on
Relaxed Backhaul [Trial]

Enable TDLAOFD-081402 when operators require CA in inter-frequency coverage by different
eNodeBs on a network with relaxed backhaul requirements. The scenarios include overlapping
areas of indoor and outdoor inter-frequency coverage.
In addition, TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul [Trial] requires
that TDLAOFD-001001 LTE-A Introduction and optionally TDLAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz be enabled. For the deployment scenarios for the two
prerequisite features, see 6.1 When to Use TDLAOFD-001001 and TDLAOFD-001002.
NOTE
In eRAN8.1, TDLAOFD-081402 can be used to aggregate only a combination of FDD and TDD carriers.
It does not work in a TDD-only network.

8.3 Planning
RF 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:
l Cells on LBBPc boards do not support this CA feature.

l Micro cells do not support this CA feature.
8.4 Deployment
Deploy this CA feature on two inter-eNodeB inter-frequency cells.
8.4.1 Requirements
None
NEs
For details, see 6.4.1 Requirements.
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 TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul requires the
licenses listed in this section. When RelaxedBackhaulCaSwitch under
ENodeBAlgoSwitch.CaAlgoSwitch is set on for an eNodeB, the eNodeB requires one sales unit
of the license for TDLAOFD-081402 Inter-eNodeB CA based on Relaxed Backhaul.
For this feature to take effect, the prerequisite features must be licensed as follows:
l If the total bandwidth of the downlink aggregated cells is less than or equal to 30 MHz,
each cell requires one sales unit of the license for TDLAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the downlink aggregated cells is between 30 MHz and 40 MHz
(including 40 MHz), each cell 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.
Feature ID Feature Model License Control NE Sales

Name Item Unit
TDLAOFD LTE-A LT1SLTE LTE-A eNodeB per cell

-001001 Introduction AID01 Introduction (per
cell)


Name Item Unit
TDLAOFD Carrier LT1SC2C4 Carrier eNodeB per cell

-001002 Aggregation 0M00 Aggregation for
for Downlink Downlink 2CC in
2CC in 40MHz 40MHz (per cell)
TDLAOFD Inter-eNodeB LT1STIBC Inter-eNodeB CA eNodeB per

-081402 CA based on AD00 based on Relaxed eNodeB
Relaxed Backhaul (per
Backhaul eNodeB)
[Trial]
Others
The prerequisite features for the CA feature must have been enabled.

Make data preparation as described in 6.4.2 Data Preparation. In addition:
l In CA-group-based configuration mode, configure CaGroup, CaGroupCell, and

CaGroupSCellCfg MOs on each BBU and ensure that the CaGroup and CaGroupCell
configurations of the BBUs involved in CA are consistent. If the configurations are
inconsistent, CA does not work.
l In frequency-based or adaptive configuration mode, no more data preparation is required.
Frequency-based or adaptive configuration mode is recommended for relaxed-backhaul-
based inter-eNodeB CA.
l Set the following switches in the ENodeBAlgoSwitch MO on.


Name
CA ENodeBAlgoS The RelaxedBackhaulCaSwitch User-defined

Algorithm witch. option of this parameter specifies
Switch CaAlgoSwitch whether to enable CA between cells
served by different macro eNodeBs on
a network with relaxed backhaul
requirements.
l To enable this type of CA, set this
switch on.
l If this type of CA is not required,
you are advised to set this switch
off.
The HetNetCaSwitch option of this
parameter specifies whether to enable
CA between macro and micro cells on
a network with relaxed backhaul
requirements.
l To enable this type of CA, set this
switch on.
l If this type of CA is not required,
you are advised to set this switch
off.
OverBBUs ENodeBAlgoS The option FreqCfgCaOverBBUsS- User-defined

Switch witch. witch specifies whether to enable inter-
OverBBUsSwit BBU CA in frequency-based
ch configuration mode. It takes effect only
when FreqCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch
parameter is on.
l If multi-BBU interconnection is
deployed on the network, select this
option to enable inter-BBU CA.
l If multi-BBU interconnection is not
deployed on the network, do not
select this option. If you select it,
inter-BBU CA may occur but fail.
This prolongs the time for SCell
configuration.
8.4.3 Precautions
The precautions described in 6.4.3 Precautions apply to relaxed-backhaul-based inter-eNodeB
CA. Frequency-based or adaptive configuration mode is recommended for this feature.

The CA-group-based configuration mode requires that the CaGroup, CaGroupCell, and
CaGroupSCellCfg MOs be configured on each eNodeB. However, frequency-based and
adaptive configuration modes do not have this requirement.

Besides the hardware adjustment described in 6.4.4 Hardware Adjustment, inter-eNodeB CA
based on relaxed backhaul requires main control boards of the eNodeBs be interconnected
through an IP network for information exchange. For details about the connections, see eX2 Self-
Management.
8.4.5 Activation
In addition to the steps in 6.4.5 Activation, set the required switches on as described in this
section.
l Activating CA between inter-eNodeB macro cells

On the U2000 client, run the MOD ENODEBALGOSWITCH command with the
RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) option of the CA Algorithm
Switch parameter selected.
MOD ENODEBALGOSWITCH:CAALGOSWITCH=RelaxedBackhaulCaSwitch-1;
Perform this step on each eNodeB.

l Activating CA between macro and micro cells
1. On the U2000 client, run the MOD ENODEBALGOSWITCH command on the macro
eNodeB with the RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) option of the
CA Algorithm Switch parameter selected.
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, in frequency-based or adaptive configuration mode, run the following command on

each eNodeB:
MOD ENODEBALGOSWITCH:OVERBBUSSWITCH=FreqCfgCaOverBBUsSwitch-1;

After inter-eNodeB CA based on relaxed backhaul is enabled, the eNodeB configures an SCell
for a CA UE when the required conditions are met. Observe the counters listed in the following
table to obtain PCell and SCell statistics.
If the values of L.Traffic.User.PCell.DL.RelaxedBackhaulCA.Avg and

L.ChMeas.PRB.DL.SCell.RelaxedBackhaulCAUsed.Avg are not zero, the CA feature has been
activated successfully. If the values of both counters remain at zero and CA UEs exist in the
network, the CA feature has not been activated.

Table 8-1 Counters related to inter-eNodeB CA based on relaxed backhaul
1526732909 L.Traffic.User.PCell.DL. Average number of downlink relaxed-

RelaxedBackhaulCA.Av backhaul-based inter-eNodeB CA UEs that
g treat the local cell as their PCell
1526732955 L.Traffic.User.SCell.DL. Average number of downlink relaxed-

RelaxedBackhaulCA.Av backhaul-based inter-eNodeB CA UEs that
g treat the local cell as their SCell
1526732911 L.ChMeas.PRB.DL.PCel Number of downlink PRBs occupied by

l.RelaxedBackhaulCAUs relaxed-backhaul-based inter-eNodeB CA
ed.Avg UEs that treat the local cell as their PCell
1526732912 L.ChMeas.PRB.DL.SCel Number of downlink PRBs occupied by

l.RelaxedBackhaulCAUs relaxed-backhaul-based inter-eNodeB CA
ed.Avg UEs that treat the local cell as their SCell
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.
8.4.7 Deactivation
l Deactivating CA between inter-eNodeB macro cells
Run the MOD ENODEBALGOSWITCH command with the
Switch parameter deselected.

l Deactivating CA between macro and micro cells
Run the MOD ENODEBALGOSWITCH command with the
Switch parameter deselected on the macro eNodeB.
Run the MOD ENODEBALGOSWITCH command with the HetNetCaSwitch

(HetNetCaSwitch) option of the CA Algorithm Switch parameter deselected on the micro
eNodeB.
MOD ENODEBALGOSWITCH:CAALGOSWITCH=HetNetCaSwitch-0;

In addition to the counters listed in 6.5 Performance Monitoring, monitor the following
counters and compare them with the network plan to evaluate feature performance.

1526732909 L.Traffic.User.PCell.DL. Number of UEs on which inter-eNodeB

RelaxedBackhaulCA.Avg CA based on relaxed backhaul takes
effect
1526732910 L.Traffic.User.PCell.DL.
RelaxedBackhaulCA.Max
1526732955 L.Traffic.User.SCell.DL.R
elaxedBackhaulCA.Avg
1526732954 L.Traffic.User.SCell.DL.R
elaxedBackhaulCA.Max
1526732911 L.ChMeas.PRB.DL.PCell. Number of PRBs occupied by relaxed-

RelaxedBackhaulCAUsed. backhaul-based inter-eNodeB CA UEs
Avg
1526732912 L.ChMeas.PRB.DL.SCell.
RelaxedBackhaulCAUsed.
Avg
1526733184 L.Thrp.bits.DL.Relaxed- Total traffic volume and duration of

BackhaulCAUser downlink PDCP-layer data transmission
to relaxed-backhaul-based inter-eNodeB
1526733185 L.Thrp.Time.DL.Relaxed- CA UEs in the local cell
BackhaulCAUser
1526733198 L.Traffic.User.PCell.Rela Number of times inter-eNodeB CA based

xedBackhaulCA.OFF on relaxed backhaul has stopped because
the inter-eNodeB transmission delay does
not meet the requirement

8.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.

Step 2 Check the L.Traffic.User.PCell.RelaxedBackhaulCA.OFF counter for the number of times CA

has stopped. If the counter value is less than 10, no further action is required. If the counter value
is equal to or greater than 10, contact Huawei engineers.
----End

eRAN TDD 9 Engineering Guidelines for TDLAOFD-081407 Carrier
Carrier Aggregation Feature Parameter Description Aggregation for Uplink 2CC [Trial]
9
Uplink 2CC [Trial]

Enable TDLAOFD-081407 when operators require aggregation of two uplink CCs.

9.3 Planning
RF 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:
Use LBBPd or UBBP, not LBBPc, for uplink CA.
9.4 Deployment
Deploy this CA feature on inter-frequency cells served by the same BBU.

9.4.1 Requirements
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. Additionally:
l To allow uplink 2CC aggregation to reach an uplink peak data rate of 20 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 20 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
Deploying TDLAOFD-081407 Carrier Aggregation for Uplink 2CC requires the licenses listed
in this section. When CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter is
on for a cell, the cell requires one sales unit of the license for TDLAOFD-081407 Carrier
Aggregation for Uplink 2CC.
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 30 MHz,
l If the total bandwidth of the downlink aggregated cells is between 30 MHz and 40 MHz
(including 40 MHz), each cell 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.

ID Name Control
Item
TDLAOF LTE-A LT1SLTEA LTE-A eNodeB per cell

D-001001 Introduction ID01 Introduction
(per cell)
TDLAOF Carrier LT1SC2C4 Carrier eNodeB per cell

D-001002 Aggregation 0M00 Aggregation
2CC in 2CC in
40MHz 40MHz (per
cell)


ID Name Control
Item
TDLAOF Carrier LT1STULC Carrier eNodeB per cell

D-081407 Aggregation A000 Aggregation
for Uplink for Uplink
2CC [Trial] 2CC (per cell)
Others

Make data preparation as described in 6.4.2 Data Preparation. In addition, set the following
switch on.

Name
Cell Level CaMgtCfg. The CaUl2CCSwitch option of this User-defined

CA CellCaAlgoSw parameter specifies whether to enable
Algorithm itch uplink 2CC aggregation.
Switch l To enable uplink 2CC aggregation,
set this switch on.
l To disable uplink 2CC aggregation,
set this switch off.
9.4.3 Precautions

For details, see 6.4.4 Hardware Adjustment.
9.4.5 Activation
In addition to the steps in 6.4.5 Activation, perform the following step on the U2000 client:
Run the MOD CAMGTCFG command with the CaUl2CCSwitch(CaUl2CCSwitch) option
of the Cell Level CA Algorithm Switch parameter selected.
l If only one of the two cells can act as the PCell for uplink 2CC aggregation, enable uplink
2CC aggregation in this cell.
MOD CAMGTCFG: LOCALCELLID=0, CELLCAALGOSWITCH=CaUl2CCSwitch-1;
l If both cells can act as PCells for uplink 2CC aggregation, enable uplink 2CC aggregation
in both cells.


Counter
After uplink CA is enabled, the eNodeB configures SCells for CA UEs in both uplink and
downlink 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.UL.Avg and
L.ChMeas.PRB.UL.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.
Table 9-1 Performance counters related to uplink CA
1526732905 L.Traffic.User.PCell.UL. Average number of uplink CA UEs that treat

Avg the local cell as their PCell
1526732894 L.Traffic.User.SCell.UL. Average number of uplink CA UEs that treat

Avg the local cell as their SCell
1526733015 L.ChMeas.PRB.UL.PCell Average number of uplink PRBs occupied by

.Used.Avg CA UEs that treat the local cell as their PCell
1526733016 L.ChMeas.PRB.UL.SCell Average number of uplink PRBs occupied by

.Used.Avg CA UEs that treat the local cell as their SCell
Probe
Start Probe and connect it to the CA UE, as shown in Figure 9-1, Figure 9-2, and Figure 9-3.


If there are uplink radio measurement values (such as PUSCH Power, Power Headroom, and
PDCCH UL Grant Count)for both the PCC and the SCC and non-zero MAC throughput on
the SCC, as shown in Figure 9-4 and Figure 9-5, the SCell has been successfully configured
and activated for the UE. If there are no radio measurement values for the SCC, the feature
activation has failed.

the PCC and the SCC in the uplink)
Figure 9-5 Successful SCell configuration and activation (MAC throughput on the SCC)
9.4.7 Deactivation
In addition to the steps in 6.4.5 Activation, perform the following step on the U2000 client:
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.
l If only one of the two cells can act as the PCell for uplink 2CC aggregation, disable uplink
2CC aggregation in the cell.

l If both cells can act as PCells for uplink 2CC aggregation, disable uplink 2CC aggregation
in both cells.
Step 2 (Optional) If uplink scheduler-based power control is not required, run MOD
CELLALGOSWITCH with the SchedulerCtrlPowerSwitch option of the Uplink schedule
switch parameter deselected.
MOD CELLALGOSWITCH: LOCALCELLID=0, ULSCHSWITCH=SchedulerCtrlPowerSwitch-0;
----End

1526732905 L.Traffic.User.PCell.UL. Average and maximum numbers of

Avg uplink CA UEs that treat the local cell as
their PCell
1526732906 L.Traffic.User.PCell.UL.
Max
1526732894 L.Traffic.User.SCell.UL.A Average and maximum numbers of

vg uplink CA UEs that treat the local cell as
their SCell
1526732895 L.Traffic.User.SCell.UL.
Max
1526733015 L.ChMeas.PRB.UL.PCell. Average number of uplink PRBs

Used.Avg occupied by CA UEs that treat the local
cell as their PCell
1526733016 L.ChMeas.PRB.UL.SCell. Average number of uplink PRBs

Used.Avg occupied by CA UEs that treat the local
cell as their SCell
1526733017 L.CA.Traffic.bits.UL.PCe Uplink MAC-layer traffic volume of all

ll CA UEs that treat the local cell as their
PCell
1526733018 L.CA.Traffic.bits.UL.SCel Uplink MAC-layer traffic volume of all

l CA UEs that treat the local cell as their
SCell
1526733019 L.Traffic.User.SCell.Activ Average and maximum numbers of

e.UL.Avg uplink CA UEs that treat the local cell as
their SCell and have the SCell activated
1526733020 L.Traffic.User.SCell.Activ
e.UL.Max

1526733021 L.CA.UL.PCell.Act.Dur Total duration in which SCells are active

for uplink CA UEs that treat the local cell
as their PCell

9.7 Troubleshooting

Carrier Aggregation Feature Parameter Description Aggregation for Downlink 3CC [Trial]
10
Downlink 3CC [Trial]

Enable TDLAOFD-081405 when operators require aggregation of three downlink CCs.

10.3 Planning
RF Planning
Network Planning
Hardware Planning
10.4 Deployment
Deploy this CA feature on three inter-frequency cells configured in the same BBU.

10.4.1 Requirements
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. Specifically:
l To allow downlink 3CC aggregation of cells with uplink-downlink configuration 2 to reach

a peak data rate of 330 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 330 Mbit/s.
License
Deploying TDLAOFD-081405 Carrier Aggregation for Downlink 3CC [Trial] requires the
licenses listed in this section. A cell can act as a PCell in downlink 3CC aggregation only if
CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter is on for the cell. Each
cell involved in downlink 3CC aggregation requires one sales unit of the license for
TDLAOFD-081405 Carrier Aggregation for Downlink 3CC.
l If the total bandwidth of any two downlink aggregated cells is less than or equal to 30 MHz,
l If the total bandwidth of any two downlink aggregated cells is between 30 MHz and 40
MHz (including 40 MHz), each cell requires one sales unit of the license for
TDLAOFD-001001 LTE-A Introduction and one sales unit of the license for
Feature ID Feature Model License NE Sales Unit

Name Control Item
TDLAOFD- LTE-A LT1SLTEAI LTE-A eNodeB per cell

001001 Introduction D01 Introduction
(per cell)
TDLAOFD- Carrier LT1SC2C40 Carrier eNodeB per cell

001002 Aggregation M00 Aggregation
2CC in 2CC in 40MHz
40MHz (per cell)

Feature ID Feature Model License NE Sales Unit

Name Control Item
TDLAOFD- Carrier LT1SCAD3 Carrier eNodeB per cell

081405 Aggregation CC00 Aggregation
Others

switch on.

Name
Cell Level CaMgtCfg. The CaDl3CCSwitch option of this User-defined

CA CellCaAlgoSw parameter specifies whether to enable
Algorithm itch downlink 3CC aggregation.
Switch l To enable downlink 3CC
aggregation, set this switch on.
l To disable downlink 3CC
aggregation, set this switch off.
10.4.3 Precautions

10.4.5 Activation
Step 1 Configure cells or frequencies.
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 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.
l If only one of the three cells can act as the PCell for downlink 3CC aggregation, enable
downlink 3CC aggregation in this cell.
MOD CAMGTCFG: LOCALCELLID=0, CELLCAALGOSWITCH=CaDl3CCSwitch-1;
l If two of the three cells can act as PCells for downlink 3CC aggregation, enable downlink
3CC aggregation in these two cells.
l If all three cells can act as PCells for downlink 3CC aggregation, enable downlink 3CC
aggregation in all three cells.
----End
Counter
After downlink 3CC aggregation is enabled, the eNodeB configures two SCells for a CA UE
when the required conditions are met. Observe the counters listed in the following table to obtain
PCell statistics. If L.Traffic.User.PCell.DL.3CC.Avg produces a non-zero value, CA has been
activated successfully. If the value remains at zero and 3CC CA UEs exist in the network, CA
feature activation may fail.
Table 10-1 Performance counters related to downlink 3CC aggregation
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
Probe
Start Probe and connect it to the CA UE, as shown in Figure 10-1, Figure 10-2, and Figure
10-3.


If there are downlink radio measurement values for the PCC and both SCCs and non-zero MAC
throughput on both SCCs, as shown in Figure 10-4 and Figure 10-5, SCells has been
both SCCs, the feature activation has failed.

SCCs in the downlink)
Figure 10-5 Successful SCell configuration and activation (MAC throughput on both SCCs)
10.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 CaDl3CCSwitch(CaDl3CCSwitch) option

of the Cell Level CA Algorithm Switch parameter deselected.
If only one of the three cells can act as the PCell for downlink 3CC aggregation, disable downlink
3CC aggregation in the cell.
If two of the three cells can act as PCells for downlink 3CC aggregation, disable downlink 3CC
aggregation in the two cells.


If all three cells can act as PCells for downlink 3CC aggregation, disable downlink 3CC
aggregation in all three cells.

1526732907 L.Traffic.User.PCell.DL. Average and maximum numbers of

3CC.Avg downlink 3CC CA UEs that treat the local
cell as their PCell
3CC.Max

3CC.Active.Avg downlink 3CC CA UEs that treat the local
cell as their PCell and have all their SCells
1526732916 L.Traffic.User.PCell.DL. activated
3CC.Active.Max
1526732917 L.CA.DL.PCell.3CC.Act.Dur Duration of CA UEs with the local cell as

their PCell and with all configured two
SCCs activated
1526733012 L.Thrp.bits.DL.3CC.CAUser Downlink PDCP-layer traffic volume of

CA UEs that are in the 3CC CA state and
treat the local cell as their PCell with two
SCells activated

10.7 Troubleshooting

11
Downlink 4CC [Trial]

Enable TDLAOFD-081404 when operators require aggregation of four downlink CCs.

11.3 Planning
RF Planning
Network Planning
Hardware Planning
11.4 Deployment
Deploy this CA feature on four inter-frequency cells configured in the same BBU.

11.4.1 Requirements
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. Specifically:
l To allow downlink 4CC aggregation of cells with uplink-downlink configuration 2 to reach

a peak data rate of 440 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 440 Mbit/s.
License
Deploying TDLAOFD-081404 Carrier Aggregation for Downlink 4CC requires the licenses
listed in this section. A cell can act as a PCell in downlink 4CC aggregation only if
CaDl4CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter is on for the cell. Each
cell involved in downlink 4CC aggregation requires one sales unit of the license for
TDLAOFD-081404 Carrier Aggregation for Downlink 4CC.
l If the total bandwidth of any two downlink aggregated cells is less than or equal to 30 MHz,
l If the total bandwidth of any two downlink aggregated cells is between 30 MHz and 40
MHz (including 40 MHz), each cell requires one sales unit of the license for
TDLAOFD-001001 LTE-A Introduction and one sales unit of the license for
l Each cell requires one sales unit of the license for TDLAOFD-081405 Carrier Aggregation
for Downlink 3CC.

ID Name Control Item
TDLAOF LTE-A LT1SLTEAI LTE-A eNodeB per cell

D-001001 Introduction D01 Introduction
(per cell)
TDLAOF Carrier LT1SC2C40 Carrier eNodeB per cell

D-001002 Aggregation M00 Aggregation
2CC in 2CC in 40MHz
40MHz (per cell)


ID Name Control Item
TDLAOF Carrier LT1SCAD3 Carrier eNodeB per cell

D-081405 Aggregation CC00 Aggregation
TDLAOF Carrier LT1SCAD4 Carrier eNodeB per cell

D-081404 Aggregation CC00 Aggregation
Others

switch on.

Name
Cell Level CaMgtCfg. l The CaDl3CCSwitch option of this User-defined

CA CellCaAlgoSw parameter specifies whether to
Algorithm itch enable downlink 3CC aggregation.
Switch – To enable downlink 3CC
– To disable downlink 3CC
l The CaDl4CCSwitch option of this
parameter specifies whether to
enable downlink 4CC aggregation.
– To enable downlink 4CC
– To disable downlink 4CC
11.4.3 Precautions


11.4.5 Activation
Step 1 Configure cells or frequencies.
6.4.5 Activation with the following exceptions: Add four cells to the CA group in step 3,
and configure three candidate SCells for each PCell in step 4.
l In frequency-based configuration mode, perform the MML-based procedure described in
6.4.5 Activation with the following exception: Add at least three 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) and CaDl4CCSwitch(CaDl4CCSwitch) options of the Cell Level CA
Algorithm Switch parameter selected.
l If only one of the four cells can act as the PCell for downlink 4CC aggregation, enable
downlink 4CC aggregation in this cell.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1&CaDl4CCSwitch-1;
l If two of the four cells can act as PCells for downlink 4CC aggregation, enable downlink
4CC aggregation in these two cells.
MOD CAMGTCFG: LOCALCELLID=1, CELLCAALGOSWITCH=CaDl3CCSwitch-1&CaDl4CCSwitch-1;
l If three of the four cells can act as PCells for downlink 4CC aggregation, enable downlink
4CC aggregation in these three cells.
l If all four cells can act as PCells for downlink 4CC aggregation, enable downlink 4CC
aggregation in all four cells.
----End
Counter
After downlink 4CC aggregation is enabled, the eNodeB configures three SCells for a CA UE
when the required conditions are met. Observe the counters listed in the following table to obtain
PCell statistics. If L.Traffic.User.PCell.DL.4CC.Avg produces a non-zero value, downlink 4CC
aggregation has been activated successfully. If the value remains at zero and 4CC CA UEs exist
in the network, the activation of downlink 4CC aggregation may fail.
Table 11-1 Performance counters related to downlink 4CC aggregation
1526737780 L.Traffic.User.PCell.D Average number of CA UEs that treat the local

L.4CC.Avg cell as their PCell and have all SCells activated
for downlink 4CC CA

1526737781 L.Traffic.User.PCell.D Maximum number of CA UEs that treat the local

L.4CC.Max cell as their PCell and have all SCells activated
for downlink 4CC CA
Probe
Start Probe and connect it to the CA UE, as shown in Figure 11-1, Figure 11-2, and Figure
11-3.

If there are downlink radio measurement values for the PCC and all three SCCs and non-zero
MAC throughput on all three SCCs, as shown in Figure 11-4 and Figure 11-5, SCells have been

the SCCs, the feature activation has failed.
Figure 11-4 Successful SCell configuration and activation (radio measurement values for three
SCCs in the downlink)
Figure 11-5 Successful SCell configuration and activation (MAC throughput on three SCCs)
11.4.7 Deactivation
Run the MOD CAMGTCFG command with the CaDl3CCSwitch(CaDl3CCSwitch) and

CaDl4CCSwitch(CaDl4CCSwitch) options of the Cell Level CA Algorithm Switch
parameter deselected.
l If only one of the four cells can act as the PCell for downlink 4CC aggregation, disable
downlink 4CC aggregation in the cell.

l If two of the four cells can act as PCells for downlink 4CC aggregation, disable downlink
4CC aggregation in the two cells.
l If three of the four cells can act as PCells for downlink 4CC aggregation, disable downlink
4CC aggregation in the three cells.
l If all four cells can act as PCells for downlink 4CC aggregation, disable downlink 4CC
aggregation in all four cells.


4CC.Avg downlink 4CC CA UEs that treat the local
cell as their PCell
4CC.Max
1526737793 L.Traffic.User.CA. Average and maximum numbers of

4CC.PCell.DL.Active.Avg downlink 4CC CA UEs that treat the local
cell as their PCell and have all their SCells
1526737794 L.Traffic.User.CA. activated
4CC.PCell.DL.Active.Max
1526737813 L.Thrp.bits.DL.4CC.CAUser Total traffic volume of downlink PDCP

SDUs to CA UEs that have all SCells
activated for downlink 4CC CA in a cell


eRAN TDD 12 Engineering Guidelines for MRFD-101231 FDD+TDD
Carrier Aggregation Feature Parameter Description Carrier Aggregation(LTE TDD) [Trial]
12
MRFD-101231 FDD+TDD Carrier Aggregation
(LTE TDD) [Trial]
12.1 When to Use MRFD-101231

Use MRFD-101231 when operators require aggregation of FDD and TDD carriers in the
downlink.

12.3 Planning
RF Planning
Network Planning
For details about network planning for TDD carriers, see 6.3 Planning. For details about network
planning for FDD carriers, see Carrier Aggregation in eRAN Feature Documentation for FDD
eRAN8.1.
Hardware Planning
For details about hardware planning for TDD carriers, see 6.3 Planning. For details about
hardware planning for FDD carriers, see Carrier Aggregation in eRAN Feature
Documentation for FDD eRAN8.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.
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
Operating Environment, NEs, and Transmission Networking
The requirements described in 6.4.1 Requirements must be fulfilled. Additionally:
l To allow downlink 2FDD+2TDD aggregation to reach a peak data rate of 520 Mbit/s in
downlink 2x2 MIMO scenarios, the maximum bit rate that the UE subscribes to in the EPC
must be greater than or equal to 520 Mbit/s.
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, the prerequisite features must be licensed as follows:
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-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-080208 Carrier Aggregation for Downlink 3CC
in 60MHz.
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-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.

Name Item Unit
LAOFD-001 LTE-A LT1SA020C LTE-A Introduction eNodeB per cell

001 Introduction A00 (per cell)
LAOFD-001 Carrier LT1SA040C Carrier Aggregation eNodeB per cell

002 Aggregation A00 for Downlink 2CC in
for Downlink 40MHz (per cell)
2CC in
40MHz
LAOFD-080 Carrier LT1SCAD4 Carrier Aggregation eNodeB per cell

207 Aggregation 0M00 for Downlink 3CC in
3CC in
40MHz
LAOFD-080 Carrier LT1SCAD6 Carrier Aggregation eNodeB per cell

208 Aggregation 0M00 for Downlink 3CC in
3CC in
60MHz
TDLAOFD- LTE-A LT1SLTEAI LTE-A Introduction eNodeB per cell

001001 Introduction D01 (per cell)
TDLAOFD- Carrier LT1SC2C40 Carrier Aggregation eNodeB per cell

001002 Aggregation M00 for Downlink 2CC in
2CC in
40MHz
TDLAOFD- Carrier LT1SCAD3 Carrier Aggregation eNodeB per cell

081405 Aggregation CC00 for Downlink 3CC
for Downlink (per cell)
3CC [Trial]
Others

Make data preparation as described in 6.4.2 Data Preparation. Set the following switch in the
CaMgtCfg MO on.

Parameter Parameter ID Setting Notes Data

Name Source
Cell Level CaMgtCfg. The InterFddTddCaSwitch option of this User-

CA CellCaAlgoSwi parameter specifies whether to enable FDD defined
Algorithm tch +TDD CA.
Switch l To enable the local FDD PCell to be
aggregated with TDD SCells, set this
switch on.
l To disable FDD+TDD CA, set this switch
off.
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
Cell Level CaMgtCfg. The CaDl3CCSwitch option of this User-defined

CA CellCaAlgoS parameter specifies whether to
Algorithm witch enable downlink 3CC aggregation.
Switch l To enable downlink 3CC
l To disable downlink 3CC
l To enable downlink FDD+TDD 4CC aggregation, set the following switches in the
CaMgtCfg MO on.

Paramet Parameter ID Setting Notes Data Source

er Name
Cell CaMgtCfg. l The CaDl4CCSwitch User-defined

Level CA CellCaAlgoSwitc option of this parameter
Algorith h specifies whether to enable
m Switch downlink 4CC aggregation.
– To enable downlink
4CC aggregation, set
this switch on.
– To disable downlink
this switch off.
l The CaDl3CCSwitch
option of this parameter
specifies whether to enable
downlink 3CC aggregation.
– To enable downlink
this switch on.
– To disable downlink
this switch off.
l To enable downlink FDD+TDD 2CC aggregation in relaxed backhaul scenarios, set the
following switch in the ENodeBAlgoSwitch MO on.
Paramet Parameter ID Setting Notes Data Source

er Name
CA ENodeBAlgoSw The RelaxedBackhaulCaS- User-defined

Algorith itch. witch option of this parameter
m Switch CaAlgoSwitch specifies whether to enable CA
between cells served by
different macro eNodeBs on a
network with relaxed backhaul
requirements.
l To enable this type of CA,
set this switch on.
l If this type of CA is not
required, you are advised to
set this switch off.
12.4.3 Precautions


12.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.
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;
In addition, in frequency-based or adaptive configuration mode, run the following command on

each eNodeB:
MOD ENODEBALGOSWITCH:OVERBBUSSWITCH=FreqCfgCaOverBBUsSwitch-1;
----End

In addition to the methods described in 6.4.6 Activation Observation, observe the counters
listed in this section to verify feature activation.
After downlink FDD+TDD 2CC aggregation is enabled, the eNodeB configures an SCell 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.PCell.DL.Avg counter produces a non-zero value, downlink FDD
+TDD 2CC aggregation has been activated. If the value remains at zero, downlink FDD+TDD
2CC aggregation may not be activated.

Table 12-1 Performance counters related to downlink FDD+TDD 2CC aggregation
1526737782 L.Traffic.User.FddTddCA.PC Average number of CA UEs that treat

ell.DL.Avg the local cell as their PCell in the
downlink FDD+TDD CA state
1526737795 L.Traffic.User.FddTddCA.PC Average number of CA UEs that treat

ell.DL.Active.Avg the local cell as their PCell and have all
SCells activated for downlink FDD
+TDD CA
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.
1526737776 L.Traffic.User.FddTddCA. Average number of CA UEs that treat

3CC.PCell.DL.Avg the local cell as their PCell in the
downlink FDD+TDD 3CC CA state

3CC.PCell.DL.Active.Avg the local cell as their PCell and have all
+TDD 3CC CA
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.

4CC.PCell.DL.Avg the local cell as their PCell in the
downlink FDD+TDD 4CC CA state


4CC.PCell.DL.Active.Avg the local cell as their PCell and have all
+TDD 4CC CA
12.4.7 Deactivation
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;

In addition to the methods described in 6.5 Performance Monitoring, monitor the counters
listed in this section and compare them with the network plan to evaluate feature performance.
To evaluate the performance of downlink FDD+TDD 2CC aggregation (excluding inter-eNodeB

CA based on relaxed backhaul), monitor the following counters.
1526737782 L.Traffic.User.FddTddC Average and maximum numbers of CA

A.PCell.DL.Avg UEs that treat the local cell as their PCell
in the downlink FDD+TDD CA state
1526737783 L.Traffic.User.FddTddC
A.PCell.DL.Max

A.PCell.DL.Active.Avg UEs that treat the local cell as their PCell
and have all SCells activated for
1526737796 L.Traffic.User.FddTddC downlink FDD+TDD CA
A.PCell.DL.Active.Max
1526737807 L.Thrp.Time.DL.FddTdd Duration of downlink PDCP-layer data

CAUser transmission to CA UEs that have all
+TDD CA in a cell
1526737808 L.Thrp.bits.DL.FddTddC Total traffic volume of downlink PDCP

AUser SDUs to CA UEs that have all SCells
activated for downlink FDD+TDD CA in
a cell

1526737768 L.E- Number of abnormal E-RAB releases for

RAB.AbnormRel.FddTdd UEs in the downlink FDD+TDD CA state
CAUser
1526737774 L.E- Number of normal E-RAB releases for

RAB.NormRel.FddTddC UEs in the downlink FDD+TDD CA state
AUser
To evaluate the performance of downlink inter-eNodeB FDD+TDD 2CC aggregation based on

relaxed backhaul, monitor the following counters in addition to those listed in 8.5 Performance
Monitoring and Table 12-4.
Table 12-5 Performance counters related to downlink inter-eNodeB FDD+TDD 2CC

aggregation based on relaxed backhaul
1526737803 L.CA.Traffic.bits.RelaxedBac DL-SCH traffic volume of CA UEs that

khaulCAUsed.DL.Pcell treat the local cell as their PCell and
have all SCells activated for downlink
relaxed-backhaul-based inter-eNodeB
CA
1526737804 L.CA.Traffic.bits.RelaxedBac DL-SCH traffic volume of CA UEs that

khaulCAUsed.DL.Scell treat the local cell as their SCell and
have all SCells activated for downlink
relaxed-backhaul-based inter-eNodeB
CA
To evaluate the performance of downlink FDD+TDD 3CC aggregation, monitor the following
counters in addition to those listed in Table 12-4 and those related to downlink FDD 3CC
aggregation. (For the counters related to downlink FDD 3CC aggregation, see Carrier
Aggregation in eRAN Feature Documentation of FDD eRAN8.1.)

A.3CC.PCell.DL.Avg UEs that treat the local cell as their PCell
in the downlink FDD+TDD 3CC CA
1526737777 L.Traffic.User.FddTddC state
A.3CC.PCell.DL.Max

A. UEs that treat the local cell as their PCell
3CC.PCell.DL.Active.Avg

1526737798 L.Traffic.User.FddTddC and have all SCells activated for

A. downlink FDD+TDD 3CC CA
3CC.PCell.DL.Active.Ma
x
1526737810 L.Thrp.Time.DL. Duration of downlink PDCP-layer data

3CC.FddTddCAUser transmission to CA UEs that have all
+TDD 3CC CA in a cell
1526737811 L.Thrp.bits.DL. Total traffic volume of downlink PDCP

3CC.FddTddCAUser SDUs to CA UEs that have all SCells
activated for downlink FDD+TDD 3CC
CA in a cell

RAB.AbnormRel.FddTdd UEs in the downlink FDD+TDD 3CC CA
CAUser.3CC state

RAB.NormRel.FddTddC UEs in the downlink FDD+TDD 3CC CA
AUser.3CC state
To evaluate the performance of downlink FDD+TDD 4CC aggregation, monitor the following
counters in addition to those listed in Table 12-4 and Table 12-6.

A.4CC.PCell.DL.Avg UEs that treat the local cell as their PCell
in the downlink FDD+TDD 4CC CA
1526737779 L.Traffic.User.FddTddC state
A.4CC.PCell.DL.Max

A. UEs that treat the local cell as their PCell
4CC.PCell.DL.Active.Avg and have all SCells activated for
downlink FDD+TDD 4CC CA
1526737800 L.Traffic.User.FddTddC
A.
4CC.PCell.DL.Active.Ma
x
1526737814 L.Thrp.Time.DL. Duration of downlink PDCP-layer data

4CC.FddTddCAUser transmission to CA UEs that have all
+TDD 4CC CA in a cell

1526737815 L.Thrp.bits.DL. Total traffic volume of downlink PDCP

4CC.FddTddCAUser SDUs to CA UEs that have all SCells
activated for downlink FDD+TDD 4CC
CA in a cell

RAB.AbnormRel.FddTdd UEs in the downlink FDD+TDD 4CC CA
CAUser.4CC state

RAB.NormRel.FddTddC UEs in the downlink FDD+TDD 4CC CA
AUser.4CC state


eRAN TDD
Carrier Aggregation Feature Parameter Description 13 Parameters
13 Parameters
Table 13-1 Parameter description
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
UeCom BlkLstC ADD LOFD-0 Automat Meaning: Indicates whether to blacklist some features.
patOpt trlSwitc UECO 02001 ic LteAnrSwitchOff: This option is used to control
h MPATO LOFD-0 Neighbo whether disable intra-RAT ANR for abnormal UEs. If
PT 02002 ur this option is selected, the following functions are
MOD Relation disabled for abnormal UEs: intra-RAT event-triggered
LOFD-0 (ANR) ANR, intra-RAT fast ANR, active PCI conflict
UECO
01105 detection, ANR management based on the specified PCI
MPATO Inter-
PT LAOFD RAT group, and E-UTRAN measurements related to event-
-001001 ANR triggered ANR triggered by MLB measurements
LST controlled by MlbBasedEventAnrSwitch.
UECO LAOFD Dynami UtranAnrSwitchOff: This option is used to control
MPATO -001002 c DRX whether to disable ANR with UTRAN for abnormal
PT LAOFD Carrier UEs. If this option is selected, the following functions
-070201 Aggrega are disabled for abnormal UEs: event-triggered ANR
LAOFD tion for with UTRAN, fast ANR with UTRAN, and UTRAN
-001003 Downlin measurements related to event-triggered ANR triggered
k 2CC in by MLB measurements controlled by MlbBasedEven-
LAOFD 20MHz tAnrSwitch. GeranAnrSwitchOff: This option is used to
-080207 control whether to disable ANR with GERAN for
Carrier
LAOFD Aggrega abnormal UEs. If this option is selected, the following
-080208 tion for functions are disabled for abnormal UEs: event-
Downlin triggered ANR with GERAN, fast ANR with GERAN,
LAOFD
k 2CC in and GERAN measurements related to event-triggered
-080202
40MHz ANR triggered by MLB measurements controlled by
LOFD-0 MlbBasedEventAnrSwitch. CdmaAnrSwitchOff: This
01048 CA for option is used to control whether to disable ANR with
Downlin CDMA2000. If this option is selected, the following
LOFD-0
k 2 CC functions are disabled for abnormal UEs: fast ANR with
01001
From CDMA2000 and event-triggered ANR with
LOFD-0 Multiple CDMA2000. DynamicDrxSwitchOff: If this option is
01003 Carriers

eRAN TDD

nd
LOFD-0 Carrier selected, dynamic DRX is disabled for abnormal UEs.

01060 Aggrega CaSwitchOff: If this option is selected, SCCs are not
LBFD-0 tion for configured for abnormal UEs and PCC anchoring is
02031 2CC disabled for abnormal UEs. TtiBundlingSwitchOff: If
based on this option is selected, TTI bundling is disabled for
LOFD-0 Coordin abnormal UEs. MimoTmMode: If this option is
01017 ated selected, the MimoAdaptiveSwitch and
TDLOF BBU InitialMimoType parameters are set to
D-00200 Carrier OL_ADAPTIVE and ADAPTIVE, respectively, for
1 Aggrega abnormal UEs. AperiodicCqiRptSwitchOff: If this
TDLOF tion for option is selected, enhanced aperiodic CQI reporting is
D-00200 Downlin disabled for abnormal UEs. RohcSwitchOff: If this
2 k 3CC in option is selected, ROHC is disabled for abnormal UEs.
40MHz Tdd2CCDlCaEnhanceSwitchOff: If this option is
TDLOF
selected, the function of enhanced DL ACK
D-00110 Carrier
demodulation with two TDD component carriers
501 Aggrega
aggregated is disabled for abnormal UEs. This option
TDLAO tion for
applies only to LTE TDD.
FD-001 Downlin
k 3CC in GUI Value Range: LteAnrSwitchOff
002
60MHz (LteAnrSwitchOff), UtranAnrSwitchOff
TDLAO (UtranAnrSwitchOff), GeranAnrSwitchOff
Carrier
FD-070 (GeranAnrSwitchOff), CdmaAnrSwitchOff
Aggrega
201 (CdmaAnrSwitchOff), DynamicDrxSwitchOff
tion for
TDLOF (DynamicDrxSwitchOff), CaSwitchOff(CaSwitchOff),
Uplink
D-00104 TtiBundlingSwitchOff(TtiBundlingSwitchOff),
2CC
8 MimoTmModeSet(MimoTmModeSet), AperiodicC-
[Trial]
qiRptSwitchOff(AperiodicCqiRptSwitchOff),
LBFD-0 TTI RohcSwitchOff(RohcSwitchOff),
81103 Bundlin Tdd2CCDlCaEnhanceSwitchOff(Tdd2CCDlCaEn-
g hanceSwitchOff)
DL 2x2
Actual Value Range: LteAnrSwitchOff,
MIMO
UtranAnrSwitchOff, GeranAnrSwitchOff,
DL 4x2 CdmaAnrSwitchOff, DynamicDrxSwitchOff,
MIMO CaSwitchOff, TtiBundlingSwitchOff,
DL 4x4 MimoTmModeSet, AperiodicCqiRptSwitchOff,
MIMO RohcSwitchOff, Tdd2CCDlCaEnhanceSwitchOff
Support Default Value: LteAnrSwitchOff:0, UtranAnrSwitch-
of Off:0, GeranAnrSwitchOff:0, CdmaAnrSwitchOff:0,
aperiodi DynamicDrxSwitchOff:0, CaSwitchOff:0,
c CQI TtiBundlingSwitchOff:0, MimoTmModeSet:0,
reports AperiodicCqiRptSwitchOff:0, RohcSwitchOff:0,
RObust Tdd2CCDlCaEnhanceSwitchOff:0
Header Unit: None
Compre
ssion
(ROHC)

eRAN TDD

nd
Automat
ic
Neighbo
ur
Relation
(ANR)
Inter-
RAT
ANR
Dynami
c DRX
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
CA for
Downlin
k 2 CC
From
Multiple
Carriers
TTI
Bundlin
g
Termina
l
Awaren
ess
Differen
tiation

eRAN TDD

nd
ENodeB CaAlgo MOD LAOFD Intra- Meaning: Indicates whether to enable carrier
AlgoSwi Switch ENODE -001001 Band aggregation (CA). The switches are described as
tch BALGO 01 Carrier follows: PdcchOverlapSrchSpcSwitch: Indicates
SWITC LAOFD Aggrega whether CA UEs regard the overlapping PDCCH
H -001001 tion for candidates of the common search space and UE-specific
LST 02 Downlin search space, which are transmitted by the primary
ENODE k 2CC in serving cell (PCell), as PDCCH candidates of the
LAOFD 20MHz common or UE-specific search space. If this switch is
BALGO -001002
SWITC Inter- On and if a CA UE supports cross-carrier scheduling
01 / and is assigned a carrier indicator field (CIF), the CA
H TDLAO Band
Carrier UE determines that the overlapping PDCCH candidates
FD-001 belong to the common search space; otherwise, the CA
002 Aggrega
tion for UE determines that the overlapping PDCCH candidates
LAOFD belong to the UE-specific search space. If this switch is
Downlin
-001002 Off, the CA UE always determines that the overlapping
k 2CC in
02 / PDCCH candidates belong to the common search space.
20MHz
TDLAO CaCapbFiltSwitch: Indicates how the eNodeB performs
FD-001 Carrier CA after a CA UE reports the combination of frequency
00102 Aggrega bands. If the UECapabilityInformation message
tion for reported by a UE does not contain the IE
LAOFD
Downlin supportedBandwidthCombinationSet, the eNodeB
-070201
k 2CC in performs CA as follows: If this option is Off, the
/
40MHz eNodeB configures a secondary component carrier
TDLAO
FD-070 Support (SCC) for the UE using the default value of the IE
201 of UE supportedBandwidthCombinationSet defined in 3GPP
Categor specifications. If this option is On, the eNodeB does not
LAOFD
y6 configure an SCC for the UE. PccAnchorSwitch:
-070202
Indicates whether to enable the anchor function of the
TDLAO CA for
primary component carrier (PCC). This switch is not
FD-001 Downlin
subject to the setting of FreqCfgSwitch of the
00111 k 2CC
CaAlgoSwitch parameter. The anchor function of the
From
LAOFD PCC is enabled only when this switch is On.
Multiple
-080202 SccBlindCfgSwitch: Indicates whether a secondary
Carriers
serving cell (SCell) can be blindly configured. If this
LAOFD Carrier switch is On, the eNodeB configures a candidate SCell
-080201 Aggrega as an SCell for a CA UE without A4 measurements. If
tion for this switch is Off, the eNodeB delivers A4 measurement
2CC configurations for measuring the frequency of a
based on candidate SCell before configuring the candidate SCell
Coordin as an SCell for the CA UE. FreqCfgSwitch: Indicates
ated whether to configure CA based on frequencies or CA
BBU groups. If this switch is On, CA can be configured based
Intra- on frequencies. If this switch is Off, CA can be
band configured based on CA groups. SccA2RmvSwitch:
Carrier Indicates whether to deliver A2 measurement
Aggrega configurations for measuring a secondary component
tion for carrier (SCC) after the SCC is configured. This option

eRAN TDD

nd
Downlin is not subject to the setting of the FreqCfgSwitch option

k 2CC in of the CaAlgoSwitch parameter. If FreqCfgSwitch is
30MHz Off and SccBlindCfgSwitch is On, the setting of
Carrier SccA2RmvSwitch does not take effect. The eNodeB
Aggrega delivers A2 measurement configurations for measuring
tion for an SCC after the SCC is configured only when
Uplink SccA2RmvSwitch is On. CaTrafficTriggerSwitch:
2CC Indicates whether to add and remove an SCC based on
the traffic volume of a CA UE after the UE accesses the
Inter- network. This switch is not subject to the settings of
eNodeB FreqCfgSwitch. If the CarrierMgtSwitch parameter is
CA set to Off and CaTrafficTriggerSwitch is On, an added
based on SCC cannot be removed based on the traffic volume of
relaxed a CA UE. HoWithSccCfgSwitch: Indicates whether an
backhau SCC can be configured for a CA UE during a handover.
l This switch is not subject to the setting of
FreqCfgSwitch of the CaAlgoSwitch parameter. If this
switch is On, the source cell sends SCC information to
the target cell during the handover and the SCC is
configured for the CA UE. If this switch is Off, the
source cell does not send SCC information to the target
cell during the handover. SccModA6Switch: Indicates
whether the eNodeB delivers event A6 measurement
configurations to a CA UE after configuring an SCC for
the UE. The eNodeB delivers event A6 measurement
configurations to a CA UE after configuring an SCC for
the UE only when the switch is On. GbrAmbrJudgeS-
witch: Indicates whether to check the GBR or AMBR
when an SCell is to be activated for downlink CA. If
this switch is On, the bit rate of the bearer or aggregate
bit rate of the CA UE is checked when an SCell is to be
activated. An SCell can be activated if the bit rate has
not reached the GBR or the aggregate bit rate of the UE
has not reached the AMBR. If this switch is Off, neither
the bit rate of the bearer nor the aggregate bit rate of the
CA UE is checked when an SCell is to be activated.
MtaAlgSwitch: Indicates whether multiple timing
advances (MTAs) are supported in uplink CA scenarios.
This parameter applies only to LTE FDD. If this switch
is On, MTAs are supported. If the reported UE
capabilities indicate that the UE supports MTAs in the
uplink, uplink timing is performed on the UE based on
multiple timing advance groups (TAGs) in uplink CA
scenarios. If the UE does not support MTAs in the
uplink, uplink timing is performed on the UE based on
a single TAG in uplink CA scenarios. If this switch is
Off, MTAs are not supported in uplink CA scenarios,

eRAN TDD

nd
and uplink timing is performed on UEs based on a single

TAG. You are advised to set this switch to On in inter-
eNodeB CA scenarios and scenarios where RRUs are
installed remotely. RelaxedBackhaulCaSwitch:
Indicates whether to enable inter-eNodeB downlink CA
based on relaxed backhaul. Inter-eNodeB CA based on
relaxed backhaul is enabled only when this switch is On.
AdpCaSwitch: Indicates whether to allow adaptive
frequency-based CA configuration. If this switch is On,
in frequency-based configuration mode, the eNodeB
can configure SCells in a blind manner based on
preconfigured CA group information. If this switch is
Off, blind SCell configuration is not allowed in
frequency-based CA configuration mode.
CaHoControlSwitch: Indicates whether CA UEs can be
handed over to non-macro cells during unnecessary
intra-RAT handovers. If this switch is On, CA UEs
cannot be handed over to non-macro cells during
unnecessary intra-RAT handovers. If this switch is Off,
CA UEs can be handed over to non-macro cells during
unnecessary intra-RAT handovers. DistributeCloudbb-
CaSwitch: Indicates whether to enable CA based on
distributed Cloud BB. CA based on distributed Cloud
BB applies to cells served by the eNodeB only when
this switch is On. SccSmartCfgSwitch: Indicates
whether to enable smart SCC selection. The eNodeB
considers the load status indicators of candidate SCells
when configuring the SCell only when this switch is On.
IdleModePccAnchorSwitch: Indicates whether to
enable the anchor function of the primary component
carrier (PCC) for UEs in idle mode. If this option is
selected, this function is enabled. If this option is
deselected, this function is disabled. FreqPriBasedHo-
CaFiltSwitch: Indicates whether the eNodeB filters out
CA UEs when delivering measurement configuration
for frequency-priority-based handovers. CA UEs are
filtered out only if this option is selected.
GUI Value Range: PdcchOverlapSrchSpcSwitch
(PdcchOverlapSrchSpcSwitch), CaCapbFiltSwitch
(CaCapbFiltSwitch), PccAnchorSwitch
(PccAnchorSwitch), SccBlindCfgSwitch
(SccBlindCfgSwitch), FreqCfgSwitch
(FreqCfgSwitch), SccA2RmvSwitch
(SccA2RmvSwitch), CaTrafficTriggerSwitch
(CaTrafficTriggerSwitch), HoWithSccCfgSwitch
(HoWithSccCfgSwitch), SccModA6Switch

eRAN TDD

nd
(SccModA6Switch), GbrAmbrJudgeSwitch
(GbrAmbrJudgeSwitch), MtaAlgSwitch
(MtaAlgSwitch), RelaxedBackhaulCaSwitch
(RelaxedBackhaulCaSwitch), AdpCaSwitch
(AdpCaSwitch), CaHoControlSwitch(CaHoControlS-
witch), DistributeCloudbbCaSwitch(Distribute-
CloudbbCaSwitch), SccSmartCfgSwitch
(SccSmartCfgSwitch), IdleModePccAnchorSwitch
(IdleModePccAnchorSwitch), FreqPriBasedHoCa-
FiltSwitch(FreqPriBasedHoCaFiltSwitch)
Actual Value Range: PdcchOverlapSrchSpcSwitch,
CaCapbFiltSwitch, PccAnchorSwitch, SccBlindCfgS-
witch, FreqCfgSwitch, SccA2RmvSwitch,
CaTrafficTriggerSwitch, HoWithSccCfgSwitch,
SccModA6Switch, GbrAmbrJudgeSwitch,
MtaAlgSwitch, RelaxedBackhaulCaSwitch,
AdpCaSwitch, CaHoControlSwitch, Distribute-
CloudbbCaSwitch, SccSmartCfgSwitch,
IdleModePccAnchorSwitch, FreqPriBasedHoCaFiltS-
witch
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,
DistributeCloudbbCaSwitch:Off,
SccSmartCfgSwitch:Off,
IdleModePccAnchorSwitch:Off,
FreqPriBasedHoCaFiltSwitch:Off
Unit: None

eRAN TDD

nd
CaMgtC CellCaA MOD MRFD- FDD Meaning: Indicates whether to enable cell-level carrier
fg lgoSwitc CAMG 101231 and aggregation (CA). This parameter includes the
h TCFG MRFD- TDD following bits: CaDl3CCSwitch(CaDl3CCSwitch):
LST 101222 Carrier Indicates whether to enable aggregation of three
CAMG Aggrega component carriers in the downlink. This type of
TCFG tion aggregation works if this option is selected and at least
(TDD) two SccFreqCfg MOs or three CaGroupCell MOs are
FDD configured. CaUl2CCSwitch(CaUl2CCSwitch):
and Indicates whether to enable aggregation of two
TDD component carriers in the uplink. This type of
Carrier aggregation works if this option is selected and at least
Aggrega one SccFreqCfg MO or two CaGroupCell MOs are
tion configured. CaDl4CCSwitch(CaDl4CCSwitch):
(FDD) Indicates whether to enable aggregation of four
component carriers in the downlink. This type of
aggregation works if this option is selected and at least
three SccFreqCfg MOs or four CaGroupCell MOs are
configured. InterFddTddCaSwitch(InterFddTddCaS-
witch): Indicates whether to enable aggregation of TDD
and FDD component carriers. This type of aggregation
works if this option is selected. In a combination of FDD
and TDD cells for CA, either an FDD cell or a TDD cell
can act as the PCell. Tdd2CCDlCaEnhanceSwitch
(Tdd2CCDlCaEnhanceSwitch): Indicates whether to
enable enhanced DL ACK demodulation when two
TDD component carriers are aggregated. If this option
is selected, PUCCH format 3 is used. If this option is
deselected, PUCCH format 1b with channel selection is
used.
GUI Value Range: CaDl3CCSwitch(CaDl3CCSwitch),
CaUl2CCSwitch(CaUl2CCSwitch), CaDl4CCSwitch
(CaDl4CCSwitch), InterFddTddCaSwitch
(InterFddTddCaSwitch), Tdd2CCDlCaEnhanceSwitch
(Tdd2CCDlCaEnhanceSwitch)
Actual Value Range: CaDl3CCSwitch,
CaUl2CCSwitch, CaDl4CCSwitch, InterFddTddCaS-
witch, Tdd2CCDlCaEnhanceSwitch
Default Value: CaDl3CCSwitch:Off,
CaUl2CCSwitch:Off, CaDl4CCSwitch:Off,
InterFddTddCaSwitch:Off,
Tdd2CCDlCaEnhanceSwitch :Off
Unit: None

eRAN TDD

nd
ENodeB FddFra MOD MRFD- FDD Meaning: Indicates the offset of the start time of a cell
FrameO meOffse ENODE 101231 and frame against a reference clock source. This offset
ffset t BFRAM MRFD- TDD applies to all LTE FDD cells served by an eNodeB.
EOFFS 101222 Carrier GUI Value Range: 0~261120,275943~307200
ET Aggrega
tion Actual Value Range: 0~261120,275943~307200
LST
ENODE (TDD) Default Value: 0
BFRAM FDD Unit: Ts
EOFFS and
ET TDD
Carrier
Aggrega
tion
(FDD)

eRAN TDD

nd
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 Actual Value Range: 0~261120,275943~307200
LST 701
ENODE configur Default Value: 0
TDLBF ation
BFRAM D-00100 Unit: Ts
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

eRAN TDD

nd
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
FDD
and
TDD
Carrier
Aggrega
tion
(TDD)
FDD
and
TDD
Carrier
Aggrega
tion
(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 Actual Value Range: 0~255
LST Default Value: None

CELLF Unit: None
RAME
OFFSE
T
MOD
CELLF
RAME
OFFSE
T
RMV
CELLF
RAME
OFFSE
T

eRAN TDD

nd
CellFra FrameO ADD None None Meaning: Indicates a cell frame offset mode.
meOffse ffsetMo CELLF CustomFrameOffset(Cell Frame Offset): Indicates that
t de RAME the cell frame offset is user defined. An FDD cell can
OFFSE use only this mode. TL_FrameOffset(T-L Dual Mode
T frame offset): Indicates that the cell frame offset is
MOD automatically configured based on the subframe
CELLF configuration type in a TD-SCDMA_TD-LTE network.
RAME TL_FrameOffset_SA2_SSP5(T-L Dual Mode SA2
OFFSE +SSP5 frame offset): Indicates that the cell frame offset
T is automatically configured based on subframe
configuration type 2 and special subframe configuration
LST type 5 in a TD-SCDMA_TD-LTE network.
CELLF
RAME GUI Value Range: CustomFrameOffset(User-defined
OFFSE frame offset), TL_FrameOffset(T-L Dual Mode frame
T offset), TL_FrameOffset_SA2_SSP5(T-L Dual Mode
SA2+SSP5 frame offset)
Actual Value Range: CustomFrameOffset,
TL_FrameOffset, TL_FrameOffset_SA2_SSP5
Default Value: CustomFrameOffset(User-defined
frame offset)
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 Actual Value Range: 0~261120,275943~307200
MOD Default Value: 0

CELLF Unit: Ts
RAME
OFFSE
T
LST
CELLF
RAME
OFFSE
T

eRAN TDD

nd
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), FDDTDD
d UP 01 Carrier (FDDTDD)
MOD LAOFD Aggrega
tion for Actual Value Range: FDD, TDD, FDDTDD
CAGRO -001001
UP 02 Downlin Default Value: FDD(FDD)
k 2CC Unit: None
LST LAOFD
CAGRO -001002 Inter-
UP 01 Band
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
TDLAO 40MHz
FD-001 Support
004 of UE
Categor
y6
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Multi-
SA
Carrier
Aggrega
tion for
Downlin
k 2CC

eRAN TDD

nd
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 PCC
LST LAOFD Aggrega has reached the parameter value, no more CA UEs can
CAMG -001001 tion for use the carrier as the PCC. A smaller parameter value
TCFG 02 Downlin leads to fewer CA UEs that are allowed to use the cell's
k 2CC in carrier as the PCC. If this parameter is set to 0, no CA
LAOFD 20MHz UE is allowed to use the cell's carrier as the PCC but CA
-001002 UEs can use the carrier as the SCC. If the total value of
01 Inter-
Band this parameter for all cells on a baseband processing unit
LAOFD exceeds the upper limit of such UEs served by the unit,
Carrier
-001002 the limit takes effect.
Aggrega
02 GUI Value Range: 0~65535
tion for
LAOFD Downlin Actual Value Range: 0~65535
-070201 k 2CC in
Default Value: 65535
LAOFD 20MHz
-070202 Unit: None
Carrier
LAOFD Aggrega
-080201 tion for
Downlin
LAOFD
k 2CC in
-080202
40MHz
LAOFD
-080207 Support
of UE
LAOFD Categor
-080208 y6
TDLAO CA for
FD-001 Downlin
00111 k 2CC
TDLAO From
FD-001 Multiple
002 Carriers
TDLAO Carrier
FD-070 Aggrega
201 tion for
2CC
based on
Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier

eRAN TDD

nd
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
CA for
Downlin
k 2CC
from
Multiple
Carriers

eRAN TDD

nd
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 AMBR
LST LAOFD Aggrega values are greater than the threshold. A larger value of
CAMG -001001 tion for this parameter leads to fewer UEs for whom the carriers
TCFG 02 Downlin can be aggregated.
k 2CC in GUI Value Range: 0~65535
LAOFD 20MHz
-001002 Actual Value Range: 0~65535
01 Inter-
Default Value: 0
Band
LAOFD Unit: Mbps
Carrier
-001001
Aggrega
02
tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
LAOFD Aggrega
-080201 tion for
Downlin
LAOFD
k 2CC in
-080202
40MHz
LAOFD
-080207 Support
of UE
LAOFD Categor
-080208 y6
TDLAO CA for
FD-001 Downlin
00111 k 2CC
TDLAO From
FD-001 Multiple
002 Carriers
TDLAO Carrier
FD-070 Aggrega
201 tion for
2CC
based on
Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier

eRAN TDD

nd
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
CA for
Downlin
k 2CC
from
Multiple
Carriers

eRAN TDD

nd
ENodeB CaLbAl MOD TDLOF CA UE Meaning: Indicates whether to enable or disable load
AlgoSwi goSwitc ENODE D-08121 Load balancing algorithms in CA scenarios, The
tch h BALGO 9 Balancin DlCaLbAlgoSwitch check box under this parameter
SWITC g controls load adjustment among different carriers after
H the load balancing algorithm is enabled in downlink CA
LST scenarios. This parameter applies only to LTE TDD
ENODE cells. If the DlCaLbAlgoSwitch check box is on, the
BALGO load balancing algorithm is enabled in downlink CA
SWITC scenarios. If the DlCaLbAlgoSwitch check box is off,
H the load balancing algorithm is disabled in downlink CA
scenarios.
GUI Value Range: DlCaLbAlgoSwitch(DlCaLbAlgoS-
witch)
Actual Value Range: DlCaLbAlgoSwitch
Default Value: DlCaLbAlgoSwitch:Off
Unit: None
eNodeB DlCaLb MOD TDLOF CA UE Meaning: Indicates the maximum number of carriers
Mlb MaxCC ENODE D-08121 Load aggregated for a CA UE whose load is to be transferred
Num BMLB 9 Balancin for load balancing. If this parameter is set to 2CC, load
LST g of CA UEs using two component carriers (CCs) can be
ENODE transferred for load balancing. If this parameter is set to
BMLB 3CC, load of CA UEs using two CCs and three CCs can
be transferred for load balancing. This parameter
applies only to LTE TDD cells.
GUI Value Range: 3CC(3CC), 2CC(2CC)
Actual Value Range: 3CC, 2CC
Default Value: 3CC(3CC)
Unit: None
eNodeB CaUeMi MOD TDLOF CA UE Meaning: Indicates the minimum data volume ratio
Mlb nDataV ENODE D-08121 Load between two CCs of a CA UE whose load is to be
olRatio BMLB 9 Balancin transferred. For example, if this parameter is set to 20,
LST g the minimum ratio of the data volume on a heavily
ENODE loaded CC to that on a lightly loaded CC is 1/5. If this
BMLB parameter is set to 0, the minimum ratio of the data
volume on a heavily loaded CC to that on a lightly
loaded CC is 0/1, that is, all data on the heavily loaded
CC can be transferred to the lightly loaded CC. This
parameter applies only to LTE TDD cells.
GUI Value Range: 0~99
Actual Value Range: 0~99
Default Value: 0
Unit: None

eRAN TDD

nd
PrivateC PrivateC ADD LAOFD Intra- Meaning: Indicates the ID of the private CA band
aBandC aCombI PRIVA -001001 Band combination. It uniquely identifies a private CA band
omb d TECAB 01 Carrier combination in an eNodeB.
ANDCO LAOFD Aggrega GUI Value Range: 0~31
MB -001001 tion for
Downlin Actual Value Range: 0~31
DSP 02
PRIVA k 2CC in Default Value: None
LAOFD 20MHz
TECAB -001002 Unit: None
ANDCO 01 / Inter-
MB TDLAO Band
LST FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
MOD TDLAO
PRIVA FD-001 Carrier
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
RMV /
40MHz
PRIVA TDLAO
TECAB FD-070 Support
ANDCO 201 of UE
MB Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
PrivateC MaxAgg ADD LAOFD Intra- Meaning: Indicates the maximum aggregated
aBandC regated PRIVA -001001 Band bandwidth supported by the CA band combination.
omb Bw TECAB 01 Carrier GUI Value Range: 20~300
ANDCO LAOFD Aggrega
MB tion for Actual Value Range: 20~300
-001001
MOD 02 Downlin Default Value: None
PRIVA k 2CC in Unit: MHz
LAOFD 20MHz
TECAB -001002
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
PrivateC BwCom ADD LAOFD Intra- Meaning: Indicates the protocol-defined ID of a CA

aBandC bSetId PRIVA -001001 Band bandwidth combination set. As defined in 3GPP TS
omb TECAB 01 Carrier 36.101, an operating frequency band supports different
ANDCO LAOFD Aggrega bandwidth combinations, which are identified by using
MB -001001 tion for different set IDs. For details, see section 5.6A.1 in 3GPP
MOD 02 Downlin TS 36.301.
PRIVA k 2CC in GUI Value Range: 0~31
LAOFD 20MHz
TECAB -001002 Actual Value Range: 0~31
ANDCO 01 / Inter-
MB Default Value: None
TDLAO Band
DSP FD-001 Carrier Unit: None
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates combination band 1. For details, see
aBandC nd1Id PRIVA -001001 Band 3GPP TS 36.101.
omb TECAB 01 Carrier GUI Value Range: 1~256
ANDCO LAOFD Aggrega
-001001
MOD 02 Downlin Default Value: 1
PRIVA k 2CC in Unit: None
LAOFD 20MHz
TECAB -001002
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
aBandC nd2Id PRIVA -001001 Band 3GPP TS 36.101.
omb TECAB 01 Carrier GUI Value Range: 1~256
ANDCO LAOFD Aggrega
-001001
MOD 02 Downlin Default Value: 1
PRIVA k 2CC in Unit: None
LAOFD 20MHz
TECAB -001002
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
aBandC nd3Id PRIVA -001001 Band 3GPP TS 36.101. If the value is 0, combination band 3
omb TECAB 01 Carrier is invalid.
MB -001001 tion for
MOD 02
PRIVA k 2CC in Default Value: 0
LAOFD 20MHz
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
aBandC nd4Id PRIVA -001001 Band 3GPP TS 36.101. If the value is 0, combination band 4
omb TECAB 01 Carrier is invalid.
MB -001001 tion for
MOD 02
PRIVA k 2CC in Default Value: 0
LAOFD 20MHz
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD
ANDCO Downlin
-001002
MB k 2CC in
02 /
20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
PrivateC CombBa ADD LAOFD Intra- Meaning: Indicates the bandwidth combination of
aBandC nd1Bw PRIVA -001001 Band combination band 1. If a bandwidth is selected, the
omb TECAB 01 Carrier carrier with the corresponding bandwidth in
ANDCO LAOFD Aggrega combination band 1 is supported in the private CA
MB -001001 tion for combination band.
MOD 02 Downlin GUI Value Range: Bandwidth_1_4M(1.4M),
PRIVA k 2CC in Bandwidth_3M(3M), Bandwidth_5M(5M),
LAOFD 20MHz
TECAB -001002 Bandwidth_10M(10M), Bandwidth_15M(15M),
ANDCO 01 / Inter- Bandwidth_20M(20M)
MB TDLAO Band Actual Value Range: Bandwidth_1_4M,
DSP FD-001 Carrier Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVA 002 Aggrega Bandwidth_15M, Bandwidth_20M
TECAB tion for
LAOFD Default Value: Bandwidth_1_4M:Off,
ANDCO Downlin
-001002 Bandwidth_3M:Off, Bandwidth_5M:Off,
MB k 2CC in
02 / Bandwidth_10M:Off, Bandwidth_15M:Off,
20MHz
LST TDLAO Bandwidth_20M:Off
Unit: None
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
LAOFD 20MHz
TECAB tion for
ANDCO Downlin
MB k 2CC in
20MHz
Unit: None
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
LAOFD 20MHz
TECAB tion for
ANDCO Downlin
MB k 2CC in
20MHz
Unit: None
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
LAOFD 20MHz
TECAB tion for
ANDCO Downlin
MB k 2CC in
20MHz
Unit: None
TECAB 00202 Aggrega
ANDCO tion for
LAOFD
MB Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
CaGrou Preferre ADD LAOFD Intra- Meaning: Indicates the priority of the cell being treated
pCell dPCellP CAGRO -001001 Band as a primary serving cell (PCell). A larger parameter
riority UPCEL 01 Carrier value represents a higher priority level. This parameter
L LAOFD Aggrega takes effect only when PccAnchorSwitch of the
MOD -001001 tion for CaAlgoSwitch parameter is on.
CAGRO 02 Downlin GUI Value Range: 0~7
UPCEL k 2CC in
LAOFD 20MHz Actual Value Range: 0~7
L -001002 Default Value: 0
LST 01 / Inter-
CAGRO TDLAO Band Unit: None
UPCEL FD-001 Carrier
L 002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
IntraRat InterFre MOD LBFD-0 Coverag Meaning: Indicates the triggering quantity for event A4
HoCom qHoA4T INTRA 0201802 e Based and event A5 measurement reports of non-coverage-
m rigQuan RATHO / Inter- based inter-frequency handovers.
COMM TDLBF frequenc GUI Value Range: RSRP, RSRQ, BOTH
LST D-00201 y
802 Handov Actual Value Range: RSRP, RSRQ, BOTH
INTRA
RATHO LOFD-0 er Default Value: RSRP
COMM 0109804 Carrier Unit: None
/ Manage
TDLAO ment
FD-001
00306

eRAN TDD

nd
CaGrou PCellA4 ADD LAOFD Intra- Meaning: Indicates the reference signal received power
pCell RsrpThd CAGRO -001001 Band (RSRP) threshold for triggering event A4 during higher-
UPCEL 01 Carrier priority cell evaluation for PCell selection in scenarios
L LAOFD Aggrega where CA is configured based on CA groups.
MOD -001001 tion for GUI Value Range: -140~-43
CAGRO 02 Downlin
k 2CC in Actual Value Range: -140~-43
UPCEL LAOFD
L 20MHz Default Value: -105
-001002
LST 01 / Inter- Unit: dBm
CAGRO TDLAO Band
L 002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
CaGrou PCellA4 ADD LAOFD Intra- Meaning: Indicates the reference signal received quality
pCell RsrqThd CAGRO -001001 Band (RSRQ) threshold for triggering event A4 during
UPCEL 01 Carrier higher-priority cell evaluation for PCell selection in
L LAOFD Aggrega scenarios where CA is configured based on CA groups.
MOD -001001 tion for If the measured RSRQ of an inter-frequency
CAGRO 02 Downlin neighboring cell in the CA group is greater than this
UPCEL k 2CC in parameter value, the CA UE reports event A4.
LAOFD 20MHz
L -001002 GUI Value Range: -40~-6
LST 01 / Inter- Actual Value Range: -20~-3
CAGRO TDLAO Band
Default Value: -20
L 002 Aggrega Unit: 0.5dB
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
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 level
ority EQCFG 01 Carrier has a positive correlation with the parameter value. This
MOD LAOFD Aggrega parameter is valid only if IdleModePccAnchorSwitch
PCCFR -001001 tion for or PccAnchorSwitch of the CaAlgoSwitch parameter is
EQCFG 02 Downlin set to 1.
k 2CC in GUI Value Range: 0~7
LST LAOFD 20MHz
PCCFR -001002 Actual Value Range: 0~7
EQCFG 01 Inter-
Band Default Value: 0
LAOFD Carrier Unit: None
-001002 Aggrega
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 Actual Value Range: 0~46589,54436~65535
ELLLIS 02
T k 2CC in Default Value: None
LAOFD 20MHz
LST -001002 Unit: None
PCCFR 01 Inter-
EQCFG Band
LAOFD Carrier
MOD -001002 Aggrega
PCCFR 02 tion for
EQCFG LAOFD Downlin
RMV -070201 k 2CC in
PCCFR LAOFD 20MHz
EQCFG -070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
PccFreq PccA4R ADD LAOFD Intra- Meaning: Indicates the reference signal received power
Cfg srpThd PCCFR -001001 Band (RSRP) threshold for triggering event A4 during higher-
EQCFG 01 Carrier priority carrier evaluation for PCC selection.
MOD LAOFD Aggrega GUI Value Range: -140~-43
PCCFR -001001 tion for
Downlin Actual Value Range: -140~-43
EQCFG 02
k 2CC in Default Value: -105
LST LAOFD 20MHz
PCCFR -001002 Unit: dBm
EQCFG 01 Inter-
Band
LAOFD Carrier
-001002 Aggrega
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
PccFreq PccA4R ADD LAOFD Intra- Meaning: Indicates the reference signal received quality
Cfg srqThd PCCFR -001001 Band (RSRQ) threshold for triggering event A4 during
EQCFG 01 Carrier higher-priority carrier evaluation for PCC selection in
MOD LAOFD Aggrega scenarios where CA is configured based on frequencies.
PCCFR -001001 tion for If the measured RSRQ of an inter-frequency
EQCFG 02 Downlin neighboring cell in the CA group is greater than this
k 2CC in parameter value, the CA UE reports event A4.
LST LAOFD 20MHz
PCCFR -001002 GUI Value Range: -40~-6
EQCFG 01 Inter- Actual Value Range: -20~-3
Band
LAOFD Carrier Default Value: -20
-001002 Aggrega Unit: 0.5dB
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 that
CAGRO 02 Downlin this cell cannot be configured as an SCell for CA UEs.
UPSCE k 2CC in GUI Value Range: 0~7
LAOFD 20MHz
LLCFG -001002 Actual Value Range: 0~7
LST 01 / Inter-
Default Value: 1
CAGRO TDLAO Band
UPSCE FD-001 Carrier Unit: None
LLCFG 002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
CaGrou SCellBli ADD LAOFD Intra- Meaning: Indicates whether this candidate secondary
pSCellC ndCfgFl CAGRO -001001 Band serving cell (SCell) can be configured as an SCell for
fg ag UPSCE 01 Carrier carrier aggregation (CA) UEs in a blind manner. This
LLCFG LAOFD Aggrega parameter is valid only when SccBlindCfgSwitch
MOD -001001 tion for option in the CaAlgoSwitch parameter is set to ON. If
CAGRO 02 Downlin this parameter is set to TRUE(TRUE), the eNodeB can
UPSCE k 2CC in configure this candidate SCell as an SCell for CA UEs
LAOFD 20MHz in a blind manner, without delivering A4-related
LLCFG -001002
Inter- measurement configurations to CA UEs. If this
LST 01 / parameter is set to FALSE(FALSE), the eNodeB cannot
CAGRO TDLAO Band
Carrier configure this candidate SCell as an SCell for CA UEs.
UPSCE FD-001 When the eNodeB configures an SCell for CA UEs, the
LLCFG 002 Aggrega
tion for eNodeB need to deliver A4-related measurement
LAOFD configurations on the frequency on which the SCell
Downlin
-001002 operates.
k 2CC in
02 / GUI Value Range: FALSE(FALSE), TRUE(TRUE)
20MHz
TDLAO
FD-001 Carrier Actual Value Range: FALSE, TRUE
00102 Aggrega Default Value: FALSE(FALSE)
tion for
LAOFD Unit: None
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
ENodeB HoMode MOD LOFD-0 SRVCC Meaning: Indicates whether to enable or disable
AlgoSwi Switch ENODE 01022 / to different types of handovers, based on which the
tch BALGO TDLOF UTRAN eNodeB determines handover policies.
SWITC D-00102 SRVCC UtranVoipCapSwitch: If this switch is on, UTRAN
H 2 to supports VoIP. If this switch is off, UTRAN does not
LST LOFD-0 GERAN support VoIP. Cdma1xRttVoipCapSwitch: If this
ENODE 01023 / switch is on, CDMA2000 1xRTT supports VoIP. If this
CS
BALGO TDLOF switch is off, CDMA2000 1xRTT does not support
Fallback
SWITC D-00102 VoIP. UtranPsHoSwitch: If this switch is on, UTRAN
to
H 3 supports PS handovers. If this switch is off, UTRAN
UTRAN
does not support PS handovers. GeranPsHoSwitch: If
LOFD-0 CS this switch is on, GERAN supports PS handovers. If this
01033 / Fallback switch is off, GERAN does not support PS handovers.
TDLOF to CdmaHrpdNonOptimisedHoSwitch: If this switch is
D-00103 GERAN on, non-optimized handovers to CDMA2000 HRPD are
3 PS Inter- enabled. If this switch is off, non-optimized handovers
LOFD-0 RAT to CDMA2000 HRPD are disabled. CdmaHrpdOptimi-
01034 / Mobility sedHoSwitch: If this switch is turned on, optimized
TDLOF between handovers to CDMA2000 HRPD are enabled. If this
D-00103 E- switch is off, optimized handovers to CDMA2000
4 UTRAN HRPD are disabled. GeranNaccSwitch: This switch
and does not take effect if GeranCcoSwitch is off. If this
LOFD-0
UTRAN switch is on, the GERAN supports network assisted cell
01019 /
PS Inter- change (NACC). If this switch is off, the GERAN does
TDLOF
RAT not support NACC. GeranCcoSwitch: If this switch is
D-00101
Mobility on, the GERAN supports cell change order (CCO). If
9
between this switch is off, the GERAN does not support CCO.
LOFD-0 UtranSrvccSwitch: If this switch is on, the UTRAN
E-
01020 / supports SRVCC. If this switch is off, the UTRAN does
UTRAN
TDLOF not support SRVCC. GeranSrvccSwitch: If this switch
and
D-00102 is on, the GERAN supports SRVCC. If this switch is
GERAN
0 off, the GERAN does not support SRVCC.
PS Inter- Cdma1xRttSrvccSwitch: If this switch is on, the
LOFD-0
RAT CDMA2000 1xRTT supports SRVCC. If this switch is
01021 /
Mobility off, the CDMA2000 1xRTT does not support SRVCC.
TDLOF
between UtranRedirectSwitch: If this switch is on, redirection to
D-00102
E- UTRAN is enabled. If this switch is turned off,
1
UTRAN redirection to UTRAN is disabled. GeranRedirectS-
TDLOF and witch: If this switch is on, redirection to GERAN is
D-00105 CDMA2 enabled. If this switch is off, redirection to GERAN is
2 000 disabled. CdmaHrpdRedirectSwitch: If this switch is
TDLOF Flash CS on, redirection to CDMA2000 HRPD is enabled. If this
D-00108 Fallback switch is off, redirection to CDMA2000 HRPD is
8 to disabled. Cdma1xRttRedirectSwitch: If this switch is
TDLOF UTRAN on, redirection to CDMA2000 1xRTT is enabled. If this
D-00104 CS switch is off, redirection to CDMA2000 1xRTT is
3 Fallback disabled. BlindHoSwitch: If this switch is on, blind

eRAN TDD

nd
TDLOF Steering handovers for CSFB are enabled. If this switch is off,
D-00107 to blind handovers for CSFB are disabled. If both this
2 UTRAN option and the BlindHoSwitch option of the Handover
TDLOF Service Mode switch parameter of the CellHoParaCfg MO are
D-00104 based selected, blind CSFB handovers for CSFB are enabled.
6 Inter- LcsSrvccSwitch: If this switch is on, an SRVCC
RAT procedure is triggered when a UE receives a CSFB
TDLOF instruction during a VoIP service. If this switch is off,
D-00107 handove
r to an SRVCC procedure is not triggered when a UE
3 receives a CSFB instruction during a VoIP service.
UTRAN
AutoGapSwitch: If this switch is on and UEs support
Distance automatic measurement gap configurations on the target
based frequency, the eNodeB does not deliver gap
Inter- configurations to UEs. If this switch is off, the eNodeB
RAT delivers gap configurations to UEs during all inter-
handove frequency and inter-RAT measurements.
r to UeVoipOnHspaCapSwitch: If this switch is on and the
UTRAN eNodeB attempts to hand over UEs using voice services
Service to UTRAN, the eNodeB checks UE capabilities when
based determining whether PS handover is applied. UEs must
Inter- support voiceOverPS-HS-UTRA-FDD-r9 if the target
RAT UTRAN cell works in FDD mode or voiceOverPS-HS-
handove UTRA-TDD128-r9 if the target UTRAN cell works in
r to TDD mode. If this switch is off, the eNodeB does not
GERAN check UE capabilities when handing over UEs to
Distance UTRAN based on PS handovers. UtranFddB1Cap-
based Switch: If this switch is on, the setting of bit 41 of FGI
Inter- specifying the UE capability of event B1 measurement
RAT on FDD UTRAN cells must be considered. If this switch
handove is off, the setting of bit 41 of FGI does not need to be
r to considered. CdmaHrpdNonOptMeaHoSwitch: If this
GERAN switch is on, measurement-based non-optimized
handovers to CDMA2000 HRPD are enabled. If this
switch is off, measurement-based non-optimized
handovers to CDMA2000 HRPD are disabled.
GUI Value Range: EutranVoipCapSwitch
(EutranVoipCapSwitch), UtranVoipCapSwitch
(UtranVoipCapSwitch), GeranVoipCapSwitch
(GeranVoipCapSwitch), Cdma1xRttVoipCapSwitch
(Cdma1xRttVoipCapSwitch), UtranPsHoSwitch
(UtranPsHoSwitch), GeranPsHoSwitch
(GeranPsHoSwitch), CdmaHrpdNonOptimisedHoS-
witch(CdmaHrpdNonOptimisedHoSwitch),
CdmaHrpdOptimisedHoSwitch(CdmaHrpdOptimised-
HoSwitch), GeranNaccSwitch(GeranNaccSwitch),
GeranCcoSwitch(GeranCcoSwitch),

eRAN TDD

nd
UtranSrvccSwitch(UtranSrvccSwitch),
GeranSrvccSwitch(GeranSrvccSwitch),
Cdma1xRttSrvccSwitch(Cdma1xRttSrvccSwitch),
UtranRedirectSwitch(UtranRedirectSwitch),
GeranRedirectSwitch(GeranRedirectSwitch),
CdmaHrpdRedirectSwitch(CdmaHrpdRedirectS-
witch), Cdma1xRttRedirectSwitch(Cdma1xRttRedir-
ectSwitch), BlindHoSwitch(BlindHoSwitch),
LcsSrvccSwitch(LcsSrvccSwitch), AutoGapSwitch
(AutoGapSwitch), UeVoipOnHspaCapSwitch
(UeVoipOnHspaCapSwitch), UtranFddB1CapSwitch
(UtranFddB1CapSwitch), CdmaHrpdNonOptMea-
HoSwitch(CdmaHrpdNonOptMeaHoSwitch)
Actual Value Range: EutranVoipCapSwitch,
UtranVoipCapSwitch, GeranVoipCapSwitch,
Cdma1xRttVoipCapSwitch, UtranPsHoSwitch,
GeranPsHoSwitch, CdmaHrpdNonOptimisedHoS-
witch, CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
UtranSrvccSwitch, GeranSrvccSwitch,
Cdma1xRttSrvccSwitch, UtranRedirectSwitch,
GeranRedirectSwitch, CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch, BlindHoSwitch,
LcsSrvccSwitch, AutoGapSwitch, UeVoipOnHspa-
CapSwitch, 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,
CdmaHrpdNonOptMeaHoSwitch:Off
Unit: None

eRAN TDD

nd
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 of
Rsrp TCFG 01 Carrier a secondary cell. When the RSRP of the UE is greater
LST LAOFD Aggrega than the threshold, event A4 is reported.
CAMG -001001 tion for GUI Value Range: -140~-43
TCFG 02 Downlin
LAOFD 20MHz Default Value: -105
-001002
01 / Inter- Unit: dBm
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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 pertaining
MOD -001001 tion for to the candidate SCell specified by the SCelleNodeBId
CAGRO 02 Downlin and SCellLocalCellId parameters to the eNodeB if the
UPSCE k 2CC in RSRP for the candidate SCell exceeds the sum of the
LAOFD 20MHz CarrAggrA4ThdRsrp and SCellA4Offset parameter
LLCFG -001002
Inter- values. If the sum is greater than –43 dBm or less than
LST 01 / –140 dBm, the threshold for event A4 takes the value –
CAGRO TDLAO Band
Carrier 43 dBm or –140 dBm, respectively.
UPSCE FD-001
LLCFG 002 Aggrega GUI Value Range: -35~62
tion for Actual Value Range: -35~62
LAOFD
Downlin
-001002 Default Value: 0
k 2CC in
02 / Unit: dBm
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
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 smaller
EQCFG 01 Carrier value of this parameter indicates a lower priority, and a
MOD LAOFD Aggrega larger value indicates a higher priority.
SCCFR -001001 tion for GUI Value Range: 1~7
EQCFG 02 Downlin
k 2CC in Actual Value Range: 1~7
LST LAOFD 20MHz Default Value: 1
SCCFR -001002
EQCFG 01 Inter- Unit: None
Band
LAOFD Carrier
-001002 Aggrega
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 in eNodeB makes the attempt only if the traffic volume of
LAOFD 20MHz the UE always meets the SCell activation condition
-001002 throughout a certain time.
01 Inter-
Band GUI Value Range: 5~60
LAOFD
Carrier Actual Value Range: 5~60
-001001
Aggrega
02 Default Value: 60
tion for
LAOFD Downlin Unit: s
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
TDLAO Aggrega
FD-001 tion for
00111 Downlin
k 2CC in
TDLAO
40MHz
FD-001
002 Support
TDLAO of UE
FD-001 Categor
00102 y6
TDLAO CA for
FD-070 Downlin
201 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
for UE
Categor
y6
CA for
Downlin
k 2CC
from
Multiple
Carriers

eRAN TDD

nd
SccFreq SccA4O ADD LAOFD Intra- Meaning: Indicates the offset of the actual threshold for
Cfg ffset SCCFR -001001 Band CA event A4 relative to the value of the
EQCFG 01 Carrier CarrAggrA4ThdRsrp parameter in the CaMgtCfg MO.
MOD LAOFD Aggrega If the actual threshold is greater than -43 dBm, the value
SCCFR -001001 tion for of -43 dBm takes effect. If the actual threshold is less
EQCFG 02 Downlin than -140 dBm, the value of -140 dBm takes effect.
k 2CC in GUI Value Range: -35~62
LST LAOFD 20MHz
SCCFR -001002 Actual Value Range: -35~62
EQCFG 01 Inter-
LAOFD Carrier Unit: dBm
-001002 Aggrega
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
CellML MlbTrig MOD LOFD-0 Intra- Meaning: Indicates the variable that triggers a mobility
B gerMod CELLM 70215 / LTE load balancing (MLB) procedure. In MLB with load
e LB TDLOF User information exchange, If this parameter is set to
LST D-07021 Number PRB_ONLY(PrbMode), PRB usage is used as a
CELLM 5 Load triggering variable and the number of UEs is used as a
LB Balancin supplementary triggering variable; PRB usage
g difference between cells is used as a UE transfer
condition; the aim of MLB is to achieve the same
number of remaining PRBs between cells. If this
parameter is set to UE_NUMBER_ONLY
(UeNumMode), the number of UEs is used as a
triggering variable; the difference of the number of UEs
per unit of bandwidth between cells is used as a UE
transfer condition; the aim of MLB is to achieve the
same number of UEs per unit of bandwidth between
cells. If this parameter is set to
PRB_OR_UE_NUMBER(PrbOrUeNumMode), the
combination of the triggering variables, UE transfer
conditions, and MLB aims for the values
UE_NUMBER_ONLY(UeNumMode) and
PRB_ONLY(PrbMode) are used. In MLB without load
information exchange, If this parameter is set to
PRB_ONLY(PrbMode), PRB usage is used as a
triggering variable and a UE transfer condition and the
number of UEs is used as a supplementary triggering
variable and a supplementary UE transfer condition; the
aim of MLB is to achieve that the PRB usage is less than
the InterFreqMlbThd parameter value. If this parameter
is set to UE_NUMBER_ONLY(UeNumMode), the
number of UEs is used as a triggering variable and a UE
transfer condition; the aim of MLB is to achieve that the
number of UEs is less than the InterFreqMlbUe-
NumThd parameter value. If this parameter is set to
PRB_OR_UE_NUMBER(PrbOrUeNumMode), the
combination of the triggering variables, UE transfer
conditions, and MLB aims for the values
UE_NUMBER_ONLY(UeNumMode) and
PRB_ONLY(PrbMode) are used.
GUI Value Range: PRB_ONLY(PrbMode),
UE_NUMBER_ONLY(UeNumMode),
PRB_OR_UE_NUMBER(PrbOrUeNumMode)
Actual Value Range: PRB_ONLY,
UE_NUMBER_ONLY, PRB_OR_UE_NUMBER
Default Value: PRB_ONLY(PrbMode)
Unit: None

eRAN TDD

nd
CellML PrbLoad MOD TDLOF Intra- Meaning: Indicates the PRB load calculation method
B CalcMet CELLM D-00103 LTE when the Mobility Load Balancing Trigger Mode
hod LB 2 Load parameter is set to PRB_ONLY or
LST Balancin PRB_OR_UE_NUMBER. The parameter value
CELLM g PRB_USAGE indicates that the PRB load is calculated
LB based on the PRB usage. The parameter value
PRB_VALUATION_WITH_CTRL indicates that the
PRB load is calculated based on the PRB evaluation for
traffic channels and control channels. The parameter
value PRB_VALUATION_NO_CTRL indicates that
the PRB load is calculated based on the PRB evaluation
only for traffic channels. If this parameter is set to
PRB_USAGE, the PRB usage of multiple cells is more
likely to reach the maximum. If this parameter is set to
PRB_VALUATION_WITH_CTRL or
PRB_VALUATION_NO_CTRL, the transmission rate
of each service is more likely to reach the minimum. Set
this parameter based on requirements. This parameter
applies only to LTE TDD cells.
GUI Value Range: PRB_USAGE(PRB_USAGE),
PRB_VALUATION_WITH_CTRL
(PRB_VALUATION_WITH_CTRL),
PRB_VALUATION_NO_CTRL
(PRB_VALUATION_NO_CTRL)
Actual Value Range: PRB_USAGE,
PRB_VALUATION_WITH_CTRL,
PRB_VALUATION_NO_CTRL
Default Value: PRB_USAGE(PRB_USAGE)
Unit: None

eRAN TDD

nd
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 PRB_ONLY
LST D-00103 Balancin (PrbMode) or PRB_OR_UE_NUMBER
CELLM 2 g (PrbOrUeNumMode), inter-frequency load balancing is
LB 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.
Default Value: 60
Unit: %

eRAN TDD

nd
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 to
CELLM 2 g 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 InterRATIdleMlbUe-
NumThd and InterRatMlbUeNumOffset parameter
values and the PRB usage of the cell is greater than or
equal to the sum of the InterRatMlbThd and LoadOffset
parameter values.
Default Value: 8
Unit: %

eRAN TDD

nd
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 PRB_ONLY
LB LOFD-0 Operator (PrbMode) or PRB_OR_UE_NUMBER
70204 Load (PrbOrUeNumMode). If the PRB usage in the source
Based cell is greater than or equal to the sum of the
Intra- InterFreqMlbThd parameter value and the
LTE InterFreqOffloadOffset parameter value, neighboring
MLB 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.
Default Value: 0
Unit: %
CellML MlbMin MOD LOFD-0 Intra- Meaning: Indicates the threshold of the minimum
B UeNum CELLM 01032 / LTE number of synchronized UEs for triggering inter-
Thd LB TDLOF Load frequency load balancing. When the MlbTriggerMode
LST D-00103 Balancin parameter is set to PRB_ONLY(PrbMode) or
CELLM 2 g PRB_OR_UE_NUMBER(PrbOrUeNumMode), load
LB balancing is triggered if the PRB usage of the cell is
greater than or equal to the sum of InterFreqMlbThd and
LoadOffset parameter values and the number of
synchronized UEs in the cell is greater than or equal to
the sum of the MlbMinUeNumThd and
MlbMinUeNumOffset 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.
Default Value: 0
Unit: None

eRAN TDD

nd
CellML MlbMin MOD LOFD-0 Intra- Meaning: Indicates the offset of the minimum number
B UeNum CELLM 01032 / LTE of synchronized UEs for triggering inter-frequency load
Offset LB TDLOF Load balancing. If the MlbTriggerMode parameter is set to
LST D-00103 Balancin PRB_ONLY(PrbMode) or PRB_OR_UE_NUMBER
CELLM 2 g (PrbOrUeNumMode), inter-frequency load balancing is
LB 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 the InterFreqMlbThd and
LoadOffset parameter values.
Default Value: 0
Unit: None
CellPrb PrbVal MOD TDLOF Intra- Meaning: Indicates the threshold for allowing inter-
ValMlb MlbAd CELLP D-00103 LTE frequency MLB based on the PRB evaluation value in
mitThd RBVAL 2 Load the target cell. This parameter takes effect only when
MLB Balancin Mobility Load Balancing Trigger Mode is set to
LST g PRB_ONLY(PrbMode) or PRB_OR_UE_NUMBER
CELLP (PrbOrUeNumMode) and Prb Load Calculation
RBVAL Method is set to PRB_VALUATION_WITH_CTRL or
MLB PRB_VALUATION_NO_CTRL. If the PRB
evaluation value of a neighboring cell is smaller than
this threshold, the load from the cell can be transferred
to the neighboring cell. If the PRB evaluation value of
a neighboring cell is greater than or equal to this
threshold, the load from the cell cannot be transferred
to the neighboring cell. This parameter applies only to
LTE TDD cells.
Default Value: 80
Unit: %

eRAN TDD

nd
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 set
d LST D-07021 Number 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.
Default Value: 100
Unit: None
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 the
LB Balancin 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.
Default Value: 20
Unit: None

eRAN TDD

nd
CellML InterFrq MOD LOFD-0 Intra- Meaning: Indicates the UL-synchronized UE number
B UeNum CELLM 01032 / LTE threshold used for transferring loads to neighboring
Offload LB TDLOF Load cells with which the source cell does not exchange load
Offset LST D-00103 Balancin information during inter-frequency load balancing.
CELLM 2 g Consider that the MlbTriggerMode parameter is set to
LB LOFD-0 Operator UE_NUMBER_ONLY(UeNumMode) or
70204 Load PRB_OR_UE_NUMBER(PrbOrUeNumMode). If the
Based number of UL-synchronized UEs in the source cell is
Intra- greater than or equal to the sum of the InterFreqMlbUe-
LTE NumThd parameter value and the InterFrqUeNumOf-
MLB floadOffset parameter value, 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.
Default Value: 0
Unit: None

eRAN TDD

nd
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 better
CAMG FD-001 tion for quality than the serving cell for reporting the event A6.
TCFG 002 Downlin GUI Value Range: -30~30
k 2CC in
TDLAO 30MHz Actual Value Range: -15~15
FD-001 Default Value: 2
00102 Carrier
Aggrega Unit: 0.5dB
TDLAO tion for
FD-070 Downlin
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 CA for
LAOFD Downlin
-001002 k 2CC
01 from
LAOFD Multiple
-001002 Carriers
02 Intra-
LAOFD Band
-070201 Carrier
Aggrega
LAOFD
tion for
-070202
Downlin
k 2CC in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin

eRAN TDD

nd
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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
LAOFD 20MHz Default Value: 50
-001002
01 / Inter- Unit: ms
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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.
TCFG 02 Downlin
-001002
01 / Inter- Unit: kB
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
CaMgtC UlCaAct MOD LAOFD Carrier Meaning: Indicates the time-to-trigger for activating an
fg iveTime CAMG -080202 Aggrega SCell for a UE in the uplink. If the uplink traffic volume
ToTrigg TCFG tion for of a CA UE is greater than the ActiveBufferLenThd
er LST Uplink parameter value throughout the period specified by the
CAMG 2CC UlCaActiveTimeToTrigger parameter, the eNodeB
TCFG initiates the SCell activation procedure.
Default Value: 20
Unit: ms

eRAN TDD

nd
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 this
TCFG 02 Downlin parameter is set to OFF(Off), the SCell is always active
k 2CC in after being activated, unless a radio link failure (RLF)
LAOFD 20MHz is detected on the SCell.
-001002
01 / Inter- GUI Value Range: OFF(Off), ON(On)
TDLAO Band Actual Value Range: OFF, ON
FD-001 Carrier
Default Value: OFF(Off)
002 Aggrega
tion for Unit: None
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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.
TCFG 02 Downlin
-001002
01 / Inter- Unit: kbit/s
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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.
TCFG 02 Downlin
-001002
01 / Inter- Unit: kB
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
CaMgtC SccDeac MOD LAOFD Intra- Meaning: Indicates the CQI threshold for deactivating
fg tCqiThd CAMG -001001 Band an SCell based on the channel quality. When the channel
TCFG 01 Carrier quality for a CA UE is worse than that indicated by this
LST LAOFD Aggrega threshold in single-codeword transmission, the eNodeB
CAMG -001001 tion for deactivates the SCell for the CA UE. If this parameter
TCFG 02 Downlin is set to 0, the eNodeB does not deactivate the SCell for
k 2CC in a CA UE based on channel quality of the SCell. This
LAOFD 20MHz parameter specifies the CQI threshold for deactivating
-001002 the SCell that the local cell acts as, and takes effect only
01 Inter-
Band when the CarrierMgtSwitch parameter on the associated
LAOFD PCell is set to ON.
Carrier
-001002 GUI Value Range: 0~15
Aggrega
02
tion for Actual Value Range: 0~15
LAOFD Downlin
k 2CC in
LAOFD 20MHz Unit: None
-070202 Carrier
TDLAO Aggrega
FD-001 tion for
00111 Downlin
k 2CC in
TDLAO
40MHz
FD-001
002 Support
TDLAO of UE
FD-001 Categor
00102 y6
TDLAO CA for
FD-070 Downlin
201 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
for UE
Categor
y6
CA for
Downlin
k 2CC
from
Multiple
Carriers

eRAN TDD

nd
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
LAOFD 20MHz Default Value: -109
-001002
01 / Inter- Unit: dBm
TDLAO Band
FD-001 Carrier
002 Aggrega
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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 PCell,
LLCFG LAOFD Aggrega the UE reports event A2 pertaining to the candidate
MOD -001001 tion for SCell specified by the SCelleNodeBId and
CAGRO 02 Downlin SCellLocalCellId parameters to the eNodeB if the
UPSCE k 2CC in RSRP for the candidate SCell exceeds the sum of the
LAOFD 20MHz CarrAggrA2ThdRsrp and SCellA2Offset parameter
LLCFG -001002
Inter- values. If the sum is greater than –43 dBm or less than
LST 01 / –140 dBm, the threshold for event A2 takes the value –
CAGRO TDLAO Band
Carrier 43 dBm or –140 dBm, respectively.
UPSCE FD-001
LLCFG 002 Aggrega GUI Value Range: -31~66
tion for Actual Value Range: -31~66
LAOFD
Downlin
k 2CC in
02 / Unit: dBm
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
SccFreq SccA2O ADD LAOFD Intra- Meaning: Indicates the offset of the actual threshold for
Cfg ffset SCCFR -001001 Band CA event A2relative to the value of the
EQCFG 01 Carrier CarrAggrA2ThdRsrp parameter in the CaMgtCfg MO.
MOD LAOFD Aggrega If the actual threshold is greater than -43 dBm, the value
SCCFR -001001 tion for of -43 dBm takes effect. If the actual threshold is less
EQCFG 02 Downlin than -140 dBm, the value of -140 dBm takes effect.
k 2CC in GUI Value Range: -31~66
LST LAOFD 20MHz
SCCFR -001002 Actual Value Range: -31~66
EQCFG 01 Inter-
LAOFD Carrier Unit: dBm
-001002 Aggrega
02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 threshold,
GROUP TDLBF frequenc event A4 is reported. The value of this parameter is also
MOD D-00201 y used as the RSRP threshold for event A4 related to
INTERF 802 Handov distance-based, UL-power-based, or SPID-based inter-
REQHO LBFD-0 er frequency handover back to the HPLMN.
GROUP 0201804 Distance GUI Value Range: -140~-43
LST / Based Actual Value Range: -140~-43
INTERF TDLBF Inter-
D-00201 frequenc Default Value: -105
REQHO
GROUP 804 y Unit: dBm
Handov
er
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for inter-
qHoGro qHoA2T INTERF 0201802 e Based frequency measurement event A2. When the measured
up hdRsrp REQHO / Inter- RSRP value is below the threshold, a measurement
GROUP TDLBF frequenc report will be sent.
MOD D-00201 y GUI Value Range: -140~-43
INTERF 802 Handov
er Actual Value Range: -140~-43
REQHO
GROUP Default Value: -109
LST Unit: dBm

INTERF
REQHO
GROUP
EutranIn InterFre ADD LBFD-0 Coverag Meaning: Indicates the event to trigger coverage-based
terNFre qHoEve EUTRA 0201802 e Based inter-frequency handovers. This parameter can be set to
q ntType NINTE / Inter- EventA3, EventA4, or EventA5. If the neighboring E-
RNFRE TDLBF frequenc UTRAN frequency and the serving frequency are in the
Q D-00201 y same frequency band, event A3 is recommended as it
MOD 802 Handov provides better handover performance in this situation.
EUTRA er If the neighboring E-UTRAN frequency and the serving
NINTE frequency are in different frequency bands, event A4 or
RNFRE A5 is used.
Q GUI Value Range: EventA3(EventA3), EventA4
LST (EventA4), EventA5(EventA5)
EUTRA Actual Value Range: EventA3, EventA4, EventA5
NINTE
Default Value: EventA4(EventA4)
RNFRE
Q Unit: None

eRAN TDD

nd
CellAlg RacAlgo MOD LBFD-0 Admissi Meaning: Indicates whether to enable the admission and
oSwitch Switch CELLA 02023 / on load control algorithms. DlSwitch: Indicates whether to
LGOSW TDLBF Control enable the algorithm of downlink admission control
ITCH D-00202 Congesti based on the satisfaction rate. If this switch is on, the
LST 3 on algorithm is enabled. If this switch is off, the algorithm
CELLA LBFD-0 Control is disabled. During the calculation of the QoS
LGOSW 02024 / satisfaction rate of services with different QCIs, the
Radio/ satisfaction estimation method used dedicatedly for
ITCH TDLBF transport
D-00202 VoIP services is implemented on services with the QCI
resource of 1. If a service with the QCI of 1 is not a VoIP service,
4 pre- the satisfaction rate calculated using this method is
LOFD-0 emption lower than the actual value, which affects the admission
0102901 of GBR services. Therefore, if not all the services with
the QCI of 1 are VoIP services, it is recommended that
this switch be off. UlSwitch: Indicates whether to enable
the algorithm of uplink admission control based on the
satisfaction rate. If this switch is on, the algorithm is
enabled. If this switch is off, the algorithm is disabled.
During the calculation of the QoS satisfaction rate of
services with different QCIs, the satisfaction estimation
method used dedicated for VoIP services is
implemented on services with the QCI of 1. If a service
with the QCI of 1 is not a VoIP service, the satisfaction
rate calculated using this method is lower than the actual
value, which affects the admission of GBR services.
Therefore, if not all the services with the QCI of 1 are
VoIP services, it is recommended that this switch be off.
DlPredictSwitch: Indicates whether to enable the
algorithm of downlink admission control based on
prediction. If this switch is on, the algorithm is enabled.
If this switch is off, the algorithm is disabled.
UlPredictSwitch: Indicates whether to enable the
algorithm of uplink admission control based on
prediction. If this switch is on, the algorithm is enabled.
If this switch is off, the algorithm is disabled.
GbrUsageSwitch: Indicates whether to enable the check
on the number of PRBs used by GBR services. If this
switch is on, the number of PRBs used by existing GBR
services is checked before a new GBR service can be
admitted. If this switch is off, the number of PRBs used
by existing GBR services is not checked during
admission evaluation of new GBR services
DlLdcSwitch: Indicates whether to implement load
control in the downlink of a cell. If this switch is on, the
system checks for congestion in the downlink of the cell.
If the downlink is congested, load control is performed.
If this switch is off, the system does not check for

eRAN TDD

nd
congestion in the downlink of the cell and the

congestion cannot be relieved. During the calculation of
the QoS satisfaction rate of services with different QCIs,
the satisfaction estimation method used dedicated for
VoIP services is implemented on services with the QCI
of 1. If a service with the QCI of 1 is not a VoIP service,
the satisfaction rate calculated using this method is
lower than the actual value, which affects the cell load
control. Therefore, if not all the services with the QCI
of 1 are VoIP services, it is recommended that this
switch be off. UlLdcSwitch: Indicates whether to
implement load control in the uplink of a cell. If this
switch is on, the system checks for congestion in the
uplink of the cell. If the uplink is congested, load control
is performed. If this switch is off, the system does not
check for congestion in the uplink of the cell and the
congestion cannot be relieved. During the calculation of
the QoS satisfaction rate of services with different QCIs,
the satisfaction estimation method used dedicated for
VoIP services is implemented on services with the QCI
of 1. If a service with the QCI of 1 is not a VoIP service,
the satisfaction rate calculated using this method is
lower than the actual value, which affects the cell load
control. Therefore, if not all the services with the QCI
of 1 are VoIP services, it is recommended that this
switch be off. RelDrbSwitch: Indicates whether low-
priority services can be released in the case of
congestion. If this switch is on, low-priority services can
be released. If this switch is off, low-priority services
cannot be released. PreemptionSwitch: Indicates
whether to enable the preemption control algorithm. If
this switch is on, preemption can be used when the
admission of high-priority services fails. If this switch
is off, only emergency calls can be admitted to the
system when resources are insufficient.
GUI Value Range: DlSwitch(dlCacSwitch), UlSwitch
(ulCacSwitch), DlPredictSwitch(dlCacPredictSwitch),
UlPredictSwitch(ulCacPredictSwitch),
GbrUsageSwitch(GbrUsedPRbCheckSwitch),
DlLdcSwitch(dlLdcSwitch), UlLdcSwitch
(ulLdcSwitch), RelDrbSwitch(LdcDrbRelSwitch),
PreemptionSwitch(PreemptionSwitch)
Actual Value Range: DlSwitch, UlSwitch,
DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch,
DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,
PreemptionSwitch

eRAN TDD

nd
Default Value: DlSwitch:Off, UlSwitch:Off,

DlPredictSwitch:Off, UlPredictSwitch:Off,
GbrUsageSwitch:Off, DlLdcSwitch:Off,
UlLdcSwitch:Off, RelDrbSwitch:Off,
PreemptionSwitch:Off
Unit: None

eRAN TDD

nd
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 scheduling
LSCHA 01 Carrier or differentiated scheduling. (If CA is applied in the
LGO LAOFD Aggrega uplink, this parameter also indicates the uplink
LST -001001 tion for scheduling polity.) If the CA basic scheduling policy is
CELLD 02 Downlin adopted, the eNodeB calculates the proportional fair
LSCHA k 2CC in (PF) scheduling priority of each component carrier (CC)
LAOFD 20MHz for a CA UE using the total data rates on both CCs of
LGO -001002
Inter- this CA UE. In this way, CA UEs and non-CA UEs can
01 / be allocated similar number of RBs. If the CA
TDLAO Band
Carrier differentiated scheduling policy is adopted, the eNodeB
FD-001 calculates the PF scheduling priority of each CC for a
002 Aggrega
tion for CA UE using the data rate only on the primary
LAOFD Downlin component carrier (PCC) or secondary component
-001002 k 2CC in carrier (SCC) of this CA UE. In this way, CA UEs can
02 / 20MHz achieve better performance than non-CA UEs.
TDLAO GUI Value Range: BASIC_SCHEDULE(Basic
FD-001 Carrier
Schedule), DIFF_SCHEDULE(differentiation
00102 Aggrega
schedule)
tion for
LAOFD Downlin Actual Value Range: BASIC_SCHEDULE,
-070201 k 2CC in DIFF_SCHEDULE
/ 40MHz Default Value: BASIC_SCHEDULE(Basic Schedule)
TDLAO
FD-070 Support Unit: None
201 of UE
Categor
LAOFD y6
-070202
CA for
TDLAO Downlin
FD-001 k 2CC
00111 From
LOFD-0 Multiple
01015 / Carriers
TDLOF Carrier
D-00101 Aggrega
5 tion for
LOFD-0 2CC
0101501 based on
/ Coordin
TDLOF ated
D-00101 BBU
501 Intra-
LOFD-0 band
0101502 Carrier
/ Aggrega
TDLOF tion for

eRAN TDD

nd
D-00101 Downlin
502 k 2CC in
30MHz
Enhance
d
Scheduli
ng
CQI
Adjustm
ent
Dynami
c
Scheduli
ng

eRAN TDD

nd
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 in to FROMPCC, the Doppler frequency offset on the
LGO -001001 20MHz primary component carrier (PCC) is measured no matter
02 / Inter- whether the SCC is configured with an uplink carrier,
TDLAO Band and then the Doppler frequency offset is applied to
FD-001 Carrier frequency selective scheduling on the SCC after
00102 Aggrega converting downlink frequencies of the PCC and SCC.
LAOFD tion for GUI Value Range: FROMSCC(FROMSCC),

-001002 Downlin FROMPCC(FROMPCC)
01 / k 2CC in Actual Value Range: FROMSCC, FROMPCC
TDLAO 20MHz
Default Value: FROMSCC(FROMSCC)
FD-001 Carrier
002 Unit: None
Aggrega
LAOFD tion for
-001002 Downlin
02 / k 2CC in
TDLAO 40MHz
FD-001 Support
00102 of UE
LAOFD Categor
-070201 y6
/ CA for
TDLAO Downlin
FD-070 k 2CC
201 From
LAOFD Multiple
-070202 Carriers
TDLAO Carrier
FD-001 Aggrega
00111 tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
CellBfM BfMimo MOD TDLOF DL 2x2 Meaning: Indicates the type of adaptive selection
imoPara Adaptiv CELLB D-00100 MIMO between beamforming and MIMO for a multi-antenna
Cfg eSwitch FMIMO 1 DL 4x2 eNodeB. The values are described as follows:
PARAC TDLOF MIMO NO_ADAPTIVE: A fixed beamforming or MIMO
FG D-00100 transmission mode is used. That is, transition between
DL 4x4 the beamforming and MIMO transmission mode is not
LST 3 MIMO
CELLB supported. TxD_BF_ADAPTIVE: The transmission
TDLOF Single mode changes adaptively between TM2 and TM7 or
FMIMO D-00106
PARAC Streami between TM2 and TM8, depending on the protocol
0 release with which UEs comply.
FG ng
TDLOF Beamfor MIMO_BF_ADAPTIVE: The transmission mode
D-00104 ming changes adaptively between TM2, TM3, and TM7,
9 between TM2, TM3, and TM8, or between TM2, TM3,
Dual
TDLOF TM8, and TM9, depending on the protocol release with
Streami
D-00106 which UEs comply. The TM9Switch check box must be
ng
1 selected if the TM9 mode is required.
Beamfor
TDLAO ming GUI Value Range: NO_ADAPTIVE
FD-081 (NO_ADAPTIVE), TxD_BF_ADAPTIVE
DL 4x2
40114 (TxD_BF_ADAPTIVE), MIMO_BF_ADAPTIVE
MIMO (MIMO_BF_ADAPTIVE)
TDLAO based on
FD-001 Actual Value Range: NO_ADAPTIVE,
TM9
00115 TxD_BF_ADAPTIVE, MIMO_BF_ADAPTIVE
DL 8x2
TDLAO Default Value: MIMO_BF_ADAPTIVE
MIMO
FD-081 (MIMO_BF_ADAPTIVE)
based on
409 TM9 Unit: None
TDLAO
FD-081
410

eRAN TDD

nd
CellBfM FixedBf MOD TDLOF DL 2x2 Meaning: Indicates the fixed beamforming or MIMO
imoPara MimoM CELLB D-00100 MIMO transmission mode configured for a multi-antenna
Cfg ode FMIMO 1 DL 4x2 eNodeB. This parameter is valid only when
PARAC TDLOF MIMO BfMimoAdaptiveSwitch is set to NO_ADAPTIVE.
FG D-00100 The values are described as follows: TM2:
DL 4x4 Transmission mode 2 is always used for UEs. TM3:
LST 3 MIMO
CELLB Transmission mode 3 is always used for UEs. TM7:
TDLOF Single Transmission mode 7 is always used for UEs. TM8:
FMIMO D-00106
PARAC Streami Transmission mode 8 is always used for UEs. TM4:
0 ng Transmission mode 4 is always used for UEs. TM9 w/
FG
TDLOF Beamfor o PMI: Transmission mode 9 without PMI reporting is
D-00104 ming always used for UEs. TM9 w PMI: Transmission mode
9 Dual 9 with PMI reporting is always used for UEs.
TDLOF Streami GUI Value Range: TM2(TM2), TM3(TM3), TM7
D-00106 ng (TM7), TM8(TM8), TM4(TM4), TM9w/oPMI(TM9w/
1 Beamfor oPMI), TM9wPMI(TM9wPMI)
TDLAO ming Actual Value Range: TM2, TM3, TM7, TM8, TM4,
FD-081 DL 4x2 TM9w/oPMI, TM9wPMI
40114 MIMO Default Value: TM3(TM3)
TDLAO based on
TM9 Unit: None
FD-001
00115 DL 8x2
TDLAO MIMO
FD-081 based on
409 TM9
TDLAO DL 4x4
FD-081 MIMO
410 based on
TM9
DL 8x4
MIMO
based on
TM9

eRAN TDD

nd
CellAlg EnhMI MOD LAOFD DL 2*2 Meaning: Indicates whether to enable enhanced MIMO.
oSwitch MOSwit CELLA -080210 MIMO This parameter now includes one switch. TM9Switch:
ch LGOSW LAOFD based on Indicates whether accessing UEs are allowed to enter
ITCH -080205 TM9 TM9 mode. Accessing UEs are allowed to enter the
LST / DL 4*2 TM9 mode only when this switch is on. This parameter
CELLA TDLAO MIMO does not apply to cells established on the LBBPc.
LGOSW FD-001 based on GUI Value Range: TM9Switch(TM9Switch)
ITCH 00113 TM9 Actual Value Range: TM9Switch
TDLAO DL 8x2 Default Value: TM9Switch:Off
FD-001 MIMO
00114 based on Unit: None
TDLAO TM9
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. If
RsParaC witch CELLC 01001 MIMO 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 the
FD-001 Layer SfnLoadBasedAdptSwitch parameter is set to OFF(Off)
00114 MIMO for an ASFN cell on an LTE TDD network, this
TDLAO Based parameter is invalid when it is set to FIXED_CFG(Fixed
FD-081 on TM9 configure) or ADAPTIVE_CFG(ADAPTIVE_CFG).
409 DL 4- GUI Value Range: NOT_CFG(Not configure),
Layer FIXED_CFG(Fixed configure), ADAPTIVE_CFG
MIMO (ADAPTIVE_CFG)
Based Actual Value Range: NOT_CFG, FIXED_CFG,
on TM9 ADAPTIVE_CFG
Default Value: NOT_CFG(Not configure)
Unit: None

eRAN TDD

nd
CellBfM SccBfM MOD TDLAO Intra- Meaning: Indicates whether to enable adaptive selection
imoPara imoAda CELLB FD-001 band of the transmission mode of an SCC for CA UEs. If this
Cfg ptiveSwi FMIMO 00111 Carrier parameter is set to ON, the transmission mode is
tch PARAC TDLAO Aggrega selected based on the beamforming and MIMO
FG FD-001 tion for configurations. If this parameter is set to OFF, the
LST 002 Downlin transmission mode is fixed to TM3 (in non-multi-RRU
CELLB k 2CC in cell scenarios) or TM1 (in single-antenna scenarios). In
TDLAO 30MHz multi-RRU cell scenarios where all RRUs of the SCC
FMIMO FD-001
PARAC Carrier work in 1T1R mode, the transmission mode can be TM1
00202 or TM2 based on the number of CRS ports of the cell.
FG Aggrega
TDLAO tion for In other multi-RRU cell scenarios, the transmission
FD-070 Downlin mode is configured to TM3.
201 k 2CC in GUI Value Range: OFF(Off), ON(On)
TDLAO 40MHz Actual Value Range: OFF, ON
FD-081 Support
405 Default Value: OFF(Off)
for UE
TDLAO Categor Unit: None
FD-081 y6
406 CA for
TDLAO Downlin
FD-081 k 2CC
407 from
Multiple
Carriers
Carrier
Aggrega
tion for
Downlin
k 3CC
TDLAO
FD-081
406 CA
for
Downlin
k 3CC
from
Multiple
Carriers
Carrier
Aggrega
tion for
Uplink
2CC

eRAN TDD

nd
ANR CaUeCh MOD LOFD-0 Automat Meaning: Indicates the policy based on which the
oseMod ANR 02001 / ic eNodeB selects UEs to perform cell global
e LST TDLOF Neighbo identification (CGI) reading for ANR. If this parameter
ANR D-00200 ur is set to CA_UE_CAP(CA UE Capability), the eNodeB
1 Relation does not select the CA UEs that support the CA bands
(ANR) in the CA band combinations supported by the eNodeB.
If this parameter is set to CA_UE_CARRIER_NUM
(CA UE Carrier Number), the eNodeB does not select
the CA UEs that are each served by more than one
carrier. If this parameter is set to ANR_UE_CAP(ANR
UE Capability), the eNodeB does not select the UEs that
do not support ANR, that is, the eNodeB does not select
the UEs that do not support CGI reading.
GUI Value Range: CA_UE_CAP(CA UE Capability),
CA_UE_CARRIER_NUM(CA UE Carrier Number),
ANR_UE_CAP(ANR UE Capability)
Actual Value Range: CA_UE_CAP,
CA_UE_CARRIER_NUM, ANR_UE_CAP
Default Value: CA_UE_CAP(CA UE Capability)
Unit: None

eRAN TDD

nd
CellAlg PucchAl MOD LBFD-0 Physical Meaning: PucchSwitch: Indicates whether to enable the
oSwitch goSwitc CELLA 02003 / Channel PUCCH resource adjustment algorithm. If this option is
h LGOSW TDLBF Manage selected, PUCCH resource adjustment is initiated when
ITCH D-00200 ment the PUCCH resources are insufficient or excessive. If
LST 3 this option is not selected, PUCCH resource adjustment
CELLA is disabled. PucchFlexCfgSwitch: Indicates whether to
LGOSW enable PUCCH flexible configuration. This function
ITCH does not take effect if an LBBPc is used or the cell
bandwidth is 1.4 or 3 MHz. When PUCCH flexible
configuration is enabled, frequency-domain uplink
ICIC and uplink frequency hopping scheduling cannot
be used. If this option is selected, an equal number of
RBs (specified by the PucchExtendedRBNum
parameter) are separately added to both ends of the
uplink band allocated for the PUCCH. The total number
of extension PUCCH RBs equals to the
PucchExtendedRBNum parameter value multiplied by
two. This parameter applies only to LTE FDD cells.
GUI Value Range: PucchSwitch(PucchSwitch),
PucchFlexCfgSwitch(PucchFlexCfgSwitch)
Actual Value Range: PucchSwitch, PucchFlexCfgS-
witch
Default Value: PucchSwitch:On,
PucchFlexCfgSwitch:Off
Unit: None

eRAN TDD

nd
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 Actual Value Range: PERMIT_HO_ENUM,
MOD FORBID_HO_ENUM
EUTRA LBFD-0 er
NINTE 0201804 Distance Default Value: PERMIT_HO_ENUM(Permit Ho)
RFREQ / Based Unit: None
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

eRAN TDD

nd
CaGrou CaGrou ADD LAOFD Intra- Meaning: Indicates the identity of the CA group. It
p pId CAGRO -001001 Band uniquely identifies a CA group within an eNodeB.
UP 01 Carrier GUI Value Range: 0~35
LST LAOFD Aggrega
CAGRO -001001
UP 02 Downlin Default Value: None
k 2CC in Unit: None
MOD LAOFD 20MHz
CAGRO -001002
UP 01 / Inter-
TDLAO Band
RMV
FD-001 Carrier
CAGRO
002 Aggrega
UP
tion for
LAOFD
Downlin
-001002
k 2CC in
02 /
20MHz
TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz
Cell eNodeB DSP None None Meaning: Indicates the ID of the eNodeB.
Id CELL GUI Value Range: 0~1048575
DSP Actual Value Range: 0~1048575
CELLP
HYTOP Default Value: None
O Unit: None

eRAN TDD

nd
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Actual Value Range: 0~255
ADD Default Value: None
CELLB
Unit: None
AND
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
LIOPTR
ULE
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND

eRAN TDD

nd
RMV
CELLN
RT
STR
CELLR
FLOOP
BACK
STR
CELLS
ELFTES
T
STR
LRTWP
RTTST
STR
PRIBBP
ADJUS
T
UBL
CELL
DSP
LRTWP
RTTST
DSP
PRIBBP
RESINF
O

eRAN TDD

nd
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
DSP -001001
CAGRO 02 Downlin Default Value: None
UPCEL k 2CC in Unit: None
LAOFD 20MHz
L -001002
LST 01 / Inter-
CAGRO TDLAO Band
L 002 Aggrega
tion for
MOD LAOFD
Downlin
CAGRO -001002
k 2CC in
UPCEL 02 /
20MHz
L TDLAO
FD-001 Carrier
RMV
00102 Aggrega
CAGRO
tion for
UPCEL LAOFD
Downlin
L -070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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
LST -001001
UPSCE k 2CC in Unit: None
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
UPSCE FD-001 Carrier
LLCFG 002 Aggrega
tion for
RMV LAOFD
Downlin
CAGRO -001002
k 2CC in
UPSCE 02 /
20MHz
LLCFG TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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
LST -001001
UPCEL k 2CC in Unit: None
LAOFD 20MHz
L -001002
MOD 01 / Inter-
CAGRO TDLAO Band
L 002 Aggrega
tion for
RMV LAOFD
Downlin
CAGRO -001002
k 2CC in
UPCEL 02 /
20MHz
L TDLAO
FD-001 Carrier
DSP
00102 Aggrega
CAGRO
tion for
UPCEL LAOFD
Downlin
L -070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
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 Actual Value Range: 0~46589,54436~65535
EQCFG 02
k 2CC in Default Value: None
MOD LAOFD 20MHz
SCCFR -001002 Unit: None
EQCFG 01 Inter-
Band
RMV LAOFD Carrier
SCCFR -001002 Aggrega
EQCFG 02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 Actual Value Range: 0~46589,54436~65535
SCCFR -001001
EQCFG 02 Downlin Default Value: None
k 2CC in Unit: None
MOD LAOFD 20MHz
SCCFR -001002
EQCFG 01 Inter-
Band
RMV LAOFD Carrier
SCCFR -001002 Aggrega
EQCFG 02 tion for
LAOFD Downlin
-070201 k 2CC in
LAOFD 20MHz
-070202 Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
GlobalP Protocol MOD LAOFD Intra- Meaning: Indicates whether the eNodeB applies
rocSwitc Compati GLOBA -001001 Band compatibility handling to the protocol-defined
h bilitySw LPROC 01 Carrier procedures. This parameter includes the following bits:
SWITC LAOFD Aggrega CaGapMeasPriOffSwitch: This bit specifies whether
H -001001 tion for the eNodeB preferentially deletes the inter-frequency
LST 02 Downlin measurement configuration after a UE reports event A4
GLOBA k 2CC in for configuring an SCell. If this bit is set to ON, the
LAOFD 20MHz eNodeB preferentially sends an A4-related
LPROC -001002
SWITC Inter- measurement configuration deletion message. If this bit
01 / is set to OFF, the eNodeB sends the SCell configuration
H TDLAO Band
Carrier message to the UE before sending an A4-related
FD-001 measurement configuration deletion message to the UE.
002 Aggrega
tion for CaHoReqWithR9ConfigSwitch: This bit specifies
LAOFD whether the handover request message sent from the
Downlin
-001002 source eNodeB during a handover for a CA UE carries
k 2CC in
02 / the IEs sourceOtherConfig-r9 and ue-ConfigRelease-
20MHz
TDLAO r9. If this bit is set to ON, the message carries these IEs.
FD-001 Carrier If this bit is set to OFF, the message does not carry these
00202 Aggrega IEs. NasSecProcSwitch: This bit controls how the
tion for eNodeB fills the IE NAS Security Parameters to E-
LAOFD
Downlin UTRAN. If this bit is set to ON, the eNodeB fills the IE
-070201
k 2CC in from octet 1. If this bit is set to OFF, the eNodeB fills
/
40MHz the IE from octet 2. AntennaFullConfigSwitch: This bit
TDLAO
FD-070 Support controls whether the full configuration function takes
201 of UE effect. When a 3GPP Release 10 UE is handed over from
Categor a third-party eNodeB to a Huawei eNodeB and the
LAOFD
y6 handover request message contains the IE antennaInfo-
-070202
r10, the setting of this bit affects the IEs contained in
TDLAO CA for
the handover command message. If this bit is set to ON,
FD-001 Downlin
the handover command message contains IEs
00111 k 2CC
antennaInfo-r8 and fullconfig-r9. If this bit is set to OFF,
From
TDLBF the handover command message contains the IE
Multiple
D-00200 antennaInfo-r10. DrxConfigMsgSwitch: This bit
Carriers
3 controls whether the eNodeB includes the DRX-Config
Carrier IE in the RRC Connection Setup message. The
Aggrega messages contain this IE only if this bit is set to ON.
tion for HARQ-Multiplexing-Table: This bit specifies the type
2CC of the HARQ multiplexing table used by a UE. If this
based on bit is set to ON, the UE sends HARQ feedback in
Coordin multiplexing mode according to HARQ-ACK
ated Multiplexing Tables 10.1.3-2, 10.1.3-3, and 10.1.3-4 in
BBU 3GPP TS 36.213. This option applies only to LTE TDD.
Intra- SCellModCaMeasRmvSwitch: This bit controls
band whether to delete the A2 and A6 measurement
Carrier configuration for SCC of the UE before deleting or
Aggrega changing the SCell of the UE. If this bit is set to ON,
tion for upon receiving an A2 or A6 measurement report from

eRAN TDD

nd
Downlin a UE, the eNodeB sends an A2- and A6-related

k 2CC in measurement configuration deletion message to the UE
30MHz before deleting or changing the SCell of the UE. If this
(Physica bit is set to OFF, upon receiving an A2 or A6
l measurement report from a UE, the eNodeB does not
Channel send an A2- and A6-related measurement configuration
Manage deletion message to the UE before deleting or changing
ment) the SCell of the UE.
GUI Value Range: CaGapMeasPriOffSwitch,
CaHoReqWithR9ConfigSwitch, NasSecProcSwitch,
AntennaFullConfigSwitch, DrxConfigMsgSwitch,
MultiplexingTabSelSwitch, SCellModCaMeasRmvS-
witch
Actual Value Range: CaGapMeasPriOffSwitch,
CaHoReqWithR9ConfigSwitch, NasSecProcSwitch,
AntennaFullConfigSwitch, DrxConfigMsgSwitch,
MultiplexingTabSelSwitch, SCellModCaMeasRmvS-
witch
Default Value: CaGapMeasPriOffSwitch:Off,
CaHoReqWithR9ConfigSwitch:Off,
NasSecProcSwitch:Off,
AntennaFullConfigSwitch:Off,
DrxConfigMsgSwitch:Off,
MultiplexingTabSelSwitch:Off,
SCellModCaMeasRmvSwitch:Off
Unit: None

eRAN TDD

nd
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), r32
CAMG FD-001 tion for (32), r64(64), Infinity(Infinity)
TCFG 002 Downlin
k 2CC in Actual Value Range: r1, r2, r4, r8, r16, r32, r64, Infinity
TDLAO 30MHz Default Value: r8(8)
FD-001
00102 Carrier Unit: None
Aggrega
TDLAO tion for
FD-070 Downlin
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 CA for
LAOFD Downlin
-001002 k 2CC
01 from
LAOFD Multiple
-001002 Carriers
02 Intra-
LAOFD Band
-070201 Carrier
Aggrega
LAOFD
tion for
-070202
Downlin
k 2CC in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin

eRAN TDD

nd
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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 is
val TCFG 00111 Carrier 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 in
TDLAO 30MHz Actual Value Range: 120ms, 240ms, 480ms, 640ms,
FD-001 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min,
00102 Carrier 12min, 30min, 60min
Aggrega
TDLAO tion for Default Value: 10240ms
FD-070 Downlin Unit: None
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 CA for
LAOFD Downlin
-001002 k 2CC
01 from
LAOFD Multiple
-001002 Carriers
02 Intra-
LAOFD Band
-070201 Carrier
Aggrega
LAOFD
tion for
-070202
Downlin
k 2CC in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin

eRAN TDD

nd
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD

nd
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
LST -001001
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
LLCFG 002 Aggrega
tion for
RMV LAOFD
Downlin
CAGRO -001002
k 2CC in
UPSCE 02 /
20MHz
LLCFG TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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
LST -001001
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
LLCFG 002 Aggrega
tion for
RMV LAOFD
Downlin
CAGRO -001002
k 2CC in
UPSCE 02 /
20MHz
LLCFG TDLAO
FD-001 Carrier
00102 Aggrega
tion for
LAOFD
Downlin
-070201
k 2CC in
/
40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD
y6
-070202
TDLAO CA for
FD-001 Downlin
00111 k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for

eRAN TDD

nd
Downlin
k 2CC in
30MHz

eRAN TDD

nd
ENodeB OverBB MOD LOFD-0 UL Meaning: Indicates whether to enable inter-BBU

AlgoSwi UsSwitc ENODE 70223 CoMP coordinating algorithms. This parameter consists of the
tch h BALGO LAOFD based on following switches: UlJointReceptionOverBBUsS-
SWITC -001001 Coordin witch: Indicates whether to enable uplink coordinated
H 01 ated multi-point (UL CoMP) between cells established on
LST BBU BBPs in different BBUs. This function is enabled only
LAOFD when this switch is on. FreqCfgCaOverBBUsSwitch:
ENODE -001001 Intra-
BALGO Band Indicates whether to enable inter-BBU carrier
02 aggregation (CA) in scenarios where CA is configured
SWITC Carrier
H LAOFD Aggrega based on frequencies. Inter-BBU CA is enabled in the
-001002 tion for preceding scenarios only when this switch is on. This
/ Downlin switch takes effect only when FreqCfgSwitch of the
TDLAO k 2CC in CaAlgoSwitch parameter in the ENodeBAlgoSwitch
FD-001 20MHz MO is on. Inter-BBU CA is enabled only when this
002 switch is on. UlJROverRelaxedBHSw: Indicates
Inter- whether to enable the relaxed-backhaul-based inter-
LAOFD Band
-001002 BBU coordinating algorithm. UlJROverRelax-
Carrier edBHSw: Indicates whether to enable uplink
02 / Aggrega
TDLAO coordinated multi-point (UL CoMP) between cells
tion for established on BBPs in different BBUs. This function
FD-001 Downlin
00202 is enabled only when this switch is on. UlSfnJROverB-
k 2CC in BUsSwitch: Indicates whether to enable UL CoMP in
LAOFD 20MHz inter-BBU SFN cells. UlSfnJROverBBUsSwitch: UL
-070201 Carrier CoMP is enabled in inter-BBU SFN cells only when this
/ Aggrega switch is on. This switch applies to LTE TDD only.
TDLAO tion for
FD-070 GUI Value Range: UlJointReceptionOverBBUsSwitch
Downlin (UlJointReceptionOverBBUsSwitch),
201 k 2CC in FreqCfgCaOverBBUsSwitch(FreqCfgCaOverBBUsS-
LAOFD 40MHz witch), UlJROverRelaxedBHSw(UlJROverRelax-
-070202 Support edBHSw), UlSfnJROverBBUsSwitch(UlSfnJROverB-
TDLAO of UE BUsSwitch)
FD-001 Categor Actual Value Range: UlJointReceptionOverBBUsS-
00111 y6 witch, FreqCfgCaOverBBUsSwitch, UlJROverRelax-
CA for edBHSw, UlSfnJROverBBUsSwitch
Downlin Default Value:
k 2CC UlJointReceptionOverBBUsSwitch:Off,
From FreqCfgCaOverBBUsSwitch:Off,
Multiple UlJROverRelaxedBHSw:Off,
Carriers UlSfnJROverBBUsSwitch:Off
Carrier Unit: None
Aggrega
tion for
2CC
based on
Coordin

eRAN TDD

nd
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN TDD

nd
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 between
CAMG FD-001 tion for an SCell and the PCell within the aging time, the
TCFG 002 Downlin eNodeB cancels the association between the SCell and
k 2CC in the PCell.
TDLAO 30MHz
FD-001 GUI Value Range: 1~65535
00102 Carrier Actual Value Range: 1~65535
Aggrega
TDLAO tion for Default Value: 15
FD-070 Downlin Unit: min
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 CA for
LAOFD Downlin
-001002 k 2CC
01 from
LAOFD Multiple
-001002 Carriers
02 Intra-
LAOFD Band
-070201 Carrier
Aggrega
LAOFD
tion for
-070202
Downlin
k 2CC in
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin

eRAN TDD

nd
k 2CC in
40MHz
Support
of UE
Categor
y6
CA for
Downlin
k 2CC
From
Multiple
Carriers
Carrier
Aggrega
tion for
2CC
based on
Coordin
ated
BBU

eRAN TDD
Carrier Aggregation Feature Parameter Description 14 Counters
14 Counters
Table 14-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name

Description
1526726740 L.ChMeas.PRB.DL Average number of Multi-mode: None Basic Scheduling

.Used.Avg used PDSCH PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/
LTE: LBFD-002025 SDMA
TDLBFD-002025
LOFD-070205

eRAN TDD

Description
1526728424 L.ChMeas.PRB.DL Average number of Multi-mode: None Intra-Band Carrier

.PCell.Used.Avg downlink PRBs GSM: None Aggregation for
occupied by CA Downlink 2CC in
UEs that use the UMTS: None 20MHz
local cell as their LTE: Inter-Band Carrier
primary serving cell LAOFD-00100101 Aggregation for
LAOFD-00100102 Downlink 2CC in
LAOFD-070201 20MHz
LAOFD-070202 Flexible CA from
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
TDLAOFD-070201 Downlink 2CC in
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728425 L.ChMeas.PRB.DL Average number of Multi-mode: None Intra-Band Carrier

.SCell.Used.Avg downlink PRBs GSM: None Aggregation for
occupied by CA Downlink 2CC in
secondary serving LAOFD-00100101 Aggregation for
cell LAOFD-00100102 Downlink 2CC in
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728426 L.Traffic.User.PCel Average number of Multi-mode: None Intra-Band Carrier

l.DL.Avg downlink CA UEs GSM: None Aggregation for
that use the local cell Downlink 2CC in
as their primary UMTS: None 20MHz
serving cells LTE: Inter-Band Carrier
LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728427 L.Traffic.User.SCel Average number of Multi-mode: None Intra-Band Carrier

l.DL.Avg downlink CA UEs GSM: None Aggregation for
as their secondary UMTS: None 20MHz
serving cells LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728516 L.Traffic.User.PCel Maximum number Multi-mode: None Intra-Band Carrier

l.DL.Max of downlink CA GSM: None Aggregation for
UEs that use the Downlink 2CC in
local cell as their UMTS: None 20MHz
primary serving LTE: Inter-Band Carrier
cells LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728517 L.Traffic.User.SCel Maximum number Multi-mode: None Intra-Band Carrier

l.DL.Max of downlink CA GSM: None Aggregation for
UEs that use the Downlink 2CC in
local cell as their UMTS: None 20MHz
secondary serving LTE: Inter-Band Carrier
cells LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728518 L.HHO.PrepAttOut. Number of outgoing Multi-mode: None Intra-Band Carrier

CAUser.PCC handover attempts GSM: None Aggregation for
for CA UEs that use Downlink 2CC in
the local cell as their UMTS: None 20MHz
PCell LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728519 L.HHO.ExecAttOut Number of outgoing Multi-mode: None Intra-Band Carrier

.CAUser.PCC handover executions GSM: None Aggregation for
for CA UEs that use Downlink 2CC in
PCell LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526728520 L.HHO.ExecSuccO Number of Multi-mode: None Intra-Band Carrier

ut.CAUser.PCC successful outgoing GSM: None Aggregation for
handovers for CA Downlink 2CC in
PCell LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
1526728564 L.Thrp.bits.DL.CA Total traffic volume Multi-mode: None Radio Bearer

User for PDCP SDUs sent GSM: None Management
to activated CA UEs Radio Bearer
in a cell UMTS: None
Management
LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025
1526728565 L.Thrp.Time.DL.C Total duration for Multi-mode: None Radio Bearer

AUser activated CA UEs GSM: None Management
transmitting Radio Bearer
downlink data at the UMTS: None
Management
PDCP layer in a cell LTE: LBFD-002008
Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
TDLBFD-002025

eRAN TDD

Description
1526729003 L.CA.DL.PCell.Act Total downlink Multi-mode: None Intra-Band Carrier

.Dur activation duration GSM: None Aggregation for
of CA UEs that use Downlink 2CC in
Pcell LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526729004 L.CA.DL.SCell.Act Total downlink Multi-mode: None Intra-Band Carrier

.Dur activation duration GSM: None Aggregation for
of CA UEs that use Downlink 2CC in
Scell LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526729045 L.CA.DLSCell.Add Number of SCell Multi-mode: None Intra-Band Carrier

.Att addition attempts for GSM: None Aggregation for
CA Ues Downlink 2CC in
UMTS: None 20MHz
LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
LAOFD-080201 30MHz
LAOFD-080207 Carrier Aggregation
for Downlink 2CC
LAOFD-080208
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526729046 L.CA.DLSCell.Add Number of Multi-mode: None Intra-Band Carrier

.Succ successful SCell GSM: None Aggregation for
additions for CA Downlink 2CC in
Ues UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
LAOFD-080201 30MHz
for Downlink 2CC
LAOFD-080208
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526729047 L.CA.DLSCell.Rm Number of SCell Multi-mode: None Intra-Band Carrier

v.Att removal attempts for GSM: None Aggregation for
CA Ues Downlink 2CC in
UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
LAOFD-080201 30MHz
for Downlink 2CC
LAOFD-080208
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526729048 L.CA.DLSCell.Rm Number of Multi-mode: None Intra-Band Carrier

v.Succ successful SCell GSM: None Aggregation for
removals for CA Downlink 2CC in
Ues UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
LAOFD-080201 30MHz
for Downlink 2CC
LAOFD-080208
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526729259 L.CA.Traffic.bits.D Total downlink Multi-mode: None Intra-Band Carrier

L.SCell traffic volume of GSM: None Aggregation for
MAC TBs Downlink 2CC in
transmitted to CA UMTS: None 20MHz
UEs that use the LTE: Inter-Band Carrier
local cell as their LAOFD-00100101 Aggregation for
Scell LAOFD-00100102 Downlink 2CC in
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526729602 L.HHO.InterFddTd Number of inter- Multi-mode: None Intra-Band Carrier

d.PrepAttOut.CAUs duplex-mode GSM: None Aggregation for
er.PCC outgoing handover Downlink 2CC in
attempts for CA UEs UMTS: None 20MHz
that use the local cell LTE: Inter-Band Carrier
as their PCell LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526729603 L.HHO.InterFddTd Number of inter- Multi-mode: None Intra-Band Carrier

d.ExecAttOut.CAU duplex-mode GSM: None Aggregation for
ser.PCC outgoing handover Downlink 2CC in
executions for CA UMTS: None 20MHz
UEs that use the LTE: Inter-Band Carrier
local cell as their LAOFD-00100101 Aggregation for
PCell LAOFD-00100102 Downlink 2CC in
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526729604 L.HHO.InterFddTd Number of Multi-mode: None Intra-Band Carrier

d.ExecSuccOut.CA successful inter- GSM: None Aggregation for
User.PCC duplex-mode Downlink 2CC in
outgoing handovers UMTS: None 20MHz
for CA UEs that use LTE: Inter-Band Carrier
the local cell as their LAOFD-00100101 Aggregation for
PCell LAOFD-00100102 Downlink 2CC in
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526730590 L.CA.DLSCell.Add Number of blind Multi-mode: None Intra-Band Carrier

.Blind.Att SCell addition GSM: None Aggregation for
attempts for CA Ues Downlink 2CC in
UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
LAOFD-080208 Coordinated BBU
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description

.Blind.Succ successful blind GSM: None Aggregation for
SCell additions for Downlink 2CC in
CA Ues UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526730592 L.CA.DLSCell.Add Number of SCell Multi-mode: None Intra-Band Carrier

.Meas.Att addition attempts for GSM: None Aggregation for
CA UEs based on Downlink 2CC in
A4-related UMTS: None 20MHz
measurements LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description

.Meas.Succ successful SCell GSM: None Aggregation for
additions for CA Downlink 2CC in
UEs based on A4- UMTS: None 20MHz
related LTE: Inter-Band Carrier
measurements LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526730594 L.CA.DLSCell.Rm Number of SCell Multi-mode: None Intra-Band Carrier

v.Meas.Att removal attempts for GSM: None Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526730595 L.CA.DLSCell.Rm Number of Multi-mode: None Intra-Band Carrier

v.Meas.Succ successful SCell GSM: None Aggregation for
removals for CA Downlink 2CC in
UEs based on A2- UMTS: None 20MHz
related LTE: Inter-Band Carrier
measurements LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526730596 L.CA.DLSCell.Mo Number of SCell Multi-mode: None Intra-Band Carrier

d.Att change attempts for GSM: None Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526730597 L.CA.DLSCell.Mo Number of Multi-mode: None Intra-Band Carrier

d.Succ successful SCell GSM: None Aggregation for
changes for CA UEs Downlink 2CC in
based on A6-related UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080201
Inter-eNodeB CA
LAOFD-080207
based on
Inter-eNodeB CA
based on Relaxed
backhaul
Carrier Aggregation
for Downlink 3CC
in 40MHz
Carrier Aggregation
for Downlink 3CC
in 60MHz

eRAN TDD

Description
1526732656 L.Traffic.User.SCel Average number of Multi-mode: None Intra-Band Carrier

l.Active.DL.Avg activated CA UEs GSM: None Aggregation for
as their Scell UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526732657 L.Traffic.User.SCel Maximum number Multi-mode: None Intra-Band Carrier

l.Active.DL.Max of activated CA UEs GSM: None Aggregation for
as their Scell UMTS: None 20MHz
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers

eRAN TDD

Description
1526732658 L.CA.Traffic.bits.D Downlink MAC- Multi-mode: None Intra-Band Carrier

L.PCell layer traffic volume GSM: None Aggregation for
for CA UEs that treat Downlink 2CC in
PCell and have their LTE: Inter-Band Carrier
SCell activated LAOFD-00100101 Aggregation for
LAOFD-070201 20MHz
Multiple Carriers
TDLAOFD-001001
11 Inter-eNodeB CA
based on
TDLAOFD-001002
Coordinated BBU
TDLAOFD-001001
Intra-band Carrier
02
Aggregation for
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Flexible CA from
Multiple Carriers
1526732894 L.Traffic.User.SCel Average number of Multi-mode: None Carrier Aggregation

l.UL.Avg uplink CA UEs that GSM: None for Uplink 2CC
use the local cell as Carrier Aggregation
their Scell UMTS: None
for Uplink 2CC
LTE:
LAOFD-080202
TDLAOFD-081407
1526732895 L.Traffic.User.SCel Maximum number Multi-mode: None Carrier Aggregation

l.UL.Max of uplink CA UEs GSM: None for Uplink 2CC
that use the local cell Carrier Aggregation
as their Scell UMTS: None
for Uplink 2CC
LTE:
LAOFD-080202
TDLAOFD-081407

eRAN TDD

Description
1526732905 L.Traffic.User.PCel Average number of Multi-mode: None Carrier Aggregation

l.UL.Avg CA UEs that use the GSM: None for Uplink 2CC
local cell as their Carrier Aggregation
PCells in the uplink UMTS: None
for Uplink 2CC
LTE:
LAOFD-080202
TDLAOFD-081407
1526732906 L.Traffic.User.PCel Maximum number Multi-mode: None Carrier Aggregation

l.UL.Max of CA UEs that use GSM: None for Uplink 2CC
the local cell as their Carrier Aggregation
PCells in the uplink UMTS: None
for Uplink 2CC
LTE:
LAOFD-080202
TDLAOFD-081407

l.DL.3CC.Avg 3CC CA UEs that GSM: None for Downlink 3CC
use the local cell as in 60MHz
their PCells in the UMTS: None
Carrier Aggregation
downlink LTE: for Downlink 3CC
LAOFD-080208
TDLAOFD-081405

l.DL.3CC.Max of 3CC CA UEs that GSM: None for Downlink 3CC
use the local cell as in 60MHz
their PCells in the UMTS: None
Carrier Aggregation
downlink LTE: for Downlink 3CC
LAOFD-080208
TDLAOFD-081405
1526732909 L.Traffic.User.PCel Average number of Multi-mode: None Inter-eNodeB CA

l.DL.RelaxedBackh downlink relaxed- GSM: None based on Relaxed
aulCA.Avg backhaul-based backhaul
inter-eNodeB CA UMTS: None
Inter-eNodeB CA
UEs that treat the LTE: based on Relaxed
local cell as their LAOFD-080201 Backhaul
Pcell TDLAOFD-081402
1526732910 L.Traffic.User.PCel Maximum number Multi-mode: None Inter-eNodeB CA

l.DL.RelaxedBackh of downlink GSM: None based on Relaxed
aulCA.Max relaxed-backhaul- backhaul
based inter-eNodeB UMTS: None
Inter-eNodeB CA
CA UEs that treat LTE: based on Relaxed
the local cell as their LAOFD-080201 Backhaul
Pcell TDLAOFD-081402

eRAN TDD

Description
1526732911 L.ChMeas.PRB.DL Number of Multi-mode: None Inter-eNodeB CA

.PCell.RelaxedBack downlink PRBs GSM: None based on Relaxed
haulCAUsed.Avg occupied by inter- backhaul
eNodeB CA UEs UMTS: None
Inter-eNodeB CA
that treat the local LTE: based on Relaxed
cell as their PCell LAOFD-080201 Backhaul
TDLAOFD-081402
1526732912 L.ChMeas.PRB.DL Number of Multi-mode: None Inter-eNodeB CA

.SCell.RelaxedBack downlink PRBs GSM: None based on Relaxed
haulCAUsed.Avg occupied by inter- backhaul
eNodeB CA UEs UMTS: None
Inter-eNodeB CA
that treat the local LTE: based on Relaxed
cell as their SCell LAOFD-080201 Backhaul
TDLAOFD-081402

l.DL. CA UEs with the GSM: None for Downlink 3CC
3CC.Active.Avg local cell as their in 60MHz
PCell and with all UMTS: None
Carrier Aggregation
configured two LTE: for Downlink 3CC
SCCs activated LAOFD-080208
TDLAOFD-081405

l.DL. of CA UEs with the GSM: None for Downlink 3CC
3CC.Active.Max local cell as PCell in 60MHz
and with all UMTS: None
Carrier Aggregation
configured two LTE: for Downlink 3CC
SCCs activated LAOFD-080208
TDLAOFD-081405
1526732917 L.CA.DL.PCell. Duration of CA UEs Multi-mode: None Carrier Aggregation

3CC.Act.Dur with the local cell as GSM: None for Downlink 3CC
their PCell and with in 60MHz
all configured two UMTS: None
Carrier Aggregation
SCCs activated LTE: for Downlink 3CC
LAOFD-080208
TDLAOFD-081405
1526732954 L.Traffic.User.SCel Maximum number Multi-mode: None Inter-eNodeB CA

l.DL.RelaxedBackh of downlink GSM: None based on Relaxed
aulCA.Max relaxed-backhaul- backhaul
based inter-eNodeB UMTS: None
Inter-eNodeB CA
CA UEs that treat LTE: based on Relaxed
the local cell as their LAOFD-080201 Backhaul
SCell TDLAOFD-081402

eRAN TDD

Description
1526732955 L.Traffic.User.SCel Average number of Multi-mode: None Inter-eNodeB CA

l.DL.RelaxedBackh downlink relaxed- GSM: None based on Relaxed
aulCA.Avg backhaul-based backhaul
inter-eNodeB CA UMTS: None
Inter-eNodeB CA
UEs that treat the LTE: based on Relaxed
local cell as their LAOFD-080201 Backhaul
SCell TDLAOFD-081402
1526733012 L.Thrp.bits.DL. Downlink PDCP- Multi-mode: None Carrier Aggregation

3CC.CAUser layer traffic volume GSM: None for Downlink 3CC
of CA UEs that are in 60MHz
in the 3CC CA state UMTS: None
Carrier Aggregation
and treat the local as LTE: for Downlink 3CC
their PCell with two LAOFD-080208
SCells activated TDLAOFD-081405
1526733015 L.ChMeas.PRB.UL Average number of Multi-mode: None Carrier Aggregation

.PCell.Used.Avg uplink PRBs GSM: None for Uplink 2CC
occupied by CA Carrier Aggregation
UEs that treat the UMTS: None
for Uplink 2CC
local cell as their LTE:
PCell LAOFD-080202
TDLAOFD-081407
1526733016 L.ChMeas.PRB.UL Average number of Multi-mode: None Carrier Aggregation

.SCell.Used.Avg uplink PRBs GSM: None for Uplink 2CC
occupied by CA Carrier Aggregation
UEs that treat the UMTS: None
for Uplink 2CC
local cell as their LTE:
SCell LAOFD-080202
TDLAOFD-081407
1526733017 L.CA.Traffic.bits.U Uplink MAC-layer Multi-mode: None Carrier Aggregation

L.PCell traffic volume of CA GSM: None for Uplink 2CC
UEs in the uplink Carrier Aggregation
CA state that treat UMTS: None
for Uplink 2CC
the local cell as their LTE:
PCell and have their LAOFD-080202
SCell activated TDLAOFD-081407
1526733018 L.CA.Traffic.bits.U Uplink MAC-layer Multi-mode: None Carrier Aggregation

L.SCell traffic volume of CA GSM: None for Uplink 2CC
UEs in the uplink Carrier Aggregation
CA state that treat UMTS: None
for Uplink 2CC
the local cell as their LTE:
SCell LAOFD-080202
TDLAOFD-081407

eRAN TDD

Description
1526733019 L.Traffic.User.SCel Average number of Multi-mode: None Carrier Aggregation

l.Active.UL.Avg CA UEs that treat GSM: None for Uplink 2CC
SCell and have the UMTS: None
for Uplink 2CC
SCell activated in LTE:
the uplink LAOFD-080202
TDLAOFD-081407
1526733020 L.Traffic.User.SCel Maximum number Multi-mode: None Carrier Aggregation

l.Active.UL.Max of CA UEs that treat GSM: None for Uplink 2CC
SCell and have the UMTS: None
for Uplink 2CC
SCell activated in LTE:
the uplink LAOFD-080202
TDLAOFD-081407
1526733021 L.CA.UL.PCell.Act Duration of CA UEs Multi-mode: None Carrier Aggregation

.Dur in the uplink CA GSM: None for Uplink 2CC
state that treat the Carrier Aggregation
local cell as their UMTS: None
for Uplink 2CC
PCell and have the LTE:
SCell activated LAOFD-080202
TDLAOFD-081407
1526733184 L.Thrp.bits.DL.Re- Total PDCP-layer Multi-mode: None Inter-eNodeB CA

laxedBackhaul- traffic volume of GSM: None based on Relaxed
CAUser downlink data sent backhaul
to active relaxed- UMTS: None
Inter-eNodeB CA
backhaul-based LTE: based on Relaxed
inter-eNodeB CA LAOFD-080201 Backhaul
UEs in a cell TDLAOFD-081402
1526733185 L.Thrp.Time.DL.Re Total duration for Multi-mode: None Inter-eNodeB CA

laxedBackhaul- sending downlink GSM: None based on Relaxed
CAUser data to active backhaul
downlink relaxed- UMTS: None
Inter-eNodeB CA
backhaul-based LTE: based on Relaxed
inter-eNodeB CA LAOFD-080201 Backhaul
UEs at the PDCP TDLAOFD-081402
layer in a cell

eRAN TDD

Description
1526733198 L.Traffic.User.PCel Number of times Multi-mode: None Inter-eNodeB CA

l.RelaxedBackhaul inter-eNodeB CA GSM: None based on Relaxed
CA.OFF based on relaxed backhaul
backhaul stops UMTS: None
Inter-eNodeB CA
because the inter- LTE: based on Relaxed
eNodeB LAOFD-080201 Backhaul
transmission delay TDLAOFD-081402
does not meet the
requirement

eRAN TDD
Carrier Aggregation Feature Parameter Description 15 Glossary
15 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN TDD
Carrier Aggregation Feature Parameter Description 16 Reference Documents
16 Reference Documents
1. Admission and Congestion Control

2. Cell Management
3. Connection Management
4. DRX and Signaling Control
5. eX2 Self-Management
6. Intra-RAT Mobility Management in Connected Mode
7. MIMO
8. MLB
9. Overview of Mobility Management in Connected Mode
10. RAN Sharing
11. Scheduling


Carrier Aggregation (eRAN TDD 8.1 02) FPD PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Carrier Aggregation (eRAN TDD 8.1 02) FPD PDF

Încărcat de

Drepturi de autor:

Formate disponibile

eRAN TDD

Carrier Aggregation Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2015-05-15) Huawei Proprietary and Confidential i

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

Issue 02 (2015-05-15) Huawei Proprietary and Confidential ii

3.2.3.3 Adaptive SCell Configuration................................................................................................................................52

6 Engineering Guidelines for TDLAOFD-001001 LTE-A Introduction and

Issue 02 (2015-05-15) Huawei Proprietary and Confidential iii

7 Engineering Guidelines for TDLAOFD-070201 Flexible CA from Multiple Carriers

8 Engineering Guidelines for TDLAOFD-081402 Inter-eNodeB CA based on Relaxed

Issue 02 (2015-05-15) Huawei Proprietary and Confidential iv

9 Engineering Guidelines for TDLAOFD-081407 Carrier Aggregation for Uplink 2CC

10 Engineering Guidelines for TDLAOFD-081405 Carrier Aggregation for Downlink 3CC

Issue 02 (2015-05-15) Huawei Proprietary and Confidential v

11 Engineering Guidelines for TDLAOFD-081404 Carrier Aggregation for Downlink 4CC

12 Engineering Guidelines for MRFD-101231 FDD+TDD Carrier Aggregation(LTE TDD)

Issue 02 (2015-05-15) Huawei Proprietary and Confidential vi

1 About This Document

Issue 02 (2015-05-15) Huawei Proprietary and Confidential 1

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro DBS3900 LTE TDD

LampSite DBS3900 LampSite TDD

1.2 Intended Audience

1.3 Change History

eRAN TDD 8.1 02 (2015-05-15)

Change Change Description Parameter Change Affected

Issue 02 (2015-05-15) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change Affected

Deleted enhanced DL ACK Removed the option Macro, micro,

Editorial Revised event A6-related descriptions. None N/A

Modified band combinations. For None N/A

Revised the descriptions of None N/A

Revised the description of the None N/A

Revised the description of impacted None N/A

Revised the description of network None N/A

Revised precautions in 6.4.3 None N/A

Issue 02 (2015-05-15) Huawei Proprietary and Confidential 3

Change Change Description Parameter Change Affected

Revised the description of CME-based None N/A

Revised descriptions in 6.7 None N/A

Revised descriptions of the None N/A

Revised descriptions of the activation, None N/A

Revised descriptions of the activation, None N/A

Revised descriptions of the activation, None N/A

Removed the requirements for EPC None N/A

Issue 02 (2015-05-15) Huawei Proprietary and Confidential 4

eRAN TDD 8.1 01 (2015-03-20)

Change Change Description Parameter Change Affected

Feature Added descriptions of frequency- Added the option Macro, micro,

Modified the band combinations that None Macro and

Canceled the license for FDD+TDD None Macro and

Editorial Revised the description in 3.3.9 Load None N/A

Revised the description of the None N/A

Revised the description in 3.2.3.2 None N/A

Revised the description of impacted None N/A

Revised the description in 6.4.5.4 None N/A

Revised the feature activation and None N/A

Modified the alarms in 6.7 None N/A

Issue 02 (2015-05-15) Huawei Proprietary and Confidential 5