11_RA4120BEN50GLA0_Initial_Parameter_Planning .pptx

© Nokia 2014 - RA4120BEN60GLA0
RA4120-60A
LTE RPESS
LTE FDD Initial Parameter Planning

5 © Nokia 2014 - RA4120BEN60GLA0
Index
 LTE/EPC Overview
 LTE Air Interface
 Air Interface Overheads
 RRM overview
 LTE Link Budget
 Radio Planning – Coverage Planning Cell Range
 Radio Planning – Capacity
 LTE Performance Simulations
 Nokia LTE Solution
 Initial Parameters Planning

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

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

Preamble generation
The random access preambles are generated from:
• 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
# root sequences = 838 in total
# preamble sequences = 64 per cell
Fig: Zadoff-Chu sequence. The real (upper) and
imaginary (lower) parts of the complex-valued
output (Wikipedia)
Fig:
example of
preambles
generation with
zero
autocorrelation
zone length equal
to 279
(prachCS=14)

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 Ncs (Cyclic Shift) and the cell radius:
Limits due to premable formats
Limits due to preamble formats
Limits due to preamble formats

10 © Nokia 2014 - RA4120BEN60GLA0
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 neighbour cells
PUSCH Rx power (SINR) can be very high compared to PRACH SINR in the neighbour cell and hence effectively swamp the PRACH preambles
and/or resulting in misdetections (ghost RACH).

11 © Nokia 2014 - RA4120BEN60GLA0
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 in RL30
Recommendation:
 Select Format0 for cell
ranges <14.53 km
 Select Format1 for cell
ranges <77.34 km
Note: An additional format to these four is specified for TDD , Preamble format 2 supported

12 © Nokia 2014 - RA4120BEN60GLA0
PRACH Configuration Index - prachConfIndex
- The parameter defines the Allowed System Frame for
random access attempts, the Sub-frame numbers for
random access attempts and the Preamble format
- 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
Extract of the random access preamble
configurations table (only for supported preamble
formats 0 and 1)
Recommendation:
Configure the same PRACH configuration Indexes at
cells belonging to the same site. E.g.:
 3 or 4 or 5 if RACH density=1 and 6 or 7or 8 if
RACH density=2 (Preamble Format 0)
1 Random access attempt = 1 RACH resource = 6 PRBs
prachConfIndex
LNCEL; 3..24;1; 3
Range is restricted to two different
ranges: 3-8 and 19-24 (internal)

13 © Nokia 2014 - RA4120BEN60GLA0
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:
freq
time
freq
time
...
...
6
0 UL
RB 

 N
nRA
PRBoffset
prachFreqOffset = roundup [maxPucchResourceSize /2]
If PRACH area is placed at the lower border of UL frequency band then:
prachFreqOffset = MAXNRB – 6 - roundup [maxPucchResourceSize /2]
If PRACH area is placed at the upper border of the UL frequency band then:
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
with PUCCH area
PUCCH
PRACH
prachFreqOff
First PRB available for PRACH in UL
LNCEL; 0...94;1; -
Max. value is ulChBw(in PRB) - 6

14 © Nokia 2014 - RA4120BEN60GLA0
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

15 © Nokia 2014 - RA4120BEN60GLA0
Preamble Generation
First: take all available cyclic shifts of one root
Zadoff-Chu sequence:
If not enough: take next logical index and so on
CS ZC CS CS
CS
RA RA RA RA RA
start shift shift CS shift group shift
0,1,..., 1, 0 for unrestricted sets
0 0 for unrestricted sets
( mod ) for restricted sets
0,1,..., 1
v
vN v N N N
N
C
d v n v n N v n n n
   
 
 



 
      
  

• Cyclic shift given by
Root Zadoff-Chu sequence order for preamble
formats 0 – 3.:
*3GPP TS 36.211 Table 5.7.2-2
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
Only unrestricted set could be selected in RL30

16 © Nokia 2014 - RA4120BEN60GLA0
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;1; 0

17 © Nokia 2014 - RA4120BEN60GLA0
PRACH Cyclic Shift - rootSeqIndex
- RootSeqIndex points to the first root sequence to be
used when generating the set of 64 preamble
sequences.
- Each logical rootSeqIndex is associated with a single
physical root sequence number.
- In case more than one root sequence is necessary the
consecutive number is selected until the full set is
generated
Logical root
sequence
number
Physical root sequence index (in increasing order of the corresponding logical
sequence number)
0–23 129, 710, 140, 699, 120, 719, 210, 629, 168, 671, 84, 755, 105, 734, 93, 746, 70, 769,
60, 779
2, 837, 1, 838
24–29 56, 783, 112, 727, 148, 691
30–35 80, 759, 42, 797, 40, 799
36–41 35, 804, 73, 766, 146, 693
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
…. …..
64–75 86, 753, 78, 761, 43, 796, 39, 800, 20, 819, 21, 818
810–815 309, 530, 265, 574, 233, 606
816–819 367, 472, 296, 543
820–837 336, 503, 305, 534, 373, 466, 280, 559, 279, 560, 419, 420, 240, 599, 258, 581, 229,
610
Extract from 3GPP TS 36.211 Table 5.7.2.-4 ( Preamble
Formats 0-3). Mapping between logical and physical root
sequences.
Recommendation:
Use different rootSeqIndex across neighbouring cells
means to ensure neighbour cells will use different
preamble sequences
rootSeqIndex
LNCEL;0…837;1; 0
Recommendation: Plan different logical root sequence
numbers to generate different physical root sequence
numbers.

18 © Nokia 2014 - RA4120BEN60GLA0
Support of high speed users
• If prachHsFlag = true the following rootSeqIndex values can be selected depending on prachCS
(restricted set)
Cell range Required amount of root
sequences
prachCS Possible range for rootSeqIndex
< 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

19 © Nokia 2014 - RA4120BEN60GLA0
Preamble generation – High Speed Case
high-speed
set
no delay spread delay spread = 5,2 µs
With
preamble
guard
NCs
Configuration NCS
sign. per 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

20 © Nokia 2014 - RA4120BEN60GLA0
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 neighbour cells
• rootSeqIndex separation between cells depends on how many are necessary per cell (depends
on PrachCS)

21 © Nokia 2014 - RA4120BEN60GLA0
Exercise
- Plan the PRACH Parameters for the sites below:
- Assumptions:
• PUCCH resources =6
• Cell range = 12km (all cells have same range)
• BW:10MHz
Sites Cell Azimuth PrachConfIndex PrachFreqOff PrachCs rootSeqIndex
A
1 0
2 120
3 240
B
1 0
2 120
3 240
C
1 0
2 120
3 240
D
1 0
2 120
3 240
E
1 0
2 120
3 240

22 © Nokia 2014 - RA4120BEN60GLA0
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

23 © Nokia 2014 - RA4120BEN60GLA0
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

24 © Nokia 2014 - RA4120BEN60GLA0
Solution (3/3)
- The final planning below:
- Assumptions:
• PUCCH resources =6
• Cell range = 12km (all cells have same range)
• BW:10MHz
Sites Cell Azimuth PrachConfIndex PrachFreqOff PrachCs rootSeqIndex
A
1 0 3 41 11 0
2 120 3 41 11 8
3 240 3 41 11 16
B
1 0 3 41 11 24
2 120 3 41 11 32
3 240 3 41 11 40
C
1 0 3 41 11 48
2 120 3 41 11 56
3 240 3 41 11 64
D
1 0 3 41 11 72
2 120 3 41 11 80
3 240 3 41 11 88
E
1 0 3 41 11 96
2 120 3 41 11 104
3 240 3 41 11 112

25 © Nokia 2014 - RA4120BEN60GLA0
• PRACH Planning
• PCI Planning
• PUSCH Masking

26 © Nokia 2014 - RA4120BEN60GLA0
PCI Planning - Introduction
• There are 504 unique Physical Cell IDs (PCI)
• Physical Layer Cell Identity = (3 × NID1) + NID2
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
phyCellId:
Physical Cell Id
LNCEL; 0..503; 1; -
(Range; Step; Default)
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

27 © Nokia 2014 - RA4120BEN60GLA0
PCI Planning
- Analogous to scrambling code planning in UMTS
• 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
neighbouring geographic areas

28 © Nokia 2014 - RA4120BEN60GLA0
Physical Cell identification and Global Cell ID identification
Physical Layer Cell ID (PCI)
Global Cell ID (ECGI)
- 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
• 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

29 © Nokia 2014 - RA4120BEN60GLA0
PCI Planning - Recommendations
• In priority order, number 1 most important (all four
should be fulfilled, ideally)
1. Avoid assigning the same PCI to neighbour cells
2. Avoid assigning the same mod3 (PCI) to
‘neighbour’ cells
3. Avoid assigning the same mod6(PCI) to ‘neighbour’
cells
4. Avoid assigning the same mod30 (PCI) to ‘neighbour’
cells
Id = 5
Id = 4
Id = 3
Id = 11
Id = 10
Id = 9
Id = 8
Id = 7
Id = 6
Id = 2
Id = 1
Id = 0
Example 1 PCI Identity Plan
Example 2 PCI Identity Plan

30 © Nokia 2014 - RA4120BEN60GLA0
• PRACH Planning
• PCI Planning
• PUSCH Masking

31 © Nokia 2014 - RA4120BEN60GLA0
UL Reference Signal - Overview
• Types of UL Reference Signals
- 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
UL DM RS allocation per slot for Normal
Cyclic Prefix

32 © Nokia 2014 - RA4120BEN60GLA0
UL DM Reference Signal - Need for Planning
• Issue:
- 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 neighbour 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
UL DM RS allocation per slot for Normal
Cyclic Prefix

33 © Nokia 2014 - RA4120BEN60GLA0
- 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’:
RS Sequences and RS Sequence Groups - Sequence Group Id, ‘u’
  30
mod
SCH
grpAssigPU

 PCI
u
grpAssigPUSCH
defines the assigned PUSCH
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

34 © Nokia 2014 - RA4120BEN60GLA0
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

35 © Nokia 2014 - RA4120BEN60GLA0
UL DM Reference Signal - Hopping Techniques
- Reason for Hoping: Simultaneous UL allocation on neighbouring 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.

36 © Nokia 2014 - RA4120BEN60GLA0
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

37 © Nokia 2014 - RA4120BEN60GLA0
Planning - From Theory to Practice… (2/2)
• Practice:
- It doesn’t seem to work
- UL Throughput gets considerably affected if UL traffic in neighbour cell
• From 40 Mbps to ~ 22 Mbps in the example
PCI grpAssigPusch sequence id u ulRsCs cinit
75 0 15 0 79
76 29 15 4 79

38 © Nokia 2014 - RA4120BEN60GLA0
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)

39 © Nokia 2014 - RA4120BEN60GLA0
Planning - Results
- UL Throughput still suffers from UL interference in neighbour cell but the effect is lower
PCI grpAssigPusch sequence id u ulRsCs cinit
75 0 15 0 79
76 0 16 0 80

40 © Nokia 2014 - RA4120BEN60GLA0
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
  30
mod
SCH
grpAssigPU

 PCI
u

41 © Nokia 2014 - RA4120BEN60GLA0
UL DM RS Planning - Wrap up
• 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 neighbouring cells and cannot be changed using grpAssigPUSCH
then assign different ulRsCs to the cells of a site. Range [0…7]
• 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
  30
mod
SCH
grpAssigPU

 PCI
u

43 © Nokia 2014 - RA4120BEN60GLA0
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

44 © Nokia 2014 - RA4120BEN60GLA0
• Uplink Reference Signals are:
• Demodulation Reference Signal for PUCCH
• Demodulation Reference Signal for PUSCH
• Sounding Reference Signal (SRS)
PUCCH Formats
1, 1a, 1b
PUCCH Formats 2, 2a,
2b
PUSCH SRS

45 © Nokia 2014 - RA4120BEN60GLA0
Group Allocation
• The allocated group for a cell is not planned explicitly but is calculated from:
  30
mod
)
( ss
s
gh f
n
f
u 

30
mod
cell
ID
PUCCH
ss N
f 
  30
mod
ss
PUCCH
ss
PUSCH
ss 

 f
f
Group
PUCCH & SRS
PUSCH
PCI
Configurable Offset
(grpAssigPUSCH)
Psuedo random sequence initialised using
ROUNDDOWN [PCI / 30]










 


 
enabled
is
hopping
group
if
30
mod
2
)
8
(
disabled
is
hopping
group
if
0
)
( 7
0 s
s
gh
i
i
i
n
c
n
f

46 © Nokia 2014 - RA4120BEN60GLA0
PCI Planning (I)
• Neighbouring cells should not be allocated PCI values with equal ‘PCI mod 30’
• This ensures that different base groups are allocated to neighbouring cells
• The Sequence Shift (SS) part of the group selection (repeated below from the previous slide) leads to
a ‘PCI mod 30’ planning rule
30
mod
cell
ID
PUCCH
ss N
f    30
mod
ss
PUCCH
ss
PUSCH
ss 

 f
f

47 © Nokia 2014 - RA4120BEN60GLA0
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










 


 
enabled
is
hopping
group
if
30
mod
2
)
8
(
disabled
is
hopping
group
if
0
)
( 7
0 s
s
gh
i
i
i
n
c
n
f
Psuedo random sequence initialised using
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
leads to 17 hopping patterns
(504 / 30 = 16.8)

48 © Nokia 2014 - RA4120BEN60GLA0
• PRACH Planning
• PCI Planning
• PUSCH Masking

49 © Nokia 2014 - RA4120BEN60GLA0
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 © Nokia 2014 - RA4120BEN60GLA0
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
• 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
Maximum number of
CCE for different BW
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 signalling, resources for TPC commands.

51 © Nokia 2014 - RA4120BEN60GLA0
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
• Desired aggregation level for users at cell edge:
- 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
maxNrSymPdcch
LNCEL; 1..3; 1; 3

53 © Nokia 2014 - RA4120BEN60GLA0
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 PUSCH transmission uses 1 RB on each side of the channel bandwidth
Note: RB in here corresponds to 3GPP definition of 12
subcarriers x 1 slot
Transmission from a single UE

54 © Nokia 2014 - RA4120BEN60GLA0
n1PucchAn
Offset to calculate ACK/NACK
resources from PDCCH CCE
LNCEL; 0..2047; 1; 36
PUCCH Structure
- The logical split between the PUCCH formats is the following:
- 1. Resources allocated for format 2/2a/2b i.e. CQI
• Number of resource blocks (RBs) defined by the parameter nCqiRb
• 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
pucchnanCS
Number of cyclic shifts for
PUCCH formats 1/1a/1b in the
mixed region
LNCEL; 0..7; 1; 0
(0 means no use of mixed
formats )
nCqiRb
reserved RBs per slot for
PUCCH formats 2/2a/2b
LNCEL; 1..98; 1; 2

55 © Nokia 2014 - RA4120BEN60GLA0
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
Number of Bits Multiplexing Capacity (UE/RB)
ON/OFF keying 36, *18, 12
1 36, *18, 12
2 36, *18, 12
20 12, *6, 4
21
22
12,* 6, 4
12, *6, 4
*typical value deltaPucchShift
delta cyclic shift for PUCCH formats 1/1a/1b
LNCEL; 1..3; 1; 2 (i.e. 6 cyclic shifts)
PUCCH formats Control type
PUCCH Format 1 Scheduling request
PUCCH Format 1a 1-bit ACK/NACK
PUCCH Format 1b 2-bit ACK/NACK
PUCCH Format 2 CQI
PUCCH Format 2a CQI + 1-bit ACK/NACK
PUCCH Format 2b CQI + 2-bit ACK/NACK

56 © Nokia 2014 - RA4120BEN60GLA0
Confi
g
Number of RRC
connected UEs
maxNumRrc
Number of
RBs
nCqiRb
CQI Periodicity
cqiPerNp
1. 840 (1680) 14 10 ms
2. 840 (1680) 7 20 ms
3. 768 (1536) 4 32 ms
4. 420 (840) 7 10 ms
5. 480 (960) 4 20 ms
6. 384 (768) 2 32 ms
7. 240 (480) 2 20 ms
8. 120 (240) 2 10 ms
9. 192 (384) 1 32 ms
10. 120 (240) 1 20 ms
11. 60 (120) 1 10 ms
Number of Resource Blocks for formats 2/2a/2b
• The number of RBs required for formats 2/2a/2b
• depends on the number of RRC connected UEs
• Defined by maxNumRrc parameter
• Example configuration 2:
• CQI periodicity is 20 ms -> there are 20 TTIs transporting CQIs
• Assuming 6 UEs multiplexed per TTI and per RB then there
are 6*20= 120 UEs (per 20 TTIs/ per RB)
• So to support 840 RRC connected UEs we need:
840/120 = 7 RBs
• Please note that only 6 cyclic shifts are used in order
• to avoid interference (even if 12 cyclic shifts possible)
• With 12 cyclic shifts 12 UEs are multiplexed per TTI
so the capacity is doubled (the number are in the
brackets in the table)
Number of RBs allocated for
formats 2/2a/2b example
maxNumRrc
Max. number of Use in the cell with established RRC
connection
LNCEL; 0..840; 1; 240 (*420 for 20 MHz bandwidth)
cqiPerNp
CQI periodicity
LNCEL; 2; 5; 10; 20; 20 ms

57 © Nokia 2014 - RA4120BEN60GLA0
Number of Resource Blocks for formats 1/1a/1b – SRI
- The number of RBs for SRI depends on:
- parameter n1PucchAn (Ack/Nack offset relative to the
Lowest CCE index of the associated DL scheduling PDCCH)
- Number of cyclic shifts deltaPucchShift
Example: Assuming that deltaPucchShift = 2 and the
periodicity of SRI is 20 ms (cellSrPeriod parameter) then
18 UEs could be multiplexed per TTI and per RB
So there are 20*18 = 360 UEs per 20 ms
Assuming that maximum number of RRC connections
maxNumRrc is 840 then we need roundup(840/360) = 3 RBs
for SRI
So the offset for Ack/Nack -> n1PucchAn = 54
deltaPucchShift n1PucchAn Number of RBs
for SRI
1 36 1
1 72 2
1 108 3
1 144 4
… … …
1 360 10
2 18 1
2 36 2
2 54 3
2 72 4
… … …
2 180 10
3 12 1
… … …
3 120 10
)
12
*
3
*
1
(
_
_
_
Shift
deltaPucch
PucchAn
n
roundup
SRI
RBs
PUCCH
Number 
cellSrPeriod
SRI repetition period
LNCEL; 5ms(0), 10ms(1), 20ms(2), 40ms(3), 80ms(4); 20ms(2)

58 © Nokia 2014 - RA4120BEN60GLA0
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 :
- The total number of CCEs depends on the system bandwidth:
- Example: Assume that bandwidth is 10Mhz and the deltaPucchShift is 2 then the number
of resource blocks for dynamic ACK/NACK is:
)
12
*
3
*
(
/
_
_
_
Shift
deltaPucch
E
TotalNumCC
roundup
NACK
ACK
RBs
PUCCH
Number 
Bandwidth Total Number of CCEs
5 MHz 21
10 MHz 43
15 MHz 65
20 MHz 87
3
)
12
*
3
2
*
43
(
/
_
_
_ 
 roundup
NACK
ACK
RBs
PUCCH
Number

59 © Nokia 2014 - RA4120BEN60GLA0
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:
- If mixed formats 1/1a/1b and 2/2a/2b are supported for small bandwidth then the total number of RBs for
PUCCH is:
 





 


12
*
3
*
1
_
_
Shift
deltaPucch
PucchAn
n
E
TotalNumCC
roundup
nCqiRb
RBs
PUCCH
Number

































8
12
*
3
*
3
*
1
_
_
pucchNAnCs
roundup
Shift
deltaPucch
Shift
deltaPucch
pucchNAnCs
PucchAn
n
E
TotalNumCC
roundup
nCqiRb
RBs
PUCCH
Number

60 © Nokia 2014 - RA4120BEN60GLA0
LTE1089 – 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
𝒓𝒆𝒒𝑷𝑼𝑪𝑪𝑯𝒓𝒆𝒔𝑺𝒊𝒛𝒆 = 𝑛𝑐𝑞𝑖𝑅𝑏 +
𝑟𝑟𝑚𝑇𝑜𝑡𝑎𝑙𝑁𝑢𝑚𝐶𝐶𝐸 + 𝑛1𝑃𝑢𝑐𝑐ℎ𝐴𝑛
3 ∗ 12
𝑑𝑒𝑙𝑡𝑎𝑃𝑢𝑐𝑐ℎ𝑆ℎ𝑖𝑓𝑡
𝒓𝒓𝒎𝑻𝒐𝒕𝒂𝒍𝑵𝒖𝒎𝑪𝑪𝑬 =
𝑚𝑎𝑥𝑁𝑟𝑆𝑦𝑚𝑃𝑑𝑐𝑐ℎ ∗ 12 − 4 ∗ 𝑑𝑙𝐶ℎ𝐵𝑤 − #𝑃𝐻𝐼𝐶𝐻𝑔𝑟𝑜𝑢𝑝𝑠 ∗ 12 − 16
36
This is the number of PRBs that are reserved for
PUCCH formats 2/2a/2b, capacity for PUCCH Format
2.x depends on the CqiPerNp
These are resources that are reserved for Scheduling
Requests (Format 1.x), capacity for SRs depends on
the cellSrPeriod
These are resources that are reserved for ACK/NACK
(Format 1.x)
Format 2.x Format 1.x
Assumption:
no 4x2 MIMO and no PUCCH
blanking
• 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
Non-CA case – recap

61 © Nokia 2014 - RA4120BEN60GLA0
• 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
for PUSCH will be decreased. Consequently, UL cell capacity will
be compromised.
• The cell playing a role of secondary one is not affected unless it
plays also a role of the primary cell (symmetrical relation between
PCell and SCell was created).
Note:
maxNumCaConfUeDc
parameter does not affect
the amount of PUCCH
resources configured to
convey multi-cell
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
LTE1089 – Carrier Aggregation

62 © Nokia 2014 - RA4120BEN60GLA0
LTE786 –Flexible Uplink Bandwidth
• 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.
• Blanked areas serve as a guard band for reducing out of band
emissions
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
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Blanked
area
PUSCH
resources
PUCCH
area
Deployment possible with narrower spacing
WCDMA 5MHz LTE 5 MHz
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

63 © Nokia 2014 - RA4120BEN60GLA0
LTE786 –Flexible Uplink Bandwidth
• 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
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

64 © Nokia 2014 - RA4120BEN60GLA0
Example configuration (uplink bandwidth 10 MHz, 50PRBs)
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
0 2 4 6 8
10 12 14 16 18 20 22 24 25 23 21 19 17 15 13 11
9 7 5 3 1
1 3 5 7 9 11 13 15 17 19 21 23 25 24 22 20 18 16 14 12 10
8 6 4 2 0
ulChBw = 10 MHz
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
0 2 4 6 8 9 7 5 3 1
1 3 5 7 9 8 6 4 2 0
nCqiRb = 20
blankedPucch = 16
Total PUSCH area: 40
PRBs
nCqiRb
= 4
Total
PUCCH
area:
2x5PRB
PUCCH Format 1.x
area
No PUCCH blanking
PUCCH Format 2.x allocations
starting from PUCCH allocation
region 16 (PRB #8)
With PUCCH blanking
Actual blanked
area: 2x8PRB
Blanked
zone
Area
reserved
with nCqiRb
Frequency
(PRBs)
Total PUSCH area: 24
PRBs
Total
PUCCH
area:
2x5PRB

65 © Nokia 2014 - RA4120BEN60GLA0
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

66 © Nokia 2014 - RA4120BEN60GLA0
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

68 © Nokia 2014 - RA4120BEN60GLA0
PUSCH masking
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.
uplink downlink uplink downlink
5 MHz + 10 MHz 20 MHz + PUSCH blanking
Combined capacity:
100Mbps (32+68)
Capacity:
142Mbps

69 © Nokia 2014 - RA4120BEN60GLA0
PUSCH masking
Each zone is determined by two parameters:
Length of the muted zone
First PRB that will be muted
ulsPuschMaskLength
LNCEL: Range: [1..100] (*)
Default: no
(*) actual values depend on ulChBw
These uplink resources
will never be allocated
11
PRBs
ulsPuschMaskStart
LNCEL : Range: [0..99] (*)
Default: no
(*) actual values depend on ulChBw
ulsPuschMaskStart =13
ulsPuschMaskLength = 11
11 PRBs muted: [#13 .. #23]

70 © Nokia 2014 - RA4120BEN60GLA0
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
Channel Aware
Scheduler
LTE1495
Fast Uplink Adaptation
LTE28
Closed Loop UL Power
Control
LTE1336
Interference Aware UL
Power Control

11_RA4120BEN50GLA0_Initial_Parameter_Planning .pptx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to 11_RA4120BEN50GLA0_Initial_Parameter_Planning .pptx

Similar to 11_RA4120BEN50GLA0_Initial_Parameter_Planning .pptx (20)

Recently uploaded

Recently uploaded (20)

11_RA4120BEN50GLA0_Initial_Parameter_Planning .pptx

Editor's Notes