Professional Documents
Culture Documents
1 | INTRODUCTION
2 | FEATURE DESCRIPTION
3 | UPGRADE RULES
4 | FEATURE ACTIVATION
5 | FEATURE MONITORING
2
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
nGBR QoS Based Load Balancing
1 | INTRODUCTION
3
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Overview
Prior to LR13.3.L, load balancing was triggered based on the estimated PRB consumption across all types of
channels (SRB, TRB, control channels). The PRB consumption used to trigger load balancing was the same as
the one used for admission control, based on a calculated average PRB cost of 1kbit/s over the air interface, as
well as the actual GBR or configuration parameters ulMinBitRateForBE and dlMinBitRateForBE for the
case of non-GBR bearers. This is referred to as a semi-static PRB consumption.
Feature 171232 aims at providing a new criterion for targeting load balancing upon radio congestion, as well
as introducing enhancements to the LA5.0/LR13.1.L load balancing solution requested by customers.
Looking strictly at real PRB consumption is not enough as a few UEs can take the whole band, so there must
be some level of QoS deficit to confirm the occurrence of congestion:
• If the real PRB consumption is high but there is no QoS degradation Î No congestion
• If the real PRB consumption is high and there are signs of QoS degradation Î Congestion
• If the real PRB consumption is low Î No congestion
Feature 171232 mainly impacts the Callp eNB subsystem, with minor impact on the modem. It is applicable to
eCCM and eCCM2, as well as Metro.
This feature is aimed at being used in a multi-carrier environment, i.e. where there is more than one carrier
deployed (LTE and possibly from other RATs). It applies to both inter-frequency and inter-RAT load balancing
and may work with a multi-carrier or multi-band eNB, operate in environments where two separate eNBs are
co-located or deployed in overlapping coverage.
4
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Benefits
This feature introduces the following benefits:
• Added flexibility for non-GBR bearers admission in a cell.
- In addition to the existing criterion, this feature allows triggering of load balancing based on real/actual
PRB consumption and average QoS degradation.
- This provides customers an additional flexibility with regards to non-GBR bearers, as it makes possible
admitting a large number of non-GBR bearers in a cell (for instance by setting ulMinBitRateForBE =
dlMinBitRateForBE = 0kbit/s) whilst taking full advantage of its spectrum assets through load balancing
in periods of congestion when QoS degradation becomes visible.
• Ability to trigger load balancing based on QoS degradation in a cell.
- Allows triggering load balancing in periods of high activity, even if the calculated/semi-static PRB
consumption remains below the preventive offload threshold.
- QoS degradation is measured in terms of downlink throughput for a non-GBR.
• Increased degrees of freedom for selection of criteria used for load balancing triggering.
- Until LR13.1 only semi-static PRB consumption was used as a criteria, introduced by L115223 and
enhanced by 114538.
- From LR13.3, real PRB consumption (171232), number of connected users per cell/eNB (163172) and
number of active users per cell (166802) are also available.
5
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
nGBR QoS Based Load Balancing
2 | FEATURE DESCRIPTION
6
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Procedure Overview and Main Steps
Overall Real Average MIN_BURST_SIZE_PER_MEASPERIOD
filteringCoefficientFor
QosBasedPreventive PRB Perceived RLC MIN_BURST_TIME_PER_MEASPERIOD
Offload Consumption Throughput ACCUMULATED_BURST_SIZE_THRESHOLD
Evaluation Evaluation periodMeasForPRBConsumption
ulPreventiveLoadControlThresholdOnRealPrb
Triggering of
dlPreventiveLoadControlThresholdOnRealPrb
Load Balancing
dlBitRateThresholdForPreventiveLoadControl
isQoSBasedPreventiveLoad
ControlEnabled = True
arpThresholdForPreventiveLoadControl
isInterFreqLoadBalancing nbrOfUsersImpactedByQosBasedPreventiveOffload
UE maxNbrOfUsersImpactedByPreventiveLoadControl
FeatureEnabled = True
Selection
extraMarginNbUeSelectedPreventiveOffload
isInterFreqPreventiveLoad inactivityTimeForPreventiveOffload
ControlEnabled = True
Defence tMeasWaitForOffload
Mechanism preventiveLoadControlHysteresisTimer
Event A4 CAC_THRESHOLD_FOR_PREVENTIVE
and preventiveLoadControlHysteresisTimer
Neighbour Cell REAL_PRB_USAGE_THRESHOLD_FOR_PREVENTIVE
Filtering DL_THROUGHPUT_THRESHOLD_FOR_PREVENTIVE
7
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Overall Real PRB Consumption Evaluation
The overall real PRB consumption is calculated by Callp, based on modem reporting. The modem already
reports the PRB consumption to Callp, although this is per type of channel: traffic channels (further split into
GBR, non-GBR and VoIP), SRB and control channels.
The evaluation of the total real PRB consumption performed by Callp is done in both uplink and downlink every
time it is reported by the modem. This applies to PRB consumption per cell only. It is filtered by Callp using a
configurable filter coefficient, defined by parameter filteringCoefficientForQosBasedPreventiveOffload.
8
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Average Perceived RLC Throughput Evaluation
There is also the need to check the level of QoS degradation (if any) experienced by bearers in the last
measurement period. This is because only a single or just a few UEs may use the full PRB band, in which case
the eNB should not consider that the cell is congested. In a first step, this is only done for non-GBR bearers,
with the expectation that QoS degradation will first be visible for this type of bearers.
This is done by relying on new QoS measurements provided by the modem that will be used to estimate the
average perceived downlink RLC throughput. The downlink scheduler reports the total RLC burst size and time
(activity duration) to Callp for each non-GBR QCI, which allows calculating the average downlink RLC user
throughput per QCI. If there is no or little activity for a specific QCI during the last measurement period, this
measurement is not taken into consideration for averaging. This is based on a pre-determined minimum RLC
burst size and time (measurement is ignored if below minimum burst size and burst time). These limits are
defined using BCI parameters MIN_BURST_SIZE_PER_MEASPERIOD,
MIN_BURST_TIME_PER_MEASPERIOD and ACCUMULATED_BURST_SIZE_THRESHOLD.
The modem implementation will be based on corresponding counters introduced by feature L115928 and
broken down per QCI by feature L115627. The scheduler tracks the total burst size and time for all non-GBR
bearers as a whole. Whenever the scheduler flushes a burst and performs the PM counter pegging it also adds
the burst size and time measurement into the per-QCI metrics on the QCI of the bearer. At the end of the
measurement period (defined by parameter periodMeasForPRBConsumption) the average, per QCI, burst
size and time are reported to Callp.
The eNB must then be able to estimate the average perceived downlink RLC throughput performance for non-
GBR bearers. A low average throughput for active non-GBR bearers is a symptom of congestion in the cell and
is used as a criterion to trigger load balancing.
9
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Triggering of Load Balancing
Upon reception of a modem PRB measurement report, Callp will trigger load balancing when the following
criteria are both met:
• The real PRB consumption (ratio of PRB usage versus the total amount of available PRBs in the cell) is above
any of the configurable thresholds at cell level, defined by parameters
ulPreventiveLoadControlThresholdOnRealPrb and dlPreventiveLoadControlThresholdOnRealPrb,
respectively for uplink and downlink.
• The reported average downlink throughput is below a configurable threshold for one or many QCIs, defined
by parameter dlBitRateThresholdForPreventiveLoadControl.
The eNB does not trigger load balancing if it is in overload (CCM or CEM in which the threshold is met) or if
reactive offloading is ongoing.
10
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
UE Selection (1/2)
After triggering load balancing based on real PRB consumption and downlink user throughput, Callp must
perform a selection of the UEs for offloading.
12
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Defence Mechanism
The defence mechanism defined for feature L115223 is also applicable for load balancing based on real/actual
PRB consumption and average QoS degradation.
This means that there is a maximum allowed time for finding an inter-frequency neighbour cell, configured
through parameter tMeasWaitForOffload. After this timer elapses, event A4 is deactivated in the UEs for
which inter-frequency handover has not been triggered.
If the handover preparation fails partially or completely, load balancing will be cancelled for the UE and its
inter-frequency measurements will be deactivated.
13
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Event A4 and Neighbour Cell Filtering (1/2)
There is a need of avoiding triggering load balancing handovers towards a cell on which the load conditions
are similar or even worse than in the cell where offload is being triggered. This requires a filtering of the
neighbour cells, as done with the legacy load balancing features, but with an additional check on a minimum
delta between serving and target cell loads.
Upon reception of event A4 measurement report for preventive offload the eNB will compare the load of the
target cell with the load of the serving cell, in order to ensure there is a minimum delta between the two cells.
The eNB will then filter out neighbour cells reported by the UE for which their load level is considered similar or
higher than the cell triggering load balancing due to real PRB usage per cell and QoS deficit. This achieved
through the following method:
• For the inter-eNB case, the neighbours for which the delta between their reported composite available
capacity versus the serving cell composite available capacity is lower than a predefined threshold (BCI
parameter CAC_THRESHOLD_FOR_PREVENTIVE) will be filtered out. The target cell available capacity
needs to be higher than the serving cell. For neighbours for which the composite available capacity is not
available this check/filtering is not done, but the verifications defined by L115223 on PRB usage, S1 TNL load
and hardware load are performed.
• For the intra-eNB case, the eNB will filter out cells for which:
- The composite available capacity is lower than any of the configurable thresholds defined using
ulCellLoadedThreshold and dlCellLoadedThreshold parameters.
- If the neighbour cell is considered “not loaded” as per the previous criterion, it will be filtered out in case
preventive offload is being triggered based on any of the possible criteria. This includes the time during
which the timer preventiveLoadControlHysteresisTimer is running.
14
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Event A4 and Neighbour Cell Filtering (2/2)
• For the intra-eNB case, the eNB will filter out cells for which (cont.):
- If the neighbour cell is considered “not loaded” as per the first criterion, the neighbour cell will be filtered
out if the real PRB consumption is within a predetermined threshold of the serving cell real PRB
consumption (BCI parameter REAL_PRB_USAGE_THRESHOLD_FOR_PREVENTIVE) and the average
downlink throughput of any QCIs is within a predetermined percentage of the serving cell average
downlink throughput for that same QCI (BCI parameter
DL_THROUGHPUT_THRESHOLD_FOR_PREVENTIVE).
• If the neighbour cell load is unknown, preventive offload is not triggered to this cell, unless blind offloading is
activated.
Threshold for event A4 (neighbour cell becomes better than an absolute threshold) has to be appropriately set
for load balancing, in order to avoid ping-pong between LTE carriers or handover triggering following load
balancing.
This may happen if A4 is set too low, such that the UEs are sent to the cell edge of the underlying LTE cell.
There is also a relation between event A4 and A5 thresholds that should be observed, in order to restrain the
UEs from handing back over to the cell from they were originally offloaded.
Note that this is not specific to this feature, but also applies to other load balancing features.
15
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Interaction and Dependencies (1/3)
Some feature interaction and dependencies should be considered for feature 171232:
• L115928 – Downlink Throughput Counter Enhancements (LA5.0) and L115627 – Performance
Management Enhancements (LA6.0):
- 171232 has a dependency of both these features since they provide the framework for modem average of
downlink RLC throughput measurements that need to be reported to Callp for 171232.
- L115627 breaks down the RLC burst time and size counters per QCI.
• L101815 – Inter-frequency FDD/TDD Handover (LR13.1):
- The new load balancing trigger (QoS degradation) introduced by 171232 is also applicable to FDD/TDD
handovers. UEs that support FDD/TDD handover (FGI bit #30) are selected first for preventive offloading
when the neighbours of the serving cell include cells of the other mode.
- Although coding was performed in LR13.1 to allow FDD/TDD redirection for preventive offload, this
functionality is not yet supported by the Alcatel-Lucent eNB (as such there is no real interaction between
these features).
• L115223 – Inter-frequency Load Balancing (LA5.0):
- L115223 uses a semi-static PRB trigger for load balancing. Both functionalities/triggers may coexist, but
when load balancing is triggered once, it won’t be triggered again (whatever the trigger) during a
configurable time hysteresis.
- Upon reception of a PRB measurement report from the modem, Callp will evaluate the load balancing
triggering criteria for both L115223 and 171232.
16
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Interaction and Dependencies (2/3)
Some feature interaction and dependencies should be considered for feature 171232 (cont.):
• L114539 – Congestion Management at Call Admission (LA4.0):
- The eNB is allowed to trigger reactive offload (preemption of lower priority bearers or UEs so that the
higher priority request can be admitted) while load balancing is ongoing.
- However, preventive offload based on real PRB consumption and QoS deficit can’t be triggered when
reactive offload is ongoing.
• 163172 – Traffic Management Evolutions (LR13.3):
- 163172 introduces preventive offload based on the number of connected UEs, per cell and per eNB.
Preventive offload based on real PRB consumption and QoS deficit can’t be triggered for another criterion
until the hysteresis timer has elapsed.
- Also, 163172 introduces, per neighbour carrier, preventive offload thresholds for QoS based preventive
offload triggering. These thresholds are used when prioritization of neighbour carriers for preventive
offload is active, meaning that the parameters introduced by 171232 are overridden.
• 166802 – eNB SW Capacity (LR13.3):
- 166802 introduces preventive offload triggered by the number of active UEs per cell.
- When preventive offload is triggered for one criterion, it cannot be trigger for another condition until the
hysteresis timer expires.
17
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Interaction and Dependencies (3/3)
Some feature interaction and dependencies should be considered for feature 171232 (cont.):
• 166502 – Out of Time Alignment (LR13.3):
- Feature 171232 requires that UEs that are inactive are filtered out (for offloading) upon reception of the
A4 measurement report. Feature 166502 has a requirement to select UEs that are active (instead of in out
of timing alignment) for offloading.
- The 166502 takes precedence over the 171232 requirement, meaning that when 166502 is active, the UE
selection based on the extra margin and inactivity time is not applied and the criteria defined for 166502
are used instead.
• 155912 – Target Cell Load Considerations for IRAT to WCDMA (LR13.1):
- The new load balancing QoS degradation trigger introduced by 171232 is also applicable to IRAT load
balancing.
- This means that preventive offloading can also be performed towards UTRAN FDD macro cells that have
spare capacity.
• L115644 – Bearer Characteristics Online Modifications (LA5.0):
- Any change to ARP will be taken into consideration for future preventive offloading decisions taken by
171232.
• L92027 – UTRA-TDD/-FDD-to-EUTRA inter-RAT PS Handover (LR14.3):
- For incoming PS handover from UTRA, the eNB will start a timer in order to avoid this UE from being
selected for reactive/preventive offload straight away.
18
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
nGBR QoS Based Load Balancing
3 | UPGRADE RULES
19
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
First Upgrade Using the Feature
To ensure the same level of functionality and performance after the upgrade as before (ISO-functionality) the
following setting should be used:
• isQoSBasedPreventiveLoadControlEnabled (ENBEquipment / Enb / ActivationService) = False.
20
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
nGBR QoS Based Load Balancing
4 | FEATURE ACTIVATION
21
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Activation and Prerequisites
For activation of preventive offload based on real PRB consumption and QoS deficit, the following setting
applies: isQoSBasedPreventiveLoadControlEnabled (ENBEquipment / Enb / ActivationService) = True.
This activates feature 171232.
22
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
RAN Model
The diagram below shows the location in the RAN model of the parameters used to configure this feature:
ENBEquipment
Enb
tMeasWaitForOffload (L103892)
ActivationService LteCell
isQoSBasedPreventiveLoadControlEnabled
isInterFreqLoadBalancingFeatureEnabled (L115223)
isInterFreqPreventiveLoadControlEnabled (L115223 / L114538) RadioCacCell
ulPreventiveLoadControlThresholdOnRealPrb
dlPreventiveLoadControlThresholdOnRealPrb
periodMeasForPRBConsumption (L92091)
DedicatedConf RrmServices
TrafficRadioBearerConf RadioCacEnb
dlBitRateThresholdForPreventiveLoadControl nbrOfUsersImpactedByQosBasedPreventiveOffload
filteringCoefficientForQosBasedPreventiveOffload
extraMarginNbUeSelectedPreventiveOffload
inactivityTimeForPreventiveOffload
arpThresholdForPreventiveLoadControl (L115223)
preventiveLoadControlHysteresisTimer (L115223)
maxNbrOfUsersImpactedByPreventiveLoadControl (L115223)
23
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Configuration and Parameters (1/3)
Parameter Description Object Range and Unit Value
25
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Configuration and Parameters (3/3)
Parameter Description Object Range and Unit Value
MIN_BURST_SIZE_PER_ QoS based preventive offload may be triggered only if the report burst size for
Kbyte 1
MEASPERIOD any non-GBR traffic is above this threshold.
MIN_BURST_TIME_PER_ QoS based preventive offload may be triggered only if the report burst time for
ms 100
MEASPERIOD any non-GBR traffic is above this threshold.
QoS based preventive offload may be triggered only if the accumulated burst
ACCUMULATED_BURST_
Kbyte size for any non-GBR QCI across several continuous measurement periods is 1
SIZE_THRESHOLD
above this threshold.
Upon reception of A4 report for QoS based preventive offload, inter-eNB target
cell will be filtered out if the delta between its reported composite available
CAC_THRESHOLD_FOR_
% capacity versus the serving cell composite available capacity is lower than this 10
PREVENTIVE
threshold (target cell available capacity must be higher than the serving cell
available capacity).
Upon reception of A4 report for QoS based preventive offload, intra-eNB target
REAL_PRB_USAGE_
cell will be filtered out if the delta between its averaged real PRB consumption
THRESHOLD_FOR_ % 10
versus the serving cell is lower than this threshold (target cell real PRB
PREVENTIVE
consumption must be lower than the serving cell real PRB consumption).
Upon reception of A4 report for QoS based preventive offload, inter-eNB target
DL_THROUGHPUT_
cell will be filtered out if the delta between its downlink throughput for any non-
THRESHOLD_FOR_ % 10
GBR QCI versus the serving cell same QCI is lower than this threshold (target
PREVENTIVE
cell throughput needs to be higher than the serving cell throughput).
27
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
nGBR QoS Based Load Balancing
5 | FEATURE MONITORING
28
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Impact on Counters/Screenings (1/3)
There are no new counters or screenings introduced by feature 171232. However a different behaviour would
be expected for the following counters due to triggering of load balancing based on real/actual PRB
consumption and average QoS degradation.
For the counters listed above, screenings 3, 4 and 5 will Screening Meaning
2 ReactiveOffloadS1HO
3 PreventiveOffloadIntraENodeBHO
4 PreventiveOffloadX2HO
5 PreventiveOffloadS1HO
6 LoadEqualizationIntraENodeBHO
7 LoadEqualizationX2HO
8 LoadEqualizationS1HO
29
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Impact on Counters/Screenings (2/3)
#12890 – VS.OutgoingInterENodeBS1HOAbortPerHOReason: number of times that an outgoing inter-
eNB S1 handover procedure towards the cell has been aborted.
6 OffLoadingForPreventiveLoadControlCellNumUEs
7 OffLoadingForPreventiveLoadControlEnbNumUEs
30
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Impact on Counters/Screenings (3/3)
#12891 – VS.OffLoadingSuccess: number of times an offloading mobility of a call is successful, i.e. the UE
leaves the congested cell or the congested band or the congested eNB upon completion of an inter-frequency,
inter-RAT mobility procedure triggered for offloading reason, CSFB completion, intra-frequency mobility
triggered for radio reason or UE context release.
#12892 – VS.OffLoadingFailure: number of times an offloading mobility of a call failed, i.e. the UE does
not leave the congested cell or the congested band or the congested eNB. The reasons may be offload not
started due to MIM, UE capabilities reasons, offload timer timeout, handover preparation failure (S1, X2),
handover preparation with partial failure, interruption by another procedure that does not solve the congestion
situation.
For the counters listed above, screening 2 will consider preventive offload handovers triggered by the criteria
of 171232, as per the table below. Screenings 4, 5 and 6 are new in LR13.3, but are not introduced by this
feature.
Screening Meaning
0 ReactiveLoadControl
1 PreventiveLoadControlSemiStaticPrbTrigger
2 PreventiveLoadControlRealPrbTrigger
3 LoadEqualizationTrigger
4 PreventiveLoadControlActiveUsersPerCellTrigger
5 PreventiveLoadControlCellNumUEsTrigger
6 PreventiveLoadControlEnbNumUEsTrigger
31
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
32
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Feature Requirements
The list below includes the requirements for feature 171232:
• Improvement of PRB consumption estimation for non-GBR UEs.
• The eNB will use the real PRB consumption as a trigger for load balancing in addition to the existing trigger
(semi-static PRB consumption based on ulMinBitRateForBE and dlMinBitRateForBE parameters). This
means that “real PRB consumption” and “semi-static PRB consumption” are both triggers for load balancing.
• Load Balancing based on real PRB consumption will only be triggered if average downlink throughput of
“active” non-GBR bearers is below a given, per QCI, threshold.
• An “active” non-GBR bearer is a non-GBR bearer for which there was user plane activity (data in buffer) over
the last measurement period.
• The selection of UEs to offload should evolve to be able to select non-GBR bearers even when
ulMinBitRateForBE and dlMinBitRateForBE parameters are set to 0. The number of UEs to select should
be scaled using the throughput deficit.
• The threshold for “real PRB consumption” will be configured independently of the threshold for “semi-static
PRB consumption”.
• Threshold for average throughput of “active” non-GBR bearers on a per QCI basis.
Note that this LR13.3 feature was previously part of LR13.1 feature L114538 (EPIC#1).
33
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Offload Triggers and Feature Interaction (1/5)
The tables below go over the several thresholds used, depending on the activated features and release:
• Preventive Offload
Note that blind preventive offloading is applicable from LR13.1, with the introduction of L114538.
34
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Offload Triggers and Feature Interaction (2/5)
The tables below go over the several thresholds used, depending on the activated features and release (cont.):
• Reactive Offload
35
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Offload Triggers and Feature Interaction (3/5)
The tables below go over the several thresholds used, depending on the activated features and release (cont.):
• Load Equalization
The figures in the following slides show the interaction between the several thresholds and illustrate the
differences between the LA6.0, LR13.1, LR13.3 (without 163172) and LR13.3 (with 163172) behaviours.
36
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Offload Triggers and Feature Interaction (4/5)
LA6.0 (L115223) LA13.1 (L115223 + L114538)
37
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Offload Triggers and Feature Interaction (5/5)
LA13.3 (L115223 + L114538 + 171232) LA13.3 (L115223 + L114538 + 171232 + 163172)
38
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Example of Calculation of Number of UEs to Offload
Below, an example of the calculation of the number of UEs to be considered for offload, with two QCIs, is
presented.
If the average downlink throughput is 180kbps for QCI8 and 100kbps for QCI9, then the deficit will be:
• (200 – 180) / 200 = 20 / 200 = 10% for QCI8.
• (150 – 100) / 150 = 50 / 150 = 33.33% for QCI9.
The number of UEs targeted for load balancing will be proportional to the QoS deficit, so a larger QoS deficit
will require more UEs to be offloaded in order to get back to more acceptable QoS levels.
39
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION