Carrier Aggregation (ERAN FDD 8.1 02) FPD

eRAN
Carrier Aggregation Feature

Parameter Description
Issue 02
Date 2015-04-30
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-04-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
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
1.4 Differences Between eNodeB Types............................................................................................................................11
2 Overview.......................................................................................................................................14
2.1 Introduction..................................................................................................................................................................14
2.2 Benefits.........................................................................................................................................................................14
2.3 Architecture..................................................................................................................................................................15
3 Technical Description.................................................................................................................17
3.1 Function Overview.......................................................................................................................................................17
3.1.1 Related Concepts.......................................................................................................................................................17
3.1.2 Usage Scenarios.........................................................................................................................................................18
3.1.2.1 Typical Scenarios...................................................................................................................................................18
3.1.2.2 Atypical Scenarios..................................................................................................................................................21
3.1.3 CA Features...............................................................................................................................................................21
3.1.3.1 LAOFD-001001 LTE-A Introduction....................................................................................................................23
3.1.3.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz....................................................................25
3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers...........................................................................................25
3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU...........................................................................25
3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul...........................................................................26
3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]...............................................................................27
3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial].......................................................................28
3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]..................................................................29
3.1.4 Band Combinations...................................................................................................................................................29
3.2 Carrier Management.....................................................................................................................................................39
3.2.1 Overview...................................................................................................................................................................39
3.2.2 PCC Anchoring (at Initial Access)............................................................................................................................41
3.2.2.1 CA-Group-based PCC Anchoring..........................................................................................................................41
3.2.2.2 Frequency-based or Adaptive PCC Anchoring......................................................................................................43
Issue 02 (2015-04-30) Huawei Proprietary and Confidential ii

eRAN
3.2.3 SCell Configuration...................................................................................................................................................45

3.2.3.1 CA-Group-based SCell Configuration...................................................................................................................47
3.2.3.2 Frequency-based SCell Configuration....................................................................................................................54
3.2.3.3 Adaptive SCell Configuration................................................................................................................................61
3.2.3.4 Load-based SCell Configuration............................................................................................................................69
3.2.4 SCell Change.............................................................................................................................................................70
3.2.5 SCell Activation........................................................................................................................................................70
3.2.6 SCell Deactivation.....................................................................................................................................................71
3.2.7 SCell Removal...........................................................................................................................................................72
3.2.8 PCC Anchoring (at RRC Connection Releases)........................................................................................................74
3.3 Other Key Techniques Under CA................................................................................................................................74
3.3.1 Connection Management Under CA.........................................................................................................................75
3.3.2 Mobility Management Under CA..............................................................................................................................75
3.3.3 Admission and Congestion Control Under CA.........................................................................................................78
3.3.4 Scheduling Under CA................................................................................................................................................79
3.3.5 MIMO Under CA......................................................................................................................................................80
3.3.6 DRX Control Under CA............................................................................................................................................81
3.3.7 RAN Sharing Under CA............................................................................................................................................81
3.3.8 Power Backoff Under CA..........................................................................................................................................82
3.3.9 MTA Under CA.........................................................................................................................................................82
4 Related Features...........................................................................................................................84
4.1 Features Related to LAOFD-001001 LTE-A Introduction..........................................................................................84
4.2 Features Related to LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz..........................................86
4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers..................................................................86
4.4 Features Related to LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.................................................87
4.5 Features Related to LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul..................................................87
4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial].....................................................88
4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial].............................................89
4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]........................................90
5 Network Impact...........................................................................................................................93
5.1 LAOFD-001001 LTE-A Introduction..........................................................................................................................93
5.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz..........................................................................94
5.3 LAOFD-070201 Flexible CA from Multiple Carriers.................................................................................................94
5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.................................................................................94
5.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul.................................................................................95
5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial].....................................................................................96
5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial].............................................................................96
Issue 02 (2015-04-30) Huawei Proprietary and Confidential iii

eRAN
5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]........................................................................96
6 Engineering Guidelines for LAOFD-001001 LTE-A Introduction and LAOFD-001002

Carrier Aggregation for Downlink 2CC in 40MHz.................................................................98
6.1 When to Use LAOFD-001001 and LAOFD-001002...................................................................................................98
6.2 Required Information...................................................................................................................................................98
6.3 Planning........................................................................................................................................................................99
6.4 Deployment................................................................................................................................................................100
6.4.1 Requirements...........................................................................................................................................................100
6.4.2 Data Preparation......................................................................................................................................................103
6.4.3 Precautions...............................................................................................................................................................105
6.4.4 Hardware Adjustment..............................................................................................................................................108
6.4.5 Activation................................................................................................................................................................108
6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................108
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.............................................................112
6.4.5.3 Using the CME to Perform Single Configuration................................................................................................113
6.4.5.4 Using Feature Operation and Maintenance on the CME......................................................................................114
6.4.5.5 Using MML Commands.......................................................................................................................................115
6.4.6 Activation Observation............................................................................................................................................118
6.4.7 Deactivation.............................................................................................................................................................123
6.4.7.1 Using the CME to Perform Batch Configuration.................................................................................................123
6.4.7.2 Using the CME to Perform Single Configuration................................................................................................124
6.4.7.3 Using MML Commands.......................................................................................................................................124
6.5 Performance Monitoring.............................................................................................................................................126
6.6 Parameter Optimization..............................................................................................................................................129
6.7 Troubleshooting..........................................................................................................................................................145
7 Engineering Guidelines for LAOFD-070201 Flexible CA from Multiple Carriers.......151

7.1 When to Use LAOFD-070201....................................................................................................................................151
7.2 Required Information.................................................................................................................................................151
7.3 Planning......................................................................................................................................................................151
7.4 Deployment................................................................................................................................................................152
7.4.1 Requirements...........................................................................................................................................................152
7.4.3 Precautions...............................................................................................................................................................153
7.4.5 Activation................................................................................................................................................................153
7.4.7 Deactivation.............................................................................................................................................................154
Issue 02 (2015-04-30) Huawei Proprietary and Confidential iv

eRAN
8 Engineering Guidelines for LAOFD-070202 Inter-eNodeB CA based on Coordinated

BBU..................................................................................................................................................155
8.1 When to Use LAOFD-070202....................................................................................................................................155
8.3 Planning......................................................................................................................................................................155
8.4 Deployment................................................................................................................................................................156
8.4.1 Requirements...........................................................................................................................................................156
8.4.3 Precautions...............................................................................................................................................................158
8.4.5 Activation................................................................................................................................................................159
8.4.7 Deactivation.............................................................................................................................................................159
9 Engineering Guidelines for LAOFD-080201 Inter-eNodeB CA based on Relaxed

backhaul.........................................................................................................................................161
9.1 When to Use LAOFD-080201....................................................................................................................................161
9.3 Planning......................................................................................................................................................................161
9.4 Deployment................................................................................................................................................................162
9.4.1 Requirements...........................................................................................................................................................162
9.4.3 Precautions...............................................................................................................................................................165
9.4.5 Activation................................................................................................................................................................166
9.4.7 Deactivation.............................................................................................................................................................167
10 Engineering Guidelines for LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
..........................................................................................................................................................169
10.1 When to Use LAOFD-080202..................................................................................................................................169
10.2 Required Information...............................................................................................................................................169
10.3 Planning....................................................................................................................................................................169
10.4 Deployment..............................................................................................................................................................169
10.4.1 Requirements.........................................................................................................................................................170
10.4.2 Data Preparation....................................................................................................................................................171
10.4.3 Precautions.............................................................................................................................................................171
Issue 02 (2015-04-30) Huawei Proprietary and Confidential v

eRAN
10.4.4 Hardware Adjustment............................................................................................................................................171

10.4.5 Activation..............................................................................................................................................................171
10.4.6 Activation Observation..........................................................................................................................................172
10.4.7 Deactivation...........................................................................................................................................................172
10.5 Performance Monitoring...........................................................................................................................................172
10.6 Parameter Optimization............................................................................................................................................173
10.7 Troubleshooting........................................................................................................................................................173
11 Engineering Guidelines for LAOFD-080207 Carrier Aggregation for Downlink 3CC in

40MHz and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz............174
11.1 When to Use LAOFD-080207 and LAOFD-080208...............................................................................................174
11.3 Planning....................................................................................................................................................................174
11.4 Deployment..............................................................................................................................................................175
11.4.1 Requirements.........................................................................................................................................................175
11.4.3 Precautions.............................................................................................................................................................176
11.4.5 Activation..............................................................................................................................................................177
11.4.7 Deactivation...........................................................................................................................................................177
12 Engineering Guidelines for LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO

[Trial]...............................................................................................................................................179
12.1 When to Use LAOFD-081237..................................................................................................................................179
12.3 Planning....................................................................................................................................................................179
12.4 Deployment..............................................................................................................................................................180
12.4.1 Requirements.........................................................................................................................................................180
12.4.3 Precautions.............................................................................................................................................................181
12.4.5 Activation..............................................................................................................................................................181
12.4.7 Deactivation...........................................................................................................................................................181
13 Engineering Guidelines for MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD)

[Trial]...............................................................................................................................................182
Issue 02 (2015-04-30) Huawei Proprietary and Confidential vi

eRAN
13.1 When to Use MRFD-101222....................................................................................................................................182

13.3 Planning....................................................................................................................................................................182
13.4 Deployment..............................................................................................................................................................183
13.4.1 Requirements.........................................................................................................................................................183
13.4.3 Precautions.............................................................................................................................................................186
13.4.5 Activation..............................................................................................................................................................187
13.4.7 Deactivation...........................................................................................................................................................189
14 Parameters.................................................................................................................................193
15 Counters....................................................................................................................................305
16 Glossary.....................................................................................................................................432
17 Reference Documents.............................................................................................................433
Issue 02 (2015-04-30) Huawei Proprietary and Confidential vii

eRAN
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 LAOFD-001001 LTE-A Introduction

LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100103 Support of UE Category 6
l LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
l LAOFD-070201 Flexible CA from Multiple Carriers
l LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
l LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
A trial feature is a feature that customers can use without paying for the license fee in the current
version. In a later version, a trial feature may be deleted or become an optional feature. The
license fee is required for optional features.
Before using a trial feature, customers need to sign a memorandum of understanding (MoU)
with Huawei.
Issue 02 (2015-04-30) Huawei Proprietary and Confidential 1

eRAN
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and
"eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
Micro BTS3202E
LampSite DBS3900 LampSite
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.
eRAN8.1 02 (2015-04-30)
This issue includes the following changes.
Change Change Description Parameter Change Affected

Type Entity
Feature None None N/A

change
Editorial Revised the description of the None N/A

change functional architecture. For details,
see 2.3 Architecture.

eRAN

Type Entity
Revised the description of typical None N/A

scenario 5. For details, see 3.1.2.1
Typical Scenarios.
Modified the total bandwidth None N/A

descriptions. For details, see 3.1.3 CA
Features.
Revised the description of CA in None N/A

networks that support downlink 4x4
MIMO. For details, see 3.1.3.9
LAOFD-081237 Carrier
Aggregation with DL 4x4 MIMO
[Trial].
Modified band combinations. For None N/A

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

configuration. For details, see 3.2.3.3
Adaptive SCell Configuration.
Revised the description of load-based None N/A

SCell configuration. For details, see
3.2.3.4 Load-based SCell
Configuration.
Modified the impacted features of None N/A

LTE-A Introduction. For details, see
4.1 Features Related to
LAOFD-001001 LTE-A
Introduction.
Modified the impacted features of None N/A

Carrier Aggregation for Uplink 2CC.
For details, see 4.6 Features Related
to LAOFD-080202 Carrier
Aggregation for Uplink 2CC
[Trial].
Revised the description of hardware None N/A

planning. For details, see 6.3
Planning.
Modified the precautions for None N/A

frequency-based configuration mode.
For details, see 6.4.3 Precautions.

eRAN

Type Entity

adjustment. For details, see 6.4.4
Hardware Adjustment.
Modified the precautions for Inter- None N/A

eNodeB CA based on Coordinated
BBU. For details, see 8.4.3
Precautions.
Modified the transmission networking None N/A

requirements and precautions for
Inter-eNodeB CA based on Relaxed
backhaul. For details, see 9.4.1
Requirements and 9.4.3
Precautions.
Modified the procedure for None N/A

deactivating Carrier Aggregation for
Uplink 2CC. For details, see 10.4.7
Deactivation.
Modified the license requirement of None N/A

downlink 3CC aggregation. For
details, see 11.4.1 Requirements.
eRAN8.1 01 (2015-03-23)
This issue includes the following changes.

Type Entity
Feature None None N/A

change
Editorial Revised the descriptions of UE None N/A

change categories in 3.1.3.1 LAOFD-001001
LTE-A Introduction.

eRAN

Type Entity
Revised the descriptions of Inter- None N/A

BBU. For details, see:
l 3.1.3.4 LAOFD-070202 Inter-
eNodeB CA based on
Coordinated BBU (feature
description)
l 5.4 LAOFD-070202 Inter-
eNodeB CA based on
Coordinated BBU (network
impact)
l 8.4.5 Activation
l 8.4.7 Deactivation
Modified band combinations. For None N/A

details, see 3.1.4 Band
Combinations.
Modified the impact of LTE-A None N/A

Introduction. For details, see 5.1
LAOFD-001001 LTE-A
Introduction.
Modified precautions in 6.4.3 None N/A

Precautions.
Revised the descriptions of the CME- None N/A

based batch configuration procedure
and the MML-based configuration
procedures. For details, see 6.4.5
Activation.

planning for FDD+TDD CA in 13.3
Planning.
eRAN8.1 Draft A (2015-01-15)

Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes
the following changes.

eRAN

Type Entity
Feature Added CA in distributed multi-BBU None Macro

change interconnection scenarios. For details, eNodeBs
see 3.1.3.4 LAOFD-070202 Inter-
BBU.
Added relaxed-backhaul-based inter- Added the option Macro and

eNodeB CA. For details, see: RelaxedBackhaul- micro
l 3.1.3.5 LAOFD-080201 Inter- CaSwitch to the eNodeBs
eNodeB CA based on Relaxed parameter
backhaul (feature description) ENodeBAlgoSwitch.
CaAlgoSwitch.
l 4.5 Features Related to
LAOFD-080201 Inter-eNodeB
CA based on Relaxed backhaul
l 5.5 LAOFD-080201 Inter-
eNodeB CA based on Relaxed
backhaul (network impact)
l 9 Engineering Guidelines for
LAOFD-080201 Inter-eNodeB
CA based on Relaxed backhaul
Added uplink 2CC aggregation. For Added the option Macro

details, see: CaUl2CCSwitch to eNodeBs
l 3.1.3.6 LAOFD-080202 Carrier the parameter
Aggregation for Uplink 2CC CaMgtCfg.CellCaAl
[Trial] (feature description) goSwitch.

[Trial]
l 5.6 LAOFD-080202 Carrier
[Trial] (network impact)
[Trial]

eRAN

Type Entity
Added downlink 3CC aggregation. Added the option Macro

For details, see: CaDl3CCSwitch to eNodeBs
l 3.1.3.7 LAOFD-080207 Carrier the parameter
Aggregation for Downlink 3CC CaMgtCfg.CellCaAl
in 40MHz (feature description) goSwitch.
l 3.1.3.8 LAOFD-080208 Carrier

Aggregation for Downlink 3CC
in 60MHz (feature description)
in 40MHz
in 60MHz
in 40MHz (network impact)
in 60MHz (network impact)
in 40MHz and LAOFD-080208
Carrier Aggregation for
Downlink 3CC in 60MHz
Added AMBR-based control over the Added the following Macro,

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

eRAN

Type Entity
Added CA in DL 4x4 MIMO None Macro

scenarios. For details, see: eNodeBs
l 3.1.3.9 LAOFD-081237 Carrier
Aggregation with DL 4x4
MIMO [Trial] (feature
description)
MIMO [Trial]
MIMO [Trial] (network impact)
MIMO [Trial]

eRAN

Type Entity
Added FDD+TDD CA. For details, l Added the Macro

see: following options eNodeBs
l 3.1.3.10 MRFD-101222 FDD to the parameter
+TDD Carrier Aggregation ENodeBAlgoSwi
(LTE FDD) [Trial] (feature tch.CaAlgoSwitc
description) h:
l 4.10 Features Related to InterFddTddC

MRFD-101222 FDD+TDD aSwitch
Carrier Aggregation(LTE FDD) CaDl4CCSwit
[Trial] ch
l 5.10 MRFD-101222 FDD+TDD l Added the
Carrier Aggregation(LTE FDD) following
[Trial] (network impact) parameters:
l 13 Engineering Guidelines for ENodeBFram
MRFD-101222 FDD+TDD eOffset.
Carrier Aggregation(LTE FDD) FddFrameOff
[Trial] set
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 implementation of features in None Macro,

CA scenarios. For details, see: micro, and
l 3.3.8 Power Backoff Under CA LampSite
eNodeBs
l 3.3.9 MTA Under CA

eRAN

Type Entity
Added adaptive configuration mode. Added the option Macro,

For details, see: AdpCaSwitch to the micro, and
l 3.2.1 Overview ENodeBAlgoSwitch. LampSite
CaAlgoSwitch eNodeBs
l 3.2.2.2 Frequency-based or parameter.
Adaptive PCC Anchoring
l 3.2.3.3 Adaptive SCell
Configuration
l 6.4.2 Data Preparation
l 6.4.3 Precautions
l 6.4.5.5 Using MML Commands
l 6.4.7.3 Using MML Commands
l 6.6 Parameter Optimization
Added the following sub-features to None Macro,

LAOFD-001001 LTE-A Introduction, micro, and
as described in 1.1 Scope and 3.1.3 LampSite
CA Features: eNodeBs
l LAOFD-00100103 Support of UE
Category 6
Category 7
Category 9
Category 10
Deleted the following sub-features None Macro,

from LAOFD-001002 Carrier micro, and
Aggregation for Downlink 2CC in LampSite
40MHz (see 1.1 Scope and 3.1.3 CA eNodeBs
Features):
l LAOFD-00100201 Carrier
Aggregation for Downlink 2CC in
40MHz
Category 6
Added band combinations. For None Macro,

details, see 3.1.4 Band micro, and
Combinations. LampSite
eNodeBs

eRAN

Type Entity
Changed the name of LAOFD-070201 None Macro,

from "CA for Downlink 2CC From micro, and
Multiple Carriers" to "Flexible CA LampSite
from Multiple Carriers". For details, eNodeBs
see:
l 3.1.3.3 LAOFD-070201 Flexible
CA from Multiple Carriers
(feature description)
LAOFD-070201 Flexible CA
from Multiple Carriers
l 5.3 LAOFD-070201 Flexible CA
from Multiple Carriers (network
impact)
LAOFD-070201 Flexible CA
from Multiple Carriers
Added load-based SCell Added the option Macro,

configuration. For details, see 3.2.3.4 SccSmartCfgSwitch micro, and
Load-based 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.
Editorial None None N/A

change
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Name Supported Supporte Supported
by Macro d by by
eNodeBs Micro LampSite
eNodeBs eNodeBs
LAOFD-001001 LTE-A Introduction Yes Yes Yes

eRAN
Feature ID Feature Name Supported Supporte Supported

by Macro d by by
eNodeBs Micro LampSite
eNodeBs eNodeBs
LAOFD-001001 Intra-Band Carrier Yes Yes Yes

01 Aggregation for Downlink
2CC in 20MHz
LAOFD-001001 Inter-Band Carrier Yes Yes Yes

02 Aggregation for Downlink
2CC in 20MHz
LAOFD-001001 Support of UE Category 6 Yes Yes Yes

03

04

05

06
LAOFD-001002 Carrier Aggregation for Yes Yes Yes

LAOFD-070201 Flexible CA from Multiple Yes Yes Yes

Carriers
LAOFD-070202 Inter-eNodeB CA based on Yes No Yes

Coordinated BBU
LAOFD-080201 Inter-eNodeB CA based on Yes Yes No

Relaxed backhaul
LAOFD-080202 Carrier Aggregation for Yes No Yes

Uplink 2CC [Trial]


LAOFD-081237 Carrier Aggregation with Yes No No

DL 4x4 MIMO [Trial]
MRFD-101222 FDD+TDD Carrier Yes No No

Aggregation(LTE FDD)
[Trial]

eRAN
Function Implementation in Macro, Micro, and LampSite eNodeBs

None

eRAN
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 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 maximize utilization of resources.
Efficient Utilization of Non-contiguous Spectrum Chunks

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

eRAN
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 achieve 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 three FDD CCs or a combination of four FDD and TDD CCs, each with
a maximum bandwidth of 20 MHz.
l CA UEs support asymmetric CA. A UE may use different numbers of CCs in the uplink
and downlink. However, the number of CCs in the downlink must always be greater than
or equal to the number of CCs in the uplink. In addition, the uplink CCs must be included
in the set of downlink CCs. Currently, Huawei eNodeBs support the aggregation of two
CCs in the uplink and the aggregation of two CCs, three CCs, or a combination of four
FDD and TDD CCs in the downlink.
l Each CC uses the same frame structure as 3GPP Release 8 carriers to support backward
compatibility.
l 3GPP Release 8 or 9 UEs are allowed to transmit and receive data on Release 10 CCs.
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 enabled.

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

eRAN
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
Related Events
l Event A2
Event A2 indicates that the signal quality of the serving cell becomes lower than a specific
threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A3
Event A3 indicates that the signal quality of the PCell's neighboring cell becomes higher
than that of the PCell. For details, see Intra-RAT Mobility Management in Connected
Mode.
l Event A4
Event A4 indicates that the signal quality of a neighboring cell becomes higher than a
specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A5
Event A5 indicates that the signal quality of the PCell becomes lower than a specific
threshold and the signal quality of a neighboring cell becomes higher than another specific
threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
l Event A6
Event A6 indicates that the signal quality of an SCell's intra-frequency neighboring cell
becomes higher than that of the SCell. If the eNodeB receives an event A6 report, it changes
the SCell while keeping the PCell unchanged. 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
Table 3-1 Typical scenarios for using CA and Huawei eNodeBs' support
Typical Scenario Supported by Remarks
Huawei eNodeBs
Scenario 1: intra- Yes None

eNodeB co-coverage
carriers

eNodeB different-
coverage carriers
Scenario 3: intra- Yes eNodeBs support this scenario in

eNodeB carriers (one frequency-based and adaptive
for macro coverage; configuration modes but not in CA-
another for edge group-based configuration mode.
coverage) NOTE
For details about the configuration
modes, see 3.2.1 Overview.
Scenario 4: intra- Yes l In frequency-based or adaptive

eNodeB carriers (one configuration mode, eNodeBs
provided by the site; support this scenario when the
another provided by ratio of macro cells to RRHs is
remote radio heads 1:N (N 1).
[RRHs]) l In CA-group-based
configuration mode, eNodeBs
support this scenario when the
ratio of macro cells to RRHs is
1:1.

eNodeB carriers (one
provided only by the
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
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
3.1.2.2 Atypical Scenarios

In addition to protocol-defined typical scenarios, Huawei CA applies to the following atypical
scenarios:
l Multi-BBU interconnection
The CA feature involved is LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.
This feature implements CA between cells served by different baseband units (BBUs). For
details, see 3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.
l Relaxed backhaul
The CA feature involved is LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul.
This feature implements CA between inter-eNodeB cells in scenarios with relaxed backhaul
requirements for delay. For details, see 3.1.3.5 LAOFD-080201 Inter-eNodeB CA based
on Relaxed backhaul.
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. No. Max. No. Max. Total Description

of UL CCs of DL CCs BW
LAOFD-001001 1 2 20 MHz This feature allows

LTE-A (CA not (2CC aggregation of two
Introduction supported) aggregation downlink CCs (referred
supported) to as downlink 2CC
aggregation in this
document) to a
maximum bandwidth of
20 MHz.

Carrier downlink 2CC
Aggregation for aggregation to a
Downlink 2CC maximum bandwidth of
in 40MHz 40 MHz.
LAOFD-070201 1 4 80 MHz This feature enables an

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

eRAN
Feature Max. No. Max. No. Max. Total Description

of UL CCs of DL CCs BW

Inter-eNodeB downlink CA between
CA based on inter-eNodeB cells in
Coordinated multi-BBU
BBU interconnection
scenarios.

Inter-eNodeB downlink 2CC
CA based on aggregation between
Relaxed inter-eNodeB cells in
backhaul scenarios with relaxed
backhaul requirements.

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

Carrier aggregation of three
Aggregation for downlink CCs (referred
Downlink 3CC to as downlink 3CC
in 40MHz aggregation in this
document) to a
40 MHz.

Carrier downlink 3CC
Aggregation for aggregation to a
Downlink 3CC maximum bandwidth of
in 60MHz 60 MHz.

Carrier downlink CA to a
Aggregation maximum bandwidth of
with DL 4x4 40 MHz on networks
MIMO [Trial] that support 4T MIMO.
MRFD-101222 1 4 80 MHz This feature allows

FDD+TDD aggregation of at most
Carrier four downlink FDD and
Aggregation TDD CCs to a
(LTE FDD) maximum bandwidth of
[Trial] 80 MHz.

eRAN
3.1.3.1 LAOFD-001001 LTE-A Introduction

This feature includes six sub-features:
l LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz

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, as shown in scenarios A and B in Figure 3-6.
The time alignment error between two intra-band contiguous or non-contiguous CCs must
be less than 130 ns or 260 ns, respectively.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band
Combinations to a maximum of 20 MHz for a CA UE.
l LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
Inter-band CA aggregates two carriers from different frequency bands for downlink data
transmission to one CA UE. Scenario C in Figure 3-6 shows inter-band CA.
The time alignment error between two inter-band CCs must be less than 260 ns.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band
Combinations to a maximum of 20 MHz for a CA UE.

eRAN
Figure 3-6 Intra-band and inter-band CA
l LAOFD-00100103 Support of UE Category 6

This sub-feature enables CA for UEs of category 6, which is defined in 3GPP TS 36.306
V10.0.0.
With this sub-feature, a UE of category 6 can reach a peak data rate of 300 Mbit/s in the
downlink and 50 Mbit/s in the uplink.
V12.0.0.
V12.0.0.
V12.0.0.

eRAN
3.1.3.2 LAOFD-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. Scenarios A and B in Figure 3-6 illustrate intra-band
contiguous and non-contiguous carriers, respectively.
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.
3.1.3.3 LAOFD-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 either two or three carriers for CA. From
TDD carriers, an eNodeB can currently select two, three, or four carriers for FDD+TDD CA.
This feature maximizes carrier utilization. It uses mobility load balancing (MLB) to achieve
efficient multi-carrier management.
3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU

This feature allows CA between inter-eNodeB cells in multi-BBU interconnection scenarios. In
eRAN6.0, only intra-BBU cells can be aggregated. Currently, CA also works between inter-
BBU cells in multi-BBU interconnection scenarios.
l eRAN7.0 supports centralized multi-BBU interconnection, in which case the peak

downlink data rate reaches 300 Mbit/s if 2x2 MIMO and downlink 2CC aggregation are
enabled.
The BBUs exchange signaling messages and transmit service data through one or two levels
of universal switching units (USUs). For details about centralized multi-BBU
interconnection, see USU3910-based Multi-BBU Interconnection.
l In addition to centralized multi-BBU interconnection, eRAN8.1 supports distributed multi-
BBU interconnection, in which case the effect of CA varies depending on the round trip
time for inter-eNodeB transmission with 2x2 MIMO enabled:
If the round trip time is less than 32 s, downlink 2CC aggregation and downlink 3CC
aggregation help achieve a peak downlink data rate of 300 Mbit/s and 450 Mbit/s,
respectively.
If the round trip time is between 32 s (including 32 s) and 260 s, downlink 2CC
aggregation and downlink 3CC aggregation help achieve a peak downlink data rate of
270 Mbit/s and 400 Mbit/s, respectively.

eRAN
If the round trip time is greater than or equal to 260 s, CA does not work.
Distributed multi-BBU interconnection requires that a Universal inter-Connection Combo
Unit (UCCU) board be installed in each BBU and connected to a USU through an optical
cable for signaling exchange and data transmission between the BBUs. For details about
distributed multi-BBU interconnection, see USU3910-based Multi-BBU Interconnection.
NOTE
In multi-BBU interconnection scenarios, each pair of BBUs are inter-eNodeB BBUs.
Inter-eNodeB CA in multi-BBU interconnection scenarios employs the same procedures as

intra-eNodeB CA for PCC anchoring, SCell configuration, SCell change, SCell activation, SCell
deactivation, and SCell removal. For details about these procedures, see 3.2 Carrier
Management.
3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul

Since eRAN8.1, CA has also applied to inter-eNodeB cells in relaxed backhaul scenarios, as
shown in Figure 3-7. The cells can be macro cells or a combination of macro and micro cells.
In relaxed backhaul 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-7 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
NOTE
l After CA is enabled, the transmission delay for CA-group-based configuration mode can be queried
by running the DSP CAGROUPCELL command, and that for frequency-based or adaptive
configuration mode can be queried by running the DSP PCCSCELLLIST command. Frequency-
based or adaptive configuration mode is recommended for inter-eNodeB CA based on relaxed backhaul
(also referred to as relaxed-backhaul-based inter-eNodeB CA in this document for clarity).
l For details about eX2 interfaces between eNodeBs, see eX2 Self-Management.
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.6 LAOFD-080202 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. Figure 3-6 illustrates intra- and inter-band carrier aggregation. 3.1.4 Band
Combinations lists the combinations of bands that support carrier aggregation.
This feature is dependent on the uplink CA capabilities of UEs and the setting of
CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter. It requires

eRAN
LAOFD-001001 LTE-A Introduction to be activated. Therefore, after LAOFD-080202 is

enabled, two carriers can be aggregated for both uplink and downlink transmission.
LAOFD-080202 works in typical scenarios and multi-BBU interconnection scenarios but does
not work between eNodeBs in relaxed backhaul scenarios.

three intra- or inter-band carriers, operators can provide higher bandwidths and improve service
This feature is dependent on the downlink CA capabilities of UEs and the setting of
CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of acknowledgments (ACKs) and negative ACKs

(NACKs) for three carriers, PUCCH format 3 is introduced. For details about PUCCH format
3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not
work between eNodeBs in relaxed backhaul scenarios.

three intra- or inter-band carriers, operators can provide higher bandwidths and improve service
CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of ACKs and NACKs for three carriers, PUCCH format
3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH format
information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not
work between eNodeBs in relaxed backhaul scenarios.
3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]

This feature allows CA in networks that support 4T MIMO.
l When transmission mode (TM) 3 or 4 is used on the network, downlink CA works in DL

4x2 MIMO or in DL 4x4 MIMO with rank 2 scenarios, depending on the reception
capabilities of the CA UEs. If a CA UE supports 2R, downlink CA works in DL 4x2 MIMO
scenarios. If a CA UE supports 4R, downlink CA works in DL 4x4 MIMO scenarios with
a maximum rank of 2, regardless of whether the UE supports rank 4. The reason is that CA
UEs (except those of category 8) can use only rank 2 in TM3 or TM4 cells, according to
section 4.1 "ue-Category" in 3GPP 36.306 V12.0.0.
The theoretical peak downlink data rate of a CA UE on this network increases in proportion
to the number of CCs aggregated. For example, downlink 2CC aggregation achieves 300
Mbit/s, and downlink 3CC aggregation achieves 450 Mbit/s.

eRAN
l When TM9 is used on the network, CA works in DL 4x2 MIMO or in DL 4x4 MIMO with
rank 4 scenarios, depending on the reception capabilities of the CA UEs. If a CA UE
supports 2R, CA works in DL 4x2 MIMO scenarios. If a CA UE supports 4R and rank 4,
CA works in DL 4x4 MIMO scenarios with a maximum rank of 4.
Aggregation of two downlink 20 MHz carriers for a CA UE on this network can
theoretically achieve a peak downlink data rate of 600 Mbit/s. However, TM9 introduces
system overheads, which limit the rate to no more than 500 Mbit/s. In addition, the data
rate depends on the UE category. In the same scenario, downlink 2CC aggregation can
achieve a peak downlink data rate of 300 Mbit/s for a category 6 or 7 CA UE and 450 Mbit/
s for a category 9 or 10 CA UE. Under CA with other numbers of CCs, the theoretical and
actual peak data rates can be deduced based on the fact that the rates are proportional to
the number of CCs aggregated.
NOTE
3GPP Release 10 introduces TM9 into LTE. TM9 supports single-user MIMO with a maximum of
eight layers and multi-user MIMO with a maximum of four data blocks (at most two layers for each
UE). For details about TM9, see MIMO.
This feature supports 2CC aggregation and 3CC aggregation. It works between intra-eNodeB
cells in typical scenarios, between inter-eNodeB cells in multi-BBU interconnection scenarios,
and between inter-eNodeB cells in relaxed backhaul scenarios.
3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [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 between macro cells works.
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 20 MHz, the feature LAOFD-001001 LTE-
A Introduction must be activated. In addition, the following features can be activated when
required: LAOFD-070201 Flexible CA from Multiple Carriers, LAOFD-070202 Inter-
eNodeB CA based on Coordinated BBU, LAOFD-080201 Inter-eNodeB CA based on

eRAN
Relaxed backhaul, LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial], and
MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial].
l If the total bandwidth is greater than 20 MHz but is less than or equal to 40 MHz, the
features LAOFD-001001 LTE-A Introduction and LAOFD-001002 Carrier Aggregation
for Downlink 2CC in 40MHz must be activated. In addition, the following features can be
activated when required: LAOFD-070201 Flexible CA from Multiple Carriers,
LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU, LAOFD-080201 Inter-
eNodeB CA based on Relaxed backhaul, LAOFD-080202 Carrier Aggregation for Uplink
2CC [Trial], LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz, and
l If the total bandwidth is greater than 40 MHz but is less than or equal to 60 MHz, the
following features must be activated: LAOFD-001001 LTE-A Introduction,
LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz, LAOFD-070201
Flexible CA from Multiple Carriers, LAOFD-080207 Carrier Aggregation for Downlink
3CC in 40MHz, and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz.
In addition, the following features can be activated when required: LAOFD-070202 Inter-
eNodeB CA based on Coordinated BBU, LAOFD-080201 Inter-eNodeB CA based on
Relaxed backhaul, LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial], and
NOTE
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.
Table 3-3 CA band combinations supported by Huawei eNodeBs
Band BW (MHz) Applicabl Version Max.

Combination e Entity Total
BW
(MHz)
Band 7 (2.6 l 15+15 Macro eRAN8.1 or 40

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

GHz), l 10+20 eNodeBs later
contiguous
l 15+20
l 20+20
Band 7 (2.6 l Band 7: {10, 15, 20} Macro, eRAN6.0 or 40

GHz) + band 3 l Band 3: {5, 10, 15, 20} micro, and later
(1.8 GHz) LampSite
eNodeBs
Band 7 (2.6 l Band 7: {10, 15, 20} Macro eRAN6.0 or 30

GHz) + band 20 l Band 20: {5, 10} eNodeBs later
(800 MHz)

eRAN

BW
(MHz)
Band 3 (1.8 l Band 3: {5, 10, 15, 20} Macro eRAN6.0 or 30

(800 MHz)
Band 1 (2.1 l Band 1: {5, 10, 15, 20} Macro, eRAN6.0 or 40

GHz) + band 3 l Band 3: {5, 10, 15, 20} micro, and later
(1.8 GHz) LampSite
eNodeBs
Band 4 l Band 4: {5, 10} Macro eRAN6.0 or 20

(advanced l Band 17: {5, 10} eNodeBs later
wireless service
[AWS]) + band
17 (700 MHz)
Band 4 (AWS) l Band 4: {5, 10} Macro

+ band 13 (700 l Band 13: {10} eNodeBs
MHz)
Band 4 (AWS) l Band 4: {5, 10} Macro

+ band 12 (low l Band 12: {5, 10} eNodeBs
frequency band
of 700 MHz)
Band 4 (AWS), Band 4: {5, 10} Macro eRAN7.0 or 20

non-contiguous eNodeBs later
Band 4 (AWS) l Band 4: {10, 15} Macro eRAN7.0 or 35

+ band 7 (2.6 l Band 7: {10, 15, 20} eNodeBs later
GHz)

GHz) + band 28 l Band 28: {5, 10, 15, 20} eNodeBs later
(APT700)
Band 4 (AWS) l Band 4: {5, 10, 15, 20} Macro and eRAN7.0 or 40
+ band 2 l Band 2: {5, 10, 15, 20} LampSite later
(Personal eNodeBs
Communicatio
n Service
[PCS])
Band 2 (PCS) + l Band 2: {5, 10, 15, 20} Macro eRAN7.0 or 40

band 7 (2.6 l Band 7: {5, 10, 15, 20} eNodeBs later
GHz)

eRAN

BW
(MHz)

(low frequency
band of 700
MHz)

(700 MHz)

(700 MHz)

(APT700)
Band 1 (2.1 l Band 1: {10} Macro and eRAN7.0 or 20

GHz) + band 5 l Band 5: {10} micro later
(850 MHz) eNodeBs
Band 1 (2.1 l Band 1: {5, 10, 15, 20} Macro and eRAN7.0 or 40
GHz) + band 7 l Band 7: {5, 10, 15, 20} LampSite later
(2.6 GHz) eNodeBs

(APT700)
Band 5 (850 l Band 5: {5, 10, 15, 20} Macro eRAN7.0 or 40

MHz) + band 7 l Band 7: {5, 10, 15, 20} eNodeBs later
(2.6 GHz)
Band 5 (850 l Band 5: {5, 10, 15, 20} Macro eRAN7.0 or 40

MHz) + band 28 l Band 28: {5, 10, 15, 20} eNodeBs later
(APT700)
Band 28 l 10+20 Macro eRAN7.0 or 40

(APT700), l 15+15 eNodeBs later
contiguous
l 15+20
l 20+20
Band 28 Band 28: {5, 10, 15, 20} Macro eRAN7.0 or 40

(APT700), non- eNodeBs later
contiguous

eRAN

BW
(MHz)

(APT700)
Band 20 (800 l Band 20: {10} Macro eRAN7.0 or 20

MHz) + band 8 l Band 8: {10} eNodeBs later
(900 MHz)
Band 3 (1.8 l Band 3: {10, 20} Macro eRAN7.0 or 30

GHz) + band 5 l Band 5: {10} eNodeBs later
(850 MHz)
Band 2 (PCS) + l Band 2: {5, 10} Macro eRAN7.0 or 20

band 29 (700 l Band 29: {5, 10} eNodeBs later
MHz)
Band 4 (AWS) l Band 4: {5, 10} Macro eRAN7.0 or 20

+ band 29 (700 l Band 29: {5, 10} eNodeBs later
MHz)

(900 MHz)

(900 MHz)
Band 2 (1.9 Band 2: {5, 10, 15, 20} Macro eRAN8.1 or 40

GHz), non- eNodeBs later
contiguous

contiguous

contiguous

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

eRAN

BW
(MHz)

(700 MHz)

(700 MHz)
Band 2 (1.9 l Band 2: {5, 10} Macro eRAN8.1 or 20

(700 MHz)
Band 5 (850 l Band 5: {5, 10} Macro eRAN8.1 or 20

MHz) + band 12 l Band 12: {5, 10} eNodeBs later
(700 MHz)
Band 4 (AWS) l Band 4: {15} Macro and eRAN8.1 or 25

+ band 12 (700 l Band 12: {10} micro later
MHz) eNodeBs
Band 4 (AWS) l Band 4: {15} Macro and eRAN8.1 or 25

+ band 13 (700 l Band 13: {10} micro later
MHz) eNodeBs
Band 1 (2.1 l Band 1: {10} Macro eRAN8.1 or 40

(850 MHz) +
band 7 (2.6 l Band 7: {5, 10, 15, 20}
GHz)
(3CC)

(1.8 MHz) +
band 8 (900 l Band 8: {5, 10}
MHz)
(3CC)

GHz) + band 7 l Band 7: {10, 15, 20} eNodeBs later
(2.6 GHz) +
band 20 (800 l Band 20: {5, 10}
MHz)
(3CC)

eRAN

BW
(MHz)
GHz) + band 7 l Band 7: {10, 15, 20} LampSite later
(2.6 GHz) + eNodeBs
band 7 (2.6 l Band 7: {10, 15, 20}
GHz)
(3CC)
GHz) + band 3 l Band 3: {5, 10, 15, 20} LampSite later
(1.8 GHz) + eNodeBs
band 7 (2.6 l Band 7: {10, 15, 20}
GHz)
(3CC)

(1.8 GHz) +
band 20 (800 l Band 20: {5, 10}
MHz)
(3CC)

GHz) + band 4 l Band 4: {5, 10, 15} eNodeBs later
(2.1 GHz) +
band 29 (700 l Band 29: {5, 10}
MHz)
(3CC)

(850 MHz) +
band 29 (700 l Band 29: {5, 10}
MHz)
(3CC)
Band 4 (2.1 l Band 4: {5, 10, 15} Macro eRAN8.1 or 45

(2.6 GHz) +
band 12 (700 l Band 12: {5, 10}
MHz)
(3CC)

eRAN

BW
(MHz)
Band 3 (1.8 l Band 3 (FDD): {5} Macro eRAN8.1 or 25

GHz) + band 40 l Band 40 (TDD): {20} eNodeBs later
(2.3 GHz)
(FDD+TDD
2CC)
Band 20 (800 l Band 20 (FDD): {10} Macro eRAN8.1 or 50

MHz) + band 38 l Band 38 (TDD): {20} eNodeBs later
(2.6 GHz) +
band 38 (2.6 l Band 38 (TDD): {20}
GHz)
(FDD+TDD
3CC)
Band 3 (1.8 l Band 3 (FDD): {10, 15} Macro eRAN8.1 or 60

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

(2.6 GHz) +
band 38 (2.6 l Band 38 (TDD): {20}
(2.6 GHz)
(FDD+TDD
4CC)
Band 3 (1.8 l Band 3 (FDD): {10, 15, 20} Macro eRAN8.1 or 80

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

eRAN

BW
(MHz)

(800 MHz) +
band 38 (2.6 l Band 38 (TDD): {20}
(2.6 GHz)
(FDD+TDD
4CC)
Band 8 (900 l Band 8 (FDD): {10, 15, 20} Macro eRAN8.1 or 80

MHz) + band 39 l Band 39 (FDD): {20} eNodeBs later
(1.9 GHz) +
band 41 (2.6 l Band 41 (TDD): {20}
(2.6 GHz)
(FDD+TDD
4CC)

(850 MHz)+
band 7 (2.6 l Band 7 (FDD): {20}
(2.3 GHz)
(FDD+TDD
4CC)

(2.6 GHz) +
band 20 (800 l Band 20 (FDD): {5}
MHz) + band 38 l Band 38 (TDD): {20}
(2.6 GHz)
(FDD+TDD
4CC)
Band 3 (1.8 l Band 3 (FDD): {10, 15, 20} Macro eRAN8.1 or 80

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

eRAN

BW
(MHz)
Band 8 (900 l Band 8 (FDD): {10, 15, 20} Macro eRAN8.1 or 80

MHz) + band 41 l Band 41 (TDD): {20} eNodeBs later
(2.6 GHz) +
band 41 (2.6 l Band 41 (TDD): {20}
(2.6 GHz)
(FDD+TDD
4CC)

(2.3 GHz) +
band 40 (2.3 l Band 40 (TDD): {20}
(2.3 GHz)
(FDD+TDD
4CC)
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.

eRAN
NOTE
l 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. For 3GPP-
defined band combinations and bandwidth combination sets, see section 5.6A.1 "Channel bandwidths
per operating band for CA" in 3GPP TS 36.101 V12.5.0.
l Since eRAN8.1, CA has applied to carriers with the 1.4 MHz or 3 MHz channel bandwidth. In 1.4
MHz cells, only six RBs are available for the PUCCH. Due to the significant increase in the PUCCH
load of PCells for CA UEs, 1.4 MHz cells cannot act as PCells.
3.2 Carrier Management
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

eRAN
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-8 shows the transitions between the SCell states.
Figure 3-8 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:

eRAN
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.
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
l Frequencies in band 29 work only for the downlink and therefore cannot work as PCCs.
l After PCC anchoring is enabled, the number of inter-frequency handovers increases.
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 has its RRC connection set up during initial access to 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-9.

eRAN
Figure 3-9 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
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.
3.2.2.2 Frequency-based or Adaptive PCC Anchoring

PCC anchoring works in the same way during frequency-based and adaptive CA. 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 has its RRC connection set up during initial access to 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-10.

eRAN
Figure 3-10 Frequency-based or adaptive 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
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 If a candidate PCC is not accompanied by candidate SCCs, the eNodeB does not deliver A4
measurement configurations related to this candidate PCC.
l In an inter-eNodeB case, configuration checks on neighboring eNodeBs are not applicable. After the
CA UE is handed over to a new PCell, CA does not work if CA configurations are absent or incorrect
in the target eNodeB or if a data link fails to be set up between the new PCell and an SCell.
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 this document to configure either FDD or TDD SCells.
An eNodeB starts SCell configuration for a CA UE if all the following conditions are met:
l The RRC connection of the UE has been set up in any of the following scenarios:

eRAN
Initial access (when PCC anchoring has finished)

RRC connection re-establishment
An incoming handover
l Signaling radio bearer 2 (SRB2) and the default data radio bearer (DRB) have been set up.
l The number of SCells for the UE has not reached the maximum allowed value.
l The UE is not running an emergency call.
The triggering of the SCell configuration procedure is also dependent on two factors:
l Setting of CaTrafficTriggerSwitch
This switch is an option of the ENodeBAlgoSwitch.CaAlgoSwitch parameter.
If this switch is off, which is the default setting, the eNodeB performs SCell
configuration when the CA UE initiates RRC connection setup (PCC anchoring has
finished) or when the traffic volume of the CA UE meets the SCell activation conditions
described in 3.2.5 SCell Activation.
If this switch is on, the eNodeB performs SCell configuration only when the traffic
volume of the CA UE meets the SCell activation conditions described in 3.2.5 SCell
Activation.
l AMBR-based control over the number of UEs configured with SCells
This function is introduced in eRAN8.1. Figure 3-11 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
Figure 3-11 Procedure for AMBR-based control over the number of UEs configured with
SCells
NOTE
l When comparing the number of UEs with the value of CaMgtCfg.CellMaxPccNumber, the
eNodeB does not consider the number of UEs that treat the cell as their SCell.
l If the AMBR of a UE configured with an SCell is decreased to less than the previous AMBR
threshold, the eNodeB does not remove the SCell unless the conditions described in 3.2.7 SCell
Removal are met.
l When the value of CaMgtCfg.CellMaxPccNumber is decreased to less than the number of UEs
that treat the cell as their PCell, the eNodeB does not remove the SCells for the UEs.
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.
NOTE
Currently, downlink 4CC aggregation works only for FDD+TDD CA.

eRAN
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.
Figure 3-12 shows the SCell configuration procedure.

eRAN
Figure 3-12 CA-group-based SCell configuration for uplink/downlink 2CC aggregation
The eNodeB treats a cell that meets all the following conditions as a candidate SCell for a CA
UE:

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

eRAN
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-13 shows the SCell configuration procedure for downlink 3CC aggregation.

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

eRAN

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
Figure 3-14 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
NOTE
Currently, downlink 4CC aggregation works only for FDD+TDD CA.


eRAN
Figure 3-15 Frequency-based SCell configuration for uplink/downlink 2CC aggregation
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:

eRAN
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.
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.
l If none of the candidate SCells can be configured as an SCell for the UE, the eNodeB
evaluates the next-priority candidate SCC.

eRAN
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
Figure 3-16 Frequency-based SCell configuration for downlink 3CC aggregation

eRAN

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
Figure 3-17 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
PCells and their candidate SCells are configured, and the

CaGroupSCellCfg.SCellBlindCfgFlag parameter is set to TRUE(TRUE).
In adaptive mode:
l The eNodeB attempts to configure SCells 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.
l If CaTrafficTriggerSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is
on, the eNodeB performs measurement-based SCell configuration, rather than blind SCell
configuration.
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
Figure 3-18 Adaptive SCell configuration for uplink/downlink 2CC aggregation

eRAN
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
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
Figure 3-19 Adaptive SCell configuration for downlink 3CC aggregation

eRAN

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
Figure 3-20 Adaptive SCell configuration for downlink 4CC aggregation

eRAN
3.2.3.4 Load-based SCell Configuration

Load-based SCell configuration takes effect if SccSmartCfgSwitch under the
ENodeBAlgoSwitch.CaAlgoSwitch parameter is on. In such a case, intra-eNodeB cells
exchange their load status, and external (that is, inter-eNodeB) cells are considered to be in the
high load state with the following exception: If eX2 routes have been set up between BBUs, the
inter-eNodeB cells also exchange their load status.
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 setting of CELLMLB.MlbTriggerMode:
l When this parameter is set to PRB_ONLY(PrbMode), a cell enters the high load state if
it meets the following condition continuously for 5s: PRB usage
CellMLB.InterFreqMLBThd + CellMLB.InterFreqOffloadOffset +
CellMLB.LoadOffset. The cell exits the high load state if it meets the following condition
continuously for 5s: PRB usage < CellMLB.InterFreqMLBThd +
CellMLB.InterFreqOffloadOffset - CellMLB.LoadOffset. The cell is in the low load state
before it enters the high load state or after it exits the high load state.
l When this parameter is set to UE_NUMBER_ONLY(UeNumMode), a cell enters the high
load state if it meets the following condition continuously for 5s: Number of uplink-
synchronized UEs in the cell CellMLB.InterFreqMlbUeNumThd +
CellMLB.InterFrqUeNumOffloadOffset + CellMLB.MlbUeNumOffset. The cell exits
the high load state if it meets the following condition continuously for 5s: Number of uplink-
synchronized UEs in the cell < CellMLB.InterFreqMlbUeNumThd +
CellMLB.InterFrqUeNumOffloadOffset - CellMLB.MlbUeNumOffset. The cell is in the
low load state before it enters the high load state or after it exits the high load state.
l When this parameter is set to PRB_OR_UE_NUMBER(PrbOrUeNumMode), a cell
enters the high load state if it meets either of the preceding entering conditions. The cell is
in the low load state if it is considered to be so based on both the PRB usage and the number
of uplink-synchronized UEs.
If blind-configurable candidate SCells have been set for the PCell of a CA UE, the eNodeB
preferentially configures SCells in a blind manner. During blind SCell configuration, if the
number of such candidates is greater than the number (for example, N) of SCells to be configured,
the eNodeB checks the load of each candidate and delivers an RRC Connection Reconfiguration
message to the N cells with the lightest load.
If blind-configurable candidate SCells have not been set for the PCell of the CA UE, the eNodeB
checks the load of each candidate SCell after collecting the measurement reports about all
candidates. (If the eNodeB does not receive measurement reports about any cell on a frequency
within 3s, it considers that the UE is not in the coverage area of the frequency and instructs the
UE to stop the measurements.) Based on the load status, the eNodeB delivers an RRC Connection
Reconfiguration message to configure SCells for the UE. This measurement-based SCell
configuration procedure has a longer delay than the blind SCell configuration procedure. To
shorten the delay, it is recommended that candidate SCells be blind-configurable.
NOTE
eNodeBs do not consider the load status of cells during A6-based SCell changes.

eRAN
3.2.4 SCell Change

SCell changes occur only in frequency-based and adaptive configuration modes. 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.
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 FDD+TDD 4CC aggregation and is configured with two
or three SCells, the eNodeB delivers an A6 measurement configuration to each SCell if
SccModA6Switch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on. The SCell change
procedure occurs in the SCells separately.
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:
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

eRAN
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 (FDD+TDD in the case of 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 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 protocol-stipulated. For FDD eNodeBs, the value is 8.
Figure 3-21 shows the SCell activation. As shown in the figure, the eNodeB sends a MAC CE
in subframe n, and the SCell is activated on the UE and eNodeB in subframe (n+x).
Figure 3-21 Traffic volumetriggered SCell activation
3.2.6 SCell Deactivation

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

eRAN
Traffic Volumetriggered 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 (FDD+TDD in the case of 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 (FDD+TDD CA in the case of three) SCells activated in the downlink, the eNodeB deactivates
the SCells as long as the downlink traffic volume meets the deactivation conditions.
Channel Qualitytriggered 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
l If the eNodeB removes the only SCell of a UE in the uplink or downlink 2CC aggregation
state, the UE falls back to the single carrier state.
l If the eNodeB removes an SCell of a UE in the downlink 3CC aggregation state, the UE
falls back to the downlink 2CC aggregation state. If the eNodeB removes both SCells, the
UE falls back to the single carrier state.
l If the eNodeB removes an SCell of a UE in the downlink FDD+TDD 4CC aggregation
state, the UE falls back to the downlink 3CC aggregation state. If the eNodeB removes two
SCells, the UE falls back to the downlink 2CC aggregation state. If the eNodeB removes
three SCells, the UE falls back to the single carrier state.
NOTE
l When a bearer for an emergency call or with a QCI of 1 is set up for a CA UE whose SCells have been
configured, the eNodeB does not automatically remove the SCells.
l In CA-group-based (with blind SCell configuration disabled), frequency-based, or adaptive
configuration mode, to maximize the probability of UEs being in the CA state, operators can set
SccA2RmvSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter off. Then, the eNodeB
will not deliver the A2 measurement configuration for SCell removal.
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
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

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 a total of four downlink FDD and TDD CCs,
the SCell configuration procedures take place for 4CC aggregation. If the target eNodeB is
configured with three or two CCs, the procedures take place for 3CC or 2CC aggregation,
respectively.

eRAN
The RRC Connection Reconfiguration and the preceding IEs can be traced as described in 6.4.6
Activation Observation.
Measurement Configuration
If an eNodeB performs CA for a CA UE whose signal quality is so poor that an inter-frequency
handover may occur, the spectral efficiency of the network decreases and the block error rate
(BLER) increases. To prevent this, set thresholds as follows:
l The threshold for CA event A4 (for SCell configuration) is greater than or equal to the
threshold for inter-frequency handover event A4 (specified by
InterFreqHoGroup.InterFreqHoA4ThdRsrp). The threshold for CA event A4 is equal
to CaMgtCfg.CarrAggrA4ThdRsrp plus CaGroupSCellCfg.SCellA4Offset in CA-
group-based configuration mode, or equal to CaMgtCfg.CarrAggrA4ThdRsrp plus
SccFreqCfg.SccA4Offset in frequency-based or adaptive configuration mode.
l The threshold for CA event A2 (for SCell removal) is greater than or equal to the threshold
for inter-frequency handover event A2 (specified by
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 or adaptive 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.

eRAN
If no SCell has been configured for the UE, the eNodeB delivers the measurement
configuration related to the event specified by
EUTRANINTERNFREQ.InterFreqHoEventType.
The eNodeB performs an inter-frequency handover for the UE when it receives a
measurement report of the specified event from the UE.
NOTE
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

eRAN
procedure. For details about the CA-group-based, frequency-based, and adaptive

configuration procedures, see 3.2.3.1 CA-Group-based SCell Configuration, 3.2.3.2
Frequency-based SCell Configuration, and 3.2.3.3 Adaptive SCell Configuration,
respectively.
NOTE
l This procedure results in a decrease in the number of blind or A4-based SCell configurations.
l SCell configuration during a handover requires that a routing relationship be set up between the
SCell and the target cell of the handover.
l If 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.

eRAN
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
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

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

In CA scenarios, each CC supports 2T or 4T MIMO. The MIMO scheme is independently
configured for each CC.
l If operators set the transmission mode adaptation switch

CellMimoParaCfg.MimoAdaptiveSwitch to NO_ADAPTIVE(NO_ADAPTIVE) for a
cell, they can set the CellMimoParaCfg.FixedMimoMode parameter to specify the
transmission mode as TM2, TM3, TM4, or TM6.
l If operators set CellMimoParaCfg.MimoAdaptiveSwitch to OL_ADAPTIVE
(OL_ADAPTIVE), CL_ADAPTIVE(CL_ADAPTIVE), or OC_ADAPTIVE
(OC_ADAPTIVE) for a cell, the specified transmission mode adaptation applies to the
cell.
l If operators select TM9Switch(TM9Switch) under the
CellAlgoSwitch.EnhMIMOSwitch parameter and set the
CellCsiRsParaCfg.CsiRsSwitch parameter to FIXED_CFG(Fixed configure), TM9-
capable CA UEs work in TM9 and other CA UEs work in a MIMO scheme depending on
the setting of the CellMimoParaCfg.MimoAdaptiveSwitch parameter.
NOTE
For more details about MIMO, see MIMO.

eRAN
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-22 shows an example of
the DRX configuration under CA.
Figure 3-22 Common DRX configuration
When CA is enabled, DRX control works as follows:

l If DRX is enabled in both the PCell and the SCell for a CA UE, the UE states in the cells
are handled as follows when the eNodeB that serves the PCell sends a MAC CE to activate
the SCell:
If the UE has entered the DRX state in the PCell, the UE now also enters the DRX state
in SCells, with the DRX parameters for the PCell applied to the SCells.
If the UE has not entered the DRX state in the PCell, the eNodeB determines whether
the UE should enter the DRX state in all the PCell and SCells based on the traffic volume
of the UE.
l If DRX is enabled in the PCell but disabled in an SCell, the UE exits and no longer enters
the DRX state after the SCell is configured for the UE.
l If DRX is disabled in the PCell, the UE will not enter the DRX state in either the PCell or
SCells, regardless of whether DRX is enabled in the SCells.
NOTE
For more details about DRX, see DRX and Signaling Control.
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:

eRAN
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.
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 MTA Under CA

For UEs that do not support uplink CA, only PCells provide uplink resources. Therefore, a UE
uses a single timing advance (TA), which is associated with its PCell. For UEs that support
uplink CA, both PCells and SCells provide uplink resources. If a UE supports multiple timing
advances (MTA) and MtaAlgSwitch under the ENODEBALGOSWITCH.CaAlgoSwitch
parameter is on in the eNodeB, timing works as follows:
After an SCell is configured and activated in both downlink and uplink for the UE, the eNodeB
sends a PDCCH order to the UE and, as instructed, the UE initiates a non-contention-based
random access procedure in the SCell. The eNodeB then sends the UE a random access response
to configure a secondary timing advance group (sTAG) for the UE. The network maintains a
TA for each serving cell of the UE.
If the number of preamble retransmissions in the SCell reaches the maximum, the random access
procedure fails. The UE stops random access without instructing the PCell to perform RRC
connection reestablishment. As a result, the UE is out-of-synchronization in the uplink, and only
downlink scheduling is allowed.
When CA is used in scenario 4 or 5 described in 3.1.2.1 Typical Scenarios or in multi-BBU

interconnection scenarios, it is recommended that the MTA switch be on to improve uplink
performance.

eRAN
NOTE
For details about PDCCH order, see section 8.0 "UE procedure for transmitting the physical uplink shared
channel" in 3GPP TS 36.213 V11.4.0.

eRAN
Carrier Aggregation Feature Parameter Description 4 Related Features
4 Related Features
4.1 Features Related to LAOFD-001001 LTE-A Introduction

Prerequisite Features
l LOFD-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. That is, for a CA UE, the priority on the PCC is the same as that of
such a non-CA UE on the PCC, and the priority on an SCC is the same as that of such a
non-CA UE on the SCC.
Mutually Exclusive Features

l LOFD-001007 High Speed Mobility and LOFD-001008 Ultra High Speed Mobility
In high speed scenarios, RRC connection reconfiguration procedures may frequently take
place because the eNodeB notifies UEs of SCell configuration or removal through RRC
Connection Reconfiguration messages. This increases the network signaling load. To
prevent the frequent RRC connection reconfiguration procedures, cells with the
Cell.HighSpeedFlag parameter set to the following values cannot participate in CA
currently:
HIGH_SPEED(High speed cell flag)
ULTRA_HIGH_SPEED(Ultra high speed cell flag)
EXTRA_HIGH_SPEED(Extra high speed cell flag)
Impacted Features
l 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 EARFCNs of
the PCC and SCCs in SccFreqCfg MOs. However, currently the eNodeB does not consider

eRAN
multi-band capabilities of cells. Therefore, the calculation produces only the primary-band
indicator.
l LOFD-001016 VoIP Semi-persistent Scheduling
According to 3GPP TS 36.321, semi-persistent scheduling takes effect only on the PCCs
for CA UEs.
l LOFD-001032 Intra-LTE Load Balancing, LOFD-001044 Inter-RAT Load Sharing to
UTRAN, LOFD-001045 Inter-RAT Load Sharing to GERAN, and LOFD-070215 Intra-
LTE User Number Load Balancing
When selecting UEs for a type of load balancing defined in these features, the eNodeB
filters out the CA UEs that treat the source cell as their PCells or SCells.
l 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.
l LOFD-070205 Adaptive SFN/SDMA
Adaptive single frequency network (SFN) requires UEs to report sounding reference signal
(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 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.
l LOFD-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 LOFD-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 LAOFD-002001 Static TDM eICIC and LAOFD-081233 Dynamic TDM eICIC
When one or both of these two features are enabled, the interference between macro and
micro cells cannot be mitigated as expected, because of subframe synchronization between
the PCell and SCells of each CA UE.
l LOFD-001066 Intra-eNodeB UL CoMP, LOFD-070222 Intra-eNodeB UL CoMP Phase
II, and LOFD-070223 UL CoMP based on Coordinated BBU
When LOFD-001005 UL 4-Antenna Receive Diversity is enabled, UL CoMP does not
work for CA UEs.

eRAN
l LOFD-081219 UL CoMP based on relaxed backhaul

eNodeBs do not select cells as coordinated cells for UL CoMP of CA UEs if the cells are
interconnected to the serving cells of the UEs based on relaxed backhaul.
4.2 Features Related to LAOFD-001002 Carrier Aggregation

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

The mutually exclusive features are the same as those described in 4.1 Features Related to
LAOFD-001001 LTE-A Introduction.
Impacted Features
The impacted features are the same as those described in 4.1 Features Related to
4.3 Features Related to LAOFD-070201 Flexible CA from

Multiple Carriers
l (Optional) LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
This feature is required if the total bandwidth of two aggregated carriers is greater than 20
MHz but not greater than 40 MHz.
This feature is required if the total bandwidth of three aggregated carriers does not exceed
40 MHz.
This feature is required if the total bandwidth of three aggregated carriers is greater than
40 MHz but not greater than 60 MHz.

Impacted Features

eRAN
4.4 Features Related to LAOFD-070202 Inter-eNodeB CA

based on Coordinated BBU
40 MHz.

Impacted Features
4.5 Features Related to LAOFD-080201 Inter-eNodeB CA

based on Relaxed backhaul
This feature is required if the total bandwidth is greater than 20 MHz but not greater than
40 MHz.

Impacted Features
In addition to the features described in 4.1 Features Related to LAOFD-001001 LTE-A
Introduction, the following features affect CA:

eRAN
l LBFD-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
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 LOFD-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.

for Uplink 2CC [Trial]
This feature is required if the total bandwidth is greater than 20 MHz but not greater than
40 MHz.

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

Uplink CA is incompatible with TTI bundling. In Huawei solutions, 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 LOFD-001066 Intra-eNodeB UL CoMP, LOFD-070222 Intra-eNodeB UL CoMP Phase
II, and LOFD-070223 UL CoMP based on Coordinated BBU
After an eNodeB configures an SCell in the uplink for a CA UE, UL CoMP does not work
in the SCell.

eRAN


Impacted Features


Impacted Features

with DL 4x4 MIMO [Trial]
l LOFD-001003 DL 4x2 MIMO

eRAN
l LOFD-001060 DL 4x4 MIMO

40 MHz.

Impacted Features
4.10 Features Related to MRFD-101222 FDD+TDD Carrier

Aggregation(LTE FDD) [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.
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.
l (Optional) TDLAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
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.

eRAN
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,
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
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.

eRAN
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
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
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.
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
Carrier Aggregation Feature Parameter Description 5 Network Impact
5 Network Impact
5.1 LAOFD-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
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.
5.2 LAOFD-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 LAOFD-001001 LTE-A Introduction.
5.3 LAOFD-070201 Flexible CA from Multiple Carriers

5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated

BBU
The prerequisite features have the impacts described in 5.1 LAOFD-001001 LTE-A
Introduction.
In a centralized multi-BBU interconnection scenario, where there is inter-BBU transmission

delay, the LAOFD-070202 feature has a slight negative impact on the peak data rate of a CA
UE but does not affect user experience. The reason is that the data to be sent does not arrive at
an SCell of the UE on the SCell's scheduling occasion and the UE cannot be scheduled at that
moment.
In a distributed multi-BBU interconnection scenario, if the round trip time for inter-eNodeB
transmission is between 32 s (including 32 s) and 260 s, the LAOFD-070202 feature imposes
the following impact on the UEs involved:
l CQI reports are delayed, causing slight deterioration in frequency-selective scheduling

performance and an increase in IBLER.

eRAN
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 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 LAOFD-080201 Inter-eNodeB CA based on Relaxed

backhaul
Introduction. Due to inter-eNodeB transmission delay and limited bandwidth, the
LAOFD-080201 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 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

eRAN
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.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC

[Trial]
Introduction. The LAOFD-080202 feature itself has the following impact:
If MTA is enabled, non-contention-based random access occurs in SCells. As a result, the

counters related to random access to the SCells produce larger values.

in 40MHz
Introduction. The LAOFD-080207 feature itself has the following impact on PUCCH
overheads:
To meet the transmission requirements of ACK, NACK, and CQI feedback for three downlink
CCs, PUCCH format 3 must be used. When downlink 3CC aggregation is enabled, one RB is
used for PUCCH format-3 overhead. If PucchSwitch under the
CellAlgoSwitch.PucchAlgoSwitch parameter is on, this RB is an additional RB for the PUCCH.
It was originally allocated for the physical uplink shared channel (PUSCH). If PucchSwitch is
off, this RB is an existing RB for the PUCCH. It was originally allocated for periodic CQI
reporting. As a result, more UEs have to use aperiodic CQI reporting.

in 60MHz
see 5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz.
5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO

[Trial]
5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE

FDD) [Trial]
Introduction. The MRFD-101222 feature itself has the following impact:

eRAN
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 LAOFD-001001 LTE-A
eRAN Introduction and LAOFD-001002 Carrier Aggregation for
Carrier Aggregation Feature Parameter Description Downlink 2CC in 40MHz
6 Engineering Guidelines for LAOFD-001001

LTE-A Introduction and LAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz
6.1 When to Use LAOFD-001001 and LAOFD-001002

Enable LAOFD-001001 and LAOFD-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 20 MHz, enable only LAOFD-001001 LTE-A
Introduction.
l If the total bandwidth is greater than 20 MHz but not greater than 40 MHz, enable both
LAOFD-001001 LTE-A Introduction and LAOFD-001002 Carrier Aggregation for
Downlink 2CC in 40MHz.
6.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.
Hardware Planning
l RF modules
To meet the time alignment error requirements, use one dual-carrier RF module or two RF
modules of the same model for intra-band CA. Inter-band CA has no special requirements
for RF modules. For the time alignment error requirements, see 3.1.3.1 LAOFD-001001
LTE-A Introduction in 3.1.3 CA Features.
If a single-carrier RRU3201 has been deployed for an eNodeB of eRAN3.0 or an earlier
version, the RRU3201 supports two carriers after a software upgrade to eRAN6.0 or a later
version. In this case, common public radio interface (CPRI) modules must be adjusted. For
details, see "Reconfiguring a Single-Carrier Sector as a Dual-Carrier Sector" in
"Reconfiguration" of Cell Management.
l BBPs, including UMDU
CA works between either intra-BBP or inter-BBP cells. For intra-BBP CA, use a BBP other
than LBBPc. For inter-BBP CA, use any combination of LBBPc, LBBPd, and UBBP
boards, except a combination of two LBBPc boards. CA applies to cells that meet the
requirements listed in Table 6-1.
NOTE
LBBPd and UBBP perform better than LBBPc in terms of UE capacities and processing capabilities.
Therefore, it is recommended that cells on LBBPd and UBBP boards, rather than cells on LBBPc
boards, act as PCells for UEs.

Table 6-1 Types of cells to which CA applies
Number BBP Name BBP Model Antenna Mode of Cells

of BBPs
for CA
2 LBBPc N/A 2T2R
LBBPd LBBPd1 2T2R
LBBPd2 2T2R, 2T4R, or 4T4R
LBBPd3 2T2R
UBBP UBBPd3 2T2R
UBBPd4 2T2R, 2T4R, or 4T4R
UBBPd5 2T2R
UBBP UBBPda 2T2R
1 LBBP or UBBP LBBPd3 2T2R
UBBPd5 2T2R
UBBPda 2T2R
UMDUa3 2T2R
6.4 Deployment
6.4.1 Requirements
Operating Environment
None
NEs
Table 6-2 describes the network requirements for CA.

Table 6-2 Network requirements for CA
Element Requirements
Evolved l The EPC must comply with 3GPP Release 10 or later.

packet core l To allow LAOFD-001001 LTE-A Introduction to reach a peak data rate
(EPC) of 150 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 150 Mbit/s.
l To allow LAOFD-001002 Carrier Aggregation for Downlink 2CC in
40MHz to reach a peak data rate of 300 Mbit/s in 2x2 MIMO scenarios,
the maximum bit rate that the UE subscribes to in the EPC must be greater
than or equal to 300 Mbit/s.
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, and that for two contiguous CCs with a bandwidth
combination of 20 MHz and 10 MHz is 14.4 MHz. Nominal channel
spacing is calculated as follows:
NOTE
BWChannel(1) and BWChannel(2) are the bandwidths of two carriers.
l RF modules and BBPs must meet the requirements described in
Hardware Planning in 6.3 Planning.
UE UEs must comply with 3GPP Release 10 or later and support the frequency
bands of the carriers to be aggregated and their channel bandwidths.
NOTE
According to 3GPP TS 36.306, CA UEs must report the IE 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 20 MHz, each cell
requires one sales unit of the license for LAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the aggregated cells is between 20 MHz and 40 MHz (including
40 MHz), each cell requires one sales unit of the license for LAOFD-001001 LTE-A

Introduction and one sales unit of the license for LAOFD-001002 Carrier Aggregation for
Feature ID Feature Name Model License NE Sales Unit

Control
Item
LAOFD-001 LTE-A LT1SA02 LTE-A eNodeB per cell

001 Introduction 0CA00 Introduction
(FDD)
LAOFD-001 Carrier LT1SA04 Carrier eNodeB per cell

002 Aggregation for 0CA00 Aggregation
Downlink 2CC in for
40MHz Downlink
2CC in
40MHz
(FDD)
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
the CoMP and SFN features, the backplane bandwidth may be insufficient. To prevent this,
it is recommended that intra-frequency cells be configured in the same BBP.
l Cells in band 29 are DL_ONLY cells, which transmit only downlink data. UEs cannot
camp on the cells (in idle mode), access the cells, or be handed over to the cells. These cells
can serve only as SCells for CA UEs. In addition, cells and sector equipment in this band
must be configured as follows:
Cell.WorkMode is set to DL_ONLY(Downlink only), Cell.FreqBand is set to 29, and
Cell.UlEarfcn is not set. In addition, SECTOREQM.ANTTYPE1 and
SECTOREQM.ANTTYPE2 (if two antennas are configured) are set to TX_MODE
(TX).
EUTRANINTERNFREQ.AnrInd is set to NOT_ALLOWED(NOT_ALLOWED)
for frequencies in band 29 so that they will not be managed by ANR. Therefore, for CA
to take effect, you must manually configure cells in band 29 as inter-frequency
neighboring cells of intended candidate PCells.
EUTRANINTERNFREQ.MlbTargetInd is set to NOT_ALLOWED
(NOT_ALLOWED) for frequencies in band 29 so that they will not be treated as targets
for mobility load balancing (MLB).

NOTE
l Each cell in band 29 can have a maximum of two transmit channels. It does not support 4T or
8T antenna modes.
l RRUs do not provide uplink resources for cells in band 29. Therefore,
SECTOREQM.AntTypeX (X = 1, 2, 3...8) cannot be set to RX_MODE(RX) or RXTX_MODE
(RX And TX).
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
Parameter Parameter ID Setting Notes Data Source
Name
CA Group CaGroupCell. 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 an FDD-only network, set required)
this parameter to FDD(FDD).
l In an FDD+TDD network, set
this parameter to FDDTDD
(FDDTDD).
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)

Frequency-based Configuration
Name
PCC Downlink PccFreqCfg. Set this parameter based on the Network plan
EARFCN PccDlEarfcn network plan. (negotiation not
required)
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)
CA Algorithm ENodeBAlgoS Set FreqCfgSwitch Network plan

Switch witch. (FreqCfgSwitch) under this (negotiation not
CaAlgoSwitch parameter on. required)
Adaptive Configuration
Name
PCC Downlink PccFreqCfg. Set this parameter based on the Network plan
required)
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)
CA Algorithm ENodeBAlgoS Set both FreqCfgSwitch Network plan

Switch witch. (FreqCfgSwitch) and (negotiation not
CaAlgoSwitch AdpCaSwitch(AdpCaSwitch) required)
under this parameter on.


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 a PCI conflict
occurs on a cell, the eNodeB will not configure the cell as an SCell for any UE.
l In a CA group, cells in a pair must have the same cyclic prefix (CP) length: either normal
CP or extended CP.
l After CA groups (for CA-group-based configuration) or candidate PCCs and SCCs (for
frequency-based or adaptive configuration) are manually configured, the eNodeB can
configure SCells for CA UEs that newly access the network. However, this action does not
apply to CA UEs that have been staying in RRC_CONNECTED mode before the CA
groups or candidate PCCs and SCCs are configured. SCells can be configured for these
UEs only after they access the network again or are handed over.
l If CaMgtCfg.ActiveBufferLenThd is set to 0, a large amount of radio resources is
consumed. There are two reasons:
The eNodeB activates a configured SCell as long as the eNodeB intends to send data
to the CA UE. However, if the traffic volume of the CA UE is low, the eNodeB

deactivates the SCell (because the deactivation condition is met) immediately after it
activates the SCell for the UE.
If no SCell has been configured for the CA UE, the eNodeB repeatedly attempts to
configure an SCell without considering CaMgtCfg.SccCfgInterval when the eNodeB
intends to send data to the CA UE.
To reduce the radio resource consumption, it is recommended that
CaMgtCfg.DeactiveBufferLenThd be less than CaMgtCfg.ActiveBufferLenThd.
l When CA is enabled, a large number of scheduling request indicators (SRIs) collide with
measurement gaps, delaying the transmission of scheduling requests from CA UEs. When
the number of SRI retransmissions reaches its maximum, the values of the following
indicators increase: service drop rate, number of RRC connection re-establishments, and
number of random access attempts. To avoid these impacts, you are advised to select the
BasedSriGapOptSwitch option of the ENodeBAlgoSwitch.HoCommOptSwitch
parameter, which resolves the collision.
l For CA-group-based configuration, note the following:
If a higher-frequency cell that provides relatively small coverage works as the PCell,
you are advised to enable blind configuration for a lower-frequency cell that provides
relatively large coverage. This prevents an unnecessary inter-frequency measurement
of the lower-frequency cell, which always meets the triggering condition for event A4,
when a CA UE is in the higher-frequency cell.
If a lower-frequency cell that provides relatively large coverage works as the PCell, you
are advised to disable blind configuration for a higher-frequency cell that provides
relatively small coverage. If blind configuration is enabled, a CA UE that has accessed
the lower-frequency cell encounters low scheduling efficiency in the higher-frequency
cell. In this case, the data rate of the CA UE does not reach twice that of a non-CA UE
even in differentiated scheduling mode.
An eNodeB can be configured with a maximum of 72 CaGroupSCellCfg MOs, which
represent candidate SCells. Ensure that the candidate SCells are included in the same
CA group as the associated PCells. Otherwise, the candidate SCell configurations do
not take effect and therefore are regarded as invalid. Delete the invalid
CaGroupSCellCfg MOs, which account for a proportion of the MO capacity.
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. If a cell on
an LBBPc is configured as the PCell for a UE, this cell can be accompanied by a smaller
number of SCells: four 20 MHz SCells, six 15 MHz SCells, or eight 10 MHz SCells.
This configuration mode uses intra- or inter-eNodeB dynamic routing and therefore
introduces certain delay in SCell configuration. In addition, this mode causes overheads
on the radio interface because inter-frequency measurements are required for an eNodeB
to select candidate SCells.
l For adaptive configuration, note the precautions taken for frequency-based configuration
and the following:
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.
l Pay attention to the following compatibility issues:
When blind SCell configuration is disabled, it is recommended that
CaGapMeasPriOffSwitch under the GlobalProcSwitch.ProtocolCompatibilitySw
parameter be on to minimize the probability of power shortage at Samsung Galaxy S4.
When a network uses equipment from different vendors, it is recommended that
CaHoReqWithR9ConfigSwitch under the
GlobalProcSwitch.ProtocolCompatibilitySw parameter be on to prevent CA-related
IE resolution failure caused by protocol release inconsistency.
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. It is recommended that PdcchOverlapSrchSpcSwitch be
on 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.
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
LBFD-081103 Terminal Awareness Differentiation with CA disabled for these UEs.
eNodeBs will not perform PCC anchoring or SCell configuration for the UEs. For details
about how to set parameters for identifying defective UEs and defining differentiated
handling policies, see Terminal Awareness Differentiation.

6.4.4 Hardware Adjustment

CA requires a BBP to be installed in slot 2 or 3 of a BBU3900, if configured. To facilitate capacity
expansion, an LBBPd or UBBP is recommended. 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-3 or Table 6-4 in a summary data file, which
also contains other data for the new eNodeBs to be deployed. Then, import the summary data
file into the Configuration Management Express (CME) for batch configuration.
For detailed instructions, see section "Creating eNodeBs in Batches" in the initial configuration
guide for the eNodeB, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 6-3 or Table 6-4 are contained in a scenario-specific
summary data file. In this situation, set the parameters in the MOs, and then verify and save
the file.
l Some MOs in Table 6-3 or Table 6-4 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.

Table 6-3 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
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,
CaA6ReportInterval,
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


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
GlobalProcSwitch User-defined sheet Protocol None

Compatibility
Switch
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-4 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,
CaA6ReportInterval,
SCC Disable CQI
Threshold, SCC
Configuration
Interval, Cell Level
CA Algorithm
Switch
CellDlschAlgo User-defined sheet Downlink CA None

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,
OverBBUsSwitch
GlobalProcSwitch User-defined sheet Protocol None

Compatibility
Switch


Summary Data
File
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 Activation
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Batch Reconfiguration
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, LAOFD-001001 LTE-A Introduction. Then, click Next.
Step 5 Under Available Base Stations in the dialog box, select the eNodeB whose data is to be exported.
Click so that the eNodeB is added to Selected Base Stations. Then, click Next.
Step 6 In the dialog box, set Export as to the format (.xls or .xlsm) in which the exported data is to be
saved. Click to the right of Export path to specify the save path. Then, click Next.
Step 7 Wait until the data is exported.
Step 8 Click the hyperlink to the save path. Alternatively, click Finish, and locate the exported file in
the save path.
Step 9 Set CA parameters in the CA data file (for example, LAOFD-001001.xls) in the save path. In
the CA data file, you can click an MO on the Home sheet and set the parameters on the displayed
sheet based on the network plan.
Step 10 After setting the parameters, choose CME > Advanced > Feature Operation and
Maintenance > Import Feature Commission Data on the U2000 client. In the displayed dialog
box, select the CA data file, and click Next.
Step 11 Wait until the file is imported. Leave the Export incremental script check box selected (default
setting). Click Finish.
Step 12 In the displayed dialog box, check that the eNodeB is displayed in the Selected NEs area. Set
Encrypt script and Script Executor Operation. You are advised to set Script Executor
Operation to Launch script executor and activate exported project so that the script will be
executed as soon as it is loaded. Then, click OK.
Step 13 In the displayed confirmation dialog box, click Yes. Data synchronization starts for the eNodeB.
When Success is displayed in the Result column, the CA feature has been activated.
----End
NOTE
After all the preceding steps are finished, you can run specific MML commands to verify that the parameter
settings take effect.

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) setting the CA algorithm switches; (2) adding a CA group; (3) adding cells into
the CA group.
If the local cells are active, CA is enabled after the local cells are added into the CA group. If
the local cells are inactive, activate them after adding them into the CA group. If the SCell priority
and blind SCell configuration flag are required, SCC configurations must be added to the eNodeB
involved in CA.
The activation procedure is as follows:
Step 1 Run the MOD ENODEBALGOSWITCH command to set the switches under CA Algorithm
Switch. Ensure that FreqCfgSwitch is off.
Step 2 Run the ADD CAGROUP command to add a CA group on the eNodeB and set the CA group
attribute.
Step 3 Run the ADD CAGROUPCELL command repeatedly to add at least two cells to the CA group.
In this step, set the PCell priority and the threshold for event A4 for each cell. You can set either
identical or different parameter values for the cells.
Step 4 (Optional. If you skip this step, the default parameter settings apply.) Run the ADD
CAGROUPSCELLCFG command to configure a candidate SCell for a cell that acts as the
PCell. In this step, set the SCell priority, blind SCell configuration flag, threshold for event A4,
and threshold for event A2 for the candidate SCell. You can set either identical or different
parameter values for the cells.
Step 5 (Optional; not required for a cell that has already been activated.) Run the ACT CELL command
to activate the cells.
----End
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.
Switch. 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.
Switch.
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

//Setting the options of the CA algorithm switch

MOD
ENODEBALGOSWITCH:CAALGOSWITCH=PdcchOverlapSrchSpcSwitch-1&CaCapbFiltSwitch-0&PccAn
chorSwitch-1&SccBlindCfgSwitch-1&FreqCfgSwitch-0&SccA2RmvSwitch-1&CaTrafficTrigger
Switch-0&HoWithSccCfgSwitch-0&SccModA6Switch-0&GbrAmbrJudgeSwitch-0;
//Adding an FDD CA group and setting its attribute

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

ADD
CAGROUPCELL:CAGROUPID=0,LOCALCELLID=0,ENODEBID=1234,PREFERREDPCELLPRIORITY=2,PCELL
A4RSRPTHD=-100,PCELLA4RSRQTHD=-18;
ADD
CAGROUPCELL:CAGROUPID=0,LOCALCELLID=1,ENODEBID=1234,PREFERREDPCELLPRIORITY=2,PCELL
A4RSRPTHD=-60,PCELLA4RSRQTHD=-10;
//Configuring SCells
ADD
CAGROUPSCELLCFG:LOCALCELLID=0,SCELLENODEBID=1234,SCELLLOCALCELLID=1,SCELLBLINDCFGF
LAG=TRUE,SCELLPRIORITY=2,SCELLA4OFFSET=10,SCELLA2OFFSET=-10;
ADD
LAG=TRUE,SCELLPRIORITY=3,SCELLA4OFFSET=20,SCELLA2OFFSET=-15;
//Activating cells

ACT CELL:LOCALCELLID=0;

MOD
//Adding candidate PCCs and setting their attributes

ADD
PCCFREQCFG:PCCDLEARFCN=123,PREFERREDPCCPRIORITY=1,PCCA4RSRPTHD=-100,PCCA4RSRQTHD=-
40;
ADD
30;
//Adding a candidate SCC for each candidate PCC and setting SCC attributes
ADD
SCCFREQCFG:PCCDLEARFCN=123,SCCDLEARFCN=567,SCCPRIORITY=2,SCCA2OFFSET=-10,SCCA4OFFS
ET=-5;
ADD
ET=-10;
//Activating cells

MOD
Switch-0&HoWithSccCfgSwitch-0&SccModA6Switch-1&GbrAmbrJudgeSwitch-0&AdpCaSwitch-1;
//Adding candidate PCCs and setting their attributes

ADD
40;
ADD
30;
//Adding candidate SCCs and setting their attributes

ADD
ET=-5;
ADD
ET=-10;
//Setting blind-configurable candidate SCells

ADD
LAG=TRUE;
ADD

LAG=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-5 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 may be used or a drive test (for example, using Probe) may be conducted to observe
configuration and activation of this SCell. If an RRC_CONN_RECFG message for configuring
an SCell is observed on a network that serves CA UEs, CA has been activated successfully.
Observing SCell Configuration on the U2000 Client
Step 1 Log in to the U2000 client, and then choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree on the left of the Signaling Trace Management tab page,
choose Trace Type > LTE > Application Layer > Uu Interface Trace.
Step 2 Select an NE, set tracing task parameters, and then click Finish to start signaling tracing.
Step 3 Check the tracing result for the RRC_CONN_RECFG message. The eNodeB configures or
removes an SCell for the CA UE by using an RRC_CONN_RECFG message that contains the

IE sCellToAddModList or sCellToReleaseList, as shown in Figure 6-2 or Figure 6-3,

respectively.
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 the CA UE is allocated radio resources on both the PCC and the SCC and has MAC throughput
on the SCC, as shown in Figure 6-8 and Figure 6-9, the SCell has been configured and activated
for the UE. If the CA UE is not allocated radio resources on the SCC, the feature activation has
failed.

Figure 6-8 Successful SCell configuration and activation (radio resources allocated on both the
PCC and the SCC)
Figure 6-9 Successful SCell configuration and activation (MAC throughput on the SCC)
6.4.7 Deactivation
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-6 or Table 6-7.

Table 6-6 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 eNodeBID, 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-7 Parameters related to deactivation of frequency-based or adaptive CA
MO Sheet in the Parameter Group Setting Notes

Summary
Data File
SccFreqCfg User-defined PccDlEarfcn, SccDlEarfcn Example: PccDlEarfcn =

sheet 12345, SccDlEarfcn =
56789
PccFreqCfg User-defined PccDlEarfcn 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 Turn off the subordinate switches of the CA algorithm switch.
Step 2 Remove cells from each CA group.
Step 3 Remove the CA groups.

Step 4 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 Turn off the subordinate switches of the CA algorithm switch.

Step 2 Remove SCC configurations.
Step 3 Remove PCC configurations.
----End
To deactivate adaptive CA by using MML commands, perform the following steps:
Step 1 Turn off the subordinate switches of the CA algorithm switch, including the adaptive CA switch.
Step 2 Remove SCC configurations.
Step 3 Remove PCC configurations.
----End
MML Command Examples

//Turning off the subordinate switches of the CA algorithm switch
MOD
//Removing cells from a CA group

RMV CAGROUPCELL:CAGROUPID=0,LOCALCELLID=0,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=2;
//Turning off the subordinate switches of the CA algorithm switch
MOD
//Removing SCC configurations

RMV SCCFREQCFG:PCCDLEARFCN=12345,SCCDLEARFCN=56789;

//Removing PCC configurations

RMV PCCFREQCFG:PCCDLEARFCN=12345;
//Turning off the subordinate switches of the CA algorithm switch, including the adaptive CA
switch
MOD
Switch-0&HoWithSccCfgSwitch-0&SccModA6Switch-0&GbrAmbrJudgeSwitch-1&AdpCaSwitch-0;
//Removing SCC configurations

RMV SCCFREQCFG:PCCDLEARFCN=12345,SCCDLEARFCN=56789;
//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

downlink 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:
1526728519 L.HHO.ExecAttOut.CAUser.P L.HHO.ExecSuccOut.CAUser.
CC PCC/
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

1526730595 L.CA.DLSCell.Rmv.Meas.Succ cell, and calculate the success

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 for CA UEs in a cell, and
1526729001 L.CA.DLSCell.Deact.Att calculate the success rate of
activating or deactivating SCells
1526729002 L.CA.DLSCell.Deact.Succ 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
In addition, monitor the following function subsets in "Measurement of Cell Performance (Cell)"
to collect CQI, MCS, and MAC statistics about PCells and SCells.
Function Subset Function Subset Name
ChMeas.CQI.CA.PCell PCell CQI Measurement (ChMeas.CQI.CA.PCell)
ChMeas.CQI.CA.SCell SCell CQI Measurement (ChMeas.CQI.CA.SCell)
ChMeas.MCS.CA.PCell PCell MCS Measurement (ChMeas.MCS.CA.PCell)
ChMeas.MCS.CA.SCell SCell MCS Measurement (ChMeas.MCS.CA.SCell)

Function Subset Function Subset Name
Traffic.MAC.CA.Cell CA Cell MAC Measurement (Traffic.MAC.CA.Cell)
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
The following table describes the parameters that are common to all CA configuration modes.

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.
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
Select this option only if you intend to allow
the eNodeB to configure and remove SCells
based on traffic volume.
l HoWithSccCfgSwitch


eter Source
Name
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
In frequency-based or adaptive
configuration mode, 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.
In CA-group-based configuration mode,
this option does not take effect. You are
not advised to select this option.
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.
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).
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.


eter Source
Name
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.
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
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.
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.
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.


eter Source
Name
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.
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.


eter Source
Name
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 parameters specific to CA-group-based configuration.

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
SCell CaGroupSCel This parameter specifies the local ID of a User-

Local lCfg. candidate SCell. defined
Cell ID SCellLocalCel
lId
SCell CaGroupSCel This parameter specifies the eNodeB ID of the User-

eNode lCfg. candidate SCell. defined
B ID SCelleNodeBI
d


eter Source
Name
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
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.
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.


eter Source
Name
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

The following table describes the parameters specific to frequency-based or adaptive
configuration.

eter Source
Name
OverB ENodeBAlgoS The option FreqCfgCaOverBBUsSwitch User-

BUsSw witch. specifies whether to enable inter-BBU CA or not defined
itch OverBBUsSwi in frequency-based or adaptive configuration
tch mode. This switch applies only to LTE FDD cells.
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.


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


eter Source
Name
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.
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.


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.
Carrier CaMgtCfg. This parameter specifies the offset for CA event User-
Aggreg CarrAggrA6O A6, which is triggered when the signal quality of defined
ation ffset a neighboring cell is higher than that of an SCell.
A6 l The greater the value, the lower the probability
Offset 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.


eter Source
Name
CA A6 CaMgtCfg. This parameter specifies the number of periodic User-

Report CaA6ReportA measurement reports sent after CA event A6 is defined
Amoun mount triggered. For details, see 3GPP TS 36.331.
t 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
efficiency.
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
Interval terval CA event A6 is triggered. For details, see 3GPP
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.
6.7 Troubleshooting
Alarm-triggered eNodeB Operations
(1) Carrier or Cell Unavailable
Alarm ID Alarm NE Feature ID Feature Name

Name
ALM-26200 Board eNodeB l LAOFD-001001 l LTE-A Introduction

Hardware l LAOFD-001002 l Carrier Aggregation for
Fault Downlink 2CC in
l LAOFD-070201
40MHz
l LAOFD-070202 l Flexible CA from
l LAOFD-080201 Multiple Carriers


Name
ALM-29240 Cell eNodeB l LAOFD-080202 l Inter-eNodeB CA

Unavaila l LAOFD-080207 based on Coordinated
ble BBU
l LAOFD-080208
l Inter-eNodeB CA
l LAOFD-081237
based on Relaxed
l MRFD-101222 backhaul
l Carrier Aggregation for
Uplink 2CC [Trial]
Downlink 3CC in
40MHz
Downlink 3CC in
60MHz
l Carrier Aggregation
with DL 4x4 MIMO
[Trial]
l FDD+TDD Carrier
Aggregation(LTE
FDD) [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.
(2) Clock Synchronization Capability Degraded


Name
ALM-26262 External eNodeB l LAOFD-001001 l LTE-A Introduction

Clock l LAOFD-001002 l Carrier Aggregation
Reference for Downlink 2CC in
Problem l LAOFD-070201
40MHz
l LAOFD-070202
l Flexible CA from
l LAOFD-080201 Multiple Carriers
l LAOFD-080202 l Inter-eNodeB CA
l LAOFD-080207 based on Coordinated
l LAOFD-080208 BBU
l LAOFD-081237 l Inter-eNodeB CA
based on Relaxed
l MRFD-101222
backhaul
for Uplink 2CC [Trial]
for Downlink 3CC in
40MHz
for Downlink 3CC in
60MHz
with DL 4x4 MIMO
[Trial]
l FDD+TDD Carrier
Aggregation(LTE
FDD) [Trial]
If the clock synchronization capability deteriorates because of a clock or hardware fault, the
eNodeB reports the alarm listed in the preceding table, and the following impact is generated:
l SCells cannot be configured for CA UEs that access the faulty eNodeB in scenarios of
initial access, handovers, or RRC connection re-establishments.
l Other eNodeBs cannot configure cells in the faulty eNodeB as SCells.
l SCells are removed for the CA UEs that treat cells served by the faulty eNodeB as their
PCells or SCells.
Handle the alarm according to the alarm reference. If the fault is rectified, CA services are
restored as follows:
l SCells can be configured for CA UEs that access the eNodeB in scenarios of initial access,
handovers, or RRC connection re-establishments.
l Functioning eNodeBs can configure cells in the originally faulty eNodeB as SCells.

Fault Description
After CA is enabled, the CA-related counters provided in 6.5 Performance Monitoring retain
the value of 0.
Fault Handling
If CA works in CA-group-based configuration mode, perform the following steps on the U2000
client:
Step 1 Run the LST ENODEBALGOSWITCH command to check whether FreqCfgSwitch under
CA Algorithm Switch is off.
l If the switch is off, go to Step 3.
l If the switch is on, go to Step 2.
Step 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 or ALM-29240 Cell Unavailable is reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce
non-zero values, no further action is required. If the counters retain the value of 0, go to Step
4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the DSP CAGROUPCELL command to check the running status of all CA groups
configured on the eNodeB. The running status includes information such as whether the link
between cells in one CA group is normal, whether related licenses work normally, and whether
the CA configuration state is normal.
l If the running status is normal, go to Step 5.
l If any status is abnormal, rectify the fault. Then, check whether the CA-related counters
5.
Step 5 Run the LST CAGROUPSCELLCFG command to check whether candidate SCells are
correctly configured in the eNodeB.
l If the configurations are correct, go to Step 6.
l If they are incorrectly configured, correct the configurations by following the instructions
described in 6.4 Deployment. Then, check whether the CA-related counters provided in 6.5
Performance Monitoring produce non-zero values. If the counters produce non-zero values,
no further action is required. If the counters retain the value of 0, go to Step 6.
Step 6 If CA-related hardware and data configurations are correct, check whether the fault is due to no
UE access to the network.
1. Start a Uu interface tracing task as follows: Choose Monitor > Signaling Trace >
Signaling Trace Management. In the navigation tree on the left of the Signaling Trace

Management tab page, choose Trace Type > 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 the required switch
(FreqCfgSwitch or AdpCaSwitch) under CA Algorithm Switch is on.
l If the switch is on, go to Step 3.
l If the switch is off, go to Step 2.
Step 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 or ALM-29240 Cell Unavailable is reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters
4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the LST PCCFREQCFG and LST SCCFREQCFG commands to check whether PCC
and SCC configurations are correct.
l If the configurations are 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 7 Engineering Guidelines for LAOFD-070201 Flexible CA
Carrier Aggregation Feature Parameter Description from Multiple Carriers

Flexible CA from Multiple Carriers
7.1 When to Use LAOFD-070201

If several carriers are to be selected from multiple carriers for flexible aggregation, enable
LAOFD-070201 Flexible CA from Multiple Carriers.
In addition, LAOFD-070201 Flexible CA from Multiple Carriers requires that LAOFD-001001

LTE-A Introduction and optionally LAOFD-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 LAOFD-001001 and LAOFD-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:
The EPC must comply with 3GPP Release 10 or later. To allow 2CC aggregation to reach a peak
data rate of 300 Mbit/s in 2x2 MIMO scenarios, the maximum bit rate that the UE subscribes to
in the EPC must be greater than or equal to 300 Mbit/s.
License
Deploying LAOFD-070201 Flexible CA from Multiple Carriers requires the following licenses:
l In CA-group-based configuration mode

In a CA group with more than two cells, each cell requires one sales unit of the license for
LAOFD-070201 Flexible CA from Multiple Carriers and one sales unit of the license for
If the total bandwidth of a cell and any other cell in the CA group is between 20 MHz and
40 MHz (including 40 MHz), the cell requires one sales unit of the license for
LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.
NOTE
l If any license is insufficient, a CA group with cells added does not take effect. However, the
original CA group still works. In this case, the eNodeB reports ALM-26819 Data Configuration
Exceeding Licensed Limit.
l If the license for LAOFD-070201 Flexible CA from Multiple Carriers is insufficient in an
eNodeB and FreqCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is set on
and then off, none of the cells in a CA group that includes more than two cells takes effect. In
addition, the eNodeB reports ALM-26819 Data Configuration Exceeding Licensed Limit.
l In frequency-based or adaptive configuration mode
If a cell and its intra-BBU CA partners (either PCell or SCell) form a cell set that covers
three or more frequencies, the cell requires one sales unit of the license for LAOFD-070201
Flexible CA from Multiple Carriers and one sales unit of the license for LAOFD-001001
LTE-A Introduction.
If the total bandwidth of a cell and any other cell in the set is between 20 MHz and 40 MHz
(including 40 MHz), the cell requires one sales unit of the license for LAOFD-001002
Carrier Aggregation for Downlink 2CC in 40MHz.

Feature ID Feature Model License NE Sales Unit

Name Control
Item
LAOFD-00 LTE-A LT1SA020 LTE-A eNodeB per cell

1001 Introduction CA00 Introduction
(FDD)
LAOFD-00 Carrier LT1SA040 Carrier eNodeB per cell

1002 Aggregatio CA00 Aggregation
n for for Downlink
Downlink 2CC in
2CC in 40MHz
40MHz (FDD)
LAOFD-07 Flexible CA LT1SCAD2 Flexible CA eNodeB per cell

0201 from MC00 from Multiple
Multiple Carriers
Carriers (FDD)
Others
The prerequisite features for LAOFD-070201 Flexible CA from Multiple Carriers must be
activated.

For details, see 6.4.2 Data Preparation.
7.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 8 Engineering Guidelines for LAOFD-070202 Inter-eNodeB
Carrier Aggregation Feature Parameter Description CA based on Coordinated BBU

Inter-eNodeB CA based on Coordinated BBU

Enable LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU if operators require
carrier aggregation between inter-BBU cells in multi-BBU interconnection scenarios.
In addition, LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU requires that

LAOFD-001001 LTE-A Introduction and optionally LAOFD-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 LAOFD-001001 and LAOFD-001002.

This CA feature shares system resources with the SFN, UL CoMP, and CSPC features. Before
deploying this CA feature, contact Huawei engineers for a resource audit.
8.3 Planning
RF Planning
Network Planning
Deploy multi-BBU interconnection, in addition to network planning described in 6.3
Planning.

Hardware Planning
Use LBBPd or UBBP as baseband processing units. Do not use LBBPc or UMDUa3. For the
antenna modes of cells supported by LBBPd and UBBP boards, see hardware planning described
in 6.3 Planning.
8.4 Deployment
CA works between two or three inter-frequency cells.
8.4.1 Requirements
None
NEs
In addition to the requirements described in 6.4.1 Requirements, CA in centralized multi-BBU
interconnection scenarios has the following requirements:
l A USU is required for data exchange between BBUs.

l The same software version runs on the BBUs to be interconnected.
l LMPT and LBBPc cannot be used for USU-based multi-BBU interconnection.
The BBUs must be time-synchronized.
License
Deploying LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU requires the
following licenses:
l In CA-group-based configuration mode, each eNodeB on which any CA group includes an

inter-eNodeB cell requires one sales unit of the license for LAOFD-070202 Inter-eNodeB
CA based on Coordinated BBU.
l In frequency-based or adaptive configuration mode, if FreqCfgCaOverBBUsSwitch
under ENodeBAlgoSwitch.OverBBUsSwitch is on, each eNodeB on which any cell is
accompanied by an inter-BBU SCell requires one sales unit of the license for
LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.
In addition, each cell involved in CA requires one sales unit of the license for LAOFD-001001
LTE-A Introduction and, if the total bandwidth of the cells is greater than 20 MHz and less than
or equal to 40 MHz, one sales unit of the license for LAOFD-001002 Carrier Aggregation for

Feature ID Feature Model License NE Sales Unit

Name Control Item
LAOFD-00 LTE-A LT1SA020C LTE-A eNodeB per cell

1001 Introduction A00 Introduction
(FDD)
LAOFD-00 Carrier LT1SA040C Carrier eNodeB per cell

1002 Aggregation A00 Aggregation for
for Downlink Downlink 2CC
2CC in in 40MHz
40MHz (FDD)
LAOFD-07 Inter-eNodeB LT1SCAFB Inter-eNodeB eNodeB per eNodeB

0202 CA based on CB00 CA based on
Coordinated Coordinated
BBU BBU (FDD)
Others
The prerequisite features for LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
must be activated.

The parameters described in 6.4.2 Data Preparation apply to LAOFD-070202 Inter-eNodeB
CA based on Coordinated BBU. In addition, make data preparation as follows:
l In CA-group-based configuration mode, set the following switch on. In addition, 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.
Param Paramete Setting Notes Data Source

eter r ID
Name
CA ENodeBA The DistributeCloudbbCaSwitch User-defined

Algorit lgoSwitch. (DistributeCloudbbCaSwitch) option
hm CaAlgoSw specifies whether to enable CA in the
Switch itch distributed multi-BBU interconnection
architecture.
l If this option is selected, this type of CA
applies to the cells served by the
eNodeB.
l If this option is deselected, this type of
CA is disabled for the cells served by
the eNodeB.

l In frequency-based or adaptive configuration mode, set the following switches on.
Param Paramete Setting Notes Data Source

eter r ID
Name
OverB ENodeBA The option FreqCfgCaOverBBUsS- User-defined

BUsSw lgoSwitch. witch specifies whether to enable inter-
itch OverBBUs BBU CA or not in frequency-based or
Switch adaptive configuration mode. This switch
applies only to LTE FDD cells. 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.
CA ENodeBA The DistributeCloudbbCaSwitch User-defined

Algorit lgoSwitch. (DistributeCloudbbCaSwitch) option
hm CaAlgoSw specifies whether to enable CA in the
Switch itch distributed multi-BBU interconnection
architecture.
l If this option is selected, this type of CA
applies to the cells served by the
eNodeB.
l If this option is deselected, this type of
CA is disabled for the cells served by
the eNodeB.
NOTE
For details about USU configurations, see USU3900-based Multi-BBU Interconnection and
USU3910-based Multi-BBU Interconnection.
8.4.3 Precautions
In addition to the precautions described in 6.4.3 Precautions, a penalty mechanism applies to
eX2 route setups. If three consecutive attempts of an eNodeB to set up an eX2 route to an inter-
BBU cell fail, the eNodeB prohibits the subsequent 30 attempts on the route.

Besides the hardware adjustment described in 6.4.4 Hardware Adjustment, CA in multi-BBU
interconnection scenarios requires a USU to connect BBUs for data exchange between BBPs.

For details about the cable connections, see USU3900-based Multi-BBU Interconnection and
USU3910-based Multi-BBU Interconnection.
8.4.5 Activation
l If the network is deployed using the centralized multi-BBU interconnection architecture,
perform the operations described in 6.4.5 Activation on each BBU.
l If the network is deployed using the distributed multi-BBU interconnection architecture,
perform the operations described in 6.4.5 Activation on each BBU and run the following
command for the serving eNodeB of each candidate PCell to set
DistributeCloudbbCaSwitch on:
MOD ENODEBALGOSWITCH:CAALGOSWITCH=DistributeCloudbbCaSwitch-1;

perform the operations described in 6.4.5 Activation on each BBU and run the following
command for each BBU to set FreqCfgCaOverBBUsSwitch on:
MOD ENODEBALGOSWITCH:OVERBBUSSWITCH=FreqCfgCaOverBBUsSwitch-1;

perform the operations described in 6.4.5 Activation on each BBU and also perform the
following steps:
Run the following command on each BBU to set FreqCfgCaOverBBUsSwitch on:
Run the following command on the serving eNodeB of each candidate PCC to set
DistributeCloudbbCaSwitch on:

8.4.7 Deactivation
delete inter-BBU cells from each CA group on a BBU. Inter-BBU cells have different
eNodeB IDs from the local BBU. The following is an example of the command:

run the following command for the serving eNodeB of each candidate PCell to set
DistributeCloudbbCaSwitch off:

run the following command on each BBU to set FreqCfgCaOverBBUsSwitch off:


run the following command for the serving eNodeB of each candidate PCell to set
DistributeCloudbbCaSwitch off:


8.7 Troubleshooting
Troubleshooting described in 6.7 Troubleshooting applies to LAOFD-070202 Inter-eNodeB
CA based on Coordinated BBU with only an exception at step 4 in the fault handling procedure
for CA in CA-group-based configuration mode. In step 4, run the command on each BBU to
check whether the configurations are consistent between the eNodeBs.
l If the configurations are consistent, go to step 5.

l If the configurations are inconsistent, follow the instructions described in 6.4.5.5 Using
MML Commands to configure CaGroupCell MOs to be consistent between the BBUs.
Then, check whether the CA-related counters provided in 6.5 Performance Monitoring
produce non-zero values. If the counters produce non-zero values, no further action is
required. If the counters retain the value of 0, go to step 5.

Carrier Aggregation Feature Parameter Description CA based on Relaxed backhaul

Inter-eNodeB CA based on Relaxed backhaul

Enable LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul 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, LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul requires that
LAOFD-001001 LTE-A Introduction and optionally LAOFD-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 LAOFD-001001 and LAOFD-001002.

9.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 cannot act as the PCells for CA UEs.

l Micro cells cannot act as the PCells for CA UEs.
9.4 Deployment
Deploy this CA feature on inter-eNodeB inter-frequency cells.
9.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 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul requires the licenses
listed in this section.
When RelaxedBackhaulCaSwitch under ENodeBAlgoSwitch.CaAlgoSwitch is on:
l In CA-group-based configuration mode, the serving eNodeB of each cell in a CA group

that includes relaxed-backhaul-based inter-eNodeB cells requires one sales unit of the
license for LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul. In addition,
each cell involved in CA requires one sales unit of the license for LAOFD-001001 LTE-
A Introduction and, if the total bandwidth of the cells is greater than 20 MHz and less than
or equal to 40 MHz, one sales unit of the license for LAOFD-001002 Carrier Aggregation
for Downlink 2CC in 40MHz.
l In frequency-based or adaptive configuration mode, if any cell served by an eNodeB acts
as a PCell and is accompanied by an inter-eNodeB SCell for relaxed-backhaul-based CA,
each of the eNodeBs requires one sales unit of the license for LAOFD-080201 Inter-
eNodeB CA based on Relaxed backhaul. In addition, each cell involved in CA requires one
sales unit of the license for LAOFD-001001 LTE-A Introduction and, if the total bandwidth
of the cells is greater than 20 MHz and less than or equal to 40 MHz, one sales unit of the
license for LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz.
Feature Feature Model License Control NE Sales

ID Name Item Unit
LAOFD-00 LTE-A LT1SA020C LTE-A Introduction eNod per

1001 Introduction A00 (FDD) eB cell


ID Name Item Unit
LAOFD-00 Carrier LT1SA040C Carrier Aggregation eNod per

1002 Aggregation A00 for Downlink 2CC in eB cell
for Downlink 40MHz (FDD)
2CC in
40MHz
LAOFD-08 Inter-eNodeB LT1S0IPRA Inter-eNodeB CA eNod per

0201 CA based on N01 based on Relaxed eB eNode
Relaxed backhaul (per B
backhaul eNodeB)
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 LAOFD-080201
Inter-eNodeB CA based on Relaxed backhaul.
l Set the following switches 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 or not in frequency-based or
ch adaptive configuration mode. This
switch applies only to FDD cells or
FDD+TDD cells. 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.
9.4.3 Precautions
In addition to the precautions described in 6.4.3 Precautions, note that:

l Frequency-based or adaptive configuration mode is recommended for relaxed-backhaul-

based inter-eNodeB CA. To use the CA-group-based configuration mode, each BBU must
be configured with CaGroup, CaGroupCell, and CaGroupSCellCfg MOs. However,
frequency-based and adaptive configuration modes do not have this requirement.
l If three consecutive attempts of an eNodeB to set up an eX2 route to an inter-eNodeB cell
fail, the eNodeB prohibits the subsequent 30 attempts on the route.

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.
9.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:

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 9-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.
9.4.7 Deactivation
l Deactivating CA between inter-eNodeB macro cells
Run the MOD ENODEBALGOSWITCH command with the
RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch) option of the CA Algorithm
Switch parameter deselected.

l Deactivating CA between macro and micro cells
Run the MOD ENODEBALGOSWITCH command with the HetNetCaSwitch
(HetNetCaSwitch) option of the CA Algorithm Switch parameter deselected.
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

9.7 Troubleshooting
In addition to the troubleshooting methods described in 6.7 Troubleshooting, the following
method is available for troubleshooting inter-eNodeB CA based on relaxed backhaul:
Step 1 On the U2000 client, check whether ALM-25888 SCTP Link Fault or ALM-25952 User Plane
Path Fault is reported.
l If either alarm is reported, handle the alarm and then check whether the CA-related counters
provided in 6.5 Performance Monitoring produce non-zero values.
If the counters produce non-zero values, no further action is required.
If the counters retain the value of 0, go to step 2.
l If neither alarm is reported, go to step 2.
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 10 Engineering Guidelines for LAOFD-080202 Carrier
Carrier Aggregation Feature Parameter Description Aggregation for Uplink 2CC [Trial]
10
LAOFD-080202 Carrier Aggregation for Uplink
Engineering Guidelines for
2CC [Trial]

Enable LAOFD-080202 when operators require aggregation of two uplink CCs.

10.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.
10.4 Deployment
Deploy this CA feature on two inter-frequency cells served by either the same eNodeB or
different eNodeBs that are interconnected in multi-BBU interconnection scenarios.

10.4.1 Requirements
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. In addition, the EPC and
UEs must meet the following requirement:
l The EPC must comply with 3GPP Release 10 or later. To allow uplink 2CC aggregation
to reach a peak data rate of 100 Mbit/s in 2x2 MIMO scenarios, the maximum bit rate that
the UE subscribes to in the EPC must be greater than or equal to 300 Mbit/s.
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
If CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter is on for a cell, the cell
can be used for uplink CA. LAOFD-080202 Carrier Aggregation for Uplink 2CC is a trial feature
in eRAN8.1 and therefore is not under license control. However, for this uplink CA feature to
take effect, downlink CA must be licensed:
l If the total bandwidth of the downlink aggregated cells is less than or equal to 20 MHz,
each cell requires one sales unit of the license for LAOFD-001001 LTE-A Introduction.
l If the total bandwidth of the downlink aggregated cells is between 20 MHz and 40 MHz
(including 40 MHz), each cell requires one sales unit of the license for LAOFD-001001
LTE-A Introduction and one sales unit of the license for LAOFD-001002 Carrier
Aggregation for Downlink 2CC in 40MHz.
Feature Feature Model License NE Sales Unit

ID Name Control
Item

(FDD)

01002 Aggregation A00 Aggregation
for Downlink for Downlink
2CC in 2CC in
40MHz 40MHz
(FDD)

Others

Make data preparation as described in 6.4.2 Data Preparation. In addition, set the following
switches 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.
Uplink CellAlgoSwitc The SchedulerCtrlPowerSwitch User-defined

schedule h.UlSchSwitch option of this parameter controls cell-
switch level functions related to uplink
scheduling. Set this switch on if you
intend to enable uplink 2CC
aggregation.
10.4.3 Precautions

For details, see 6.4.4 Hardware Adjustment.
10.4.5 Activation
In addition to the steps in 6.4.5 Activation, perform the following steps on the U2000 client:
Step 1 Run the MOD CELLALGOSWITCH command with the SchedulerCtrlPowerSwitch

(SchedulerCtrlPowerSwitch) option of the Uplink schedule switch parameter selected.
MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=SchedulerCtrlPowerSwitch-1;
Step 2 Run the MOD CAMGTCFG command with the CaUl2CCSwitch(CaUl2CCSwitch) option
of the Cell Level CA Algorithm Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaUl2CCSwitch-1;
----End


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 10-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
10.4.7 Deactivation
Step 1 On the U2000 client, run the MOD CAMGTCFG command with the CaUl2CCSwitch
(CaUl2CCSwitch) option of the Cell Level CA Algorithm Switch parameter deselected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaUl2CCSwitch-0;
Step 2 (Optional) If uplink scheduler-based power control is not required, run the MOD
CELLALGOSWITCH command with the SchedulerCtrlPowerSwitch
(SchedulerCtrlPowerSwitch) option of the Uplink schedule switch parameter deselected.
MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=SchedulerCtrlPowerSwitch-0;
----End

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

10.7 Troubleshooting

11 Engineering Guidelines for LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz and
eRAN LAOFD-080208 Carrier Aggregation for Downlink 3CC in
Carrier Aggregation Feature Parameter Description 60MHz
11
LAOFD-080207 Carrier Aggregation for
Downlink 3CC in 40MHz and LAOFD-080208

Carrier Aggregation for Downlink 3CC in
60MHz
11.1 When to Use LAOFD-080207 and LAOFD-080208

When operators require aggregation of three downlink CCs:
l If the total bandwidth is less than or equal to 40 MHz, enable only LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz.
l If the total bandwidth is greater than 40 MHz and less than or equal to 60 MHz, enable both
LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz and LAOFD-080208
Carrier Aggregation for Downlink 3CC in 60MHz.

11.3 Planning
RF Planning
Network Planning

Hardware Planning
In addition to hardware planning described in 6.3 Planning, select BBPs as follows:
Do not use LBBPc as the BBP to serve the PCells of CA UEs.
11.4 Deployment
Deploy this CA feature on three inter-frequency cells served by either the same eNodeB or
different eNodeBs that are interconnected in multi-BBU interconnection scenarios.
11.4.1 Requirements
None
NEs
The requirements described in 6.4.1 Requirements must be fulfilled. Specifically:
l The EPC must comply with 3GPP Release 10 or later and support UE categories 9 and 10.
To allow downlink 3CC aggregation to reach a peak data rate of 450 Mbit/s in 2x2 MIMO
scenarios, the maximum bit rate that the UE subscribes to in the EPC must be greater than
or equal to 450 Mbit/s.
License
A cell can act as a PCell in downlink 3CC aggregation only if CaDl3CCSwitch under the
CaMgtCfg.CellCaAlgoSwitch parameter is on for the cell. LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz and LAOFD-080208 Carrier Aggregation for
Downlink 3CC in 60MHz are both under license control in eRAN8.1. Each cell involved in 3CC
aggregation requires one sales unit of the license for LAOFD-080207 Carrier Aggregation for
Downlink 3CC in 40MHz or LAOFD-080208 Carrier Aggregation for Downlink 3CC in
60MHz. For the two features to take effect, their prerequisite features must be licensed. See the
following table.
Feature Feature Name Model License NE Sales Unit

ID Control Item

(FDD)

Feature Feature Name Model License NE Sales Unit

ID Control Item

01002 Aggregation for A00 Aggregation
Downlink 2CC for Downlink
in 40MHz 2CC in 40MHz
(FDD)
LAOFD-0 Carrier LT1SCAD4 Carrier eNodeB per cell

80207 Aggregation for 0M00 Aggregation
(FDD)
LAOFD-0 Carrier LT1SCAD6 Carrier eNodeB per cell

80208 Aggregation for 0M00 Aggregation
(FDD)
Others

Make data preparation as described in 6.4.2 Data Preparation. In addition, set the following
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.
11.4.3 Precautions


11.4.5 Activation
Step 1 Configure cells or frequencies.
l In CA-group-based configuration mode, perform the MML-based procedure described in
6.4.5 Activation with the following exceptions: Add three cells to the CA group in step 3,
and configure two candidate SCells for each PCell in step 4.
l In frequency-based or adaptive configuration mode, perform the MML-based procedure
described in 6.4.5 Activation with the following exception: Add at least two candidate SCCs
and set their attributes for each candidate PCC in step 3.
Step 2 On the U2000 client, run the MOD CAMGTCFG command with the CaDl3CCSwitch
(CaDl3CCSwitch) option of the Cell Level CA Algorithm Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1;
----End

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


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
1526732908 L.Traffic.User.PCell.DL.
3CC.Max
1526732915 L.Traffic.User.PCell.DL. Average and maximum numbers of

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 Total duration in which all SCells are

active for 3CC CA UEs that treat the local
cell as their PCell
1526733012 L.Thrp.bits.DL.3CC.CAUser Total downlink PDCP-layer traffic

volume of 3CC CA UEs that treat the
local cell as their PCell and have all their
SCells activated


Carrier Aggregation Feature Parameter Description Aggregation with DL 4x4 MIMO [Trial]
12
LAOFD-081237 Carrier Aggregation with DL 4x4
MIMO [Trial]

Use LAOFD-081237 when operators require CA on a network where one or more frequencies
support 4x2 MIMO or 4x4 MIMO.
In addition, LAOFD-081237 requires that LAOFD-001001 LTE-A Introduction and optionally

LAOFD-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 LAOFD-001001
and LAOFD-001002.

12.3 Planning
RF Planning
Network Planning
Hardware Planning
For details about hardware planning, see 6.3 Planning.

12.4 Deployment
CA applies to two single-carrier cells or a dual-carrier sector. For details about how to deploy a
dual-carrier sector, see Cell Management.
12.4.1 Requirements
The requirements described in 6.4.1 Requirements must be fulfilled. Additionally:
The EPC must comply with 3GPP Release 10 or later. To allow downlink CA to reach a peak
data rate of 300 Mbit/s or 450 Mbit/s in downlink 4x4 MIMO scenarios, the maximum bit rate
that the UE subscribes to in the EPC cannot be less than 300 Mbit/s or 450 Mbit/s, respectively.
License
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO is a trial feature in eRAN8.1 and
therefore is not under license control. However, for this feature to take effect, the features listed
in the following table must be licensed.
The license for LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz is required
only if the total bandwidth of aggregated cells is between 20 MHz and 40 MHz (including 40
MHz).

ID Name Item Unit
LAOFD-0 LTE-A LT1SA020 LTE-A Introduction eNodeB per cell

01001 Introduction CA00 (FDD)
LAOFD-0 Carrier LT1SA040 Carrier Aggregation eNodeB per cell

01002 Aggregation CA00 for Downlink 2CC in
2CC in
40MHz
LOFD-001 DL 4x2 LT1S0D4I2 DL 4x2 MIMO (FDD) eNodeB per cell

003 MIMO O00
LOFD-001 DL 4x4 LT1S0DMI DL 4x4 MIMO (FDD) eNodeB per cell

060 MIMO MO00
Others

For details, see 6.4.2 Data Preparation.

12.4.3 Precautions

12.4.5 Activation
For details, see 6.4.5 Activation.

12.4.7 Deactivation
For details, see 6.4.7 Deactivation.



eRAN 13 Engineering Guidelines for MRFD-101222 FDD+TDD
Carrier Aggregation Feature Parameter Description Carrier Aggregation(LTE FDD) [Trial]
13
MRFD-101222 FDD+TDD Carrier Aggregation
(LTE FDD) [Trial]
13.1 When to Use MRFD-101222

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

13.3 Planning
RF Planning
Network Planning
For details about network planning for FDD carriers, see 6.3 Planning. For details about network
planning for TDD carriers, see Carrier Aggregation in LTE TDD Feature Documentation for
eRAN TDD 8.1.
Hardware Planning
For details about hardware planning for FDD carriers, see 6.3 Planning. For details about
hardware planning for TDD carriers, see Carrier Aggregation in LTE TDD Feature
Documentation for eRAN TDD 8.1.
In addition, make the hardware plan for FDD+TDD CA with the following requirements taken
into consideration:

l If an FDD cell on an LBBPd4 board acts as the PCell for a CA UE, downlink FDD+TDD
3CC or 4CC CA will not work.
l The PCell and SCells of a CA UE cannot be configured on a single BBP that works for
both FDD and TDD.
l The LTE TDD cells whose carriers are to be aggregated for a single CA UE must be
configured in the same BBU.
l FDD+TDD CA does not apply to cells on LBBPc boards.
13.4 Deployment
CA applies to two single-carrier cells or a dual-carrier sector. For details about how to deploy a
dual-carrier sector, see Cell Management.
13.4.1 Requirements
The requirements described in 6.4.1 Requirements must be fulfilled. Additionally:
l The EPC must comply with 3GPP Release 12 or later. To allow downlink 2FDD+2TDD
aggregation to reach a peak data rate of 520 Mbit/s, the maximum bit rate that the UE
subscribes to in the EPC must be greater than or equal to 520 Mbit/s.
License
FDD+TDD CA is a trial feature in eRAN8.1 and therefore is not under license control. However,
for this feature to take effect, its prerequisite features must be licensed:
l If at least two FDD carriers are involved in FDD+TDD CA and the total bandwidth of the
FDD carriers does not exceed 20 MHz, each of the cells requires one sales unit of the license
for LAOFD-001001 LTE-A Introduction.
l If at least two FDD carriers are involved in FDD+TDD CA and the total bandwidth of the
FDD carriers is between 20 MHz and 40 MHz (including 40 MHz), each of the cells requires
one sales unit of the license for LAOFD-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.

ID Name Item Unit
LAOFD-0 LTE-A LT1SA020 LTE-A Introduction eNodeB per cell

01001 Introduction CA00 (FDD)
LAOFD-0 Carrier LT1SA040 Carrier Aggregation eNodeB per cell

01002 Aggregation CA00 for Downlink 2CC in
2CC in 40MHz
LAOFD-0 Carrier LT1SCAD Carrier Aggregation eNodeB per cell

80207 Aggregation 40M00 for Downlink 3CC in
3CC in 40MHz
LAOFD-0 Carrier LT1SCAD Carrier Aggregation eNodeB per cell

80208 Aggregation 60M00 for Downlink 3CC in
3CC in 60MHz
TDLAOF LTE-A LT1SLTE LTE-A Introduction eNodeB per cell

D-001001 Introduction AID01 (TDD)
TDLAOF Carrier LT1SC2C4 Carrier Aggregation eNodeB per cell

D-001002 Aggregation 0M00 for Downlink 2CC in
for Downlink 40MHz (TDD)
2CC in 40MHz
TDLAOF Carrier LT1SCAD Carrier Aggregation eNodeB per cell

D-081405 Aggregation 3CC00 for Downlink 3CC
for Downlink (TDD)
3CC
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
aggregation, set this switch on.
l To disable downlink 3CC
aggregation, set this switch off.
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.
13.4.3 Precautions


13.4.5 Activation
In addition to the steps in 6.4.5 Activation, perform the following steps on the U2000 client:
Step 1 For the eNodeB that serves the PCell, run the MOD CAMGTCFG command with the
InterFddTddCaSwitch(InterFddTddCaSwitch) option of the Cell Level CA Algorithm
Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=InterFddTddCaSwitch-1;
Step 2 (Optional) To enable downlink FDD+TDD 3CC aggregation, run the MOD CAMGTCFG
command with Local cell ID set to the ID of the intended PCell and with the CaDl3CCSwitch
(CaDl3CCSwitch) option of the Cell Level CA Algorithm Switch parameter selected.
Step 3 (Optional) To enable downlink FDD+TDD 4CC aggregation, run the MOD CAMGTCFG
command with Local cell ID set to the ID of the intended PCell and with both the
CaDl3CCSwitch(CaDl3CCSwitch) and CaDl4CCSwitch(CaDl4CCSwitch) options of the
Cell Level CA Algorithm Switch parameter selected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=CaDl3CCSwitch-1&CaDl4CCSwitch-1;
Step 4 (Optional) To enable downlink FDD+TDD 2CC aggregation in relaxed backhaul scenarios, run
the MOD ENODEBALGOSWITCH command with the RelaxedBackhaulCaSwitch
(RelaxedBackhaulCaSwitch) option of the CA Algorithm Switch parameter selected.
MOD ENODEBALGOSWITCH:LOCALCELLID=0,CAALGOSWITCH=RelaxedBackhaulCaSwitch-1;
In addition, in frequency-based or adaptive configuration mode, run the following command on

each eNodeB:
----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 13-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
13.4.7 Deactivation
In addition to the steps in 6.4.7 Deactivation, perform the following step on the U2000 client:
Run the MOD CAMGTCFG command with the InterFddTddCaSwitch

(InterFddTddCaSwitch) option of the Cell Level CA Algorithm Switch parameter
deselected.
MOD CAMGTCFG:LOCALCELLID=0,CELLCAALGOSWITCH=InterFddTddCaSwitch-0;

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 9.5 Performance
Monitoring and Table 13-4.
Table 13-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 13-4.
counters in addition to those listed in 11.5 Performance Monitoring and Table 13-4.

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 and have all SCells activated for
downlink FDD+TDD 3CC CA
A.
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
counters in addition to those listed in Table 13-4.
counters in addition to those listed in Table 13-4 and Table 13-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

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
Carrier Aggregation Feature Parameter Description 14 Parameters
14 Parameters
Table 14-1 Parameters
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
ENodeB CaAlgo MOD LAOFD Intra- Meaning:

AlgoSwi Switch ENODE -001001 Band Indicates whether to enable carrier aggregation (CA).
tch BALGO 01 Carrier The switches are described as follows:
SWITC LAOFD Aggrega
H -001001 tion for PdcchOverlapSrchSpcSwitch: Indicates whether CA
LST 02 Downlin UEs regard the overlapping PDCCH candidates of the
ENODE k 2CC in common search space and UE-specific search space,
LAOFD 20MHz
BALGO which are transmitted by the primary serving cell
-001002
SWITC Inter- (PCell), as PDCCH candidates of the common or UE-
01 /
H Band specific search space. If this switch is On and if a CA
TDLAO
Carrier UE supports cross-carrier scheduling and is assigned a
FD-001
Aggrega carrier indicator field (CIF), the CA UE determines that
002
tion for the overlapping PDCCH candidates belong to the
LAOFD Downlin common search space; otherwise, the CA UE
-001002 k 2CC in determines that the overlapping PDCCH candidates
02 / 20MHz belong to the UE-specific search space. If this switch is
TDLAO Off, the CA UE always determines that the overlapping
FD-001 Carrier
PDCCH candidates belong to the common search space.
00102 Aggrega
tion for CaCapbFiltSwitch: Indicates how the eNodeB performs
LAOFD Downlin
-070201 CA after a CA UE reports the combination of frequency
k 2CC in bands. If the UECapabilityInformation message
/ 40MHz
TDLAO reported by a UE does not contain the IE
FD-070 Support supportedBandwidthCombinationSet, the eNodeB
201 of UE performs CA as follows: If this option is Off, the
Categor eNodeB configures a secondary component carrier
LAOFD y6 (SCC) for the UE using the default value of the IE
-070202 supportedBandwidthCombinationSet defined in 3GPP
Flexible
CA from specifications. If this option is On, the eNodeB does not
configure an SCC for the UE.

eRAN

nd
TDLAO Multiple PccAnchorSwitch: Indicates whether to enable the

FD-001 Carriers anchor function of the primary component carrier
00111 Inter- (PCC). This switch is not subject to the setting of
LAOFD eNodeB FreqCfgSwitch of the CaAlgoSwitch parameter. The
-080202 CA anchor function of the PCC is enabled only when this
based on switch is On.
LAOFD
-080201 Coordin SccBlindCfgSwitch: Indicates whether a secondary
ated serving cell (SCell) can be blindly configured. If this
LBFD-0 BBU
0201805 switch is On, the eNodeB configures a candidate SCell
/ Intra- as an SCell for a CA UE without A4 measurements. If
TDLBF band this switch is Off, the eNodeB delivers A4 measurement
D-00201 Carrier configurations for measuring the frequency of a
805 Aggrega candidate SCell before configuring the candidate SCell
tion for as an SCell for the CA UE.
LOFD-0 Downlin
0105401 k 2CC in FreqCfgSwitch: Indicates whether to configure CA
/ 30MHz based on frequencies or CA groups. If this switch is On,
TDLOF CA can be configured based on frequencies. If this
D-00105 Carrier switch is Off, CA can be configured based on CA
401 Aggrega groups.
tion for
Uplink SccA2RmvSwitch: Indicates whether to deliver A2
2CC measurement configurations for measuring a secondary
Inter- component carrier (SCC) after the SCC is configured.
eNodeB This option is not subject to the setting of the
CA FreqCfgSwitch option of the CaAlgoSwitch parameter.
based on If FreqCfgSwitch is Off and SccBlindCfgSwitch is On,
relaxed the setting of SccA2RmvSwitch does not take effect.
backhau The eNodeB delivers A2 measurement configurations
l for measuring an SCC after the SCC is configured only
when SccA2RmvSwitch is On.
Service
Based CaTrafficTriggerSwitch: Indicates whether to add and
Inter- remove an SCC based on the traffic volume of a CA UE
frequenc after the UE accesses the network. This switch is not
y subject to the settings of FreqCfgSwitch. If the
Handov CarrierMgtSwitch parameter is set to Off and
er CaTrafficTriggerSwitch is On, an added SCC cannot be
Camp & removed based on the traffic volume of a CA UE.
Handov HoWithSccCfgSwitch: Indicates whether an SCC can
er Based be configured for a CA UE during a handover. It is
on SPID recommended that the SccA2RmvSwitch option of the
CaAlgoSwitch parameter be selected when the
HoWithSccCfgSwitch option of the same parameter is
selected. If the SccA2RmvSwitch option is deselected,
UEs cannot report the signals of neighboring cells that
operate on the frequencies of their SCell, affecting SCell

eRAN

nd
configuration in handovers. 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.
GbrAmbrJudgeSwitch: 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,
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,

eRAN

nd
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.
DistributeCloudbbCaSwitch: 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.
FreqPriBasedHoCaFiltSwitch: 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.
CaSccSuspendSwitch: Indicates whether the eNodeB
stops scheduling carrier aggregation (CA) UEs in their
secondary serving cells (SCells) when the channel
quality for the CA UEs is poor. If this option is selected,
the eNodeB stops scheduling CA UEs when the channel
quality for the CA UEs is worse than that indicated by
the SccDeactCqiThd parameter value in single-
codeword transmission. The eNodeB resumes
scheduling CA UEs in their SCells when the channel
quality for the CA UEs is better than that indicated by
the SccDeactCqiThd parameter value plus 2 in single-
codeword transmission.
GUI Value Range: PdcchOverlapSrchSpcSwitch
(PdcchOverlapSrchSpcSwitch), CaCapbFiltSwitch

eRAN

nd
(CaCapbFiltSwitch), PccAnchorSwitch
(PccAnchorSwitch), SccBlindCfgSwitch
(SccBlindCfgSwitch), FreqCfgSwitch
(FreqCfgSwitch), SccA2RmvSwitch
(SccA2RmvSwitch), CaTrafficTriggerSwitch
(CaTrafficTriggerSwitch), HoWithSccCfgSwitch
(HoWithSccCfgSwitch), SccModA6Switch
(SccModA6Switch), GbrAmbrJudgeSwitch
(GbrAmbrJudgeSwitch), MtaAlgSwitch
(MtaAlgSwitch), RelaxedBackhaulCaSwitch
(RelaxedBackhaulCaSwitch), AdpCaSwitch
(AdpCaSwitch), CaHoControlSwitch(CaHoControlS-
witch), DistributeCloudbbCaSwitch(Distribute-
CloudbbCaSwitch), SccSmartCfgSwitch
(SccSmartCfgSwitch), IdleModePccAnchorSwitch
(IdleModePccAnchorSwitch), FreqPriBasedHoCa-
FiltSwitch(FreqPriBasedHoCaFiltSwitch),
CaSccSuspendSwitch(CaSccSuspendSwitch)
Unit: None
Actual Value Range: PdcchOverlapSrchSpcSwitch,
CaCapbFiltSwitch, PccAnchorSwitch, SccBlindCfgS-
witch, FreqCfgSwitch, SccA2RmvSwitch,
CaTrafficTriggerSwitch, HoWithSccCfgSwitch,
SccModA6Switch, GbrAmbrJudgeSwitch,
MtaAlgSwitch, RelaxedBackhaulCaSwitch,
AdpCaSwitch, CaHoControlSwitch, Distribute-
CloudbbCaSwitch, SccSmartCfgSwitch,
IdleModePccAnchorSwitch, FreqPriBasedHoCaFiltS-
witch, CaSccSuspendSwitch
Default Value: PdcchOverlapSrchSpcSwitch:On,
CaCapbFiltSwitch:Off, PccAnchorSwitch:Off,
SccBlindCfgSwitch:Off, FreqCfgSwitch:Off,
SccA2RmvSwitch:On, CaTrafficTriggerSwitch:Off,
HoWithSccCfgSwitch:Off, SccModA6Switch:Off,
GbrAmbrJudgeSwitch:On, MtaAlgSwitch:Off,
RelaxedBackhaulCaSwitch:Off, AdpCaSwitch:Off,
CaHoControlSwitch:Off,
DistributeCloudbbCaSwitch:Off,
SccSmartCfgSwitch:Off,
IdleModePccAnchorSwitch:Off,
FreqPriBasedHoCaFiltSwitch:Off,
CaSccSuspendSwitch:Off

eRAN

nd
CaMgtC CellCaA MOD MRFD- FDD Meaning:

fg lgoSwitc CAMG 101231 +TDD CaDl3CCSwitch(CaDl3CCSwitch): Indicates whether
h TCFG MRFD- Carrier to enable aggregation of three component carriers in the
LST 101222 Aggrega downlink. This type of aggregation works if this option
CAMG tion is selected and at least two SccFreqCfg MOs or three
TCFG (LTE CaGroupCell MOs are configured.
TDD)
FDD CaUl2CCSwitch(CaUl2CCSwitch): Indicates whether
+TDD to enable aggregation of two component carriers in the
Carrier uplink.This type of aggregation works if this option is
Aggrega selected and at least one SccFreqCfg MO or two
tion CaGroupCell MOs are configured.
(LTE CaDl4CCSwitch(CaDl4CCSwitch): Indicates whether
FDD) 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(InterFddTddCaSwitch):
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(Tdd2CCDlCaEnhan-
ceSwitch): Indicates whether to enable enhanced DL
ACK demodulation when two TDD component carriers
are aggregated. This option does not apply to LTE FDD.
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)
Unit: None
Actual Value Range: CaDl3CCSwitch,
CaUl2CCSwitch, CaDl4CCSwitch, InterFddTddCaS-
witch, Tdd2CCDlCaEnhanceSwitch
Default Value: CaDl3CCSwitch:Off,
CaUl2CCSwitch:Off, CaDl4CCSwitch:Off,
InterFddTddCaSwitch:Off,
Tdd2CCDlCaEnhanceSwitch:Off

eRAN

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 Unit: None
-070201 k 2CC in
Actual Value Range: 0~65535
LAOFD 20MHz
-070202 Default Value: 65535
Carrier
LAOFD Aggrega
-080201 tion for
Downlin
LAOFD
k 2CC in
-080202
40MHz
LAOFD
-080207 Support
of UE
LAOFD Categor
-080208 y6
TDLAO Flexible
FD-001 CA from
00111 Multiple
TDLAO Carriers
FD-001
Inter-
002
eNodeB
TDLAO CA
FD-070 based on
201 Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier
Aggrega
tion for
2CC

eRAN

nd
based on
inter
site)
Carrier
Aggrega
tion for
Uplink
2CC
Carrier
Aggrega
tion for
Downlin
k 3CC in
40MHz
Carrier
Aggrega
tion for
Downlin
k 3CC in
60MHz
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Flexible
CA from
Multiple
Carriers

eRAN

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 Unit: Mbps
01 Inter-
Band
LAOFD Default Value: 0
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 Flexible
FD-001 CA from
00111 Multiple
TDLAO Carriers
FD-001
Inter-
002
eNodeB
TDLAO CA
FD-070 based on
201 Coordin
ated
BBU
IP RAN
based
Inter
Site CA
(Carrier
Aggrega
tion for
2CC

eRAN

nd
based on
inter
site)
Carrier
Aggrega
tion for
Uplink
2CC
Carrier
Aggrega
tion for
Downlin
k 3CC in
40MHz
Carrier
Aggrega
tion for
Downlin
k 3CC in
60MHz
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz
Flexible
CA from
Multiple
Carriers

eRAN

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

eRAN

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 Unit: Ts
LST 701
ENODE configur Actual Value Range: 0~261120,275943~307200
TDLBF ation
BFRAM D-00100 Default Value: 0
EOFFS 702 uplink-
ET downlin
TDLOF k
D-00102 subfram
6 e
TDLOF configur
D-00102 ation
601 type1&2
TDLOF uplink-
D-00102 downlin
602 k special
TDLOF subfram
D-00102 e
603 configur
ation
MRFD- type 7
101231
Optional
MRFD- uplink-
101222 downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur

eRAN

nd
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
FDD
+TDD
Carrier
Aggrega
tion
(LTE
TDD)
FDD
+TDD
Carrier
Aggrega
tion
(LTE
FDD)
CellFra LocalCe ADD None None Meaning: Indicates the local ID of a cell. It uniquely
meOffse llId CELLF identifies a cell within an eNodeB.
t RAME GUI Value Range: 0~255
OFFSE
T Unit: None
LST Actual Value Range: 0~255

CELLF Default Value: None
RAME
OFFSE
T
MOD
CELLF
RAME
OFFSE
T
RMV
CELLF
RAME
OFFSE
T

eRAN

nd
CellFra FrameO ADD None None Meaning:

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

CELLF Default Value: 0
RAME
OFFSE
T
LST
CELLF
RAME
OFFSE
T

eRAN

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 Unit: None
CAGRO -001001
UP 02 Downlin Actual Value Range: FDD, TDD, FDDTDD
k 2CC in Default Value: FDD(FDD)
LST LAOFD 20MHz
CAGRO -001002
UP 01 / Inter-
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 Flexible
FD-001 CA from
00111 Multiple
Carriers
LAOFD
-081236 Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
FDD
+TDD
Carrier
Aggrega
tion

eRAN

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 Unit: None
DSP 02
PRIVA k 2CC in Actual Value Range: 0~31
LAOFD 20MHz
TECAB -001002 Default Value: None
ANDCO 01 / Inter-
MB TDLAO Band
LST FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
MOD TDLAO
PRIVA FD-001 Carrier
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
RMV / 40MHz
PRIVA TDLAO
TECAB FD-070 Support
ANDCO 201 of UE
MB Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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 Unit: MHz
-001001
MOD 02 Downlin Actual Value Range: 20~300
PRIVA k 2CC in Default Value: None
LAOFD 20MHz
TECAB -001002
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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 Unit: None
ANDCO 01 / Inter-
MB Band Actual Value Range: 0~31
TDLAO
DSP FD-001 Carrier Default Value: None
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
MB tion for Unit: None
-001001
PRIVA k 2CC in Default Value: 1
LAOFD 20MHz
TECAB -001002
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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

eRAN

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
Downlin Unit: None
MOD 02
LAOFD 20MHz
TECAB -001002 Default Value: 0
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
Downlin Unit: None
MOD 02
LAOFD 20MHz
TECAB -001002 Default Value: 0
ANDCO 01 / Inter-
MB TDLAO Band
DSP FD-001 Carrier
PRIVA 002 Aggrega
TECAB tion for
LAOFD Downlin
ANDCO -001002
MB k 2CC in
02 / 20MHz
LST TDLAO
TECAB 00202 Aggrega
ANDCO tion for
LAOFD Downlin
MB -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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. The selected bandwidths must be
MOD 02 Downlin consistent with the actual bandwidth configurations.
PRIVA k 2CC in Otherwise, the bandwidths that a UE does not support
LAOFD 20MHz are determined as supported by the eNodeB, causing CA
TECAB -001002
ANDCO Inter- configuration failures in the eNodeB.
01 /
MB TDLAO Band GUI Value Range: Bandwidth_1_4M(1.4M),
DSP FD-001 Carrier Bandwidth_3M(3M), Bandwidth_5M(5M),
PRIVA 002 Aggrega Bandwidth_10M(10M), Bandwidth_15M(15M),
TECAB tion for Bandwidth_20M(20M)
LAOFD Downlin
ANDCO -001002 Unit: None
MB k 2CC in
02 / 20MHz Actual Value Range: Bandwidth_1_4M,
LST TDLAO Bandwidth_3M, Bandwidth_5M, Bandwidth_10M,
PRIVA FD-001 Carrier Bandwidth_15M, Bandwidth_20M
TECAB 00202 Aggrega
tion for Default Value: Bandwidth_1_4M:On,
ANDCO LAOFD Bandwidth_3M:Off, Bandwidth_5M:Off,
MB Downlin
-070201 k 2CC in Bandwidth_10M:Off, Bandwidth_15M:Off,
/ 40MHz Bandwidth_20M:Off
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
TECAB -001002
01 /
LAOFD Downlin
MB k 2CC in
TECAB 00202 Aggrega
tion for Default Value: Bandwidth_1_4M:On,
MB Downlin
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
TECAB -001002
01 /
LAOFD Downlin
MB k 2CC in
TECAB 00202 Aggrega
tion for Default Value: Bandwidth_1_4M:Off,
MB Downlin
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
TECAB -001002
01 /
LAOFD Downlin
MB k 2CC in
TECAB 00202 Aggrega
tion for Default Value: Bandwidth_1_4M:Off,
MB Downlin
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
CaGrou SCellBli ADD LAOFD Intra- Meaning:

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

eRAN

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 Unit: None
L -001002
Inter- Actual Value Range: 0~7
LST 01 /
CAGRO TDLAO Band Default Value: 0
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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

eRAN

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 Unit: dBm
UPCEL LAOFD
L 20MHz Actual Value Range: -140~-43
-001002
LST 01 / Inter- Default Value: -105
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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- Unit: 0.5dB
CAGRO TDLAO Band
Carrier Actual Value Range: -20~-3
UPCEL FD-001
L 002 Aggrega Default Value: -20
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
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 Unit: None
EQCFG 01 Inter-
Band Actual Value Range: 0~7
LAOFD Carrier Default Value: 0
-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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: None
ELLLIS 02
T k 2CC in Actual Value Range: 0~46589,54436~65535
LAOFD 20MHz
LST -001002 Default Value: 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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: dBm
EQCFG 02
k 2CC in Actual Value Range: -140~-43
LST LAOFD 20MHz
PCCFR -001002 Default Value: -105
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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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- Unit: 0.5dB
TDLAO Band
Carrier Actual Value Range: -20~-3
FD-001
002 Aggrega Default Value: -20
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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: None
LST 01 / Inter-
Band Actual Value Range: 0~7
CAGRO TDLAO
UPSCE FD-001 Carrier Default Value: 1
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
ENodeB HoMode MOD LOFD-0 SRVCC Meaning:

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

D-00104 CS CDMA2000 1xRTT supports SRVCC. If this switch is
3 Fallback off, the CDMA2000 1xRTT does not support SRVCC.

eRAN

nd
TDLOF Steering UtranRedirectSwitch: If this switch is on, redirection to

D-00107 to UTRAN is enabled. If this switch is turned off,
2 UTRAN redirection to UTRAN is disabled.
TDLOF Service
GeranRedirectSwitch: If this switch is on, redirection to
D-00104 based
GERAN is enabled. If this switch is off, redirection to
6 Inter-
GERAN is disabled.
TDLOF RAT
D-00107 handove CdmaHrpdRedirectSwitch: If this switch is on,
3 r to redirection to CDMA2000 HRPD is enabled. If this
UTRAN switch is off, redirection to CDMA2000 HRPD is
Distance disabled.
based Cdma1xRttRedirectSwitch: If this switch is on,
Inter- redirection to CDMA2000 1xRTT is enabled. If this
RAT switch is off, redirection to CDMA2000 1xRTT is
handove disabled.
r to
BlindHoSwitch: If this switch is on, blind handovers for
UTRAN
CSFB are enabled. If this switch is off, blind handovers
Service for CSFB are disabled. If both this option and the
based BlindHoSwitch option of the Handover Mode switch
Inter- parameter of the CellHoParaCfg MO are selected, blind
RAT CSFB handovers for CSFB are enabled.
handove
r to LcsSrvccSwitch: If this switch is on, an SRVCC
GERAN procedure is triggered when a UE receives a CSFB
instruction during a VoIP service. If this switch is off,
Distance
an SRVCC procedure is not triggered when a UE
based
receives a CSFB instruction during a VoIP service.
Inter-
RAT AutoGapSwitch: If this switch is on and UEs support
handove automatic measurement gap configurations on the target
r to frequency, the eNodeB does not deliver gap
GERAN configurations to UEs. If this switch is off, the eNodeB
delivers gap configurations to UEs during all inter-
frequency and inter-RAT measurements.
UeVoipOnHspaCapSwitch: If this switch is on and the
eNodeB attempts to hand over UEs using voice services
to UTRAN, the eNodeB checks UE capabilities when
determining whether PS handover is applied. UEs must
support voiceOverPS-HS-UTRA-FDD-r9 if the target
UTRAN cell works in FDD mode or voiceOverPS-HS-
UTRA-TDD128-r9 if the target UTRAN cell works in
TDD mode. If this switch is off, the eNodeB does not
check UE capabilities when handing over UEs to
UTRAN based on PS handovers.
UtranFddB1CapSwitch: If this switch is on, the setting
of bit 41 of FGI specifying the UE capability of event

eRAN

nd
B1 measurement on FDD UTRAN cells must be

considered. If this switch is off, the setting of bit 41 of
FGI does not need to be considered.
CdmaHrpdNonOptMeaHoSwitch: If this 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),
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)
Unit: None
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

eRAN

nd
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

eRAN

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
k 2CC in Unit: dBm
LAOFD 20MHz Actual Value Range: -140~-43
-001002
01 / Inter- Default Value: -105
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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 Unit: dBm
LAOFD Downlin
-001002 k 2CC in Actual Value Range: -35~62
02 / 20MHz Default Value: 0
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
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 Unit: None
LST LAOFD 20MHz Actual Value Range: 1~7
SCCFR -001002
EQCFG 01 Inter- Default Value: 1
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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: s
-001001
Aggrega
02 Actual Value Range: 5~60
tion for
LAOFD Downlin Default Value: 60
-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 Flexible
FD-070 CA from
201 Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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

eRAN

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 Unit: dBm
EQCFG 01 Inter-
Band Actual Value Range: -35~62
-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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

nd
CellML MlbTrig MOD LOFD-0 Intra- Meaning:

B gerMod CELLM 70215 / LTE Indicates the variable that triggers a mobility load
e LB TDLOF User balancing (MLB) procedure.
LST D-07021 Number
CELLM 5 Load In MLB with load information exchange, If this
LB Balancin parameter is set to PRB_ONLY(PrbMode), PRB usage
g is used as a triggering variable and the number of UEs
is used as a supplementary triggering variable; PRB
usage 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 InterFreqMlbUeNumThd
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)
Unit: None

eRAN

nd
Actual Value Range: PRB_ONLY,

UE_NUMBER_ONLY, PRB_OR_UE_NUMBER
Default Value: PRB_ONLY(PrbMode)
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.
GUI Value Range: 1~100
Unit: %
Default Value: 60

eRAN

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.
Unit: %
Default Value: 0

eRAN

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.
Unit: %
Default Value: 8

eRAN

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

eRAN

nd
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.
Unit: None
Default Value: 20

eRAN

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 Unit: 0.5dB
FD-001 Actual Value Range: -15~15
00102 Carrier
Aggrega Default Value: 2
TDLAO tion for
FD-070 Downlin
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 Flexible
LAOFD CA from
-001002 Multiple
01 Carriers
LAOFD Intra-
-001002 Band
02 Carrier
LAOFD Aggrega
-070201 tion for
Downlin
LAOFD
k 2CC in
-070202
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz

eRAN

nd
Support
of UE
Categor
y6
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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
k 2CC in Unit: ms
LAOFD 20MHz Actual Value Range: 0~300
-001002
01 / Inter- Default Value: 50
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
k 2CC in Unit: kB
-001002
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
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.
Unit: ms
Default Value: 20

eRAN

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 Unit: None
FD-001 Carrier
Aggrega Actual Value Range: OFF, ON
002
tion for Default Value: OFF(Off)
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
k 2CC in Unit: kbit/s
-001002
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
k 2CC in Unit: kB
-001002
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
CaMgtC SccDeac MOD LAOFD Intra- Meaning:

fg tCqiThd CAMG -001001 Band Indicates the CQI threshold for deactivating an SCell or
TCFG 01 Carrier stopping scheduling CA UEs in the SCell based on the
LST LAOFD Aggrega channel quality.
CAMG -001001 tion for
TCFG 02 Downlin If the CaSccSuspendSwitch option of the SCell is
k 2CC in deselected and the channel quality for the CA UEs is
LAOFD 20MHz worse than that indicated by the SccDeactCqiThd
-001002 parameter value in single-codeword transmission, the
01 Inter-
eNodeB deactivates the SCell. If the SccDeactCqiThd
Band
LAOFD parameter is set to 0, the eNodeB does not deactivate
Carrier
-001002 the SCell for a CA UE based on channel quality of the
Aggrega
02 SCell.
tion for
LAOFD Downlin If the CaSccSuspendSwitch option of the SCell is
-070201 k 2CC in selected, the eNodeB stops scheduling CA UEs when
LAOFD 20MHz the channel quality for the CA UEs is worse than that
-070202 Carrier indicated by the SccDeactCqiThd parameter value in
TDLAO Aggrega single-codeword transmission. The eNodeB resumes
FD-001 tion for scheduling CA UEs in their SCells when the channel
00111 Downlin quality for the CA UEs is better than that indicated by
k 2CC in the SccDeactCqiThd parameter value plus 2 in single-
TDLAO codeword transmission. If the SccDeactCqiThd
40MHz
FD-001 parameter is set to 0, the eNodeB does not stop
002 Support
scheduling CA UEs in their SCells due to poor channel
TDLAO of UE
quality.
FD-001 Categor
y6 GUI Value Range: 0~15
00102
Flexible Unit: None
TDLAO
FD-070 CA from Actual Value Range: 0~15
201 Multiple Default Value: 0
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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

eRAN

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
k 2CC in Unit: dBm
LAOFD 20MHz Actual Value Range: -140~-43
-001002
01 / Inter- Default Value: -109
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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 Unit: dBm
LAOFD Downlin
-001002 k 2CC in Actual Value Range: -31~66
02 / 20MHz Default Value: 0
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
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 Unit: dBm
EQCFG 01 Inter-
Band Actual Value Range: -31~66
-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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: dBm
INTERF TDLBF Inter-
D-00201 frequenc Actual Value Range: -140~-43
REQHO
GROUP 804 y Default Value: -105
Handov
er
InterFre InterFre ADD LBFD-0 Coverag Meaning:

qHoGro qHoA2T INTERF 0201802 e Based Indicates the RSRP threshold for event A2 related to
up hdRsrp REQHO / Inter- event-A4/A5-triggered inter-frequency handover.
GROUP TDLBF frequenc
MOD D-00201 y When the measured RSRP value is lower than this
INTERF 802 Handov threshold, a measurement report will be sent.
REQHO er GUI Value Range: -140~-43
GROUP Unit: dBm
LST Actual Value Range: -140~-43
INTERF
Default Value: -109
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 Unit: None
NINTE
Actual Value Range: EventA3, EventA4, EventA5
RNFRE
Q Default Value: EventA4(EventA4)

eRAN

nd
CellAlg RacAlgo MOD LBFD-0 Admissi Meaning:

oSwitch Switch CELLA 02023 / on Indicates whether to enable the admission and load
LGOSW TDLBF Control control algorithms.
ITCH D-00202 Congesti
LST 3 on DlSwitch: Indicates whether to enable the algorithm of
CELLA LBFD-0 Control downlink admission control based on the satisfaction
LGOSW 02024 / rate. If this switch is on, the algorithm is enabled. If this
Radio/ switch is off, the algorithm is disabled. During the
ITCH TDLBF transport
D-00202 calculation of the QoS satisfaction rate of services with
resource different QCIs, the satisfaction estimation method used
4 pre- dedicatedly for VoIP services is implemented on
LOFD-0 emption services with the QCI of 1. If a service with the QCI of
0102901 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.
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

eRAN

nd
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
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),

eRAN

nd
UlPredictSwitch(ulCacPredictSwitch),
GbrUsageSwitch(GbrUsedPRbCheckSwitch),
DlLdcSwitch(dlLdcSwitch), UlLdcSwitch
(ulLdcSwitch), RelDrbSwitch(LdcDrbRelSwitch),
PreemptionSwitch(PreemptionSwitch)
Unit: None
Actual Value Range: DlSwitch, UlSwitch,
DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch,
DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,
PreemptionSwitch
Default Value: DlSwitch:Off, UlSwitch:Off,
DlPredictSwitch:Off, UlPredictSwitch:Off,
GbrUsageSwitch:Off, DlLdcSwitch:Off,
UlLdcSwitch:Off, RelDrbSwitch:Off,
PreemptionSwitch:Off

eRAN

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 Unit: None
-070201 k 2CC in Actual Value Range: BASIC_SCHEDULE,
/ 40MHz DIFF_SCHEDULE
TDLAO
FD-070 Support Default Value: BASIC_SCHEDULE(Basic Schedule)
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
LOFD-0 Inter-
01015 / eNodeB
TDLOF CA
D-00101 based on
5 Coordin
LOFD-0 ated
0101501 BBU
/ Intra-
TDLOF band
D-00101 Carrier
501 Aggrega
LOFD-0 tion for
0101502 Downlin
/ k 2CC in
TDLOF 30MHz

eRAN

nd
D-00101 Enhance
502 d
Scheduli
ng
CQI
Adjustm
ent
Dynami
c
Scheduli
ng

eRAN

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 Unit: None
TDLAO 20MHz
Actual Value Range: FROMSCC, FROMPCC
FD-001 Carrier
002 Aggrega Default Value: FROMSCC(FROMSCC)
LAOFD tion for

-001002 Downlin
02 / k 2CC in
TDLAO 40MHz
FD-001 Support
00102 of UE
LAOFD Categor
-070201 y6
/ Flexible
TDLAO CA from
FD-070 Multiple
201 Carriers
LAOFD Inter-
-070202 eNodeB
TDLAO CA
FD-001 based on
00111 Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
CellMi MimoA MOD LOFD-0 DL 2x2 Meaning:

moPara daptiveS CELLM 01001 MIMO Indicates the type of adaptive MIMO for a multi-
Cfg witch IMOPA LOFD-0 DL 4x2 antenna eNodeB. The values are described as follows:
RACFG 01003 MIMO
LST NO_ADAPTIVE: A fixed MIMO transmission mode is
LOFD-0 DL 4X4 used. That is, transition between MIMO transmission
CELLM 01060 / MIMO
IMOPA modes is not supported.
TDLOF DL 2x2
RACFG D-00106 OL_ADAPTIVE: The open-loop adaptive MIMO
MIMO
0 transmission mode is used. In this mode, UEs report
TDLOF RANK and CQI values but do not report PMI values to
D-00100 the eNodeB.
1 CL_ADAPTIVE: The closed-loop adaptive MIMO
transmission mode is used. In this mode, UEs report
RANK, CQI, and PMI values to the eNodeB.
OC_ADAPTIVE: UEs switch between the open-loop

and closed-loop adaptive MIMO transmission modes
automatically.
GUI Value Range: NO_ADAPTIVE
(NO_ADAPTIVE), OL_ADAPTIVE
(OL_ADAPTIVE), CL_ADAPTIVE
(CL_ADAPTIVE), OC_ADAPTIVE
(OC_ADAPTIVE)
Unit: None
Actual Value Range: NO_ADAPTIVE,
OL_ADAPTIVE, CL_ADAPTIVE, OC_ADAPTIVE
Default Value: OL_ADAPTIVE(OL_ADAPTIVE)

eRAN

nd
CellMi FixedMi MOD LOFD-0 DL 2x2 Meaning:

moPara moMod CELLM 01001 MIMO Indicates the fixed MIMO transmission mode
Cfg e IMOPA LOFD-0 DL 4x2 configured by a multi-antenna eNodeB for UEs. This
RACFG 01003 MIMO parameter is valid only when MimoAdaptiveSwitch is
LST LOFD-0 DL 4X4 set to NO_ADAPTIVE. There are four values.
CELLM 01060 / MIMO
IMOPA TM2: Transmission mode 2 is permanently applied to
TDLOF DL 2x2 UEs.
RACFG D-00106 MIMO
0 TM3: Transmission mode 3 is permanently applied to
TDLOF UEs.
D-00100 TM4: Transmission mode 4 is permanently applied to
1 UEs.
TM6: Transmission mode 6 is permanently applied to

UEs.
GUI Value Range: TM2(TM2), TM3(TM3), TM4
(TM4), TM6(TM6)
Unit: None
Actual Value Range: TM2, TM3, TM4, TM6
Default Value: TM3(TM3)
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 Unit: None
TDLAO DL 8x2 Actual Value Range: TM9Switch
FD-001 MIMO
00114 based on Default Value: TM9Switch:Off
TDLAO TM9
FD-080 DL 4x4
406 MIMO
TDLAO based on
FD-080 TM9
407 DL 8x4
MIMO
based on
TM9

eRAN

nd
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),
LAOFD Layer FIXED_CFG(Fixed configure), ADAPTIVE_CFG
-080210 MIMO (ADAPTIVE_CFG)
Based Unit: None
LAOFD on TM9
-080205 Actual Value Range: NOT_CFG, FIXED_CFG,
DL 2*2 ADAPTIVE_CFG
MIMO
based on Default Value: NOT_CFG(Not configure)
TM9
DL 4*2
MIMO
based on
TM9
Cell HighSpe ADD LOFD-0 High Meaning: Indicates the speed flag of the cell. Set this
edFlag CELL 01007 / Speed parameter to HIGH_SPEED if the cell is used to provide
MOD TDLOF Mobility coverage for an ultra-high-speed railway. Set this
CELL D-00100 Ultra parameter to LOW_SPEED in other scenarios. TDD
7 High cells with a bandwidth of 5 MHz or in 8T8R mode can
LST only be configured as low speed cells. TDD cells don't
CELL LOFD-0 Speed
01008 Mobility support ULTRA_HIGH_SPEED mode.
GUI Value Range: LOW_SPEED(Low speed cell flag),
HIGH_SPEED(High speed cell flag),
ULTRA_HIGH_SPEED(Ultra high speed cell flag),
EXTRA_HIGH_SPEED(Extra high speed cell flag)
Unit: None
Actual Value Range: LOW_SPEED, HIGH_SPEED,
ULTRA_HIGH_SPEED, EXTRA_HIGH_SPEED
Default Value: LOW_SPEED(Low speed cell flag)

eRAN

nd
ANR CaUeCh MOD LOFD-0 Automat Meaning:

oseMod ANR 02001 / ic Indicates the policy based on which the eNodeB selects
e LST TDLOF Neighbo UEs to perform cell global identification (CGI) reading
ANR D-00200 ur for ANR.
1 Relation
(ANR) If this parameter is set to CA_UE_CAP(CA UE
Capability), the eNodeB does not select the CA UEs that
support the CA bands 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)
Unit: None
Actual Value Range: CA_UE_CAP,
CA_UE_CARRIER_NUM, ANR_UE_CAP
Default Value: CA_UE_CAP(CA UE Capability)

eRAN

nd
CellAlg PucchAl MOD LBFD-0 Physical Meaning:

oSwitch goSwitc CELLA 02003 / Channel PucchSwitch: Indicates whether to enable the PUCCH
h LGOSW TDLBF Manage resource adjustment algorithm.
ITCH D-00200 ment
LST 3 If this option is selected, PUCCH resource adjustment
CELLA is initiated when the PUCCH resources are insufficient
LGOSW or excessive.
ITCH If this option is not selected, PUCCH resource
adjustment is disabled.
PucchFlexCfgSwitch: Indicates whether to enable

PUCCH flexible configuration. This function 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)
Unit: None
Actual Value Range: PucchSwitch, PucchFlexCfgS-
witch
Default Value: PucchSwitch:On,
PucchFlexCfgSwitch:Off

eRAN

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 Unit: None
MOD
EUTRA LBFD-0 er Actual Value Range: PERMIT_HO_ENUM,
NINTE 0201804 Distance FORBID_HO_ENUM
RFREQ / Based Default Value: PERMIT_HO_ENUM(Permit Ho)
NCELL TDLBF Inter-
LST D-00201 frequenc
EUTRA 804 y
NINTE LBFD-0 Handov
RFREQ 0201805 er
NCELL / Service
TDLBF Based
D-00201 Inter-
805 frequenc
LOFD-0 y
02012 / Handov
TDLOF er
D-00201 Cell
2 Outage
Detectio
n and
Compen
sation

eRAN

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
tion for Unit: None
CAGRO -001001
UP 02 Downlin Actual Value Range: 0~35
k 2CC in Default Value: None
MOD LAOFD 20MHz
CAGRO -001002
UP 01 / Inter-
TDLAO Band
RMV Carrier
CAGRO FD-001
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
Cell eNodeB DSP None None Meaning: Indicates the ID of the eNodeB.
Id CELL GUI Value Range: 0~1048575
DSP Unit: None
CELLP
HYTOP Actual Value Range: 0~1048575
O Default Value: None

eRAN

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 Unit: None
ADD Actual Value Range: 0~255
CELLB
Default Value: 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

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

nd
Cell WorkM ADD LAOFD Intra- Meaning: Indicates the work mode of the cell. The
ode CELL -001001 Band DL_ONLY mode applies only to the carrier aggregation
MOD 01 Carrier scenario.
CELL LAOFD Aggrega GUI Value Range: UL_DL(Uplink and downlink),
-001001 tion for DL_ONLY(Downlink only)
LST Downlin
CELL 02 Unit: None
k 2CC
LAOFD Actual Value Range: UL_DL, DL_ONLY
-001002 Inter-
01 Band Default Value: UL_DL(Uplink and downlink)
Carrier
LAOFD Aggrega
-001002 tion for
02 Downlin
TDLAO k 2CC
FD-001 Carrier
003 Aggrega
TDLAO tion for
FD-001 Downlin
002 k 2CC in
40MHz
Support
of UE
Categor
y6
Aggrega
tion for
Downlin
k 2CC in
30MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz

eRAN

nd
Cell FreqBan ADD LBFD-0 Cell Meaning: Indicates the frequency band in which the cell
d CELL 0201803 Selectio operates. For details about this parameter, see 3GPP TS
ADD / n and 36.104.
CELLB TDLBF Re- GUI Value Range: 1~64
AND D-00201 selection
803 Unit: None
LST Broadca
LBFD-0 st of Actual Value Range: 1~64
CELLB
02009 / system Default Value: None
AND
TDLBF informat
MOD D-00200 ion
CELL 9 Multi-
RMV LBFD-0 Band
CELLB 70103 / Compati
AND TDLBF bility
LST D-00201 Enhance
CELL 806 ment
Cell UlEarfc ADD LBFD-0 Coverag Meaning: Indicates the UL EARFCN of the cell. It is
n CELL 0201801 e Based optional, depending on the setting of the UL EARFCN
MOD / Intra- configuration indicator (UlEarfcnCfgInd). If the value
CELL TDLBF frequenc of this parameter is not specified, the default UL
D-00201 y EARFCN is used, which is calculated based on the DL
LST 801 Handov EARFCN. For details, see 3GPP TS 36.104.
CELL er
LBFD-0 GUI Value Range: 18000~46589,54436~65535
0201803 Cell Unit: None
/ Selectio
TDLBF n and Actual Value Range: 18000~46589,54436~65535
D-00201 Re- Default Value: 18000
803 selection
LBFD-0 Broadca
02009 / st of
TDLBF system
D-00200 informat
9 ion

eRAN

nd
EutranIn AnrInd ADD LOFD-0 Automat Meaning: Indicates whether information about inter-
terNFre EUTRA 02001 / ic frequency neighboring cells and external cells
q NINTE TDLOF Neighbo configured on the frequency associated with the serving
RNFRE D-00200 ur cell can be maintained by ANR. If this parameter is set
Q 1 Relation to ALLOWED, the information can be maintained by
MOD (ANR) ANR. If this parameter is set to NOT_ALLOWED, the
EUTRA information cannot be maintained by ANR.
NINTE GUI Value Range: NOT_ALLOWED
RNFRE (NOT_ALLOWED), ALLOWED(ALLOWED)
Q Unit: None
LST Actual Value Range: NOT_ALLOWED, ALLOWED
EUTRA
NINTE Default Value: ALLOWED(ALLOWED)
RNFRE
Q
EutranIn MlbTarg ADD LOFD-0 Intra- Meaning: Indicates whether the neighboring frequency
terNFre etInd EUTRA 01032 / LTE of the serving frequency can be a target frequency in
q NINTE TDLOF Load load balancing. If this parameter is set to ALLOWED,
RNFRE D-00103 Balancin the neighboring frequency of the serving frequency can
Q 2 g be selected as a target frequency in load balancing. If
MOD this parameter is set to NOT_ALLOWED, the
EUTRA neighboring frequency of the serving frequency cannot
NINTE be selected as a target frequency in load balancing.
RNFRE GUI Value Range: NOT_ALLOWED
Q (NOT_ALLOWED), ALLOWED(ALLOWED)
LST Unit: None
EUTRA Actual Value Range: NOT_ALLOWED, ALLOWED
NINTE
RNFRE Default Value: ALLOWED(ALLOWED)
Q

eRAN

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
tion for Unit: None
DSP -001001
CAGRO 02 Downlin Actual Value Range: 0~35
UPCEL k 2CC in Default Value: 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 Aggrega
CAGRO 00102
tion for
UPCEL LAOFD Downlin
L -070201 k 2CC in
/ 40MHz
TDLAO
FD-070 Support
201 of UE
Categor
LAOFD y6
-070202
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
tion for Unit: None
LST -001001
UPSCE k 2CC in Default Value: None
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
UPSCE FD-001 Carrier
LLCFG 002 Aggrega
tion for
RMV LAOFD Downlin
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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

eRAN

nd
SccFreq PccDlEa ADD LAOFD Intra- Meaning: Indicates the downlink E-UTRA absolute
Cfg rfcn SCCFR -001001 Band radio frequency channel number (EARFCN) of the
EQCFG 01 Carrier PCC.
LST LAOFD Aggrega GUI Value Range: 0~46589,54436~65535
SCCFR -001001 tion for
Downlin Unit: None
EQCFG 02
k 2CC in Actual Value Range: 0~46589,54436~65535
MOD LAOFD 20MHz
SCCFR -001002 Default Value: 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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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 Unit: None
SCCFR -001001
EQCFG 02 Downlin Actual Value Range: 0~46589,54436~65535
k 2CC in Default Value: 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
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

nd
ENodeB HoCom MOD LBFD-0 Distance Meaning:

AlgoSwi mOptSw ENODE 0201802 Based Indicates whether to enable optimization on handover-
tch itch BALGO / Inter- related common configurations and algorithms. This
SWITC TDLBF frequenc parameter includes the following switches:
H D-00201 y
LST 802 Handov BasedSriGapOptSwitch: Indicates whether to consider
ENODE LBFD-0 er transmission of scheduling request indicators (SRIs)
BALGO 0201804 when configuring measurement gaps for a UE that is not
Service
SWITC / in the discontinuous reception (DRX) state. The
Based
H TDLBF transmission of SRIs is considered in the preceding
Inter-
D-00201 scenario only when this switch is on.
frequenc
804 y L2UBasedHoPolicyPenaltySwitch: Indicates whether
LBFD-0 Handov the eNodeB distinguishes PS HO from single radio
0201805 er voice call continuity (SRVCC) when imposing
/ CS penalties on UEs after the UEs fail the non-resource-
TDLBF Fallback based admission control in PS HO or SRVCC during
D-00201 to inter-operations between the LTE and UMTS. If this
805 UTRAN switch is on, the eNodeB distinguishes PS HO from
LOFD-0 SRVCC when imposing penalties on UEs in the
PS Inter-
01019 / preceding scenario, and the PS-HO-induced penalty (or
RAT
TDLOF SRVCC-induced penalty) does not affect the initiation
Mobility
D-00101 of SRVCC (or PS HO) during the penalty period. If this
between
9 switch is off, the eNodeB does not distinguish PS HO
E-
from SRVCC when imposing penalties on UEs.
LOFD-0 UTRAN
01020 / and DrxBasedSriGapOptSwitch: Indicates whether to
TDLOF GERAN consider transmission of scheduling request indicators
D-00102 Service (SRIs) when configuring measurement gaps for a UE in
0 based the discontinuous reception (DRX) state. The
LOFD-0 inter- transmission of SRIs is considered in the preceding
01043 / RAT scenario only when this switch is on.
TDLOF handove GUI Value Range: BasedSriGapOptSwitch
D-00104 r to (BasedSriGapOptSwitch), L2UBasedHoPolicyPenal-
3 UTRAN tySwitch(L2UBasedHoPolicyPenaltySwitch),
LOFD-0 Service DrxBasedSriGapOptSwitch(DrxBasedSriGapOptS-
01046 / based witch)
TDLOF inter- Unit: None
D-00104 RAT Actual Value Range: BasedSriGapOptSwitch,
6 handove L2UBasedHoPolicyPenaltySwitch, DrxBasedSriGa-
LOFD-0 r to pOptSwitch
01072 / GERAN
Default Value: BasedSriGapOptSwitch:On,
TDLOF Distance L2UBasedHoPolicyPenaltySwitch:Off,
D-00107 based DrxBasedSriGapOptSwitch:On
2 inter-
LOFD-0 RAT
01073 / handove

eRAN

nd
TDLOF r to
D-00107 UTRAN
3 Distance
based
inter-
RAT
handove
r to
GERAN
Mobility
Manage
ment

eRAN

nd
GlobalP Protocol MOD LAOFD Intra- Meaning:

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

eRAN

nd
(Physica Multiplexing Tables 10.1.3-2, 10.1.3-3, and 10.1.3-4 in

l 3GPP TS 36.213. This option applies only to LTE TDD.
Channel
Manage SCellModCaMeasRmvSwitch: This option controls
ment) whether to delete the A2 and A6 measurement
configuration for SCC of the UE before changing the
SCell of the UE. If this option is selected, upon receiving
an A6 measurement report from a UE, the eNodeB
sends an A2- and A6-related measurement
configuration deletion message to the UE before
changing the SCell of the UE. If this option is
deselected, upon receiving an A6 measurement report
from a UE, the eNodeB does not send an A2- and A6-
related measurement configuration deletion message to
the UE before changing the SCell of the UE.
GUI Value Range: CaGapMeasPriOffSwitch,
CaHoReqWithR9ConfigSwitch, NasSecProcSwitch,
AntennaFullConfigSwitch, DrxConfigMsgSwitch,
MultiplexingTabSelSwitch, SCellModCaMeasRmvS-
witch
Unit: None
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

eRAN

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
tion for Unit: None
LST -001001
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
LLCFG 002 Aggrega
tion for
RMV LAOFD Downlin
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

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
tion for Unit: None
LST -001001
LAOFD 20MHz
LLCFG -001002
MOD 01 / Inter-
CAGRO TDLAO Band
LLCFG 002 Aggrega
tion for
RMV LAOFD Downlin
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
Flexible
TDLAO CA from
FD-001 Multiple
00111 Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC in
30MHz

eRAN

nd
ENodeB OverBB MOD LOFD-0 UL Meaning:

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

eRAN

nd
Carrier Default Value:

Aggrega UlJointReceptionOverBBUsSwitch:Off,
tion for FreqCfgCaOverBBUsSwitch:Off,
Downlin UlJROverRelaxedBHSw:Off,
k 2CC in UlSfnJROverBBUsSwitch:Off
30MHz
UL
CoMP
based on
relaxed
backhau
l
UL
CoMP
based on
Coordin
ated
BBU

eRAN

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 Unit: min
Aggrega
TDLAO tion for Actual Value Range: 1~65535
FD-070 Downlin Default Value: 15
201 k 2CC in
LAOFD 40MHz
-001001 Support
01 for UE
LAOFD Categor
-001001 y6
02 Flexible
LAOFD CA from
-001002 Multiple
01 Carriers
LAOFD Intra-
-001002 Band
02 Carrier
LAOFD Aggrega
-070201 tion for
Downlin
LAOFD
k 2CC in
-070202
20MHz
Inter-
Band
Carrier
Aggrega
tion for
Downlin
k 2CC in
20MHz
Carrier
Aggrega
tion for
Downlin
k 2CC in
40MHz

eRAN

nd
Support
of UE
Categor
y6
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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

eRAN

nd
Support
of UE
Categor
y6
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

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

eRAN

nd
Support
of UE
Categor
y6
Flexible
CA from
Multiple
Carriers
Inter-
eNodeB
CA
based on
Coordin
ated
BBU

eRAN

nd
CellAlg UlSchS MOD LOFD-0 VoIP Meaning:

oSwitch witch CELLA 01016 / Semi- This parameter indicates the switches related to uplink
LGOSW TDLOF persisten (UL) scheduling in the cell. The switches are used to
ITCH D-00101 t enable or disable specific UL scheduling functions.
LST 6 Scheduli
CELLA LOFD-0 ng SpsSchSwitch: Indicates the switch used to enable or
LGOSW 01048 / TTI disable semi-persistent scheduling during talk spurts of
ITCH TDLOF Bundlin VoIP services. If this switch is on, semi-persistent
D-00104 g scheduling is applied during talk spurts of VoIP
8 services. If this switch is off, dynamic scheduling is
Dynami applied during talk spurts of VoIP services.
LOFD-0 c
0101502 Scheduli SinrAdjustSwitch: Indicates whether to adjust the
/ ng measured signal to interference plus noise ratio (SINR)
TDLOF Basic based on ACK/NACK in UL hybrid automatic repeat
D-00101 Scheduli request (HARQ) processes.
502 ngTDL PreAllocationSwitch: Indicates whether to enable
TDLBF OFD-07 preallocation in the uplink. When this switch is on: (1)
D-00202 0224:Sc If SmartPreAllocationSwitch is off and a UE is in the
5 heduling discontinuous reception (DRX) state, preallocation is
LBFD-0 Based disabled for the UE in the uplink; (2) If SmartPreAlloca-
70102 / on Max tionSwitch is off and the UE is not in the DRX state,
TDLBF Bit Rate preallocation is enabled for the UE in the uplink; (3) If
D-07010 MBR>G SmartPreAllocationSwitch is on and the
2 BR SmartPreAllocationDuration parameter value is greater
LOFD-0 Configu than 0, smart preallocation is enabled for the UE in the
01002 ration uplink; (4) If SmartPreAllocationSwitch is on and the
UL 2x2 SmartPreAllocationDuration parameter value is 0,
LOFD-0 preallocation is disabled for the UE in the uplink. If this
01058 MU-
MIMO switch is off, preallocation is disabled for the UE in the
LBFD-0 uplink. If bearer-level preallocation or bearer-level
01006 UL 2x4 smart preallocation is enabled for a UE with a QCI class,
MU- cell-level preallocation and cell-level smart
MIMO preallocation do not apply to UEs with the QCI.
AMC
UlVmimoSwitch: Indicates whether to enable multi-
user MIMO (MU-MIMO) in the UL. If this switch is on,
the eNodeB performs MU-MIMO pairing among UEs
based on related principles. UEs forming a pair transmit
data using the same time-frequency resources, which
improves system throughput and spectral efficiency.
TtiBundlingSwitch: Indicates whether to enable

transmission time interval (TTI) bundling. If TTI
bundling is enabled, more transmission opportunities
are available to UEs within the delay budget for VoIP

eRAN

nd
services on the Uu interface, thereby improving uplink

coverage.
ImIcSwitch: Indicates whether to enable the

intermodulation interference (IM) cancellation for UEs.
When data is transmitted in both uplink and downlink,
two IM components are generated symmetrically beside
the Direct Current (DC) subcarrier on the downlink
receive channel due to interference from uplink radio
signals. If this switch is on, IM component elimination
is performed on UEs. If this switch is off, IM component
elimination is not performed on UEs. This switch
applies only to FDD cells working in frequency band
20.
SmartPreAllocationSwitch: Indicates whether to enable

uplink smart preallocation when preallocation is
enabled (by turning on PreAllocationSwitch). If both
PreAllocationSwitch and SmartPreAllocationSwitch
are on and SmartPreAllocationDuration is set to a value
greater than 0, uplink smart preallocation is enabled;
otherwise, uplink smart preallocation is disabled.
PuschDtxSwitch: Indicates whether the eNodeB uses

the physical uplink shared channel (PUSCH)
discontinuous transmission (DTX) detection result
during UL scheduling. In an LTE FDD cell, if this
switch is on, based on the PUSCH DTX detection result,
the eNodeB determines whether to perform adaptive
retransmission during UL scheduling and also adjusts
the control channel element (CCE) aggregation level of
the physical downlink control channel (PDCCH)
carrying downlink control information (DCI) format 0.
If an FDD cell is established on an LBBPc, this switch
takes effect only when the cell uses less than four RX
antennas and normal cyclic prefix (CP) in the uplink and
the SrsCfgInd parameter in the SRSCfg MO is set to
BOOLEAN_TRUE. Note that the LBBPc does not
support PUSCH DTX detection for UEs with MU-
MIMO applied. In an LTE TDD cell, this switch takes
effect only when the cell is configured with subframe
configuration 2 or 5. After this switch takes effect, the
eNodeB adjusts the CCE aggregation level based on the
PUSCH DTX detection results. Note that LTE TDD
cells established on LBBPc boards do not support
PUSCH DTX detection.
UlIblerAdjustSwitch: Indicates whether to enable the

uplink initial block error rate (IBLER) adjustment

eRAN

nd
algorithm. If this switch is on, IBLER convergence

target is adjusted to increase the cell edge throughput.
When this switch is on, the recommended configuration
of parameter DopMeasLevel in MO CellUlschAlgo is
CLASS_1.
UlEnhancedFssSwitch: Indicates whether to enable

uplink load-based enhanced frequency selection. This
switch applies only to FDD cells.
UlIicsAlgoSwitch: Indicates whether to enable the UL

IICS algorithm. If this switch is on, interference can be
reduced based on accurate detection of user attributes
and resource scheduling coordination, thereby
increasing the cell edge throughput.
UlEnhancedSrSchSwitch: Indicates whether uplink re-

scheduling is performed only when the On Duration
timer for the DRX long cycle starts. Uplink re-
scheduling is required if the number of HARQ
retransmissions for a scheduling request (SR) reaches
the maximum value but the scheduling still fails. If this
switch is on, uplink re-scheduling is performed only
when the On Duration timer for the DRX long cycle
starts. If this switch is off, uplink re-scheduling is
performed immediately when the number of HARQ
retransmissions for SR reaches the maximum value but
the scheduling still fails. It is recommended that the
switch be turned on in live networks.
SchedulerCtrlPowerSwitch: Indicates whether the

uplink scheduler performs scheduling without
considering power control restrictions. If this switch is
on, the uplink scheduler performs scheduling without
considering power control restrictions, which ensures
full utilization of the transmit power for all UEs. If this
switch is off, the uplink scheduler considers power
control restrictions while performing scheduling, which
prevents full utilization of the transmit power for UEs
at far or medium distances from the cell center.
UlMinGbrSwitch: Indicates whether to enable uplink

minimum guaranteed bit rate (GBR). If this switch is
on, the minimum GBR of non-GBR services is ensured
by increasing the scheduling priority of UEs whose non-
GBR service rates are lower than the minimum GBR of
GBR services.
UlMbrCtrlSwitch: Indicates whether to enable uplink

scheduling based on the maximum bit rate (MBR) and

eRAN

nd
guaranteed bit rate (GBR) on the GBR bearer. If this

switch is on, the eNodeB performs uplink scheduling on
GBR bearers based on the MBR and GBR. If this switch
is off, the eNodeB performs uplink scheduling on GBR
bearers based only on the GBR.
MbrUlSchSwitch: Indicates whether the eNodeB

performs uplink scheduling based on MBR. If this
switch is on, the eNodeB prioritizes UEs based on the
MBRs during uplink scheduling. This parameter applies
only to LTE TDD cells.
UeAmbrUlSchSwitch: Indicates whether the eNodeB

performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this switch is on,
the eNodeB prioritizes UEs based on the AMBRs during
uplink scheduling. This parameter applies only to LTE
TDD cells.
UlEnhancedDopplerSwitch: Indicates whether to

enable enhanced uplink scheduling based on mobility
speed. If this switch is on, enhanced uplink scheduling
based on mobility speed is enabled. If this switch is on,
the eNodeB determines whether a UE is a low-mobility
UE based on the Doppler measurement in the physical
layer, and then improves uplink frequency selective
scheduling performance for low-mobility UEs. If this
switch is off, enhanced uplink scheduling based on
mobility speed is disabled. This switch takes effect only
when the UlEnhancedDopplerSwitch parameter is set to
CLASS_1. This switch does not take effect on cells
established on an LBBPc.
UlRaUserSchOptSw: Indicates whether the eNodeB

raises the scheduling priority of UEs sending uplink
access signaling, including MSG5 and the RRC
Connection Reconfiguration Complete message. If this
switch is on, the eNodeB raises the scheduling priority
of UEs sending uplink access signaling. If this switch is
off, the eNodeB does not raise the scheduling priority
of UEs sending uplink access signaling.
UlLast2RetransSchOptSwitch: Indicates whether to

enable optimization on the scheduling policy for the last
two retransmissions. If this switch is on, optimization
on the scheduling policy for the last two retransmissions
is enabled. If the UE transmit power is not limited,
adaptive retransmission is used and the number of RBs
increases in the last two retransmissions to increase the

eRAN

nd
receive success rate of the last two retransmissions and

decrease uplink RBLER. If this switch is off,
optimization on the scheduling policy for the last two
retransmissions is disabled. This switch does not apply
to LTE TDD cells.
UlInterfFssSwitch: Indicates whether to enable

interference-based uplink frequency-selective
scheduling.
UlSmallRBSpectralEffOptSw: Indicates whether to

enable spectral efficiency optimization on uplink small
RBs. If this switch is on, the optimization is enabled,
thereby ensuring that the transmission block size
calculated based on optimized spectral efficiency is not
less than the traffic volume needs to be scheduled. If this
switch is off, the optimization is disabled.
PuschUsePucchRbSwitch: Indicates whether PUCCH

RBs can be occupied by the PUSCH. In scenarios with
a single user, if this switch is on, PUCCH RBs can be
occupied by the PUSCH. If this switch is off, PUCCH
RBs cannot be occupied by the PUSCH. In scenarios
with multiple users, PUCCH RBs cannot be occupied
by the PUSCH no matter whether this switch is on or
off.
PuschDtxSchOptSwitch: If this switch is on, the

eNodeB determines whether to perform adaptive
retransmission during UL scheduling based on the
PUSCH DTX detection result. This switch takes effect
only when subframe configuration 2 or 5 is used. If a
TDD cell is established on an LBBPc, PUSCH DTX
detection is not supported. This switch applies only to
LTE TDD cells.
PrachRbReuseSwitch:If this switch is on, the PUSCH

and PRACH transmissions can use the same resource.
If this switch is off, the PUSCH and PRACH

transmissions cannot use the same resource. This switch
applies only to LTE TDD cells.
ULFSSAlgoswitch:If this switch is off, uplink

frequency-selective scheduling is disabled. If this
switch is on, uplink frequency-selective scheduling is
enabled. This switch is invalid if the HighSpeedFlag
parameter in the Cell MO is set to HIGH_SPEED(High
speed cell flag) or ULTRA_HIGH_SPEED(Ultra high
speed cell flag), that is, uplink frequency-selective

eRAN

nd
scheduling is disabled in high speed and ultra high speed

mobility conditions. This switch applies only to LTE
TDD cells.
SrSchDataAdptSw: Indicates whether to enable data

volume adaption in SR scheduling. Data volume
adaption in SR scheduling is enabled only when this
option is selected.
UlFssUserThdStSwitch: UlFssUserThdStSwitch:
Indicates whether to enable the optimization policy on
the UE number threshold for frequency selective
scheduling. The optimization policy is enabled only
when this option is selected.
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationS-
witch(PreAllocationSwitch), UlVmimoSwitch
(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingS-
witch), ImIcSwitch(ImIcSwitch), SmartPreAlloca-
tionSwitch(SmartPreAllocationSwitch),
PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustS-
witch(UlIblerAdjustSwitch), UlEnhancedFssSwitch
(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch
(UlEnhancedSrSchSwitch), SchedulerCtrlPowerS-
witch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch
(UlIicsAlgoSwitch), UlMinGbrSwitch
(UlMinGbrSwitch), UlMbrCtrlSwitch
(UlMbrCtrlSwitch), MbrUlSchSwitch
(MbrUlSchSwitch), UeAmbrUlSchSwitch
(UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch
(UlEnhancedDopplerSwitch), UlRaUserSchOptSw
(UlRaUserSchOptSw), UlLast2RetransSchOptSwitch
(UlLast2RetransSchOptSwitch), UlInterfFssSwitch
(UlInterfFssSwitch), UlSmallRBSpectralEffOptSw
(UlSmallRBSpectralEfficiencyOptSw), PuschUse-
PucchRbSwitch(PuschUsePucchRbSwitch),
PuschDtxSchOptSwitch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch)
Unit: None
Actual Value Range: SpsSchSwitch, SinrAdjustSwitch,
PreAllocationSwitch, UlVmimoSwitch, TtiBundlingS-
witch, ImIcSwitch, SmartPreAllocationSwitch,
PuschDtxSwitch, UlIblerAdjustSwitch,
UlEnhancedFssSwitch, UlEnhancedSrSchSwitch,

eRAN

nd
SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch,
UlMinGbrSwitch, UlMbrCtrlSwitch,
MbrUlSchSwitch, UeAmbrUlSchSwitch,
UlEnhancedDopplerSwitch, UlRaUserSchOptSw,
UlLast2RetransSchOptSwitch, UlInterfFssSwitch,
UlSmallRBSpectralEffOptSw, PuschUsePucchRbS-
witch, PuschDtxSchOptSwitch, ULFSSAlgoSwitch,
PrachRbReuseSwitch, SrSchDataAdptSw,
UlFssUserThdStSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:Off,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:Off,
SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:Off,
UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:Off,
UlInterfFssSwitch:Off,
UlSmallRBSpectralEffOptSw:Off,
PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off

eRAN
Carrier Aggregation Feature Parameter Description 15 Counters
15 Counters
Table 15-1 Counters
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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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
1526729466 L.RLC.FirstPacket Number of times Multi-mode: None Active Queue

Delay.NonGBR.In- delay of the first GSM: None Management
dex0 RLC SDU for a non- (AQM)
GBR bearer ranges UMTS: None
LTE-A Introduction
within index 0 LTE:
LOFD-001027
LAOFD-001001

LTE-A Introduction
within index 1 LTE:
LOFD-001027
LAOFD-001001

eRAN

Description

LTE-A Introduction
within index 2 LTE:
LOFD-001027
LAOFD-001001

LTE-A Introduction
within index 3 LTE:
LOFD-001027
LAOFD-001001

LTE-A Introduction
within index 4 LTE:
LOFD-001027
LAOFD-001001

eRAN

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

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

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
1526730252 L.CA.PCell.ChMea Number of periodic Multi-mode: None Flexible CA from

s.CQI.DL.SingleC wideband CQI GSM: None Multiple Carriers
W.Periodic.0 reports with the Flexible CA from
value of 0 in single- UMTS: None
Multiple Carriers
codeword LTE:
transmission sent by LAOFD-070201
CA UEs that use the TDLAOFD-070201
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell
1526730268 L.CA.SCell.ChMea Number of periodic Multi-mode: None Flexible CA from

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description
1526730284 L.CA.PCell.ChMea Number of aperiodic Multi-mode: None Flexible CA from

W.Aperiodic.0 reports with the Flexible CA from
Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

Multiple Carriers
codeword LTE:
local cell as their
Pcell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Pcell
1526730300 L.CA.SCell.ChMea Number of aperiodic Multi-mode: None Flexible CA from

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

eRAN

Description

Multiple Carriers
codeword LTE:
local cell as their
Scell

Multiple Carriers
codeword LTE:
local cell as their
Scell

s.CQI.DL.DualCW. wideband CQI GSM: None Multiple Carriers
Code0.Periodic.0 reports with the Flexible CA from
value of 0 for UMTS: None
Multiple Carriers
codeword 0 in dual- LTE:
codeword LAOFD-070201
transmission sent by TDLAOFD-070201
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Code0.Aperiodic.0 reports with the Flexible CA from
Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell
1526730444 L.CA.PCell.ChMea Number of times Multi-mode: None Flexible CA from

s.PDSCH.MCS.0 MCS index 0 is used GSM: None Multiple Carriers
for scheduling on Flexible CA from
the PDSCH for CA UMTS: None
Multiple Carriers
UEs that use the LTE:
local cell as their LAOFD-070201
Pcell TDLAOFD-070201

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

s.PDSCH.MCS.10 MCS index 10 is GSM: None Multiple Carriers
used for scheduling Flexible CA from
on the PDSCH for UMTS: None
Multiple Carriers
CA UEs that use the LTE:

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers
1526730476 L.CA.SCell.ChMea Number of times Multi-mode: None Flexible CA from

Multiple Carriers
Scell TDLAOFD-070201

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

Multiple Carriers

eRAN

Description

Multiple Carriers
1526730508 L.CA.PCell.Traffic. Number of TBs Multi-mode: None Flexible CA from

DL.SCH.QPSK.TB initially transmitted GSM: None Multiple Carriers
on the downlink Flexible CA from
SCH in QPSK UMTS: None
Multiple Carriers
modulation mode LTE:
for CA UEs that use LAOFD-070201
the local cell as their TDLAOFD-070201
Pcell

DL.SCH. initially transmitted GSM: None Multiple Carriers
16QAM.TB on the downlink Flexible CA from
SCH in 16QAM UMTS: None
Multiple Carriers
Pcell

Multiple Carriers
Pcell
1526730511 L.CA.SCell.Traffic. Number of TBs Multi-mode: None Flexible CA from

DL.SCH.QPSK.TB initially transmitted GSM: None Multiple Carriers
on the downlink Flexible CA from
SCH in QPSK UMTS: None
Multiple Carriers
Scell

eRAN

Description

Multiple Carriers
Scell

Multiple Carriers
Scell
1526730514 L.CA.PCell.Traffic. Number of Multi-mode: None Flexible CA from

DL.SCH.QPSK.Err downlink error TBs GSM: None Multiple Carriers
TB.Ibler after initial Flexible CA from
transmission in UMTS: None
Multiple Carriers
QPSK modulation LTE:
mode for CA UEs LAOFD-070201
that use the local cell TDLAOFD-070201
as their Pcell

DL.SCH. downlink error TBs GSM: None Multiple Carriers
16QAM.ErrTB.Ible after initial Flexible CA from
r transmission in UMTS: None
Multiple Carriers
16QAM modulation LTE:
as their Pcell

Multiple Carriers
as their Pcell

eRAN

Description
1526730517 L.CA.SCell.Traffic. Number of Multi-mode: None Flexible CA from

TB.Ibler after initial Flexible CA from
transmission in UMTS: None
Multiple Carriers
as their Scell

Multiple Carriers
as their Scell

Multiple Carriers
as their Scell

TB.Rbler after the maximum Flexible CA from
number of UMTS: None
Multiple Carriers
transmissions in LTE:
QPSK modulation LAOFD-070201
mode is reached for TDLAOFD-070201
CA UEs that use the
local cell as their
Pcell

16QAM.ErrTB.Rbl after the maximum Flexible CA from
er number of UMTS: None
Multiple Carriers
16QAM modulation LAOFD-070201
CA UEs that use the
local cell as their
Pcell

eRAN

Description

Multiple Carriers
CA UEs that use the
local cell as their
Pcell

TB.Rbler after the maximum Flexible CA from
number of UMTS: None
Multiple Carriers
QPSK modulation LAOFD-070201
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

Multiple Carriers
CA UEs that use the
local cell as their
Scell

eRAN

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

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

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

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

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

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

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

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

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

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

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
1526732697 L.ChMeas.PRB.PU Number of samples Multi-mode: None LTE-A Introduction

SCH.Util.Samp.In- with the PUSCH GSM: None Carrier Aggregation
dex0 PRB usage ranging for Downlink 2CC
within index 0 UMTS: None
in 40MHz
LTE:
LAOFD-001001 SFN
LAOFD-001002 Basic Scheduling
TDLOFD-001075 Basic Scheduling
LBFD-002025
TDLBFD-002025

eRAN

Description

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

eRAN

Description

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

eRAN

Description

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025
1526732727 L.ChMeas.PRB.PD Number of samples Multi-mode: None LTE-A Introduction

SCH.Util.Samp.In- with the PDSCH GSM: None Carrier Aggregation
in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

eRAN

Description

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

eRAN

Description

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025

in 40MHz
LTE:
LAOFD-001001 SFN
LBFD-002025
TDLBFD-002025
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

eRAN

Description
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
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

eRAN

Description
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
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

eRAN

Description
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
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
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
1526733013 L.Thrp.bits.UL.CA Uplink PDCP-layer Multi-mode: None Carrier Aggregation

User traffic volume of CA GSM: None for Uplink 2CC
UEs that are in the Carrier Aggregation
uplink CA state and UMTS: None
for Uplink 2CC
treat the local as LTE:
their PCell with all LAOFD-080202
SCells activated TDLAOFD-081407
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

eRAN

Description
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
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
1526733022 L.CA.UL.SCell.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
SCell and have the LTE:
SCell activated LAOFD-080202
TDLAOFD-081407

eRAN

Description
1526733023 L.CA.PCell.ChMea Number of times Multi-mode: None Carrier Aggregation

s.PUSCH.MCS.0 MCS index 0 is used GSM: None for Uplink 2CC
for scheduling on Carrier Aggregation
the PUSCH for CA UMTS: None
for Uplink 2CC
UEs that treat the LTE:
PCell TDLAOFD-081407

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

s.PUSCH.MCS.10 MCS index 10 is GSM: None for Uplink 2CC
used for scheduling Carrier Aggregation
on the PUSCH for UMTS: None
for Uplink 2CC
CA UEs that treat LTE:
the local cell as their LAOFD-080202

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC
1526733055 L.CA.SCell.ChMea Number of times Multi-mode: None Carrier Aggregation

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC
1526733087 L.CA.PCell.ChMea Number of used Multi-mode: None Carrier Aggregation

s.PRB.UL.MCS.0 PRBs when MCS GSM: None for Uplink 2CC
index 0 is used for Carrier Aggregation
scheduling on the UMTS: None
for Uplink 2CC
PUSCH for CA UEs LTE:
that treat the local LAOFD-080202
cell as their PCell TDLAOFD-081407

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description
1526733119 L.CA.SCell.ChMea Number of used Multi-mode: None Carrier Aggregation

for Uplink 2CC
cell as their SCell TDLAOFD-081407

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC
1526733151 L.CA.PCell.Traffic. Number of TBs Multi-mode: None Carrier Aggregation

UL.SCH.QPSK.TB initially transmitted GSM: None for Uplink 2CC
on the uplink SCH in Carrier Aggregation
QPSK modulation UMTS: None
for Uplink 2CC
mode for CA UEs LTE:

UL.SCH. initially transmitted GSM: None for Uplink 2CC
16QAM.TB on the uplink SCH in Carrier Aggregation
16QAM modulation UMTS: None
for Uplink 2CC

64QAM.TB on the UL SCH in Carrier Aggregation
for Uplink 2CC
1526733154 L.CA.SCell.Traffic. Number of TBs Multi-mode: None Carrier Aggregation

UL.SCH.QPSK.TB initially transmitted GSM: None for Uplink 2CC
on the uplink SCH in Carrier Aggregation
QPSK modulation UMTS: None
for Uplink 2CC

eRAN

Description

for Uplink 2CC

for Uplink 2CC
1526733157 L.CA.PCell.Traffic. Number of uplink Multi-mode: None Carrier Aggregation

UL.SCH.QPSK.Err error TBs after GSM: None for Uplink 2CC
TB.Ibler initial transmission Carrier Aggregation
in QPSK UMTS: None
for Uplink 2CC
for CA UEs that treat LAOFD-080202
PCell

UL.SCH. error TBs after GSM: None for Uplink 2CC
16QAM.ErrTB.Ible initial transmission Carrier Aggregation
r in 16QAM UMTS: None
for Uplink 2CC
PCell

for Uplink 2CC
PCell

eRAN

Description
1526733160 L.CA.SCell.Traffic. Number of uplink Multi-mode: None Carrier Aggregation

UL.SCH.QPSK.Err error TBs after GSM: None for Uplink 2CC
TB.Ibler initial transmission Carrier Aggregation
in QPSK UMTS: None
for Uplink 2CC
SCell

for Uplink 2CC
SCell

for Uplink 2CC
SCell

UL.SCH.QPSK.Err error TBs after the GSM: None for Uplink 2CC
TB.Rbler maximum number Carrier Aggregation
of retransmissions in UMTS: None
for Uplink 2CC
mode is reached for LAOFD-080202
CA UEs that treat TDLAOFD-081407
the local cell as their
PCell

UL.SCH. error TBs after the GSM: None for Uplink 2CC
16QAM.ErrTB.Rbl maximum number Carrier Aggregation
er of retransmissions in UMTS: None
for Uplink 2CC
PCell

eRAN

Description

for Uplink 2CC
PCell

UL.SCH.QPSK.Err error TBs after the GSM: None for Uplink 2CC
TB.Rbler maximum number Carrier Aggregation
of retransmissions in UMTS: None
for Uplink 2CC
SCell

for Uplink 2CC
SCell

for Uplink 2CC
SCell
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

eRAN

Description
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
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

Description
1526737775 L.E- Number of normal Multi-mode: None Intra-Band Carrier

RAB.NormRel.Re- E-RAB releases for GSM: None Aggregation for
laxedBackhaul- UEs in the downlink Downlink 2CC in
CAUser relaxed-backhaul- UMTS: None 20MHz
based CA state LTE: Inter-Band Carrier
LAOFD-070201 20MHz
Multiple Carriers
LAOFD-080202
Inter-eNodeB CA
LAOFD-080207
based on
TDLAOFD-001001 Carrier Aggregation
11 for Uplink 2CC
TDLAOFD-001001 for Downlink 3CC
02 in 40MHz
for Downlink 3CC
TDLAOFD-070201
in 60MHz
Intra-band Carrier
Aggregation for
Downlink 2CC in
30MHz
Carrier Aggregation
for Downlink 2CC
in 40MHz
Support for UE
Category 6
Inter-eNodeB DL
CoMP based on
Relaxed backhaul
Flexible CA from
Multiple Carriers

eRAN
Carrier Aggregation Feature Parameter Description 16 Glossary
16 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Carrier Aggregation Feature Parameter Description 17 Reference Documents
17 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. Overview of Mobility Management in Connected Mode
9. RAN Sharing
10. Scheduling
11. USU3900-based Multi-BBU Interconnection
12. USU3910-based Multi-BBU Interconnection


Carrier Aggregation (ERAN FDD 8.1 02) FPD

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Carrier Aggregation (ERAN FDD 8.1 02) FPD

Загружено:

Авторское право:

Доступные форматы

eRAN

Carrier Aggregation Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2015-04-30) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue 02 (2015-04-30) Huawei Proprietary and Confidential ii

3.2.3 SCell Configuration...................................................................................................................................................45

Issue 02 (2015-04-30) Huawei Proprietary and Confidential iii

5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]........................................................................96

6 Engineering Guidelines for LAOFD-001001 LTE-A Introduction and LAOFD-001002

7 Engineering Guidelines for LAOFD-070201 Flexible CA from Multiple Carriers.......151

Issue 02 (2015-04-30) Huawei Proprietary and Confidential iv

8 Engineering Guidelines for LAOFD-070202 Inter-eNodeB CA based on Coordinated

9 Engineering Guidelines for LAOFD-080201 Inter-eNodeB CA based on Relaxed

Issue 02 (2015-04-30) Huawei Proprietary and Confidential v

10.4.4 Hardware Adjustment............................................................................................................................................171

11 Engineering Guidelines for LAOFD-080207 Carrier Aggregation for Downlink 3CC in

12 Engineering Guidelines for LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO

13 Engineering Guidelines for MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD)

Issue 02 (2015-04-30) Huawei Proprietary and Confidential vi

13.1 When to Use MRFD-101222....................................................................................................................................182

Issue 02 (2015-04-30) Huawei Proprietary and Confidential vii

1 About This Document

l LAOFD-001001 LTE-A Introduction

Issue 02 (2015-04-30) Huawei Proprietary and Confidential 1

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

LampSite DBS3900 LampSite

1.2 Intended Audience

1.3 Change History

Change Change Description Parameter Change Affected

Feature None None N/A

Editorial Revised the description of the None N/A

Issue 02 (2015-04-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change Affected

Revised the description of typical None N/A

Modified the total bandwidth None N/A

Revised the description of CA in None N/A

Modified band combinations. For None N/A

Revised the description of adaptive None N/A

Revised the description of load-based None N/A

Modified the impacted features of None N/A

Modified the impacted features of None N/A

Revised the description of hardware None N/A

Modified the precautions for None N/A

Issue 02 (2015-04-30) Huawei Proprietary and Confidential 3

Change Change Description Parameter Change Affected

Revised the description of hardware None N/A

Modified the precautions for Inter- None N/A

Modified the transmission networking None N/A

Modified the procedure for None N/A

Modified the license requirement of None N/A

Change Change Description Parameter Change Affected

Feature None None N/A

Editorial Revised the descriptions of UE None N/A

Issue 02 (2015-04-30) Huawei Proprietary and Confidential 4

Change Change Description Parameter Change Affected

Revised the descriptions of Inter- None N/A

Modified band combinations. For None N/A

Modified the impact of LTE-A None N/A