Fastlink IRAQ LR13.3 - 2ndcarrier - LoadBalance - Introduction Ed1.1

FASTLINK-IRAQ
DUAL CARRIER FEATURE INTRODUCTION “LR13.3”

ALU RF Team
29th Jan 2014
COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

AGENDA
Introduction
LTE Inter-frequency Cell Reselection
LTE Inter-frequency Handover
Load balancing features
Conclusion
Conclusion
3
INTRODUCTION
DUAL CARRIER
• As a result of traffic growth in Fastlink network, increased capacity and offloading is

considered through the 2nd carrier approach
• the second carrier is proposed with:
- 10 MHz carrier bandwidth adjacent to the original 20MHz.
- No Guard band required.
• Alcatel-Lucent’s Dual carrier feature is implemented in LR13.3 using:
- 1 extra bCEM to handle the second carrier 3 cells in the same BBU (alongside the original 20MHz
Carrier bCEM)
- 3 RRHs
- 3 Antennas
• The presentation purpose is to showcase dual functionality and features associated with
the Dual carrier in LR13.3 such as Selection, Reselection , Mobility and load balancing.
4
AGENDA
Introduction
Conclusion
Conclusion
5
THEORY
RESELECTION SUMMARY
6
THEORY
RESELECTION SUMMARY
7
FIELD RESULTS
RESELECTION - PARAMETER SETTINGS
Parameter Value
1 isInterfrequencyEutraSameFrameStructureMobilityAllowed TRUE
2 cellReselectionPriority (High) 4
3 cellReselectionPriority (Low) 3
4 threshServingLow (dB) 10
5 threshXhigh (dB) 20
6 threshXLow (dB) 0
7 qRxLevMin (dBm) -120
8 tReselectionEUTRAN (S) 2
9 sIntraSearch (dB) 62
10 sNonIntraSearch (dB) 20
8
FIELD RESULTS
RESELECTION EQUAL PRIORITY/INTRA ENB
1.SIB3 message
9
FIELD RESULTS
SIB3
10
FIELD RESULTS
1.SIB5 message
11
FIELD RESULTS
Reselection to intra freq

And SIB5 for 2nd carrier
12
FIELD RESULTS
Cell reselection to 2nd carrier

Phys cell Id=1
13
FIELD RESULTS
RESELECTION TO HIGH PRIORITY/INTER ENB
14
FIELD RESULTS
3.Reselection to lower priority cell
15
FIELD RESULTS
16
FIELD RESULTS
Reselection to high
priority carrier F2
17
AGENDA
Introduction
Conclusion
Conclusion
18
THEORY
HANDOVER EVENTS SUMMARY
UE measurement report trigger types supported in eNB:

• Event A1 – UE sends measurement reports when serving is better than a threshold value.
• Event A2 – UE sends measurement reports when serving is worse than a threshold value.
• Event A3 – UE sends measurement reports when neighbor becomes offset better than serving.
it is used to trigger intra-frequencyuency HO and inter-frequencyuency redirection/HO if UE does not support event A5 configuration.
• Event A4 – UE sends measurement reports when neighbor becomes better than a threshold.
• Event A5 – UE sends measurement reports when serving becomes worse than threshold1
and neighbor becomes better than threshold2.
It is used to trigger inter-frequencyuency redirection/HO and intra-frequencyuency with ANR.
• Event B1 – UE sends measurement report when Inter-RAT neighbor becomes better than
Threshold.
• Event B2 – UE sends measurement report when serving becomes worse than threshold1
and inter-RAT neighbor becomes better than threshold2.
19
THEORY
HANDOVER EVENTS SUMMARY
20
FIELD RESULTS
HANDOVER - PARAMETER SETTINGS
# Parameter Value
1 isInterfrequencyEutraSameFrameStructureMobilityAllowed TRUE
2 isMeasurementGapsAllowed TRUE
3 ReportConfigEUTRA::thresholdEutraRsrp (Event A2 Coverage Alarm f1) -98
5 ReportConfigEUTRA::thresholdEutraRsrp (Event A2 Below Serving Floor) -118
21
FIELD RESULTS
INTER-FREQUENCY HO BASED ON EVENT A3
22
FIELD RESULTS
23
FIELD RESULTS
24
FIELD RESULTS
Add
A1 EVENT 3050
A3 EVENT 2900
25
FIELD RESULTS
26
FIELD RESULTS
27
FIELD RESULTS
28
FIELD RESULTS
29
KPI RESULTS
TRAFFIC
Traffic_Volume_DL(Gbyte)
300.00 272
264
248 241 247
238 234
250.00
211 213
197
186 188
200.00 180 174 171
143
150.00 128
87
100.00
50.00
0.00
Domeez04_2 Domeez04_4 Total traffic(Domeez04_2 and Domeez04_4)
Overall Total traffic have increased as result of 2nd carrier cell
30
KPI RESULTS
# OF USERS
Max RRC Connected Users

700.00
600
600.00
506 508
500.00 457
411 414
391 393 384
367 350 354
400.00
No Unit
333 343 331 336

320
300.00 261
200.00
100.00
0.00
Domeez04_2 Domeez04_4 Total RRC connected users (Domeez04_2 and Domeez04_4)
Total RRC connected users have increased as result of 2nd carrier cell
31
KPI RESULTS
PRB UTILIZATION(%)
DL PRB utilization(%)
80%
69.22%
70% 61.80% 60.98% 60.87%
60.29%
58.18% 57.03% 57.82%
55.53%
60% 53.36%
47.72% 49.21% 48.71% 47.89%
50% 43.34% 44.07%
38.11%
40%
29.92%
30%
20%
10%
0%
Domeez04_2 Domeez04_4
Offloading towards 2nd carrier and hence PRBs consumption was reduced.
2nd carrier utilization is considering 10Mhz BW (50PRBs only)
32
KPI RESULTS
PRB UTILIZATION (%)
PRB Utilization BH (%)

90%
100%
96% 97% 97%
95% 95%
93%
95%
93%
80%
95% 94% 95% 94%
95%
94%
93% 70%
90%
77%
90%
89% 89% 60%
90% 74% 60%
50%
%
%
53%
85% 50%
48%
50%
40%
40%
80% 30%
20%
75%
10%
70% 0%
0% 0% 0% 0% 0% 0% 0% 0% 0% 0%
Offloading towards 2nd carrier and hence PRBs consumption was reduced.
2nd carrier utilization is considering 10Mhz BW (50PRBs only)
33
KPI RESULTS
DL Max throughput(Mbps)
Max DL Throughput(Mbps)
70
60
50
Mbps
40
30
20
10
0
2nd carrier reaching Max cell thrpt ~50Mbps reflecting majority of users are in good
radio conditions.
34
AGENDA
Introduction
Conclusion
Conclusion
35
ENHANCED LOAD BALANCING
OFFLOADING MECHANISM
•Step 1: Load equalization threshold is reached:

 Compare the load of the target with the load of the serving  decide to invoke or not
offloading;
 Select the UEs to offload;
 Trigger load equalization offloading.
•Step 2: Preventive offload threshold is reached:
 Compare the load of the target with the load of the serving (note that the delta for
preventive is in the code)  decide to invoke or not offloading;
 Select the UEs to offload;
 Trigger preventive offloading.
The main difference between load equalization & preventive offloading:
 starting earlier for load equalization
 customer can decide to monitor only certain carriers for load equalization
36
THEORY
In addition to LA6 load balancing implementation. The enhanced LoB feature brings the following
benefits:
 Possibility to equalize load between two LTE carriers early when there is a large load difference,
resulting in better usage of spectrum resources;
 Possibility to perform blind preventive offload, i.e. offloading towards a cell for which no load
information is available (e.g. because there is no X2 link);
 Avoid the ping-pong effect between the two bands that can appear when the load on both bands
exceeds the threshold and the UE is offloaded between bands - by introducing parameter
ThresholdRelativePreventiveOffload (now offloading based on load equalization will only be triggered
when the load delta between target and serving cell is above this threshold);
 Filtering out neighbors with similar load – due to parameter ThresholdRelativePreventiveOffload, cells
with similar load as the serving one will not be taken into account as a possible candidate for offloading
based on load equalization.
37
THEORY
• Preventive Load Control

will be triggered if PRB
usage falls in the “yellow”
region.
<xx> PreventiveLoadControlThresholdOnStaticPrb • Radio CAC will select
Rejection or reactive enough UEs to offload to
load control may
appear stay in the “green” region.
<xx> PreventiveLoadControlThresholdOnStaticPrb – LoadEqualizationDeltaThreshold

 load equalization triggered
38
MAIN PARAMETERS AND FLAGS
Parameter Value
isInterFreqLoadBalancingFeatureEnabled TRUE
isInterFreqPreventiveLoadControlEnabled TRUE
isQoSBasedPreventiveLoadControlEnabled FALSE
Feature activation Flags isNumUeBasedPreventiveLoadControlEnabled FALSE
isOffloadUponReactiveLoadControlAllowed TRUE
spare15 (bit0) 1
isPerNeighborCarrierLoadControlEnabled FALSE
A4 Threshold Domeez04_2 thresholdEutraRsrp (ReportConfigEUTRA – Event A4) //-87 (for F2 not F1)
A4 Threshold Domeez04_4 thresholdEutraRsrp (ReportConfigEUTRA – Event A4) //-93 (for F1 not F2)
Action outgoingMobility
isPviAndPciBypassForReactiveOffloadEnabled FALSE
arpThresholdForPreventiveLoadControl 1
Main Parameters cellcapacityclass 100%
isNonGbrPrbCacEnabled TRUE
maxNbrOfUsersImpactedByReactiveLoadControl unset
maxNbrOfUsersImpactedByPreventiveLoadControl unset
periodMeasForPRBConsumption 1
preventiveLoadControlHysteresisTimer 3000
Offloading timers tMeasWaitForOffload 2000
inactivityTimeForPreventiveOffload 10
ueTimerNoOffload 1000
39
ENHANCED LOAD BALANCING-load equalization
PARAMETERS AND ACTIONS TAKEN
Parameter Name Implemented Action1 Action2 Action3 Action4

isStaticPrbBasedPreventiveLoadControlEnabled TRUE TRUE TRUE TRUE TRUE
isLoadEqualizationEnabled TRUE TRUE TRUE TRUE TRUE
eNB Level: isReactiveLoadControlAllowed TRUE TRUE TRUE TRUE TRUE
Doomez04 dlCellLoadedThreshold 15% 15% 15% 15% 15%
UlCellLoadedThreshold 15% 15% 15% 15% 15%
ulPreventiveLoadControlThresholdOnStaticPrb 25% 25% 50% 50% 50%
dlPreventiveLoadControlThresholdOnStaticPrb 25% 25% 50% 50% 50%
LoadEqualizationDeltaThreshold 15% 5% 5% 5% 5%
Domeez04_2 dlMinBitRateForBE 66 66 66 66 66
ulMinBitRateForBE 66 66 66 66 66
dlAdmissionThresholdOnPrb 90% 90% 90% 90% 90%
ulAdmissionThresholdOnPrb 90% 90% 90% 90% 90%
ulPreventiveLoadControlThresholdOnStaticPrb 70% 70% 70% 70% 80%
dlPreventiveLoadControlThresholdOnStaticPrb 70% 70% 70% 70% 80%
LoadEqualizationDeltaThreshold 20% 20% 20% 20% 10%
Domeez04_4 dlMinBitRateForBE 11 11 11 33 33
ulMinBitRateForBE 11 11 11 33 33
dlAdmissionThresholdOnPrb 90% 90% 90% 90% 90%
ulAdmissionThresholdOnPrb 90% 90% 90% 90% 90%
40
30.00
60.00
90.00
0.00
120.00
150.00
180.00
210.00
240.00
270.00
300.00
12/23/2014 00:00
12/23/2014 00:45
12/23/2014 01:30
12/23/2014 02:15
12/23/2014 03:00
12/23/2014 03:45
KPIS RESULTS
12/23/2014 04:30
12/23/2014 05:15
12/23/2014 06:00
12/23/2014 06:45
12/23/2014 07:30
12/23/2014 08:15 Implementation
12/23/2014 09:00
12/23/2014 09:45
12/23/2014 10:30
12/23/2014 11:15
A1
12/23/2014 12:00
12/23/2014 12:45
A2
12/23/2014 13:30
12/23/2014 14:15
12/23/2014 15:00
12/23/2014 15:45
12/23/2014 16:30
12/23/2014 17:15
12/23/2014 18:00
A3
Domeez04_2
12/23/2014 18:45
41
12/23/2014 19:30
12/23/2014 20:15
12/23/2014 21:00
12/23/2014 21:45
12/23/2014 22:30
12/23/2014 23:15
12/24/2014 00:00
RRC connected Users

12/24/2014 00:45
Domeez04_4
ENHANCED LOAD BALANCING-load equalization
12/24/2014 01:30
12/24/2014 02:15
12/24/2014 03:00
12/24/2014 03:45
12/24/2014 04:30
12/24/2014 05:15
12/24/2014 06:00
approximately equal after A4 parameter tuning
12/24/2014 06:45
12/24/2014 07:30
F1 users are almost double F2 users
12/24/2014 08:15
12/24/2014 09:00
A4
12/24/2014 09:45
12/24/2014 10:30
12/24/2014 11:15
12/24/2014 12:00
12/24/2014 12:45
12/24/2014 13:30
12/24/2014 14:15
F1 and F2
12/24/2014 15:00
Max RRC Connected Users on 2 carriers are within 2:1 after A3 Parameters tuning and
12/24/2014 15:45
Users almost same at
12/24/2014 16:30
ENHANCED LOAD BALANCING-SEMI STATIC PRB LOAD BALANCE
PARAMETERS
Parameter Name Action_1 Action_2

dlCellLoadedThreshold 15% 32%
eNB Level: Doomez04
UlCellLoadedThreshold 15% 15%
dlMinBitRateForBE 66 170
dlPreventiveLoadControlThresholdOnStaticPrb 80% 68%
Doomez04_2
ulMinBitRateForBE 66 20
ulPreventiveLoadControlThresholdOnStaticPrb 80% 80%
UlMinBitRateForBE 33 20
ulPreventiveLoadControlThresholdOnStaticPrb 55% 80%
Doomez04_4
dlMinBitRateForBE 33 76
dlPreventiveLoadControlThresholdOnStaticPrb 55% 25%
42
ENHANCED LOAD BALANCING-SEMI STATIC PRB LOAD BALANCE
KPIS RESULTS
Max RRC connected Users

Load balance based on semi static PRB_Utilization
500.00 120%
450.00
103% Parameter tuning to achieve 2:1
98% 96% 96%
100%
400.00 83%
80%
350.00
74%
80%
66%
300.00
No Unit
250.00 60%
46% 43% 43%
41% 43% 41%
200.00
40%
150.00
100.00
20%
50.00
0.00 0%
Domeez04_2 Domeez04_4 (RRC_Connected_Users_F2)/RRC_Connected_User_F1)(%)
Max RRC Connected Users between 2 carriers are within 2:1 after iterative Parameters tuning
43
NGBR QOS BASED LOAD BALANCING
THEORY
Prior to LR13.3.L, load balancing was triggered based on semi-static PRB consumption.
New LR13.3 feature aims at providing new criteria for targeting load balancing based on Real PRB
consumption addition to QoS degradation.
load balancing based ONLY on 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
- f the real PRB consumption is high and there are signs of QoS degradation  Congestion
- If the real PRB consumption is low  No congestion
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.
44
THEORY Average MIN_BURST_SIZE_PER_MEASPERIOD
Overall Real PRB
Perceived RLC MIN_BURST_TIME_PER_MEASPERIOD
Consumption ACCUMULATED_BURST_SIZE_THRESHOLD
Throughput
Evaluation periodMeasForPRBConsumption
Evaluation
filteringCoefficientFor
QosBasedPreventive
Offload
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
45
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
PARAMETERS
Parameter Real_PRB_activation Real_PRB_A1 Real_PRB_A2
isInterFreqLoadBalancingFeatureEnabled TRUE TRUE TRUE
isInterFreqPreventiveLoadControlEnabled TRUE TRUE TRUE
isStaticPrbBasedPreventiveLoadControlEnabled FALSE FALSE FALSE
isLoadEqualizationEnabled FALSE FALSE FALSE
isQoSBasedPreventiveLoadControlEnabled TRUE TRUE TRUE
isNumUeBasedPreventiveLoadControlEnabled FALSE FALSE FALSE
isOffloadUponReactiveLoadControlAllowed TRUE TRUE TRUE
eNB Level: isReactiveLoadControlAllowed TRUE TRUE TRUE
Doomez04 spare15 (bit0) 1 1 1
isPerNeighborCarrierLoadControlEnabled FALSE FALSE FALSE
dlBitRateThresholdForPreventiveLoadControl 500 500 150
filteringCoefficientForQosBasedPreventiveOffload 0.8 0.8 0.8
nbrOfUsersImpactedByQosBasedPreventiveOffload 5 5 5
extraMarginNbUeSelectedPreventiveOffload 50 50 50
dlCellLoadedThreshold 15% 32% 32%
UlCellLoadedThreshold 15% 15% 15%
Domeez04_2 ulPreventiveLoadControlThresholdOnRealPrb 85% 85% 85%
dlPreventiveLoadControlThresholdOnRealPrb 80% 80% 90%
ulPreventiveLoadControlThresholdOnRealPrb 85% 85% 85%
Domeez04_4
dlPreventiveLoadControlThresholdOnRealPrb 80% 40% 44%
46
KPIS RESULT
Domeez04_PRB_Utilization
60.00% 90.00%
81.57%
75.33% 80.00%
50.00% 68.09%
62.07% 70.00%
60.78% 60.13% 59.64%
57.98%
40.00% 55.19% 54.62% 53.62% 53.74% 60.00%
52.61%
45.17% 50.00%
30.00% 40.29%
40.00%
20.00% 30.00%
Real PRB offloading Real PRB offloading
Real PRB offloading
Parameter tuning A1 Parameter tuning A2 20.00%
10.00% Activation
10.00%
0.00% 0.00%
_PRB_average_Utilization_F1(Domeez04_2)(%) _PRB_average_Utilization_F2(Domeez04_4)(%) Ratio F2:F1
PRB utilization between 2 carriers are maintained within 2:1 after iterative Parameters tuning
47
TRAFFIC MANAGEMENT EVOLUTION
THEORY
Rationale: Prior to this feature, preventive load balance was only based on
estimated PRB consumption or real PRB consumption and non-GBR
downlink throughput.
Number of UE as criterion for Load Balancing: this feature adds a new load
criteria's for load balancing decision allowing customers to trigger load
balancing based on number of connected UEs per cell or number of
connected UEs per eNB.
If ActivationService::isNumUeBasedPreventiveLoadControlEnabled = True,
then the thresholds RadioCacCell:: cellNbrOfUsersLoadControlThreshold or
PreventiveOffload::cellNbrOfUsersLoadControlThreshold (depending or not
on Prioritization of neighbor carriers activation),
RadioCacEnb::enbNbrOfUsersLoadControlThreshold apply to preventive
offload to both intra-LTE and IRAT UTRAN-FDD.
Observation: RadioCacCell::cellNbrOfUsersLoadControlThreshold is used if
RadioCacCell::isPerNeighborCarrierLoadControlEnabled = False, and
PreventiveOffload::cellNbrOfUsersLoadControlThreshold is used if
RadioCacCell::isPerNeighborCarrierLoadControlEnabled = True.
48
PARAMETERS
Parameter initial Value A1

cellNbrOfUsersLoadControlThreshold 68%
Domeez04_2
preventiveLoadControlThresholdNbrOfActiveUsers 68%
cellNbrOfUsersLoadControlThreshold 28%
Domeez04_4
preventiveLoadControlThresholdNbrOfActiveUsers 28%
averagingPeriodForNbrActiveUsersPreventiveOffload 500
enbNbrOfUsersLoadControlThreshold unset unset
isInterFreqLoadBalancingFeatureEnabled TRUE TRUE
isInterFreqPreventiveLoadControlEnabled TRUE TRUE
isStaticPrbBasedPreventiveLoadControlEnabled FALSE FALSE
eNB Level: Doomez04 isLoadEqualizationEnabled FALSE FALSE
isQoSBasedPreventiveLoadControlEnabled FALSE FALSE
isNumUeBasedPreventiveLoadControlEnabled TRUE TRUE
isOffloadUponReactiveLoadControlAllowed TRUE TRUE
isReactiveLoadControlAllowed TRUE TRUE
spare15 (bit0) 1 1
49
KPIS RESULT
Max RRC Connected load balance based on traffic management

118.14%
400.00 120.00%
101.57% 110.00%
350.00 97.25% 94.94%
94.49%
100.00%
85.42% 83.62% 82.96% 87.90% 86.64%
300.00 82.14% 80.36% 90.00%
80.00%
250.00 62.58%
59.54% 70.00%
200.00 60.00%
47.26%
50.00%
150.00
40.00%
100.00 30.00%
20.00%
50.00
10.00%
0.00 0.00%
Domeez04_2 Domeez04_4 RRC_connected_Users_F2/RRC_connected_users_F1(%)
Max RRC connected users between 2 carriers are approximately within 2:1 after feature activation
50
AGENDA
Introduction
Conclusion
Conclusion
51
CONCLUSION
The table below lists the available features in LR13.3 and their main impacts on load balancing procedures.
Feature Load Balancing Effect Decision
In addition to the load balancing Considering the low traffic and the thresholds that are
Load balancing
implementation of L115223, allows load currently used for preventive offload it would be difficult to
based on semi-
equalization triggering and inter-frequency achieve a status of load imbalance between the two LTE
static PRB
preventive offloading without neighbour load carriers, in order to properly manage load equalization and
utilization
information. avoid ping-pong between carriers.
A sensible approach would be setting the real PRB
consumption thresholds to the same values as the semi-static
Load balancing Allows triggering of load balancing based on
PRB consumption ones. However the definition of the
based on real real/actual PRB consumption and average
thresholds using monitoring data would not be as intuitive as
PRB utilization QoS degradation of non-GBR bearers.
the number of connected users, especially in a low loaded
network.
Allows triggering load balancing based on
In terms of consistency with CAC settings there is not a critical
Load balancing the number of connected UEs per cell or
choice between the criteria based on the number of users and
based on number of connected UEs per eNB in
PRB consumption. However, the number of users criterion is
number of addition to the existing semi-static/real PRB
easier to monitor and define suitable thresholds, so it is the
users consumption and non-GBR downlink
selected criterion for LR13.3 load balancing.
throughput.
52
CONCLUSION
• Alcatel-Lucent’s Dual Carrier Solution is capable of operating six cells of two carriers.
• Inter-freq Mobility functions of Reselection and Handover is ensuring coverage continuity

between the two carriers/layers.
• Enhanced Load Balancing features introduced by LR13.3 software for load balancing
PRBs ,Users and maintain good QoS per user between two carriers are working properly
and achieving 2:1 ratio following carrier bandwidth; F1/F2 = 20Mhz/10Mhz.
• the number of users criterion is easier to monitor and define suitable thresholds, so it is
the preferred criterion for LR13.3 load balancing.
53

Fastlink IRAQ LR13.3 - 2ndcarrier - LoadBalance - Introduction Ed1.1

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

Fastlink IRAQ LR13.3 - 2ndcarrier - LoadBalance - Introduction Ed1.1

Uploaded by

Copyright:

Available Formats

FASTLINK-IRAQ

DUAL CARRIER FEATURE INTRODUCTION “LR13.3”

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

LTE Inter-frequency Cell Reselection

LTE Inter-frequency Handover

Load balancing features

• As a result of traffic growth in Fastlink network, increased capacity and offloading is

LTE Inter-frequency Cell Reselection

LTE Inter-frequency Handover

Load balancing features

7 qRxLevMin (dBm) -120

Reselection to intra freq

Cell reselection to 2nd carrier

3.Reselection to lower priority cell

LTE Inter-frequency Cell Reselection

LTE Inter-frequency Handover

Load balancing features

UE measurement report trigger types supported in eNB:

Domeez04_2 Domeez04_4 Total traffic(Domeez04_2 and Domeez04_4)

Overall Total traffic have increased as result of 2nd carrier cell

Max RRC Connected Users

333 343 331 336

Domeez04_2 Domeez04_4 Total RRC connected users (Domeez04_2 and Domeez04_4)

PRB UTILIZATION (%)

PRB Utilization BH (%)

LTE Inter-frequency Cell Reselection

LTE Inter-frequency Handover

Load balancing features

•Step 1: Load equalization threshold is reached:

• Preventive Load Control

<xx> PreventiveLoadControlThresholdOnStaticPrb – LoadEqualizationDeltaThreshold

Parameter Name Implemented Action1 Action2 Action3 Action4

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Parameter Name Action_1 Action_2

Max RRC connected Users

Domeez04_2 Domeez04_4 (RRC_Connected_Users_F2)/RRC_Connected_User_F1)(%)

_PRB_average_Utilization_F1(Domeez04_2)(%) _PRB_average_Utilization_F2(Domeez04_4)(%) Ratio F2:F1

Parameter initial Value A1

Max RRC Connected load balance based on traffic management

Domeez04_2 Domeez04_4 RRC_connected_Users_F2/RRC_connected_users_F1(%)

LTE Inter-frequency Cell Reselection

LTE Inter-frequency Handover

Load balancing features

Feature Load Balancing Effect Decision

• Inter-freq Mobility functions of Reselection and Handover is ensuring coverage continuity

You might also like