UL CA

Feature Presentation to Customer
SRAN17.A ORF ARCEP 2019

LTE1092– UL Carrier Aggregation 2CC
MN/CS/RNS
• Version : 1.0
• Date : 20/12/2018
• Author : Raja HASNI (raja.hasni@nokia.com)
1 © Nokia 2018 Confidential

LTE1092- UL Carrier Aggregation 2CC
Table of contents
Overview & Feature Features Configuration Performance

Expected Description Interactions Management Evaluation
Benefits & Pre-
requisites
Validation KINSEI results Restrictions & Conclusion

Strategy Issues

Overview &
Expected Benefits
Table of contents

Overview & Expected benefits
Overview
LTE1092 FDD Uplink Carrier Aggregation 2CC introduces uplink Carrier Aggregation with 2 component
carriers.
• Aggregated bandwidth up to 40MHz
• UL CC is used in combination with DL CC with either 2 or 3 DL carriers
• UL and DL carrier aggregation share the same Pcell
• Scells can be DL only or UL/DL but they cannot be uplink only
• Only non-GBR data is transferred across the secondary cell
FDD UL CA
capable UE

Expected benefits
Primary aim of the feature is to increase average and peak uplink user throughput via sending user data
simultaneously over two FDD component carriers.
Maximum achievable UL peak user throughput can be even two times higher comparing to non-CA case.
1CC (20MHz) 2CC (20+20MHz) 1CC (10MHz) 2CC (10MHz+10MHz) 2CC (20MHz + 10MHz)
L1 Throughput 66.59 Mbps 133.18 Mbps 29.3 Mbps 58.59 Mbps 95.86 Mbps
FTP 63.11 Mbps 122.85 Mbps 27.83 Mbps 54.2 Mbps 88.52 Mbps
UDP 63.68 Mbps 124 Mbps 28.06 Mbps 54.66 Mbps 89.33 Mbps

Supported band combinations (1/2)
• All combinations of 5/10/15/20 MHz channel bandwidths are supported by LTE1092 FDD UL CA 2CC
- It gives possibility to use up to 40 MHz of spectrum by 2CC UL CA-capable UEs
• Certain band combinations are supported by LTE1092:
2CC DL + 2CC UL 3CC DL + 2CC UL
3GPP Bands Notes 3GPP Bands Notes 3GPP Bands Notes 3GPP Bands Notes
1+3 - 3+3 C 4 + 17 - DL (1 + 3 + 5) + UL (1 + 3, 1 + 5, 3 + 5) -
1+5 BCS 0, 1 3+5 BCS 0, 1, 2 5 + 12 - DL (1 + 3 + 8) + UL (1 + 3, 1 + 8, 3 + 8) -
1+7 - 3+7 - 5 + 17 - DL (1 + 5 + 7) + UL (1 + 5, 1 + 7, 5 + 7) -
1+8 BCS 0, 1, 2 3+8 BCS 0, 1, 2 7+7 C DL (1 + 18 + 28) + UL (1 + 18, 1 + 28, 18 + 28) -
1 + 18 BCS 0, 1 3 + 20 BCS 0, 1 7 + 20 BCS 0, 1 DL (2 + 4 + 12) + UL (2 + 4, 4 + 12) -
1 + 28 BCS 0, 1 4+4 NC 7 + 28 - DL (2 + 5 + 13) + UL (2 + 13) -
2+2 C 4+5 - 18 + 28 - DL (3 + 3 + 7) + UL (3 + 3, 3 + 7) Band 3 C
2+4 BCS 0, 1, 2 4+7 - DL (3 + 7 + 7) + UL (3 + 7, 7 + 7) Band 7 C
2 + 12 - 4 + 12 BCS 0, 1, 2, 3, 4 DL (3 + 7 + 20) + UL (3 + 7, 3 + 20, 7 + 20) -
2 + 13 BCS 0, 1 4 + 13 BCS 0, 1 DL (4 + 5 + 13) + UL (4 + 13) -
BCS - Bandwidth Combination Set, C – contiguous carriers deployment, NC – non-contiguous carriers deployment

Supported band combinations (2/2)
• Additional band combinations are introduced by feature LTE3213 Additional UL Carrier Aggregation
band combinations:
3CC DL + 2CC UL
3GPP Bands Notes
DL (1 + 3 + 7) + UL (1 + 3, 1 + 7, 3 + 7) -
DL (2 + 12 + 12) + UL (2 + 12) -
DL (2 + 12 + 30) + UL (2 + 12) -
DL (4 + 12 + 30) + UL (4 + 12) -
DL (4 + 12 + 12) + UL (4 + 12) -

Expected benefits
Before After
• There was no possibility to transmit UL • There is possibility to transmit UL data
data on multiple FDD carriers – all UL on two FDD Component Carriers (CCs)
traffic was handled only on a single • Performance of UEs using UL Carrier
carrier Aggregation is improved comparing to
• Operators with fragmented spectrum legacy deployments without UL CA
could not use it in more efficient way • Part of UL traffic is handled by
Secondary Cell introducing ‘soft load
balancing’ in the network
• Possibility to use fragmented spectrum
more efficiently

Feature Description
Table of contents

Feature Description
Activation
LTE1092 feature is activated by the parameter actULCAggr.
The following conditions must be fulfilled:

• actDLCAggr must be set to 'true‘
• ulCaPathlossThr must be configured
• caMinUlAmbr must be configured
• caUlIntraBandAmpr must be configured
• dlCaPreferred must be configured

Feature Description
Scell candidates
LNBTS
In LTE1092, only the cells that are already
configured as potential SCells for DL CA can be
used for UL CA PCell SCell SCell
There is no possibility to configure cell as an SCell for SCell PCell SCell
UL CA only
SCell SCell PCell
CAREL objects are used to define secondary cell
LNCEL LNCEL LNCEL
candidates for both uplink and downlink lcrId lcrId lcrId
No new parameters are created within the CAREL
object CAREL
lcrId
CAREL
lcrId
Only cells that are already configured

for DL CA can be used for UL CA

Feature Description
Parameter Consistency Check
All of the parameter consistency checks for downlink Carrier Aggregation must be satisfied, i.e. some
parameters must have equal settings in the Pcell and Scell(s):
• riEnable (Rank indication reporting enable)
• periodicCqiFeedbackType (Periodic CQI feedback type)
• cqiPerSbCycK (Periodic CQI subbands cycles)
• caSchedFairFact (Carrier Aggregation scheduling fairness control factor)
In addition, the following have to be satisfied within the Pcell:

• deltaPucchShift (Delta cyclic shift for PUCCH) ≤ 2
• n1PucchAn (ACK/NACK offset) must be equal to 10 or ≥ 72 (current ORF value =36)

Feature Description
UE Capability
UL CA capability of the given UE is analyzed by the eNB if:
− UE accessStratumRelease is rel10 or higher
− at least one valid band combination could be extracted from:
− supportedBandCombination-r10 or
− supportedBandCombinationAdd-r11
The UE is treated as UL CA-capable if at least one valid band combination can be obtained from ca-
BandwidthClassUL-r10
UL CA capabilities do not impact DL CA capabilities meaning that UE may be DL 2CC or 3CC CA-capable,
being at the same time not capable for UL 2CC CA
However, UE cannot be UL CA-capable without being DL CA-capable at the same time

Feature Description
Initial Checks
Secondary Cell could be configured for UL CA for capable UE only if:
− UE UL Aggregate Maximum Bit Rate (AMBR) is not lower than configured minimum AMBR for which UL CA is allowed
in the given site that is:
• UE-AMBR(UL) ≥ caMinUlAmbr * 1000
− Particular SCell will be also configured for DL Carrier Aggregation basing on band/bandwidth combinations
supported by the UE and eNB
− TTI bundling has not been started for this UE. Simultaneous UE operation in TTI Bundling mode and CA mode is
forbidden
− Initial Context Setup Request does not contain CS Fallback Indicator
If all of the above conditions are fulfilled, Radio Admission Control is checked

Feature Description
Admission Control
All UL CA UEs are already also a DL CA ones, meaning that all of the legacy admission control conditions
must be satisfied (no new restrictions are introduced by LTE1092):
• overall max number of CA UEs in the cell (maxNumCaConfUe)
• max number of CA UEs configured with 2 component carriers (maxNumCaConfUeDc)
• max number of CA UEs configured with 3 component carriers (maxNumCaConfUe3c)
Adding a secondary cell leads to:

• the number of RRC connections in the secondary cell increasing by 1
• no increase in the number of active UE in the secondary cell
• consequently, admission control checks whether the number of RRC connections (as set by the legacy
maxNumRrc parameter) would be exceeded

Feature Description
Scell Addition
SCell(s) for DL and UL Carrier Aggregation are configured using single (joint configuration)
RRC:RRCConnectionReconfiguration message that is sent to the UE
sCellToAddModList-r10
sCellIndex-r10 1,
cellIdentification-r10
physCellId-r10 333,
dl-CarrierFreq-r10 3000
,
radioResourceConfigCommonSCell-r10
nonUL-Configuration-r10
dl-Bandwidth-r10 n100,
antennaInfoCommon-r10
antennaPortsCount an4
,
…
,
ul-Configuration-r10
ul-FreqInfo-r10
ul-CarrierFreq-r10 21000,
ul-Bandwidth-r10 n100,
additionalSpectrumEmissionSCell-r10 1
,

Feature Description
DL CA vs UL CA PCell
SCell 1
In current implementation, eNB supports:
SCell 2
• 3CCDL CA + 2CC UL CA
3CC DL CA
• 4CC DL CA +
2CC UL CA
But does not support:
• 4CC DL CA + 2CC UL CA Add another DL SCell due to
high DL non-GBR buffer state
eNB must decide which of the supported dlCaPreferred

configurations to allocate:
DL and UL DL only
• 3CC DL + 2CC UL (maximise UL throughput)
• 4CC DL (maximise DL throughput) PCell PCell
SCell 1 SCell 1
Preferred approach can be chosen using
dedicated dlCaPreffered parameter SCell 2 SCell 2
3CC DL CA SCell 3
+
2CC UL CA 4CC DL CA

Feature Description
Scell Addition – state machine
A general state machine for secondary cell addition is shown below. It applies only if
LNBTS:numTxWithHighNonGbr is not set to 0.

Feature Description
Scell Activation (1/3)
Legacy SCell activation methods remain applicable:
• Blind
• Buffer Based
• Buffer Based Stepwise
Selection is made using the legacy parameter sCellActivationMethod
As LTE1092 supports only one SCell in the UL, buffer based stepwise will behave in the same way as
buffer based.
Both DL and UL non-GBR buffer status is monitored separately for each UE

• SCell is activated if any of the buffers exceeds its dynamically calculated threshold (DL only, UL
only or both at the same time)

Feature Description
Both the uplink and downlink buffer status are monitored to determine whether or not secondary cell
activation is required

Nokia Internal Use
Feature Description
Activation of SCell is always done for both DL and UL directions at the same time using
single Activation/Deactivation MAC CE
• There is no possibility to activate SCell for DL only or UL only CA
Set to 1 for SCell activation

NOT USED
Activation of the Secondary Cell means for the UE that:

• PDCCH of that SCell monitored in order to find potential DL and UL grants
• PHICH of that SCell is monitored in order to receive HARQ ACK/NACK feedback for UL transmissions
• CQI/PMI/RI reporting for the SCell is performed in a specific way

Feature Description
Data Division
The fact of having the SCell activated does not necessarily mean that it will be actually used in every TTI
Still, only non-GBR data buffer status reported by the UE in extended Buffer Status Reports (eBSR) is
used during data division factors calculation to be applied for UL transmission in PCell and SCell
Non-GBR data division factor for UL traffic is calculated independently from DL division factor, however
(as in case of 2CC DL CA scenario), it is limited to the range of 10…90% to avoid possible deadlock
• As in case of DL CA, if any of the serving cells succeeds in allocating all of its UL data share in current TTI (while the
other cell does not), it will be given additional 10% of the throughput share in next TTI
PCell SCell
(UL traffic) (UL traffic)
0% 10% Division factor 90% 100%

Feature Description
Data Division
Dynamic UL data share among PCell and SCell is calculated only when path loss for both carriers is not
higher than certain configurable threshold (ulCaPathlossThr).
• otherwise all UL traffic is served by a single CC (the one with path loss lower than the configured threshold) what
assures that power-limited UEs will not suffer degraded UL throughput by transmitting on both CCs
• in case path loss observed in both cells exceeds configured threshold, only the PCell is used for UL data
transmission

Feature Description
Scheduler – Fairness factor
In LTE1092 (similarly to legacy DL CA features), UL scheduling weights of the UEs in CA
mode are modified as well
• Modification consists of multiplying the original weight in both PCell and SCell by the additional
component (2 – caSchedFairFact)
0 1
caSchedFairFact
Lower value  probability of serving Higher value  more fair treatment
CA UEs in the given TTI is increased of CA and non-CA UEs – specific
at the cost of non-CA UEs boost given to CA UEs is limited
Setting of the scheduling fairness factor (caSchedFairFact) is common for both DL and UL
Carrier Aggregation as the same parameter is used

Feature Description
Scheduler – data types
In LTE1092 (as in legacy CA features) all decisions related to the SCell handling
(activation/deactivation, data share calculation, etc.) are based on the non-GBR buffer state
only
However, it is up to the UE to decide what kind of data (non-GBR, GBR, SRB) will be finally
sent on assigned resources
• It may happen that resources assigned to the UE on the SCell will finally carry not only non-GBR
data but also UL GBR or SRB data

Feature Description
Scell Deactivation
Active Secondary Cell is deactivated if:
• there is no data scheduled for particular SCell during specific timer duration
(sCellDeactivationTimerEnb)
• no positive HARQ feedback was received during sCellDeactivationTimerEnb
If sCellDeactivationTimerEnb = 'infinity', the SCell is not deactivated and the timer is not
handled at all
Secondary Cell configured for DL and UL Carrier Aggregation handles separate deactivation
timers for each link
• Decision of SCell deactivation is taken only if both deactivation timers (for DL and UL
transmissions separately) have expired

Feature Description
Scell Deactivation
SCell deactivation triggered only when both DL and UL deactivation timers have expired
PDSCH on SCell
DL timer expired but

SCell is not deactivated
as the UL timer has still
SCell DL deactivation timer not expired
time
SCell deactivation
PUSCH on SCell
SCell UL deactivation timer
time

Feature Description
Scell Deactivation
SCell deactivation is done via Activation/Deactivation MAC CE
Set to 0 for cell deactivation
NOT USED
Deactivation means that:

• no transmission could be scheduled to the UE on the particular SCell
• UE stops sending periodic CSI reports related to the particular SCell
• UE stops monitoring SCell’s PDCCH and PHICH
Deactivated SCell can be activated again later on basing on the DL or UL non-GBR data
buffer status

Feature Description
Scell Release
Secondary cell is released if:
• RRC Connection is released
• TTI Bundling is about to be enabled
• a handovers is triggered (Secondary Cell is re-added at target cell)
• Inactivity timer expires
LTE1541: Advanced Scell Measurement Handling
• Radio conditions become poor

Feature Description
RRM impact – Uplink Control Information (UCI)
If SCell is configured for DL CA only, there are no changes to the Channel State Information
(CSI) or HARQ ACK/NACK reporting – it is done in exactly the same way as in legacy DL CA
features
In case SCell is configured for DL and UL CA, the way Uplink Control Information (UCI) is
sent, depends on the UE’s UL scheduling:
• UE is not scheduled for PUSCH transmission on any of the serving cells (PCell or SCell)
• UE transmits UCI using PUCCH on PCell
• UE is scheduled for UL transmission at least in the PCell

• UE transmits UCI using PUSCH on PCell
• UE is scheduled for UL transmission on SCell only

• UE transmits UCI using PUSCH on SCell

Feature Description
RRM impact – extended Buffer Status Report (eBSR)
• The ‘extended’ buffer Buffer Size Levels Extended Buffer Size Levels
size levels allow the UE to
report larger buffer
occupancies
• 3 000 000 bytes rather
than 150 000 bytes
• Increased buffer
occupancies are
associated with higher
throughputs
• Reporting range is still 0
to 63 so granularity of
values is reduced

Indicates if virtual report is present
MAC Control Element
Feature Description PUCCH report
RRM impact – Extended Power Headroom Report (PHR) Indicates presence of PHR
report for a specific carrier
• The ‘extended’ Power Headroom Report allows the
power headroom to be signaled for both primary and
secondary cells
• 1 primary cell and 1 secondary cell for LTE1092
• The UE can transmit the report on either carrier so it
must be exchanged between cells at the eNode B
• Power Headroom Report can be:
• Real: based upon an actual transmission on the serving cell
that is reporting. Based upon the number of PRB used to
transmit the message that includes the report
• Virtual: applicable to a serving cell that has no transmission
in the subframe in which the report is sent. Based upon the
reference format defined in 3GPP TS 36.213 (5.1.1.2).
Flagged by setting V = 1 PUSCH report
Indicates if power back-off is applied Transmit power capability
Features Interactions
& Pre-requisites
Table of contents

Interdependencies
LTE1092 FDD UL Carrier Aggregation 2CC
prerequisites LTE1089 DL Carrier Aggregation

LTE1332 DL Carrier Aggregation 40 MHz
LTE1562 Carrier Aggregation for multi-carrier eNBs
LTE1803 DL Carrier Aggregation 3CC 40 MHz
LTE1804 DL Carrier Aggregation 3CC 60 MHz
LTE1092 reuses logic and basic algorithms taken from legacy LTE1089 and
LTE1332 with extensions introduced in LTE1562 or LTE1803/1804.
All mentioned features are enabled with the same activation flag and as far
as DL Carrier Aggregation is required for UL Carrier Aggregation - they can
be treated as prerequisites for LTE1092.

Interdependencies
prerequisites LTE496 Support of QCI 2, 3 and 4

LTE587 Multiple GBR EPS Bearers per UE
LTE496 and LTE587 are required by LTE1092, so they should be treated as
prerequisites for UL Carrier Aggregation.

Interdependencies
prerequisites LTE2324 Network requested UE capabilities

With LTE2324, network can request UE to update available UE radio
capabilities if reported CA band combinations are not sufficient to
configure CA for the given UE.
It extends the number of signaled band combination from 128 to 384.
Without LTE2324, UE can signal up to 128 CA band combinations in its UE
radio capabilities. According to 3GPP, UE is supposed to report all
supported 2CC band combinations.
It may happen that 3CC band combinations used by the operator in its
network may not be a part of reported UE capabilities

Interdependencies
LTE2006 Flexible SCell selection
extensions
LTE1541 Advanced SCell measurement handling
LTE2275 PCell swap
LTE2233 N-out-of-M Carrier Aggregation
LTE2007 Inter-eNB Carrier Aggregation
All above features introduce means for more flexible selection and
handling of cells involved in Carrier Aggregation basing on additional
statistics, dedicated measurements or extended hardware configurations.
All PCell/SCell handling procedures will impact also UL SCells selection and
can be used for more flexible CA management.

Interdependencies
LTE42 DRX in RRC Connected mode
extensions
LTE473 Extended DRX
LTE585 Smart DRX
Cooperation of LTE1092 with DRX functionality is supported with some
certain dependencies in active time handling. The same active time
applies to all activated serving cells in both DL and UL.
LTE1113 eICIC macro
LTE1092 can be activated simultaneously with eICIC at the macro eNBs.
CA UEs are simply not scheduled in the TTIs which are used for Almost
Blank Subframes (ABS) transmission.

Interdependencies
limitations LTE2531 DL Carrier Aggregation 4CC

LTE2531 DL CA 4CC and LTE1092 can be activated simultaneously on the
eNB, however UEs that are configured with 4CC DL CA will not use 2CC UL
CA. There will be a possibility to configure (by a dedicated dlCaPreferred
parameter) if UE should remain configured with DL and UL CA or if it should
be reconfigured to DL CA only, but with higher number of Component
Carriers.
LTE907 TTI Bundling
UE which is configured with TTI bundling could not be configured with the
Secondary Cells – but features as such could run in BTS in parallel

Configuration
Management
Table of contents

Configuration management
Activation flag
MOC Parameter Description Class Range & Unit Recommended Value
The parameter activates uplink carrier

aggregation. The feature can only be activated in
addition to downlink carrier aggregation. 0: false
LNBTS actULCAggr On-line 1: UL_CA_without_smartSched 2:UL_CA_with_smartSched
If "UL_CA_with_smartSched" is activated, only UEs 2: UL_CA_with_smartSched
with pathloss less than ulCaPathlossThr could be
scheduled in multiple serving cells for uplink.

New Parameters (1/2)
This parameter excludes those UEs from uplink

carrier aggregation, whose UE-AMBR Uplink is below
On-line 64...150000 kb/s, step 1
LNBTS caMinUlAmbr the caMinUlAmbr threshold. Downlink carrier 512 kb/s
kb/s
aggregation is still possible for the UE when the DL
conditions are met.
Pathloss threshold for UE scheduled on single cell for

UL CA. When UE’s pathloss is larger than the On-line
LNBTS ulCaPathlossThr 70...140 dB, step 1 dB 100 dB
threshold, then this UE is only scheduled in single
cell.

New Parameters (2/2)
This parameter defines whether or not A-MPR values as defined

in Tables 6.2.4.A-1 and 6.2.4.A-2 of 3GPP 36.101 will be sent to
the UE.
If set to 'disabled',
A-MPR values will NOT be sent to the UE. 0: disabled
LNBTS caUlIntraBandAmpr On-line disabled (0)
1: enabled
If set to 'enabled',
A-MPR values will be sent for all bands where A-MPR is defined.
For bands where A-MPR is NOT defined, the parameter does
not apply.
The parameter defines the preference for SCell addition in case

of DL+UL carrier aggregation.
dlCaPreferred is used to decide whether to add an additional
downlink SCell when that additional DL SCell will result in an
existing DL+UL SCell being reconfigured as a DL only SCell.
0: DLonly
LNBTS dlCaPreferred dlCaPreferred = 'DLonly' On-line DLandUL (1)
1: DLandUL
the eNB will choose to add the additional DL SCell and
reconfigure the existing DL+UL SCell to DL only.
dlCaPreferred = 'DLandUL'
the eNB will choose to keep the existing DL+UL SCell and will
NOT add the additional DL Scell.

Related parameters
MOC Parameter Description Class Range & Recommended

Unit Value
The parameter activates the family of downlink carrier
aggregation features.
The feature allows higher UE downlink peak data rates by
Conditional BTS 0 (false), 1
LNBTS actDLCAggr aggregation of two cells. 1 (true)
restart (true)
eNB will dynamically decide dependent on the current and newly
required DSP deployment if eNB restart or dropping of all cells is
needed.
Threshold to limit the maximum number of carrier aggregation

configured UEs in a PCell (P-LNCEL);
UEs may have 1 PCell (P-LNCEL) and 1 or several SCell(s) (S-
LNCEL
maxNumCaConfUe LNCEL). On-line 0...400, step 1 48
_FDD
Carrier aggregated UEs with 1 or more SCell need more
resources than nonCA Ues (PUCCH and MAC PS);
Therefore limiting the amount of CA-UEs is necessary.

Related parameters
MOC Parameter Description Class Range & Recommended

Unit Value
configured UEs in a cell PCell (P-LNCEL); Dc (Double carrier)
indicates that these UEs have 1 PCell (P-LNCEL) and only 1 SCell
LNCEL
(S-LNCEL). On-line
_FDD maxNumCaConfUeDc 0...400, step 1 48
Carrier aggregated UEs with 1 SCell need double amount of UL
resources compared with single carrier UEs as long as UL
signalling is done only via PCell. That's why the information Dc is
relevant.

configured UEs in a PCell (P-LNCEL); 3c (3 carriers) indicates that
these UEs have 1 PCell (P-LNCEL) and 2 or more (up to 3) SCells
LNCEL
(S-LNCEL). On-line
_FDD maxNumCaConfUe3c 0...400, step 1 48
Carrier aggregated UEs with 2 or more SCell need a higher
amount of resources (PUCCH) compared with single carrier UEs
as long as UL signalling is done only via PCell. That's why the
information 3c is relevant.

Performance
Evaluation
Table of contents

Performance evaluation
Expected impact on KPIs
Feature impact How to measure

Improved mean and instantaneous UL UE throughput for To monitor UE throughput following dedicated KPIs may be
UEs with activated SCells (non-GBR data only) employed:
Gain depends on the overall network load – once the load is high, E-UTRAN Averaged IP scheduled Throughput in UL for QCIs 5
better performance (in terms of mean throughput) for CA UEs is no – 9 (LTE_5363a - LTE_5367a)
longer assured. To test achievable peak throughput values, network To verify peak UE throughput for the UEs with activated Secondary
has to be low loaded Cells it is recommended to perform drive tests
Higher achievable peak throughput in the sector PDCP_DATA_RATE_MAX_UL

All involved (paired) cells have to be analyzed jointly M8012C22
UL cell capacity improvements Average PDCP Layer Active Cell Throughput UL

It is not expected that major UL cell capacity improvements will be LTE_5289d
visible if CA is activated but for certain deployments and traffic
profiles some gains may be observed.
Impact on KPIs can be observed only if the number of UL 2CC capable UEs is high which is not currently
the case.

Performance evaluation
New counters
Counter id Counter Name Unit/Type Description
M8011C171 CA_UL_SCELL_CONFIG_ATT Integer This counter provides the number of SCell configuration attempts by UL CA
This counter provides the number of successful SCell configuration attempts by UL

M8011C172 CA_UL_SCELL_CONFIG_SUCC Integer
CA.
This counter provides the UL volume (in that cell with PCell role) that is received via
M8012C174 RLC_PDU_UL_VOL_CA_SCELL kBytes
Scell's PHY.
This counter provides the average number of CA UEs in the current cell, which have
M8051C53 CA_UL_SCELL_CONFIG_UE_AVG Integer one configured SCell in UL.The reported value is 100 times higher than the actual
value (for example 1.00 is stored as 100).
This counter provides the average number of UL CA-capable UEs for 2 component
carriers (2 CCs) in the current cell. The counter is updated in the PCell.
M8051C54 CA_UL_CAPAB_UE_2CC_AVG Integer
The reported value is 100 times higher than the actual value (for example 1.00 is
stored as 100)
This counter provides the average number of UL CA UEs in the current cell, which
have one activated SCell.
M8051C118 CA_UL_SCELL_ACT_UE_AVG Integer
The reported value is 100 times higher than the actual value (for example 1.00 is
stored as 100).

Validation Strategy
Table of contents

Validation Strategy & Results
Pre-Requisites
• In order to be able to configure 2CC in UL for a 4CC capable UE, SCells addition need to be done step
wise. To do so, parameter LNBTS:numTxWithHighNonGbr must be set to a value different from 0
(current ORF value=0)
• Feature LTE2324 Network requested UE capabilities should be enabled

Lab Tests
The lab testing should allow to compare the UL performance before and after feature activation, and
thus validate the feature gain on throughput when 2CC UL is triggered.
• UL transfer tests (with UL 2CC eligible UE) should be performed in near cell and also in medium cell
and cell edge.
• Different values of ulCaPathlossThr should be tested to select the more convenient one.
• 2CC UL usage and UL throughput should be checked and compared to pathloss.
• Curves of Throughput and MCS versus pathloss should be built with and without the feature.
• UE Tx power, MCS, BLER and PRB usage should be checked

Field Tests
KPI monitoring should be performed before and after feature activation to assess UL 2CC usage and UL
throughput impact. The impact of the feature on KPIs depends on the number of UL 2CC eligible UEs in
the field.
Drive test should also be performed to assess UL throughput gain.
• Curves of Throughput versus Pathloss should be built with and without the feature.
• UE Tx power, MCS, BLER and PRB usage should be checked.

KINSEI results
Table of contents

CRT Lab tests Results
Test 02 – Peak UL Throughput near cell on B3+B7 (2/2)
PUSCH Throughput
Max 125.92 Mbps
Avg 124.93 Mbps
PDCP UL Throughput
Max 125.73 Mbps
Avg 124.56 Mbps
In this test, PUSCH BLER was around 0%. (seen in very few occasions)

Test 04 – ulCaPathlossThr parameter tuning
2CC vs 1CC UL PDCP Throughput (ulCaPathlossThr=140dB)
UL UDP transfer tests were performed in

different radio conditions with feature
ON and feature OFF.
ulCaPathlossThr was set to 140dB (max
value) to check starting from which
pathloss value, the throughput is better
with 1CC than 2CC.
This occurs between RSRP -105dBm and
-110dBm which corresponds to Pathloss
between 123dB and 128dB.
=> Proposal to set ulCaPathlossThr=
125dB

Test 05 – UL Throughput vs Pathloss on B7+B3 (40MHz)
UL Throughput 1CC vs 2CC
Two values of
ulCaPathlossThr were
tested: 100dB (default)
and 125dB.
2CC with
ulCaPathlossThr=125dB is
the configuration that
provides better
throughput in larger RSRP
2CC to 1CC
range.
2CC to 1CC

Test 05 – UL Throughput vs Pathloss on B7+B3 (40MHz)
UL Throughput (ulCaPathlossThr=125dB)
2CC vs 1CC PCell vs SCell
Scell PL > 125dB => traffic on Pcell only

Field
Static tests results
58
58 © Nokia 2016
2018 Confidential
UL 2CC CA – QC 8998 – Ecole – November 10th
UL Throughput – UDP test
PUSCH Throughput
Max 125.48 Mbps
Avg 121.50 Mbps
PDCP UL Throughput
Max 125.31 Mbps
Avg 120.45 Mbps

UL Throughput on Pcell/Scell – UDP test
Pcell PUSCH Throughput
Max 63.79 Mbps
Avg 61.91 Mbps
Scell PUSCH Throughput
Max 61.75 Mbps
Avg 58.89 Mbps

Per Cell results – UDP test
 Test has been performed in very good radio conditions
 Most of the time MCS28 and UL 64QAM are used
PUSCH MAC UL
WB CQI WB CQI PRB PUSCH
PCI Band RSRP[dBm] SINR[dB] UL MCS Throughput Throughput
CW0 CW1 Number BLER[%]
[Mbps] [Mbps]
Pcell 126 7 -82.28 29.88 14.98 14.96 27.84 88.46 0.23 62.61 62.47
Scell 88 3 -79.76 29.95 14.99 14.99 27.55 86.79 0.55 58.89 57.75

Field
Drive tests results
62
62 © Nokia 2016
2018 Confidential
Drive tests
Test conditions
Drive tests have been performed to assess UL CA feature performance in mobility. The drive was
performed on 5 sites:
Villefranche_CPE, Villefranche_Gare, Villefranche_Sablonniere, Villefranche_Usine,
Villefranche_Grand_Vivier
A reference drive was performed on November 7th with Xperia XZ1 UE.
As a UE issue was encountered with Xperia XZ1, the drive with feature ON was performed with another
UE (QC8998 GSKU) on November 14th : Comparison between the 2 drives is not fully reliable.

Drive tests
Comparison 2CC vs 1CC – UL PDCP Throughput
Average PDCP UL Throughput
1CC (Xperia XZ1) 23.82 Mbps
2CC (QC8998) 65.24 Mbps
Throughput with reference drive is

low compared to phase 1 results.
(30Mbps)

Drive tests
Comparison 2CC vs 1CC (Phase 1 results) – UL PDCP Throughput
Average PDCP UL Throughput
1CC (Xperia XZ- 29.52 Mbps

Premium – Phase 1)
2CC (QC8998) 65.24 Mbps

Drive test – QC8998 GSKU - November 14th
Statistics
1CC - Traffic on 1CC - Traffic on

2CC usage 1CC usage
Pcell only Scell only
Drive 88.44% 11.56% 9.39% 2.17%
PUSCH
BLER PRB 64QAM 16QAM UE Tx Power UE PHR
Band Thp MCS QPSK usage
[%] Number usage usage [dBm] [dB]
[Mbps]
Pcell
B7 38.38 8.86 84.77 20.73 63.6% 26.59% 9.81% 7.85 -2.04
(2600MHz)
Scell
B3 37.86 9.02 87.44 20.86 65.28% 25.76% 8.95% 6.34 2.97
(1800MHz)

Restrictions & Issues
Table of contents

Restrictions & Issues
No restriction or issue so far.

Conclusion
Table of contents

Conclusion
Primary aim of the feature is to increase average and peak uplink user throughput via sending user data
simultaneously over two FDD component carriers.
Maximum achievable UL peak user throughput can be even two times higher comparing to non-CA case.

BACKUP

LTE2324 Network Requested UE Capabilities
Determination if stored UE EUTRAN capabilities are sufficient for CA
LTE2324 check in eNB
• The S1AP message INITIAL CONTEXT
NO All conditions YES SETUP REQUEST does not contain the IE
fulfilled “CS Fallback Indicator”
AND
• Feature LTE2324 is active
(actNwReqUeCapa is set to true)
requestedBands-
YES NO AND
r11 is in UE EUTRA
capabilities?
• CA is active (actDLCAggr is set to true)
AND
• UE supports freqBandRetrieval-r11
Are all bands
YES supported by eNB, IsYES
number of bands in
NO
Conditions
which are used for CA, supportedBandComb
contained in ination-r10 < 128
requestedBands-r11? YES
NO YES
UE capabilities UE capabilities
sufficient insufficient
(no additional (additional retrieval)
retrieval)

Feature activation conditions- eNB side
Feature activation flag LNBTS: actNwReqUeCapa should be set to
‘true’ LNBTS
structure LNBTS: reqFreqBands must be configured
Operator should: reqFreqBands
• enter band numbers aligned with 3GPP TS 36.101 into structure
bandNumber bandPrio
reqFreqBands: bandNumber
3 2
bandNumber defines, which band/s UE uses for filtering of CA band
18 3
combinations
1 5
all bands supported in the network should be included in order to minimize
number of UE Capability Transfer procedures
• assign priority for every specified band number via reqFreqBands: reqFreqBands:bandNumber
bandPrio Range: 1..256
reqFreqBands: bandPrio
bandPrio (1..16, where 1 is the highest priority) defines the order in which eNB Range 1..16
fills the related bandNumber into the UE Capability Retrieval message to UE
(requestedFrequencyBands-r11)

UE side support
LTE2324 functionality is supported by UEs from
Release 11
UE supports LTE2324 if the IE freqBandRetrieval-r11
is set in rf-Parameters-v1180
• no dedicated FGI bit to indicate feature support
Having received UECapabilityEnquiry from eNB with
requestedFrequencyBands-r11 IE, UE may use the
field supportedBandCombinationAdd to report
additional 256 CA band combinations
Please note that UE applies
requestedFrequencyBands-r11 filter only for band
combinations with more than 2 CC or UL CA
• According to 3GPP, UE is supposed to report all
2DL+1UL combinations

Copyright and confidentiality
The contents of this document are proprietary Such Feedback may be used in Nokia products warranties of merchantability and fitness for a
and confidential property of Nokia. This document and related specifications or other particular purpose, are made in relation to the
is provided subject to confidentiality obligations documentation. Accordingly, if the user of this accuracy, reliability or contents of this document.
of the applicable agreement(s). document gives Nokia Feedback on the contents NOKIA SHALL NOT BE RESPONSIBLE IN ANY EVENT
of this document, Nokia may freely use, disclose, FOR ERRORS IN THIS DOCUMENT or for
This document is intended for use of Nokia’s reproduce, license, distribute and otherwise any loss of data or income or any special,
customers and collaborators only for the purpose commercialize the feedback in any Nokia product, incidental, consequential, indirect or direct
for which this document is submitted by Nokia. No technology, service, specification or other damages howsoever caused, that might arise
part of this document may be reproduced or documentation. from the use of this document or any contents of
made available to the public or to any third party this document.
in any form or means without the prior written Nokia operates a policy of ongoing development.
permission of Nokia. This document is to be used Nokia reserves the right to make changes and This document and the product(s) it describes
by properly trained professional personnel. Any improvements to any of the products and/or are protected by copyright according to the
use of the contents in this document is limited services described in this document or withdraw applicable laws.
strictly to the use(s) specifically created in the this document at any time without prior notice.
applicable agreement(s) under which the Nokia is a registered trademark of Nokia
document is submitted. The user of this The contents of this document are provided "as Corporation. Other product and company names
document may voluntarily provide suggestions, is". Except as required by applicable law, no mentioned herein may be trademarks or trade
comments or other feedback to Nokia in respect warranties of any kind, either express or implied, names of their respective owners.
of the contents of this document ("Feedback"). including, but not limited to, the implied

Язык

Добро пожаловать в Scribd!

UL CA

Загружено:

Сведения о документе

Описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

UL CA

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

Feature Presentation to Customer

SRAN17.A ORF ARCEP 2019

1 © Nokia 2018 Confidential

Overview & Feature Features Configuration Performance

Validation KINSEI results Restrictions & Conclusion

2 © Nokia 2018 Confidential

3 © Nokia 2018 Confidential

4 © Nokia 2018 Confidential

5 © Nokia 2018 Confidential

1+5 BCS 0, 1 3+5 BCS 0, 1, 2 5 + 12 - DL (1 + 3 + 8) + UL (1 + 3, 1 + 8, 3 + 8) -

1+8 BCS 0, 1, 2 3+8 BCS 0, 1, 2 7+7 C DL (1 + 18 + 28) + UL (1 + 18, 1 + 28, 18 + 28) -

1 + 18 BCS 0, 1 3 + 20 BCS 0, 1 7 + 20 BCS 0, 1 DL (2 + 4 + 12) + UL (2 + 4, 4 + 12) -

1 + 28 BCS 0, 1 4+4 NC 7 + 28 - DL (2 + 5 + 13) + UL (2 + 13) -

2+2 C 4+5 - 18 + 28 - DL (3 + 3 + 7) + UL (3 + 3, 3 + 7) Band 3 C

2+4 BCS 0, 1, 2 4+7 - DL (3 + 7 + 7) + UL (3 + 7, 7 + 7) Band 7 C

2 + 12 - 4 + 12 BCS 0, 1, 2, 3, 4 DL (3 + 7 + 20) + UL (3 + 7, 3 + 20, 7 + 20) -

2 + 13 BCS 0, 1 4 + 13 BCS 0, 1 DL (4 + 5 + 13) + UL (4 + 13) -

6 © Nokia 2018 Confidential

7 © Nokia 2018 Confidential

8 © Nokia 2018 Confidential

9 © Nokia 2018 Confidential

The following conditions must be fulfilled:

10 © Nokia 2018 Confidential

Only cells that are already configured

11 © Nokia 2018 Confidential

In addition, the following have to be satisfied within the Pcell:

12 © Nokia 2018 Confidential

13 © Nokia 2018 Confidential

14 © Nokia 2018 Confidential

Adding a secondary cell leads to:

15 © Nokia 2018 Confidential

16 © Nokia 2018 Confidential

eNB must decide which of the supported dlCaPreferred

17 © Nokia 2018 Confidential

18 © Nokia 2018 Confidential

Both DL and UL non-GBR buffer status is monitored separately for each UE

19 © Nokia 2018 Confidential

20 © Nokia 2018 Confidential

Set to 1 for SCell activation

Activation of the Secondary Cell means for the UE that:

21 © Nokia 2018 Confidential

0% 10% Division factor 90% 100%

22 © Nokia 2018 Confidential

23 © Nokia 2018 Confidential

24 © Nokia 2018 Confidential

25 © Nokia 2018 Confidential

26 © Nokia 2018 Confidential

DL timer expired but

SCell UL deactivation timer

27 © Nokia 2018 Confidential

Deactivation means that:

28 © Nokia 2018 Confidential

29 © Nokia 2018 Confidential

• UE is scheduled for UL transmission at least in the PCell

• UE is scheduled for UL transmission on SCell only

30 © Nokia 2018 Confidential

31 © Nokia 2018 Confidential

33 © Nokia 2018 Confidential