Vous êtes sur la page 1sur 58

Carrier aggregation for

multi-carrier eNode Bs
Please always check the latest version of this NEI slides!
LTE1562
Network Engineering Information
• Dariusz Tomeczko
• 13-10-2014
• ver. 1.10
1 11/12/2019 © Nokia 2014 - MBB Customer Support Network Engineering / Andrzej Maciołek
For internal use only
LTE1562 Carrier aggregation for multi-carrier eNode Bs
Table of contents

1 2 3 4 5 6
Introduction Technical Inter – Benefits and Configuration Deployment
Details dependencies Gains Management Aspects
Motivation and Feature Detailed Functionality Simulation, Lab and Parameters and
Interdependencies with Activation, Configuration
Overview Description Field Findings Parameterization
other features and Simulation, Lab Examples, Fault Mgmt,
functions Scenarios Trial Area
1 and Field Findings

7 8
Performance End-to-End
Aspects Operability
Counters and KPIs, OSS and Core
Feature Impact Analysis Interworking
and Verification

2 11/12/2019 © Nokia 2014 - MBB Customer Support Network Engineering / Andrzej Maciołek
For internal use
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Introduction

Table of contents

3 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Carrier aggregation for multi-carrier eNode Bs (RL70)

three CA
capable cells in
the single sector
– for dual carrier
CA UEs
4 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
Carrier Aggregation feature package
CA feature set got extended in RL70

>
RL60 RL70
LTE1332 (on top of basic CA feature LTE1089
from RL50) – two CA carriers with up to 20
>
>
LTE1562 – three CA cells in the single sector
LTE1803 – triple CA from the UE perspective
MHz + 20 MHz aggregated bandwidth > LTE1951 – Automatic Configuration support
> LTE1367 – NetAct supporting functionality for for CA for multi-carrier eNBs
automatic CA configuration > LTE2033 – Additional CA band combinations

5 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Key functionalities
CA capable UE PCell
• Up to two secondary cells could be configured in the eNB for
the single primary cell
• Similarly, given cell could play a role of a secondary cell for up
to two primary cells
SCell candidate 1
• Hint: Before LTE1562 there was 1:1 relationship between
primary and secondary cell
• Up to two SCell candidates could be in place for the given UE
• Choice of the actual SCell to be configured for the UE is done SCell candidate 2
according to the UE capabilities and cell load information
• Note: still all the involved cells need to be collocated, created
in the same system module and the serve the same
geographical sector

6 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Technical Details

Table of contents

7 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Technical Details
Dependency Table (LTE)

FDD LTE RL release eNodeB NetAct


Release/version RL70 LN7.0 OSSx.x
TDD LTE RL release eNodeB NetAct
Release/version - (feature will come in TDD later than RL55)

Flexi Zone Micro


RL release eNodeB NetAct
(FZM)
Release/version -
HW Specified by
HW & IOT MME SAE GW UE
requirements 3GPP
CA capable UE
For CA with UE aggregated bandwidth Nokia proprietaty
supporting eNB
higher than 20 MHz, FlexiNS 4.0/Flexi feature running on
FSMF NG 3.2 is a must in order to fully
configured carriers
top of 3GPP CA
– cf. Technical
benefit from this functionality. Rel. 10/Rel. 11
Details
8 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Allowed bandwidth configurations

• Bandwidth combinations consisting of three elements could be configured in the eNB


(instead of two as it was in RL60 for LTE1089/LTE1332)
• Allowed bandwidth configurations: any
possible combinations of three elements

flexible choice
out of (5 MHz, 10 MHz, 15 MHz, 20 MHz)
are allowed with LTE 1562
• No bandwidth combinations that include
1.4 or 3 MHz bandwidth are allowed. of bandwidth
• Feature is FDD only
configuration
9 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Band combinations (1/4)

• Allowed band combinations: any combination of the size of three (with repetitions)
from the set of bands supported by basic LTE1089/LTE1332, which contains at least
two different supported band combinations (incl. intra-band combinations).
Band combinations supported for Resultant allowed band combinations for LTE1562 – site sector level
dual carrier deployments PCell SCell 1 SCell 2

Band A Band B Band A Band B Band C

Band A Band C Band B Band C Band A

Band B Band C Band C Band A Band B

band configs for 2 carriers reused


10 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Band combinations (2/4)

• Due to LTE2033 feature (Additional carrier aggregation band combinations – I) from


RL70 onwards following band combinations are also allowed – on top of RL60 ones.
- 1+3 (2100 + 1800)
- 1+28 (2100 + 700 APT)
- 2+12 (1900 + 700 AC)
- 3+27 (1800 + 800 SMR)
- 8+27 (900 + 800 SMR)
• These band combinations are technically supported also by FSME but not
necessarily officially tested.
• These combinations are also supported in the context of LTE1562.
• NEW: LTERLCR-3372 introduces support for band 7+ band 28 combination from
RL70 onwards
11 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Band combinations (3/4)

• Feature LTE1562 as such does not extend the list of supported band combinations:
Band combinations supported for Resultant allowed band combinations for LTE1562 – site sector level
dual carrier deployments PCell SCell candidate 1 SCell candidate 2

Band E Band F Band E Band F Band G

Band E Band G Band F Band G Band E

Band F Band G Band G Band E Band F

no new band combinations


12 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Band combinations (4/4)

• Clarification note: Three cell configurations


with all cells in the same band constructed
three carriers
from:
for the same
band could
- an NSN supported intra-band non-contiguous band
combination or
- constructed from an NSN supported intra-band
contiguous band combination together with an NSN
supported intra-band non-contiguous band combination
be also
configured
are also included.

Recap on RL60 contiguous CA allocation defnition (more details in NEI LTE1332):


carrier-to-carrier spacing ≤ nominalSpacing → contiguous intra-band CA allocation is in place
carrier-to-carrier spacing > nominalSpacing → non-contiguous intra-band CA allocation is in place
where nominalSpacing is defined by the 3GPP. Examples of nominal spacing figures for the selected BW combinations:
10 + 10 -> 9.9 MHz, 10 + 15 -> 12.0 MHz, 15 + 15 -> 15.0 MHz, 15 + 20 -> 17.1 MHz, 20 + 20 -> 19.8 MHz

13 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
HW configurations

Feature works only with FSMF system module, amount of FSPs needed depends on the
Tx/Rx configurations and cell bandwidth values:
1 FSP 2 FSPs 3 FSPs
20 MHz bandwidth: At least one 20 MHz 4 Tx/Rx cell configured in the eNB:
Single CA LTE1562 sector per eNB: Single CA LTE1562 sector per eNB: Two CA LTE1562 sectors per eNB:
20 MHz 4 Tx/Rx + 3x20 MHz 4 Tx/RX 3x20 MHz 4 Tx/Rx +
10 MHz 2 Tx/Rx + 3x20 MHz 2 Tx/Rx
10 MHz 2 Tx/Rx
20 MHz bandwidth: No 20 MHz 4 Tx/Rx cell configured in the eNB
Single CA LTE1562 sector per eNB: Two CA LTE1562 sectors per eNB: Three CA LTE1562 sectors per eNB:
3x20 MHz 2Tx/Rx 3x20 MHz 2Tx/Rx + 3x20 MHz 2Tx/Rx 3x20 MHz 2Tx/Rx +
3x20 MHz 2Tx/Rx +
3x20 MHz 2Tx/Rx

Note: Here, FSP is the baseband capability of either FSMF or FBBC or FBBA, so 3 FSPs means here FSMF + 2
baseband extension modules

15 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
HW configurations

1 FSP 2 FSPs 3 FSPs


10 MHz bandwidth:
instead of each 1x20 MHz 2 Tx/Rx cell in the configurations put in the previous slide:
2x10MHz 2Tx/Rx or 1x10 MHz 4 Tx/Rx can be configured (info on 1x10 MHz 4 Tx/Rx valid only if there is no 4Rx UL CoMP).
General info: in the context of RL70, any cells configured in the eNB could be arranged into CA sector;
15 MHz cell could replace 20 MHz cell put in this table, similarly: 5 MHz cell could replace 10 MHz cell;
Additional limitations may be in place for certain features like e.g. UL CoMP 4Rx

So, in case of generic 9-cell CA deployment following Tx/Rx settings are allowed:
-2TX/2RX + 2TX/2RX + 2TX/2RX
-4TX/4RX + 4TX/4RX + 4TX/4RX (4Tx/Rx for 5 MHz and 10 MHz only)
-2TX/4RX + 4TX/4RX + 4TX/4RX (4Tx/Rx for 5 MHz and 10 MHz only)
-2TX/2RX + 2TX/2RX + 4TX/4RX (4Tx/Rx for 5 MHz and 10 MHz only)

Note that some configurations (incl. Tx/Rx variants) are technically supported but not
necessarily officially tested. For the up-to-date LTE BTS Officially supported and Tested Configurations please
refer to: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D-152655

16 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
eNB configuration

• Concept of CAREL objects carrying the PCell-SCell relationship is extended to create


CA pool of the size of three – two CAREL objects per LNCEL are allowed.
LNBTS

LNCEL LNCEL LNCEL

CAREL CAREL
lcrId lcrId

CAREL CAREL
lcrId lcrId

The instance range of MOC CAREL (Carrier Aggregation RELation) is increased to 2


Multiple CAREL instances can point to the same cell

17 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
eNB configuration

• LCELL/sectorId parameters conveying sector identity should have the same value for
the cells inolved in the CA functionality in the given sector. Cells not participating in
CA should have other unique sectorId.
LNBTS

LNCEL LNCEL
LNCEL

CAREL CAREL
lcrId lcrId

CAREL CAREL
lcrId lcrId

LCELL LCELL LCELL


sectorId sectorId sectorId

18 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Configuration of the secondary cell for the given UE

Process of the SCell configuration for the UE has been changed:


Not influenced by CA features. But: If INITIAL CONTEXT
RRC Connection Setup SETUP REQUEST contains “CS Fallback Indicator”, no SCell
configuration for this UE
eNB verifies whether UE CA capability matches the eNB CA
UE capability check
configuration according to the procedure defined for LTE1332.

Detection of number of SCell eNB verifies whether one or two suitable SCell candidates* for
candidates the UE are in place.

Establishment of SRB2 and non-GBR MeasObjectEUTRA for each candidate SCell carrier provided in
DRB via RRC Conn. Reconfiguration RRC Connection Reconfiguration. No measId for these objects.

Need for measurement gap creation If considering the data for any candidate band combination there
is a need to configure the measurement gap for the UE, these
verified gaps will be setup due to inter-XXX measurements
*As in LTE1089/LTE1332 SCell has to be unlocked, not barred, to have operational stated enabled and primPlmnCellres is set to
“Not Reserved”
19 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Configuration of the secondary cell for the given UE

SCell could be configured for the UE only if UE aggregate maximum bit rate is
not lower than LNBTS/caMinDlAmbr, no TTI bundling has been started,
UE AMBR and other checks extended VoLTE Talk Time trigger to not configure SCell has not been triggered
(cf. NEI on EVTT)
Admission Control check Radio Admission Control procedures are run for all (= one or two) SCell
candidates
Load dependent choice of If two SCell candidates remain valid at this stage than choice of the
the single SCell single SCell* is made basing on the cell load figures

Configuration of the single RRC Connection Reconfiguration with the chosen SCell is sent to the UE
SCell for the particular UE and the process of SCell configuration for the given UE is concluded
*Assumption is taken that maxNumScells is set to 1 (default). If set to 2 please refer to LTE1803 feature (CA 3CC).

one SCell for the UE is chosen


20 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Load based SCell candidate selection – introduction

If there are two suitable SCell candidates, choice of the single SCell to be configured for
the given UE is based on the current load metric NLCV (Normalized Load Compare
Value). Lower loaded SCell is taken. If the load is exact same, cell with higher BW is
chosen.
Following factors contribute to NLCV value:
• PDCCH load measurements
• non-GBR load measurements,
• available PRBs for non-GBR traffic.

These load calculations are independent from activation of any load balancing features.

load based SCell selection


21 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Load based SCell candidate selection – role of CRG feture

As in RL60, Cell Resource Groups (CRG) feature could run in paralel with LTE1562.
PCell and SCell works according to the cell individual share configuration and
maxNumCaConfUeDc configured for the cell is split according to CRG shares.
RL70 extension: all load calculations needed for SCell candidate selection are made
considering target CRGs. So only TTIs used by the given CRG are considered during
the load calculations.
Note that if valid CRG mapping could not be retrieved for the SCell candidate (meaning
fallback to the default CRG for non-CA cases) such a SCell candidate is excluded from

CRG-aware load
the further SCell selection

based SCell
22 11/12/2019
Confidential
© Nokia 2014 - File Name - Version - Creator - DocID
selection
LTE1562
Load based SCell candidate selection – calculation details

Factors that contribute to the load based comparison via NLCV between two candidate
SCells:
• PDCCH load measurements:
- time-averaged PDCCH load per CRG, combined for UL and DL,
- ratio of utilized CCEs to total number of available CCEs (taken from maxNrSymPdcch,
independently from the currently used PDCCH symbols)
• non-GBR load measurements:
- time-averaged sum of weights of active non-GBR DL bearers
• available PRBs for non-GBR traffic.
- time-averaged number of PRBs available for weight-based scheduling of non-GBR traffic in
this CRG (so PRBs used for GBR, system usage and required for the "duty part" of nominal
bitrate bearers (LTE1042) not included)

23 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Load based SCell candidate selection

Normalized load metric means that it considers potentially different bandwidth for two
candidated SCells.
NLCV calculation:

average non - GBR load


NLCV  average PDCCH load 
max(1, average available PRBs)  CRG share  DL BW

Dynamic load calculation


24 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
eNB capacity

As in RL60 a cell can act as a primary carrier for PCell A Max. 50 CA PCell UEs
up to 50 UEs with the PCell role (parameter
maxNumCaConfUeDc).
SCell SCell
The number of RRC connected users per sector Max. 50 CA SCell UEs Max. 50 CA SCell UEs
is dynamically reduced by up to a maximum of Each UE using the cell as an SCell reduces the
50 UEs for each configured cell that can act as maximum number of RRC connected users per
cell
SCell within a cell pair for Carrier Aggregation.
PCell A PCell
If a cell belongs to two cell pairs (SCell with 2 Max. 50 CA PCell UEs B
PCells) the maximum reduction would be 100 Max. 50 CA PCell UEs
cause up to 100 SCell UEs could be assigned to
SCell
a single carrier. Max. 100 CA SCell UEs

25 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
eNB capacity

Selected RL70 capacity figures


actHighRrc = FALSE case

Max number of RRC connected users per cell 840


- Max number of CA UEs from this pool for
50
which given cell is PCell
Maximum number of CA UEs for which this cell 2*50 = 100 – each such UE reduces the maximum
is SCell number of RRC connected users per cell by 1
Maximum number of UEs per TTI once CA is
No additional limitations on top of non-CA case
enabled
actHighRrc could be set to TRUE if there are up to 3 cells in eNB. This could enabled together with CA.
Specifically, if there are up to 3 CA cells per eNB or up to 2 CA cells plus one non-CA, actHighRrc could be set to TRUE.
For other capacity figures in RL70 please refer to the dedicated NEI
26 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
PUCCH implications

General comment on CA and PUCCH: Multi-cell ACK/NACK sent via PUCCH is


handled via special message: PUCCH format 1b with channel selection – standardized
specifically for Carrier Aggregation for the cases where there is a need to send up to 4
bits of HARQ information (2 per each cell due to MIMO – one bit for each transport
block)

no PUCCH
LTE1562: PUCCH 1b CS resources in the
primary cell are statically split 50/50

size increase
between SCell A and SCell B:
• UEs configured with SCell A got only odd-

for LTE1562
numbered PUCCH 1b CS resources
• UEs configured with SCell B got only even-
numbered PUCCH 1b CS resources

27 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
PUCCH implications

As introduced in LTE1089, up to four CA UEs could share the same HARQ resources
(group) in the given TTI.
Other CA UEs sharing the same HARQ resources (group) are blocked from scheduling
in this TTI. The UEs with lower scheduling weights are excluded firstly. This is treated
as blocked due to PDCCH Link Adaptation.
As a consequence of LTE1562 specific
PUCCH handling (PUCCH resources split PDCCH
statically between SCell A and SCell B),
probability of UE blocking due to scheduling blocking may
is increased
Note: No PUCCH collisions in the SCell for the
UEs for which PCells are different cause PUCCH
increase
is always transmitted via PCell only.

28 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Periodic Channel State Information handling in case of SCell transmission –
recap (before RL70)
Simultaneous sending of ACK/NACK and CSI via PUCCH channel*:
• if PDSCH is scheduled from PCell only: ACK/NACK and periodic CQI are sent
simultaneously (format 2a/2b could be used instead of PUCCH format 1b with
channel selection).
• If PDSCH is scheduled from SCell or PCell and Scell: periodic CQI is dropped
* considerations valid only if cqiPerSimulAck is set to TRUE (default value)

In RL50/RL60 there was no solution to mitigate the effect of dropping of perioding CSI in
the above mentioned cases. In extreme cases (many periodic CQIs dropped in a row
and no aperiodic CQIs that might compensate this loss) this could lead to fallback to
TxDiv and/or may cause some issues in Timing Advance estimation algorithm
Hint for LTE1803: situation will be similar also for PUCCH format 3: any SCell
ACK/NACK causes dropping of CSI if colliding with this ACK/NACK.

30 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Periodic CSI handling in case of SCell transmission – RL70

In RL70 if according to eNB internal algorithms:


• fallback to TX diversity from CL MIMO Spatial Multiplexing (monitored separately in
PCell and SCell)
• entering UL out-of-sync (monitored in PCell)
negative
may happen due to dropping of CSI (of PCell/SCell
respectively) in TTI n+4
effect of
or there is a need of fresh CQI for the UE in DRX CSI
dropping
on duration (monitored in PCell and SCell)
then: UE is not selected for the scheduling in TTI n

may be
in SCell* leaving the room to send CSI in TTI n+4
* scheduling of retransmission may override the CSI dropping solution.

31 11/12/2019
Confidential
© Nokia 2014 - File Name - Version - Creator - DocID mitigated
LTE1562
Periodic CSI handling in case of SCell transmission – RL70

Together with LTE1562, similar solution for prevention from negative effect of CSI
dropping was introduced for the cases where cqiPerSimulAck is set to ‘false’
and/or UE indicates FGI2 ”0” (= not supported). This is valid for PCell or SCell CSI
transmission as well as non-CA cases.
Note: FGI2 reflects among others capability of the UE to simultaneously send CQI & ACK/NACK on PUCCH
2a/2b

RRM triggers are the same as for the CA specific solution (see previous slide).

CSI dropping avoidance


algorithm extended to non-CA
32
scenarios
11/12/2019
Confidential
© Nokia 2014 - File Name - Version - Creator - DocID
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Interdependencies

Table of contents

33 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Interdependencies with other features

limitations Interworking not supported at all with:


FZM product – CA not supported for FZM
LTE1117 MBMS

Additional limitations (1/2):


LTE1542 Supercell – simultaneous enabling of LTE1562
and LTE1542 allowed only if super cell is activated in all
cells having the same sector id

Note: only changes on top of LTE1089/LTE1332 listed

34 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Interdependencies with other features

limitations Additional limitations (2/2):


LTE1691 Uplink intra eNodeB CoMP 4RX – interworking
possible if HW configuration allows for it, additional
limitations are in place – please refer to NEI on LTE1691

E.g. With FSMF + 2xFBBC, one can have a 10MHz 4RX cell (UL
CoMP 4Rx) + 10MHz 2RX cell + 10 MHz 2RX cell with the same
sector ID

Note: only changes on top of LTE1089/LTE1332 listed

35 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Interdependencies with other features

extensions Optional supporting functionality:


LTE1951 – Automatic Configuration support for CA for
multi-carrier eNBs
Interworking assured:
LTE1382 – Cell Resource Groups – if LTE1382 is enabled,
CRG specific load metrics are considered during SCell
candidate selection – instead of cell level ones
NEW: due to PR 45396ESPE06 from RL70 onwards LTE1140
& Carrier Aggregation could be enabled simultaneously
(from the given UE perspective), so from RL70 onwards
Load Balancing algorithm could offload also CA UEs
Note: only changes on top of LTE1089/LTE1332 listed
36 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Benefits and Gains

Table of contents

37 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Benefits and gains

As in case of LTE1089/LTE1332, the main goal of LTE1562 is to improve end user DL


non-GBR throughput.

With the help of LTE1562 more flexible CA configuration is allowed targetting multi-
carrier eNB deployment. Probability that UE capability matches at least one CA
combination configured in the eNB may be higher.

LTE1089/LTE1332 introduced a kind of soft load balancing between CA-enabled layers


(soft = without involvement of inter-frequency handovers).

Additional level of load balancing on top of already existing in RL50/RL60 is in place.


This is because three cells could participate in the CA functionality instead of two.

38 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562

Configuration
Management
Table of contents

39 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Configuration management

No new parameters are introduced together with LTE1562.

Feature inherits the activation flag LNBTS/actDLCAggr from RL50 LTE1089/RL60 LTE1332.

Modifications in existing parameters:


• CAREL/caRelId range extended to 2 as two CARELs may exist under given LNCEL
• LCELL/sectorId covers the possiblity of having up to three cells with the same
sectorId. PCell and SCells must have the same sectorId configured in the
corresponding LCELL object instances
If actDLCAggr is set to 'true' in all LCELL instances the sectorId must be configured:
- with the same sectorId for a carrier aggregated cell (CA cell) with subordinated CAREL instances or which is
linked by CAREL-lcrId of another LNCEL (maximal 3 LCELL instances are allowed to have the same
sectorId);
- for non-CA cells the sectorId must be unique within the eNB
40 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Configuration management

Modifications in existing parameters (2/2):

• Natural extensions of existing parameter consistency checks to reflect potential


existence of two configured SCells per PCell (e.g. lcrId)
• CAREL/caSchedFairFact must have the same value in all CAREL MOs under cells
(LNCELs) which have configured the same sector ID (LCELL-sectorId) value.

Note: maxNumScells parameter is introduced to cover LTE1803 functionality (DL CA


3CC) – for maxNumScells = 2 case please refer to NEI for LTE1803 feature.
Within the scope of LTE1562 maxNumScells is set to 1

41 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Configuration management

PUCCH allocation rules have been changed:

If maxNumSCells = 1 (no LTE1803 in place):


- in P-LNCEL, if exactly one CAREL instance exists for the LNCEL instance,
n1PucchAn must configured to '10' or >= '72‘ (legacy approach inherited from
LTE1089/1332)
- in P-LNCEL, if two or more CAREL instance exist for the LNCEL instance,
n1PucchAn must configured to >= '72‘ (no n1PucchAn = 10 allowed for LTE1562)
If maxNumSCells =2 please refer to LTE1803 NEI.
No special PUCCH settings for
tests/trials allowed for
42
LTE1562
11/12/2019
Confidential
© Nokia 2014 - File Name - Version - Creator - DocID
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

43 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

LTE1562
Feature targets only the deployments for which at
least three LTE carriers having bandwidth 5, 10, 15

targets
or 20 MHz exist.

Coverage of three involved cells is assumed to be


overlapping with each other. multi-carrier
Specifically, coverage criterion is not considered
during SCell candidate selection (as well as it is
LTE
not involved in the process of SCell activation and
deactivation).
deployments
44 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 1: Assignment of sector identifiers

For all cells to be involved in the Carrier


Aggregation sector ID should be assigned
This id is meaningful only for Carrier
Aggregation set of features
The same sector ID should be provided for the
cells serving the same geographical sector
(here 1, 2 and 3. local cell)

45 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 2: Creation of the first


PCell – SCell relation via
CAREL object put under
LNCEL of PCell

Local cell resource id of the


SCell is put in CAREL of the
primary cell

46 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 3: Creation of the


second PCell – SCell relation
via CAREL object put under
LNCEL of PCell

Local cell resource id of the


second SCell is put in CAREL
of the primary cell
Finally, there are two CAREL
objects under LNCEL-1
pointing to two different cells
(here: LNCEL-2 and LNCEL-
3)
47 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 4: Parameter dependencies


Following rules inherited from RL50 LTE1089 and RL60 LTE1332 have to be
obeyed:
• LNBTS/actEnhAcAndGbrServices (Activate enhanced AC and GBR services) has to be set to 'true‘
• LNCEL/riEnable has to be set to the same value in PCell as well as SCell
• LNCEL/riPerM must be set to '1' when riEnable is set to 'true’
• for P-LNCEL where riEnable is configured to 'false', cqiPerNp must bigger than or equal to '5ms' and less than
or equal to '40ms'
• LNCEL/cqiPerSbCycK has to be set to the same value in PCell as well as SCell
• LNCEL/deltaPucchShift in PCell must be <= 2
• LNCEL/periodicCqiFeedbackType has to be set to the same value in PCell as well as SCell
• PUCCH/Admission Control dimensioning rules have to be satisfied– please refer to NEI on LTE1332 for
further details

48 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 5: CA specific parameter settings


Following parameters inherited from RL50 LTE1089/RL60 LTE1332 could be set for
all involved cells:
• BASIC parameters
- CAREL/caSchedFairFact – default equal to 1 (= fairness assured between non-CA and CA UEs), key CA
parameter, it will play significant role as for non-CA/CA data share under medium-to-high load scenarios,
could be tuned to lower values (even 0) to boost CA performance at any cost
- LNBTS/sCellActivationCyclePeriod – default equal to 2s, could be tuned to 0.5s to boost CA penetration

49 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

• ADVANCED parameters – no need to be touched unless there is a justified need to do so


- LNCEL/maxNumCaConfUeDc – default equal to 50 (maximum value)
- LNBTS/caMinDlAmbr – default: 512 kbps,
- LNBTS/sCellActivationMethod – default: nonGBRBufferBased
- CAREL/disableSCellPDCCHOlLa – default: false
- LNBTS/sCellpCellHARQFdbkUsage – default: conservative (0)
- LNBTS/sCellDeactivationTimereNB – default: 128rf (6)

Note: LNCEL/maxNumCaConfUe3c (Max number carrier aggr configured UEs 3 Carriers) parameter is
LTE1803 specific and it is not relevant in the context of LTE1562 feature.

50 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Deployment aspects – BTS Site Manager

Step 6: Feature activation


LTE 1562 is activated via feature flag (inherited from LTE1089/LTE1332)

51 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562 Carrier aggregation for multi-carrier eNode Bs

Performance
Aspects
Table of contents

52 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Performance aspects

No new PM counters were introduced, counters introduced for LTE1089 in RL50 are
reused.
Info on legacy PM counters:
Legacy CA related PM counters like:
M8012C151: PCell RLC data volume in DL via SCell
M8001C495: Average number of UEs with a configured Scell
M8001C496: Average number of UEs with an activated SCell' include information related to both
SCells
M8011C67: Number of SCell configuration attempts
M8011C68: Number of successful SCell configurations
are updated in case of LTE1562 irrespectively of the chosen SCell

53 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Performance aspects

Note that following RL50/RL60 formulas to calculate the amount of RLC data
transmitted physically in the given cells is no more valid in the context of LTE1562:
RLC data volume of cell 1: M8012C18 (cell1) – M8012C151 (cell1) + M8012C151
(cell2)
RLC data volume of cell 2: M8012C18 (cell2) – M8012C151 (cell2) + M8012C151
(cell1)
Note: M8012C18 RLC PDU volume transmitted

54 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Performance aspects

Generally, recommendations on counters and KPIs to be monitored, as provided for


LTE1089/LTE1332, are still valid in the context of LTE1562 – please refer to NEI on
LTE1332.
On top, following LTE1562 specific aspects should be considered:
PDCCH blocking to be monitored – especially if there is a strong asymetry between CA
use in the first and second SCell candidate. Due to LTE1562-specific PUCCH handling
probability of PDCCH blocking may increase in specific cases (cf. Technical Details
section). Hint: Use LTE_1154a to monitor PDCCH blocking.
DL throughput may suffer – due to CSI dropping avoidance algorithm – avoid using
unidirectional DL traffic pattern during trials/showcases as this traffic pattern increases
the probability of triggering the CSI dropping avoidance algorithm.

55 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562 Carrier aggregation for multi-carrier eNode Bs

End-to-End
Operability
Table of contents

56 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
LTE1562
Performance aspects

LTE1562 feature does not need any dedicated support from the Core Network
However, in case of CA with UE aggregated bandwidth higher than 20 MHz, support for
UEs of cat. 5 and higher need to be in place in FlexiNS/FlexiNG in order to benefit from
improved user throughput for these categories.
Flexi NS status:
• Flexi NS 3.0 supports Category 4
• Flexi NS 4.0 supports Categories 5 and 6
Flexi NG status:
• Flexi NG 3.0 supports Category 4
• Flexi NG 3.2 supports Categories 5, 6 and 7
For CA with UE aggregated bandwidth higher than 20 MHz, FlexiNS 4.0/Flexi NG 3.2 is a
must in order to fully benefit from this functionality.
57 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
58 11/12/2019 © Nokia 2014 - MBB Customer Support Network Engineering / Andrzej Maciołek
For internal use only
Hidden parameter

CSI dropping LNBTS/actCsiDroppingSolution


solution
This parameter was introduced already in RL60 to enable/disable a solution
to prevent from dropping of periodic CSI due to DL scheduling on the SCell.
However, due to CRL1504 the CSI dropping solution was removed from
RL60 and moved to RL70. Consequently, parameter in RL60 is meaningless
while in RL70 it is meaningful.

This parameter enables/disables a solution to dropping of periodic CSI due to


DL scheduling on the SCell. This parameter also enables/disables a solution
to dropping of periodic CSI in the PCell/single serving cell caused by setting
of cqiPerSimulAck of this PCell/single serving cell to ‘false’ and/or caused by
UE indicating in FGI2 value ‘0’.

59 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Hidden parameter

CSI dropping LNBTS/actCsiDroppingSolution


solution
If set to 'enable', DL scheduling avoidance is always used in subframes that
collide with periodic CSI.

If set to ‘disable’, DL scheduling avoidance is never used (the same as in as


in earlier releases). This setting is intended for peak data rate demonstration
and is recommended to be used with proactive UL assignment
(ilReacTimerUl not set to zero) so that aperiodic CSI of PCell and SCell is
ensured even if all periodic CSI is dropped.

If set to ‘enableIfNeeded’, the DL scheduling avoidance is used on demand


based on triggers from MIMO-MC (MIMO Mode Control) and the UL TA (Time
Alignment) Control.

60 11/12/2019 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential