Capacity Management

Capacity Management for Air Interface
Soc Classification level

1 Nokia Siemens Networks Presentation / Author / Date
Content
Network + field KPIs summary
KPI targets and reference values
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Relevant features and parameters summary
Project example

The most important usage KPIs traffic tput
PDCP mean DL
LTE_5292c Average PDCP Layer Active Cell Throughput DL, kbps
PDCP mean UL
LTE_5289c Average PDCP Layer Active Cell Throughput UL, kbps
PDCP peak DL
LTE_291a Maximum PDCP Throughput DL, Mbps
PDCP peak UL
LTE_288a Maximum PDCP Throughput UL, Mbps
See notes section of this slide, these are tput figures.

The most important usage KPIs number of users
Definitions
Active user = user with at least one DRB established
RRC-connected user = user in RRC-connected mode
Mean number of active users per cell
LTE_717a Average number of active users per cell
Peak number of active users per cell
LTE_718a Maximum number of active users per cell
Mean number of RRC-connected users
LTE_805a Average of RRC connected users
Peak number of RRC-connected users
LTE_806a Maximum of RRC connected users
Radio Admission Control
LTE_5231b E-UTRAN RRC Connection Setup Failure Ratio per Cause
RRMRAC
LTE_5104a E-UTRAN HO Preparation Failure Ratio per Cause, intra eNB AC
LTE_5107a E-UTRAN HO Preparation Failure Ratio per Cause, inter eNB X2
based AC
The most important usage KPIs data channel
usage per cell
PRB usage, PDSCH cell-level
LTE_5276b E-UTRAN average PRB usage per TTI DL
PRB usage, PUSCH cell-level

LTE_5273b Average PRB usage per TTI UL

The most important usage KPIs CCH usage
Usage, PDCCH
PDCCH utilization or total blocking KPI not available directly in RL30
M8011C61 PDCCH_3_OFDM_SYMBOLS
M8011C60 PDCCH_2_OFDM_SYMBOLS
M8011C59 PDCCH_1_OFDM_SYMBOL
LTE_776a AGG1 blocked distribution rate
Usage PUCCH
LTE_781a PRB PUCCH distribution Rate (does not identify blocking)

The most important usage KPIs RACH usage
Usage, RACH
LTE_138a RACH Setup Complete Success ratio
Identifies ratio of downlink RARs to received contention-based preambles
Dedicated preambles in RL40: M8001C286 RACH_STP_ATT_DEDICATED
M8001C6 RACH_STP_ATT_SMALL_MSG
M8001C7 RACH_STP_ATT_LARGE_MSG

The most important usage KPIs PCH usage
Usage, PCH
No utilization KPI available
LTE_5031b E-UTRAN RRC Paging Discard Ratio
LTE_5032a # RRC paging messages (pag records received from S1)

Drive test KPIs
No drive test KPIs for air interface utilization

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

KPI Targets
Traffic/user volume
n/a
PDSCH/PUSCH channel usage
n/a
PDCCH/PUCCH channel usage
No PUCCH blocking should be allowed
Some PDCCH blocking is acceptable (increases delay, FFS)
RACH usage
Average of 3 preambles per PRACH slot should not be exceeded
(higher values are ok in bursts)
PCH usage
FFS, with FSMr2 paging capacity is ~400 S1 paging messages per
second. TA splitting or reduction of paging load should take place well
in advance before this limit is reached
KPI Reference values, March 2012
traffic volumes:
Busiest sites have average 20Mbps DL bit rate during BH
PDCCH blocking
In RL20 network, some PDCCH blocking seen. Possibly due to pro-
active scheduling, PDCCH CQI shift -5 and <3 OFDM symbols
statically allocated ??
In the busiest RL30 network no PDCCH blocking, 5% of subframes use
3 OFDM symbols for PDCCH
PUCCH blocking
Some seen due to Golden SCF default values, which are not suitable
for production networks
No RACH congestion
No PCH congestion

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

PDCCH blocking
PDCCH can be allocated in blocks of 1, 2, 4, 8 CCEs
Full PDCCH capacity cannot be typically used
Example: 10MHz has max 43 CCEs/TTI, however in one TTI it is not
possible to allocate the combination 5*8CCE + 1*2CCE + 1*1CCE =
43CCEs (due to 3GPP PDCCH limitations)
PDCCH blocking can occur which may result in handover
delays, data tput reduction etc
RL30 supports load-based PDCCH allocation
(recommended!)
PDCCH blocking KPIs need to be monitored

PDCCH blocking example from Operator X, RL20
One site examined as an example
AGG4 most used, AGG8 second most
High AGG8 PDCCH block ratio up to 14% lot of users in bad RF

PDCCH blocking impact of PUSCH pro-active
scheduling, RL30 field test
PUSCH proactive scheduling increases PDCCH usage
Pro-active scheduling has low priority, hence it wont block real traffic
Drawback: three OFDM symbols are scheduled more often less
room for PDSCH.
Drawback: cannot tell real blocking from dummy grant blocking
Benefit: reduced latency
PDCC PDCCH PDCCH
UL RB
H 3
DL RB Avg.
Item Usage Blocki OFDM
Usage Usag CFI
ng Symbo
e
[RB] Rate l Rate
ilReacTimerUl=15 5907355
3.50% 33.20% 3.90% 45% 2.1
00ms 4
ilReacTimerUl=0m
3.00% 3.40% 7533658 0.10% 8% 1.3
s
5153989
Delta 0.60% 29.80%
6
3.80% 36.10% 0.7
DL tput
90% 87%
Improvement, 97% 37% 5.2%
Reductio Reductio
16 percents
Nokia Siemens Networks Presentation / Author / Date
n n
Reduction Reduction improveme
PDCCH blocking how to reduce it?
Some PDCCH blocking is acceptable as it kind of means
that PDCCH is efficiently utilized
NOTE: pro-active scheduling results in virtual blocking
How much is acceptable?
If UE scheduling is blocked, then it will be scheduled in a later TTI, so
basically blocking just increases delay
If AGG8 blocking is high, it means that cell has RF problems
Fixing it:
Check that load adaptive PDCCH size is used
<p name="actLdPdcch">true</p>
Off-loading users to neighbouring cells by shrinking cell size by physical
RF tuning, or by using handover and idle mode cell reselection offsets
Load balancing between layers
Increase the network capacity, add sectors, indoor BTSs, etc
PDCCH CQI shift value of -5 is current Golden SCF default, could be
changed? Reduce pro-active scheduling timers?
Somehow reduce PDCCH load: ghost RARs, paging, high reTx rate,
PDCCH orders
Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

PUCCH blocking
If there is not enough resources to allocate CQI/SR PUCCH
resources to a new user, admission control will reject the
user
LTE_5218c Total E-UTRAN RRC Connection Setup Success Ratio
LTE_5231b E-UTRAN RRC Connection Setup Failure Ratio per Cause
RRMRAC
LTE_5104a E-UTRAN HO Preparation Failure Ratio per Cause, intra
eNB AC
LTE_5107a E-UTRAN HO Preparation Failure Ratio per Cause, inter
eNB X2 based AC
The solution is to increase PUCCH region size
However, PUCCH region should be aligned with the number
of allowed RRC connected users
otherwise PUSCH PRBs are reduced needlessly

PUCCH Configuration
The PUCCH carries uplink control signalling during the subframes where
UL data has not been allocated for UE on PUSCH:
Channel Quality Indicator (CQI)
Ranking Indicator (RI) and Precoding Matrix Indicator (PMI) for MIMO
HARQ acknowledgements (ACK/NACKs)
Scheduling requests (SR)
Format 1/1a/1b Format 1/1a/1b

Format 2/2a/2b Format 2/2a/2b

20 Nokia Siemens Networks
PUCCH Configuration Physical Resources
1 subframe with PRACH occasion
1 PRB for SR, 1 PRB for CQI (RI & PMI),

n1PucchAN = 18 nCqiRb = 1
1-3 PRBs for ACK/NACKs,

# of PRBs are depending on
CCEs required for dynamic
PDCCH scheduling,
actLdPdcch = 1
For 10MHz system:

6 PRBs for PRACH 10 CCEs -> 1 PRB
26 CCEs -> 2 PRB
prachFreqOff = 3
42 CCEs -> 3 PRB (shown)

PUCCH ACK/NACK region
PUCCH capacity will limit the number of RRC-connected
users in a cell. If exceeded, radio admission control will
reject incoming handover and call setup attempts.
With maxNrSymPdcch =3, 3PRBs for PUCCH ACK/NACK
required at 10MHz, and 5PRBs at 20MHz
One PRB can handle 18 users (deltaPucchShift=2)
PRBs required for PUCCH ACK/NACK:

10MHz: ROUNDUP(42/18) = 3 PRBs
20MHz: ROUNDUP(87/18) = 5 PRBs

PUCCH Scheduling Request region
Use SR period = 10ms faster UL latency
18 users per PRB can be multiplexed (deltaPucchShift=2)
Total UEs at 10MHz: 18 x 10 = 180 UEs SR capacity
Total UEs at 20MHz: 36 x 10 = 360 UEs SR capacity
Proposal 10MHz: n1PucchAn = 18
Proposal 20MHz: n1PucchAn = 36

PUCCH CQI/RI reporting region
Use CQI reporting period = 20ms (default)
Number of PRBs for CQI reporting = 2
Total UEs 10MHz = 2* 6 * 20 =240 users CQI reporting
capacity
Total UEs 20MHz = 3* 6 * 20 =360 users CQI reporting
capacity
Proposal 10/20MHz: cqiPerNp = 20ms
Proposal 10MHz: nCqiRb = 2
Proposal 20MHz: nCqiRb = 3

PUCCH summary 10MHz
With the proposed settings,
there are no unused UL
PRBs
10MHz: prachFreqOff = 3
Max number of RRC-
connected users = 180,
limited by scheduling
request capacity
Details:
CQI region = 2
SR region = 1 A/N + SR region
A/N region = 3 CQI region

PUCCH Configuration Format 2.x Capacity
Every UE with a SRB1 in the cell is required to send CQI reports

periodically and thus, every active UE requires Format 2.x PUCCH
resource assignment.
The total capacity provided for Format 2.x in a cell is defined by the
number of dedicated PRBs (nCqiRb), cyclic shifts (6 cyclic shifts are set
by the system in order to reduce interference) and periodicity of CQI
reports (cqiPerNp):
nCqiRb * 6 * cqiPerNp = 1 * 6 * 20 ms = 120 users
Number of bits per
PUCCH format Purpose subframe,
1 Scheduling request (SR) N/A
1a 1-bit HARQ ACK/NACK with/without SR 1
1b 2-bit HARQ ACK/NACK with/without SR 2
2 CQI (20 coded bits) 20
CQI and 1-bit HARQ ACK/NACK (20 + 1
2a 21
coded bits)
2b 22
coded bits)

Every user in RRC connected mode requires Format 1.x resource

assignment for scheduling resource requests (SR). The total scheduling
capacity is defined by scheduling periodicity (cellSrPeriod) and number
of resources reserved for SRs (n1pucchAn):
cellSrPeriod * n1pucchAn = 10 ms * 18 = 180 users
The number of resources for PUCCH format 1.x per PRB is based on
spreading factor (c) and allowed cyclic shifts (12/deltaPucchShift):
c * 12 / deltaPucchShift = 3 * 12 / 2 = 18 users per PRB
1 PRB is reserved for scheduling requests as per n1pucchAn = 18.
Number of bits per
PUCCH format Purpose subframe,
1 Scheduling request (SR) N/A
1a 1-bit HARQ ACK/NACK with/without SR 1
1b 2-bit HARQ ACK/NACK with/without SR 2
2 CQI (20 coded bits) 20
2a 21
coded bits)
2b 22
coded bits)

The number of Format 1.x resources are also required for DL data
acknowledgements which are related to the actual amount of symbols
used for PDCCH, and as this amount can vary on TTI basis the amount
of PRBs reserved for Format 1.x resources can also vary on TTI basis.
Thus, 1-3 PRBs can be dynamically allocated for ACK/NACKs
depending on the used PDCCH symbols in terms of CCEs which is
based on the amount of UEs scheduled per TTI and required
aggregation levels:
# CCEs / format 1.x resources per PRB =
10 CCE (1 PDCCH symbol) => Roundup (10/18) = 1 PRB
26 CCE (2 PDCCH symbols) => Roundup (26/18) = 2 PRB
42 CCE (3 PDCCH symbols) => Roundup (42/18) = 3 PRB

PUCCH Configuration PUSCH Bandwidth
The PUCCH resource allocation defines the available PRBs for PUSCH
transmission and thus, the peak UL throughput for a single UE.
46 PRBs for PUSCH 46 PRBs for PUSCH 44 PRBs for PUSCH
45 PRBs for single UE (2-3-5 rule) 45 PRBs for single UE (2-3-5 rule) 40 PRBs for single UE (2-3-5 rule)
10 CCE = 1 PDCCH symbol 26 CCE = 2 PDCCH symbol 42 CCE = 3 PDCCH symbol

PUCCH Configuration Parameters
The following parameter are deployed for PUCCH configuration (10 MHz).
Recommendation
Parameters Range Description
10MHz
nCqiRb 1...98 Number of PRBs dedicated to Formats 2.x 1
2ms (0), 5ms
Periodicity of periodic CQI / PMI feedback
cqiperNp (1), 10ms (2), 20 ms
on PUCCH or PUSCH
20ms (3)
Offset to decide the number of resources
n1pucchAn 10...2047 reserved for SRI (and A/N from persistent 18
PDSCH scheduling in later releases).
deltapucchsh Maximum number of cyclic shifts allowed
13 2
ift for Formats 1/1a/1b
5ms (0),
Scheduling Request periodicity in the cell.
10ms (1),
The recommendation is to have one
cellSrPeriod 20ms (2), 10 ms
scheduling request (SR) configured per
40ms (3),
frame.
80ms (4)
First physical resource block available for
PRACH in the UL system frequency band.
prachFreqOff 0...94, step 1 3
Roundup [PUCCH resources/2]. Must not
overlap with PUSCH.
The PUSCH hopping offset parameter
puschHopOff defines the offset used for PUSCH
098 4
set frequency hopping, expressed in a number
of resource blocks
Activate or deactivate the load adaptive
number of PDCCH symbols in a cell. The
false (0), true actual OFDM symbol amount used for
Periodic Rank Indicator (RI) parameters
The periodic Rank Indicator (RI) reporting on PUCCH needs to be aligned
with a CQI reporting instance in order to allocate only 1 Format 2.x resource
for a single UE per cqiPerNp.
Rank Indication periodicity = cqiPerNp * riPerM = 20 ms * 2 = 40ms
Recommendati
on 10MHz
false (0), Determines whether RI reporting is enabled (true) or not
riEnable true
true (1) (false).
Multiplier M for defining periodic RI feedback reporting
period.
The parameter defines the offset for the periodic Rank
Indicator reporting instance in relation to the CQI reporting
subframe. If, for example, subframe 5 is chosen for CQI
1 (0), 2 reporting and riPerOffset is -1, then subframe 4 is chosen
riPerM 2
(1) for the RI report.
In case riPerM is set to value 1 than riPerOffset must be set
to -1. In case riPerM is set to value 2 than riPerOffset
must be set to 0. In case riEnable is set to 'true' and
additionally riPerM is set to 1, cqiPerNp cannot be set to 1
(5ms)
Time offset for periodic CQI/PMI reporting for defining the
periodic RI reporting instance. The parameter defines the
offset for periodic Rank Indicator reporting instance. The
riPerOffset -1...0 0
offset tells the time shift for the periodic CQI/PMI reporting
instance. The range of the offset depends on the
periodicity (cqiPerNp) of periodic CQI/PMI reporting
Radio Admission Control parameters
RAC thresholds for the maximum number of RRC connected users and the
active (DRB) users in a cell should be aligned according to the configured
PUCCH capacity.
Recommendati
on 10MHz
The number of RRC-connections established in the cell
cannot exceed maxNumRrc. RAC shall always be
invoked for the admission of SRB1 at RRC Connection
Setup. An RRC connection is considered as established if
the SRB1 has been admitted and successfully
maxNumRrc 0...840 120
configured. Maximum number of RRC connections
(maxNumRrc) is to be set to a higher value (or equal)
than maximum number of active UEs in the cell:
maxNumActUE + max [addAUeRrHo, addAUeTcHo]
<= maxNumRrc.
The RAC will check this condition for the admission of the
single non-GBR DRB at S1AP Initial Context Setup. A UE is
termed active if at least one single non-GBR data radio
maxNumActUE 0...840 bearer has been successfully configured for it. The 100
number of active UEs in the cell cannot exceed
maxNumActUE + max[addAUeRrHo (15),
addAUeTcHo (20)]
Threshold for the maximum number of established QCI1-
maxNumQci1Dr
0200 GBR-DRBs in the cell. maxNumQci1Drb must 100
b
be equal or less than maxNumActUE.

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

PRACH blocking
In RL30 no KPI or counter for Msg4 contention resolutions
(preamble collisions)
To monitor the number received contention-based
preambles
M8001C6 RACH_STP_ATT_SMALL_MSG
M8001C7 RACH_STP_ATT_LARGE_MSG
R&D target: on average, there should be no more than 3
preambles per PRACH slot
Based on CPU consumption estimate
If preamble load higher, consider adding more PRACH capacity
R&D value to be re-checked when RACH load increases in networks
Example:
Assume one PRACH slot per FDD radio frame 100 slots per second
Hence M8001C6 + M8001C7 value should not exceed 3600*100*3
1M preambles per hour
PRACH parameters and uplink interference situation should
be assessed if ratio of received preambles and Msg3 is very
34
low
Nokia Siemens Networks Presentation / Author / Date
PRACH blocking collision probability
The probability of PRACH contention is proportional to the
square of the UE PRACH attempts and the inverse of the
number of contention based preambles.
The UE attempts per PRACH region should be kept much
lower than the number of contention preamble to avoid
excessive retries
??

PRACH
Recommendation to start with one PRACH slot per 10ms
Target: max three preambles per PRACH slot on average,
this keeps preamble collision probability at <10%
PRACH capacity = 3 * 100 = ~300 preambles per second
PRACH frequency offset comes from PUCCH plan (=3 for
10MHz, 5 for 20MHz)
PRACH time resource index = 3, the same in all cells
Proposal 10MHz/20MHz: prachConfIndex = 3
Proposal 10MHz: prachFreqOff = 3
Proposal 20MHz: prachFreqOff = 5

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

PCH
NSN recommendation to start with one paging occasion
every 40ms 25 paging occasions per second
Each radio interface paging occasion can carry paging for
up to 16 UEs max air interface paging capacity =
16*25=400 UEs paged per second
Proposal: pagingNb = quarterT (40ms)

PCH blocking
Number of UEs blocked (could not fit to air interface paging
message)
LTE_5031b E-UTRAN RRC Paging Discard Ratio
No paging blocking should be allowed
Fixes:
Increase paging capacity
split or replan tracking area
break TA list to smaller sublists
increase inactivity timer
Average number of UEs paged per paging message:
M8008C1 RRC_PAGING_REQUESTS divided by M8008C3
RRC_PAGING_MESSAGES
May be useful for trending
Paging success ratio needs to be checked from MME KPIs

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Project example

Relevant features
RL30
LTE616 Usage based PDCCH adaptation
Adapts number of PDCCH symbols and reduces PDCCH blocking, while not
improving PDSCH tput when cell has few users
LNCEL/actLdPdcch
RL40
LTE979 Interference Rejection Combining (IRC)
eNode B improves the uplink SINR by applying antenna weights in the receiver
which leads to
an improved cell edge performance and
slightly better uplink cell capacity
LTE1387 Intra-eNB Inter-frequency Load Balancing
Inter-frequency load balancing
Measurement based handover (A4), Downlink load criteria

41 Nokia Siemens Networks THa November 2011
Relevant features - continued
RL40
LTE46 Channel Aware Scheduler (UL)
Assignment of PRBs (physical resource blocks) in the frequency domain based
on CSI (channel state indicator)
UE specific CSI is based on filtered measurements from the UL reference signal
and sounding reference signal

Content
PDCCH optimization
PUCCH optimization
PRACH optimization
PCH optimization
Exercise
Project example
For more info:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437727741

Operator X PUCCH configuration
.. and how this is linked to network performance
Operator X LTE800 is network

3Mbps, 7.2 Mbps subscription available for market
no UE mobility configured in the network
Operator X generates eUTRAN parameter list
Default roll-out configuration is

FSME + 2 x FRMA (all 2Tx MIMO)
1/1/1 configuration
Most loaded eNBs highly asymetric number of UEs between cells

example: cell 1: 5 / UE cell 2: 10 / UE cell 3: 80 UE
depending on where in rural area the customer /villages are located

RRC Setup Success Rate
Cell Load counters present max and/or avg number of active UEs in a cell
active means having at least a default bearer activated
MaxNumberActUE indicate there is bottleneck in cell - max never higher than 50

Allocation of PUCCH resources is RAC-Admission Control task and can be
rejected if no further resources are available (counter triggered)
This negative counter is directely impacting RRC setup success rate KPIs

PUCCH configuration as it is in Operator X
<3 Resource Blocks needed for PUCCH> 2 x 6* x 10 = 120 resources for periodic CQI
* currently fixed to 6 in NSN eUTRAN
F2/2a/2b
F2/2a/2b
n1PucchAN = 10 nCqiRb = 2
F1/1a/1b
10 out of 36 resources for SR

10 resources for SR: 26 out of 36 resources for
-> 10 x 5 = 50 for SR PUSCH dynamic ACK-NACK
PUCCH dimensioning is allways trade-off

between resources needed for UL
signaling and resources for UL data
transmission.
Here we have very special setting.

PUCCH configuration as it is Operator X
How UL scheduler allocates physical resources : PUCCH, PUSCH
F2/2a/2b F2/2a/2b
F1/1a/1b unused
Intra-Subframe hopping for PUCCH

50 Physical Resource Blocks
Subframe duration = 1ms
This is very special PUCCH

PUSCH
configuration typically used for
Inter-Subframe hopping
show cases to present maximum
throughput in UL.
On other hand UL PUCCH resources
for signalling are set to minimal
capacities.
unused F1/1a/1b
F2/2a/2b F2/2a/2b
0.5 ms 0.5 ms
Optimised PUCCH config for eNB Site XYX
Increasing capacity for PUCCH in case this is reason for RAC blocking
<6 Resource Blocks needed for PUCCH> 2 x 6* x 10 = 240 resources for periodic CQI
* currently fixed to 6 in NSN eUTRAN
F2/2a/2b
F2/2a/2b
LNCEL: n1PucchAN = 36 LNCEL: nCqiRb = 2
F1/1a/1b
F1/1a/1b
F1/1a/1b
2x18 resources for SR:
2x18x10 = 360 for SR F1/1a/1b
dynamic ACK-NACK area ends here

dynamic ACK-NACK starts here PUSCH Alignment with RRM parameters:
Lookup from CCE table for dyn.ACK-NACK: LNCEL: maxNumRrc = 160
# of CCEs = 26 LNCEL: maxNumActUE = 160
-> roundup( 26/18) = 1

Optimised PUCCH config for Site XYX
How UL scheduler allocates physical resources : PUCCH, PUSCH
F2/2a/2b F2/2a/2b Intra-Subframe hopping for PUCCH

F1/1a/1b F1/1a/1b Subframe duration = 1ms
F1/1a/1b F1/1a/1b
50 Physical Resource Blocks
PUSCH Even more efficient because

no Physical Resource Block(s)
Inter-Subframe hopping
remain unused.
F1/1a/1b F1/1a/1b
F1/1a/1b F1/1a/1b
F2/2a/2b F2/2a/2b
0.5 ms 0.5 ms
PUCCH resources: Impact of other RRM parameters
Options for the periodic transmission of CQI and/or Rank Indication on PUCCH:
option a)
<UE reports Rank Indicator every 2x cqiPerNp>
LNCEL: riPerM = 2 (internal parameter mapping = 1)
LNCEL: riPerOffset = 0
LNCEL: cqiPerNp = 20ms
20 subframes cqiPerNp
CQI Rank CQI Rank CQI
time
20ms 20ms

-> One PUCCH resource allocated per cqiPerNp (here 20ms).
Options for the periodic transmission of CQI and/or Rank Indication on PUCCH:
option b)
<UE reports Rank Indicator every 1x cqiPerNp (one subframe before CQI)>
LNCEL: riPerM = 1 (internal parameter mapping = 0)
LNCEL: riPerOffset = -1
LNCEL: cqiPerNp = 20ms
20 subframes cqiPerNp
Rank CQI Rank CQI Rank CQI Rank CQI Rank CQI
time
20ms 20ms

-> Two PUCCH resources allocated per cqiPerNp (here 20ms).
Conclusion
Option b) needs 2 PUCCH resources to be allocated to a single UE per

cqiPerNp
This additional requirement could be handled with higher amount of
Physical Resource Blocks for Format 2/2a/2b (LNCEL: nCqiRb)
NSN recommendation is option a)

Finally: Site XYX after parameter optimisation
parameter change introduced 31.10. / 11:00
Number of RAC-AC rejects..
..gone !
RRC Setup Success Rate recovering very close to 100%


Capacity Management

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Capacity Management

Încărcat de

Drepturi de autor:

Formate disponibile

Capacity Management for Air Interface

Soc Classification level

Soc Classification level

See notes section of this slide, these are tput figures.

PRB usage, PUSCH cell-level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Format 1/1a/1b Format 1/1a/1b

Soc Classification level

1 subframe with PRACH occasion

1 PRB for SR, 1 PRB for CQI (RI & PMI),

1-3 PRBs for ACK/NACKs,

For 10MHz system:

Soc Classification level

PRBs required for PUCCH ACK/NACK:

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Every UE with a SRB1 in the cell is required to send CQI reports

Soc Classification level

Every user in RRC connected mode requires Format 1.x resource

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

Soc Classification level

For more info:

Soc Classification level

.. and how this is linked to network performance

Operator X LTE800 is network

Operator X generates eUTRAN parameter list

Default roll-out configuration is

Most loaded eNBs highly asymetric number of UEs between cells

Soc Classification level

MaxNumberActUE indicate there is bottleneck in cell - max never higher than 50

Soc Classification level

10 out of 36 resources for SR

PUCCH dimensioning is allways trade-off

Soc Classification level

Intra-Subframe hopping for PUCCH

Subframe duration = 1ms

This is very special PUCCH

dynamic ACK-NACK area ends here

Soc Classification level

F2/2a/2b F2/2a/2b Intra-Subframe hopping for PUCCH