• No results found

Carrier Aggregation(ERAN8.1 06)

N/A
N/A
Protected

Academic year: 2021

Share "Carrier Aggregation(ERAN8.1 06)"

Copied!
556
0
0

Loading.... (view fulltext now)

Full text

(1)

Carrier Aggregation Feature

Parameter Description

Issue 06

(2)

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

(3)

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

2 Overview... 18

2.1 Introduction... 18 2.2 Benefits...19 2.3 Architecture... 19

3 Technical Description...21

3.1 Function Overview... 21 3.1.1 Related Concepts... 21 3.1.2 Usage Scenarios...22 3.1.2.1 Typical Scenarios...22 3.1.2.2 Atypical Scenarios...25 3.1.3 CA Features... 25

3.1.3.1 LAOFD-001001 LTE-A Introduction...27

3.1.3.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz...28

3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers... 29

3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU... 29

3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul... 30

3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]...32

3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz...32

3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz...33

3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]... 34

3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]...35

3.1.4 Band Combinations... 36

3.2 Carrier Management... 37

3.2.1 Overview... 37

3.2.2 PCC Anchoring (at Initial Access)... 40

3.2.2.1 CA-Group-based PCC Anchoring... 40

(4)

3.2.3 SCell Configuration...44

3.2.3.1 CA-Group-based SCell Configuration... 46

3.2.3.2 Frequency-based SCell Configuration...53

3.2.3.3 Adaptive SCell Configuration... 60

3.2.3.4 Load-based SCell Configuration... 68

3.2.4 SCell Change... 69

3.2.5 SCell Activation... 69

3.2.6 SCell Deactivation...71

3.2.7 SCell Removal...73

3.2.8 PCC Anchoring (at RRC Connection Releases)...75

3.3 Other Key Techniques Under CA...75

3.3.1 Connection Management Under CA... 75

3.3.2 Mobility Management Under CA...76

3.3.3 Admission and Congestion Control Under CA... 79

3.3.4 Scheduling Under CA...80

3.3.5 MIMO Under CA... 81

3.3.6 DRX Control Under CA... 81

3.3.7 RAN Sharing Under CA...82

3.3.8 Power Backoff Under CA...83

3.3.9 MTA Under CA... 83

4 Related Features...84

4.1 Features Related to LAOFD-001001 LTE-A Introduction...84

4.2 Features Related to LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz... 86

4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers...86

4.4 Features Related to LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU... 87

4.5 Features Related to LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul...87

4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]... 88

4.7 Features Related to LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz... 89

4.8 Features Related to LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz... 89

4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]... 89

4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]... 90

5 Network Impact... 94

5.1 LAOFD-001001 LTE-A Introduction...94

5.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz...95

5.3 LAOFD-070201 Flexible CA from Multiple Carriers... 95

5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU... 95

5.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul... 96

5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]...97

5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz...97

5.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz...97

5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]... 97

(5)

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

Carrier Aggregation for Downlink 2CC in 40MHz... 99

6.1 When to Use LAOFD-001001 and LAOFD-001002... 99

6.2 Required Information... 99 6.3 Planning... 100 6.4 Deployment... 101 6.4.1 Requirements... 101 6.4.2 Data Preparation... 104 6.4.3 Precautions...106 6.4.4 Hardware Adjustment...109 6.4.5 Activation... 109

6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs...109

6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs...113

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

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

7.1 When to Use LAOFD-070201...152

7.2 Required Information... 152 7.3 Planning... 152 7.4 Deployment... 153 7.4.1 Requirements... 153 7.4.2 Data Preparation... 154 7.4.3 Precautions...154 7.4.4 Hardware Adjustment...154 7.4.5 Activation... 154 7.4.6 Activation Observation...155 7.4.7 Deactivation...155 7.5 Performance Monitoring...155 7.6 Parameter Optimization...155 7.7 Troubleshooting... 155

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

BBU...156

(6)

8.2 Required Information... 156 8.3 Planning... 156 8.4 Deployment... 157 8.4.1 Requirements... 157 8.4.2 Data Preparation... 158 8.4.3 Precautions...159 8.4.4 Hardware Adjustment...159 8.4.5 Activation... 160 8.4.6 Activation Observation...160 8.4.7 Deactivation...160 8.5 Performance Monitoring...161 8.6 Parameter Optimization...161 8.7 Troubleshooting... 161

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

backhaul... 162

9.1 When to Use LAOFD-080201...162

9.2 Required Information... 162 9.3 Planning... 162 9.4 Deployment... 163 9.4.1 Requirements... 163 9.4.2 Data Preparation... 165 9.4.3 Precautions...166 9.4.4 Hardware Adjustment...167 9.4.5 Activation... 167 9.4.6 Activation Observation...167 9.4.7 Deactivation...168 9.5 Performance Monitoring...168 9.6 Parameter Optimization...169 9.7 Troubleshooting... 169

10 Engineering Guidelines for LAOFD-080202 Carrier Aggregation for Uplink 2CC

[Trial]...170

10.1 When to Use LAOFD-080202...170

10.2 Required Information... 170 10.3 Planning... 170 10.4 Deployment... 170 10.4.1 Requirements... 171 10.4.2 Data Preparation... 172 10.4.3 Precautions...172 10.4.4 Hardware Adjustment...172 10.4.5 Activation... 172 10.4.6 Activation Observation...172 10.4.7 Deactivation...173

(7)

10.5 Performance Monitoring...173

10.6 Parameter Optimization...174

10.7 Troubleshooting... 174

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

in 40MHz and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz...175

11.1 When to Use LAOFD-080207 and LAOFD-080208... 175

11.2 Required Information...175 11.3 Planning... 175 11.4 Deployment...176 11.4.1 Requirements... 176 11.4.2 Data Preparation... 177 11.4.3 Precautions...177 11.4.4 Hardware Adjustment... 177 11.4.5 Activation...178 11.4.6 Activation Observation... 178 11.4.7 Deactivation... 178 11.5 Performance Monitoring...178 11.6 Parameter Optimization... 179 11.7 Troubleshooting... 179

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

[Trial]...180

12.1 When to Use LAOFD-081237...180

12.2 Required Information... 180 12.3 Planning... 180 12.4 Deployment... 181 12.4.1 Requirements... 181 12.4.2 Data Preparation... 181 12.4.3 Precautions...182 12.4.4 Hardware Adjustment...182 12.4.5 Activation... 182 12.4.6 Activation Observation...182 12.4.7 Deactivation...182 12.5 Performance Monitoring...182 12.6 Parameter Optimization...182 12.7 Troubleshooting... 182

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

FDD) [Trial]... 183

13.1 When to Use MRFD-101222...183 13.2 Required Information... 183 13.3 Planning... 183 13.4 Deployment... 184 13.4.1 Requirements... 184

(8)

13.4.2 Data Preparation... 186 13.4.3 Precautions...187 13.4.4 Hardware Adjustment...188 13.4.5 Activation... 188 13.4.6 Activation Observation...188 13.4.7 Deactivation...190 13.5 Performance Monitoring...190 13.6 Parameter Optimization...193 13.7 Troubleshooting... 193

14 Parameters...194

15 Counters... 324

16 Glossary...547

17 Reference Documents... 548

(9)

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

– LAOFD-00100104 Support of UE Category 7 – LAOFD-00100105 Support of UE Category 9 – LAOFD-00100106 Support of UE Category 10

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

l LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU l LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] l LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz l LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]

A trial feature is a feature that customers can use without paying for the license fee in the current version. In a later version, a trial feature may be deleted or become an optional feature. The license fee is required for optional features.

Before using a trial feature, customers need to sign a memorandum of understanding (MoU) with Huawei.

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases.

(10)

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 06 (2015-12-30)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

None None N/A

Editorial change

Revised the description of relaxed-backhaul-based inter-eNodeB CA in 3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul.

(11)

Change

Type Change Description Parameter Change AffectedEntity

Revised the description of the methods for determining cell load status in load-based SCell

configuration. For details, see 3.2.3.4 Load-based SCell Configuration.

None N/A

Revised the description of the switch setting related to SCell deactivation. For details, see 3.2.6 SCell

Deactivation.

None N/A

Revised the description of SCell configuration during handovers. For details, see 3.3.2 Mobility

Management Under CA.

None N/A

Revised the description of the switch settings related to congestion control. For details, see 3.3.3 Admission and Congestion Control Under CA.

None N/A

Revised the description of the scenario where MTA is

recommended. For details, see 3.3.9 MTA Under CA.

None N/A

Added the description of the impacted feature Emergency Call. For details, see 4.1 Features Related to LAOFD-001001 LTE-A

Introduction.

None N/A

Revised the description of hardware planning. For details, see 6.3 Planning.

None N/A

eRAN8.1 05 (2015-11-03)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

Added the function of setting a scheduling weight for CA UEs to basic scheduling. For details, see 3.3.4 Scheduling Under CA.

Added the parameter eNBCellRsvdPara.R svdU16Para2. Macro, micro, and LampSite eNodeBs

(12)

Change

Type Change Description Parameter Change AffectedEntity

Editorial change

Modified band combinations. For details, see 3.1.4 Band

Combinations.

None N/A

Revised the description of SCell deactivation. For details, see 3.2.6 SCell Deactivation.

None N/A

Revised the description of handover events under CA. For details, see 3.3.2 Mobility Management Under CA.

None N/A

Revised the description of deployment requirements in 6.4.1 Requirements.

None N/A

Revised the description of hardware planning for relaxed-backhaul-based inter-eNodeB CA. For details, see 9.3 Planning.

None N/A

Optimized the descriptions in this document.

None N/A

eRAN8.1 04 (2015-08-31)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

None None N/A

Editorial change

Revised the description of benefits. For details, see 2.2 Benefits.

None N/A

Revised the description of CA-related measurement events. For details, see 3.1.1 Related Concepts.

None N/A

Modified band combinations. For details, see 3.1.4 Band

Combinations.

None N/A

Revised the description of

measurement parameters. For details, see 3.2.3 SCell Configuration.

(13)

Change

Type Change Description Parameter Change AffectedEntity

Added the uplink traffic volume as a condition for SCell deactivation. For details, see 3.2.6 SCell Deactivation.

None N/A

Revised the description of UE-number-based admission control under CA. For details, see 3.3.3 Admission and Congestion Control Under CA.

None N/A

Revised the description of the features impacted by the LTE-A Introduction and Carrier Aggregation for Uplink 2CC features. For details, see: l 4.1 Features Related to LAOFD-001001 LTE-A Introduction l 4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

None N/A

Revised the description of the prerequisite features for the FDD +TDD Carrier Aggregation feature and license-related description. For details, see: l 4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] l 13.4.1 Requirements None N/A

Revised the description of the impact of LTE-A Introduction on the number of RRC_CONNECTED UEs. For details, see 5.1 LAOFD-001001 LTE-A Introduction.

None N/A

Revised the description of

deployment requirements for LTE-A Introduction. For details, see 6.4.1 Requirements.

None N/A

Modified the precautions for CA-group-based configuration mode. For details, see 6.4.3 Precautions.

(14)

Change

Type Change Description Parameter Change AffectedEntity

Revised the description of MML-based configurations in frequency-based and adaptive modes. For details, see 6.4.5.5 Using MML Commands.

None N/A

Added the description of SCell measurement periods to 6.6 Parameter Optimization.

None N/A

Revised and added descriptions of figures. For details, see:

l 2 Overview

l 3 Technical Description

None N/A

Revised descriptions in the entire document.

None N/A

eRAN8.1 03 (2015-06-30)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

None None N/A

Editorial change

Revised the description of event A6 in 3.1.1 Related Concepts.

None N/A

Revised the description of usage scenarios of CA in networks that support downlink 4x4 MIMO. For details, see 3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial].

None N/A

Modified band combinations. For details, see 3.1.4 Band

Combinations.

None N/A

Revised the description of load-based SCell configuration. For details, see 3.2.3.4 Load-based SCell

Configuration.

(15)

Change

Type Change Description Parameter Change AffectedEntity

Revised the description of mutually exclusive features of FDD+TDD CA. For details, see 4.10 Features Related to MRFD-101222 FDD +TDD Carrier Aggregation(LTE FDD) [Trial].

None N/A

Removed the requirements for EPC versions from the engineering guidelines for each feature.

None N/A

eRAN8.1 02 (2015-04-30)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

None None N/A

Editorial change

Revised the description of the functional architecture. For details, see 2.3 Architecture.

None N/A

Revised the description of typical scenario 5. For details, see 3.1.2.1 Typical Scenarios.

None N/A

Modified the total bandwidth descriptions. For details, see 3.1.3 CA Features.

None N/A

Revised the description of CA in networks that support downlink 4x4 MIMO. For details, see 3.1.3.9 LAOFD-081237 Carrier

Aggregation with DL 4x4 MIMO [Trial].

None N/A

Modified band combinations. For details, see 3.1.4 Band

Combinations.

None N/A

Revised the description of adaptive configuration. For details, see 3.2.3.3 Adaptive SCell Configuration.

(16)

Change

Type Change Description Parameter Change AffectedEntity

Revised the description of load-based SCell configuration. For details, see 3.2.3.4 Load-based SCell

Configuration.

None N/A

Modified the impacted features of LTE-A Introduction. For details, see 4.1 Features Related to

LAOFD-001001 LTE-A Introduction.

None N/A

Modified the impacted features of Carrier Aggregation for Uplink 2CC. For details, see 4.6 Features Related to LAOFD-080202 Carrier

Aggregation for Uplink 2CC [Trial].

None N/A

Revised the description of hardware planning. For details, see 6.3 Planning.

None N/A

Modified the precautions for

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

None N/A

Revised the description of hardware adjustment. For details, see 6.4.4 Hardware Adjustment.

None N/A

Modified the precautions for Inter-eNodeB CA based on Coordinated BBU. For details, see 8.4.3 Precautions.

None N/A

Modified the transmission networking requirements and precautions for Inter-eNodeB CA based on Relaxed backhaul. For details, see 9.4.1 Requirements and 9.4.3 Precautions.

None N/A

Modified the procedure for

deactivating Carrier Aggregation for Uplink 2CC. For details, see 10.4.7 Deactivation.

None N/A

Modified the license requirement of downlink 3CC aggregation. For details, see 11.4.1 Requirements.

(17)

eRAN8.1 01 (2015-03-23)

This issue includes the following changes. Change

Type Change Description Parameter Change AffectedEntity

Feature change

None None N/A

Editorial change

Revised the descriptions of UE categories in 3.1.3.1

LAOFD-001001 LTE-A Introduction.

None N/A

Revised the descriptions of Inter-eNodeB CA based on Coordinated 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

None N/A

Modified band combinations. For details, see 3.1.4 Band

Combinations.

None N/A

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

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

None N/A

Revised the description of hardware planning for FDD+TDD CA in 13.3 Planning.

(18)

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.

Change

Type Change Description Parameter Change AffectedEntity

Feature change

Added CA in distributed multi-BBU interconnection scenarios. For details, see 3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.

None Macro

eNodeBs

Added relaxed-backhaul-based inter-eNodeB CA. For details, see: l 3.1.3.5 LAOFD-080201

Inter-eNodeB CA based on Relaxed backhaul (feature description) 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 the option RelaxedBackhaul-CaSwitch to the parameter ENodeBAlgoSwitch. CaAlgoSwitch. Macro and micro eNodeBs

Added uplink 2CC aggregation. For details, see:

l 3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] (feature description) l 4.6 Features Related to

LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

l 5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] (network impact) l 10 Engineering Guidelines for

LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

Added the option CaUl2CCSwitch to the parameter CaMgtCfg.CellCaAl goSwitch. Macro eNodeBs

(19)

Change

Type Change Description Parameter Change AffectedEntity

Added downlink 3CC aggregation. For details, see:

l 3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz (feature description) l 3.1.3.8 LAOFD-080208 Carrier

Aggregation for Downlink 3CC in 60MHz (feature description) l 4.7 Features Related to

LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz

l 4.8 Features Related to LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz

l 5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz (network impact) l 5.8 LAOFD-080208 Carrier

Aggregation for Downlink 3CC in 60MHz (network impact) l 11 Engineering Guidelines for

LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz

Added the option CaDl3CCSwitch to the parameter CaMgtCfg.CellCaAl goSwitch. Macro eNodeBs

Added AMBR-based control over the number of UEs configured with SCells. For details, see 3.2.3 SCell Configuration.

Added the following parameters: l CaMgtCfg.CellM axPccNumber l CaMgtCfg.CaAm brThd Macro, micro, and LampSite eNodeBs

(20)

Change

Type Change Description Parameter Change AffectedEntity

Added CA in DL 4x4 MIMO scenarios. For details, see:

l 3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] (feature description) l 4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] l 5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] (network impact) l 12 Engineering Guidelines for

LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]

None Macro

(21)

Change

Type Change Description Parameter Change AffectedEntity

Added FDD+TDD CA. For details, see: l 3.1.3.10 MRFD-101222 FDD +TDD Carrier Aggregation(LTE FDD) [Trial] (feature description) l 4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] l 5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] (network impact)

l 13 Engineering Guidelines for MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] l Added the following options to the parameter ENodeBAlgoSwi tch.CaAlgoSwitc h: –InterFddTddC aSwitch –CaDl4CCSwit ch l Added the following parameters: –ENodeBFram eOffset.FddFr ameOffsetENodeBFram eOffset.TddFr ameOffsetCellFrameOff set.LocalCellI dCellFrameOff set.FrameOffs etModeCellFrameOff set.FrameOffs et

l Added the option FDDTDD to the parameter CaGroup.CaGro upTypeInd. Macro eNodeBs

Added implementation of features in CA scenarios. For details, see: l 3.3.8 Power Backoff Under CA l 3.3.9 MTA Under CA

None Macro,

micro, and LampSite eNodeBs

(22)

Change

Type Change Description Parameter Change AffectedEntity

Added adaptive configuration mode. For details, see:

l 3.2.1 Overview l 3.2.2.2 Frequency-based or 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 option AdpCaSwitch to the ENodeBAlgoSwitch. CaAlgoSwitch parameter. Macro, micro, and LampSite eNodeBs

Added the following sub-features to LAOFD-001001 LTE-A

Introduction, as described in 1.1 Scope and 3.1.3 CA Features: l LAOFD-00100103 Support of UE Category 6 l LAOFD-00100104 Support of UE Category 7 l LAOFD-00100105 Support of UE Category 9 l LAOFD-00100106 Support of UE Category 10 None Macro, micro, and LampSite eNodeBs

Deleted the following sub-features from LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz (see 1.1 Scope and 3.1.3 CA Features):

l LAOFD-00100201 Carrier Aggregation for Downlink 2CC in 40MHz l LAOFD-00100202 Support of UE Category 6 None Macro, micro, and LampSite eNodeBs

Added band combinations. For details, see 3.1.4 Band

Combinations.

None Macro,

micro, and LampSite eNodeBs

(23)

Change

Type Change Description Parameter Change AffectedEntity

Changed the name of

LAOFD-070201 from "CA for Downlink 2CC From Multiple Carriers" to "Flexible CA from Multiple Carriers". For details, see: l 3.1.3.3 LAOFD-070201 Flexible

CA from Multiple Carriers (feature description)

l 4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers

l 5.3 LAOFD-070201 Flexible CA from Multiple Carriers

(network impact)

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

None Macro,

micro, and LampSite eNodeBs

Added load-based SCell

configuration. For details, see 3.2.3.4 Load-based SCell Configuration.

Added the option SccSmartCfgSwitch to the parameter ENodeBAlgoSwitch. CaAlgoSwitch. Macro, micro, and LampSite eNodeBs Added PCC anchoring at RRC

connection releases. For details, see 3.2.8 PCC Anchoring (at RRC Connection Releases).

Added the option IdleModePccAncho rSwitch to the parameter ENodeBAlgoSwitch. CaAlgoSwitch. Macro, micro, and LampSite eNodeBs Editorial change

None None N/A

1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs

Feature ID Feature Name Supported

by Macro eNodeBs Supporte d by Micro eNodeBs Supported by LampSite eNodeBs

(24)

Feature ID Feature Name Supported by Macro eNodeBs Supporte d by Micro eNodeBs Supported by LampSite eNodeBs LAOFD-001001 01 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz

Yes Yes Yes

LAOFD-001001 02

Inter-Band Carrier Aggregation for

Downlink 2CC in 20MHz

Yes Yes Yes

LAOFD-001001 03

Support of UE Category 6 Yes Yes Yes

LAOFD-001001 04

Support of UE Category 7 Yes Yes Yes

LAOFD-001001 05

Support of UE Category 9 Yes Yes Yes

LAOFD-001001 06

Support of UE Category 10

Yes Yes Yes

LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz

Yes Yes Yes

LAOFD-070201 Flexible CA from Multiple Carriers

Yes Yes Yes

LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU

Yes No Yes

LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul

Yes Yes No

LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

Yes No Yes

LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz

Yes No Yes

LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz

Yes No Yes

LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] Yes No No MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] Yes No No

(25)

Function Implementation in Macro, Micro, and LampSite eNodeBs

(26)

2

Overview

2.1 Introduction

3rd Generation Partnership Project (3GPP) requires LTE-Advanced networks to provide a downlink peak data rate of 1 Gbit/s. However, radio spectrum resources are so scarce that in most cases an operator owns only non-adjacent chunks of the spectrum. Due to the limited bandwidth of a single chunk of the spectrum, the 1 Gbit/s data rate requirement is hard to meet.

To deal with this situation, 3GPP specifications Release 10 introduced carrier aggregation (CA) to LTE-Advanced networks, allowing aggregation of contiguous or non-contiguous carriers. These carriers are called component carriers (CCs). CA achieves wider bandwidths (a maximum of 100 MHz). Figure 2-1 shows CA for UEs.

Figure 2-1 CA for UEs

During CA, upper-layer data streams are mapped to individual component carriers (CCs) at the Media Access Control (MAC) layer in LTE-Advanced networks. An eNodeB constructs one (two or more in the case of spatial multiplexing) transport block (TB) in each

transmission time interval (TTI) for each CC. Each CC uses its own hybrid automatic repeat request (HARQ) entities and link adaptation mechanism. Therefore, the LTE-Advanced system can inherit single-carrier-based physical layer designs from the LTE system. 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. For details about the configuration modes, see 3.2.1 Overview.

(27)

2.2 Benefits

CA achieves wider bandwidth and allows a CA-capable UE (referred to as CA UE in this document) to use idle resource blocks (RBs) on non-contiguous CCs. With CA enabled, a single UE can reach higher uplink and downlink peak data rates. Figure 2-2 shows the benefits of CA.

Figure 2-2 Benefits of CA

2.3 Architecture

Functional Architecture

The functional architecture for CA includes primary component carrier (PCC) anchoring, SCell configuration, and transitions between SCell states. For details, see 3.2 Carrier Management. This architecture also includes special implementation of other features under CA, as described in 3.3 Other Key Techniques Under CA.

Huawei CA operates in accordance with the following constraints, which are stipulated in 3GPP TS 36.300 of Release 10:

l In the uplink or downlink, a CA UE supports the aggregation of up to five CCs, each with a maximum bandwidth of 20 MHz. Currently, Huawei eNodeBs support the aggregation of no more than three FDD CCs or a combination of four FDD and TDD CCs, each with a maximum bandwidth of 20 MHz.

l CA UEs support asymmetric CA. A UE may use different numbers of CCs in the uplink and downlink. However, the number of CCs in the downlink must always be greater than or equal to the number of CCs in the uplink. In addition, the uplink CCs must be

included in the set of downlink CCs. Currently, Huawei eNodeBs support the

aggregation of two CCs in the uplink and the aggregation of two CCs, three CCs, or a combination of four FDD and TDD CCs in the downlink.

l Each CC uses the same frame structure as 3GPP Release 8 carriers to support backward compatibility.

l 3GPP Release 8 or 9 UEs are allowed to transmit and receive data on Release 10 CCs.

Protocol Stack Architecture

The uplink and downlink air-interface protocol stack with CA enabled has the following characteristics:

(28)

l A single radio bearer has only one Packet Data Convergence Protocol (PDCP) entity and one Radio Link Control (RLC) entity. In addition, the number of CCs at the physical layer is invisible to the RLC layer.

l User-plane data scheduling at the MAC layer is performed separately for individual CCs. l Each CC has an independent set of transport channels and separate HARQ entities and

retransmission processes.

Figure 2-3 shows the uplink and downlink air-interface protocol stack with CA enabled. Figure 2-3 Uplink and downlink air-interface protocol stack with CA enabled

ARQ: automatic repeat request ROHC: robust header compression

(29)

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

(30)

Related Events

l Event A2

Event A2 indicates that the signal quality of the serving cell becomes lower than a specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.

l Event A3

Event A3 indicates that the signal quality of the PCell's neighboring cell becomes higher than that of the PCell. For details, see Intra-RAT Mobility Management in Connected Mode.

l Event A4

Event A4 indicates that the signal quality of a neighboring cell becomes higher than a specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.

l Event A5

Event A5 indicates that the signal quality of the PCell becomes lower than a specific threshold and the signal quality of a neighboring cell becomes higher than another specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.

l Event A6

Event A6 indicates that the signal quality of an SCell's intra-frequency neighboring cell becomes higher than that of the SCell. If the eNodeB receives an event A6 report, it changes the SCell while keeping the PCell unchanged.

The entering condition for event A6 is as follows: Mn + Ocn - Hys > Ms + Ocs + Off. The following explains the variables involved:

Mn is the RSRP measurement result of a neighboring cell.

Ocn is the cell-specific offset for an intra-frequency neighboring cell. The offset is specified by the EutranIntraFreqNCell.CellIndividualOffset parameter.

Hys is the hysteresis for event A6. The value of this variable is always 0.Ms is the RSRP measurement result of the serving cell.

Ocs is the cell-specific offset for the serving cell. The offset is specified by the Cell.CellSpecificOffset parameter.

Off is the offset for event A6. The offset is specified by the CaMgtCfg.CarrAggrA6Offset parameter.

For details about this event, see section 5.5.4.6a "Event A6 (Neighbour becomes offset better than SCell)" in 3GPP TS 36.331 V10.12.0.

NOTE

If the CellMcPara.TimetoTrigger parameter is set to a value greater than the value (3s) of the timer for gap-assisted measurement, measurement results cannot be reported.

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 carriers are intra-eNodeB carriers in these scenarios. In 3GPP

specifications, 2CC aggregation is used as an example. Table 3-1 lists the typical scenarios and whether Huawei eNodeBs support the scenarios. The following features apply to the typical scenarios:

(31)

l LAOFD-001001 LTE-A Introduction

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

l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] l LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz l LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]

Table 3-1 Typical scenarios for using CA and Huawei eNodeBs' support

Typical Scenario Supported by

Huawei eNodeBs Remarks

Scenario 1: intra-eNodeB co-coverage carriers Yes None Scenario 2: intra-eNodeB different-coverage carriers Yes None Scenario 3: intra-eNodeB carriers (one for macro coverage; another for edge coverage)

Yes eNodeBs support this scenario in

frequency-based and adaptive configuration modes but not in CA-group-based configuration mode. NOTE

For details about the configuration modes, see 3.2.1 Overview. Scenario 4:

intra-eNodeB carriers (one provided by the site; another provided by remote radio heads [RRHs])

Yes l In frequency-based or adaptive

configuration mode, eNodeBs support this scenario when the ratio of macro cells to RRHs is 1:N (N ≥ 1).

l In CA-group-based

configuration mode, eNodeBs support this scenario when the ratio of macro cells to RRHs is 1:1.

Scenario 5: intra-eNodeB carriers (one provided only by the site; another provided by the site and a repeater)

Yes None

The following figures show the typical scenarios. In the figures, F1 and F2 denote two carrier frequencies.

(32)

Figure 3-1 Intra-eNodeB co-coverage carriers

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)

(33)

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.

of UL CCs Max. No.of DL CCs Max. TotalBW Description

LAOFD-001001 LTE-A Introduction 1 (CA not supported) 2 (2CC aggregation supported)

20 MHz This feature allows

aggregation of two downlink CCs (referred to as downlink 2CC aggregation in this document) to a maximum bandwidth of 20 MHz. LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz

1 2 40 MHz This feature allows

downlink 2CC aggregation to a maximum bandwidth of 40 MHz. LAOFD-070201 Flexible CA from Multiple Carriers

1 4 80 MHz This feature enables an

eNodeB to select the most suitable downlink carriers for CA.

(34)

Feature Max. No.

of UL CCs Max. No.of DL CCs Max. TotalBW Description

LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU

1 4 80 MHz This feature allows

downlink CA between inter-eNodeB cells in multi-BBU interconnection scenarios. LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul

1 2 40 MHz This feature allows

downlink 2CC aggregation between inter-eNodeB cells in scenarios with relaxed backhaul requirements. LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

2 2 40 MHz This feature allows

aggregation of two uplink CCs (referred to as uplink 2CC aggregation in this document) to a maximum bandwidth of 40 MHz. LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz

1 3 40 MHz This feature allows

aggregation of three downlink CCs (referred to as downlink 3CC aggregation in this document) to a maximum bandwidth of 40 MHz. LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz

1 3 60 MHz This feature allows

downlink 3CC aggregation to a maximum bandwidth of 60 MHz. LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]

1 4 80 MHz This feature allows

downlink CA to a maximum bandwidth of 80 MHz on networks that support 4T MIMO.

(35)

Feature Max. No.

of UL CCs Max. No.of DL CCs Max. TotalBW Description

MRFD-101222 FDD+TDD Carrier

Aggregation(LT E FDD) [Trial]

1 4 80 MHz This feature allows

aggregation of at most four downlink FDD and TDD CCs to a maximum bandwidth of 80 MHz.

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 Figure 3-6.

Figure 3-6 Intra-band CA for downlink 2CC in 20 MHz

The time alignment error between two intra-band contiguous or non-contiguous CCs must be less than 130 ns or 260 ns, respectively.

This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 20 MHz for a CA UE.

l LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz Inter-band CA aggregates two carriers from different frequency bands for downlink data transmission to one CA UE, as shown in Figure 3-7.

(36)

The time alignment error between two inter-band CCs must be less than 260 ns. This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 20 MHz for a CA UE.

l LAOFD-00100103 Support of UE Category 6

This sub-feature enables CA for UEs of category 6, which is defined in 3GPP TS 36.306 V10.0.0.

With this sub-feature, a UE of category 6 can reach a peak data rate of 300 Mbit/s in the downlink and 50 Mbit/s in the uplink.

l LAOFD-00100104 Support of UE Category 7

This sub-feature enables CA for UEs of category 7, which is defined in 3GPP TS 36.306 V12.0.0.

With this sub-feature, a UE of category 7 can reach a peak data rate of 300 Mbit/s in the downlink and 100 Mbit/s in the uplink.

l LAOFD-00100105 Support of UE Category 9

This sub-feature enables CA for UEs of category 9, which is defined in 3GPP TS 36.306 V12.0.0.

With this sub-feature, a UE of category 9 can reach a peak data rate of 450 Mbit/s in the downlink and 50 Mbit/s in the uplink.

l LAOFD-00100106 Support of UE Category 10

This sub-feature enables CA for UEs of category 10, which is defined in 3GPP TS 36.306 V12.0.0.

With this sub-feature, a UE of category 10 can reach a peak data rate of 450 Mbit/s in the downlink and 100 Mbit/s in the uplink.

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. Figure 3-8 shows CA for downlink 2CC in 40 MHz. Figure 3-8 CA for downlink 2CC in 40 MHz

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.

(37)

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. Figure 3-9 shows flexible CA from multiple carriers.

Figure 3-9 Flexible CA from multiple carriers

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

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.

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

(38)

NOTE

In multi-BBU interconnection scenarios, each pair of BBUs are inter-eNodeB BBUs.

Figure 3-10 shows inter-eNodeB CA based on coordinated BBUs. For details about

centralized multi-BBU interconnection, see USU3900-based multi-BBU interconnection. For details about distributed multi-BBU interconnection, see USU3910-based multi-BBU interconnection.

Figure 3-10 Inter-eNodeB CA based on coordinated 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

This feature allows inter-eNodeB CA in relaxed backhaul scenarios where 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.

Since eRAN8.1, CA has also applied to inter-eNodeB cells in relaxed backhaul scenarios. The cells can be macro cells or a combination of macro and micro cells. Figure 3-11 shows inter-eNodeB CA based on relaxed backhaul.

Figure 3-11 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

(39)

transport module of the micro eNodeB. When one-way delay and round trip time between eNodeBs are not greater than 4 ms and 8 ms, respectively, downlink 2CC aggregation increases the downlink average data rate of a CA UE by 40%–80% and peak data rate by more than 80%, compared with the data rates of a non-CA UE. The data rate reaches the peak value when the CA UE is the only UE in the cell and is located in the cell center.

NOTE

l After CA is enabled, the transmission delay for CA-group-based configuration mode can be queried by running the DSP CAGROUPCELL command, and that for frequency-based or adaptive configuration mode can be queried by running the DSP PCCSCELLLIST command. Frequency-based or adaptive configuration mode is recommended for inter-eNodeB CA Frequency-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:

If the pair of eNodeBs are both macro eNodeBs, RelaxedBackhaulCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs. – If the eNodeBs are a pair of macro and micro eNodeBs,

RelaxedBackhaulCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs. In addition, HetNetCaSwitch under this parameter must also be on for the micro eNodeB.

3. After activating the SCell, the eNodeB that serves the PCell will divert RLC traffic of the CA UE from the PCell to the SCell. When inter-eNodeB transmission quality

deteriorates (for example, the transmission delay does not meet requirements or transmission is interrupted), the eNodeB removes the SCells to exit inter-eNodeB CA. The eNodeB may configure SCells again at UE access, an incoming handover, or an RRC connection re-establishment after transmission quality recovers.

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. With this inter-eNodeB CA feature, the PCell supports LBFD-060103 Enhanced DL Frequency Selective Scheduling but SCells do not.

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.

(40)

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-band contiguous or non-contiguous carriers or two inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-12 shows uplink 2CC aggregation.

Figure 3-12 Uplink 2CC aggregation

This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 40 MHz for a CA UE in the uplink.

This feature is dependent on the uplink CA capabilities of UEs and the setting of CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter. It requires LAOFD-001001 LTE-A Introduction to be activated. Therefore, after LAOFD-080202 is enabled, two carriers can be aggregated for both uplink and downlink transmission. LAOFD-080202 works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz

This feature allows a maximum of 40 MHz downlink bandwidth for a CA UE. By aggregating three intra- or inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-13 shows CA for downlink 3CC in 40 MHz.

(41)

Figure 3-13 CA for downlink 3CC in 40 MHz

This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 40 MHz for a CA UE in the downlink.

This feature is dependent on the downlink CA capabilities of UEs and the setting of CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.

To meet the transmission requirements of acknowledgments (ACKs) and negative ACKs (NACKs) for three carriers, PUCCH format 3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.

This feature works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz

This feature allows a maximum of 60 MHz downlink bandwidth for a CA UE. By aggregating three intra- or inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-14 shows CA for downlink 3CC in 60 MHz.

(42)

Figure 3-14 CA for downlink 3CC in 60 MHz

This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 60 MHz for a CA UE in the downlink.

This feature is dependent on the downlink CA capabilities of UEs and the setting of CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.

To meet the transmission requirements of ACKs and NACKs for three carriers, PUCCH format 3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.

This feature works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]

This feature allows CA in networks that support 4T MIMO. Figure 3-15 shows CA with DL 4x4 MIMO.

(43)

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.

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 and other MIMO-related concepts and principles, see MIMO. This feature supports 2CC and 3CC aggregation in typical and multi-BBU interconnection scenarios and supports only 2CC aggregation in relaxed-backhaul-based inter-eNodeB CA.

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. Figure 3-16 shows FDD+TDD CA.

(44)

In this feature, only FDD carriers can be PCCs of CA UEs. TDD cells must use uplink-downlink configuration 1 or 2. There is no subframe configuration requirement for FDD cells. If a frame offset is configured for a TDD cell, the same frame offset must be specified for the FDD cells involved in CA.

NOTE

For details about the principles and engineering guidelines for subframe configuration, see Subframe

Configuration for LTE TDD.

This feature is dependent on the downlink CA capabilities of UEs and the setting of InterFddTddCaSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.

This feature works in typical scenarios and between eNodeBs in relaxed backhaul scenarios. In typical scenarios, downlink 2CC, 3CC, or 4CC aggregation works. However, in relaxed backhaul scenarios, only downlink 2CC aggregation between macro cells works.

3.1.4 Band Combinations

3GPP-defined Band Combinations

eNodeBs support the band combinations defined in section 5.6A.1 "Channel bandwidths per operating band for CA" of 3GPP TS 36.101 V11.7.0.

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.

(45)

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 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 Reconfiguration is required if a band combination that consists of some bands within the band range of an operator-defined band combination is not defined in 3GPP specifications either or if the operator has special requirements for the band combination.

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. FDD+TDD CA does not apply to carriers with the 1.4 MHz or 3 MHz channel bandwidth.

3.2 Carrier Management

3.2.1 Overview

Features Involved

Carrier management involves the following features: l LAOFD-001001 LTE-A Introduction

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

l LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU l LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul l LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] l LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz l LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz l LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] l MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]

Procedures Involved

Carrier management involves the following procedures for CA UEs: l PCC anchoring

PCC anchoring, during which the PCell is selected, occurs when CA UEs initially access networks or when their RRC connections are released. It does not occur during incoming handovers or RRC connection re-establishments. During PCC anchoring, an eNodeB selects a PCell for a CA UE based on PCell or PCC priorities. For details about PCC anchoring at initial access, see 3.2.2 PCC Anchoring (at Initial Access). For details about PCC anchoring at an RRC connection release, see 3.2.8 PCC Anchoring (at RRC Connection Releases).

NOTE

(46)

l SCell configuration, change, activation, deactivation, and removal

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

Figure 3-17 shows the transitions between the SCell states. Figure 3-17 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, as shown in Figure 3-18. Only the cells in the group can be aggregated.

References

Related documents

HKEY LOCAL MACHINE SOFTWARE Microsoft Windows CurrentVersion Uninstall Spri nt virtual assistant Dealer diagnostic program for cars PEUGEOT CITROEN.. - All the skills involved

To examine whether this saliency of the eye region at the early stage of face inspection is attributed to its local structure properties or to the knowledge of its essence in facial

Opinion dynamics influences the ↵ value that regulates the number of shares in which the secret messages are divided and distributed from each DS node to the rest of the network

o To determine the academic preparedness of the postgraduate students of the Faculty Community Health Science (FCHS) at the University of the Western Cape (UWC) as evidenced

If you need assistance to design your matching network beyond this application note, please contact support@ignion.io, or try our free-of-charge 1 NN Wireless Fast-Track

5.12.1 Prior to commencing work or services under this Quote, Contractor shall furnish the County with certificates of insurance, or formal endorsements as required by the Contract

We put emphasis on Type 3 model, since this type of bivariate PCSDE models are useful in explaining the existence of bivariate power law data in social networks, web networks

They sometimes quilted tops others had pieced, but since their large family could keep a steady supply of scrap material coming in, they found it more profitable to make