4CC Carrier Aggregation - Alex
4CC Carrier Aggregation - Alex
4CC Carrier Aggregation - Alex
Feature Description
© Ericsson AB 2016, 2017. All rights reserved. No part of this document may
be reproduced in any form without the written permission of the copyright
owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
Contents
2 Feature Operation 4
2.1 Network Requirements 4
2.2 Feature Operation Sequence Diagram 4
2.3 Process Steps 5
3 Parameters 8
3.1 Feature Configuration Parameters 8
3.2 Affected Parameters 8
4 Network Impact 9
4.1 Capacity 9
4.2 Coverage 9
4.3 Mobility 9
6 Performance 12
6.1 Key Performance Indicators 12
6.2 Counters 12
6.3 PM Events 12
Summary
No of TX 64-QAM 256-QAM
Layers
TDD UL/DL 2 110 220 330 440 143 285 428 580
Configuration 2
(SSF7) 4 213 426 N/A N/A 286 N/A N/A N/A
TDD UL/DL 2 108 216 324 432 139 279 418 556
Configuration 2
(SSF6) 4 208 416 N/A N/A 279 N/A N/A N/A
• 3GPP TS 36.331
• 3GPP TS 36.211
• 3GPP TS 36.212
• 3GPP TS 36.213
• 3GPP TS 36.101
• Carrier Aggregation
• 256-QAM Downlink
• Elastic RAN
2 Feature Operation
• A license key for feature Dynamic SCell Selection for Carrier Aggregation
must be activated.
1 UL & 1 DL CCs
CA UE with 4CC CA
1 UL & 1 DL CCs
CA UE with 2CC CA
1 UL & 1 DL CCs
CA UE with 3CC CA
1 UL & 1 DL CCs
UE without CA
L0001478A
• The first, second and third SCells are configured using blind selection. The
initial selection and configuration of SCells depends on the attribute
CarrierAggregationFunction.sCellSelectionMode :
– If sCellSelectionMode is set to
ACK_SEQUENTIAL_SCell_SELECTION, SCells are selected and
configured in sequence. A1 is configured per SCell to confirm the
coverage. The second SCell is only selected once the first SCell has
been concluded as being in coverage and the third SCell is only
selected once the second SCell has been concluded as being in
coverage.
– If sCellSelectionMode is set to
ACK_SIMULTANEOUS_SCell_SELECTION, three SCells are selected
and configured simultaneously. A1 is configured per SCell to confirm
the coverage.
– If sCellSelectionMode is set to
UN_ACK_SIMULTANEOUS_SCell_SELECTION, three SCells are
selected and configured simultaneously. This mode assumes SCells
to have good coverage. To reduce RRC overhead no A1
measurements are configured.
For the initial SCell selection of the first, second and third SCell, please
see Dynamic SCell Selection for Carrier Aggregation.
• The maximum TX layers that both the eNodeB and UE can support are
reconfigured on each component carrier. If the maximum allowed TX
layers are changed on a component carrier due to other SCell being
added or removed, they are reconfigured at the same time along with
SCell reconfiguration.
• All three SCells are implicitly deconfigured upon release of the UE.
For more details, see Dynamic SCell Selection for Carrier Aggregation.
• Need based:
• Coverage based:
CarrierAggregationFunction.sCellDeactOutOfCoverageTimer >=
MAX(160, 2 * CarrierAggregationFunction.sCellDeactProhibitTimer + 80) ms
or:
CarrierAggregationFunction.sCellDeactOutOfCoverageTimer = -1
• Potential throughput:
3 Parameters
• CarrierAggregationFunction.caPreference
• EUtranCellFDD.noOfPucchFormat3PrbPairs
• EUtranCellTDD.noOfPucchFormat3PrbPairs
4 Network Impact
4.1 Capacity
A UE configured with an SCell consumes more resources than a UE
connected only to a PCell. For each additional SCell configured a new
resource is allocated at PCell. However, it is counted as one from a connected
UE license perspective. As the 4CC DL Carrier Aggregation Extension feature
allows up to three configured SCells per UE, the loading limit is reached by
fewer UEs than previously, with 2CC, or 3CC.
4.2 Coverage
The feature does not have any impact on coverage.
4.3 Mobility
The feature has no impact on mobility since mobility is based on PCell
coverage.
• Carrier Aggregation
Feature Description
Carrier Aggregation-Aware IFLB The Carrier Aggregation-Aware IFLB feature aims to improve
average system throughput by efficient distribution of carrier
aggregation capable users to cells where the carrier aggregation
capability can be utilized, or utilized in a better way. This leads
to better throughput for Carrier Aggregation (CA)-capable UEs.
Dynamic SCell Selection for Carrier The feature is based on Carrier Aggregation feature and has the
Aggregation following additional functionality: A cell used as PCell can have
multiple cells as SCell candidates. Based on UE measurements
and the SCell selection algorithm, the SCell of a UE is
dynamically configured or deconfigured.
Supplemental Downlink for Carrier The main benefits of Supplemental Downlink for Carrier
Aggregation Aggregation are as follows: Spectrum utilization on bands
defined as downlink only, for example Band 29 using Carrier
Aggregation. Increased downlink User Equipment (UE) peak
throughput. Increased aggregated downlink throughput and
capacity.
3CC DL Carrier Aggregation The benefit of the 3CC DL Carrier Aggregation Extension
Extension feature is the capability to transmit data to a single UE on three
carriers simultaneously. In addition, support is added for the new
band combination signaling according to 3GPP TS 36.331.
Uplink Carrier Aggregation The Uplink Carrier Aggregation feature enables a User
Equipment (UE) to transmit data on more than one carrier
simultaneously. This means increased uplink throughput across
the coverage area, more efficient use of scattered spectrum and
higher capacity. The feature is specified by 3GPP.
Cross-DU Carrier Aggregation This feature allows carrier aggregation to be used with multi-DU
Support eNodeB configurations where the primary and secondary cells
are terminated on different DUs. This can be used to support
carrier pooling deployments. Some carriers are terminated on
one DU and other carriers on a second DU in a multi-DU
configuration, without losing support for carrier aggregation.
Multiple Frequency Band Indicators The MFBI feature will: Simplify frequency band compatibility for
operators and UE vendors. Enable the cell to accommodate UE
which supports the physical frequency but not the primary band
of the cell. Allow efficient use of license spectrum by allowing
harmonized 3GPP bands and legacy band in the same cell.
Increase the number of UE which are compatible with the
operators network, including roaming UE.
Elastic RAN The Elastic RAN feature enables high speed, low latency
interaction between eNodeBs, such that eNodeBs can be added
as required to increase the capacity and cell interaction scope.
Elastic RAN eliminates fixed-sized coordination boundaries and
scalability constraints, allowing the sets of cells that can be
considered for use as secondary cells to be expanded across
multiple eNodeBs.
6 Performance
6.2 Counters
The following counters are associated with this feature:
• EUtranCellFDD.pmCaCapableDlSum
• EUtranCellTDD.pmCaCapableDlSum
• EUtranCellFDD.pmCaConfiguredDlSum
• EUtranCellTDD.pmCaConfiguredDlSum
• EUtranCellFDD.pmCaActivatedDlSum
• EUtranCellTDD.pmCaActivatedDlSum
• EUtranCellFDD.pmCaScheduledDlSum
• EUtranCellTDD.pmCaScheduledDlSum
• EUtranCellFDD.pmCaActivatedDlFddTddSum
For a full list with detailed information about counters, see the list files in the
List Files library folder.
6.3 PM Events
Table 4 lists PM events related to this feature:
Table 4 Events
Event Event Parameter
INTERNAL_EVENT_UE_CAPABILITY EVENT_PARAM_UE_CAP_CATEGORY
INTERNAL_PER_CELL_TRAFFIC REPORT EVENT_PARAM_CA_PF3_ASSIGNED_1...12
INTERNAL_PER_UETR_CELL_TRAFFIC_RE EVENT_PARAM_CA_PF3_ASSIGNED_1...12
PORT
For a full list with detailed information about PM events, see the list files in the
List Files library folder.
Prerequisites
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.
Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week.
This ensures there is troubleshooting data available if something goes wrong.
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.