HSDPA Inter-Frequency Load Sharing (FAJ 121 1467)

Date : 21/09/2014
RLAM/O/R/X/B/Arun Peelwal
 HSDPA Inter-Frequency Load Sharing
1.- DESCRIPCIÓN:

Current Configuration Enhanced Configuration

No Sharing of HS & EUL User between the Carriers of a sector This optional feature enables loads haring of HSDPA & EUL
at RAB Set-up. connections between several coverage-related HSDPA capable
cells. The HSDPA load is measured as the number of HS users.

S No. RNC Cell

2.- ALCANCE: 1 MXW4933
2 MXZ4933
3 MXX5984
Feature Activate from 11th Agosto to 18th Agosto. 4
ECAEV1
MXU5984
5 MXX3463
Feature Deactivated from 19th Agosto to 26th Agosto 6 MXU3463
7 MXX0056
Case I : Impact on 3rd Carrier ( MXA3526 & DFA1809) 8 MXU0056
9 NEXEV1 MXA3526
Case II : Impact on 1 & 2nd Carrier ( RNC ECAEV1 Cells in attached table) 10 XOCRN1 DFA1809

3.- KPI A EVALUAR:

Accessibility , Retain ability & Traffic of all Services , Average HS/EUL User per Carrier

4.- BENEFICIO ESPERADO:

• Better Sharing of HS & EUL User between Carriers so better Utilization of Licenses-HS & EUL User Licenses.
• Improve Accessibility in Node B having high Traffic of Data.
• More Data Traffic.
 WCDMA Mobility

To be implemented to make Traffic Balance between Carriers

 DESCRIPTION
This feature enables that HSDPA users are divided between several HSDPA enabled carriers
based on operator configurations. Multi Carrier, MIMO and EUL capability is also considered.
The load on HSDPA is measured as number of users. This feature is triggered when a user
is setting up a RAB on HSDPA or having channel switching to HSDPA.

This feature requires the optional RAN feature FAJ 121 405, Inter Frequency Handover and
Cell Reselection.

This feature includes following improvements:

◾Consider EUL congestion state at Inter-frequency load
sharing (IFLS) decisions. This enhancement requires optional feature FAJ 121 1584 UL
efficiency - DCH/EUL load balancing.

◾Recalculation of Margin parameter (UtranCell::hsIflsMarginUsers) in congested situations.

◾Re-attempting loadsharing evaluations for lower capabilities in congested scenarios.

◾More coverage-relations (up to 8), and pathloss-threshold per relation.

A coverage relation is a configured relation used between cells on different frequencies. A

coverage relation is used in IFLS and HS cell selection functions for blind hard handover or
Radio Bearer reconfiguration between WCDMA carriers.
 Parameter Description
5.- DETALLES:
MO Class
Name Parameter Name Node Parameter Description Valid Values TELCEL Value
CoverageRelati relationCapability RNC Specifies which features use this relation.
on
CoverageRelati relationCapability.hsLoadSh RNC Specifies if HS interfrequency load sharing can be used between the OFF = 0 ON
on aring source and target cells defined by this relation. This can also result in ON = 1
selecting a cell based only on capability.
Handover iflsHyst RNC Hysteresis load between the target and source cell that must be fulfilled 0---100 20
before triggering a load sharing redirection to the target cell, relative to
the current load in the source cell.

UtranCell hsIflsMarginUsers RNC Margin for HS interfrequency load sharing, relative to the admission limit 0---100 20
hsdpaUsersAdm. When calculating remaining free resources in the cell
during evaluation of a RAB transition, this margin is subtracted from the
result, making the cell look more loa
UtranCell hsIflsThreshUsers RNC Threshold for triggering HS interfrequency load sharing in the source cell, 0---100 50
relative to the admission limit hsdpaUsersAdm. If more than
hsIflsThreshUsers/100 * hsdpaUsersAdm HS users are present when a
RAB transition is being evaluated, load sharing is tr
UtranCell iflsMode RNC Defines the types of RAB reconfiguration that can trigger load sharing RAB_EST = 0 0
actions. Can be set to RAB Establishment, Upswitch attempts caused by UPSWITCH_ATT = 1
channel switching, or both. RAB_EST_AND_UPSWITCH
_ATT = 2
UtranCell pathlossThreshold RNC Pathloss threshold. A pathloss check is performed before triggering a 130
blind IFHO to a candidate cell, when performing load sharing from DCH
state. If the pathloss is higher than this threshold, the blind IFHO is not
allowed.
 HS Load sharing – TELCEL
Without HS Load Sharing Feature :
• No Mobility of UE at HS/EUL RAB Set-up from 3rd Carrier to 1st or
2nd Carrier on the basis of Load of User.

3rd Carrier-2100 Band • No Mobility of UE between 1st and 2nd Carrier on the basis of Average
HS/EUL User in case of high Load.

2nd Carrier
Carrier-850 Band

1st Carrier-850 Band

With HS Load Sharing Feature :

• Mobility of UE at HS/EUL RAB Set-up from 3rd Carrier to 1st or 2nd
Carrier on the basis of Load of User.

• Mobility of UE between 1st and 2nd Carrier on the basis of Average

HS/EUL User in case of high Load.

• Equal distribution of Data User on the 1 & 2nd Carrier.

• Better Usage of Resources

• Better Trunking Efficiency

• The HS & EUL Traffic is balanced.

Case : Impact on 1st & 2nd Carrier of the Sector

Cells : MXX0056 -MXU0056

DATE : Feature Activated from 11th August to 19th August.

Feature De-activated from 19th August to 4th Sept.

Purpose : The Network have two Carriers of 850 Band in all the sites.
To analyze the impact of this feature on KPI of 1st & 2nd
Carriers of the sector of the Site.
 Average User per Carrier
Feature Activated Feature De-activated

With Feature Without Feature

With Feature Without Feature

The Average HS User per Carrier distribution between 1st and 2nd Carrier of the Sector is balanced with Feature Activation.
So , Average HS & EUL User License of two Carrier of the Sector are used in a Pool for the Sector.
The Feature de-activation causes imbalance in Average Users between two Carriers.
 Data Traffic

With Feature With-out Feature

With Feature With-out Feature

• HS Traffic Balanced on Both Carriers HS Traffic Imbalanced on Carriers
• EUL Traffic Balanced on both Carriers EUL Traffic Imbalanced
 With Feature Without Feature

The Feature de-activation caused in degradation EUL Set-up Success Rate of both Carriers..

Reason Imbalance in EUL Attempts due to Feature deactivation and EUL rejections due to blocking

Same EUL Attempts in both Carrier with Feature Activation.

EUL Set-up Success Rate 2nd Carrier : 55.0% -> 45.0% 1st Carrier : 55.0% -> 50.0%

EUL Call Attempts 2nd Carrier : 18K -> 21.0K 1st Carrier : 18K -> 16K
 With Feature Without Feature

With Feature With-out Feature

• Same EUL Rejections on both Carriers Different EUL Rejections on both Carriers
• 1st Carrier : 3500 2nd Carrier:3500 1st Carrier : 4000 2nd Carrier:7500
• Total EUL Rejections :7000 Total EUL Rejections :11500
 With Feature Without Feature

The reason of EUL rejections are due to admission.

The EUL blocking is almost same on both the Carriers but Feature de activation create imbalance on two carriers.

The Feature de activation increase more EUL blocking.

 With Feature Without Feature

Imbalance in HS Attempts due to Feature deactivation.

HS Set-up Success Rate 2nd Carrier : 98.5% -> 94% 1st Carrier : 98.3% -> 97.0%

HS HS Call Attempts 2nd Carrier : 22K -> 20K 1st Carrier : 22K -> 25K
 With Feature Without Feature

With Feature With-out Feature

• Good RRC Accessibility Poor RRC Accessibility
• RRC Access. 1st Carrier : 99% 2nd Carrier:99% 1st Carrier : 98% 2nd Carrier: 94%
• Same RRC Attempts on both Carriers Difference RRC Attempts on both Carriers
• RRC Attempts 1st Carrier : 27500 2nd Carrier:27500 1st Carrier : 29000 2nd Carrier:35500
 CS Accessibility

With Feature Without Feature

The CS Accessibility also affected.

The CS RRC Accessibility degraded from 99.5 % to 99.3% while the Call Attempts are same.

The RRC Failures after admission also degraded.

 CS Accessibility

With Feature Without Feature

The CS Accessibility degraded on both Carriers after feature deactivation.

 Retainability (CS,PS & EUL)

With Feature
Without Feature

The CS Drop Rate degraded from 1.0% to 1.4% with Feature Deactivation.

The PS Drop Rate degraded from 2.0% to 2.5%.

The EUL Drop Rate degraded from 1.0% to 1.2% .

 Sector Retain ability-CS

With Feature Without Feature

With Feature With-out Feature

• Good CS Retainability Poor CS Retainability
• CS Drop Rate of Sector : 1.5% 1.7%
 Carriers Retain ability-CS

Without Feature
With Feature

The CS Drop Rate increased in Peak hour from

 Sector Retainability-PS

With Feature Without Feature

With Feature With-out Feature

• Good PS Retainability Poor PS Retainability
• PS Drop Rate of Sector : 3.0% 4.0%
 Carrier Retain ability-PS

With Feature Without Feature

With Feature With-out Feature

• Good PS Retainability Poor PS Retainability
• PS Drop Rate. 1st Carrier : 4.0% 2nd Carrier:2.2% 1st Carrier : 5.0% 2nd Carrier: 2.5%
 Case II:KPI Summary

With Feature Without Feature

Average HS User Balanced (48 per Carrier) Imbalanced
Average EUL User Almost Balanced More Imbalanced
HS Traffic Balanced Imbalanced
EUL Traffic Almost Balanced More Imbalanced
EUL Attempts Balanced ( 18K) Imbalanced (1st Carrier:16K & 2nd Carrier :21K)
HS Call Attempts Balanced (22K) Imbalanced (1st Carrier:25K & 2nd Carrier :20K)
RRC Attempts Balanced ( 27.5K) Imbalanced (1st Carrier:29K & 2nd Carrier :35.5K)
EUL Rejections Balanced ( 3500 on both Carriers) Degraded ( Total 11500 on both Carriers)
HS Set-up Success Rate Almost Balanced (98%) Degraded ( (1st Carrier:97% & 2nd Carrier :94%)
EUL Set-up Success Rate Balanced ( 55% in Peak Hours) Degraded (1st Carrier:50% & 2nd Carrier :45%)
RRC Accessibility Almost Balanced (99%) Degraded ( (1st Carrier:98% & 2nd Carrier :94%)

CS Accessibilitty (1st Carrier:97.4% & 2nd Carrier :98%) Degraded (1st Carrier:97% & 2nd Carrier :96%)
CS Drop Rate 1.50% 1.70%
PS Drop Rate 3.00% 4.00%
 CONCLUSIONES & RECOMENDACIONES CASE II
8.- CONCLUSIONES:

- The distribution of HS User & Data Traffic on 1st & 2nd Carrier balanced with Feature.

-The HS & EUL Accessibility is better with Feature Activation.

-The EUL Rejections due to blocking increased from 7000K to 11500K after feature de activation.
-The CS Accessibility degraded after feature de activation.
-The CS , PS and EUL Drop rate increased after feature de activation.
-Good Feature to Use HS User License Capacity of Carriers in Pool .

9.- RECOMENDACIONES:
This Feature should be good to implement in Sites with high Data Traffic and Good Data Users.
Case : Sector having 3 Carrier ( MXA 3526 , MXU0156 & MXX0156)

Action : To analyze the impact of “HS Load Sharing “ in the 3rd Carrier of the Sector.

Date : Feature Activated from 9th August to 19th August in 3rd Carrier of the Sector.
Feature De-activated from 19th August to 31st August in 3rd Carrier of the Sector.

Purpose : This feature allows sharing of HS Load between Carriers of the Sector.
The feature disabling in 3rd Carrier will not allow sharing of HS Load with
1st & 2nd Carrier in high Data Traffic case.
To analyze the impact of this Feature on 3rd Carrier KPI and also1st & 2nd
Carrier KPI.
 Feature De activation

With Feature Without Feature

The Feature deactivation in 3rd Carrier caused Inter Frequency Load Sharing Attempt
from 3rd Carrier to 0.
 Average Data User-Between 1st,2nd ,3rd Carriers
3rd Carrier:MXA3526

With Feature 2nd Carrier:MXU0156 Without Feature

1st Carrier : MXX0156

The de-activation of Feature in 3rd Carrier causes stop sharing of HS & EUL User to 1st & 2nd Carrier.
The Average HS User in 3rd Carrier increased from 50 to 56 But the Average HS User in 1st and 2nd Carrier reduced .
 With Feature Without Feature

The 3rd Carrier HS Set-Up Success Rate degraded without Feature because of not sharing of HS & EUL Users with the 1 st &2nd Carriers at PS RAB Set-up.
3rd Carrier HS Set-up Success Rate : 98.5% -> 96% Reason HS Attempts increased due to increase Average in HS User in 3rd Carrier.
After Feature disable in 3rd Sector , no load sharing at HS Rab set-up by 1st & 2nd Carrier of the Sector causes Poor HS Set-up Success Rate.
The 1st & 2nd Carrier HS Set-up Success Rate are stable.
 With Feature Without Feature

The 3rd Carrier EUL Set-Up Success Rate degraded without Feature because of not sharing of HS & EUL Users with the 1 st &2nd Carriers at PS RAB Set-up.
3rd Carrier EUL Set-up Success Rate : 60.0% -> 48% in Peak Hour.
After Feature disable in 3rd Sector , no load sharing at PS Rab set-up by 1st & 2nd Carrier of the Sector causes Poor EUL Set-up Success Rate.
The 1st & 2nd Carrier HS Set-up Success Rate are stable.
 With Feature Without Feature

The EUL rejections in 3rd Sector increased from 18,000 to 22,000 after disabling this Feature in 3rd Sector.
This increased EUL Rejections also degraded EUL Set-up Success Rate in 3rd Sector.
The EUL rejections in 1st & 2nd Carrier are Stable.
 With Feature Without Feature

The HS and EUL Set-up Success Rate of 3rd Carrier degraded due to blocking in PS RRC and PS RAB in 3rd Sector.
There was no CS & PS RRC blocking in 1 and 2nd Carrier.
With Feature Without Feature
With Feature Without Feature
 With Feature Without Feature

The PS Set-up Success Rate becomes poor due to blocking of PS RRC in 3rd Sector.
The PS RRC blocking incresed from 0 to 20 % in 3rd Sector.
 With Feature Without Feature

The PS Attempts on 3rd Carrier increased but on 1st & 2nd Carrier are stable.

The PS Attempts on 3rd Carrier are almost double than 1st & 2nd Carrier.
 CS Accessibility

With Feature Without Feature

The CS Accessibility degradaed on 3rd Carrier from 98.2 % to 94%.

 CS Blocking

With Feature Without Feature

 RAB Failures Reason

With Feature Without Feature

 CS & PS Drop Rate

With Feature
 No. Of Drops

With Feature Without Feature

 HS Throughput

With Feature Without Feature

The HS User Throughput degraded from 1,000 Kbps to 800Kbps in Peak Hour and Working Days.
With Feature Without Feature
 CS Traffic

With Feature Without Feature

 HS Traffic

Without Feature

With Feature
 EUL Traffic

With Feature Without Feature

 Code Usage
MXA 3526

With Feature Without Feature

The Code Usage increased from 84% to 95% in 3rd Sector.

The Code Usage decreaded in 2nd and 1st Carrier.

 CASE I:KPI Summary
The following KPI of 3rd Carrier affected after this Feature de- activation:

Without
S No. KPI With Feature Feature Comment

1 Avg. HS User on3rd Carrier 50 56 Avg. User on 1st & 2nd Carrier reduced.
2 HS Accessibility 99% 96% In peak hour
3 EUL Accessibility 80% 48% In peak hour
4 No. Of EUL Blocking 18K 22K Per Hour
5 Total RRC Accessibility 98.00% 95% Due to Increase in PS Attempts.
6 CS RRC Accessibility 99.50% 96%
7 HS Throughput 1000Kbps 800Kbps Because of increase in Users.
8 code Usage 84% 95%
 CONCLUSIONES & RECOMENDACIONES
8.- CONCLUSIONES:
- The HS User shared evenly between the Carriers with Feature. The 3rd Carrier becomes heavily
loaded after deactivation of Feature. It is a good Feature to offload the PS User from 3rd Carrier to
other Carriers.
-The load of PS User on 3rd Carrier degraded the HS & EUL Accessibility without Feature.
-The increased load of HS & EUL User on 3rd Carrier after feature deactivation caused degradation
in RRC Accessibility and blocking in RRC.
-Feature de-activation affected CS Accessibility and it becomes poor from 99.5 % to 96.0%.
-Feature de-activation cause decrease in Average HS User Throughput from 1000 Kbps to 800
Kbps.

9.- RECOMENDACIONES:
The fe ature is recommended to implement in all the Sites having high Data Users.