05 LR13.3 ORF Workshop Proposed Validation Strategy For Load Balancing Features

Proposed Validation Strategy for Load
Balancing Features
LR13.3 Orange France Workshop
MGR TIPS / NEA / WLF

October 8th 2013
1
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Network Architecture and Environment
Load balancing features are aimed at being used in a multi-carrier environment, where there is more than one
LTE carrier deployed.
As such, the suitable environment for feature activation will be a two layered configuration that is implemented
in Orange’s network using 800Mhz (as coverage layer) and 2600Mhz (as capacity layer) frequency bands. The
figure below illustrates the configuration used.
DL EARFCN = 3000; UL EARFCN = 21000;

2600MHz (Band 7) DL Bandwidth = UL Bandwidth = n100-20MHz
DL EARFCN = 6400; UL EARFCN = 24400;

800MHz (Band 20) DL Bandwidth = UL Bandwidth = n50-10MHz
The new strategy will take into consideration the possible activation and interaction of the features listed
below, following direct upgrade from LA6.0 to LR13.3.
• L114538 – Enhanced Load Balancing Criteria (LR13.1).
• 171232 – nGBR QoS Based Load Balancing (LR13.3).
• 163172 – Traffic Management Evolution (LR13.3).
2
Current Strategy (1/2)
In the current network configuration, inter-frequency load balancing and preventive offload are activated using
feature L115223 – Inter-frequency Load Balancing.
• isInterFreqLoadBalancingFeatureEnabled (Activation Service) = True.
• isPreventiveLoadControlAllowed (ActivationService) = True.
Load balancing based on semi-static PRB consumption is enabled through the appropriate flag.
• isStaticPrbBasedPreventiveLoadControlEnabled (ActivationService) = True.
The thresholds for triggering preventive offload based on semi-static PRB consumption are quite low. This is
related to the low traffic served and to try and perform some early balancing of traffic, aiming at replicating
the effect of a load equalization, that is not available in the LA6.0 release.
• dlPreventiveLoadControlThresholdOnPrb (RadioCacCell) = 15%.
• ulPreventiveLoadControlThresholdOnPrb (RadioCacCell) = 20%.
In case of inter-eNB load balancing, the eNB evaluates the status of a neighbour cell based on the X2 load
exchange and this cell will be considered as not loaded, if the composite available capacity is higher than 40%.
The capacity class considered in the composite available capacity calculation corresponds to a macro cell.
• dlCellLoadedThreshold (Enb) = 40%.
• ulCellLoadedThreshold (Enb) = 40%.
• cellCapacityClass (RadioCacCell) = 100%.
3
Current Strategy (2/2)
When PRB consumption is higher than 90%, reactive offloading is triggered for the neighbouring carrier. With
these settings this procedure is almost never triggered.
• dlAdmissionThresholdOnPrb (RadioCacCell) = 90%.
• ulAdmissionThresholdOnPrb (RadioCacCell) = 90%.
There is no limit on the number of UEs that can be offloaded by the preventive offload procedure.
• maxNbrOfUsersImpactedByPreventiveLoadControl (RadioCacEnb) = <unset>.
All UEs, independently of their ARP, can be selected for offload. The selection is done from the highest ARP
level (lower priority) to the lowest ARP level (higher priority).
• arpThresholdForPreventiveLoadControl (RadioCacEnb) = 1.
The defence mechanism defines a maximum allowed time for finding an inter-frequency neighbour cell of 2
seconds. In order not to trigger load balancing too often, an hysteresis timer of 3 seconds is used, during
which no other load balancing procedure can’t be started (independently of the criterion).
• preventiveLoadControlHysteresisTimer (RadioCacEnb) = 3000ms.
• tMeasWaitForOffload (Enb) = 2000ms.
The execution phase of the offloading, following selection of the UE, involves the configuration of Event A4.
After the neighbour cell RSRP is measured higher than -100dBm, the UE sends a MEASUREMENT REPORT to
the eNB.
• thresholdEutraRsrp (ReportConfigEUTRA – Event A4) = -100dBm.
4
Possible Challenges for Load Balancing (1/3)
During L115223 feature validation it was seen that the distribution of users between 800MHz and 2600MHz
layers was not balanced.
There are some aspects that justify this uneven distribution:

• Some UEs do not support the 2600MHz frequency band (iPhone 5, for instance) which also contributes to the
higher number of RRC CONNECTION REQUEST messages received from the UE in the 800MHz band. Existing
counters do not provide information on UE capabilities, so it would be beneficial to obtain this information from
the customer, to understand the potential load that can be transferred to the 2600MHz layer.
• Effectiveness of load balancing from 800MHz to 2600MHz is limited, mainly due to the different coverage
provided by these layers, which is aggravated by the settings used in idle mode and RSRP thresholds for event
A4.
5
Indicator data analysis shows that numerous times a UE in the 800MHz cell is not even reporting event A4,
meaning that it is not able to find a suitable 2600MHz cell fulfilling the -100dBm threshold.
This is expected if the load balancing procedure is happening at cell edge, which is likely the case, taking into
consideration the idle mode strategy and associated parameters.
Parameter 800MHz 2600MHz 2600MHz

qRxLevMin (SIB1) -130 -130
qRxLevMin (SIB5) -126 -126
threshXHigh 14 Not relevant 800MHz

sNonIntraSearch 10 14
Cell reselection favours 2600MHz layer
threshServingLow Not relevant 4
Preventive offload from 800MHz to 2600MHz
cellReselectionPriority (SIB1) 4 5 layer (mainly occurring at cell edge)
Preventive offload from 2600MHz to 800MHz
cellReselectionPriority (SIB5) 5 4
layer (hardly happening due to low traffic)
From the values in the table, inter-frequency cell reselection will happen at the following RSRP values:
• 800MHz Î 2600MHz when RSRP2600 = [qRxLevMin (SIB5) + thresXHigh]800 > -112dBm.
• 2600MHz Î 800MHz when RSRP2600 = [qRxLevMin (SIB1) + sNonIntraSearch]2600 < -116dBm(this is
actually the condition for UE starting inter-frequency measurements when camped in the 2600MHz cell, but at
this stage the RSRP level measured for 800MHz should be higher anyway).
6
Considering the previous values, load balancing from 800MHz to 2600MHz layer will rarely take place, because
all UEs that have a RSRP higher than -112dBm on 2600MHz are already on this layer in idle mode. So, there is
almost no chance of reaching the desired -100dBm threshold for inter-frequency handover from 800MHz to
2600MHz.
Possible RSRP range for load

balancing from 800MHz to 2600MHz Reselection from 2600Mhz
to 800MHz when
RSRP2600 < -116dBm
-95 -100 -105 -110 -115 -120

2600MHz (Band 7)
RSRP
-85 -90 -95 -100 -105 -110

800MHz (Band 20) RSRP
Load Balancing from Reselection from 800Mhz

800MHz to 2600MHz when to 2600MHz when
RSRP2600 > -100dBm RSRP2600 > -112dBm
Handover from 2600Mhz

to 800MHz when
RSRP2600 < -115dBm
7
Selection of Load Balancing Strategy in LR13.3
The table below lists the available features in LR13.3 and their main impacts on load balancing procedures.
The selected criteria is marked in green.
Feature Load Balancing Effect Decision
Considering the low traffic and the thresholds that are currently
In addition to the load balancing implementation of
used for preventive offload it would be difficult to achieve a
L115223, allows load equalization triggering and
L114538 status of load imbalance between the two LTE carriers, in order
inter-frequency preventive offloading without
to properly manage load equalization and avoid ping-pong
neighbour load information.
between carriers.
A sensible approach would be setting the real PRB consumption

Allows triggering of load balancing based on thresholds to the same values as the semi-static PRB
171232 real/actual PRB consumption and average QoS consumption ones. However the definition of the thresholds
degradation of non-GBR bearers. using monitoring data would not be as intuitive as the number of
connected users, especially in a low loaded network.
Allows prioritization of neighbour carriers for Balancing of load based on preventive offload with prioritization
preventive offload, defining up to four different sets of neighbour carriers is not so relevant, because there are only 2
163172 of preventive offload thresholds, where each set of LTE carriers deployed. It would still be possible to activate it, as
(Epic 1) per carrier load thresholds can include semi- the WCDMA system is available for offload, but not really a
static/real PRB consumption or number of rational solution as the legacy system is likely more loaded than
connected UEs per cell/eNB. the LTE one.
Allows triggering load balancing based on the In terms of consistency with CAC settings there is not a critical
number of connected UEs per cell or number of choice between the criteria based on the number of users and
163172
connected UEs per eNB in addition to the existing PRB consumption. However, the number of users criterion is
(Epic 3)
semi-static/real PRB consumption and non-GBR easier to monitor and define suitable thresholds, so it is the
downlink throughput. selected criterion for LR13.3 load balancing.
8
Proposed Strategy (1/3)
Considering the contents of the previous slide, the preventive offload strategy will be based on feature 163172
(Epic 3), with the number of connected users per cell and eNB as the sole criterion for triggering load
balancing.
Load balancing and preventive offload are activated using feature L115223 – Inter-frequency Load Balancing
so, although the semi-static PRB consumption condition won’t be used, it is still necessary activating the load
balancing functionality of this feature.
• isInterFreqLoadBalancingFeatureEnabled (Activation Service) = True.
Activation of inter-frequency preventive offload is still required. The activation flag, originally associated to
feature L115223, has been renamed in LR13.1, following the introduction of feature L114538.
• isInterFreqPreventiveLoadControlEnabled (ActivationService) = True.
Preventive offload based on real PRB consumption and QoS (throughput) deficit of non-GBR bearers will be
disabled. This is done by keeping feature 171232 deactivated.
• isQoSBasedPreventiveLoadControlEnabled (ActivationService) = False.
Load balancing based on semi-static PRB consumption will be disabled through the appropriate flag. As such,
the current thresholds (for which the parameters have been renamed) can be left with the same values.
• isStaticPrbBasedPreventiveLoadControlEnabled (ActivationService) = False.
• dlPreventiveLoadControlThresholdOnPrb (RadioCacCell) = 15%.
• ulPreventiveLoadControlThresholdOnPrb (RadioCacCell) = 20%.
9
The load condition for triggering preventive offload will be based on the number of connected UEs so the flag
corresponding to 163172 Epic 3 will have to be enabled. The thresholds for triggering load balancing will be
defined based on monitoring results prior to validation. They correspond to a percentage of the maximum
number of connected users that can be admitted on the cell and eNB, 800 and 1200, respectively (for n50-
10MHz and n100-20MHz, in LR13.3 using bCEM).
• isNumUeBasedPreventiveLoadControlEnabled (ActivationService) = True.
• cellNbrOfUsersLoadControlThreshold (RadioCacCell) = TBD.
• enbNbrOfUsersLoadControlThreshold (RadioCacEnb) = TBD.
The functionalities of feature L114538 won’t be activated, meaning that the flags controlling load equalisation,
FDD/TDD redirection and blind inter-frequency preventive offloading disabled. Other parameters related to
load equalization will be kept with their default values, as they are irrelevant.
• isLoadEqualizationEnabled (LteNeighboringFreqConf) = False.
• ulAdmissionThresholdOnPrb (ActivationService) = False.
• spare15 bit 0 (Enb) = 0.
• thresholdRelativePreventiveOffload (RadioCacEnb) = 10%.
• loadEqualizationDeltaThreshold (RadioCacCell) = 0%.
Balancing of load based on preventive offload with prioritization of neighbour carriers, corresponding to
163172 Epic 1 will be disabled.
• isPerNeighborCarrierLoadControlEnabled (ActivationService) = False.
10
Remaining parameters already used in the current configuration will keep the same values.
• dlAdmissionThresholdOnPrb (RadioCacCell) = 90%.
• ulAdmissionThresholdOnPrb (RadioCacCell) = 90%.
• dlCellLoadedThreshold (Enb) = 40%.
• ulCellLoadedThreshold (Enb) = 40%.
• cellCapacityClass (RadioCacCell) = 100%.
• maxNbrOfUsersImpactedByPreventiveLoadControl (RadioCacEnb) = <unset>.
• arpThresholdForPreventiveLoadControl (RadioCacEnb) = 1.
• preventiveLoadControlHysteresisTimer (RadioCacEnb) = 3000ms.
• tMeasWaitForOffload (Enb) = 2000ms.
• thresholdEutraRsrp (ReportConfigEUTRA – Event A4) = -100dBm.
11
Preventive and Reactive Offload Triggers
Preventive Offload Reactive Offload
12
Conclusions
The proposed validation strategy for load balancing in LR13.3 will be based on the number of connected users
per cell and eNB criteria, for which monitoring and thresholds definition are easier and more intuitive.
The objective is to optimise the validation efforts in live network in order to focus on the most promising
option for load balancing.
The load balancing procedure would be more suitable for offloading traffic from 2600MHz layer if it was more
loaded than the 800MHz layer. However, this is not the case due to weaker coverage (especially indoor) and
also because RSRP thresholds for handover from 2600MHz to 800MHz are relatively high, not forgetting the
limitation of some UEs in terms of 2600MHz band support.
Having 2600MHz preferred in cell reselection is somehow mandatory at this stage because there is an
important part of the UEs not supporting this frequency band. So, the only way to minimally fill this layer is to
force all other UEs to camp on it.
In view of the challenges posed in terms of coverage and UE capabilities, it is not expected to perceive a major
difference in traffic balancing and preventive offloading efficiency compared to the semi-static PRB
consumption based LA6 solution, unless 2600MHz coverage is modified and penetration of 2600MHz capable
UEs evolves.
13
14
Step-by-step Behaviour Comparison (1/5)
Criteria for LA6.0:
Triggering
Load Preventive offload is triggered based on the (estimated) semi-static PRB consumption
Balancing
across all types of channels.
For non-GBR bearers, the estimated PRB consumption is calculated partly using
Triggering of configuration parameters defining the UL and DL bit rates that radio CAC assumes for a
Load Balancing best-effort radio bearer (ulMinBitRateForBE and dlMinBitRateForBE).
LR13.3:
UE
The current criterion won’t be used, as the number of users per cell and eNB will be
Selection
considered instead as the condition for triggering preventive offload.
Defence
Mechanism
Event A4
and
Neighbour Cell
Filtering
15
Criteria for LA6.0:
Triggering
Load Preventive offloading is triggered when the estimated PRB consumption either in UL or
Balancing
DL is higher than ulPreventiveLoadControlThresholdOnPrb or
dlPreventiveLoadControlThresholdOnPrb, respectively.
Triggering of
Load Balancing LR13.3:
Preventive offloading is triggered when the number of users per cell or eNB is higher
than cellNbrOfUsersLoadControlThreshold or
enbNbrOfUsersLoadControlThreshold, respectively.
UE
Selection
The number of connected UEs per eNB threshold is included because the eNB capacity
limit may be hit before the individual cell capacity limits are reached, especially when
there are 6 or more cells per eNB.
Defence
Mechanism
Event A4
and
Neighbour Cell
Filtering
16
Criteria for LA6.0:
Triggering
Load The UEs must support inter-frequency handover, event A4 and the carrier of at least one
Balancing
configured LTE neighbour. The aggregate priority must be higher than or equal to the
one defined by arpThresholdForPreventiveLoadControl. The UE is not in an
ongoing procedure, including release, handover, CCO, CSFB and ANR.
Triggering of
Load Balancing The total amount of offloaded UEs will never exceed the configured maximum that is
defined by maxNbrOfUsersImpactedByPreventiveLoadControl.
LR13.3:
UE
Selection
When the criterion for preventive offloading is the number of UEs per cell or per eNB,
the UE selection logic is the same as for PRB load criterion.
As such, the UE selection conditions defined for feature L115223 are also applicable for
Defence load balancing based on number of connected users per cell or eNB implemented by
Mechanism 163172 Epic 3.
Event A4
and
Neighbour Cell
Filtering
17
Criteria for LA6.0:
Triggering
Load There is a maximum allowed time for finding an inter-frequency neighbour cell,
Balancing
configured through parameter tMeasWaitForOffload. After this timer elapses, event
A4 is deactivated in the UEs for which inter-frequency handover has not been triggered.
Triggering of An hysteresis timer, defined by parameter preventiveLoadControlHysteresisTimer,

Load Balancing will also apply to avoid triggering load balancing too often. This applies to all types of
load balancing, so if another load balancing procedure has been triggered,
independently of the triggering cause, no further preventive offload procedures may be
started.
UE
Selection
LR13.3:
The defence mechanism defined for feature L115223 is also applicable for load
balancing based on number of connected users per cell or eNB implemented by 163172
Defence Epic 3.
Mechanism
Event A4
and
Neighbour Cell
Filtering
18
Criteria for LA6.0:
Triggering
Load Load filtering is introduced for preventive load control and it is applicable to neighbour
Balancing
LTE carriers, used for selection of unloaded carriers and target cells. To pass this filter,
at least one cell of a neighbour LTE carrier can’t be “loaded” (it must be either “not
loaded” or with “load unknown”). The available capacity that defines the load status of a
Triggering of cell is calculated using parameter cellCapacityClass and compared against thresholds
Load Balancing ulCellLoadedThreshold and dlCellLoadedThreshold.
LR13.3:
UE
Selection Since features L114538 and 171232 won’t be activated, the additional filtering done on
neighbours based on the composite available capacity delta between source and target
cells won’t be used.
This means that there is no criteria on the relative load of source and target cells, so the
Defence neighbour cell filtering will be strictly based on the load level of the neighbour LTE
Mechanism
carrier, as currently done.
Event A4
and
Neighbour Cell
Filtering
19

05 LR13.3 ORF Workshop Proposed Validation Strategy For Load Balancing Features

Uploaded by

Document Information

Original Title

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

05 LR13.3 ORF Workshop Proposed Validation Strategy For Load Balancing Features

Uploaded by

Copyright:

Available Formats

Proposed Validation Strategy for Load

MGR TIPS / NEA / WLF

DL EARFCN = 3000; UL EARFCN = 21000;

DL EARFCN = 6400; UL EARFCN = 24400;

There are some aspects that justify this uneven distribution:

Parameter 800MHz 2600MHz 2600MHz

qRxLevMin (SIB5) -126 -126

threshXHigh 14 Not relevant 800MHz

Possible RSRP range for load

-95 -100 -105 -110 -115 -120

-85 -90 -95 -100 -105 -110

Load Balancing from Reselection from 800Mhz

Handover from 2600Mhz

Feature Load Balancing Effect Decision

A sensible approach would be setting the real PRB consumption

Triggering of An hysteresis timer, defined by parameter preventiveLoadControlHysteresisTimer,

You might also like