Professional Documents
Culture Documents
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
3 Feature Operation 5
3.1 Network Requirements 5
4 Parameters 6
4.1 Feature Configuration Parameters 6
4.2 Affected Parameters 6
5 Network Impact 7
5.1 Coverage 7
7 Performance 10
7.1 KPIs 10
7.2 Counters 10
7.3 Events 10
Summary
The Carrier Aggregation FDD-TDD feature combines the best of FDD and
TDD spectrum. It allows DL traffic to be offloaded on the TDD spectrum
without being constrained by the limited UL application coverage of a TDD
carrier. Instead, a UE can be served by the larger range FDD UL while still
enjoying the substantial DL performance boost provided by the TDD carrier.
FDD Region
DL Throughput [Mbps]
TDD UL cell-edge
FDD cell-edge
Distance L0001091B
In sites where operators have access to both FDD and TDD spectra, the
Carrier Aggregation FDD-TDD feature enables both spectrum resources to be
used. The use of both spectrum resources improves system performance and
end-user experience.
• Extends TDD DL coverage and provides user data rate gains by using the
UL of FDD carriers. As UL HARQ feedback is sent on FDD carriers, TDD
HARQ bundling is not required.
• Increases user peak throughput by combining FDD and TDD data rates.
• FDD-TDD 2CC DL CA, where the PCell is FDD and the SCell is TDD.
• FDD-TDD 3CC DL CA, where the PCell is FDD and the SCells can both
be TDD, or a mix of FDD and TDD.
• Dynamic switching between TM3 and TM4 is not available for SCells.
• 3GPP TS 36.101
• 3GPP TS 36.211
• 3GPP TS 36.212
• 3GPP TS 36.213
• 3GPP TS 36.321
• 3GPP TS 36.331
• Carrier Aggregation
The Carrier Aggregation (CA) FDD-TDD feature allows TDD cells to be used
as Secondary Cells (SCell) for an FDD Primary Cell (PCell).
• Carrier Aggregation
In addition, some or all of the following features can be required. This depends
on the desired number of SCell candidates, number of DUs within the
eNodeB, and the number of carriers to be aggregated:
3 Feature Operation
– Baseband 5212
– Baseband 5216
– Baseband 6303
– Baseband 6502
– Baseband 6620
– Baseband 6630
• A license key for feature FDD and TDD on Same eNodeB must be
activated.
4 Parameters
5 Network Impact
This section describes how the Carrier Aggregation FDD-TDD feature impacts
the network functions and capabilities.
5.1 Coverage
This section provides information on the impact of the feature on network
coverage.
As a result of Carrier Aggregation FDD-TDD using the FDD UL carrier for TDD
SCells, a significant coverage gain is experienced by TDD cells.
This section describes how the Carrier Aggregation FDD-TDD feature affects
other features and functions.
7 Performance
7.1 KPIs
This feature has no associated Key Performance Indicators (KPIs).
7.2 Counters
Table 3 lists the counters associated with the Carrier Aggregation FDD-TDD
feature.
Table 3 Counters
Counter Description
pmCaCapableDlFddTddSum Shows the number of UEs capable of FDD-TDD Carrier
Aggregation, and their number of corresponding SCells.
pmCaConfiguredDlFddTddSum Shows the number of configured UEs capable of FDD-TDD
Carrier Aggregation, and their number of corresponding SCells.
pmCaActivatedDlFddTddSum Shows the number of activated UEs capable of FDD-TDD Carrier
Aggregation, and their number of corresponding SCells.
7.3 Events
This feature has no associated events.
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.