Sei sulla pagina 1di 50

RU30 P3 Enabling by Network Engineering

RAN2172 Multi-Band Load Balancing


& Blind IFHO (RAN2289)

Grzegorz Ścibior
Network Engineering
NWS LTE RA E2E Mgmt SA NE
Wroclaw, 07.10.2010

Company Confidential
1 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
Software implementation

Supplementary O&M Information Release Information

Common O&M Platform WCDMA Release RU30


No
Feature
I-HSPA System Rel4
Basic SW/Additional SW ASW
RNC Release RN6.0
RU SW Component HSPA
mcRNC Release mcRNC1.0

License Control RNC LK


BTS (Ultra) WBTS7.0

BTS (Flexi) WBTS7.0 EP2

NetAct OSS5.2

Ultrasite: EUBB
HW Requirements
Flexi: FSMC/D/E

Company Confidential
2 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Terms used in this presentation
HSDPA or HSPA capable UE
the 3GPP Rel5 or Rel6 compliant UE supporting HSDPA/DCH or HSDPA/HSUPA
Non-HSPA capable UE
UE without HSDPA support
UE with DCH service
Non-HSPA capable Or HSPA capable UE with DCH channel assigned in UL and DL
UE with HSDPA service
The HSPA capable UE with HS-DSCH DL channels assigned
UE with HSPA service
The HSPA capable UE with E-DCH UL and HS-DSCH DL channels assigned
DCH cell
The UTRAN cell without enabled HSDPA support (HSDPAenabled:WCEL)
HSDPA cell
The UTRAN cell with HSDPA support enabled
HSPA cell
The UTRAN cell with HSDPA and HSUPA support enabled. HSPA cell is also HSDPA cell
Source cell
The cell with highest RSCP among reported in RACH intra-freq measurements

Company Confidential
3 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Brief description:
 Optional RAN feature with RNC level license: „Multi-band Load Balancing”
 RU20 and earlier RAN, intra/inter-band redirections/handover, for example:
Capability based redirection: HSPA/non HSPA capable UEs to HSDPA/non HSPA cell during
connection setup (RAN502) Or/And during FACH->DCH transition (RAN1011) , assuring load
balancing of target HSDPA cells (redirection always within the same sector)
HSPA capability based IFHO (RAN1596): periodically searches for HO candidates in DCH cells.
Pushes HSPA capable UEs to HSPA layers: cells of same/different BTS in UTRAN/I-HSPA. No load
is checked in target cells before handover
Load based HO (RAN140): moves non-HSPA calls. HSPA load can not trigger the load based HO
 New/extended in RU30, HSPA+ capable inter-band handovers/ redirections
Target cell selection can depend on: UE capability & service, freq band, target/source cell (or avg
band) load, UE distance from source/target cells. It extends existing scenarios by for example:
 HSPA capable UE with CS RAB in HSDPA cell can be moved to DCH cell
(RAN502/1011 extension)
 Target and source cell loads can be checked prior HSDPA inactivity triggered HO
(RAN1596 extension)
 The load based HO can be triggered by HSPA traffic overload (RAN140 extension)
 Load sharing/balancing between HSPA cells/bands is provided

Motivation and benefits:


 Better frequency resource utilization by directing UE to different frequency bands or layers in multi-
band networks. Capability, service, load and distance based HO are now possible for HSPA+
between e.g. U2100 and U900/U850 cells
 The feature supports service vs. band strategy realization in multi-band networks (e.g. 2.1GHz and
Company Confidential
4
850/900MHz) RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
© Nokia Siemens Networks
RAN2172 Multi-Band Load Balancing
Interdependencies

Restricts RAN 2172 Requires


RAN 1596 RAN 2289
HSPA Capability IFHO Multi-band Load Balancing Blind IFHO in RAB Setup phase

RAN1011 RAN 1276


HSDPA Layering for UE on CCH HSDPA IFHO

RAN502 RAN2172 requires:


DRRC at RAB Setup for HSDPA  RAN2289 (Blind IFHO at RAB
Setup) – functional part of MBLB
 RAN1276 (HSDPA IFHO) –
required for Mobility Or Inactivity
triggered MBLB modes

RAN2172 restrict concurrent usage of:


 RAN1011 (HSDPA layering for UE in CCH) –deactivated when MBLB
Layering in State Change* mode active
 RAN1596 (HSPA Capability Based HO)
to be deactivated event triggered mode when MBLB Inactivity triggered*
mode active
 RAN502 (DDRC at RAB Setup for HSDPA) –deactivated when MBLB
Blind IFHO* mode active
Company *Confidential
The MBLB scenarios are superset of those allowed by deactivated modes of HO/redirection features
5 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Inter-freq redirection/handover – situation till RU30
Feature
Non HSPA HSPA
Redirection or
capable UE capable UE
RAN502 handover at:
Directed RRC Connection Setup for HSDPA cell
HSDPA Layer (RAS05) RRC connection setup only
DCH cell

RAN1011
HSDPA cell
Same / different band Connection Setup or
HSPA Layering for UEs in Common HSDPA cell
Channels (RAS6.0) with DCH
service CTS FACH to DCH
DCH cell
Redirection with HSDPA load balancing

i-HSPA cell
RAN1596
1 2
HSPA Capability Based Handover Same / different band HSPA cell
[inter-frequency] (RU10) HSPA cell Anytime during
1
DCH cell DCH cell CELL_DCH or on HSPA
traffic inactivity

1 HSPA capability based HO to other HSPA layer Or Load balancing between


HSPA layers Or HSPA load based triggered HO
HO from DCH cell
2 Confidential
Company to i-HSPA
6 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Use cases – modes of operation

RAN 2172
Multi-band Load Balancing

provided in RAN2289
a

Blind HO at Inactivity Layering in Mobility


RAB setup triggered state change triggered
IF handover to higher prioritised frequency layer in same or different band
w/out CM activation, with CM activation for UE w/out CM activation, with CM activation for UE
in case: with HS-DSCH, in case: in case: with HS-DSCH (or DCHx/x), in
 NRT/RT RAB is setup  UL and DL traffic inactivity  State change from case:
(1st RAB) detected which otherwise CELL_FACH to DCH  New cell in active set (1A/1C)
 AMR call is setup while cause CTS to FACH and  State change from may trigger SCC and has
UE with assigned NRT any freq layer with IF PCH/URA-PCH to DCH PLFIdentifier other then SC
RAB is in CELL_DCH or neighbours to AS cells, is whenever fast call setup  Removed cell (1B/1C)
CELL_FACH state higher prioritised then allowed and possible PLFIdentifier was used for UE
currently used for reasons and was different then any
other then only lower other cells left in AS
HSDPA load  Detected high mobility of UE
with HS-DSCH

Each type can be enabled on cell level independently on others, by corresponding source
cell WCEL parameter (enabling in target cell not needed):
MBLBRABSetupEnabled
Company Confidential
7 © Nokia Siemens Networks
MBLBInactivityEnabled MBLBStateTransEnabled
RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
MBLBMobilityEnabled
RAN2172 Multi-Band Load Balancing
Capability and service, RSCP, freq band, load controlled HO targets (1/2)
Redirection/Blind IFHO to
Blind IFHO AND Layering in State Change modes higher priority layer cell, at:
Connection setup Or CTS
DCH/HSPA cell (band Z) FACH/PCH/URA  DCH
DCH/HSPA cell (band Z)

DCH/HSPA cell (band Y, RF2) DCH/HSPA cell (band Y, RF1)

DCH/HSPA cell (band X)

MBLB extends RAN502/1011 redirection scenarios. Target cell can be any


intra-RNC, IF neighbour cell which is not in overload state1). It can be in same or
different BTS, same or different frequency band supported by UE.
IF neighbour must have higher priority then source cell (slide 10). Priority is
influenced by OAM configurable preferences:
 Carrier preference for pairs: UE Capability, Used or Requested Service/RAB
 Frequency band preference for multi-band UEs
 High or low band preference based on UE distance from source cell
 HSDPA load (HSDPA cell pwr per user & unused DL cell power)
1)
Overload state is checked prior HO. Both the overload according RAN140 criterions and HSPA MBLB criterions are respected. HSPA overload (ref to backup slides) is
indicated
Company based on: HSDPA/HSUPA used power & user bit rate, HSUPA resource indicator, HSDPA users in cell / scheduler
Confidential
8 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Capability and service, RSCP, freq band, load controlled HO targets (2/2)

HSDPA inactivity Or Mobility triggered mode CM IF handover to


higher priority layer cell, on:
HSDPA traffic inactivity
DCH/HSPA cell (band Z) DCH/HSPA cell (band Z) (instead CTS to FACH)
HS-DSCH
DCH/HSPA cell (band Y, RF2) DCH/HSPA cell (band Y, RF1)
HS-DSCH

DCH/HSPA cell (band X)

MBLB extends RAN1596 event triggered mode scenarios (on HSDPA traffic
inactivity) and adds new HSDPA mobility triggers. Target cell can be any intra-
RNC, inter-frequency neighbour cell which is not in overload state1). It can be in
same or different BTS, same or different frequency band. IF neighbour must have
higher priority then source cell (slide 10). Priority is influenced by OAM
configurable preferences:
 Carrier preference for pairs: UE Capability, Used Service/RAB
 Frequency band preference for multi-band UEs
 High or low band preference based on UE distance from source cell
 HSDPA load (avg cell2) HSDPA pwr per user & unused DL power)
1)
Overload state is checked prior HO. Both the overload according RAN140 criterions and HSPA MBLB criterions are respected. HSDPA/HSUPA used power & user bit
rate, HSUPA
Company resource indicator, HSDPA users in cell / scheduler
Confidential
9 2) © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
Average from HSDPA power results for cells on same carrier / frequency layer. Only cells neighbouring to active set cells are considered
RAN2172 Multi-Band Load Balancing
Frequency layer priority - Preference Score (1/5)
Each carrier (& frequency band) used in RNS can be differently prioritised.
Carrier/frequency layer priority (preference score) is effected by:
 Selection of carrier preferred for configurations: UE capability & used RAB
 RNC level selection of one preferred frequency band
 High and/or low band preference depending on UE distance from source cell
 HSDPA cell or carrier / freq layer load preference
Each factor represented by weight is OAM configurable. Candidates for MBLB
are IF neighbours on freq layer higher prioritised then source cell layer, in bands
supported by UE Not considered Not considered for
for fast moving non-HSPA UEs or
UEs other with CS RAB in
DCH cell
Freq layer priority Preferred Freq Freq Band RSCP Load
= + + +
(Preference Score) weight weight weight weight
= = = =

0 0 0 0
or or or or
LaySelWeightPrefLayer LaySelWeightBand LaySelWeightRSCP >=LaySelWeightLoad
Company Confidential
10 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Frequency layer priority – Preferred Layer weight (2/5)
Each combination „UE capability – Used/Requested Service” may be redirected by
Operator to preferred frequency. For example MIMO capable UE with NRT RAB should be
redirected to frequency with MIMO configured cells. Preferences are defined in new object
PFL (Preferred Frequency Layer – up to 50 in RNC) by PrefLayerXXX carriers tables (one
table with up to 8 carriers per „UE capability-Used Service” pair)

PFL.PrefLayerXXX[1÷8]= 0=not defined


UE capability & Service/RAB  preferred RF freq
>0 (RF freq anumber)

PFL:LaySelWeightPrefLayer
UE capability Service/RAB combination Preferred carrier
table
CS over HSPA NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerCSHSxxx
Preferred Layer
DC HSDPA+MIMO NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerDCMIxxx = OR
weight
DC HSDPA NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerDCHSDxxx

0
MIMO NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerMIMOxxx
HSDPA 64QAM NRT or Streaming or AMR or AMR+NRT PFL:PrefLayer64QAMxxx
F-DPCH NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerFDPCHxxx
HSPA NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerHSPAxxx
HSDPA NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerHSDPAxxx
R99 DCH NRT or Streaming or AMR or AMR+NRT PFL:PrefLayerR99xxx
Fast moving
Company UE
Confidential PS domain or CS domain PrefLayerFastMoveUExx
WCEL:PFLIdentifier
11 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
UE capability search order (MIMO vs DC HSDPA order can be changed with RNC:DCellVsMIMOpreference)
RAN2172 Multi-Band Load Balancing
Example1: selecting best frequency/cells for UE capabilities / RAB
AMR or NRT RAB Setup/ cell_32 freq_priority=112
CTS to DCH 3 cell_11
freq_priority=0(200)
Idle/FACH/ PCH/URA cell_12
freq_priority=200(0)
HSDPA load=4 HSDPA load=10
RF3, band A
Cell_31: Cell_32:
3
PFLIdentifier=1 PFLIdentifier=1
MIMO UE&NRT RAB to MIMO
cell (best RSCP target) R99 UE with any RAB to
DCH cell (best RSCP target)
MIMO UE
AMR RAB Setup/ 1
2 cell_11 AMR in NRT/FACH (multirab)
freq_priority=0(200) Idle/FACH/ PCH/URA R99 UE
cell_12 1 cell_21 freq_priority=110
freq_priority=200(0) NRT RAB Setup/ cell_31
cell_21 freq_priority=110 CTS to DCH freq_priority=218(0) HSDPA UE
cell_32 HSDPA load=7
2
RNC-1/PFL-1 freq_priority=0(212)
LaySelWeightLoad=100 RF2,band A
LaySelWeightRSCP=0 Cell_21: HSDPA load=12 Cell_22: Depending on
4
PFLIdentifier=1 cell_12
LaySelWeightPrefLayer=100 PFLIdentifier=1 HSDPA load
(load balancing) freq_priority=100
LaySelWeightBand=0 cell_22
PrefLayerMIMONRT=RF3 freq_priority=215
PrefLayerHSDPAAMR=RF1 Any UE with AMR 4 Idle/FACH/ PCH/URA
cell_32
to DCH cell freq_priority=212
PrefayerHSDPANRT=RF2, NRT RAB Setup/ CTS to DCH
RF3
PrefLayerR99xxx=RF1
RF1, band A
Cell_11: PFLIdentifier=1 Cell_12: PFLIdentifier=1

In same geographical area cells shall be preferably assigned with same PFLIdentifier. It
is not mandatory but helps to avoid looping in preference definitions, which otherwise
mayConfidential
Company easily happen leading to ping pong handovers
12 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Frequency layer priority – Preferred Band weight (3/5)
Operator can promote one frequency band among used by neighbours of source
cell. The Freq Band weight of candidate cell carrier is determined from its absolute
RF number. Candidate cells in promoted band are assigned with non-zero weight
(PLY:LaySelWeightBand)
1÷15 (preferred freq band num)
Preferred UMTS band in RNC
PFL:PreferBandForLayering NO Candidate’s cell freq
0=no band preferred a
in preferred band?
YES
Band ID Frequency band (DL range)
1 RF band I (2110÷2170MHz) / IMT

PFL:LaySelWeightBand
2 RF band II (1930÷1990MHz) / PCS
3 Band III (1805÷1880MHz) / DCS
Freq Band OR
4 Band IV (2110÷2155MHz) / AWS =
5 Band V (869÷894MHz) / CLR
weight

0
6 Band VI (875÷885MHz)
7 Band VII (2620÷2690MHz) / IMT-E
8 Band VIII (925÷960MHz) / GSM
.. …
11 Band XI (1475.9÷1495.9MHz)

Company Confidential
13 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Example2: preferred band for multi-band UE

dual band UE
(U2100/U900)

Band I (2GHz) U900 UE

Cell_12 U2100 UE
Cell_11 31 Cell_13
Idle/FACH/PCH/URA

32
RAB Setup or 12 HSDPA traffic inactivity
11 HS-DSCH
CTS to DCH
cells in U900
WCEL:PFLIdentifier=1 Band VII (U900MHz)
RNC-1/PFL-1 Cell_22
LaySelWeightRSCP=0
LaySelWeightPrefLayer=0 Cell_21 Cell_23
LaySelWeightBand=100 cell_12
PreferBandForLayering=1 21 freq_priority=100 cell_13
22 freq_priority=100 Blind IFHO
cell_13
freq_priority=100 cell_22 freq_priority=0
Cell_23 freq_priority=0
CM & IFHO
cell_22 freq_priority=0
Cell_23 freq_priority=0

With Band weighting enabled, one frequency band can be prioritised (configuration on
per cell basis). Multi-band UE can be directed to cells in preferred band (if supported by
UE) during: a) CTS to DCH, b) RAB Setup via blind IFHO Or in CELL_DCH state with
HS-DSCH on: a) DL traffic inactivity trigger, b) mobility triggers via IFHO with CM
Company Confidential
14 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Frequency layer priority – RSCP weight (4/5)
Operator can prioritise IFHO to lower/higher band in case RSCP is below/above
defined thresholds. RSCP is used as indication of UE distance from source cell.
Close UE can be moved to higher band (smaller cell range), while distant UE to
lower band to improve radio link situation

RSCPscr_cell>PFL:BlindHOThrAbove a
YES
or BlindHOThrBelow≠0 BlindHOThrAbove≠0
RSCPscr_cell<PFL: BlindHOThrBelow a AND candidate’s cell freq AND candidate’s cell freq
in lower band? in higher band?
RSCP of Note: NO NO
source cell* BlindHOThrXXX=0 (not used)
NB1 a

PFL:LaySelWeightRSCP
RSCP
= OR

0
weight

* Source
Company cell – best RSCP cell
Confidential in
15 RACH intra-freq
© Nokia Siemens report
Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Example3: co-located multi-band cells, optimised usage of freq bands
High or low band preference based on UE distance/pathloss from the source cell
CPICH RSCP
source cell (f2) RAB Setup/ cell(f1) freq_priority=0
WCEL:PFLIdentifier=5 State change cell(f2)
freq_priority=100
RNC-1/PFL-5 RSCP „high”
BlindHOThrAbove=-72 Rf2 band preferred BlindHORSCPThrAbove
BlindHOThrBelow=-92 2
LaySelWeightRSCP=100 1 2 BlindHORSCPThrBelow 1
LaySelWeightPrefLayer=0 RSCP „low”
LaySelWeightBand=0 RAB Setup/ cell(f1) band preferred
State change
cell(f1)
Rf1 cell(f2) freq_priority=100
cell(f2) freq_priority=0

1 Pathloss to source/serving cell is low (P-CPICH RSCP exceeds PFL:BlindHOThrAbove). Higher frequency band
carriers are preferred (get non-zero RSCP weight; for all others the weight is zero)

2 Pathloss to source/serving cell is high (P-CPICH RSCP drops underneath PFL:BlindHOThrBelow). Lower
frequency band carriers are preferred (get non-zero RSCP weight; for all others the weight is zero)

With RSCP weight enabled, UE in locations close to source cell can be directed to
co-located cells in higher band to save radio resources. UE in locations close to cell edge
can moved to lower band to improve coverage and likely end user performance. RSCP
weight can be checked on RAB setup or state change
Company Confidential
16 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Frequency layer priority – Load weight (5/5)
The Load weight is used to avoid IFHO to more loaded cell or direct traffic to
balance the load. The weight is decided based on mean HSDPA power per User
HSDPA pwr per Unused HSPA
NRT user [W] DL pwr load lev
Enabled 16 Yes 1
Preferred low HSPA cell/layer
16 >Pwr  10 Yes 2
load: PFL:LaySelLowLoadPref
10 >Pwr  4.2 Yes 3
Disabled
4.2 >Pwr  2.2 Yes 4
Source or target cell
result or freq layer 2.2 >Pwr  1.3 Yes 5
average, depending on HSPAloadLevel
MBLB mode 1 1.3 >Pwr  0.8 Yes 6
NO low?
lowLoadPreference= 0.8 >Pwr  0.5 Yes 7
YES
0.5 >Pwr  0.23 Yes 8
1000
… … …
HSPA overload No 21

0 PFY:LaySelWeightLoad=0 load unknown or non


HSDPA cell
No 22

Load low HSPA load (1÷7)


weight
=
Not considered for Rel99
UEs (or CSoHS with AMR) PFL: +22-HSPAloadLevel  lowLoadPreference
DCH cell (source/serving) LaySelWeightLoad

Company Confidential
HSPAloadLevel
17 © NokiaisSiemens
single cell result (Blind IFHO,
Networks Layering
RU30 Featuresmodes) OrEnabling
– NetEng freq layer average
/ COO RA RDfrom same/ Grzegorz
SA NE2 carrier neighbours
Ścibior of current active set (Mobility and Inactivity modes)
RAN2172 Multi-Band Load Balancing
Blind IFHO at RAB Setup & Layering at State Change – configuration (1/2)
 Blind IFHO at RAB Setup
is enabled by WCEL:MBLBRABSetupEnabled
 Layering in State Change
is enabled by WCEL:MBLBStateTransEnabled

 Both triggers utilize the blind IFHO mechanism (w/out CM activation). The target
can be IF neighbour in same or different BTS, frequency, frequency band
 MBLB adds inter-freq RACH measurements to have target cell info before blind
HO decision. It also modifies existing SIB11/11bis/12 intra-freq RACH
measurement quantity from EcNo to RSCP
 RSCP is used as pathloss equivalence indicating UE position within a cell
 RACH IF info from UE contains SIB cell indexes (one/best per frequency) of cells
with RSCP measurements above threshold
 HO to distant cells, not defined as blind IFHO targets is avoided by setting min
required RSCP (threshold HOPI:BlindHORSCPThrTarget)
 Layering at State Change and RAN1011 (HSDPA Layering in Common
Channels) can not be activated in the same time, thus the latter is deactivated
when WCEL:MBLBStateTransEnabled
Company Confidential
18 © Nokia Siemens Networks
enabled
RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Blind IFHO candidate cells (1/2)

Configured blind IFHO candidate


the neighbour cell of current source cell, OAM enabled as blind HO target
(ADJI:BlindHOTargetCell=Enabled, max one per frequency). The configured
candidate can be also a measured candidate
Measured blind IFHO candidate
the cell which SIB index is sent in RACH IF measurements info from UE, i.e.
best measured cell (one per frequency) with RSCP above source cell
WCEL:BlindHORSCPThrTarget, i.e. „not distant” cells
 Measured candidates are suitable blind IFHO targets if their frequency
priority is non-zero due any weight other then Load, and is better then priority
of source cell frequency (both controlled by same RNC)
 Configured candidates are suitable blind IFHO targets in case UE location is
„not distant” (source RSCP above HOPI:BlindHORSCPThr, corrected by
source and candidate cells P-CPICH power difference). RSCP check can be
avoided by BTS:BlindHOIntraBTSQCheck for same sector & band cells

Company Confidential
19 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Blind IFHO - candidate cells (2/2)
Inter-freq cells exceeding BlindHORSCPThrTarget in descending
1 MBLB adds and configures in SIB11/11bis/12 the inter-freq order (the list of indexes as used in SIB11/11bis/12)
RACH measurements (new in RU30), to filter out distant cells Intra-freq RACH measurement results for current and
i.e. once exceeding allowed pathloss best neighbour cell:
Current cell, here also
cell_1 RSCP=-93dBm
Source cell (highest RSCP)
cell_2 RSCP=-104dBm
3 IF measurement indication is provided by UE in
Inter-freq RACH measurements on non-used carriers:
CELL_UPDATE or RRC Connection Request messages interFreqCellID=1 (i.e. cell_3) Measured potential
together with intra-freq RACH RSCP results interFreqCellID=2 (i.e. cell_4) target cells
3
NB2
NB1

interFreqCellID: 1 (cell_3) …
interFreqCellID: 2 (cell_4) …
interFreqReportingQuantityForRACH
..intraFreqRepQuantityRACH-FDD: 1
Idle or CELL_FACH/
..interFreqRACHRepThreshold: -95
PCH/URA-PCH
..maxReportedInterFreCellsOnRACH=8

1
Configured potential target cell
RNC-1/WBTS-1/WCEL-cell_1/ADJI-1
AdjiCI=cell_3
BlindHOTargetCell=Enabled
RNC-1/WBTS-1/WCEL-cell_1/HOPI-1 2
Inter-freq RACH measurements
BlindHORSCPThr=-92 RSCP cell_4=-94dBm < BlindHORSCPThrTarget=-95
RNC-1/WBTS-1/WCEL-cell_1 RSCP cell_3=-86dBm > BlindHORSCPThrTarget
BlindHORSCPThrTarget=-95

Blind IFHO candidates are either configured or measured IF, intra-RNC, intra/inter BTS cells. The
configured are once enabled with ADJI:BlindHOTargetCell in source cell (max one per frequency).
The measured are once reported in IF RACH measurement info, i.e. non-distant cells (with RSCP
above
Company WCEL:BlindHORSCPThrTarget). Only cells in bands supported by UE are considered
Confidential
20 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Inactivity or Mobility in CELL_DCH triggered modes (1/2)
 Inactivity triggered
is enabled by WCEL:MBLBInactivityEnabled
 Mobility triggered
is enabled by WCEL:MBLBMobilityEnabled

 Both modes use CM measurement on preferred frequency layer(a), activated


only for UE with HS-DSCH assigned (w/out CS RAB). The target HO cell can be
IF neighbour to AS cell in same or different BTS / frequency / frequency band
 Mobility MBLB triggers CM by: a) adding to active set (1A/1C) a cell with different
PFLIdentifier then used, b) removing (1B/1C) the only AS cell with PFL index
used by UE, c) SRNC relocation or d) UE fast mobility detection. UE must have
RAB combination decided by WCEL:MobilityRABComb (NRT or all RABs)
 Inactivity MBLB triggers CM on detection of HSPA traffic inactivity
 Preferred carrier is not overload* one, with IF neighbour having better then
source cell freq priority, non-zero due to any weight other then Load. Priorities
varying in Load weight only are equal, unless the source cell is in overload state
 In Mobility mode HO is started to best priority cell it exceeds serving cell EcNo by
FSMC:MBLMMobilityOffset (if not passed, check is repeated until SCC)
Company Confidential
21 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
* Load state as per RAN140 (SLBHO) or MBLM HSPA load (see Backup slides: HSPA overload detection in MBLB)
RAN2172 Multi-Band Load Balancing
Mobility triggered mode
Ec/No
HSDPA_DL compressed mode Cell_23; PFLIdentifier=4
Diffrent PFLIdentifier cell in AS becomes dominant or triggers
HO targets Rf3 1A/1C (or leaves AS with different PFLIdentifier cells)

2 2
IF cell_2x P-CPICH
2 Rf2 MBLBMobilityOffset
HS-DSCH
cell_22; 1
1 SCC if triggered PFLIdentifier=3
during MBLB Serving HSPA cell
CM triggered P-CPICH EcNo
Rf1 Rf1 on 1A
cell_11; PFLIdentifier=1 cell_21; PFLIdentifier=2 Cell_12 P-CPICH time
MBLBEnabled=enabled
MobilityRABComb=NRT Rf1, Rf2, Rf3 – same or different band

Serving cell (cell_11) RFLIdentifier is different then cell_21 added to active set (1A/1C). Mobility in serving cell is
1
enabled thus all neighbouring IF layer priorities are checks (Rf2 & Rf3). In this example both carriers are preferred for
HSDPA NRT (in PFL=1:PrefLayerHSDPANRT), thus CM is started
2 Cell_22 or cell_23 is selected for IFHO depending on which carrier has lower HSDPA load (Rf2 or Rf3). The
selected cell on highest prioritised freq layer must have quality above current serving cell
(EcNo_cell2x-EcNo_cell_11>MBLBMobilityOffset, where cell_2x is either cell_22 or cell_23), or otherwise
CM is continued and condition re-checked until fulfilled or SCC is executed or cell_21 left active set

Mobility triggered MBLB mode may be used in scenarios where neighbouring cell configuration
is different then in serving / AS cells. This for example allow to direct HSDPA connection to
better supporting freq layer/band, instead leaving in layer where channel is likely reconfigured

Company Confidential
22 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Impact on network, parameters, network design and dimensioning tools

 MBLB introduce HSPA+ inter-band handovers. It supports realization of so


far not available strategies of traffic direction and split between bands in
multi-band or multi-layer networks. For example strategy to keep HSPA
traffic in 2.1GHz and Rel99/HSDPA traffic in 850MHz
 MBLB allow to direct new CSoHSPA UEs or HSPA+ capable UE categories
to cells supporting CSoHSPA or HSPA+ features (MIMO, DC, MIMO+DC,
QAM64, CSoHSPA) as well as realize strategies to increase cell capacity
gains (for example redirect non-MIMO UEs to non-MIMO layers when
cell/layer loading is not longer low)
 MBLB adds complementary RSCP based parameters in procedures which
used EcNo based RACH measurements
 There is no RAN2172/2289 impact on existing dimensioning tools. Real time
mobility is not considered in network dimensioning or planning. The feature
may closer to optimal distribute traffic between cells with different capability
to fit to UE capability and used service. This is however already considered
in network dimensioning thus no impact.

Company Confidential
23 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
Backup Slides
Blind IFHO (RAN2289)

Company Confidential
24 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
Blind IFHO decision diagram
NO
Any IF candidate exist Is selected cell YES
A
(neighbour configured for Blind a measured candidate?
IFHO or sent in IF RACH report)? NO

YES NO Is selected cell


a configured candidate?
FOR ECH candidate cell YES
CHECK freq layer priority1) Is sector&band same3) YES
BUILD list in descending order a as source cell OR priority A

a IFHO at RAB Setupa a greater due to RSCP?


Or Layering FACHDCH NO
NO Any cell higher a NO YES
Layering:
URA/PCH DCH
Is quality check4) passed? A
prioritised then source?
B a
YES
a NO Is RNC_ID & PLMN_ID
Select next best candidate cell same as source cell?
with highest layer priority YES

Start Blind IFHO


Is selected cell load/ YES to selected cell
B
HSPA load exceeded?
NO
1) Cells on carriers with priority>0 due to Load weight only are not considered
a
2) Applies to Layering in State Change PCH/URA-PCH to DCH:
URA/PCH to DCH & A PLY:LaySelWeightRSCP>0 & PLY:BlindHORSCPThrAbove≠0 &
No MBLB YES PLY:BlindHORSCPThrAbove≠0
RSCP weight>0 & low,
Blind IFHO 3) And blind IFHO neighbour (ADJI:BlindHOTargetCell) set w/out quality
high threshold set2) check, i.e. WBTS:BlindHOIntraBTSQCheck=1
NO 4) RSCPsource_cell–HOPI:BlindHORSCPThr
Company Confidential
25 © Nokia Siemens Networks
PtxPrimaryCPICH
RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior src_cell
–ADJI:AdjiCPICHTxPwr
RAN2172 Multi-Band Load Balancing
MBLB Intra and Inter-freq RACH measurement configuration
 MBLB configures P-CPICH RSCP based IF RACH measurements
 Inter-freq RACH measurement configuration can be read by >=3GPP rel.6 UEs
from SIB11/11bis or 12
 MBLB requires that existing intra-freq RACH measurement quantity is also
changed to RSCP

SIB11/11bis/12 intra and inter-freq RACH meas


...
-.............intraFreqReportingQuantityForRACH
-................sfn-SFN-OTD-Type: 0 ( noReport)
-................modeSpecificInfo:- fdd
1 (cpich_rscp) via RACHIntraFreqMesQuant
-................intraFreqRepQuantityRACH-FDD: 0 ( cpich_EcN0) WCEL parameter

-................maxReportedCellsOnRACH: 1 ( currentCell) 2 (current cell+best neighbour), if MBLB active

-.............interFreqReportingQuantityForRACH RACH inter-freq measurements added


(3GPP Rel6 UEs, 25.331)
-................modeSpecificInfo:- fdd configured for P-CPICH RSCP
1 (cpich_rscp) via RACHInterFreqMesQuant
-................intraFreqRepQuantityRACH-FDD: 1 ( cpich_RSCP) WCEL parameter
-................interFreqRACHRepThreshold: -95 configured via BlindHORSCPThrTarget
WCEL parameter
-................maxReportedInterFreCellsOnRACH: 8
...
Company Confidential
26 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
Backup Slides
Example configuration with mixed preferences
This example is to show that mixing of different preference objects (PFLIdentifiers) in same geographical area is possible
and allow to gain additional HO targets. However one need to remember that it is an easy way to create LOOPING which
cause ping pong HOs between layers. Therefore as long as scenario can be implemented using one common preference
object (same PFLIdentifier) mixing shall be avoided

Company Confidential
27 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
Example4: selecting best frequency/cells for UE capabilities / RAB
RNC-1/PFL-1
LaySelWeightRSCP=0
LaySelWeightPrefLayer=100
cell_31 freq_priority=0 cell_31 freq_priority=0
LaySelWeightBand=0
cell_12 freq_priority=0 cell_22
PrefLayerMIMONRT=RF3
cell_32 freq_priority=0 freq_priority=100
PrefLayerxxxAMR=RF1
cell_22 cell_32 freq_priority=0
PrefayerHSDPANRT=RF2 23
freq_priority=100 CTS to DCH cell_222freq_priority=0
PrefLayerR99xxx=RF1 Idle/FACH/ PCH/URA 4
cell_21 (NRT RAB) FACH
freq_priority=100 13 AMR or NRT RAB Setup/
14 CTS to DCH
RNC-1/PFL-2
LaySelWeightRSCP=0
33 RF3, band A
LaySelWeightPrefLayer=100 Cell_31: Cell_32:
LaySelWeightBand=0 PFLIdentifier=1 Cell_21 or cell_22 depending PFLIdentifier=2
PrefLayerMIMONRT=RF3 on which has better RSCP
PrefLayerHSDPAAMR=RF1 cell_21 RSCP > BlindHOThr And 31
PrefLayerR99xxx=RF1 cell_32 RSCP < BlindHOThrTarget MIMO UE
34
AMR RAB Setup/ Idle/FACH/ PCH/URA R99 UE
RNC-1/PFL-3 AMR in NRT/FACH (multirab)
LaySelWeightLoad=100 12 NRT RAB Setup/
LaySelWeightRSCP=0 11 CTS to DCH HSDPA UE
LaySelWeightPrefLayer=100
LaySelWeightBand=0
PrefLayerMIMONRT=RF3
RF2,band A
Cell_21: Cell_22:
PrefLayerHSDPANRT=RF2, 24 PFLIdentifier=2 21 PFLIdentifier=2
RF3 Cell_22 or cell_32 depending
22 cell_21 freq_priority=0 34 on which HSDPA load is lower
32 cell_11 freq_priority=0
RNC-1/WBTS-1/WCEL-cell_21/ADJI-1 cell_21 freq_priority=0
cell_31 Idle/FACH/ PCH/URA
AdjiCI=cell_31 cell_11
BlindHOTargetCell=Enabled freq_priority=100 freq_priority=100 NRT RAB Setup/
cell_12 cell_32 14 CTS to DCH
RNC-1/WBTS-2/WCEL-cell_31/ADJI-1
AdjiCI=cell_22 freq_priority=100 freq_priority=100
RF1, band A
BlindHOTargetCell=Enabled cell_31 freq_priority=0
RNC-1/WBTS-2/WCEL-cell_32/ADJI-2 Cell_11: PFLIdentifier=3 Cell_12: PFLIdentifier=3
AdjiCI=cell_32
Company Confidential
28 © Nokia Siemens Networks
BlindHOTargetCell=Enabled RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
HSPA overload detection in MBLB

Company Confidential
29 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
HSPA loaded cell indication (1/3)

In MBLB procedures RNC checks that candidate cell(s) are not HSPA
loaded. HSPA load state is decided based on results of the following
checks:

 HSDPA used power and average user bit rate


 HSUPA used power and average user bit rate
 Number of HSDPA users
 HSUPA resource status

If any element indicates that resources are exhausted, a cell is turned


into „HSPA loaded” state

Company Confidential
30 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
HSPA loaded cell indication (2/3)

1) HSDPA used power and average user bit rate


In case both: a) unused DL power AND b) HSDPA bit rate per User are below
min thresholds, the cell is considered HSPA loaded
a) Unused DL pwr < WCEL:HSLoadStateHSDOffset
for more then time to trigger: WCEL:DLLoadStateTTT
b) HSDPA Thr per HSDPA NRT CELL_DCH User < WCEL:HSLoadStateHSDBRLimit

2) HSUPA used power and average bit rate


In case both: a) unused UL noise rise AND b) HSUPA bit rate per User are
below min thresholds, the cell is considered HSPA loaded
a) maxAllowed NoiseRise - current NoiseRise* < WCEL:HSLoadStateHSUOffset
for more then time to trigger: WCEL:ULLoadStateTTT
* if case of UL Interference Cancellation enabled, condition a) must be fulfilled for both original and residual measurements

b) HSUPA Thr per HSUPA NRT CELL_DCH User < WCEL:HSLoadStateHSUBRLimit

Company Confidential
31 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
HSPA loaded cell indication (3/3)

3) Number of HSDPA users


In case number current Users exceeds max allowed in scheduler, all cells
served by this scheduler are considered HSPA loaded

4) HSUPA resource status


In case the averaged HSUPA Resource Status reported by BTS exceeds given
threshold, then cell is considered HSPA loaded. HSUPA resource status is an
integer value from 1 to 6. Highest status number indicate HSUPA base-band
resource shortage and are mapped to value 1. Lowest status numbers are
meaningless for HSUPA load evaluation, thus mapped to value 0. The mapped
values are averaged („running” average)

avgHSUPA Resource Status  WCEL:HSLoadStateHSUResThr

Company Confidential
32 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
New parameters (MBLB and
in procedures effected by RAN2289)

Preliminary info, subject to change (!)

Company Confidential
33 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (1/7)
Abbreviated name MOC Range Description
disabled This parameter indicates whether the neighbor cell is defined as a target cell for
BlindHOTargetCell ADJI enabled inter-frequency blind handover.
-6...6dBm Multi-Band Load Balancing due to mobility can be done when the quality criteria
MBLBMobilityOffset FMCI defined with this parameter is met.
all, NRT This parameter defines the RAB combinations for which Multi-Band Load
MBLBMobilityRABComb FMCI Balancing due to mobility is allowed.
0...60 s Penalty time for a WCDMA neighbour cell that has rejected a resource request
AdjiPenaltyTimeNCHO HOPI of a handover attempt.

BlindHORSCPThr HOPI -115...-25 dBm This parameter determines the minimum required CPICH RSCP level which the
RACH measurement result of the source cell must achieve before the blind
inter-frequency handover is possible
BlindHORSCPThrAbove PFL -115...-25 dBm This parameter determines the minimum required CPICH RSCP level which the
RACH measurement result of the source cell must achieve before the blind
inter-frequency handover can be done because of a high RSCP value
BlindHORSCPThrBelow PFL -115...-25 dBm This parameter determines the maximum allowed CPICH RSCP level which the
RACH measurement result of the source cell must not exceed before the blind
inter-frequency handover can be done because of a low RSCP value.
LaySelLowLoadPref PFL disabled, This parameter defines whether extra weight is given to HSPA load in layer
enabled selection for cells where HSPA load is low.
LaySelWeightBand PFL 1...10000 This parameter defines how much weight the band capability has in layer
selection.

LaySelWeightLoad PFL 1...10000 Parameter defines how much weight HSPA load has in layer selection.

LaySelWeightPrefLayer PFL 1...10000 This parameter defines how much weight the preferred layer definitions have in
Company Confidential layer selection.
34 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (2/7)
Abbreviated name MOC Range Description
This parameter defines how much weight RSCP below or above the threshold
LaySelWeightRSCP PFL 1...10000 has in layer selection.
This parameter defines the preferred layers for HSDPA 64QAM capable UE that
PrefLayer64QAMAMR PFL 0...16383 has only an AMR RAB allocated.
This parameter defines the preferred layers for HSDPA 64QAM capable UE that
PrefLayer64QAMAMRNRT PFL 0...16383 has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA 64QAM capable UE that
PrefLayer64QAMAMRNRT PFL 0...16383 has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA 64 QAM capable UE
PrefLayer64QAMNRT PFL 0...16383 that has only NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA 64 QAM capable UE
PrefLayer64QAMStr PFL 0...16383 that has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for CS voice over HSPA capable UE
PrefLayerCSHSAMRNRT PFL 0...16383 that has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
PrefLayerCSHSNRT PFL 0...16383 This parameter defines the preferred layers for CS voice over HSPA capable UE
that has only NRT RAB(s) allocated.
PrefLayerCSHSStr PFL 0...16383 This parameter defines the preferred layers for CS voice over HSPA capable UE
that has a streaming RAB and 0...3 NRT RAB(s) allocated.
PrefLayerDCHSDAMR PFL 0...16383 This parameter defines the preferred layers for Dual Cell HSDPA capable UE
that has only an AMR RAB allocated.
PrefLayerDCHSDAMRNRT PFL 0...16383 This parameter defines the preferred layers for Dual Cell HSDPA capable UE
that has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated
PrefLayerDCHSDAMRNRT PFL 0...16383 This parameter defines the preferred layers for Dual Cell HSDPA capable UE
that has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
Company Confidential
35 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (3/7)
Abbreviated name MOC Range Description
This parameter defines the preferred layers for CS voice over HSPA capable UE
PrefLayerCSHSAMRNRT PFL 0...16383 that has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for Dual Cell HSDPA capable UE
PrefLayerDCHSDStr PFL 0...16383 that has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for UE that supports both Dual Cell
PrefLayerDCMIAMR PFL 0...16383 HSDPA and MIMO and that has only an AMR RAB allocated.
This parameter defines the preferred layers for UE that supports both Dual Cell
HSDPA and MIMO and that has an AMR RAB, 0...1 streaming RAB, and 1...3
PrefLayerDCMIAMRNRT PFL 0...16383 NRT RAB(s) allocated.
This parameter defines the preferred layers for Dual Cell HSDPA capable UE
PrefLayerDCHSDNRT PFL 0...16383 that has only NRT RAB(s) allocated.
This parameter defines the preferred layers for UE that supports both Dual Cell
PrefLayerDCMINRT PFL 0...16383 HSDPA and MIMO and which has only NRT RAB(s) allocated.
This parameter defines the preferred layers for Dual Cell HSDPA capable UE
PrefLayerDCHSDStr PFL 0...16383 that has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for Dual Cell HSDPA capable UE
PrefLayerDCHSDStr PFL 0...16383 that has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for F-DPCH capable UE that has
PrefLayerFDPCHAMR PFL 0...16383 only an AMR RAB allocated.
This parameter defines the preferred layers for F-DPCH capable UE that has an
PrefLayerFDPCHAMRNRT PFL 0...16383 AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for F-DPCH capable UE that has
PrefLayerFDPCHNRT PFL 0...16383 only NRT RAB(s) allocated
This parameter defines the preferred layers for F-DPCH capable UE that has a
PrefLayerFDPCHStr
Company Confidential PFL 0...16383 streaming RAB and 0...3 NRT RAB(s) allocated.
36 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (4/7)
Abbreviated name MOC Range Description
This parameter defines the preferred layers for fast moving UE with AMR RAB
PrefLayerFastMovUECS PFL 0...16383 or other CS RAB, 0...1 streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for fast moving UE with 0...3 PS
PrefLayerFastMovUEPS PFL 0...16383 NRT RAB(s) and 0...1 PS streaming RAB allocated.
This parameter defines the preferred layers for HSDPA capable UE that has
PrefLayerHSDPAAMR PFL 0...16383 only an AMR RAB allocated.
This parameter defines the preferred layers for HSDPA capable UE that has an
PrefLayerHSDPAAMRNRT PFL 0...16383 AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA capable UE that has
PrefLayerHSDPANRT PFL 0...16383 only NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA capable UE that has a
PrefLayerHSDPAStr PFL 0...16383 streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSPA (HSDPA + HSUPA)
PrefLayerHSPAAMR PFL 0...16383 capable UE that has only AMR RAB allocated.
This parameter defines the preferred layers for HSPA (HSDPA + HSUPA)
capable UE that has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s)
PrefLayerHSPAAMRNRT PFL 0...16383 allocated.
This parameter defines the preferred layers for HSPA (HSDPA + HSUPA)
PrefLayerHSPANRT PFL 0...16383 capable UE that has only NRT RAB(s) allocated.
This parameter defines the preferred layers for HSPA (HSDPA + HSUPA)
PrefLayerHSPAStr PFL 0...16383 capable UE that has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA MIMO capable UE that
PrefLayerMIMOAMR PFL 0...16383 has only an AMR RAB allocated
This parameter defines the preferred layers for HSDPA MIMO capable UE that
PrefLayerMIMOAMRNRT
Company Confidential PFL 0...16383 has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
37 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (5/7)
Abbreviated name MOC Range Description
This parameter defines the preferred layers for HSDPA MIMO capable UE that
PrefLayerMIMONRT PFL 0...16383 has only NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA MIMO capable UE that
PrefLayerMIMOStr PFL 0...16383 has a streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for R99 capable UE that has only an
PrefLayerR99AMR PFL 0...16383 AMR RAB allocated.
This parameter defines the preferred layers for R99 capable UE that has an
PrefLayerR99AMRNRT PFL 0...16383 AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for R99 capable UE that has only
PrefLayerR99NRT PFL 0...16383 NRT RAB(s) allocated.
This parameter defines the preferred layers for R99 capable UE that has a
PrefLayerR99Str PFL 0...16383 streaming RAB and 0...3 NRT RAB(s) allocated.
This parameter defines the preferred layers for HSDPA MIMO capable UE that
PrefLayerMIMOAMRNRT PFL 0...16383 has an AMR RAB, 0...1 streaming RAB, and 1...3 NRT RAB(s) allocated.
This parameter defines the preferred frequency band under the RNC.
PreferBandForLayering RNC 0...51
This parameter defines time to trigger value to activate and deactivate UL
ULLoadStateTTT RNC 0...10 s loaded state and HSPA load state.
This parameter defines if the inter-frequency blind handover can be done
without quality check between two frequency layers inside one BTS if
Qual check, No frequencies are in same band and the source and target cells are in same
BlindHOIntraBTSQCheck WBTS Qual check sector
This parameter determines the minimum required CPICH EcNo level that the
inter-frequency RACH measurement result of the target cell must exceed before
BlindHOEcNoThrTarget WCEL -24...0 dBm the blind inter-frequency handover is possible
Company Confidential
38 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (6/7)
Abbreviated name MOC Range Description
This parameter determines the minimum required CPICH RSCP level that the
inter-frequency RACH measurement result of the target cell must exceed before
BlindHORSCPThrTarget WCEL -115...-25 dBm the blind inter-frequency handover is possible
This parameter defines the threshold for CPICH RSCP to determine whether
CPICHRSCPSRBMapRRC WCEL -115...-25 dBm RRC connection setup is allowed to be performed on common channels (CCH).
This parameter defines the threshold value which is compared to the CPICH
CUCRSCPThreshold WCEL -115...-25 dBm RSCP measurement value received from the UE in the Cell Update message.
This parameter defines time to trigger value to activate and deactivate HSPA
DLLoadStateTTT WCEL 0...10 s load state due to DL load.
Disabled, Enables / disables the use of the Directed RRC connection setup for the HSDPA
DirectedRRCForHSDPALayerEnabled WCEL Enabled layer in the cell.
This parameter defines a HSDPA bit rate per NRT user in the cell under which
HSLoadStateHSDBRLimit WCEL 0...248 kpbs the cell is set to HSPA load state if transmitted wide band power is high enough.
This parameter defines an offset to maximum transmitted wide band target
HSLoadStateHSDOffset WCEL -3...3 dB power that is used for HSPA load state checking.
0...248 kpbs, This parameter defines an E-DCH bit rate per NRT user in the cell under which
HSLoadStateHSUBRLimit WCEL step 2 kpbs the cell is set to HSPA load state if received wide band power is high enough.
This parameter defines an offset to maximum received wide band target power
HSLoadStateHSUOffset WCEL -3...3 dB that is used for HSPA load state checking.
HSLoadStateHSUResThr WCEL 0.3...1 This parameter defines a threshold on which HSUPA resource indications can
set the cell to HSPA load state
MBLBInactivityEnabled WCEL disabled, This parameter defines if Multi-Band Load Balancing is enabled when inactivity
enabled is detected in Cell_DCH state.

Company Confidential
39 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters / preliminary info – list (7/7)

Abbreviated name MOC Range Description


disabled, This parameter defines if Multi-Band Load Balancing is enabled due to mobility
MBLBMobilityEnabled WCEL enabled in Cell_DCH state.
disabled, This parameter defines whether Multi-Band Load Balancing is enabled in the
MBLBRABSetupEnabled WCEL enabled RAB setup phase.
disabled, This parameter defines if Multi-Band Load Balancing is enabled in state
MBLBStateTransEnabled WCEL enabled transition to Cell_DCH state.
This parameter defines the parameter set (PFL object) which controls the
PFLIdentifier WCEL 1...50 preferred frequency layer definitions.
This parameter defines the inter-frequency measurement quantity for RACH
RACHInterFreqMesQuant WCEL EcNo, RSCP measurements.
This parameter defines the intra-frequency measurement quantity for RACH
RACHIntraFreqMesQuant WCEL EcNo, RSCP measurements.
MBLBInactivityEnabled WCEL disabled, This parameter defines if Multi-Band Load Balancing is enabled when inactivity
enabled is detected in Cell_DCH state.
MBLBMobilityEnabled WCEL disabled, This parameter defines if Multi-Band Load Balancing is enabled due to mobility
enabled in Cell_DCH state.

Company Confidential
40 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New parameters in procedures effected by Blind IFHO (RAN2289)

With MBLB activated the decision whether:


 SRB can be setup on CCH (RAN1797) is based on new RSCP based
threshold WCEL:CPICHRSCPSRBMapRRC (w/out MBLB the RACH EcNo
based measurements are configured and WCEL:CPICHEcNoSRBMapRRC
used instead)
 SRB is mapped to HS-DSCH (RAN1201) is based on new RSCP based
threshold WCEL:CPICHRSCPThreSRBHSDPA (w/out MBLB the RACH
EcNo based measurements are configured and
WCEL:CPICHECNOSRBHSPA used instead)
 E-DCH can be used in CELL_DCH after transitions from FACH/URA-PCH
or CELL_PCH (RAN981/RAN1470) is based on new RSCP based threshold
WCEL:CPICHRSCPThreEDCH2MS (w/out MBLB the RACH EcNo based
measurements are configured and WCEL:CPICHECNOThreEDCH2MS
used instead)
 UE can be transferred directly from CELL_PCH / URA_PCH to CELL_DCH
is based on new RSCP based threshold WCEL:CUCRSCPThreshold
(w/out MBLB the RACH EcNo based measurements are configured and
WCEL:CUCEcNoThreshold used instead)
Company Confidential
41 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
MBLB counters

Preliminary info, subject to change (!)

Company Confidential
42 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
New MBLB and Blind IFHO related counters (1/4)

Counter Name Counter ID Description


ATTEMPTED INTER-BTS LAYER M1006C240 The number of attempted inter-BTS layer changes in PCH/FACH to Cell_DCH
CHANGES IN PCH/FACH TO DCH transition.
SUCCESSFUL INTER-BTS LAYER M1006C241 The number of successful inter-BTS layer changes in PCH/FACH to
CHANGES IN PCH/FACH TO DCH Cell_DCH transition.
FAILED INTER-BTS LAYER CHANGES M1006C242 The number of failed inter-BTS layer changes in PCH/FACH to Cell_DCH
IN PCH/FACH TO DCH transition.
MBLB IFHO ATTEMPTS WITH UE M1008C296 The number of Multi-Band Load Balancing (MBLB) IFHO attempts with UE
BAND CAPA band capability as highest trigger weight.
MBLB IFHO ATTEMPTS WITH SERVICE M1008C297 The number of MBLB IFHO attempts with service and UE feature capability as
AND UE FEATURE CAPA highest weight.
MBLB IFHO ATTEMPTS WITH M1008C298 The number of MBLB IFHO attempts with RSCP as highest trigger
RSCP weight.
MBLB IFHO ATTEMPTS WITH M1008C299
The number of MBLB IFHO attempts with load as highest weight.
LOAD
SUCCESSFUL MBLB IFHO M1008C300 The number of successful MBLB IFHOs. This is a common success
counter for attempt counters M1008C296-C299.

FAILED MBLB IFHO DUE TO M1008C301 The number of failed MBLB IFHOs due to UTRAN. This is a common
UTRAN failure counter for attempt counters M1008C296-C299.
FAILED MBLB IFHO DUE TO UE M1008C302 The number of failed MBLB IFHOs due to negative UE response. It is
NACK a common failure counter for attempt counters M1008C296-C299

FAILED MBLB IFHO DUE TO UE M1008C303 The number of failed MBLB IFHOs due to UE lost. It is a common
LOST failure counter for attempt counters M1008C296-C299
MBLB IFHO ATTEMPTS DUE FAST M1008C304 The number of Multi-Band Load Balancing (MBLB) IFHO attempts due
MOVING UE to fast moving UE.
Company Confidential
43 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New MBLB and Blind IFHO related counters (2/4)

Counter Name Counter ID Description


NOT STARTED MBLB IFHO DUE M1008C305 The number of times when no cell good enough was found for Multi-
TO NO CELL GOOD ENOUGH Band Load Balancing (MBLB) IFHO

RRC CPICH ECNO CLASS 0 M1033C0 The number of CPICH EcNo values reported by the Ues in which the
value is inside Class 0 range (CPICH EcNo < -18 dB).
RRC CPICH ECNO CLASS 1 M1033C1 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 1 range (-18 dB <= CPICH EcNo < -16 dB).
RRC CPICH ECNO CLASS 2 M1033C2 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 2 range (-16 dB <= CPICH EcNo < -14 dB).
RRC CPICH ECNO CLASS 3 M1033C3 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 3 range (-14 dB <= CPICH EcNo < -12 dB).

RRC CPICH ECNO CLASS 4 M1033C4 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 4 range (-12 dB <= CPICH EcNo < -10 dB).
RRC CPICH ECNO CLASS 5 M1033C5 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 5 range (-10 dB <= CPICH EcNo < -8 dB).
RRC CPICH ECNO CLASS 6 M1033C6 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 6 range (-8 dB <= CPICH EcNo < -6 dB).

RRC CPICH ECNO CLASS 7 M1033C7 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 7 range (-6 dB <= CPICH EcNo < -4 dB).
RRC CPICH ECNO CLASS 8 M1033C8 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 8 range (-4 dB <= CPICH EcNo < -2 dB).

RRC CPICH ECNO CLASS 9 M1033C9 The number of CPICH EcNo values reported by the UEs in which the
value is inside Class 9 range (-2 dB <= CPICH EcNo).
RRC CPICH RSCP CLASS 0 M1033C10 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 0 range (CPICH RSCP < -113 dBm).
Company Confidential
44 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New MBLB and Blind IFHO related counters (3/4)

Counter Name Counter ID Description


RRC CPICH RSCP CLASS 1 M1033C11 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class1 range (-113dBm<=CPICH RSCP<-110dBm)

RRC CPICH RSCP CLASS 2 M1033C12 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 2 range (-110dBm<=CPICH RSCP<-107 dBm)

RRC CPICH RSCP CLASS 3 M1033C13 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 3 range (-107dBm<=CPICH RSCP<-104 dBm)
RRC CPICH RSCP CLASS 4 M1033C14 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 4 range (-104dBm<=CPICH RSCP<-101 dBm)
RRC CPICH RSCP CLASS 5 M1033C15 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 5 range (-101 dBm <= CPICH RSCP < -98 dBm).
RRC CPICH RSCP CLASS 6 M1033C16 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 6 range (-98 dBm <= CPICH RSCP < -95 dBm).

RRC CPICH RSCP CLASS 7 M1033C17 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 7 range (-95 dBm <= CPICH RSCP < -92 dBm).
RRC CPICH RSCP CLASS 8 M1033C18 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 8 range (-92 dBm <= CPICH RSCP < -89 dBm).
RRC CPICH RSCP CLASS 9 M1033C19 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 9 range (-89 dBm <= CPICH RSCP < -86 dBm).

RRC CPICH RSCP CLASS 10 M1033C20 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 10 range (-86 dBm <= CPICH RSCP < -80 dBm).
RRC CPICH RSCP CLASS 11 M1033C21 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 11 range (-80 dBm <= CPICH RSCP < -74 dBm).

RRC CPICH RSCP CLASS 12 M1033C22 The number of CPICH RSCP values reported by the UEs in which the
value is inside Class 12 range (-74 dBm <= CPICH RSCP < -68 dBm).
Company Confidential
45 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
New MBLB and Blind IFHO related counters (4/4)

Counter Name Counter ID Description


M1033C23 The number of CPICH RSCP values reported by the UEs in which the
RRC CPICH RSCP CLASS 13
value is inside Class 13 range (-68 dBm <= CPICH RSCP < -62 dBm).

M1033C24 The number of CPICH RSCP values reported by the UEs in which the
RRC_CPICH_RSCP_CLASS_14
value is inside Class 14 range (-62 dBm <= CPICH RSCP < -56 dBm).

M1033C25 The number of CPICH RSCP values reported by the UEs in which the
RRC_CPICH_RSCP_CLASS_15
value is inside Class 15 range (-56 dBm <= CPICH RSCP < -50 dBm).

M1033C26 The number of CPICH RSCP values reported by the UEs in which the
RRC_CPICH_RSCP_CLASS_16
value is inside Class 16 range (-50 dBm <= CPICH RSCP).

Company Confidential
46 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
Load, service or capability based handovers &
redirections in RAN sw prior RU30

Company Confidential
47 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO NWS LTE RA E2E SA NetEng
RAN2172 Multi-Band Load Balancing
Load/capability based redirections/handovers – situation till RU30 (1/3)
1) Capability based redirection at connection setup, between cells
of same sector (max one HSPDA cell) – since RAS05
Directed RRC connection set-up HSDPA (DRRC for HSDPA Layer – RAN502)
 HSDPA capable UEs are moved from non HSPA to HSDPA cell
 Non HSPA capable UEs are moved from HSPA to non HSPA cell (no target cell
load is considered)
2) Capability based redirection at connection setup Or state change
FACH->DCH, between cells of same sector (load balancing if more
HSPA cells) – since RAS06
Enhancements for DRRC for HSDPA Layer (HSPA layering for UE- RAN1011)
HO is applied for predefined RAB type/class requested by UE
 HSDPA capable UEs are moved from non HSPA cell to one of available
HSDPA, assuring load sharing
 HSDPA capable UEs may be moved between HSPA capable cells to balance
the load
 Load balancing is not used for HSUPA capable UEs, if already on HSPA cell
 Non HSPA capable UEs are moved from HSPA to non HSPA cells, if latter not
48
extensively loaded
Company Confidential
© Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
Load/capability based redirection/handover – situation till RU30 (2/3)
3) Capability Based IFHO in CELL_DCH to HSPA cell on same/different
sector in same/different NodeB/RNC/band/system, w/out balancing
the load of HSPA layer – since RU10
HSPA Capability Based HO (HSCAHO– RAN1596)
 Push HSPA UEs to HSPA cells: HSPA capable UEs with DCH RAB
combinations defined by Operator are checked periodically in non HSPA cells
and if considered by HSCAHO in given period, may be handed over to IF HSPA
cells
 Push HSPA UEs to i-HSPA cells: UE with HSDPA service in HSDPA capable cell
may be triggered for HO to i-HSPA cell, when UE DL traffic inactivity is detected
(if used, HSUPA is CTS to DCH prior to HSCAHO)
 HSPA layers can be prioritized in HSCAHO: if more candidate HSDPA
carriers/layers are available, the order in which carriers are considered/
measured during HSCAHO may be influenced by configurable priorities
 HSCAHO initiated to cell in other RNC or system (I-HSPA) are combined with
SRNC relocation
 No check of target cell load is done by SRNC
 HSCAHO utilize HSPA IFHO (RAN1276/RU10): e.g. HSCAHO handover initiate
49
from DCH in source
Company Confidential
© Nokia Siemens Networks
cell to HSDPA/HSPA in target cell
RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior
RAN2172 Multi-Band Load Balancing
HSPA load/capability based redirection/handover – situation till RU20 (3/3)

4) Load and Service based HO (SLHO - RAN140) – since RAS5.1


 Balance the load between WCDMA or WCDMA and GSM
 The connection with suitable DCH RAB classes are moved to other
frequency layers (IFHO) or to GSM (ISHO) unconditionally (service based
HO) or when source cell load threshold is exceeded and connection is not
in preferred layer/RAT (load based HO)
 Few independent load indicators may be activated for detection of cell
overload state: uplink received total wideband power and throughput, DL
transmitted code power, NRT rejection rate, DL spreading codes usage,
HW resource usage (BB,AAL2)
 When overload is detected based on any enabled load indicator, the RNC
starts load based HO procedure, searching for candidate connections for
SLHO. It is performed to preferred RAT/WCDMA layer (micro/macro)
defined per each RAB category.
 The definition and selection of target system may be done on single DCH
RAB class basis (e.g. CS voice to GSM, PS NRT to WCDMA macro …).
Suitable RAB combination for HCSAHO are not considered by SLHO if
HCSAHO is enabled in the cell (RU10 extension)
Company Confidential
50 © Nokia Siemens Networks RU30 Features – NetEng Enabling / COO RA RD SA NE2 / Grzegorz Ścibior