Beruflich Dokumente
Kultur Dokumente
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 1/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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)
1.3.8 ZLF34-00-060Carrier Aggregation(DL 4CC, FDD+TDD)
1.3.9 ZLF34-00-062 Carrier Aggregation(DL 5CC, FDD+TDD)
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 FrequencyPriority
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
3.9.2 PUCCH Configuration
3.9.3 Activation/Deactivation
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 2/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 EngineeringGuide
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 BandwidthRequirements
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.4.1 Enabling the Feature
4.4.2 Data Synchronization
4.4.3 Disabling the Feature
4.5 Carrier Aggregation (DL 3CC)
4.5.1 Enabling the Feature
4.5.2 Data Synchronization
4.5.3 Disabling the Feature
4.6 Carrier Aggregation (UL 2CC)
4.6.1 Enabling the Feature
4.6.2 Data Synchronization
4.6.3 Disabling the Feature
4.7 Cloud CA (Centralized)
4.7.1 Enabling the Feature
4.7.2 Data Synchronization
4.7.3 Disabling the Feature
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 ConfiguringFlexible SCell Selection
4.8.8 ConfiguringUser-Based Admission
4.8.9 ConfiguringCA UE Monitor
4.8.10 Configuring CA UE Handover with SCell
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.2 Test Specification
6.2.3 Test Result
6.3 Contiguous Intra-Band Carrier Aggregation
6.3.1 Topology
6.3.2 Test Specification
6.3.3 Test Result
6.4 SCell Adding and Deleting Test
6.4.1 Topology
6.4.2 Test Specification
6.4.3 Test Result
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 3/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.5 SCell Modifying Test(A6 Event)
6.5.1 Topology
6.5.2 Test Specification
6.5.3 Test Result
6.6 SCell Activating and Deactivating
6.6.1 Topology
6.6.2 Test Specification
6.6.3 Test Result
6.7 Handover of CA
6.7.1 Topology
6.7.2 Test Specification
6.7.3 Test Result
6.8 CAPrimary Carrier Frequency Priority
6.8.1 Topology
6.8.2 Test Specification
6.8.3 Test Result
6.9 Carrier Aggregation(DL 3CC)
6.9.1 Topology
6.9.2 Test Specification
6.9.3 Test Result
6.10 Carrier Aggregation(DL 2CC, FDD+TDD)
6.10.1 Topology
6.10.2 Test Specification
6.10.3 Test Result
6.11 Carrier Aggregation (UL CA)
6.11.1 Topology
6.11.2 Test Specification
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.2 Test Specification
6.13.3 Test Result
6.14 RRC UserBased CA Enable
6.14.1 Topology
6.14.2 Test Specification
6.14.3 Test Result
6.15 RRC UserBased CA Back Off
6.15.1 Topology
6.15.2 Test Specification
6.15.3 Test Result
6.16 Cloud CA with Non-Ideal Backhaul (Distributed)
6.16.1 Topology
6.16.2 Test Specification
6.16.3 Test Result
6.17 Carrier Aggregation(DL 3CC, FDD+TDD)
6.17.1 Topology
6.17.2 Test Specification
6.17.3 Test Result
6.18 Monitoring Based SCell Addition
6.18.1 Topology
6.18.2 Test Specification
6.18.3 Test Result
6.19 Service Based PCC Dynamic Selection
6.19.1 Topology
6.19.2 Test Specification
6.19.3 Test Result
6.20 Carrier Aggregation(DL 5CC, 1FDD+4TDD)
6.20.1 Topology
6.20.2 Test Specification
6.20.3 Test Result
6.21 Carrier Aggregation(DL 4CC, 1FDD+3TDD)
6.21.1 Topology
6.21.2 Test Specification
6.21.3 Test Result
7 Impact on Network
8 Abbreviations
9 References
10 Attachments
FIGURES
TABLES
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 7/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Table 4‑2 Center Frequency Spacing of Intra-Band Contiguous CA with Different Bandwidths
Table 4‑3CA Configuration Parameters
Table 4‑4Active/De-active Parameters
Table 4‑5FDD + TDD CA Configuration Parameters
Table 4‑6Cloud 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 5‑1 Related Counters
Table 6‑1Required Devices for the Carrier Aggregation Function
Table 6‑2DL Inter-Band Two Carries Aggregation Function Test Specification
Table 6‑3DL Non-Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Table 6‑4DL Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
Table 6‑5CA SCell Adding and Deleting Function Test Specification
Table 6‑6CA SCell Modifying Function Test Specification
Table 6‑7SCell Activating and DeactivatingTest Specification
Table 6‑8Required Devices for the Carrier Aggregation Function
Table 6‑9Handover of CA Test
Table 6‑10CAPrimary Carrier Frequency Priority
Table 6‑11Carrier Aggregation(DL 3CC)
Table 6‑12 CA bandwidth classes and corresponding nominal guard bands
Table 6‑13Test Devices for FDD+TDD Carrier Aggregation
Table 6‑14Carrier Aggregation(DL 2CC, FDD+TDD)
Table 6‑15Carrier Aggregation (UL CA)
Table 6‑16Flexible SCell Configuration of Multi-Carriers Function Test Specification
Table 6‑17SCC Selection Based on Cell Load
Table 6‑18Test Devices for Inter-eNodeB Carriers Aggregation
Table 6‑19Cloud Centralized CA with Ideal Backhaul
Table 6‑20RRC User Based CA Enable
Table 6‑21RRC UserBased CA Back Off
Table 6‑22Cloud Centralized CA with Non-Ideal Backhaul Function Test Specification
Table 6‑23DL Three Carriers Aggregation between FDD and TDD Test Specification
Table 6‑24Monitoring Based SCell Addition Function Test Specification
Table 6‑25Service Based PCC Dynamic Selection
Table 6‑26Carrier Aggregation(DL 5CC, 1FDD+4TDD)
Table 6‑27Carrier Aggregation(DL 4CC, 1FDD+3TDD)
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.
FDD single-modeV3.5.10 corresponds to GUL multi-mode V4.17.10,and LTE technology description and operation requirements in the corresponding versions are the
same.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 8/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
√ √ - - - - - -
Note:
*-: Not involved
*√: involved
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 9/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Feature Feature Name Required Mutually Impacted
ID
Feature Exclusive Feature
Feature
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 multi-
015/ZLF34-00-
carriers 017/
ZLF34-00-049
Note: About the description and configuration of ZLF34-00-056PCC dynamic selection based on service see details in ZTE LTE FDD VoLTE Feature Guide.
Required Features:
ZLF34-00-013 Carrier Aggregation(Inter-Band, DL 2CC)
ZLF34-00-015 Carrier Aggregation(Intra-Band,DL 2CC)
Exclusive Features:
None
Impacted Features:
None
Exclusive Features:
None
Impacted Features:
None
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 10/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1.3.3 ZLF34-00-034 Cloud CA (centralized)
Required Features:
ZLF34-00-013 Carrier Aggregation(Inter-Band, DL 2CC)
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
Exclusive Features:
None
Impacted Features:
None
Exclusive Features:
None
Impacted Features:
None
Required Features:
ZLF34-00-013 Carrier Aggregation(Inter-Band, DL 2CC)
ZLF34-00-015 Carrier Aggregation(Intra-Band,DL 2CC)
ZLF34-00-017 Carrier Aggregation(DL 3CC)
Reason: Flexible SCell configuration of multi-carriers is based on basic functions of CA. Exclusive Features:
None
Impacted Features:
None
Reason: This feature is based on 3-carrier CA (DL) and FDD+TDD CA (DL 2CC). Exclusive Features:
None
Impacted Features:
None
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:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 11/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
None
Impacted Features:
None
Required Features:
ZLF34-00-013 Carrier Aggregation(Inter-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)
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:
ZLF34-00-013 Carrier Aggregation(Inter-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)
ZLF34-00-060 Carrier Aggregation(DL 4CC, FDD+TDD)
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.
l Make full use of resources. CA UEs can use idle RBs on two carriers at the same time to realize the maximum resource utilization.
l 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:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 12/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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:
For super cell scenario, Super CA, that is, CA of multiple SuperCell on different bands, is also supported. About the description and configuration of Super CA, see details
inZTE LTE FDD Super Cell Feature Guide.
3 Technical Description
l The PCell and SCell are defined only for the UE-level. In light of cell, there is no difference between PCell and SCell;
l 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.
l 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.
l During the CA UE accessing procedure, the SCell can be directly added based on neighbor relationEUtranRelation.shareCoverconfigured as same coverage or
containing through the EMSor added through the A4 measurement report
l The PCell of the CA UE can only be changed through the handover procedure, while the SCell can be changed through the A6measurement event.
l The PCell of the CA UE is always activated, while the SCell can be deactivated.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 13/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 14/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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:
If Carrier Aggregation(DL 5CC, FDD+TDD) is enabled, first enableSwitch 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 enableSwitch for CA between FDD
and TDD and Switch for 3CC CA between FDD and TDD.
Note:
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.
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:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 15/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
l 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.
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
In the non-ideal backhaul scenario, one cell each from two sites forms CA, and the minimum bandwidth for various delays is listed below:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 16/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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).
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.
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.
When Switch of CA User RestrictAC.caUserSwchis 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 totheThreshold 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 theproblem 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:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 17/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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);
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.
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.
Up to 5CC SCC selection is supported. SCC selection methods include basic SCC selection, frequency priority-based SCC selection, and load-based 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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 18/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.scellSelBaseFreqPriSwchis turned on).
SCC configuration: The SCC is added to the serving cell set through the RRCConnectionReconfiguration. 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 systemwill configure the
SCC to the UE.
Figure 3‑3Initial SCC Configuration when neighbor relationship is same coverage or containing
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 19/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
When the SCell is activated, the UE performs the following operations on the SCell:
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 20/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. Sends SRS;
2. Reports CQI/PMI/RI;
When the SCell is deactivated, the UE does not perform the following operations on the SCC:
1. Sends SRS;
2. Reports CQI/PMI/RI;
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.
a) The amount of the buffered service data is larger than the length threshold of the CA terminal SCC activated data buffer
(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.
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),.
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 scheduledboth 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:
l Fair scheduling (GlobleSwitchInformation.fairSchdSwch): the system calculates the scheduling priority using the total historical traffic of allCCs. 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.
l Differentiated scheduling: the system calculates the scheduling priority using the historical traffic perCC. 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 factorENBFunctionFDD.fairSchdFactorcan 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 21/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
- SCC addition/deletion/ modification is supported.
PUCCH format is Format3 (PhyChannel.pucch3RB), it also uses Format3 instead of Format 1b with channel selection whenmulti-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:
l 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.
l 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.
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:
Table 3‑7CSI Request field for PDCCH with uplink DCI format in UE specific search space
3.10 Uplink CA
The UE with ongoing NGBR service determines whether there is uplink congestion based on BSR scheduling.
Starting from the first BSR who exceeds thebuffer size threshold of activatingthe secondary carrier for ULCA UE ThrBufferSizeHCarrierAggregatin.scellActBuSizeThdUL.
When UL BSR Delay is bigger than SCell Active Data buffer delay threshold for ULCA UECarrierAggregatin.scellActBufDelayThdUL, it is considered congestion, and as a
condition of SCell Active. Otherwise, the uplink is regarded asnon-congested.
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 activationcondition: QCI2 is configured or the configured GBRexceeds the uplink SCellactivationGBR service
threshold(CarrierAggregatin.caSccActGbrThrUl);
b) NGBR service activation condition: Uplink services congest and AMBR is not satisfied.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 22/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 thresholdCarrierAggregatin.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 SCellactivationGBR service
threshold(CarrierAggregatin.caSccActGbrThrUl);
In the latest deactivation period, the number of uplink services congestion times isless 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 thresholdCarrierAggregatin.caSchdSizeDeActThrUL.
If there is no scheduling within theSCell deactivation timer, the timer is considered to be expired, deactivate the SCell.
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.caScellHOSwchneeds 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 23/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
With service deployment's diversity, operators impose layer requirement on different services. Especially for VoLTE service, operators expect VoLTE service to reside on
specifiedcarrier. 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 EngineeringGuide
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.
- 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”.
The table provides the TM3 FDD theoretical peak rate in the condition of 20M, 2*2, 2*4 and 64QAM.
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 satisfythe
conditions below:
The condition 1 is related with frequency band, center frequency and bandwidth of PCell and SCell, which need to be judgedaccording 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.
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 contiguousCCs 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).
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 24/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Table 4‑2 Center Frequency Spacing of Intra-Band Contiguous CA with Different Bandwidths
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.
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‑2SCellAddition
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 25/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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).
Parameter Parameter
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 1:Use partial
Space frequency band(performance no impaired), guard
3 GlobleSwitchInformation.freqSpaceCfgMode N/A
Configuration space 2:Use all guard band(performance band(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
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 26/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 27/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The Uplink Total
PRB Ratio
Threshold of
PCell for Active
SCell is one
The Uplink
reason of scell
Total PRB
active, it is valid
Ratio
8 CarrierAggregatin.pcellPRBRatioActThrUl when CA is [0,100] unit % N/A 0
Threshold of
configured. The
Pcell(Active
smaller the
SCell)
value, the
easier it is to
activate the
secondary
carrier.
The Uplink Total
PRB Ratio
Threshold of
SCell for Active
SCell is one
The Uplink
reason of scell
Total PRB
active, it is valid
Ratio
9 CarrierAggregatin.scellPRBRatioActThrUl when CA is [0,100] unit % N/A 100
Threshold of
configured.The
SCell(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 of CA is [0,100] unit % N/A 0
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 [0,100] unit % N/A 0
Threshold of CA is
SCell(DeActive configured.The
SCell) smaller the
value, the
easier it is to
deactivate the
secondary
carrier.
if this thr is
smaller more
actual value,
SCC is
deactivated.The
smaller the
value, the more
Threshhold of
difficult it is to
Mcs deactive
12 CarrierAggregatin.sccMcsEDeactThr deactivate the [0,28] N/A 0
for Scc in UL
secondary
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
activated.The
Sinr of Active
13 CarrierAggregatin.caSccActSinrThrUl smaller the [0..40],step=0.5 N/A 22.5
scell in UL CA
value, the
easier it is to
activate the
secondary
carrier.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 28/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
if this thr is
smaller than
actual value
,SCC is
Sinr of Deactivated.
14 CarrierAggregatin.caSccDeactSinrThrUl Deactive scell The smaller the [0..40],step=0.5 N/A 19
in UL CA value, the more
difficult it is to
deactivate the
secondary
carrier.
buffer Length
threshold for UL
CA UE, when
UL BSR is
bigger than this
threshold, it is
considered
SCell Active
Congestion,
Data Buffer
and as a
15 CarrierAggregatin.scellActBuSizeThdUL Length [0..20],step=0.1 Kbyte 1
condition of
Threshold for
SCell
UL CA UE
Active.The
smaller the
value, the
easier it is to
activate the
secondary
carrier.
SCell Active
Data buffer
delay threshold
for ULCA UE,
when UL BSR
Delay is bigger
than this
threshold, it is
SCell Active
considered
Data Buffer
Congestion,
16 CarrierAggregatin.scellActBufDelayThdUL Delay [5,200] ms 20
and as a
Threshold for
condition of
ULCA UE
SCell
Active.The
smaller the
value, the
easier it is to
activate the
secondary
carrier.
ULCA Schedule
data size
Threshold for
ULCA deactiving
Schedule Data SCell. The
17 CarrierAggregatin.caSchdSizeDeActThrUL Size Threshold smaller the [0,200] Kbyte 70
for Deactive value, the more
SCell difficult it is to
deactivate the
secondary
carrier.
If this threshold
is smaller than
actual GBR
configured
,SCC is
Gbr Threshold
activated.The
18 CarrierAggregatin.caSccActGbrThrUl of Active SCell [10,64000] kbytes 500
smaller the
in UL CA
value, the
easier it is to
activate the
secondary
carrier.
The parameter
is MCS
threshold of
SCell DeActive
for CA,when CA
The MCS
is configured.if
19 CarrierAggregatin.mcs4SCellDeActiveDl Threshold Of [0..28] N/A 1
MCS of SCell
SCell DeActive
is less or equal
to the
threshold,SCell
will be
deActived.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 29/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The CA
schedule data
size Threshold
for DeActive
SCell is one
CA Schedule reason of Scell
Data Size deactive, it is
20 CarrierAggregatin.caSchdSizeDeActThrDl 0:50,1:100,2:200,3:500,4:1000 Kbit 1:100
Threshold for valid when CA
Deactive SCell is configured
and deactive
SCC when
schedule data
is less than the
threshold.
Parameter
Parameter Range Default
SN Parameter name panel Unit
explanation value value
name
This
Switch for 0:
parameter is
CA Close
switch for
1 GlobleSwitchInformation.fddTddCaSwch between N/A Close[0]
CA between 1:
FDD and
FDD and Open
TDD
TDD.
This
Switch for parameter is 0:
3CC CA switch for Close
2 GlobleSwitchInformation.fddTdd3ccCaSwch between 3CC CA N/A Close[0]
1:
FDD and between
Open
TDD FDD and
TDD.
This
parameter is
the switch
for the
FDD+TDD
Switch for 4CC CA 0:
4CC CA function. It Close
3 GlobleSwitchInformation.fddTdd4ccCaSwch between needs to be N/A Close[0]
1:
FDD and set to
Open
TDD "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
4 GlobleSwitchInformation.fddTdd5ccCaSwch between needs to be N/A Close[0]
1:
FDD and set to
Open
TDD "Open"
when it is
required to
perform
FDD+TDD
5CC CA.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 30/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4.2.5 Primary Carrier Frequency Priority Parameters
Parameter
Range Default
SN Parameter name panel Parameter explanation value
Unit
name
value
If this switch is opened, CA UE use fair
scheduling, else use Differentiation
This
scheduling.
Parameter
Note: if
is Used to 0:Close
GlobleSwitchInformation.fairSchdSwch
1 GlobleSwitchInformation.fairSchdSwch Open CA N/A Close[0]
is set to open, the 1:Open
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
Note: if 0.1
Schedule
GlobleSwitchInformation.fairSchdSwch
is set to open, the
ENBFunctionFDD.fairSchdFactor is
configured only to support 2CC;the
3CC cannot achieve the absolute
fairness.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 31/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
When the PRB ratio
PRB Ratio
of PCell is higher
Threshold of
than this threshold, [0,100]
2 CarrierAggregatin.prbThrd4GetLBInfo PCell for N/A 20
eNB should get RPB unit %
getting Load
ratio information of
Information
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
5 CarrierAggregatin.scellSelBaseFreqPriSwch Based on N/A Close[0]
higher Scell will be 1:
Frequency
selection and Open
Priority
configuration
When the switch is
The Switch opened, the Scell 0:
of Scell with smaller DL PRB Close
6 CarrierAggregatin.scellBaseDlPRBSwch N/A Close[0]
based on DL ratio will be 1:
PRB ratio selection and Open
configuration
Parameter
Parameter Range Default
SN Parameter name panel Unit
explanation value value
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
1 GlobleSwitchInformation.caBackOffSwch CA UE N/A Close[0]
this switch is 1:Open
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
3 AC.caUserSwch CA User in cell reaches N/A Close[0]
1:Open
Restrict threshold of
forbid Configured
as SCell, the cell
cannot be
configured as
SCell.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 32/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
This parameter is
the Threshold of
forbid Configured
as SCell. If the
rate of number of
users in cell
(including the
Users connected
Threshold
in cell and the
of Forbid [0,100]
4 AC.forbidSCellThrd Users is N/A 80
Configured unit %
configured with
As SCell
this cell) and
max number of
users allowed in
cell reaches
threshold, the
cell cannot be
configured as
SCell.
Parameter
Parameter Range Default
SN Parameter name panel Unit
explanation value value
name
If this switch
is open, CA
UE would
be
monitored,
only if the
suitable UE
could be
Switch of 0:Close
configured
1 GlobleSwitchInformation.caMonitorSwch CA UE N/A Close[0]
SCell; If this 1:Open
Monitor
switch is
close, CA
UE would
not be
monitored
before
configuring
SCell.
Parameter
Parameter Range Default
SN Parameter name panel Unit
explanation value value
name
When this switch
is opened, the
target cell choose
appropriate
SCells after
received
HandoverRequest
message, and
Switch of
configure these 0:Close
CA User
1 GlobleSwitchInformation.caScellHOSwch SCells to UE; N/A Close[0]
Handover 1:Open
When this switch
With SCell
is closed, all the
SCells of source
cell are deleted.
SCells of target
cell will be added
Until handover
procedure
completed.
- 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.
Open CA switch in EMS. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration>Global Switch,and set the related CA switches as shown below.
Configure the frequency and bandwidth of the two cells according to network planningas shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 34/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
Notes:
Insert the CR0 board in the corresponding slot according to slot planning.
1. Select Managed Element> Deviceto 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.
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 nameto 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 35/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. In the Configuration Management window of the EMS, select Special Function of Standard -> Neighbor Cell Management as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 36/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 37/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
5. The neighbor relation configuration records for the two cells are shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 38/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 39/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
4. Neighbor Cell List dialog box is displayed. Then select which SCell to group with Pcell.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 40/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
5. SelectDL CA in the Neighbor Cell List dialog box and select the SCell according to network planning.
6. Then click OKbutton. The system executes CA coordination cells combination. The successfuly result is shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 41/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 42/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 43/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. Synchronize data
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 44/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4.4.1 Enabling the Feature
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
nametoFS5Cas shown below.
In the Configuration Management window of EMS, selectModify Area >Transmission Network > LTE FDD+TD-LTE > IP Transport> X2+IP Configuration, double-
click the record. In the X2+IP window, configure X2+IP as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 45/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
In the Configuration Management window of EMS, selectModify 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 the address configured in Step2; Used
IP Layer Configuration and Used Bandwidth Resource is FDD configuration in mixed mode. In the Co-eNodeB X2+Port IP Link Table window, configure Co-eNodeB
X2+Port IP Link Table as shown below.
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 the address configured in
Step2; Used IP Layer Configuration and Used Bandwidth Resource is TDD configuration in mixed mode.
5. Configure theSwitch for CA between FDD and TDD, Switch for 3CC CA Between FDD and TDD
In the Configuration Management window of EMS, selectModify 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 46/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 47/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Figure 4‑27Configuring PUCCH Format Resources
Configure theMax SCell Num for CA. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE, double-click the record. In the
window, configuretheMax SCell Num for CAto 2 as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 48/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The cells are configured to neighbor relation.For detailed method, refer to theneighbor relation Configuration of the DL 2cells.
9. Configure Coordinationrelation
The cells are configured to CA coordinating relation. For detailed method, refer to theCoordinationrelation Configuration of the DL 2cells.
1. Configure the frequency and bandwidth for the three cells according to UE capability. And then configure theMax SCell Num for CA, The RB number of PUCCH
format 3,Neighbor relation andCoordinationrelationas shown below.
2. Configure theMax SCell Num for CA. In the Configuration Management window of EMS, selectModify 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, selectModify Area > Radio Parameter > LTE FDD >E-UTRAN
FDD Cell >PUCH And PDCH, double-click the record.Configure the three cellsRB number of PUCCH format 3to 1as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 49/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 theneighbor relation Configuration of the DL 2cells.
5. Configure the Coordinationrelation. TheCoordinationrelationConfiguration of DL 3cells CA is to make DL Coordinationrelationfor any two of the three. For detailed
method, refer to theCoordinationrelation Configuration of the DL 2cells.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 50/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
When all the initial parameters including CA part are configured completely, and make sure that the configuration is correct, perform the whole table synchronization.
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 thePcell of CA, and then click Group button as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 51/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
3. Pop-up Neighbor list dialog box, set collaborative relationship TypetoUL and DL CA , and then choose SCell of CA according to the network planning as shown
below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 52/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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).
- 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;
In configuration management window, select Modify ->Device ->B8200 ->CCE1->Clock Device Set->Clock Device. Createnew record that Clock Device with
default parameters.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 53/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
In configuration management window, select Modify ->Device ->B8200 ->CCE1->Clock Device Set. Set Clock synchronization mode to Phase synchronization.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 54/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. Inter-eNodeB FDD+FDD2cells CAconfiguration 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 55/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Connect the right optical port of two CR0 Boards with 10G optical module directly. Then set the Port Working Mode to 10Gbpsas shown below.
In EMS configuration management window, select Modify ->Transmission Network -> LTE FDD ->X2+IP Configuration(FDD). Createnew record that IP Address
and Gateway IP with the same network section as shown below.Two CR0, one IP Addressis configured as 169.0.0.1, and the other IP Addressis configured as
169.0.0.2.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 56/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
In EMS configuration management window, select Modify ->Transmission Network -> LTE FDD ->Signaling and Business ->SCTP. Createnew 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 flexibilityfunction cannot be activated.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 57/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Both eNodeB must be configured.In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD >Resource Interface
Configuration> Co-eNodeB X2 + Port IP Link Table. Createnew 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
Addressof CR0). Configure the Used IP Layer ConfigurationandUsed Bandwidth Resourceof FDD,Co-eNodeB X2 + Port IP Link Table ofFDD is complete. And
the other eNodeBis similar to this one as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 58/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
8. Configure Neighbor relation and Coordination relation. For detailed method, refer to the DL 2cells CA.
When all the initial parameters including CA part are configured completely, and make sure that the configuration is correct, perform the whole table synchronization.
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.
2. In the UE E-UTRAN Measurement List window, select the record whose measurement configuration function name is Add SCell Measurementand Measurement
Configuration Index is 500, then click button, enter to UE E-UTRAN Measurement Window.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 59/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑45Configuring the Parameter RSRP Absolute Threshold of Event Decision for A4 Event
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 60/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
5. Click button, and complete the configuration for Add SCell Measurement.
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.
3. In this window, modify the parameter RSRP Absolute Threshold of Event Decision for A2 event according to test requirement.
Figure 4‑47 Modify the Parameter RSRP Absolute Threshold of Event Decision for A2 Event
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 61/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4. Click button, and complete the configuration for Remove SCell Measurment.
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 Measurementand
Measurement Configuration Index is 520, then click button, enter to UE E-UTRAN Measurement Window.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 62/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
3. In this window, modify the parameter RSRP Absolute Threshold of Event Decision for A6 event according to test requirement.
Figure 4‑49 Modify the Parameter RSRP Absolute Threshold of Event Decision for A6 Event
4. Click button, and complete the configuration for Add SCell Measurment.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 63/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
2. In Carrier Aggregation Config window, modify the RB ratio threshold for SCC activating/deactivating.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 64/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
1. In the Configuration Management window of EMS, selectModify 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 65/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 recordas shown below.
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‑54Modify the Switch for fixed Primary carrier based measurement
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 66/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. Differentiated scheduling is used by default. To enable fair scheduling function, open the Fair scheduling switch. In the Configuration Management window of EMS,
selectModify 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 Scheduleas shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 67/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD to configurethe Factor of CA Fair Scheduleto 0-1as shown
below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 68/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 ConfigurationPRB Ratio Threshold of PCell for Getting Load Information andLoad Type Indicator as shown below.
4. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD > E-UTRAN FDD Cell >Measurement Parameter, double-click
the record, configurescell frequency priority as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 69/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD >E-UTRAN FDD Cell >Admission Control, double-click the
record, configureSwitch of CA User Restrict to open, and you can alsosetThreshold of forbid Configured as SCelland Threshold of CA UE Back Off as shown
below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 70/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch, double-
click the record. In the Global Switch window, configurethe Switch of CA UE Backoff as shown below.
1. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch, double-
click the record. In the Global Switch window, configurethe Switch of CA UE Monitorto Openas shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 71/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. In the Configuration Management window of EMS, selectModify Area > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch, double-
click the record. In the Global Switch window,modify the Switch of CA UE Handover With SCell as shown below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 72/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 73/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
30 C374241929 Number of UL RB obtained by MCS29 on PCell
31 C374241930 Number of UL RB obtained by MCS30 on PCell
32 C374241931 Number of UL RB obtained by MCS31 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
44 C374241943 Number of UL RB obtained by MCS1 on SCell
45 C374241944 Number of UL RB obtained by MCS2 on SCell
46 C374241945 Number of UL RB obtained by MCS3 on SCell
47 C374241946 Number of UL RB obtained by MCS4 on SCell
48 C374241947 Number of UL RB obtained by MCS5 on SCell
49 C374241948 Number of UL RB obtained by MCS6 on SCell
50 C374241949 Number of UL RB obtained by MCS7 on SCell
51 C374241950 Number of UL RB obtained by MCS8 on SCell
52 C374241951 Number of UL RB obtained by MCS9 on SCell
53 C374241952 Number of UL RB obtained by MCS10 on SCell
54 C374241953 Number of UL RB obtained by MCS11 on SCell
55 C374241954 Number of UL RB obtained by MCS12 on SCell
56 C374241955 Number of UL RB obtained by MCS13 on SCell
57 C374241956 Number of UL RB obtained by MCS14 on SCell
58 C374241957 Number of UL RB obtained by MCS15 on SCell
59 C374241958 Number of UL RB obtained by MCS16 on SCell
60 C374241959 Number of UL RB obtained by MCS17 on SCell
61 C374241960 Number of UL RB obtained by MCS18 on SCell
62 C374241961 Number of UL RB obtained by MCS19 on SCell
63 C374241962 Number of UL RB obtained by MCS20 on SCell
64 C374241963 Number of UL RB obtained by MCS21 on SCell
65 C374241964 Number of UL RB obtained by MCS22 on SCell
66 C374241965 Number of UL RB obtained by MCS23 on SCell
67 C374241966 Number of UL RB obtained by MCS24 on SCell
68 C374241967 Number of UL RB obtained by MCS25 on SCell
69 C374241968 Number of UL RB obtained by MCS26 on SCell
70 C374241969 Number of UL RB obtained by MCS27 on SCell
71 C374241970 Number of UL RB obtained by MCS28 on SCell
72 C374241971 Number of UL RB obtained by MCS29 on SCell
73 C374241972 Number of UL RB obtained by MCS30 on SCell
74 C374241973 Number of UL RB obtained by MCS31 on SCell
75 C374241974 Number of DL RB obtained by MCS0 on PCell
76 C374241975 Number of DL RB obtained by MCS1 on PCell
77 C374241976 Number of DL RB obtained by MCS2 on PCell
78 C374241977 Number of DL RB obtained by MCS3 on PCell
79 C374241978 Number of DL RB obtained by MCS4 on PCell
80 C374241979 Number of DL RB obtained by MCS5 on PCell
81 C374241980 Number of DL RB obtained by MCS6 on PCell
82 C374241981 Number of DL RB obtained by MCS7 on PCell
83 C374241982 Number of DL RB obtained by MCS8 on PCell
84 C374241983 Number of DL RB obtained by MCS9 on PCell
85 C374241984 Number of DL RB obtained by MCS10 on PCell
86 C374241985 Number of DL RB obtained by MCS11 on PCell
87 C374241986 Number of DL RB obtained by MCS12 on PCell
88 C374241987 Number of DL RB obtained by MCS13 on PCell
89 C374241988 Number of DL RB obtained by MCS14 on PCell
90 C374241989 Number of DL RB obtained by MCS15 on PCell
91 C374241990 Number of DL RB obtained by MCS16 on PCell
92 C374241991 Number of DL RB obtained by MCS17 on PCell
93 C374241992 Number of DL RB obtained by MCS18 on PCell
94 C374241993 Number of DL RB obtained by MCS19 on PCell
95 C374241994 Number of DL RB obtained by MCS20 on PCell
96 C374241995 Number of DL RB obtained by MCS21 on PCell
97 C374241996 Number of DL RB obtained by MCS22 on PCell
98 C374241997 Number of DL RB obtained by MCS23 on PCell
99 C374241998 Number of DL RB obtained by MCS24 on PCell
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 74/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
100 C374241999 Number of DL RB obtained by MCS25 on PCell
101 C374242000 Number of DL RB obtained by MCS26 on PCell
102 C374242001 Number of DL RB obtained by MCS27 on PCell
103 C374242002 Number of DL RB obtained by MCS28 on PCell
104 C374242003 Number of DL RB obtained by MCS29 on PCell
105 C374242004 Number of DL RB obtained by MCS30 on PCell
106 C374242005 Number of DL RB obtained by MCS31 on PCell
Number of RB obtained DL by MCS20~23 for
107 C374242006
256QAM ITBS table2 on PCell
Number of RB obtained DL by MCS24~27 for
108 C374242007
256QAM ITBS table2 on PCell
Number of RB obtained DL by MCS31 for
109 C374242008
256QAM ITBS table2 on PCell
110 C374242009 Number of CQI0 Be Used on PCell
111 C374242010 Number of CQI1 Be Used on PCell
112 C374242011 Number of CQI2 Be Used on PCell
113 C374242012 Number of CQI3 Be Used on PCell
114 C374242013 Number of CQI4 Be Used on PCell
115 C374242014 Number of CQI5 Be Used on PCell
116 C374242015 Number of CQI6 Be Used on PCell
117 C374242016 Number of CQI7 Be Used on PCell
118 C374242017 Number of CQI8 Be Used on PCell
119 C374242018 Number of CQI9 Be Used on PCell
120 C374242019 Number of CQI10 Be Used on PCell
121 C374242020 Number of CQI11 Be Used on PCell
122 C374242021 Number of CQI12 Be Used on PCell
123 C374242022 Number of CQI13 Be Used on PCell
124 C374242023 Number of CQI14 Be Used on PCell
125 C374242024 Number of CQI15 Be Used on PCell
126 C374242025 Number of DL RB obtained by MCS0 on SCell
127 C374242026 Number of DL RB obtained by MCS1 on SCell
128 C374242027 Number of DL RB obtained by MCS2 on SCell
129 C374242028 Number of DL RB obtained by MCS3 on SCell
130 C374242029 Number of DL RB obtained by MCS4 on SCell
131 C374242030 Number of DL RB obtained by MCS5 on SCell
132 C374242031 Number of DL RB obtained by MCS6 on SCell
133 C374242032 Number of DL RB obtained by MCS7 on SCell
134 C374242033 Number of DL RB obtained by MCS8 on SCell
135 C374242034 Number of DL RB obtained by MCS9 on SCell
136 C374242035 Number of DL RB obtained by MCS10 on SCell
137 C374242036 Number of DL RB obtained by MCS11 on SCell
138 C374242037 Number of DL RB obtained by MCS12 on SCell
139 C374242038 Number of DL RB obtained by MCS13 on SCell
140 C374242039 Number of DL RB obtained by MCS14 on SCell
141 C374242040 Number of DL RB obtained by MCS15 on SCell
142 C374242041 Number of DL RB obtained by MCS16 on SCell
143 C374242042 Number of DL RB obtained by MCS17 on SCell
144 C374242043 Number of DL RB obtained by MCS18 on SCell
145 C374242044 Number of DL RB obtained by MCS19 on SCell
146 C374242045 Number of DL RB obtained by MCS20 on SCell
147 C374242046 Number of DL RB obtained by MCS21 on SCell
148 C374242047 Number of DL RB obtained by MCS22 on SCell
149 C374242048 Number of DL RB obtained by MCS23 on SCell
150 C374242049 Number of DL RB obtained by MCS24 on SCell
151 C374242050 Number of DL RB obtained by MCS25 on SCell
152 C374242051 Number of DL RB obtained by MCS26 on SCell
153 C374242052 Number of DL RB obtained by MCS27 on SCell
154 C374242053 Number of DL RB obtained by MCS28 on SCell
155 C374242054 Number of DL RB obtained by MCS29 on SCell
156 C374242055 Number of DL RB obtained by MCS30 on SCell
157 C374242056 Number of DL RB obtained by MCS31 on SCell
Number of RB obtained DL by MCS20~23 for
158 C374242057
256QAM ITBS table2 on SCell
Number of RB obtained DL by MCS24~27 for
159 C374242058
256QAM ITBS table2 on SCell
Number of RB obtained DL by MCS31 for
160 C374242059
256QAM ITBS table2 on SCell
161 C374242060 Number of CQI0 Be Used on SCell
162 C374242061 Number of CQI1 Be Used on SCell
163 C374242062 Number of CQI2 Be Used on SCell
164 C374242063 Number of CQI3 Be Used on SCell
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 75/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
165 C374242064 Number of CQI4 Be Used on SCell
166 C374242065 Number of CQI5 Be Used on SCell
167 C374242066 Number of CQI6 Be Used on SCell
168 C374242067 Number of CQI7 Be Used on SCell
169 C374242068 Number of CQI8 Be Used on SCell
170 C374242069 Number of CQI9 Be Used on SCell
171 C374242070 Number of CQI10 Be Used on SCell
172 C374242071 Number of CQI11 Be Used on SCell
173 C374242072 Number of CQI12 Be Used on SCell
174 C374242073 Number of CQI13 Be Used on SCell
175 C374242074 Number of CQI14 Be Used on SCell
176 C374242075 Number of CQI15 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 CA
191 C373384377
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 Mac
224 C373597002
CE(Exclude Implicit Deactive Scell)
225 C373597023 UL Scheduled RB Number for SCC UE
226 C373597024 UL Scheduled TB Number for SCC UE
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 76/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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
C374281115 Number of Successfully transferred DL MAC
263
TBSize for SCell
C374281116 Number of Successfully transferred UL MAC
264
TBSize for PCell
C374281117 Number of Successfully transferred UL MAC
265
TBSize for SCell
C374281118 Number of Successfully transferred DL MAC
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
C374281121 Number of Successfully transferred UL MAC
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
CC Number) CA Capability
C374210762 DL Maximum User Number With 3CC(Maximum
278
CC Number) CA Capability
C374210763 DL Average User Number With 3CC(Maximum
279
CC Number) CA Capability
280 C374210766 DL Maximum User Number With 2CC CA Enabled
281 C374210767 DL Average User Number With 2CC CA Enabled
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 77/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
282 C374210768 DL Maximum User Number With 3CC CA Enabled
283 C374210769 DL Average User Number With 3CC CA Enabled
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.1 Topology
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 78/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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
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 aredefined as below.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 79/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Check whether the SCell is added by RRC Connection Reconfiguration message. The following figure shows the SCell(PCI 189) adding successfully.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 80/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Check the PCell and SCell PCI are 188 and 189 respectively after UE attached successfully by QXDM tools, as shown in the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 81/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
6.2.1 Topology
Table 6‑3DL Non-Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 82/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
frequency band of Cell 1 and Cell2 are band3. The nominal
channel spacing between Cell1 and Cell2 is 20MHz. 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 bandwidths of Cell 1 and Cell 2 are all 20MHz;
3. The CA function is open;
4. LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
6. The UE supports CA function.
7. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Intra Band
Open[1]
Incontinuous 2CC 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
6.3.1 Topology
Refer to Section 6.1.1Topology.
For the DL contiguous intra-band two carrier aggregation test specification, refer tothe table below.
Table 6‑4DL Contiguous Intra-Band Two Carrier Aggregation Function Test Specification
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 83/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4. LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
6. The UE supports CA function.
7. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Intra Band
Open[1]
Continuous 2CC 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
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‑6Measurement 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 84/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Then eNodeB sends the RRC Connection Reconfiguration message, adding the cell with PCI=78 to SCell, as shown in the figure below.
Figure 6‑8eNodeBSends 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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 85/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.4.1 Topology
Refer to Section 6.1.1Topology.
For the CA SCell adding and deleting test specification, refer tothe table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 86/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Other Parameters Configured N/A
according to the
actual network
After UE attached, the eNodeB sends RRC Connection Reconfiguration message which carries A2 event to trigger SCell deleting. See the figure below.
Adjust SCell’s signal quality and make it weaker, the A2 event reporting is triggered.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 87/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The eNodeB sends the RRC Connection Reconfiguration message, which carried A4 event of SCell and deletes SCell. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 88/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Adjust the SCell’s signal quality and make it better.The A4 event measurement reporting is triggered to report. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 89/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The eNodeB sends RRC Connection Reconfiguration to add SCell. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 90/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.5.1 Topology
For the CA SCell modifying test specification, refer tothe table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 91/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Table 6‑6CA SCell Modifying Function Test Specification
After UE attached, the eNodeB sends RRC Connection Reconfiguration message which carries A6 event. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 92/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 93/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.6.1 Topology
Refer to Section 6.1.1Topology.
For the CA SCell activating and deactivating test specification, refer tothe table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 94/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Switch for Inter Band 2CC Open[1] N/A
CA
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC 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
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.
After SCC is active, the service data will transmit on both PCC and SCC. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 95/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
After SCC deactivated, the data service is only transmits on PCC. See the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 96/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.7 Handover of CA
6.7.1 Topology
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 97/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Test item Handover of CA Test.
Feature ID ZLF34-00-013
Verify that the function handover of CA is supported by LTE
Purpose
system.
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;
3. The CA function is enabled;
4. The LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
6. The UE supports CA function.
7. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Prerequisites
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
Switch of CA User
Close[0]
Handover With Scell 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
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 98/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
3. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 99/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4. Then eNodeB sends the RRC Connection Reconfiguration message to add SCell.
Figure 6‑27eNodeB 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‑28UE Sends the RRC Connection Reconfiguration Complete Message to eNodeB after the SCell Adding Successfully
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 100/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured 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.
3. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
4. Then eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
5. UE sends the Measurement Report message for A4 event to eNodeB according to the measurement configuration received.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 101/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6. Then eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
Figure 6‑31eNodeB 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)
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
2. Source eNodeB sends the Handover Required message to MME to request the target eNodeB to prepare radio resource.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 102/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 103/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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
MobilityControlInfo IE.
6. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
7. The target eNodeB sends the RRC Connection Reconfiguration message to add SCell.
8. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the SCell is added successfully.
6.7.3.4 Inter-eNodeB CA Handoverwithout SCell based on S1 interface (SCell adding based on A4 measurement)
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
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
MobilityControlInfo IE.
6. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
7. The target eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
8. UE sends the Measurement Report message for A4 event to eNodeB according to the measurement configuration received.
9. Then eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
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)
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 104/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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
MobilityControlInfo IE.
5. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
6. The target eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
7. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the SCell is added successfully.
6.7.3.6 Inter-eNodeB CA Handover without SCell based on X2 interface (SCell adding based on A4 measurement)
1. UE sends the Measurement Report message after the channel quality was reached to the threshold of configured handover A3 Event.
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
MobilityControlInfo IE.
5. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after UE initiates random access in target cell.
6. The target eNodeB sends the RRC Connection Reconfiguration message to UE to indicated UE to measure the SCC.
7. UE sends the Measurement Report message for A4 event to eNodeB according to the measurement configuration received.
8. Then eNodeB sends the RRC Connection Reconfiguration message to indicate adding SCell.
9. UE sends the RRC Connection Reconfiguration Complete message to eNodeB after the UE added SCell completely.
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‑36RRC Connection Reconfiguration Message for Deleting the Source SCell and Adding the New SCell
6.8.1 Topology
For CA primary carrier frequency priority test specification, refer tothe table below.
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.
ii. After UE is handover completely, the eNodeB sends the RRC Connection Reconfiguration message to add SCell. See the figure below.
2. The parameterSwitch 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‑39The Second RRC Connection Reconfiguration Message Carries the Handover A5 Event Configuration
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 107/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
The third RRC Connection Reconfiguration message carries the adding SCell A4 event configuration. See the figure below.
Figure 6‑40The 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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 108/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 109/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2 Power on UE and initiate UE accesses to the serving cell1
attachoperation. successfully and the cell1 is a PCell.
Cell2 and cell3 are added as SCells in
the RRC Connection Reconfiguration
message.
Two SCells activate successfully.
The downlink throughput can reach to
450Mbps for three carriers aggregated
Start best-effort FTP download
3 with bandwidth 60MHz in the case of no
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
The downlink peak throughput is 450Mbps if maximum
result
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 110/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
eNodeB sends the RRC Connection Reconfiguration message which carried SCell PCI in measObjectEUTRA IE. See the figure below.
Figure 6‑44eNodeB 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‑45Deleting SCell Measurement Event A2 Configuration is Carried in the Same RRC Connection Reconfiguration Message
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 111/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 112/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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‑50The 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‑51The 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 113/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.10.1 Topology
The test network for FDD+TDD carrier aggregation is shown in the figure below.
The test devices for FDD+TDD carrier aggregation are shown in the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 114/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
NO Test Devices Notes
4 PDN server One
The test specification of Carrier Aggregation(DL 2CC, FDD+TDD) is shown in the table below.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 115/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑55eNodeB 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 116/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑57There 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‑58The Downlink Peak Throughput is 265Mbps for FDD+TDD Carriers Aggregated with Bandwidth 40MHz
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 117/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.11.1 Topology
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 118/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 119/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑61The Uplink Peak Throughput is 149Mbps for Two Carriers Aggregated with Bandwidth 40MHz
6.12.1.1 Topology
For the flexible SCell configuration of multi-carriers test specification, refer to the table below.
Feature ID ZLF34-00-036
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.
2. The LTE EPC works normally;
3. The downlink AMBR of UE is larger than 450Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
4. The UE supports two CA function.
5.The performance of computer for FTP server and UEs satisfies
the performance test requirement.
6. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
Carrier Aggregation Config
The Switch of Scell Based
Open[1]
on Frequency Priority N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
12
1b N/A
Measurement Parameter
Inter-Frequency Number 2 N/A
Inter-Frequency Item0: N/A
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 120/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Measurement - Band Indication for
Configuration DL Frequency:3
- Inter-
Frequency:same with
cell2;
- Scell Frequency
Priority:255;
Item1:
- Band Indication for
DL Frequency:3
- Inter-
Frequency:same with
cell2;
- Scell Frequency
Priority:100;
Configured according N/A
Other Parameters
to the actual network
Step Expected step result
1 Place UE in the center of cell1.
Power on UE and initiate UE accesses cell1 successfully.
2 attach operation.Make sure
The primary cell is cell1.
UE accesses to the 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
sCellToAddModList IE, adding the cell2
as a SCell.
Start downlink FTP service on The SCC is activated.
4 UE and check whether the
The downlink throughput is normal.
SCC is activated.
Stop downlink FTP service
and startPing service. Check
5 The SCC is deactivated.
whether the SCC is
deactivated.
Stop service and release UE.
6 UE is detached successfully.
Recordthe 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.
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‑62RRC 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 121/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
Figure 6‑64eNodeB Sends the RRC Connection Reconfiguration Message to Add SCell
6.12.2.1 Topology
For SCC selection based on cell load function test specification, refer to the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 122/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps.
5. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
6. The main parameters are configured as below.
Parameter Test Value Unit
Carrier Aggregation Config
The Switch of Scell Based
Open[1]
on DL PRB N/A
The Switch of Scell Based
Open[1]
on UpLink PRB N/A
The Switch of Scell Based
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
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
Measurement Parameter
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
Item1:
Configuration
- Band Indication for
DL Frequency:3
- Inter-
Frequency:same with
cell2;
- Scell Frequency
Priority:255; N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
The RB Number of
0
PUCCH Format 3 N/A
Number of PUCCH Format N/A
12
1b
Configured according N/A
Other Parameters
to the actual network
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 123/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 124/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
6.13.1 Topology
The test network for inter-eNodeB carrier aggregation is shown in the figure below.
Test devices for inter-eNodeB carrier aggregation are shown in the table below.
SN Device Remarks
1 eNodeB Two
2 UE One
3 MME One
4 PDN server One
The test specification of cloud centralized CA withideal backhaul is shown in the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 125/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Test item Cloud Centralized CA with Ideal backhaul
Feature ID ZLF34-00-034
Verify that aggregated carrier could be configured in different BBU
Purpose
under centralized deployed.
1. Cell1 belonged to eNodeB1 and cell2 belonged to eNodeB2
areestablished 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.
3. The eNodeB enabled CA function.
4.The LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 150Mbps;
5. The UE supports CA function.
6. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
7. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
12
1b N/A
Clock Device
Clock reference source
GNSS clock category
category N/A
Clock reference source
Inner GNSS
type N/A
Prerequisites
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
Configured according
Network Mask
to the actual network N/A
Configured according
Gateway IP
to the actual network N/A
Configured according
Used X2+ Channel
to the actual network N/A
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
Configured according
Used Bandwidth Resource
to the actual network N/A
Configured according N/A
Other Parameters
to the actual network
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 126/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
eNodeB sends the RRC Connection
Reconfiguration message, carried
sCellToAddModList IE, adding the cell2
as a SCell.
SCells activate successfully.
The downlink throughput can reach to
150Mbps for two carriers aggregated
Start best-effort FTP download with bandwidth 20MHz in the case of no
3 interference.
service.
Record the throughput on UE and
eNodeB sides.
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.
6.14.1 Topology
The test specification of RRC user based CA enable function is shown in the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 127/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Cell2 are configured to neighbor cells and 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 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 UE1 and UE2 support CA function.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
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
Connection User Number Cell2:9 N/A
Configured N/A
Other Parameters according to the
actual network
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 messageto UE1 to add the cell2 (PCI222) as a SCell.
Figure 6‑70The eNodeB sends the Cell1 RRC Connection Reconfiguration message carried adding SCell A4 event measurement configuration to UE1
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 128/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
Figure 6‑72eNodeB sends the RRC Connection Reconfiguration messageto UE1 to add the cell2 (PCI222) as a SCell
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 129/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑73The eNodeB sends the RRCConnectionReconfiguration message carried adding SCell A4 measurement event to UE2
Figure 6‑74UE2 Sends the MeasurementReport Message of A4 and eNodeB does not Send the RRC Connection Reconfiguration message to UE2
6.15.1 Topology
The test specification of RRC user based CA back off is shown in the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 130/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. The carrier frequency of Cell 1 belong to Band 3, and the
carrier frequency of Cell2 belongs to Band 1;
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 UE1 supports CA function and UE2 not supports CA
function.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
Switch of CA UE Backoff Open[1] N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
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
Other Parameters according to the
actual network
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 messageto UE1 to add the cell2 (PCI222) as a SCell.
Figure 6‑75The eNodeB sends the Cell1 RRC Connection Reconfiguration message carried adding SCell A4 event measurement configuration to UE1
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 131/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 132/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑79The UE1’s SCell is deleted because of the number of UEs in cell2 reached to the “Threshold of CA UE Back Off”
6.16.1 Topology
For the cloud CA with non-ideal backhaul test specification, refer to the table below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 133/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
3. The eNodeB enabled CA function.
4.The LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 150Mbps;
5. The UE supports CA function.
6. The transmission delay between eNodeB1 and eNodeB2 is
larger than 0.2ms, but less than 4ms.
7. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
LTE FDD
Max Scell Num for CA 1 N/A
PUCH and PDCH
Number of PUCCH Format
12
1b N/A
Clock Device
Clock reference source
GNSS clock category
category N/A
Clock reference source
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
Configured according
Network Mask
to the actual network N/A
Configured according
Gateway IP
to the actual network N/A
Configured according
Used X2+ Channel
to the actual network N/A
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
Configured according
Used Bandwidth Resource
to the actual network N/A
Configured according N/A
Other Parameters
to the actual network
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 134/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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.
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.
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 135/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
For the DL three carriers aggregation between FDD and TDD test specification, refer to the table below.
Table 6‑23DL Three Carriers Aggregation between FDD and TDD Test Specification
Test item DL three carriers aggregation between FDD and TDD test
Feature ID ZLF34-00-049
Verify that the LTE system supports three carries aggregation
Purpose
betweenFDD 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 downlink throughput can be reached in the same
location.
2. The LTE EPC works normally;
3. The downlink AMBR of UE is larger than 450Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
4. The UE supports FDD+TDD CA function.
5. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
6. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for CA between
Prerequisites Open[1]
FDD and TDD N/A
Switch for 3CC CA
Open[1]
Between FDD and TDD N/A
LTE FDD
Max Scell Num for CA 2 N/A
PUCH and PDCH
The RB Number of PUCCH
1
Format 3 N/A
E-UTRAN TDD Cell
Uplink-Downlink Subframe N/A
2
Configuration
Special Subframe N/A
7
Configuration
Configured N/A
Other Parameters according to the
actual network
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‑82UE Supports Three Carriers Aggregation between FDD and TDD
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 136/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
After UE access successfully, the eNodeB sends the RRC Connection Reconfiguration messageto UE to add the cell2 and cell3 as SCell as shown in the figure below.
Figure 6‑83Add Band1 Cell as a SCell in the RRC Connection Reconfiguration Message
Figure 6‑84Add Band41 Cell as a SCell in the RRC Connection Reconfiguration Message
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 137/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑85The 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 138/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
2. The frequency band of Cell 1 belongs to Band 3, and the
frequency band of Cell 2 belongs to Band 28;
3. The bandwidths of Cell 1 and Cell 2 are all 20MHz;
4. LTE EPC works normally;
5. The downlink AMBR of UE is larger than 300Mbps, and the
uplink AMBR of UE is larger than 100Mbps;
6. The UE supports CA function.
7. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
8. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for Inter Band 2CC
Open[1]
CA N/A
Switch for Intra Band
Open[1]
Continuous 2CC CA N/A
Switch for Intra Band
Open[1]
Incontinuous 2CC CA N/A
Switch of CA UE Monitor Open[1] 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
If the neighbor relation is same coverage, after UE accessed the cell and did not dodata 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‑86When UE Has Large Data Transferring, the SCell Based on Blind Addition Is Added Successfully
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 139/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑87When 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 141/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
byeNodeB.
2. After UEs access cell 182, the cell184 is added as SCell, as shown in the figure below.
3. Start full-buffer FTP service for UEs and the SCC is activated, as shown in the figure below.
4. Trigger VoLTE service between UE1 and UE2, the dedicated bearers QCI5 and QCI1 are established successfully, as shown in the figure below.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 142/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑92eNodeB 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‑93eNodeB Sends the RRC Connection Reconfiguration Message to Indicate UE to Be Handover to Cell 184
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 143/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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‑94eNodeB 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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 144/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
4. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
5. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for CA between
Open[1]
FDD and TDD N/A
Switch for 3CC CA
Open[1]
Between FDD and TDD N/A
Switch for 4CC CA Open[1]
between FDD and TDD N/A
Switch for 5CC CA Open[1]
between FDD and TDD N/A
LTE FDD
Max Scell Num for CA 4 N/A
PUCH and PDCH
The RB Number of PUCCH
1
Format 3 N/A
E-UTRAN TDD Cell
Uplink-Downlink Subframe N/A
2
Configuration
Special Subframe N/A
7
Configuration
Configured N/A
Other Parameters according to the
actual network
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.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 145/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
than 1Gbps, and the uplink AMBR of UE is larger than 100Mbps.
4. The performance of computer for FTP server and UEs
satisfies the performance test requirement.
5. The main parameters are configured as below.
Parameter Test Value Unit
Global Switch
Switch for CA between
Open[1]
FDD and TDD N/A
Switch for 3CC CA
Open[1]
Between FDD and TDD N/A
Switch for 4CC CA Open[1]
between FDD and TDD N/A
LTE FDD
Max Scell Num for CA 3 N/A
PUCH and PDCH
The RB Number of PUCCH
1
Format 3 N/A
E-UTRAN TDD Cell
Uplink-Downlink Subframe N/A
2
Configuration
Special Subframe N/A
7
Configuration
Configured N/A
Other Parameters according to the
actual network
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
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.
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"
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 146/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
3. 3GPP TS 36.300,"Overall description"
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
configurations increasing carrier frequency Maximum
Bandwidth
E-UTRA CA (NOTE 3) Channel Channel Channel aggregated
combination
configuration bandwidths bandwidths bandwidths bandwidth
set
for carrier for carrier for carrier [MHz]
[MHz] [MHz] [MHz]
15 15
CA_1C CA_1C 40 0
20 20
5 20
10 15, 20
CA_2C 15 10, 15, 20 40 0
5, 10, 15,
20
20
5, 10, 15 20
CA_3C CA_3C 5, 10, 15, 40 0
20
20
CA_7B 15 5 20 0
15 15
40 0
20 20
10 20
CA_7C CA_7C 15 15, 20 40 1
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
5, 10, 15,
CA_41C CA_41C
20 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
CA_42C CA_42C 5, 10, 15, 40 0
20 20
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 147/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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))
E-UTRA CA configuration / Bandwidth combination set
Uplink CA Maximum
E- Bandwidth
E-UTRA CA configurations 1.4 3 5 10 15 20 aggregated
UTRA combination
Configuration (NOTE 4) MHz MHz MHz MHz MHz MHz bandwidth
Bands 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
1 Yes Yes Yes Yes
35 0
18 Yes Yes Yes
CA_1A-18A CA_1A-18A
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 - See CA_41C Bandwidth Combination Set 60 0
41
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 - See CA_42C Bandwidth Combination Set 60 0
42
0 in Table 5.6A.1-1
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
See CA_2A-2A Bandwidth Combination
CA_2A-2A- 2
- Set 0 in Table 5.6A.1-3 60 0
4A
4 Yes Yes Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-
- See CA_4A-4A Bandwidth Combination 60 0
4A 4
Set 0 in Table 5.6A.1-3
See CA_2A-2A Bandwidth Combination
2
CA_2A-2A- Set 0 in Table 5.6A.1-3
- 80 0
4A-4A See CA_4A-4A Bandwidth Combination
4
Set 0 in Table 5.6A.1-3
2 Yes Yes Yes Yes
30 0
5 Yes Yes
CA_2A-5A -
2 Yes Yes
20 1
5 Yes Yes
See CA_2A-2A Bandwidth Combination
CA_2A-2A- 2
- Set 0 in Table 5.6A.1-3 50 0
5A
5 Yes Yes
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 148/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
See CA_2C in Table 5.6A.1-1 Bandwidth
2
CA_2C-5A - combination set 0 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
See CA_2A-2A Bandwidth Combination
CA_2A-2A- 2
- Set 0 in Table 5.6A.1-3 50 0
12A
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-12B - 12 See CA_12B Bandwidth Combination Set 35 0
0 in Table 5.6A.1-1
See CA_2C in Table 5.6A.1-1 Bandwidth
2
CA_2C-12A - combination set 0 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
2 See CA_2A-2A Bandwidth Combination
CA_2A-2A-
- Set 0 in Table 5.6A.1-3 50 0
13A
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
2 Yes Yes
20 0
29 Yes Yes Yes
2 Yes Yes
CA_2A-29A - 20 1
29 Yes Yes
2 Yes Yes Yes Yes
30 2
29 Yes Yes
See CA_2C Bandwidth Combination Set 0
2
CA_2C-29A - in table 5.6A.1-1 50 0
29 Yes Yes
2 Yes Yes Yes Yes
CA_2A-30A - 30 0
30 Yes Yes
See CA_2C in Table 5.6A.1-1 Bandwidth
2
CA_2C-30A - combination set 0 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
3
CA_3C-5A - in Table 5.6A.1-1 in 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 - See CA_7B bandwidth combination set 0 40 0
7
in table 5.6A.1-1
3 Yes Yes Yes Yes
See CA_7C Bandwidth combination set 1 60 0
7
in table 5.6A.1-1
CA_3A-7C -
3 Yes Yes Yes Yes
See CA_7C Bandwidth combination set 2 60 1
7
in table 5.6A.1-1
See CA_3C Bandwidth Combination Set 0
3
CA_3C-7A - in table 5.6A.1-1 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
50
Set 0 in table 5.6A.1-3 0
CA_3A-3A- 8 Yes Yes
-
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
CA_3A-20A CA_3A-20A 3 Yes Yes Yes Yes
30 0
20 Yes Yes
3 Yes Yes Yes Yes 40 1
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 149/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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 - 40 See CA_40C Bandwidth Combination Set 60 0
1 in Table 5.6A.1-1
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
4 Yes Yes
20 0
5 Yes Yes
CA_4A-5A -
4 Yes Yes Yes Yes
30 1
5 Yes Yes
See CA_4A-4A Bandwidth Combination
CA_4A-4A- 4
- Set 0 in table 5.6A.1-1 50 0
5A
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-
- 4 Yes Yes 40 0
7A
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
4 See CA_4A-4A Bandwidth Combination
CA_4A-4A-
- Set 0 in Table 5.6A.1-3 50 0
12A
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-12B - 12 See CA_12B Bandwidth Combination Set 35 0
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
4 See CA_4A-4A Bandwidth Combination
CA_4A-4A-
- Set 0 in Table 5.6A.1-3 50 0
13A
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
CA_5A-30A - 5 Yes Yes 20 0
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 150/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
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
7 Yes Yes Yes Yes
CA_7A-12A - 30 0
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
See CA_7B bandwidth combination set 0
7
CA_7B-28A - in table 5.6A.1-1 40 0
28 Yes Yes Yes Yes
See CA_7C bandwidth combination set 2
7
CA_7C-28A - in table 5.6A.1-1 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 - See CA_41C bandwidth combination set 2 50 0
41
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 - See CA_42C Bandwidth Combination Set 55 0
42
0 in Table 5.6A.1-1
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 - See CA_42C Bandwidth Combination Set 55 0
42
0 in Table 5.6A.1-1
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 - See CA_41C Bandwidth Combination Set 60 0
41
1 in Table 5.6A.1-1
25 Yes Yes Yes Yes
CA_25A-41D - See CA_41D Bandwidth Combination Set 80 0
41
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 - See CA_41C Bandwidth Combination Set 55 0
41
1 in Table 5.6A.1-1
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 151/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
29 Yes Yes
CA_29A-30A - 20 0
30 Yes Yes
38 Yes Yes
CA_38A-40A - 40 0
40 Yes Yes
CA_38A-40A- 38 Yes Yes
- 60 0
40A 40 See CA_40A-40A in Table 5.6A.1-3
38 Yes Yes
CA_38A-40C - 40 See CA_40C Bandwidth Combination Set 60 0
0 in Table 5.6A.1-1
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
39 See CA_39C Bandwidth Combination Set
CA_39C-41A - 0 in Table 5.6A.1-1 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 See CA_42C Bandwidth Combination Set 60 0
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 3: For the supported CC bandwidth combinations, the CC downlink and uplink bandwidths are equal.
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)
E-UTRA CA configuration / Bandwidth combination set
Maximum
Uplink CA E- Bandwidth
E-UTRA CA 1.4 3 5 10 15 20 aggregated
configurations UTRA combination
Configuration MHz MHz MHz MHz MHz MHz bandwidth
(NOTE 5) Bands set
[MHz]
1 Yes Yes Yes Yes
3 Yes Yes Yes Yes 50 0
5 Yes Yes
CA_1A-3A-5A -
1 Yes Yes
3 Yes Yes Yes Yes 40 1
5 Yes Yes
1 Yes Yes Yes Yes
3 Yes Yes Yes Yes 50 0
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
CA_1A-3A-
- 3 Yes Yes Yes Yes 55 0
19A
19 Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-3A-
- 3 Yes Yes Yes Yes 50 0
26A
26 Yes Yes
CA_1A-3A- 1 Yes Yes Yes Yes
20A (NOTE - 3 Yes Yes Yes Yes 60 0
4) 20 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-3A-
- 3 Yes Yes Yes Yes 60 0
28A
28 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-3A-
- 3 Yes Yes Yes Yes 60 0
42A
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
CA_1A-7A- 1 Yes Yes Yes Yes
20A (NOTE - 7 Yes Yes Yes 50 0
4) 20 Yes Yes
1 Yes Yes Yes Yes
CA_1A-7A-
- 7 Yes Yes Yes 55 0
28A
28 Yes Yes Yes
1 Yes Yes Yes Yes
18 Yes Yes Yes 45 0
CA_1A-18A- 28 Yes Yes
-
28A 1 Yes Yes Yes Yes
18 Yes Yes 40 1
28 Yes Yes
CA_1A-19A- - 1 Yes Yes Yes Yes 50 0
21A 19 Yes Yes Yes
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 152/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
21 Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-19A-
- 19 Yes Yes Yes 55 0
42A
42 Yes Yes Yes Yes
1 Yes Yes Yes Yes
CA_1A-21A-
- 21 Yes Yes Yes 55 0
42A
42 Yes Yes Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-5A - 4 Yes Yes Yes Yes 50 0
5 Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-
- 4 Yes Yes Yes Yes 50 0
12A
12 Yes Yes
2 See CA_2A-2A Bandwidth Combination
CA_2A-2A- Set 0 in Table 5.6A.1-3
- 70 0
4A-12A 4 Yes Yes Yes Yes
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A- 4 See CA_4A-4A Bandwidth Combination
- 70 0
4A-12A Set 0 in Table 5.6A.1-3
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-
- 4 Yes Yes Yes Yes 50 0
13A
13 Yes
2 Yes Yes Yes Yes
CA_2A-4A-
- 4 Yes Yes Yes Yes 50 0
29A
29 Yes Yes
2 Yes Yes Yes Yes
CA_2A-4A-
- 4 Yes Yes Yes Yes 50 0
30A
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-
- 5 Yes Yes 40 0
12A
12 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-
- 5 Yes Yes 40 0
13A
13 Yes
2 Yes Yes Yes Yes
CA_2A-5A-
- 5 Yes Yes 40 0
29A
29 Yes Yes
2 Yes Yes Yes Yes
CA_2A-5A-
- 5 Yes Yes 40 0
30A
30 Yes Yes
2 See CA_2C in Table 5.6A.1-1 Bandwidth
CA_2C-5A- combination set 0
- 60 0
30A 5 Yes Yes
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-12A-
- 12 Yes Yes 40 0
30A
30 Yes Yes
2 See CA_2C in Table 5.6A.1-1 Bandwidth
CA_2C-12A- combination set 0
- 60 0
30A 12 Yes Yes
30 Yes Yes
2 Yes Yes Yes Yes
CA_2A-29A-
- 29 Yes Yes 40 0
30A
30 Yes Yes
2 See CA_2C in Table 5.6A.1-1 Bandwidth
CA_2C-29A- Combination set 0
- 60 0
30A 29 Yes Yes
30 Yes Yes
3 Yes Yes Yes
7 Yes Yes 40 0
8 Yes Yes
CA_3A-7A-8A -
3 Yes Yes Yes Yes
7 Yes Yes Yes 50 1
8 Yes Yes
3 Yes Yes Yes Yes
CA_3A-7A-
- 7 Yes Yes Yes 60 0
20A
20 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-7A-
- 7 Yes Yes Yes Yes 60 0
28A
28 Yes Yes Yes Yes
3 Yes Yes Yes Yes
CA_3A-19A-
- 19 Yes Yes Yes 55 0
42A
42 Yes Yes Yes Yes
4 Yes Yes Yes Yes
CA_4A-5A-
- 5 Yes Yes 40 0
12A
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-5A-
- 5 Yes Yes 40 0
13A
13 Yes
4 Yes Yes Yes Yes
CA_4A-5A-
- 5 Yes Yes 40 0
30A
30 Yes Yes
CA_4A-7A- - 4 Yes Yes 40 0
12A 7 Yes Yes Yes Yes
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 153/154
18/11/2019 ZTE LTE FDD Carrier Aggregation Feature Guide
12 Yes Yes
4 Yes Yes Yes Yes
CA_4A-12A-
- 12 Yes Yes 40 0
30A
30 Yes Yes
4 Yes Yes Yes Yes
CA_4A-29A-
- 29 Yes Yes 40 0
30A
30 Yes Yes
7 Yes Yes Yes
CA_7A-8A-
- 8 Yes Yes Yes 40 0
20A
20 Yes Yes
19 Yes Yes Yes
CA_19A-21A- -
21 Yes Yes Yes 50 0
42A
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 3: For the supported CC bandwidth combinations, the CC downlink and uplink bandwidths are equal.
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.
NOTE 5: Uplink CA configurationsare the configurations supported by the present release of specifications.
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))
E-UTRA CA configuration / Bandwidth combination set
Component carriers in order of
increasing carrier frequency Maximum
Uplink CA Bandwidth
E-UTRACA aggregated
configurations Channel Channel Channel combination
configuration bandwidths bandwidths bandwidths bandwidth
(NOTE 1) set
for carrier for carrier for carrier [MHz]
[MHz] [MHz] [MHz]
5, 10, 15, 5, 10, 15,
CA_2A-2A - 40 0
20 20
5, 10, 15, 5, 10, 15,
40 0
20 20
CA_3A-3A -
5, 10, 15,
5, 10 30 1
20
5, 10, 15, 5, 10, 15,
CA_4A-4A CA_4A-4A 40 0
20 20
5 15
10 10, 15
CA_7A-7A - 40 0
15 15, 20
20 20
CA_23A-
- 5 10 15 0
23A
5, 10 5, 10 20 0
CA_25A-
- 5, 10, 15, 5, 10, 15,
25A 40 1
20 20
CA_40A-
- 10, 20 10, 20 40 0
40A
10, 15, 20 10, 15, 20 40 0
CA_41A-
- 5, 10, 15, 5, 10, 15,
41A 40 1
20 20
See CA_41C Bandwidth
CA_41A- 5, 10, 15,
- Combination Set 1 60 0
41C 20
inTable 5.6A.1-1
See CA_41C Bandwidth
CA_41C- 5, 10, 15,
- Combination Set 1 60 0
41A 20
inTable 5.6A.1-1
CA_42A- 5, 10, 15, 5, 10, 15,
- 40 0
42A 20 20
See CA_42C Bandwidth
CA_42A- 5, 10, 15,
- Combination Set 0 60 0
42C 20
inTable 5.6A.1-1
See CA_42C Bandwidth
CA_42C- 5, 10, 15,
- Combination Set 0 60 0
42A 20
inTable 5.6A.1-1
NOTE 1: Uplink CA configurationsare the configurations supported by the present release of
specifications.
127.0.0.1:8890/web/index.html#?pid=Lib20180326fdd35&pv=R1_1 154/154