IF Load Sharing in multi-

carrier network
July. 2011
Content

General Concept of Loadsharing and coverage relation

HSDPA Inter Frequency Load Sharing

Non-HSDPA Inter Frequency Load Sharing

General Concept
Load Sharing features
Inter-Frequency Load Sharing, (FAJ 121 435)
Directed Retry to GSM, (FAJ 121 406)
Load based HO to GSM, (FAJ 121 1356)
Inter-frequency load based HO, (FAJ 121 1402)
HSDPA Inter-frequency loadsharing, (FAJ 121 1467)
Non-HSPA Inter-frequency loadsharing, (FAJ 121 1468)
HS Cell Selection (included in FAJ 121 801, HSDPA Mobility)
General Concept
HS & non-HS IF Load Sharing
Balance the remaining resource among the load-sharing neighbors.
Triggered when UE starts to set up a connection.
Blind IFHO without measurements is used in HSDPA IFLS.
Up to 5 load-sharing candidate cells can be defined for each source cell
The attribute RelationCapability specifies whether the target cell is a hs or non-
hs load-sharing neighbor of the source cell.
Coverage relation can only be between the cells in same RNC
Basic strategy of relation setting:
All the co-located cells and nearby IF cell should be defined as neighbour relation.
Only co-located IF cells should be defined as coverage relation.

2nd Carrier 2nd Carrier 2nd Carrier

R99
Risk of
Block/drop
HS & EUL

1st Carrier 1st Carrier 1st Carrier 1st Carrier

Camp on 1st Carrier

Neighbour Relation Coverage Relation

General Concept
There must be at least one HS or non-HS loadsharing candidate cell.
Cells on frequency bands not supported by the UE shall not be used and are
filtered out.
If there are no defined candidate cells, or all are removed by the band filtering,
then loadsharing is aborted.
Load-sharing decisions are made based on the amount of remaining resource
in the cell.
remaining-resource = 1 cell-load excluded-resource
A pathloss check is performed at RAB setup from SRB before a blind IFHO
can be triggered.
Note that the pathloss check is not performed before an upswitch from FACH.
Pathloss has to be below a configured threshold:
CPICH_TxPwr - reported DL CPICH_RSCP < pathlossThreshold
HSDPA IF Load Sharing
Distribute HSDPA, EUL, MIMO and MultiCarrier users between cells with this
capability.
The load is measured as the number of HS users.
The feature can be triggered when:
connection establishing in HSDPA
connection upswitching from FACH or DCH to HSDPA.
Cell selection based on capability is replaced by HSDPA IFLS.
Capability matching principle:

R99/HS
Always to a higher Not prefer. Target
capability cell, cell capability
regardless load. mismatch

R99,EUL/HS
 HSDPA IFLS, Logic flow
Trigger for HS: The HSDPA IFLS is triggered by the
SRB HS following transitions:
FACH HS
DCH HS SRB HS
DCH DCH + HS FACH HS
DCH HS
Feature is active?
NO RAB on DCH DCH + HS
YES Check if the feature is active.
Pathloss test OK?
NO Pathloss check on serving cell.
YES Proceed according to Select target cell based on capabilities
installed
Select target cell based
and on remaining resources.
features/strategies
on load and capability Perform Blind IFHO or the required
algorithms reconfiguration.
Other Current
Cell Cell Continue the call setup on the target cell.

Trigger Blind IFHO, OK Stay in current cell

FACH HS,
HS reconfig

FAIL UE in target cell

IFHO fail, no drop,

stay in serving cell Continue RAB setup
HSDPA IFLS, Execution
If the serving cell has the same capability of the UE, the trigger condition and the hysteresis are applied.

If no_of_HS_users > hsIflsThreshUsers x hsdpaUserAdm (in current cell) then

Compute remaining HS resources (rr) in the source and all candidate cells:
rr = hsdpaUsersAdm no_of_HS_users hsIflsMarginUsers x hsdpaUserAdm

Do not consider cells with

rr <= 0 or
no_of_HS_users >= hsdpaUserAdm or
no_of_serving_cell_EUL_users >= eulServingCellUserAdm

Hysteresis condition:
rr (candidate cell) > (1 + iflsHyst) * rr (source cell)

Select the candidate cell with the most remaining HS resources;

Re-direct the call to this cell and setup the call
 HSDPA IFLS, Execution example
iflsHyst hsIflsMarginUsers
(ex 20%) (ex 10%) no_of_HS_users >
Remaining resources hsIflsThreshUsers
Source (a) : 9 > 50% x 16 = 8
(a) rr = hsdpaUsersAdm no_of_HS_users
hsIflsMarginUsers x hsdpaUserAdm
hsIflsThreshUsers
(ex 50% = 8)
no_of_HS_users
hsdpaUsersAdm
(ex 16)
rr(b) = 16 5 (10% x 16)
(ex 9)
= 9.4
hsIflsMarginUsers
ex 10%
rr(c) = 16 12 (0% x 16)
Remaining resources
Target1 =4
(b)
rr(a) = 16 9 (10% x 16)
no_of_HS_users hsdpaUsersAdm
(ex 5)
hsIflsThreshUsers
(ex 16)
= 5.4
(ex 50% = 8)

hsIflsMarginUsers
rr(b) > (1 + 0.2) x rr(a)
ex 0% 9.4 > 1.2 x 5.4 = 6.48 OK
Remaining resources
Target2
(c) rr(c) > (1 + 0.2) x rr(a)
4 > 1.2 x 5.4 = 6.48 NO
no_of_HS_users
hsdpaUsersAdm
(ex 12) hsIflsThreshUsers
(ex 16)
(ex 90% = 14.4)
Non-HSPA if Load Sharing

This feature will enable the R99 DCH load to be divided between several
coverage-related carriers.
The DCH load in a cell is measured as the DL power usage and the
DL code tree utilization, and loadsharing based on the DL power takes
preference and is evaluated first.
This feature can be triggered at RAB establishment of a new RAB, but not by
channelswitching cases.
Blind IFHO without measurements is used in IFLS.
The non-HSPA loadsharing does not apply to Emergency calls.
 Non-HSDPA IFLS, Logic flow
Trigger for DCH: The Non-HSPA IFLS is triggered by
SRB DCH
the following transitions:
FACH DCH SRB DCH
FACH DCH
Check if the feature is active.
NO
Feature is active?
Pathloss check on serving cell.
YES

Pathloss test OK?

NO Select target cell based on remaining
YES Proceed according to resources.
Select target cell based
installed
features/strategies
Perform Blind IFHO or the required
on load and capability reconfiguration.
algorithms
Current Continue the call setup on the target
Other
Cell Cell cell.
Trigger Blind IFHO, OK Stay in current cell
FACH DCH

FAIL UE in target cell

IFHO fail, no drop,
stay in serving cell
Continue RAB setup
Non-HSPA IFLS, Power Loadsharing
Compute
maxPower = min (maximumTransmissionPower,
dlPowerCapability(RBS)),
this value is used as 100% DL power.

If dchIflsThreshPower > 0 then check if

(Dl_Pwr_Non_HS + HS_Required_Pwr) > dchIflsThreshPower

if NO then check if Code loadsharing is triggered.

Non-HSPA IFLS, Power Loadsharing
Evaluate the remaining DL Pwr resource (rr) in the current cell and in the non-HSPA
loadsharing candidate cells:
rr = 100% (Dl_Pwr_Non_HS + HS_Required_Pwr) dchIflsMarginPower

Note that the value of dchIflsMarginPower from each cell is used.

Do not consider cells with

rr <= 0 or
DL-DCH Congested State

Hysteresis condition:
rr (candidate cell) > (1 + iflsHyst) * rr (source cell)

Select the candidate cell with the most remaining DL power resources;
Re-direct the call to this cell and setup the call
 Non-HSPA IFLS,
Power Loadsharing example
iflsHyst dchIflsMarginPower
(ex 10%)
(ex 20%)
Remaining resources
(Dl_Pwr_Non_HS +
HS_Required_Pwr) >
Source
dchIflsThreshPower
(a)
100% (a) : 75% > 70%
dchIflsThreshPower Dl_Pwr_Load
pwrAdm
rr = 100% Dl_Pwr_Load
(ex 70%) (ex 75%)
(ex 80%) dchIflsMarginPower
rr(b) = 100% 40% 0%
= 60%
dchIflsMarginPower
(ex 0%)
Remaining resources rr(a) = 100% 75% 10%
Target1 = 15%
(b)
100%
Dl_Pwr_Load dchIflsThreshPower
pwrAdm
rr(b) > (1 + 0.2) x rr(a)
(ex 40%) (ex 60%)
(ex 80%) 60% > 1.2 x 15% = 18% OK
Non-HSPA IFLS, Code Loadsharing
If Power loadsharing is not triggered, which means

(Dl_Pwr_Non_HS + HS_Required_Pwr) <= dchIflsThreshPower

and
dchIflsThreshCode > 0

then check if
Dl_Code_Tree_Load > dchIflsThreshCode
in the current cell.

If these conditions are not fulfilled, the call setup proceeds in the current cell with the
RAB establishment.
Non-HSPA IFLS, Code Loadsharing
Evaluate the remaining Code Tree resource (rr) in the current cell and in the non-HSPA
loadsharing candidate cells:
rr = 100% Dl_Code_Tree_Load dchIflsMarginCode

Note that the value of dchIflsMarginCode from each cell is used.

Do not consider cells with

rr <= 0 or DL-DCH Congeted State

Hysteresis condition:
rr (candidate cell) > (1 + iflsHyst) * rr (source cell)

Select the candidate cell with the most remaining DL code resources;
Re-direct the call to this cell and setup the call.
 Non-HSPA IFLS,
Code Loadsharing example
iflsHyst dchIflsMarginCode
(ex 20%) (ex 10%) Dl_Code_Tree_Load > dchIflsThreshCode
Remaining resources
(a) : 75% > 70%
Source
rr = 100% Dl_Code_Tree_Load
(a) dchIflsMarginCode
100%
dchIflsThreshCode rr(b) = 100% 40% 20%
Code_Tree_Load
(ex 70%)
(ex 75%)
dlCodeAdm = 40%
(ex 80%)

rr(a) = 100% 75% 10%

dchIflsMarginCode
= 15%
(ex 20%)
Remaining resources
Target1 rr(b) > (1 + 0.2) x rr(a)
(b) 40% > 1.2 x 15% = 18% OK
100%

Code_Tree_Load dchIflsThreshCode dlCodeAdm

(ex 40%) (ex 60%) (ex 80%)
Parameter List
The table below summarizes the described parameters and shows the default values.
Thresholds parameter are set to 0 (which means features not active) because these are
optional features.
Parameter Name Default Value Value Range Resolution Unit

Coverage relation
loadSharingCandidate FALSE (FALSE; TRUE) - -

hsLoadsharing ON (ON; OFF) - -

dchLoadsharing ON (ON; OFF) - -

pathlossThreshold 170 15..170 1 dB

HSDPA Inter-frequency loadsharing

hsIflsThreshUsers 0 0..100 1 %

hsIflsMarginUsers 0 0..100 1 %

non-HSPA Inter-frequency loadsharing

dchIflsThreshPower 0 0..100 1 %

dchIflsMarginPower 0 0..100 1 %

dchIflsThreshCode 0 0..100 1 %

dchIflsMarginCode 0 0..100 1 %

Common for HSDPA and non-HSPA Inter-frequency loadsharing

iflsHyst 20 0..100 1 %

iflsMode RAB_EST_OR_ RAB_EST,

UPSWITCH_AT UPSWITCH_ATT,
T RAB_EST_OR_UPSWITC
H_ATT
Q&a

THANK YOU!