Model Site

LTE FDD Initial Parameter Planning

 Module Objectives – Model Site
After completing this module, the participant will be able to:

• Describe the concept of channel configuration parameters

• Describe the PUCCH capacity & parameters
• Describe the PRACH configuration parameters
• Describe the PCI configuration parameters
• Describe the PDCCH capacity & parameters

2
 Physical Channels in LTE

DOWNLINK UPLINK

Physical Channels
 physical layer uses resource blocks (e.g. 12 subcarriers with 6 or 7 OFDM symbols) to transmit binary coded
information in QPKS, 16QAM or 64QAM modulation form. Physical channels determine how data is processed
and then mapped via dynamical scheduling onto resource blocks. Thus physical channels also in EUTRAN
represent the available physical resources. Like transport channels, also physical channels are unidirectional.
There is usually a fixed linkage between transport channel types and physical channel type used to transmit the
transport blocks. Next to the physical channels that are used to carry transport channels, there are also physical
channels that carry physical layer control data and physical signals that are mainly used for synchronization and
measurement purposes.
3
 Physical Channels in LTE (1/3)
• On the downlink side we have the following:

• PBCH (Physical Broadcast Channel): The PBCH is the physical channel used to carry BCH (BCCH), in other words on this
channel the system information can be found. It will use a fixed mapping onto resource blocks. There will be one PBCH per
cell.

• PDSCH (Physical Downlink Shared Channel): The PDSCH can carry DL-SCH or PCH. Thus this channel type will allocate
most of the capacity in a cell. It is still under investigation how many PDSCHs a cell can have and how many PCH and DL-
SCH a single PDSCH can carry.

• PMCH (Physical Multicast Channel): This channel type is used to carry MCH. It implements the option of MBSFN where a
UE receives the PMCH from several cells operating in the same area on the same frequency band. All the PMCH will be
jointly decoded by the UE. This would allow a UE to do cell re-selection without interrupting MBMS services.

• PDCCH (Physical Downlink Control Channel): This is a pure physical layer control channel. It contains the scheduler
signaling to inform the UEs about the coming downlink (and maybe also uplink) resource block assignments to PDSCH. The
PDCCH will be sent in each subframe shortly before PDSCH starts.
4
 Physical Channels in LTE (2/3)
• PCFICH (Physical Control Format Indicator Channel): The PCFICH is like the PDCCH a pure physical layer control
channel. It indicates how many OFDM symbols are used to encode the PDCCH. So the order of decoding for a UE is to read
first the PCFICH to get the PDCCH format. Then the PDCCH is decoded to find out which resource blocks to the PDSCH of
interest for the UE.

5
 Physical Channels in LTE (3/3)
• In the uplink there some less physical channels defined:

• PUSCH (Physical Uplink Shared Channel): The PUSCH is the major uplink channel, because on it we will find the
transport blocks of UL-SCH on which all radio bearers uplink occur. Like PDSCH also the PUSCH is dynamically assigned to
uplink resource blocks. This happens via so called UL Assignments which are not completely specified yet. The PUSCH
supports DTX, HARQ and at least QPSK and 16QAM. 64QAM is under investigation for this channel.
• PUCCH (Physical Uplink Control Channel): This is a pure physical layer control channel. One idea is to use this channel for
UL capacity requests and HARQ ACK/NACK indications by the UE as well as CQI (Carrier Quality Indication) feedback
information to optimize CDS and MIMO.
• PRACH (Physical Random Access Channel): The PRACH carries the RACH. Currently this means, that the PRACH simply
transmits preamble sequences that act as initial access request for UL and DL resources when the UE is RRC_IDLE.

6
Model Site CO704L100

7
 Initial Parameter Planning

• PUCCH Dimensioning
• PRACH Planning
• PCI Planning
• PDCCH Dimensioning

8
 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

Transmission from a single UE subcarriers x 1 slot

9
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:

10
Size of PUCCH Region
PUCCH
Total UL Bandwith

PUSC
H
12 subcarriers

PUCCH

1 subframe = 1ms

 The size of the overall PUCCH region is dependent on:

1. For CQI (periodic) the resources are reserved in advance and depend on the number of UL scheduled Ues
2. For ACK/ NACK the number of resources is directly related with the size of the Downlink PDCCH region (1,2,3
symbols) which in turn is dependent on the number of the DL scheduled users
3. For SRI Scheduling Request Indicator the ressources are allocated on the need basis
 The overal number of the Resource Blocks used in UL is configured by higher layer parameters
 The UE knows the parameters from the system information
11
 pucchnanCS
PUCCH Structure nCqiRb
reserved RBs per slot for PUCCH Number of cyclic shifts for
- The logical split between the PUCCH formats is the following: formats 2/2a/2b PUCCH formats 1/1a/1b in the
- 1. Resources allocated for format 2/2a/2b i.e. CQI LNCEL; 1..98; 1; 2 mixed region
LNCEL; 0..7; 1; 0
• Number of resource blocks (RBs) defined by the parameter nCqiRb (0 means no use of mixed formats
)

- maxNumRrc + max(addAUeRrHo,addAUeTcHo) <= (nCqiRb - blankedPucch) * 6 * cqiPerNp/2

- 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
n1PucchAn
• Used for small bandwidth (e.g. 1.4 MHz) Offset to calculate ACK/NACK
• pucchNanCS parameter used to calculated the number resources from PDCCH CCE
of RBs for mixed formats LNCEL; 0..2047; 1; 36
12
 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 UE/RB
• 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

*typical value deltaPucchShift

delta cyclic shift for PUCCH formats 1/1a/1b
13 LNCEL; 1..3; 1; 2 (i.e. 6 cyclic shifts)
 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
maxNumRrc +
• Assuming 6 UEs multiplexed per TTI and per RB then there
are 6*20/2= 120 UEs (per 20 TTIs/ per RB)
max(addAUeRrHo,addAUeTcHo)
• So to support 840 RRC connected UEs we need: <= (nCqiRb - blankedPucch) * 6
480/60 = 8 RBs * cqiPerNp/2
• 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)

maxNumRrc
Max. number of Use in the cell with established RRC cqiPerNp
connection CQI periodicity
LNCEL; 0..840; 1; 240 (*420 for 20 MHz bandwidth) LNCEL; 2; 5; 10; 20; 20 ms Number of RBs allocated for
formats 2/2a/2b example
14
Number of Resource Blocks for formats 1/1a/1b – SRI
- The number of RBs for SRI depends on: deltaPucchShift n1PucchAn Number of RBs
for SRI
- parameter n1PucchAn (Ack/Nack offset relative to the
1 36 1
Lowest CCE index of the associated DL scheduling PDCCH) 1 72 2
- Number of cyclic shifts deltaPucchShift 1 108 3

1 144 4

Example: Assuming that deltaPucchShift = 2 and the … … …

periodicity of SRI is 20 ms (cellSrPeriod parameter) then 1 360 10

18 UEs could be multiplexed per TTI and per RB 2 18 1

So there are 20*18 = 360 UEs per 20 ms 2 36 2

2 54 3
Assuming that maximum number of RRC connections
2 72 4
maxNumRrc is 480 then we need roundup(480/360) = 2 RBs
… … …
for SRI
2 180 10
So the offset for Ack/Nack -> n1PucchAn = 36
3 12 1
cellSrPeriod … … …
SRI repetition period
LNCEL; 5ms(0), 10ms(1), 20ms(2), 40ms(3), 80ms(4); 20ms(2) 3 120 10

15
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: Bandwidth Total Number of CCEs

5 MHz 21

10 MHz 43

15 MHz 65

20 MHz 87

16
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:

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

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

18
 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 480 RRC connected UEs we need: 2(MiMo)*480/120 = 4 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 480 / 360 so 2 RB is enough for SRI
• Note that n1PucchAn = 36
• 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 = 4RBs + 2 RB + 3 RBs = 9 RBs

19
 Initial Parameter Planning

• PUCCH Dimensioning
• PRACH Planning
• PCI Planning
• PDCCH Dimensioning

20
 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).
21
 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 Nokia

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 in NOKIA
22
PRACH Configuration Index - prachConfIndex Extract of the random access preamble configurations
table (only for supported preamble formats 0 and 1)
- 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
Recommendation:

prachConfIndex Configure the same PRACH configuration Indexes at

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

23
 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
LNCEL; 0...94;1; -
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

freq
border of frequency band to maximize the PUSCH area but not overlap with PUCCH

freq
area
time time
24
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

25
 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
Only unrestricted set could be selected in RL30

• Cyclic shift given by

26

*3GPP TS 36.211 Table 5.7.2-2

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

27
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 sequences.
- RootSeqIndex points to the first root sequence to be used
when generating the set of 64 preamble sequences.
Logical root Physical root sequence index (in increasing order of the corresponding logical
- Each logical rootSeqIndex is associated with a single physical sequence sequence number)
number
root sequence number.
- In case more than one root sequence is necessary the
0–23 129, 710, 140, 699, 120, 719, 210, 629, 168, 671, 84, 755, 105, 734, 93, 746, 70, 769,
consecutive number is selected until the full set is generated 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 neighbouring cells means 36–41 35, 804, 73, 766, 146, 693
to ensure neighbour cells will use different preamble
42–51 31, 808, 28, 811, 30, 809, 27, 812, 29, 810
sequences
52–63 24, 815, 48, 791, 68, 771, 74, 765, 178, 661, 136, 703

…. …..
rootSeqIndex
LNCEL;0…837;1; 0 64–75 86, 753, 78, 761, 43, 796, 39, 800, 20, 819, 21, 818

810–815 309, 530, 265, 574, 233, 606

Recommendation: Plan different logical root sequence numbers 816–819 367, 472, 296, 543
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

28
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 prachCS Possible range for rootSeqIndex
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

29
 Preamble generation – High Speed Case

high-speed
set With
preamble
      no delay spread delay spread = 5,2 µs guard          
NCs sign. per root
Configuration NCS 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

30
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)

31
Exercise

- Plan the PRACH Parameters for the sites below:

- Assumptions:
• PUCCH resources =9
• Cell range = 12km (all cells have same range)
• BW:10MHz Sites Cell Azimuth PrachConfIndex PrachFreqOff PrachCs rootSeqIndex
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        

32
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 = 9)
prachFreqOff = 50 – 6 – roundup[9/2] = 39
33
 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

34
Solution (3/3)

- The final planning below:

- Assumptions:
• PUCCH resources =9
• Cell range = 12km (all cells have same range)
• BW:10MHz Sites Cell Azimuth PrachConfIndex PrachFreqOff 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

35
 Initial Parameter Planning

• PUCCH Dimensioning
• PRACH Planning
• PCI Planning
• PDCCH Dimensioning

36
 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

37
Synchronization Signals allocation (DL) – FDD Case

Primary Synchronization Channel (PSS)

Secondary Synchronization Channel (SSS)

Frequency
 Transmitted during the 1st and 11th slots

6 RBs – 72 subcarriers = 1.4 MHz

within a radio frame

(minimum LTE Bandwidth)

 Occupy the central 62 Subcarriers (around
the DC subcarrier) to facilitate the cell
search
 5 Subcarriers above and 5 Subcarriers
below the synch. Signals are reserved and
transmitted as DTx
 Synchronisation Signal can indicate 504
(168 x 3) CellID different values and from 5 ms repetition Time
those one can determine the location of period
cell specific reference symbols
10 ms Radio frame
SSS
PSS
One subframe (1 ms)
Reference signals
38
Unused RE
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

39
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
40
 PCI Planning - Recommendations
• In priority order, number 1 most important (all four should
Id = 0 Id = 6
be fulfilled, ideally)
Id = 2 Id = 8

Id = 1 Id = 7
1. Avoid assigning the same PCI to neighbour cells Id = 3 Id = 9
Id = 5 Id = 11

2. Avoid assigning the same mod3 (PCI) to ‘neighbour’ Id = 4 Id = 10

cells
Example 1 PCI Identity Plan

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

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

41 Example 2 PCI Identity Plan

 Initial Parameter Planning

• PUCCH Dimensioning
• PRACH Planning
• PCI Planning
• PDCCH Dimensioning

42
 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

43
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
LNCEL; 1..3; 1; 3
• 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

44