You are on page 1of 42

Capacity Management and Special

event solution guideline


Etisalat, Sri Lanka
Prepared by: Chandan Kumar Singh
Vendor : Alcatel lucent

Privileged and confidential. The information contained in this material is privileged and confidential, and is intended only for the use of the individual to whom it is addressed and others who have been specifically authorized to receive it.
If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this material is strictly prohibited. If you have received this material in error, please destroy it immediately.
Table of content
Special Event Definition & Context
Key challenges
RNC Capacity
RNC Load
NODEB CAPACITY
Carrier Configuration & Mobility strategy
Carrier Configuration & Mobility strategy
UL Cell load
DL Power & Code utilization
Radio bearer management
SHO mobility
Transmission capacity
Emergency setting

2
Special Events and capacity management recommendation

Current RNC,
NodeB
Capacity

Develop Action Plan(Capacity Plan activated Post event


enhancement & Parameter
during the event or review/lesson
changes RNC, NodeB, Cell etc.)
at any instance learnt

Predicted subscriber
growth during the
event and throughout
the year

3
Special Events and capacity management recommendation
Introduction Special Event Definition & Context
There are two type types of specific events:
Planned ones (e.g. match) where a capacity/optim study can be done.
Unplanned (natural disaster) where no capacity study can be done, only emergency
settings can be applied

A special event is usually defined as:


Increased Traffic Profile: traffic volume, BHCA; Increase in SMS activity in the
venues. Hence, RRC traffic, paging and radio interface for SMS type of signalling
only activities require some attention. There is also an increase in MMS activity in
these locations (proceeded by an SMS). Hence, PS calls increase due to MMS.
Customer focus is usually more capacity than call quality
Limited Mobility: in situation of localized events, we can expect the mobility scenarios
to be limited. The change of radio conditions is more a result of high traffic load and
interferences than user mobility itself.
Overall increased customer support: due to limited time activity and high exposure,
this kind of events usually requires high reactivity to the KPI degradation.
Sporadic events, with limited experience and knowledge of the real profile .

4
Special Events and capacity management recommendation
Key challenges
RNC Capacity(User plane & Signaling plane traffic)
NodeB Capacity(R99, HSDPA,HSUPA users & Throughput Licesnses\Tokens) or
Channel Element configuration
Carrier configuration and mobility strategy for event to utilize each carrier to maximum
extent and use 2G Layer in case of severe degradation for Voice(via RRC Redirection).
High UL Cell Load
DL Power & Code utilization

Radio Bearer Management


SHO

Transmission Capacity to handle NodeB Traffic


Optimization during the event to minimize any severe degradation(using WPS in Alcatel)

5
Special Events and capacity management recommendation
RNC Capacity

TMU Handles
signalling(Control
Plane e.g.
RRC,RANAP,MBAP
messages) load

RAB Handles the


Traffic(Use plane
traffic)

6
Special Events and capacity management recommendation
RNC Load
Based on RNC Load following checks need to be done

RNC Capacity check e.g. if RNC have sufficient headroom to carry traffic expected
during the event.
Any migration plan if require to offload RNC in which event is planned.
Any TMU Rebalancing required to balance TMU Load(RRC, Signaling) on RNC.

New RNC Recommendation based on expected traffic during the mass event(Cricket
World Cup, long Religious event). Based on subscribers data e.g. Roamers expected
during the event, increase in traffic expected from past years.
Capacity expansion on RNC by adding additional eDCPs Cards or converting RAB to
TMU to handle signaling load during the event.

7
Special Events and capacity management recommendation
RNC Load
Specific Radio features tuning to limit impact of high traffic on RNC PMC load.

Due to higher number of subscribers, the RNC can experience abnormal PMC (TMU,
RAB, PC) load. Some action can be taken to reduce the number of RAB reconfigurations,
therefore reduce the TMU load.

One proposal is to reduce the number of reconfigurations (downsizing) on the 64kbps


Uplinks by increasing the size of the threshold sampling window from 2 seconds to 5
seconds.
Special Event
Parameter Path Class Normal Setting
Setting
RadioAccessService/0 UlRbSetConf/PS_64K_IB
raNbOfSample 3 4 10
UlRbRaTrafficMonitoring/0
RadioAccessService/0 UlRbSetConf/PS_64K_IB_MUX
raNbOfSample 3 4 10
UlRbRaTrafficMonitoring/0
RadioAccessService/0 UlRbSetConf/PS_64K_IB_MUX3
raNbOfSample 3 4 10
UlRbRaTrafficMonitoring/0

Reduce the number of RRC automatic repetitions (cf Initial Access Settings)
T300 = 6s, N300 = 1, T351 = 800ms, isQuickRepeatAllowed = False

8
Special Events and capacity management recommendation
NODEB CAPACITY

Engineering
Load of 70% as
the average load
at which 95% of
calls meet KPIs.

256 CE per CEM


Board

9
Special Events and capacity management recommendation
NODEB CAPACITY

1 eCEM\xCEM can handle


256 R99 Calls
128 HSDPA and 128 HSUPA Calls
39.4 Mbps HSDPA Throughput supported on xCEM whereas eCEM supports up
to 61 Mbps.
eCEM can handle higher RL messages compare to xCEM.

TEOCO provide two kind of NodeB Solutions:D2U or D4U Solution


D2U can support 3 eCEM\xCEM boards
D4U Can support up to 5 eCEM\Xcem Board

TEOCO recommend to have D4U which can support up to 5 CEM Boards(1280 R99
CE, 640 HSDPA CE & 640 HSUPA CE) on each Sites. Carrier configuration can be
based on spectrum availability.

10
Special Events and capacity management recommendation
Carrier Configuration & Mobility strategy

Carrier Configuration
Carrier configuration can be decided on basis of spectrum availability, taking
expected traffic into account.
Need to be careful on making layers contiguous in the area to avoid loading on
any specific layers or carriers.

Mobility strategy
Parameter tuning
Equal Priority\Load balancing strategy need to be applied which ensure better
resource utilization in terms of power, carrier and Channel element which in
terms bring improvement in CSSR & CDR KPIs with improvement in
throughput(Observed across most of network).
Reduction in carrier power allocated to Voice & R99 & signalling which in term
bring decrease in DL Power R99 ,Voice and signaling transmitted power results
in improvement in overall KPIs.

11
Special Events and capacity management recommendation
Equal Priority or Load Balancing strategy
Equal Priority Settings to distribute equally the traffic among the layers

Guarantee that load distribution among different cells is performed in idle mode and
that minimum EcN0 / RSCP are respected to maintain an acceptable Qos.
For each FDDLayer, only neighbour cells from 2 different layers are broadcast in the
SIB11 to introduce a deterministic round robin selection between all carriers.
Idle Mode strategy with UEs camping homogenously across carriers (qOffset1sn and
qoffset2sn set to 0). However Qoffset2sn can be increased to 2 on a cleaner FDD
layer to favour this layer in the second ranking and ensure equal load distribution.
Asymmetric CS/Data traffic profile (in some cases PS traffic is 30 times the CS traffic).
E.g. dedicated layer for CS services would lead to unused resources on CS preferred
layer and be detrimental to high value end users camping on Data layers.
Suitable for capacity oriented purposes. On high traffic conditions there is a real
capacity gain by spreading Voice and HSPA traffic in a symmetric way across different
layers.
Radio resource connection (RRC) Redirection strategy based on Load Distribution. RRC
Redirection is restricted to collocated 3G carriers. No RRC redirection from 3G to 2G

12
Special Events and capacity management recommendation
Equal Priority or Load Balancing strategy

Redirect calls to twin layers (3G) upon Call admission control (CAC) Failure on Traffic
Radio Bearer

Higher reactivity to cell quality degradation


The sIntraSearch and sInterSearch are deliberately increased to be more reactive in
case of quality degradation.

Restricted Cell Selection/reselection coverage criteria


The qRxLevMin is increased to avoid unnecessary interference on cell edge. Also this
avoids UE camping on clean capacity layers and being unable to come back to
coverage layers when leaving the special event area.

13
Special Events and capacity management recommendation
Equal Priority or Load Balancing strategy

Special Event and capacity


Parameter Normal Setting management Setting

CellSelectionInfo/0 F1 F2

Qoffset1sn 0 0 0 qQualmin can be lowered


to -18 to avoid some UE to
Qoffset2sn 0 0 0 loose the cell during high
qHyst1 4 4 4 traffic load.

qHyst2 4 2 2
Set qRxLevMin = -101 in all
qQualMin -16 -16 (*or -18) -16 (*or -18)
layers avoiding UEs on cell
qRxLevMin -115 -101 -101 edge to create unnecessary
qualMeas qualMeasEcN0 qualMeasEcN0 qualMeasEcN0 interference. This level will also
ensure not performing RRC
sHcsRatGsm 0 0 0 redirection on cell edge.
sInterSearch 6 10 10 (or 8*)
* Option: cleaner Spectrum
sIntraSearch 8 10 10
layers (non continuous layers in
sSearchHcs 0 0 0 the network) are preferred for
cell reselection to take benefit
sSearchRatGsm 4 4 4
from EcNo capacity
tReselection 1 1 1

14
Special Events and capacity management recommendation
Equal Priority or Load Balancing strategy

HoConfClass/ Cells on 3G couvrage

cpichEcNoThre timeToTrigger F1 2100 CS/Data


sholdUsedFreq 2D/2F
2D/2F

UsHoConf/CsS 640/640 F2 2100 CS/Data


peech -14/-11

UsHoConf/PsH 640/640
SDPA -24/0

Radio resource connection (RRC) Redirection


Declare all inter carrier collocated layers strategy based on Load Distribution. RRC Redirection
Use sib11AndDch parameter to manage Idle is restricted to collocated 3G carriers. RRC redirection
aassessment starts at load RED
iMCRA strategy based on a early Load Distribution (YELLOW). RRC Redirection is
restricted to cells in the same NodeB.
isRrcRedirectionInterFreq = TRUE;
rrcRedirectionType = preferredFa;
rrcRedirectOrigCellColourThreshold = YELLOW;

15
Special Events and capacity management recommendation
Equal Priority or Load Balancing strategy

HoConfClass/ Cells on 3G couvrage

cpichEcNoThre timeToTrigger F1 2100 CS/Data


sholdUsedFreq 2D/2F
2D/2F

UsHoConf/CsS 640/640 F2 2100 CS/Data


peech -14/-11

UsHoConf/PsH 640/640
SDPA -24/0

Declare all inter carrier collocated layers


Radio resource connection (RRC) Redirection
Use sib11AndDch parameter to manage Idle strategy based on Load Distribution. RRC Redirection
is restricted to collocated 3G carriers. RRC redirection
aassessment starts at load RED
iMCRA strategy based on a early Load Distribution (YELLOW).
RRC Redirection is restricted to cells in the same NodeB.
isRrcRedirectionInterFreq = TRUE;
rrcRedirectionType = preferredFa;
rrcRedirectOrigCellColourThreshold = YELLOW;

16
Special Events and capacity management recommendation
UL Cell load

Initial Access Paging Repetitions | The aim is to guarantee a balanced configuration for the
RRC repetitions from UE to minimize signalization load and limit peaks of UL RSSI in RACH and
limit the load due to higher paging volume
High network load after a natural disaster or special event, leads to degradation in
Accessibility. This degradation is driven by a large volume of RACH attempts and Radio
Resource connections (RRC), that can snowball as repetitions increase the congestion. Purpose
is to protect against this snowball effect and preserve the best accessibility performance.
Limit spikes of RSSI due to retransmissions on the RACH
The open loop parameters are modified to limit the power ramp up, ie the first transmission
power of the UE on the preamble part, the number of preamble repetitions and the step on
power increase on the PRACH.
Increase of RACH persistency level in case of high BLER on RACH
Limit the maximum Ue Tx Power to 18 dBm instead of 24 dBm on Rach.
Limit the number of RRC repetitions
Limit the number of automatic repetitions from the UE and introduce a delay on the UE side
before reattempting, therefore relieving the radio resource congestion (UL Load, DL power and
OVSF codes, CEM and Iub, and TMU load). The main drawback is a possible increase on the
Call setup time for all calls in bad RF conditions which require subsequent RRC attempts.
Alternatively to disabling RRC paging repetitions, activate the paging repetition per domain
only for CS and SMS in case intent is to protect those services.

17
Special Events and capacity management recommendation
UL Cell load

Initial Access Paging Repetitions | The aim is to guarantee a balanced


configuration for the RRC repetitions from UE to minimize signalization load and limit peaks of UL RSSI in
RACH and limit the load due to higher paging volume

Special Event preambleRetransMax


Parameter Class Normal Setting
Setting can be increased to
T300 3 2s 6s 20 if Fach call drop
increases
N300 3 4 1
T352 3 4s 4s
T351 3 700 800
N351 3 1 1
isQuickRepeatAllowed 3 True False
ConstantValue 3 -17 -21 dynamicPersistenceLevel
powerOffsetPO 3 3 2 (under BTSCell) set to 2
preambleRetransMax 3 32 15 divides by 2 the
Other settings can be probability for the UE to
mmax 3 8 4
proposed in case of make a RACH attempt
dynamicPersistenceLevel 3 1 2 after a first attempt. Shall
TMU overload (See
maxUlInterferenceLevel 3 -50 -50 be used in case of high
Section on RNC Load)
waitTimerOnRRCConnectionRejection 3 5s 0 RACH BLER (RACH
sibMaxAllowedUlTxPowerOnRach 3 24 18 demodulator resource
shortage or high RSSI)
The open loop power control parameters are reduced to limit the power ramp-up
during initial access.

18
Special Events and capacity management recommendation
UL Cell load

The aim is to play with a whole parameters setting to minimize the RSSI contribution from different
calls and being able to accept traffic in acceptable conditions

Fast Sir decrease feature for Edch is applicable to a special event context:

Avoids that the SIR target for a Mac-d flow remains unchanged when no MAC-es PDUs are
received (inactivity case), and therefore avoids UL physical channels to be transmitted at power
levels higher than required.

Parameter Class Type Normal Setting Special Event Setting

isEdchFastSirTargetDecreaseAllowed Class 3 False True


eDCHOlpcInactivityTimeThreshold Class 3 0.5 0.5

eDCHOlpcInactivitySIRDecreaseLimit Class 3 5 5

edchSirStepFastDecrease Class 3 -0.05 (10ms) -0.05 (10ms)


edchNrOfConsecutiveZeroHarqReTxThreshold Class 3 200 200

19
Special Events and capacity management recommendation
DL Power & Code utilization
The objective is to protect the Qos as much as possible for the Voice (e.g: reducing the PcpichPower
on cells covering the event to prevent blocking, enable the dynamic Code tree management or Fair
sharing to improve code usage efficiency)

Avoid usage of SRB13,6K on establishment causes (see Radio Bearer Management slides). If not
possible due to lack of CEM resources, set initial, min, and max DL Tx Power to lower values for
SRB13,6K.
Reduce the PcpichPower on cells covering the event to prevent blocking;
Enable the dynamic Code tree management or Fair sharing to improve code usage efficiency.
Disable downlink 64QAM to avoid high throughput data taking all the DL resources, at the expense
of other voice or PS R99 services.
If lots of HSDPA calls are running in your cell, system may experience quite strong cell breathing
effect. It is possible to limit this by reducing the Power allocated to HSDPA using hsdpaAmpUsage.
Reduce maxDlTxPowerPerOls for PS R99 services. This is to prevent high speed PS R99 services
from consuming too much power.
Increase callAdmissionRatio to extend available power for first RL creation. Reduce Nbap Common
Meas reporting period to enhance power estimation by the RNC. Reduce Power_Margin and
overestimate for better accuracy of the power estimation
Reduce the IRM PLC thresholds to favour call admission capacity versus call throughput.

20
Special Events and capacity management recommendation
DL Power & Code utilization
The objective is to protect the Qos as much as possible for the Voice (e.g: reducing the PcpichPower on
cells covering the event to prevent blocking, enable the dynamic Code tree management or Fair sharing
to improve code usage efficiency)

The idea is to reduce the contribution of the SRB on the DL power usage, assuming the higher
call attempts and signalling activity generated by the event.

Special Event
Parameter Class Type Normal Setting
Setting

initialDlEcN0Target Class 3 -16 -16


SRB3,4K
minDlTxPower Class 3 -18 -21
SRB3,4K
maxDlTxPowerPerOLS Class 3 -5 -5
SRB3,4K
initialDlEcN0Target Class 3 -13 -13
SRB13,6K
minDlTxPower Class 3 -18 -18
SRB13,6K
maxDlTxPowerPerOLS Class 3 1 -2
SRB13,6K

21
Special Events and capacity management recommendation
DL Power & Code utilization
The objective is to protect the Qos as much as possible for the Voice (e.g: reducing the PcpichPower
on cells covering the event to prevent blocking, enable the dynamic Code tree management or Fair
sharing to improve code usage efficiency)

Objective is to protect the Qos as much as possible for R99 services and limit DL resource for
HSDPA.

Normal Special Event


Parameter Class
Setting Setting
maxTxPower maxTxPower -13
pcpichPower 3
-10dB dB
isdl64QamAllowed 3 True False
hsdpaAmpUsage 3 100 80

22
Special Events and capacity management recommendation
DL Power & Code utilization
The objective is to protect the Qos as much as possible for the Voice (e.g: reducing the
PcpichPower on cells covering the event to prevent blocking, enable the dynamic Code
tree management or Fair sharing to improve code usage efficiency)

algo1DeltaTarg
algo1DeltaTarge maxDlTxPowerPer maxDlTxPowerPerOl
etPower maxDlTxPowerPerOl
DlUsPowerConf tPower (Special Ols (Normal s (Special Event
(Normal s (Special Event)
Event) Setting) Not Validated)
Setting)
CS_AMR_LRxSRB_3_4K 6.0 6.0 -5.0,-5.0,-5.0 -5.0,-5.0,-5.0 -5.0,-5.0,-5.0
CS_AMR_NBxPS_8K_IBxSRB_3_4K 9.0 9.0 4.0, 4.0, 4.0 1.0, 1.0, 1.0 0.0, 0.0, 0.0
CS_AMR_NBxPS_16K_IBxSRB_3_4K 6.0 6.0 4.0, 4.0, 4.0 1.0, 1.0, 1.0 0.0, 0.0, 0.0
CS_AMR_NBxPS_32K_IBxSRB_3_4K 9.0 9.0 4.0, 4.0, 4.0 3.0, 3.0, 3.0 0.0, 0.0, 0.0
CS_AMR_NBxPS_64K_IB_MUX3xSRB_3
_4K
9.0 9.0 4.0, 4.0, 4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
CS_AMR_NBxPS_64K_IB_MUXxSRB_3_
9.0 9.0 4.0, 4.0, 4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
4K
CS_AMR_NBxPS_64K_IBxSRB_3_4K 9.0 9.0 4.0, 4.0, 4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
CS_AMR_NBxPS_128K_IB_MUXxSRB_3
_4K
9.0 9.0 6.0, 6.0, 6.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
CS_AMR_NBxPS_128K_IBxSRB_3_4K 9.0 9.0 6.0, 6.0, 6.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
CS_AMR_NBxPS_384K_IB_MUXxSRB_3
_4K
6.0 6.0 7.0, 7.0, 7.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
CS_AMR_NBxPS_384K_IBxSRB_3_4K 6.0 6.0 7.0, 7.0, 7.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0

23
Special Events and capacity management recommendation
DL Power & Code utilization
The objective is to protect the Qos as much as possible for the Voice (e.g: reducing the
PcpichPower on cells covering the event to prevent blocking, enable the dynamic Code
tree management or Fair sharing to improve code usage

algo1DeltaTarg
algo1DeltaTarg maxDlTxPowerPerOls
etPower maxDlTxPowerPerO maxDlTxPowerPerOl
DlUsPowerConf etPower (Special Event Not
(Normal ls (Normal Setting) s (Special Event)
(Special Event) Validated)
Setting)
CS_AMR_NBxPS_HSDSCHxSRB_3_4
K
9.0 9.0 1.0, 1.0, 1.0 1.0, 1.0, 1.0 0.0, 0.0, 0.0
CS_AMR_NBxSRB_3_4K 9.0 15.0 1.0, 1.0, 1.0 1.0, 1.0, 1.0 0.0, 0.0, 0.0
PS_8K_IBxSRB_3_4K 9.0 9.0 1.0, 1.0, 1.0 -2.0, -2.0, -2.0 -2.0, -2.0, -2.0
PS_16K_IBxSRB_3_4K 6.0 6.0 4.0,4.0,4.0 1.0, 1.0, 1.0 0.0, 0.0, 0.0
PS_32K_IBxSRB_3_4K 9.0 9.0 4.0,4.0,4.0 3.0, 3.0, 3.0 0.0, 0.0, 0.0
PS_64K_IB_MUX3xSRB_3_4K 9.0 9.0 4.0,4.0,4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_64K_IB_MUXxSRB_3_4K 9.0 9.0 4.0,4.0,4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_64K_IBxSRB_3_4K 9.0 9.0 4.0,4.0,4.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_128K_IB_MUXxSRB_3_4K 9.0 9.0 6.0,6.0,6.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_128K_IBxSRB_3_4K 9.0 9.0 6.0,6.0,6.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_384K_IB_MUXxSRB_3_4K 6.0 6.0 7.0,7.0,7.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_384K_IBxSRB_3_4K 6.0 6.0 7.0,7.0,7.0 3.0, 3.0, 3.0 1.0, 1.0, 1.0
PS_HSDSCHxSRB_3_4K 14.0 14.0 -5.0,-5.0,-5.0 -5.0,-5.0,-5.0 -5.0,-5.0,-5.0

24
Special Events and capacity management recommendation
DL Power & Code utilization
Increase Call Admission Ratio to extend available power for first RL creation.
At the expense of the Power Margin for SHO which is reduced, which is acceptable in a
limited mobility context:
Increase of Call Admission Ratio to 95% can be done at cell level with a specific
PowerConfClass for Special Event Area:

Normal Special Event


Parameter Class Type Setting Setting
CallAdmissionRatio Class 3 85% 95%

In this example a call


Admission Ratio of 95%
leads to a gain of 1.2W
on the traffic power for
admission

25
Special Events and capacity management recommendation
DL Power & Code utilization
Reduce NBAP Common Measurement Reporting Period for better accuracy of the power estimation
in the RNC (BTSPowerSelfTuning).
Reduce Power_Margin and overestimate to increase the capacity
RNC power tuning compares the actual load to internal estimate
Underestimated: Raises new estimate to actual plus powerMargin (0.1dB instead of
0.2 dB)
Overestimated: If the load has been overestimated by at least overEstimate
0.2 dB instead of 1 dB), then lowers the new estimate to the actual

Special
Normal
Parameter Class Type Event
Setting
Setting
CommonMeasurementReportingPe
Class 3 10 s 2s
riod
isBtsPowerSelfTuningActivated Class 3 True True

overestimate Class 3 1 dB 0.2 dB

PowerMargin Class 3 0.2 dB 0.1 dB


activityFactorCCCH Class 3 66% (GM) 50%
PowerMargin Class 3 0.2 dB 0.1 dB

26
Special Events and capacity management recommendation
DL Power & Code utilization
FachPowerAdjustment changes to limit FACH power:
In case of high percentage of RRC Connection setup repeated by the RNC, to decrease
the power utilisation, we can lower the fachPowerAdjustmentCpichEcNoThreshold to
value -13, this represents the absolute threshold of Pcpich quality which activates the
feature. During special events, the number of bad EC/N0 samples is generally higher so
it makes sense to decrease the activation threshold to mitigate the impact of RRC
Connection storm and reduce DL power usage.

Special Event
Parameter Class Normal Setting
Setting
fachPowerAdjustmentCpichEcN0Threshold 3 -8 -13

27
Special Events and capacity management recommendation
DL Power & Code utilization
DualCell Deactivation to save power & CEM resources.
Dual cell need to be deactivated as purpose is not to provide high throughput but
reasonable throughput by taking care overall traffic into account.

Special Event
Parameter Class Normal Setting
Setting
DualCellActivation 3 True False

28
Special Events and capacity management recommendation
DL Power & Code utilization
IRM Colour thresholds allow quicker trigger based on Code load, UL RF power, Downlink RF power,
DL/UL CEM and IuB. This will allow NodeB to handle its capacity much better.

RRC Redirection - IMCRA | Interfrequency load balancing during the RRC phase and offload the 3G in
case of specific events

RRC redirection aassessment starts at load RED

29
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Rate Capping for PS R99 services


Activate the rate capping feature and modify the default parameters in uplink and downlink to limit
the R99 load

Activate the AMR LR feature at call setup


Activate feature 34403 AMR Low Rate Selection to select the AMR 5,9K voice calls in limited
OVSF codes scenario. The multimode rate changes during the call with codec rate adaptation
based on RF & Iub Load and Trfo is disabled (feature 32687 AMR mode change during the call is
disabled).
AMR codec selection at call setup is chosen according to DL OVSF code load and OLS. For this
selection the RNC is using the already existing IRM table for the downlink OVSF load. This AMR
codec set can be mapped to physical channel with SF128 or SF256. We choose the SF128 setting
since due to high puncturing, CS2 5.9K (SF256) is less power efficient than CS1 5.9K (SF128).

Map Establishment Causes on SRB3,4k


Forces the call setup on the SRB3,4K, which is less demanding than SRB13,6K on power and
code resource (if call setup time is not a key criteria RNC level change). This is highly
recommended for causes as reselection and registration which can generate high signalling traffic.
The drawback is an extra cost on CEM utilisation, so shall be used only if no lack of CEM
resource.

30
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Activate MultiRAB Call Drop Reduction


Purpose of this algorithm is to avoid voice call drop in case of multi-service RAB. This option shall
be considered if customer priority is to protect CS calls in a special event context since

Increase capacity on CELL_FACH state


The higher usage of cell_fach advises to use higher values for CAC fac failure

31
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Limit the data rates for a better utilization of the radio resources.
The rate capping parameters can be modified in uplink and in downlink to limit the R99 load :

Special
Normal
Parameter Class Event
Setting
Setting
isOamCappingOfDataAllowed 3 TRUE TRUE
Downlink maxDlRateHsdpaAndDchToDchAndDch 3 PS_384K PS_128K
maxDlRateHsdpaAndEdchToDchAndDch 3 PS_384K PS_128K

maxDlRateRabEstablishDchAndDch 3 PS_384K PS_128K

maxDlRateTransitionToDchDlTriggerDchAndDch 3 PS_384K PS_128K

maxDlRateTransitionToDchUlTriggerDchAndDch 3 PS_64K PS_64K


Uplink maxUlRateHsdpaAndDchToDchAndDch 3 PS_64K PS_64K
maxUlRateHsdpaAndEdchToDchAndDch 3 PS_64K PS_64K

maxUlRateHsdpaAndEdchtoHsdpaAndDch 3 PS_64K PS_32K

maxUlRateRabEstablishDchAndDch 3 PS_64K PS_64K

maxUlRateRabEstablishHsdpaAndDch 3 PS_64K PS_32K 32


Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Limit the data rates for a better utilization of the radio resources.
At the call setup, select only a subset of the offered AMR codec in case of high DL OVSF
code load.

Special Event
Parameter Path Class Normal Setting
Setting

isAmrMultiModeAllowed RadioAccessService 3 completelyEnabled completelyEnabled

isAmrMultiModeSetupAllowed FDDCell 3 True True

allowedIuUpVersion CsCoreNetworkAccess 3 V2_or_V1 V2_or_V1

isAmrRbSelectionV2AtAdmissionAllowed RadioAccessService 3 False (default) True


isAmrRbSelectionV2AtAdmissionAllowedIn
FDDCell 3 False (default) True
Cell
isAmrRateControlDuringTheCallAllowed RadioAccessService 3 False (default) False

isAmrRateControlOnUlCellLoadAllowed RadioAccessService 3 False (default) False

isAmrRateControlOnDlPowerLoadAllowed RadioAccessService 3 False (default) False

isAmrRateControlIubDsLoadAllowed RadioAccessService 3 False (default) False

33
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Limit the data rates for a better utilization of the radio resources.
At the call setup, select only a subset of the offered AMR codec in case of high DL OVSF
code load.
Parameter Path Class Special Event Setting

amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/0 irmAmrconfParOls/0 3 HighRate


amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/0 irmAmrconfParOls/1 3 HighRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/0 irmAmrconfParOls/2 3 HighRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/0 3 LowRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/1 3 LowRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/2 3 LowRate
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/0 3 SF128
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/1 3 SF128
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/1 irmAmrconfParOls/2 3 SF128
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/0 3 LowRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/1 3 LowRate
amrRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/2 3 LowRate
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/0 3 SF128
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/1 3 SF128
amr5p9MonoRateConfig RadioAccessService dlCodeirmTable/0 irmAmrConfList/2 irmAmrconfParOls/2 3 SF128

34
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Limit the data rates for a better utilization of the radio resources.
Forces the call setup on the SRB3,4K, which is less demanding on power and code resource (if call
setup time is not a key criteria RNC level change). This is highly recommended for causes as
reselection and registration which can generate high signalling traffic.

Special Event
Parameter Path Class Normal Setting
Setting

dlUserServiceId ServiceInit/0 UserServices/InterRatCellReselection 3 SRB_13_6K_DCH SRB_3_4K_DCH

ulUserServiceId ServiceInit/0 UserServices/InterRatCellReselection 3 SRB_13_6K_DCH SRB_3_4K_DCH

dlUserServiceId ServiceInit/0 UserServices/Registration 3 SRB_13_6K_DCH SRB_3_4K_DCH

ulUserServiceId ServiceInit/0 UserServices/Registration 3 SRB_13_6K_DCH SRB_3_4K_DCH


ServiceInit/0
dlUserServiceId 3 SRB_13_6K_DCH SRB_3_4K_DCH
UserServices/OriginatingHighPrioritySignalling
ServiceInit/0
ulUserServiceId 3 SRB_13_6K_DCH SRB_3_4K_DCH
UserServices/OriginatingHighPrioritySignalling
ServiceInit/0
dlUserServiceId 3 SRB_13_6K_DCH SRB_3_4K_DCH
UserServices/TerminatingHighPrioritySignalling
ServiceInit/0
ulUserServiceId 3 SRB_13_6K_DCH SRB_3_4K_DCH
UserServices/TerminatingHighPrioritySignalling

35
Special Events and capacity management recommendation
Radio bearer management | limit the data rates for a better utilization of the radio resources

Limit the data rates for a better utilization of the radio resources.

If the intent of the customer is to protect the CS call in a Special Event, the feature MultiRAB call
drop reduction can be activated. In RF degraded conditions, specific action with regards to the PS
portion of the call can be applied to secure the CS call.

Once the UE is considered in a Vulnerable state thanks to UL (based on SIR target) & DL (based
on DL Tx Power) measurements, the proposed setting for special event will:
Block PS RAB setups (discarding PS Paging and/or rejecting new PS RAB setup)
Release PS RABs from CS + PS RAB combination (except PS0/0 from CS + PS0/0 session)
In case RRE feature (34290) is activated, this feature allows (upon PS DL TRB RLC failure) a
controlled PS release without modification of the CS speech call state (i.e. not invoking an CS
RRE, as is the case today).

36
Special Events and capacity management recommendation
SHO mobility | limit number of RL in the active Set in a static dominant context

As most of the users are static for a special event, it is possible to apply specific settings to limit
SHO procedures (RL Add/ Delete) to reduce UL/DL signalling load on the network.

With the decrease of CpichEcN0ReportingRange1A and CpichEcN0ReportingRange1B.


Purpose is to add later a new leg when it is 3,5 dB under the primary (instead of 4,5 dB).
Remove sooner a weak leg when it is 6,5 dB under the primary (instead of 7,5 dB).

With the Weight1A/Weight1B parameters which reflect the impact of the macro diversity on
the UE received quality / level.

37
Special Events and capacity management recommendation
SHO mobility | limit number of RL in the active Set in a static dominant context

Aim is to control the number of links in the active set and reduce signalling load on the network:

Parameter Class Old Value New Value


CpichEcN0ReportingRange1A 3 4,5 dB 3,5 dB
timeToTrigger1A 3 200 ms 640 ms
CpichEcN0ReportingRange1B 3 7,5 dB 6,5 dB
timeToTrigger1D 3 640 ms 1280 ms
Weight1A 3 0 0.5
Weight1B 3 0 0.5

As illustrated in the example, Cell 1 best


Cell 2 Cell 3 Weight Resulting Value Rs
with weight parameters cell
greater than 0 it is more -15 -18 -20 1,0 -12,4
difficult to add and keep a new -15 -15 -15 1,0 -10,2
leg when there is macro
SHO margin: Reduce from 15% to 10%, thereby giving more capacity to traffic (new PowerPartConfClass/x):
diversity.

Parameter Class Old Value New Value


CallAdmissionRatio 3 85 95

38
Special Events and capacity management recommendation
Transmission capacity

With smart phone penetration all over the world, huge HS Payload increase observe across all
WCDMA network in past years. To carry User plane traffic, proper transport configuration should be
done to avoud IuB Congestion issue during the event.
D4U Can support up to 5 xCEM Board. Each CEM Boards can support up to 60 Mbps.
Based on past experience we need to have Transmission capacity >100 Mbps on each Site to
avoid any IuB Congestion issue during the event.

Once Transmission capacity is breached on IuB, Following can be observed


Packet loss Causing degradation in Throughput.
Higher packet loss can degradation in CSSR HS KPIs.
Beyond a certain limit, packet loss can cause degradation in CS KPIs too.
Once it became very high, Site will start fluctuating with frequent LOS Alarm. This can cause
instability in over all area.

39
Special Events and capacity management recommendation
Emergency setting | (No capacity planning can be done)

Specific settings to apply in case of emergency to mitigate traffic storm and ensure basic
services

Special Event
Parameter Class Normal Setting
Setting
T300 3 2s 6s
N300 3 4 1
T352 3 4s 4s
T351 3 700 800
N351 3 1 1
isQuickRepeatAllowed 3 True False
ConstantValue 3 -17 -21
powerOffsetPO 3 3 2
preambleRetransMax 3 32 15
mmax 3 8 4
maxUlInterferenceLevel 3 -50 -50
waitTimerOnRRCConnectionRejection 3 5s 0
sibMaxAllowedUlTxPowerOnRach 3 24 18
RadioAccessService/0 UlRbSetConf/PS_64K_IB
3 4 10
UlRbRaTrafficMonitoring/0 raNbOfSample
RadioAccessService/0 UlRbSetConf/PS_64K_IB_MUX
3 4 10
UlRbRaTrafficMonitoring/0 raNbOfSample
RadioAccessService/0 UlRbSetConf/PS_64K_IB_MUX3
3 4 10
UlRbRaTrafficMonitoring/0 raNbOfSample

40
Special Events and capacity management recommendation
Optimization during events and Capacity Management

During the event even after making lot of optimization changes, we may have further requirement of
optimization changes during the event.
ALU had a tool called WPS used for making optimization changes offline. Following are the
advantage
WO can be created offline with help of network snapshot.
For each WO, a reverse WO is generated which make efficient turnaround in case something
went wrong while implementation.
Impact of WO can be checked(if it requires RNC Restart, NodeB Restart or No service imapct
in WPS itself which helps in planning the implementation time.
Can be checked if there are any errors in WO which may cause WO to stuck in
implementation phase. WOs can be corrected(few with help of tools) as information regarding
which kind and where is error in WO.

41
Thanks