MBLB Design - Presentation

Kirsi Teräväinen NPO Capability Creation

26.11.2012 v3

For internal use

1 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Introduction

NSN have several layering features that can be used to balance HSDPA load between carriers.

1. UMTS carriers in same band, having same coverage area and configured under common sector id
• Directed RRC Connection Setup features
• HSPA layering for UE’s in Common Channel
• Multi-band Load Balancing – MBLB
• HSDPA load balancing is included to MBLB Blind HO and MBLB state transition features
2. UMTS carriers in different band, having different coverage areas or BTS’s
• Multi Band Load Balancing – MBLB
• HSDPA load balancing is included to MBLB Blind HO and MBLB state transition features
• (In certain conditions HSPA layering for UE’s in common channel can be used between bands also, require same
sector id and meant to be used between cells with same coverage areas – not recommended)

Additionally idle mode settings & different type of IFHO can be used move UE’s between bands/carriers, but
HSDPA load balancing between carriers is done either with DRRC or MBLB.

For internal use

2 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Introduction

MBLB has 4 different triggers which all can be enabled

separately.
MBLB Blind HO and MBLB state transition features can Band 1 F1-HSPA
be used to balance HSDPA load between 3G cells. MBLB actions
• Similar Configuration can be used
• Between 3G cells belonging to same frequency band Band 2 F2-HSPA
• Between 3G cells belonging to different frequency bands

• This slide set present case where MBLB Blind HO

and MBLB State transition features are enabled. Band 1 F1-HSPA
• Idle mode camping is not biasing any frequency band.
UE’s are always camping on “best radio” MBLB actions
• If earlier setup is done without neighbour definitions Band 1 F2-HSPA
between cells (e.g. DRRC used) those need to be created

For internal use

3 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Blind HO and MBLB State Transition - Activation

• Blind IFHO in RAB Setup Phase is activated with parameter

MBLBRABSetupEnabled (WCEL)
• Blind IFHO to the target cell in the preferred carrier or band is
triggered during RAB setup phase
– First RAB setup is done for the UE
– AMR RAB Setup is done for the UE when it already has a NRT RAB (s)
MBLBRABSetupMultiRAB (WCEL)
– Feature require that adji definitions are done

• MBLB Layering in State transition Phase is activated with parameter

MBLBStateTransEnabled (WCEL) If blind Ho is triggered, new frequency info is included
to RB setup message and UE is moved to other
• Layering in state transition the target cell in the preferred carrier or frequency with RB setup complete message
band is triggered during State transition
– State transitions from CELL_FACH, URA_PCH or CELL_PCH F2
– Does not include transition from RRC Idle mode
– Feature require that Adji definitions are done
F1
For internal use

4 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Blind HO and MBLB State Transition - Activation

• Intra frequency RACH measurements quantity must Example of SIB11/11bis/12 intra and inter-freq RACH
be changed from EcNo to RSCP with parameter measurement when MBLB activated and measurement
RACHIntraFreqMesQuant (WCEL) quantity is changed to RSCP.

– This will impact other features – first trials show no

negative impact
 HSUPA 2ms TTI, SRB on HSPA, Common Channel
Setup and Fast Call setup from Cell_PCH

• Inter-frequency measurement are added for RACH Defined with parameter BlindHORCSPThrTarget
– Target cell measurements can be used instead of totally Intra - UE measures and reports RSCP value from current cell and
blind HO for Rel6 or Newer UEs. (optional UE feature) best neighbour cell to RNC in RRC Connection Request and Cell
– Inter-frequency measurements can be configured using Update messages
RACHInterFreqMesQuant (WCEL) Parameter Inter - UE does not report the CPICH EcNo or CPICH RSCP but
only the indication if the measured value is over the threshold. This
is optional UE feature, currently number of UE’s supporting is
increasing.

For internal use

5 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Blind HO and MBLB State Transition – Target Cell

Target cell for MBLB Blind HO and MBLB State Transition can be any Intra-RNC Inter- frequency neighbor
cell which is not in the load state. Target cell can be within same or different BTS/within same or different
UMTS bands.
Possible target cells for MBLB can be identified with two
complementary methods.
• Based on source cell measurements:
– Possible target cell is defined with BlindHOTargetCell (ADJI) BlindHOTargetCell

parameter. Only one target cell per frequency can be defined.

• Based on target cell measurements:
– Cell is possible target cell for blind HO if that cell was included to
inter-frequency measurement results on RACH (even though
blind HO to that cell is not enabled from source cell with • One possible target cell per frequency for the UE’s
BlindHOTargetCell parameter) and is from same RNC than not supporting Inter-frequency measurements on
source cell. RACH.
• For the UE’s supporting inter-frequency
Note! The cell, which is in the frequency band that UE does not measurements, the target cell can be any Inter-
support, cannot be selected as a target cell. frequency cell included to RACH measurements

For internal use

6 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Blind HO and MBLB State Transition - Optimization

If source and target cells are having different coverage areas (e.g. due the different antenna alignment or
power settings)
• There may be need to optimise (tighten) Source/Target cells thresholds to ensure that Blind HO is done
in the areas with overlapping coverage
• BlindHORSCPThr (HOPI) is applicable to UE which do not provide measurement from the target cell (RACH
interfrequency measurement not supported by UE or not available).
• BlindHORSCPThrTarget (WCEL) or BlindHOEcNOThrTarget (WCEL) is applicable to UE which provide
measurement from the target cell. Which one is used depend on value of RACHInterFreqMesQuant parameter.
.
Parameter Object Default Value Comment
RACHInterFreqMesQuant WCEL RSCP (1)  RSCP

f2
f1
BlindHOEcNoThrTarget WCEL -12 dBm  - Not applicable as RSCP used
Target cell Quality check
BlindHORSCPThrTarget WCEL -95 dBm  -95 threshold when RSCP used
RACHIntraFreqMesQuant WCEL EcNo (0)  RSCP Must be RSCP
BlindHORSCPThr HOPI -92 dBm  -92 Source Cell threshold

If the difference between coverage areas is too big to be handled with parameters, it is possible to activate one way
MBLB only (e.g. Micro -> Macro), or to activate MBLB only for those UE’s supporting inter-frequency measurements on
RACH For internal use

7 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

 MBLB Blind HO and MBLB State Transition - Counters

MBLB Blind HO performance Counters MBLB Layering Performance Counters

•With/without measurement means whether the UE had • Counters below are incremented when the UE is in
reported inter-frequency cell measurement results on RACH. URA_PCH/ Cell_PCH/ Cell_FACH state, and there is
• Not all the UE’s are supporting inter-frequency state transition attempt/success/failure into CELL_DCH
measurements state under another BTS
Counter ID Counter Name Counter ID Counter Name

M1006C234 RB Setup Attempt with BLIND HO M1006C240 ATTEMPTED INTER-BTS LAYER CHANGES IN PCH/FACH TO
DCH
M1006C235 RB SETUP SUCCESSFUL WITH BLIND HO M1006C241 SUCCESSFUL INTER-BTS LAYER CHANGES IN PCH/FACH TO
M1006C236 RB SETUP FAIL BLIND HO DUE TO UE NACK WITHOUT MEAS DCH
M1006C242 FAILED INTER-BTS LAYER CHANGES IN PCH/FACH TO DCH
M1006C237 RB SETUP FAIL BLIND HO DUE TO UE NACK WITH MEAS 

M1006C238 RB SETUP FAIL BLIND HO DUE TO UE LOST WITHOUT MEAS  Intra – BTS counters are implemented later (RU40)
M1006C239 RB SETUP FAIL BLIND HO DUE TO UE LOST WITH MEAS 
• E0695 EFS CR#E0695 MBLB Counter enhancement
If there are lots of failures with RSCP/EcNo measurements,
then BlindHOEcNoThrTarget / BlindHORSCPThrTarget
may have too low values

For internal use

8 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Preference Score calculation - Introduction

The decision making is based on preference score calculation to every available frequency.
• Preference score calculation includes 4 components
• Both Preferred frequency Layer weight and Load Weight is enabled (load cannot be enabled alone)
– With Preferred frequency it is defined which services are included to load balancing
– There is no need to activate Band Weight as it is assumed that there is enough UE’s in the market
supporting both bands.
– RSCP weight also not used Not considered for non-HSPA UEs or
Only for Blind HO and layer in state other with CS RAB in DCH cell
Not considered for fast moving UEs
transitions

Preference Preferred Freq + + +

Score = weight
Freq Band weight RSCP Weight Load Weight

LaySelWeightPrefLayer LaySelWeightBand LaySelWeightRSCP >=LaySelWeightLoad

or 0 or 0 or 0 or 0

Not used in this example

For internal use

9 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Preferred Frequency Layer – UE capability and Service

PrefLayerWeight value is set based on UE capability and service type (e.g. HSDPA UE with NRT service)
• Preferred layers for UE capability and service combination are checked from PFL-PrefLayer…parameters. If the
frequency layer is preferred for the UE, PrefLayerWeight is set to value taken from LaySelWeightPrefLayer (PFL)
Parameter. If the frequency layer is not preferred for the UE, PrefLayerWeight is set to value 0.
UE capability & Service Combination define correct parameter.
• UE capabilities has following priority order. For one UE capability and service combination, up to eight preferred layers
can be defined. The one selected is affected by other definitions
UE Capability Priority Order Service parameters included to PFL object
CS Voice Over HSPA PrefLayerCSHSNRT PrefLayerCSHSStr PrefLayerCSHSAMR PrefLayerCSHSAMR&NRT
that mach its capability
UE select first defined

DC HSUPA ? PrefLayerDCHSUNRT PrefLayerDCHSUStr PrefLayerDCHSUAMR PrefLayerDCHSUAMRNRT

DC HSDPA + MIMO PrefLayerDCMINRT PrefLayerDCMIStr PrefLayerDCMIAMR PrefLayerDCMIAMR&NRT
DB-DC-HSDPA ? PrefLayerDBDCHSDPANRT PrefLayerDBDCHSDPAStr PrefLayerDBDCHSDPAAMR PrefLayerDBDCHSDPAAMR&NRT
DC HSDPA * PrefLayerDCHSDNRT PrefLayerDCHSDStr PrefLayerDCHSDAMR PrefLayerDCHSDAMR&NRT
MIMO** PrefLayerMIMONRT PrefLayerMIMOStr PrefLayerMIMOAMR PrefLayerMIMOAMR&NRT
HSDPA 64QAM PrefLayer64QAMNRT PrefLayer64QAMStr PrefLayer64QAMAMR PrefLayer64QAMAMR&NRT
F-DPCH PrefLayerFDPCHNRT PrefLayerFDPCHStr PrefLayerFDPCHAMR PrefLayerFDPCHAMR&NRT
HSPA PrefLayerHSPANRT PrefLayerHSPAStr PrefLayerHSPAAMR PrefLayerHSPAAMR&NRT
HSDPA PrefLayerHSDPANRT PrefLayerHSDPAStr PrefLayerHSDPAAMR PrefLayerHSDPAAMR&NRT
R99 PrefLayerR99NRT PrefLayerR99Str PrefLayerR99AMR PrefLayerR99AMR&NRT
For internal use

10 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

PFL Configuration Using PFL object – Preferred layers for each UE capability and service
combination can be defined -> define services based on local knowledge
- you can define all services used in the network or just few.
Each cell should point PFL = 1 object • UE’s have priority order, HSPA capable UE is always also HSDPA
Parameter Object Default Value Value
capable UE. If HSPA not defined UE goes down until it finds next
PFLIdentifier PFL - 1
AMRToNonPreferredLayer PFL disabled (0) priority (HSDPA) and should follow those definitions
BlindHORSCPThrAbove PFL 0 dBm - Parameter Object Default Value Value
BlindHORSCPThrBelow PFL -126 dBm - PrefLayerFDPCHAMR PFL 0  
LaySelLowLoadPref PFL disabled (0) Enabled PrefLayerFDPCHAMRNRT PFL 0  
LaySelWeightBand PFL 0 0 PrefLayerFDPCHNRT PFL 0  
LaySelWeightLoad PFL 0 10 * PrefLayerFDPCHStr PFL 0  
LaySelWeightPrefLayer PFL 1000 10 * PrefLayerFastMovUECS PFL 0  
LaySelWeightRSCP PFL 0  0 PrefLayerFastMovUEPS PFL 0
PrefLayer64QAMAMR PFL 0   PrefLayerHSDPAAMR PFL 0 F1/F2
PrefLayer64QAMAMRNRT PFL 0   PrefLayerHSDPAAMRNRT PFL 0 F1/F2
PrefLayer64QAMNRT PFL 0   PrefLayerHSDPANRT PFL 0 F1/F2
PrefLayer64QAMStr PFL 0   PrefLayerHSDPAStr PFL 0
PrefLayerCSHSAMR PFL 0   PrefLayerHSPAAMR PFL 0
PrefLayerCSHSAMRNRT PFL 0   PrefLayerHSPAAMRNRT PFL 0
PrefLayerCSHSNRT PFL 0   PrefLayerHSPART PFL 0
PrefLayerCSHSStr PFL 0   PrefLayerHSPAStr
Example: All HSDPA capable PFL UE’s doing0
PrefLayerDCHSDAMR PFL 0   PrefLayerMIMOAMR PFL
NRT, AMR or MultiRAB (AMRNRT) call 0
PrefLayerMIMOAMRNRT
PrefLayerDCHSDAMRNRT PFL 0  
select either F1 or F2 based on load as 0
PFL
PrefLayerDCHSDNRT PFL 0   PrefLayerMIMONRT PFL 0
PrefLayerDCHSDStr PFL 0  
both are market to be preferred
PrefLayerMIMOStr PFL
layers for0
PrefLayerDCMIAMR PFL 0   PrefLayerR99AMR those UEs PFL 0
PrefLayerDCMIAMRNRT PFL 0   PrefLayerR99AMRNRT PFL 0  
PrefLayerDCMINRT PFL 0   PrefLayerR99NRT PFL 0  
PrefLayerDCMIStr PFL 0   PrefLayerR99Str PFL 0  

For internal use

11
*Depends how PFL definitions are done, see example
© Nokia Siemens Networks 2012
in page 13
PS NPO CC / Nov 2012
HSPA Load

HSPA load information is used for

• HSDPA load balancing – Selecting less loaded frequency layer when it is suitable
• HSPA overload handling – try to direct UEs away from loaded cell and not to select loaded cell to target for any
layering activities
Different load is used for Load balancing and for load state.
• For load balancing
– HSDPA power per NRT users & DL used power
• If any of the following indicates loaded state, the HSPA load level in the cell is set to HSPA load state:
– DL used power & average HSDPA provided bit rate for NRT users
– UL receiver noise & average E-DCH provided bit rate for NRT users
– Max number of HSDPA users
– HSUPA resource status
• MBLB include only HSPA load state detection, load based HO (LHO) feature can activated
simultaneously with MBLB to include load state detection. HSPA load state and load state are evaluated
independently. LHO load state is also taken into account in decision making and layer changes due to
MBLB load balancing is not done to the cell which is in LHO load state.
• .
For internal use

12 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

LoadWeight
Hidden parameter LoadbalancingLevels (RNC)
defines HSPA load levels which can have
LoadWeight value is set based on HSPA load. special value from 1 – 22
• If value of parameter LaySelWeightLoad is bigger than zero, cell • Values 1-3 indicates low load
specific packet scheduler defines the load level
HSDPA pwr per Unused HSPA load
LoadWeight  LaySelWeig htLoad * ( 22  HSPAloadLe vel ) * LowLoad Pr eference NRT user (W) DL pwr level
16 Yes 1
• LowLoadPreference defines whether extra weight is given to
16 >Pwr 10 Yes 2
HSPA load in layer selection for cells where HSPA load is low
10 >Pwr 4.2 Yes 3
• HSPA load level is evaluated calculating HSDPA power per NRT
user 4.2 >Pwr 2.2 Yes 4
2.2 >Pwr 1.3 Yes 5
P 
HSDPApower PerUser  NRTHSDPA

*CellWeight ForHSDPALa yering
1.3 >Pwr 0.8 Yes 6
NumberOfNR THSDPAuser s
0.8 >Pwr 0.5 Yes 7
• Different load is used for Load balancing and for load state. 0.5 >Pwr 0.23 Yes 8
HSPA Load State (overload) is defined with 4 … … …
different methods.
• DL used power & average HSDPA provided bit HSPA overload No 21
rate for NRT users,
• UL Received Noise & average E-DCH provided Load unknown or
bit rate for NRT users non HSDPA cell No 22
• Max Number of HSDPA users
• HSUPA resource Status
For internal use

13 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Preference Score Calculation - Example
Load Weight with Preference Score = Load
  Load Level different load levels weight + pref layer weight
As long as all layers are preferred for the UE and LaySelWeightPrefLayer     50 90
only difference is load level , the UE will LayselWeightLoad   10    
  1 210 260 300
select less loaded carrier   2 200 250 290
• In case PFL definition are done so that only   3 190 240 280
one layer is preferred for the UE (F1), then   4 180 230 270
preference score calculation goes as below   5 170 220 260
  6 160 210 250
for different carriers.   7 150 200 240

Load Increase
• F1 = LoadWeight + PrefLayerWeight   8 140 190 230
  9 130 180 220
• F2 = LoadWeight + 0   10 120 170 210
  11 110 160 200
  12 100 150 190
Example show calculation with 2 different   13 90 140 180
PrefLayerWeight values (50/90), Load weight   14 80 130 170
is same (10) in both case.   15 70 120 160
  16 60 110 150
• Using different value it is possible to define   17 50 100 140
how big load difference between carriers is   18 40 90 130
allowed before UE can start to use carrier   19 30 80 120
which is not preferred for it.   20 20 70 110
  21 10 60 100
  22 0 50 90

When the use

For internal site is overloaded (in load state) MBLB is not moving new UE’s to the cell which is in load state, but it is also
14
NOT moving UE’s having higher score away from that
© Nokia Siemens Networks 2012
layer they already camping, this can lead for the blocking.
PS NPO CC / Nov 2012
Other MBLB Parameters Load state triggered by low throughput requires cell
locking, otherwise not used.
Parameter Object Range Default Value Comment
BlindHOTargetCell ADJI disabled (0), enabled (1) disabled (0) Enabled One target per frequency layer
MBLBMobilityOffset FMCI -6...6 dB, step 0.5 dB 2 dB N/A
MBLBMobilityRABComb FMCI all (0), NRT (1) all (0) N/A
BlindHORSCPThr HOPI -115...-25 dBm, step 1 dBm -92 dBm -92 Source cell quality check threshold
MBLBGuardTimer RNMOBI 0...60 s, step 1 s 10 s N/A
PreferBandForLayering RNMOBI 0...51, step 1 0 N/A
BlindHOIntraBTSQCheck WBTS quality check done (0), quality check not done (1) quality check done (0) 0
PFLIdentifier WCEL 1...50, step 1 0 1
BlindHOEcNoThrTarget WCEL -24...0 dBm, step 0.5 dBm -12 dBm N/A RSCP used
BlindHORSCPThrTarget WCEL -115...-25 dBm, step 1 dBm -95 dBm -95 Target cell threshold
DLLoadStateTTT WCEL 0...10 s, step 0.5 s 2s 2s
HSLoadStateHSDBRLimit WCEL 0...248 kbps, step 2 kbps 32 kbps 32
HSLoadStateHSDOffset WCEL -3...0 dB, step 0.1 dB 127 dB -1 127=not used, when activated -1 recommended
ULLoadStateTTT RNPA 0...10 s, step 0.5 s 2s 2s
HSLoadStateHSUBRLimit WCEL 0...248 kbps, step 2 kbps 24 kbps 24
HSLoadStateHSUOffset WCEL -3...3 dB, step 0.1 dB 127 dB -1 127=not used, when activated -1 recommended
HSLoadStateHSUResThr WCEL 0.3...1, step 0.1 2 (not used) 0.7
MBLBInactivityEnabled WCEL Disabled (0), Enabled (1) Disabled (0) Disabled
MBLBMobilityEnabled WCEL Disabled (0), Enabled (1) Disabled (0) Disabled
MBLBRABSetupEnabled WCEL Disabled (0), Enabled (1) Disabled (0) Enabled MBLB Blind HO enabled
disabled (0), enabled when UE is in
Cell_FACH/Cell_PCH state (1), enabled when UE enabled when UE is in
is in Cell_DCH state (2), enabled when UE is in Cell_FACH/Cell_PCH
MBLBRABSetupMultiRAB WCEL Cell_DCH/Cell_FACH/Cell_PCH (3) state (1) 3  
MBLBStateTransEnabled WCEL Disabled (0), Enabled (1) Disabled (0) Enabled MBLB State Transition Enabled
RACHInterFreqMesQuant WCEL EcNo (0), RSCP (1) RSCP (1) RSCP  
Intra frequency measurement quantity must be
RACHIntraFreqMesQuant WCEL EcNo (0), RSCP (1) EcNo (0) RSCP RSCP
CellWeightForHSDPALayering WCEL 0.01...1, step 0.01 1 1 Cell weight parameter

For internal use

15 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

 Background Slides

For internal use

16 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

MBLB Parameter template

Parameter in excel format – can be used as template

Microsoft Office
Excel Worksheet

For internal use

17 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Load state Detection with LHO

Load based HO (LHO) feature can activated Load state detection can be activated with following LHO Load
simultaneously with MBLB to include load parameters – Load handovers not activated
state detection. Parameter
LHONumbUEInterRAT
Object
WCEL
Range
0…32, step 1
Default
0
Value
0
HSPA load state (MBLB) and load state are LHONumbUEInterFreq WCEL 0…32, step 1 0 0
LHOWinSizeONCapaReqRejRate WCEL 0...60 s, step 1 s 0s 15
evaluated independently (LHO). LHOHystTimeCapaReqRejRate WCEL 0...10 s, step 1 2s 2
LHOWinSizeOFFCapaReqRejRate WCEL 1...60 s, step 1 s 5s 5
LHO load state is also taken into account in LHODelayOFFCapaReqRejRate WCEL 0...255 s, step 1 s 30 s 30
decision making and layer changes due to LHOCapaReqRejRateDL WCEL 0...100 %, step 1 % 70 % 70
LHOCapaReqRejRateUL WCEL 0...100 %, step 1 % 70 % 70
MBLB load balancing is not done to the LHOWinSizeONInterference WCEL 0...60 s, step 1 s 0s 15
cell which is in LHO load state. LHOHystTimeInterference WCEL 0...10 s, step 1 s 2s 2
LHOWinSizeOFFInterference WCEL 1...60 s, step 1 s 5s 5
LHODelayOFFInterference WCEL 0...255 s, step 1 s 30 s 30
LHOPwrOffsetDL WCEL -30...0 dB, step 0.1 dB -1.5 dB -1.5
LHOPwrOffsetUL WCEL -10...0 dB, step 0.1 dB -0.7 dB -0.7
LHOWinSizeONHardBlocking WCEL 0...60 s, step 1 s 0s 15
LHOHystTimeHardBlocking WCEL 0...10 s, step 1 s 2s 2
LHOWinSizeOFFHardBlocking WCEL 1...60 s, step 1 s 5s 5
LHODelayOFFHardBlocking WCEL 0...255 s, step 1 s 30 s 30
LHOHardBlockingBaseLoad WCEL 0...255, step 1 10 10
LHOHardBlockingRatio WCEL 0...100 %, step 1 % 50 % 50
LHOWinSizeONResRateSC WCEL 0...60 s, step 1 s 0s 15
LHOHystTimeResRateSC WCEL 0...10 s, step 1 s 2s 2
LHOWinSizeOFFResRateSC WCEL 1...60 s, step 1 s 5s 5
LHODelayOFFResRateSC WCEL 0...255 s, step 1 s 30 s 30
For internal use
LHOResRateSC WCEL 0...100 %, step 1 % 80 % 80
LHONRTTrafficBaseLoad WCEL 0...255, step 1 10 10
18 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012
Other Impacted Features

Changing RACHIntraFreqMesQuant from EcNo to RSCP will have impact for following features:

HSUPA 2ms TTI

• RNC uses RSCP instead of EcNo to define if 2ms TTI is used on E-DCH in state transitions to Cell_DCH
state
SRB on HSPA
• RNC uses RSCP instead of EcNo to define if standalone SRBs are mapped to HSPA in RRC connection
establishment phase
Common Channel Setup
• RNC uses RSCP instead of EcNo to define if RRC connection setup is performed in common channels.
Parameter CPICHEcNoSRBMapRRC is replaced with CPICHRSCPSRBMapRRC
Fast Call Setup from Cell_PCH
• RNC uses RSCP instead of EcNo to define if fast call setup is performed. Parameter
CUCEcNoThreshold is replaced with CUCRSCPThreshold.

For internal use

19 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

Change in load calculation algorithm

Load weight has been earlier calculated with the following equation:
LoadWeight LaySelWeightLoad( 22 HSPAloadLevel ) LowLoadPr eference OLD

The preference score is calculated to all frequencies for which a possible target cell for MBLB handover and for the
source frequency exists. The equation shows that all the frequency layers will get the same value for
LaySelWeightLoad, which is the value taken from PFL-LaySelWeightLoad parameter. From the decision making point
of view, it does not make any difference which value between 1 and 10000 is used PFL-LaySelWeightLoad
parameter as the absolute change is identical to all calculated preference scores. Only using value 0 makes
difference as it makes the LoadWeight to 0 meaning that load does not have effect on decision making.
To improve configurability of how HSPA load level affects the decision making, the following modification is made to the
equation:

LoadWeight  LaySelWeig htLoad * ( 22  HSPAloadLe vel ) * LowLoad Pr eference NEW

This increases the flexibility of configuration. However, the functionality before this change can be kept. If any value
between 1 and 10000 is used before the change, exactly the same functionality can be kept by configuring the PFL-
LaySelWeightLoad parameter to value 1. The same is true about the value 0. Using any value from 2 to 10000 after
this change can change the functionality, depending on how other weight- related parameters are set (PFL-
LaySelWeightPrefLayer, PFL-LaySelWeightBand and PFL-LaySelWeightRSCP).
For internal use

20 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

PRFILE 002:1888 RN60_Maint_12

MBLB blind HO is done during RAB setup phase, if

MBLB is triggered, the new frequency info is
included to Radio Bearer Setup message and Radio
bearer Setup complete message is send already
with new frequency.

PRFILE 002:1888 RN60_MAINT_12 allows possibility to

activate two procedure functionality for MBLB in
case there is UE’s which does not support one
procedure functionality. If two procedure functionality
is used, the Blind HO is first done either using
Physical Channel Reconfiguration, Transport
Channel Reconfiguration or Radio Bearer Blind HO with two procedure functionality
Reconfiguration and then RB setup is done triggers layer change in Physical channel
reconfiguration
separately.
Blind HO with one procedure functionality
triggers layer change in Radio Bearer
Setup Phase (and Physical channel
reconfiguration is not done )

For internal use

21 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012

PRIFILE 002:1897 RN60_MAINT_22 I

Following source cell measurement results can be available for blind HO: RRC_CONNECTION_REQUEST
8.8.0 Rel 8)
(3GPP TS 25.331 ver

1. UE measures and reports RSCP value from current cell and best neighbor cell to UL-CCCH-Message

RNC in RRC Connection Request and Cell Update messages. message

rrcConnectionRequest
initialUE-Identity
– IF best neighbor is having better RSCP than current cell it will use best tmsi-and-LAI
tmsi
neighbor instead Bin : 63 AC 5F 01 (= 1672240897)
lai
– This is causing problems due the inaccuracy of best neighbor measurement plmn-Identity
mcc
results as in some cases too good compared to reality mcc value : 2, 4, 4
mnc
– PRFILE 002:1897 RN60_MAINT_22 can be used to disable the use of lac
mnc value : 0, 7

monitored cell (intra-frequency neighbor cell) in RACH measurement results. Bin : 24 54 (= 9300)
establishmentCause : registration
This means that Blind HO can be triggered only from the current cell and the protocolErrorIndicator : noError
current cell’s RSCP value is used when defining the initial power for Blind HO measuredResultsOnRACH
currentCell
modeSpecificInfo
2. UE also reports RSCP values within event 1a and even 1c Measurement Report fdd

messages for soft handover radio link addition/replacement measurementQuantity

cpich-RSCP : 56 (= -60 dBm)
monitoredCells
3. The UE also provides periodic RSCP reports if the SRB is mapped to HSPA monitoredCells value 1
modeSpecificInfo
For Blind HO latest available measurement report containing RSCP value of Source fdd
primaryCPICH-Info
cell is used. primaryScramblingCode : 142
measurementQuantity
Source cell for Blind HO in RAB setup phase is the cell which has reported highest cpich-RSCP : 57 (= -59 dBm)
v3d0NonCriticalExtensions
RSCP value in latest measurement report rRCConnectionRequest-v3d0ext :
v4b0NonCriticalExtensions
rrcConnectionRequest-v4b0ext
accessStratumReleaseIndicator : rel-6
For internal use v590NonCriticalExtensions
rrcConnectionRequest-v590ext
predefinedConfigStatusInfo : false
22 © Nokia Siemens Networks 2012 NPO CC / Oct 2012
PRIFILE 002:1897 RN60_MAINT_22 II

Performance before and after PRIFILE activatioin

For internal use

23 © Nokia Siemens Networks 2012 PS NPO CC / Nov 2012