Zte - Ca

ZTE LTE FDD Carrier Aggregation Feature Guide Page 1 of 111
ZTE LTE FDD Carrier Aggregation Feature Guide
ZTE LTE FDD Carrier Aggregation Feature Guide

Version Date Author Reviewer Notes
1. Add new feature:
Carrier Aggregation(DL 4CC,
FDD+TDD)
Carrier Aggregation(DL 5CC,
FDD+TDD)
Luo Su, 2. Add Uplink Inter-eNodeB CA in

V1.0 2018-01-30 Wang Min
Mi Dezhong Chapter 3.10.5
3. Update Downlink multi-carrier CA

in Chapter 3.9
4. Configuration and validation parts

are updated.
ZLF34-00-035 RRC user based CA
Z h a n g Luo Su, enable and backoff is modified to
V1.1 2018-06-30
Junpeng Mi Dezhong “Load and Service Monitor Based
Scell Dynamic Configuration”.
Correct one configuration mistake:
Luo Su, For intra-eNodeB F+T, X2+IP does
V1.2 2018-09-25 Su Shaohua
Mi Dezhong not need to be configured. For
details, see Chapter 4.4.1.
TABLE OF CONTENTS
1 Introduction
1.1 Feature Attribute
1.2 Related Feature List and License Control
1.3 Correlation with Other Feature
1.3.1 ZLF34-00-016 Carrier Aggregation(UL CA)
1.3.2 ZLF34-00-017Carrier Aggregation(DL 3CC)
1.3.3 ZLF34-00-034 Cloud CA (centralized)
1.3.4 ZLF34-00-027Carrier Aggregation(DL 2CC, FDD+TDD)
1.3.5 ZLF34-00-036Flexible SCell Configuration of Multi-Carriers
1.3.6 ZLF34-00-049 Carrier Aggregation(DL 3CC, FDD+TDD)
1.3.7 ZLF34-00-051Cloud CA (Distributed)
2 Function Description
3 Technical Description
3.1 Technical Principle
3.2 Application Scenario
3.3 Carrier Aggregation Networking
3.3.1 Intra/Inter-Board CA
3.3.2 FDD+TDD Carrier Aggregation
3.3.3 Inter-eNodeB Carrier Aggregation
3.4 Carrier Aggregation Type
3.4.1 Intra-Band Contiguous CA
3.4.2 Intra-Band Non-Contiguous CA
3.4.3 Inter-Band CA
3.4.4 Band Combination Supported by Protocols
3.5 Admission Control in CA Scenario
3.5.1 User-Based Admission Control
3.5.2 PRB Usage-Based Admission Control
3.6 Specify Pcell of UE According to Frequency Priority
3.7 SCC Management in CA
3.7.1 SCC Selection
3.7.2 SCC Configuration and De-Configuration
3.7.3 SCC Activation and Deactivation
3.8 Scheduling of CA
3.9 Downlink Multi-Carrier Aggregation
3.9.1 SCell Addition/Release/Modification
http://127.0.0.1:8890/go_outfiles/Lib20180326fdd35_R1_2/documents/153958749428... 23/1/2019
3.9.2 PUCCH Configuration

3.9.3 Activation/Deactivation
3.9.4 CQI Feedback
3.10 Uplink CA
3.10.1 Uplink Congestion Judgment
3.10.2 Activation Strategy
3.10.3 Explicit deactivation strategy
3.10.4 Implicit deactivation strategy
3.10.5 Uplink Inter-eNodeB CA
3.10.6 Function Constraints
3.11 Handover of CA
3.12 Carrier Aggregation in Network Sharing
3.13 Monitoring Based SCell Addition
3.14 Service Based PCC Dynamic Selection
4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
4.1.2 EPC Requirements
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
4.1.4 UE Requirement
4.1.5 Transmission Bandwidth Requirements
4.1.6 FTP Server Requirements
4.2 Related parameters
4.2.1 CA Configuration Parameters
4.2.2 Active/De-active Parameters
4.2.3 FDD + TDD CA Configuration Parameters
4.2.4 Cloud CA Configuration Parameters
4.2.5 Primary Carrier Frequency Priority Parameters
4.2.6 CA Fair scheduling parameters
4.2.7 Flexible SCell Selection parameters
4.2.8 User-Based Admission parameters
4.2.9 CA UE Monitor parameters
4.2.10 CA UE Handover with SCell parameters
4.3 Intra/Inter-Board CA (DL 2CC)
4.3.1 Enabling the Feature
4.3.2 Data Synchronization
4.3.3 Disabling the Feature
4.4 DL Multi-Carrier Aggregation (FDD+TDD)
4.5 Carrier Aggregation (DL 3CC)
4.6 Carrier Aggregation (UL 2CC)
4.7 Cloud CA (Centralized)
4.8 Other Relevant Configuration
4.8.1 Configuring Measurement Parameter for Adding CA SCell
4.8.2 Configuring Measurement Parameter for Removing CA SCell
4.8.3 Configuring Measurement Parameter for Modifying CA SCell
4.8.4 Configuring Carrier Aggregation Parameter
4.8.5 Configuring CAPrimary Carrier Frequency Priority
4.8.6 Configuring CA Fair scheduling
4.8.7 Configuring Flexible SCell Selection
4.8.8 Configuring User-Based Admission
4.8.9 Configuring CA UE Monitor
4.8.10 Configuring CA UE Handover with SCell
5 Related Counters, KPI and Alarms

5.1 Related Counters
5.2 Related KPI
5.3 Related Alarms
6 Feature Validation
6.1 DL Inter-Band Carrier Aggregation (2CC)
6.1.1 Topology
6.1.2 Test Specification
6.1.3 Test Result
6.2 Non-contiguous Intra-Band Carrier Aggregation
6.2.1 Topology
6.2.3 Test Result
6.3 Contiguous Intra-Band Carrier Aggregation
6.3.1 Topology
6.3.3 Test Result
6.4 SCell Adding and Deleting Test
6.4.1 Topology
6.4.3 Test Result
6.5 SCell Modifying Test(A6 Event)
6.5.1 Topology
6.5.3 Test Result
6.6 SCell Activating and Deactivating
6.6.1 Topology
6.6.3 Test Result

6.7 Handover of CA
6.7.1 Topology
6.7.3 Test Result
6.8 CA Primary Carrier Frequency Priority
6.8.1 Topology
6.8.3 Test Result
6.9 Carrier Aggregation(DL 3CC)
6.9.1 Topology
6.9.3 Test Result
6.10 Carrier Aggregation(DL 2CC, FDD+TDD)
6.10.1 Topology
6.10.3 Test Result
6.11 Carrier Aggregation (UL CA)
6.11.1 Topology
6.11.3 Test Result
6.12 Flexible SCell Configuration of Multi-Carriers
6.12.1 SCC Selection Based on Frequency Priority
6.12.2 SCC Selection Based on Cell Load
6.13 Cloud CA with Ideal Backhaul (Centralized)
6.13.1 Topology
6.13.3 Test Result
6.14 RRC User Based CA Enable
6.14.1 Topology
6.14.3 Test Result
6.15 RRC User Based CA Back Off
6.15.1 Topology
6.15.3 Test Result
6.16 Cloud CA with Non-Ideal Backhaul (Distributed)
6.16.1 Topology
6.16.3 Test Result
6.17.1 Topology
6.17.3 Test Result
6.18.1 Topology
6.18.3 Test Result
6.19.1 Topology
6.19.3 Test Result
6.20 Carrier Aggregation(DL 5CC, 1FDD+4TDD)
6.20.1 Topology
6.20.3 Test Result
6.21.1 Topology
6.21.3 Test Result
7 Impact on Network
8 Abbreviations
9 References
10 Attachments
FIGURES
Figure 2-1 Carrier aggregation scenarios

Figure 3-1 Frequency Priority-Based SCC Selection Flow
Figure 3-2 Load-Based SCC Selection flow
Figure 3-3 Initial SCC Configuration when neighbor relationship is same coverage or containing
Figure 3-4 Initial SCC Configuration when neighbor relationship is neighboring
Figure 3-5 SCC De-configuration Procedure Based on Measurement
Figure 4-1 Frequency Space Mode
Figure 4-2 SCellAddition
Figure 4-3 Configuring the Switch of CA
Figure 4-4 Configuring Frequency and Bandwidth of CA Cells
Figure 4-5 Adding the CR0 Board
Figure 4-6 Configure the CR0 Board
Figure 4-7 Neighbor Cell Management

Figure 4-8 Configuring Neighbor Relation
Figure 4-9 Configuring Neighbor Relation 2
Figure 4-10 Complete Neighbor Relation 3
Figure 4-11 Neighbor Relation Configuration Records
Figure 4-12 Cell Coordination Management
Figure 4-13 Query Cell Configuration Information of eNodeB
Figure 4-14 Configuring Cell Listof eNodeB
Figure 4-15 Coordination Configuration
Figure 4-16 Selecting SCell
Figure 4-17 DL CA Configuration Complete
Figure 4-18 PUCH and PDCH List
Figure 4-19 PUCCH 1bConfiguration
Figure 4-21 Select the eNodeB to split CA Coordination
Figure 4-22 Add FS5CBoard
Figure 4-23 Configuring X2+IP Configuration
Figure 4-24 Configuring the Switch for CA between FDD and TDD
Figure 4-25 Configuring the Switch for 3CC CA between FDD and TDD
Figure 4-26 Configuring PUCCH Format Resources
Figure 4-27 Configuring the Max SCell Num for CA
Figure 4-29 Modify The RB number of PUCCH format 3
Figure 4-30 Configuring the neighbor relation of DL 3cells CA
Figure 4-31 Configure the Coordination relation of DL 3cells CA
Figure 4-32 Configuring the UL CA coordination relation
Figure 4-33 Configuring Collaborative Relation Type
Figure 4-34 Complete CA Configuration
Figure 4-35 Configure Clock Device
Figure 4-36 Configure Clock Synchronization mode
Figure 4-37 Configuring CR0 Board
Figure 4-38 Configure X2+(FDD) of CR0 Board
Figure 4-39 Createnew X2+IP Configuration
Figure 4-40 Configuring SCTP
Figure 4-41 Configure the Co-eNodeB X2 + Port IP Link Table
Figure 4-42 UE E-UTRAN Measurement List
Figure 4-43 UE E-UTRAN Measurement Window
Figure 4-44 Configuring the Parameter RSRP Absolute Threshold of Event Decision for A4 Event
Figure 4-45 Configuration Record for Remove SCell Measurement
Figure 4-46 Modify the Parameter RSRP Absolute Threshold of Event Decision for A2 Event
Figure 4-49 Carrier Aggregation Config List Window
Figure 4-50 Modify the RB Ratio Threshold for SCC Activating/Deactivating
Figure 4-51 Modify the Primary carrier frequency priority switch for CA
Figure 4-52 Add a frequency priority of Pcell record
Figure 4-53 Modify the Switch for fixed Primary carrier based measurement
Figure 4-54 Open the Switch of CA Fair Schedule
Figure 4-55 Modify the Factor of CA Fair Schedule
Figure 4-56 Configuring the Switch for Selecting SCell flexibility
Figure 4-57 Configuring SCell frequency priority
Figure 4-58 Modify the Switch of CA User Restrict
Figure 4-59 Configuring the Switch of CA UE Backoff
Figure 4-60 Modify the Switch of CA UE Monitor
Figure 4-61 Modify the Switch of CA UE Handover with SCell
Figure 6-1 Intra-eNodeB Carrier Aggregation Test
Figure 6-2 UE Capability Information
Figure 6-3 SCell Adding Successfully
Figure 6-4 CA UE Attached Successfully
Figure 6-5 Downlink Throughput of PCell and SCell
Figure 6-6 Measurement Configuration for SCC Adding in the RRC Connection Reconfiguration Message
Figure 6-7 UE Sends the Measurement Report Message
Figure 6-8 eNodeBSends the RRC Connection Reconfiguration Message, Adding the Cell with PCI=78 to SCell
Figure 6-9 SCC Is Activated
Figure 6-10 Downlink Throughput in the Contiguous Intra-Band Carrier Aggregation
Figure 6-11 A2 Event Sending

Figure 6-12 A2 Measurement Reporting
Figure 6-13 eNodeB Sends A4 Event Configuration of SCell and Deletes SCell
Figure 6-14 A4 Measurement Event Reporting
Figure 6-15 A4 Measurement Reporting Triggers Adding SCell
Figure 6-16 A6 Event Configuration
Figure 6-17 A6 Measurement Report
Figure 6-18 Deletes Old SCell and Adds New SCell
Figure 6-19 MAC CE for Activating SCell
Figure 6-20 Scheduling Information after SCC Activating
Figure 6-21 MAC CE for Deactivating SCell
Figure 6-22 Scheduling Information after SCC Deactivated
Figure 6-23 Inter-eNodeB Carrier Aggregation Test
Figure 6-24 UE Sends the Measurement Report Message of Handover A3 Event
Figure 6-25 Indicate UE to Delete SCell and be Handover to Target Cell
Figure 6-26 Handover Completes
Figure 6-27 eNodeB Sends the RRC Connection Reconfiguration Message to Add SCell
Figure 6-28 UE Sends the RRC Connection Reconfiguration Complete Message to eNodeB after the SCell Adding Successfully
Figure 6-29 eNodeB Indicates UE to Measure the SCC
Figure 6-30 UE Sends the Measurement Report Message for A4 Event
Figure 6-31 eNodeB Sends the RRC Connection Reconfiguration Message to Indicate Adding SCell.
Figure 6-32 Handover Required Message
Figure 6-33 Handover Request Message
Figure 6-34 Handover Command Message
Figure 6-35 X2 handover Procedure
Figure 6-36 RRC Connection Reconfiguration Message for Deleting the Source SCell and Adding the New SCell
Figure 6-37 RRC Connection Reconfiguration Message Carried MobilityControlInfo IE
Figure 6-38 RRC Connection Reconfiguration Message for Adding SCell
Figure 6-39 The Second RRC Connection Reconfiguration Message Carries the Handover A5 Event Configuration
Figure 6-40 The Third RRC Connection Reconfiguration Message Carries the Adding SCell A4Event Configuration
Figure 6-41 UE Sends the Measurement Report Message for A5 Handover
Figure 6-42 RRC Connection Reconfiguration Message Carried Adding SCell A4 Event
Figure 6-43 The CA Supported Information is Shown in the UE CapabilityInformation message
Figure 6-44 eNodeB Add Two SCell in measObjectEUTRA IE in the RRC Connection Reconfiguration Message
Figure 6-45 Deleting SCell Measurement Event A2 Configuration is Carried in the Same RRC Connection Reconfiguration Message
Figure 6-46 Add Two SCells at the Same Time
Figure 6-47 The First SCell Information
Figure 6-48The Second SCell Information
Figure 6-49 Two SCells are Activated
Figure 6-50 The Data Transmitted on PDSCH after the First SCell is Activated
Figure 6-51 The Data Transmitted on PDSCH after the Second SCell is Activated
Figure 6-52 Downlink Peak Throughput after Two SCells Activation
Figure 6-53 Test Network for FDD+TDD Carrier Aggregation
Figure 6-54 UE Supports UL/DL CA in band3 and DL CA in band38
Figure 6-55 eNodeB Sends the RRC Connection Reconfiguration Message to Add TDD Cell2 as a SCell
Figure 6-56 The SCell is Activated by Received the Activation MAC CE
Figure 6-57 There Is Data Transmitted on the PCell and SCell with SCellIndex1
Figure 6-58 The Downlink Peak Throughput is 265Mbps for FDD+TDD Carriers Aggregated with Bandwidth 40MHz
Figure 6-59 Check the UE whether Supports UL CA
Figure 6-60 Adding SCell Successfully
Figure 6-61 The Uplink Peak Throughput is 149Mbps for Two Carriers Aggregated with Bandwidth 40MHz
Figure 6-62 RRC Connection Reconfiguration Message Carries the SCell’s Frequency Information
Figure 6-63 UE Measures the Cell with Higher Priority Frequency
Figure 6-65 eNodeB Adds Cell 183 as SCell for UE1
Figure 6-66 The Downlink Throughput of UE1 Is Normal
Figure 6-67 eNodeB Adds the Cell 184 as SCell for UE2
Figure 6-68 Test Network for Inter-eNodeB Carrier Aggregation
Figure 6-69 The Downlink Throughput after SCell activation
Figure 6-70 The eNodeB sends the Cell1 RRC Connection Reconfiguration message carried adding SCell A4 event measurement configuration to UE1
Figure 6-71 UE1 Sends the Measurement Report Message of A4
Figure 6-72 eNodeB sends the RRC Connection Reconfiguration messageto UE1 to add the cell2 (PCI222) as a SCell
Figure 6-73 The eNodeB sends the RRCConnectionReconfiguration message carried adding SCell A4 measurement event to UE2
Figure 6-74 UE2 Sends the MeasurementReport Message of A4 and eNodeB does not Send the RRC Connection Reconfiguration message to UE2

Figure 6-77 UE1’s SCell is added successfully
Figure 6-78 UE2 Accesses to Cell2 Successfully
Figure 6-79 The UE1’s SCell is deleted because of the number of UEs in cell2 reached to the “Threshold of CA UE Back Off”
Figure 6-80 The Combination Test Interface
Figure 6-81 The Test Result of Transmission Delay
Figure 6-82 UE Supports Three Carriers Aggregation between FDD and TDD
Figure 6-83 Add Band1 Cell as a SCell in the RRC Connection Reconfiguration Message
Figure 6-85 The Downlink Peak Throughput with bandwidth 60MHz in the Case of Two FDD Cell and One TDD Cell Aggregation
Figure 6-86 When UE Has Large Data Transferring, the SCell Based on Blind Addition Is Added Successfully
Figure 6-87 When UE Has Large Data Transferring, the SCell Based on Measurement Addition Is Added Successfully
Figure 6-88 eNodeB Adds Cell184 as SCell for UEs
Figure 6-89 SCC Is Activated Successfully
Figure 6-90 QCI5 Is Established Successfully
Figure 6-92 eNodeB Sends the RRC Connection Reconfiguration Message, Including the Handover Measurement Configuration with Event A5 Based on Service
Figure 6-93 eNodeB Sends the RRC Connection Reconfiguration Message to Indicate UE to Be Handover to Cell 184
Figure 6-94 eNodeB Sends the RRC Connection Reconfiguration Message to Add the Cell182 as SCell for UE after Handover Ended
TABLES
Table 1-1 Related Feature List

Table 1-2 Correlation with Other Feature
Table 3-1 CA Deployment Scenarios (F2 > F1)
Table 3-2 Related parameters for FDD+TDD carrier aggregation
Table 3-3 Scenarios of Downlink Inter-eNodeB Carrier Aggregation Supporting
Table 3-4 Number of RBs allocated to an SCC in the non-ideal backhaul scenario
Table 3-5 Minimum bandwidth for various delay
Table 3-6 Recommended Spacing between Centre Frequencies
Table 3-7 CSI Request field for PDCCH with uplink DCI format in UE specific search space
Table 3-8 Scenarios of uplink inter-eNodeB CA supporting
Table 4-1 FDD Theoretical peak rate in TM3
Table 4-2 Center Frequency Spacing of Intra-Band Contiguous CA with Different Bandwidths
Table 4-3 CA Configuration Parameters
Table 4-4 Active/De-active Parameters
Table 4-5 FDD + TDD CA Configuration Parameters
Table 4-6 Cloud CA Configuration Parameters
Table 4-7 Primary Carrier Frequency Parameters
Table 4-8 CA Fair scheduling parameters
Table 4-9 Flexible SCell Selection parameters
Table 4-10 User-Based Admission parameters
Table 4-11 CA UE Monitor parameters
Table 4-12 CA UE Handover with SCell parameters
Table 5-1 Related Counters
Table 6-1 Required Devices for the Carrier Aggregation Function
Table 6-2 DL Inter-Band Two Carries Aggregation Function Test Specification
Table 6-3 DL Non-Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Table 6-4 DL Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Table 6-5 CA SCell Adding and Deleting Function Test Specification
Table 6-6 CA SCell Modifying Function Test Specification
Table 6-7 SCell Activating and DeactivatingTest Specification
Table 6-9 Handover of CA Test
Table 6-10 CAPrimary Carrier Frequency Priority
Table 6-11 Carrier Aggregation(DL 3CC)
Table 6-12 CA bandwidth classes and corresponding nominal guard bands
Table 6-13 Test Devices for FDD+TDD Carrier Aggregation
Table 6-14 Carrier Aggregation(DL 2CC, FDD+TDD)
Table 6-15 Carrier Aggregation (UL CA)
Table 6-16 Flexible SCell Configuration of Multi-Carriers Function Test Specification
Table 6-17 SCC Selection Based on Cell Load
Table 6-18 Test Devices for Inter-eNodeB Carriers Aggregation
Table 6-19 Cloud Centralized CA with Ideal Backhaul
Table 6-20 RRC User Based CA Enable

Table 6-21 RRC User Based CA Back Off
Table 6-22 Cloud Centralized CA with Non-Ideal Backhaul Function Test Specification
Table 6-23 DL Three Carriers Aggregation between FDD and TDD Test Specification
Table 6-24 Monitoring Based SCell Addition Function Test Specification
Table 6-25 Service Based PCC Dynamic Selection
Table 6-26 Carrier Aggregation(DL 5CC, 1FDD+4TDD)
Table 10-1 (Table 5.6A.1-1: E-UTRA CA configurations and bandwidth combination sets defined for intra-band contiguous CA)
Table 10-2 (Table 5.6A.1-2: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (two bands))
Table 10-3 (Table 5.6A.1-2a: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (three bands)
Table 10-4 (Table 5.6A.1-3: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra-band CA (with two sub-blocks))
1 Introduction
This document provides the introduction, technical descriptions, parameter configuration, counters, alarms, and validation procedure of the LTE FDD carrier
aggregation feature.
The parameters, alarms and counters in this document are the same as those of the latest software version when this document is released. To obtain the MO,
parameters, alarms, and KPIs of the existing software version, please refer to the product manuals of the existing software version.
This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in this document respectively refer to "LTE FDD" and "LTE FDD-based eNodeB"
without further description.
1.1 Feature Attribute

OMMB EMS
Single-mode eNodeB V12.18.30 V12.18.30
V3.50.10
Multi-mode eNodeB V12.18.30 V12.18.30
V4.17.10
FDD single-mode V3.5.10 corresponds to GUL multi-mode V4.17.10, and LTE technology description and operation requirements in the corresponding versions are
the same.
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
√ √ - - - - - -
Note:
*-: Not involved
*√: involved
1.2 Related Feature List and License Control
Table 1-1 Related Feature List
No Feature List No. Feature List Name License Control

or not
1 ZLF34-00-013 Carrier Aggregation(Inter- Yes

Band, DL 2CC)
2 ZLF34-00-015 Carrier Aggregation(Intra- Yes

Band, DL 2CC)
3 ZLF34-00-016 Carrier Aggregation(UL CA) Yes
4 ZLF34-00-017 Carrier Aggregation(DL 3CC) Yes
5 ZLF34-00-027 Carrier Aggregation((DL 2CC, Yes

FDD+TDD)
6 ZLF34-00-034 Cloud CA (centralized) Yes
7 ZLF34-00-035 Load and Service Monitor No

Based Scell Dynamic
Configuration
8 ZLF34-00-036 Flexible SCell configuration of No

multi-carriers
9 ZLF34-00-049 Carrier Aggregation(DL 3CC, Yes

FDD+TDD)
10 ZLF34-00-051 Cloud CA (distributed) Yes
11 ZLF34-00-055 Carrier Aggregation(DL 4CC Yes

of FDD)
12 ZLF34-00-056 PCC dynamic selection No

based on service

FDD+TDD)
No Feature List No. Feature List Name License Control

or not
FDD+TDD)
1.3 Correlation with Other Feature
Table 1-2 Correlation with Other Feature
Feature Feature Name Required Mutually Impacted

ID
Feature Exclusive Feature
Feature
ZLF34-00- Carrier Aggregation None None

013 (Inter-Band, DL
2CC)
ZLF34-00- Carrier Aggregation None None

015 (Intra-Band,DL2CC)
ZLF34-00- Carrier Aggregation ZLF34-00-013 None
016 (UL CA) ZLF34-00-015
ZLF34-00- Carrier Aggregation ZLF34-00-013 None
017 (DL 3CC) ZLF34-00-015
ZLF34-00- Carrier Aggregation ZLF34-00-013 None None

027 (DL 2CC,
FDD+TDD)
ZLF34-00- Cloud CA ZLF34-00-013/ None None

ZLF34-00-015/
034 (centralized)
ZLF34-00-017/
ZLF34-00-027
ZLF34-00- Load and Service ZLF34-00-013/ None None

ZLF34-00-015/
035 Monitor Based Scell
Dynamic
Configuration
ZLF34-00- Flexible SCell ZLF34-00-013/ None None

ZLF34-00-
036 configuration of
015/ZLF34-00-
multi-carriers 017/
ZLF34-00-049
ZLF34-00- Carrier Aggregation ZLF34-00- None None

017/ZLF34-00-
049 (DL 3CC,
027
FDD+TDD)
ZLF34-00- Cloud CA ZLF34-00- None None

051 (distributed) 013/ZLF34-00-
015/ ZLF34-
00-017/
ZLF34-00-034
ZLF32-05-001
ZLF34-00- Carrier Aggregation ZLF34-00-013 None None

055 (DL 4CC of FDD) ZLF34-00-015
ZLF34-00-017
ZLF34-00- PCC dynamic ZLF31-07- None None

056 selection based on 034Service
service Triggered
Inter-frequency
HO
ZLF34-00-060 Carrier Aggregation ZLF34-00-013/
(DL 4CC, ZLF34-00-017/
ZLF34-00-027/
FDD+TDD)
ZLF34-00-049
ZLF34-00-062 Carrier Aggregation ZLF34-00-013/
(DL 5CC, ZLF34-00-017/
ZLF34-00-027/
FDD+TDD)
ZLF34-00-049/
ZLF34-00-060
Note: About the description and configuration of ZLF34-00-056PCC dynamic selection based on service see details in ZTE LTE FDD VoLTE Feature Guide.
1.3.1 ZLF34-00-016 Carrier Aggregation(UL CA)
Required Features:
ZLF34-00-013 Carrier Aggregation(Inter-Band, DL 2CC)
ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)
Reason: According to the protocol, UL CA is based on DL CA.
Exclusive Features:
None
Impacted Features:
None
1.3.2 ZLF34-00-017Carrier Aggregation(DL 3CC)
Required Features:
Reason: 3-carrier CA is based on 2-carrier CA (intra-band or inter-band CA depends on band combination)
Exclusive Features:
None
Impacted Features:
None
1.3.3 ZLF34-00-034 Cloud CA (centralized)
Required Features:
ZLF34-00-017 Carrier Aggregation(DL 3CC)
ZLF34-00-027 Carrier Aggregation(DL 2CC, FDD+TDD)
ZLF32-05-001 GPS Synchronization
Reason: Cloud CA supports basic functions of CA and requires phase synchronization.
Exclusive Features:
None
Impacted Features:
None
Required Features:
Reason: FDD+TDD CA is based on 2-carrier CA (inter-band).
Exclusive Features:
None
Impacted Features:
None
1.3.5 ZLF34-00-036Flexible SCell Configuration of Multi-Carriers
Required Features:
Reason: Flexible SCell configuration of multi-carriers is based on basic functions of CA. Exclusive Features:
None
Impacted Features:
None
Required Features:
Reason: This feature is based on 3-carrier CA (DL) and FDD+TDD CA (DL 2CC). Exclusive Features:
None
Impacted Features:
None
1.3.7 ZLF34-00-051Cloud CA (Distributed)
Required Features:
ZLF34-00-034 Cloud CA (centralized)
ZLF32-05-001 GPS Synchronization
Reason: Cloud CA (Distributed) is enhanced feature of CA, and it supports Cloud CA and basic functions of CA. At the same time, phase synchronization is required.
Exclusive Features:
None
Impacted Features:
None
Required Features:
Reason: Carrier Aggregation(DL 4CC, FDD+TDD) is based on the CA basic functions as listed above.
Exclusive Features:
None
Impacted Features:
None
Required Features:
Reason: Carrier Aggregation(DL 5CC, FDD+TDD) is based on the CA basic functions as listed above.
Exclusive Features:
None
Impacted Features:
None
2 Function Description
To provide a higher service rate, 3GPP requires that downlink data rate of 1Gbps should be achieved on the LTE-Advanced phase. Many network operators usually
have non-contiguous spectrum resources because of a shortage of radio spectrum resources. Every single frequency band has difficulty in meeting the bandwidth
requirements of LTE-Advanced.
As a result, 3GPP Release 10 (TR36.913) introduced the Carrier Aggregation (CA). By aggregating multiple or discontinuous carriers, larger bandwidth can be
achieved to meet the requirements of 3GPP.
Carrier aggregation technology is to combine multiple contiguous or non-contiguous component carriers to obtain greater transmission bandwidth and to gain a higher
peak rates and throughput, and user experience can be improved and more applications can be supported. This solution can solve the problem of non-contiguous
spectrum for operators.
CA can bring about the following benefits:
Make full use of resources. CA UEs can use idle RBs on two carriers at the same time to realize the maximum resource utilization.
Effectively use separate spectrum of operators
Bring better user experience. In the MIMO 2T2R environment, the downlink peak data rate of a CA UE can reach to 300 Mbps. In the multi-user scenario of a
commercial network, CA UEs can use idle resources after activating Secondary Cells (SCells), thus increasing the throughput of CA UEs when the network is not
at full load and bringing better experience to users.
To achieve the smooth evolution from LTE to LTE-A, reduce network construction cost for operators and maintain compatibility with LTE system, Release 10 defines
that each component carrier to be aggregated should be totally compatible with LTE terminal and each carrier bandwidth be LTE operating bandwidth, and each
component carrier includes synchronization, broadcast and other messages. Non-compatible carrier is introduced in Release 11.
The carriers to be aggregated can be contiguous or non-contiguous. And carriers can be in the same band or different bands. Therefore, the carrier aggregation can
be divided into the following categories:
Intra-band contiguous carrier aggregation
Intra-band non-contiguous carrier aggregation
Inter-band non-contiguous carrier aggregation
TDD+FDD carrier aggregation
Figure 2-1 Carrier aggregation scenarios
In LTE system, each cell corresponds to one downlink carrier and uplink carrier (for TDD system, each cell corresponds to the same carrier), and each UE accesses to
one cell. The concept of multiple carriers is introduced to carrier aggregation. Considering asymmetric characteristics of uplink and downlink, each cell of carrier
aggregation corresponds to one downlink and selectable UL/DL carrier. From the perspective of top layer, carrier aggregation can be regarded as cell aggregation,
and each UE can access to multiple cells simultaneously.
Primary serving cell (PCell) and Secondary Cell (SCell) are defined for carrier aggregation. Primary Component Carrier (PCC) includes downlink PCC and uplink PCC
and Secondary Component Carrier (SCC) includes one downlink SCC and optional uplink SCC. Each UE has only one PCell and SCell can be configured based on
UE aggregation capability and service requirements.
For carrier aggregation, this document focuses on the following key technologies:
Admission for carrier aggregation
Scheduling for carrier aggregation
SCC activation and deactivation for carrier aggregation
SCC addition and release for carrier aggregation
Load and Service Monitor Based Scell Dynamic Configuration
Handover for carrier aggregation
CA enhancement in network sharing
Specify PCell of UE according to frequency priority
Flexible SCell configuration of multi-carriers
service based PCC dynamic selection
For super cell scenario, Super CA, that is, CA of multiple Super Cell on different bands, is also supported. About the description and configuration of Super CA, see
details in ZTE LTE FDD Super Cell Feature Guide.
3 Technical Description
3.1 Technical Principle

Each carrier in a carrier aggregation acts as an independent cell, which has no difference for the R8/R9 UE. The CA UE selects and accesses a carrier according to
the signal strength and frequency priority of the carrier. The cell that the UE initially accesses is the PCell. This document uses downlink two carriers as an example to
describe the features.
The PCell and SCell are defined only for the UE-level. In light of cell, there is no difference between PCell and SCell;
After accessing the network and being configured with a SCell, a CA UE only establishes an RRC connection with the PCell. The C-RNTI of the SCell is the same
as that of the PCell.
After the CA UE accesses the network, the eNodeB determines whether to enable the CA function and configure the SCell according to the CA capability reported
by the UE.
During the CA UE accessing procedure, the SCell can be directly added based on neighbor relation EUtranRelation.shareCover configured as same coverage or
containing through the EMS or added through the A4 measurement report
The PCell of the CA UE can only be changed through the handover procedure, while the SCell can be changed through the A6measurement event.
The PCell of the CA UE is always activated, while the SCell can be deactivated.
3.2 Application Scenario

CA combinations can be configured between the cells according to the actual network deployment, including same coverage, containing, contained and neighboring. If
the neighbor relationship of CA cells is same coverage or containing, the CA-UE will be configured with the SCell after it initially accesses the network, handover or re-
establishment complete. Otherwise, A4 measurement should be configured for SCC addition. After receiving an A4 measurement report, the system adds SCCs in
accordance with the report.
The table below shows some of the potential deployment scenarios for CA. In Rel-10, for the uplink, the focus focuses on the support of intra-band carrier
aggregations (e.g. scenarios #1, as well as scenarios #2 and #3 when F1 and F2 are in the same band). Scenarios related to uplink inter-band CA are supported from
Rel-11. For the downlink, all scenarios should be supported in Rel-10.
Table 3-1 CA Deployment Scenarios (F2 > F1)
Description Example
1 F1 and F2 cells are co-located and overlaid,
providing nearly the same coverage. Both
layers provide sufficient coverage and
mobility can be supported on both layers.
Likely scenario is when F1 and F2 are of
the same band, e.g., 2 GHz, 800 MHz, etc.
It is expected that aggregation is possible
between overlaid F1 and F2 cells.
2 F1 and F2 cells are co-located and overlaid,
but F2 has smaller coverage due to larger
path loss. Only F1 provides sufficient
coverage and F2 is used to improve
throughput. Mobility is performed based on
F1 coverage. Likely scenario when F1 and
F2 are of different bands, e.g., F1 = {800
MHz, 2 GHz} and F2 = {3.5 GHz}, etc. It is
expected that aggregation is possible
between overlaid F1 and F2 cells.
3 F1 and F2 cells are co-located but F2

antennas are directed to the cell boundaries
of F1 so that cell edge throughput is
increased. F1 provides sufficient coverage
but F2 potentially has holes, e.g., due to
larger path loss. Mobility is based on F1
coverage. Likely scenario is when F1 and
F2 are of different bands, e.g., F1 = {800
MHz, 2 GHz} and F2 = {3.5 GHz}, etc. It is
expected that F1 and F2 cells of the same
eNodeB can be aggregated where
coverage overlaps.
4 F1 provides macro coverage and on F2

Remote Radio Heads (RRHs) are used
to improve throughput at hot spots.
Mobility is performed based on F1
coverage. Likely scenarios are both
when F1 and F2 are DL non-
contiguous carrier on the same band,
e.g., 1.7 GHz, etc. and F1 and F2 are
of different bands, e.g., F1 = {800 MHz,
2 GHz} and F2 = {3.5 GHz}, etc. It is
expected that F2 RRHs cells can be
aggregated with the underlying F1
macro cells.
5 Similar to scenario #2, but frequency
selective repeaters are deployed so
that coverage is extended for one of
the carrier frequencies. It is expected
that F1 and F2 cells of the same
eNodeB can be aggregated where
coverage overlaps.
3.3 Carrier Aggregation Networking
3.3.1 Intra/Inter-Board CA
This version supports intra-board and inter-board CA. The intra-board CA means that the two cells that implement CA are in the same baseband board. The inter-
board CA means that the two cells that implement CA are in different baseband boards (The two baseband boards can be both BPL1 or BPN boards, or one BPL1
board and one BPN board.BPL1, BPN, and BPQ support this function, and these baseband boards can be mixed inserted.
3.3.2 FDD+TDD Carrier Aggregation
The UE before R12 only supports intra-RAT CA like Intra-TDD CA and Intra-FDD CA, but the R12 UE can support TDD+FDD CA. In this version, eNodeB only
supports the configuration of FDD as PCell and TDD as SCell. The configuration of FDD as SCell and TDD as PCell is not supported. When adding Inter-RAT cell as
SCell, it should be confirmed whether UE capability supports. If UE capability supports, the Inter-RAT cell can be configured as SCell. Otherwise, the cell cannot be
configured as SCell.
FDD+TDD downlink CA (up to 1 FDD + 4TDD five-carrier aggregation) is supported, and FDD macro base station +TDD Massive MIMO for DL carrier aggregation is
also supported.For TDD carrier, only UL/DL Configuration (EUtranCellTDD.sfAssignment) is 1 or 2 can be supported. According to the protocol, the followings are
listed:
1. The maximum number of downlink HARQ process of TDD SCell is consistent with FDD;
2. The downlink ACK/NACK feedback sequence in subframe N of TDD SCell is reported by FDD ACK/NACK feedback sequence N+4;
3. The downlink DCI packets of TDD SCell is consistent with FDD DCI packet format;
For FDD+TDD carrier aggregation, the related parameters are listed below:
Table 3-2 Related parameters for FDD+TDD carrier aggregation
FDD+TDD CA switch Related parameters

Carrier Aggregation(DL GlobleSwitchInformation.fddTddCaSwch
2CC, FDD+TDD)
Carrier Aggregation(DL GlobleSwitchInformation.fddTdd3ccCaSwch
3CC, FDD+TDD)
4CC, FDD+TDD)
5CC, FDD+TDD)
If Carrier Aggregation(DL 5CC, FDD+TDD) is enabled, first enable Switch for CA between FDD and TDD, Switch for 3CC CA between FDD and TDD, Switch for 4CC
CA between FDD and TDD and Switch for 5CC CA between FDD and TDD. If Carrier Aggregation(DL 3CC, FDD+TDD) is enabled, first enable Switch for CA between
FDD and TDD and Switch for 3CC CA between FDD and TDD.
Note:
For CA (DL 5CC FDD +TDD), only 5CC (1F+4T) is supported;
For CA (DL 4CC FDD +TDD ), only 4CC (1F+3T) is supported;
For CA (DL 3CC FDD +TDD ), 3CC (1F+2T and 2F+1T) is supported.
There are no commercial terminals supporting 5CC and 4CC. For 3CC CA, QUALCOMM Terminals has supported.
3.3.3 Inter-eNodeB Carrier Aggregation
Inter-eNodeB carrier aggregation is applied in the scenarios shown below:
Table 3-3 Scenarios of Downlink Inter-eNodeB Carrier Aggregation Supporting
Inter-eNodeB Intra-RAT/Inter-RAT Max Number of

scenarios carriers
Ideal backhaul (the intra-RAT 3CC
delay of inter-BBU link inter-RAT 5CC (1F+4T)
is less than 0.2ms)
4CC (1F+3T)
3CC (1F+2T or 2F+1T),
2CC (1F+1T)
Non-ideal backhaul (the intra-RAT 3CC (only one
delay of inter-BBU link is coordinate link delay is
longer than 0.2ms but non-ideal backhaul)
shorter than 4ms) inter-RAT 2CC (1F+1T)
For ulca, only ideal backhaul is supported.
In the non-ideal backhaul scenario, the longest downlink inter-BBU link delay tolerance supported is 4ms (When the delay is longer than 4ms, SCCs are not
scheduled). When the delay is larger than Threshold of Transmission Delay between the eNBs (ENBFunctionFDD.crossEnbDelayThrsh), eNodeB will determine
whether to delete the SCC according to Switch of Del SCell Based on Transmission Delay Between the eNBs (GlobleSwitchInformation.relScellOnDelaySwch). SCCs
will not be added for initially accessed terminals, even if the delay reduces to a value less than 4 ms afterwards.
In the non-ideal backhaul scenario, to ensure the delivery of the air interface data on the SCC not affected by link delays, SCC advance-scheduling is required.
Advance -scheduling may cause the reduction of scheduled packets in the single-UE scenario (the scheduled packet formula: 1000*8/(8+3n), n indicates the link delay
value) and preempt the air interface resources of normal UE. Therefore, the number of RBs for advance -scheduling of SCC should be limited. In this version, in the
non-ideal backhaul scenario, the number of RBs allocated to an SCC is as follows:
Table 3-4 Number of RBs allocated to an SCC in the non-ideal backhaul scenario
Bandwidth (MHZ) the number of RBs allocated to an SCC
20 52
15 36
10 24
5 12
3 8
Two connection methods are supported. The two carriers of Inter-BBU can be FDD+FDD CA or TDD+FDD CA.
1. Inter-BBU interaction by direct optical fiber connection via FS5C/CR0
2. Inter-BBU interaction by public transmission equipment via FS5C/CR0
Transmission requirements:
Co-located inter-BBU is designed according to baseband pooling strategy, and inter-BBU delay is estimated to be 100us. If the inter-BBU delay can be
guaranteed to be less than 200us, the CA has no influence on service schemes for uplink CA or downlink CA. For inter-BBU non-ideal backhaul scenario, uplink
CA is not supported; only downlink CA is supported in non-ideal backhaul scenario.
Switch capability requirements:
According to switch capacity requirement, supposing single UE with FDD 2*2 MIMO mode, the data traffic is 150M, and the delay of full scheduling should be
within 0.2ms, then at least 0.75Gbps bandwidth is required. Taking other overheads into consideration, the maximum number of inter-BBU coordinated cell
should be:
(10*0.8)/0.75=10
For the configuration, 10Gbps optical module is recommended.
In the non-ideal backhaul scenario, one cell each from two sites forms CA, and the minimum bandwidth for various delays is listed below:
Table 3-5 Minimum bandwidth for various delay
Delay (ms) Minimum bandwidth (Mbps)

1 150
2 120
3 100
4 90
3.4 Carrier Aggregation Type

The uplink and downlink of each carrier in a carrier aggregation can be configured independently on condition that the number of uplink carriers does not exceed that
of downlink carriers. Each carrier to be aggregated is called as a Component Carrier (CC). The bandwidth of a component carrier can be 3, 5, 10, 15 or 20MHz. A
maximum of five carriers can be aggregated and the maximum aggregated bandwidth is 100MHz. Three types of spectrum allocation are defined in a 3GPP
specification to meet the requirements of different operators.
3.4.1 Intra-Band Contiguous CA
Intra-band CA means that two contiguous component carriers are in the same frequency band, and the central frequency interval between the two component carriers
is less than or equal to the channel spacing. The spacing between centre frequencies of contiguously aggregated CCs shall be a multiple of 300 kHz. This is in order
to be compatible with the 100 kHz frequency raster of Rel-8/9 and at the same time preserve orthogonality of the subcarriers with 15 KHz spacing.
For the recommended spacing between centre frequencies, refer to the following table. The central frequency interval need to configure the parameter: the
frequencies space configuration mode for multi carrier (GlobleSwitchInformation.freqSpaceCfgMode), and there are two options: Use partial guard band(performance
no impaired) or Use all guard band(performance impaired).
Table 3-6 Recommended Spacing between Centre Frequencies
BW1 BW2 Nominal Partial protection Full protection

channel bandwidth (no bandwidth
spacing performance (performance
loss) loss)
20 20 19.8 18.6 18
20 15 17.1 16.5 15.8
20 10 14.4 14.1 13.5
20 5 11.7 11.7 11.3
20 3 10.5 10.5 10.4
15 15 15 14.1 13.5
15 10 12 12 11.3
15 5 9.3 9.3 9
15 3 8.4 8.4 8.1
10 10 9.9 9.3 9
10 5 7.2 7.2 6.8
10 3 6 6 5.9
5 5 4.8 4.8 4.5
5 3 3.9 3.9 3.6
There are two deployment scenarios of intra-band contiguous CA:
F1 and F2 are overlaid, providing nearly the same coverage; both layers provide sufficient coverage and mobility can be supported on both layers, which is the case in
scenario #1;
Or F1 and F2 are co-located but F2 antennas are directed to the cell boundaries of F1 so that cell edge throughput is increased. F1 provides sufficient coverage but F2
potentially has holes, which is the case in scenario #3.
3.4.2 Intra-Band Non-Contiguous CA
Intra-band non-contiguous CA means that the centre frequencies of two component carriers are in the same band, but the spacing between centre frequencies of the
non-contiguous CCs is greater than the channel spacing. This type of CA can be implemented in scenarios #1, #2, and #3.
3.4.3 Inter-Band CA
Inter-band CA means that two component carriers are in different frequency bands.
3.4.4 Band Combination Supported by Protocols
This version supports the 2-carrier band and bandwidth combination defined by protocols 36.104 and 36.101 E50, and 3-carrier and above carrier aggregation support
the combinations supported by the UE.
3.5 Admission Control in CA Scenario

After the CA function is enabled, the user-based and PRB usage-based admission control can be affected. The user based admission control can be performed in
both PCell and SCell at the same time, and the number of primary and secondary UEs in each cell is considered. The PRB usage-based admission control is only
performed in PCell.
3.5.1 User-Based Admission Control
For a CA UE, its PCell and SCell are counted as a UE respectively, and then the corresponding admission control is performed. If the number of UEs in a cell exceeds
the threshold, the admission fails. To solve the problem that the number of UEs supported in the network decreases, the number of CA-UE admission can be limited
by the system.
When Switch of CA User Restrict AC.caUserSwch is enabled, modify Threshold offorbid Configured as SCell (AC.forbidSCellThrd) to prohibit adding aSCell for the
new coming UEs’SCell. When Switch of CA UE backoff (GlobleSwitchInformation.caBackOffSwch) is enabled, modify Threshold of CA UE Back Off
(AC.caBackOffThrd), when the cell UEs reaches the CA UE back off threshold, CA-UEs’ SCC is deleted. In this way, the relative balance between the system
capacity and the number of CA UEs can be achieved. If the number of UE in one cell reaches the Threshold of forbid Configured as SCell (AC.forbidSCellThrd), the
CA-capable UEs will not be added with a SCell. If the number of UEs keeps on rising to the Threshold of CA UE Back Off (AC.caBackOffThrd), the system will select a
CA UE to delete its SCell .
The selection policies of which CA-UEs are to delete SCells is listed below:
To avoid the problem that a SCell is deleted the moment it has just been added, the CA-UE with a SCell is put in the disable queue after 2 seconds since its SCell was
added. Then CA-UEs are selected to perform de-configuring secondary carrier in the following order:
1. The secondary carrier is in deactivated state;
2. The UE with more carriers (with the same conditions, the UE with more carriers is preferentially selected);
3. The UE supporting only downlink CA (with the same conditions, the UE supporting downlink CA only is preferentially selected);
4. The UE with lower frequency efficiency is preferentially selected.
3.5.2 PRB Usage-Based Admission Control
When the CA UE initially accesses or is handed over to a network, the DRB (Data Radio Bearer) usage based admission control is performed according to the
remaining PRB resources in the PCell because SCell has not been successfully configured. The admission control procedure of the CA UE is the same as that of
ordinary UEs.
3.6 Specify Pcell of UE According to Frequency Priority

This version provides UE primary carrier designation in accordance with cell frequency priority (CAPCellFeqPri.pcellFeqPri) during SCC addition after the access of
the UE. If the frequency priority of the cell that the UE accesses is low, it need to handover to the cell with a higher frequency priority before SCC addition. In this
case, the handover modes include blind handover and A5 measurement-based handover (the handover mode is configured through
EUtranCellMeasurement.caPcellMeasure on the EMS). If blind handover is configured, the UE initiates handover first after access, and adds an SCC after
successfully handover to a cell with a high-priority frequency point. If measurement-based handover is configured, the system sends the measurement event to the UE
after UE access. On the reception of the measurement report, the system initiates handover of the UE to a cell with a high-priority frequency point before adding an
SCC for it.
Note: for inter-eNodeB handover, only measurement based handover is supported. The cells with high frequency priority and the cell with low frequency priority should
be configured with CA Coordination Relation.
3.7 SCC Management in CA
3.7.1 SCC Selection
Up to 5CC SCC selection is supported. SCC selection methods include basic SCC selection, frequency priority-based SCC selection, and load-based SCC selection.
3.7.1.1 Basic SCC Selection
Basic SCC selection determines the candidate CA combinations for SCC addition in accordance with the maximum number of SCC (ENBFunctionFDD.maxScellNum)
configured on the eNodeB, the CA coordination relationship of the cell (EUtranRelation.coperType) that the UE accessed and the CA capabilities supported by the
UE. The system selects the CA combination with the maximum number of CCs to perform SCC addition. During the SCC addition procedure, the addition is performed
directly in the case of same coverage and containing. Otherwise, A4 measurement event is delivered for SCC addition. For details, refer to secondary configuration
and de-configuration in Section 3.7.2 SCC Configuration and De-Configuration.
3.7.1.2 Frequency Priority-Based SCC Selection
Frequency priority-based SCC selection (CarrierAggregatin.scellSelBaseFreqPriSwch) first uses the basic SCC selection method to determine the candidate CA
combinations for SCC addition (namely, in accordance with the maximum number of CCs configured on the eNodeB, the CA coordination relationship of the cell
accessed by the UE and the CA capabilities supported by the UE). Then, it sorts these combinations based on frequency priorities, and selects the combination with
the highest frequency priority for SCC addition.
Figure 3-1 Frequency Priority-Based SCC Selection Flow
3.7.1.3 Load-Based SCC Selection
Load-based SCC selection selects the CA combination with the lightest load among multiple candidate CA combinations to perform CA after basic SCC selection and
frequency priority-based SCC selection (when the frequency priority-based SCC selection switch CarrierAggregatin.scellSelBaseFreqPriSwch is turned on).
Figure 3-2 Load-Based SCC Selection flow
3.7.2 SCC Configuration and De-Configuration
SCC configuration: The SCC is added to the serving cell set through the RRC Connection Reconfiguration. In the scenario of same coverage or containing coverage
(EUtranRelation.shareCover), after the CA UE accesses the network, the eNodeB will add SCC to the CA capable UEs. In the neighboring scenario, the system
delivers A4 measurement event configuration to the UE firstly, once an SCC meets the measurement condition and the UE sends a measurement report, the system
will configure the SCC to the UE.
Figure 3-3 Initial SCC Configuration when neighbor relationship is same coverage or containing
Figure 3-4 Initial SCC Configuration when neighbor relationship is neighboring
SCC de-configuration: When the eNodeB configures an SCC for the CA UE, it also configures an A2 measurement for the SCC. If the RSRP of the SCC is lower than
the configured A2 threshold, the UE reports the A2 measurement report, and the eNodeB deletes the SCC and configures an A4 measurement event to the UE.
Figure 3-5 SCC De-configuration Procedure Based on Measurement
3.7.3 SCC Activation and Deactivation
To better manage CA UE battery consumption, LTE provides SCell activation and deactivation mechanism. The PCC is always activated, and the SCC is deactivated
by default.
When the SCell is activated, the UE performs the following operations on the SCell:
1. Sends SRS;
2. Reports CQI/PMI/RI;
3. Monitors the SCell and the PDCCH transmitted on the SCell.
When the SCell is deactivated, the UE does not perform the following operations on the SCC:
1. Sends SRS;
2. Reports CQI/PMI/RI;
3. Transmit uplink data (only uplink CA)
4. Monitors the SCell and the PDCCH transmitted on the SCell.
SCC activation: the system delivers an MAC CE in the PCC to activate the SCC if the following three conditions are met
1. The AMBR of the NGBR services or the GBR service cannot be satisfied.
2. The current PCC cannot satisfy the UE service requirements and cause service congestion.
Service congestion conditions:
a) T h e a m o u n t o f t h e b u f f e r e d s e r v i c e d a t a i s l a r g e r t h a n t h e l e n g t h t h r e s h o l d o f t h e CA t e r m i n a l S C C a c t i v a t e d d a t a b u f f e r
(CarrierAggregatin.scellActBufLenThd). This threshold can be configured on the EMS, and its default value is 20 KB.
b) The time of service data buffering is longer than the delay threshold of the CA terminal SCC activated data buffer
(CarrierAggregatin.scellActBufDelayThd). This threshold can be configured on the EMS, and its default value is 15ms.
If the service meets the above two conditions at the same time, it is deemed to be congested.
Service non-congestion condition
If the amount of buffered service data is smaller than buffer limited, the service is deemed to be not congested. This threshold is not configurable.
3. The PCC PRB usage is higher than the configured PCC activation threshold (CarrierAggregatin.pcellPRBRatioActThrDl), and the SCC PRB usage is lower than
the configured SCC activation threshold (CarrierAggregatin.scellPRBRatioActThrDl) (PRB usage of network sharing level),.
SCC can be deactivated if any of the following conditions is met:
1. The PCC PRB usage is lower than the configured PCC deactivation threshold (CarrierAggregatin.pcellPRBRatioDeActThrDl), and the SCC PRB usage is lower
than the configured SCC deactivation threshold (CarrierAggregatin.scellPRBRatioDeActThrDl). The eNodeB delivers an MAC CE in the PCC to deactivate the
SCC.
2. The MCS of the current SCC is lower than a threshold (CarrierAggregatin.mcs4SCellDeActiveDl), The SCC delivers an MAC CE through the PCC to
deactivate,including itself.
3. The amount of UE’s cached scheduled data is less than the threshold (CarrierAggregatin.caSchdSizeDeActThrDl) and the UE is in service non-congestion
condition, the eNodeB delivers an MAC CE in the PCC to deactivate the SCC.
4. If the SCC deactivation timer (CarrierAggregatin.deactCATimer) configured is not Infinity, and the CA-UE has not received any data or the PDCCH message at
the expiry of the deactivation timer, the CA-UE automatically deactivates the SCC. The deactivation timer starts when SCC is activated. Whenever there is new
data transmission or retransmission in the uplink or downlink, the SCC deactivation timer is reset.
3.8 Scheduling of CA
As defined in protocols, the carrier aggregation of the CA UE is transparent to the PDCP and RLC layers. There is one independent hybrid-ARQ on eachcarrier entity
in MAC layer, providing resource mapping, HARQ and channel coding to PHY layer. Therefore, the MAC knows the scheduling activities of each carrier so that the
scheduling becomes more flexible.
For GBR bearers, if the GBR of a bearer is larger than GBR split threshold, when SCC is activated, the GBR service will be scheduled both on PCC and SCC to
guarantee QOS.
For NGBR bearers, to achieve relative fairness between CA UEs and non-CA UEs, performs differentiated scheduling through the following two policies:
Fair scheduling (GlobleSwitchInformation.fairSchdSwch): the system calculates the scheduling priority using the total historical traffic of all CCs. Under the same
channel conditions, the non-CA UE has only one carrier, nevertheless it has a relative high PF priority. Therefore, the fairness between the non-CA UEs and CA
UEs in terms of traffic and physical resource is achieved.
Differentiated scheduling: the system calculates the scheduling priority using the historical traffic per CC. Under the same channel conditions, the non-CA UE and
CA UE achieve relative fairness per CC. However, the CA UE performs scheduling on two CCs by occupying double resources. Therefore, the CA UE’s traffic is
far more than the non-CA UE’s traffic.
The scheduling strategies above can be controlled by configuring fair scheduling scaling factor:
CA fair scheduling scaling factor ENBFunctionFDD.fairSchdFactor can be configured on EMS to select the scheduling strategy of non-CA UE and CA UE. The larger
the value is, the more opportunity for non-CA UE scheduling is, and the traffic of non-CA UE and CAUE tend to be even. The value “1” means fair scheduling, and
value “0” means differentiated scheduling.
3.9 Downlink Multi-Carrier Aggregation

The multiple carrier in this chapter refer the carriers of more than two carriers
The following CAs are supported:
Downlink 5CC CA (same mode)
5CC F+T (F is PCC)
SCC addition/deletion/ modification is supported.
3.9.1 SCell Addition/Release/Modification
The SCell addition/release/modification procedures of multi-carrier CA SCell are similar to those of 2CC CA. When the neighbors have same coverage, the UE can
add two SCells at the same time; for the measurement report based SCC, only one SCell can be added.
3.9.2 PUCCH Configuration
PUCCH format is Format3 (PhyChannel.pucch3RB), it also uses Format3 instead of Format 1b with channel selection when multi-carrier is downgraded to 2CCs.
3.9.3 Activation/Deactivation
The parameter configuration and process of three-carrier activation and deactivation procedures are similar to those of two-carrier CA. But there are some differences:
For activation processing, even if multi-carrier SCells meet the activation conditions, only one SCell can be activated each time. The SCell with light load (low PRB
usage) is selected.
After the activation, judge whether the number of activated carriers reaches the maximum configurable carrier number. If not, continue the activation judgment
and select the remaining carrier to be activated.
For deactivation processing, even if multi-carrier SCells meet the deactivation conditions, only one SCell can be deactivated each time. The SCell with high load
(high PRB usage) is selected.
3.9.4 CQI Feedback
Periodical CQI Feedback is same with that of 2CCCA.
According to DCI0 CSI-Req field and the set of aperiodic Trigger defined in 3GPP, for 3CC CA, the CQI of only one SCell will be reported in one trigger, the
configuration options of trigger and CSI-Req field is as follow:
DCI0 CSI-Req=’00: ’ No aperiodic CSI report is triggered;
DCI0 CSI-Req=‘01’: Aperiodic CSI report is triggered for PCC(ServCellIndex=0);
DCI0 CSI-Req=‘10’: Aperiodic CSI report is triggered for SCC1 (ServCellIndex=1);
DCI0 CSI-Req=‘11’: Aperiodic CSI report is triggered for SCC 2(ServCellIndex=2) ;
Table 3-7 CSI Request field for PDCCH with uplink DCI format in UE specific search space
Value of CSI request field Description
’00’ No aperiodic CSI report is triggered

‘01’ Aperiodic CSI report is triggered for serving cell
‘10’ Aperiodic CSI report is triggered for a 1st set of

serving cells configured by higher layers
‘11’ Aperiodic CSI report is triggered for a 2nd set of

serving cells configured by higher layers
3.10 Uplink CA
3.10.1 Uplink Congestion Judgment
The UE with ongoing NGBR service determines whether there is uplink congestion based on BSR scheduling.
Starting from the first BSR who exceeds the buffer size threshold of activating the secondary carrier for ULCA UE ThrBufferSizeH
CarrierAggregatin.scellActBuSizeThdUL. When UL BSR Delay is bigger than SCell Active Data buffer delay thr eshold for ULCA UE
CarrierAggregatin.scellActBufDelayThdUL, it is considered congestion, and as a condition of SCell Active. Otherwise, the uplink is regarded as non-congested.
3.10.2 Activation Strategy
If UE has NGBR service ongoing, the activation conditions are judged as soon as receiving the uplink service congested label. If the UE only has GBR service, the
activation conditions judgment starts every 2s from the moment when UE delivers BSR.
Activate the secondary carrier when all the following conditions are satisfied:
1. The SingleRBSinr on primary carrier calculated exceeds the uplink activation secondary carrier SNR threshold ThrUeSinrH
(CarrierAggregatin.caSccActSinrThrUl);
2. PCell’s PRB utilization exceeds the PCell’s UL total RB utilization activation threshold (CarrierAggregatin.pcellPRBRatioActThrUl), and SCell’s PRB utilization is
lower than the SCell’s uplink’s UL total RB utilization threshold (CarrierAggregatin.scellPRBRatioActThrUl);
3. UE’s GBR service has to satisfy the condition a) or NGBR service satisfies the condition b) as following:
a) GBR service activation condition: QCI2 is configured or the configured GBR exceeds the uplink SCell activation GBR service threshold
(CarrierAggregatin.caSccActGbrThrUl);
b) NGBR service activation condition: Uplink services congest and AMBR is not satisfied.
3.10.3 Explicit deactivation strategy
UE performs the activation conditions judgment at every 2s deactivation period; when one of the following conditions is satisfied, deactivate the secondary carrier.
1. UE’s SingleRBSinr is lower than uplink deactivated secondary carrier SNR threshold (CarrierAggregatin.caSccDeactSinrThrUl);
2. Secondary carrier equivalent MCS is lower than uplink CA secondary carrier deactivation MCS threshold CarrierAggregatin.sccMcsEDeactThr.
3. PCell’s RB utilization is lower than PCell’s total RB utilization deactivation threshold (CarrierAggregatin.pcellPRBRatioDeActThrUl) and the SCell’s RB utilization is
lower than SCell uplink’s total RB utilization deactivation threshold (CarrierAggregatin.scellPRBRatioDeActThrUl);
4. If UE has GBR and NGBR services ongoing, the following deactivation conditions have to be satisfied simultaneously; if UE only has GBR or NGBR service
ongoing, only the correspondent deactivation conditions has to be satisfied:
a) GBR deactivation condition: UE has no video service ongoing and GBR is not larger than the uplink SCell activation GBR service threshold
(CarrierAggregatin.caSccActGbrThrUl);
b) NGBR service deactivation condition:
In the latest deactivation period, the number of uplink services congestion times is less than the threshold or UL service non-congested possibility is
larger than ThrP. Meanwhile, the summation of the scheduled data amount of NGBR services and user plane cached data amount is lower than ULCA
data amount deactivation threshold CarrierAggregatin.caSchdSizeDeActThrUL.
3.10.4 Implicit deactivation strategy
If there is no scheduling within the SCell deactivation timer, the timer is considered to be expired, deactivate the SCell.
3.10.5 Uplink Inter-eNodeB CA
Table 3-8 Scenarios of uplink inter-eNodeB CA supporting
Inter-eNodeB scenarios Intra-RAT/Inter-RAT Max Number of

carriers
Ideal backhaul (the delay Intra-RAT 2CC
of inter-BBU link is less
than 0.2ms)
For the inter-BBU connection method, refer to Chapter 3.3.3.
In ideal backhaul scenario, inter-eNodeB uplink super CA is supported.
3.10.6 Function Constraints
Uplink 2CC aggregation is supported.
Type 1 extended PHR and extended BSR are supported.
Inter-eNodeB CA with ideal backhaul is supported;
FDD+TDD uplink CA is not supported.
The multi-TA function is not supported.
Simultaneous transmission of PUCCH and PUSCH is not supported.
3.11 Handover of CA
In LTE-A, LTE handovers are processed in the same way as that in R9 and R8. The CA-supporting eNB releases the source-side SCC first, and then adds the target-
side SCC after handover to enable the UE CA. Apart from that, CA can also be maintained during intra-LTE handovers (GlobleSwitchInformation.caScellHOSwch
needs to be turned on). That is, the SCCcan be selected for the UE by the target eNB, and the new SCell is configured for the UE via the handover command so that
the UE enters CA state. The source eNodeB selects a PCell according to the measurement result and sends a handover request to the corresponding target eNodeB.
The target eNodeB selects and adds a SCell during or after the handover.CA Enhancement in Network Sharing Scenario
In the network sharing scenario, the limitation of each PLMN should be considered for the PCell and SCell of the CA UE. During MAC scheduling, the resource
scheduled by the PCell and SCell should not exceed the PRB resource of the local PLMN. The admission in PCell and the addition of SCell are based on the number
of RRC Users capacity or the PRB resource proportion of its own PLMN.
3.12 Carrier Aggregation in Network Sharing

In the network sharing scenario, the restrictions on each PLMN need to be considered for the CA UE primary and secondary carriers. The resources scheduled by the
primary and the secondary carriers do not exceed the PRB resources of the PLMN during MAC scheduling. For primary cell admission and the secondary carrier
addition, the number of RAN sharing users and PRB ratio should be considered.

Because CA UE occupies the resources of multiple carriers at the same time, some occupied carrier resources are actually not used when there is less traffic (low
PRB usage). When the system’s RRC User capacity is full, other UEs cannot access due to admission failure, resulting in resource waste to some extent. To solve the
problem, monitoring based SCell addition is introduced. For CA UE, if the switch (GlobleSwitchInformation.caMonitorSwch) is turned on, whether to add a SCell or not
depend on the service load. Only when the service load needs the SCell to share can a SCell to be added. In addition, for SCell release caused by RRC User based
CA backoff, monitoring is not performed after release complete.

With service deployment's diversity, operators impose layer requirement on different services. Especially for VoLTE service, operators expect VoLTE service to reside
on specified carrier. In CA scenario, considering that the QCI=1 VoLTE service only bears on the primary carrier; hence when CA-UE initiates voice services, the
VoLTE service based primary carrier handover is able to be initiated according to the VoLTE services' frequency priority (that is configured by operators). If the current
PCell is not of the highest priority frequency for VoLTE service, the PCell will initiate handover for the UE as to reside the VoLTE service on the high priority frequency.
This feature depends on the inter-frequency handover. For details, please refer to ZTE LTE FDD VOLTE Feature Guide.
Note that since CA does not support A4 based primary carrier handover, the measurement event A5 should be configured in CA scenario for CA-UEs to perform inter-
frequency measurement and primary carrier handover. If a CA-UE has multiple bearers, the measurement tasks should be delivered according to the frequency
priorities in terms of the highest priority service.
4 Engineering Guide
4.1 Requirements
In this version, the eNodeB supports DL 2CC CA,DL 3CC CA, DL 4CC CA, DL 5CC (only supporting test), ULDL 2CC CA, DL F+T 2CC CA, DL F+T 3CC CA, DL F+T
4CC CA, DL F+T 5CC CA and inter-eNodeB CA.
4.1.1 Hardware Requirements
If eNodeB enables CA function, the hardware restrictions of eNodeB is shown below :
Baseband part: all support CA except BPL0.
RF part: No special requirement for RRU.
Baseband data switch board: only FS5C/CR0, FS5D/CR1 is used for inter-baseband board data switch( FS5C/CR0 is taken as an example to illustrate the
configuration below).
Note:
1. If eNodeB enables inter-board/inter-eNodeB CA function, theCR0 board must be configured, and the function mode of CR0 should be configured to “CloudRadio”.
2. eNodeBs needs GPS to keep clock synchronization.
4.1.2 EPC Requirements
The UE’s UL/DL AMBR configured in EPC side must be larger than theoretical peak rate.
Table 4-1 FDD Theoretical peak rate in TM3
FDD 1CC 2CC 3CC 4CC 5CC

theoretical
peak rate
TM3 150Mbps 300Mbps 450Mbps 600Mbps 750Mbps
The table provides the TM3 FDD theoretical peak rate in the condition of 20M, 2*2, 2*4 and 64QAM.
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
According to the protocol, whether each carrier frequency band supportsintra-band contiguous CA, intra-band non-contiguous CA and inter-band CA is defined in
3GPP specification. And it also defines the bandwidth combination in each carrier frequency bands. For intra-band CA, the center frequencies of PCell and SCell have
also been defined.
In this version, the center frequencies of PCell and SCell must be different. After UE access or handover, the PCell is fixed and the corresponding SCell must satisfy
the conditions below:
1. UE supports CA function between this cell and PCell;
2. This cell and PCell are mutually configured as neighbor cells;
3. This cell and PCell are mutually configured as CA coordination cells.
The condition 1 is related with frequency band, center frequency and bandwidth of PCell and SCell, which need to be judged according to 3GPP specification and UE
capability. Section 5.6 in 3GPP 36.101 E21 defines the channel bandwidth for CA.
Tips:
Intra-band contiguous CA: Frequency bands of PCell and SCell are same, and the spacing between center frequencies of contiguously aggregated CCs is configured;
Intra-band non-contiguous CA: Frequency bands of PCell and SCell are the same, and the spacing between center frequencies of non-contiguously aggregated CCs
is larger than the maximum spacing listed.
Inter-band CA: Frequency bands of PCell and SCell are different.
The details of Intra-band contiguous CA, Intra-band non-contiguous CAand Inter-band CA thatare defined in 36.101 E21 are listed in the attachment.
Before CA function is turned on, it must be confirmed the CA is in which frequency bands and the bandwidth information. The corresponding carrier center frequency
and bandwidths should be configured correctly. The table below shows the spacing between center frequencies of contiguous CCs with different bandwidths in 3GPP
(For intra-band non-contiguous CA, configure the center frequency spacing larger than the maximum spacing of bandwidth combination in the table.); For example,
two 20MHz CCs aggregation, the minimum spacing of two center frequencies is 18MHz, and the maximum spacing is 19.8MHz, and it also can be configured as the
value of any multiple of 300KHz between 18.3MHz and 19.8MHz (Such as 18.6MHz=62*300KHz).
Table 4-2 Center Frequency Spacing of Intra-Band Contiguous CA with Different Bandwidths
Bandwidth 5M 10M 15M 20M

4.5MHz 9MHz
5M 6.9-7.2MHz 11.4-11.7MHz
Or 4.8MHz Or 9.3MHz
9MHz 13.5MHz
10M 11.4-12MHz
Or 9.3-9.9MHz Or 13.8-14.4MHz
13.5MHz
15M 15.9-17.1MHz
Or 13.8-15MHz
18MHz
20M
Or 18.3-19.8MHz
If any item of frequency band, bandwidth and center frequency does not meet the 3GPP specification requirements for CA, the CA configuration information will not
be normal in UE access procedure.
Note:
If the two cells of intra-band contiguous CA are based on a RRU, according to the center frequency interval of two cells in table 4-2, configure the Frequency Space
Mode. Select Modify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration > Global Switch, double-click the record, In the Global Switch window,
Modify the Frequency Space Mode as shown below.Otherwise, the EMS constraint check cannot be passed.
Figure 4-1 Frequency Space Mode
4.1.4 UE Requirement
For CA function belongs to LTE-A, the UE should support CA function defined by 3GPP R10 specification. It can be checked by UE Capability Information message.
The UE should be compliant with specification R10( AccessStratumRelease is Rel10) and UE category should be greater than or equal to 4. For UE capacity, please
refer to Section 6.1.3. UECapabilityInformation.
Only if UE capability and specification both support CA, that is, the UE supports the CA frequency band combinations configured in OMC, the neighbor cell can be
chosen to be a SCell. eNodeB notifies the UE to add SCell by RRC Connection Reconfiguration message.
Figure 4-2 SCellAddition
If data cards are adopted for testing, high performance laptop should be configured (except primary frequency, read/write rate of the hard disk should be
considered and solid hard disk is suggested).
4.1.5 Transmission Bandwidth Requirements
The S1 transmission bandwidth must meet the throughput requirements for eNodeB multiple cells.
4.1.6 FTP Server Requirements
For FTP server, Linux operating system is recommended. Network card can satisfy the demands of theoretical peak rate.
4.2 Related parameters
4.2.1 CA Configuration Parameters
Table 4-3 CA Configuration Parameters
Parameter P a ra m e t e r
SN Parameter name Range value Unit Default value
panel name explanation
The
The RB parameter
Number of indicates the
1 PhyChannel.pucch3RB [0,98] N/A 0
PUCCH RB number
Format 3 of PUCCH
format 3
The
parameter
Uplink-
indicates
Downlink
2 EUtranCellTDD.sfAssignment uplink- [0,6] N/A 2
Subframe
downlink
Configuration
subframe
allocation
This
The parameter 0:Not use guard band,
Frequency indicates the 1:Use partial guard band 1:Use partial
Space frequency (performance no impaired), guard band
3 GlobleSwitchInformation.freqSpaceCfgMode N/A
Configuration space 2:Use all guard band(performance (performance
Mode for configuration impaired), no impaired)
Multi Carrier mode for 3:Use in-band frequencies
multi carrier.
The
parameter
indicates the
location
Intra-LTE relation
0:Neighboring,1:Same
4 EUtranRelation.shareCover Neighbor between N/A 0:Neighboring
Coverage,2:Containing,3:Contained
Relation server cell
and
EUTRAN
neighboring
cell
This
Max SCell parameter is
5 ENBFunctionFDD.maxScellNum [1,4] N/A 1
Num for CA Max SCell
Num for CA
This
parameter is
used to
configure
the CoMP
and CA 0:Not Support,1:Only UL Comp
Cooperative types, uses Support,2:Only DL Comp
6 EUtranRelation.coperType Relationship the bitmap Support,3:UL&DL Comp N/A 0:Not Support
Type way, from Support,8:Only DL CA
low to high Support,12:UL&DL CA Support
followed by
UL CoMP,
DL CoMP,
UL CA, DL
CA.
4.2.2 Active/De-active Parameters
Table 4-4 Active/De-active Parameters
Parameter
Parameter Default
SN Parameter name p a n e l Range value Unit
explanation value
name
The Downlink
The
Total PRB Ratio
Downlink
Threshold of
Total PRB
PCell for
Ratio
1 CarrierAggregatin.pcellPRBRatioActThrDl Activating SCell [0,100] N/A 60
Threshold
is one reason of
of PCell
SCell active, it is
(Active
valid when CA
SCell)
is configured
The Downlink
T h e
Total PRB Ratio
Downlink
Threshold of
Total PRB
SCell for Active
R a t i o
2 CarrierAggregatin.scellPRBRatioActThrDl SCell is one [0,100] N/A 100
Threshold
reason of SCell
of SCell
active, it is valid
(Active
when CA is
SCell)
configured.
The Downlink
T h e
PRB Ratio
Downlink
Threshold of
Total PRB
P C e l l f o r
R a t i o
3 CarrierAggregatin.pcellPRBRatioDeActThrDl DeActive SCell [0,100] N/A 20
Threshold
is one reason of
of PCell
scell deactive, it
(DeActiv e
is valid when
SCell)
CA is configured
The Downlink
The Total PRB Ratio
Downlink Threshold of
Total PRB S C e l l f o r
CarrierAggregatin.scellPRBRatioDeActThrDl Ratio DeActive SCell
4 [0,100] N/A 20
Threshold is one reason of
of SCell scell deactive, it
(DeActive is valid when
SCell) C A i s
configured.
This parameter
is a timer used
SCC
to deactivate 2[0],4[1],8[2],16[3],32[4],64 infinity
5 CarrierAggregatin.deactCATimer Deactivate N/A
SCC through [5],128[6],infinity[7] [7]
Timer (rf)
M A C -
MainConfig IE.
Buffer Length
threshold for CA
SCell UE, when RLC
Active Data Length is
Data buffer bigger than this
6 CarrierAggregatin.scellActBufLenThd [0,100] kbyte 5
Length threshold, it is
Threshold considered
for CA UE Congestion, and
as a condition of
SCell Active.
SCell Active
Data buffer
SCell delay threshold
Active for CA UE,
Data when RLC Data
Buffer Delay is bigger
7 CarrierAggregatin.scellActBufDelayThd [0,100] ms 5
Delay t h a n t h i s
Threshold threshold, it is
for CA UE considered
(ms) Congestion, and
as a condition of
SCell Active.
The Uplink Total
PRB Ratio
Threshold of
PCell for Active
The Uplink SCell is one
Total PRB reason of scell
Ratio active, it is valid
8 CarrierAggregatin.pcellPRBRatioActThrUl Threshold when CA is [0,100] unit % N/A 0
of Pcell configured. The
(Active smaller the
SCell) value, the
easier it is to
activate the
secondary
carrier.
The Uplink Total
PRB Ratio
Threshold of
SCell for Active
The Uplink SCell is one
Total PRB reason of scell
Ratio active, it is valid
9 CarrierAggregatin.scellPRBRatioActThrUl Threshold when CA is [0,100] unit % N/A 100
of SCell configured. The
(Active bigger the
SCell) value, the
easier it is to
activate the
secondary
carrier.
The Uplink PRB
Ratio Threshold
of PCell for
DeActive SCell
The Uplink is one reason of
Total PRB scell deactive, it
Ratio is valid when
10 CarrierAggregatin.pcellPRBRatioDeActThrUl Threshold CA is [0,100] unit % N/A 0
of PCell configured. The
(DeActive smaller the
SCell) value, the more
difficult it is to
deactivate the
secondary
carrier.
The Uplink Total
PRB Ratio
Threshold of
SCell for
DeActive SCell
The Uplink
is one reason of
Total PRB
scell deactive, it
Ratio
is valid when
11 CarrierAggregatin.scellPRBRatioDeActThrUl Threshold [0,100] unit % N/A 0
CA is
of SCell
configured. The
(DeActive
smaller the
SCell)
value, the
easier it is to
deactivate the
secondary
carrier.
if this thr is
smaller more
actual value,
SCC is
deactivated.
The smaller the
Threshhold value, the more
of Mcs difficult it is to
12 CarrierAggregatin.sccMcsEDeactThr deactive deactivate the [0,28] N/A 0
for Scc in secondary
UL CA carrier. The
default value is
“0”, which
indicates that
the parameter is
not used for
deactivating.
if this thr is
bigger than
actual value,
SCC is
Sinr of activated. The
13 CarrierAggregatin.caSccActSinrThrUl Active scell smaller the [0..40],step=0.5 N/A 22.5
in UL CA value, the
easier it is to
activate the
secondary
carrier.
if this thr is
smaller than
actual
value ,SCC is
Sinr of
Deactivated.
Deactive
14 CarrierAggregatin.caSccDeactSinrThrUl The smaller the [0..40],step=0.5 N/A 19
scell in UL
value, the more
CA
difficult it is to
deactivate the
secondary
carrier.
buffer Length
threshold for UL
CA UE, when
UL BSR is
SCell bigger than this
Active threshold, it is
Data considered
Buffer Congestion, and
15 CarrierAggregatin.scellActBuSizeThdUL [0..20],step=0.1 Kbyte 1
Length as a condition of
Threshold SCell Active.
for UL CA The smaller the
UE value, the
easier it is to
activate the
secondary
carrier.
SCell Active
Data buffer
delay threshold
for ULCA UE,
when UL BSR
SCell Delay is bigger
Active than this
Data threshold, it is
Buffer considered
16 CarrierAggregatin.scellActBufDelayThdUL [5,200] ms 20
Delay Congestion, and
Threshold as a condition of
for UL CA SCell Active.
UE The smaller the
value, the
easier it is to
activate the
secondary
carrier.
ULCA Schedule
data size
ULCA Threshold for
Schedule deactiving
Data Size SCell. The
17 CarrierAggregatin.caSchdSizeDeActThrUL Threshold smaller the [0,200] Kbyte 70
for value, the more
Deactive difficult it is to
SCell deactivate the
secondary
carrier.
If this threshold
is smaller than
actual GBR
Gbr configured ,SCC
Threshold is activated. The
18 CarrierAggregatin.caSccActGbrThrUl of Active smaller the [10,64000] kbytes 500
SCell in UL value, the
CA easier it is to
activate the
secondary
carrier.
The parameter
is MCS
threshold of
SCell DeActive
The MCS for CA, when
Threshold CA is
19 CarrierAggregatin.mcs4SCellDeActiveDl [0..28] N/A 1
Of SCell configured. if
DeActive MCS of SCell is
less or equal to
the threshold,
SCell will be
deActived.
The CA
schedule data
size Threshold
for DeActive
CA
SCell is one
Schedule
reason of Scell
Data Size
deactive, it is
20 CarrierAggregatin.caSchdSizeDeActThrDl Threshold 0:50,1:100,2:200,3:500,4:1000 Kbit 1:100
valid when CA
for
is configured
Deactive
and deactive
SCell
SCC when
schedule data is
less than the
threshold.
4.2.3 FDD + TDD CA Configuration Parameters
Table 4-5 FDD + TDD CA Configuration Parameters
Parameter
Parameter Range Default
SN Parameter name p a n e l Unit
explanation value value
name
This
Switch for 0:
parameter
CA Close
is switch for Close
1 GlobleSwitchInformation.fddTddCaSwch between N/A
CA between 1: [0]
FDD and
FDD and Open
TDD
TDD.
This
Switch for parameter 0:
3CC CA is switch for Close Close
2 GlobleSwitchInformation.fddTdd3ccCaSwch between 3CC CA N/A
1: [0]
FDD and between
TDD FDD and Open
TDD.
This
parameter
is the switch
for the
FDD+TDD
Switch for 4CC CA 0:
4CC CA function. It Close Close
3 GlobleSwitchInformation.fddTdd4ccCaSwch between needs to be N/A
1: [0]
FDD and set to
TDD "Open" Open
when it is
required to
perform
FDD+TDD
4CC CA.
This
parameter
is the switch
for the
FDD+TDD
Switch for 5CC CA 0:
5CC CA function. It Close Close
4 GlobleSwitchInformation.fddTdd5ccCaSwch between needs to be N/A
1: [0]
FDD and set to
TDD "Open" Open
when it is
required to
perform
FDD+TDD
5CC CA.
4.2.4 Cloud CA Configuration Parameters
Table 4-6 Cloud CA Configuration Parameters
Parameter Parameter Range Default

SN Parameter name Unit
panel name explanation value value
When
transmission
Threshold of
delay between
Transmission [0.2,10]
eNodeBs exceed
1 ENBFunctionFDD.crossEnbDelayThrsh Delay step ms 10
the value of this
between the 0.1
parameter, the
eNBs
function of CA is
disabled.
When switch is
Switch of Del open, the scell of
SCell Based UE is released if 0:
Transmission the transmission Close Close
2 GlobleSwitchInformation.relScellOnDelaySwch N/A
Delay delay between 1: [0]
Between the eNBs exceeds Open
eNBs the value of
rossEnbDelayThr.
4.2.5 Primary Carrier Frequency Priority Parameters
Table 4-7 Primary Carrier Frequency Parameters
Parameter Parameter Range Default

whether
handover
based
Switch for
measurement
Fixed
when Primary 0:No
Primary
1 carrier N/A No[0]
EUtranCellMeasurement.caPcellMeasure Carrier 1:Yes
frequency
Based
priority is
Measurement
lower than
inter-
frequency
Primary
carrier
frequency
priority switch
for CA. When
Primary
the switch is
carrier 0:Close
opened, if Close
2 GlobleSwitchInformation.pcellFeqPriSwch frequency N/A
frequency 1:Open [0]
priority switch
priority of
for CA
neighboring
cell is higher,
handover first
and then add
scell.
The
Primary parameter
carrier represents
3 CAPCellFeqPri.pcellFeqPri [0,255] N/A 0
frequency the frequency
priority priority of
Pcell for CA
4.2.6 CA Fair scheduling parameters
Table 4-8 CA Fair scheduling parameters
Parameter
Range Default
SN Parameter name panel Parameter explanation Unit
value value
name
If this switch is opened, CA UE use fair
scheduling, else use Differentiation
This
scheduling.
Parameter
N o t e : i f
is Used to 0:Close
GlobleSwitchInformation.fairSchdSwch Close
1 GlobleSwitchInformation.fairSchdSwch Open CA N/A
i s s e t t o o p e n , t h e 1:Open [0]
Fair
ENBFunctionFDD.fairSchdFactor is
Schedule
configured only to support 2CC;the
Enable
3CC cannot achieve the absolute
fairness.
This parameter is use to configure CA
user and non CA user's schedule ratio
in downlink, the smaller the value
means the CA user get more schedule
opportunity, when FairSchdFactor = 0
means difference schedule; when
The
FairSchdFactor = 1 means fair [0,1]
Factor of
2 ENBFunctionFDD.fairSchdFactor schedule. step N/A 0[0]
CA Fair
N o t e : i f 0.1
Schedule
GlobleSwitchInformation.fairSchdSwch
i s s e t t o o p e n , t h e
ENBFunctionFDD.fairSchdFactor is
configured only to support 2CC;the
3CC cannot achieve the absolute
fairness.
4.2.7 Flexible SCell Selection parameters
Table 4-9 Flexible SCell Selection parameters
Parameter P a r a m e t e r Range Default

1 CarrierAggregatin.caMeasIDSwch The Switch When the switch is 0:Close N/A Close

of MeasID opened,SCell 1:Open [0]
Sorting for adding
CA measurement in all
inter frequency will
be configured and
the measID of SCell
adding
measurement will
sort by certain rule.
When the PRB ratio
PRB Ratio of PCell is higher
Threshold of than this threshold,
[0,100]
2 CarrierAggregatin.prbThrd4GetLBInfo PCell for eNB should get N/A 20
unit %
getting Load RPB ratio
Information information of
neighbor cell by X2.
When
PRB Ratio SCellBasePRBSwch
Threshold of is opened, SCell [0,100]
3 CarrierAggregatin.scellPRBThrd N/A 100
SCell configuration need unit %
Configuration to consider this
threshold
This parameter 0: PRB
Load Type indicates Load ratio 1:PRB
4 CarrierAggregatin.loadTypeInd N/A
Indicator Typer condition for 1: PRB number
selecting scells. number
When the switch is
The Switch 0:
opened, the
of Scell Close
frequency priority Close
5 CarrierAggregatin.scellSelBaseFreqPriSwch Based on N/A
higher Scell will be 1: [0]
Frequency
selection and Open
Priority
configuration
When the switch is
The Switch opened, the Scell 0:
of Scell with smaller DL PRB Close Close
6 CarrierAggregatin.scellBaseDlPRBSwch N/A
based on DL ratio will be 1: [0]
PRB ratio selection and Open
configuration
4.2.8 User-Based Admission parameters
Table 4-10 User-Based Admission parameters
Parameter
name
If this switch is
open, CA UE
would be
removed SCell
when number of
UEs in the Cell is
reach
Switch of 0:Close
CaBackOffThrd;If Close
1 GlobleSwitchInformation.caBackOffSwch CA UE N/A
this switch is 1:Open [0]
Backoff
close, none of
the CA UE would
be removed
SCell when
number of UEs in
the Cell is reach
CaBackOffThrd.
This parameter is
the Threshold of
CA UE Back Off.
If number of
users in cell
(including the
Users connected
in cell and the
Threshold Users is
[0,100]
2 AC.caBackOffThrd of CA UE configured with N/A 90
unit %
Back Off this cell) and
max number of
users allowed in
cell reaches
threshold, CA
Users in this
SCell will be
chosen to back
off.
This parameter is
the Switch of CA
User Restrict.
When this switch
is opened, If the
Switch of number of users 0:Close Close
3 AC.caUserSwch CA User in cell reaches N/A
1:Open [0]
Restrict threshold of
forbid Configured
as SCell, the cell
cannot be
configured as
SCell.
4 AC.forbidSCellThrd Threshold This parameter is [0,100] N/A 80
of Forbid the Threshold of unit %
Configured forbid Configured
As SCell as SCell. If the
rate of number of
users in cell
(including the
Users connected
in cell and the
Users is
configured with
this cell) and
max number of
users allowed in
cell reaches
threshold, the
cell cannot be
configured as
SCell.
4.2.9 CA UE Monitor parameters
Table 4-11 CA UE Monitor parameters
Parameter
name
If this switch
is open, CA
UE would
be
monitored,
only if the
suitable UE
could be
Switch of 0:Close
configured Close
1 GlobleSwitchInformation.caMonitorSwch CA UE N/A
SCell; If this 1:Open [0]
Monitor
switch is
close, CA
UE would
not be
monitored
before
configuring
SCell.
4.2.10 CA UE Handover with SCell parameters
Table 4-12 CA UE Handover with SCell parameters
Parameter
Pa ram et er Range Default
name
When this switch
is opened, the
target cell choose
appropriate
SCells after
r e c e i v e d
HandoverRequest
message, and
S wi t c h o f
con figu re the se 0:Close
CA User Close
1 GlobleSwitchInformation.caScellHOSwch SCells to UE; N/A
Handover 1:Open [0]
When this switch
With SCell
is closed, all the
SCells of source
cell are deleted.
SCells of target
cell will be added
Until handover
p r o c e d u r e
completed.
4.3 Intra/Inter-Board CA (DL 2CC)
There are two CA configurations in current version:
Intra-Board CA: the two CA cells are established on the same Baseband Board.
Inter-Board/eNodeB CA: the two CA cells are established on the different Board/eNodeB respectively.
a) CR0 is required, and other configuration method is similar to that of intra-board CA;
b) If there is no CR0, the two boards must be inserted on Slot 3 and Slot8 in B8200 BBU or on Slot 3 and Slot 5 in B8300 BBU.
c) The two configuration methods above are exclusive.
4.3.1.1 Configuring Switch of CA
Open CA switch in EMS. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration>Global Switch, and set the related CA switches as shown below.
Figure 4-3 Configuring the Switch of CA
4.3.1.2 Configuring Frequency and Bandwidth of CA Cells
Configure the frequency and bandwidth of the two cells according to network planningas shown below.
Figure 4-4 Configuring Frequency and Bandwidth of CA Cells
4.3.1.3 Configuring CR0 Board(Optional, only for Inter-Board/eNodeB CACase)
For activating intra-eNodeB inter-Board CA functions, extra CR0 board must be configured. If there is no CR0 board, BPN (slot 3) +BPN (slot 8), BPL1 (slot 3) +BPL1
(slot 8) can also be configured for Inter-Board CA, but the mixed configuration of BPL1(slot 3) +BPN (slot 8) or BPN(slot 3) +BPL1 (slot 8) is not supported. If you mix
it, the CR0 board must be configured.
4.3.1.3.1 Configuring CR0 Board
Add CR0 board to realize SRIO switch of baseband data.
Notes:
CR0 board is usually configured in slot 3 or Slot 4.
Insert the CR0 board in the corresponding slot according to slot planning.
1. Select Managed Element> Device to add the CR0 board on the corresponding slot. Right-click in the blank of slot 3 or slot 4 according to the slot planning, then
choose Add board as shown below.
Figure 4-5 Adding the CR0 Board
2. In the dialog of Add Board, set the board type to FS and Board standard to ALL, Board function mode to LTE-FDD CloudRadio, Physical Board name to
CR0 as shown below.
Notes:
If inter-board CA function is enabled, the Board function mode of CR0 must be configured to LTE-FDD ClouldRadio.
Figure 4-6 Configure the CR0 Board
4.3.1.4 Configuring Neigbor Relation
Configure neighbor relation for the two CA cells.
1. In the Configuration Management window of the EMS, select Special Function of Standard -> Neighbor Cell Management as shown below.
Figure 4-7 Neighbor Cell Management
2. Configuring intra-eNodeB neighbor relation:
Fill in Source eNodeB and Neighbor eNodeB, and the Source eNodeB and Neighbor eNodeB choose the same value. Then ClickQuery button,and available
Neighbor Relation list is shown.
Figure 4-8 Configuring Neighbor Relation
3. In the Neighbor Cell Management window, select a record in the available neighbor Cells, and then click the add button. The selected cells will be configured to
Neighbor cell as shown below.
Figure 4-9 Configuring Neighbor Relation 2
4. In EMS configuration management window, selectModify -> wireless parameters - > LTE FDD ->Neighbor Relation Configuration ->E-UTRANNeighbor
Relation.Configure Intra-LTE neighbor relationtoSame Coverage or Neighboring as shown below.
Figure 4-10 Complete Neighbor Relation 3
5. The neighbor relation configuration records for the two cells are shown below.
Figure 4-11 Neighbor Relation Configuration Records
4.3.1.5 Configuring DL CA Coordination
Configure the cell coordination relation for the two cells by Cell Coordination Management tools. That means combinating the two cells to a group of CA cell.
1. In the Configuration Management window of the EMS, selectConfiruration Management -> Special Function of Standard -> Cell Coordination Management.
2. In the Cell Coordination Management view, select the eNodeB to perform CA and click Querybutton to check the cell configuration informationof the selected
eNodeB.
Figure 4-13 Query Cell Configuration Information of eNodeB
3. After query successful, the configured cell listof eNodeB is shown in the cell management column. Select one of the serving cell as PCell, and then click Group
button.
Figure 4-14 Configuring Cell Listof eNodeB
4. Neighbor Cell List dialog box is displayed. Then select which SCell to group with Pcell.
Figure 4-15 Coordination Configuration
5. SelectDL CA in the Neighbor Cell List dialog box and select the SCell according to network planning.
Figure 4-16 Selecting SCell
6. Then click OKbutton. The system executes CA coordination cells combination. The successfuly result is shown below.
Figure 4-17 DL CA Configuration Complete
4.3.1.6 Configuring PUCCH 1b
Configure the parameter Number of PUCCH Format 1b according to network planning.
1. guration Management window of the EMS, selectModify Area ->Managed Element -> Radio Parameter -> LTE FDD-> E-UTRAN FDD Cell->PUCH and PDCH,
select a cell configuation record and click button to enter PUCH and PDCH window.
Figure 4-18 PUCH and PDCH List
2. Configure the parameter Number of PUCCH Format 1b according to actual requirement. The parameter Number of PUCCH Format 1b indicates how many UEs
that using two carriers in the CA cell and it should be configured according to the number of UEs that the system supported. If the value is larger, the RB number
that PUCCH occupied is more, which will affect the throughput of eNodeB. If the value is 0, the CA service cannot be enabled. For example, if this parameter is
configured to 12, it indicates that the CA cell can has 120 UEs to do two carriers CA service. If there is more than 120 UEs, the other UEs only can do single-
carriers service.
Figure 4-19 PUCCH 1bConfiguration
3. Click button to complete configuring the parameter of Number of PUCCH Format 1b.
4. Repeat above steps to complete the other cell configuration for Number of PUCCH Format 1b.
When all the initial parameters including CA part are configured completely, and make sure that the configuration is correct, perform the whole table synchronization.
When configuration for deactivating the CA function is ready, split the downlink CA coordination relation, and then do data synchronization to the eNodeB.
1. Split DL CA Coordination Relation:
In the Configuration Management window of the EMS, select EMS -> Configuration Management -> Special Function of Standard -> Cell Coordination
Management, open the Coordination Management Window,select the test eNodeB and split CA coordination relation.
Figure 4-21 Select the eNodeB to split CA Coordination
2. Synchronize data
After the above steps, perform incremental synchronization to the eNodeB.
4.4 DL Multi-Carrier Aggregation (FDD+TDD)
This version supports FDD+TDD downlink CA multiple carrier aggregations, namely, 2CC, 3CC, 4CC, 5CC. The following configuration for Intra-eNodeB FDD+2TDD
3cells CA is taken as an example. The configuration for Inter-eNodeBFDD+TDD downlink CA, refers to chapter 4 Inter- eNodeBCA.
1. Intra-eNodeB FDD+2TDD 3cells CAconfiguration involves configure frequency and bandwidth of CA Cells, and this configuration is based on UE capability. In
addition, Configure CR0 board and X2+IP, Switch for CA between FDD and TDD, Switch for 3CC CA Between FDD and TDD, Max SCell Num for CA, configure
PUCCH format resources, FDD+TDD Neighbor relation and Coordinationrelation.
2. Configure CR0/CR1/FS5Dboard
Insert theCR0board in the slot3 of BBU (B8200), then set the Board standard to ALL, Board function mode to TDD&FDD CloudRadio, Physical Board name to
FS5C as shown below.
Figure 4-22 Add FS5CBoard
3. Configure Co-eNodeB X2+Port IP Link Table
In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD >Resource Interface Configuration >Co-eNodeB
X2+Port IP Link Table, double-click the record. The Cooperating eNodeB ID is TDD eNodeB ID in mixed mode, and X2+Port IP Address is an arbitrary address.
In the Co-eNodeB X2+Port IP Link Table window, configure Co-eNodeB X2+Port IP Link Table as shown below.
Figure 4-23 Configuring X2+IP Configuration
The same configuration is applied to TDD mode. The Coordinating eNodeB ID is FDD eNodeB ID in mixed mode, and X2+Port IP Address is an arbitrary address.
4. Configure the Switch for CA between FDD and TDD, Switch for 3CC CA Between FDD and TDD
In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration > Global Switch,
double-click the record. In the Global Switch window, configure the Switch for CA between FDD and TDD as shown below.
Figure 4-24 Configuring the Switch for CA between FDD and TDD
Figure 4-25 Configuring the Switch for 3CC CA between FDD and TDD
5. Configuring PUCCH Format Resources
In the Configuration Management window of the EMS, selectModify Area ->Managed Element -> Radio Parameter -> LTE FDD-> E-UTRAN FDD Cell->PUCH
and PDCH, select a cell configuation record and click button to enter PUCH and PDCH window.The FDD cell parameter of the RB Number of PUCCH Format
3 is 1. The TDD cell parameter of the RB Number of PUCCH Format 3 is also 1 as shown below.
Figure 4-26 Configuring PUCCH Format Resources
6. Configuring the Max SCell Num for CA
Configure the Max SCell Num for CA. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE, double-click the record. In
the window, configure the Max SCell Num for CA to 2 as shown below.
7. Configure FDD+TDD Neighbor relation
The cells are configured to neighbor relation. For detailed method, refer to theneighbor relation Configuration of the DL 2cells.
8. Configure Coordinationrelation
The cells are configured to CA coordinating relation. For detailed method, refer to the Coordination relation Configuration of the DL 2cells.
Disabling the feature, refers to Intra/Inter-Board CA (DL 2CC).
4.5 Carrier Aggregation (DL 3CC)
Configure the Intra-eNodeB DL 3Cells CA according to network planning.
1. Configure the frequency and bandwidth for the three cells according to UE capability. And then configure the Max SCell Num for CA, The RB number of
PUCCH format 3,Neighbor relation and Coordinationrelationas shown below.
2. Configure the Max SCell Num for CA. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD, double-click the
record. In the window, configure the Max SCell Num for CAto 2 as shown below.
3. Configure The RB number of PUCCH format 3. In the Configuration Management window of EMS, select Modify Area > Radio Parameter> LTE FDD
>E-UTRAN FDD Cell >PUCH And PDCH, double-click the record. Configure the three cells RB number of PUCCH format 3to 1as shown below.
Figure 4-29 Modify The RB number of PUCCH format 3
4. Configure neighbor relation. The neighbor relation Configuration of DL 3cells CA is to make neighbor relation for any two of the three.
In EMS configuration management window, select Modify -> wireless parameters - > LTE FDD ->Neighbor Relation Configuration ->E-UTRANNeighbor
Relation.In the Window, ,modify the list of Three neighbor relationship ,"Intra-LTE neighbor relation” is configured toSame Coverage or Neighboring. For
detailed configuration method, refer to the neighbor relation Configuration of the DL 2cells.
Figure 4-30 Configuring the neighbor relation of DL 3cells CA
5. Configure the Coordinationrelation. The CoordinationrelationConfiguration of DL 3cells CA is to make DL Coordinationrelationfor any two of the three. For
detailed method, refer to the Coordinationrelation Configuration of the DL 2cells.
Figure 4-31 Configure the Coordination relation of DL 3cells CA
4.6 Carrier Aggregation (UL 2CC)
Configure the Intra-eNodeB UL 2Cells CA according to network planning.
1. UL CA cannot be configured individually, and it must be configured with DL CA, so the frequency, bandwidth and neighbor relation of the two cells must be
consistent with DL CA. The difference between UL CA and DL CA is theCoordination configuration.
2. Configure the UL CA coordination relation. In the Configuration Management window of the EMS, selectConfiruration Management -> Special Function of
Standard -> Cell Coordination Management.Select the eNodeB, then click Query, select the Pcell of CA, and then click Group button as shown below.
Figure 4-32 Configuring the UL CA coordination relation
3. Pop-up Neighbor list dialog box, set collaborative relationship Type to UL and DL CA , and then choose SCell of CA according to the network planning as
shown below.
Figure 4-33 Configuring Collaborative Relation Type
4. Click OK button, the results are as shown below.
Figure 4-34 Complete CA Configuration
4.7 Cloud CA (Centralized)
Configure the Inter-eNodeB DL 2cells CA according to network planning(including Inter-eNodeB FDD+FDD CA andInter-eNodeB FDD+TDD2cells CA. The
configuration for Inter-eNodeB FDD+FDD CA is taken as an example).
1. The hardware requirements:
Each eNodeB must have a CR0 Board; And two CR0 are both inserted in Slot 3 of BBU.
Connect the right optical port of two CR0 boards with 10G optical module directly;
The GPS clock must be connected and synchronized;
Clock synchronization mode must be phase synchronization.
In configuration management window, select Modify ->Device ->B8200 ->CCE1->Clock Device Set->Clock Device. Create new record that Clock Device with
default parameters.
Figure 4-35 Configure Clock Device
In configuration management window, select Modify ->Device ->B8200 ->CCE1->Clock Device Set. Set Clock synchronization mode to Phase synchronization.
Figure 4-36 Configure Clock Synchronization mode
2. Inter-eNodeB FDD+FDD2cells CA configuration involves Configure CR0 board, Configure X2+(FDD) of CR0 Board and X2+IP Configuration, SCTP, Co-eNodeB
X2 + Port IP Link Table, Neighbor relation and Coordination relation.
3. Configure CR0 Board. Insert the CR0 board in the slot3, and then set the Board standard to ALL, Board function mode to LTE-FDD CloudRadio, Physical Board
name to CR0 as shown below.
Figure 4-37 Configuring CR0 Board
4. Configure X2+(FDD) of CR0 Board.
Connect the right optical port of two CR0 Boards with 10G optical module directly. Then set the Port Working Mode to 10Gbpsas shown below.
Figure 4-38 Configure X2+(FDD) of CR0 Board
5. Configure X2+IPof CR0 Board.
In EMS configuration management window, select Modify ->Transmission Network -> LTE FDD ->X2+IP Configuration(FDD). Create new record that IP
Address and Gateway IP with the same network section as shown below. Two CR0, one IP Address is configured as 169.0.0.1, and the other IP Address is
configured as 169.0.0.2.
Figure 4-39 Createnew X2+IP Configuration
6. ConfigureSCTP. Both eNodeBs must be configured.
In EMS configuration management window, select Modify ->Transmission Network -> LTE FDD ->Signaling and Business ->SCTP. Create new record set
the Local port number = Remote port number = 36422,set Remote address to the IP of Coordination eNodeB for FDD.
Note: This step is optional. If omitted, the selecting SCell flexibility function cannot be activated.
Figure 4-40 Configuring SCTP
7. Configure the Co-eNodeB X2 + Port IP Link Table
Both eNodeB must be configured. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD >Resource Interface
Configuration> Co-eNodeB X2 + Port IP Link Table. Create new record, then set the Cooperating eNodeB ID to X(X= Coordination eNodeB >Modify Area
> Radio Parameter > LTE FDD, double-click the record, In the window, find the value of eNodeB ID), set the X2 + Port IP Address to Y(Y=Coordination
eNodeB >IP Address of CR0). Configure the Used IP Layer Configuration and Used Bandwidth Resource of FDD, Co-eNodeB X2 + Port IP Link Table of
FDD is complete. And the other eNodeB is similar to this one as shown below.
Figure 4-41 Configure the Co-eNodeB X2 + Port IP Link Table
8. Configure Neighbor relation and Coordination relation. For detailed method, refer to the DL 2cells CA.
4.8 Other Relevant Configuration
4.8.1 Configuring Measurement Parameter for Adding CA SCell
Modify the parameter RSRP threshold of Add SCell Measurement event A4 according to actual requirements.
1. In the Configuration Management window of the EMS, select Modify Area ->Radio Parameter -> LTE FDD -> Measurement Parameter Configuration -> UE
E-UTRAN Measurement.
Figure 4-42 UE E-UTRAN Measurement List
2. In the UE E-UTRAN Measurement List window, select the record whose measurement configuration function name is Add SCell Measurement and
Measurement Configuration Index is 500, then click button, enter to UE E-UTRAN Measurement Window.
3. In this window, modify the parameter RSRP Absolute Threshold of Event Decision for A4 event according to test requirement. SCell A4 measurement
configuration parameters MaxRptCellNum need to be configured according to the actual coverage scene. When site is independently covered with a different
frequency, there is only one neighbor cell, the parameters is recommended to 1; when the site is between the overlapping coverage, there are multiple neighbor
cells for the same and different frequency, the parameter is recommended to 3.
4. Click button, and complete the configuration for Add SCell Measurement.
Figure 4-44 Configuring the Parameter RSRP Absolute Threshold of Event Decision for A4 Event
5. Click button, and complete the configuration for Add SCell Measurement.
4.8.2 Configuring Measurement Parameter for Removing CA SCell
Modify the parameter RSRP threshold of Remove SCell Measurement A2 event according to actual requirements.
1. In the Configuration Management window of the EMS, select Modify Area -> Radio Parameter -> LTE FDD -> Measurement Parameter Configuration -> UE
E-UTRAN Measurement, the UE E-UTRAN Measurement List window is displayed.
2. In the UE E-UTRAN Measurement List window, select the record whose measurement configuration function name is Remove SCell Measurementand
Measurement Configuration Index is 510, then click button to enter the UE E-UTRAN Measurement window.
Figure 4-45 Configuration Record for Remove SCell Measurement
3. In this window, modify the parameter RSRP Absolute Threshold of Event Decision for A2 event according to test requirement.
4. Click button, and complete the configuration for Remove SCell Measurment.
4.8.3 Configuring Measurement Parameter for Modifying CA SCell
Modify the parameter RSRP threshold of Add SCell Measurement A6 event according to test requirement.
1. In the Configuration Management window of the EMS, select Modify Area ->Radio Parameter -> LTE FDD -> Measurement Parameter Configuration -> UE
E-UTRAN Measurement, the UE E-UTRAN Measurement List window is displayed.
2. In the UE E-UTRAN Measurement List window, select the record whose measurement configuration function name that is Modify SCell Measurement and
Measurement Configuration Index is 520, then click button, enter to UE E-UTRAN Measurement Window.
3. In this window, modify the parameter RSRP Absolute Threshold of Event Decision for A6 event according to test requirement.
4. Click button, and complete the configuration for Add SCell Measurment.
4.8.4 Configuring Carrier Aggregation Parameter
Modify RB ratio threshold for SCC activating and deactivating according to requirement.
1. In the Configuration Management window of the EMS, selectModify Area > Radio Parameter> LTE FDD > E-UTRAN FDD Cell >Carrier Aggregation Config,
and select a record of Carrier Aggregation Config in Carrier Aggregation Config List window, then click button , and Carrier Aggregation Config window is
shown below.
Figure 4-49 Carrier Aggregation Config List Window
2. In Carrier Aggregation Config window, modify the RB ratio threshold for SCC activating/deactivating.
Figure 4-50 Modify the RB Ratio Threshold for SCC Activating/Deactivating
3. Click button, and complete a cell configuration parameter for Carrier Aggregation Config.
4. Repeat above steps to complete the other cell configuration for Carrier Aggregation Config.
4.8.5 Configuring CAPrimary Carrier Frequency Priority
Modify CA primary carrier frequency priorityaccording to test requirement.
1. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch,
double-click the record. In the Global Switch window, modify the Primary carrier frequency priority switch for CA as shown below.
Figure 4-51 Modify the Primary carrier frequency priority switch for CA
2. In the Configuration Management window of EMS, click Modify Area> Radio Parameter > LTE FDD > E-UTRAN Service Configuration>frequency priority of
Pcell, click the button new, Add a frequency priority record as shown below.
Figure 4-52 Add a frequency priority of Pcell record
3. Configure the Switch for fixed Primary carrier based measurement (default value is no). In the measurement Parameter Window, modify the Switch for fixed
Primary carrier based measurement as shown below.
Figure 4-53 Modify the Switch for fixed Primary carrier based measurement
4.8.6 Configuring CA Fair scheduling
1. Differentiated scheduling is used by default. To enable fair scheduling function, open the Fair scheduling switch. In the Configuration Management window of
EMS, select Modify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch, double-click the record. In the Global Switch
window, open the Switch of CA Fair Schedule as shown below.
Figure 4-54 Open the Switch of CA Fair Schedule
2. In the Configuration Management window of EMS, select Modify Area > Radio Parameter > LTE FDD to configure the Factor of CA Fair Schedule to 0-1as
shown below.
Figure 4-55 Modify the Factor of CA Fair Schedule
4.8.7 Configuring Flexible SCell Selection
Flexible Scell selection can be configured according to actual requirements. Flexbile Scell selection includes Frequency Priority-Based SCC Selection and Load-Based
SCC Selection. These two functions can be enabled separately or at the same time.
1. Configuring of Frequency Priority-Based SCC Selection includes The Switch of SCell Based on Frequency Priority, scell frequency priority and The Switch of
MeasID Sorting for CA. After The Switch of SCell Based on Frequency Priority is configured to open, this function is enabled; For scell frequency priority, the
higher the value is, the higher priority it is; for The Switch of MeasID Sorting for CA, after the switch is open, the Measurement ID will be ranked according to
SCell frequency priority when delivering A4 of SCell measurement.
2. Configruing of Load-Based SCC Selection includes The Switch of SCell Based on DL PRB Ratio, PRB Ratio Threshold of SCell Configuration (%) , PRB Ratio
Threshold of PCell for Getting Load Information (%) and Load Type Indicator and other parameters as shown in the figure below. The switch of Scell Based on
DL PRB Ratio is configured to Open to enable the function, and PRB Ratio Threshold of SCell Configuration (%) , PRB Ratio Threshold of PCell for Getting Load
Information (%) and Load Type Indicator can be configured according to actual demands.
3. In the Configuration Management window of EMS, selectModify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Carrier Aggregation Config,
double-click the record, configureThe Switch of SCell Based on Frequency Priority, The Switch of SCell Based on DL PRB Ratio, The Switch of MeasID Sorting
for CA, PRB Ratio Threshold of SCell Configuration PRB Ratio Threshold of PCell for Getting Load Information and Load Type Indicator as shown below.
Figure 4-56 Configuring the Switch for Selecting SCell flexibility
4. In the Configuration Management window of EMS, selectModify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell >Measurement Parameter, double-
click the record, configure scell frequency priority as shown below.
Figure 4-57 Configuring SCell frequency priority
4.8.8 Configuring User-Based Admission
Configuring user-based admissionaccording to test requirement.
1. In the Configuration Management window of EMS, select Modify Area > Radio Parameter> LTE FDD >E-UTRAN FDD Cell >Admission Control, double-click
the record, configure Switch of CA User Restrict to open, and you can also set Threshold of forbid Configured as SCell and Threshold of CA UE Back Off as
shown below.
Figure 4-58 Modify the Switch of CA User Restrict
double-click the record. In the Global Switch window, configure the Switch of CA UE Backoff as shown below.
Figure 4-59 Configuring the Switch of CA UE Backoff
4.8.9 Configuring CA UE Monitor
double-click the record. In the Global Switch window, configure the Switch of CA UE Monitor to Open as shown below.
Figure 4-60 Modify the Switch of CA UE Monitor
4.8.10 Configuring CA UE Handover with SCell
double-click the record. In the Global Switch window, modify the Switch of CA UE Handover With SCell as shown below.
Figure 4-61 Modify the Switch of CA UE Handover with SCell
5 Related Counters, KPI and Alarms
5.1 Related Counters
Table 5-1 Related Counters
SN CounterID Counter name

1 C374241900 Number of UL RB obtained by MCS0 on PCell

33 C374241932 Error Number of DL Init TBs for PCell
34 C374241933 Total Number of DL Init TBs for PCell
35 C374241934 Error Number of UL Init TBs for PCell
36 C374241935 Total Number of UL Init TBs for PCell
37 C374241936 Error Number of DL Init TBs for SCell
38 C374241937 Total Number of DL Init TBs for SCell
39 C374241938 Error Number of UL Init TBs for SCell
40 C374241939 Total Number of UL Init TBs for SCell
41 C374241940 Max Number of CrossBBU UEs
42 C374241941 Average Number of CrossBBU UEs
43 C374241942 Number of UL RB obtained by MCS0 on SCell
75 C374241974 Number of DL RB obtained by MCS0 on PCell

Number of RB obtained DL by MCS20~23 for
107 C374242006
256QAM ITBS table2 on PCell
108 C374242007
Number of RB obtained DL by MCS31 for
109 C374242008
110 C374242009 Number of CQI0 Be Used on PCell
126 C374242025 Number of DL RB obtained by MCS0 on SCell
158 C374242057
256QAM ITBS table2 on SCell
159 C374242058
Number of RB obtained DL by MCS31 for
160 C374242059
161 C374242060 Number of CQI0 Be Used on SCell

177 C374210750 Uplink Maximum User Number of SCell
178 C374210751 Downlink Maximum User Number of SCell
179 C373343812 DL High PDCP Throughput of CA User
180 C373343813 DL Low PDCP Throughput of CA User
181 C373343814 DL PDCP Time of CA User
182 C373343897 UL High PDCP Throughput of CA User
183 C373343898 UL Low PDCP Throughput of CA User
184 C373343899 UL PDCP Time of CA User
185 C373384352 Maximum User Number With CA Capability
186 C373384356 Maximum User Number of Enabled CA
187 C373384367 Average User Number of Scell
188 C373384368 Average Active User Number of Pcell
189 C373384369 Average Active User Number of Scell
Maximum RRC-connected user instances in the
190 C373384376
CA scenario
Average RRC-connected user instances in the
191 C373384377
CA scenario
192 C373384381 Maximum Active User Number of Pcell
193 C373384382 Average User Number With CA Capability
194 C373384383 Downlink Average User Number of Enabled CA
195 C373384384 Uplink Maximum User Number of Enabled CA
196 C373384385 Uplink Average User Number of Enabled CA
197 C373384386 Downlink Maximum Active User Number of SCell
Downlink Average Active 2CC User Number of
198 C373384387
PCell
Downlink Maximum Active 2CC User Number of
199 C373384388
PCell
Downlink Average Active 3CC User Number of
200 C373384389
PCell
Downlink Maximum Active 3CC User Number of
201 C373384390
PCell
202 C373384391 Uplink Average User Number of Enabled 2CC CA
Uplink Maximum User Number of Enabled 2CC
203 C373384392
CA
204 C373384393 Uplink Average Active User Number of PCell
205 C373384394 Uplink Maximum Active User Number of PCell
206 C373384395 Uplink Average Active 2CC User Number of PCell
Uplink Maximum Active 2CC User Number of
207 C373384396
PCell
208 C373384397 Uplink Average Active User Number of SCell
209 C373384398 Uplink Maximum Active User Number of SCell
210 C373384399 Uplink Average User Number of SCell
211 C373596932 DL Scheduled RB Number for SCC UE
212 C373596933 DL Scheduled TB Number for SCC UE
213 C373596934 DL Scheduled TB Size for SCC UE
214 C373596951 DL Scheduled RB Number for PCC UE
215 C373596952 DL Scheduled TB Number for PCC UE
216 C373596953 DL Scheduled TB Size for PCC UE
PRB Number of PDSCH(DTCH) Borrowed from
217 C373596956
Scell
218 C373596957 PRB Number of PDSCH Borrowed from Scell
219 C373596958 Active Scell Number
220 C373596959 Active Scell Success Number
221 C373596960 Deactive Scell Number
222 C373596961 Deactive Scell Success Number
223 C373597001 Number of Implicit Deactive Scell due to Timeout
Number of Deactive Scell No due to Deactive
224 C373597002
Mac CE(Exclude Implicit Deactive Scell)
225 C373597023 UL Scheduled RB Number for SCC UE
226 C373597024 UL Scheduled TB Number for SCC UE
227 C373597025 UL Scheduled RB Number for PCC UE
228 C373597026 UL Scheduled TB Number for PCC UE
229 C373597027 UL Scheduled TB Size for SCC UE
230 C373597028 UL Scheduled TB Size for PCC UE
231 C373597029 UL Active Scell Request Number
232 C373597030 UL Deactive Scell Request Number
234 C373597033 DL Active Scell Request Number

235 C373597034 DL Deactive Scell Request Number
236 C373597085 UL Scheduled Number for PCC UE
237 C373597086 DL Scheduled Number for PCC UE
238 C373597087 UL Scheduled RB Number for CA Active UE
239 C373597088 DL Scheduled RB Number for CA Active UE
240 C373597089 UL Scheduled Number for CA Active UE
241 C373597090 DL Scheduled Number for CA Active UE
242 C373597091 PRB Number of PUSCH Borrowed from SCell
243 C373597092 PRB Number of PUSCH Lend to PCell
245 C373220657 Number of Add DL Scell
246 C373220658 Number of Add DL Scell Success
247 C373220659 Number of Delete DL Scell
248 C373220660 Number of Delete DL Scell Success
249 C373220662 Number of Blind Add Scell
250 C373220663 Number of Blind Add Scell Success
251 C373220664 Number of Attempted SCell Switch
252 C373220665 Number of Successful SCell Switch
253 C373220666 Number of Context Online
254 C373220668 CA limited times due to SPID restriction
255 C373220669 Times of Add UL Scell
256 C373220670 Times of Add UL Scell Succ
257 C373220671 Times of Delete UL Scell
C374281110 Total Number of DL TB Remained Error Packets
258
for PCell
C374281111 Total Number of DL TB Remained Error Packets
259
for SCell
C374281112 Total Number of UL TB Remained Error Packets
260
for PCell
C374281113 Total Number of UL TB Remained Error Packets
261
for SCell
C374281114 Number of Successfully transferred DL MAC
262
TBSize for PCell
263
TBSize for SCell
C374281116 Number of Successfully transferred UL MAC
264
TBSize for PCell
265
TBSize for SCell
266 TBSize for SCell which PCell of UE is another
frame structure
C374281119 Number of DL RB for SCell which PCell of UE is
267
another frame structure
C374281120 Number of Successfully transferred DL MAC TB
268 for SCell which PCell of UE is another frame
structure
269 TBSize for SCell which PCell of UE is another
frame structure
C374281122 Number of UL RB for SCell which PCell of UE is
270
another frame structure
C374281123 Number of Successfully transferred UL MAC TB
271 for SCell which PCell of UE is another frame
structure
C374222609 the DL Scheduled total RB Number for PCC UE
272
when configure SCC
C374222610 the DL Scheduled total TB Number for PCC UE
273
when configure SCC
C374222611 the DL Scheduled total TB Size for PCC UE when
274
configure SCC
C374210760 DL Maximum User Number With 2CC(Maximum
275
CC Number) CA Capability
C374210761 DL Average User Number With 2CC(Maximum
276
C374210762 DL Maximum User Number With 3CC(Maximum
278
C374210763 DL Average User Number With 3CC(Maximum
279
C374210766 DL Maximum User Number With 2CC CA
280
Enabled
281 C374210767 DL Average User Number With 2CC CA Enabled
C374210768 DL Maximum User Number With 3CC CA
282
Enabled
283 C374210769 DL Average User Number With 3CC CA Enabled
5.2 Related KPI

None
5.3 Related Alarms
None
6 Feature Validation
Take the following test specifications as example, and other CA test scenarios arethe same, they are not covered in this document.
6.1 DL Inter-Band Carrier Aggregation (2CC)
6.1.1 Topology
For the test environment, see the figure below.
Figure 6-1 Intra-eNodeB Carrier Aggregation Test
For the required devices, refer to the table below.
SN Device Remarks
1 eNodeB One BBU;
Two or three RRUs
2 UE One.
3 Adjustable attenuator Four
4 EPC One.
5 FTP server One.
For the DL Inter-Bandtwo carriers’ aggregation test specification, refer tothe table below.
Table 6-2 DL Inter-Band Two Carries Aggregation Function Test Specification
Test item DL Inter-Band Two Carries Aggregation Function Test

Feature ID ZLF34-00-013
Verify that the LTE system supports the inter-band DL two carriers
Purpose
aggregation.
1. Cell1 and Cell 2 that belong to the same eNodeB are
established successfully and they work properly; Two UEs
access Cell1 and Cell2 respectively and the peak throughput
of UEs can be reached in the same location. Cell1 and Cell2
are configured as CA cells.
2. The frequency band of Cell 1 belongs to Band 3, and the
frequency band of Cell 2 belongs to Band 7;
3. The bandwidths of Cell 1 and Cell 2 are all 20MHz;
4. The CA function is open;
5. LTE EPC works normally;
6. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
7. The UE supports CA function.
8. The performance of computer for FTP server and UEs satisfies
the performance test requirement.
Prerequisites
9. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
12
1b N/A
Configured N/A
Other Parameters according to the
actual network
Step Expected step result

Place the UE to the center of the
1
cell 1 and cell 2.
UE accesses Cell2 successfully, so the
Cell2 is a PCell and Cell1 is a SCell.
Power on UE and initiate attach
2 The sCellToAddModList IE is included
operations.
in the RRC Connection Reconfiguration
message.
The throughput is normal.
Start FTP download service on The SCC is activated.
3
the UE side. Record the test result of eNodeB side
and UE side.
Stop downlink FTP service and
4 The UE detaches successfully.
detach UE.
The SCC can be added and activated.
Expected result
The downlink throughput is normal.
In the inter-band DL carrier aggregation scenario, the SCC can be
Criteria
added and activated, and the downlink throughput is normal.
Test result Passed.
6.1.3 Test Result
After UE attaches successfully, Whether the UE supports CA function can be checked in the UE Capability Information message. According to Section 5.6A in 3GPP
TS 36.101 E21, CA bandwidth classes are defined as below.
1. A indicates a non-contiguous carrier.
2. B indicates two intra-band contiguous carries, and the number of aggregated RB is between 25 and 100.
3. C indicates two intra-band contiguous carries, and the number of aggregated RB is between 100 and 200.
4. D indicates three intra-band contiguous carries, and the number of aggregated RB is between 300 and 400.
5. In the UE Capability Information, if a band supports UL and DL carrier aggregation simultaneously, it can be a PCC. If the band only supports UL or DL carrier
aggregation, it can be a SCC only.
The following figure shows the UE capability information with UE category 6. Band7 supports UL and DL carrier aggregation simultaneously, so it can be a PCC.
Band3 only supports DL carrier aggregation, so it can be a SCC.
Figure 6-2 UE Capability Information
Check whether the SCell is added by RRC Connection Reconfiguration message. The following figure shows the SCell(PCI 189) adding successfully.
Figure 6-3 SCell Adding Successfully
Check the PCell and SCell PCI are 188 and 189 respectively after UE attached successfully by QXDM tools, as shown in the figure below.
Figure 6-4 CA UE Attached Successfully
Start downlink FTP or UDP service, and check the downlink throughput by QXDM DL Throughput and BLER view, as shown in the figure below. The downlink
throughput of PCell and SCell are all 150Mbps. So the downlink total throughput of UE is 300Mbps, which is met the test requirement.
Figure 6-5 Downlink Throughput of PCell and SCell
6.2 Non-contiguous Intra-Band Carrier Aggregation
6.2.1 Topology
Refer to Section 6.1.1Topology.
For the DL non-contiguous intra-band two carrier aggregation test specification, refer tothe table below.
Table 6-3 DL Non-Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Test item DL non-contiguous intra-band two carrier aggregation test

Verify that the LTE system supports the non-contiguous intra-band
Purpose
DL two carriers aggregation.
established successfully and they work properly. The
frequency band of Cell 1 and Cell2 are band3. The nominal
channel spacing between Cell1 and Cell2 is 20MHz. Two UEs
Prerequisites 8. The main parameters are configured as below.
Global Switch
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

1
cell 1 and cell 2.
operations.
message.
3
and UE side.
detach UE.
Expected result
In the DL non-contiguous intra-band carrier aggregation scenario,
Criteria the SCC can be added and activated, and the downlink throughput
is normal.
Test result Passed.
6.2.3 Test Result
Refer to Section 6.1.3Test Result.
6.3 Contiguous Intra-Band Carrier Aggregation
6.3.1 Topology
For the DL contiguous intra-band two carrier aggregation test specification, refer tothe table below.
Table 6-4 DL Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Test item DL contiguous intra-band two carrier aggregation test

Verify that the LTE system supports the contiguous intra-band DL
Purpose
two carriers aggregation.
established successfully and they work properly. The
frequency band of Cell 1 and Cell2 are band3. The nominal
channel spacing between Cell1 and Cell2 is 14.4MHz. Two
UEs access Cell1 and Cell2 respectively and the peak
throughput of UEs can be reached in the same location. Cell1
and Cell2 are configured as neighboring cells and CA cells.
2. The bandwidths of Cell 1 is 20MHz, and Cell2 is 10MHz;
Prerequisites 8. The main parameters are configured as below.
Global Switch
Open[1]
Continuous 2CC CA N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

1
cell 1 and cell 2.
operations.
message.
3
and UE side.
detach UE.
Expected result
In the DL contiguous intra-band carrier aggregation scenario, the
Criteria SCC can be added and activated, and the downlink throughput is
normal.
Test result Passed.
6.3.3 Test Result
After UE accesses in cell, the event A4 measurement configuration for SCC adding is including in the RRC Connection Reconfiguration message, and the threshold of
event A4 is -80, as shown in the figure below.
Figure 6-6 Measurement Configuration for SCC Adding in the RRC Connection Reconfiguration Message
After the UE’s signal quality is higher than the event A4 threshold, the UE sends the Measurement Report message, as shown in the figure below.
Figure 6-7 UE Sends the Measurement Report Message
Then eNodeB sends the RRC Connection Reconfiguration message, adding the cell with PCI=78 to SCell, as shown in the figure below.
Figure 6-8 eNodeBSends the RRC Connection Reconfiguration Message, Adding the Cell with PCI=78 to SCell
Start downlink full-buffer service to UE, and the SCC is activated, as shown in the figure below.
Figure 6-9 SCC Is Activated
The downlink throughput is normal and about 205Mbps, as shown in the figure below. The PCI of PCell is 75 and SCell is78. The E-ARFCN of PCell is 1650 and SCell
is 1506.
Figure 6-10 Downlink Throughput in the Contiguous Intra-Band Carrier Aggregation
6.4 SCell Adding and Deleting Test
6.4.1 Topology
For the CA SCell adding and deleting test specification, refer to the table below.
Table 6-5 CA SCell Adding and Deleting Function Test Specification
Test item CA SCell adding and deleting function test.

Purpose Verify that the CA SCell adding and deleting function.
Prerequisites

established successfully and they work properly;Two UEs
2. The carrier frequency of Cell 1 belongs to Band 3, and the
carrier frequency of Cell 2 belongs to Band 7;
4. The LTE EPC works normally;
6. The A2/A4 events for CA function are configured;
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

The UE is connected to the serving cell
Place the UE to the center of the successfully.
1 cell 1 and cell 2, and perform the The eNodeB sends RRC Connection
attach operation. Reconfiguration message to add SCell,
and the message carries A2 event.
After the signal quality goes to weaker,
Adjust the signal quality to make UE reports A2 event, and the eNodeB
2 it weaker, and trigger the A2 sends RRC Connection Reconfiguration
event to delete SCell. message to delete SCell and it also
carries A4 event in the message.
Adjust the signal quality to make After the signal goes to better, UE
it better, and trigger the A4 event reports A4 event, and the eNodeB
3
to adding SCell, and activate sends RRC Connection Reconfiguration
SCell to sharing partial service. message to add SCell.
Expected result The function of SCell adding and deleting works normally.
SCell adding and deleting flows can be triggered successfully and
Criteria
the flows are correct.
Test result Passed.
6.4.3 Test Result
After UE attached, the eNodeB sends RRC Connection Reconfiguration message which carries A2 event to trigger SCell deleting. See the figure below.
Figure 6-11 A2 Event Sending
Adjust SCell’s signal quality and make it weaker, the A2 event reporting is triggered.
Figure 6-12 A2 Measurement Reporting
The eNodeB sends the RRC Connection Reconfiguration message, which carried A4 event of SCell and deletes SCell. See the figure below.
Figure 6-13 eNodeB Sends A4 Event Configuration of SCell and Deletes SCell
Adjust the SCell’s signal quality and make it better.The A4 event measurement reporting is triggered to report. See the figure below.
Figure 6-14 A4 Measurement Event Reporting
The eNodeB sends RRC Connection Reconfiguration to add SCell. See the figure below.
Figure 6-15 A4 Measurement Reporting Triggers Adding SCell
6.5 SCell Modifying Test(A6 Event)
6.5.1 Topology
For the CA SCell modifying test specification, refer tothe table below.
Table 6-6 CA SCell Modifying Function Test Specification
Test item CA SCell Modifying Function Test.

Purpose Verify that the CA SCell modifying function can be used normally.
Prerequisites 1. Cell1 and Cell 2 that belong to the same eNodeB are
are configured as CA cells
3. The bandwidths of Cell 1 and Cell2 are all 20MHz;
4. The CA function is enabled;
7. The A6 event for CA function is configured.
8. The intra-frequency neighbor cell of SCell is configured and
the neighbor cell works normally.
Global Switch
Open[1]
CA N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Measurement Config Group
Modify Scell Measurement 520

Configuration Index
UE E-UTRAN Measurement
Measurement N/A
Configuration Index
Measurement Modify Scell N/A
Configuration Function Measurement
Triggered Event Quantity RSRP N/A
Event ID A6 N/A
Configured N/A
actual network

successfully.
1 cell 1 and cell 2, and perform the The eNodeB sends RRC Connection
attach operation. Reconfiguration message to adding
SCell and the message carries A6
event configuration.
Adjust the attenuator, make the
intra-frequency neighbor cell’s
signal quality is better than SCell After A6 measurement event threshold
2 and reach the threshold of A6 is reached, the UE will report A6
event configured on OMC to measurement event reporting.
trigger A6 measurement event
reporting.
The eNodeB sends RRC
Connection Reconfiguration After the eNodeB received the
message, deletes the original Measurement Report message, it will
3
SCell and adds the intra- send RRC Connection Reconfiguration
frequency of original SCell to a message to modify SCell.
new SCell.
Expected result The function of SCell modifying works normally.
SCell modifying flows are triggered successfully and they are
Criteria
correct.
Test result Passed.
6.5.3 Test Result
After UE attached, the eNodeB sends RRC Connection Reconfiguration message which carries A6 event. See the figure below.
Figure 6-16 A6 Event Configuration
The intra-frequency neighbor cell’s signal quality is better than SCell and reaches the threshold of A6 event configured on OMC. The UE reports A6 Measurement
Report message. See the figure below.
Figure 6-17 A6 Measurement Report
After the eNodeB received A6 measurement report, the eNodeB deletes old SCell and adds new SCell in RRC Connection Reconfiguration message. See the figure
below.
Figure 6-18 Deletes Old SCell and Adds New SCell
6.6 SCell Activating and Deactivating
6.6.1 Topology
For the CA SCell activating and deactivating test specification, refer tothe table below.
Table 6-7 SCell Activating and DeactivatingTest Specification
Test item CA activating and deactivatingfunction test

Verify that the CA SCell activating and deactivating function can
Purpose
be used normally.
are configured as CA cells
3. The bandwidths of Cell 1 and Cell are all 20MHz;
Prerequisites
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

1
cell 1 and cell 2.
Power on UE and perform the
Check the PCell and SCell
attach operation; make sure that
2 configuration are normal in attach
the Cell1 as PCell and cell2 as
message.
SCell.
3 The throughput is normal.
Start ping operation from UE side The SCell is activated.

and downlink FTP service. Check
whether the SCC is activated.
4 keep ping operation, check The SCC is deactivated.
whether the SCC is deactivated.
Stop service; detach UE, and
5 UE detaches successfully.
record log of UE.
Expected result The function of SCell activating and deactivating works normally.
SCell activating and deactivating flows are triggered successfully
Criteria
and they are correct.
Test result Passed.
6.6.3 Test Result
When UE keeps full-buffer downlink FTP service, the SCC active threshold is reached. The eNodeB sends active MAC CE to UE. The MAC CE has a fixed size and
consists of a single octet containing seven C-fields and one R-field. The lowest bit is R-field, the C-fields indicate the activation/deactivation status of the SCell. The Ci
field is set to "1" to indicate that the SCell with SCellIndex i shall be activated. The Ci field is set to "0" to indicate that the SCell with SCellIndex i shall be deactivated.
See the figure below, The last two bits 02 changes to binary is 0000 0010, which indicated the SCell with SCellIndex1 is activated.
Figure 6-19 MAC CE for Activating SCell
After SCC is active, the service data will transmit on both PCC and SCC. See the figure below.
Figure 6-20 Scheduling Information after SCC Activating
Then UE does ping operation, and make it reaches SCell deactivating threshold. The eNodeB sends deactivating MAC CE to UE, see the figure below. The last two
bits 00 changes to binary are 0000 0000, which indicated the SCell with SCellIndex1 is deactivated.
Figure 6-21 MAC CE for Deactivating SCell
After SCC deactivated, the data service is only transmits on PCC. See the figure below.
Figure 6-22 Scheduling Information after SCC Deactivated
6.7 Handover of CA
6.7.1 Topology
The test environment of inter-eNodeB CA handover refers to the figure below.
Figure 6-23 Inter-eNodeB Carrier Aggregation Test
For the required devices, refer to the table below.
SN Device Remarks
1 eNodeB Two, each eNodeB
established two cells.
2 UE One.
3 Adjustable attenuator Four
4 EPC One.
5 FTP server One.
For the handover of CA test specification, refer tothe table below.
Table 6-9 Handover of CA Test
Test item Handover of CA Test.

Verify that the function handover of CA is supported by LTE
Purpose
system.
Prerequisites 1. There are four cells are established successfully; Cell1 and
Cell2 are configured to a group of CA cell, Cell3 and Cell4 are
configured to a group of CA cell.
2. The carrier frequency of Cell 1 and Cell3 belong to Band 3,
and the carrier frequency of cell2 and Cell4 belongs to Band 1;
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Switch of CA User
Close[0]
Handover With Scell N/A
LTE FDD

PUCH and PDCH
12
1b N/A
Configured N/A
actual network

Place the UE to the center of the 1 successfully.
1 cell 1, and perform the attach The eNodeB sends RRC Connection
operation. Reconfiguration message to adding
Cell2 to a SCell.
UE sends the Measurement Report
message to eNodeB;
Then eNodeB sends the RRC
Connection Reconfiguration message
to UE delete the SCell and indicate UE
to be handover to the target cell;
2 Move the UE from Cell1 to Cell3
UE sends the RRC Connection
Reconfiguration Complete message to
eNodeB after handover;
Then eNodeB sends the RRC
to add cell4 as a SCell.
message to eNodeB.
Configure the parameterSwitch of
3 CA User Handover With SCell as Then eNodeB sends the RRC
Open, repeat steps 1~2. Connection Reconfiguration message
to UE, deleting the SCell Cell2 and
adding the new SCell Cell4.
Expected result The function of handover of CA works normally.
Criteria UE can be handover in the scenario of CA network.
Test result Passed.
6.7.3 Test Result
There are 7 test scenarios are described below.
6.7.3.1 Intra-eNodeB CA Handover without SCell (SCell blind adding)
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
Figure 6-24 UE Sends the Measurement Report Message of Handover A3 Event
2. Then eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
MobilityControlInfo IE.
Figure 6-25 Indicate UE to Delete SCell and be Handover to Target Cell
3. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
Figure 6-26 Handover Completes
4. Then eNodeB sends the RRC Connection Reconfiguration message to add SCell.
5. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the SCell is added successfully.
Figure 6-28 UE Sends the RRC Connection Reconfiguration Complete Message to eNodeB after the SCell Adding Successfully
6.7.3.2 Intra-eNodeB CA Handover without SCell (SCell adding based on A4 measurement)
2. Then eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
4. Then eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
Figure 6-29 eNodeB Indicates UE to Measure the SCC
5. UE sends the Measurement Report message for A4 event to eNodeB according to the measurement configuration received.
Figure 6-30 UE Sends the Measurement Report Message for A4 Event
6. Then eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
Figure 6-31 eNodeB Sends the RRC Connection Reconfiguration Message to Indicate Adding SCell.
7. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the UEadded SCell completely.
6.7.3.3 Inter-eNodeB CA Handover without SCell based on S1 interface (SCell blind adding)
2. Source eNodeB sends the Handover Required message to MME to request the target eNodeB to prepare radio resource.
Figure 6-32 Handover Required Message
3. MME sends the Handover Request message to target eNodeB. The target eNodeB sends the Handover Request Acknowledge message after the target cell
prepared radio resource.
Figure 6-33 Handover Request Message
4. MME sends the Handover Command message the source eNodeB to indicate that the target cell is ready for handover.
Figure 6-34 Handover Command Message
5. Source eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
7. The target eNodeB sends the RRC Connection Reconfiguration message to add SCell.
6.7.3.4 Inter-eNodeB CA Handover without SCell based on S1 interface (SCell adding based on A4 measurement)
2. Source eNodeB sends the Handover Required message to MME to request the target eNodeB to prepare radio resource.
3. MME sends the Handover Request message to target eNodeB. The target eNodeB sends the Handover Request Acknowledge message after the target cell
prepared radio resource.
4. MME sends the Handover Command message the source eNodeB to indicate that the target cell is ready for handover.
5. Source eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
7. The target eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
10. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the UE added SCell completely.
6.7.3.5 Inter-eNodeB CA Handover without SCell based on X2 interface (SCell blind adding)
2. Source eNodeB sends the Handover Request message to the target eNodeB to request the target eNodeB to prepare radio resource.
Figure 6-35 X2 handover Procedure
3. The target eNodeB sends the Handover Request Acknowledge message to the source eNodeB after the radio resource is ready.
4. The Source eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
6. The target eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
6.7.3.6 Inter-eNodeB CA Handover without SCell based on X2 interface (SCell adding based on A4 measurement)
2. Source eNodeB sends the Handover Request message to the target eNodeB to request the target eNodeB to prepare radio resource.
3. The target eNodeB sends the Handover Request Acknowledge message to the source eNodeB after the radio resource is ready.
4. The Source eNodeB sends the RRC Connection Reconfiguration message to UE, indicating UE to delete the SCell and be handover to the target cell with
6. The target eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
9. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the UE added SCell completely.
6.7.3.7 CA Handover with SCell
Configure the parameter “Switch of CA User Handover With Scell“ to Open, the CA handover with SCell can be triggered if the handover conditions satisfied. Take the
inter-eNodeB CA handover with SCell based on S1 as example, and other CA handover with SCell test scenarios arethe same, they are not covered in this document.
After the handover measurement threshold is reached, eNodeB sends the RRC Connection Reconfiguration message to UE, deleting the source SCell and adding the
new SCell, as shown in the figure below.
Figure 6-36 RRC Connection Reconfiguration Message for Deleting the Source SCell and Adding the New SCell
6.8 CA Primary Carrier Frequency Priority
6.8.1 Topology
For CA primary carrier frequency priority test specification, refer to the table below.
Table 6-10 CAPrimary Carrier Frequency Priority
Test item CA Primary Carrier Frequency Priority

Verify that the LTE system supports CA primary carrier frequency
Purpose
priority function.
Prerequisites 1. There are two cells are established successfully; Cell1 and
Cell2 are configured to a group of CA cell.
2. The carrier frequency of Cell 1 belong to Band 3, and the
carrier frequency of Cell2 belongs to Band 1;
3. The CA function is enabled,;
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Primary Carrier Frequency
Open[1]
Priority Switch for CA N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Frequency Priority of Pcell
0
ID N/A
Band Indicator for DL
Same with cell1
Frequency of Pcell N/A
DL Frequency of Pcell Same with cell1 MHz
100
Priority N/A
1
ID N/A
Band Indicator for DL
Same with cell2
Frequency of Pcell N/A
DL Frequency of Pcell Same with cell2 MHz

200
Priority N/A
Measurement Parameter
Switch for Fixed Primary
Carrier Based No
Measurement N/A
Configured N/A
actual network

1
cell 1
UE accesses to cell1 successfully.
The eNodeB sends the RRC
to UE to indicate UE handover to cell2,
Power on UE and perform because the frequency priority of cell2
2
attaching operation, is larger than cell1.
After handover procedure was
complete, eNodeB sends the RRC
to UE to add cell1 as a SCell.
The eNodeB sends the RRC
to UE to indicate UE handover based
Configure the parameter Switch
measurement to cell2, because the
for Fixed Primary Carrier Based
3 frequency priority of cell2 is larger than
Measurement is configured to
cell1.
Yes, repeat step 1~2.
After handover procedure was
complete, eNodeB sends the RRC
to add cell1 as a SCell for UE.
If CA UE access to a cell which is not CA primary carrier, UE will
Expected result
perform handover to the primary carrier.
If CA UE access to a cell which is not CA primary carrier, UE will
Criteria
perform handover to the primary carrier.
Test result Passed.
6.8.3 Test Result
1. The parameter Switch for Fixed Primary Carrier Based Measurement is configured to No
i. After UE accesses to the lower priority carrier cell, the eNodeB sends RRC Connection Reconfiguration message to UE to indicate UE to be handover to the
higher priority carrier. See the figure below.
Figure 6-37 RRC Connection Reconfiguration Message Carried MobilityControlInfo IE
ii. After UE is handover completely, the eNodeB sends the RRC Connection Reconfiguration message to add SCell. See the figure below.
Figure 6-38 RRC Connection Reconfiguration Message for Adding SCell
2. The parameter Switch for Fixed Primary Carrier Based Measurement is configured to Yes.
i. After UE accesses to the lower priority carrier cell, the eNodeB sends two RRC Connection Reconfiguration message to UE to indicate UE to be handover
A5 event and add SCell A4 event if the neighbor cell relation is neighboring, See the figure below. The second RRC Connection Reconfiguration message
carries the handover A5 event configuration.
NOTE: If the neighbor cell relation is same coverage, after UE accesses to the lower priority carrier, the eNodeB sends the RRC Connection
Reconfiguration message to add SCell and carry handover A5 event configuration.
Figure 6-39 The Second RRC Connection Reconfiguration Message Carries the Handover A5 Event Configuration
The third RRC Connection Reconfiguration message carries the adding SCell A4 event configuration. See the figure below.
Figure 6-40 The Third RRC Connection Reconfiguration Message Carries the Adding SCell A4Event Configuration
ii. The eNodeB does the corresponding flow according to the first Measurement Report message which carried. In this example, UE sends the Measurement
Report message for A5 handover firstly, so the eNodeB sends the RRC Connection Reconfiguration message to indicate UE to be handover to the higher
priority carrier.
Figure 6-41 UE Sends the Measurement Report Message for A5 Handover
iii. After UE is handover to the higher priority carrier, the eNodeB sends the RRC Connection Reconfiguration message carried adding SCell A4 event to UE to
wait UE reporting measurement report.
Figure 6-42 RRC Connection Reconfiguration Message Carried Adding SCell A4 Event
6.9 Carrier Aggregation(DL 3CC)
6.9.1 Topology
Refer to Section 6.1.1Topology. There are three cells that needed in the test scenario.
The test specification of Carrier Aggregation(DL 3CC) is shown in the table below.
Table 6-11 Carrier Aggregation(DL 3CC)
Test item Carrier Aggregation(DL 3CC)
Purpose Verify that the LTE system supports three carriers aggregation.
1. Cell1, cell2 and cell3 belonged to the same eNodeB are

established successfully. The carrier frequency of Cell 1 belongs
to Band 1, and the carrier frequency of Cell2 and cell3 belong to
Band 3. The bandwidth of cells is 20MHz. Cell1, cell2 and cell3
are configured as same coverage neighbor cells and a CA
group. Three UEs access to cell1, cell2 and cell3 respectively
and the downlink throughput can be reached peak throughput in
the same location.
2. The CA function is enabled.
5. The UE supports three CA function.
6. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
Prerequisites
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
The RB Number of PUCCH
1
Format 3 N/A
Configured N/A
actual network

Place UE in the center of
1
cell1, cell2 and cell3.
UE accesses to the serving cell1
successfully and the cell1 is a PCell.
Power on UE and initiate
2 Cell2 and cell3 are added as SCells in
attachoperation.
the RRC Connection Reconfiguration
message.
Two SCells activate successfully.
The downlink throughput can reach to
450Mbps for three carriers aggregated
Start best-effort FTP
3 with bandwidth 60MHz in the case of no
download service.
interference.
Record the throughput on UE and
eNodeB sides.
4 Stop service, and detach UE. UE detaches successfully.
Two SCells can be added and activated successfully.
Expected
result The downlink peak throughput is 450Mbps if maximum
aggregated bandwidth 60MHz.
Two SCells can be added and activated successfully.
Criteria The downlink peak throughput is 450Mbps if maximum
aggregated bandwidth 60MHz with no interference.
6.9.3 Test Result
Aggregated Transmission Bandwidth Configuration is the number of the aggregated RBs within the fully allocated Aggregated Channel bandwidth and is defined per
CA Bandwidth Class in the table below.
Table 6-12 CA bandwidth classes and corresponding nominal guard bands
CA Bandwidth Aggregated Number of Nominal Guard Band

Class Transmission contiguous BWGB
Bandwidth CC
Configuration
A NRB,agg ≤ 100 1 a1 BWChannel(1) - 0.5∆f1
(NOTE 2)
B 25 <NRB,agg ≤ 100 2 0.05 max(BWChannel
(1),BWChannel(2))
- 0.5 f1
C 100 < NRB,agg ≤ 200 2 0.05 max(BWChannel
(1),BWChannel(2)) - 0.5 f1
D 200 < NRB,agg ≤ 300 3 0.05 max(BWChannel
(1),BWChannel(2), BWChannel
(3)) - 0.5 f1
E 300 < NRB,agg ≤ 400 4 NOTE 3
F 400 < NRB,agg ≤ 500 5 NOTE 3

NOTE 1: BWChannel(j), j = 1, 2, 3, is the channel bandwidth of an E-UTRA component
carrier according to Table 5.6-1 and f1 = f for the downlink with f the subcarrier
spacing while f1 = 0 for the uplink.
NOTE 2: a1 = 0.16/1.4 for BWChannel(1) = 1.4 MHz whereas a1 = 0.05 for all other
channel bandwidths.
NOTE 3: Applicable for later releases.
Test this case by Qualcomm UE 9X45. The UE supported band combination is shown in the UE Capability Information. The CA supported information can be shown
in the figure below in UE log 0XB0C0 LTE RRC OTA Packet. The ca-BandwidthClassDL and ca-BandwidthClassUL of band1 are both a, which means band1 can be a
PCC because band1 has the DL and UL CA bandwidth class. The band3 only has a ca-BandwidthClassDL, which means band3 can be SCC only. The CA bandwidth
class c means supported two contiguous CCs. So the UE supports band 1+3+3 combination. Two cells with frequency band3 can be supported intra-Band contiguous
CA and the channel spacing is 19.8MHz.
Figure 6-43 The CA Supported Information is Shown in the UE CapabilityInformation message
eNodeB sends the RRC Connection Reconfiguration message which carried SCell PCI in measObjectEUTRA IE. See the figure below.
Figure 6-44 eNodeB Add Two SCell in measObjectEUTRA IE in the RRC Connection Reconfiguration Message
There is also deleting SCell measurement event A2 configuration in the same RRC Connection Reconfiguration message.
Figure 6-45 Deleting SCell Measurement Event A2 Configuration is Carried in the Same RRC Connection Reconfiguration Message
Add two SCells in the sCellToAddModList_r10 IE in the same RRC Connection Reconfiguration message and the n is 2, and the detail SCell information can be shown
in the below figures.
Figure 6-46 Add Two SCells at the Same Time
Figure 6-47 The First SCell Information
Figure 6-48The Second SCell Information
The activation/deactivation MAC CE can be shown in the UE log 0XB063 LTE MAC DL Transport Block. The last two bits 06 changed to binary is 0000 0110, which
indicated the SCells with SCellIndex1 and 2 are activated.
Figure 6-49 Two SCells are Activated
The MAC scheduling information can be shown in the UE log 0xB173 LTE PDSCH Stat Indication.
1. After the first SCell is activated, the data on PDSCH can be shown in the figure below. There is data transmitted on the PCell and SCell with SCellIndex1.
Figure 6-50 The Data Transmitted on PDSCH after the First SCell is Activated
2. After the second SCell is activated, the data on PDSCH can be shown in the figure below. There is data transmitted on the PCell and SCell with SCellIndex1/2.
Figure 6-51 The Data Transmitted on PDSCH after the Second SCell is Activated
After two SCells are activated, the downlink throughput can be shown in the figure below. The downlink peak throughput can be reached to 450Mbps in the case of
20MHz+20MHz+20MHz carriers aggregation.
Figure 6-52 Downlink Peak Throughput after Two SCells Activation
6.10.1 Topology
The test network for FDD+TDD carrier aggregation is shown in the figure below.
Figure 6-53 Test Network for FDD+TDD Carrier Aggregation
The test devices for FDD+TDD carrier aggregation are shown in the table below.
Table 6-13 Test Devices for FDD+TDD Carrier Aggregation
NO Test Devices Notes

1 eNodeB Two(One eNodeB is FDD mode,
and the other is TDD Mode);
Or One eNodeB, which establishes
a FDD cell and TDD cell.
2 UE One
3 MME One
4 PDN server One
The test specification of Carrier Aggregation(DL 2CC, FDD+TDD) is shown in the table below.
Table 6-14 Carrier Aggregation(DL 2CC, FDD+TDD)
Test item Carrier Aggregation(DL 2CC, FDD+TDD)
Verify that the LTE system supported two downlink carrier

Purpose
aggregations between FDDand TDD.
Prerequisites 1. FDD cell1 and TDD cell2 are established successfully. The
center frequencies of cell1 and cell2 are band3 and band 38.
The bandwidth of cell1 and cell2 are both 20MHz. Cell1 and
cell2 are configured as same coverage neighbor cells and a CA
group.Two UEs access to cell1 and cell respectively and the
downlink throughput can be reached in the same location.
2.The LTE EPC works normally;
4. The UE supports FDD+TDD CA function.
Global Switch
Switch for CA between
Open[1]
FDD and TDD N/A
LTE FDD
PUCH and PDCH
12
1b N/A
E-UTRAN TDD Cell
Uplink-Downlink Subframe N/A
2
Configuration
Special Subframe N/A
7
Configuration
Configured N/A
actual network

Place the UE in the center of
1
cell1 and cell2.
UE accesses to FDD cell1 successfully.
The cell1 is a PCell.
2 attachoperation, make sure eNodeB sends the RRC Connection
UE accesses in FDD cell1. Reconfiguration message carried
sCellToAddModList IE, adding the cell2
as a SCell.
SCells activate successfully.
265Mbps for FDD+TDD carriers
3 aggregated with bandwidth 40MHz in the
download service.
case of no interference.
eNodeB sides.
4 Stop service, and detach UE. UE detaches successfully
The TDD cell can be added as a SCell for a UE in FDD and TDD
carrier aggregation.
Expected
result The downlink peak throughput is 265Mbps for FDD+TDD
carriers aggregated with bandwidth 40MHz in the case of no
interference.
The downlink peak throughput is 265Mbps for FDD+TDD
Criteria carriers aggregated with bandwidth 40MHz in the case of no
interference.
6.10.3 Test Result
Test this case by UE M8994. Check whether the UE supports FDD+TDD CA in the UE CapabilityInformation message (log 0XB0C0 LTE RRC OTA Packet), which is
shown in the figure below.
Figure 6-54 UE Supports UL/DL CA in band3 and DL CA in band38
eNodeB sends the RRC Connection Reconfiguration message (log 0XB0C0 LTE RRC OTA Packet) carried sCellToAddModList IE, adding the TDD cell2 as a SCell.
See the figure below.
Figure 6-55 eNodeB Sends the RRC Connection Reconfiguration Message to Add TDD Cell2 as a SCell
Start downlink best-effort FTP service. The SCell is activated after the SCell activation threshold is reached. UE received the activation MAC CE (log 0xB063 LTE
MAC DL Transport Block) is shown in the figure below. The last bits 02 indicate the SCell with sCellIndex 1 is activated.
Figure 6-56 The SCell is Activated by Received the Activation MAC CE
There is data transmitted on the PDSCH (log 0xB173 LTE PDSCH Stat Indication) of PCell and SCell with SCellIndex1. See the figure below.
Figure 6-57 There Is Data Transmitted on the PCell and SCell with SCellIndex1
The downlink peak throughput is 265Mbps for FDD+TDD carriers aggregated with bandwidth 40MHz in the case of no interference. See the figure below.
Figure 6-58 The Downlink Peak Throughput is 265Mbps for FDD+TDD Carriers Aggregated with Bandwidth 40MHz
6.11 Carrier Aggregation (UL CA)
6.11.1 Topology
The test specification of UL two carriers aggregation is shown in the table below.
Table 6-15 Carrier Aggregation (UL CA)
Test item Carrier Aggregation (UL CA)
Purpose Verify that the LTE system supported UL two carriers aggregation.
Prerequisites 1.Cell1 and cell2 are established successfully. The center

frequencies of cell1 and cell2 are band1 and band3. The
bandwidth of cell1 and cell2 is 20MHz. Cell1 and cell2 are
configured as same coverage neighbor cells and a UL and DL
CA group. Two UEs access to cell1 and cell respectively and the
UL peak throughput can be reached in the same location.
2. The eNodeB enabled CA function.
5. The UE supports UL CA function.
Global Switch
Open[1] N/A

CA
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

1
cell1 and cell2.
UE accesses to FDD cell1 successfully.
Power on UE and initiate eNodeB sends the RRC Connection
2
attachoperation. Reconfiguration message carried
as a SCell.
The uplink throughput can reach to
Start best-effort FTP upload
service.
interference.
eNodeB sides.
The uplink throughput can reach to 150Mbps for three carriers
Expected
aggregated with bandwidth 20MHz in the case of no
result
interference.
The uplink throughput can reach to 150Mbps for three carriers
Criteria aggregated with bandwidth 20MHz in the case of no
interference.
6.11.3 Test Result
Test this case by Qualcomm UE M8996. After UE accesses to the serving cell, the UL CA capabilityinformation can be shown in the UE CapabilityInformation
message (log 0XB0C0 LTE RRC OTA Packet), which is shown in the figure below.
Figure 6-59 Check the UE whether Supports UL CA
eNodeB sends the RRC Connection Reconfiguration message (log 0XB0C0 LTE RRC OTA Packet) which carried sCellToAddModList IE, adding the cell2 as a SCell.
See the figure below.
Figure 6-60 Adding SCell Successfully
UE supports 64QAM. The uplink peak throughput is 149Mbps for two carriers aggregated with bandwidth 40MHz in the case of no interference. See the figure below.
Figure 6-61 The Uplink Peak Throughput is 149Mbps for Two Carriers Aggregated with Bandwidth 40MHz
6.12 Flexible SCell Configuration of Multi-Carriers
6.12.1 SCC Selection Based on Frequency Priority
6.12.1.1 Topology
6.12.1.2 Test Specification
For the flexible SCell configuration of multi-carriers test specification, refer to the table below.
Table 6-16 Flexible SCell Configuration of Multi-Carriers Function Test Specification
Test item Flexible SCell Configuration of Multi-Carriers Function Test
Verify that the LTE system supports flexible SCell configuration of multi-
Purpose carriers function.
Prerequisites 1. Cell1, cell2 and cell3 belonged to the same eNodeB are
established successfully. The carrier frequency of Cell 1, Cell2
and cell3 belong to Band 3. The bandwidth of cells is 20MHz.
Cell1, cell2 and cell3 are configured as neighbor cells. Cell1 and
cell2 are configured as a CA group. Cell1 and cell3 are
configured as a CA group.
4. The UE supports two CA function.
5.The performance of computer for FTP server and UEs satisfies
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Carrier Aggregation Config
The Switch of Scell Based
Open[1]
on Frequency Priority N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Inter-Frequency Number 2 N/A
Item0 ：
- Band Indication for
DL Frequency:3
- Inter-
Frequency:same with
cell2;
- Scell Frequency
Inter-Frequency Priority:255;
Measurement
Configuration Item1 ：
DL Frequency:3
- Inter-
Frequency:same with
cell2;
- Scell Frequency
Priority:100; N/A
Configured according N/A
Other Parameters
to the actual network

1
cell1.
Power on UE and initiate UE accesses cell1 successfully.
2 attach operation. Make sure
UE accesses to the cell1. The primary cell is cell1.
Because the cell2’s Scell Frequency

Priority is higher than cell3, so the cell2
is added as SCell for UE.
Move UE to satisfy the SCell
3 eNodeB sends the RRC Connection
adding conditions.
Reconfiguration message, carried
as a SCell.
Start downlink FTP service The SCC is activated.
4 on UE and check whether the
SCC is activated. The downlink throughput is normal.
Stop downlink FTP service

and start Ping service. Check
5 The SCC is deactivated.
whether the SCC is
deactivated.
Stop service and release UE.
6 UE is detached successfully.
Record the UE side log.
Expected Flexible SCell configuration of multi-carriers is supported by LTE
result system.
Criteria SCell can be added and activated successfully in multi-carries.
6.12.1.3 Test Result
1. After UE accesses the cell, the RRC Connection Reconfiguration message carries the SCell’s frequency information according to the frequency priority, as shown
in the figure below.
Figure 6-62 RRC Connection Reconfiguration Message Carries the SCell’s Frequency Information
2. UE measures the cell quality with higher priority frequency and sends the Measurement Report message to eNodeB as shown in the figure below.
Figure 6-63 UE Measures the Cell with Higher Priority Frequency
3. Because the measurement result is satisfied the SCell adding condition, eNodeB sends the RRC Connection Reconfiguration message to add the cell as SCell as
shown in the figure below.
6.12.2 SCC Selection Based on Cell Load
6.12.2.1 Topology
6.12.2.2 Test Specification
For SCC selection based on cell load function test specification, refer to the table below.
Table 6-17 SCC Selection Based on Cell Load
Test item SCC Selection Based on Cell Load
Verify that the function SCC selection based on cell load works
Purpose
normally.
Prerequisites 1. LTE system works normally.

2. Cell1, cell2 and cell3 that belong to the different eNodeBs are
established successfully. The frequency band of their cells is
band3. The channel spacing among cells is 20MHz. All the
bandwidth of cells is 20MHz. All the cells are configured as
neighbor cells. Cell1 and cell2 are configured as CA group. Cell1
and cell3 are configured as CA group.
3. E is supported the intra-band CA function.
uplink AMBR of UE is larger than 100Mbps.
Carrier Aggregation Config
Open[1]
on DL PRB N/A
Open[1]
on UpLink PRB N/A
Open[1]
on Frequency Priority N/A
PRB Ratio Threshold of
100
Scell Configuration %
PRB Ratio Threshold of
PCell for Getting Load 20
Information %
Load Type Indicator PRB number N/A
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]

Item0 ：
DL Frequency:3
- Inter-
Frequency:same with
cell2;
Inter-Frequency - Scell Frequency
Measurement Priority:255;
Configuration Item1 ：
DL Frequency:3
- Inter-Frequency:
same with cell2;
- Scell Frequency
Priority:255; N/A
LTE FDD
PUCH and PDCH
The RB Number of
0
PUCCH Format 3 N/A
Number of PUCCH Format N/A
12
1b
Other Parameters
Ste Expected step result

Place UE1 and UE2 in the
1
center ofcell1.
Power on UE1 and initiate UE1 accesses cell1 successfully and
2
attach operation. adds cell2 as SCell.
Start downlink full-buffer FTP
service on UE1. Make sure
the cell1 load to satisfy the
3 “PRB Ratio Threshold of
The SCC is activated successfully.
PCell for Getting Load
Information” and SCC of UE1
activating.
UE2 accesses cell1 successfully.
The cell1 is the primary cell.
Because of the cell2 load is higher than
Power on UE2 and initiate cell3, the cell3 is added as SCell for
4 UE2.
attach operation.
eNodeB sends the RRC Connection
Reconfiguration message to UE2,
carried sCellToAddModList IE, adding
the cell2 as a SCell.
Start full-buffer downlink FTP
5 service on UE2 and check
The SCC is activated successfully.
whether the SCC is activated.
Stop service and detach UEs.
6 UEs are detached successfully.
Record the test logs.
Expected
The eNodeB can add SCell for UE based on the cell’s load.
result
Criteria The eNodeB can add SCell for UE based on the cell’s load.
6.12.2.3 Test Result
1. UE1 accesses to the serving cell 182 and adds the cell 183 as SCell as shown in the figure below.
Figure 6-65 eNodeB Adds Cell 183 as SCell for UE1
2. Start full-buffer downlink FTP service for UE1 and the getting load information threshold is satisfied, as shown in the figure below. The downlink throughput is the
peak throughput in the case of two carriers aggregation with 20MHz+20MHz bandwidth.
Figure 6-66 The Downlink Throughput of UE1 Is Normal
3. After UE2 accessed to cell 182, because of the load of cell 183 is higher than cell 184, so eNodeB adds the cell 184 as SCell for UE2 as shown in the figure
below.
Figure 6-67 eNodeB Adds the Cell 184 as SCell for UE2
6.13 Cloud CA with Ideal Backhaul (Centralized)
6.13.1 Topology
The test network for inter-eNodeB carrier aggregation is shown in the figure below.
Figure 6-68 Test Network for Inter-eNodeB Carrier Aggregation
Test devices for inter-eNodeB carrier aggregation are shown in the table below.
Table 6-18 Test Devices for Inter-eNodeB Carriers Aggregation
SN Device Remarks
1 eNodeB Two
2 UE One
3 MME One
4 PDN server One
The test specification of cloud centralized CA with ideal backhaul is shown in the table below.
Table 6-19 Cloud Centralized CA with Ideal Backhaul
Test item Cloud Centralized CA with Ideal backhaul
Verify that aggregated carrier could be configured in different BBU

Purpose under centralized deployed.
Prerequisites
1. Cell1 belonged to eNodeB1 and cell2 belonged to eNodeB2

are established successfully. The bandwidth of cell1 and cell2
are 10MHz. Cell1 and cell2 are configured as neighbor cells and
a CA group. The frequency band of cell1 is band1, and the
frequency band of cell2 is band 7. Two UEs access to cell1 and
cell2 respectively and the downlink peak throughput can be
reached in the same location.
2.eNodeB1 and eNodeB2 are connected by optical fiber on CR0.
The delay of inter-eNodeB link is less than 0.2ms.
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Clock Device
Clock reference source
GNSS clock category
category N/A
Inner GNSS
type N/A
Clock Device Set
Clock synchronization Phase
mode synchronization N/A
Device Group
Board standard LTE FDD N/A
LTE-FDD
Board function mode
CloudRadio N/A
Physical board type FS5C N/A
X2+ Device
Port Working Speed 10Gbps N/A
X2+ IP Configuration
Configured according
IP Address
to the actual network N/A
Network Mask
Gateway IP
Used X2+ Channel
Co-eNodeB X2+ Port IP Link Table
The peer eNodeB’s
Cooperating eNodeB ID
ID N/A
Same with the peer
eNodeB’sIP
X2+ Port IP Address
configuration of X2+
IP Configuration N/A
IP Link Transmission Delay 0.2ms Delay N/A
Used IP Layer Configured according
Configuration to the actual network N/A
Used Bandwidth Resource
Other Parameters

1
cell1 and cell2.
UE accesses to the cell1 successfully.

Power on UE and initiate eNodeB sends the RRC Connection
2
attach operation Reconfiguration message, carried
as a SCell.
3 Start best-effort FTP SCells activate successfully.
download service. The downlink throughput can reach to
150Mbps for two carriers aggregated
with bandwidth 20MHz in the case of no
interference.
eNodeB sides.

Expected Aggregated carrier could be configured in different BBU under
result centralized deployed.
When the carrier aggregation is configured in different BBU
Criteria under centralized deployed, the SCell is added and activated
successfully.
6.13.3 Test Result
The SCell adding and activation signaling is same with the test scenario of intra-eNodeB carrier aggregation.
PCI394 is a PCell and PCI422 is a SCell. The downlink throughput is shown in the figure below.
Figure 6-69 The Downlink Throughput after SCell activation
6.14 RRC User Based CA Enable
6.14.1 Topology
The test specification of RRC user based CA enable function is shown in the table below.
Table 6-20 RRC User Based CA Enable
Test item RRC user based CA enable
Verify that if the RRC user in a cell reaches a certain threshold, the new
Purpose access CA-UE would not be added the cell as a SCell.
Cell2 are configured to neighbor cells and a group of CA
cell.
7. The UE1 and UE2 support CA function.
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Admission Control
Switch of CA User Restrict Open[1] N/A
Threshold of Forbid Cell1:80
Configured As Scell Cell2: 10 %
Threshold of RRC Cell1:100 N/A
Connection User Number
Cell2:9
Configured N/A
actual network

UE1 accesses to cell1 successfully.
Place UE1 in the edge of eNodeB sends the RRC Connection
cell1. Initiate attach operation Reconfiguration message, carried
1
and make sure UE1 sCellToAddModList IE, adding the cell2
accesses to cell1. as a SCell.
The cell1 is a PCell and cell2 is a SCell.
Place UE2 in the edge of
cell1. Initiate attach operation Because of the number of UEs in cell2 is
2 exceeding the “Threshold of forbid
and make sure UE2
accesses to cell1. Configured as SCell”, the UE2 which add
this cell2 as SCell will be forbidden.
The cell2 is added as a SCell for UE1.
Expected The cell2 is forbidden to add as a SCell for UE2 because of the
result number of UEs in cell2 is reached to the “Threshold of forbid
Configured as SCell”.
If the number of UEs in one cell exceeds the “Threshold of forbid
Criteria Configured as SCell”, the new UE which add this cell as SCell
will be forbidden.
6.14.3 Test Result
After UE1 accessed to the cell1, the eNodeB sends the RRC Connection Reconfiguration message carried adding SCell A4 event measurement configuration to UE1.
When the channel quality is reached to the A4 event threshold, the UE1 sends the MeasurementReport message to eNodeB. Then eNodeB sends the RRC
Connection Reconfiguration message to UE1 to add the cell2 (PCI222) as a SCell.
Figure 6-72 eNodeB sends the RRC Connection Reconfiguration messageto UE1 to add the cell2 (PCI222) as a SCell
After UE2 accessed to cell1, the eNodeB sends the RRCConnectionReconfiguration message carried adding SCell A4 measurement event to UE2. When the channel
quality is reached to the A4 event threshold, the UE2 sends the MeasurementReport message to eNodeB. Because the number of UEs in cell2 is exceeding
to“Threshold of forbid Configured as SCell”, the eNodeB does not send RRCConnectionReconfiguration message to add cell2 as a SCell for UE2.
Figure 6-73 The eNodeB sends the RRCConnectionReconfiguration message carried adding SCell A4 measurement event to UE2
Figure 6-74 UE2 Sends the MeasurementReport Message of A4 and eNodeB does not Send the RRC Connection Reconfiguration message to UE2
6.15 RRC User Based CA Back Off
6.15.1 Topology
The test specification of RRC user based CA back off is shown in the table below.
Table 6-21 RRC User Based CA Back Off
Test item RRC UserBased CA Back Off
Verify that the RRC user in a cell reaches to a certain threshold, the
Purpose enabled CA-UE would be deleted the SCell.
Cell2 are configured to neighbor cells and a group of CA
cell.
7. The UE1 supports CA function and UE2 not supports CA
function.
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Switch of CA UE Backoff Open[1] N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Admission Control
Threshold of CA UE Back Cell1:90
Off Cell2: 10 %
Threshold of RRC Cell1:100
Connection User Number Cell2:15 N/A
Configured N/A
actual network

Place UE1 in the edge of The eNodeB sends the RRC Connection
cell1. Initiate attach operation Reconfiguration message, carried
1
and make sure UE1 sCellToAddModList IE, adding the cell2
accesses to cell1. as a SCell.
UE2 accesses to the cell2 successfully.
Place UE2 in the center of Because of the number of UEs in cell2 is
2 cell2 and initiate attach exceeding to the “Threshold of CA UE
operation. Back Off”, the eNodeB sends the RRC
Connection Reconfiguration message to
UE1 to delete the SCell.
After UE2 accessed to the cell2, the number of UEs in cell2
Expected reaches to the “Threshold of CA UE Back Off”, the eNodeB
result sends the RRC Connection Reconfiguration message to UE1 to
delete the SCell.
When the number of UEs in one cell exceeds to the “Threshold
Criteria of CA UE Back Off”, the eNodeB sends the RRC Connection
Reconfiguration message to a CA-UE to delete the SCell.
6.15.3 Test Result
After UE1 accessed to the cell1, the eNodeB sends the RRC Connection Reconfiguration message carried adding SCell A4 event measurement configuration to UE1.
When the channel quality is reached to the A4 event threshold, the UE1 sends the MeasurementReport message to eNodeB. Then eNodeB sends the RRC
Connection Reconfiguration message to UE1 to add the cell2 (PCI222) as a SCell.
Figure 6-77 UE1’s SCell is added successfully
After UE2 accessed to the cell2, the number of UEs in cell2 exceeds to the “Threshold of CA UE Back Off”, the eNodeB sends the RRC Connection Reconfiguration
message to UE1 to delete the SCell.
Figure 6-78 UE2 Accesses to Cell2 Successfully
Figure 6-79 The UE1’s SCell is deleted because of the number of UEs in cell2 reached to the “Threshold of CA UE Back Off”
6.16 Cloud CA with Non-Ideal Backhaul (Distributed)
6.16.1 Topology
For the cloud CA with non-ideal backhaul test specification, refer to the table below.
Table 6-22 Cloud Centralized CA with Non-Ideal Backhaul Function Test Specification
Test item Cloud Centralized CA with Ideal Backhaul test
Verify that aggregated carrier could be configured in different BBU

Purpose under distributed deployed.
Prerequisites 1. Cell1 belonged to eNodeB1 and cell2 belonged to eNodeB2

are established successfully. The bandwidth of cell1 and cell2
are 10MHz. Cell1 and cell2 are configured as neighbor cells and
a CA group. The frequency band of cell1 is band1, and the
frequency band of cell2 is band 7. Two UEs access to cell1 and
cell2 respectively and the downlink peak throughput can be
reached in the same location.
2.eNodeB1 and eNodeB2 are connected by optical fiber on CR0.
6. The transmission delay between eNodeB1 and eNodeB2 is
larger than 0.2ms, but less than 4ms.
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
LTE FDD
PUCH and PDCH
12
1b N/A
Clock Device
GNSS clock category
category N/A
Inner GNSS
type N/A
Clock Device Set
Clock synchronization Phase

mode synchronization N/A
Device Group
Board standard LTE FDD N/A
LTE-FDD
Board function mode
CloudRadio N/A
Physical board type FS5C N/A
X2+ Device
Port Working Speed 10Gbps N/A
X2+ IP Configuration
IP Address
Network Mask
Gateway IP
Used X2+ Channel
Co-eNodeB X2+ Port IP Link Table
The peer eNodeB’s
Cooperating eNodeB ID
ID N/A
Same with the peer
eNodeB’sIP
X2+ Port IP Address
configuration of X2+
IP Configuration N/A
IP Link Transmission Delay Adapt N/A
Used IP Layer Configured according
Configuration to the actual network N/A
Used Bandwidth Resource
Other Parameters

1
cell1 and cell2.
UE accesses cell1 successfully.
Power on UE and initiate Reconfiguration message, carried
2
attachoperation. sCellToAddModList IE, adding the cell2
as a SCell.
150Mbps for two carriers aggregated
Start best-effort FTP with bandwidth 20MHz in the case of no
3 interference.
download service.
eNodeB sides.

Trigger the transmission
delay between eNodeB1 and eNodeB sends the RRC Connection
5 eNodeB2 to be larger than Reconfiguration message, which not
4ms, repeat the test step including sCellToAddModList IE.
1~3.
If the inter-eNodeB carrier aggregation with non-ideal backhaul,
Expected
the SCell is added and deleted successfully. The SCC can be
result
activated and deactivated successfully.
If the inter-eNodeB carrier aggregation with non-ideal backhaul,
Criteria the SCell is added and deleted successfully. The SCC can be
activated and deactivated successfully.
6.16.3 Test Result
Check the transmission delay between eNodeB1 and eNodeB2. In the Diagnosis Test interface, click button, the Combination Test box is displayed, as shown in
the figure below. Select “X2+ Link Status Query(L)” and then click OK. Wait the diagnosis test result.
Figure 6-80 The Combination Test Interface
The transmission delay is 458ns as shown in the figure below. The non-ideal backhaul test scenario is hard to trigger in the lab test. The Scell adding and activate
signaling flows are same with the intra-eNodeB carrier aggregation.
Figure 6-81 The Test Result of Transmission Delay
6.17.1 Topology
Refer to Section 6.10.1Topology. Establish two FDD cells and one TDD cell, or one FDD cell and two TDD cells. Take two FDD cells and one TDD cell as an example.
For the DL three carriers aggregation between FDD and TDD test specification, refer to the table below.
Table 6-23 DL Three Carriers Aggregation between FDD and TDD Test Specification
Test item DL three carriers aggregation between FDD and TDD test
Verify that the LTE system supports three carries aggregation
Purpose
between FDD and TDD.
1. FDD cell1 and cell2 are established successfully. TDD cell3 is
established successfully. The center frequencies of cell1, cell2
and cell3 are band3, band 1 and band 41 respectively. The
bandwidth of cells is both 20MHz. Cell1, cell2 and cell3 are
configured as same coverage neighbor cells and a CA group.
Three UEs access to cell1, cell2 and cell3 respectively and the
4. The UE supports FDD+TDD CA function.
Global Switch
Open[1]
Prerequisites FDD and TDD N/A
Switch for 3CC CA
Open[1]
Between FDD and TDD N/A
LTE FDD
PUCH and PDCH
1
Format 3 N/A
E-UTRAN TDD Cell
2
Configuration
7
Configuration
Configured N/A
actual network

1
cell1, cell2 and cell3.
UE accesses to the serving cell1
successfully and the cell1 is a PCell.
2 Cell2 and cell3 are added as SCells in
attach operation.
the RRC Connection Reconfiguration
message.
download service.
interference.
eNodeB sides.
Expected Two SCell can be added successfully in the three carries
result aggregation between FDD and TDD.
The downlink peak throughput can reach to 410Mbps for three

carriers aggregated with bandwidth 60MHz in the case of no
interference.
The downlink peak throughput can reach to 410Mbps for three
Criteria carriers aggregated with bandwidth 60MHz in the case of no
interference.
6.17.3 Test Result
Check the UE whether supports three carriers aggregation between FDD and TDD function in the UE Capability Information message, as shown in the figure below.
Band3 can be a PCC. Band1 and Band 41 can be SCCs.
Figure 6-82 UE Supports Three Carriers Aggregation between FDD and TDD
After UE access successfully, the eNodeB sends the RRC Connection Reconfiguration message to UE to add the cell2 and cell3 as SCell as shown in the figure
below.
Start best-effort downlink data service to UE, the downlink peak throughput can reach to 410Mbps with bandwidth 60MHz in the case of two FDD cell and one TDD
cell aggregated as shown in the figure below.
Figure 6-85 The Downlink Peak Throughput with bandwidth 60MHz in the Case of Two FDD Cell and One TDD Cell Aggregation
6.18.1 Topology
For the monitoring based SCell addition test specification, refer to the table below.
Table 6-24 Monitoring Based SCell Addition Function Test Specification
Test item Monitoring Based SCell Addition test

Verify that LTE FDD system supports SCell addition based on
Purpose
monitoring.
established successfully and they work properly;Two UEs
are configured as same coverage neighbor cells and CA
cells.
2. The frequency band of Cell 1 belongs to Band 3, and the
frequency band of Cell 2 belongs to Band 28;
Prerequisites Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Switch of CA UE Monitor Open[1] N/A
LTE FDD
PUCH and PDCH
12
1b N/A
Configured N/A
actual network

1
cell1 and cell2.
Power on UE and initiate The RRC Connection Reconfiguration
2
attach operation. message is not including the SCell
addition information.
UE receives the RRC Connection
Reconfiguration message, adding the
cell2 as a SCell.
Start best effort downlink data
3 SCell is activated successfully. The
service on UE.
downlink throughput is normal.
eNodeB sides.
5 Configure the cell1 and cell2 UE accesses to cell1 successfully.
as neighboring neighbor cells, When the UE does not do data service,
and repeat step 1~3. the eNodeB do not add SCell for UE.
After UE do full-buffer data service,

Reconfiguration message, including the
event A4 measurement configuration for
addition SCell.
After the measurement threshold of A4 is
reached, the UE receives the RRC
Connection Reconfiguration message to
add the Cell2 as Scell. The downlink
throughput is normal.
eNodeB sides.
When UE does not do data service or the data service is less,
Expected the eNodeB does not add a SCell for UE.
result When the data service of UE needs a SCC to share, the eNodeB
add and activate a SCC for UE.
When UE does not do data service or the data service is less,
the eNodeB does not add a SCell for UE.
Criteria
When the data service of UE needs a SCC to share, the eNodeB
add and activate a SCC for UE.
6.18.3 Test Result
If the neighbor relation is same coverage, after UE accessed the cell and did not do data service, the eNodeB do not add a SCell for UE.
When the data service of UE needs a SCC to share, the eNodeB add and activate a SCC for UE, as shown in the figure below.
Figure 6-86 When UE Has Large Data Transferring, the SCell Based on Blind Addition Is Added Successfully
If the neighbor relation is neighboring, afterUE accessed the cell and did not dodata service, the eNodeB do not add a SCell for UE.
When UE has larger data transferring, the eNodeB sends the RRC Connection Reconfiguration message, including event A4 measurement configuration for addition
SCell. After the measurement A4 threshold is satisfied, the eNodeB sends RRC Connection Reconfiguration message to add a SCell for UE, as shown in the figure
below.
Figure 6-87 When UE Has Large Data Transferring, the SCell Based on Measurement Addition Is Added Successfully
6.19.1 Topology
For service based PCC dynamic selection function test specification, refer to the table below.
Table 6-25 Service Based PCC Dynamic Selection
Test item Service Based PCC Dynamic Selection

Verify that if the PCC frequency is not the highest priority
Purpose frequency of VOLTE service, the eNodeB will update the PCC
for CA-UE.
Prerequisites 1. LTE system works normally and it supports VOLTE function.

2. Cell1 and cell2 that belong to the same eNodeB are
established successfully. Cell1’s frequency band is band1 and
cell2 is band3. The bandwidth of cell1 and cell2 is 20MHz. Cell1
and cell2 are configured as same coverage neighbor cells. Cell1
and cell2 are configured as CA group.
3. UE supports carrier aggregation function between band1 and
band3.
uplink AMBR of UE is larger than 100Mbps.
Global Switch
Open[1]
CA N/A
Open[1]
Open[1]
Voice Admit Switch for HO
Open[1]
Based Service N/A
Handover Switch Base
General Strategy [1]
Service N/A
Item0 ：
-- Band Indication for
Inter-Frequency DL Frequency:3
Measurement - Inter-Frequency:
Configuration same with cell2;
- VOIP Ability of
Inter-Frequency:1. N/A
PerQCI Inter-Freq Measure
1
GrpID N/A
PerQCI Strategy
PerQCI Strategy GroupID 1 N/A
Label Number of Service
1
Class N/A
Strategy Priority 255 N/A
- Band Indicator :3
Expect Frequencies - Expect
Configuration for QCI Frequencies: same
with cell2; N/A
LTE FDD
PUCH and PDCH
0
Format 3 N/A
Number of PUCCH Format N/A
12
1b
Configured N/A
actual network

1
cell1 andcell2.
UEs access cell1 successfully.
The cell1 is primary cell and cell2 is
Power on UEs and initiate SCell.
2 attach operations. Make sure eNodeB sends the RRC Connection
UEs access cell1. Reconfiguration message to UE2,
carried sCellToAddModList IE, adding
the cell2 as a SCell.
Start full-buffer downlink FTP The downlink throughput is normal.
3 service on UEs and check
whether the SCC is activated. The SCC is activated.
The dedicated bearers QCI5 and QCI1

are established successfully.
Reconfiguration message, including the
handover measurement configuration
about event A5 based on service.
4 UE1 calls UE2.
message to eNodeB.
Reconfiguration message, indicating UE
to modify the primary cell to cell2 and
adding cell1 as SCell.
Expected The function service based PCC dynamic selection is supported
result by eNodeB.
The function service based PCC dynamic selection is supported
Criteria
by eNodeB.
6.19.3 Test Result
1. Configure the related parameters according to the Prerequisites.
2. After UEs access cell 182, the cell184 is added as SCell, as shown in the figure below.
Figure 6-88 eNodeB Adds Cell184 as SCell for UEs
3. Start full-buffer FTP service for UEs and the SCC is activated, as shown in the figure below.
Figure 6-89 SCC Is Activated Successfully
4. Trigger VoLTE service between UE1 and UE2, the dedicated bearers QCI5 and QCI1 are established successfully, as shown in the figure below.
5. eNodeB sends the RRC Connection Reconfiguration message, including the handover measurement configuration with event A5 based on service as shown in
the figure below.
Figure 6-92 eNodeB Sends the RRC Connection Reconfiguration Message, Including the Handover Measurement Configuration with Event A5 Based on Service
6. The eNodeB sends the RRC Connection Reconfiguration message to indicate UE to be handover to cell 184 as shown in the figure below.
Figure 6-93 eNodeB Sends the RRC Connection Reconfiguration Message to Indicate UE to Be Handover to Cell 184
7. After handover flows ended, the eNodeB sends the RRC Connection Reconfiguration message to add the cell182 as SCell for UE, as shown in the figure below.
Figure 6-94 eNodeB Sends the RRC Connection Reconfiguration Message to Add the Cell182 as SCell for UE after Handover Ended
6.20.1 Topology
Refer to Section 6.10.1Topology. Establish one FDD cell and four TDD cells.
For one FDD carrier and 4 TDD carriers aggregation function test specification, refer to the table below.
Test item Carrier Aggregation(DL 5CC, 1FDD+4TDD)
Verify that LTE system supports one FDD carrier and 4 TDD carriers
Purpose aggregation.
Prerequisites 1. LTE system works normally.

2. FDD cell1 and TDD cell2, cell3, cell4 and cell 5 are
established successfully. Cell1’s frequency band is band1, TDD
cell2 and cell3’s frequency band is band 41. TDD cell4 and
cell5’s frequency band is band 42. All the bandwidth of cells is
20MHz. Cell1, cell2, cell3, cell3, cell4 and cell5 are configured
as same coverage neighbor cells and CA group. Five UEs
access to cell1, cell2, cell3, cell4 and cell5 respectively and the
3. UE supports the carrier aggregation function for the
configured frequency band. The downlink AMBR of UE is larger
than 1Gbps, and the uplink AMBR of UE is larger than
100Mbps.
Global Switch
Open[1]
FDD and TDD N/A
Switch for 3CC CA
Open[1]
Switch for 4CC CA
Open[1]
between FDD and TDD N/A
Switch for 5CC CA
Open[1]
LTE FDD
PUCH and PDCH
1
Format 3 N/A
E-UTRAN TDD Cell
2
Configuration
7 N/A
Special Subframe
Configuration
Configured N/A
actual network

Place UE at the location
1
according Prerequisite 2.
UE accesses the cell1 successfully.
The cell1 is primary cell.
2 eNodeB sends the RRC Connection
attach operation.
Reconfiguration message to add cell2,
cell3, cell4 and cell5 as SCells.
3 All the SCCs are activated.
service on UE.
Record the test logs of eNodeB and UE.
Stop downlink service and
detach UE.
Expected
All the SCCs can be activated.
result
Criteria All the SCCs can be activated.
6.20.3 Test Result
There is no commercial UE supporting.
The SCC adding and activating procedure can refer the case of DL 3CC. eNodeB sends the RRC Connection Reconfiguration to add 4 SCells. eNodeB sends the
activation MAC CE to activate the 4SCCs. The last bits of MAC CE are 0000 1111, which indicated the SCells with SCellIndex1 to 4 are activated.
6.21.1 Topology
Refer to Section 6.10.1Topology. Establish one FDD cell and three TDD cells.
For one FDD carrier and 3 TDD carriers aggregation function test specification, refer to the table below.
Test item Carrier Aggregation(DL 4CC, 1FDD+3TDD)
Verify that LTE system supports one FDD carrier and three TDD
Purpose
carriers aggregation.
1. LTE system works normally.
2. FDD cell1 and TDD cell2, cell3, and cell4 are established
successfully. Cell1’s frequency band is band1, TDD cell2 and
cell3’s frequency band is band 41. TDD cell4 s frequency band
is band 42. All the bandwidth of cells is 20MHz. Cell1, cell2,
cell3, cell3 and cell4 are configured as same coverage neighbor
cells and CA group. Four UEs access to cell1, cell2, cell3 and
cell4 respectively and the downlink throughput can be reached in
the same location.
3. UE supports the carrier aggregation function for the
configured frequency band. The downlink AMBR of UE is larger
than 1Gbps, and the uplink AMBR of UE is larger than 100Mbps.
Global Switch
Open[1]
FDD and TDD N/A
Prerequisites
Switch for 3CC CA
Open[1]
Switch for 4CC CA
Open[1]
LTE FDD
PUCH and PDCH
1
Format 3 N/A
E-UTRAN TDD Cell
2
Configuration
7
Configuration
Configured N/A
actual network
1 Place UE at the location

according Prerequisite 2.
UE accesses the cell1 successfully.
The cell1 is primary cell.
2 The eNodeB sends the RRC Connection
attach operation.
Reconfiguration message to add cell2,
cell3 and cell4 as SCells.
3 All the SCCs are activated.
service on UE.
Record the test logs of eNodeB and UE.
Stop downlink service and
detach UE.
Expected
All the SCCs can be activated.
result
Criteria All the SCCs can be activated.
6.21.3 Test Result
There is no commercial UE supporting.
The SCC adding and activating procedure can refer the case of DL 3CC. eNodeB sends the RRC Connection Reconfiguration to add 3 SCells. The eNodeB sends the
activation MAC CE to activate the 3 SCCs. The last bits of MAC CE are 0000 0111, which indicated the SCells with SCellIndex1 to 3 are activated.
7 Impact on Network
1. Impact on Equipment Performance
None
2. Impact on Network KPIs
Advantages of this feature:
Enabling carrier aggregation can increase the peak throughout of UE supporting CA and reduce the inter-cell handover triggered by LB, if the number of CA UEs
reaches to some extent which enhanced inter-cell load balance. But this feature cannot improve the valid throughput of the cell and it has no impact on access
success rate, RRC establishment success rate and handover success rate.
Disadvantage of this feature:
Because CA UE is treated as an independent user in primary and SCC cells respectively, so the maximum number of users that can access the cell decreases.
But the maximum number of users and CA users in cell can be configured on EMS to achieve the relative balance.
8 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.
9 References
1. 3GPP TS, 36.101,"User Equipment (UE) radio transmission and reception"
2. 3GPP TS, 36.104,"Base Station (BS) radio transmission and reception"
3. 3GPP TS 36.300,"Overall description"
4. 3GPP TS 36.306,"User Equipment (UE) radio access capabilities"
5. 3GPP TS 36.321,"Medium Access Control (MAC) protocol specification"
6. 3GPP TS 36.331,"Radio Resource Control (RRC);Protocol specification"
10 Attachments
Table 10-1 (Table 5.6A.1-1: E-UTRA CA configurations and bandwidth combination sets defined for intra-band contiguous CA)
E-UTRA CA configuration / Bandwidth combination set

Uplink CA Component carriers in order of increasing carrier frequency Maximum
E-UTRA CA configurations Bandwidth
Channel bandwidths for Channel bandwidths Channel bandwidths aggregated
configuration combination set
(NOTE 3) carrier [MHz] for carrier [MHz] for carrier [MHz] bandwidth [MHz]
15 15
CA_1C CA_1C 40 0
20 20
5 20
10 15, 20
CA_2C 40 0
15 10, 15, 20
20 5, 10, 15, 20
5, 10, 15 20
CA_3C CA_3C 40 0
20 5, 10, 15, 20
CA_7B 15 5 20 0
CA_7C CA_7C 15 15
40 0
20 20
10 20 40 1
15 15, 20

Uplink CA Component carriers in order of increasing carrier frequency Maximum
E-UTRA CA configurations Bandwidth
Channel bandwidths for Channel bandwidths Channel bandwidths aggregated
configuration combination set
(NOTE 3) carrier [MHz] for carrier [MHz] for carrier [MHz] bandwidth [MHz]
20 10, 15, 20
15 10, 15
40 2
20 15, 20
CA_12B - 5 5, 10 15 0
10 10
CA_23B - 20 0
5 15
1.4, 3, 5 5
CA_27B - 1.4, 3 10 13 0
15 15
CA_38C CA_38C 40 0
20 20
5,10,15 20
CA_39C CA_39C 35 0
20 5, 10, 15
10 20
15 15 40 0
20 10, 20
CA_40C CA_40C
10, 15 20
15 15 40 1
20 10, 15, 20
10, 15, 20 20 20
CA_40D CA_40C 20 10, 15 20 60 0
20 20 10, 15
10 20
15 15, 20 40 0
20 10, 15, 20
5, 10 20
15 15, 20 40 1
CA_41C CA_41C 20 5, 10, 15, 20
10 15, 20
15 10, 15, 20 40 2
20 10, 15, 20
10 20
40 3
20 20
10 20 15
10 15, 20 20
15 20 10, 15
CA_41D CA_41C 60 0
15 10, 15, 20 20
20 15, 20 10
20 10, 15, 20 15, 20
5, 10, 15, 20 20
CA_42C CA_42C 40 0
20 5, 10, 15
5,10,15,20 20 20
CA_42D CA_42D 60 0
20 20 5,10,15
NOTE 1: The CA configuration refers to an operating band and a CA bandwidth class specified in Table 5.6A-1 (the indexing letter). Absence of a CA bandwidth class for an
operating band implies support of all classes.
NOTE 2: For the supported CC bandwidth combinations, the CC downlink and uplink bandwidths are equal.
NOTE 3: Uplink CA configurationsare the configurations supported by the present release of specifications.
Table 10-2 (Table 5.6A.1-2: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (two bands))

Uplink CA Maximum
E-UTRA CA configurations E-UTRA 1.4 3 5 10 15 20 aggregated Bandwidth
Configuration (NOTE 4) Bands MHz MHz MHz MHz MHz MHz bandwidth combination set
[MHz]
1 Yes Yes Yes Yes
CA_1A-3A CA_1A-3A 40 0
3 Yes Yes Yes Yes
1 Yes
20 0
5 Yes
CA_1A-5A CA_1A-5A
1 Yes Yes Yes Yes
30 1
5 Yes Yes
1 Yes Yes Yes Yes
CA_1A-7A CA_1A-7A 40 0
7 Yes Yes Yes
1 Yes Yes Yes Yes
30 0
8 Yes Yes
1 Yes Yes
CA_1A-8A CA_1A-8A 20 1
8 Yes Yes
1 Yes Yes Yes Yes
30 2
8 Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-11A - 30 0
11 Yes Yes
CA_1A-18A CA_1A-18A 1 Yes Yes Yes Yes 35 0

Uplink CA Maximum
[MHz]
18 Yes Yes Yes
1 Yes Yes
20 1
18 Yes Yes
1 Yes Yes Yes Yes
CA_1A-19A CA_1A-19A 35 0
19 Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-20A - 40 0
20 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-21A CA_1A-21A 35 0
21 Yes Yes Yes
1 Yes Yes Yes Yes
35 0
26 Yes Yes Yes
CA_1A-26A CA_1A-26A
1 Yes Yes
20 1
26 Yes Yes
1 Yes Yes Yes Yes
40 0
28 Yes Yes Yes Yes
CA_1A-28A CA_1A-28A
1 Yes Yes
20 1
28 Yes Yes
1 Yes Yes Yes Yes
CA_1A-40A - 40 0
40 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-41A - 40 0
41 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-41C - 60 0
41 See CA_41C Bandwidth Combination Set 1 in Table 5.6A.1-1
1 Yes Yes Yes Yes
CA_1A-42A - 40 0
42 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-42C - 60 0
2 Yes Yes Yes Yes Yes Yes
40 0
4 Yes Yes Yes Yes
2 Yes Yes
CA_2A-4A CA_2A-4A 20 1
4 Yes Yes
2 Yes Yes Yes Yes
40 2
4 Yes Yes Yes Yes
2 See CA_2A-2A Bandwidth Combination Set 0 in Table 5.6A.1-3
CA_2A-2A-4A - 60 0
4 Yes Yes Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-4A - 60 0
CA_2A-2A-4A-4A - 80 0
2 Yes Yes Yes Yes
30 0
5 Yes Yes
CA_2A-5A -
2 Yes Yes
20 1
5 Yes Yes
CA_2A-2A-5A - 50 0
5 Yes Yes
2 See CA_2C in Table 5.6A.1-1 Bandwidth combination set 0
CA_2C-5A - 50 0
5 Yes Yes
2 Yes Yes Yes Yes
30 0
12 Yes Yes
CA_2A-12A -
2 Yes Yes Yes Yes
30 1
12 Yes Yes Yes
CA_2A-2A-12A - 50 0
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-12B - 35 0
12 See CA_12B Bandwidth Combination Set 0 in Table 5.6A.1-1
CA_2C-12A - 50 0
12 Yes Yes
2 Yes Yes Yes Yes
30 0
13 Yes
CA_2A-13A CA_2A-13A
2 Yes Yes
20 1
13 Yes
CA_2A-2A-13A - 50 0
13 Yes
2 Yes Yes
CA_2A-17A - 20 0
17 Yes Yes
2 Yes Yes Yes Yes
CA_2A-28A - 40 0
28 Yes Yes Yes Yes
CA_2A-29A - 2 Yes Yes
20 0
29 Yes Yes Yes
2 Yes Yes 20 1

Uplink CA Maximum
[MHz]
29 Yes Yes
2 Yes Yes Yes Yes
30 2
29 Yes Yes
2 See CA_2C Bandwidth Combination Set 0 in table 5.6A.1-1
CA_2C-29A - 50 0
29 Yes Yes
2 Yes Yes Yes Yes
CA_2A-30A - 30 0
30 Yes Yes
CA_2C-30A - 50 0
30 Yes Yes
3 Yes Yes Yes
30 0
5 Yes Yes
3 Yes
20 1
5 Yes Yes
CA_3A-5A CA_3A-5A
3 Yes Yes Yes Yes
30 2
5 Yes Yes
3 Yes Yes Yes Yes
30 3
5 Yes Yes Yes
See CA_3C Bandwidth Combination Set 0 in Table 5.6A.1-1 in
3
CA_3C-5A - TS 36.101 50 0
5 Yes Yes
3 Yes Yes Yes Yes
40 0
7 Yes Yes Yes
CA_3A-7A CA_3A-7A
3 Yes Yes Yes Yes
40 1
7 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-7B - 40 0
7 See CA_7B bandwidth combination set 0 in table 5.6A.1-1
3 Yes Yes Yes Yes
60 0
7 See CA_7C Bandwidth combination set 1 in table 5.6A.1-1
CA_3A-7C -
3 Yes Yes Yes Yes
60 1
7 See CA_7C Bandwidth combination set 2 in table 5.6A.1-1
3 See CA_3C Bandwidth Combination Set 0 in table 5.6A.1-1
CA_3C-7A - 60 0
7 Yes Yes Yes Yes
3 Yes Yes Yes
30 0
8 Yes Yes
3 Yes
20 1
8 Yes Yes
CA_3A-8A CA_3A-8A
3 Yes Yes Yes Yes
30 2
8 Yes Yes Yes
3 Yes Yes Yes Yes
30 3
8 Yes Yes
3 See CA_3A-3A Bandwidth Combination Set 0 in table 5.6A.1-3 50
0
8 Yes Yes
CA_3A-3A-8A -
3 See CA_3A-3A Bandwidth Combination Set 1 in table 5.6A.1-3
40 1
8 Yes Yes
3 Yes Yes Yes Yes
CA_3A-19A CA_3A-19A 35 0
19 Yes Yes Yes
3 Yes Yes Yes Yes
30 0
20 Yes Yes
CA_3A-20A CA_3A-20A
3 Yes Yes Yes Yes
40 1
20 Yes Yes Yes Yes
3 Yes Yes Yes Yes
35 0
26 Yes Yes Yes
CA_3A-26A CA_3A-26A
3 Yes Yes
20 1
26 Yes Yes
3 Yes Yes Yes Yes
CA_3A-27A - 30 0
27 Yes Yes
3 Yes Yes Yes Yes
CA_3A-28A - 40 0
28 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-31A - 25 0
31 Yes Yes
3 Yes Yes Yes Yes
CA_3A-38A - 40 0
38 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-40A - 40 0
40 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-40C - 60 0
3 Yes Yes Yes Yes
CA_3A-42A - 40 0
42 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-42C - 60 0
42 See Table 5.6A.1-1

Uplink CA Maximum
[MHz]
4 Yes Yes
20 0
5 Yes Yes
CA_4A-5A -
4 Yes Yes Yes Yes
30 1
5 Yes Yes
4 See CA_4A-4A Bandwidth Combination Set 0 in table 5.6A.1-1
CA_4A-4A-5A - 50 0
5 Yes Yes
4 Yes Yes
CA_4A-7A CA_4A-7A 30 0
7 Yes Yes Yes Yes
4 Yes Yes
CA_4A-4A-7A - 4 Yes Yes 40 0
7 Yes Yes Yes Yes
4 Yes Yes Yes Yes
20 0
12 Yes Yes
4 Yes Yes Yes Yes Yes Yes
30 1
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-12A CA_4A-12A 30 2
12 Yes Yes Yes
4 Yes Yes
20 3
12 Yes Yes
4 Yes Yes Yes Yes
30 4
12 Yes Yes
CA_4A-4A-12A - 50 0
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-12B - 35 0
12 See CA_12B Bandwidth Combination Set 0 in Table 5.6A.1-1
4 Yes Yes Yes Yes
30 0
13 Yes
CA_4A-13A CA_4A-13A
4 Yes Yes
20 1
13 Yes
CA_4A-4A-13A - 50 0
13 Yes
4 Yes Yes
CA_4A-17A CA_4A-17A 20 0
17 Yes Yes
4 Yes Yes Yes Yes
CA_4A-27A - 30 0
27 Yes Yes Yes
4 Yes Yes Yes Yes
CA_4A-28A - 40 0
28 Yes Yes Yes Yes
4 Yes Yes
20 0
29 Yes Yes Yes
4 Yes Yes
CA_4A-29A - 20 1
29 Yes Yes
4 Yes Yes Yes Yes
30 2
29 Yes Yes
4 Yes Yes Yes Yes
CA_4A-30A - 30 0
30 Yes Yes
5 Yes Yes Yes Yes
30 0
7 Yes Yes Yes
CA_5A-7A CA_5A-7A
5 Yes Yes
30 1
7 Yes Yes Yes
5 Yes Yes
CA_5A-12A CA_5A-12A 20 0
12 Yes Yes
5 Yes Yes
CA_5A-13A - 20 0
13 Yes
5 Yes Yes
CA_5A-17A - 20 0
17 Yes Yes
5 Yes Yes
CA_5A-25A - 30 0
25 Yes Yes Yes Yes
5 Yes Yes
CA_5A-29A - 20 0
29 Yes Yes
5 Yes Yes
CA_5A-30A - 20 0
30 Yes Yes
5 Yes Yes
30 0
40 Yes Yes Yes Yes
CA_5A-40A -
5 Yes Yes Yes
30 1
40 Yes Yes Yes Yes
7 Yes Yes Yes
30 0
8 Yes Yes Yes
CA_7A-8A -
7 Yes Yes Yes
30 1
8 Yes Yes
CA_7A-12A - 7 Yes Yes Yes Yes 30 0

Uplink CA Maximum
[MHz]
12 Yes Yes
7 Yes Yes Yes
30 0
20 Yes Yes
CA_7A-20A CA_7A-20A
7 Yes Yes Yes
40 1
20 Yes Yes Yes Yes
7 Yes Yes Yes
CA_7A-22A - 40 0
22 Yes Yes Yes Yes
7 Yes Yes Yes Yes
35 0
28 Yes Yes Yes
CA_7A-28A CA_7A-28A
7 Yes Yes Yes Yes
40 1
28 Yes Yes Yes Yes
7 See CA_7B bandwidth combination set 0 in table 5.6A.1-1
CA_7B-28A - 40 0
28 Yes Yes Yes Yes
7 See CA_7C bandwidth combination set 2 in table 5.6A.1-1
CA_7C-28A - 60 0
28 Yes Yes Yes Yes
8 Yes Yes
CA_8A-11A - 20 0
11 Yes Yes
8 Yes Yes
20 0
20 Yes Yes
CA_8A-20A -
8 Yes Yes Yes
20 1
20 Yes Yes
8 Yes Yes
CA_8A-40A - 30 0
40 Yes Yes Yes Yes
8 Yes Yes Yes Yes
CA_8A-41A 30 0
41 Yes Yes
8 Yes Yes Yes Yes
CA_8A-41C - 50 0
41 See CA_41C bandwidth combination set 2 in table 5.6A.1-1
11 Yes Yes
CA_11A-18A - 25 0
18 Yes Yes Yes
12 Yes Yes
CA_12A-25A - 30 0
25 Yes Yes Yes Yes
12 Yes Yes
CA_12A-30A - 20 0
30 Yes Yes
18 Yes Yes Yes
CA_18A-28A CA_18A-28A 25 0
28 Yes Yes
19 Yes Yes Yes
CA_19A-21A CA_19A-21A 30 0
21 Yes Yes Yes
19 Yes Yes Yes
CA_19A-42A - 35 0
42 Yes Yes Yes Yes
19 Yes Yes Yes
CA_19A-42C - 55 0
20 Yes Yes Yes Yes
CA_20A-31A - 25 0
31 Yes Yes
20 Yes Yes
CA_20A-32A - 30 0
32 Yes Yes Yes Yes
21 Yes Yes Yes
CA_21A-42A - 35 0
42 Yes Yes Yes Yes
21 Yes Yes Yes
CA_21A-42C - 55 0
23 Yes Yes Yes Yes
30 0
29 Yes Yes Yes
CA_23A-29A -
23 Yes Yes
20 1
29 Yes Yes Yes
25 Yes Yes Yes Yes Yes
35 0
26 Yes Yes Yes Yes Yes
25 Yes Yes Yes
CA_25A-26A - 20 1
26 Yes Yes Yes
25 Yes Yes
20 2
26 Yes Yes
25 Yes Yes Yes Yes
CA_25A-41A - 40 0
41 Yes Yes Yes Yes
25 Yes Yes Yes Yes
CA_25A-41C - 60 0
25 Yes Yes Yes Yes
CA_25A-41D - 80 0
41 See CA_41D Bandwidth Combination Set 0 in Table 5.6A.1-1
26 Yes Yes Yes
CA_26A-41A - 35 0
41 Yes Yes Yes Yes
26 Yes Yes Yes
CA_26A-41C - 55 0

Uplink CA Maximum
[MHz]
29 Yes Yes
CA_29A-30A - 20 0
30 Yes Yes
38 Yes Yes
CA_38A-40A - 40 0
40 Yes Yes
38 Yes Yes
CA_38A-40A-40A - 60 0
40 See CA_40A-40A in Table 5.6A.1-3
38 Yes Yes
CA_38A-40C - 60 0
39 Yes Yes Yes
CA_39A-41A CA_39A-41A 40 0
41 Yes
39 Yes Yes Yes
CA_39A-41C - 41 Yes 60 0
41 Yes
CA_39C-41A - 55 0
41 Yes
41 Yes Yes Yes
CA_41A-42A - 40 0
42 Yes Yes Yes
41 Yes Yes Yes
CA_41A-42C - 42 60 0
See CA_42C Bandwidth Combination Set 0 in Table 5.6A.1-1
NOTE 1: The CA Configuration refers to a combination of an operating band and a CA bandwidth class specified in Table 5.6A-1 (the indexing letter). Absence of a CA
bandwidth class for an operating band implies support of all classes.
NOTE 2: For each band combination, all combinations of indicated bandwidths belong to the set.
NOTE 4: Uplink CA configurations are the configurations supported by the present release of specifications.
Table 10-3 (Table 5.6A.1-2a: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (three bands)

Maximum
Uplink CA aggregated
E-UTRA CA E-UTRA 1.4 3 5 10 15 20 Bandwidth
configurations bandwidth
Configuration Bands MHz MHz MHz MHz MHz MHz combination set
(NOTE 5)
[MHz]
1 Yes Yes Yes Yes
3 Yes Yes Yes Yes 50 0
5 Yes Yes
CA_1A-3A-5A -
1 Yes Yes
5 Yes Yes
1 Yes Yes Yes Yes
8 Yes Yes Yes
1 Yes Yes
CA_1A-3A-8A - 3 Yes Yes Yes Yes 40 1
8 Yes Yes Yes
1 Yes Yes Yes
3 Yes Yes Yes 40 2
8 Yes Yes Yes
1 Yes Yes Yes Yes
19 Yes Yes Yes
1 Yes Yes Yes Yes
26 Yes Yes
1 Yes Yes Yes Yes
CA_1A-3A-20A (NOTE 4) - 3 Yes Yes Yes Yes 60 0
20 Yes Yes Yes Yes
1 Yes Yes Yes Yes
28 Yes Yes Yes Yes
1 Yes Yes Yes Yes
42 Yes Yes Yes Yes
1 Yes Yes
5 Yes Yes 40 0
7 Yes Yes Yes
CA_1A-5A-7A -
1 Yes Yes Yes Yes
5 Yes Yes 50 1
7 Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-7A-20A (NOTE 4) - 7 Yes Yes Yes 50 0
20 Yes Yes

Maximum
(NOTE 5)
[MHz]
1 Yes Yes Yes Yes
CA_1A-7A-28A - 7 Yes Yes Yes 55 0
28 Yes Yes Yes
1 Yes Yes Yes Yes
18 Yes Yes Yes 45 0
28 Yes Yes
CA_1A-18A-28A -
1 Yes Yes Yes Yes
18 Yes Yes 40 1
28 Yes Yes
1 Yes Yes Yes Yes
21 Yes Yes Yes
1 Yes Yes Yes Yes
42 Yes Yes Yes Yes
1 Yes Yes Yes Yes
42 Yes Yes Yes Yes
2 Yes Yes Yes Yes
5 Yes Yes
2 Yes Yes Yes Yes
12 Yes Yes
CA_2A-2A-4A-12A - 4 Yes Yes Yes Yes 70 0
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-4A-12A - 4 See CA_4A-4A Bandwidth Combination Set 0 in Table 5.6A.1-3 70 0
12 Yes Yes
2 Yes Yes Yes Yes
13 Yes
2 Yes Yes Yes Yes
29 Yes Yes
2 Yes Yes Yes Yes
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-12A - 5 Yes Yes 40 0
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-13A - 5 Yes Yes 40 0
13 Yes
2 Yes Yes Yes Yes
CA_2A-5A-29A - 5 Yes Yes 40 0
29 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-30A - 5 Yes Yes 40 0
30 Yes Yes
CA_2C-5A-30A - 5 Yes Yes 60 0
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-12A-30A - 12 Yes Yes 40 0
30 Yes Yes
CA_2C-12A-30A - 12 Yes Yes 60 0
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-29A-30A - 29 Yes Yes 40 0
30 Yes Yes
2 See CA_2C in Table 5.6A.1-1 Bandwidth Combination set 0
CA_2C-29A-30A - 29 Yes Yes 60 0
30 Yes Yes
CA_3A-7A-8A - 3 Yes Yes Yes
7 Yes Yes 40 0
8 Yes Yes

Maximum
(NOTE 5)
[MHz]
7 Yes Yes Yes
8 Yes Yes
3 Yes Yes Yes Yes
20 Yes Yes Yes Yes
3 Yes Yes Yes Yes
28 Yes Yes Yes Yes
3 Yes Yes Yes Yes
42 Yes Yes Yes Yes
4 Yes Yes Yes Yes
CA_4A-5A-12A - 5 Yes Yes 40 0
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-5A-13A - 5 Yes Yes 40 0
13 Yes
4 Yes Yes Yes Yes
CA_4A-5A-30A - 5 Yes Yes 40 0
30 Yes Yes
4 Yes Yes
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-12A-30A - 12 Yes Yes 40 0
30 Yes Yes
4 Yes Yes Yes Yes
CA_4A-29A-30A - 29 Yes Yes 40 0
30 Yes Yes
7 Yes Yes Yes
20 Yes Yes
19 Yes Yes Yes
CA_19A-21A-42A - 21 Yes Yes Yes 50 0
42 Yes Yes Yes Yes
NOTE 1: The CA Configuration refers to a combination of an operating band and a CA bandwidth class specified in Table 5.6A-1 (the indexing letter). Absence of a CA
bandwidth class for an operating band implies support of all classes.
NOTE 2: For each band combination, all combinations of indicated bandwidths belong to the set.
NOTE 4: A terminal which supports a DL CA configuration shall support all the lower order fallback DL CA combinations and it shall support at least one bandwidth combination
set for each of the constituent lower order DL combinations containing all the bandwidths specified within each specific combination set of the upper order DL combination.
Table 10-4 (Table 5.6A.1-3: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra-band CA (with two sub-blocks))

Component carriers in order of increasing carrier frequency
Maximum
E-UTRACA Uplink CA Channel Channel Channel Bandwidth
aggregated
configuration configurations (NOTE 1) bandwidths for bandwidths for bandwidths for combination set
bandwidth [MHz]
carrier [MHz] carrier [MHz] carrier [MHz]
CA_2A-2A - 5, 10, 15, 20 5, 10, 15, 20 40 0
5, 10, 15, 20 5, 10, 15, 20 40 0
CA_3A-3A -
5, 10, 15, 20 5, 10 30 1
CA_4A-4A CA_4A-4A 5, 10, 15, 20 5, 10, 15, 20 40 0
5 15
10 10, 15
CA_7A-7A - 40 0
15 15, 20
20 20
CA_23A-23A - 5 10 15 0
5, 10 5, 10 20 0
CA_25A-25A -
5, 10, 15, 20 5, 10, 15, 20 40 1
CA_40A-40A - 10, 20 10, 20 40 0
10, 15, 20 10, 15, 20 40 0
CA_41A-41A -
5, 10, 15, 20 5, 10, 15, 20 40 1
See CA_41C Bandwidth Combination Set 1
CA_41A-41C - 5, 10, 15, 20 60 0
inTable 5.6A.1-1
CA_41C-41A - 5, 10, 15, 20 60 0
inTable 5.6A.1-1
CA_42A-42A - 5, 10, 15, 20 5, 10, 15, 20 40 0
CA_42A-42C - 5, 10, 15, 20 60 0
inTable 5.6A.1-1

Component carriers in order of increasing carrier frequency
Maximum
E-UTRACA Uplink CA Channel Channel Channel Bandwidth
aggregated
configuration configurations (NOTE 1) bandwidths for bandwidths for bandwidths for combination set
bandwidth [MHz]
carrier [MHz] carrier [MHz] carrier [MHz]
CA_42C-42A - See CA_42C Bandwidth Combination Set 0 5, 10, 15, 20 60 0
inTable 5.6A.1-1

Zte - Ca

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Zte - Ca

Încărcat de

Drepturi de autor:

Formate disponibile

ZTE LTE FDD Carrier Aggregation Feature Guide Page 1 of 111

ZTE LTE FDD Carrier Aggregation Feature Guide

ZTE LTE FDD Carrier Aggregation Feature Guide

Luo Su, 2. Add Uplink Inter-eNodeB CA in

3. Update Downlink multi-carrier CA

4. Configuration and validation parts

3.9.2 PUCCH Configuration

5 Related Counters, KPI and Alarms

6.6.3 Test Result

Figure 2-1 Carrier aggregation scenarios

Figure 4-7 Neighbor Cell Management

Figure 6-11 A2 Event Sending

Figure 6-76 UE1 Sends the Measurement Report Message of A4

Table 1-1 Related Feature List

Table 6-20 RRC User Based CA Enable

1.1 Feature Attribute

1.2 Related Feature List and License Control

Table 1-1 Related Feature List

No Feature List No. Feature List Name License Control

1 ZLF34-00-013 Carrier Aggregation(Inter- Yes

2 ZLF34-00-015 Carrier Aggregation(Intra- Yes

3 ZLF34-00-016 Carrier Aggregation(UL CA) Yes

4 ZLF34-00-017 Carrier Aggregation(DL 3CC) Yes

5 ZLF34-00-027 Carrier Aggregation((DL 2CC, Yes

6 ZLF34-00-034 Cloud CA (centralized) Yes

7 ZLF34-00-035 Load and Service Monitor No

8 ZLF34-00-036 Flexible SCell configuration of No

9 ZLF34-00-049 Carrier Aggregation(DL 3CC, Yes

10 ZLF34-00-051 Cloud CA (distributed) Yes

11 ZLF34-00-055 Carrier Aggregation(DL 4CC Yes

12 ZLF34-00-056 PCC dynamic selection No

13 ZLF34-00-060 Carrier Aggregation(DL 4CC, Yes

No Feature List No. Feature List Name License Control

1.3 Correlation with Other Feature

Table 1-2 Correlation with Other Feature

Feature Feature Name Required Mutually Impacted

ZLF34-00- Carrier Aggregation None None

ZLF34-00- Carrier Aggregation None None

ZLF34-00- Carrier Aggregation ZLF34-00-013 None None

ZLF34-00- Cloud CA ZLF34-00-013/ None None

ZLF34-00- Load and Service ZLF34-00-013/ None None

ZLF34-00- Flexible SCell ZLF34-00-013/ None None

ZLF34-00- Carrier Aggregation ZLF34-00- None None

ZLF34-00- Cloud CA ZLF34-00- None None

ZLF34-00- Carrier Aggregation ZLF34-00-013 None None

ZLF34-00- PCC dynamic ZLF31-07- None None

1.3.1 ZLF34-00-016 Carrier Aggregation(UL CA)

ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)

Reason: According to the protocol, UL CA is based on DL CA.

1.3.2 ZLF34-00-017Carrier Aggregation(DL 3CC)

ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)

Reason: 3-carrier CA is based on 2-carrier CA (intra-band or inter-band CA depends on band combination)

1.3.3 ZLF34-00-034 Cloud CA (centralized)

ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)

ZLF34-00-017 Carrier Aggregation(DL 3CC)

ZLF34-00-027 Carrier Aggregation(DL 2CC, FDD+TDD)

ZLF34-00-049 Carrier Aggregation(DL 3CC, FDD+TDD)

ZLF32-05-001 GPS Synchronization

Reason: Cloud CA supports basic functions of CA and requires phase synchronization.

1.3.4 ZLF34-00-027Carrier Aggregation(DL 2CC, FDD+TDD)

ZLF34-00-013 Carrier Aggregation(Inter-Band, DL 2CC)

Reason: FDD+TDD CA is based on 2-carrier CA (inter-band).

1.3.5 ZLF34-00-036Flexible SCell Configuration of Multi-Carriers