NokiaEDU

Initial Parameter Planning

LTE Radio Planning Essentials Course

RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

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

2 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Index
 LTE/EPC Overview
 LTE Air Interface
 Air Interface Overheads
 RRM overview
 LTE Link Budget
 Radio Planning – Coverage Planning & Cell Range
 Radio Planning – Capacity Planning
 LTE Performance Simulations
 Nokia Flexi Multiradio 10 LTE Solution
 Initial Parameters Planning

5 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Objectives

After completing this module, the participant will be able to:

• Describe the concept of channel configuration parameters
• Describe the PRACH configuration parameters
• Describe the PCI configuration parameters
• Describe the UL DM & RS configuration parameters
• Describe the PDCCH capacity & parameters
• Describe the PUCCH capacity & parameters

6 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

7 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Preamble generation

# root sequences = 838 in total

The random access preambles are generated from: # preamble sequences = 64 per cell
• Zadoff-Chu root sequences (838 in total) with zero correlation zone
• one or several sequences (length 839 each)
Zadoff–Chu sequence is known as a CAZAC sequence (Constant Amplitude Zero AutoCorrelation waveform).

There are 64 preambles sequences available in each cell. The set of 64 preamble sequences in a cell is found by including
first, in the order of increasing cyclic shift, all the available cyclic shifts of a root Zadoff-Chu sequence

Fig:
example of
preambles
generation with
zero
autocorrelation
zone length equal
to 279 Fig: Zadoff-Chu sequence. The real (upper) and
(prachCS=14) imaginary (lower) parts of the complex-valued
output (Wikipedia)

8 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Preamble generation
Zero correlation zone and Cyclic shift
• zero correlation zone  decode PRACH even if sent on the same time/ frequency
• preamble signals generated based on two different ZC sequences are not correlated within the geographical range related
to prachCS
• the dimensioning of the cyclic shift, must be greater than the maximum round-trip delay

Required number of different root Zadoff–Chu sequences grows with N cs (Cyclic Shift) and the cell radius:

Limits due to preamble

premable formats

9 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PRACH Planning Principle
• PRACH configuration: two cells must be different within the PRACH re-use distance to increase the RACH decoding
success rate
• PRACH transmission can be separated by:
- Time (prachConfIndex)
• PRACH-PUSCH interference: If PRACH resources are separated in time within eNB
• PRACH-PRACH interference: If same PRACH resources are used for the cells of an eNodeB.
• PRACH-PRACH interference is preferred to PRACH-PUSCH interference so prachConfIndex of the cells on one
site should be the same
- Frequency (prachFreqOff)
• Allocation of PRACH area should be next to PUCCH area either at upper or lower border of frequency band, however
should not overlap with PUCCH area
• Avoid separation of PUSCH in two areas by PRACH (The scheduler can only handle one PUSCH area)
• For simplicity use same configuration for all cells
- Sequence (PRACH CS and RootSeqIndex)
• Use different sequences for all neighbor cells

PUSCH Rx power (SINR) can be very high compared to PRACH SINR in the neighbor cell and hence effectively swamp the PRACH preambles
and/or resulting in misdetections (ghost RACH).

10 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Preamble Formats
- 3GPP (TS36.211) specifies 4 random access formats for FDD

• Difference in formats is based in the different durations for the cyclic prefix, sequence and guard time which have an effect
on the maximum cell radius
• Formats 0 and 1 are supported from RL30

Recommendation:
 Select Format0 for cell
ranges <14.53 km
 Select Format1 for cell
ranges <77.34 km

Note: An additional format to these format four is specified for TDD

11 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PRACH Configuration Index - prachConfIndex
Extract of the random access preamble
- The parameter defines the Allowed System Frame for
random access attempts, the Sub-frame numbers for configurations table (only for supported preamble
random access attempts and the Preamble format formats 0 and 1)
- Supported values:
• For Preamble Format 0: 3 to 8
• For Preamble Format 1: 19 to 24

- RACH Density indicates how many RACH resources

are per 10ms frame.
- Only RACH density values of 1 and 2 are
supported .E.g.
• RACH density=1 Only one random access attempt
per frame
• RACH density=2 Two random access attempts per
frame

Recommendation:
Configure the same PRACH configuration Indexes at
prachConfIndex cells belonging to the same site. E.g.:
LNCEL; 3..24;1; 3  3 or 4 or 5 if RACH density=1 and 6 or 7or 8 if
Range is restricted to two different RACH density=2 (Preamble Format 0 )
ranges: 3-8 and 19-24 (internal)

1 Random access attempt = 1 RACH resource = 6 PRBs

12 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PRACH
Where PRACH is placed in frequency domain:
• PRACH can be placed either on lower or upper edge of the bandwidth
• Therefore the possible range for prachFreqOffset is:
prachFreqOff
First PRB available for PRACH in UL
RA UL LNCEL; 0...94;1; -
0  nPRBoffset N RB 6 Max. value is ulChBw(in PRB) - 6

...

If PRACH area is placed at the lower border of UL frequency band then: PRACH

PUCCH
prachFreqOffset = roundup [maxPucchResourceSize /2]

If PRACH area is placed at the upper border of the UL frequency band then:

prachFreqOffset = MAXNRB – 6 - roundup [maxPucchResourceSize /2] ...

The PRACH area (6 PRBs) should be next to PUCCH area either at upper or
lower border of frequency band to maximize the PUSCH area but not overlap

freq
with PUCCH area
freq

time time

13 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PRACH Cyclic Shift - PrachCS
- PrachCS defines the configuration used for the preamble generation. i.e. how many cyclic shifts are needed to
generate the preamble
- PrachCS depends on the cell size
• Different cell ranges correspond to different PrachCS
- Simplification: To assume all cells have same size (limited by the prachConfIndex)

Recommendation:
Select PrachCS based on the cell range E.g. if estimated
cell range is 15km then PrachCS: 12
If all cells in the network are assumed to have same cell
range then PrachCS is the same network wise

prachCS
Preamble cyclic shift (Ncs
configuration)
LNCEL;0…15;1; 12

14 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Preamble Generation Root Zadoff-Chu sequence order for
preamble formats 0 – 3.:
First: take all available cyclic shifts of one root
Zadoff-Chu sequence:

If not enough: take next logical index and so on

prachCS
Preamble cyclic shift (Ncs configuration)
LNCEL;0…15;1; 0
Restricted set (high speed) in RL40

prachHSFlag
Unrestricted or restricted (high speed) set selection
LNCEL; true, false; false

• Cyclic shift given by

vN CS v 0,1,...,  N ZC NCS   1, NCS 0 for unrestricted sets



Cv 0 N CS 0 for unrestricted sets
  v nshift
RA
  (v mod nshift
RA RA RA RA

 d start ) N CS v 0,1,..., nshift ngroup  nshift 1 for restricted sets

*3GPP TS 36.211 Table 5.7.2-2

15 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016
 PrachCS and rootSeqIndex
- PrachCS defines the number of cyclic shifts (in terms of
number of samples) used to generate multiple preamble
sequences from a single root sequence
- Example based on PrachCS=12 -> number of cyclic shifts: 119
• Root sequence length is 839 so a cyclic shift of 119
samples allows ROUNDDOWN (839/119)= 7 cyclic shifts
before making a complete rotation (signatures per root
sequence)
- 64 preambles are transmitted in the PRACH frame. If one root
is not enough to generate all 64 preambles then more root
sequences are necessary
• To ensure having 64 preamble sequences within the cell it
is necessary to have ROUNDUP (64/7)= 10 root sequences
per cell

rootSeqIndex
LNCEL;0…837;step 1;
No default

16 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PRACH Cyclic Shift - rootSeqIndex
Extract from 3GPP TS 36.211 Table 5.7.2.-4 ( Preamble
Formats 0-3). Mapping between logical and physical root
- RootSeqIndex points to the first root sequence to be sequences.
used when generating the set of 64 preamble
sequences. Logical Physical root sequence index (in increasing order of the
- Each logical rootSeqIndex is associated with a single root corresponding logical sequence number)
sequence
physical root sequence number. number
- In case more than one root sequence is necessary the
consecutive number is selected until the full set is
0–23 129, 710, 140, 699, 120, 719, 210, 629, 168, 671, 84, 755, 105,
generated 734, 93, 746, 70, 769, 60, 779
2, 837, 1, 838

24–29 56, 783, 112, 727, 148, 691

Recommendation: 30–35 80, 759, 42, 797, 40, 799
Use different rootSeqIndex across neighboring cells
means to ensure neighbor cells will use different 36–41 35, 804, 73, 766, 146, 693
preamble sequences
42–51 31, 808, 28, 811, 30, 809, 27, 812, 29, 810

52–63 24, 815, 48, 791, 68, 771, 74, 765, 178, 661, 136, 703

rootSeqIndex …. …..
LNCEL;0…837;step 1; 64–75 86, 753, 78, 761, 43, 796, 39, 800, 20, 819, 21, 818
No default
810–815 309, 530, 265, 574, 233, 606
Recommendation: Plan different logical root sequence
816–819 367, 472, 296, 543
numbers to generate different physical root sequence
numbers. 820–837 336, 503, 305, 534, 373, 466, 280, 559, 279, 560, 419, 420,
240, 599, 258, 581, 229, 610

17 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Support of high speed users
• If prachHsFlag = true the following rootSeqIndex values can be selected depending on prachCS
(restricted set) prachHsFlag
0 (false), 1 (true)
Default 0 (false)

Cell range Required amount of prachCS Possible range for rootSeqIndex

root sequences
< 1.0 km 4 0 24...816
< 1.4 km 6 1 30…810
< 2.0 km 6 2 36…804
< 2.6 km 8 3 42…796
< 3.4 km 9 4 52…787
< 4.3 km 11 5 64…779
< 5.4 km 14 6 76…764
< 6.7 km 17 7 90…749
< 8.6 km 20 8 116…732
< 10.6 km 26 9 136…704
< 13.2 km 32 11 168…676
< 17.2 km 44 11 204…526
< 21.5 km 64 12 264…566
< 27.7 km 64 13 328…498
< 32.8 km 64 14 384…450

18 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Preamble generation – High Speed Case

high-
speed set With
preamble
no delay spread delay spread = 5,2 µs guard

NCs sign. per

Configuration NCS root seq. #root seq. µs km µs km Guard NCS µs km µs km
0 15 18 4 14.3 2.15 9.1 1.37 2.25 12.75 12.2 1.82 7.0 1.04
1 18 15 6 17.2 2.57 12.0 1.79 2.25 15.75 15.0 2.25 9.8 1.47
2 22 12 6 21.0 3.15 15.8 2.37 2.25 19.75 18.8 2.82 13.6 2.04
3 26 10 8 24.8 3.72 19.6 2.94 2.25 23.75 22.6 3.40 17.4 2.62
4 32 8 9 30.5 4.58 25.3 3.80 2.25 29.75 28.4 4.26 23.2 3.48
5 38 7 11 36.2 5.44 31.0 4.66 2.25 35.75 34.1 5.11 28.9 4.33
6 46 6 14 43.9 6.58 38.7 5.80 2.25 43.75 41.7 6.26 36.5 5.48
7 55 4 17 52.4 7.87 47.2 7.09 2.25 52.75 50.3 7.54 45.1 6.76
8 68 4 20 64.8 9.73 59.6 8.95 2.25 65.75 62.7 9.40 57.5 8.62
9 82 3 26 78.2 11.73 73.0 10.95 2.25 79.75 76.0 11.41 70.8 10.63
10 100 2 32 95.4 14.30 90.2 13.52 2.25 97.75 93.2 13.98 88.0 13.20
11 128 2 44 122.1 18.31 116.9 17.53 2.25 125.75 119.9 17.99 114.7 17.21
12 158 1 64 150.7 22.60 145.5 21.82 2.25 155.75 148.5 22.28 143.3 21.50
13 202 1 64 192.6 28.89 187.4 28.11 2.25 199.75 190.5 28.57 185.3 27.79
14 237 1 64 226.0 33.90 220.8 33.12 2.25 234.75 223.8 33.58 218.6 32.80

19 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PRACH Planning - Wrap Up

• Steps:
• 1. Define the prachConfIndex
• Depends on preamble format (cell range)
• It should be the same for each cell of a site
• 2. Define the prachFreqOff
• Depends on the PUCCH region
• It can be assumed to be the same for all cells of a network (simplification)
• 3. Define the PrachCS
• Depends on the cell range
• If for simplicity same cell range is assumed for all network then prachCS is the same for all cells
• 4. Define the rootSeqIndex
• It points to the first root sequence
• It needs to be different for neighbor cells
• rootSeqIndex separation between cells depends on how many are necessary per cell (depends
on PrachCS)

20 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Exercise
- Plan the PRACH Parameters for the sites below:

- Assumptions:
• PUCCH resources =6
• Cell range = 12km (all cells have same range)
• BW:10MHz

PrachConfInde PrachFreqOf rootSeqInde

Sites Cell Azimuth x f PrachCs x
1 0
A 2 120
3 240
1 0
B 2 120
3 240
1 0
C 2 120
3 240
1 0
D 2 120
3 240
1 0
E 2 120
3 240

21 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Solution (1/3)
• Steps:
1. Define the prachConfIndex
• Cell Range is 12 Km therefore Format 0 is
• planned
• For start RACH density 1 is selected
• Therefore:
• prachConfIndex = 3, for example the same in
• all the cells

• 2. Define the prachFreqOff

• We assume that PRACH area is placed at the upper border of the UL frequency band then:

PRACH-Frequency Offset= NRB -6- roundup [PUCCH resources/2]

(NRB = 50 for 10 MHz (1...50) & PUCCH resources = 6)
prachFreqOff = 50 – 6 – roundup[6/2] = 41

22 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Solution (2/3)
• Steps:
• 3. Define the prachCs
• Cell range is 12 Km therefore the prachCS = 11
• In this case there are 93 cyclic shifts to generate the
• preambles and 9 signatures per root sequence

• 4. Define the rootSeqIndex

• There are in total 838 root sequences
• There are 8 root signatures required per cell
• The planning could be done to allocate the
• rootSeqIndex per cluster
• We assume that the planned cells in the example are belonging to one cluster
• In this way the first cell is taking the rootSeqIndex= 0..7, the second cell 8..15, the third cell
16..23 and so on

23 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Solution (3/3)
- The final planning below:

- Assumptions:
• PUCCH resources =6
• Cell range = 12km (all cells have same range)
• BW:10MHz

PrachFreqOf
Sites Cell Azimuth PrachConfIndex f PrachCs rootSeqIndex
1 0 3 41 11 0
A 2 120 3 41 11 8
3 240 3 41 11 16
1 0 3 41 11 24
B 2 120 3 41 11 32
3 240 3 41 11 40
1 0 3 41 11 48
C 2 120 3 41 11 56
3 240 3 41 11 64
1 0 3 41 11 72
D 2 120 3 41 11 80
3 240 3 41 11 88
1 0 3 41 11 96
E 2 120 3 41 11 104
3 240 3 41 11 112

24 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

25 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PCI Planning - Introduction
phyCellId:
Physical Cell Id
• There are 504 unique Physical Cell IDs (PCI) LNCEL; 0..503; 1; -
• Physical Layer Cell Identity = (3 × NID1) + NID2 (Range; Step; Default)

NID1: Physical Layer Cell Identity group. Range 0 to 167

• Defines SSS sequence
• NID2: Identity within the group. Range 0 to 2
• Defines PSS sequence
PCI impacts the allocation of resource elements to the
reference signal and the set of physical channels

Resource element allocation to

the Reference Signal

• Allocation pattern repeats every 6th Physical Layer Cell

Identity

First: PSS and SSS signals:

The PSS is generated out of 3 different sequences – each of these sequences indicates one Physical Layer
Cell Identity
The SSS is generated out of 168 sequences – each of these sequences indicates one Physical Layer Cell
Identity Group

26 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PCI Planning

• Maximum isolation between cells with the same PCI

- To ensure that UE never simultaneously receive the same identity from more than a single cell
- Physical Cell Identity is defined by the parameter phyCellID:

Parameter Object Range Default

phyCellId LNCEL 0 to 503 Not
Applicable

• There should be some level of co-ordination across international borders when allocating PCIs.
– This will help to avoid operators allocating the same identity to cells on the same RF carrier and in
neighboring geographic areas

27 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Physical Cell identification and Global Cell ID
identification

Physical Layer Cell ID (PCI)

- The sequence to generate the Reference Signal depends upon

the PCI
- Short repetition cycle of 1 ms
- Limited to 504 values so not unique
- Careful assignment needed because a UE shall never receive
the same value from 2 different cells

77 77

Global Cell ID (ECGI)

• E-UTRAN Cell Global identifier

• Part of SIB 1
• SIB 1 is sent once every 20ms
• Unique in the network: constructed from MCC, MNC en E-UTRAN Cell Identifier

ECGI ( E-UTRAN Cell Global Identifier) is used to identify cells globally. It can change (if necessary) once every
80ms but then it is repeated 3 times before it can be changed again

28 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PCI Planning - Recommendations
• In priority order, number 1 most important (all four
should be fulfilled, ideally) Id = 0 Id = 6
Id = 2 Id = 8

1. Avoid assigning the same PCI to neighbor cells Id = 1 Id = 7

Id = 3 Id = 9

2. Avoid assigning the same mod3 (PCI) to Id = 5 Id = 11

‘neighbor’ cells
Id = 4 Id = 10

3. Avoid assigning the same mod6(PCI) to ‘neighbor’

Example 1 PCI Identity Plan
cells

4. Avoid assigning the same mod30 (PCI) to ‘neighbor’

cells

Example 2 PCI Identity Plan

29 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

30 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

UL Reference Signal - Overview
UL DM RS allocation per slot for
• Types of UL Reference Signals Normal Cyclic Prefix
- Demodulation Reference Signals (DM RS)
• PUSCH/PUCCH data estimation
- Sounding Reference Signals (SRS)
• Mainly UL channel estimation UL (not in RL30)
DM RS is characterised by:
- Sequence (Zadoff Chu codes)
- Sequence length: equal to the # of subcarriers used for
PUSCH transmission (multiple of 12)
- Sequence group:
- 30 options
- Cell specific parameter
- Cyclic Shift: UE and cell specific parameter

31 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

UL DM Reference Signal - Need for Planning

• Issue: UL DM RS allocation per slot for

Normal Cyclic Prefix
- DM RS occupy always the same slot in time domain
- In frequency domain DM RS of a given UE occupies the
same PRBs as its PUSCH/PUCCH data transmission
- Possible inter cell interference for RS due to
simultaneous UL allocations on neighbor cells
• No intra cell interference because users are
separated in frequency
• Possible inter cell interference

• Scope of planning:
- DM RS in co-sited cells needs to be different

32 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 RS Sequences and RS Sequence Groups - Sequence
Group Id, ‘u’
- RS sequences for PUSCH have different lengths depending the UL bandwidth allocated for a UE
- 30 possible sequences for each PRB allocation length of 1-100 PRBs
- Sequences are grouped into 30 groups so they can be assigned to cells (different sequence group to
different cells)
- Sequence group number ‘u’:

grpAssigPUSCH
defines the assigned PUSCH
u PCI  grpAssigPUSCH mod 30 group
LNCEL; 0..29; 1; 0

6 or more PRBs there are two sequences per group, for a given PRB allocation length.
With sequence hopping, there are 2x30=60 sequences for 6 or more PRBs

33 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Cyclic Shift
- Additional sequences can be derived from a basic sequence by applying a cyclic shift
- The reference signals derived from different cyclic shift of the same basic reference signal are
orthogonal
- The basic reference signal length is 12 therefore up to 12 cyclic shifts can be derived
- However in practice not 12 but maximum 8 cyclic shifts of a basic sequence are derived given by the
parameter ulRsCs = 0..7
• The main reason to use only 8 cyclic shifts is to preserve the orthogonality between the
reference signals
- Cyclic Shifts of a basic reference sequence are used to multiplex RS from different UEs within a cell

- Note that Cyclic shifts of an extended ZC sequence are not fully orthogonal, but have low cross-
correlation
• An extended sequence is a sequence with the length multiple of 12, e.g. 36, 72, …

• ulRsCs
Defines cyclic shift of UL
RS
LNCEL; 0..7; 1; 0

34 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 UL DM Reference Signal - Hopping Techniques
- Reason for Hoping: Simultaneous UL allocation on neighboring cells can have different bandwidth -> prevent RS cross-
correlation between cells
- Sequence Hopping
• Intra-Subframe hopping between two sequences within a sequence group for allocations larger than 5PRBs
• Only enabled is Sequence Group hopping in disabled
• Not enabled in RL30: ulSeqHop= false
- Sequence Group Hopping
• In each slot, the UL RS sequences to use within a cell are taken from one specific group
• If group varies between slots: Group hopping
• Group Hopping not enabled in RL30: UlGrpHop = false
- Group is the same for all slots
- Cyclic Shift Hopping
• Always used
• Cell specific cyclic shift added on top of UE specific cyclic shift

If RB allocations is 5 or less, there is only one base sequence per group whereas for allocations of more
than 5 PRBs there are 2 RS base sequences per group.

35 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Planning - From Theory to Practice… (1/2)
• Theory:
- It should be possible to assign to the cells of one site the same sequence group ‘u’ and
‘differentiate’ the sequences using different cell specific cyclic shifts i.e. allocating different ulRsCs

Remember!: Cyclic shifts of an extended ZC sequence are

not fully orthogonal, but have low cross-correlation

36 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Planning - From Theory to Practice… (2/2)
PCI grpAssigPusch sequence id u ulRsCs cinit
• Practice: 75 0 15 0 79
- It doesn’t seem to work 76 29 15 4 79

- UL Throughput gets considerably affected if UL traffic in neighbor cell

• From 40 Mbps to ~ 22 Mbps in the example

37 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Planning - New rule
- Allocate different sequence group u for every cell, including cells of the same site
• Cross-correlation properties between sequences from two different groups are good because of
sequence grouping in the 3GPP spec
- ulRsCs does not matter (it is only relevant for sequences within one seq group u)

38 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Planning - Results
- UL Throughput still suffers from UL interference in neighbor cell but the effect is lower

PCI grpAssigPusch sequence id u ulRsCs cinit

75 0 15 0 79
76 0 16 0 80

39 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Pros an cons of the new planning rule
- [+]: Results seem to be better
- [+]: Less parameters to plan, only PCI planning needed

• UlRsCs only relevant when using sequences of the same group

• ‘u’ will be different if PCI module 3 rule is followed. In that case ‘grpAssigPUSCH’ value is not relevant

- [ -]: Reduced group reuse distance compared to the case of assigning the same group per each site

u PCI  grpAssigPUSCH mod 30

40 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

UL DM RS Planning - Wrap up
• Principle: DM RS needs to be different in cells from a same eNodeB

• Current planning approach:

– Assign different sequence group number ‘u’ to the cells of the same site. Range: [0…29].
grpAssigPUSCH can be constant =no need for planning

u PCI  grpAssigPUSCH mod 30

• If cells of the site follow the PCImod3 rule, the sequence group number ‘u’ will be different

• If PCImod3 rule is not followed, check PCImod30 rule

- If problems use grpAssigPUSCH to differentiate the ‘u’ - sequence group number-

• If same ‘u’ has to be used in neighboring cells and cannot be changed using grpAssigPUSCH then
assign different ulRsCs to the cells of a site. Range [0…7]

41 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Group hopping for UL reference signal

• This feature randomises the sequence used to generate the:

• Demodulation Reference Signal for the PUCCH
• Demodulation Reference Signal for the PUSCH
• Sounding Reference Signal (SRS)
• Helps to improve performance when the ‘PCI mod 30’ rule was not followed during the
PCI planning process
• reduces risk of potential issues caused by cross-talk between neighboring cells
• UE are informed whether group hopping is enabled or disabled using SIB2 content

actUlGrpHop
Activation of uplink group hopping
LNCEL; 0 (False); 1 (True); 1

43 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Group hopping for UL reference signal
• Uplink Reference Signals are:
• Demodulation Reference Signal for PUCCH
• Demodulation Reference Signal for PUSCH
• Sounding Reference Signal (SRS)

PUCCH Formats PUCCH Formats 2, 2a, PUSCH SRS

1, 1a, 1b 2b

44 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Group hopping for UL reference signal
Group Allocation
• The allocated group for a cell is not planned explicitly but is calculated from:

Group u  f gh (ns )  f ss mod 30

PCI

PUCCH & SRS

0 if group hopping is disabled f ssPUCCH  N ID

cell
mod 30
f gh (ns ) 
i 0 c(8ns  i) 2i  mod 30
7
if group hopping is enabled
 PUSCH

 
f ssPUSCH  f ssPUCCH   ss mod 30

Psuedo random sequence initialised using

ROUNDDOWN [PCI / 30] Configurable Offset
(grpAssigPUSCH)

45 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Group hopping for UL reference signal
PCI Planning (I)
• The Sequence Shift (SS) part of the group selection (repeated below from the previous slide) leads
to a ‘PCI mod 30’ planning rule

f ssPUCCH  N ID
cell
mod 30 
f ssPUSCH  f ssPUCCH   ss mod 30 
• Neighboring cells should not be allocated PCI values with equal ‘PCI mod 30’
• This ensures that different base groups are allocated to neighboring cells

46 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Group hopping for UL reference signal
PCI Planning (II)
• When group hopping is enabled, cells with different PCI but equal ‘PCI mod 30’ results use different
hopping patterns
• helps to protect against scenarios where the ‘PCI mod 30’ rule has not been obeyed

0 if group hopping is disabled

f gh (ns ) 
 i ) 2i  mod 30 if group hopping is enabled
7

 i 0
c(8ns


leads to 17 hopping patterns

Psuedo random sequence initialised using (504 / 30 = 16.8)
ROUNDDOWN [PCI / 30]

• For example, PCI 1 and 31 use the same base sequence group when hopping is disabled, but use
different hopping patterns when hopping is enabled

47 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 UL-DM-RS planning conclusion

It is recommended by Nokia to enable group hopping feature

(LTE801) to relax the planning requirements to ordinary PCI
planning.

48 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

49 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PDCCH Overview
- The PDCCH carries the UL & DL scheduling assignments
- A PDCCH is transmitted on an aggregation of one 1, 2, 4 or 8 control channel elements (CCE). A CCE
consists of 36 REs
- The aggregations of CCEs have a tree structure, where an aggregation consisting of n CCEs starts on
position (i mod n), where i is the CCE number
- Further restrictions on the aggregations are defined with a Hashing function

pdcchAggDefUE
PDCCH LA UE default aggregation; used, when
enableAmcPdcch disabled or no valid CQI exists
LNCEL; 1(0), 2 (1), 4 (2), 8 (3); -; 4 (2)

The target error probability for a missed detection of a PDCCH is 10 -2

50 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PDCCH Dimensioning
• Scope: Optimize the resources reserved for PDCCH as they represent an overhead via maxNrSymPdcch
• Note that in RL30 with the feature LTE616: Usage based PDCCH adaptation the number of OFDM symbols for
PDCCH is dynamically adapted
- PDCCH resources are accounted in terms of CCEs that can also be aggregated in groups of 1, 2, 4 or 8 CCE.
• 1 CCE = 9 Quadruplets = 36 RE
• The higher the aggregation the more robust PDCCH (e.g. good at cell edge)
- Max. number of CCE for PDCCH depends on the bandwidth and the parameter maxNrSymPdcch

Maximum number of
CCE for different BW

• As PDCCH carriers the DCI not all the CCE are available for allocating user plane resources
– Some of those CCEs broadcast DCI for system information and paging

Table above assumes no quadruplets have been allocated to PHICH and 4x4 MIMO is not used.
Each DCI format includes a 16 bit CRC scrambled by an RNTI. RNTI is used to address the appropriate UE. RNT also provides indication of the
information content of the resource allocation: resources for paging messages on PDSCH, resources for system information messages on PDSCH,
resources for application data or Signaling, resources for TPC commands.

51 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PDCCH Dimensioning - maxNrSymPdcch
- maxNrSymPdcch defines how many symbols per subframe (1ms) are dedicated to carry PDCCH resources
- Considerations when planning the parameter value:
• Max. number of simultaneous UL and DL grants to be scheduled per TTI maxNrSymPdcch
• Desired aggregation level for users at cell edge: LNCEL; 1..3; 1; 3

- if not enough PDCCH capacity available scheduling will be blocked

• Additional DL overhead introduced by increasing the number of PDCCH symbols and its impact on the max
achievable user throughputs
- Recommendation: maxNrSymPdcch = 2 required to support 10UEs per TTI in RL10 & RL 20
• Information coming from Integration &Verification (I&V) for 20MHz BW.
• It could be possible than in 10MHz value 3 is needed
- In RL30 maxNrSymPdcch = 3 since the actual size will be dynamically adapted

52 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

53 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PUCCH Dimensioning
• Scope: Dimensioning of the PUCCH region (how many RBs) to avoid excessive overheads
- PUCCH is used to transfer Uplink Control Information (UCI) when the PUSCH is not in use through
different PUCCH formats:

• PUCCH is allocated RBs at the 2 edges of the channel BW

– To avoid fragmenting PUSCH RBs
– To provide frequency diversity
• PUCCH always occupies 2 RBs distributed across the two time slots of a subframe
• Each PUCCH transmission uses 1 RB on each side of the channel bandwidth

Note: RB in here corresponds to 3GPP definition of 12

Transmission from a single UE subcarriers x 1 slot

54 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PUCCH Structure nCqiRb
pucchnanCS
Number of cyclic shifts for
reserved RBs per slot for
PUCCH formats 1/1a/1b in the
PUCCH formats 2/2a/2b
- The logical split between the PUCCH formats is the following: mixed region
LNCEL; 1..98; 1; 2
- 1. Resources allocated for format 2/2a/2b i.e. CQI LNCEL; 0..7; 1; 0
(0 means no use of mixed
• Number of resource blocks (RBs) defined by the parameter nCqiRb
formats )
• The Parameter is semistatic allocated (and broadcasted)
• Depends on the number of RRC connected UEs
• Allocated on the outermost RBs (edge of the
UL bandwidth)
- 2. Resources allocated for format 1/1a/1b
• Semistatic allocation for Scheduling
Request Information (SRI)
• For SRI the parameter n1pucchAn is used
to calculate the number of RBs (the parameter
is broadcasted)
• It depends on the number of RRC connected UEs
• Dynamic allocation for ACK/NACK
• The number of RBs for ACK/NACK depends
on the total number of scheduled UEs
- 3. Mixed formats 1 & 2
• Used for small bandwidth (e.g. 1.4 MHz)
• pucchNanCS parameter used to calculated the number
of RBs for mixed formats

n1PucchAn
Offset to calculate ACK/NACK
resources from PDCCH CCE
LNCEL; 0..2047; 1; 36

55 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

PUCCH UEs Multiplexing in One Resource Block
- For formats 2/2a/2b UEs are separated using CDM (code division multiplexing) inside the RB
• CDM is using the cyclic shift of the length 12 CAZAC sequence
• The number of cyclic shifts is given by the parameter deltaPucchShift
• deltaPucchShift = 1,2,3 indicating 12, 6 or 4 shifts
• With 12 shifts 12 UEs could be multiplexed in one RB, with 6 shifts 6 UEs could be multiplexed and so on
• It is recommended that no more than 6 UEs are multiplexed per RB (even if 12 are possible) to minimize interference
- For formats 1/1a/1b on top of CDM also a block wise spreading with an orthogonal cover sequence is applied
• 3 orthogonal codes are used so the multiplexing capacity is 3 times increased
• If 6 cyclic shifts and 3 orthogonal codes are used then the multiplexing capacity is 6*3= 18 UEs per RB

PUCCH formats Control type Number of Bits Multiplexing Capacity (UE/RB)

PUCCH Format 1 Scheduling request ON/OFF keying 36, *18, 12
PUCCH Format 1a 1-bit ACK/NACK 1 36, *18, 12
PUCCH Format 1b 2-bit ACK/NACK 2 36, *18, 12
PUCCH Format 2 CQI 20 12, *6, 4
PUCCH Format 2a CQI + 1-bit ACK/NACK 21 12,* 6, 4
PUCCH Format 2b CQI + 2-bit ACK/NACK 22 12, *6, 4

deltaPucchShift
*typical value delta cyclic shift for PUCCH formats 1/1a/1b
LNCEL; 1..3; 1; 2 (i.e. 6 cyclic shifts)

56 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Number of Resource Blocks for formats 2/2a/2b
• The number of RBs required for formats 2/2a/2b
Con Number of Number CQI Periodicity
• depends on the number of RRC connected UEs fig RRC of RBs cqiPerNp
• Defined by maxNumRrc parameter connected nCqiRb
UEs
• Example configuration 2:
maxNumRrc
• CQI periodicity is 20 ms -> there are 20 TTIs transporting CQIs
• Assuming 6 UEs multiplexed per TTI and per RB then there
1. 840 (1680) 14 10 ms

are 6*20= 120 UEs (per 20 TTIs/ per RB)

2. 840 (1680) 7 20 ms
• So to support 840 RRC connected UEs we need:
840/120 = 7 RBs 3. 768 (1536) 4 32 ms
• Please note that only 6 cyclic shifts are used in order
4. 420 (840) 7 10 ms
• to avoid interference (even if 12 cyclic shifts possible)
• With 12 cyclic shifts 12 UEs are multiplexed per TTI 5. 480 (960) 4 20 ms
so the capacity is doubled (the number are in the
brackets in the table) 6. 384 (768) 2 32 ms

maxNumRrc 7. 240 (480) 2 20 ms

Max. number of Use in the cell with established RRC
connection 8. 120 (240) 2 10 ms
LNCEL; 0..1500; Step 1
1.4 MHz bandwidth 0 .. 40
3 MHz bandwidth 0 .. 120 9. 192 (384) 1 32 ms
5 MHz bandwidth 0 .. 600
10 MHz bandwidth 0 .. 750 10. 120 (240) 1 20 ms
15 MHz bandwidth 0 .. 1250
20 MHz bandwidth 0 .. 1500
Default
11. 60 (120) 1 10 ms
cqiPerNp
1.4 MHz bandwidth 20 CQI periodicity
3 MHz bandwidth 80 LNCEL; 2ms (2), 5ms (5),
5 MHz bandwidth 300 Number of RBs allocated for
10ms (10), 20ms (20), 40ms
10 MHz bandwidth 300 formats 2/2a/2b example
(40), 80ms (80) default:
15 MHz bandwidth 600 40ms(40)
20 MHz bandwidth 600
57 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016
 Number of Resource Blocks for formats 1/1a/1b – SRI
- The number of RBs for SRI depends on: deltaPucchShift n1PucchAn Number of
- parameter n1PucchAn (Ack/Nack offset relative to the RBs for SRI

Lowest CCE index of the associated DL scheduling PDCCH) 1 36 1

- Number of cyclic shifts deltaPucchShift 1 72 2

1 108 3
n1PucchAn * deltaPucch Shift
Number _ PUCCH _ RBs _ SRI roundup ( ) 1 144 4
3 *12
… … …
Example: Assuming that deltaPucchShift = 2 and the 1 360 10
periodicity of SRI is 20 ms (cellSrPeriod parameter) then
2 18 1
18 UEs could be multiplexed per TTI and per RB
So there are 20*18 = 360 UEs per 20 ms 2 36 2

Assuming that maximum number of RRC connections 2 54 3

maxNumRrc is 840 then we need roundup(840/360) = 3 RBs 2 72 4
for SRI
… … …
So the offset for Ack/Nack -> n1PucchAn = 54
2 180 10

3 12 1
cellSrPeriod
SRI repetition period … … …
LNCEL; 5ms(0), 10ms(1), 20ms(2), 40ms(3), 80ms(4); 20ms(2)
3 120 10

58 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Number of Resource Blocks for formats 1/1a/1b –
dynamic ACK/NACK
- The number of resource blocks for dynamic ACK/NACK is not fixed but it depends on the amount of
scheduled UEs
- For the dimensioning of PUCCH resources for ACK/NACK the total number of CCE (control channel
elements) available for PDCCH are considered :

TotalNumCC E * deltaPucch Shift

Number _ PUCCH _ RBs _ ACK / NACK roundup ( )
- The total number of CCEs depends on the system bandwidth: 3 *12
- Example: Assume that bandwidth is 10MHz and the deltaPucchShift is 2 then the number
of resource blocks for dynamic ACK/NACK is:

Bandwidth Total Number of CCEs

5 MHz 21

10 MHz 43
43 * 2
Number _ PUCCH _ RBs _ ACK / NACK roundup ( ) 3 15 MHz 65
3 *12
20 MHz 87

59 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Number of RBs for PUCCH – total
- The total number of RBs required for PUCCH is the sum of RBs required for CQI, for SRI and dynamic
ACK/NACK:

 TotalNumCC E  n1PucchAn* deltaPucch Shift 

Number _ PUCCH _ RBs nCqiRb  roundup  
 3 *12 

- If mixed formats 1/1a/1b and 2/2a/2b are supported for small bandwidth then the total number of RBs
for PUCCH is:

 pucchNAnCs * 3  
  TotalNumCC E  n1PucchAn   * deltaPucch Shift 
 deltaPucch Shift    pucchNAnCs 
Number _ PUCCH _ RBs nCqiRb  roundup     roundup  
3 *12  8 
 
 
 

60 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Carrier Aggregation
• Principles behind dependency between parameters like nCqiRb, n1PucchAn, deltaPucchShift and amount of PRBs
devoted for PUCCH are not affected by the introduction of the Carrier Aggregation

Format 2.x Format 1.x

Non-CA case – recap
𝑟𝑟𝑚𝑇𝑜𝑡𝑎𝑙𝑁𝑢𝑚𝐶𝐶𝐸+ 𝑛1𝑃𝑢𝑐𝑐ℎ𝐴𝑛
𝒓𝒆𝒒𝑷𝑼𝑪𝑪𝑯𝒓𝒆𝒔𝑺𝒊𝒛𝒆 = 𝑛𝑐𝑞𝑖𝑅𝑏+ ආ ඊ
3 ∗12
𝑑𝑒𝑙𝑡𝑎𝑃𝑢𝑐𝑐ℎ𝑆ℎ𝑖𝑓𝑡
Assumption:
no 4x2 MIMO and no PUCCH
blanking

ሺ𝑚𝑎𝑥𝑁𝑟𝑆𝑦𝑚𝑃𝑑𝑐𝑐ℎ ∗12 − 4ሻ ∗𝑑𝑙𝐶ℎ𝐵𝑤− #𝑃𝐻𝐼𝐶𝐻𝑔𝑟𝑜𝑢𝑝𝑠 ∗12 − 16

𝒓𝒓𝒎𝑻𝒐𝒕𝒂𝒍𝑵𝒖𝒎𝑪𝑪𝑬= ቞ ቟
36

This is the number of PRBs that are reserved for These are resources that are reserved for Scheduling
PUCCH formats 2/2a/2b, capacity for PUCCH Format Requests (Format 1.x), capacity for SRs depends on
2.x depends on the CqiPerNp the cellSrPeriod

These are resources that are reserved for ACK/NACK

(Format 1.x)

• However, the maximum number of the UEs that given amount of PUCCH resources could handle is reduced in contrast to the
cell not involved in the Carrier Aggregation
• This reduction is needed to make room for multi-cell ACK/NACKs that are processed by PCell alone

61 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Carrier Aggregation
• PUCCH resources are adjusted at once if only CAREL object is
created under given LNCEL what implies that this cell could play a
role of a primary cell in the Carrier Aggregation
• Note that if PUCCH size is extended, amount of PRBs to be used Note:
for PUSCH will be decreased. Consequently, UL cell capacity will maxNumCaConfUeDc
be compromised. parameter does not affect
the amount of PUCCH
• The cell playing a role of secondary one is not affected unless it resources configured to
plays also a role of the primary cell (symmetrical relation between convey multi-cell
PCell and SCell was created). ACK/NACK and taken out
from SR resources

It is likely the case that UL capacity will be compromised in contrast to

non-CA case because n1PucchAn has to be equal to at least 72 for
regular CA deployments

62 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Carrier aggregation for multi-carrier eNode Bs
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)

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

50/50 between SCell A and SCell B:

• UEs configured with SCell A got only odd numbered PUCCH 1b CS

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

63 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUSCH

All UL traffic (PUCCH as well as PUSCH) related to PCell and both SCells is
transmitted on the PCell, including all corresponding signaling needed for proper
handling of RRM algorithms in the SCells
Uplink Control Information to be considered here consists of ACK/NACK, CQI,
PMI and RI

R, UL
D L n on - G B
R,
DL GB er 1
t Carri
onen
Comp
n -G BR
DL no rier 2
ne nt Ca r
o
Comp
n -G BR
DL no er 3
ri
t Ca r
onen
Comp
CA capable UE

64 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUCCH
If CA is activated for a UE, there will be a need to transmit multi-cell ACK/NACK
messages – reports covering simultaneously all transport blocks for all cells
(PCell and two SCells)
- At maximum there are six transport blocks (one pair for each serving cell)

TB1 PCell TB2 PCell TB1 SCell 1 TB2 SCell 1 TB1 SCell 2 TB2 SCell 2

ACK/NACK ACK/NACK ACK/NACK ACK/NACK ACK/NACK ACK/NACK

This requires more data to be sent in a single ACK/NACK report than normally
available so PUCCH Format 3 is used (designed specifically for Carrier
Aggregation deployments with more than one SCell, where more than 4 bits of
HARQ information have to be reported)

65 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUCCH

DMRS

DMRS
• Introduced in R10 to support increased HARQ acks from CA.
•For FDD supports up to 5CC CA each with 2 acks- up to
HARQ 10 acks total.
•For TDD supports up to 5CC CA each with 2 acks, may have
to ack multiple frames, support up to 20HARQ acks total(further
mux can be used).
•Unlike format 1,1a,1b format 3 can transmit Scheduling
Request at the same time as the HARQ acks, (format 1,1a,1b
use a dedicated SR PUCCH resource) .
•Format 3 uses 5 orthogonal codes to differentiate UEs using
the same PUCCH resource (unlike format1) .
•The PUCCH 3 resource in use is signalled by n3PUCCH-AN- PUCCH format 3 uses the same
List parameter range 0-549 ( to all for 5 Ues per RB over 110
DMRS structure as format 2
RB).
•RRC signaling gives the UE 4 values of n3PUCCH-AN-List,
UE is dynamically allocated one of the 4 values via the TPC
command for PUCCH (different interpretation for PUCCH3).
This value determines the allocated RB and the orthogonal
code, (ie only 4 codes orthogonal codes used).

66 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUCCH nPucchF3Prbs
Number of PUCCH PRBs for
HARQ format 3
LNCEL: 0..1; 0
PUCCH Format 3 reports are sent in dedicated PRBs
allocated on the outer edge of PUCCH region
Number of PRBs dedicated for PUCCH Format 3 can be
adjusted using nPucchF3Prbs parameter
- In LTE1803 number of PRBs for PUCCH Format 3 is
restricted to 1 (nPucchF3Prbs=1)
In LTE1803, PRB dedicated for PUCCH Format 3 can carry
up to 4 such reports (contains four PUCCH Format 3
resources), meaning that it can simultaneously serve up to
4CA UEs with more than one SCell configured
Format 3 will be placed on the outer bandwidth after format
2 have been allocated.
Format 3 will be allocated within the area defined nCqiRB
but according to nPucchF3Prbs only 1 RB is used,
therefore nCqiRb needs to be increased by 1 to maintain
capacity for PUCCH Format 2 nCqiRB
PUCCH bandwidth for CQI
LNCEL: 0..98; 2

67 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUCCH

• PUCCH Format 3 resources are semi-

statically assigned to the given UE (similarly
as in case of Format 1b CS) and provided to
that UE in n3PUCCH-AN-List-r10 structure
• Each UE with more than one SCell
configured is assigned with four PUCCH
Format 3 resources
Value of ‘TPC ( 3, p )
• Exact resource that have to be used by the command for nPUCCH
PUCCH’
UE is dynamically signaled via TPC field The first PUCCH resource value
‘00’
• Value in the TPC field points to the position of the resource in configured by the higher layers
n3PUCCH-AN-List-r10 resource list The second PUCCH resource
‘01’ value configured by the higher
layers
The third PUCCH resource value
‘10’
configured by the higher layers
The fourth PUCCH resource value
‘11’
configured by the higher layers

68 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1803 DL Carrier Aggregation 3CC 40 MHz
PUCCH
Actual PUCCH Format that is used by the UE for HARQ feedback depends on in which cells the UE was scheduled in
corresponding DL TTI (in case both SCells are configured):
- PCell only – PUCCH Format 1a/1b or 2a/2b is used
- PCell and at least one of the SCells – PUCCH Format 3 is used
- any of the SCells (or both of them) – PUCCH Format 3 is used
In LTE1803 CSI cannot be multiplexed with PUCCH Format 3 reports
- If UE is scheduled from at least one SCell (it will use Format 3) – periodic CQI will be dropped

The CQI reports for PCell and SCells are sent according to the following pattern:

real PCell CQI periodicity

cqiPerNp real SCell CQI periodicity

PCell CQI SCell1 CQI PCell CQI SCell2 CQI PCell CQI SCell1 CQI … time

For the UEs with added (but not activated) secondary cells:
• CQI periodicity for CQIs related to PCell increased from cqiPerNp (non-CA case) to 2*cqiPerNp
• No CQIs for the SCells are sent

For the UEs with added and activated (not scheduled) secondary cells:
• CQI periodicity for CQIs related to both SCells is 4*cqiPerNp

69 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1562: Carrier aggregation for multi-carrier eNode Bs
Configuration Management

New parameters

Abbrev Full name MO

maxNumScells Max number of secondary cells for DL carrier aggr LNCEL

maxNumCaConfUe3c Max number carrier aggr configured UEs 3 Carriers LNCEL

maxNumCaConfUe Max number carrier aggr configured UEs LNCEL

nPucchF3Prbs Number of PUCCH PRBs for HARQ format 3 LNCEL

70 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 LTE1804: Downlink carrier aggregation 3CC - 60
Impact on PUCCH capacity

PUCCH re-dimensioning:
• Restrictions related to 2CC CA case are still • Cell being a SCell is not affected unless it
effective becomes a PCell
• Restrictions introduced with LTE1803: • PUCCH resources are adjusted once CAREL
− Introduction of PUCCH Format 3 needed for object is created under the LNCEL, i.e. the cell is
3CC CA UEs enabled to be a PCell
• Additional restrictions introduced with • The bigger PUCCH size, the less PRBs for
LTE1804: PUSCH are left, which decreases UL cell capacity
− Maximum number of PRBs for PUCCH Format 3
is increased to 2

PUSCH PUCCH

2CC impact + LTE1803

impact
+ LTE1804
impact

71 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization (LTE1808)
Feature Overview
• PUCCH capacity optimization automatically adjusts the PUCCH resource size according to the actual
traffic load in the LTE cell.
• It evaluates cell’s performance counters for a defined period of time and determines adjustment
needed to Admission control parameters (i.e., maxNumRRC, maxNumRRCEmergency,
maxNumActDrb, maxNumActUE and maxNumQci1Drb) as per traffic load in the cell.
• Based on the adjustment to Admission control parameters, it does the adaptation of PUCCH size
adjusting the values for the parameters: nCqiRb and n1PucchAn. Additionally, PUCCH Periodicity
parameters (cellSrPeriod and cqiPerNp) are also adjusted.
• In order to ensure that PUCCH resources do not overlap with PRACH resources, changes in PUCCH
size would trigger check for consistency of PRACH assignment, i.e., check/recalculation of PRACH
parameters.
• The finally proposed changes are saved to a plan and provisioned to the network automatically
eventually increasing efficient usage of resources and efficiency of the network.

72 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
High level use case
Detect Resolve Keep control

Detect cells which needs increase or Automated optimization actions for Result visualization,
decrease in PUCCH resources based user cases: activation/deactivation and
on the evaluation of their KPIs • Auto adjust admission control configurability giving full user control
parameters
Detect cells with high/low utilization • Auto adjust PUCCH parameters as
• Evaluate KPIs per changes in admission control
• Find cells with high utilization of parameters
PUCCH resource • Auto adjust PRACH parameters as
• Find cells with low utilization of per changes in PUCCH
PUCCH resources parameters

73 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
KPI/Counter Collection

KPI/Counter Collection

Send and apply Optimization Decision

modifications to eNB based on KPIs

Automatic PUCCH
Capacity Optimization

Re-adjust Admission
control and PRACH Adjust admission control
parameters, if needed parameters

Adjust PUCCH size

parameters

74 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Optimization Decision based on KPI/counter (1/2)
KPI/Counter
• The ratio of the number of RRC connected UEs over the Collection
configured maximum RRC connected UEs is taken as follows:

RRC_CONN_UE
percentRRCConn 100 * Send and
maxNumRRC apply
Optimization
Decision
modifications
based on KPIs
• The resulting value is compared against configurable to eNB

thresholds to decide if adjustments to PUCCH is needed

1) ThrPucchSizeUpper (in %)
Automatic
• If the percentage of actual number of connected UEs from PUCCH
counter percentRRCConn is above ThrPucchSizeUpper, Capacity
then PUCCH size must be increased Optimization
2) ThrPucchSizeLower (in %)
• If the percentage of actual number of connected UEs from Re-adjust
Admission Adjust
counter percentRRCConn is below ThrPucchSizeLower, control and admission
then PUCCH size must be decreased PRACH control
parameters, if parameters
needed

• P.T.O
Adjust PUCCH
size
parameters

75 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Optimization Decision based on KPI/counter (2/2)

Trigger to Increase PUCCH size Trigger to Decrease PUCCH size

Actual # Actual #

% wrt to % wrt to
maxNumRRC maxNumRRC

maxNumRRC 100% maxNumRRC 100%

RRC_CONN_UE percentRRCConn

(ThrPucchSizeUpper* ThrPucchSizeUpper (ThrPucchSizeUpper* ThrPucchSizeUpper

maxNumRRC) maxNumRRC)

(ThrPucchSizeLower* (ThrPucchSizeLower*
ThrPucchSizeLower maxNumRRC) ThrPucchSizeLower
maxNumRRC)

RRC_CONN_UE percentRRCConn

76 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Adjustment of Admission control parameters (1/5)
KPI/Counter
Collection
• When adaptation of PUCCH size is triggered from
previous step, new values for admission control
parameters are calculated
Send and
• The parameter maxNumRRC is the first parameter apply
Optimization
Decision
adjusted as counter used to trigger algorithm is in modifications
to eNB
based on KPIs
reference to number of RRC connected Ues
• The new value for maxNumRRC is calculated to
ensure that actual number of RRC connected Ues is Automatic
between the thresholds (ThrPucchSizeUpper*maxNumRRC) PUCCH
and (ThrPucchSizeLower*maxNumRRC) Capacity
Optimization
• The other admission control parameters are adjusted
according to how much maxNumRRC was adjusted Re-adjust
Admission Adjust
control and admission
PRACH control
parameters, if parameters
needed

Adjust PUCCH
size
parameters

77 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Adjustment of Admission control parameters (2/5)

Actual # Actual #

UpperLimit_maxNumRRC UpperLimit_maxNumRRC

newMaxNumRRCEmergency

newMaxNumRRC

maxNumRRCEmergency

maxNumRRC ThrPucchSizeUpper*maxNumRRC

RRC_CONN_UE RRC_CONN_UE

ThrPucchSizeUpper*maxNumRRC maxNumActDrb

ThrPucchSizeLower*maxNumRRC
maxNumActUE
maxNumActDrb

ThrPucchSizeLower*maxNumRRC

maxNumActUE

numActUELower numActUELower

78 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Adjustment of Admission control parameters (3/5)

UpperLimit_maxNumRRC UpperLimit_maxNumRRC

maxNumRRCEmergency

maxNumRRC

newMaxNumRRCEmergency

ThrPucchSizeUpper*maxNumRRC
newMaxNumRRC

maxNumActDrb
ThrPucchSizeUpper*maxNumRRC
ThrPucchSizeLower*maxNumRRC

RRC_CONN_UE
RRC_CONN_UE

maxNumActDrb
maxNumActUE ThrPucchSizeLower*maxNumRRC

maxNumActUE

numActUELower numActUELower

79 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization An
i
Sl ma
id ted
Adjustment of Admission control parameters (4/5) es

• The new parameter maxNumUEConn defines adaptMaxUEConn

the upper limit for the adaptation of
UpperLimit
=0
maxNumActUE maxNumRRC
• The algorithm will never increase
maxNumActUE beyond maxNumUEConn
• A new flag adaptMaxUeConn is introduced to
allow for the feature to adjust maxNumUEConn
• When adaptMaxUEConn is set to 0, maxNumRRCEmergency
adjustments are made with the limitation that
maxNumRRC
maxNumActUE only can be adjusted by the
algorithm within the range defined by the lower
limit and maxNumUEConn ThrPucchSizeUpper*maxNumRRC

Note:
• maxNumUEConn maxNumActDrb

• adaptMaxUEConn ThrPucchSizeLower*maxNumRRC

New Parameter ( Name:

• numActUELower Max Num Connected UEs
maxNumActUE
- maxNumUEConn)
are all NetAct parameters

maxNumActUE
lower limit

80 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization An
i
Sl ma
id ted
Adjustment of Admission control parameters (5/5) es

• A new flag adaptMaxUeConn is adaptMaxUEConn

introduced to allow for the feature =1
to adjust maxNumUEConn UpperLimit
maxNumRRC
• When adaptMaxUeConn = 1,
maxNumUEConn can be adjusted
when needed (need to increase
maxNumActUE above current value
of maxNumUeConn)
maxNumRRCEmergency
• The algorithm only increases the
limit maxNumUEConn, never maxNumRRC

decrease. A lower limit can be

defined by manual configuration of
ThrPucchSizeUpper*maxNumRRC
maxNumUECon
• Adjustment of maxNumUEConn
allows for more flexible PUCCH maxNumActDrb

adaptation ThrPucchSizeLower*maxNumRRC

New Parameter ( Name: maxNumActUE

Max Num Connected UEs
- maxNumUEConn)

maxNumActUE
lower limit due to
minimum PUCCH
resources

81 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Adjustment of PUCCH size
KPI/Counter
Collection

• The adjustment of PUCCH size assures that the

new values of admission control parameters can
be supported in terms of PUCCH resources Send and
Optimization
apply
- In particular, new values of maxNumRRC and (if modifications
Decision
based on KPIs
needed) maxNumRRCEmergency to eNB

- These calculations are based on existing consistency

checks between PUCCH parameters and admission
control parameters Automatic
PUCCH
• The feature mainly adapt nCqiRb and n1PucchAn
Capacity
Optimization

Re-adjust
Admission Adjust
control and admission
PRACH control
parameters, if parameters
needed

Adjust PUCCH
size
parameters

82 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Re-adjustment of admission control and PRACH parameters
KPI/Counter
Collection

• After appropriate adjustment of PUCCH size, the

new values of admission control parameters are
rechecked if new value is needed Send and
Optimization
apply
• In addition, prachFreqOffset is adjusted if needed modifications
Decision
based on KPIs
to eNB
- Adjustment to prachFreqOffset is needed when
PRACH and PUCCH allocation is overlapping after
PUCCH adaptation
Automatic
- The feature LTE1808 triggers the PRACH SON
PUCCH
features to align PRACH parameters with newly
Capacity
adapted PUCCH parameters Optimization

Re-adjust
Admission Adjust
control and admission
PRACH control
parameters, if parameters
needed

Adjust PUCCH
size
parameters

83 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Apply modifications to eNodeB
KPI/Counter
• The algorithm shall create a plan with all the Collection
proposed changes to admission control, PUCCH
and PRACH parameters
• It is possible to configure whether:
Send and
Optimization
apply
1. Operator wants NetAct to automatically modifications
Decision
based on KPIs
activate modifications OR to eNodeB

2. Operator wants to manually activate the

proposed changes Automatic
• Note that modifications of PUCCH parameters PUCCH
(nCqiRb and n1PucchAn) require object locking, Capacity
Optimization
as well as PRACH parameter modification
requires BTS restart
Re-adjust
Admission Adjust
control and admission
PRACH control
parameters, if parameters
needed

Adjust PUCCH
size
parameters

84 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Automatic PUCCH Capacity Optimization
Summary

PUCCH
increase
Increase in PUCCH capacity when more
UEs are connected
 Automatic response to gradual increase in LTE penetration
 Provide service to more UEs

Decrease PUCCH capacity when less UEs

are connected
 Efficient resource allocation between control (PUCCH) and
data
 More resources are available for data traffic when there are
few UEs connected
PUCCH
decrease

85 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

actL1PM (LNBTS)

Configuration Management
New parameters introduced:
Abbrev Description MO

ThrPucchSizeUpper If the percentage of actual number of connected UEs from LNCEL

counter percentRRCConn is above ThrPucchSizeUpper, then
PUCCH size must be increased

ThrPucchSizeLower If the percentage of actual number of connected UEs from LNCEL

counter percentRRCConn is below ThrPucchSizeLower, then
PUCCH size must be decreased

86 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Flexible Uplink Bandwidth (LTE786)
Purpose of the feature is to define an area at the borders of uplink band where PUSCH nor
PUCCH are not allocated to any UE

• Achieved by increasing the bandwidth allocated to PUCCH, and

not using the resources situated at spectrum edge.
• LTE transmission bandwidth thus reduced, leaving blanked areas
at bandwidth edge. WCDMA 5MHz LTE 5 MHz
• Blanked areas serve as a guard band for reducing out of band
emissions Deployment possible with narrower spacing

0 1 2 3 4 5 6 7 8 9 1011 12131415161718192021222324252627282930313233343536373839404142434445464748

Blanked PUCCH PUSCH

area area resources

LTE786 modifies the receiver at the eNodeB. The blanked PUCCH PRBs are not received, therefore they do not influence
the received SINR. This means that the blanked resources do not contribute to the PUCCH RSSI nor SINR statistics, the
measurements of the PUSCH RSSI and SINR are performed on the reduced amount of PRBs

87 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Flexible Uplink Bandwidth
LNCEL: blankedPucch (Blanked PUCCH resources):
Range:0..60 (depends on ulChBw); step 2 default: 0 (feature off)
determines how many PRBs shall be excluded from PUCCH
allocations
• Allows for leaving border uplink PRBs unused
• Based on standardized possibility to freely determine the size of the PUCCH area allocated for
PUCCH Format 2.x
• These resources are used for CQI transmission.
- LTE786 in the first step allocates more PRBs for PUCCH, and then modifies the algorithm
allocating PUCCH CQI with an offset effectively preventing the border PRBs from being used.
• The number of blanked PRBs is determined by blankedPucch.

- The feature affects both sides of the spectrum

• Only symmetrical configurations possible
• Any modification of PUCCH size affects the remaining PUSCH area
- The operator has to assure sufficient PUCCH capacity with PUCCH blanking activated
• PUCCH planning has to consider only actually used PUCCH Format 2.x resources

It is not possible to use blanked areas for PUSCH scheduling

88 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Example configuration (uplink bandwidth 10 MHz,
50PRBs)
No PUCCH blanking ulChBw = 10 MHz
PUCCH Format 1.x
area Frequency
(PRBs)
0 1 2 3 4 5 6 7 8 9 1011 12131415161718192021222324252627282930313233343536373839404142434445464748
0 2 4 6 8 Total PUSCH area: 40 9 7 5 3
1 3 5 7 9 PRBs 8 6 4 2
Total
PUCCH
area:
nCqiRb 2x5PRB
=4 With PUCCH blanking

Area PUCCH Format 2.x allocations

nCqiRb = 20 Actual blanked
reserved starting from PUCCH allocation
area: 2x8PRB
with nCqiRb region 16 (PRB #8)
blankedPucch = 16

0 1 2 3 4 5 6 7 8 9 1011 1213 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37383940 4142434445 46 47 48 49

0 2 4 6 8 10 12 14 16 18 20 22 24 Total PUSCH area: 24 25 23 21 19 17 15 13 11 9 7 5 3 1

1 3 5 7 9 PRBs
11 13 15 17 19 21 23 25 24 22 20 18 16 14 12 10 8 6 4 2 0
Blanked Total
zone PUCCH
area:
2x5PRB

89 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 Exercise

• Assumptions:
• Mixed formats 1/1a/1b and 2/2a/2b not used
• Channel Bandwidth = 10 MHz
• Maximum Number of RRC connections is MaxNumRrc = 240
• The number of cyclic shifts is given by deltaPucchShift = 2 (6 cyclic shifts)
• CQI periodicity given by CqiPerNp = 20 ms
• SRI periodicity given by cellSrPeriod = 20 ms

• Task:
• Plan the number of required RBs for PUCCH

90 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Solution
• Step 1: identify the number of RBs required for formats 2/2a/2b (CQI)
- CQI periodicity is 20 ms -> there are 20 TTIs transporting CQIs
- The cyclic shift is 6 so there are 6 UEs multiplexed per TTI and per RB
- 6 UEs multiplexed per TTI and per RB then there are 6*20= 120 UEs (per 20 TTIs/ per RB)
- So to support 240 RRC connected UEs we need: 240/120 = 2 RBs
• Step 2: identify the number of RBs required for formats 1/1a/1b for SRI
• deltaPucchShift = 2 and because another 3 orthogonal codes are used -> 6*3= 18 UEs could be multiplexed per RB and per
TTI
• SRI periodicity is cellSrPeriod = 20 ms so in 20ms there are 20*18 = 360 UEs per 20 ms
• The number of RRC connected UEs is 240 < 360 so 1 RB is enough for SRI
• Note that n1PucchAn = 18
• Step 3: identify the number of RBs required for formats 1/1a/1b for dynamic ACK/NACK
• Channel Bandwidth is 10 MHz so the total number of CCEs is 43
• Number of required RBs = roundup((43*2)/(3*12)) = 3 RBs
• Total number of RBs is the sum of the above = 2RBs + 1 RB + 3 RBs = 6 RBs

91 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

Module Contents

• PRACH Planning
• PCI Planning
• UL DM RS Planning
• PDCCH Dimensioning
• PUCCH Dimensioning
• PUSCH Masking

92 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PUSCH masking (LTE944)
The PUSCH blanking feature allows to overcome the regulatory limitations of certain zones in the uplink
This allows the operators to deploy LTE in wider system bandwidth, rather than in two separate smaller
systems
• Obvious benefits in downlink capacity and especially peak throughputs (user experience,
marketing reasons)
• No need for inter-frequency measurements and handovers (measurement gaps!), load
balancing etc.

5 MHz + 10 MHz 20 MHz + PUSCH blanking

uplink downlink uplink downlink

Combined capacity: Capacity:

100Mbps (32+68) 142Mbps

93 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PUSCH masking

Each zone is determined by two parameters:

First PRB that will be muted

ulsPuschMaskStart
LNCEL : Range: [0..99] (*)
Default: no 11
(*) actual values depend on ulChBw PRBs

These uplink resources Length of the muted zone

will never be allocated

ulsPuschMaskLength
LNCEL: Range: [1..100] (*)
Default: no
(*) actual values depend on ulChBw

ulsPuschMaskStart =13
ulsPuschMaskLength = 11 11 PRBs muted: [#13 .. #23]

94 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016

 PUSCH masking
Interdependencies
• Affected features
• The features that use Sounding Reference Signals are affected by PUSCH masking
• These features will work in modified modes, which may result in reduced gains these features are
expected to bring about
• The Channel Aware Scheduler will derive the Channel State Information exclusively from
DMRS.
• For the Link Adaptation and Power Control, the configuration modes that use SRS will not be
available.

LTE944
PUSCH masking

LTE46 LTE1495 LTE28 LTE1336

Channel Aware Closed Loop UL Power Interference Aware UL
Fast Uplink Adaptation
Scheduler Control Power Control

95 RA4120BEN160GLA0 © Nokia Solutions and Networks 2016