FEMTO Parameter User Guide 01.01

7/21/2019 FEMTO Parameter User Guide 01.01

1/59

FEMTO Parameter User Guide BCR2.1

Document number: UMT/IRC/DD/024270Document issue: 01.01 / ENDocument status: DraftDate: 26/May/2008

INTERNAL Document

Passing on or copying of this document, use and communication of its contents notpermitted without AlcatelLucent written authorization

Copyright!2008 Alcatel-Lucent, All Rights Reserved

Printed in France

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write

protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.

Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded

as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-

Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information

contained herein confidential, shall disclose the information only to its employees with a need to know, and shall

protect the information from disclosure and dissemination to third parties. Except as expressly authorized in

writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have

received this document in error, please notify the sender and destroy it immediately.

BSR - Base Station Router


2/59


Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written authorization

UMT/IRC/DD/024270 01.01 / EN Draft 26/May/2008 Page 2/59


3/59




CONTENTS

1.

INTRODUCTION............................................................................................................................5

1.1. OBJECT....................................................................................................................................5

1.2. SCOPE OF THE DOCUMENT ........................................................................................................5

1.3. NOMENCLATURE.......................................................................................................................6

2. RELATED DOCUMENTS..............................................................................................................8

2.1. 3GPPREFERENCE DOCUMENTS ...............................................................................................8

2.2. ALCATEL-LUCENT REFERENCE DOCUMENTS ..............................................................................8

3.

BSR OAM MODEL ........................................................................................................................9

4. POWER CONTROL.....................................................................................................................10

4.1. POWER SETTING ....................................................................................................................10

4.1.1 Initial CPICH Power ......................................................................................................104.1.2 Updating CPICH Power ................................................................................................104.1.2.1 CPICH Power update based on Coverage................................................................114.1.2.2 CPICH Power update based on UE receiver range ..................................................134.1.2.3 CPICH Power update based on UE measurements .................................................144.1.3 Maximum BSR Tx Power..............................................................................................164.1.4 Other DL Common Channel Power setting...................................................................16

5.

RADIO RESSOURCE MANAGEMENT.......................................................................................19

5.1. CALL ADMISSION CONTROL.....................................................................................................19

5.1.1 Emergency Call redirection...........................................................................................195.1.2 Processing CAC............................................................................................................195.1.3 Rejecting RRC Connection ...........................................................................................22

5.2. DYNAMIC BEARER CONTROL ...................................................................................................22

5.2.1 DBC based on UL & DL Load measurement ................................................................225.2.2 DBC based on Baseband processing limitation............................................................25

5.3. AIR INTERFACE CONGESTION CONTROL...................................................................................26

6.

MOBILITY MANAGEMENT.........................................................................................................27

6.1. CELL RESERVATION AND ACCESS RESTRICTION.......................................................................27

6.2. NEIGHBOURHOOD DEFINITION .................................................................................................28

6.2.1 3G Macro neighbourhood .............................................................................................286.2.2 GSM Macro neighbourhood..........................................................................................32

6.3. CELL RESELECTION ................................................................................................................34

6.3.1 Cell Reselection Measurement Rules...........................................................................366.3.1.1 Intra-frequency measurements .................................................................................376.3.1.2 Inter-frequency measurements .................................................................................376.3.1.3 Inter-RAT measurements ..........................................................................................386.3.1.4 Measurement Triggers Parameters...........................................................................38

6.3.2

Cell Eligibility Criteria ....................................................................................................406.3.2.1 3G Neighbouring Cell Criteria ...................................................................................42

6.3.2.2 GSM Neighbouring Cell Criteria ................................................................................43


4/59




6.3.3 Cell Reselection Ranking Criterion ............................................................................456.3.3.1 First Ranking .............................................................................................................466.3.3.2 Second Ranking ........................................................................................................476.3.3.3 Target Cell Selection .................................................................................................48

6.4. HARD HANDOVER ...................................................................................................................50

6.4.1

Eligibility for Handover ..................................................................................................50

6.4.2 Detecting Radio Degradation........................................................................................516.4.3 Handover Execution......................................................................................................55

7. INDEXES......................................................................................................................................58

7.1. TABLE INDEX ..........................................................................................................................58

7.2. FIGURE INDEX ........................................................................................................................58


5/59




1. INTRODUCTION

1.1. OBJECT

The FEMTO Parameter User Guide (FPUG) document provides parameter setting

recommendation from Alcatel-Lucents experience, coming from studies, simulations

and experimentations. It gives the rationale of these settings by describing Alcatel-

Lucents FEMTO BSR algorithms and parameters from an engineering point of view. It

also gives some engineering rules related to parameter settings.

The FPUG does not contain the complete list of configuration parameters; the

parameters described in this document are only customer configuration parameters

accessible by the customer (operator) via the MMI of the OMC.

In the case where the recommended values of the FPUG are different from any other

document, the FPUG recommendation should prevail.

1.2. SCOPE OF THE DOCUMENT

The FPUG describes the features and the associated parameters which represent the

salient functions available within Alcatel-lucent BSR FEMTO solution, based on

BCR2.1 Phase 5.

The relevant features are listed in the following table.


6/59




Category Feature ID Feature Title Basic/Option

34586 Dynamic Bearer Control Basic

34596 Active call redirect from BSR FEMTO to Macro Basic

34527 Pre-emption process for emergency call Basic

36217 CAC on backhaul resources Basic

75103 Emergency call redirection to the Macro network Basic

34526 Air Interface Congestion control Basic

34528 Power control Basic

RRM

74769 Voice Prioritisation over Data Basic

34529

Cell Reselection to/from macro layer (2G or 3G, intra/inter

frequency)

Basic

34530 Handover BSR FEMTO to Macro 3G Option

34531 Handover BSR FEMTO to Macro 2G Option

34535 BSR FEMTO auto-configuration Basic

34536 BSR FEMTO self-optimisation Basic

Mobility

34537 3G Network Listening Basic

1.3. NOMENCLATURE

In this document, BSR stands for BSR FEMTO.

The parameter names are written in bold italic.

The objects names are written in bold.

The parameters properties are presented as follow:

Parameter

Object

Granularity

Range & Unit

Class

Value

Note: the information fields Parameter, Object, Range & Unit, and User & Class

are based on External


7/59




The protocol messages are written in CAPITAL LETTERS.

The Information Elements (IE) contained in the protocol messages are written the

following way: TPC_DL_Step_Size.

The data fill rules (non negotiable) are presented as the following. These are

typically OAM checks performed on parameters settings (structure of table, range,

etc)

Rule:

The system restrictions are presented as the following. Typically when the

behaviour of product is not as specified (e.g. parameters not used by algorithm)

Restriction:

The engineering recommendations on parameter value are presented as the

following. These are recommendations related to performance (QoS, Capacity,

KPI) to get the best of the network.

Engineering Recommendation:


8/59




2. RELATED DOCUMENTS

2.1. 3GPP REFERENCE DOCUMENTS

[3GPP_R01] 3GPP TS 25.304 UE procedures in Idle mode and procedures for cell

reselection in connected mode

[3GPP_R02] 3GPP TS 25.331 Radio Resource Control (RRC); protocol specification

[3GPP_R03] GSM TS 05-05 Radio Transmission and Reception

2.2. ALCATEL-LUCENT REFERENCE DOCUMENTS

[R01] NTP 411-8111-813 Access Network Parameters

[R02] UMT/SYS/INF/023452 BSR FEMTO Feature Planning Guide BCR2.1

[R03] SRD-FBSR-RRM Radio Resource Management System Requirements

Document

[R04] SRD-BSR-POW Power Control System Requirements Document


9/59




3. BSR OAM MODEL

The following figure depicts, within the BSR OAM Model, the location of all the

parameters that are presented in this document.

Figure 1: BSR OAM Model


10/59




4. POWER CONTROL

4.1. POWER SETTING

4.1.1 INITIAL CPICH POWER

During auto-configuration phase, BSR uses autoConfigPWpCPICHPowerIni as the

initial CPICH power.

Parameter autoConfigPWpCPICHPowerIni

Object BSRProfile

Granularity BSR Profile

Range & Unit Float (dBm)

[-3020] step 0.1

Class Class 3

Value -10

4.1.2 UPDATING CPICH POWER

The following sections define the different algorithms that aim at updating CPICH

power which always remain within its range, defined by the 2 following parameters,

autoConfigPWminPilotPowerdBmand autoConfigPWmaxPilotPowerdBm.

Parameter autoConfigPWminPilotPowerdBm

Object BSRProfile



[-3024] step 0.1

Class Class 3Value -10


11/59




Parameter autoConfigPWmaxPilotPowerdBm

Object BSRProfile



[-3024] step 0.1

Class Class 3

Value 3

Cf. recommendation hereafter

Engineering Recommendation: autoConfigPWmaxPilotPowerdBm

Keeping in mind that MaxBSRPowerdBm is 10 dB higher than CPICH power (cf. section 4.1.3), it is

recommended to set autoConfigPWmaxPilotPowerdBm 10 dB lower than

maxBSRPowerLimitdBm, i.e. 3 dB.

4.1.2.1 CPICH POWER UPDATE BASED ON COVERAGE

The dynamic setting of CPICH power is enabled through

bsrBasedPilotPowerAdjustModeparameter.

Parameter bsrBasedPilotPowerAdjustMode

Object BSRProfile


Range & Unit Enumerated (ms)

{disable, ecIoBased}

Class Class 3

Value ecIoBased

When set to disable, BSR uses pCPICHPower as the static CPICH power.

Parameter pCPICHPower

Object LCell



[-3020] step 0.1

Class Class 3

Value -10

When set to ecIoBased, BSR dynamically adjusts CPICH power using the following

formula:

CPICHpower[new]= autoConfigPWtargetPilotEcIodB+ IodBm + MaximumPathLoss


12/59




where:

IodBm is the average UTRA RSSI (converted in dBm) measured during the

network listening period (autoConfigPWBsrBasedPilotPowerAdjustIntervalseconds)

MaximumPathLoss=FreeSpacePathloss+ autoConfigPWindoorPenetrationLoss

o FreeSpacePathloss= 20*log10(DL_frequencyMHz) +

20*log10(autoConfigPWmaxCoverageDistancem) 27.5582

Refer to [R04] for further explanations on these formulas.

Parameter autoConfigPWtargetPilotEcIodBObject BSRProfile


Range & Unit Float (dB)

[-250] step 0.1

Class Class 3

Value -14

autoConfigPWindoorPenetrationLoss is used to control the minimum BSR pilot

coverage, in order to maintain the BSR's minimum coverage.

Parameter autoConfigPWindoorPenetrationLoss

Object BSRProfile


Range & Unit Integer (dB)

[0100]

Class Class 3

Value Cf. recommendation hereafter

autoConfigPWmaxCoverageDistancem is used to adjust the BSR coverage

within the limit set by autoConfigPWmaxPilotPowerdBm.

Parameter autoConfigPWmaxCoverageDistancem

Object BSRProfile


Range & Unit Integer (m)

[1200]

Class Class 3



13/59




Engineering Recommendation: autoConfigPWindoorPenetrationLoss and

autoConfigPWmaxCoverageDistancem

For initial deployment, it is recommended that the operator setup a few profiles for typical residential

property types, such as farm house, city house and apartment flat

Parameter autoConfigPWBsrBasedPilotPowerAdjustInterval

Object BSRProfile


Range & Unit Integer (s)

[0600]

Class Class 3

Value 120

4.1.2.2 CPICH POWER UPDATE BASED ON UE RECEIVERRANGE

To make sure that the total power received by UE remains within its dynamic receiver

range, an UE internal measurement is configured after RAB establishment: Event 6E

is then reported by UE when measuring an RSSI that reaches its dynamic receiver

range (as specified by [3GPP_R02]).

uEtoBSRReportingCriteriaRSSITimetoTrigger, in ms, indicates the periodof time between the timing of event detection and the timing of sending

Measurement Report (Event 6E).

Parameter uEtoBSRReportingCriteriaRSSITimetoTrigger

Object BSRProfile



{timetotrigger0, timetotrigger10, timetotrigger20,

timetotrigger40, timetotrigger60, timetotrigger80,

timetotrigger100, timetotrigger120,




timetotrigger2560, timetotrigger5000}

Class Class 3

Value timetotrigger20

uEtoBSRReportingCriteriaReportingInterval, in ms, indicates the interval of

periodical reporting when such reporting is triggered by Event 6E. 0 means no

periodical reporting.


14/59




Parameter uEtoBSRReportingCriteriaReportingInterval

Object BSRProfile



{reportinginterval0, reportinginterval250,

reportinginterval500, reportinginterval1000,






reportinginterval64000}

Class Class 3

Value reportinginterval8000

When BSR receives such Event 6E, it reduces the CPICH power by

autoConfigPWpAdjustmentStepdB, keeping the new CPICH power above its

minimimum value, autoConfigPWminPilotPowerdBm.

CPICHpower[new] = max (CPICHpower[old] -autoConfigPWpAdjustmentStepdB,

autoConfigPWminPilotPowerdBm)

Parameter autoConfigPWpAdjustmentStepdBObject BSRProfile



[010]

Class Class 3

Value 1

4.1.2.3 CPICH POWER UPDATE BASED ON UE

MEASUREMENTS

Once a new RAB is established, BSR may configure at UE side Events 1C and 1F:

Event 1C: The CPICH of an intra-frequency monitored (or detected) cell

becomes better than the active BSRs.

Event 1F: the active BSRs CPICH becomes worse than an absolute

threshold.

ueBasedPilotPowerAdjustMode allows to activate this feature and to define how

CPICH power is updated.


15/59




Parameter ueBasedPilotPowerAdjustMode

Object BSRProfile

Granularity BSR ProfileRange & Unit Enumerated (ms)

{disable, neighbourEcIo, targetEcIo}

Class Class 3


When set to disable, BSR does not use UE measurements to update CPICH power;

both Events are thus not configured.

When set to neighbourEcIo, BSR only configures Event 1C and optimizes the CPICHpower by comparing the CPICH Ec/Io of all Intra-frequency reported cells, as follows:

If

Active BSRs CPICH Ec/Io < Neighbouring cells CPICH Ec/Io

then

CPICHpower[new] = CPICHpower[old] +autoConfigPWpAdjustmentStepdB

When set to targetEcIo, BSR only configures Event 1F and optimizes the CPICH

power based on the worst CPICH Ec/Io (of this active BSR) reported by any UE in

DCH during the last autoConfigPWUeBasedPilotPowerAdjustIntervalseconds, as

follows:

If

Active BSRs CPICH Ec/Io < autoConfigPWtargetPilotEcIodB

then

CPICHpower[new] = CPICHpower[old] +autoConfigPWpAdjustmentStepdB

Engineering Recommendation: ueBasedPilotPowerAdjustMode

If BSR is deployed on a dedicated carrier and for own usage (i.e. different than Enterprise network),

ueBasedPilotPowerAdjustModeshall be set to targetEcIo.

Otherwise, ueBasedPilotPowerAdjustModeshall be set to neighbourEcIo.


16/59


17/59




pSCHPowerdefines the Primary SCH power, in dB, with respect to P-CPICH

power.

Parameter pSCHPower

Object LCellGranularity BSR Profile


[-3515] step 0.100

Class Class 3

Value -3.0

sSCHPower defines the Secondary SCH power, in dB, with respect to P-

CPICH power.

Parameter sSCHPower

Object LCell



[-3515] step 0.100

Class Class 3

Value -5.0

bCHPowerdefines the BCH power, in dB, with respect to P-CPICH power.

Parameter bCHPower

Object LCell



[-3515] step 0.100

Class Class 3

Value -3.0

pCHPowerdefines the PCH power, in dB, with respect to P-CPICH power.

Parameter pCHPower

Object CCPower

Granularity LCell


[-3515] step 0.1

Class Class 3

Value 4.0


18/59




pICHPowerdefines the PICH power, in dB, with respect to P-CPICH power.

Parameter pICHPower

Object CCPower

Granularity LCellRange & Unit Integer (dB)

[-105]

Class Class 3

Value -5

aICHPowerdefines the AICH power, in dB, with respect to P-CPICH power.

Parameter aICHPower

Object CCPower

Granularity LCellRange & Unit Float (dB)

[-225] step 0.1

Class Class 3

Value -5


19/59




5. RADIO RESSOURCE MANAGEMENT

5.1. CALL ADMISSION CONTROL

The Call Admission Control (CAC) algorithm is used to admit or deny new RRC

Connection Request based on several criterions presented in section 5.1.2.

5.1.1 EMERGENCY CALL REDIRECTION

Prior to the CAC processing described in section 5.1.2, a specific treatment is

performed for Emergency calls, i.e. when RRC Connection Request cause is set to

Emergency. In such a case, emergencyCallAlwaysRedirectFlag is checked; when

set to True, BSR directly performs an Emergency call redirection to Macro 3G or 2G,

depending on emergencyCallRedirectNetworkvalue.

Parameter emergencyCallAlwaysRedirectFlag

Object LCell


Range & Unit Boolean

{True, False}Class Class 3

Value False

Parameter emergencyCallRedirectNetwork

Object LCell


Range & Unit Enum

{redirectGsmPreferred or redirectUmtsPreferred}

Class Class 3

Value redirectGsmPreferred

If Emergency call redirection is disabled or no Macro neighbouring cell is available nor

eligible, CAC check is performed, as presented hereafter.

5.1.2 PROCESSING CAC

CAC is based on several checks:


20/59




DL/UL loads are lower than thrCACDL/UL (thrCACEmergencyDL/UL for

Emergency calls);

DL & UL resource consumptions are ok;

For non-Emergency call, the number of Cell DCH users is lower than

numCellDCHUE.

Parameter numCellDCHUE

Object LCell


Range & Unit Integer

[132]

Class Class 3

Value 4

Refer to section 5.2 for more details on CAC thresholds.

If the above checks fail, the following process applies depending on the RRC

Connection Request establishment cause

CAC rejection for non-Emergency calls

BSR first tries and preempts an UE which is marked for Measurement Acceleration(i.e. which is in Cell DCH for radio optimization).

If there is no UE marked for Measurement Acceleration, BSR performs Active Call

Redirection which allows handing-over an existing CS Speech call such that resources

are freed up to enable the new call. This only takes place if

activeCallRedirectEnabled is set to True and aCRpreference is set to

nonEmergencyCallor both(the type of the RAB to establish).

Parameter activeCallRedirectEnabled

Object BSRProfileGranularity BSR Profile


{True, False}

Class Class 3

Value True



21/59




Parameter aCRpreference

Object BSRProfile


Range & Unit Enum

{nonEmergencyCall, emergencyCall or Both}

Class Class 3

Value emergencyCall


Engineering Recommendation: Active Call Redirection

It is recommended to enable Active Call Redirection feature for emergencyCallonly. This will allow to

pre-empt a normal CS Speech call in order to establish an Emergency CS call.

In case Active Call Redirection is disabled or fails, BSR may perform normal call pre-

emption, depending onenableNormalCallPreemption value. When set to True, BSR

pre-empts an existing Cell DCH UE based on the order below:

Cell DCH UE with only PS RAB Background

Cell DCH UE with only PS RAB Interactive

Parameter enableNormalCallPreemption

Object BSRProfileGranularity BSR Profile


{True, False}

Class Class 3

Value True

CAC rejection for Emergency calls

If CAC fails, BSR first tries and pre-empts an UE marked for Measurement

Acceleration; BSR eventually pre-empts, if needed, an existing Cell DCH UE when

emergencyCallPreemptionEnabledis set to True.

Parameter emergencyCallPreemptionEnabled

Object LCell



{True, False}

Class Class 3

Value True


22/59




If emergencyCallPreemptionEnabled is set to False, BSR finally attempts Active

Call Redirection if activeCallRedirectEnabled is set to True and aCRpreference is

set to emergencyCallor both.

5.1.3 REJECTING RRC CONNECTION

In case the previous checks did not allow to accept the new RRC Connection, BSR

sends back RRC Connection Release to UE with cause Congestion and specifies in

the same RRC message which network to be redirected to, using:

emergencyCallRedirectNetworkfor Emergency calls,

redirectNetworkfor non-Emergency calls.

Parameter redirectNetwork

Object LCell


Range & Unit Enum

{disable, redirectGSM or redirectUMTS}

Class Class 3

Value redirectGSM

5.2. DYNAMIC BEARER CONTROL

The Dynamic Bearer Control (DBC) is in charge of the rate allocation for PS and CS

Conversational services on DCH and/or HS-DSCH transport channels based on:

UL and DL load information,

the baseband processor resource usage.

Refer to [R03] for further details on DBC.

5.2.1 DBC BASED ON UL & DL LOAD MEASUREMENT

DBC algorithm first evaluates the environment status for UL & DL based on the latest

CPICH Ec/N0 measurement reported by UE in RRC Connection Request, RRC Cell

Update or RRC Measurement Report (while in Cell DCH). The comparison of CPICH

Ec/No with hardcoded thresholds leads to 2 different values for each UL and DL

environment status: Cell Center or Cell Edge.

Then, DBC admits the incoming request if the following condition is satisfied,

depending on the bearer to be granted.


23/59




PS bearer to be granted

PS bearer Condition for the bearer to be granted

ULPS bearer with 8k, 16k or 32k or 64k load_UL


24/59




Parameter thrCACDL

Object LCell


Range & Unit Integer (%)

[0100]

Class Class 3

Value 75

Cf. rule below

Parameter thrDBCDL

Object LCell



[0100]Class Class 3

Value 50

Cf. rule below

Rule: thrDBC and thrCAC

thrDBCDL (resp. thrDBCUL) must be lower than thrCACDL(resp. thrCACUL).

CS bearer to be granted

A similar algorithm applies for CS services:

CS bearer Condition for the bearer to be granted

ULnon-emergency CS bearer with 12.2k or 64k load_UL


25/59




Parameter thrCACEmergencyDL

Object LCell



[0100]

Class Class 3

Value 90

Cf. rule below

Rule: thrCAC and thrCACEmergency

thrCACDL (resp. thrCACUL) must be lower than thrCACEmergencyDL (resp.

thrCACEmergencyUL)

If DBC admission check fails in DL only and DL is allocated on DCH, then the DL data

rate shall be the next lower one. The UL rate shall be the existing UL rate. If no such

combination exists, the UL rate can be negotiated, too.

If DBC check fails in UL only, then the UL data rate shall be changed to the next lower

one. The DL rate shall be the existing DL rate. If no such combination exists and DL is

allocated on DCH, the DL rate can be negotiated, too. If DL is allocated on HS-DSCH,

the DL rate cannot be negotiated.

If finally no combination could be found, DBC negotiation shall be rejected and

procedure shall be stopped.

5.2.2 DBC BASED ON BASEBAND PROCESSING LIMITATION

The BSR shall reject all RAB Setup which is not Emergency call when the most recent

measured load_DL is greater than or equal to thrConCDL.

Parameter thrConCDL

Object LCell



[0100]

Class Class 3

Value 90

Otherwise, the BSR shall check whether:

the DL resource consumption is ok,

the UL resource consumption is ok,

the UL SF usage (including the new RAB) is ok,


26/59




multiple RAB service combination is supported.

In case one of these checks fails, the BSR renegotiates the RAB setup as presented

in section 5.2.1. If renegotiation attempt fails, BSR pre-empts resources from otherestablished PS RAB by reconfiguring it (several PS RABs if needed).

If the new RAB is a CS emergency voice call and the PS RAB(s) pre-emption did not

release enough resources, the BSR will pre-empt an existing CS RAB (CS Data first,

then CS Voice) if emergencyCallPreemptionEnabledis set to True.

5.3. AIR INTERFACE CONGESTION CONTROL

For the purpose of UL and DL load calculation, BSR periodically evaluates the

Received Total Wideband Power (RSSI) and Transmitted Carrier Power (TSSI).

When load_DL becomes greater than or equal to thrConCDL(parameter is presented

in section 5.2.2), Congestion Control is triggered for DL and BSR starts pre-empting

existing RAB(s) until load_DL < thrConCDLin the following order:

PS DCH of the highest data rate with lowest traffic handling priority.

If no PS DCH left, CS Data.

If no PS DCH and CS Data left, CS Voice (non-emergency call).

If no PS DCH, no CS Data and no CS Voice (non-emergency call) left, CS

Voice (emergency call).


27/59


28/59




Parameter sIB3CellResExtension

Object LCell


Range & Unit Enum

{reserved, notreserved}

Class Class 3

Value notreserved

Under certain circumstances, operators may want to prevent a selected group of UE

from making any access attempts or responding to pages in specified areas of a

PLMN.

System Information Block type 3 (SIB 3) transmits "Cell Access Restriction" IE which

itself contains another IE called "Access Class Barred list". This list includes the UE

Access Class for which the cell has to be considered as barred.

When sIB3AccClassBarredAc0 is set to True, the UEs that are defined with

Access Class 0 are only allowed to initiate Emergency call on this cell. One

parameter is defined at OMC for each Access Class, i.e. 16 parameters, from

sIB3AccClassBarredAc0to sIB3AccClassBarredAc15.

Parameter sIB3AccClassBarredAc0

Object LCell


Range & Unit Boolean{True, False}

Class Class 3

Value False

6.2. NEIGHBOURHOOD DEFINITION

6.2.1 3G MACRO NEIGHBOURHOOD

Auto-configuration first aims at generating an initial 3G Macro neighbouring cell list by

scanning and measuring pre-defined 3G Macro cells or frequencies which are

provided to BSR at switch-on.

FDDExtCellobject first provides pre-defined 3G Macro cells, identified by its

instance (mobileCountryCode.mobileNetworkCode.rncId.cellId) and:

o primaryScramblingCode

o fddFreqBand, dlFrequencyNumberandulFrequencyNumber

o routingAreaCodeand locationAreaCode


29/59




LCellMacroUmtsCellFrequencyList object may provide a list of UMTS

frequencies that can be scanned in case no FDDExtCell is declared or BSR

does not manage to get enough eligible 3G Macro cells (cf. next paragraphs):

o freqBand, uARFCNDLand uARFCNULare the parameters to be set

A neighbouring 3G Macro cell is considered as eligible to be broadcast into SIB11 if its

measured CPICH RSCP or CPICH EcNo level is above a certain threshold.

macroCellMeasurementQuantity defines the measurement quantity (either

CPICH RSCP or CPICH EcNo) that is used for the eligibility of a measured 3G

Macro cell.

Parameter macroCellMeasurementQuantity

Object LCell


Range & Unit Enum

{ecNO, rSCP}

Class Class 3

Value ecNO

macroCellRSCPThreshold defines the threshold applied to CPICH RSCP

above which a measured 3G Macro cell is considered as eligible when

macroCellMeasurementQuantityis set to rSCP.

Parameter macroCellRSCPThreshold

Object LCell



[-120-25]

Class Class 3

Value -115

Cf. recommendation below

macroCellEcNoThreshold defines the threshold applied to CPICH EcNo

above which a measured 3G Macro cell is considered as eligible when

macroCellMeasurementQuantityis set to ecNO.


30/59




Parameter macroCellEcNoThreshold

Object LCell



[-250]

Class Class 3

Value -16


Engineering Recommendation: macroCellRSCPThreshold and macroCellEcNoThreshold

Since 3G Macro neighbourhood is only used for Cell Reselection purpose (Blind HO only applies to

CS speech calls), macroCellRSCPThreshold and macroCellEcNoThreshold shall be setaccordingly to eligibility thresholds for Cell Reselection (cf. section 6.3.2.1):

umtsMacroCellRsInfoQRxLevMin and umtsMacroCellRsInfoQQualMin.

3G measurements are either performed:

by BSR itself in case 3G Network Listening feature is enabled; in that case,

BSR switches to a UE mode with receive-only capability and is able to

decode the 3G neighbourhood present in the best 3G Macros SIB11 to

improve its self-learning;

by requesting an UE to perform intra-frequency or inter-frequencymeasurements (using Compressed Mode if needed by UE); such

measurements are only applicable when a CS call is running.

umtsNtwkListenEnableFlagenables the 3G Network listening feature which

means BSR is able to measure 3G Macro cells by itself. When set to False,

UE is requested to perform such measurements.

Parameter umtsNtwkListenEnableFlag

Object BSRProfile

Granularity BSR ProfileRange & Unit Boolean

{True, False}

Class Class 3

Value True

umtsOpenSearchEnableFlag: when umtsNtwkListenEnableFlag is set to

True, this flag allows the reading of the best neighbouring cells SIB11 to

improve the knowledge of BSRs 3G neighbourhood.


31/59




Parameter umtsOpenSearchEnableFlag

Object BSRProfile



{True, False}

Class Class 3

Value True

BSR stops searching for eligible 3G Macro neighbours when more than

ratioMacroCellBelowThreshold percents of maximum 3G Macro cells to be

broadcast in SIB11 (macroCellListSIB11) respect RSCP or EcNo threshold.

macroCellListSIB11 defines the maximum number of 3G Macro

neighbouring cells to be broadcast in BSRs SIB11.

Parameter macroCellListSIB11

Object LCell



[132]

Class Class 3

Value 8*N3G_FREQ


ratioMacroCellBelowThreshold indicates the ratio of the number of 3G

macro cells out of the number of 3G macro cell detected that are above

macroCellEcNoThresholdor macroCellRSCPThresholddepending on the

chosen quality measurement.

Parameter ratioMacroCellBelowThreshold

Object LCell


Range & Unit Decimal

[0.01.0] range 0.1Class Class 3

Value 0.2


Engineering Recommendation: macroCellListSIB11 and ratioMacroCellBelowThreshold

Since ALU UTRAN can support up 4 carriers per BTS, it is recommended to define up to 8

neighbouring Macro 3G cells per available carrier, i.e. macroCellListSIB11=8*N3G_FREQ. Then,

recommending ratioMacroCellBelowThreshold=0.2makes BSR stops scanning 3G carriers when at

least 2 Macro 3G cells per available carrier are eligible.


32/59




Once such criterion is fulfilled, BSR periodically maintains its 3G Macro

neighbourhood every periodicMacroCellCheckdays.

Parameter periodicMacroCellCheckObject LCell


Range & Unit Decimal (days)

[1365]

Class Class 3

Value 3

6.2.2 GSM MACRO NEIGHBOURHOOD

2G Network Listening feature is not available in BCR2.1 timeframe. Therefore, the

generation of GSM Macro cells strongly relies on pre-configuration through the 2

following objects:

GsmExtCellobject first providing pre-defined GSM Macro cells, identified by

the mobileCountryCode.mobileNetworkCode.locationAreaCode.cellId

(i.e. cell global identifier) and:

o nCC andbCC

o gsmFrequBand andbCCHArfcn

o rAC

LCellGsmFrequencyListobject providing a list of BCCH ARFCN in case:

o no GsmExtCell is declared or BSR does not manage to get enough

eligible GSM Macro cells (cf. next paragraphs)

o and allowedGSMOpenSearchis set to True.

allowedGSMOpenSearch: when set to True, this flag allows:

o to scan the BCCH ARFCN list provided by one or several

LCellGsmFrequencyListobjects,

o and to improve GSM neighbourhood knowledge by reading the best

3G neighbouring cells SIB11 when umtsNtwkListenEnableFlag is

set to True(cf. section 6.1).


33/59




Parameter allowedGSMOpenSearch

Object LCell



{True, False}

Class Class 3

Value True

Note that only the GSM target cells that have been defined under GsmExtCellcan be

eligible to CS Blind Handover (cf. section 6.4.3) as locationAreaCode and rAC,

needed for Relocation procedure, can not be dynamically retrieved by BSR.

Contrary to 3G measurements, GSM measurements are only performed by requesting

an UE to perform GSM measurements (using Compressed Mode if needed by UE).

A neighbouring GSM Macro cell is considered as eligible to be broadcast into BSRs

SIB11 if its measured RSSI level is above gsmcellRSSIThresholdthreshold.

Parameter gsmCellRSSIThreshold

Object LCell



[-110-48]

Class Class 3

Value -101


Engineering Recommendation: gsmcellRSSIThreshold

gsmcellRSSIThreshold shall be set accordingly to gsmMacroCellRsInfoQRxLevMin (cf. section

6.3.2.2).

BSR stops searching for eligible GSM Macro neighbours when more than

ratioGSMCellAboveThreshold percents of maximum GSM Macro cells to bebroadcast in SIB11 (gsmCellListSIB11) respect gsmcellRSSIThresholdthreshold.


34/59




gsmCellListSIB11 defines the maximum number of GSM Macro

neighbouring cells to be broadcast in BSRs SIB11.

Parameter gsmCellListSIB11



[132]

Class Class 3

Value 10

ratioGSMCellAboveThreshold indicates the ratio of the number of GSM

macro cells out of the number of GSM macro cell detected that are above

gsmcellRSSIThreshold.

Parameter ratioGSMCellAboveThreshold

Object LCell



[0.01.0] range 0.1

Class Class 3

Value 0.2

With this recommended setting (ratioGSMCellAboveThreshold=0.2 and

gsmCellListSIB11=10), BSR stops scanning GSM carriers when at least 10*0.2=2GSM Macro cells are eligible.

Once such criterion is fulfilled, BSR periodically maintains its GSM Macro

neighbourhood every periodicGSMCellCheckdays.

Parameter periodicGSMCellCheck

Object LCell


Range & Unit Integer (days)

[1365]

Class Class 3

Value 3

6.3. CELL RESELECTION

In BCR2.1, HCS (Hierarchical Cell Structure) is NOT implemented and classical cell

reselection algorithms are used, as defined per [3GPP_R01] and explained hereafter.

Moreover, SIB4 & SIB12 are NOT supported so that Cell Reselection information isonly broadcast into SIB3 and SIB11.


35/59




The following parameters are broadcast in SIB3 or SIB11, and detailed in the coming

sections:

SIB3 for cell reselection parameters related to the serving cell

o qQualMin

o qRxLevMin

o maximumAllowedULTXPower

o sIntraSearch

o sInterSearch

o sSearchRAT

o sHCSRAT

o sSearchHCS

o sIB3CrQualityMeasure

o sib3qHyst1s

o sib3qHyst2s

o sIB3InterRATScalingFactor

o sIB3InterFreqScalingFactor

o sIB3TReselection

SIB11 for cell reselection parameters related to the neighbouring cells

o umtsMacroCellRsInfoQQualMin

o umtsMacroCellRsInfoQRxLevMin

o umtsMacroCellRsInfoQOffset1s

o umtsMacroCellRsInfoQOffset2s

o umtsMacroCellRsInfoMaxAllowedULTXPwr

o gsmMacroCellRsInfoQRxLevMin

o gsmMacroCellRsInfoQOffset1s

o gsmMacroCellRsInfoMaxAllowedULTXPwr

o interBSRCellRsInfoQQualMin

o interBSRCellRsInfoQRxLevMin

o interBSRCellRsInfoQOffset1s

o interBSRCellRsInfoQOffset2s

o interBSRCellRsInfoMaxAllowedULTXPwr


36/59




6.3.1 CELL RESELECTION MEASUREMENT RULES

Squaland possibly Srxlevof the BSR serving cell is compared to different threshold

broadcast in the System Information to determine which kind of measurement (intra-

frequency, inter-frequency and inter-RAT) the UE shall do.

Squalis defined by Squal= Qqualmeas qQualMin

Srxlevis defined by Srxlev= Qqualmeas qRxLevMin + Pcompensation

where:

Pcompensation= max (maximumAllowedUlTxPower- P_MAX, 0)

P_MAX = maximum UE output power (dBm) according to its power class.

Power (dBm)Operating Band

Class 1 Class 2 Class 3 Class 4

I UMTS 2100 MHz +33 +27 +24 +21

II UMTS 1900 MHz N.A. N.A. +24 +21

V UMTS 850 MHz (not supported by BSR) N.A. N.A. +24 +21

VI UMTS 850 MHz (not supported by BSR) N.A. N.A. +24 +21

VIII UMTS 900 MHz (not supported by BSR) N.A. N.A. +24 +21

Table 1: UE power Class vs. maximum output power

Parameter qQualMin

Object LCell


Range & Unit Decimal (dB)

[-24...0]

Class Class 3

Value -15

Parameter qRxLevMin

Object LCell


Range & Unit Decimal (dBm)

[-115..-25] step 2

Class Class 3

Value -111


37/59




Parameter maximumAllowedULTXPwr

Object LCell



[-5033]

Class Class 3

Value 24

In order to limit the time during which the mobile performs measurements on UMTS

and GSM neighbouring cells, criteria for neighbour cells tracking and measurements

are applied.

6.3.1.1 INTRA-FREQUENCY MEASUREMENTS

Squalis compared with the parameter sIntraSearch:

If Squal > sIntraSearch, the UE does not perform intra-frequency

measurements.

If Squal!sIntraSearch, the UE performs intra-frequency measurements.

If sIntraSearch is not sent for the serving cell, the UE performs intra-

frequency measurements.

BSR also makes use of the optional parameter sSearchHCSwhich is a threshold to

be compared with Srxlev in order to define Intra- and Inter-frequency measurements.

Refer to Figure 2 to get a view on measurement decision based on Squaland Srxlev.

6.3.1.2 INTER-FREQUENCY MEASUREMENTS

Squalis compared with the parameter sInterSearch:

If Squal > sInterSearch, the UE does not perform inter-frequency

measurements.

If Squal!sInterSearch, the UE performs inter-frequency measurements.

If sInterSearch is not sent for the serving cell, the UE performs inter-

frequency measurements.


38/59




6.3.1.3 INTER-RAT MEASUREMENTS

Squalis compared with the parameter sSearchRAT:

If Squal > sSearchRAT, the UE does not perform measurements on GSM

cells.

If Squal!sSearchRAT, the UE performs measurements on GSM cells.

If sSearchRAT is not sent for the serving cell, the UE performs

measurements on GSM cells.

BSR also makes use of the optional parameter sHCSRAT which is a threshold to be

compared with Srxlev in order to define GSM measurements.

If sHCSRAT is not sent, GSM measurement is only defined by comparing

Squal and sSearchRAT(cf. above conditions)

If sHCSRAT is sent, refer to Figure 2 to get a view on GSM measurement

decision based on Squaland Srxlev.

6.3.1.4 MEASUREMENT TRIGGERS PARAMETERS

The following tables present the parameters used by the UE to decide whether or not

to perform intra-frequency, inter-frequency or inter-rat measurements.

Parameter sIntraSearch

Object LCell



[-32..20] step 2

Class Class 3


Note: If a negative value is datafilled and sent in SIB3, the UE shall consider the value

to be 0 (see [3GPP_R02]).

Note: The value broadcast in SIB3/4 is half the real value sIntraSearch

Engineering Recommendation: sIntraSearch

sIntraSearchsetting depends on the deployment scenario for FEMTO:

In case FEMTO is deployed by a private and standalone user, sIntraSearchshall be set to 2

so as to delay Intra-frequency measurements as much as possible.

Otherwise, sIntraSearchshall be set to 9.


39/59


40/59




Parameter sHCSRAT

Object LCell



[-1..91] step 2

Class Class 3

Value 0

Note: If a negative value is datafilled and sent in SIB3, the UE shall consider the value

to be 0 (see [3GPP_R02]).

Note: The value broadcast in SIB3 is half the real value sHCSRAT

The following picture depicts the decision for selecting Intra-frequency, Inter-frequency

or GSM measurements based on the different thresholds presented before and Squal

and Srxlev levels of the FDD cell selected by UE.

Intra-frequency No measurement

Intra-frequencyInter-frequency

Inter-frequency

Intra-frequencyInter-frequency

GSM

Inter-frequency

GSM

Srxlev

sInterSearch sIntraSearchsSearchRAT

sSearchHCS

sHCSRAT

Squal

Figure 2: Decision thresholds for Measurement

6.3.2 CELL ELIGIBILITY CRITERIA

Once the criteria for measurement decision is hit, UE shall measure the neighbouring

cells that are broadcast in SIB11; there are 3 different categories of neighbouring cell:

3G Macro neighbouring cells

BSR neighbouring cells

GSM neighbouring cells

In the coming sections, UMTS neighbouring cell stands for either 3G Macro or BSR

neighbouring cell.

umtsMacroCellRsInfoEnableBroadcast: when set to True, this flagallows to

broadcast the 3G Macro neighbouring cells in SIB11. When set to False, the

broadcast is inhibited.


41/59




Parameter umtsMacroCellRsInfoEnableBroadcast

Object LCell



{True, False}

Class Class 3

Value True

gsmMacroCellRsInfoEnableBroadcast: when set to True, this flagallows to

broadcast the GSM neighbouring cells in SIB11. When set to False, the


Parameter gsmMacroCellRsInfoEnableBroadcast

Object LCell



{True, False}

Class Class 3

Value True

interBSRCellRsInfoEnableBroadcast: when set to True, this flag allows to

broadcast the BSR neighbouring cells in SIB11. When set to False, the


Parameter interBSRCellRsInfoEnableBroadcast

Object LCell



{True, False}

Class Class 3


Engineering Recommendation: interBSRCellRsInfoEnableBroadcast

In case FEMTO is deployed as part of an Enterprise network (substituting Pico network),

interBSRCellRsInfoEnableBroadcastshall be set to Trueso as inter-BSR mobility is allowed.

In case FEMTO is deployed by a private and standalone user, interBSRCellRsInfoEnableBroadcast

shall be set to False.

Following measurement decision and SIB11 decoding, UE applies criterion S on the

measured GSM or UMTS neighbouring cells to assess their eligibility to cell

reselection, as presented in the following sections.


42/59




6.3.2.1 3G NEIGHBOURING CELL CRITERIA

To be eligible, the 3G Macro (intra and/or inter-frequency) and BSR neighbouring cells

must fulfill the following criterion:

Squal> 0 ANDSrxlev> 0

i.e.

Qqualmeas> qQualMinAND Qrxlevmeas> qRxLevMin+ Pcompensation

i.e.

CPICH_Ec/No > qQualMinAND CPICH_RSCP > qRxLevMin+ Pcompensation

Where Pcompensation= max (maxAllowedUlTxPower- P_MAX, 0)

Note: These relationships shall be verified on the 3G Macro neighbouring cell and

possibly on BSC neighbouring cell.

Parameter umtsMacroCellRsInfoQQualMin

Object LCell



[-24...0]

Class Class 3

Value -16

Parameter umtsMacroCellRsInfoQRxLevMin

Object LCell



[-115...-25] step 2

Class Class 3

Value -115Note: As per 3GPP, IE present in SIB is encoded as follows: qRxLevMin= (IE * 2) +1

Parameter umtsMacroCellRsInfoMaxAllowedULTXPwr

Object LCell



[-5033]

Class Class 3

Value 24


43/59




Parameter interBSRCellRsInfoQQualMin

Object LCell



[-24...0]

Class Class 3

Value -15

Parameter interBSRCellRsInfoQRxLevMin

Object LCell



[-115...-25] step 2

Class Class 3

Value -111

Note: As per 3GPP, IE present in SIB is encoded as follows: qRxLevMin= (IE * 2) +1

Parameter interBSRCellRsInfoMaxAllowedULTXPwr

Object LCell



[-5033]

Class Class 3

Value 24

6.3.2.2 GSM NEIGHBOURING CELL CRITERIA

To be eligible, the inter-system GSM cells must fulfill the following criteria:

SrxLev> 0

i.e.

QRxLevMeas> qRxLevMin+ Max (MaxAllowedUlTxPower Pmax, 0)

Neighbouring cell which does not fulfill these criteria can not be eligible to reselection.


44/59




Parameter gsmMacroCellRsInfoQRxLevMin

Object LCell



[-115...-25] step 2

Class Class 3

Value -101


Note: As per 3GPP, IE present in SIB is encoded as follows: qRxLevMin= (IE * 2) +1

Engineering Recommendation: qRxLevMin

It is recommended to align the value of gsmMacroCellRsInfoMaxAllowedULTXPwr with the used

2G rxLevAccessMinparameter present in the GSM network.The difference between GSM 900/GSM 850 and GSM 1800/1900 is due to MS sensitivity:

GSM 900: -104 dBm,

GSM 1800: -102 dBm.

Parameter gsmMacroCellRsInfoMaxAllowedULTXPwr

Object LCell


Range & Unit Decimal (dBm)[-5033]

Class Class 3

Value Refer to following recommendation

Engineering Recommendation: gsmMacroCellRsInfoMaxAllowedULTXPwr

The value of gsmMacroCellRsInfoMaxAllowedULTXPwr shall be set according to the GSM band

which is used on the 2G network, taking also into account the classes of the mobiles ( cf.

[3GPP_R03]).

The following values can be used as a starting point when no information is available from 2G:

33 for GSM 900 MHz Cells

30 for GSM 1800 MHz Cells


45/59




Nominal Maximum output PowerPower Class

GSM400, GSM 850 & GSM 900 DCS 1800 PCS 1900

1 1 W (30 dBm) 1 W (30 dBm)

2 8 W (39 dBm) 0.25 W (24 dBm) 0.25 W (24 dBm)

3 5 W (37 dBm) 4 W (36 dBm) 2 W (33 dBm)

4 2 W (33 dBm)

5 0.8 W (29 dBm)

Table 2: Maximum output power for GSM mobiles

6.3.3 CELL RESELECTION RANKING CRITERION

The cell ranking criterion is used to rank the cells prior to the reselection.

The cell-ranking criterion for serving cell is:

Rs= Qmeas,s + qHyst,s

When sIB3CrQualityMeasure = CPICH_Ec/N0:

Rs=Ec/No + sib3qHyst2s

When sIB3CrQualityMeasure =CPICH_RSCP:

Rs=RSCP +

sib3qHyst1s

Cell ranking criterion for neighbouring cells is:

Rn= Qmeas,n Qoffset s,n

Where:

Qmeas,n = CPICH_Ec/N0or CPICH_RSCP for FDD cells. For GSM cells, the

RxLev (average received signal level) is used instead of CPICH Ec/N0 or

CPICH RSCP in the mapping function.

Qoffset s,n specifies the offset between the serving cell and the neighbouring

cell; it can have two different values:

o qOffset1sn is used with GSM cells or UMTS cells when the quality

measure for cell selection and re-selection is set to CPICH RSCP.

o qOffset2snis only used for UMTS cells when the quality measure for

cell selection and re-selection is set to CPICH EC/N0.

The cells (serving and neighbouring) will be ranked according to the R criterion.


46/59




6.3.3.1 FIRST RANKING

Among the GSM and UMTS Cells verifying S criterion, UE shall perform ranking

according to ranking R criterion, as specified above.

In a first step, the mobile shall always consider the CPICH RSCP / RxLev

measurement and associated set of parameters (qHyst1, qOffset1sn):

Serving Cell: Rs= CPICH_RSCP + sib3qHyst1s

Eligible UMTS Neighbour cell: RnUMTS= CPICH_RSCP qOffset1sn

Eligible GSM Neighbour cell: RnGSM= RxLev qOffset1sn

sib3qHyst1sis the hysteresis value of the serving BSR cell. It is used in the

process of Cell Reselection of cell by the UE when the quality measure for cell

selection and re-selection is the CPICH RSCP.

Parameter sib3qHyst1s

Object LCell


Range & Unit Integer (dBm)

[040] range 2

Class Class 3

Value 2

umtsMacroCellRsInfoQOffset1sis the offset between the BSR cell and one

of its 3G Macro neighbouring cells, in case the quality measure for cell

selection/reselection is set to RSCP.

Parameter umtsMacroCellRsInfoQOffset1s

Object LCell



[-5050] range 2

Class Class 3

Value 0

interBSRCellRsInfoQOffset1sis the offset between the BSR cell and one of

its BSR neighbouring cells, in case the quality measure for Cell Reselection is

set to RSCP.


47/59




Parameter interBSRCellRsInfoQOffset1s

Object LCell



[-5050] range 2

Class Class 3

Value 0

gsmMacroCellRsInfoQOffset1s is the offset between the BSR cell and one

of its GSM neighbouring cells.

Parameter gsmMacroCellRsInfoQOffset1s

Object LCell



[-5050] range 2

Class Class 3

Value 0

Then the cell reselection process is as follows (as specified in [3GPP_R01]):

If a GSM cell is ranked as the best cell, then the UE shall perform cell re-

selection to that GSM cell.

If an UMTS cell is ranked as the best cell and the quality measure parameter

sIB3CrQualityMeasure for cell re-selection is set to rSCP, then UE shall

perform cell re-selection to that UMTS cell.

If an UMTS cell is ranked as the best cell and the quality measure parameter

sIB3CrQualityMeasure for cell re-selection is set to eCN0, then UE shall

perform a second ranking.

Parameter sIB3CrQualityMeasure

Object LCell


Range & Unit Enum

{ecN0, rSCP}

Class Class 3

Value ecN0

6.3.3.2 SECOND RANKING

In case an UMTS cell is ranked as the best cell according to the first ranking, a second

ranking of the UMTS cells is applied at the CPICH EC/NOcase with the associated set

of parameters (qHyst2, qOffset2sn):


48/59




Serving Cell: Rs= CPICH_Ec/No + qHyst2

Eligible UMTS Neighbour cell: RnUMTS= CPICH_Ec/No qOffset2sn

sib3qHyst2sis the hysteresis value of the serving BSR cell. It is used in the

process of Cell Reselection of cell by the UE when the quality measure for cell

selection and re-selection is the CPICH EcNo.

Parameter sib3qHyst2s

Object LCell



[040] range 2

Class Class 3

Value 2

umtsMacroCellRsInfoQOffset2sis the offset between the BSR cell and one

of its 3G Macro neighbouring cells, in case the quality measure for Cell

Reselection is set to EcNo.

Parameter umtsMacroCellRsInfoQOffset2s

Object LCell


Range & Unit Integer (dB)[-5050] range 2

Class Class 3

Value 0

interBSRCellRsInfoQOffset2sis the offset between the BSR cell and one of

its BSR neighbouring cells, in case the quality measure for Cell Reselection is

set to EcNo.

Parameter interBSRCellRsInfoQOffset2s



[-5050] range 2

Class Class 3

Value 0

6.3.3.3 TARGET CELL SELECTION

Following these rankings, the UE shall perform cell re-selection to the best-rankedUMTS or GSM cell.


49/59




In any case, the UE shall reselect the new cell when both following conditions are met:

The new cell is better ranked than the serving cell during sib3TReselection

time interval.

More than 1 second has elapsed since the UE camped on the current serving

cell.

Parameter sib3TReselection

Object LCell


Range & Unit Integer (s)

[031]

Class Class 3

Value 1

Several scaling factors, introduced by 3GPP R5 (and thus only considered by R5

UEs), can be applied to sib3TReselection:

sib3InterFreqScalingFactor between 1 and 4.75, in order to delay the

reselection to Inter-frequency neighbouring cell.

sib3InterRATScalingFactor between 1 and 4.75, in order to delay the

reselection to GSM neighbouring cell.

Parameter sib3InterFreqScalingFactor

Object LCell



[14.75] step 0.25

Class Class 3

Value 1.5

Note: IE present in SIB is encoded as follows: sib3InterFreqScalingFactor = IE *

0.25

Parameter sib3InterRATScalingFactor

Object LCell



[14.75] step 0.25

Class Class 3

Value 2

Note: IE present in SIB is encoded as follows: sib3InterRATScalingFactor = IE *0.25


50/59




6.4. HARD HANDOVER

In BCR2.1 release, BSR only supports Blind HO to Macro cell (either 3G or 2G) for CSspeech calls due to radio degradation. This means that:

No action is performed when standalone PS call is running.

In case of multi-service (CS+PS), PS call is first released then handover is

triggered.

6.4.1 ELIGIBILITY FOR HANDOVER

When a CS (resp. CS+PS) call is running, BSR checks the eligibility for blind

handover using the following activation flag targetHOCS (resp. targetHOCSPS)

whose behaviour is as follows:

When set to disable, handover is disabled and CS call eventually drops if

radio condition keeps on degrading.

When set to fdd, only handover to Macro 3G may occur.

When set to gsm, only handover to Macro 2G may occur.

When set to fddPreferred, handover to Macro 3G is the preference but HO to

Macro 2G may occur as a backup if needed.

When set to gsmPreferred, handover to Macro 2G is the preference but HO toMacro 3G may occur as a backup if needed.

Parameter targetHOCS

Object LCell


Range & Unit Enumerated

{disable, fdd, gsm, fddPreferred, gsmPreferred}

Class Class 3

Value fddPreferredCf. recommendation hereafter


51/59




Parameter targetHOCSPS

Object LCell




Class Class 3

Value fddPreferred


Note: targetHOPSis present in OAM Model even though not used.

Parameter targetHOPS

Object LCell




Class Class 3

Value disable


Engineering Recommendation: targetHO

For CS and CS+PS, it is recommended to perform blind HO to Macro 3G as much as possible;

however, blind HO to GSM should be considered as a backup in case no 3G neighbouring cells is

available. Therefore, targetHOCSand targetHOCSPSmust be set to fddPreferred.

Since Blind HO while in standalone PS is not supported, targetHOPSmust be set to disable.

6.4.2 DETECTING RADIO DEGRADATION

Each time BSR detects the need for radio degradation assessment (i.e. when

targetHOCSor targetHOCSPSare NOT set to disable), 2 Events are configured at

UE side, as per [3GPP_R02]:

Radio is degrading: Event 2D is reported by UE when BSR CPICH Ec/No orCPICH Rscp becomes below a certain threshold;

Radio is back to normal: Event 2F is reported by UE when BSR CPICH Ec/No

or CPICH Rscp becomes above a certain threshold.


52/59




The following setting is used for Event 2D EcNo:

Parameter blindHO2d2fEcnoThreshold2d

Object LCell

Granularity BSR ProfileRange & Unit Decimal (dB)

[-240]

Class Class 3


Parameter blindHO2d2fEcnoTimeToTrigger2d

Object LCell


Range & Unit Enumerated (s)








Class Class 3


Parameter blindHO2d2fEcnoHysteresis2d

Object LCell



[0...14.5] step 0.5

Class Class 3


The following setting is used for Event 2D Rscp:

Parameter blindHO2d2fRscpThreshold2d

Object LCell



[-115-25]

Class Class 3



53/59




Parameter blindHO2d2fRscpTimeToTrigger2d

Object LCell










Class Class 3


Parameter blindHO2d2fRscpHysteresis2d

Object LCell



[0...14.5] step 0.5

Class Class 3


The following setting is used for Event 2F EcNo:

Parameter blindHO2d2fEcnoThreshold2f

Object LCell



[-240]

Class Class 3



54/59




Parameter blindHO2d2fEcnoTimeToTrigger2f

Object LCell










Class Class 3


Parameter blindHO2d2fEcnoHysteresis2f

Object LCell



[0...14.5] step 0.5

Class Class 3


The following setting is used for Event 2F Rscp:

Parameter blindHO2d2fRscpThreshold2f

Object LCell



[-115-25]

Class Class 3



55/59




Parameter blindHO2d2fRscpTimeToTrigger2f

Object LCell










Class Class 3


Parameter blindHO2d2fRscpHysteresis2f

Object LCell



[0...14.5] step 0.5

Class Class 3


The following table resumes the recommendations for 2D setting:

blindHO2d2fEcnoThreshold2d -14 dB -12 dB blindHO2d2fEcnoThreshold2f

blindHO2d2fEcnoTimeToTrigger2d 1280 ms blindHO2d2fEcnoTimeToTrigger2f

blindHO2d2fEcnoHysteresis2d 1 dB blindHO2d2fEcNoHysteresis2f

The following table resumes the recommendations for 2F setting:

blindHO2d2fRscpThreshold2d -105 dB -103 dB blindHO2d2fRscpThreshold2f

blindHO2d2fRscpTimeToTrigger2d 1280 ms blindHO2d2fRscpTimeToTrigger2f

blindHO2d2fRscpHysteresis2d 1 dB blindHO2d2fRscpHysteresis2f

6.4.3 HANDOVER EXECUTION

Once UE has reported an Event 2D, BSC tries to find an eligible target cell starting

from the Macro 3G and/or 2G neighbourhood built during auto-configuration and self-

optimisation steps (cf. section 6.2).

A Macro neighbouring cell is eligible to Blind handover if it fulfills the following

conditions:


56/59




Frequency band is supported by UE

Radio level (if previously determined by BSR) is above a certain threshold

o minBlindHoUmtsMacroEcNo and minBlindHoUmtsMacroRSCP

for Macro 3G;

o minBlindHoGsmMacroRSSI for Macro 2G.

Parameter minBlindHoUmtsMacroEcNo

Object LCell



[0...49]

Class Class 3

Value 22

(i.e. -13 dB, cf. formula hereafter)

Parameter minBlindHoUmtsMacroRSCP

Object LCell



[0...91]

Class Class 3

Value 15(i.e. -100 dBm, cf. formula hereafter)

Parameter minBlindHoGsmMacroRSSI

Object LCell



[0...63]

Class Class 3

Value 10

(i.e. -100 dBm, cf. formula hereafter)

The following formulas apply to get the real threshold:

3G EcNo: real_threshold [dB] = -24 + minBlindHoUmtsMacroEcNo / 2

3G Rscp: real_threshold [dBm] = -115 + minBlindHoUmtsMacroRSCP

2G RSSI: threshold [dBm] = -110 +minBlindHoGsmMacroRSSI

BSC then builds a list of eligible Macro 3G (resp. 2G) neighbours ranked using EcNo

(resp. RSSI) if available, else Rscp.


57/59




Note: among GSM neighbouring cells, only those provisioned under GsmExtCellare

eligible to Blind HO as they contain the mandatory information (locationAreaCode

and rAC) for RANAP Relocation procedures that would not have been dynamically

retrieved by BSR itself.

Finally, depending on targetHOCSor targetHOCSPSvalues (cf. section 6.4.1), BSC

triggers the handover to the best ranked eligible cell. If relocation fails, a new attempt

is made on the next eligible cell until handover succeeds or eligible cell list is empty.

In such a case, handover to the other access can be performed if fddPreferred or

gsmPreferredis selected.

Note: In case of multi-service CS+PS, Iu PS is released before performing thehandover.


58/59




7. INDEXES

7.1. TABLE INDEX

Table 1: UE power Class vs. maximum output power .......................................................................... 36Table 2: Maximum output power for GSM mobiles ............................................................................... 45

7.2. FIGURE INDEX

Figure 1: BSR OAM Model...................................................................................................................... 9Figure 2: Decision thresholds for Measurement.................................................................................... 40


59/59


!!!!END OF DOCUMENT """"

Documents

FEMTO Parameter User Guide 01.01