09 RA47049EN70GLA1 Capacity Management

Capacity Management
RA47049EN70GLA1 1
Capacity Management
RA47049EN70GLA1 2
Capacity Management
RA47049EN70GLA1 4
Capacity Management
RA47049EN70GLA1 5
Capacity Management
RA47049EN70GLA1 6
Capacity Management
RA47049EN70GLA1 7
Capacity Management
RA47049EN70GLA1 8
Capacity Management
RA47049EN70GLA1 9
Capacity Management
RA47049EN70GLA1 10
Capacity Management
RA47049EN70GLA1 11
Capacity Management
RA47049EN70GLA1 12
Capacity Management
RA47049EN70GLA1 13
Capacity Management
RA47049EN70GLA1 14
Capacity Management
RA47049EN70GLA1 15
Capacity Management
RA47049EN70GLA1 16
Capacity Management
RA47049EN70GLA1 17
Capacity Management
RA47049EN70GLA1 18
Capacity Management
RA47049EN70GLA1 19
Capacity Management
RA47049EN70GLA1 20
Capacity Management
RA47049EN70GLA1 21
Capacity Management
RA47049EN70GLA1 22
Capacity Management
For the previous solution (w/o OLLA for PDCCH):

Pros:
very simple algorithm (i.e. PDSCH OLLA information are already available).
Cons:
the PDSCH OLLA Offset is based on 10% BLER target and an accurate
setting of parameter pdcchCqiShift is not easy without risking to be too
conservative (i.e. using unnecessary many resources for PDCCH);
the parameter pdcchCqiShift is the same for all the UEs in the system;
unaware of the actual reliability of PDCCH transmissions;
unaware of channel estimation errors occurring when using the Wideband
CQI as the PDSCH ILLA is based on a Frequency Selective CQI.
RA47049EN70GLA1 23
Capacity Management
- if dlChBw is 5MHz then maxNumOfCce is 21

RA47049EN70GLA1 24
Capacity Management

RA47049EN70GLA1 25
Capacity Management

RA47049EN70GLA1 26
Capacity Management
Future features: semi-persistent scheduling for 2-3PRB allocations, like VoIP
RA47049EN70GLA1 27
Capacity Management
RA47049EN70GLA1 28
Capacity Management
RA47049EN70GLA1 29
Capacity Management
(1) The maximum value of nCqiRb depends on ulChBw (in PRB)

- if ulChBw is set to '1.4 MHz', nCqiRb must be configured to 1
- if ulChBw is set to '3 MHz', nCqiRb must be configured to 1
- if ulChBw is set to '5 MHz', nCqiRb is restricted to 1..25
- if ulChBw is set to '20 MHz', nCqiRb is not limited
RA47049EN70GLA1 30
Capacity Management
RA47049EN70GLA1 31
Capacity Management
RA47049EN70GLA1 32
Capacity Management
RA47049EN70GLA1 33
Capacity Management
RA47049EN70GLA1 34
Capacity Management
RA47049EN70GLA1 35
Capacity Management
LTE1089
RA47049EN70GLA1 36
Capacity Management
LTE1089
RA47049EN70GLA1 37
Capacity Management
LTE1562
RA47049EN70GLA1 38
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 39
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 40
Capacity Management
Adaptations proposed by the feature are based on current

cell situation derived from the following counters:
1.Maximum number of RRC connected UEs (M8001C200)
The value of this counter determines if the algorithm would trigger
the optimization of PUCCH capacity by the feature
2.Maximum number of Active/Connected UEs (M8001C224)
The value of the counter serves as a lower limit with respect to
maxNumActUE when adjustments are made to admission control
parameters
3.QCI-specific maximum number of simultaneous ERAB
established (M8006C224 C232)
The value of the counters serves to calculate the lower limit with
respect to maxNumQci1Drb and maxNumActDrb when adjustments
are made to admission control parameters
The counters are collected and averaged over the LTE1808

evaluation period before being used by the algorithm
RA47049EN70GLA1 41
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 42
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 43
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 44
Capacity Management
Example: Trigger to increase PUCCH size

ThrPucchSizeUpper serves as a trigger to possibly increase PUCCH size based
on collected counter information regarding number of RRC Connected Ues.
If number of RRC connected Ues exceed the threshold, admission controls are
adjusted such that the number of RRC connected Ues concide between/within the
Upper and Lower threshold levels, as shown in the figure
Adjustment of admission control parameters are done as a block to carry with the
adjustments the consistency checks existing between parameters
RA47049EN70GLA1 45
Capacity Management
Example: Trigger to decrease PUCCH size

ThrPucchSizeLower serves as a trigger to possibly decrease PUCCH size based
on collected counter information regarding number of RRC Connected Ues.
If number of RRC connected Ues exceed the threshold, admission controls are
adjusted such that the number of RRC connected Ues coincide between/within the
Upper and Lower threshold levels, as shown in the figure
Adjustment of admission control parameters are done as a block to carry with the
adjustments the consistency checks existing between parameters
RA47049EN70GLA1 46
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 47
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 48
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 49
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 50
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 51
Capacity Management
LTE1808 RL70
RA47049EN70GLA1 52
Capacity Management
LTE786 RL50
RA47049EN70GLA1 53
Capacity Management
LTE786 RL50
RA47049EN70GLA1 54
Capacity Management
LTE786 RL50
RA47049EN70GLA1 55
Capacity Management
RA47049EN70GLA1 56
Capacity Management
RA47049EN70GLA1 57
Capacity Management
RA47049EN70GLA1 58
Capacity Management
RA47049EN70GLA1 59
Capacity Management
RA47049EN70GLA1 60
Capacity Management
Maxnumrrc
The recommended default value depends on min(ulChBw, dlChBw) with following condition:
min(ulChBw, dlChBw) = '1.4 MHz', recommended default 20
min(ulChBw, dlChBw) = '3 MHz', recommended default 80
MaxnumActUE
The recommended default value depends on min(ulChBw, dlChBw) with following condition
min(ulChBw, dlChBw) = '1.4 MHz', recommended default 20
MaxnumQci1Drb
default value depends on min(ulChBw, dlChBw) with following condition
RA47049EN70GLA1 61
Capacity Management
RA47049EN70GLA1 62
Capacity Management
Additional preamble sequences:

in case the 64 preambles cannot be generated from a single root Zadoff-Chu
sequence, then remaining preambles are obtained from the root
sequences with the consecutive logical indexes until all the 64 sequences
are found.
RA47049EN70GLA1 63
Capacity Management
zero correlation zone existence in Zadoff-Chu sequence provides the possibility

to decode signals on PRACH even if sent on the same shared resources: on the
same frequency and in the same time.
preamble signals generated based on two different ZC sequences are not
correlated within the geographical range related to prachCS (i.e. Cyclic Shift
configuration index)
the size of the cyclic shift, must be larger than the maximum round-trip delay, so
prachcs is dependant on the cell radius
RA47049EN70GLA1 64
Capacity Management
RA47049EN70GLA1 65
Capacity Management
RA47049EN70GLA1 66
Capacity Management
Note: By configuring the PRACH Configuration Indexes at cells

belonging to the same site we use the same subframes for PRACH
transmission
Neighboring eNodeBs are not synchronized so even if the same
PRACH configuration indices, there is no guarantee that the PRACH
will clash in the time domain. It is possible to set different frequency
offsets so PRACH doesnt clash in frequency domain.
RA47049EN70GLA1 67
Capacity Management
RA47049EN70GLA1 68
Capacity Management
PrachCS also depends on the high speed flag.
Currently the common practice is to assume the same cell ranges for
all cells: If all cells are considered to have the same size, the utilization
of root sequences will not be optimal as we will end up using more root
sequences per cell than the needed for certain cell range.
RA47049EN70GLA1 69
Capacity Management
RA47049EN70GLA1 70
Capacity Management
RA47049EN70GLA1 71
Capacity Management
RA47049EN70GLA1 72
Capacity Management
RA47049EN70GLA1 73
Capacity Management
RA47049EN70GLA1 74
Capacity Management
RA47049EN70GLA1 75
Capacity Management
RA47049EN70GLA1 76
Capacity Management
RA47049EN70GLA1 77
Capacity Management
RA47049EN70GLA1 78
Capacity Management
RA47049EN70GLA1 79
Capacity Management
E-mail communication with R&D, March 23 2012:
RL 40: Up to 64 Preambles per Access slot shall be possible to handle on UL PHY

and up to 8 on MAC PS as a burst capacity. However the amount C-Plane actions
during one second have been defined on LTE_CAP_3325 and _3771.
It has been internally calculated that 3 would be realistic amount of Preambles per
Access slot at least on theory.
That value has been calculated assuming that it is enough to be able to handle
>99% of preambles and assuming that there are 50% of all C-Plane actions of eNB
in one cell and all using RA procedure. With 3 Preambles per Access slot it should
also be possible to handle all 150 Actions/s in one cell in case two Access slots per
frame configured.
Additionally there have been added some margin due to ghost preambles.
RA47049EN70GLA1 80
Capacity Management
RA47049EN70GLA1 81
Capacity Management
RA47049EN70GLA1 82
Capacity Management
Maximum air interface capacity is 1600 Paging Records per second per cell.
Obviously, this is more than our eNB can provide in C-Plane. We see roughly
4% CPU load on FSMP for 30 S1 Pagings per second. So with 500 S1 Paging
messages per second (and one FSMP per cell), we would occupy 2/3 of CPU
processing power for Paging alone. We regards this as the maximum possible value.
RA47049EN70GLA1 83
Capacity Management
RA47049EN70GLA1 84
Capacity Management
Comments from NPO:

1. MME dimensioning has until now been based on the traffic mix and the
signaling transaction processing capacity of MME, with the product line internal
assumption that TA size is 40eNBs.
2. Since TA size is often made equal to underlying 3G LA, the limitation of 40
eNBs is not practical from planning point of view.
3. However if TA size is >>40eNBs it is the S1 paging load that starts limiting
MME CPU capacity. These rules have not been recorded in trainings before
and relatively or completely unknown even in EPC planning community.
4. MME S1 paging message capacity depends on the sw release and hw
configuration. As an example with the latest NS2.2 2.0 and minimum MME hw
config (one IPDU pair), it is around 25000 S1 paging messages per second. In
NS3 it will be at least twice that.
a. Hence if you have 1000 BTSs in one TA and total of 25 subs camping
in the whole TA, and each sub generates one paging from S11 interface
per second, you are hitting the MME S1 paging capacity, even if there is
no other signaling at all. (stupid example)
5. Summary is that
a. both i) the number of signaling transactions for the given traffic mix
(attaches, bearer activations, TAUs, S1 releases, Service Requests etc)
b. and the ii) S1 paging load have to be taken into account, in order to find
which one is the bottleneck.
c. Until now only item i) was considered.
RA47049EN70GLA1 85
Capacity Management
RA47049EN70GLA1 86
Capacity Management
RA47049EN70GLA1 87
Capacity Management
RA47049EN70GLA1 88
Capacity Management
RA47049EN70GLA1 89
Capacity Management
RA47049EN70GLA1 90
Capacity Management
RA47049EN70GLA1 91
Capacity Management
RA47049EN70GLA1 92
Capacity Management
RA47049EN70GLA1 93
Capacity Management
RA47049EN70GLA1 94

09 RA47049EN70GLA1 Capacity Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

09 RA47049EN70GLA1 Capacity Management

Uploaded by

Copyright:

Available Formats

Capacity Management

For the previous solution (w/o OLLA for PDCCH):

- if dlChBw is 5MHz then maxNumOfCce is 21

- if dlChBw is 5MHz then maxNumOfCce is 21

- if dlChBw is 5MHz then maxNumOfCce is 21

Future features: semi-persistent scheduling for 2-3PRB allocations, like VoIP

(1) The maximum value of nCqiRb depends on ulChBw (in PRB)

Adaptations proposed by the feature are based on current

The counters are collected and averaged over the LTE1808

Example: Trigger to increase PUCCH size

Example: Trigger to decrease PUCCH size

Additional preamble sequences:

zero correlation zone existence in Zadoff-Chu sequence provides the possibility

Note: By configuring the PRACH Configuration Indexes at cells

PrachCS also depends on the high speed flag.

E-mail communication with R&D, March 23 2012:

RL 40: Up to 64 Preambles per Access slot shall be possible to handle on UL PHY

Comments from NPO:

You might also like