TLA2.1 LPUG 02.06 Volume 6 Mobility Approved Preliminary External

LTE/DCL/APP/031549
TDD ENODEB LTE PARAMETERS USER GUIDE
V02.06 / EN
27 APR 2011
EXTERNAL
LTE PARAMETERS USER GUIDE

VOLUME 6
MOBILITY
Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written authorization
Alcatel-Lucent-Proprietary
External
TDD eNodeB LTE Parameters User Guide
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Approved-Preliminary
Volume 6 : Mobility
Copyright 2010 by Alcatel-Lucent. All Rights Reserved.

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.
About Alcatel-Lucent
Alcatel-Lucent (Euronext Paris and NYSE: ALU) provides solutions that enable service providers,
enterprises and governments worldwide, to deliver voice, data and video communication services to
end-users. As a leader in Fixed, mobile and converged broadband networking, IP technologies,
applications, and services, Alcatel-Lucent offers the end-to-end solutions that enable compelling
communications services for people at home, at work and on the move. For more information, visit
Alcatel-Lucent on the Internet:
http://www.alcatel-lucent.com
Notice
The information contained in this document is subject to change without notice. At the time of
publication, it reflects the latest information on Alcatel-Lucents offer, however, our policy of
continuing development may result in improvement or change to the specifications described.
Trademarks
Alcatel, Lucent Technologies, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of AlcatelLucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no
responsibility for inaccuracies contained herein.
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
CONTENTS AND PARAMETER GUIDE

1
INTRODUCTION..............................................................................................................................10
1.1
OBJECT ...................................................................................................................................10
1.2
SCOPE OF THIS VOLUME ........................................................................................................10
1.3
LIST OF RELATED FEATURES ............................................................................................11
RELATED DOCUMENTS AND PREREQUISITES.........................................................................12

2.1
LPUG VOLUMES ......................................................................................................................12
2.2
REFERENCE DOCUMENTS..........................................................................................................12
2.3
PREREQUISITES FOR READING THIS VOLUME ...............................................................13
OVERVIEW ......................................................................................................................................13
INTRA-RAT MOBILITY FOR LTE ...................................................................................................14

4.1
INTRA-FREQUENCY MOBILITY FOR LTE .....................................................................................14
4.1.1
RRC IDLE MODE MOBILITY ...........................................................................................14
4.1.1.1
INTER TRACKING AREA MOBILITY:.........................................................................15
LteCell::trackingAreaCode................................................................................15
LteNeighboringCellRelation::trackingAreaCode.............................................16
4.1.1.2
4.1.1.3
4.1.1.3.1
PLMN Selection & CELL RESERVATION and CELL RESTRICTION: .......................16

CELL RESELECTION ALGORITHM DESCRIPTION .................................................16
CELL SELECTION CRITERION......................................................................................16
CellSelectionReselectionConf::qRxLevMin.....................................................18
CellSelectionReselectionConf::qRxlevminoffset ............................................18
CellSelectionReselectionConf::sIntraSearch ..................................................19
CellSelectionReselectionConf::measurementBandwidth ..............................19
4.1.1.3.2
INTRA-FREQUENCY AND EQUAL PRIORITY INTER-FREQUENCY CELL
RESELECTION CRITERIA .......................................................................................................................21
CellSelectionReselectionConf::qHyst..............................................................22
CellSelectionReselectionConf::tReselectionEUTRAN....................................23
LteNeighboringCellRelation::qOffsetCell ........................................................24
CellSelectionReselectionConf::qRxLevMinIntraFreqNeighbour ...................25
4.1.1.3.3
UE SPEED MANAGEMENT ............................................................................................25

SpeedStateEvalBroadcastConf::tEvaluation...................................................26
SpeedStateEvalBroadcastConf::nCellChangeHigh ........................................27
SpeedStateEvalBroadcastConf::nCellChangeMedium...................................28
SpeedStateEvalBroadcastConf::tHystNormal.................................................28
SpeedStateEvalBroadcastConf::qHystSfHigh.................................................29
LteSpeedConf::tReselectionEutraSfHigh ........................................................30
SpeedStateEvalBroadcastConf::qHystSfMedium ...........................................31
LteSpeedConf::tReselectionEutraSfMedium...................................................32
4.1.1.3.3.1 .......... MIM MODEL

32
4.1.2
RRC connected MODE MOBILITY...................................................................................34
4.1.2.1
MOBILITY ACTIVATION..............................................................................................36
ActivationService:: isIntraFreqMobilityAllowe ................................................36
4.1.2.2
4.1.2.2.1
4.1.2.3
INTRA-FREQUENCY INTRA-eNB MOBILITY ............................................................37

Key Refresh or Re-keying...................................................................................................40
INTRA-FREQUENCY INTER-eNB X2 Handover .....................................................41
Page 1/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ActivationService::isDataForwardingAllowed.................................................45
RadioBearerConf::dataForwardingForX2HoEnabled .....................................46
X2GtpConf::endX2HoDataFwdTarget ..............................................................48
4.1.2.3.1
4.1.2.3.2
4.1.2.4
4.1.2.4.1
4.1.2.4.2
4.1.2.4.3
Failure Cases .......................................................................................................................48

FEATURE INTERACTIONS.............................................................................................50
INTRA-FREQUENCY Inter-eNB S1 Handover.........................................................51
Failure Cases .......................................................................................................................55
Feature Interactions .............................................................................................................56
S1 Handover Parameters .....................................................................................................57
ActivationService::isS1HoAllowed...................................................................58
RadioBearerConf::dataForwardingForS1HoEnabled .....................................58
X2Access::directFwdPathAvailability ..............................................................59
S1HoTimersConf:: tS1RelocPrepForS1Handover...........................................60
S1HoTimersConf:: tS1RelocOverallForS1Handover ......................................61
S1HoTimersConf::endS1HoDataFwdTarget ....................................................62
4.1.2.5
INTRA-FREQUENCY MEASUREMENT REPORTING SETTING ..............................62

MeasurementIdentityConf::measurementPurpose .........................................63
MeasurementIdentityConf::measObjectId .......................................................64
MeasurementIdentityConf:: reportConfigId.....................................................64
ReportConfig:: reportConfigId..........................................................................64
4.1.2.5.1
4.1.2.5.2
Measurement setup upon transition to RRC-Connected state .............................................65

Measurement update upon completion of handover ...........................................................66
MeasObjectEUTRA::dlEARFCN ........................................................................69
MeasObjectEUTRA::measurementBandwidth.................................................69
MeasObjectEUTRA::offsetFreq.........................................................................70
4.1.2.5.3
4.1.2.6
EventA3 and HO Measurement: ALGORITHM and CONFIGURATION ........................70

NEIGHBOR CELL INFORMATION PROVIDED TO UES IN CONNECTED MODE...73
LteNeighboringCellRelation::cellIndividualOffset ..........................................74
4.1.2.7
MOBILITY TRIGGER MANAGEMENT ........................................................................74
4.1.2.7.1
Intra-frequency handover ....................................................................................................74
4.1.2.7.2
Reception of a RRCConnection including the mobility ControlInformation by the UE
(handover)
75
UeTimers::t304 ...................................................................................................77
4.1.2.7.3
TARGET CELL SELECTION ...........................................................................................78

LteNeighboringCellRelation::noHO..................................................................79
X2Access::noX2HO ...........................................................................................80
LteNeighboringCellRelation::relativeCellIdentity............................................80
LteNeighboringCellRelation::macroEnbId.......................................................81
LteNeighboringCellRelation::physicalLayerCellIdentityGroupIndex ............82
LteNeighboringCellRelation::physicalLayerCellIdentityIndex .......................82
LteNeighboringCellRelation::plmnMobileCountryCode.................................83
LteNeighboringCellRelation::plmnMobileNetworkCode ................................83
4.1.2.7.4
HANDOVER TYPE SELECTION.....................................................................................84
4.1.2.7.4.1 .......... X2-C INTERFACE NOT AVAILABLE
84
4.1.2.7.5
TARGET eNB NOT CONNECTED TO SERVING MME................................................85
4.1.2.7.5.1 .......... X2 HANDOVER REJECTED WITH APPROPRIATE CAUSE 87
4.1.2.7.5.2 .......... Selection of S1 HANDOVER or X2 HANDOVER BASED ON CONFIGURATION
........................... 88
4.2
INTER-FREQUENCY MOBILITY FOR LTE .....................................................................................88
4.2.1
RRC IDLE MODE MOBILITY ...........................................................................................88
4.2.1.1
CELL RESELECTION activation .................................................................................89
ActivationService:: isCellReselectionToInterFreqAllowed ...........................89
4.2.1.2
4.2.1.3
4.2.1.3.1
SYSTEM INFORMATION BLOCK TYPE5 ..................................................................89

CELL RESELECTION ALGORITHM DESCRIPTION .................................................89
CELL SELECTION CRITERION......................................................................................89
Page 2/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
CellReselectionConfInterFreq::qRxLevMin .....................................................90
CellSelectionReselectionConf::sNonIntraSearch ...........................................91
LteNeighboringFreqConf::measurementBandwidth.......................................91
4.2.1.3.2
EQUAL PRIORITY INTER-FREQUENCY CELL RESELECTION CRITERIA ............91

CellReselectionConfInterFreq:: cellReselectionPriority.................................92
CellReselectionConfInterFreq:: offsetFreq......................................................92
LteNeighboringFreqConf:: priorityOfFreq .......................................................92
4.2.1.3.3
E-UTRAN INTER-FREQUENCY CELL RESELECTION CRITERIA ...........................93

CellReselectionConfInterFreq:: threshXHigh ..................................................93
CellReselectionConfInterFreq:: threshXLow...................................................93
CellReselectionConfInterFreq:: tReselectionEUTRAN ...................................94
4.2.2
RRC connected MODE MOBILITY...................................................................................94
4.2.2.1
MOBILITY ACTIVATION..............................................................................................94
ActivationService:: isInterFreqHOAllowed......................................................94
ActivationService :: isInterFreqBlindRedirectionAllowed..............................95
4.2.2.2
4.2.2.2.1
4.2.2.2.2
4.2.2.2.3
4.2.2.3
4.2.2.3.1
INTER-FREQUENCY INTer-eNB HO..........................................................................95

Trigger of handover.............................................................................................................95
INTER-FREQUENCY INTER-eNB X2 Handover .........................................................95
INTER-FREQUENCY Inter-eNB S1 Handover..............................................................95
INTER-FREQUENCY MEASUREMENT REPORTING SETTING ..............................96
MEASUREMENT UPDATE UPON COMPLETION OF HANDOVER ..........................96
LteNeighboringFreqConf::dlEARFCN ..............................................................96
4.2.2.4
Measurements CONFIGURATION..............................................................................96
4.2.2.4.1
measurement configuration for inter-freq HO.....................................................................97
4.2.2.4.2
measurement configuration for blind redirection ................................................................97
4.2.2.4.3
measurement configuration for gap.....................................................................................97
4.2.2.4.4
Inter-frequency measurement at call setup..........................................................................97
4.3
MEASUREMENTS CONFIGURATION .....................................................................................101
4.3.1
MEASUREMENT CONFIGURATION MODEL...............................................................101
4.3.1.1
RrcMeasurementConf................................................................................................102
RrcMeasurementConf::filterCoefficientRSRP ...............................................103
RrcMeasurementConf::filterCoefficientRSRQ...............................................104
RrcMeasurementConf::measurementIdentityConfIdList..............................105
RrcMeasurementConf::sMeasure...................................................................106
4.3.1.2
REPORTCONfig/reportconfig EUTRA.......................................................................107
ReportConfigEUTRA::triggerQuantity ...........................................................107
ReportConfigEUTRA::reportQuantity ............................................................108
ReportConfigEUTRA::maxReportCells ..........................................................110
ReportConfigEUTRA::hysteresis....................................................................112
ReportConfigEUTRA::timeToTrigger .............................................................114
ReportConfigEUTRA::reportInterval ..............................................................115
ReportConfigEUTRA::reportAmount .............................................................116
4.3.1.3
Blind
THRESHOLDS FOR INTER-RAT MOBILITY WITH INTRA-LTE MEASUREMENTS:

117
ReportConfigEUTRA::triggerTypeEUTRA .....................................................118
ReportConfigEUTRA::eventA3Offset .............................................................119
ReportConfigEUTRA::thresholdEutraRsrp....................................................120
ReportConfigEUTRA::thresholdEutraRsrq....................................................121
4.3.1.4
SPEED STATE MEASUREMENTS CONFIGURATION ...........................................123

SpeedStateEvalConf::tEvaluation ..................................................................124
SpeedStateEvalConf::nCellChangeHigh........................................................124
SpeedStateEvalConf::nCellChangeMedium ..................................................125
SpeedStateEvalConf::tHystNormal ................................................................125
TimeToTriggerConf::timeToTriggerSfHigh....................................................125
TimeToTriggerConf::timeToTriggerSfMedium ..............................................126
4.4
AUTOMATIC NEIGHBOUR RELATION (ANR) CONFIGURATION AND OPTIMISATION ............126
Page 3/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.4.1
ANR Overview ................................................................................................................126

ActivationService::anrEnable .........................................................................128
4.4.2
ANR neighbor relation creation function .........................................................................129
4.4.2.1
ANR in Active Phase - Discover Neighbor Relation through UE Reporting ..............129
4.4.2.1.1
Parameters Included in a NEIGHBOR RELATION.........................................................130
LteNeighboringCellRelation::discoveredByAnr............................................132
LteNeighboringCellRelation::noRemove .......................................................132
4.4.2.1.2
ANR MEASUREMENT CONFIGURATION .................................................................132

ReportConfigEUTRA::threshold2EutraRsrp..................................................136
ReportConfigEUTRA::threshold2EutraRsrq..................................................136
4.4.2.1.3
DRX Configuration for ECGI Retrieving .........................................................................137

AutomaticNeighborRelation::drxCycleForReportCGI ..................................137
AutomaticNeighbourRelation::isLcgRemovalAllowed .................................138
4.4.2.1.4
Set Up X2 links .................................................................................................................138

X2Access::macroEnbId...................................................................................140
X2Access::noRemove .....................................................................................140
X2Access::plmnMobileCountryCode .............................................................141
X2Access::plmnMobileNetworkCode.............................................................141
4.4.2.2
4.4.2.3
Receiving Neighbor Relation through X2 Messages .................................................142

End of Active Phase...................................................................................................143
AutomaticNeighbourRelation::activePhaseMeasReportHysteresis............143
AutomaticNeighborRelation::activePhaseMeasReportThreshold...............144
4.4.2.4
ANR in Dormant/Wake-up Phase ..............................................................................144
4.4.2.5
4.4.2.6
4.4.2.7
ANR Neighbor Relation Maintenance Function - Garbage Collection.......................146

ANR Synchronization Function ..................................................................................146
ANR Reset Function ..................................................................................................146
AutomaticNeighborRelation::dormantPhaseTimerForEcgiDiscovery ........145
5 EUTRAN TO UTRAN INTER-RAT MOBILITY FOR LTE (USE CASES & CONTROL
PROCEDURES) ...................................................................................................................................148
5.1
RRC IDLE MODE MOBILITY: ..............................................................................................148
5.1.1
CELL RESELECTION ACTIVATION..............................................................................148

ActivationService:: isCellReselectionToUtraTddAllowed ............................148
LteCell::utraTddNeighboringCellRelationIdList ............................................149
5.1.2
SYSTEMINFORMATIONBLOCKTYPE 6 AND SIB3 INTER-WORKING.......................149
5.1.3
CELL RESELECTION ALGORITHM DESCRIPTION ....................................................150
5.1.3.1
CELL SELECTION CRITERION................................................................................150
CellReselectionConfUtraTdd::qRxLevMin .....................................................152
CellReselectionConfUtraTdd::pMaxUTRA .....................................................153
CellSelectionReselectionConf::sNonIntraSearch .........................................154
CellSelectionReselectionConf::cellReselectionPriority ...............................155
5.1.3.1.1
5.1.3.2
MIM MODEL ...................................................................................................................156

CELL RESELECTION PRIORITIES HANDLING ......................................................157
5.1.3.3
UE SPEED MANAGMENT ........................................................................................159
UeTimers::t320 .................................................................................................158
UtraSpeedConf::tReselectionUtraSfHigh.......................................................160
UtraSpeedConf::tReselectionUtraSfMedium .................................................160
5.1.3.4
E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL RESELECTION CRITERIA161

CellSelectionReselectionConf::tReselectionUtra .........................................162
CellSelectionReselectionConf::threshServingLow.......................................163
CellReselectionConfUtraTdd::threshXHigh...................................................163
CellReselectionConfUtraTdd::threshXLow....................................................164
5.1.3.5
ALGORITHM FOR CELL RESELECTION PRIORITY ..............................................165
Page 4/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
FrequencyAndBandwidthTDD::priorityOfFreq..............................................167
UtraTddNeighboringFreqConf::bandUtraTdd128..........................................168
UtraTddNeighboringFreqConf::carrierFreq ...................................................169
5.2
5.1.3.6
LTE TO UTRA tDD reselection configuration ............................................................169
RRC CONNECTED MODE MOBILITY: ...............................................................................170
5.2.1
REDIRECTION ACTIVATION ........................................................................................171

ActivationService:: isRedirectionToUtraTddAllowed ...................................171
5.2.2
CONTROL PROCEDURES FOR RADIO MEASUREMENTS CONFIGURATION AND
MOBILITY TRIGGER MANAGEMENT ...........................................................................................172
5.2.2.1
MEASUREMENTS CONFIGURATION AT CALL SETUP ........................................172
5.2.2.2
RRC MEASUREMENTS CONFIGURATION: USAGE OF MIM MODEL..................174
5.2.2.3
CONTROL OF UE MOBILITY IN RRC CONNECTED STATE: REDIRECTION
EUTRA-TO-UTRA-TDD ................................................................................................................176
5.2.2.3.1
EXECUTION PHASE: .....................................................................................................177
5.2.2.3.2
COMPLETION PHASE: ..................................................................................................178
5.2.2.3.3
SYSTEM CALL FLOW: ..................................................................................................178
5.2.2.4
ALGORITHM FOR RRC MEASUREMENT CONFIGURATION................................179
5.2.2.5
5.2.2.5.1
MIM MODEL ...................................................................................................................180
5.2.2.6
LTE TO UTRAN MEASUREMENT REPORTING SETTING.....................................181
MeasObjectUTRA::offsetFreqUTRA ...............................................................181
5.2.2.7
NEIGHBOR CELL INFORMATION PROVIDED TO UES IN CONNECTED MODE.181

UtraTDDNeighboringCellRelation::physCellIdUTRATDD .............................182
UtraTDDNeighboringCellRelation::utraTDDNeighboringFreqConfId ..........183
5.2.2.8
AT CALL SETUP OR AN INCOMING MOBILITY .....................................................183
5.2.2.8.1
GOOD RADIO CONDITIONS:INTRA-FREQUENCY(A3);INTER-RAT(B2): ............183
5.2.2.8.2
BLIND REDIRECTION:RECEPTION OF EVENT A2_BLIND: ...................................186
5.2.2.9
STATE DIAGRAM OF RADIO CONDITIONS ...........................................................188
5.2.3
LTE TO UTRAN MEASUREMENTS CONFIGURATION ...............................................189
5.2.3.1
RRCMEASUREMENTCONF .....................................................................................190
RrcMeasurementConf::measQuantityUtraTdd ..............................................191
RrcMeasurementConf::filterCoefficientOfQuantityConfigUtra ....................191
5.2.3.2
REPORTCONFIGUTRAN:.........................................................................................191
ReportConfigUTRA::maxReportCells ............................................................192
ReportConfigUTRA::hysteresis ......................................................................193
ReportConfigUTRA::timeToTrigger................................................................194
ReportConfigUTRA::reportInterval.................................................................195
ReportConfigUTRA::reportAmount................................................................196
5.2.3.3
THRESHOLDS FOR INTER-RAT MOBILITY and MEASUREMENTS for EVENT B2196

ReportConfigUTRA::triggerTypeInterRAT.....................................................198
ReportConfigUTRA::threshold1EutraRsrp ....................................................199
ReportConfigUTRA::threshold1EutraRsrq ....................................................199
ReportConfigUTRA::threshold2UtraRscp......................................................200
5.3
EUTRAN-TO-UTRAN-TDD PS HANDOVER ........................................................................201

UtraTddNeighboringCellRelation::voiceOverIpEnabled...............................201
5.3.1
Blind PS Handover Activation and Measurement Configuration ....................................202

ActivationService::isBlindPsHoToUtraTddAllowed......................................202
RncAccess::psHandoverUtraEnabled ...........................................................203
5.3.2
Blind PS Handover Triggering and Target Cell Selection...............................................204

UtraTddNeighboringCellRelation::rncAccessId............................................204
UtraTddNeighboringFreqConf::priorityOfBandUtraTdd...............................205
5.3.3
Control of PS Handover ..................................................................................................205
Page 5/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RncAccess::plmnMobileCountryCode...........................................................207
RncAccess::plmnMobileNetworkCode ..........................................................208
RncAccess::rncId ............................................................................................208
RncAccess::extendedRncId............................................................................209
UtraTddNeighboringCellRelation::lac ............................................................209
UtraTddNeighboringCellRelation::rac............................................................210
RncAccess::directFwdPathAvailability..........................................................211
UtraTddNeighboringCellRelation::cId ............................................................212
PsHoToUtraTimersConf::tS1RelocPrepForPsHandoverToUtra...................212
PsHoToUtraTimersConf::tS1RelocOverallForPsHandoverToUtra ..............213
5.3.3.1
FAILURE CASES.......................................................................................................214
5.3.4
MIM Model for EUTRAN-to-UTRAN-TDD PS Handover ................................................215
RADIOBEARERCONF::dataForwardingForPsHoToUtraTddEnabled ..........216
RADIOBEARERCONF::psHoToUtraTddEnabled...........................................216
6 EUTRAN TO GERAN INTER-RAT MOBILITY FOR LTE (USE CASES & CONTROL
PROCEDURES) ...................................................................................................................................217
6.1
RRC IDLE MODE MOBILITY: ..............................................................................................217
6.1.1
CELL RESELECTION ACTIVATION..............................................................................218

ActivationService:: isCellReselectionToGeranAllowed ...............................218
6.1.2
CELL RESELECTION ALGORITHM DESCRIPTION ....................................................218
6.1.2.1
CELL SELECTION CRITERION................................................................................219
CellReselectionConfGERAN::qRxLevMin......................................................221
CellReselectionConfGERAN::pMaxGeran .....................................................222
CellSelectionReselectionConf::sNonIntraSearch .........................................223
CellSelectionReselectionConf::cellReselectionPriority ...............................224
CellReselectionConfGERAN::nccPermitted ..................................................224
6.1.2.2
6.1.2.3
CELL RESELECTION PRIORITIES HANDLING ......................................................224

UE SPEED MANAGEMENT ......................................................................................225
GeranSpeedConf::tReselectionGERANSfHigh..............................................226
GeranSpeedConf::tReselectionGERANSfMedium ........................................227
6.1.2.4
E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL RESELECTION CRITERIA227

GeranNeighboring::tReselectionGERAN .......................................................229
CellReselectionConfGERAN::threshXHigh....................................................230
CellReselectionConfGERAN::threshXLow ....................................................230
6.1.2.5
ALGORITHM FOR CELL RESELECTION PRIORITY ..............................................232

GeranNeighboringFreqsConf::priorityOfFreqs .............................................233
GeranNeighboringFreqsConf::BandIndicatorGERAN ..................................233
GeranNeighboringFreqsConf::GeranARFCNList ..........................................234
GeranNeighboringFreqsConf::bandGERAN..................................................234
6.2
6.1.2.6
LTE TO GERAN RESELECTION CONFIGURATION...............................................234
RRC CONNECTED MODE MOBILITY: ...............................................................................235
6.2.1
REDIRECTION ACTIVATION ........................................................................................238

ActivationService:: isRedirectionToGERANAllowed....................................239
6.2.2
CONTROL PROCEDURES FOR RADIO MEASUREMENTS CONFIGURATION AND
MOBILITY TRIGGER MANAGEMENT ...........................................................................................239
6.2.2.1
MEASUREMENTS CONFIGURATION AT CALL SETUP ........................................239
6.2.2.2
ALGORITHM FOR RRC MEASUREMENT CONFIGURATION................................241
6.2.2.3
6.2.3
LTE TO GERAN MEASUREMENT REPORTING SETTING .........................................242
6.2.3.1
LTE TO GERAN MeasurEMENT REPORTING SETING:.........................................242
MeasObjectGERAN::offsetFreqGERAN .........................................................244
MeasObjectGERAN::nccPermitted.................................................................244
6.2.4
LTE TO GERAN MEASUREMENTS CONFIGURATION...............................................244
6.2.4.1
RRCMEASUREMENTCONF .....................................................................................248
Page 6/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RrcMeasurementConf::measQuantityGERAN...............................................248
RrcMeasurementConf::filterCoefficientOfQuantityConfigGERAN ..............248
RrcMeasurementConf::transmissionGapRepetitionPeriod .........................249
6.2.4.2
REPORTCONFIGGERAN: ........................................................................................249
ReportConfigGERAN::maxReportCells .........................................................249
ReportConfigGERAN::triggerTypeInterRAT ..................................................250
ReportConfigGERAN::hysteresis ...................................................................251
ReportConfigGERAN::timeToTrigger.............................................................252
ReportConfigGERAN::reportInterval..............................................................253
ReportConfigGERAN::reportAmount.............................................................254
6.2.4.3
THRESHOLDS FOR INTER-RAT MOBILITY:...........................................................254

ReportConfigGERAN::threshold1EutraRsrp .................................................255
ReportConfigGERAN::threshold1EutraRsrq .................................................256
ReportConfigGERAN::B2ThresholdGERAN ..................................................256
ActivationService:: isGeranCcoAllowed........................................................257
ActivationService:: isDSIMallowed ................................................................257
BscAccess::rimForNaccEnabled....................................................................257
ANNEX:..........................................................................................................................................258
8.1
ABBREVIATIONS ................................................................................................................258
8.2
INTRA-FREQUENCY INTRA-ENB CALL FLOW: ................................................................262
8.3
INTRA-FREQUENCY INTER-ENB CALL FLOW .................................................................263
Page 7/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
TABLES
Table 1: Cell Reselection Criteria parameters
17
Table 2: Transmission bandwidth configuration NRB in E-UTRA channel bandwidths
20
Table 3: Cell Ranking Procedure parameters
21
Table 4: Measurements of EUTRAN TDD cells selection [3GPP 36133].
23
Table 5: Mobility information parameters
36
Table 6: Measurement information parameters
64
Table 7: Mobility activation and information parameters
89
Error! Bookmark not defined.
Table 9: MeasConfig information element
105
Table 10: ReportConfigEUTRA information element
112
151
Table 13: UE power Class vs. maximum output power, Pumax.
154
Table 14: Measurements of UTRAN TDD cells selection [3GPP 36133].
162
Table 16: ReportConfigInterRAT field descriptions
192
220
Table 19: Maximum TX power level
222
223
250
Page 8/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
FIGURES
Figure 1: The Definition of Channel Bandwidth and Transmission Bandwidth Configuration for
one E-UTRA carrier.................................................................................................................................... 20
Figure 2 : Cell Reselection criteria intra-LTE ................................................................................................. 24
Figure 3 : MIM Model SPEEDDEPENDENTBROADCASTCONF .............................................................. 33
Figure 4 : Intra-LTE reselection configuration................................................................................................ 34
Figure 5 : Mobility activation ............................................................................................................................. 36
Figure 6 : Call flow for Intra-eNB mobility - UE in RRC CONNECTED ...................................................... 38
Figure 7: Call flow for Inter-eNB mobility, X2 HO - UE in RRC CONNECTED ......................................... 44
Figure 8: Call flow for Inter-eNB mobility, S1 HO - UE in RRC CONNECTED ......................................... 53
Figure 9: Measurement setup at call setup .................................................................................................... 65
Figure 10: Measurement update upon handover inter-eNB handover.................................................... 67
Figure 11: Measurement update upon handover intra-eNB handover.................................................... 68
Figure 12 : Parameters in relationship with Event A3: Entering condition ................................................. 72
Figure 13 : EventA3 measurments configuration .......................................................................................... 72
Figure 14: LTE cell/eNB neighborhood MIM model TLA2.1 ........................................................................ 84
Figure 15 : MME pools Handover type decision......................................................................................... 86
Figure 16: Inter-frequency measurement configuration 1 ........................................................................... 99
Figure 17 : Inter-frequency measurement configuration 2 ......................................................................... 100
Figure 18 : Measurement configuration MIM model in TLA2.1 ................................................................. 101
Figure 19 : Hysteresis used to tuning HO decision, reportAmount = 4 .................................................... 115
Figure 20 : Redirection towards another RAT or carrier ............................................................................ 122
Figure 21 : Blind and intraFreq Measurements for redirection towards another RAT or carrier ......... 123
Figure 22 : ANR Phases.................................................................................................................................. 128
Figure 23 : Intra-Frequency Neighbor Cell Search ..................................................................................... 129
Figure 24 : S1 Procedure for Neighbor eNB X2 IP Address Retrieval ..................................................... 139
Figure 25 : Snonintrasearch drive cell detection frequency and lower priority cell detection. ............. 155
Figure 26 : MIM Model UTRATDDNEIGHBORING .................................................................................... 157
Figure 27 : Reselection configuration towards UTRAN cell....................................................................... 170
Figure 28 : Measurement setup at call setup ............................................................................................... 173
Figure 29 : RRC Measurements Configuration inter-RAT mobility ........................................................... 176
Figure 30 : Call flow Redirection EUTRA-TO-UTRA-TDD ......................................................................... 179
Figure 32 : Inter RAT threshold for Event B2 ............................................................................................... 184
Figure 33 : Call Flow for mobility INTRA-FREQUENCY (A3;A2_BLIND);INTER-RAT(B2) .................. 185
Figure 34 : waits for an intra-frequency measurement report or an inter-RAT measurement report... 186
Figure 35 : Inter RAT threshold for Event A2_blind .................................................................................... 187
Figure 36 : State diagram of radio conditions TLA2.1 ................................................................................ 189
Figure 37 : UTRA Event B2 Configuration.................................................................................................... 190
Figure 38 : Hysteresis used to tuning HO decision, reportAmount = 4 .................................................... 195
Figure 39 : Event B2 : Entering conditions ................................................................................................... 198
Figure 40: Call Flow for EUTRAN-to-UTRAN-TDD PS Handover ........................................................... 206
Figure 41: MIM Model for EUTRAN-to-UTRAN-TDD PS Handover........................................................ 215
Figure 42 : Reselection from eUTRAN to GERAN ...................................................................................... 217
Figure 43 : User Case, with UE Class3 and in the same PLMN, showing reselection towards lower
priority GERAN cell. ................................................................................................................................. 231
Figure 44 : LTE to GERAN reselection MIM configuration. ....................................................................... 235
Figure 45 : Redirection from eUTRAN to GERAN....................................................................................... 236
Figure 46 : Measurement setup at call setup ............................................................................................... 241
Figure 47 : Data model for MeasObjectGERAN .......................................................................................... 243
Figure 48: Hysteresis used to tuning HO decision, reportAmount = 4................................................... 253
Page 9/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1 INTRODUCTION
1.1 OBJECT
The objective of this document is to describe from an engineering point of view the
Mobility algorithms and parameters applicable to LTE system.
This includes a system
recommendations.
description,
configuration
aspect
and
engineering
1.2 SCOPE OF THIS VOLUME

This document provides configuration information for LTE eNodeB products in LTE
Release TLA2.1 (drops TLA2.1.1, TLA2.1.2, and TLA2.1.3) for the Time Division
Duplex (TDD) implementation. Information that is added in this edition to support the
TLA2.1 drops is colored with a gray background as illustrated by this paragraph.
References to LA0.x, LA1.0, and TLA2.0 in this volume refer to features that became
available in those releases.
For an LTE release earlier than TLA2.1, please refer to the LPUG Edition that
supports that release.
Engineering Recommendation: Parameter Values

Parameter values provided in this version of the LPUG document reflect the best
information available at the time of publication.
If a newer SW delivery is used, then the related Release Notes should be consulted for
newer parameter values.
Restriction: Frequency Division Duplex (FDD) System

Support for the Frequency Division Duplex (FDD) implementation will be provided in a
separate document.
Restriction: eNodeB equipments type covered

The Femto & Pico eNodeB product are out of scope of this document, thus all
engineering information, algorithms description and parameters values provided in this
document are strictly related to standard Alcatel-Lucent eNodeB products.
Page 10/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1.3 LIST OF RELATED FEATURES
The system aspects described in this volume are related to the following features:
LA0.x
Feature
Number
Feature Title
FRS 34348
Commercial LTE Introduction Call Processing,

RRM, MM
FRS 75908
Seamless Intra-LTE Mobility
Release
LA0.1
LA0.2
LA1.0
Feature
Number
Feature Title
Release
FRS 76501
3GPP Alignment
LA1.0
FRS 76500
Lossless Intra-LTE Handover
LA1.0
TLA2.0
Feature
Number
FRS 82729
Feature Title
S1 Flex Introduction
Release
TLA2.0
TLA2.1
Feature
Number
Feature Title
Release
FRS 97933
Dynamic SysInfo Modification under Cell

Parameter Change
TLA2.1
FRS 98841
Inter-eNB S1 HO with MME&SGW Relocation for

Inter-vendor Mobility
TLA2.1
FRS 97979
Support of Partial Handover Failure
TLA2.1
FRS 97941
Support of new mobility procedure interactions
TLA2.1
FRS 97940
Handover Cancel Support
TLA2.1
FRS 84807
eUTRAN to GERAN Inter-RAT Mobility Cell

Reselection and redirection LA2.0
TLA2.1
FRS 105474
Inter-RAT handover from LTE to TD-SCDMA
TLA2.1
FRS 103791
Inter-frequency Cell reselelction for multi-band

support
TLA2.1
FRS 96760
eNB Configuration Update Enhancements
TLA2.1
Page 11/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
FRS 81872
Automatic Neighbour Relation Configuration and

Optimisation
TLA2.1
Whenever possible and/or necessary, a reference is given to the feature in question

(parameter tables) or to (one of) its requirements.
2 RELATED DOCUMENTS AND

PREREQUISITES
2.1 LPUG VOLUMES
[Vol. 1] Introduction
[Vol. 2] LTE Overview
[Vol. 3] LTE Air Interface
[Vol. 4] Radio Resource Management
[Vol. 5] Call Management
[Vol. 6] Mobility
[Vol. 7] Transport
[Vol. 8] Hardware
[Vol. 9] OAM
2.2 REFERENCE DOCUMENTS

[R01] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical channels and modulation".( 2009-06 )
Multiplexing and channel coding".( 2009-06 )
Physical layer procedures".( 2009-06 )
[R04] 3GPP TS 36.401: Evolved Universal Terrestrial Radio Access Network (EUTRAN; Architecture description R8 .( 2009-06 )
[R05] 3GPP TS 36.300: " Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Overall
description Stage 2".( 2009-06 )
Page 12/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
[R06] 3GPP TS 23.003: "Numbering, addressing and identification".( 2009-06 )
[R07] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".(2009-06)
[R08] 3GPP TS 36.331: Evolved Universal Terrestrial Radio Access Network (EUTRAN; Radio Resource Control (RRC) ( 2009-06 )
[R09] 3GPP TS 36.321: Evolved Universal Terrestrial Radio Access Network (EUTRAN; Redium Access Control (MAC) R8 .( 2009-06 )
[R10] 3GPP TS 36.322: Evolved Universal Terrestrial Radio Access Network (EUTRAN; Radio Link Control (RLC) R8 .( 2009-06 )
[R11] 3GPP TS 22.011: Service accessibility .( 2009-06 )
[R12] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA);
User Equipment (UE) radio transmission and reception. ( 2009-06 )
[R13] 3GPP TS 36.413: Evolved Universal Terrestrial Radio Access (E-UTRA);
S1 Application Protocol (S1AP) ( 2009-06 v8.6.1)
[R14] 3GPP TS 36.304 Evolved Universal Terrestrial Radio Access (E-UTRA);
User Equipment (UE) procedures in idle mode ( 2009-06 )
[R15] 3GPP TS 23.122 "NAS functions related to Mobile Station (MS) in idle mode".
( 2009-06 )
[R16] 3GPP2 C.S0005-A: "Upper Layer (Layer 3) Signalling Standard for cdma2000
Spread Spectrum Systems".( 2009-06 )
http://www.3gpp.org/ftp/Specs/html-info/36304.htm
2.3 PREREQUISITES FOR READING THIS VOLUME

Before reading this volume, the reader should read the introduction (Volume 1).
Volume 1 provides an explanation of the presentation and conventions that are used
throughout the document (i.e., common to all volumes).
3 OVERVIEW
This volume depicts the LTE Parameters regarding Mobility features. The granularity
of all Mobility parameters is Cell by Cell.
This document is built in the same chronological order of the events attributed to the
work of the mobile and the network, like if you begin to attach the mobile to the
network and after you moved with this one.
Page 13/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
In first step, you moved in idle mode and reselection process is used by your mobile.
In second step, you are on call, and Handover process is practiced by your mobile.
These two steps are reported for each type of mobility features.
It specifies:
intra-LTE mobility features, covering the control plane aspects. The

management of intra-LTE and inter-LTE measurements configuration is also
specified in this document.
Inter-RAT mobility features, covering control plane aspects, regarding the two
following mobilities:
o
eUTRAN to UTRAN Inter-RAT Mobility Cell Reselection and

redirection
eUTRAN to GERAN Inter-RAT Mobility Cell Reselection and

redirection (TLA2.1.3)
4 INTRA-RAT MOBILITY FOR LTE

4.1 INTRA-FREQUENCY MOBILITY FOR LTE
4.1.1 RRC IDLE MODE MOBILITY
Cell Reselection is a procedure lunched by the UE in Idle Mode to determine which
LTE cell to camp on. The trigger can be internal (e.g. periodic trigger to ensure that
UE is still on the best cell) or external (e.g. upon change of Cell Reselection
parameters broadcast on the selected cells BCH). The cell selection and reselection
is controlled by the System Information parameters provided in SIB1 and SIB3. Cell
Reselection is a procedure triggered by UEs in Idle Mode to determine which LTE
cell to camp on. When a UE, camps on a cell it monitors its broadcast and paging
channels. The procedure is internal to the UE and there is therefore no E-UTRA level
use case for it.
Access Class Barring are introduced in TLA2.0 (to see [Vol. 5] and [R14] for more
details.), minor changes regarding this part for TLA2.1.
The cell selection and reselection is controlled by the System Information parameters
provided in SIB1 and SIB3, 3GPP [R08].
Before cell reselection algorithm description, we depict inter tracking area mobility.
Page 14/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.1.1.1 INTER TRACKING AREA MOBILITY:
When the UE is in RRC-Idle state, its position is known by the network on a per
Tracking Area (TA) basis. In case of network originated transition from RRC-idle to
RRC-connected, the network will page the UE across the whole Tracking
AreaTracking area mobility is supported by the System Information broadcast of TAI.
The TA Code information is broadcast on the BCCH channel on SIB-1.
When the UE enters a new cell which belongs to a TAI where it is not registered it will
initiate the TAU procedure.
Rule: Regarding TLA2.1
In TLA2.1, the TA identity is provisioned by OAM on a per cell basis, like in TLA2.0
The corresponding MIM parameters are described below.
trackingAreaCode: 3GPP 36.331 This parameters identifies the TAC (Tracking

Area Code) to which the cell belongs. A trackingAreaCode that is common for all
the PLMNs listed.
LteCell::trackingAreaCode
Parameter
trackingAreaCode
Object
Enb/ LteCell
Range & Unit
BitString
stringMinLength = 16
string Length = 16
Class/Category
A / Fixed
Value
O.D. See Engineering Recommendation
Feature
FRS 96760, 97933
Engineering Recommendation: trackingAreaCode

We recommend that the operator always puts the cells of a given eNB in the
same tracking area.
Page 15/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
trackingAreaCode : 3GPP 36.331 This parameter identifies the Tracking Area

Code to which belongs the cell.
LteNeighboringCellRelation::trackingAreaCode
Parameter
trackingAreaCode
Object
Enb/ LteCell/ LteNeighboringCellRelation
Range & Unit
BitString
Maxlength = 16
Class/Category
C / Fixed
Value
O.D (set by ANR function or by operator)
Feature
81872
4.1.1.2 PLMN SELECTION & CELL RESERVATION AND CELL

RESTRICTION:
Note: PLMN Selection Procedure in depict in [Vol. 5] section 7 (Call Handling). The
mechanism of cell reservation and cell restriction will play on the intra LTE mobility
procedures for Idle mobiles. This procedure is depicted in [Vol. 5] Section 7 Call
Handling.
4.1.1.3 CELL RESELECTION ALGORITHM DESCRIPTION

Cell Reselection is a procedure run in the UE that relies on:
- Measured RF quality related metrics of camped on and detected cells
- System parameters broadcast by the cell on which the UE is currently camping on.
4.1.1.3.1 CELL SELECTION CRITERION

The cell selection S criterion (Calculated by the UE) is fulfilled when:
Srxlev > 0
Where:
Srxlev = Qrxlevmeas (Qrxlevmin + Qrxlevminoffset) - Pcompensation

Where:
The signalled value QrxlevminOffset is only applied when a cell is evaluated for cell
selection as a result of a periodic search for a higher priority PLMN while camped
normally in a VPLMN [R14]. During this periodic search for higher priority PLMN the
UE may check the S criteria of a cell using parameter values stored from a different
cell of this higher priority PLMN.
Page 16/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Srxlev
Calclated by
the UE
Measured
by the UE
Cell Selection RX level value (dB).
Minimum required RX level in the cell (dBm).
fset
qRxLevMin
or
qRxLevMinIn
traFreqNeigh
bour
qRxlevminoff
set
Pcompen
sation
Pemax
Calculated
by the UE
Hardcoded
Qrxlevmeas
Qrxlevmin
Qrxlevminof
Pumax
Hardcoded
Measured cell RX level value. This is received signal, PCCPCH RSCP for TDD cells (dBm).
Offset to the signalled Qrxlevmin taken into account in the

Srxlev evaluation as a result of a periodic search for a
higher priority PLMN while camped normally in a
VPLMN [5] (SIB1)
max(Pemax Pumax, 0) (dB).
Maximum TX power level an UE may use when
transmitting on the uplink in the cell (dBm) defined as PEMAX
in [TS 36.101] and the value is provided by IE p-Max if a value
is signalled to a UE (see TS 36.331). Note that signalling the
value of p-Max to a UE is not supported in TLA2.1. But this is
scheduled for future release.
Maximum RF output power of the UE (dBm) according to
the UE power class as defined in [TS 36.101] and fixed to
23dBm for UE class 3 (for all the EUTRA band)
T
a
Restriction: Regarding TLA2.1 and Pemax
b
l Note: Information Element p-Max is not yet broadcasted for intra-LTE mobility, the
eUE ignores Pemax, and Pcompensation value is 0.
1: Cell Reselection Criteria parameters
In order to further restrict the amount of measurement carried out by the UE in RRCIdle mode, the following rules are used by the UE:
Sintrasearch : This specifies the threshold (in dB) for intra frequency measurements.
MIM parameter is sIntrasearch
If SServingCell > Sintrasearch, UE may choose to not perform intra-frequency

measurements. (SServingCell is a S Criterion in the Serving cell, i.e SServingCell = SRxLev like
formula above)
If SServingCell Sintrasearch, or CellSelectionReselectionConf::sIntrasearch is not sent
in the serving cell, UE shall perform intra-frequency measurements.
Where:
SservingCell = Qrxlevmeas (Qrxlevmin + Qrxlevminoffset) - Pcompensation
qRxLevMin : 3GPP 36.331[R08] This parameter configures the serving cell min
required RSRP level used by the UE in cell reselection. The value sent over
Page 17/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
the RRC interface is half the value configured. Broadcast by the eNB in
SystemInformationBlockType1
CellSelectionReselectionConf::qRxLevMin
Parameter
qRxLevMin
Object
Enb/ LteCell/ CellSelectionReselectionConf
Range & Unit
dBm
[-140..-44] step = 2
Class/Category
C / Optimization - Tuning
Value
-110 see Engineering Recommendation
Feature
96760
Parameter qRxLevMin in [R14]. Actual value Qrxlevmin = IE value*2

[dBm].
Specifies the minimum required Rx RSRP level in the cell. (Where IE value specify the
message value send to the UE)
Changing this value will affect cell size in terms of re-selection area. Increasing this
value will lead the mobile to start cell-selection/re-selection procedure sooner
and then will artificially decrease cell size in idle mode.
Engineering Recommendation: qRxLevMin
The field tests trial have shown best results with the value : -110 dBm
This parameter has impact on idle mode coverage
qRxlevminoffset: This parameter defines an offset to be applied in cell selection

criteria by the UE when it is engaged in a periodic search for a higher priority
PLMN. The value sent over the RRC interface is half the value configured
Defined
in
TS
36.331.
Broadcast
by
the
eNB
in
SystemInformationBlockType1[R14]
CellSelectionReselectionConf::qRxlevminoffset
Parameter
qRxlevminoffset
Object
Range & Unit
dB
[2..16] step = 2
Class/Category
Value
2 (default:2)
Feature
96760
Note: If you do not use inter-PLMN mobility, this parameter is inhibited.

Page 18/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
sIntraSearch : 3GPP 36.331 Threshold for serving cell reception level under
which the UE triggers intra-frequency measurements for cell reselection (the
actual value the UE will use is twice the configured value). The value sent over
the RRC interface is half the value configured. For more details consult TS36.304.
Broadcast in SystemInformationBlockType3
CellSelectionReselectionConf::sIntraSearch
Parameter
sIntraSearch
Object
Range & Unit
dB
[0..62] step = 2
Class/Category
Value
2 See Engineering Recommendation
Feature
96760
Engineering Recommendation: sIntraSearch

UE starts intra-frequency measurements for cell re-selection when serving cells
RSRP value <= qRxLevMin + sIntraSearch. Increasing sIntraSearch value will
make UE to start intra-frequency neighbor search earlier. Test results indicate
sIntraSearch should be set to the highest allowed value to minimize SINR
degradation in reselection boundaries.
measurementBandwidth: Expressed in number of resource blocks. Also referred

to as Transmission Bandwidth Configuration NRB in TS 36.101(UE) &
36.104(BTS). Defined in TS 36.331. Broadcast in SystemInformationBlockType3
CellSelectionReselectionConf::measurementBandwidth
Parameter
measurementBandwidth
Object
Range & Unit
Enumerate
[mbw6, mbw15, mbw25, mbw50, mbw75, mbw100]
Class/Category
C / Fixed
Value
MbW100
Feature
96760, 97933
Note: Default value for 20 MHz bandwidth is mbw100. MeasurementBandwidth should

not exceed Channel Bandwidth.
Page 19/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Measurement bandwidth information common for all neighbouring cells on the serving
frequency. If absent, the value corresponding to the downlink bandwidth indicated by
the dl-Bandwidth included in MasterInformationBlock applies.
If bandwidth is larger within target cell than within current cell, then its needed
to inform UE.
The IE MeasurementBandwidth used to indicate measurement bandwidth defined by
the parameter Transmission Bandwidth Configuration "NRB" [TS 36.104]. The values
mbw6, mbw15, mbw25, mbw50, mbw75, mbw100 indicate 6, 15, 25, 50, 75 and 100
resource blocks respectively. [R08]
Channel bandwidth
BWChannel [MHz]
1.4
10
15
20
Transmission bandwidth
configuration NRB
15
25
50
75
100
Table 2: Transmission bandwidth configuration NRB in E-UTRA channel

bandwidths
Figure below shows the relation between the Channel bandwidth (BW Channel) and the
Transmission bandwidth configuration (NRB). The channel edges are defined as
the lowest and highest frequencies of the carrier separated by the channel bandwidth,
i.e. at FC +/- BW Channel /2. For more information regarding the frame structure, you can
refer to [Vol. 3] section 6.
Channel Bandwidth [MHz]

Transmission Bandwidth Configuration [RB]
Active Resource Blocks
Channel edge
Resource block
Channel edge
Transmission
Bandwidth [RB]
Center subcarrier (corresponds to DC in

baseband) is not transmitted in downlink
Figure 1: The Definition of Channel Bandwidth and Transmission Bandwidth

Configuration for one E-UTRA carrier
Note: As a general rule, the resolution bandwidth of the measuring equipment
should be equal to the measurement bandwidth. However, to improve measurement
accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the
Page 20/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measurement bandwidth. When the resolution bandwidth is smaller than the
measurement bandwidth, the result should be integrated over the measurement
bandwidth in order to obtain the equivalent noise bandwidth of the measurement
bandwidth.[R12] [TS 36.101]
4.1.1.3.2 INTRA-FREQUENCY AND EQUAL PRIORITY INTERFREQUENCY CELL RESELECTION CRITERIA

The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined
by [R14]:
Rs = Qmeas,s + QHyst
Rn = Qmeas,n - Qoffset
where:
RSRP measurement quantity used in cell reselections.
Qmeas
The quality value of the received signal derived from the averaged
P-CCPCH RSCP for TDD cells
Qoffset
qOffsetCell
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is

valid, otherwise this equals to zero.
For inter-frequency: Equals to Qoffsets,n plus
Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to
Qoffsetfrequency. NOT YET IMPLEMENTED
QHyst
qHyst
This parameter configures the hysteresis value of the serving cell

used by the UE for ranking criteria in cell reselection.
Table 3: Cell Ranking Procedure parameters

The UE will perform ranking of all cells that fulfil the cell selection S criterion, which is
defined in section 4.1.1.3.1.1,
The cells are be ranked according to the R criteria specified above, deriving Qmeas,n
and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE will perform cell re-selection to that cell.
In all cases, the UE will actually reselect the new cell, only if the following conditions
are met:
-
The new cell is better ranked than the serving cell during a time interval
tReselectionEUTRANs or tReselectionRATs
Qmeas,s + QHyst < Qmeas,n QOffset
Page 21/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
-
If the UE is in high mobility state multiply TreselectionEUTRAN or

tReselectionRATs (and Qhyst FFS) by the IE "Speed dependent ScalingFactor
for TreselectionEUTRANs or tReselectionRATs " if sent on system information
and UE. (to see section 5.1.3.3)
More than 1 second(s) has elapsed since the UE camped on the current serving
cell.
qHyst : 3GPP 36.331[R08] This parameter configures the hysteresis value of

the serving cell used by the UE for ranking criteria in cell reselection.
Broadcast in SystemInformationBlockType3
CellSelectionReselectionConf::qHyst
Parameter
qHyst
Object
Range & Unit
Enumerate in dB
[dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14,
dB16, dB18, dB20, dB22, dB24]
Class/Category
C / Optimization - Selection
Value
dB4 (Default:dB4)
Feature
96760,97933
This parameter is an environment dependent parameter. This parameter configures

the hysteresis value of the serving cell used by the UE for ranking criteria in cell
reselection.
Current value is 4dB. According to this value, the cell-reselection should be made with
a neighboring cell at RSRP > -86dBm (case with qRxLevMin (see by the UE) =-100
dBm, sIntraSearch=10, intra-frequency mobility )
Decreasing qHyst leads to do cell-reselection earlier
Note: Value Q-hyst = IE; If qHyst =4 in DLU, in sysinfo UE see the value 4. 3GPP
compliant.
Engineering Recommendation: qHyst

We can adjust qHyst according to the RSRP values seen on the field and this needs to be
cell by cell basis. But the recommended value is dB4.
Page 22/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionEUTRAN : 3GPP 36.331 This parameter specifies the value of the

cell reselection UE timer in the serving cell. Broadcast in
CellSelectionReselectionConf::tReselectionEUTRAN
Parameter
tReselectionEUTRAN
Object
Range & Unit
s
[0..7] step = 1
Class/Category
Value
Feature
96760,97933
This parameter avoids ping pong radio phenomena during the RA-Update & idle
mobility.
Increasing this value will lead the mobile to start cell-reselection later.
Warning: For an intra-frequency cell that has been already detected, but that has not
been reselected to, the filtering will be such that the UE will be capable of evaluating
that the intra-frequency cell has met reselection criterion defined in this section within
Tevaluate,E-UTRAN_intra = 5,12 sec when tReselectionEUTRAN = 0 as specified in
table below (with Enb::defaultPagingCycle=rf32 [Vol. 5]), provided that the cell is at
least 3dB better ranked. [TS 36.133]
DRX
cycle
length
[s]
Tdetect,EUTRAN_Intra [s]
(number of DRX
cycles)
0.32
0.64
1.28
2.56
[11.52 (36)]
[17.92 (28)]
[32(25)]
[58.88 (23)]
Tmeasure,EUTRAN_Intra [s]
(number
of
DRX
cycles)
Tevaluate,E-UTRAN_intra
[s] (number of DRX
cycles)
[1.28 (4)]
[1.28 (2)]
[1.28 (1)]
[2.56 (1)]
[5.12 (16)]
[5.12 (8)]
[6.4 (5)]
[7.68 (3)]
Table 4: Measurements of EUTRAN TDD cells selection [3GPP 36133].
Page 23/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Qoff
Serving
QHyst
RSRP
Cell
Serving Cell
Timer is started
Cell2 becomes better than
the serving cell
sIntraSearch
tReselectionEUTRAN
Cell 1
Cell 2
UE triggers intra-frequency
measurements
Timer is aborted
Cell2 is reselected
Figure 2 : Cell Reselection criteria intra-LTE
qOffsetCell : This parameter defines the offset between the current LteCell and
the LteNeighbouringCell. This parameter shall be present and configured if the
neighbour cell is included in the neighbour cell list to be provided in the System
Information.
In
dB.
Defined
in
TS
36.331.
Broadcast
in
SystemInformationBlockType4. Not implemented in TLA2.1
LteNeighboringCellRelation::qOffsetCell
Parameter
qOffsetCell
Object
Range & Unit
Enumerate in dB
[dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8,
dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4,
dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22,
dB24]
Class/Category
Value
dB3
Feature
96760,81872,97933
Page 24/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: Regarding TLA2.1 and LteNeighboringCellRelation::qOffsetCell
Not qimplemented in TLA2.1, and the algorithm ignores this parameter.
R
qRxLevMinIntraFreqNeighbour: This parameter specifies the mininum required

RSRP level used by the UE for the intra-frequency neighbouring E-UTRA cells.
The value sent over the RRC interface is half the value configured (the UE then
multiplies the received value by 2) Defined in TS36.331 and TS36.304. Broadcast
in SystemInformationBlockType3
CellSelectionReselectionConf::qRxLevMinIntraFreqNeighbour
Parameter
qRxLevMinIntraFreqNeighbour
Object
Range & Unit
Integer in dBm
[-140..-44] step = 2
Class/Category
Value
-110
Feature
96760
Note: The qRxLevMin to send by the SIB3 (in TLA2.1, it is the parameter
qRxLevMinIntraFreqNeighbour) applies to the signal of the same neighbors frequency
than the serving cell.
Engineering Recommendation: qRxLevMinIntraFreqNeighbour

The field tests trial have shown best results with the value : -110 dBm
Follow the CellSelectionReselectionConf::qRxLevMin value at this moment.
4.1.1.3.3 UE SPEED MANAGEMENT

Parameters in relationship with mobility speed states of a UE, in case of intra-LTE
mobility, are the same as in case of inter-RAT mobility, except parameters in the MO
object UtraSpeedConf and tReselectionUtra, which are specific. Please report to
section 5.1.3.3 or 6.1.2.3 for those parameters in case of inter-RAT mobility.
Besides Normal-mobility state a High-mobility and a Medium-mobility state are
applicable if the parameters (tEvaluation (TCRmax), nCellChangeHigh (NCR_H),
nCellChangeMedium (NCR_M) and tHystNormal (TCRmaxHyst)) are sent in the
system information broadcast SIB3 of the serving cell.
State detection criteria:
Medium-mobility state criteria:
-
If number of cell reselections during time period tEvaluation exceeds

nCellChangeMedium and not exceeds nCellChangeHigh
Page 25/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
High-mobility state criteria:
If number of cell reselections during time period tEvaluation exceeds
nCellChangeHigh
The UE shall not count consecutive reselections between same two cells into mobility
state detection criteria if same cell is reselected just after one other reselection.
State transitions:
The UE shall:
-
if the criteria for High-mobility state is detected:

-
enter High-mobility state.
else if the criteria for Medium-mobility state is detected:

-
enter Medium-mobility state.
else if criteria for either Medium- or High-mobility state is not detected during
time period tHystNormal:
-
enter Normal-mobility state.
If the UE is in High- or Medium-mobility state, the UE shall apply the speed

dependent scaling rules as defined in subclause [R14] section 5.2.4.3.1.
tEvaluation: TS36.331: this parameter contributes to the configuration of the

SystemInformationBlockType3. This parameter configures the IE t-Evaluation
included in the IE MobilityStateParameters. The duration for evaluating criteria to
enter mobility states. Corresponds to TCRmax in TS 36.304. Value in seconds,
s30 corresponds to 30 s and so on.
SpeedStateEvalBroadcastConf::tEvaluation
Parameter
tEvaluation
Object
Enb/ LteCell/ SpeedDependentBroadcastConf/

SpeedStateEvalBroadcastConf
Range & Unit
Enumerate in s
[s30, s60, s120, s180, s240]
Class/Category
C / Fixed
Value
N.A.
Feature
76498
Keys for Hierarchy: ENBEquipment Enb LteCell SpeedDependentBroadcastConf

Page 26/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
nCellChangeHigh: TS36.331: this parameter contributes to the configuration of

the SystemInformationBlockType3. This parameter configures the IE nCellChangeHigh included in the IE MobilityStateParameters. The number of cell
changes to enter high mobility state. Corresponds to NCR_H in TS 36.304.
SpeedStateEvalBroadcastConf::nCellChangeHigh
Parameter
nCellChangeHigh
Object

Range & Unit
Integer
[1..16] step = 1
Class/Category
Value
N.A
Feature
76498
Page 27/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
nCellChangeMedium: TS36.331: this parameter contributes to the configuration

of the SystemInformationBlockType3. This parameter configures the IE nCellChangeMedium included in the IE MobilityStateParameters. The number of
cell changes to enter medium mobility state. Corresponds to NCR_M in TS
36.304.
SpeedStateEvalBroadcastConf::nCellChangeMedium
Parameter
nCellChangeMedium
Object

Range & Unit
Integer
[1..16] step = 1
Class/Category
C / Optimization Tuning
Value
N.A
Feature
76498
tHystNormal: TS36.331: this parameter contributes to the configuration of the

SystemInformationBlockType3. This parameter configures the IE t-HystNormal
included in the IE MobilityStateParameters. The additional duration for evaluating
criteria to enter normal mobility state. Corresponds to TCRmaxHyst in TS 36.304.
Value in seconds, s30 corresponds to 30 s and so on.
SpeedStateEvalBroadcastConf::tHystNormal
Parameter
tHystNormal
Object

Range & Unit
Enumerate in s
[s30, s60, s120, s180, s240]
Class/Category
C / Fixed
Value
N.A
Feature
76498
Scaling rules:
The cell ranking procedure is the same as in 4.1.1.3.2 but with variable values for
parameters qHyst and tReselection. UE shall apply the following scaling rules:
-
If neither Medium- nor Highmobility state is detected:

-
no scaling is applied.
If High-mobility state is detected:

- Add the qHystSfHigh to Qhyst (to see section 4.1.1.3.2) for high mobility
state if sent on system information.
- For E-UTRAN cells multiply tReselectionEUTRAN (to see section 4.1.1.3.2)
by tReselectionEutraSfHigh if sent on system information.
- For UTRAN cells multiply tReselectionUtra by tReselectionUtraSfHigh if
sent on system information. (Please refer to section 5.1.3.3)
Page 28/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
-
If Medium-mobility state is detected:

- Add qHystSfMedium to Qhyst (to see section 4.1.1.3.2) for medium mobility
state, if sent on system information.
by tReselectionEutraSfMedium if sent on system information.
- For UTRAN cells multiply tReselectionUtra by tReselectionUtraSfMedium,
if sent on system information. (Please refer to section 5.1.3.3)
In case scaling is applied to any TreselectionRAT parameter the UE shall round up the
result after all scalings to the nearest second.
qHystSfHigh: TS36.331: this parameter contributes to the configuration of the IE

SystemInformationBlockType3.This parameter configures the IE sf-High
included in the IE SpeedStateReselectionPars. Parameter Speed dependent
ScalingFactor for Qhyst in TS 36.304. The sf-High concerns the additional
hysteresis to be applied, in High Mobility state, to Qhyst as defined in TS
36.304 and in 4.1.1.3.2. In dB. Value dB-6 corresponds to -6dB, dB-4
corresponds to -4dB and so on.
SpeedStateEvalBroadcastConf::qHystSfHigh
Parameter
qHystSfHigh
Object

Range & Unit
Enumerate in dB
[dB-6, dB-4, dB-2, dB0]
Class/Category
C / Optimization Selection
Value
N.A
Feature
76498

reselection.
Exemple with the Value 4dB: With this value, the cell-reselection should be made with
dBm, sIntraSearch=10, intra-frequency mobility )
Decreasing qHystSfHigh leads to do cell-reselection earlier
Page 29/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionEutraSfHigh : TS36.331: this parameter contributes to the

configuration of the IE SystemInformationBlockType3. This parameter configures
the t-ReselectionEUTRA-SF included in the IE SystemInformationBlockType3
and timeToTrigger-SF in IE MeasConfig. Parameter Speed dependent
ScalingFactor for TReselectionEUTRA in TS 36.304. If the field is not present,
the UE behaviour is specified in TS 36.304. The concerned mobility control
related parameter is multiplied with this factor if the UE is in High Mobility
state as defined in TS 36.304. Value oDot25 corresponds to 0.25, oDot5
corresponds to 0.5 , oDot75 corresponds to 0.75 and so on.
LteSpeedConf::tReselectionEutraSfHigh
Parameter
tReselectionEutraSfHigh
Object
Enb/ LteCell/ SpeedDependentBroadcastConf/ LteSpeedConf
Range & Unit
Enumerate
[oDot25, oDot5, oDot75, lDot0]
Class/Category
C / Optimization Tuning
Value
N.A
Feature
76498
This parameter avoid ping pong radio phenomena during the RA-Update & idle
mobility.
Page 30/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
qHystSfMedium: TS36.331: this parameter contributes to the configuration of

the IE SystemInformationBlockType3.This parameter configures the IE sfMedium included in the IE SpeedStateReselectionPars. Parameter Speed
dependent ScalingFactor for Qhyst in TS 36.304. The sf-Medium concerns the
additional hysteresis to be applied, in Medium Mobility state, to Qhyst as
defined in TS 36.304 and in 4.1.1.3.2. In dB. Value dB-6 corresponds to -6dB,
dB-4 corresponds to -4dB and so on.
SpeedStateEvalBroadcastConf::qHystSfMedium
Parameter
qHystSfMedium
Object

Range & Unit
Enumerate in dB
[dB-6, dB-4, dB-2, dB0]
Class/Category
Value
N.A
Feature
76498

reselection.
Exemple with the Value 4dB: With this value, the cell-reselection should be made with
dBm, sIntraSearch=10, intra-frequency mobility)
Decreasing qHystSfMedium leads to do cell-reselection earlier
Page 31/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionEutraSfMedium : TS36.331: this parameter contributes to the

the t-ReselectionEUTRA-SF included in the IE SystemInformationBlockType3
and timeToTrigger-SF in IE MeasConfig. Parameter Speed dependent
ScalingFactor for TReselectionEUTRA in TS 36.304. If the field is not present,
the UE behaviour is specified in TS 36.304. The concerned mobility control
related parameter is multiplied with this factor if the UE is in Medium Mobility
state as defined in TS 36.304. Value oDot25 corresponds to 0.25, oDot5
corresponds to 0.5 , oDot75 corresponds to 0.75 and so on.
LteSpeedConf::tReselectionEutraSfMedium
Parameter
tReselectionEutraSfMedium
Object
Enb/ LteCell/ SpeedDependentBroadcastConf/ LteSpeedConf
Range & Unit
Enumerate
Class/Category
Value
N.A
Feature
76498
This parameter avoids ping pong radio phenomena during the RA-Update & idle
mobility.
4.1.1.3.3.1
MIM MODEL
Page 32/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 3 : MIM Model SPEEDDEPENDENTBROADCASTCONF
Page 33/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 4 : Intra-LTE reselection configuration
4.1.2 RRC CONNECTED MODE MOBILITY

RRC CONNECTED mode intra-frequency mobility is supported including intra and
inter-eNB mobility based on UE measurements reporting.
PDCP layer shall perform sequence number maintenance for each RB and SRB.
There are several purposes of PDCP SN maintenance, some simple some complex.
The following is a list of these functions.
Basic maintenance to assign SN (for both Uplane and Cplane)
SN maintenance for Integrity protection (for Cplane)
SN maintenance for ciphering/deciphering (for both Uplane and Cplane)
SN maintenance for data forwarding (for Uplane HO)
Duplicate detection and in-order delivery (for Uplane HO)
Depends on the scenarios, the SN maintenance may use one or several of these
functions, or a combination of them, in each PDCP entity.
PDCP SN maintenance relies on RLC layer in-sequence delivery (for all modes)
during non-HO period. During HO period, special PDCP SN maintenance procedures
are used.
Page 34/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
The following control procedures are covered by this version of the LPUG:
-
Intra-eNB mobility (Like in TLA2.0,LA1.0, LA0.x)

o
without PDCP SN (to see 3GPP TS 36.323) preservation (i.e. only

RLC-UM data bearers)
with PDCP SN preservation (i.e. at least one RLC-AM data bearer)
Inter-eNB mobility
o
without X2 data forwarding (Like inTLA2.0,LA1.0, LA0.x)

without PDCP SN preservation (i.e. only RLC-UM data bearers)
with PDCP SN preservation (i.e. at least one RLC-AM data

bearer)
with X2 data forwarding of DL S1 fresh packets (Like in TLA2.0,LA1.0,

LA0.x)
without PDCP SN preservation (i.e. only RLC-UM data bearers)
with X2 data forwarding of DL PDCP SDUs with their SN that have not
been acknowledged by the UE and DL fresh data arriving over S1
forwarded over X2 without a PDCP SN to the target eNB. (Like in LA1.x)
with PDCP SN preservation (i.e. RLC-AM data bearer)
Mobility Management
The mobility is initiated by eNodeB, based on UE RSRP or RSRQ measurements.
These measurements report are sent via PUSCH. In this release:
In TLA2.1 an intra frequency measurement (Event A3) triggers a mobility within
EUTRAN.
In TLA2.1 an intra frequency measurement (Event A2 blind) triggers a mobility
towards another RAT in a blindly fashion i.e. without measurement on the target cell
that belongs to the target RAT.
The current cell neighborhood is not transmitted to the UE in the measurement
configuration command (Except if the parameter sibOrMeasObjectUsage is present
and set to MeasObject-only or SIB-and-MeasObject). The UE reports every detected
and measurable cell.
Mobility procedures supported are:
The intra-eNodeB mobility only involves UE and eNB.
The inter-eNodeB mobility procedure performed over X2. MME is involved for the
path switch command.
The inter-eNodeB mobility procedure performed over S1.
The PDCP sequence number preservation during mobility is fully supported.
In TLA2.1, Access Stratum security (FRS92638) is supported. This capability
requires that key and synchronization information transfer is supported during both
intra-eNB and inter-eNB mobility.
Page 35/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction:TLA2.1
Due to UE restriction, measurementPurpose Blind-PS-Handover-To-UTRA-TDD, BlindRedirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD,
Meas-Redirection-To-UTRA-TDD,
Meas-Redirection-To-GERAN are not supported in TLA2.1.
4.1.2.1 MOBILITY ACTIVATION

Rule: Mobility Management
the mobility is enabled via MIM configuration / MIM
isIntraFreqMobilityAllowed set to TRUE in MO ActivationService
parameter
Figure 5 : Mobility activation

The parameters below are in the scope of mobility activation and information
options. Be careful, it is mandatory to activate them, for mobility. Theyre
Fixed category and they are C class parameters:
ActivationService:: isIntraFreqMobilityAllowe
Parameter
object name
Definition
This flag enables or disables the procedure of intra-
isIntraFreqM
ActivationServi frequency mobility. If disabled, the eNB will not
trigger any outgoing intra-frequency mobility
obilityAllow
ce
procedure and will reject any incoming mobility
ed
Range &
default value
unit
[false,
true]
O.D. (true )
[false,
true]
O.D. (true )
procedure.
isDataForwa
ActivationServi This flag enables data forwarding (see section
rdingAllowe
4.1.2.2)
ce
d
Table 5: Mobility information parameters
Page 36/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: Mobility Configuration Management
-If you want to activate the eUTRAN mobility, the parameter
ActivationService::isIntraFreqMobilityAllowed need to be set to true.
-If you want to activate the eUTRAN mobility with data forwarding enabled, the
parameter ActivationService::isDataForwardingAllowed need to be set to
true.
4.1.2.2 INTRA-FREQUENCY INTRA-ENB MOBILITY

The following describes the required call flow and high level procedure
The Intra eNB handover use case is transparent to the ePC, i.e. there is no signalling
exchange eNB - MME
Purpose: the RRC Connection is handed over from the source cell to target cell intra
eNB.
Pre-conditions:
The UE is RRC CONNECTED in the source cell.
The default E-RAB is established .According to 3GPP an intra-LTE handover should
not be triggered until the security is activated (the UE only accepts a handover
message when security is activated). The eNB may trigger an intra-LTE handover
only after the default bearer is established and security activated
Initial state:
UE in RRC CONNECTED in the source cell: SRB1/SIB2 + default bearer
(+dedicated bearer) are established.
Applicable eNB procedures:

RRC Connection Reconfiguration (mobility)
Final state:
UE in RRC CONNECTED in the target cell: SRB1/SIB2 + default bearer (+dedicated
bearer). If the handover occurs, all the bearers from the source are handed over to the
target cell.
UE context and associated resources in the source cell are deleted.
See Section 8.2 INTRA-FREQUENCY INTRA-ENB CALL FLOW:
Page 37/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
eNB
RRCConnectionReconfiguration
MME/SGW
S1-AP INITIAL UE MESSAGE
MeasurementConfiguration
RRCConnectionReconfigurationComplete
Default E-RAB establishment and security activation
DL Data
Measurement Report
measid
measResultServing
neighboring MeasResults
Handover Decision
Integrity protected
and ciphered with
former keys
Setup UE associated resources

in the target cell
AS security algorithms
selection
RadioResourceConfigDedicated
MobilityControlInformation
UE RelatedInformation
security information including
(integrityProtAlgorithm &
cipheringAlgorithm)
Derive Keys
Switch DL to Target cell
Start receiving UL in Target cell
Detach from old cell and

synchronize to new cell
DL Data
Random Access Preamble

Random Access Response
Start RRC integrity protection with new key
Start RRC integrity
protection with new key
Start RRC and UP UL deciphering with new keys

Start RRC and UP DL ciphering with new keys
Start RRC and UP UL

ciphering with new keys
Start transmitting DL in target cell
Integrity protected and ciphered with new keys
Start RRC and UP DL

deciphering with new keys
UE
Release UE associated
resources in the source cell
eNB
MME/SGW
Figure 6 : Call flow for Intra-eNB mobility - UE in RRC CONNECTED

Page 38/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Note that in Figure 6, new actions and message content that are associated with the
Integrity Protection and Confidentiality feature (FRS92638) are highlighted with a gray
background.
After the S1-AP Initial UE message is transmitted, the eNB sets-up the measurement
configuration in the UE used for intra-frequency mobility trigger. This happens before
the default bearer is established or DL NAS signalling occurs.
When the eNB receives a MeasurementReport it will decide if a handover procedure
needs to be triggered. In case of handover trigger, the eNB selects the target cell
based on the UE measurement report and trigger an intra-eNB handover procedure if
the selected target cell belongs to the same eNB. If the selected target cell belongs to
a different eNB then trigger an inter-eNB handover procedure.
In case of intra-eNB handover, the eNB will:
-
perform admission control
setup L1/L2 resources in the target cell
perform U-plane actions in the source cell
Transmit the RRC CONNECTION RECONFIGURATION to the UE. The RRC

CONNECTION RECONFIGURATION message contains security information that
the UE uses to derive new keys to use with the target cell
In TLA2.1, up to 4 Bearers is supported per UE. So, for handover, the up to 4 Bearer
HO is also supported. In TLA2.1, AMBR is supported.
When the UE receives RRC CONNECTION RECONFIGURATION it is not aware
whether an intra-eNB or inter-eNB handover is to be executed. The UE has the same
behaviour for both cases.
The UE stops receiving/transmitting from the source cell, reconfigures its L1/L2 as
requested in RRC CONNECTION RECONFIGURATION. The UE performs
synchronization to the target cell and accesses it via a contention-based random
access. Once access to the new cell is available, the UE and the target ENB use new
keys for integrity protection and ciphering.
Both contention-based and non-contention based random access are supported. If
resources are available the eNB allocates a dedicated preamble to the UE.
If the UE succeeds to access the target cell it will transmit RRC CONNECTION
RECONFIGURATION COMPLETE.
When the eNB receives the RRC CONNECTION RECONFIGURATION COMPLETE,
it will
-
perform U-plane actions in the target cell Release UE resources in the source cell
Procedure interactions:
If there is no match between UE supported security algorithms and eNB supported
security algorithms, the handover is aborted and the eNB initiates the S1 UE context
release procedure.
Page 39/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: TLA2.1 FRS 98841
In TLA2.1, up to 4 Bearers is supported per UE. So, for handover, the up to 4 Bearer
HO is also supported. In TLA2.1, AMBR is supported. For handover, the last updated
AMBR shall be updated by the eNB and the AMBR be forwarded to L2 scheduler.
Failure cases:
-
[97979] In TLA2.1, partial failure is introduced. So, only when all TRBs fail CAC
(i.e. no TRBs can be established at target cell) will lead to HO cancel.
If at least one TRB succeeds (and at least one TRB fails) in RRM in target cell, the
HO execution will continue.
The TRB that was successful in RRM will be handed over to the target cell and the
failed TRB will be released.
In case the eNB is requested to release a non-existent radio bearer Id or a

duplicate request to delete the same radio bearer Id, the eNB should respond
back with an appropriate cause value to indicate this.
If any UL RRC messge is received with integrity verification failure, the procedure is
aborted, and the eNB initiates the S1 UE context release procedure.
On reception of an RRC Connection Re-establishment Request with any cause,
mobility has failed. The eNB processes the re-establishment request normally and
resumes SRD1, SRB2, and DRBs (this will lead to new security keys computation) on
the cell that is selected for re-establishment.
4.1.2.2.1 KEY REFRESH OR RE-KEYING

Key refresh is triggered by:
Notification from the PDCP layer that a COUNT is about to wrap around.
COUNTS cannot be reused, so new keys must be generated
Detection that all DRB-id values have been used with a given key (meaning
that no new RB-id can be allocated without a security key change)
Re-keying is initiated by the MME by the transmission of an S1 UE CONTEXT

MODIFICATION REQUEST message with information allowing derivation of new
keys.:
After a successful EPS Authentication and Key Agreement procedure is run.
After a handover from UTRAN/GERAN in order to activate a native EPS
security context
For either key reresh or re-keying, an intra-cell handover is performed as shown in

Figure 6. The principal differences are:
The key refresh procedure is triggered by PDCP layer notification or
detection that all DRB-id values have been used (instead of a
Page 40/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measurement report trigger), and the RadioResourceConfigDedicated IE
is not included in the RRCConnectionReconfiguration message.
The re-keying is initiated by the MME using the S1 UE CONTEXT
MODIFICATION REQUEST message, and Figure 6 is modified as
follows
o
for the RRCConnectionReconfiguration message:

the RadioResourceConfigDedicated IE is not included
the keyChangeIndicator is set equal to TRUE
On receipt of the RRCConnectionReconfigurationComplete message,

the eNB will send an S1 UE CONTEXT MODIFICATION
RESPONSE message to the MME.
4.1.2.3 INTRA-FREQUENCY INTER-ENB X2 HANDOVER
The following describes the required call flow and high level procedure
X2 based Inter-eNB handover without MME node change
Purpose: the RRC Connection is handed over from the source to target cell inter eNB.
Pre-conditions:
X2 interface is setup towards the target eNB (to see [Vol. 5])
The UE is RRC CONNECTED in the source eNB
In TLA2.1; the default E-RAB is established and security activated. Handover is not
triggered before as per 3GPP specification..
According to 3GPP an intra-LTE handover should not be triggered until the security is
activated (the UE only accepts a handover message when security is activated). The
eNB may trigger an intra-LTE handover only after the default bearer is established
and security activated Initial state:
UE in RRC CONNECTED in the source cell source eNB: SRB1/SRB2 + default
bearer (+dedicated bearer) are established.

X2-AP Handover preparation procedure
X2-AP SN status transfer procedure only if PDCP SN status preservation applies for
at least one of the Radio Bearers handed over. This is applicable only to RB using
RLC-AM mode
RRC Connection Reconfiguration (mobility) procedure
X2 U-plane data forwarding (if enabled via MIM configuration)
X2-AP UE CONTEXT RELEASE procedure
S1-AP path switch request procedure
Page 41/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Final state:
UE in RRC CONNECTED in the target cell, target eNB: SRB1/SRB2 + default bearer
(+dedicated bearer). If the handover occurs, all the bearers from the source eNB are
handed over to the target eNB cell.
UE context and associated resources in the source eNB are deleted.
To see annex 8.3 INTRA-FREQUENCY
INTER-ENB CALL FLOW
In TLA2.1, up to 4 Bearers are supported per UE. So, for handover, up to 4 Bearer HO
will be supported. In TLA2.1, AMBR is also supported. For handover, the last updated
AMBR shall be transferred by Source eNB and received by Target eNB over X2, the
AMBR will be forwarded to L2 scheduler. For X2 handover, the AMBR in S1AP PATH
SWITCH REQUEST ACKNOWLEDGE is taken into account.
Page 42/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
Source eNB
Target eNB
Measurement Report
MME/SGW
DL Data
Handover Decision with
Target Cell Selection
X2 Handover Request
UE Context Information
AS Information
Handover Preparation
Setup UE context & associated

resources in the target cell
AS security algorithms selection
and key derivation
Prepared by Target eNB and transparently

forwarded by Source eNB to UE
Integrity protected and ciphered with former keys
X2 Handover Request Acknowledge

Start forwarding DL
packets to Target
eNB
RadioResourceConfigDedicated
MobilityControlInformation
UE RelatedInformation
security information including
(integrityProtAlgorithm &
cipheringAlgorithm)
Start RRC Integrity protection

with new key
Start RRC and UP ciphering with
with new keya
Start buffering DL packets from
source eNB
DL Data Forwarding
DL Data
Derive Keys
X2 SN Status Transfer
Handover Execution

Start RRC integrity

Start RRC and UP UL
Integrity protected and ciphered with new keys
Continued on next page
Page 43/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
Source eNB
Target eNB
MME/SGW
Start transmitting DL packets
DL Data
S1 Path Switch Request
UE Security Capabilities
Start buffering packets from

S1
DL Data
DL Data Forwarding
Derive Key for ciphering

Verify UE security capability
DL Data
DL data (end marker)
S1 Path Switch Request Ack
Security Context
Store received security

context
X2 UE CONTEXT
RELEASE
Transmit all DL X2 packets

before S1 packets
Continue forwarding DL
packets
Release UE context and

associated resources
UE
Source eNB
DL forwarding data (end marker)
Release X2 resources
Target eNB
MME/SGW
Figure 7: Call flow for Inter-eNB mobility, X2 HO - UE in RRC CONNECTED

Page 44/266
Handover Completion
Path switch
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Note: In the call flow above the Downlink user plane actions are mentioned for
information. The yellow boxes and blue text apply in case of DL data forwarding. For
the sake of simplicity, the UL user plane actions were omitted from the call flow. UL
data forwarding is not supported also in TLA2.1 like in TLA2.0. In Figure 7, new
actions and message content that are associated with the Integrity Protection and
Confidentiality feature (FRS92638) are highlighted with a gray background.
In TLA2.1, after the S1-AP Initial UE message is transmitted, the eNB sets-up the
measurement configuration in the UE used for intra-frequency mobility trigger. This
happens before the default bearer is established or DL NAS signalling occurs.
When the eNB receives a MEASUREMENT REPORT it will decide if a handover
procedure needs to be triggered. In case of handover trigger, the eNB selects the
target cell based on the UE measurement report and trigger an intra-eNB handover
procedure if the selected target cell belongs to the same eNB. If the selected target
cell belongs to a different eNB, either the X2 bases or the S1 based inter-eNB
handover procedure is triggered.
In the following presentation the X2 based handover procedure presentation is split in
3 distinct phases similar to 3GPP TS 36.300:
Phase 1: handover preparation
- This phase involves the Source eNB, the target eNB and finally the UE.
- In case of inter-eNB handover trigger, the Source eNB will initiate the X2-AP
handover preparation providing in X2-AP HANDOVER REQUEST the
necessary information to prepare the handover in the Target eNB. If the
data forwarding is enabled in the Source eNB via MIM configuration
then the Source eNB will propose to the target eNB to perform DL
data forwarding via X2. The eligibility to DL forwarding of each
supported QoS Label (QCI) is configured via MIM. If Integrity Protection
and Confidentiality services are enabled, AS security data is also included
in the X2 HANDOVER REQUEST message.
isDataForwardingAllowed : This flag enables data forwarding.
ActivationService::isDataForwardingAllowed
Parameter
isDataForwardingAllowed
Object
Enb/ ActivationService
Range & Unit
Boolean
[False, True]
Class/Category
C / Fixed
Value
True
Feature
FRS 96760
- The target eNB prepares the handover based on the received request from
the Source eNB and includes in HANDOVER REQUEST
Page 45/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ACKNOWLEDGE the RRC CONNECTION RECONFIGURATION
message to be transmitted transparently by the Source eNB to the UE. If
the data forwarding is enabled in the Target eNB via MIM configuration
then the Target eNB will accept the proposal from the Source eNB to
perform DL data forwarding via X2 by establishing the one DL X2
tunnel for each E-RAB subject to forwarding. The eligibility to DL
forwarding of each supported QoS Label (QCI) is configured via MIM.
After this step the target eNB is ready to receive UL transmission from the
UE and DL data forwarded over X2 from the Source eNB if configured
previously. If AS security services are enabled, the target eNB also
derives keys that will be used for integrity protection and ciphering.
dataForwardingForX2HoEnabled : This flag enables or not the data

forwarding for this Radio Bearer in case of X2 HO.
RadioBearerConf::dataForwardingForX2HoEnabled
Parameter
dataForwardingForX2HoEnabled
Object
Enb/ DedicatedConf/ RadioBearerConf
Range & Unit
Boolean
[False, True]
Class/Category
C / Fixed
Value
O.D (Default value:True)
Feature
FRS
Note: If you want to set this parameter to True it should be mandatory to set the
parameter isDataForwardingAllowed above to True also.
TLA2.0 TLA2.1 : dataForwardingForX2HoEnabled

The name of this parameter is dataForwardingEnabled in TLA2.0
- The Source eNB transmits the RRC CONNECTION RECONFIGURATION

message to the UE
- The Source eNB transmits the X2-AP SN STATUS TRANSFER to the
Target eNB to convey the UL and DL PDCP SN (and HFN) of E-RABs for
which PDCP status preservation applies (i.e. mapped on RLC-AM mode).
This message is transmitted only if there is at least one E-RAB with PDCP
SN status preservation, otherwise it is omitted. When this message is
transmitted the Source eNB stops transmitting/receiving PDCP PDUs in
the source cell for the bearers for which status preservation applies.
Note: the X2-AP SN STATUS TRANSFER message handling as above in
the Source eNB is independent on whether data forwarding is enabled or
not.
Page 46/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Phase 2: handover execution

- This phase involves the UE, the Source eNB and the Target eNB
- If data forwarding was configured in the handover preparation phase, the
Source eNB forwards over X2 the DL PDCP SDUs numbered but not
acknowledged by the UE (only applicable for RLC-AM DRBs) followed by
fresh unnumbered PDCP SDUs (applicable for both RLC-UM and RLC AM
DRBs) received from S1 after HANDOVER REQUEST ACKNOWLEDGE
reception and stops transmitting in the source cell the fresh unnumbered DL
PDCP SDUs.
- When the UE receives RRC CONNECTION RECONFIGURATION in the
source cell it will stop receiving/transmitting data in the source cell and will
initiate synchronization to the target cell followed by random access procedure
as indicated in the received message. Both contention-based and noncontention based random access is supported. If resources are available the
eNB allocates a dedicated preamble to the UE. When the UE random access
is successful, it will transmit the RRC CONNECTION RECONFIGURATION
COMPLETE using updated integrity protection and ciphering keys for the new
connection. Starting from this point the UL and DL data transmission is
resumed. The handover procedure ends in the UE
Phase 3: handover completion

- This phase involves the the Source eNB, the Target eNB end the ePC
- When
the
Target
eNB
receives
the
RRC
CONNECTION
RECONFIGURATION COMPLETE it will send the S1-AP PATH SWITCH
REQUEST to the MME to inform the that the UE changed the cell
- After the transmission of S1-AP PATH SWITCH REQUEST, the Target eNB
is ready to receive DL data over S1
- Upon request from the MME (at reception of S1-AP PATH SWITCH
REQUEST), the SGW switches the DL data path to the Target eNB. The
SGW sends one or more GTP-U End Marker per GTP-U tunnel through
the old path (i.e. old S1 U-plane interface) to the Source eNB and then
release the U-plane resources and confirms the path switch to the MME
which in turn sends S1 PATH SWITH REQUEST ACKNOWLEDEGE to
the Target eNB. This message contains the security information for the
NAS signalling messages that will have integrity protection.
- During the handover completion the UL data transmission occurs normally in
the Source or the Target eNB
- if DL data forwarding was configured, the Source eNB continue to
forward via X2 interface the received DL S1 packets until reception
of GTP-U End Marker or resources are released
- if DL data forwarding was configured, the Target eNB shall transmit the over
the radio the DL X2 received packets until reception of X2 GTP-U End
Marker or resources are released. Only after that DL S1 packets are
transmitted.
- if DL data forwarding was not configured, the Target eNB will transmit the S1
DL packets normally
Page 47/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
- At the reception of S1 PATH SWITH REQUEST ACKNOWLEDEGE, the
Target eNB transmits X2-AP UE CONTEXT RELEASE to the Source eNB.
After the target eNB transmitted the X2-AP UE CONTEXT

RELEASE the handover procedure ends. The specific trigger to
end the procedure depends on whether the X2 data forwarding
occurred and specific GTP-U End Marker handling as specified in
the later of this document
After the Source eNB received the X2-AP UE CONTEXT

RELEASE the handover procedure ends and UE associated
resources are deleted. The specific trigger to end the procedure
depends on whether the X2 data forwarding occurred and specific
GTP-U End Marker handling as specified in the later of this
document ALU INTERNAL:
endX2HoDataFwdTarget: For X2 HO, maximum time to wait in the target eNB

for reception of eGTP end of forwarding packet (29.274) received via X2 if DL
data forwarding over X2 is configured. A single timer is started for all E-RABs
subject to forwarding when X2-AP Release Resource is transmitted to the Source
eNB. At the reception of eGTP end of forwarding packet (29.274) over X2 or
timer expiry, the target eNB starts transmitting DL packets received over the new
S1 and releases X2 associated ressouces of X2 eGTP tunnel.
X2GtpConf::endX2HoDataFwdTarget
Parameter
endX2HoDataFwdTarget
Object
Enb/ X2AccessGroup/ X2GtpConf
Range & Unit
ms
[1..5000] step = 1
Class/Category
Value
100
Feature
FRS
LA1.1 - LA2.0 : dataForwardingForX2HoEnabled

The name of this parameter is endDataFwdTarget in TLA2.0
This parameter is there, just for get the right time to release the X2 Setup. This timer is
armed with the message X2 UE CONTEXT RELEASE at the level of Figure 7 just
above.
4.1.2.3.1 FAILURE CASES

The outcoming handover fails in the source eNB:
Page 48/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
On the following triggers:
-
reception of HANDOVER PREPARATION FAILURE, or
HANDOVER REQUEST ACKNOWLEDGE containing admitted and rejected ERAB or
The expiry of the internal defence timer X2Preparation supervising the X2

procedure handover preparation,
The handover procedure is aborted in the eNB and the UE call context is returned to
the state before the handover trigger was received.
If the RRCConnectionReconfiguration fails the UE initiates RRC Connection reestablishment procedure in the source cell and in the preparation or execution phase.
The eNB initiates RRC re-establishment procedure and handover is aborted in the
Source eNB.
[97940 Support of HO Cancel: The eNB transmits the X2-AP HANDOVER CANCEL
message].
[97979] In TLA2.1, partial failure is introduced. So, only when all TRBs fail CAC
(i.e. no TRBs can be established at target cell) will lead to Reject HO.
If at least one TRB succeeds (and at least one TRB fails) in RRM in target cell, the
HO execution will continue.
The TRB that was successful in RRM will be handed over to the target cell and the
In case the eNB is requested to release a non-existent radio bearer Id or a

duplicate request to delete the same radio bearer Id, the eNB should respond
back with an appropriate cause value to indicate this.
The incoming handover fails in the target eNB:

At the level of the handover preparation phase
o
If mobility is not enabled (i.e. MIM parameter isIntraFreqMobilityAllowed is

not set to TRUE in MO ActivationService) or if the cell is barred; in this case
the Cause IE is set to Radio Network Layer Cause "Cell not Available"
If the S1 link to the MME identified by the GUMMEI information element is

down or the S1 Setup procedure has not completed successfully; in this case
the Cause IE is set to Radio Network Layer Cause "Cell not Available"
If the GUMMEI is unknown; in this case the Cause IE is set to Radio Network
Layer Cause "Invalid MME Group ID" or "Unknown MME Code"
Or due to failure to establish the requested resources (admission control

failure, eNB internal failure, RLC mode is not the same, etc); in this case the
Cause IE is set to Radio Network Layer Cause "Cell not Available"
And the target eNB will transmit HANDOVER PREPARATION FAILURE to the
source eNB and delete any context/resources related to this failed request.
[97940] Support of HO Cancel: If the eNB receives the X2-AP HANDOVER CANCEL
message after the successful handover preparation then the handover is cancelled
and all UE related configuration and prepared resources are released.
[97979] In TLA2.1, partial failure is introduced. So, CAC will fail, implying a preparation
failure, only when:
Page 49/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
- all TRBs fail CAC (i.e. Nno TRBs can be established atin target cell) will
lead to HO cancel
- No non-GBR TRB can be established in the target cell (according to ).
If at least one non-GBR TRB succeeds (and at least onewhile other TRBs may fails) in
RRM in the target cell, the HO execution will continue.
The TRB that was successful in RRM will be handed over to the target eNB and the
In case the eNB is requested to release a non-existent radio bearer Id or a duplicate
request to delete the same radio bearer Id, the eNB should respond back with an
appropriate cause value to indicate this.(Valide also in execusion phase)
4.1.2.3.2 FEATURE INTERACTIONS

At the level of the source eNB, during handover preparation phase:
Procedures triggered after HANDOVER REQUEST transmission and before reception
HANDOVER REQUEST ACKNOWLEDGE:
-
S1 release is executed. X2 HANDOVER CANCEL is transmitted to the target eNB

with cause IE set to Radio Network Layer Cause / Unspecified.
UL or DL NAS transfer procedures are executed normally
S1-AP E-RAB setup/release procedures are failed
Internal traffic inactivity detection trigger is ignored.
If internal RL failure is triggered or if the UE initiates RRC Connection Reestablishment procedure,

-
the handover procedure is cancelled and the eNB enters the RRC
Connection Re-establishment procedure as described in .
[97940 Support of HO Cancel: The eNB transmits the X2-AP HANDOVER CANCEL
message].
[97941
Support of new mobility procedure interactions for KPI improvements:
If a UE MeasurementReport triggering a handover procedure is received after X2-AP

HANDOVER REQUEST transmission and before reception X2-AP HANDOVER
REQUEST ACKNOWLEDGE then
-
the ongoing handover procedure is cancelled in the Source eNB. The source eNB
transmits X2-AP HANDOVER CANCEL to the Target eNB.
A new handover procedure is triggered according to the UE MeasurementReport.

This is applicable only once, i.e. any new UE MeasurementReport triggering a
handover procedure received is ignored]
A MeasurementReport received during an ongoing reconfiguration procedure (i.e.

dedicated bearer setup/release, UE context release) is ignored.
At the level of the target eNB, during handover completion phase:

[97941
Support of new mobility procedure interactions:
If the S1AP PATH SWITCH REQUEST ACKNOWLEDGE (Before RELEASE

RESOURCE and after Path switch in the MME) is received with the E-RAB To Be
Page 50/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Switched in Uplink List IE, the target eNB will update the uplink GTP TEIDs with the
new uplink tunnel endpoints.]
4.1.2.4 INTRA-FREQUENCY INTER-ENB S1 HANDOVER

In
order
to
use
S1
handover,
the
overall
activation
parameter
isIntraFreqMobilityAllowed (see Section 4.1.2.1) must be set to true. In addition,
an activation flag isS1HoAllowed (see Section 4.1.2.4.3) must also be set to activate
S1 handover capability.(FRS 98841)
As with X2 handover, an S1 handover is triggered by an A3 event trigger for which
the measurement purpose is intra-LTE mobility. With the introduction of S1
handover, the eNB must decide whether to use X2 handover or S1 handover. In LA2.0,
the basic eNB logic is that the eNB will use S1 handover when X2 handover
cannot be used. In addition, with the ANR feature (FRS 81872), the operator can
favor S1 handover over X2 handover through the use of the noX2HO flag (defined in
[Vol. 9]).
The scenarios that lead to S1 handover being triggered are:
There is no X2-C interface setup towards the target eNB, or the X2-C interface
is not available (e.g., SCTP down):
The target eNB is not connected to the serving MME;
The target eNB rejected the X2HO Request with an appropriate cause (e.g.,
invalid MME Group ID);
Configuration data indicates a preference for S1 handover (i.e., noX2HO

parameter introduced by ANR is set)
The following describes the call flow and high level procedure for inter-eNB handover
without MME change. If an MME change is required, the source eNB is not aware of
the change, but there is additional messaging between the source MME and the target
MME.
Page 51/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
Source eNB
Target eNB
MME/SGW
Measurement Report
DL Data
S1 Handover Decision with
Target Cell Selection
S1 HANDOVER REQUIRED
Handover Type & Target ID
UE Context Information
AS Information
E-RABs List
Store Security Information

Compute fresh security
information for target eNB
S1 HANDOVER REQUEST
Prepared by Target eNB and transparently

forwarded by Source eNB to UE
Integrity protected and ciphered with former keys
Handover Type (Intra LTE)

E-RABs to Setup List
UE Security Capabilities
Security Context
Setup UE Context & Assoc
Resources Including UE Capabilities
Derive Keys
S1 HANDOVER REQUEST ACKNOWLEDGE
E-RABs Admitted List

E-RABs Failed to Setup List
Start Buffering
Forwarded Packets
S1 HANDOVER COMMAND
mobility control information
securityConfigurationHO
handoverType = LTE
integrityProtAlgorithm &
cipheringAlgorithm
Derive New Keys
key information

Handover Type & Target ID

E-RABs Subject to Forwarding List
E-RABs to Release List
Target to Source eNB Transparent Container
Start RRC integrity protection with new key
Start RRC and UP UL ciphering with new
keys
S1 ENB STATUS TRANSFER

UL Count, DL Count
Start forwarding DL
packets to Target eNB
S1 MME STATUS TRANSFER

UL Count, DL Count
DL Data
DL Data Forwarding
(Possibly through
SGW)
Continued on next page
Page 52/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
Source eNB
Target eNB
MME/SGW
Start RRC integrity

Start RRC and UP UL
Integrity protected and ciphered with new
keys and algorithms

DL Data
Start buffering packets from

S1
S1 HANDOVER NOTIFY
DL Data
DL Data Forwarding
(possibly through SGW)
Derive Key for ciphering

Verify UE security capability
Path switch
DL Data
DL data (end marker)
Transmit forwarded packets

before S1 packets
Continue forwarding DL packets

DL forwarding data (end marker)
S1 UE CONTEXT RELEASE COMMAND

Release data forwarding

resources
S1 UE CONTEXT RELEASE COMPLETE
UE
Source eNB
Target eNB
MME/SGW
Figure 8: Call flow for Inter-eNB mobility, S1 HO - UE in RRC CONNECTED
Page 53/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Purpose: the RRC Connection is to be handed over vrom the source to target cell
inter-eNB
Pre-conditions:
The UE is in RRC-CONNECTED mode in the source eNB
One or more of the conditions listed above that will cause S1 handover
(instead of X2 handover) is in effect.
The default bearer is established and security activated. Handover is not
triggered before as per 3GPP specification.
According to 3GPP an intra-LTE handover should not be triggered until the
security is activated (the UE only accepts a handover message when security
is activated). The eNB may trigger an intra-LTE handover only after the
default bearer is established and security activated .
At least one of the following conditions is met:
o there is no X2 link between the two eNBs, or the X2 link is not
operational (X2Access object may or may not be defined);
o the target eNB is not connected to the MME currently serving the UE;
o the operator has favored (through provisioning) S1 handover over X2
handover for this source to target eNB pair;
o an X2-based handover has been rejected by the target eNB with
cause invalid MME group.
Initial state:
UE in RRC CONNECTED in the source cell source eNB: SRB1/SRB2 +
default bearer (+dedicated bearer) are established.
Trigger:
The eNB receives a measurement report for event A3_intra-frequency
mobility that indicates a potential target cell. When receiving event A3_intrafrequency mobility, the eNB triggers S1 handover.
S1-AP Handover preparation procedure
S1-AP SN status transfer procedure only if PDCP SN status preservation
applies for at least one of the Radio Bearers handed over. This is applicable
only to RB using RLC-AM mode.
RRC Connection Reconfiguration (mobility) procedure
X2 U-plane or S1 U-plane data forwarding depending on availability of a direct
forwarding path (and if enabled via MIM configuration)
S1-AP UE Context Release resourceUE CONTEXT RELEASE procedure
S1-AP Handover Notify procedure
Page 54/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Main Success Scenario (see Figure 4.1-4):

The eNB triggers handover preparation to the MME by sending the S1
HANDOVER REQUEST message
The MME requests the target eNB to prepare resources for the UE through
the S1 HANDOVER REQUEST message
The source eNB does not provide any key information to the MME. Fresh
information for deriving new keys is provided to the target eNB by the
MME.
The target eNB performs admission control and builds the handover
command, which it sends in the transparent container back to the MME,
which sends it to the source eNB
Upon reception of the RRC CONNECTION RECONFIGURATION message,
the UE switches cell and sends the HO complete to the target eNB
Once the UE is synchronized to the arget eNB cell, the target eNB requests
the MME to perform the path switch by sending the S1 HO NOTIFY
message
Post Conditions:
The UE has moved to the target cell
UE in RRC CONNECTED state in the target cell, target eNB: SRB1/SRB2 +
default bearer (+dedicated bearer). If the handover occurs, all the bearers
from the source eNBnot rejected by target eNB and/or MME are handed over
to the target eNB cell.
UE context and associated resources in the source eNB are deleted.
4.1.2.4.1 FAILURE CASES

If the source eNB sends an S1 HANDOVER REQUIRED message and receives an
S1-AP HANDOVER PREPARATION FAILURE message in response, the handover
has failed in the EPC or target eNB. In this case, the source eNB aborts the handover
procedure and returns the UE context to its state before the handover was triggered.
Some potential reasons for failure in the target eNB include:
S1 handover is not enabled or parameter isIntraFreqMobilityAllowed is
set to false or the cell is barred
Failure to establish the required resources (admission control failure, eNB
internal failure, RLC mode not the same, or other internal failure) in the
target eNB
Target eNB cannot find a security algorithm that matches the UE security
capability for either ciphering or integrity protection
Page 55/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Timer expiration. A timer, TS1RelocPrepForS1Handover, is introduced with S1

handover capability. This timer is started in the source eNB when it sends the S1
HANDOVER REQUIRED message, and the timer is cancelled when the S1
HANDOVER COMMAND message is received from the MME. If the timer expires
before the S1 HANDOVER COMMAND message is received from the MME, then the
source eNB sends an S1 HANDOVER CANCEL message to the MME, and expects to
receive an S1 HANDOVER CANCEL ACKNOWLEDGE message in response from
the MME. The UE context is returned to its state prior to the handover trigger.
When the source eNB receives the S1 HANDOVER COMMAND from the MME, it
starts timer tS1RelocOverallForS1Handover. The timer is stopped when the source
eNB receives the S1 UE CONTEXT RELEASE COMMAND message from the MME.
If the timer expires before the source eNB receives the S1 UE CONTEXT RELEASE
COMMAND message from the MME, then the source eNB sends an S1 UE
CONTEXT RELEASE REQUEST message. The expected result is that the MME will
send an S1 UE CONTEXT RELEASE COMMAND message to the source eNB, and
the UE context will be released.
At the level of execution phase:
If the RRCConnectionReconfiguration fails the UE initiates RRC Connection reestablishment procedure. The eNB initiates RRC re-establishment procedure and
handover is aborted in the Source eNB.
[97940 Support of HO Cancel: The eNB transmits the S1-AP HANDOVER CANCEL
message to the MME with cause IE set to Radio Network Layer Cause /
Interaction with other procedure.]
[97937 Support of new RRC Reestablishment cases: The eNB supports the RRC
connection re-establishment if received on any of its serving cells]
4.1.2.4.2 FEATURE INTERACTIONS

Similar to the actions with X2 handovers, once S1 handover preparation has been
triggered:
The source eNB could receive a request from the MME for an E-RAB
management procedure (Setup, Modify, or Release). With the current
implementation, the source eNB will reject the E-RAB management
procedure request.
If the eNB receives an S1-AP UE CONTEXT RELEASE COMMAND from
the MME, it will proceed with the release procedure.
NAS message transfer occurs normally.
Page 56/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE measurement reports received during the handover preparation are
ignored.
The UE can trigger RRC re-establishment towards a cell of the eNB. When
this happens, the eNB aborts the handover and processes the RRC reestablishment request. When this happens, the source eNB needs to:
o
[97940] Cancel the handover procedure by sending S1-AP

HANDOVER CANCEL to the MME with cause IE set to Radio
Network Layer Cause / Interaction with other procedure. This is
valide for preparation and execution phase.
Treat the re-establishment request from the UE . [97937 Support of

new RRC Re-establishment cases]: the source eNB will handle reestablishment requests on any of its cells. This is valide for
preparation and execution phase.
o
The source eNB may receive an S1-AP UE Context Modification request
from the MME. This can occur for several reasons:
o
Security re-keying. In this case, the source eNB will reject the
request with proper cause.
Providing an updated Service Profile Identifier (SPID) to be stored

in the UE context. In this case, the source eNB will reject the request
with proper cause.
Triggering Circuit Switched (CS) Fallback. In this case, the CS

fallback request takes precedence over the S1 handover procedures
so the CS call can be established as quickly as possible. As a result,
the handover is aborted
If the target eNB receives the S1-AP RESET message from the MME, it will
abort the handover and release the UE context. In this scenario, the UE
would not succeed its handover completion: it would perform RACH and likely
fail until expiry of T304. It may succeed its RACH (e.g. in case of contentionbased RACH) in which case the target eNB decoding of the RRC
CONNECTION RECONFIGURATION COMPLETE would fail due to security
and target eNB would release the UE S1 HANDOVER PARAMETERS
The parameters that are described in this section are introduced to support FRS
98841.
Page 57/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
In order to activate the S1 handover capability, an associated activation parameter
must be set equal to true.
isS1HoAllowed : This flag enables or disables the S1 handover procedure. If

disabled, the eNB will not trigger any outgoing S1 handover procedure and will
reject any incoming S1 handover procedure.
ActivationService::isS1HoAllowed
Parameter
isS1HoAllowed
Object
Range & Unit
Boolean
[True, False]
Class/Category
C / Fixed
Value
O.D (False is a default value)
Feature
FRS 98841
Engineering Recommendation: isS1HoAllowed

We recommend setting this parameter to True if you want activated S1
handover procedure.
Like for X2 HO, The operator can configure whether or not data forwarding is
performed for S1 handover for a specific radio bearer and associated QoS by the
setting of the dataForwardingForS1HoEnabled parameter. This parameter must be
enabled in both the source and the target eNB for S1 data forwarding to occur.
dataForwardingForS1HoEnabled : This flag enables or not the data forwarding

for this Radio Bearer in case of S1 HO. If set to true on both source and target
eNB, data forwarding will be performed. If set to False on either source or
target eNB, there will be no data forwarding.
RadioBearerConf::dataForwardingForS1HoEnabled
Parameter
dataForwardingForS1HoEnabled
Object
Enb/ DedicatedConf/ RadioBearerConf
Range & Unit
Boolean
[True, False]
Class/Category
C / Fixed
Value
True
Feature
FRS 98841
In the S1-AP HANDOVER REQUEST ACKNOWLEDGE message, the target eNB

must provide the address information that is to be used for data forwarding. The
Page 58/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
value of parameter directFwdPathAvailability is used by the target eNB to infer
whether a direct path is available. The target eNB may use different IP addresses for
direct
and
indirect
data
forwarding.
If
the
value
of
parameter
directFwdPathAvailability is true, then the target eNB supplies the IP address
for direct forwarding. If the value of this parameter is false, then the target eNB
supplies the IP address for indirect forwarding.
directFwdPathAvailability : Flag to Indicate whether or not a direct data

forwarding path is available with the peer eNB. True indicates that a direct path is
available
X2Access::directFwdPathAvailability
Parameter
directFwdPathAvailability
Object
Enb/ X2AccessGroup/ X2Access
Range & Unit
Boolean
[True, False]
Class/Category
C / Fixed
Value
False
Feature
FRS 98841
Page 59/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
As described in Section 4.1.2.4.1, several timers are used to protect the source and
target eNBs during S1 handover. The parameters that control the duration of these
timers are described below.
When the source eNB sends the S1-AP HANDOVER REQUIRED message to the
serving MME, it starts timer tS1RelocPrepForS1Handover. The duration of the
tS1RelocPrepForS1Handover timer is controlled by a configurable parameter with
the same name. The timer is stopped when a response is received from the serving
MME. If the timer expires before a response is received, then the source eNB cancels
the handover preparation procedure.
tS1RelocPrepForS1Handover : TS36.413: When the source ENB sends the

S1AP HANDOVER REQUIRED message for the S1 handover, it shall start the
timer tS1RelocPrepForS1Handover
S1HoTimersConf:: tS1RelocPrepForS1Handover
Parameter
tS1RelocPrepForS1Handover
Object
Enb/ S1AccessGroup/ S1Timers/ S1HoTimersConf
Range & Unit
Integer ms
[1 10000] step = 1
Class/Category
Value
5000
Feature
FRS 98841
Page 60/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
When the source eNb sends the S1-AP HANDOVER COMMAND, it starts timer
tS1RelocOverallForS1Handover. The duration of this timer is set using a
configurable parameter of the same name. This timer is stopped when the source eNB
receives an S1AP UE CONTEXT RELEASE COMMAND message from the MME. If
the S1AP UE CONTEXT RELEASE COMMAND message is not received from the
MME before the timer expires, then the eNB will send the S1-AP UE CONTEXT
RELEASE COMMAND message to the MME to start the release of the UE context.
tS1RelocOverallForS1Handover : TS36.413: Upon reception of the S1AP

HANDOVER COMMAND message (in case of S1 handover) the source eNB
shall start the timer tS1RelocOverallForS1Handover
S1HoTimersConf:: tS1RelocOverallForS1Handover
Parameter
tS1RelocOverallForS1Handover
Object
Range & Unit
Integer ms
[1 10000] step = 1
Class/Category
Value
5000
Feature
FRS 98841
Page 61/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
After having transmitted the S1-AP HANDOVER NOTIFY message and received the
S1-AP MME STATUS TRANSFER message (if applicable), the target eNB starts an
operator-configurable timer (endS1HoDataFwdTarget). A single timer is started for all
radio bearers for which data forwarding was accepted by the target eNB,The timer
is stopped upon reception of all GTP-U end marker packets. While this timer is
running, the target eNB prioritizes DL Forwarded data from the source eNB (both with
and without PDCP SN) over fresh S1-U plane data coming from the SGW. If the timer
expires, then the target eNB stops prioritizing the DL Forwarded data over the fresh
S1-U plane data.
endS1HoDataFwdTarget : For S1 HO, maximum time to wait in the target eNB

for reception of eGTP end of forwarding packet (29.281) received via X2 or S1 if
DL data forwarding is configured. A single timer is started for all E-RABs
subject to forwarding when S1-AP Handover Notify is transmitted to the MME. At
the reception of eGTP end of forwarding packet (29.281) or timer expiry, the
target eNB starts transmitting DL packets received over the new S1 and releases
ressouces associated with the eGTP tunnel.
S1HoTimersConf::endS1HoDataFwdTarget
Parameter
endS1HoDataFwdTarget
Object
Range & Unit
Integer ms
[1 5000] step = 1
Class/Category
Value
150
Feature
FRS 98841
4.1.2.5 INTRA-FREQUENCY MEASUREMENT REPORTING

SETTING
The handover strategy relies entirely on measurement reports from the UE. The UE
reports to the eNB when the handover trigger conditions are met. Upon receipt of the
measurement report the eNB is expected to trigger a handover procedure.
The measurements are setup, modified or deleted in the UE using RRC signalling,
more precisely the RRCConnectionReconfiguration message including the IE
MeasurementConfiguration.
The measurements defined as intra-frequency LTE mobility triggers are configured as
early as possible in the UE. These measurements are identified by a measurement
identity
configured
to
measId
and
the
attribute
MeasurementIdentityConf.measurementPurpose equal to intra-frequency
handover trigger
Page 62/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measurementPurpose: This
measurement reporting.
parameter
configures
the
purpose
of
this
MeasurementIdentityConf::measurementPurpose
Parameter
measurementPurpose
Object
Enb/ RrmServices/ UeMeasurementConf/

MeasurementIdentityConf
Range & Unit
Enumerate
[Intra-frequency-handover-trigger, Inter-frequencyhandover-trigger ,Redirection-to-HRPD-via-Event-A2,
Automatic-Neighbour-Relation, Report-CGI, Deactivation-OfMeasurement-Gap, Activation-Of-Measurement-Gap, BlindRedirection-To-3GPP-RAT, Blind-PS-Handover-To-UTRA-TDD,
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD,
Meas-Redirection-To-UTRA-TDD, Meas-Redirection-To-GERAN,
Meas-PS-Handover-To-UTRA-TDD, Meas-Redirection-Or-PSHandover-To-UTRA-TDD, Meas-CellChangeOrder-To-GERAN,
Meas-Redirection-Or-CellChangeOrder-To-GERAN]
Class/Category
C / Fixed
Value
Meas-Redirection-Or-PS-Handover-To-UTRA-TDD
Feature
FRS 96760
Warning: Lots of proposal for this parameters are not possible because not yet
implemented. In black and bold, its implemented in previous release. In black and
highlighted in grey, its implemented in TLA2.1.
The values in red barred are not implemented in TLA2.1.x.
Restriction: TLA2.1
Due to UE restriction, measurementPurpose Blind-PS-Handover-To-UTRA-TDD,
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD, Meas-RedirectionTo-UTRA-TDD, Meas-Redirection-To-GERAN are not supported in TLA2.1.
Rule: measurementPurpose
Only one instance of MeasurementIdentityConf MO per cell can have
measurementPurpose set to Automatic-Neighbour-Relation.
Only one instance of MeasurementIdentityConf MO per cell can have
measurementPurpose set to Report-CGI
The parameters below are in the scope of measurement information elements.

Theyre Fixed category and they are C class parameters:
Page 63/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
MeasurementIdentityConf::measObjectId
Rule: measObjectId
measObjectId for MeasurementIdentityConf insance with measurementPurpose =
'Automatic-Neighbor-Relation' can only be set to the same value as the
measObjectId for MeasurementIdentityConf instance with measurementPurpose =
'Intra-frequency-handover-trigger', where both MeasurementIdentityConf instances
are pointed to by the same instance of RrcMeasurementConf.
measObjectId for MeasurementIdentityConf insance with measurementPurpose =
'Report-CGI ' can only set to the same value as the measObjectId for
MeasurementIdentityConf instance with measurementPurpose = 'Intra-frequencyhandover-trigger', where both MeasurementIdentityConf instances are pointed to
by the same instance of RrcMeasurementConf.
MeasurementIdentityConf:: reportConfigId
ReportConfig:: reportConfigId
Parameter
measObjectId
object name
MeasurementId
entityConf
reportConfigI
d
MeasurementId
entityConf
reportConfigI
d
ReportConfig
Definition
This parameter refers to the instance of the
MeasObject MO that must be considered when the
UE is configured with the measurement
configured by this instance of the MO
This parameter refers to the instance of the
ReportConfig MO that must be considered when
the UE is configured with the measurement
configured by this instance of the MO
3GPP 36.331. This parameter configures the RRC
IE reportConfigId in the
MeasurementConfiguration IE
Range
& unit
Service
Link
Service
Link
pointer
RrmServices/0
UeMeasurementConf/0
MeasObject /2
RrmServices/0
UeMeasurementConf/0
ReportConfig/6
[1..32]
step=1
Table 6: Measurement information parameters
The IE MeasObjectId used to identify a measurement object configuration. Existing a

maximum of 32 MeasurementIdentityConf MO possible.
The IE ReportConfigId is used to identify a measurement reporting
configuration.[R08]
The description of the measurements model object is found in paragraph 4.3
Page 64/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.1.2.5.1 MEASUREMENT SETUP UPON TRANSITION TO RRCCONNECTED STATE
If the intra-frequency mobility is enabled via MIM configuration (i.e.
isIntraFreqMobilityAllowed set to TRUE in MO ActivationService) the eNB will
initiate a RRC Connection reconfiguration procedure after the RRC Connection
establishment completion to setup the intra-frequency measurements corresponding
to the instances of the MOs MeasurementIdentityConf having the parameter
measurementPurpose set to intra-frequency handover trigger
If the procedure fails the UE will transit to idle mode. Indeed, according to 3GPP if a
RRC reconfiguration procedure fails in the UE, the UE will initiate a RRC
Connection Re-establishment procedure. If this happens before the security
activation, the UE will transit directly to idle mode.
The eNB will initiate after the default bearer establishment (and security activation)
another RRC Connection reconfiguration procedure to set-up intra-frequency
measurements corresponding to the instances of the MOs MeasurementIdentityConf
having the parameter measurementPurpose different than intra-frequency
handover trigger (if any). The RRC message RRCConnectionReconfiguration
includes the IE measurementConfiguration used to configure the intra-frequency
measurement profile described in section 4.3.1. This profile is applicable for the cell
on which the call is established.
If the measurement configuration fails in the UE, it will initiate RRC Connection Reestablishment.
UE
ENB
MME/SGW
S1-AP INITIAL UE MESSAGE
Default SAE Bearer establishment and security activation [A15]

UE
Optional depending
on OAM configuration
ENB
MME/SGW
Figure 9: Measurement setup at call setup
Page 65/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.1.2.5.2 MEASUREMENT UPDATE UPON COMPLETION OF
HANDOVER
The measurement configuration is specified in section 4.3.1.
The measurement configuration updated by the eNB is that of the target cell intrafrequency measurement profile described in section 4.3.1.
Inter-eNB handover :
In case of inter-eNB handover, (both X2 based or S1 based) the target eNB updates
the measurement triggering the handover procedure (if target configuration is different
from the source configuration) by including the Measurement Configuration
parameters in the RRCConnectionReconfiguration message transmitted to the UE via
the Source eNB. Based on the MIM configuration applicable in the target cell and
received UE capability, the target eNB prepares the target cell measurement
configuration.
The
target
eNB
uses
the
RRC
container
(i.e.
HandoverPreparationInformation. AS-Configuration. MeasurementConfiguration) to
learn the configuration used in the source eNB. In order to minimize the size of the
signalling message, the target eNB will update only the changing configuration, the
unchanged configuration is not signalled (i.e. OC option in asn.1 definition) and the UE
keeps the previous configuration.
In the handover message, the configuration of any measurement not matching the
target cell configuration for handover trigger (i.e. same measId, same
MeasObjectEUTRA, same ReportConfigEUTRA) is handled as follows:
-
Source ReportConfigEUTRA is kept in the UE,
Source MeasObjectEUTRA is deleted. In 3GPP RRC only one MeasObject

per frequency is supported in the UE. In TLA2.0 only one frequency is
supported.
Source MeasId is kept in the UE.
After the handover procedure is completed at the target eNB (i.e. after the X2
CONTEXT RELEASE transmitted to the Source eNB for X2 based handover, or after
the end of data forwarding if any for S1 based handover), based on its own MIM
configuration, the target eNB configures (add/modify/delete) other measurements
compared to the source eNB configuration (not for handover triggering purposes). The
target eNB takes into account the configuration resulting from the measurement
update done in the handover message (as explained in the previous paragraph) and
updates it using a separate RRC procedure.
Note: The description above only applies to event-based UE measurements.
Page 66/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 10: Measurement update upon handover inter-eNB handover

Intra-eNB handover
In case of intra-eNB handover, the measurements are re-configured only if the
configuration of the target cell is different than the source cell.
Page 67/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 11: Measurement update upon handover intra-eNB handover

If the measurement MIM configuration is different in the target cell compared to the
source cell the eNB updates the measurement triggering the handover procedure by
including the Measurement Configuration parameters in the RRC CONNECTION
RECONFIGURATION message transmitted to the UE.
In the handover message, the configuration of any measurement not matching the
target cell configuration for handover trigger (i.e. same MeasId, same
MeasObjectEUTRA, and same ReportConfigEUTRA) is handled as follows:
-
Source ReportConfigEUTRA is kept in the UE,
Source MeasObjectEUTRA is deleted. In 3GPP RRC only one MeasObject

per frequency is supported in the UE. In TLA2.0 only one frequency is
supported.
Source MeasId is kept in the UE.
After the handover procedure is completed, based on MIM configuration, the eNB
configures (add/modify/delete) other measurements compared to the source cell
configuration (not for handover triggering purposes) after the handover procedure is
completed. The eNB takes into account the configuration resulting from the
measurement update done in the handover message (as explained in the previous
paragraph) and updates it using a separate RRC procedure.
The measurement configuration fails in the UE, it will initiate RRC Connection Reestablishment.
Rule: Regarding dlEARFCN ( sourceDL-CarrierFreq under AS-Config field

descriptions in the 3GPP36.331) parameter
dlEARFCN (sourceDL-CarrierFreq) is used in the several process: in Reception of
a RRCConnectionReconfiguration including the mobilityControlInformation by the
Page 68/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE (handover); in Inter-RAT mobility, in Handover to E-UTRA, in Reception of the
RRCConnectionReconfiguration by the UE; [R08]
dlEARFCN is always in relationship with ulEARFCN and frequencyBandIndicator;
which are all descripted in [Vol. 3] LTE Air Interface
dlEARFCN: 3GPP 36.331. This parameter configures the RRC IE carrierFreq of

MeasObjectEUTRA IE (sourceDL-CarrierFreq is the 3GPP name of this
parameter)
MeasObjectEUTRA::dlEARFCN
Parameter
dlEARFCN
Object
Enb/0 RrmServices/ UeMeasurementConf/ MeasObject/

MeasObjectEUTRA
Range & Unit
Integer
[0..39649] step=1
Class/Category
C / Fixed
Value
N.A to see the rule just above
Feature
FRS
Note: dlEARFCN = 10 ( f 0, DL - FDL_low ) + NOffs-DL [where FDL_low and NOffs-DL are some
constants which various with E-UTRA Band using for radio. f 0, DL is the central carrier
frequency of the bandwidth.]
measurementBandwidth: 3GPP 36.331. This parameter configures the RRC IE

MeasurementBandwidth used to indicate measurement bandwidth defined by the
parameter Transmission Bandwidth Configuration NRB [3GPP 36.104]. The unit
is blocks.
MeasObjectEUTRA::measurementBandwidth
Parameter
Object
Enb/ RrmServices/ UeMeasurementConf/ MeasObject/

MeasObjectEUTRA
Range & Unit
Enumerate
Class/Category
C / Fixed
Value
O.D (mbw100 for 20MHz bandwidth)
Feature
FRS 96760
Note: Default value for 20 MHz bandwidth is mbw100. MeasurementBandwidth should

not exceed Channel Bandwidth. to see section 4.1.1.3.1
Page 69/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: Regarding offsetFreq parameter

offsetFreq is used in the process Event A3 (Neighbour becomes offset better than
serving) Ofs; [R08]
offsetFreq: 3GPP 36.331. This parameter configures the RRC IE offsetFreq

included in the IE MeasObjectEUTRA . Offset value applicable to the carrier
frequency. If this parameter is absent then the default value is configured in
RRC
MeasObjectEUTRA::offsetFreq
Parameter
offsetFreq
Object

MeasObjectEUTRA
Range & Unit
Enumerate in dB
dB24, spare]
Class/Category
Value
dB0
Feature
FRS 96760
Note:
For
the
same
frequency
measurement,
MeasObjectEUTRA::offsetFreq is used to set both Ofs and Ofn.
value
of
The function of this parameter is to favor or not, HO between some specific

neighboring frequencies.
To see Inequality A3-1 and A3-2 in section 4.1.2.5.3.
4.1.2.5.3 EVENTA3 AND HO MEASUREMENT: ALGORITHM AND

CONFIGURATION
Event A3 (Neighbour becomes offset better than serving) [R08] : The UE shall:
1>
apply inequality A3-1, as specified below, as the entry condition for this event;
1>
apply inequality A3-2, as specified below, as the leaving condition for this
event;[R08]
Page 70/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Inequality A3-1 (Entering condition)
Mn + Ofn + Ocn Hys > Ms + Ofs + Ocs + Off
Inequality A3-2 (Leaving condition)

Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell. Not taking into account any
offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (equals Ofs
for intra-frequency measurements and is included in MeasObjectEUTRA
corresponding to the the frequency of the neighbour cell: offsetFreq).
Ocn is the cell specific offset of the neighbour cell. If not configured zero offset shall
be applied (included in LteNeighboringCellRelation of the serving frequency as
parameter cellIndividualOffset corresponding to the frequency of the neighbour
cell).
Ms is the measurement result of the serving cell, not taking into account any offset.
Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq within
the MeasObjectEUTRA corresponding to the serving frequency).
Ocs is the cell specific offset of the serving cell (included in
LteNeighboringCellRelation of the serving frequency as parameter
cellIndividualOffset), and is set to zero if not configured for the serving cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within
reportConfigEUTRA for this event).
Off is the offset parameter for this event (i.e. eventA3Offset (3GPP name:a3-Offset)
as defined within reportConfigEUTRA for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.
Page 71/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Measurement
eventA3
Mn
off
Mn - Hyst
TimeToTrigger
Ms + Off
hyst
Ms
t
Figure 12 : Parameters in relationship with Event A3: Entering condition
If inequality A3-1 is verified during TimeToTrigger, the HO is trigger.

Note: Please report to section 4.3.1.2 for the parameters definition.
Figure 13 : EventA3 measurments configuration
Page 72/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.1.2.6 NEIGHBOR CELL INFORMATION PROVIDED TO UES IN
CONNECTED MODE
In 3GPP RRC a measurement object is defined as an object on which the UE shall

perform the measurements. For intra-frequency measurements a measurement
object is a single E-UTRA carrier frequency. Associated with this carrier frequency, the
eNB can configure a list of cell specific offsets.
The eNB can configure a list of blacklisted cells, i.e. cells that are not considered in
event evaluation or measurement reporting. Not supported in TLA2.1 drop1.
In TLA2.1.3, neighbour cells can be either configured by the operator or autonomously
discovered by the eNB thanks to ANR function.
Neighbour cells are represented by an LteNeighboringCellRelation MO instance.
A neighbour cell will be included in the neighbor cell list in the measurement object
only in case it has specific (i.e. non-null) specific offset value associated.This value is
provided by qOffsetCell attribute attached to LteNeighboringCellRelation object
class.
If a neighbour cell list is configured in the cell where initial context setup is
performed the eNB will added it (by modifying the Measurement Object) in the RRC
Connection reconfiguration procedure dedicated to measurement configuration
after the initial context setup as specified in section 4.1.2.5.1.
The neighbour cell list may be updated at cell change using the RRC Connection
reconfiguration procedure dedicated to measurement configuration after the
handover as specified in previous section 4.1.2.5.2. It is not updated in the handover
command message.
If this optional parameter is implemented, then, the UE receives from the eNB the list
of the neighbouring; else, the neighbouring list is build by UE himself.
Reminder: in order to understand this algorithm, one needs to understand the roles of
the different parameters of a neighbouring cell :
cellIndex is only used to unambiguously identify a neighbouring cell within a
measurement configuration of a given UE
physCellId permanently identifies a cell in the network (although it is not
guaranteed unique across the network), therefore this is the parameter to test in order
to decide whether a neighbour of source cell and a neighbour of target cell are actually
the same cell
cellIndividualOffset is just a parameter of a given neighbour cell in the
neighbouring of a given cell
Principle: The algorithm compares the cell instances of the old and target
st
configurations in 2 steps (actually 2 loops). The 1 step loops through the old
configuration: instances found identical in the target configuration are unchanged,
nd
instances found different are modified, and instances not found are removed. The 2
Page 73/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
step loops through the target configuration: instances not matched in the previous step
are added.
The algorithm manages in particular the cellIndex values so that:
a neighbouring cell present in both source and target configurations (identified
by it physical cell identity) keeps its cellId
a neighbouring cell present in target configuration but not in source configuration
gets as cellId the lowest available value
The algorithm updates the target cell list by setting the cellIndex values, therefore
targetCellsList is both input and output parameter.
cellIndividualOffset: 3GPP 36.331.This parameter defines the cell individual

offset between the current LteCell and the neighbour cell provided to the UE in
RRC Connected mode for measurement. This parameter shall be present if the
neighbour cell is included in the neighbour cell list to be provided in MeasObject.
In dB.
LteNeighboringCellRelation::cellIndividualOffset
Parameter
cellIndividualOffset
Object
Range & Unit
Enumerate in dB
dB24]
Class/Category
Value
dB0
Feature
FRS 96760,81872
Note: The function of this parameter is to favor or not, HO between some

specific neighboring cells.
Dependencies: For using this parameter,
LteNeighboringCellRelation::noHO to False.
it
is
mandatory
to
set
4.1.2.7 MOBILITY TRIGGER MANAGEMENT

4.1.2.7.1 INTRA-FREQUENCY HANDOVER
If the intra-LTE mobility is enabled (i.e. MIM parameter isIntraFreqMobilityAllowed
set to TRUE in MO ActivationService) then the only trigger for intra-frequency
handover is the reception of an intra-frequency event-triggered RRC
MeasurementReport from the UE. This is true for both X2 based and S1 based
handovers.
Page 74/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: event A3
Only intra-frequency eventA3 is used to trigger an intra-frequency handover.
This could be triggered either on RSRP or RSRQ.
If the eNB receives a MeasurementReport including MeasId configured for intrafrequency mobility trigger then a handover procedure is initiated. The eNB proceeds
with target cell selection as described in 4.1.2.7.3
The eNB behaviour at reception of MeasurementReport including Measurement
Identity not defined as intra-frequency mobility trigger is not in the scope of this
section,.
Parameter with Link service like rrcMeasurementConfId in MO LteCell are
introduce in OAM Volume [Vol. 1] .For example, rrcMeasurementConfId is a link
with a comme back to RrcMeasurementConf (ENBEquipment/0 Enb/1
RrmServices/0 UeMeasurementConf/0 RrcMeasurementConf/0)
4.1.2.7.2 RECEPTION OF A RRCCONNECTION INCLUDING THE

MOBILITY CONTROLINFORMATION BY THE UE
(HANDOVER)
Note 1: The UE should perform the handover as soon as possible following the
reception of the RRC message triggering the handover, which could be before
confirming successful reception (HARQ and ARQ) of this message.
If the RRCConnectionReconfiguration message includes the
mobilityControlInformation and the UE is able to comply with the configuration
included in this message, the UE shall:
1>
stop timer T310, if running;
1>
start timer T304 with the timer value set to t304, as included in the
mobilityControlInformation;
1>
if the CarrierFreq (for exemple earfcn-DL; dlEARFCN 4.1.2.5.2) is included:
2>
consider the target cell to be one on the frequency indicated by the
CarrierFreq (for exemple earfcn-DL; dlEARFCN 4.1.2.5.2) with a physical cell identity
indicated by the targetPhysCellId;
1>
else:
2>
consider the target cell to be one on the current frequency with a
physical cell identity indicated by the targetPhysCellId;
1>
start synchronising to the DL of the target cell;
1>
reset MAC;
1>
re-establish PDCP for all RBs that are established;
Page 75/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
NOTE 2:
The handling of the radio bearers after the successful completion of
the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs
(as well as the associated status reporting), the handling of the SN and the HFN, is
specified in TS 36.323.
1>
re-establish RLC for all RBs that are established;
1>
apply the value of the newUE-Identity as the C-RNTI ;
1>
configure lower layers in accordance with the received
radioResourceConfigCommon;
1>
if the RRCConnectionReconfiguration message includes the
radioResourceConfigDedicated:
2>
perform the radio resource configuration procedure as specified in
[R08] section 5.3.10;
1>
if the keyChangeIndicator received in the securityConfigHO is set to TRUE:
2>
update the KeNB key based on the fresh KASME key taken into use with
the previous successful NAS SMC procedure, as specified in TS 33.401;
1>
else:
2>
update the KeNB key based on the current KeNB or the NH, using the
nextHopChainingCount value indicated in the securityConfigHO, as specified in TS
33.401.
1>
store the nextHopChainingCount value;
1>
if the securityAlgorithmConfig is included in the securityConfigHO:
2>
derive the KRRCint key associated with the integrityProtAlgorithm, as
specified in TS 33.401;
2>
derive the KRRCenc key and the KUPenc key associated with the
cipheringAlgorithm, as specified in TS 33.401;
1>
else:
2>
derive the KRRCint key associated with the current integrity algorithm,
as specified in TS 33.401;
2>
derive the KRRCenc key and the KUPenc key associated with the
current ciphering algorithm, as specified in TS 33.401;
1>
configure lower layers to apply the integrity protection algorithm and the
KRRCint key, i.e. the integrity protection configuration shall be applied to all
subsequent messages received and sent by the UE, including the message used to
indicate the successful completion of the procedure;
1>
configure lower layers to apply the ciphering algorithm, the KRRCenc key and
the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent
messages received and sent by the UE, including the message used to indicate the
successful completion of the procedure;
1>
perform the measurement related actions as specified in [R08] section 5.5.6.1;
1>
if the RRCConnectionReconfiguration message includes the measConfig:
Page 76/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
2>
perform the measurement configuration procedure as specified in
[R08] section 5.5.2;
1>
submit the RRCConnectionReconfigurationComplete message to lower layers
for transmission;
1>
if MAC successfully completes the random access procedure:

2>
stop timer T304;
2>
apply the parts of the configuration that do not require the UE to know
the SFN of the target cell;
2>
apply the parts of the measurement and the radio resource
configuration that require the UE to know the SFN of the target cell (e.g. measurement
gaps, periodic CQI reporting, scheduling request configuration, sounding RS
configuration), if any, upon acquiring the SFN of the target cell;
2>
the procedure ends;
NOTE 3:
The UE is not required to determine the SFN of the target cell by
acquiring system information from that cell before performing RACH access in the
target cell.
t304: This UE timer is started in the UE in connected mode upon reception of

RRCConnectionReconfiguration message including the MobilityControl
Information or reception of MobilityFromEUTRACommand message. At timer
expiry the UE initiates the RRC connection re-establishment procedure. Defined
in
TS
36.331.
Sent
in
MobilityFromEUTRACommand
and
RRCConnectionReconfiguration.
UeTimers::t304
Parameter
t304
Object
Enb/ DedicatedConf/ UeTimers
Range & Unit
Enumerate in ms
[Timer100MS, Timer200MS, Timer500MS, Timer1000MS,
Timer2000MS, Timer4000MS, Timer8000MS]
Class/Category
C / Fixed
Value
Timer2000MS
Feature
FRS 96760
Involved in defense mechanism of intra frequency intra eNB handover procedure.

Involved in target eNB, Handover preparation phase.
Involved in S1 reset, when target eNB receives the S1-AP RESET.
Page 77/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.1.2.7.3 TARGET CELL SELECTION

When the eNB receives a MEASUREMENT REPORT triggering a handover as
specified in section 4.1.2.7.1 it will proceed with the selection of the target cell as
follows.
The radio cell identity of the target cell selected by the eNB is the PhysicalCellIdentity
of the best cell (i.e. first in the list) reported by the UE in the IE
neighbouringMeasResults. MeasResultListEUTRA list.
It should be noted that according to 3GPP RRC if in the configuration of the reporting
of this measurement for E-UTRA the reportQuantity was set as both the UE will
include the E-UTRA cells in order of decreasing triggerQuantity, i.e. the best cell is
included first; else the UE will include the cells in order of decreasing reportQuantity,
i.e. the best cell is included first.
The measured results included by the UE in measResultEUTRA are not taken in
account to select the target cell.
The PhysicalCellIdentity reported by the UE corresponds to a radio cell identity. The
radio cell identity is computed from physical-layer cell-identity group and physical-layer
identity within the physical-layer cell-identity group (i.e. Cell_Identity = 3*
Cell_Identity_Group + Identity_within_Group as specified in 3GPP 36.211
section 6.11) resulting in an integer value (0..503).
The eNB will determine the target cell as follows:
-
via MIM configuration each cell has configured a list of neighbours cells (i.e.
instances of LteNeighboringCellRelation MO under the MO LteCell). These
neighbour cells can be either local cells (served by the same eNB than the current
cell) or distant ones (served by another eNB). This can be easily determined
based on ECGI, which contains eNB Global Identity of cell serving eNB.
Please note that even if all learnt from the MIM, some of these neighbour cells
may have been previously discovered by ANR function.
Each neighbor cell has a radio identity derived using a similar computation as the
UE (i.e. using the MIM Parameters physicalLayerCellIdentityGroupIndex and
physicalLayerIdentityIndex under LteNeighboringCellRelation MO instance)
If the eNB finds a neighbour cell having a radio identity derived as above which
equals the Cell Identity reported by the UE and handover is allowed towards this
neighbour cell, then it is selected as Target cell.
Handover is allowed in case noHO attribute attached
LteNeighboringCellRelation MO instance is set to false.
to
matching
If the target cell is under the same eNB then an intra-eNB handover procedure is
triggered and the eNB will proceed as specified in section 4.1.2.2
If the target cell is under a different eNB the eNB will determine which type of
handover is required . In case of X2 handover, the eNB will determine the X2
Page 78/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
interface corresponding to this target cell via the MIM configuration by using the
parameter x2AccessId under MO LteNeighboringCellRelation (to see [Vol. 5]
Call Management: X2 Setup). This parameter points to the corresponding instance
of the MO X2Access. An inter-eNB handover procedure is triggered and the eNB
proceeds as specified in section 4.1.2.3. In case of S1 handover, the eNB will use
the S1-MME interface currently used to serve the UE to trigger the handover
preparation.
-
In case:
- There is no X2 interface configured (x2AccessId does not refer to any
existing X2Access instance)
- Or the X2 interface is not available (X2Access operational state equal to
disabled)
- Or the X2 interface cannot be used for mobility procedure (X2Access::
noX2HO attribute set to true)
Then a S1 handover procedures is performed (see clause 4.1.2.4)
If handover is not allowed toward the reported cell, then the handover procedure
is aborted in the eNB and the UE call context is returned to the state before the
handover trigger was received.
noHO
:
This
flag
allows
or
LteNeighboringCellRelation for HO.
forbids
eNodeB
to
use
the
LteNeighboringCellRelation::noHO
Parameter
noHO
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / Fixed
Value
False
Feature
81872
Note: Introduced with the ANR feature. (81872 is the ANR feature), Setting noHO to
true is meaning that no incoming HO is allowed.
Page 79/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
noX2HO : This flag allows or forbids eNodeB to use X2 link for HO. The permitted
values are true and false. The default value is false.
X2Access::noX2HO
Parameter
noX2HO
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / Fixed
Value
false
Feature
81872
relativeCellIdentity: The relativeCellIdentity associated with the macroEnbId

allows to uniquely identify a cell within E-UTRAN. This parameter corresponds to
the 8 rightmost bits of E-UTRAN Cell Identifier in TS 36.423 9.2.14 ECGI.
LteNeighboringCellRelation::relativeCellIdentity
Parameter
relativeCellIdentity
Object
Range & Unit
BitString
stringMinLength = 8
Maxlength = 8
Class/Category
Value
Feature
N.A1 / Fixed
O.D. (set by ANR function or by operator)
81872
This parameter exists also under Enb MO - please see [Vol. 5] Call P for more
explanations.
Setting by ANR if ANR feature in implemented.
LA1.1 - LA2.0 : relativeCellIdentity & macroEnbId

The object of both parameters is RemoteLteCell in TLA2.0
Page 80/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
macroEnbId : TS 36.423 9.2.22 Global eNB ID of the neighbouring eNodeB. This

parameter corresponds to the 20 leftmost bits of E-UTRAN Cell Identifier in TS
36.423 9.2.14 ECGI.
LteNeighboringCellRelation::macroEnbId
Parameter
macroEnbId
Object
Range & Unit
BitString
Maxlength = 20
Class/Category
Value
Feature
N.A1 / Fixed
81872
This parameter exists also under Enb MO - please see [Vol. 5] Call P for more
explanations.
Setting by ANR if ANR feature in implemented.
For both parameters below existing also under MO LteCell you can see [Vol. 5] Call
Management with explanations.
1 Class does not apply to an internal XMS parameter such as this one, because changing its value
does not directly affect the state of the associated NodeB state.
Page 81/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
physicalLayerCellIdentityGroupIndex: The physical layer cell identity group as

N (1)
specified by 36.211, Chapter 6.11. ID secondary synchronization signal
LteNeighboringCellRelation::physicalLayerCellIdentityGroupIndex
Parameter
physicalLayerCellIdentityGroupIndex
Object
Range & Unit
Integer
[0..167]
Class/Category
Value
Feature
C / Fixed
O.D.(set by ANR function or by operator)
81872
physicalLayerCellIdentityIndex : The physical layer cell identity group member

N (2)
index as specified by 36.211, Chapter 6.11. ID primary synchronization
signal
LteNeighboringCellRelation::physicalLayerCellIdentityIndex
Parameter
physicalLayerCellIdentityIndex
Object
Range & Unit
Integer
[0..2]
Class/Category
Value
Feature
C / Fixed
81872
The previous name of the physicalLayerCellIdentityIndex was

physicalLayerCellIdentityGroupMemberIndex in LA0.x
The physical layer cell identity group as specified by 36.211, Chapter 6.11. A physicallayer cell identity is uniquely defined by a number in the range of 0 to 167,
representing the physical-layer cell-identity group, and a number in the range of 0 to 2,
representing the physical-layer identity within the physical-layer cell-identity group.
plmnMobileCountryCode: value identifying the country covered and helpfull to
identify ECGI (Evolved Cell Global Identifier) defining the globally unique identity of
a cell in E-UTRAN. To see [Vol. 5]
Page 82/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
LteNeighboringCellRelation::plmnMobileCountryCode
Parameter
plmnMobileCountryCode
Object
Range & Unit
BcdString
stringMinLength = 3
string Length = 3
Class/Category
N.A1 / Fixed
Value
Feature
FRS 81872
plmnMobileNetworkCode : value identifying the operator covered and helpfull to

identify ECGI (Evolved Cell Global Identifier) defining the globally unique identity of
a cell in E-UTRAN. To see [Vol. 5]
LteNeighboringCellRelation::plmnMobileNetworkCode
Parameter
plmnMobileNetworkCode
Object
Range & Unit
BcdString
stringMinLength = 2
string Length = 3
Class/Category
N.A1 / Fixed
Value
Feature
FRS 81872
If the eNB does not find any neighbor cell configured with a radio identity equal to
the Cell Identity reported by the UE then the handover procedures is aborted in
the eNB and the UE call context is returned to the state before the handover
trigger was received.
Please not that in this case, if ANR function is activated, received measurement
may be used to automatically discover and configure a new neighbour relation.
The MIM model is described in the next figure including hierarchy and associations
(pointers) of the MOs. Note that S1 handover can still be triggered even if the
X2Access MO does not exsit for neighbor cells reported by the UE.
Page 83/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 14:: LTE cell/eNB neighborhood MIM model TLA2.1
4.1.2.7.4 HANDOVER TYPE SELECTION

With the introduction of the S1 handover feature, the eNB now needs to decide
whether X2 or S1-based handover needs to be triggered. In LA2.1, the eNB logic is
based on a simple principle: S1-based handover should be triggered when X2based handover cant be used. In addition to this simple rule, the operator is
allowed to favor S1 handovers over X2-based through a configuration parameter (the
noX2HO flag introduced by the ANR feature ). In summary, the following scenarios
will lead to the S1 handover being triggered (each of these is further detailed below):
There is no X2-C interface setup towards target eNB, or the X2-C interface is
not available (e.g. SCTP down);
Target eNB is not connected to the serving MME (based on GU Group ID);
Target eNB rejected X2 HO Request with appropriate cause (invalid MME

Group ID);
Configuration data indicates preference for S1 Handover over X2 Handover

(noX2HO flag introduced by ANR);
If S1 handover is selected but the MmeAccess corresponding to the UEs serving

MME is disabled, S1 handover is not performed.
4.1.2.7.4.1
X2-C INTERFACE NOT AVAILABLE
The X2-based handover cannot be triggered when there is no X2 interface available

between the two eNBs. This could be because the X2 interface has not been setup at
X2-AP level, or because the SCTP connection between the two eNBs is down.
Page 84/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Instead of wasting precious time trying to setup the X2 interface, the eNB will use the
S1-based handover assuming it has enough information to trigger it (i.e. global eNB
ID and TAI). This should be the first check performed by the source eNB when
deciding on X2 vs S1-based HO. Other checks/conditions are only relevant if the X2
interface is present and operational.
The above implies that when the ANR feature is activated, the eNB need not wait for
the retrieval of a neighbouring eNBs transport address or the establishment of the X2
interface before triggering the S1 handover.
Note that if there is no X2Access corresponding to the neighbor cell reported by the
UE, the eNB will trigger S1-based handover using default values for parameters
related to the X2Access object required for S1 Handover:
directFwdPathAvailability = False, refer to section 4.1.2.4.3
S1HoTimersConf is the first available S1HoTimersConf object. Refer to section
4.1.2.4.3.
4.1.2.7.5 TARGET ENB NOT CONNECTED TO SERVING MME

MME relocation cannot be achieved using the X2 handover procedure. This is the
way the X2 handover procedure has been standardized in 3GPP. Thus, in order for
an X2 handover to succeed, or to have the possibility of succeeding, the target eNB
must be connected to the MME currently serving the UE.
Upon making a handover decision, the eNB should know if the potential target eNB is
connected to the same MME pool as the current serving MME, through the GU Group
Id List provided by this potential target eNB. If the potential target is connected to the
same MME pool as the serving MME, then it is necessarily connected to that serving
MME (since the eNB needs to be connected to all the MMEs in the MME pool).
This is depicted in the figure below.
Page 85/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
MME Group ID=
mmegi No.1
MME Group ID=

mmegi No.2
MME code=
mmec #A
MME code=
mmec #B
MME code=
mmec #A
MME Access Instance No.0
one MME group =

one MME pool
-C
S1
me
1-m
=S
MME Pool Area 1

MME Pool Area 2
X2
eNB1
X2
eNB2
eNB3
Overlapping pool
area
Figure 15 : MME pools Handover type decision

The figure shows that an X2 handover can be achieved from eNB1 to eNB2 because
both eNBs are connected to the same MME (MME instance #0). An X2 handover
between eNB1 and eNB3 (assuming there was an X2 interface that connected them)
would not be possible since they are not connected to a common MME (they are
connected to separate pools).
The possibility of performing an X2 handover from eNB2 to eNB1 will depend on the
MME selected by eNB2 for the UE:
If eNB2 selected MME instance #1 or MME instance #2, then X2 HO cannot be
performed towards eNB1 since eNB1 is not connected to MME Group 2.
If eNB2 selected MME #0, then X2 HO can be performed towards eNB1 since it is
connected to MME Group 1 and thus no MME relocation is required.
Consequently, by checking if the potential target is connected to the same MME pool
as the serving MME, the eNB can know in advance that a X2 Handover will fail. In
order to avoid the un-necessary request, the eNB should avoid triggering the X2
handover to an eNB that is not connected to the UEs serving MME. The eNB will
trigger an S1 Handover when the potential target is not connected to the same MME
as the UEs serving MME.
Upon receiving an A3 measurement report for mobility, the eNB shall check if the
potential target eNB is connected to the same MME pool as the UEs serving MME.
The eNB shall not trigger an inter-eNB X2 Handover to an eNB that is not connected
Page 86/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
to the same MME pool as the UEs serving MME. This is determined using the GU
Group Id information exchanged over X2 between eNBs. Instead, the source eNB
shall trigger an S1 handover procedure.
When triggering an X2 Handover, the source eNB needs to include the serving
MMEs GUMMEI in the X2 HO Request. Since an MME can have multiple GUMMEIs
and that any of these GUMMEI can be used to trigger mobility (see R3-090998), the
eNB could any GUMMEI in the list provided by the MME to populate the GUMMEI
field in the X2 HO Request. For consistency, the source eNB should use one of the
LTE GUMMEIs stored by the eNB, but exactly which GUMMEI is left to
implementation.
Since the eNB might not have the GU Group Id List from the potential target eNB
upon triggering the handover (because X2 Setup might occur before S1 Setup), the
eNB might not have the MME pooling information it requires to know if that target eNB
is connected to the same MME as the UEs serving MME. It is preferable to trigger
the S1 handover in this case instead of risking an X2 handover failure.
4.1.2.7.5.1
X2 HANDOVER REJECTED WITH APPROPRIATE CAUSE
Another case for which S1 handover needs to be triggered when the X2 interface is
available is when the target eNB rejects the X2-based handover request with the
proper cause. A detailed study of the reject causes in TS36.423 shows that most
causes are linked to the cell or eNB not be able to accept the UE, in which case the
S1 handover will not be triggered. There may be cases when the target eNB
indicates that it is not connected to the GUMMEI indicated in the X2 HO REQUEST
(through the cause Invalid MME Group Id in the X2-AP HANDOVER
PREPARATION FAILURE). This might happen if the GU Group ID List information
has not been updated recently by the target eNB.
Note: as per feature 97982 Support for MME Group, the TLA2.1 eNB is expected to
transfer any new GUMMEI related information it receives over S1-AP over the X2-AP
as soon as it receives it.
Here is a recap of the failure causes that the source eNB could receive from the
target eNB in the X2-AP HANDOVER PREPARATION FAILURE, and the associated
behavior in TLA2.1:
Failure cause
TLA2.1 eNB behavior
HO Target not allowed
Same as TLA2.0 (HO is aborted)
No radio resources available inSame as TLA2.0 (HO is aborted)
target cell
Invalid MME Group ID
Trigger S1 handover
Unknown MME Code
Same as TLA2.0 (HO is aborted) *
Encryption And/Or Integrity
Abort HO
Protection Algorithms Not
Supported
Unspecified
Same as TLA2.0 (HO is aborted)
Transport resources unavailable Abort HO **
Cell not available
Same as TLA2.0(HO is aborted)
Page 87/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
* As per [R13], the unknown MME Code cause should be used by the eNB if the
eNB belongs to the same pool area of the source eNB and recognizes the MME
Group ID, but the MME Code is unknown to the target eNB. This is seen as a rare
and transient scenario. Triggering S1 handover would not help in this case.
Restriction: Regarding TLA2.1

** This cause is currently not used by the ALU eNB, but it may be used by another
eNB when the S1 transport ressources are not available over S1 (e.g. SCTP is
down). In this case, S1 handover could succeed if the MME was to trigger an MME
relocation within the MME pool. This is not supported by the ALU MME in the LA2.0
timeframe, but could be supported by another MME. Due to the unlikelyhood of this
scenario in TLA2.1, handover will be aborted.
4.1.2.7.5.2
SELECTION OF S1 HANDOVER OR X2 HANDOVER BASED ON

CONFIGURATION
If both S1 handover and X2 handover are supported between two eNB, whether to
perform S1 handover or X2 handover should base on network configuration. The
general rule is to select the one with shorter round trip time (RTT).
If direct X2 link exists between the two eNB, X2 handover should always be favored.
However, if the X2 link between two eNB is not a direct link but is the one through
routing, the X2 handover RTT could be longer than S1 handover RTT. With this type
of X2 configuration, case by case study should be performed to determine whether X2
handover or S1 handover should be used as the handover type between the two eNB.
If it is determined to use S1 handover, operator can set 'noX2HO' to 'True' between
the two eNB and so S1 handover will be used. However, even if 'noX2HO' is set to
'False' (X2 handover is favored), X2 handover can be used for a call only if the target
eNB is connected to the serving MME of the call.
Operator can also set 'noX2HO' to 'True' if X2 link does not exist between two eNB.
4.2 INTER-FREQUENCY MOBILITY FOR LTE

4.2.1 RRC IDLE MODE MOBILITY
Cell Reselection is a procedure launched by the UE in Idle Mode to determine which
LTE cell to camp on. The trigger can be internal (e.g. periodic trigger to ensure that
UE is still on the best cell) or external (e.g. upon change of Cell Reselection
parameters broadcast on the selected cells BCH).
In RRC_IDLE state, the UE can perform inter-frequency cell re-selection according to
information provided in SIB3 and SIB5.
Page 88/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.2.1.1 CELL RESELECTION ACTIVATION
the parameter below is in the scope of mobility activation and information options. Be
careful, it is mandatory to activate them, for mobility related to. Its Fixed
category and C class parameters:
ActivationService:: isCellReselectionToInterFreqAllowed
Parameter
isCellReselectionToInterFreqAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
false
Feature
103792
This parameter is an activation flag to enable or disable inter-freq cell reselection.

4.2.1.2 SYSTEM INFORMATION BLOCK TYPE5

E-UTRA inter-frequency cell reselection parameters rely on the broadcast of
SystemInformationBlockType5 IE read from the serving cell.
The IE SystemInformationBlockType5 contains information relevant only for EUTRAN inter-frequency cell reselection. The IE includes cell reselection parameters
common for a frequency as well as cell specific reselection parameters.
When there is modification in SIB5-related class C parameters, and isDSIMallowed is
TRUE, eNB triggers DSIM procedure.
Note: DSIM can also be triggered in other cases such as SIBx parameter changed, or
cell barred. SIB5 should always be constructed during DSIM.
SIB5 mapping information is included in SIB1 and scheduled and
broadcasted to UE.
4.2.1.3 CELL RESELECTION ALGORITHM DESCRIPTION

The S criterion is again used to select the good cells for cell reselection, but with the
SIB5 parameters.
4.2.1.3.1 CELL SELECTION CRITERION

The cell selection criterion S (Calculated by the UE) is fulfilled when:
Page 89/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Srxlev > 0
Where:

Where:
See cell reselection criteria parameters in secton 4.1.1.3.1.
In order to further restrict the amount of measurement carried out by the UE in RRCIdle mode, the following rules are used by the UE:
Snonintrasearch : This parameter specifies the threshold (in dB) for inter frequency and
inter-RAT measurements. MIM parameter name is sNonIntrasearch
If SServingCell > Snonintrasearch, UE may choose not to perform measurements of inter-RAT
frequency cells of equal or lower cellReselectionPriority
If SServingCell <= Snonintrasearch, or if sNonIntrasearch is not sent in
SystemInformationBlockType3 in the serving cell, The UE shall perform
measurements of inter-RAT frequency cells of equal or lower cellReselectionPriority
qRxLevMin : 3GPP 36.331 This parameter configures the min required RSRP
level used by the UE in cell reselection on the frequency Carrier.The value sent
over the RRC interface is half the value configured (the UE then multiplies the
received value by 2). Broadcast in SystemInformationBlockType1
CellReselectionConfInterFreq::qRxLevMin
Parameter
qRxLevMin
Object
CellReselectionConfInterFreq
Range & Unit
Integer dBm
Class/Category
Value
-70
Feature
Parameter qRxLevMin in [R14]. Actual value Qrxlevmin = IE value*2
[dBm].
Specifies the minimum required Rx RSRP level in the cell. (Where IE value specify the
message value send to the UE)
Changing this value will affect cell size in terms of re-selection area. Increasing this
value will lead the mobile to start cell-selection/re-selection procedure sooner and then
will artificially decrease cell size in idle mode.
Page 90/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
sNonIntraSearch: Threshold for serving cell reception level under which the UE
shall trigger inter-frequency and inter-RAT measurements for cell reselection.
The value sent over the RRC interface is half the value configured (the UE then
multiplies the received value by 2). For more details consult TS36.304. Defined
in TS 36.331. Broadcast in SystemInformationBlockType3
CellSelectionReselectionConf::sNonIntraSearch
Parameter
sNonIntraSearch
Object
CellSelectionReselectionConf
Range & Unit
dB
[0..62] step = 2
Class/Category
C / Optimization Individual
Value
Feature
96760
measurementBandwidth: Expressed in number of resource blocks. Also referred

to as Transmission Bandwidth Configuration NRB in TS 36.101. Defined in TS
36.331. Broadcast in SystemInformationBlockType3
LteNeighboringFreqConf::measurementBandwidth
Parameter
Object
LteNeighboringFreqConf
Range & Unit
Enumerate
Class/Category
C / Fixed
Value
mbw100
Feature
103789103791
Note: Default value for 20 MHz bandwidth is mbw100.
4.2.1.3.2 EQUAL PRIORITY INTER-FREQUENCY CELL

RESELECTION CRITERIA
To see section 4.1.1.3.1 for the reselection criteria in detail .
Page 91/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
cellReselectionPriority : Relative priority for cell reselection (0 means lowest

priority). Defined in TS 36.331. Broadcast in SystemInformationBlockType5
CellReselectionConfInterFreq:: cellReselectionPriority
Parameter
cellReselectionPriority
Object
Range & Unit
Integer
Class/Category
C/ Optimization- Tuning
Value
Feature
offsetFreq : 3GPP 36.331. This parameter configures the RRC IE q-OffsetFreq

included in the SIB5. Offset value applicable to the carrier frequency
CellReselectionConfInterFreq:: offsetFreq
Parameter
offsetFreq
Object
Range & Unit
Enumerate
Class/Category
C / Optimization- Tuning
Value
dB0
Feature
PriorityofFreq : This attribute is used by the Algorithm for Control Procedure for
Mobility (inter-freq chosen for the blind redirection)
LteNeighboringFreqConf:: priorityOfFreq
Parameter
priorityOfFreq
Object
Range & Unit
Integer
Class/Category
C /Optimization- Selection
Value
Feature
Page 92/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.2.1.3.3 E-UTRAN INTER-FREQUENCY CELL RESELECTION
CRITERIA
The inter-frequency cell reselection criteria is defined in section 6.1.3.4

If more than one cell meets the above criteria, the UE shall reselect a cell ranked
as the best cell among the cells meeting the criteria on the highest priority
frequencies or the highest priority RAT if the highest priority RAT is E-UTRA according
to criteria defined in 4.1.1.3 or in [R14] section 5.2.4.6.
threshXHigh : 3GPP 36.331 This parameter configures the IE threshX-High

included in IE SystemInformationBlockType5
CellReselectionConfInterFreq:: threshXHigh
Parameter
threshXHigh
Object
Range & Unit
Integer
Class/Category
Value
20
Feature
threshXLow : 3GPP 36.331 This parameter configures the IE threshX-Low

included in IE SystemInformationBlockType5
CellReselectionConfInterFreq:: threshXLow
Parameter
threshXLow
Object
Range & Unit
Integer
Class/Category
Value
10
Feature
Page 93/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionEUTRAN : This parameter specifies the value of the cell reselection

UE timer in the cell on the indicated EUTRAN frequency. Defined in TS
36.331.Broadcast in SystemInformationBlockType 5
CellReselectionConfInterFreq:: tReselectionEUTRAN
Parameter
tReselectionEUTRAN
Object
Range & Unit
Integer
Class/Category
C / Optimization- Tuning
Value
Feature
This parameter avoids ping pong radio phenomena during the RA-update & idle
mobility.
4.2.2 RRC CONNECTED MODE MOBILITY

4.2.2.1 MOBILITY ACTIVATION
Like in 4.2.1, at the same place in the data model, the parameter below are in the
scope of mobility activation and information options. Be careful, they are mandatory
to activate them, for mobility related to. They are Fixed category and they are C
class parameters:
ActivationService:: isInterFreqHOAllowed
Parameter
isInterFreqHOAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
false
Feature
103792
This parameter is an activation flag to enable or disable inter-freq intra-LTE handover.
Page 94/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ActivationService :: isInterFreqBlindRedirectionAllowed
Parameter
isInterFreqBlindRedirectionAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
false
Feature
103792
This parameter is an activation flag to enable or disable inter-freq intra-LTE blindredirection.
4.2.2.2 INTER-FREQUENCY INTER-ENB HO

4.2.2.2.1 TRIGGER OF HANDOVER
When the measurement report of Inter-frequency-handover-trigger is received, eNB
checks isInterFreqHOAllowed firstly. If the check shows inter-frequency handover is
not supported, the report will be ignored.
If inter-frequency handover is supported, eNB checks trigger type, ignores the
periodical report.
For the measurement report of Inter-frequency-handover-trigger, the target cell
selection algorithm of Intra-frequency handover is used. And now this algorithm (for
both inter-frequency and intra-frequency) should take handover restriction list, if it has
been stored when SIAP/X2AP message is received, into account. In other word, the
cell in restriction list should be filtered out.
Note: only PLMN identity is used to filter the cell.
4.2.2.2.2 INTER-FREQUENCY INTER-ENB X2 HANDOVER

It is the same as section 4.1.2.3
4.2.2.2.3 INTER-FREQUENCY INTER-ENB S1 HANDOVER

It is the same as section 4.1.2.4
Page 95/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.2.2.3 INTER-FREQUENCY MEASUREMENT REPORTING
SETTING
The handover strategy relies entirely on measurement reports from the UE. The UE
reports to the eNB when the handover trigger conditions are met. Upon receipt of the
measurement report the eNB is expected to trigger a handover procedure.
The measurements are setup, modified or deleted in the UE using RRC signalling,
more precisely the RRCConnectionReconfiguration message including the IE
MeasurementConfiguration.
The measurements defined as inter-frequency LTE mobility triggers are configured as
early as possible in the UE. These measurements are identified by a measurement
identity
configured
to
measId
and
the
attribute
MeasurementIdentityConf.measurementPurpose equal to inter-frequency
handover trigger
4.2.2.3.1 MEASUREMENT UPDATE UPON COMPLETION OF

HANDOVER
See section 4.1.2.5.2
dlEARFCN: Inter-frequency Neighbourhood E-UTRA Absolute Radio Frequency

Channel Number for downlink in the cell (DL centre carrier frequency), defined in
TS 36.104 5.4.3.
LteNeighboringFreqConf::dlEARFCN
Parameter
dlEARFCN
Object
Range & Unit
Integer
[0..39649] step=1
Class/Category
C / Fixed
Value
unset
Feature
FRS 103789, 103791
4.2.2.4 MEASUREMENTS CONFIGURATION

These configurations come from instances of object MeasurementIdentityConf
whose attribute measurementPurpose is set to Inter-frequency-handover-trigger. see
this parameter in section 4.1.2.5
Page 96/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.2.2.4.1 MEASUREMENT CONFIGURATION FOR INTER-FREQ
HO
In IE MeasObjectEUTRA, the neighboring cell list contains maximum 32 cells of this
frequency in object LteNeighboringFreqconf.LteNeighboringCellRelation, ranked by
instance index. These cells should have attribute noHO set as FALSE.
The black cell list contains maximum 32 cells of this frequency in object
LteNeighboringFreqconf.LteNeighboringCellRelation, ranked by instance index. These
cells should have attribute noHO set as TRUE.
4.2.2.4.2 MEASUREMENT CONFIGURATION FOR BLIND

REDIRECTION
This configuration comes from instance of object MeasurementIdentityConf whose
attribute measurementPurpose is set to Blind-Redirection-To-Inter-Freq.see this
parameter in section 4.1.2.5.
When the measurement report of Blind-Redirection-To-Inter-Freq is received, and if
isInterFreqBlindRedirectionAllowed is TRUE, eNB sends RRCConnectionRelease
with EUTRA redirection information in IE RedirectedCarrierInfo to UE. The target
EARFCN is the neighboring frequency with the highest priorityOfFreq. If there is more
than one such frequency, select the one has lower instance index.
4.2.2.4.3 MEASUREMENT CONFIGURATION FOR GAP

<1>. for gap setup:
This configuration comes from instances of object MeasurementIdentityConf whose
attribute measurementPurpose is set to Activation-Of-Measurement-Gap.
When the measurement report of Activation -Of-Measurement-Gap is received, eNB
sets up gap for UE.
<2>. for gap release:
This configuration comes from instances of object MeasurementIdentityConf whose
attribute measurementPurpose is set to Deactivation -Of-Measurement-Gap.
When the measurement report of Deactivation-Of-Measurement-Gap is received, eNB
releases gap for UE.
4.2.2.4.4 INTER-FREQUENCY MEASUREMENT AT CALL SETUP

eNB
checks
attribute
isInterFreqBlindRedirectionAllowed
in
object
ActivationService. If it is TRUE, measurement configurations for blind redirection is
constructed and added into the low priority measurement configurations that will be
sent to UE .
Page 97/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
eNB checks attribute isInterFreqHOAllowed in object ActivationService to know if
inter-frequency handover is allowed in eNB; and checks UE capability to know if such
handover is supported by UE. Only when both eNB and UE support this function can
inter-frequency measurement be added into the low priority measurement
configurations that will be sent to UE.
The figure below shows the scenario that all frequencies configured for inter-frequency
handover need gap for measurement.
Page 98/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
eNB
MME
S1AP INITIAL CONTEXT SETUP REQUEST
(optional) UECapabilityEnquiry
UECapabilityInformation (optional)
SecurityModeCommand
SecurityModeComplete
S1AP INITIAL CONTEXT SETUP RESPONSE
Add Blind-Redirection-For-Inter-Freq
Add Activation-Of-Measurement-Gap
MeasurementReport
Corresponding to Activation-Of-Measurement-Gap
Setup gap
Add Inter-frequency-handover-trigger
Add Deactivation-Of-Measurement-Gap
Case 1:
Remove Activation-Of-Measurement-Gap
MeasurementReport
Corresponding to Inter-frequency-handover-trigger
Handover Decision
Case 2:
MeasurementReport
Corresponding to Deactivation-Of-Measurement-Gap
Release gap
Remove Inter-frequency-handover-trigger
Remove Deactivation-Of-Measurement-Gap
Figure 16: Inter-frequency measurement configuration 1

The figure below shows the scenario that some of the frequencies configured for inter-frequency
handover need gap for measurement and others do not need it.
Page 99/266
02.06 / EN
EXTERNAL
LTE/DCL/APP/031549
27 Apr 2011
Volume 6 : Mobility
UE
eNB
MME
(optional) UECapabilityEnquiry
UECapabilityInformation (optional)
SecurityModeCommand
SecurityModeComplete
Add Blind-Redirection-For-Inter-Freq
Add Inter-frequency-handover-trigger of the
frequency that doesnt need gap
Case 1:
MeasurementReport
Handover Decision
Case 2:
MeasurementReport
Corresponding to Activation-Of-Measurement-Gap
Setup gap
Add Inter-frequency-handover-trigger of the
frequency that need gap
Add Deactivation-Of-Measurement-Gap
Case 2.1:
Remove Activation-Of-Measurement-Gap
MeasurementReport
Handover Decision
Case 2.2:
MeasurementReport
Corresponding to Deactivation-Of-Measurement-Gap
Release gap
Remove Inter-frequency-handover-trigger of the
frequency that need gap
Remove Deactivation-Of-Measurement-Gap
Figure 17 : Inter-frequency measurement configuration 2
Page 100/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.3 MEASUREMENTS CONFIGURATION
4.3.1 MEASUREMENT CONFIGURATION MODEL
The MIM model is described in the next figure including hierarchy and associations
(pointers) of the MOs and MOs cardinality.
Figure 18 : Measurement configuration MIM model in TLA2.1
Page 101/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
In each cell, the UE measurements configuration (i.e. the list of one or more
measurement identities and their related measurement configuration parameters) is
provided by the MO RrcMeasurementConf.
Each measurement (i.e. measurement identity and its related configuration
parameters) is defined by one instance of the MO MeasurementIdentityConf.
Each instance of the MeasurementIdentityConf together with associated MOs
ReportConfig and MeasObject form a complete configuration of one RRC
measurement configuration.
One instance of the MO MeasurementIdentityConf is a profile of one RRC
measurement configuration. In the eNB one or more profiles (instances of
MeasurementIdentityConf) could be configured. The profiles are shared in the cells
under the eNB among the measurement configurations (i.e. RrcMeasurementConf).
4.3.1.1 RRCMEASUREMENTCONF
The RrcMeasurementConf contains parameters needed to configure the IEs in the
RRCConnectionReconfiguration.. The MO MeasurementIdentityConf contains the
RRC MeasId and the associations with the MOs ReportConfig and MeasObject
which contains the parameters to configure the RRC ReportConfig and respectively
MeasObject. (to see section 4.1.2.5)
One or more instances of the MO MeasurementIdentityConf can be configured with

the measurementPurpose attribute set to intra-frequency handover trigger.
Only intra-frequency eventA3 is used to trigger an intra-frequency handover.
This could be triggered either on RSRP or RSRQ.
One instance of MeasurementIdentityConf MO can be configured
measurementPurpose attribute set to Automatic-Neighbour-Relation.
with
This type of measurement is only dedicated to ANR function and is not used for call
management.
The eNB could provide or not neighbour list to the UE based on MIM configuration. If
the eNB does NOT provide a neighbour list to the UE, the UE is able to detect on
its own the radio identity of the neighbour cells. The eNB should have via MIM
configuration a mapping between this radio cell id and the associated X2 interface.
TLA2.0-TLA2.1 : measId & measObjectId

In TLA2.0, LA1.0, only is implemented measId in MO MeasurementIdentityConf.
Page 102/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measID do not exist like OAM parameter in TLA2.1, but is broadcasted by the Call
P.
The quantities used to evaluate the triggering condition for the event. The values rsrp
and rsrq correspond to Reference Signal Received Power (RSRP) and Reference
Signal Received Quality (RSRQ) [R08]
filterCoefficientRSRP: [R08]. This parameter configures the RRC IE

filterCoefficientRSRP included in the IE quantityConfigEUTRA in the
MeasurementConfiguration IE.
RrcMeasurementConf::filterCoefficientRSRP
Parameter
filterCoefficientRSRP
Object

RrcMeasurementConf
Range & Unit
Enumerate
[fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15,
fc17, fc19]
Class/Category
Value
Fc4
Feature
FRS 96760
Note: The higher the value of filterCoefficientRSRP, the less likely ping-ponging
occurs between sectors.
Engineering Recommendation: filterCoefficientRSRP
The new recommended value is Fc4.
Page 103/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
filterCoefficientRSRQ :. [R08]. This parameter configures the RRC IE

filterCoefficientRSRQ included in the IE quantityConfigEUTRA in the
MeasurementConfiguration IE.
RrcMeasurementConf::filterCoefficientRSRQ
Parameter
filterCoefficientRSRQ
Object

RrcMeasurementConf
Range & Unit
Enumerate
fc17, fc19]
Class/Category
Value
Fc4
Feature
FRS 96760
Engineering Recommendation: filterCoefficientRSRQ

Must be kept it consistent with filterCoefficientRSRP value, at this moment.
MeasConfig field descriptions

measObjectToRemoveList
List of measurement objects to remove.
measObjectId
Used to identify a measurement object configuration.
measObject
Specifies measurement object configurations for E-UTRA, UTRA, GERAN, or CDMA2000
measurements.
reportConfigToRemoveList
List of measurement reporting configurations to remove.
reportConfigId
Used to identify a measurement reporting configuration.
reportConfig
Specifies measurement reporting configurations for E-UTRA, UTRA, GERAN, or CDMA2000
measurements.
measIdToRemoveList
List of measurement identities to remove.
measGapConfig
Used to setup and release measurement gaps.
s-Measure
Serving cell quality threshold controlling whether or not the UE is required to perform
measurements of intra-frequency, inter-frequency and inter-RAT neighbouring cells. Value 0
indicates to disable s-Measure.
PreRegistrationInfoHRPD
The CDMA2000 HRPD Pre-Registration Information tells the UE if it should pre-register with
the CDMA2000 HRPD network and identifies the Pre-registration zone to the UE.
Page 104/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
MeasConfig field descriptions
timeToTrigger-SF
The timeToTrigger in ReportConfigEUTRA and in ReportConfigInterRAT are multiplied with the
scaling factor applicable for the UEs speed state.
Table 8: MeasConfig information element
measurementIdentityConfIdList : This parameter refers to the instance of

MeasurementIdentityConf MO that must be considered when the UE is handled
on this cell.
RrcMeasurementConf::measurementIdentityConfIdList
Parameter
measurementIdentityConfIdList
Object

RrcMeasurementConf
Range & Unit
ServiceLink
listSizeMin = 1
listSizeMax = 8
Class/Category
C / Fixed
Value
Value is a link, see Engineering Recommendation
Feature
FRS
Rule: Regarding measurementIdentityConfIdList
Warning: Attribute 'measurementIdentityConfIdList' must point to an

existing object
Value should be a List of 32 maximum elements of Link
For be able to link this parameter to MeasurementIdentityConf/1 , you must create
this one and also ReportConfig/1 for example
Engineering Recommendation: measurementIdentityConfIdList

The recommended value for this parameter is the following:
RrmServices/X UeMeasurementConf/Y MeasurementIdentityConf/Z
Page 105/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
sMeasure : 3GPP 36.331. This parameter configures the RRC IE s-Measure

used to define the serving cell quality threshold controlling whether or not the
UE is required to perform measurements of intra-frequency, inter-frequency
and inter-RAT neighbouring cells. Value in dBm.
RrcMeasurementConf::sMeasure
Parameter
sMeasure
Object
Enb/ RrmServices/ UeMeasurementConf/ RrcMeasurementConf
Range & Unit
Enumerate in dBm
[less_than_minus140, minus_x_to_minus_x-1 (x from 140 to 45),
more_than_minus44]
User
Value
-43
Feature
FRS 96760
Rule: Regarding TLA2.1 : sMeasure

Be careful: Subject to modification with field tests trial results. Keep you up to date
regarding the apply value.
E-UTRAN applies the procedure as follows:

to configure at most one measurement identity using a reporting configuration with
the purpose set to reportCGI;[R08] section 5.5.2.1
The UE shall:
1> if the received measConfig includes the measObjectToRemoveList:
2>
perform the measurement object removal procedure as specified in [R08]
section 5.5.2.4;
1> if the received measConfig includes the measObjectToAddModList:
2>
perform the measurement object addition/ modification procedure as specified
in [R08] section 5.5.2.5;
1> if the received measConfig includes the reportConfigToRemoveList:
2>
perform the reporting configuration removal procedure as specified in [R08]
section 5.5.2.6;
1> if the received measConfig includes the reportConfigToAddModList:
2>
perform the reporting configuration addition/ modification procedure as
specified in [R08] section 5.5.2.7;
1> if the received measConfig includes the quantityConfig:
2>
perform the quantity configuration procedure as specified in [R08] section
5.5.2.8 ;
1> if the received measConfig includes the measIdToRemoveList:
Page 106/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
2>
perform the measurement identity removal procedure as specified in [R08]
section 5.5.2.2;
1> if the received measConfig includes the measIdToAddModList:
2>
perform the measurement identity addition/ modification procedure as
specified in [R08] section 5.5.2.3;
1> if the received measConfig includes the measGapConfig:
2>
perform the measurement gap configuration procedure as specified in [R08]
section 5.5.2.9;
1> if the received measConfig includes the s-Measure:
2>
set the parameter s-Measure within VarMeasConfig to the lowest value of the
RSRP ranges indicated by the received value of s-Measure;
1> if the received measConfig includes the preRegistrationInfoHRPD:
2>
forward the preRegistrationInfoHRPD to CDMA2000 upper layers;
1> if the received measConfig includes the speedStatePars:

2>
set the parameter speedStatePars within VarMeasConfig to the received value
of speedStatePars;
4.3.1.2 REPORTCONFIG/REPORTCONFIG EUTRA

The MO MeasurementIdentityConf contains the RRC reportConfigId and
MeasObjectId the associations with the MOs ReportConfig and MeasObject which
contains the parameters to configure the RRC ReportConfig and respectively
MeasObject.
triggerQuantity: 3GPP 36.331. This parameter configures the RRC IE

triggerQuantity
included
in
the
IE
reportConfigEUTRA
in
the
ReportConfigEUTRA::triggerQuantity
Parameter
triggerQuantity
Object
Enb/ RrmServices/ UeMeasurementConf/ ReportConfig/

ReportConfigEUTRA
Range & Unit
Enumerate
[rsrp, rsrq]
Class/Category
C / Fixed
Value
RSRP
Feature
FRS 96760
Rule: Regarding triggerQuantity in TLA2.1

In TLA2.1 like in TLA2.0, for Intra-Frequency Handover Trigger, you can set
Page 107/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RSRP within the instance
ReportConfigEUTRA/1
ReportConfigEUTRA/0 and/or RSRQ within
If both measurements are activated, the measurement which trigger the HO is this
one which is the first to reach the HO criterions
Rule: triggerQuantity
For Automatic-Neighbour-Relation trigger, triggerQuantity can only be set to
rsrp.
For Report-CGI trigger, triggerQuantity is not used but must not be left unset.
reportQuantity: 3GPP 36.331. This parameter configures the RRC IE

reportQuantity
included
in
the
IE
reportConfigEUTRA
in
the
ReportConfigEUTRA::reportQuantity
Parameter
reportQuantity
Object

ReportConfigEUTRA
Range & Unit
Boolean
[sameAsTriggerQuantity, both]
Class/Category
C / Fixed
Value
sameAsTriggerQuantity
Feature
FRS 96760
Rule: reportQuantity
For Intra-Frequency Handover Trigger, reportQuantity should be set to
sameAsTriggerQuantity
For Automatic-Neighbour-Relation trigger, reportQuantity should be set to
sameAsTriggerQuantity.
For Report-CGI trigger, reportQuantity is not used but must not be left unset.
Note: reportQuantity is used in several process: in general in Measurement report
triggering; in Measurement reporting.
For the measId for which the measurement reporting procedure was triggered, the UE
shall set the measResults within the MeasurementReport message as follows: [R08]
section 5.5.5
1>
set the measId to the measurement identity that triggered the measurement
reporting;
Page 108/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1>
set the measResultServCell to include the quantities of serving cell;
1>
if there is at least one applicable neighbouring cell to report:
2>
set the measResultNeighCells to include the best neighbouring cells
up to maxReportCells in accordance with the following:
3>
if the triggerType is set to event:
4>
include the cells included in the cellsTriggeredList as
defined within the VarMeasReportList for this measId;
3>
else:
4>
include the applicable cells for which the new
measurement results became available since the last periodical
reporting or since the measurement was initiated or reset;
NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on
the concerned frequency) depends on the measurement configuration i.e. the
reportInterval. The related performance requirements are specified in TS 36.133 [16].
3>
for each cell that is included in the measResultNeighCells,
include the physCellId;
3>
if the triggerType is set to event; or the purpose is set to
reportStrongestCells or to reportStrongestCellsForSON:
4>
for each included cell, include the layer 3 filtered
measured results in accordance with the reportConfig for this measId,
ordered as follows:
5>
if the measObject associated with this measId
concerns E-UTRA:
6>
set the measResult to include the
quantity(ies) indicated in the reportQuantity within the
concerned reportConfig in order of decreasing
triggerQuantity, i.e. the best cell is included first;
5>
else:
3>
6>
set the measResult to the quantity as
configured for the concerned RAT within the
quantityConfig in order of decreasing quantity, i.e. the
best cell is included first;
else if the purpose is set to reportCGI:
4>
if the mandatory present fields of the cellGlobalId for
the cell indicated by the cellForWhichToReportCGI in the associated
measObject have been obtained:
5>
include the cgi-Info containing all the fields
that have been successfully acquired;
1>
increment the numberOfReportsSent as defined within the VarMeasReportList
for this measId by 1;
1>
stop the periodical reporting timer, if running;
1>
if the numberOfReportsSent as defined within the VarMeasReportList for this
measId is less than the reportAmount as defined within the corresponding
reportConfig for this measId:
Page 109/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
2>
start the periodical reporting timer with the value of reportInterval as
defined within the corresponding reportConfig for this measId;
1>
else:
2>
if the triggerType is set to periodical:

3> remove the entry within the VarMeasReportList for this measId;
3> remove this measId from the measIdList within VarMeasConfig;
1>
if the measured results are for CDMA2000 HRPD:
2>
set the preRegistrationStatusHRPD to the UEs CDMA2000 upper
layers HRPD preRegistrationStatus;
1>
if the measured results are for CDMA2000 1xRTT:

2>
set the preRegistrationStatusHRPD to FALSE;
1>
submit the MeasurementReport message to lower layers for transmission,
upon which the procedure ends;[R08] section 5.5.5
maxReportCells: 3GPP 36.331 [R08]. section 5.5.5 This parameter configures

the RRC IE maxReportCells included in the IE reportConfigEUTRA in the
ReportConfigEUTRA::maxReportCells
Parameter
maxReportCells
Object

ReportConfigEUTRA
Range & Unit
integer
[1..8] step = 1
Class/Category
Value
1 Refer to Engineering Recommendation below
Feature
FRS 96760
This parameter defines the maximum number of cells to be reported in a

measurement report
Page 110/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: maxReportCells
This parameter allows UE to report up to number of maxReportCells neighbor
cells in each MeasurementReport message. UE may include less than
maxReportCells neighbor cells in the MeasurementReport message based on
environment (e.g. how many neighbor cells actually exist) and the settings of other
measurement configuration parameters (e.g. how many neighbor cells are good
enough to trigger the report based on measurement configuration).
For Intra-Frequency-Handover-Trigger, the default value of the corresponding
maxReportCells is set to 1. Setting the parameter to a value greater than 1 will
not be useful in TLA2.1. This is because in the current target cell selection
algorithm, only the best neighbor cell will be considered as the handover target.
The setting of the parameter will need to be updated once more candidate cells
are considered in handover target selection.
For Automatic-Neighbour-Relation trigger, the value of the corresponding
maxReportCells should be set to the maximum value of 8. This is to ensure UE
to report as many new neighbor cells as possible in a short time.
For Report-CGI trigger, maxReportCells is not used but must not be left unset.
Page 111/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ReportConfigEUTRA field descriptions
eventId
Choice of E-UTRA event triggered reporting criteria.
aN-ThresholdM
Threshold to be used in EUTRA measurement report triggering condition for event number
aN. If multiple thresholds are defined for event number aN, the thresholds are differentiated
by M.
a3-Offset
Offset value to be used in EUTRA measurement report triggering condition for event a3. The
actual value is IE value * 0.5 dB.
reportOnLeave
Indicates whether or not the UE shall initiate the measurement reporting procedure when the
leaving condition is met for a cell in cellsTriggeredList, as specified in [R08] section 5.5.4.1.
triggerQuantity
The quantities used to evaluate the triggering condition for the event. The values rsrp and
rsrq correspond to Reference Signal Received Power (RSRP) and Reference Signal
Received Quality (RSRQ), see TS 36.214 [48].
timeToTrigger
Time during which specific criteria for the event needs to be met in order to trigger a
measurement report.
reportQuantity
The quantities to be included in the measurement report. The value both means that both the
rsrp and rsrq quantities are to be included in the measurement report.
maxReportCells
Max number of cells, excluding the serving cell, to include in the measurement report.
reportAmount
Number of measurement reports applicable for triggerType event as well as for triggerType
periodical. In case purpose is set to reportCGI only value 1 applies.
ThresholdEUTRA
For RSRP: RSRP based threshold for event evaluation.
For RSRQ: RSRQ based threshold for event evaluation.
Table 9: ReportConfigEUTRA information element
hysteresis: 3GPP 36.331. This parameter configures the RRC IE hysteresis

included in the IE reportConfigEUTRA in the MeasurementConfiguration IE
This parameter defines the hysteresis used by the UE to trigger an intra-frequency or

blind Inter-RAT event-triggered measurement report.
ReportConfigEUTRA::hysteresis
Parameter
hysteresis
Object

ReportConfigEUTRA
Range & Unit
dB
[0.0..15.0] step = 0.5
Class/Category
Value
2.0 See Engineering Recommendation
Feature
FRS 96760
Note: hysteresis is used in several process: Event A3 (Neighbour becomes offset

better than serving); Event A2 (Serving becomes worse than threshold); The 3GPP
name is Hys in [R08] Event A1 (Serving becomes better than threshold);Event A4
Page 112/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
(Neighbour becomes better than threshold); Event A5 (Serving becomes worse than
threshold1 and neighbour becomes better than threshold2)
Engineering
Recommendation:
hysteresis
triggerQuantity and eventA3offset for Event A3
and
inter-working
with
Tests field trial are shown best results, with the value of hysteresis set to 2.0
regarding RSRP measurements (triggerQuantity set to RSRP), and eventA3offset
set to 0dB. This means the two entry/exit criteria are at 2dB and -2 dB which means
once UE triggers A3 for a neighbor that is 2dB above serving RSRP.
We recommend set hysteresis to 7.5 regarding RSRQ measurements,

(triggerQuantity set to RSRQ).
Engineering
Recommendation:
triggerQuantity for Event A2
hysteresis
and
inter-working
with
Tests field trial are shown best results, with the value of hysteresis set to 3.0
regarding RSRP measurements (triggerQuantity set to RSRP),
We recommend set hysteresis to 7.5 regarding RSRQ measurements,

(triggerQuantity set to RSRQ).
Rule: hysteresis
For Automatic-Neighbour-Relation trigger, hysteresis should be set to the same
value as the hysteresis (corresponding to triggerQuantity = rsrp if it exists;
otherwise, corresponding to triggerQuantity = rspq) used for Intra-frequencyhandover-trigger.
For Report-CGI trigger, hysteresis is not used but must not be left unset.
timeToTrigger : 3GPP 36.331. This parameter configures the RRC IE

TimeToTrigger
included
in
the
IE
reportConfigEUTRA
in
the
This parameter defines the period of time during which the conditions to trigger an
event report have to be satisfied before sending a RRC measurement report in event
triggered mode
timeToTrigger is used in several process: Measurement identity removal;
Measurement identity addition/ modification; Measurement object removal;
Measurement object addition/ modification; Reporting configuration removal;
Reporting configuration addition/ modification; Quantity configuration; in general in
Page 113/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Measurement report triggering; Measurement related actions upon handover
and re-establishment; [R08]
ReportConfigEUTRA::timeToTrigger
Parameter
timeToTrigger
Object

ReportConfigEUTRA
Range & Unit
ms
[0, 10, 20, 40, 64, 80, 100, 128, 160, 200, 256, 320, 640, 1280,
2560, 5120]
Class/Category
Value
100 Refer to Engineering Recommendation and Rule below
Feature
FRS 96760
Rule: timeToTrigger
For Automatic-Neighbour-Relation trigger, timeToTrigger can only be set to the
same value of the timeToTrigger (corresponding to triggerQuantity = rsrp if it
exists; otherwise, corresponding to triggerQuantity = rspq) used for intrafrequency-handover-trigger.
For Report-CGI trigger, timeToTrigger is not used but must not be left unset.
Engineering Recommendation: timeToTrigger for Event A3 or Event A2

Tests field trial are shown best results, with the value of timeToTrigger set to 100
Page 114/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Hysteresis used to tuning HO decision

RSRP
Target Cell
Serving Cell
8
7
6
5
4
3
2
1
0
5
timeToTrigger
10
15
20
reportingInterval
25
30
hysteresis
Time
35
reportAmount: nb of mes.
Figure 19 : Hysteresis used to tuning HO decision, reportAmount = 4
reportInterval: 3GPP 36.331. This parameter configures the RRC IE

reportInterval
included
in
the
IE
reportConfigEUTRA
in
the
ReportConfigEUTRA::reportInterval
Parameter
reportInterval
Object

ReportConfigEUTRA
Range & Unit
Enumerate in ms or min
[ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120,
ms10240, min1, min6, min12, min30, min60]
Class/Category
Value
ms1024 See Engineering Recommendation
Feature
FRS 96760
Page 115/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: reportInterval
For event A3 LTE intra-frequency HO and event A2 LTE to HRPD HO,
recommended value by performace testing team for reportInterval is ms240.
For event A3 Automatic-Neighbour-Relation trigger, the recommended value for
reportInterval is ms1024. For ANR, each PCI measurement report will trigger a
Report-CGI request. Since the Report-CGI procedure has a 1 second supervision
timer (UE has 1 second to report ECGI), the reportInterval is set to ms1024 to
match the supervision timer.
The ReportInterval indicates the interval between periodical reports. The
ReportInterval is applicable if the UE performs periodical reporting (i.e. when
reportAmount exceeds 1), for triggerType event as well as for triggerType
periodical.[R08]
reportAmount: 3GPP 36.331. This parameter configures the RRC IE

reportAmount
included
in
the
IE
reportConfigEUTRA
in
the
reportInterval is used in the process: Measurement reporting [R08] ;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this
2>
start the periodical reporting timer with the value of reportInterval as defined
within the corresponding reportConfig for this measId;[R08]
ReportConfigEUTRA::reportAmount
Parameter
reportAmount
Object

ReportConfigEUTRA
Range & Unit
Enumerate
[r1, r2, r4, r8, r16, r32, r64, infinity]
Class/Category
Value
r1 Refer to Engineering Recommendation below.
Feature
FRS 96760
This parameter configures the number of periodical reports the UE has to transmit
after the event was triggered.
Page 116/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
This parameter informs UE to send up to number of reportAmount duplicated
measurement reports during the interval when the measurement report entering
condition is continuously satisfied.
Engineering Recommendation: reportAmount
For Intra-Frequency-Handover-Trigger Event A3 trigger, the recommended value
of reportAmount is r8
The main reason to set reportAmount to r8 for Intra-Frequency-HandoverTrigger is to increase the handover successful rate when the source cell or the
target cell is congested. In this case, multiple handover triggers may increase the
chance for the handover request to go through. Also, according to standards eNB
can not send HO command until SecurityMode is completed. Setting
reportAmount to r8 in this case will increase the chance for HO command to be
sent.
For Redirection-to-HRPD-via-Event-A2 trigger, the recommended value of
reportAmount is r8.
The reason to set to r8 for Redirection-to-HRPD-via-Event-A2 trigger is similar to
the reason given above for Intra-Frequency-Handover-Trigger. Also, since
Redirection-to-HRPD-via-Event-A2 trigger has lower priority than IntraFrequency-Handover-Trigger, event A2 measurement report will be dropped in
case eNB is processing event A3 LTE intra-frequency handover measurement
report. Setting reportAmount to r8 in this case will increase the chance for the
event A2 measurement report to be processed.
For Automatic-Neighbour-Relation trigger, the value of the corresponding
reportAmount should be set to r4.
The reason to set the reportAmount to r4 is that with ANR feature, one PCI
measurement report will trigger one Report-CGI request. Multiple Report-CGI
requests may increase the chance for a UE to find the ECGI corresponding to a
PCI reported.
For Report-CGI trigger, the value of the corresponding reportAmount must be
set to r1.
4.3.1.3 THRESHOLDS FOR INTER-RAT MOBILITY WITH INTRALTE MEASUREMENTS: BLIND
Page 117/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
triggerTypeEUTRA : This parameter configures the RRC IE triggerType included

in the IE reportConfigEUTRA in the MeasurementConfiguration IE .This
parameter defines the event-triggered type of the intra-frequency measurement ,
of the RRC measurement.
ReportConfigEUTRA::triggerTypeEUTRA
Parameter
triggerTypeEUTRA
Object

ReportConfigEUTRA
Range & Unit
Enumerate
[eventA3, periodicalStrongestCells, eventA2, eventA4,
eventA1, eventA5, periodicalReportCGI]
Class/Category
C / Fixed
Value
eventA3 (Refer to Restriction and Rule below)
Feature
FRS 96760
Restriction: Regarding triggerTypeEUTRA in TLA2.1.3

The following values of are supported for triggerTypeEUTRA: eventA2 (for
Redirection-to-HRPD-via-Event-A2 trigger, Blind-Redirection-To-3GPP-RAT
trigger, Blind-PS-Handover-To-UTRA-TDD trigger, Blind-Redirection-To-3GPPRAT-Or-PS-Handover-To-UTRA-TDD trigger), eventA3 (for intra-frequencyhandover-trigger or for Automatic-Neighbour-Relation trigger), eventA4 (for trial
of Automatic-Neighbour-Relation trigger), eventA5 (for trial of AutomaticNeighbour-Relation trigger) and periodicalReportCGI.
Page 118/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
event
Rule: triggerTypeEUTRA
For Intra-Frequency-Handover-Trigger, triggerTypeEUTRA should be set to
eventA3
For Redirection-to-HRPD-via-Event-A2 trigger, triggerTypeEUTRA should be set
to eventA2
For Automatic-Neighbour-Relation trigger, triggerTypeEUTRA should be set to
eventA3.
For Report-CGI trigger, triggerTypeEUTRA must be set to periodicalReportCGI.
A3Offset: [R08]. This parameter configures the RRC IE a3-Offset included in the IE
reportConfigEUTRA in the MeasurementConfiguration IE. This IE should be present
if the parameter triggerTypeEUTRA is set to eventA3. Otherwise it should be absent.
The value sent over the RRC interface is twice the value configured (the UE then
divides the received value by 2)
ReportConfigEUTRA::eventA3Offset
Parameter
eventA3Offset
Object

ReportConfigEUTRA
Range & Unit
dB
[-15.0..15.0] step = 0.5
Class/Category
Value
2.0 Refer to Engineering Recommendation below
Feature
FRS 96760
Engineering Recommendation: eventA3Offset for Automatic-NeighborRelation Trigger

The value of eventA3Offset ANR used for Automatic-Neighbour-Relation trigger
should be set to a value around 2 dB lower than the value of eventA3Offset HO
used for intra-frequency-handover-trigger.
If
eventA3Offset ANR must be set to a value less than eventA3Offset HO .
Refer to Volume 6 section 4.4.2.1.2 for details on setting of eventA3Offset ANR .
Page 119/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: eventA3Offset for Intra-Frequency-HandoverTrigger
The recommended value for eventA3Offset used for intra-frequency-handovertrigger is 0 dB, in inter-working with ReportConfigEUTRA::hysteresis setting.
Please refer to this latest parameter for more explanations.
thresholdEutraRsrp:. [R08]. This parameter configures the RRC IE Threshold

EUTRA RSRP included in the IE reportConfigEUTRA in the
MeasurementConfiguration IE. This IE should be present if the parameter
triggerTypeEUTRA is set to eventA1, eventA2, eventA4 or eventA5 and
triggerQuantity is set to RSRP. Otherwise it should be absent.
ReportConfigEUTRA::thresholdEutraRsrp
Parameter
thresholdEutraRsrp
Object

ReportConfigEUTRA
Range & Unit
Enumerate in dBm
more_than_minus44]
Class/Category
Value
Refer to Engineering Recommendation below
Feature
FRS 82728
Notes: The default value of this parameter used for event A4 or A5 for ANR purpose is
not available currently. Refer to Notes under ReportConfigEutra::threshold2EutraRsrp.
Engineering Recommendation: thresholdEutraRsrp

This parameter can be set to different value for different purpose. Currently same
value is recommendated for all inter-RAT mobility applications:
For mobility towards UMTS, thresholdEutraRsrp= minus101_to_minus100
For mobility towards GERAN, thresholdEutraRsrp= minus101_to_minus100
minus109_to_minus110 is better if your activation strategy is to keep UE

attached in 4G network longer.
Page 120/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
thresholdEutraRsrq:. [R08]This parameter configures the RRC IE Threshold

EUTRA RSRQ included in the IE reportConfigEUTRA in the
MeasurementConfiguration IE. This IE should be present if the parameter
triggerTypeEUTRA is set to eventA1, eventA2, eventA4 or eventA5 and
triggerQuantity is set to RSRQ. Otherwise it should be absent.
ReportConfigEUTRA::thresholdEutraRsrq
Parameter
thresholdEutraRsrq
Object

ReportConfigEUTRA
Range & Unit
Enumerate in dB
[less_than_minus19dot5, minus19dot5_to_minus19,
minus19_to_minus18dot5, minus18dot5_to_minus18,
more_than_minus3]
Class/Category
Value
N.A
Feature
FRS 82728
Notes: The default value of this parameter used for event A4 or A5 for ANR purpose is
not available currently. Refer to Notes under ReportConfigEutra::threshold2EutraRsrp.
Page 121/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 20 : Redirection towards another RAT or carrier
A2_floor_threshold in the chart

thresholdEutraRsrq threshold.
above
is
thresholdEutraRsrp
or
The UE is established within the serving cell. The intra-LTE intra-frequency

measurements for the monitoring of the serving floor are configured in the UE. The
radio conditions enter bad radio conditions. The ENB receives an intra-frequency
measurement report indicating that the serving radio level is below this floor, the
ENB redirects to another (RAT;carrier) by an inter-frequency or inter-RAT mobility
procedure in a blindly fashion i.e. without measurements on the target (RAT;Carrier)
Page 122/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 21 : Blind and intraFreq Measurements for

redirection towards another RAT or carrier
4.3.1.4 SPEED STATE MEASUREMENTS CONFIGURATION
Parameters working to speed state measurements configuration in case of intra-LTE

mobility, work also to speed state measurements configuration in case of inter-RAT
mobility.
The implementation is similar to the state idle mode: report to section 4.1.1.3.3, but
with the following parameters:
Page 123/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tEvaluation: TS36.331: this parameter contributes to the configuration of the IE

MeasConfig. This parameter configures the IE t-Evaluation included in the IE
MobilityStateParameters. The duration for evaluating criteria to enter mobility
states. Corresponds to TCRmax in TS 36.304. Value in seconds, s30
corresponds to 30 s and so on.
SpeedStateEvalConf::tEvaluation
Parameter
tEvaluation
Object

RrcMeasurementConf/ SpeedDependentConf/
SpeedStateEvalConf
Range & Unit
Enumerate in s
[s30, s60, s120, s180, s240]
Class/Category
C / Fixed
Value
N.A.
Feature
76498

the IE MeasConfig. This parameter configures the IE n-CellChangeHigh included
in the IE MobilityStateParameters. The number of cell changes to enter high
mobility state. Corresponds to NCR_H in TS 36.304.
SpeedStateEvalConf::nCellChangeHigh
Parameter
nCellChangeHigh
Object

SpeedStateEvalConf
Range & Unit
Integer
[1..16] step = 1
Class/Category
Value
N.A
Feature
76498
Page 124/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility

of the IE MeasConfig.This parameter configures the IE n-CellChangeMedium
included in the IE MobilityStateParameters. The number of cell changes to enter
medium mobility state. Corresponds to NCR_M in TS 36.304.
SpeedStateEvalConf::nCellChangeMedium
Parameter
nCellChangeMedium
Object

SpeedStateEvalConf
Range & Unit
Integer
[1..16] step = 1
Class/Category
Value
N.A
Feature
76498
tHystNormal: TS36.331: this parameter contributes to the configuration of the IE

MeasConfig. This parameter configures the IE t-HystNormal included in the IE
MobilityStateParameters. The additional duration for evaluating criteria to enter
normal mobility state. Corresponds to TCRmaxHyst in TS 36.304. Value in
seconds, s30 corresponds to 30 s and so on.
SpeedStateEvalConf::tHystNormal
Parameter
tHystNormal
Object

SpeedStateEvalConf
Range & Unit
Enumerate in s
[s30, s60, s120, s180, s240]
Class/Category
C / Fixed
Value
N.A.
Feature
76498
timeToTriggerSfHigh: TS36.331: this parameter configures the timeToTriggerSF included in the IE MeasConfig. Parameter Speed dependent ScalingFactor
for timeToTrigger. The concerned mobility control related parameter is multiplied
with this factor if the UE is in High Mobility state as defined in TS 36.304. Value
oDot25 corresponds to 0.25, oDot5 corresponds to 0.5 , oDot75 corresponds to
0.75 and so on.
TimeToTriggerConf::timeToTriggerSfHigh
Parameter
timeToTriggerSfHigh
Object

TimeToTriggerConf
Page 125/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Range & Unit
Enumerate
[oDot25, oDot5, oDot75, 1Dot0]
Class/Category
C / Fixed
Value
N.A.
Feature
76498
Status: this mandatory attribute is unset
timeToTriggerSfMedium: TS36.331:
this
parameter
configures
the
timeToTrigger-SF included in the IE MeasConfig. Parameter Speed dependent
ScalingFactor for timeToTrigger. The concerned mobility control related
parameter is multiplied with this factor if the UE is in Medium Mobility state as
defined in TS 36.304. Value oDot25 corresponds to 0.25, oDot5 corresponds to
0.5 , oDot75 corresponds to 0.75 and so on.
TimeToTriggerConf::timeToTriggerSfMedium
Parameter
timeToTriggerSfMedium
Object

TimeToTriggerConf
Range & Unit
Enumerate
Class/Category
C / Fixed
Value
N.A.
Feature
76498
Status: this mandatory attribute is unset
4.4 AUTOMATIC NEIGHBOUR RELATION (ANR)

CONFIGURATION AND OPTIMISATION
4.4.1 ANR OVERVIEW
The Automatic Neighbor Relation (ANR) Configuration and Optimisation feature (FRS
81872) is for the eNB cells to automatically create and update their neighbor relations.
The feature will minimize the need for the manual provisioning of the neighbor
relations by operators. More important, the ANR feature provides more accurate
neighbor relations than the manual method. This is because the neighbor relations
manually provisioned are based on the theoretical analysis. A neighbor cell selected
this way may not necessarily be used as the target candidate for handover. With ANR,
the neighbor relations are created and constantly updated based on the actual
measurement and report from UE. Therefore, for a well implemented ANR feature, the
neighbor relations will only include the neighbor cells that are good target candidates
Page 126/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
for handover. In TLA2.1, ANR will support intra-frequency neighbor relation creation
only.
The ANR feature includes the ANR neighbor relation creation function, the ANR
neighbor relation maintenance function, the ANR synchronization function and
the ANR reset function.
The ANR neighbor relation creation function builds up the neighbor relations by
requesting the UEs to search for neighbor cells (Volume 6 section 4.4.2.1 of LPUG),
or by receiving the neighbor relations from the neighbor eNB (Volume 6 section
4.4.2.2 of LPUG).
The ANR neighbor relation maintenance function (aka garbage collection) deletes
the obsolete neighbor relations and obsolete X2 links (Volume 6 section 4.4.2.5 of
LPUG).
Since the operator can enter the new neighbor relations through XMS or modify the
neighbor relations created by ANR even when ANR is activated, the ANR
synchronization function is needed to provide the automatic synchronization
between eNB and XMS (Volume 6 section 4.4.2.6 of LPUG).
The ANR reset function allows the tester to reset the internal counters and to delete
neighbor relations created by ANR or provisioned by operator so that testing can
restart from the initial status (Volume 6 section 4.4.2.7 of LPUG).
The ANR feature activation (ActivationService::anrEnable) is controlled on per eNB
basis. When ANR is activated, each of its cells can be in one of the three phases
independently, ANR active phase (Volume 6 section 4.4.2.1 of LPUG), ANR
dormant phase (Volume 6 section 4.4.2.4 of LPUG), and ANR wake-up phase
(Volume 6 section 4.4.2.4 of LPUG).
Figure 22 illustrates the ANR phases and when it will transfer from one phase to the
other.
Page 127/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ANR idle
ANR activation &&

(LteCell->anrState ==
notComplete)
ANR
deactivation
ANR activation &&

(LteCell->anrState ==
Complete)
ANR
deactivation
ANR active
phase
ANR
deactivation
(Nb PCI meas > threshold1)

&& (Nb PCI meas w/o unknown
PCI > threshold2)
HO meas report
w/ best PCI
being unknown
ANR dormant
phase
ANR wake-up
phase
HO meas
report w/
best PCI
being
unknown
dormantPhaseTimerForEcgiDiscovery Timeout
Or
ECGI for unknown PCI received
Figure 22 : ANR Phases

ActivationService::anrEnable
Parameter
anrEnable
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / I&C - OMC
Value
False
Feature
81872
This parameter is used to activate/deactivate the ANR feature.
Page 128/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: Configure ANR measurements before setting anrEnable to True
When setting anrEnable to True:
1. Each LteCell instance served by the eNB must add a reference
(through rrcMeasurementconfId attribute) to an instance of
RrcMeasurementConf
that
references
(through
measurementIdentityConfIdList attribute) one and only one instance
of MeasurementIdentityConf with measurementPurpose set to
Automatic-Neighbour-Relation.
2. Each LteCell instance served by the eNB must add a reference
(through rrcMeasurementConfId attribute) to an instance of
RrcMeasurementConf
that
references
(through
measurementIdentityConfIdList
attribute)
an
instance
of
MeasurementIdentityConf with measurementPurpose set to
Report-CGI.
4.4.2 ANR NEIGHBOR RELATION CREATION FUNCTION

4.4.2.1 ANR IN ACTIVE PHASE - DISCOVER NEIGHBOR RELATION
THROUGH UE REPORTING
In Figure 23, Cell A is in eNB A and Cell B is in eNB B.
Cell A
Phy-CID=3
Global-CID =17
Cell B
Phy-CID=5
Global-CID =19
1) report(Phy-CID=5,
strong signal)
3) Report
Global-CID=19
2b) Read BCH()
2) Report Global-CID
Request (Target PhyCID=5)
Figure 23 : Intra-Frequency Neighbor Cell Search

When Cell A is in ANR active phase, eNB A will send ANR measurement
configuration (Volume 6 section 4.4.2.1.2) to all UEs that are in RRC connected state
in Cell A to search for neighbor cells.
Page 129/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1. UE will send a measurement report with Cell Bs PCI when triggered by ANR
measurement configuration.
2. If eNB A does not know the ECGI associated with the reported PCI, it will
direct UE to read from PBCH of Cell B to obtain the ECGI.
3. After UE finds out the ECGI of Cell B, it will report back to eNB A.
UE can detect Cell Bs PCI and makes reference signal measurements directly. Since
the neighbor eNB ID used for X2 link setup is not contained in PCI but in ECGI, eNB A
has to direct the UE to read Cell Bs PBCH for its ECGI if it does not know the ECGI
associated with the PCI. In order for the UE to read PBCH of Cell B, eNB A will force
the UE into DRX cycle (Volume 6 section 4.4.2.1.3 of LPUG).
After ECGI of Cell B is received, if the X2 link does not already exist between eNB A
and eNB B, ANR will attempt to set up the X2 link (Volume 6 section 4.4.2.1.4 of
LPUG). X2 link may already exist if any cell in eNB A already has a neighbor relation
with one or more cells in eNB.
4.4.2.1.1 PARAMETERS INCLUDED IN A NEIGHBOR RELATION

Neighbor relations are used in a cell to route the handover request. When a UE
reports the PCI of a handover target candidate cell, source cell will check the stored
neighbor relations to find out whether the X2 link exists between the source eNB and
the target eNB. If the X2 link exists, and X2 handover is permitted, source eNB will
initiate the X2 handover procedure. If X2 link does not exist, or X2 handover is not
permitted, but S1 handover is possible, S1 handover will be attempted. Otherwise, the
handover request will be discarded.
Some parameters in the neighbor relations are used to build different types of
neighbor lists to be included in SIB or in the RRCConnectionReconfiguration message
to help UE with their neighbor cell search. One example is to use the no handover
neighbors to build the black cell list included in RRCConnectionReconfiguration
message. It is to help UE to avoid the useless measuring and reporting of the black
cells that are forbidden to be used as handover target cells.
A summary is provided below on how ANR will set the parameters in the
LteNeighboringCellRelation MO for an automatically created instance of neighbor
relation:
cellIndividualOffset This parameter is the cell individual offset of the

neighbor cell provided to UE in connected mode to perform measurement
(Volume 6 section 4.1.2.6 of LPUG). It is set to the default value of 0 dB.
discoveredByAnr This parameter indicates whether the neighbor relation

is discovered by ANR. It is set to true.
macroEnbId This parameter is set to the 20 leftmost bits of the E-UTRAN

Cell Identifier contained in the ECGI of the neighbor cell (Volume 6 section
4.1.2.7.3 of LPUG).
noHO This parameter indicates whether handover to the neighbor cell is

permitted. It is set to the default value of false indicting handover is permitted
(Volume 6 section 4.1.2.7.3 of LPUG).
Page 130/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
noRemove This parameter indicates whether the neighbor relation can be

removed by the ANR garbage collection function. It is set to the default value
of false indicating it can be removed by the ANR garbage collection function.
physicalLayerCellIndentityGroupIndex This parameter indicates the

physical layer cell identity group. It is calculated from PCI of the neighbor cell
(Volume 6 section 4.1.2.7.3 of LPUG).
physicalLayerCellIndentityIndex This parameter indicate the physical

layer cell identity. It is calculated from PCI of the neighbor cell (Volume 6
section 4.1.2.7.3 of LPUG).
plmnMobileCountryCode This parameter indicates the Mobile Country

Code (MCC) of the EUTRA system the neighbor cell belong to. It is obtained
from PLMNID of the neighbor cell (Volume 6 section 4.1.2.7.3 of LPUG).
plmnMobileNetworkCode This parameter indicates the Mobile Network

Code (MNC) of the EUTRA system the neighbor cell belongs to. It is obtained
from PLMNID of the neighbor cell (Volume 6 section 4.1.2.7.3 of LPUG).
qOffsetCell This parameter indicates the offset between the serving cell
and the neighbor cell. It is provided to UE in idle mode to perform cell
reselection. This parameter is set to default value of 3 dB (Volume 6 section
4.1.1.3.2 of LPUG).
relativeCellIdentity - This parameter is the rightmost 8 bits of the E-UTRAN

Cell Identifier contained in ECGI of the neighbor cell (Volume 6 section
4.1.2.7.3 of LPUG).
trackingAreaCode TAC is used to identify the tracking area within the

scope of a PLMN. It is reported by UE or received from neighbor eNB through
X2 messages (Volume 6 section 4.1.1.1 of LPUG).
x2AccessId This parameter refers to the instance of X2Access MO that

represents the X2 link to the eNB of the neighbor cell. It is set to X2Access
rdnId of the X2 link.
For a neighbor relation created by ANR, cellIndividualOffset, noHO, noRemove and

qOffsetCell are always set to default values by ANR. It is up to the operator to
change them to non-default values based on different needs.
Page 131/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
LteNeighboringCellRelation::discoveredByAnr
Parameter
discoveredByAnr
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / Fixed
Value
True, if Neighbor Relation is discovered by ANR

False, if Neighbor Relation is provisioned though OMC
Feature
81872
This parameter indicates whether the LteNeighboringCellRelation is created by ANR

or is provisioned by operator.
LteNeighboringCellRelation::noRemove
Parameter
noRemove
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / I&C - OMC
Value
True
Feature
81872
This parameter indicates whether the LteNeighboringCellRelation is allowed to be

removed by the ANR garbage collection function.
Rule: Set noRemove to True when noHO is set to True
If noHO is set to True, the noRemove must also be set to True for the
same LteNeighboringCellRelation instance to make the neighbor relation
belong to the HO black list.
4.4.2.1.2 ANR MEASUREMENT CONFIGURATION

Three events can be used to trigger the UE to send an ANR measurement report.
They are:
Event A3: when the neighbor cell becomes a given offset better than the serving
cell;
Page 132/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Event A4: when the neighbor cell becomes better than a given absolute threshold;
Event A5: when the serving cell becomes worse than a given threshold and the
neighbor cell becomes better than a given absolute threshold2.
At any given time, only one of the above three triggers can be used for ANR
measurement configuration. The selection is made through
ReportConfigEUTRA::triggerTypeEUTRA. Event A3 is recommended for ANR
measurement configuration. Event A4 and Event A5 are also available for trial and
testing.
Event A3, A4 or A5 each has its own entering condition(s) and leaving condition(s) as
listed below. For a selected event, only when the entering conditions are continuously
satisfied for ReportConfigEUTRA::timeToTrigger ms, a UE will send the first
measurement report to the eNB. UE may also be directed to send multiple duplicated
measurement reports (up to ReportConfigEUTRA::reportAmount reports with
interval ReportConfigEUTRA::reportInterval) in the duration when the entering
conditions are continuously satisfied.
Event A3 Entering Condition (for intra-frequency measurement):
Mn - hysteresis > Ms + eventA3Offset
Event A3 Leaving Condition (for intra-frequency measurement):
Mn + hysteresis < Ms + eventA3Offset
Event A4 Entering Condition:
Mn + offsetFreq - hysteresis > thresholdEutraRsrp or thresholdEutraRsrq
Event A4 Leaving Condition:
Mn + offsetFreq + hysteresis < thresholdEutraRsrp or thresholdEutraRsrq
Event A5 Entering Conditions:
Ms + hysteresis < thresholdEutraRsrp or thresholdEutraRsrq and
Mn + offsetFreq hysteresis > threshold2EutraRsrp or threshold2EutraRsrq
Event A5 leaving condition:
Ms hysteresis > thresholdEutraRsrp or thresholdEutraRsrq or
Mn + offsetFreq + hysteresis < threshold2EutraRsrp or threshold2EutraRsrq
Where:
Mn is the measurement result of the neighbor cell.
Ms is the measurement result of the serving cell.
Mn, Ms are in unit of dBm if RSRP is used or dB if RSRQ is used.
offsetFreq is a parameter defined in MeasObjectEUTRA MO. (Volume 6 section
4.1.2.5.2 of LPUG).All other parameters used in the event entering or leaving
inequalities are defined under ReportConfigEUTRA MO.
When ANR feature is activated, an instance of ReportConfigEUTRA MO

corresponding (MeasurementIdentityConf::measurementPurpose = AutomaticNeighbour-Relation) must exist to trigger and control the ANR measurement
reports.The parameters are listed below:
eventA3Offset - This parameter used in Event A3 entering and leaving

conditions. (Volume 6 section 4.3.1.3 of LPUG)
Page 133/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
hysteresis This parameter is used in Event A3, A4 and A5 entering and

leaving conditions (Volume 6 section 4.3.1.2 of LPUG).
threshold2EutraRsrp This parameter is used in Event A5 entering and

leaving conditions if RSRP is used as triggerQuantity.
threshold2EutraRsrq - This parameter is used in Event A5 entering and

leaving conditions if RSRQ is used as triggerQuantity.
thresholdEutraRsrp This parameter is used in Event A4 and Event A5

entering and leaving conditions if RSRP is used as triggerQuantity (Volume
6 section 4.3.1.3 of LPUG).
thresholdEutraRsrq - This parameter is used in Event A4 and Event A5

entering and leaving conditions if RSRQ is used as triggerQuantity (Volume
6 section 4.3.1.3 of LPUG).
timeToTrigger This parameter indicates the time during which the entering
condition(s) for the select event needs to be met in order to trigger a
measurement report (Volume 6 section 4.3.1.2 of LPUG).
triggerQuantity This parameter indicates whether RSRP (Reference Signal

Received Power) or RSRP (Reference signal Received Quality) is used to
evaluate the measurement report triggering condition(s) for the selected event
triggerTypeEUTRA This parameter indicates whether Event A3, Event A4

or Event A5 is selected to trigger the measurement report for ANR purpose.
(Volume 6 section 4.3.1.3 of LPUG)
maxReportCells This parameter indicates the maximum number of

neighbor cells that can be included in the measurement report for ANR
purpose. Default value is not provided (Volume 6 section 4.3.1.2 of LPUG).
reportAmount This parameter indicates the maximum number of times the

UE should send the duplicated measurement reports in each duration that the
entering conditions are satisfied. (Volume 6 section 4.3.1.2 of LPUG).
reportInterval This parameter indicates the time interval between two

measurement report if the reportAmount is set to a value greater than r1
(one time) (Volume 6 section 4.3.1.2 of LPUG).
reportQuantity This parameter indicates whether RSRP, RSRQ of both are

to be included in the measurement report. The default value is set to be the
same as the setting of triggerQuantity (Volume 6 section 4.3.1.2 of LPUG).
When ANR feature is activated, an instance of ReportConfigEUTRA MO

corresponding (MeasurementIdentityConf::measurementPurpose = Report-CGI)
must also exist to support the ECGI search and report. In this instance of
ReportConfigEUTRA MO, only two parameters are used by the system:
triggerTypeEUTRA must be set to periodicalReportCGI and reportAmount must be
set to r1.
To support ANR, two instances of MeasurementIdentityConf MO must also be
added (one for Automatic-Neighbour-Relation and one for Report-CGI) including the
following parameters:
Page 134/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measObjectId This parameter is set to the ID of the MeasObject instance to

be used for Automatic-Neighbour-Relation or for Report-CGI (Volume 6
section 4.1.2.5 of LPUG).
measurementPurpose This parameter is set to Automatic-NeighbourRelation for ANR measurement configuration or Report-CGI for ECGI search
reportConfigId This parameter is set to the ID of the ReportConfigEUTRA

instance to be used for Automatic-Neighbour-Relation or Report-CGI
In TLA2.1, Event A3 is used to trigger the intra-frequency handover measurement

report. It is also recommended to be used to trigger the ANR intra-frequency
measurement report. With Event A3, eventA3Offset is the critical parameter to
ensure the performance of measurement reporting.
For ANR intra-frequency measurement report, Event A3 entering condition is:
Mn hysteresis > Ms + eventA3Offset ANR
(1)
For intra-frequency handover measurement report with target candidate cell not yet
included in the neighbor relations, Event A3 entering condition is:
Mn hysteresis > Ms + eventA3Offset HO

From (1) and (2),
(2)
eventA3Offset ANR should be set to satisfy the following inequality to
meet the ANR performance needs:
eventA3Offset ANR < eventA3Offset HO

Denote
(3)
= eventA3Offset HO eventA3Offset ANR . When is set too low, ANR
tends to miss the target candidate cells during neighbor cell detection. If the missed
neighbor cell is reported as a target candidate cell in the handover measurement
report, the handover request will be discarded. This will degrade the handover
successful rate.
On the other hand, if is set too high. ANR tends to detect and include the cells in
the neighbor relations that will never be used for handover. This will have impact on
the eNB processing load, although the cells that are not used for handover will
become obsolete and will be deleted by garbage collection eventually.
For the above reasons, it is recommended to set value of
eventA3Offset ANR 2 dB
lower than the default value of eventA3Offset HO .
Page 135/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ReportConfigEUTRA::threshold2EutraRsrp
Parameter
threshold2EutraRsrp
Object

ReportConfigEUTRA
Range & Unit
Enumerate in dBm
[less_than_minus140, minus_x_to_minus_x-1 (x from 140 to
45), more_than_minus44]
Class/Category
Value
N.A.
Feature
81872
This parameter is used in the entering and leaving inequalities for Event A5 if RSRP is
used as triggerQuantity.Default value to be used for this parameter is not available
currently.
Notes: For ANR purpose, event A3 is recommended to the customers as the
measurement report trigger. Event A4 and A5 are proposed for testing and trial
purpose only for ANR.
ReportConfigEUTRA::threshold2EutraRsrq
Parameter
threshold2EutraRsrq
Object

ReportConfigEUTRA
Range & Unit
Enumerate in dB
more_than_minus3]
Class/Category
Value
N.A.
Feature
81872
Page 136/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
This parameter is used to set Thresh2Thresh2in the entering and leaving inequalities for
Event A5 if RSRQ or RSRP is used as triggerQuantity. Default value to be used for
this parameter is not available currently.
Notes: The default value of this parameter used for event A5 for ANR purpose is not available
currently. Refer to Notes under ReportConfigEutra::threshold2EutraRsrp.
4.4.2.1.3 DRX CONFIGURATION FOR ECGI RETRIEVING

DRX (Discontinuous Reception) can be configured for a UE in RRC connected state
so that it stops monitoring the downlink PDCCH channel during the DRX period. The
main purpose of DRX is for the UEs to go the sleep (to save battery) after a period of
inactivity when no data was sent or received.
When a UE is configured to Report-CGI (to find ECGI of a neighbor cell), however,
eNB forces UE into DRX through the DRX Command in MAC control element. During
the DRX period in DRX cycle, the UE listens to the PBCH of the neighbor cell to
receive its ECGI, TCA and PLMN ID.
When a UE is forced into DRX, it will cause transmission gap noticeable by the end
user of a voice call or of any other services required guarantee bit rate (GBR). For this
reason, eNB A will direct a UE for ECGI search only if it is capable to support the
reportCGI procedure, and it does not have on going GBR bearers. For the same
reason, DRX length defined drxCycleForReportCGI should be set just long enough for
the UE to listen to PBCH of the neighbor cell to find its ECGI.
AutomaticNeighborRelation::drxCycleForReportCGI
Parameter
drxCycleForReportCGI
Object
Enb/ SelfOrganizingNetwork/ AutomaticNeighbourRelation
Range & Unit
Enumerate
{sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320,
sf512, sf640, sf1024, sf1280, sf2048, sf2560}
Class/Category
C / I&C - OMC
Value
sf160
Feature
81872
This parameter defines the DRX long cycle length that will be used when a UE is
requested to listen to PBCH of a neighbor cell to find its ECGI.
Engineering Recommendation: drxCycleForReportCGI
drxCycleForReportCGI should be configured to ensure the UE has enough time
to read the System Information Block Type 1 in order to retrieve the ECGI of a
neighbor cell. For this purpose,
drxCycleForReportCGI should be set to at least 145ms. sf160 (160ms) is
recommended as the default value for this parameter.
Page 137/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Another parameter, AutomaticNeighborRelation::isLcgRemovalAllowed, can be used
to stop the UE from transmitting UL user data during DRX period. This parameter
indicates whether to include the field of logicalChannelGroup in the drb-ToAddModList
of the RRCConnectionReconfiguration message sent to the UE for report-CGI. If
isLcgRemovalAllowed is set to true, the field of logicalChannelGroup will be omitted
from RRCConnectionReconfiguration and UE will not be scheduled to send UL user
data. This will increase the chance to the UE to obtain the ECGI by reading the PCCH
of the neighbor cell.
AutomaticNeighbourRelation::isLcgRemovalAllowed
Parameter
isLcgRemovalAllowed
Object
AutomaticNeighbourRelation
Range & Unit
Boolean
[false, true]
Class/Category
C / I&C - OMC
Value
true
Feature
81872
Restriction: isLcgRemovalAllowed
In TLA2.1, the setting of this parameter is ignored by system (not supported).
4.4.2.1.4 SET UP X2 LINKS

Once a new PCI is detected and its ECGI is found, ANR on eNB A will automatically
attempt to establish the X2 link to neighbor eNB B if the X2 link does not already exist.
Setting up X2 link is essential to create a neighbor relation. This is because the direct
X2 handover (with X2 link directly connected to two neighboring eNB) provides better
performance than S1 handover in general as S1 handover has to go through SGW
which normally takes much longer time.
There are three steps for this procedure:
1. Automatically retrieve the X2 IP address of the eNB B from MME through S1
procedure
2. Set up SCTP association between eNB A and eNB B (Volume 7 section
4.2.2.2 of LPUG).
3. Establish X2 link between eNB A and eNB B (Volume 7 section 4.2.2.2 of
LPUG).
S1 Procedure to automatically retrieve X2 IP address of a distant eNB is illustrated in
Figure 24:
Page 138/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Messages routed accross one or
several MMEs (use of TAI required)
Local eNB
MME
Distant eNB
eNB CONFIGURATION TRANSFER

(Source Global eNB ID & TAI, Target Global eNB ID & TAI,
SON information request)
MME CONFIGURATION
TRANSFER
If failure, the local eNB may try with
another MME to which it is
connected (possibly of another MME
group)
Local eNB
MME CONFIGURATION TRANSFER

(Source eNB ID & TAI, Target eNB ID & TAI,
SON information reply = 1 or 2 transport address(es) )
eNB CONFIGURATION
TRANSFER
MME
Distant eNB
Figure 24 : S1 Procedure for Neighbor eNB X2 IP Address Retrieval

Local eNB may try up to 3 MME it is connected to with the S1 procedure to retrieve
the X2 IP address of the distant eNB. If local eNB fails to find the X2 IP address of the
distant eNB after retry of the S1 procedure, it will unset the X2 IP address so that
operator may provision it manually if he/she has the information. Refer to Volume 7
section 4.2.2.2 for the X2 IP address parameters
X2TransportLayerAccess::sctpAssocRemAddr or
X2TransportLayerAccess::sctpAssocRemAddrIpv6.
If the X2 IP address is found, eNB A will set up the SCTP association with eNB B and
establish the X2 link (Volume 7 section 4.2.2.2). After X2 link setup procedure is
completed, the parameters in the X2Access object MO are set by ANR as below:
directFwdPathAvailability This parameter indicates whether X2 link to the

neighbor eNB is available and successfully setup. It is set to default value of
true (Volume 6 section 4.1.2.4.3 of LPUG).
macroEnbId - This parameter is set to the 20 leftmost bits of the E-UTRAN

Cell Identifier contained in ECGI of the neighbor cell.
noRemove This parameter indicates whether the X2 link can be removed

by ANR garbage collection function. It is set to default value of false
indicating the X2 link can be removed by ANR garbage collection function.
noX2 This parameter indicates whether X2 link to the neighbor eNB can be
setup. It is set to default value of false indicating X2 link is permitted to be
setup (refer to Volume 5 section 6.2.1 of LPUG).
noX2HO This parameter indicates whether X2 handover is permitted. It is

set to false indicating X2 handover is allowed (refer to Volume 6 section
4.1.2.7.3 of LPUG).
plmnMobileCountryCode - This parameter indicates the Mobile Country

Code (MCC) of the EUTRA system for the neighbor eNB. MNC and MCC are
used to construct the PLMNID of a EUTRA system. ANR obtains this
parameter from PLMNID of the neighbor cell.
Page 139/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
plmnMobileNetworkCode - This parameter indicates the Mobile Network

Code (MNC) of the EUTRA system for the neighbor eNB. MNC and MCC are
used to construct the PLMNID of a EUTRA system. ANR obtains this
parameter from PLMNID of the neighbor cell.
s1HoTimersConfId This parameter is set to the ID of rhw instance of the

S1HoTimersConf MO to be used for this instance of X2Access MO (Volume 2
of LPUG).
X2Access::macroEnbId
Parameter
macroEnbId
Object
Range & Unit
BitString
Maxlength = 20
Class/Category
C / Fixed
Value
Feature
81872
This parameter is the 20 leftmost bits of the neighbour cells E-UTRAN Cell Identifier
contained in its ECGI.
X2Access::noRemove
Parameter
noRemove
Object
Range & Unit
Boolean
[false, true]
Class/Category
C / I&C - OMC
Value
True
Feature
81872
This parameter indicates whether the X2 link can be removed by the ANR garbage
collection function.
Page 140/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: Set noRemove to True when noHO or noX2HO is to True
1. If noX2 is set to True, the noRemove must also be set to True for
the same X2Access instance to make the X2 link belong to the noX2
black list.
2. If noX2HO is set to True, the noRemove must also be set to True
for the same X2Access instance to make the X2 link belong to the HO
black list.
X2Access::plmnMobileCountryCode
Parameter
Object
Range & Unit
BcdString
stringMinLength = 3
stringLength = 3
Class/Category
C / Fixed
Value
Feature
81872
This parameter indicates the Mobile Country Code (MCC) of the EUTRA system the
neighbor cell belongs to. MCC and MNC are used to construct the PLMNID of a
EUTRA system. For a neighbor relation created by ANR, it is obtained from PLMNID
X2Access::plmnMobileNetworkCode
Parameter
Object
Range & Unit
BcdString
stringMinLength = 2
stringLength = 3
Class/Category
C / Fixed
Value
Feature
81872
This parameter indicates the Mobile Country Code (MCC) of the EUTRA system the
neighbor cell belongs to. MCC and MNC are used to construct the PLMNID of a
EUTRA system. For a neighbor relation created by ANR, it is obtained from PLMNID
Page 141/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: X2 interface configuration and management
If ANR is deactivated on two eNBs and an X2 relation needs to be

established between them, it is essential that an instance of object
X2Access corresponding to the peer eNB be generated and populated
appropriately in the configuration of each eNB. If this is done for only one
eNB, the SCTP connection (see [Vol. 7]) may be established but the X2-AP
setup procedure (see [Vol. 5]) will not be successful.
If ANR is activated on two eNBs, the need to establish an X2 relation will

depend on radio measurements (i.e. there is no guarantee that there will be
at least one neighbor relation between a cell hosted by the first eNB and a
cell hosted by the second eNB).
Nevertheless, it is possible to enforce the X2 relation through OAM by
generating an instance of object X2Access corresponding to the peer eNB
in the configuration of one of the two eNBs (it is not essential to do the same
in the configuration of the other eNB, ANR being activated for it is enough
for both the SCTP connection establishment (see [Vol. 7]) and the X2-AP
setup procedure (see [Vol. 5]) to be successful). Note, however, that
parameter X2Access::noRemove must be set to True, otherwise if no
cell-to-cell neighbor relation is created between the 2 eNBs, the X2Access
instance will be removed by ANR.
If ANR is deactivated on some eNB (we will call it eNB1) and activated on
some other eNB (we will call it eNB2), the latter may try to establish an X2
connection but even though the SCTP connection can be established the
subsequent X2-AP setup procedure will fail (the X2-AP setup request
message will be rejected as the eNB1 (ANR deactivated) will have no
X2Access defined for the eNB2 (ANR activated).
Nevertheless, it is possible to enforce an X2 relation between these 2 eNBs
through OAM by generating an instance of object X2Access corresponding
to eNB2 (ANR activated) in the configuration of eNB1 (ANR deactivated). It
is not essential to do the same in the configuration of the eNB2, ANR being
activated is enough for both the SCTP connection establishment (see [Vol.
7]) and the X2-AP setup procedure (see [Vol. 5]) to be successful). Note,
however, that parameter X2Access::noRemove must be set to True,
otherwise if no cell to cell neighbor relation is created between the 2 eNBs,
the X2Access instance will be removed by ANR.
4.4.2.2 RECEIVING NEIGHBOR RELATION THROUGH X2

MESSAGES
Page 142/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ANR will receive neighbor relations from the messages sent by a neighbor eNB
through X2 links either in ANR active phase or in ANR dormant phase. There are
three messages carrying the information of neighbor relations. They are: ENB
CONFIGURATION UPDATE message, X2 SETUP REQUEST message and X2
SETUP RESPONSE message.
ENB CONFIGURATION UPDATE message is sent by an eNB whenever there is a
change in its served cell(s) (add, modify, or delete) or there is a change in its served
cell(s) neighbor list(s) (add, modify, or delete). X2 SETUP REQUEST and X2 SETUP
RESPONSE message are used to set up the X2 links.
All three messages include two types of information lists:
Served cell information list Since the served cells of eNB B (sender of the
messages) are the neighbor cells of eNB A (receiver of the messages), eNB A
will use the served cell information list received from eNB B to update its own
neighbor relation list.
Neighbor cell information list It is the neighbor list of the served cells in eNB
B. eNB A will store the neighbor cell information list received from eNB B for
future use: If the same PCI is later reported to eNB A by a UE, the stored
PCI/ECGI/X2 IP information received from eNB B is ready to be used to
create a new neighbor relation. eNB A will not need to request UE to search
for ECGI in this case.
4.4.2.3 END OF ACTIVE PHASE

Two criteria are used to determine whether the neighbor relations are considered to
be completed and ANR active phase can be ended:
Total number of measurement reports received in the cell during ANR active
phase (excluding the number of measurement reports to report ECGI) is
greater than
AutomaticNeighbourRelation::activePhaseMeasReportThreshold.
Total number of consecutive measurement reports received in the cell during

ANR active phase (excluding the number of measurement reports to report
ECGI) without reporting new PCI is greater than
AutomaticNeighbourRelation::activePhaseMeasReportHysteresis.
AutomaticNeighbourRelation::activePhaseMeasReportHysteresis
Parameter
activePhaseMeasReportHysteresis
Object
Range & Unit
Integer
[5..500] step = 5
Class/Category
C / I&C - OMC
Value
200
Feature
81872
Page 143/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
This parameter defines the minimum number of consecutive measurement reports
received by the eNB without discovering a new neighbor relation required to exit the
active phase of ANR. The other condition is given by parameter
activePhaseMeasReportThreshold.
Engineering Recommendation: activePhaseMeasReportHysteresis
The two thresholds, activePhaseMeasReportThreshold and
activePhaseMeasReportHysteresis should be considered together.
If either one of the thresholds is set too low, there is a risk of early ending of ANR
active phase when the neighbor relation creation is not yet completed. This will
impact the handover successful rate as no handover can be initiated to a PCI that
is not in list of neighbor relations. If either one of the thresholds is set too high,
however, it may cause the ANR active phase to last longer than necessary.
During the time, the eNB will process more measurement reports without finding
new PCI.
The
default
value
of
1000
is
recommended
for
activePhaseMeasReportThreshold and the default value of 200 is recommended
for activePhaseMeasReportHysteresis.
AutomaticNeighborRelation::activePhaseMeasReportThreshold
Parameter
activePhaseMeasReportThreshold
Object
Range & Unit
Integer
[10..2000] step of 10
Class/Category
C / I&C - OMC
Value
1000
Feature
81872
This parameter defines the minimum number of measurement reports received by the
eNB required to exit the active phase of ANR. The other condition is given by
parameter activePhaseMeasReportHysteresis.
Engineering Recommendation: activePhaseMeasReportThreshold
Refer to Engineering Recommendation under
activePhaseMeasReportHysteresis.
4.4.2.4 ANR IN DORMANT/WAKE-UP PHASE

When the neighbor relation creation is completed in a cell (LteCell::anrState ==
Complete), ANR enters ANR dormant phase. In this phase, however, eNB may still
receive new PCI measurement reports sent by UE.
Page 144/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
There are several reasons for receiving new PCI measurement reports. Setting either
one or both of the ANR active phase ending thresholds (Volume 6 section 4.4.2.3 of
LPUG) too low will cause the new PCI measurement reports to be received in ANR
dormant phase. Moreover, radio propagation condition changes of the existing cells
or a new eNB being deployed nearby may also cause new PCI to be reported.
If a new PCI is reported as the strongest cell in a handover measurement report, ANR
will enter ANR wake-up phase and trigger the ECGI search as below:
1. Start a configurable timer,
AutomaticNeighbourRelation::dormantPhaseTimerForEcgiDiscovery to
limit the duration of the ECGI search procedure.
2. Request the UE to find ECGI for the new PC
To increase the chance to find ECGI, before the timer is expired or until the ECGI is
found:
1. Configure all UEs in RRC connected state for ANR measurement.
2. Request the UEs that report the same new PCI to search for the associated
ECGI.
Once the ECGI is found, eNB will start the process to setup the X2 link if it does not
already exist. The procedure described in Volume 6 section 4.4.2.1.4 of LPUG will be
used.
AutomaticNeighborRelation::dormantPhaseTimerForEcgiDiscovery
Parameter
dormantPhaseTimerForEcgiDiscovery
Object
Range & Unit
Integer/minutes
[5..60] step = 5
Class/Category
C / I&C - OMC
Value
Feature
81872
This parameter defines the time the eNB may dedicate to actively attempt identifying
the ECGI associated to a newly discovered PCI during the dormant phase of ANR.
Engineering Recommendation: dormantPhaseTimerForEcgiDiscovery
Setting dormantPhaseTimerForEcgiDiscovery to a larger number may increase
the chance to find the ECGI of a new neighbor cell during ANR wake-up phase.
However, this will use more eNB and UE resource since more UE may be
configured for ANR measurement report or report-CGI to find PCI and ECGI. The
default value of this parameter is set to 5 minutes.
Page 145/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4.4.2.5 ANR NEIGHBOR RELATION MAINTENANCE FUNCTION GARBAGE COLLECTION
ANR has the mechanism to automatically delete the obsolete neighbors through a
process called garbage collection:
A PCI that does not have a valid ECGI associated with it for a week is
regarded as obsolete.
A neighbor relation that has not been reported by any UE for handover
purpose for a week and its LteNeighboringCellRelation::noRemove flag is
set to false is regarded as obsolete.
Once a day at midnight, ANR will delete the obsolete PCIs and the obsolete neighbor
relations. ANR will also delete an obsolete X2 link if all neighbor relations between the
two eNB have been deleted and the X2 link does not have its X2Access::noRemove
flag set to true.
The two noRemove flags mentioned above are used by operator to control whether
a neighbor relation or an X2 link can be deleted by the ANR garbage collection
function regardless the neighbor relation or the X2 link is created by ANR or is
provisioned by operator. When a neighbor relation or an X2 link is in the black list
(LteNeighboringCellRelation::NoHO is set to true or X2Access::NoX2HO is set to
true), the corresponding noRemove flag should also be set to true
4.4.2.6 ANR SYNCHRONIZATION FUNCTION

XMS and eNB should be synchronized to ensure the data consistency between the
neighbor relations created by ANR in eNB and the neighbor relations provisioned by
operator through XMS.
The neighbor relations provisioned by operator through XMS will be downloaded to
eNB like all other MIM parameters. For the neighbor relations created by the ANR,
synchronization between XMS and eNB will be performed based on the existing Last
Change Counter polling mechanism.
At the polling time when OAMSyncControl::anrState is equal to complete (All of the
cells in the eNB have entered ANR dormant phase), XMS will perform
synchronization to retrieve the latest parameters of LteNeighboringCellRelation MO,
X2Access MO or X2TransportLayerAccess MO.
A function exists that allows the operator to perform a manual synchronization
between XMS and eNB through XMS GUI. When the manual synchronization is
performed, ANR parameters will be synchronized, no matter it is in ANR active phase,
in ANR wake-up phase or in ANR dormant phase.
4.4.2.7 ANR RESET FUNCTION

Restriction: TLA2.1
This function is not supported for TLA2.1.
T
o
support the testing needs, ANR neighbor relationship can be deleted by resetting the
ANR feature. The ANR reset command through XMS GUI is not supported currently.
Page 146/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Instead, ANR function can be reset by a NEM command through the SNMP MIB
browser. The ANR reset command will take effect only if the ANR feature is
deactivated (ActivationService::anrEnable is set to false).
After an NEM user issues an ANR reset (SNMP parameter
automaticNeighbourRelationControl::anrReset set to True):
LteCell.anrState in each cell is set by ANR to notComplete
automaticNeighborRelationControl::anrState is set by ANR to

notComplete
All LteNeighboringCellRelation, X2Access and X2TransportLayerAccess

instances with noRemove flag set to false will be removed by ANR.
Once ANR parameters are removed and internal counters are reset,
automaticNeighbourRelationControl::anrReset is again set by ANR to
false.
ANR feature is ready to be reactivated.
Page 147/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5 EUTRAN TO UTRAN INTER-RAT MOBILITY

FOR LTE (USE CASES & CONTROL
PROCEDURES)
The feature PM76498 provides the basic mobility capability to ensure cell reselection
and packet service continuity for a dual-mode UE moves away from LTE coverage
area to a UMTS coverage area. The feature PM76498 covers LTE to UMTS mobility
capability for a dual-mode UE in both RRC idle and connected modes
5.1 RRC IDLE MODE MOBILITY:

The feature PM76498 provides basic mobility capability for UE moving from LTE
radio coverage to UMTS radio coverage. This feature enables the LTE-to-UMTS
mobility for a multi-mode UEs in RRC idle mode. This feature allows a UE to leave
the LTE coverage (island or hot-spot or hot-spots cloud) to recover the service in the
UMTS coverage; as soon as the UMTS coverage gets available i.e. inter-RAT
measurement demonstrate that the UMTS radio conditions are sufficiently good.
5.1.1 CELL RESELECTION ACTIVATION

Like in 4.1.2.1, at the same place in the data model, the both parameters below are in
the scope of mobility activation and information options. Be careful, it is mandatory
to activate them, for mobility related to. Theyre Fixed category and they are C
class parameters:
ActivationService:: isCellReselectionToUtraTddAllowed
Parameter
isCellReselectionToUtraTddAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
O.D. (false)
Feature
This parameter is an activation flag to set whether the EUTRAN to UTRA-TDD cell
reselection is enabled or disabled.
Page 148/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
utraTddNeighboringCellRelationIdList :This parameter is a list of associations

(also called indirections or pointers). This parameter refers to the list of instances
of UtraTddNeighboringCellRelation MO that must be considered when the UE
is handled on this cell. This parameter is used for blind PS HO. Each
utraTddNeighboringCellRelationId points to a twin UTRA-TDD overlay cell that
ensures the mobility continuity in the UTRA-TDD system. There are up to 3
UTRA-TDD twin cells: one per UTRA-TDD band.
LteCell::utraTddNeighboringCellRelationIdList
Parameter
utraTddNeighboringCellRelationIdList
Object
Enb/ LteCell
Range & Unit
BitString
listSizeMin = 0
istSizeMax = 3
Class/Category
C / Fixed
Value
O.D Value can be a List of 3 maximum elements of Link
Feature
105474
5.1.2 SYSTEMINFORMATIONBLOCKTYPE 6 AND SIB3 INTERWORKING

Inter-RAT cell reselection to UTRA parameters relies on the broadcast of
The IE SystemInformationBlockType3 contains cell re-selection information common
for intra-frequency, inter-frequency and/or inter-RAT cell re-selection (i.e. applicable
for more than one type of cell re-selection but not necessarily all) as well as intrafrequency cell re-selection information other than neighbouring cell related.
SystemInformationBlockType3 contains also speed dependant reselection
parameters.[R08] [R14]
Inter-RAT cell reselection to UTRA parameters relies on the broadcast of

The IE SystemInformationBlockType6 contains information relevant only for interRAT cell re-selection i.e. information about UTRA-TDD frequencies and UTRATDD neighboring cells relevant for cell re-selection. The IE includes cell reselection parameters common for a frequency as well as cell specific re-selection
parameters. [R08] [R14]
The IE contains common parameters to all UTRA frequencies: t-ReselectionUTRA; tReselectionUTRA-SF.
Page 149/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
The IE t-Reselection concerns the cell reselection timer tReselectionRAT for UTRA
(tReselectionUtra).
The IE t-ReselectionUTRA-SF concerns factors, to be applied to the
tReselectionRAT for UTRA when the UE is in medium or high speed state
(tReselectionUtraSfHight, tReselectionUtraSfMedium).
Besides tReselectionUtra; t-ReselectionUTRA-SF, the IE
SystemInformationBlockType6 contains also carrierFreqListUTRA-TDD; threshXHigh;
threshXLow; qRxLevMin; pMaxUTRA; qQualMin.
The eNodeB builds the IE SystemInformationBlockType6 only from MIM configuration
that is contained in MO UtraTddNeighboringFreqConf, in MO
CellReselectionConfUtraTdd, and in MO SpeedDependantConf. No feature SON
shall be applied to build SystemInformationBlockType6
5.1.3 CELL RESELECTION ALGORITHM DESCRIPTION

SIB6 parameters.
SystemInformationBlockType6 field descriptions
t-ReselectionUTRA
Parameter TreselectionUTRAN in TS 36.304.
t-ReselectionUTRA-SF
Parameter Speed dependent ScalingFactor for TreselectionUTRA in TS 36.304 [4]. If the
field is not present, the UE behaviour is specified in TS 36.304.
carrierFreqListUTRA-FDD
List of carrier frequencies of UTRA FDD.
carrierFreqListUTRA-TDD
List of carrier frequencies of UTRA TDD.
threshX-High
Parameter "Threshx,high" in TS 36.304.
threshX-Low
Parameter "Threshx,low" in TS 36.304.
q-RxLevMin
Parameter Qrxlevmin, see TS 25.304. Actual value = IE value * 2+1. Specifies the minimum
required Rx level in the cell expressedin dBm.
p-MaxUTRA
The maximum allowed transmission power on the (uplink) carrier frequency, see TS 25.304
[40]. In dBm
q-QualMin
Parameter Qqualmin in TS 25.304. In dB.
5.1.3.1 CELL SELECTION CRITERION

The cell selection criterion S (Calculated by the UE) is fulfilled when [3GPP 25.304]:
Srxlev > 0
Where:
Page 150/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Where:
Cell Selection RX level value (dB). Calclated by the UE

Measured cell RX level value (RSRP). Measured by the UE
Srxlev
Qrxlevmeas
This is received signal, P-CCPCH RSCP for TDD cells (dBm),
Minimum required RX level in the cell (dBm). SIB6

Srxlev evaluation as a result of a periodic search for a higher
priority PLMN while camped normally in a VPLMN [R15].
SIB6
max(Pemax Pumax, 0) (dB). Calculated by the UE
Maximum TX power level an UE may use when transmitting
on the uplink in the cell (dBm) defined as PEMAX in [TS 36.101].
Qrxlevmin
Qrxlevminoffset
Pcompensation
Pemax
SIB6
Pumax
Maximum RF output power of the UE (dBm) according to the

UE power class as defined in [TS 36.101]
When camped normally, the UE shall perform the following tasks [R14]:
select and monitor the indicated Paging Channels of the cell according to
information sent in system information;
monitor relevant System Information;
perform necessary measurements for the cell reselection evaluation procedure;
execute the cell

occasions/triggers:
reselection
evaluation
process
on
the
following
UE internal triggers;
When information on the BCCH used for the cell reselection

evaluation procedure has been modified.
Rule: To limite UTRA TDD Measurements

In order to further restrict the amount of measurement carried out by the UE in
RRC-Idle mode, The UE shall apply the following rules for inter-RAT UtraTdd
frequencies, which are indicated in in SystemInformationBlockType6 and for
which the UE has cellReselectionPriority:
For inter-RAT UtraTdd frequency, with a cellReselectionPriority higher than the
cellReselectionPriority of the current E-UTRA frequency, the UE shall perform
Page 151/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
measurements of higher priority inter-RAT UtraTdd frequencies.
For inter-RAT UtraTdd frequency, with cellReselectionPriority lower than the
cellReselectionPriority of the current E-UTRAN frequency:
If SServingCell > Snonintrasearch, UE may choose not to perform measurements of
inter-RAT frequency cells of equal or lower cellReselectionPriority
measurements of inter-RAT frequency cells of equal or lower
qRxLevMin : 3GPP 36.331[R08] Minimum required RX level in the UMTS cell

(dBm) . This parameter configures the q-RxLevMin included in the
SystemInformationBlockType6. The value sent over the RRC interface is
computed by substracting 1 to the configured value and dividing by 2 (the UE
performs the opposite computation, i.e. IE vale * 2 + 1)
CellReselectionConfUtraTdd::qRxLevMin
Parameter
qRxLevMin
Object
Enb/ LteCell/ UtraTddNeighboring/

UtraTddNeighboringFreqConf/ CellReselectionConfUtraTdd
Range & Unit
dBm
[-60..-13] step = 1
Class/Category
Value
-60
Feature
TEL-FID130617
Keys for Hierarchy: ENBEquipment Enb LteCell UtraTddNeighboring

UtraTddNeighboringFreqConf CellReselectionConfUtraTdd
Parameter qRxLevMin in [R14]. Actual value Qrxlevmin = IE value * 2+1 [dBm].
Specifies the minimum required Rx RSRP level in the cell. ( Where IE specify the DLU
database value)
Changing this value will affect cell size in terms of re-selection area toward UMTS.
Increasing this value will lead the mobile to start cell-selection/re-selection procedure
sooner and then will artificially decrease cell size in idle mode.
Page 152/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: qRxLevMin

regarding the apply value. 60 is the current value.
Rule: Regarding TLA2.1 : qRxlevminoffset MO CellSelectionReselectionConf

The same Offset used for inter-LTE mobility is used whatever is the target cell,
indeed the qRxlevminoffset parameter is unique in the database.4.1.1.3.1
pMaxUTRA : TS36.331: this parameter configures the p-MaxUTRA included in

the IE SystemInformationBlockType6
CellReselectionConfUtraTdd::pMaxUTRA
Parameter
pMaxUTRA
Object

Range & Unit
dBm
[-50..33] step = 1
Class/Category
Value
Feature
TEL-FID130617
Pcompensation is a compensation factor to penalize the low power mobiles.
Pcompensation = max(PEMAX - PUMAX, 0)

Where:
PEMAX = pMaxUTRA
PUMAX = maximum UE output power (dBm) according to its power class in 3g and
operating band. (to see table below)
Page 153/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Power (dBm)
Operating Band
Class 1
Class 2
Class 3
Class 4
UMTS 2100 MHz
+33
+27
+24
+21
II
UMTS 1900 MHz
N.A.
N.A.
+24
+21
UMTS 850 MHz
N.A.
N.A.
+24
+21
VI
UMTS 850 MHz
N.A.
N.A.
+24
+21
VIII
UMTS 900 MHz
N.A.
N.A.
+24
+21
shall trigger inter-frequency and inter-RAT measurements for cell
reselection. The value sent over the RRC interface is half the value configured
(the UE then multiplies the received value by 2). For more details consult
TS36.304. Defined in TS 36.331. Broadcast in SystemInformationBlockType3
Parameter
sNonIntraSearch
Object
Range & Unit
dB
[0..62] step = 2
Class/Category
Value
Feature
96760
Note: sNonIntraSearch drive the beginning of the measurements towards lower

priority cell than the serving cell. Below this threshold, the frequency of the
measurements can be twice greater than at the top of this threshold.
Engineering Recommendation: sNonIntraSearch
To keep RRC idle mode, we recomend to do measurements earlier.
The value 2 is the recommended value
If the SservingCell of the E-UTRA serving cell (or other cells on the same frequency
layer) is greater than Snonintrasearch then (3GPP 36133):
the UE may not search for, or measure inter-RAT layers of lower priority.

the UE search for inter-RAT layers of higher priority at least every
Thigher_priority_search = (60 * Nlayers) seconds, where
Page 154/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Nlayers is the total number of configured higher priority E-UTRA, UTRA FDD, UTRA
TDD, CDMA2000 1x and HRPD carrier frequencies and is additionally increased by
one if one or more groups of GSM frequencies is configured as a higher priority.
RSRP of
serving cell
At least
detected:60sec* Nlayers
Qrxlevmin+Qrxlevminoffset
+ Snonintrasearch
Higher priority cell

(NUTRA_carrier) * 30 sec
ALL priority cell
Figure 25 : Snonintrasearch drive cell detection frequency

and lower priority cell detection.
cellReselectionPriority: Relative priority for cell reselection (0 means lowest

CellSelectionReselectionConf::cellReselectionPriority
Parameter
Object
Range & Unit
Integer
[0..7] step = 1
Class/Category
Value
0 See Engineering Rule and Engineering Recommendation
Feature
96760,97933
Engineering Rule: cellReselectionPriority

Warning for TLA2.1: in relationship with cellReselectionPriority within
Cannot be equal to HrpdBandClassInfo::cellReselectionPriority
Page 155/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
0 is the lowest priority
Inter-working
with
:
UtraTddNeighboringFreqConf::priorityOfFreq
GeranNeighboringFreqsConf::priorityOfFreqs
Proposal setting:
The value 5 for cellReselectionPriority should be good. With this value, we can build the
following priority rancking cells:
The LTE cells with the highest priority: setting
CellSelectionReselectionConf::cellReselectionPriority to 5
The UMTS cells with a priority less high: setting
UtraTddNeighboringFreqConf::priorityOfFreq to 3 for example
The GERAN cells with lowest priority: setting
GeranNeighboringFreqsConf::priorityOfFreqs to 2 for example
In this proposal setting, the values of priority 0,1 and 4 are in spare.
5.1.3.1.1 MIM MODEL

The MO UtraTddNeighboring contains information related to the cells neighboring
(e.g. at the network level but not at the frequency level): this information is gathered in
a child MO that is called UtraTddNeighboringCellRelation MO.
The MO UtraTddNeighboring contains information related only to the frequencies
neighboring (i.e. only at the frequency level): this information is gathered in a child MO
that is called UtraTddNeighboringFreqConf MO.
Page 156/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 26 : MIM Model UTRATDDNEIGHBORING
5.1.3.2 CELL RESELECTION PRIORITIES HANDLING

Absolute priorities of different E-UTRAN frequencies ([R14] in 5.2.4.1) or inter-RAT
frequencies may be provided to the UE in the:
system information
or , in the RRCConnectionRelease message releasing the RRC connection.,
or by inheriting from another RAT at inter-RAT cell (re)selection.
In the case of system information, an E-UTRAN frequency or inter-RAT frequency
may be listed without providing a priority (i.e. the field cellReselectionPriority is
absent for that frequency).
If priorities are assigned via provided in dedicated signalling, the UE shall ignore all
the priorities provided in system information.
If UE is in camped on any cell state, UE shall only apply the priorities provided by
system information from current cell, and the UE preserves priorities provided by
dedicated signalling unless specified otherwise. When the UE in camped normally
state, has only dedicated priorities other than for the current frequency, the UE shall
Page 157/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
consider the current frequency to be the lowest priority frequency (i.e. lower than
the eight network configured values).
The UE shall delete priorities provided by dedicated signalling when:
the UE enters RRC_CONNECTED state; or
the optional validity time of dedicated priorities (t320) expires; or
a PLMN selection is performed on request by NAS.
NOTE:
Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and
inter-RAT frequencies that are given in system information and for which the UE has a
priority provided. The UE shall not consider any black listed cells as candidate for cell
reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining
validity time (i.e., t320), if configured, at inter-RAT cell (re)selection.
NOTE: The network may assign dedicated cell reselection priorities for
frequencies not configured by system information.
t320: TS36.331: This parameter contributes to the configuration of the IE

IdleModeMobilityControlInfo used in the message RRCConnectionRelease.
This parameter is optional.
UeTimers::t320
Parameter
t320
Object
Enb/ DedicatedConf/ UeTimers
Range & Unit
Enumerate in s
[min5, min10, min20, min30, min60, min120, min180]
Class/Category
C / Fixed
Value
Min5
Feature
FRS 76498
Keys for Hierarchy: ENBEquipment Enb DedicatedConf UeTimers
Start: Upon receiving t320 or upon cell (re)selection to E-UTRA from another RAT
with validity time configured for dedicated priorities (in which case the remaining
validity time is applied).
Stop: Upon entering RRC_CONNECTED, when PLMN selection is performed on
request by NAS, or upon cell (re)selection to another RAT (in which case the timer is
carried on to the other RAT).
At expiry: Discard the cell reselection priority information provided by dedicated
signalling.This parameter is optional: if not present, then the eNB shall not send the IE
IdleModeMobilityControlInfo in the message RRCConnectionRelease.
Page 158/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.1.3.3 UE SPEED MANAGMENT
Parameters in relationship with mobility speed states of a UE, in case of inter-LTE
mobility, are the same as in case of intra-RAT mobility, except parameters in the MO
object UtraSpeedConf and tReselectionUtra, which are specific: Then you can
report to section 4.1.1.3.3 with this latest restriction.
Scaling rules:
-

-

- Add qHystSfHigh to Qhyst (to see section 4.1.1.3.2) for high mobility state if
sent on system information.
- For UTRAN cells multiply tReselectionUtra by tReselectionUtraSfHigh if

- Add the IE sf-Medium of "Speed dependent ScalingFactor for Qhyst (to see
section 4.1.1.3.2) for medium mobility state " to Qhyst if sent on system
information. qHystSfMedium is The MIM parameter used to.
by tReselectionEutraSfMedium, if sent on system information.
- For UTRAN cells multiply tReselectionUtra by tReselectionUtraSfMedium,
if sent on system information.
Page 159/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionUtraSfHigh : TS36.331: this parameter contributes to the

the t-ReselectionUTRA-SF included in the IE SystemInformationBlockType6.
Parameter Speed dependent ScalingFactor for TreselectionUTRA in TS 36.304.
If the field is not present, the UE behaviour is specified in TS 36.304. The
concerned mobility control related parameter is multiplied with this factor if the
UE is in High Mobility state as defined in TS 36.304. Value oDot25 corresponds
to 0.25, oDot5 corresponds to 0.5 , oDot75 corresponds to 0.75 and so on.
UtraSpeedConf::tReselectionUtraSfHigh
Parameter
tReselectionUtraSfHigh
Object
Enb/ LteCell/ SpeedDependentBroadcastConf/ UtraSpeedConf
Range & Unit
Enumerate
[oDot25, oDot5, oDot75, 1Dot0]
Class/Category
Value
N.A
Feature
76498
mobility.
tReselectionUtraSfMedium : TS36.331: this parameter contributes to the

the t-ReselectionUTRA-SF included in the IE SystemInformationBlockType6.
Parameter Speed dependent ScalingFactor for TreselectionUTRA in TS 36.304.
If the field is not present, the UE behaviour is specified in TS 36.304. The
UE is in Medium Mobility state as defined in TS 36.304. Value oDot25
corresponds to 0.25, oDot5 corresponds to 0.5 , oDot75 corresponds to 0.75 and
so on.
UtraSpeedConf::tReselectionUtraSfMedium
Parameter
tReselectionUtraSfMedium
Object
Enb/ LteCell/ SpeedDependentBroadcastConf/ UtraSpeedConf
Range & Unit
Enumerate
Class/Category
Value
N.A
Feature
76498
mobility.
Page 160/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.1.3.4 E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL

Criteria 1: the SnonServingCell,x of a cell on evaluated frequency is greater than
threshXHigh during a time interval tReselectionRAT
For UTRAN and E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated
cell. Plesae report to section 5.1.3.1 to know what is Srxlev.
Rule: Regarding TLA2.1 : tReselectionRAT matching with the type of mobility

tReselectionRAT : This specifies the cell reselection timer value. For each target
frequency/frequency group per RAT a specific value for the cell reselection timer is
defined, which is applicable when evaluating reselection within E-UTRAN or towards
other RAT (i.e. tReselectionRAT for E-UTRAN is tReselectionEUTRAN, for
UTRAN tReselectionUtra, for GERAN tReselectionGERAN, for Cdma
tReselectionCdmaHrpd, and for TreselectionCDMA_1xRTT).
Note: tReselectionRAT is not sent on system information, but used in reselection
rules by the UE for each RAT.
Cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT
frequency than serving frequency shall be performed if:
-
A cell of a higher priority E-UTRAN frequency or inter-RAT frequency fulfils

criteria 1; and
more than 1 second has elapsed since the UE camped on the current serving
cell.
Cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT

-
No cell on serving frequency or on an equal priority E-UTRAN frequency or on

a higher priority E-UTRAN frequency or inter-RAT frequency than serving
frequency fulfills the criteria 1; and
SservingCell < threshServingLow and the SnonServingCell,x (on the target

cell) of a cell of a lower priority E-UTRAN frequency or inter-RAT frequency is
greater than threshXLow during a time interval tReselectionRAT; and
cell.
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based

on ranking for Intra-frequency Cell Reselection as defined in section 4.1.1.3.2 or in
[R14] section 5.2.4.6.
In all the above criteria the value of tReselectionRAT is scaled when the UE is in the
medium or high mobility state as defined in section 5.1.3.3 or in subclause [R14]
5.2.4.3.1.
to criteria defined in 4.1.1.3.2 or in [R14] section 5.2.4.6.
Page 161/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
For E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated cell.
tReselectionUtra : TS36.331: this parameter configures the t-ReselectionUTRA

included
in
the
IE
SystemInformationBlockType6.
Parameter
TreselectionUTRAN in TS 36.304. This concerns the cell reselection timer
TreselectionRAT for UTRA. Value in seconds.
CellSelectionReselectionConf::tReselectionUtra
Parameter
tReselectionUtra
Object
Range & Unit
s
[0..7] step = 1
Class/Category
Value
2 (default:2)
Feature
76498
mobility.
Warning: For a cell that has been already detected, but that has not been reselected
to, the filtering shall be such that the UE shall be capable of evaluating that an already
identified UTRA TDD cell has met reselection criterion within NUTRA_carrier_TDD
*TevaluateUTRA_TDD when Treselection = 0 as specified in table 4.2.2.5.2-1 provided that the
reselection criteria is met by a margin of at least 6dB.
NUTRA_carrier: number of carriers used for all UTRA TDD cells in the neighbour cell
list.
DRX
cycle
length
[s]
0.32
0.64
1.28
2.56
TdetectUTRA_TDD
[s]
30
60
TmeasureUTRA_TDD
[s] (number of
DRX cycles)
TevaluateUTRA_TDD
[s] (number of
DRX cycles)
5.12 (16)
5.12 (8)
6.4(5)
7.68 (3)
15.36 (48)
15.36 (24)
19.2 (15)
23.04 (9)
Table 12: Measurements of UTRAN TDD cells selection [3GPP 36133].
Page 162/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
threshServingLow: Threshold for serving cell reception level used in reselection

evaluation towards lower priority E-UTRAN frequency or RAT. The value sent
received
value
by
2)
Defined
in
TS
36.331
Broadcast
in
CellSelectionReselectionConf::threshServingLow
Parameter
threshServingLow
Object
Range & Unit
Integer, dB
[0..62] step = 2
Class/Category
Value
Feature
96760
Note: You cannot leave serving cell, if this one gets some reception level,
greater than threshServingLow.
Engineering Recommendation: threshServingLow
To get the option to reselect as soon as possible, with serving cell reception level
below sNonIntraSearch, we can set threshServingLow at the same level than
sNonIntraSearch. i.e set threshServingLow to 16 dB.
threshXHigh: TS36.331: this parameter configures the threshX-High included in

CellReselectionConfUtraTdd::threshXHigh
Parameter
threshXHigh
Object

Range & Unit
Integer, dB
[0..31] step = 1
Class/Category
Value
20
Feature
TEL-FID130617
Note: This parameter is used in the Algorithm of cell selection and reselection towards
an iRAT cell which get priority greater than the LTE serving cell.
Page 163/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Keys for Hierarchy: ENBEquipment Enb LteCell UtraTddNeighboring
UtraTddNeighboringFreqConf CellReselectionConfUtraTdd
Note: Like we have chosen to favor LTE cell in our proposal implementation and that:
CellSelectionReselectionConf:: cellReselectionPriority
>
>
HrpdBandClassInfo::cellReselectionPriority
or
Then
threshXHigh is not used because it does not exist iRAT cell with a greater priority
than the source cell.
threshXLow: TS36.331: this parameter configures the threshX-Low included in

CellReselectionConfUtraTdd::threshXLow
Parameter
threshXLow
Object

Range & Unit
Integer, dB
[0..31] step = 1
Class/Category
Value
10
Feature
TEL-FID130617
Note: If some selected cell reach this threshold, when Sserving cell <
threshServingLow, then treselectionUtra is start.
Engineering Recommendation: threshXLow

To favor the reselection, we can set this parameter to 0.
For E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated cell.
Page 164/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
For Utra-Tdd, another S criterion is used in the Utra-Tdd cell reselection process;
to determine which UtraTdd cell(s) can be selected. S-criterion is divided into 2 subcriteria:
o
SnonServingCell=Srxlev: it aims at checking the good level of reception in the

cell (measurement is based on P-CCPCH_RSCP). If above a Rx minimum level,
the UtraTdd cell has a sufficient signal level.
Squal:(refer to 5.1.3.1) it aims at checking the good quality of the signal, it means
not to much interferences (measurement is based on P-CCPCH_RSCP). If above
a minimum quality level, the cell has a sufficient signal quality.
Finally, if both criteria are fulfilled (1) SnonServingCell=Srxlev>ThresX** and (2)

Squal>0 allows the UtraTdd cell to be selected
The reselection process works as follows:
1 : Serving cell become less good and the RSRP level decrease under
[Qrxlevmin(SIB3)+sNonIntraSearch]. Then cell detection of better cell is
possible twice more frequently in average towards all cells, and we can detect
and measured lower priority cells than the serving.
2 : Serving cell becomes worse and the RSRP level decrease under
[Qrxlevmin(SIB3)+threshServingLow]. Cell reselection would be possible, but
not
yet
candidate
cell,
reaching
[Qrxlevmin+Qrxlevminoffset
+Pcompensation+threshXLow]. In this user case, 1 and 2 occur at the same
time because
we have chosen to
implement sNonIntraSearch=
threshServingLow.
3 :
The situation just above is still reached and also, in the target cell,
are
thresholds
[Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXLow]
reached. tReselectionUTRA is started.
During
tReselectionUTRA,
NO
higher
cell
priority
[Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXHigh]
4 :
reaches
tReselectionUTRA is achieved, reselection is triggered.
5.1.3.5 ALGORITHM FOR CELL RESELECTION PRIORITY
The presence and the content of IE freqPriorityListEUTRA depends on the attribute

FrequencyAndBandwidthTDD priorityOfFreq; the priority of the carrierFreq (this
is an optional parameter in the MiM).
The ENB call processing
(1.) Retrieves from its UE context, the bandUtraTdd supported by the UE as
specified by [RRC] UE-EUTRA-Capability that are specified by
SupportedBandUTRA-TDD
(2.) Retrieves from attributes ENBEquipment Enb LteCell UtraTddNeighboring
UtraTddNeighboringFreqConf {bandUtraTdd128; bandUtraTdd384;
Page 165/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
bandUtraTdd768; carrierFreq} the carrierFreq supported by both the network
and the UE
(3.) Retrieves from attributes ENBEquipment Enb LteCell UtraTddNeighboring
UtraTddNeighboringFreqConf priorityOfFreq the priority of the carrierFreq
retrieved during (2.)
1. Case Blind-Redirection-To-3GPP-RAT: the eNB receives a MeasReport that

corresponds to a measurement purpose Blind-Redirection-To-3GPP-RAT
The eNB does not send the idleModeMobilityControlInfo. In this case if the
redirection fails and the UE comes back to idle then the UE relies on SiB6.
2. Case Meas-Redirection-To-UTRA-TDD: the eNB receives a MeasReport that
corresponds to a measurement purpose Meas-Redirection-To-UTRA-TDD
The eNB sends the idleModeMobilityControlInfo
The eNB shall builds the RRC IE
1>IdleModeMobilityControlInfo and
2>freqPriorityListUTRA-TDD
o takes the MiM configuration as entered by the Operator in
UtraTddNeighboringFreqConf MO and.
o gives the highest priority to the UTRAN Freq or GERAN Freqs received in
MeasReport
o builds all the other priorities by following the order configured in
UtraTddNeighboringFreqConf
During t320, the UE will follow the cell reselection priorities provided by
IdleModeMobilityControlInfo.
After t320, the UE will follow the SIB6 (and/or SIB7) (as specified by 36.304
section[36304-860] 5.2.4.1)
3. Optional sending of this IE idleModeMobilityControlInfo: depens on the presence

of optional MiM parameter "t320" (see definition of attribute t320)
Page 166/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
priorityOfFreq: [36331]: this parameter contributes to the configuration of the IE

IdleModeMobilityControlInfo: freqPriorityListEUTRA-TDD (Optional). This
attribute is used by the Algorithm for RRC Measurement Configuration,
and/or for Control Procedure for Mobility (RAT chosen for the blind
redirection) : not in TLA2.1; valid for an inter-frequency LTE deployment.
FrequencyAndBandwidthTDD::priorityOfFreq
Parameter
priorityOfFreq
Object
Enb/ LteCell/ FrequencyAndBandwidthTDD
Range & Unit
Integer
[0..7] step = 1
Class/Category
Value
Feature
105095
Note: The lowest priority is 0
priorityOfFreq: [36331 v850]: this parameter contributes to the configuration of

the IE IdleModeMobilityControlInfo::= SEQUENCE { ......, freqPriorityListUTRAFDD (Optional); freqPriorityListUTRA-TDD (Optional); ......}. . This attribute is used
by the Algorithm for RRC Measurement Configuration, and/or for Control
Procedure for Mobility (RAT chosen for the blind redirection); to fill
cellReselectionPriority in the 36331 RRC IE SystemInformationBlockType6
Parameter
priorityOfFreq
Object

Range & Unit
Integer
[0..7] step = 1
Class/Category
Value
Feature
TEL-FID130120
Note: The lowest priority is 0

Rule: Configure priorityOfFreq
Inter working with CellSelectionReselectionConf::cellReselectionPriority
bandUtraTdd128: ENUMERATED{ a, b, c, d, e, f, g, h, i, j, k, l, m, n,o, p, ...}that

is compared with the IE supportedBandUTRA-TDD128 of the IE UE-EUTRA-
Page 167/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Capability. TS36.331: the IE UE-EUTRA-Capability is used to convey the E-UTRA
UE Radio Access Capability Parameters, see TS 36.306, to the network. The IE
UE-EUTRA-Capability is transferred in E-UTRA or in another RAT.
UtraTddNeighboringFreqConf::bandUtraTdd128
Parameter
bandUtraTdd128
Object
Range & Unit
Enumerate
{a, b, c, d, e, f, g, h, i, j, k, l, m, n,o, p, ...}
Class/Category
C / Fixed
Value
N.A
Feature
TEL-FID130120
bandUtraTdd384: ENUMERATED { a, b, c, d, e, f, g, h, i, j, k, l, m, n,o, p, ...} that

is compared with the IE supportedBandUTRA-TDD384 of the IE UE-EUTRACapability. TS36.331: the IE UE-EUTRA-Capability is used to convey the E-UTRA
Parameter
bandUtraTdd384
Object
Range & Unit
Enumerate
Class/Category
C / Fixed
Value
N.A
Feature
TEL-FID130120
Page 168/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
bandUtraTdd768: ENUMERATED { a, b, c, d, e, f, g, h, i, j, k, l, m, n,o, p, ...} that

is compared with the IE supportedBandUTRA-TDD768 of the IE UE-EUTRACapability. TS36.331: the IE UE-EUTRA-Capability is used to convey the E-UTRA
Parameter
bandUtraTdd768
Object
Range & Unit
Enumerate
Class/Category
C / Fixed
Value
N.A
Feature
TEL-FID130120
carrierFreq: The IE carrierFreq is used to indicate the ARFCN applicable for a

downlink (Nd, FDD) or bi-directional (Nt, TDD) UTRA carrier frequency, as
defined in TS 25.331. For example in TS36.331: this parameter configures the IE
carrierFreq included in SystemInformationBlockType6
UtraTddNeighboringFreqConf::carrierFreq
Parameter
carrierFreq
Object

Range & Unit
Integer
[0..16383] step = 1
Class/Category
C / Fixed
Value
Feature
TEL-FID130120
5.1.3.6 LTE TO UTRA TDD RESELECTION CONFIGURATION
Page 169/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 27 : Reselection configuration towards UTRAN cell.
5.2 RRC CONNECTED MODE MOBILITY:

The feature PM76498 enables the LTE-to-UMTS mobility in RRC connected mode
with a redirection to UMTS based on radio measurements.
The feature PM76498 introduces a redirection to UMTS that allows the ENB to help
the UE to perform a cell reselection to a target UMTS cell. The feature PM76498
requires this redirection to be based on radio measurements: the intra-frequency
EUTRA radio conditions shall be below a configured threshold; the inter-RAT
UTRA-TDD radio conditions shall be better than a configured threshold.
Compared with a blind redirection without inter-RAT UTRA-TDD radio measurements,
the redirection with measurement improves the end-user QoE (Quality of
Experience) by redirecting the UE from an LTE island/hot-spot to an UMTS overlay in
a timely fashion.
The redirection with measurement avoids the UE from being stuck in an LTE source
cell with bad radio conditions and allows the UE being redirected towards an UMTS
target cell with good radio conditions.
Inter-RAT mobility functionality shall provide UE mobility while its packet session is
on-going.
Page 170/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering
Recommendation:
triggerTypeEUTRA=eventA2
triggerTypeInterRAT=eventB2
or
measurementPurpose = Meas-Redirection-To-UTRA-TDD (eventB2) should be

configured only if the network will have UEs capable of IRAT measurements without
Gap. This is the most radio preferred mechanism for IRAT mobility to UE but this
one is not yet recommended in TLA2.1.3.
measurementPurpose = Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-ToUTRA-TDD (eventA2) should be configured if the network will have UEs capable of
blind redirection and/or blind PS HO(Future release). Blind PS HO is the next
preferred mechanism for IRAT mobility to UMTS. Blind redirection is the least
preferred mechanism for IRAT mobility to UMTS.
In conclusion in TLA2.1.3 we recommend to implement the network with
triggerTypeEUTRA=eventA2 and
measurementPurpose = Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-ToUTRA-TDD.
5.2.1 REDIRECTION ACTIVATION

Like in 4.1.2.1, at the same place in the data model, the both parameters below are in
the scope of mobility activation and information options. Be careful, it is mandatory
to activate them, for mobility related to. Theyre Fixed category and they are C
class parameters:
ActivationService:: isRedirectionToUtraTddAllowed
Parameter
isRedirectionToUtraTddAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
O.D. (false)
Feature
This parameter is an activation flag for feature eUTRAN to UTRAN-TDD Inter-RAT
Mobility Cell Reselection-Redirection.
Engineering Recommendation: isRedirectionToUtraTddAllowed

If you want to implement redirection towards UMTS, set this parameter to true
To see diagram in section 4.3.1.3 for A2 blind configuration.

Page 171/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.2.2 CONTROL PROCEDURES FOR RADIO MEASUREMENTS

CONFIGURATION AND MOBILITY TRIGGER
MANAGEMENT
The TLA2.1 redirection EUTRA-to-UTRA-TDD relies entirely on measurement reports
from the UE. The UE reports to the source ENB when the serving radio quality is
sufficiently degraded and an inter-RAT neighbor is a good candidate.
In TLA2.1, one specific measurement purpose can trigger EUTRA to UTRA-TDD interRAT mobility. In addition, other measurements could be configured like intrafrequency
EUTRA
measurements
or
inter-RAT
EUTRA-TDD-to-GERAN
measurements (see section 6.2.2).
The next sections specify the triggers to transmit successive RRC messages for RRC
measurement configuration. The measurements are set-up upon transition to the RRC
connected mode; setup/released upon receipt of measurement reports indicating the
radio level quality of an intra-frequency EUTRA cell or an inter-RAT UTRA-TDD cell.
The measurements can be updated upon completion of an intra-frequency intra-ENB
handover or an intra-frequency X2 handover (inter-ENB).
5.2.2.1 MEASUREMENTS CONFIGURATION AT CALL SETUP

The eNodeB call processing distinguishes many phases of RRC measurements:
-
Phase No.1: high priority measurements are configured for the intra-LTE intrafrequency handover. At call setup, such a measurement is configured just after
RRC Connection Setup procedure and before configuration of security mode.
Any measurement report received before completion of security mode
configuration and SRB2 + default bearer (+ optional bearers) is ignored and
discarded by the eNodeB. Because intra-LTE intra-frequency mobility cannot
be performed while security mode and SRB2 + default bearer are not
configured successfully.
Phase No.2: one configures low priority measurements i.e. measurements not
dedicated for the intra-LTE intra-frequency handover. At call setup, these
measurements are configured only once security mode and SRB2 + default
bearer are configured successfully.
Phase No.3: subsequent low priority measurements are configured upon the
evolution of the radio quality as described in this document.
If the attribute isRedirectionToUtraTddAllowed is set to TRUE, a measurement

control RRCConnectionReconfiguration message with the IE MeasConfig may be
(depending on MiM configuration) sent to the UE during Phase No.2 (low priority
measurement).
The message RRCConnectionReconfiguration includes the IE MeasConfig to
configure the inter-RAT (UTRAN) measurement profile described below in section
Page 172/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.2.2.4 algorithm for RRC Measurement configuration. This RRC Measurement
Configuration is applied in the serving cell on which the call is established.
In TLA2.1 up to maxMeasId INTEGER=32 measurements could be setup including
the mobility triggering measurement. The failure of the measurement set-up is
supported in TLA2.1.
The next figure hereafter describes the measurement setup at call setup.
UE
eNodeB
MME
RRC CONNECTION REQUEST
RRC CONNECTION SETUP
RRC CONNECTION SETUP COMPLETE

S1AP INITIAL UE MESSAGE
Algorithm for RRC

Measurement Configuration
Phase No.1
Algorithm for RRC

Measurement Gap
Configuration (not used)
RRC Measurement
Configuration only for
Intra-Frequency Mobility
RRC CONNECTION RECONFIGURATION

RRC CONNECTION RECONFIGURATION COMPLETE

RRC UE CAPABILITY ENQUIRY
(Optional)
RRC UE CAPABILITY INFORMATION
Algorithm for
callpUeCapabilityInformation
SECURITY MODE COMMAND
SECURITY MODE COMPLETE

Algorithm for RRC

Phase No.2
Algorithm for RRC

Measurement Gap

RRC Measurement
Configuration
UE
eNodeB
MME
Figure 28 : Measurement setup at call setup
Page 173/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.2.2.2 RRC MEASUREMENTS CONFIGURATION: USAGE OF MIM

MODEL
Restriction: TLA2.1
T
The MiM model for measurement configuration is described in the next figure
including hierarchy and associations (pointers as called indirections) of the MOs and
cardinality of the MOs.
The configuration of RRC measurement that is dedicated to the inter-RAT mobility is
based on MiM configuration.
The path of decision for RRC measurements configuration (example of the inter-RAT
measurements to UTRA-TDD) can be summarized as follows:
The ENB (call processing) knows the instance of MO LteCell of the UE serving
cell
The ENB knows the instances (if any) of MO UtraTddNeighboringCellRelation

for the serving cell
The ENB configures the inter-RAT measurements to UTRA-TDD for each carrier
frequency
The ENB knows the instances of MO RrcMeasurementConf for the serving cell
from which it retrieves the measurementIdentityConfIdList i.e. the list of the
instances of MO MeasurementIdentityConf
To configure an event B2, the ENB selects the instance of MO

MeasurementIdentityConf for which measurementPurpose is configured to
Meas-Redirection-To-UTRA-TDD
From which it retrieves the measObjectId i.e. the instance of MO

MeasObject; the reportConfigId i.e. the instance of MO ReportConfig;
the binding between (measObjectId; reportConfigId) i.e. between the
instances of MO MeasObject and MO ReportConfig
the measObjectId identifies the instance of MO MeasObject and its child subMO MeasObjectUTRA
the reportConfigId identifies the instance of MO ReportConfig and its child

sub-MO ReportConfigUTRA
Page 174/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
o
from the instance of MO MeasObjectUTRA retrieved thanks to measObjectId

the ENB retrieves the utraTddNeighboringCellRelationId i.e. the instance of
MO UtraTddNeighboringCellRelation that contains the carrier frequency used in
the RRC IE MeasObject
Note that the daisy chain is repeated for each neighbour carrier frequency
(UTRA-TDD) configured for the instance of MO LteCell of the UE serving cell:
The ENB (call processing) calculates as many measId and measObjectId as

necessary: one per UTRA TDD carrier frequency (for the sole UTRA).
The ENB (call processing) retrieves as many configured reportConfigId as

necessary: one per UTRA TDD carrier frequency (for the sole UTRA).
Page 175/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 29 : RRC Measurements Configuration inter-RAT mobility
5.2.2.3 CONTROL OF UE MOBILITY IN RRC CONNECTED STATE:

REDIRECTION EUTRA-TO-UTRA-TDD
Page 176/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: Regarding UE &TLA2.1 network capability
WB2 event is only applied for the case where UE can support UTRAN/GERAN
hmeasurement without measurement GAP, which we don't have a UE that do that.
eFor this reason, TLA2.1 redirection is A2 based mainly, this case is depicted in
n4.3.1.3
the EUTRA serving cell becomes worse than a threshold and the UTRA-TDD
neighboring cell becomes better than another threshold, the eNodeB receives a
Measurement Report message with Event-B2 from the mobile. (*) The Algorithm for
Control Procedures for Mobility decides to trigger a redirection EUTRA-to-UTRATDD.
When the eNodeB does not receive any Measurement Report message from the
mobile and (*) the selection of mobility mechanism decides to trigger a blind EUTRAto-UTRA-TDD redirection (i.e. without measurements).
The function of EUTRA-to-UTRA-TDD redirection, the eNodeB provides the following
functions;
(1) EUTRA-to-UTRA-TDD redirection execution phase;
(2) EUTRA-to-UTRA-TDD redirection completion phase.
5.2.2.3.1 EXECUTION PHASE:

During the previous phase (selection of the control procedures for mobility),
the source ENB has decided to initiate a EUTRA-to-UTRA-TDD redirection to the
target access network (UTRA-TDD).
The source ENB will give a command to the UE to re-select a cell in the target
access network via the RRC CONNECTION RELEASE. The RRCConnectionRelease
message is used to command the release of an RRC connection.
The
eNodeB
builds
the
RRCConnectionRelease
message
with
the
redirectionInformation, so that the UE select a suitable cell on the UTRA-TDD
frequency indicated by the redirectionInformation in accordance with the usual cell
selection process.
The eNodeB may provide IRAT/frequency priority information
RRCConnectionRelease message with the redirectionInformation.
during
The
eNodeB
builds
the
RRCConnectionRelease
message;
with
the
idleModeMobilityControlInfo (optional) so that the UE stores the cell reselection
priority information provided by the idleModeMobilityControlInfo; or without the
idleModeMobilityControlInfo (optional) so that the UE applies the cell reselection
priority information broadcast in the system information
The source ENB sends an S1AP UE CONTEXT RELEASE REQUEST message to the source
MME. This message is sent by the eNB to request the release of the UE-associated
S1-logical connection over the S1 interface: with Cause IE set to Inter-RAT
redirection to indicate the reason for triggering the UE Context Release Request
procedure.
Upon receipt of the Redirection Information received in the RRC Connection Release
message, the UE leaves EUTRA-TDD old cell and start access UTRA-TDD new cell.
Page 177/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.2.2.3.2 COMPLETION PHASE:
Upon receipt of the S1AP UE CONTEXT RELEASE REQUEST, the source MME sends a
S1AP UE CONTEXT RELEASE COMMAND message to the Source eNodeB.
The completion in the ENB ends upon receipt S1AP UE CONTEXT RELEASE COMMAND
and sending by the ENB to the source MME of a S1AP UE CONTEXT RELEASE
COMPLETE of a or upon guard timer expiration.
5.2.2.3.3 SYSTEM CALL FLOW:
Page 178/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 30 : Call flow Redirection EUTRA-TO-UTRA-TDD
5.2.2.4 ALGORITHM FOR RRC MEASUREMENT CONFIGURATION

In TLA2.x, the EUTRAN system deployment requires an algorithm for RRC
measurement configuration as already started in LA1.0.
Page 179/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: Regarding TLA2.1
Note: Measurement gap is supported in TLA2.1 with configuration restriction:
Supported:
20MHz TDD DL-UL Configuration 1, special configuration
10MHz TDD
5.2.2.5
S DL-UL Configuration 1, special configuration
P
Not supported:
E
all configuration
in TDD DL-UL Configuration 2 are not
E
7,
5,
7,
5,
2ant
2ant
2ant
2ant
and
and
and
and
8ant
8ant
8ant
8ant
supported
D
STATE MEASUREMENTS CONFIGURATION
Parameters working to speed state measurements configuration in case of inter-RAT

mobility, work also to speed state measurements configuration in case of intra-LTE
mobility. Then you can report to section 4.3.1.4
The implementation is similar to the state idle mode: report to section 5.1.3.3 but with
the parameters depicted in section 4.3.1.4
5.2.2.5.1 MIM MODEL

Keys for Hierarchy: ENBEquipment Enb RrmServices UeMeasurementConf
RrcMeasurementConf SpeedDependentConf SpeedStateEvalConf
Keys for Hierarchy: ENBEquipment Enb RrmServices UeMeasurementConf

RrcMeasurementConf SpeedDependentConf TimeToTriggerConf
Page 180/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.2.2.6 LTE TO UTRAN MEASUREMENT REPORTING SETTING
offsetFreqUTRA: TS36.331: this parameter configures the IE offsetFreq included

in the IE MeasObjectUTRA in the IE MeasConfig. offsetFreq that is used to
indicate a frequency specific offset to be applied when evaluating triggering
conditions for measurement reporting. The value in dB.
MeasObjectUTRA::offsetFreqUTRA
Parameter
offsetFreqUTRA
Object

MeasObjectUTRA
Range & Unit
Integer in dB
[-15..15] step = 1
Class/Category
Value
Feature
FRS 76498
As of TLA2.1, MO MeasObjectUTRA is used to configure a measurement when the

associated measurementPurpose is set to a new value introduced in TLA2.1: MeasRedirection-To-UTRA-TDD (TLA2.1).
[R08] specifies that the eNodeB cannot configure more than one MeasObject per
UTRA carrier frequency in an UE.
One and only one instance of MeasObjectUTRA MO is configured for all the RRC
measurements for one UTRA carrier frequency in the UE. One and only one MO
MeasObjectUTRA is configured per UTRA carrier frequency.
The MeasObjectUTRA MO is a child of the MeasObject MO: before TLA2.1, each
instance of MeasObject MO had only a child MeasObjectEUTRA. As of TLA2.1, there
are other children defined because intra-LTE measurements towards another LTE
cell are supported and also because inter-RAT measurements towards GERAN are
supported (as of TLA2.1.3).
5.2.2.7 NEIGHBOR CELL INFORMATION PROVIDED TO UES IN

CONNECTED MODE
Page 181/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
physCellIdUTRATDD:
TS36.331:
this
parameter
configures
the
IE
PhysCellIdUTRA-TDD that is used to indicate the physical layer identity of the
cell, i.e. the cell parameters ID (TDD), as specified in TS 25.331. Also
corresponds to the Initial Cell Parameter Assignment in TS 25.223. The IE
PhysCellIdUTRA-TDD is included in the IE MeasObjectUTRA in the IE MeasConfig.
The IE PhysCellIdUTRA-TDD is included in the IE MeasResults in the IE
MeasResultUTRA.
UtraTDDNeighboringCellRelation::physCellIdUTRATDD
Parameter
physCellIdUTRATDD
Object
Enb/ LteCell/ UtraTDDNeighboring/

UtraTDDNeighboringCellRelation
Range & Unit
Integer
[0..511] step = 1
Class/Category
C / Fixed
Value
O.D
Feature
TEL-FID130120
The MO UtraTDDNeighboringCellRelation is a child of MO UtraTDDNeighboring. It

contains information related to the cells neighboring (e.g. at the network level but
not at the frequency level).
Keys for Hierarchy: ENBEquipment Enb LteCell UtraTDDNeighboring
utraTDDNeighboringFreqConfId: This parameter is an association (also called

indirection or pointer). This parameter refers to the instance of the
UtraTDDNeighboringFreqConf MO that must be considered to retrieve all the
frequency information related to this instance of the MO
Page 182/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UtraTDDNeighboringCellRelation::utraTDDNeighboringFreqConfId
Parameter
utraTDDNeighboringFreqConfId
Object
Enb/ LteCell/ UtraTDDNeighboring/

Range & Unit
ServiceLink
LteCell/1 UtraTddNeighboring/0
UtraTddNeighboringFreqConf/0
Class/Category
C / Fixed
Value
Value is a link,
LteCell/1 UtraTddNeighboring/0
UtraTddNeighboringFreqConf/0
Feature
TEL-FID130120
5.2.2.8 AT CALL SETUP OR AN INCOMING MOBILITY

In this document, blind redirection means redirection without inter-RAT
measurement (or measurements on another target RAT). The blind redirection is
also called non-optimized redirection as TLA2.0 and LA1.0 heritage.
5.2.2.8.1 GOOD RADIO CONDITIONS:INTRAFREQUENCY(A3);INTER-RAT(B2):
Restriction: TLA2.1
ADue to UE restriction, measurementPurpose Blind-PS-Handover-To-UTRA-TDD,
t Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD, Meas-RedirectionTo-UTRA-TDD, Meas-Redirection-To-GERAN are not supported in TLA2.1.
c
all setup or an incoming mobility in target eNodeB, the eNodeB CallP configures
Event A3 (to detect an intra-frequency neighbor cell candidate); retrieves the UE
capabilities; launches the algorithm for calculation of CallP UE Capability
Information; launches the algorithm for RRC Measurement Configuration (TLA2.x
improvement); when the CallP UE Capability Information determines that the
Measurement Gaps (MG) are not required; configures Event A2_blind to detect a
serving cell degradation for blind redirection; configures Event B2 to detect interRAT UTRA-TDD (and/or GERAN) neighbor cell candidate with a degraded serving cell.
Page 183/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 32 : Inter RAT threshold for Event B2

B2_threshold1 => threshold1EutraRsrp or threshold1EutraRsrq (see section
5.2.3.3)
B2_threshold2 => threshold2UtraRscp (see section 5.2.3.3)
Entry in cell:
A2_blind addition;
B2's activation;
A3 addition
Join-0 initial
state
good radio
conditions on
serving
Algorithm for RRC

Algorithm for RRC
Measurement Gap
Addition of Event A3
(intra-frequency
neighbour cell candidate)
Algorithm for Calculation of
callpUECapabilityInformation
Algorithm for RRC

Algorithm for RRC
Measurement Gap
a1
2
activation of Event B2
(i-RAT neighbour candidate)
(UTRAN;Carrier_utran0)
Addition of Event
A2_blind (serving cell
degradation for blind
redirection)
activation of Event B2
(i-RAT neighbour candidate)
(GERAN;Carriers_geran0)
Case: one measurement

towards UTRAN
a2
Case: one measurement

towards GERAN
a2
2
a1
Case: many measurement

towards many RAT
b
2
activation of Many Event B2

(RAT_k; Carrier_k)
Join-2 "Wait for

intra-freq and
inter-RAT
measurements"
Page 184/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
eNodeB
MME

Measurement Configuration Phase No.1

Algorithm for RRC
Phase No.1
Algorithm for RRC

Measurement Gap
RRC Measurement

(Optional)
Algorithm for

Measurement Configuration Phase No.2

Algorithm for RRC
Phase No.2
Algorithm for RRC

Measurement Gap
UE
RRC Measurement
Configuration
eNodeB
MME
Figure 33 : Call Flow for mobility INTRA-FREQUENCY (A3;A2_BLIND);INTER-RAT(B2)

When the CallP UE Capability Information demonstrate the Measurement Gaps are
not required; CASE: MG NOT REQUIRED; INTRA-FREQUENCY (A3; A2_BLIND); INTERRAT (B2) applies ; the eNodeB CallP waits for an intra-frequency measurement
report or an inter-RAT measurement report i.e. waits for:
an RRC Measurement Report Event A2_blind (serving cell degradation for

blind redirection towards another RAT) or;
an RRC Measurement Report Event A3 (intra-frequency neighbor cell

candidate) or;
Page 185/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
o
an RRC Measurement Report Event B2 (inter-RAT neighbor cell candidate).
Figure 34 : waits for an intra-frequency measurement report or an inter-RAT measurement

report
Restriction: TLA2.1
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD, Meas-RedirectionTo-UTRA-TDD, Meas-Redirection-To-GERAN are not supported in TLA2.1
5.2.2.8.2 BLIND REDIRECTION:RECEPTION OF EVENT

A2_BLIND:
This section describes the case when the UE is entering bad radio conditions in
the source cell without sending to the eNodeB any measurement report on any
target cell [MG not required].
When the eNodeB CallP waits for intra-frequency measurements and receives an
RRC Measurement Report Event A2_blind (serving cell degradation for blind
redirection); the eNodeB CallP triggers the Algorithm for Control Procedures for
Mobility in order to determine the target RAT towards which the blind redirection
shall be launched.
Page 186/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 35 : Inter RAT threshold for Event A2_blind
Page 187/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
The thrsholds related to Event A2 Blind are the following:
ReportConfigEUTRA::thresholdEutraRsrp if you have chosen to trigger RSRP for
measuments via ReportConfigEUTRA::triggerQuantity set to rsrp
ReportConfigEUTRA::thresholdEutraRsrq if you have chosen to trigger RSRQ for
measuments via ReportConfigEUTRA::triggerQuantity set to rsrq
To see diagram in section 4.3.1.3 for configuration.
5.2.2.9 STATE DIAGRAM OF RADIO CONDITIONS
Page 188/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Figure 36 : State diagram of radio conditions TLA2.1
5.2.3 LTE TO UTRAN MEASUREMENTS CONFIGURATION
Page 189/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ENBEquipment
eNB
LTECell
- 63
UtraTddNeighbouringCellRelation/0
UtraFddNeighbouringCellRelation/0
63
UtraTddNeighbouring
rac
Cid/Lac/physCellidUTRAN/rac
utraFddNeighboringFreqConfId
- 15
UtraTddNeighbouringFreqConf/0
UtraFddNeighbouringFreqConf/0
priorityOfFreq
bandUtraFDDsupported by the UE
bandUtraTDD
RrmServices
priorityOfBandUtraFddexhibits the highest priority

priorityOfBandUtraTdd
UeMeasurementConf
-5
RRCMeasurementConf/1
RRCMeasurementConf/0
measQuantityUtraFdd
measQuantityUtraFdd
measQuantityUtraTdd
31
-31
MeasurementIdentityConf/0
MeasObject/0- 31
MeasObjectUUTRA
TRA
offsetFreqUTRA
ReportConfigUTRA
threshold1EutraRsrp
threshold2UtraRscp
triggerQuantity
To identify that an instance of

MeasurementIdentityConf is relating to a
mobility case to UTRA-FDD, the parameter
measurementPurpose shall be set to BlindRedirection-To-3GPP-RAT-Or-PS-HandoverTo-UTRA-TDD or Meas-Redirection-To-UTRATDD
ReportConfig MO: each instance defines the
characteristics of the measurements.
A specific instance shall be valorized in MIM
to configure the RRC measurement
dedicated to the event B2 for UTRA TDD.
List
ReportConfig/0- 31
ReportConfig
ReportConfigEUTRA
MeasurementIdentityConf MO: each instance

defines a RRC measurement identity and
refers to an instance of MeasObject MO and
an instance of ReportConfig MO. The
parameter measurementPurpose identifies the
goal of the measurement.
triggerTypeInterRAT
When the MG are required or not required,

the operator shall provide at least one
instance dedicated to B2 for UTRA- TDD.
ReportConfig MO: in TLA2.1, each instance
has a child ReportConfigUTRA. There are
other children defined in TLA2.1 because
intra-frequency measurements and interRAT measurements towards GERAN are
Hysteresis
timeToTrigger
Figure 37 : UTRA Event B2 Configuration
Restriction: TLA2.1
RrcMeasurementConf MO: this MO provides the configuration of measurement in

the UE and includes the following parameters:
o
A list of associations (indirections) towards instances of MO

MeasurementIdentityConf where each instance links one instance of MO
MeasObject with one instance of MO ReportConfig. By configuring
MeasurementIdentityConf it is possible to link more than one instances of MO
Page 190/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
MeasObject to the same instance of MO ReportConfig, as well as to link more
than one instances of MO ReportConfig to the same instance of MO MeasObject.
o
Quantity configurations: One quantity configuration is configured for intrafrequency measurements and one per RAT type. The quantity configuration
defines the measurement quantities and associated filtering used for all event
evaluation and related reporting of that measurement type. One filter can be
configured per measurement quantity.
measQuantityUtraTdd: measQuantityUtraTdd = ENUMERATED {PCCPCHRSCP } to configure the IE measQuantityUTRA-TDD of the QuantityConfigUTRA
SEQUENCE
{measQuantityUTRA-FDD,
measQuantityUTRA-TDD,
filterCoefficient}
RrcMeasurementConf::measQuantityUtraTdd
Parameter
measQuantityUtraTdd
Object

RrcMeasurementConf
Range & Unit
Enumerate
[pccpch-RSCP]
Class/Category
C / Fixed
Value
pccpch-RSCP
Feature
TEL-FID130120
filterCoefficientOfQuantityConfigUtra: filterCoefficientOfQuantityConfigUtra
DEFAULT fc4 to configure the IE filterCoefficient of the QuantityConfigUTRA
SEQUENCE
{measQuantityUTRA-FDD,
measQuantityUTRA-TDD,
filterCoefficient}
RrcMeasurementConf::filterCoefficientOfQuantityConfigUtra
Parameter
filterCoefficientOfQuantityConfigUtra
Object

RrcMeasurementConf
Range & Unit
Enumerate
fc17, fc19]
Class/Category
Value
fc4
Feature
TEL-FID130120
5.2.3.2 REPORTCONFIGUTRAN:
Page 191/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
The ReportConfigUTRA MO is a child of the ReportConfig MO: each instance
defines the characteristics of the measurements for the inter-RAT mobility to UTRATDD.
maxReportCells: 3GPP 36.331 [R08]. This parameter configures the IE

maxReportCells included in the IE ReportConfigInterRAT in the MeasConfig IE
ReportConfigUTRA::maxReportCells
Parameter
maxReportCells
Object

ReportConfigUTRA
Range & Unit
integer
[1..32] step = 1
Class/Category
Value
1 (Default:1)
Feature
FRS 76498

measurement report
ReportConfigInterRAT field descriptions

eventId
Choice of inter-RAT event triggered reporting criteria.
bN-ThresholdM
Threshold to be used in inter RAT measurement report triggering condition for event number
bN. If multiple thresholds are defined for event number bN, the thresholds are differentiated
by M.
timeToTrigger
measurement report.
Purpose
reportStrongestCellsForSON applies only in case reportConfig is linked to a measObject set
to measObjectUTRA or measObjectCDMA2000.
maxReportCells
Max number of cells, excluding the serving cell, to include in the measurement report. In case
purpose is set to reportStrongestCellsForSON only value 1 applies.
reportAmount
periodical. In case purpose is set to reportCGI or reportStrongestCellsForSON only value
1 applies.
ThresholdUTRA
utra-RSCP corresponds to P-CCPCH_RSCP in TS 25.123 for TDD and CPICH_RSCP in
TS 25.133 for FDD.
For utra-RSCP: The actual value is IE value 115 dBm. Integer value according to mapping
table in TS 25.123 and TS 25.133 , for TDD and FDD, respectively.
ThresholdGERAN
The actual value is IE value 110 dBm. . Integer value according to mapping table in TS
45.008 .
Page 192/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
hysteresis: TS36.331: This parameter configures the IE hysteresis included in

the IE ReportConfigInterRAT in the MeasConfig IE
This parameter defines the hysteresis used by the UE to trigger an intra-frequency

event-triggered measurement report.
ReportConfigUTRA::hysteresis
Parameter
hysteresis
Object

ReportConfigUTRA
Range & Unit
Float in dB
[0.0..15.0] step = 0.5
Class/Category
Value
1.0 see Engineering Recommendation
Feature
FRS 76498
Margin for HO Value to be confirmed.
Rule: Regarding hysteresis parameter

hysteresis is used in the following process: Event B2 (Serving becomes worse than
threshold1 and inter RAT neighbour becomes better than threshold2). The 3GPP
name is Hys in [R08]. Event A4 (Neighbour becomes better than threshold); Event
A5 (Serving becomes worse than threshold1 and neighbour becomes better than
threshold2);
Restriction: TLA2.1
Rule: hysteresis
For Automatic-Neighbour-Relation trigger, hysteresis should be set to the same
value of the hysteresis (corresponding to triggerQuantity = rsrp if it exists;
otherwise, corresponding to triggerQuantity = rspq) used for intra-frequencyhandover-trigger.
For Report-CGI trigger, hysteresis is not used but must not be unset.
Note: In TLA2.1, we only support Event B2 based LTE to UTRAN redirection for UE
that does not require measurement Gap.
Page 193/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: hysteresis
Be careful: Value is subject to modification according tests case results. Please keep
up to date regarding the apply value.
timeToTrigger : TS36.331: This parameter configures the IE TimeToTrigger

included in the IE ReportConfigInterRAT in the MeasConfig IE
triggered mode
ReportConfigUTRA::timeToTrigger
Parameter
timeToTrigger
Object

ReportConfigUTRA
Range & Unit
Enumerate in ms
[ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320,
ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120]
Class/Category
Value
ms100 (Default:ms5120)
Feature
FRS 76498
Rule: Regarding timeToTrigger parameter

Engineering Recommendation: timeToTrigger

Page 194/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility

RSRP
Target Cell
Serving Cell
8
7
6
5
4
3
2
1
0
5
timeToTrigger
10
15
20
reportingInterval
25
30
hysteresis
Time
35
Figure 38 : Hysteresis used to tuning HO decision, reportAmount = 4
reportInterval: TS36.331: This parameter configures the IE reportInterval

ReportConfigUTRA::reportInterval
Parameter
reportInterval
Object

ReportConfigUTRA
Range & Unit
[ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120,
Class/Category
Value
ms1024 See Engineering Recommendation
Feature
FRS 76498

periodical.[R08]
Engineering Recommendation: ReportConfigUTRA::reportInterval

The previouse default value was ms1024. We can keep this value for 20Mhz
bandwith configuration.
For 5Mhz bandwith configuration it is advis to set this parameter to ms240.
Page 195/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
reportAmount: TS36.331: This parameter configures the IE reportAmount

ReportConfigUTRA::reportAmount
Parameter
reportAmount
Object

ReportConfigUTRA
Range & Unit
Enumerate
Class/Category
Value
r1 (Default:r1)
Feature
FRS 76498
This parameter configures the number of periodical reports the UE has to transmit
Rule: Regarding reportInterval & reportAmount parameter

2>start the periodical reporting timer with the value of reportInterval as defined
5.2.3.3 THRESHOLDS FOR INTER-RAT MOBILITY AND

MEASUREMENTS FOR EVENT B2
Restriction:TLA2.1
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD, Meas-RedirectionFTo-UTRA-TDD, Meas-Redirection-To-GERAN are not supported in TLA2.1.
o
r
redirection, the UE shall:
Page 196/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1>
for UTRA, only trigger the event for cells included in the corresponding
measurement object; i.e these cells are identified in
UtraTddNeighbouringCellRelation MO
1>
consider the entering condition for this event to be satisfied when both
condition B2-1 and condition B2-2, as specified below, are fulfilled;
1>
consider the leaving condition for this event to be satisfied when condition
B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled;
Inequality B2-1 (Entering condition 1)
Ms + Hys < Thresh1
Inequality B2-2 (Entering condition 2)
Mn + Ofn Hys > Thresh2
Inequality B2-3 (Leaving condition 1)
Ms Hys > Thresh1
Inequality B2-4 (Leaving condition 2)
Mn + Ofn + Hys < Thresh2
The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.
is expressed in dBm in case of RSRP, or in dB in case of RSRQ. i.e
ReportConfigEUTRA::triggerQuantity setting.
Mn is the measurement result of the inter-RAT neighbour cell, not taking into
account any offsets. is expressed in dBm or dB, depending on the measurement
quantity of the inter-RAT neighbour cell. i.e
RrcMeasurementConf::measQuantityUtraTdd setting.
Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell
(i.e. offsetFreq as defined within the measObject corresponding to the frequency of
the inter-RAT neighbour cell). i.e MeasObjectUTRA::offsetFreqUTRA
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within
reportConfigInterRAT for this event). i.e ReportConfigUTRA::hysteresis
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined
within reportConfigInterRAT for this event).i.e
ReportConfigUTRA::threshold1EutraRsrp if you had chosen to use RSRP
ReportConfigUTRA::threshold1EutraRsrq if you had chosen to use RSRQ
Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined
within reportConfigInterRAT for this event). i.e
ReportConfigUTRA::threshold2UtraRscp or
ReportConfigUTRA::threshold2UtraEcN0 , depending of measQuantityUtrTdda
Ofn, Hys are expressed in dB.
Thresh1 is expressed in the same unit as Ms.
Thresh2 is expressed in the same unit as Mn.
Page 197/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Measurement
eventB2
Mn
Hys
Mn - Hys
Thresh2
TimeToTrigger
Thresh1
Ms + Hys
Hys
Ms
t
Figure 39 : Event B2 : Entering conditions
triggerTypeInterRAT: TS36.331: This parameter configures the IE triggerType

included in the IE ReportConfigInterRAT in the IE MeasConfig
ReportConfigUTRA::triggerTypeInterRAT
Parameter
triggerTypeInterRAT
Object

ReportConfigUTRA
Range & Unit
Enumerate
[eventB1, eventB2 ]
Class/Category
C / Fixed
Value
eventB2
Feature
FRS 76498
Page 198/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
threshold1EutraRsrp: TS36.331: This parameter configures the IE Threshold

EUTRA RSRP included in the IE ReportConfigInterRAT in the MeasConfig IE.
This IE should be present if the parameter triggerTypeInterRAT is set to event
B2. Otherwise it should be absent.
ReportConfigUTRA::threshold1EutraRsrp
Parameter
threshold1EutraRsrp
Object

ReportConfigUTRA
Range & Unit
integer
[0..97] step = 1
Class/Category
Value
N.A
Feature
FRS 76498
Status: this optional attribute is unset

Note: The value 0 matching with the value -140 dBm and the value 97 matching with
the value -44 dBm and so on. (40 matching to minus101_to_minus100)
Restriction: TLA2.1
Due t to UE restriction, measurementPurpose Blind-PS-Handover-To-UTRA-TDD,
h
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD,
Meas-Redirectionr
To-UTRA-TDD,
Meas-Redirection-To-GERAN are not supported in TLA2.1.
e
shold1EutraRsrq: TS36.331: This parameter configures the IE Threshold
EUTRA RSRQ included in the IE ReportConfigInterRAT in the MeasConfig IE.
This IE should be present if the parameter triggerTypeInterRAT is set to event
B2. Otherwise it should be absent.
ReportConfigUTRA::threshold1EutraRsrq
Parameter
threshold1EutraRsrq
Object

ReportConfigUTRA
Range & Unit
integer
[0..34] step = 1
Class/Category
Value
N.A
Feature
FRS 76498
Page 199/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: TLA2.1
h
oDue to UE restriction, measurementPurpose Blind-PS-Handover-To-UTRA-TDD,
l Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-To-UTRA-TDD, Meas-RedirectiondTo-UTRA-TDD, Meas-Redirection-To-GERAN are not supported in TLA2.1.
2
threshold2UtraRscp: TS36.331: This parameter configures the IE utra-RSCP

included in the IE ReportConfigInterRAT in the MeasConfig IE. This IE should be
present if the parameter triggerTypeInterRAT is set to eventB2. Otherwise it
should be absent.
ReportConfigUTRA::threshold2UtraRscp
Parameter
threshold2UtraRscp
Object

ReportConfigUTRA
Range & Unit
Enumerate in dBm
[less_than_minus120, minus_x_to_minus_x-1 (x from 120 to
26), more_than_minus25]
Class/Category
Value
N.A
Feature
FRS 76498

threshold2UtraRscp corresponds to P-CCPCH_RSCP in TS 25.123 for TDD.
This measurement is for handover evaluation, DL open loop power control, UL open
loop power control and for the calculation of pathloss.
The P-CCPCH_RSCP intra-frequency relative accuracy is defined as the PCCPCH_RSCP measured from one cell compared to the P-CCPCH_RSCP measured
from another cell on the same frequency.
The reporting range for P-CCPCH RSCP is from -120 ...-25 dBm.
In table below mapping of the measured quantity is defined. Signalling range may be
larger than the guaranteed accuracy range.
Reported value
P-CCPCH RSCP_LEV _-05
P-CCPCH RSCP_LEV _89

Measured quantity value

P-CCPCH RSCP <-120
-120 P-CCPCH RSCP < -119

-25 P-CCPCH RSCP
Unit
dBm
dBm
dBm
dBm
dBm
dBm
Page 200/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.3 EUTRAN-TO-UTRAN-TDD PS HANDOVER
The feature 105474 introduces the Eutran to UTRAN-TDD Packet Switched (PS)
handover mobility mechanism in RRC connected mode that allows continuous service
to a target UMTS cell. Compared with a redirection, the PS handover aims at
ensuring a minimum interruption time for the RRC connection (thanks to the resource
allocation in the target RNC during the preparation phase).
In TLA2.1.3, only blind eUTRAN-to-UTRAN-TDD PS handover without any inter-RAT
measurements is supported and the triggering for PS handover is based on
degradation of LTE radio conditions in the source cell below a pre-defined threshold
and relies on the support of RRC measurement Event A2 as described in earlier
sections of this volume. PS handover with inter-RAT measurements is expected to be
supported in a future release and will replace blind PS handover.
Restriction:
Blind Inter-RAT PS Handover from eUTRAN towards UTRAN-TDD is in total restriction
in TLA2.1.3. The restriction is due to the late UE availability This restriction is expected
to be removed in a future release The blind trigger will be replaced with measurementtriggered PS HO in a future release
voiceOverIpEnabled: This flag enables or not the PS handover to UTRA TDD for Voice
Over IP. If set to true on source eNB, PS handover to this UTRA TDD target cell will
be performed for VoIP since the target cell supports VoIP. If set to False on source
eNB, there will be no PS handover to UTRA TDD for this Voice over IP
UtraTddNeighboringCellRelation::voiceOverIpEnabled
Parameter
voiceOverIpEnabled
Object
Enb/ UtraTddNeighboring/ UtraTddNeighboringCellRelation
Range & Unit
Boolean
[True, False]
Class/Category
Value
N.A
Feature
FRS 105474
Page 201/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction:
PS Handover to UTRAN for non-VoIP data bearers is in the scope of future
release. Parameter voiceOverIpEnabled is expected to be supported in a future
release when UTRAN cell capability supports VoIP bearers.
5.3.1 BLIND PS HANDOVER ACTIVATION AND MEASUREMENT

CONFIGURATION
In order for blind PS handover to be activated, the conditions described in this section
are required. If any of these conditions are not met, then Event A2 used to trigger
blind PS Handover will not be configured and thus blind PS handover will not be
triggered.
1. Feature activated: parameter isBlindPsHoToUtraTddAllowed is set to TRUE.
isBlindPsHoToUtraTddAllowed: Activation flag for feature eUTRAN to UTRAN

TDD Inter-RAT Mobility Blind PS Handover
ActivationService::isBlindPsHoToUtraTddAllowed
Parameter
isBlindPsHoToUtraTddAllowed
Object
Enb/ActivationService
Range & Unit
Boolean
[True, False]
Class/Category
C / Fixed
Value
See engineering recommendation (False is a default value)
Feature
FRS 105474
Engineering Recommendation: isBlindPsHoToUtraTddAllowed

Parameter isBlindPsHoToUtraTddAllowed should be set to TRUE inTLA 2.1.3.
LTEconfigurations with adjacent UTRAN networks.
Page 202/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction:
Parameter isBlindPsHoToUtraTddAllowed is used only in TLA2.1.3 for activation
of blind PS Handover. This parameter will not be used in a later release when
blind PS handover is replaced by PS handover with inter-RAT measurements.
2. Appropriate UE capabilities:
UE must support the capability to perform PS Handover to UTRAN;
UE must support UTRA-TDD and one or more UTRA-TDD bands
corresponding to provisioned neighbor UTRA-TDD cell(s) with the same
UTRA-TDD band(s), that is, there must be a match between a UTRA-TDD
band
in
the
UE
capabilities
with
a
UtraTddNeighboringFreqConf::bandUtraTdd instance associated with at
least one UTRA-TDD cell neighbor.
3. UTRA-TDD provisioned neighbor cells correspond to an RNC with an administrative
state which is unlocked and supports PS Handover:
RncAccess::administrativeState = UNLOCKED
RncAccess::psHandoverUtraEnabled = TRUE.
psHandoverUtraEnabled: Flag to indicate whether or not the neighbour RNC is

able to support the PS handover from eUTRAN to UTRAN. True indicates that the
neighbour RNC is capable to support the PS handover from eUTRAN to UTRAN.
RncAccess::psHandoverUtraEnabled
Parameter
psHandoverUtraEnabled
Object
Enb/ UtranAccessGroup/ RncAccess
Range & Unit
Boolean
[True, False]
Class/Category
C / Fixed
Value
True See engineering recommendation
Feature
FRS 105474
Engineering Recommendation: psHandoverUtraEnabled

Parameter psHandoverUtraEnabled should be set to TRUE whenever parameter
isBlindPsHoToUtraTDDAllowed is set to TRUE in an TLA2.1.3 configuration
with an adjacent UTRAN network. As a consequence, if the parameter is FALSE
under this condition, a warning may be raised.
Page 203/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
4. Since only blind inter-RAT PS handover is supported in TLA2.1.3, the eNB will use
intra-frequency measurement reports with event trigger A2 for handover triggering. In
the case of blind inter-RAT PS handover to 3G, the specific measurement purpose
Blind-PS-Handover-To-UTRA-TDD (if only blind PS Handover allowed

activation is true, but blind redirection allowed activation is not true) or
Blind-Redirection-To-3GPP-RAT-Or-PS-Handover-ToUTRA-TDD (if both PS

Handover allowed activation is true and blind redirection allowed activation is
true)
The parameter MeasurementIdentityConf::measurementPurpose

configured for the above purposes as described in section 4.1.2.5.
is
to
be
5.3.2 BLIND PS HANDOVER TRIGGERING AND TARGET CELL

SELECTION
When an RRC measurement report for Event A2 is received with a measurement
purpose set to Blind-PS-Handover-To-UTRA-TDD or Blind-Redirection-Or-PSHandover-To-UTRA-TDD, and conditions in section 5.3.1 are met such that blind PS
Handover is possible, then the Target-UTRAN-Cell is selected based on the following
criteria:
-
the target cell is a provisioned UTRA-TDD neighbor of the serving LTE cell. An
LTE cell can have up to 3 provisioned UTRA-TDD neighboring cells, with each
UTRA-TDD neighboring assigned to a different UTRA-TDD band.
the RNC associated with the target cell supports PS Handover to UTRAN, that is,
RncAccess::psHandoverUtraEnabled = TRUE. The rncAccessId is an
association parameter (also called indirection or pointer). which refers to the
instance of RncAccess MO that must be considered to retrieve all the information
related to the target RNC controlling the UTRA TDD cell modeled by this instance
of the MO UtraTddNeighboringCellRelation.
UtraTddNeighboringCellRelation::rncAccessId
Parameter
rncAccessId
Object
Enb/ UtraTddNeighboring/ UtraTddNeighboringCellRelation
Range & Unit
ServiceLink
Class/Category
C / Fixed
Value
UtranAccessGroup/0 RncAccess/0
Feature
105474
the UE supports the UTRA-TDD band of the target cell.
Page 204/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
-
the target cell has the highest priority UTRA-TDD band (among the other potential
target
cells)
according
to
the
parameter
setting
of
UtraTddNeighboringFreqConf::priorityOfBandUtraTdd
UtraTddNeighboringFreqConf::priorityOfBandUtraTdd
Parameter
Object
Enb/UtraTddNeighboring/UtraTddNeighboringFreqConf
Range & Unit
Integer
[0 - 7] step = 1
Class/Category
Value
0 See engineering recommendation
Feature
FRS 105474
Lowest priority is 0. Highest priority is 7.
Engineering Recommendation: priorityOfBandUtraTdd

In a TLA2.1.3 configuration, parameter priorityOfBandUtraTdd should be set
whenever multiple bands will be supported in the UE and provisioned UTRA-TDD
neighbor cells to optimize target cell selection.
Restriction:
Parameter priorityOfBandUtraTdd is used only for blind PS Handover in
TLA2.1.3. This parameter is not expected to be used in future releases when the
blind mechanism is replaced by inter-RAT measurements.
With the successful selection of a Target-UTRAN-Cell and Target-RNC, the eNB can
trigger the blind PS Handover towards the UTRAN.
5.3.3 CONTROL OF PS HANDOVER

The eNodeB provides the following functions for EUTRA-to-UTRAN-TDD PS
handover:
(1) EUTRA-to-UTRAN handover preparation phase
(2) EUTRA-to-UTRAN handover execution phase
(3) EUTRA-to-UTRAN handover completion phase
Page 205/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
Source ENB
Source
MME/SGW
Target RNC
Target
SGSN
DL Data
RRC MeasurementReport
Decision of mobility is
blind_ps_handover
or ps_handover
S1 HANDOVER REQUIRED
MME UE S1AP ID
eNB UE S1AP ID
Handover Type
Cause
Target ID
Direct Forwarding Path Availability
Source to Target Transparent Container
Forward
relocation
request
RANAP RELOCATION REQUEST
Setup of UE context and
RANAP RELOCATION REQUEST ACKNOWLEDGE
Ready to buffer forwarded
packets
Forward
relocation
response
S1AP HANDOVER COMMAND

RRC Mobility From Eutra Command
Start forwarding DL packets

to Target eNB
Detach from old LTE cell and
synchronize to new
TDSCDMA cell
Handover Execution
MME UE S1AP ID
eNB UE S1AP ID
Handover Type
NAS Security Parameters from E-UTRAN
E-RABs Subject to Forwarding List
>E-RABs Subject to Forwarding Item IEs
>> E-RAB ID
>> DL Transport Layer Address
>> DL GTP-TEID
>> UL Transport Layer Address
>> UL GTP-TEID
E-RABs to Release List
Target to Source Transparent Container
Criticality Diagnostics
DL Data
DL Data Forwarding (possibly through SGW/SGSN)

UTRAN L1 Access
RANAP RELOCATION DETECT
RRC HandoverToUtranComplete
Handover Preparation
measId
measResultServing
neighbouringMeasResults

DL Data
Start buffering packets
from IuPS-U
RANAP RELOCATION COMPLETE
DL Data
DL Data Forwarding
Path switch
DL Data
arker)
(End M
End Mar
ker po
ss
Handover Completion
ta
DL Da
Transmit forwarded packets

before IuPS
ibly thro
ugh SGW
/S
GSN
Routeing Area Update Procedure
S1AP UE CONTEXT RELEASE COMMAND
S1AP UE CONTEXT RELEASE COMPLETE

UE
Source ENB
Release data forwarding

resources
Target RNC
Source
MME/SGW
Target
SGSN
Figure 40: Call Flow for EUTRAN-to-UTRAN-TDD PS Handover
Page 206/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
1. Handover Preparation:
The handover decision to trigger PS handover is the result of the measurement report
analysis. Upon PS Handover triggering, the eNB will enter the preparation phase by
sending the S1 HANDOVER REQUIRED message to the Source MME. This
message includes the following parameters:
> Target RNC-ID: selected by handover decision algorithm, consisting of:
RncAccess::plmnMCC + plmnMNC
plmnMobileCountryCode identifies the country covered and is used to help

identify the Target-RNC selected for PS handover. See definition of PLMN (Public
Land Mobile Network in LPUG Volumes 1 and 5).
plmnMobileCountryCode: A Public Land Mobile Network is uniquely identified by its
PLMN identifier. PLMN-Id consists of Mobile Country Code (MCC) and Mobile
Network Code (MNC)
PLMN-Id = MCC || MNC
Refer to TS 23.003
MCC(36.331): SEQUENCE (SIZE (3)) OF INTEGER (0..9), The first element
contains the first MCC digit, the second element the second MCC digit and so on
RncAccess::plmnMobileCountryCode
Parameter
Object
Enb/UtranAccessGroup/RncAccess
Range & Unit
BcdString
stringMinLength = 3
string Length = 3
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 96732,103612
plmnMobileNetworkCode identifies the operator covered and is used to help identify

the Target-RNC selected for PS handover. See definition of PLMN (Public Land
Mobile Network in LPUG Volumes 1 and 5).
plmnMobileNetworkCode: A Public Land Mobile Network is uniquely identified by its
PLMN identifier. PLMN-Id consists of Mobile Country Code (MCC) and Mobile
Network Code (MNC)
PLMN-Id = MCC || MNC
Refer to TS 23.003
MNC(36.331): SEQUENCE (SIZE (2..3)) OF INTEGER (0..9), The first element
contains the first MNC digit, the second element the second MNC digit and so on
Page 207/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RncAccess::plmnMobileNetworkCode
Parameter
Object
Range & Unit
BcdString
stringMinLength = 2
string Length = 3
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 96732,103612
RncAccess::rncId (used if RNC identity has value <= 4095)
rncId uniquely identifies the Target RNC in the UTRAN for LTE-UMTS handover as
selected by the eNB. Set for an rncId value less than or equal to 4095.
plmnMobileNetworkCode: TS36.413: RNC-ID is an INTEGER (0..4095) and if the

Extended RNC-ID IE is included in the Target ID IE, the RNC-ID IE shall be ignored
Target ID: it identifies the target for the handover. The target ID is the RNC-ID for
SAE/LTE-UMTS handover as selected by the ENB.
The Target ID when set to Target RNC-ID includes RNC-ID
RncAccess::rncId
Parameter
rncId
Object
Range & Unit
Integer
[0 - 4095] step = 1
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 96732,103612
RncAccess::extendedRncId (used if RNC identity has value > 4095)

TS36.413: Extended RNC-ID is an INTEGER (4096..65535), used to identify
an RNC and used if the RNC identity has a value larger than 4095.
The Target ID when set to Target RNC-ID includes Extended RNC-ID
extendedRncId uniquely identifies the Target RNC in the UTRAN for LTE-UMTS
handover as selected by the eNB. Set for an rncId value greater than 4095.
Page 208/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RncAccess::extendedRncId
Parameter
extendedRncId
Object
Range & Unit
Integer
[4096 - 65535] step = 1
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 96732,103612
UtraTddNeighboringCellRelation::lac + rac
lac is the Location Area Code. TS36.413: Target ID: it identifies the target for the
handover. The target ID is the RNC-ID for SAE/LTE-UMTS handover as selected
by the ENB. The Target ID when set to Target RNC-ID includes LAI: LAI is used to
uniquely identify a Location Area. The LAI is made of the PLMN identity and of the
LAC. Semantics description: 0000 and FFFE not allowed
UtraTddNeighboringCellRelation::lac
Parameter
lac
Object
Enb/UtraTddNeighboring/UtraTddNeighboringCellRelation
Range & Unit
OctetString
stringMinLength = 2
string Length = 2
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 105474
Restriction:
stringLength = 2 corresponds to 2 hex characters (8 bits). Therefore,.the range for
parameter lac is restricted to 1...255 in TLA2.1.3. This will restrict the operator
from using the full range of location area codes for LTE to UTRAN PS handover.
This restriction is expected to be removed in a future releasewhen stringLength is
increased to 4.
rac is the Routing Area Code. TS36.413: RAC is used to identify a Routing Area
within a Location Area. It is used for PS services
Page 209/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
The Target ID when set to Target RNC-ID includes RAC.
UtraTddNeighboringCellRelation::rac
Parameter
rac
Object
Range & Unit
OctetString
stringMinLength = 1
string Length = 1
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 105474
Restriction:
stringLength = 1 corresponds to 1 hex character (4 bits). Therefore, the range for
parameter rac is restricted to 0...15 in TLA2.1.3. This will restrict the operator
from using the full range of routing area codes for LTE to UTRAN PS handover.
This restriction is expected to be removed in a future release when stringLength is
increased to 2.
Rule:
The UMTS Location Area Code (LAC) and Routing Area Code (RAC) must
be provisioned to map to the LTE Tracking Area Code (TAC) in the network.
That is, the UMTS LAC/RAC and the LTE TAC must overlay each other.
> Direct Forwarding Path Availability: RncAccess::directFwdPathAvailability

directFwdPathAvailability is a flag to indicate whether or not a direct data
forwarding path for downlink data is available with the target RNC. True indicates
that a direct path to the RNC is available. False indicates indirect data forwarding
in which case downlink data is forwarded through the core network (SGW and
possibly SGSN). Note that PDCP Sequence Number (SN) preservation does not
apply to inter-RAT data forwarding (for a discussion of PDCP sequence
numbering, refer to Volume 3). Only SDUs for which a PDCP sequence number
was not assigned will be forwarded towards the target system. This implies that
Page 210/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
the TLA2.1 data forwarding solution does not guarantee lossless delivery of
packets.
RncAccess::directFwdPathAvailability
Parameter
Object
Range & Unit
Boolean
[True, False]
Class/Category
C / I&C OMC
Value
True See engineering recommendation
Feature
FRS 96732, 103612
Engineering Recommendation: directFwdPathAvailability

Parameter directFwdPathAvailability should be set to False if direct data
forwarding is not supported on the Target RNC. Otherwise,, it should be set to
True as a preferred mechanism for data forwarding.
Restriction:
The TLA2.1 data forwarding solution does not guarantee lossless delivery of
packets.
> Source RNC To Target RNC Transparent Container. This is the same Transparent
Container which is used by the UMTS network via the RANAP protocol for the RNC
interface with the SGSN/core network. It is also used for LTE to UMTS handover to
allow inter-operability with the target RNC in the UMTS network. This Transparent
Container includes:
Target Cell-ID: UtraTddNeighboringCellRelation::cId
cId (Cell identifier) uniquely identifies one cell in one Target RNC in the UTRAN
for LTE-UMTS handover as selected by the eNB.
Page 211/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UtraTddNeighboringCellRelation::cId
Parameter
cId
Object
Range & Unit
Integer
[0 - 65535] step = 1
Class/Category
C / I&C OMC
Value
O.D.
Feature
FRS 105474
Last Visited LTE Cell Information, which includes:

o
PLMN: LteCell::plmnMCC + plmnMNC
Cell Identity: Enb::macroEnbId + LteCell::relativeCellIdentity
Cell Type: LteCell::cellSize
The UE capabilities are also passed to the target RNC in theTransparent Container.
The UE capabilities are retrieved by the Source eNB before the handover is triggered
sometime after the UE entered the RRC_Connected mode.
Once the S1 HANDOVER COMMAND is sent to the Source MME, timer
S1RelocPrepForPsHandoverToUtra is started. The duration of this timer is set by a
MIM parameter with the same name:
tS1RelocPrepForPsHandoverToUtra: TS36.413: When the source ENB sends the

S1AP HANDOVER REQUIRED message for the PS handover to Utran , it shall
start the timer tS1RelocPrepForPsHandoverToUtra.
PsHoToUtraTimersConf::tS1RelocPrepForPsHandoverToUtra
Parameter
tS1RelocPrepForPsHandoverToUtra
Object
Enb/ S1AccessGroup/ S1Timers/ PsHoToUtraTimersConf
Range & Unit
Integer ms
[1 10000] step = 1
Class/Category
Value
5000
Feature
FRS 105474
This timer is defined in 3GPP 36.413 as TS1-RELOCprep.
When the call admission allocation on the UTRAN target is done, the Source MME
ends the PS handover preparation to the Source eNB by sending the S1 HANDOVER
COMMAND message which ends the preparation phase. This message contains a
Page 212/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Target to Source Transparent Container.
S1RelocPrepForPsHandoverToUtra is stopped.
At
this
point,
the
timer
2. Handover Execution:
The Target to Source transparent container has the RRC MOBILITY FROM EUTRA
Command message, built by the Target RNC, which contains all radio related
information that the UE needs for handover. The Source eNB sends this message
transparently to the UE. At this point, timer S1RelocOverallForPsHandoverToUtra
is started. The duration of this timer is set by a MIM parameter with the same name:
tS1RelocOverallForPsHandoverToUtra: TS36.413: Upon reception of the S1AP

HANDOVER COMMAND message (in case of PS handover to UTRA ) the source
eNB shall start the timer tS1RelocOverall (for PS HO set by
tS1RelocOverallForPsHandoverToUtra).
PsHoToUtraTimersConf::tS1RelocOverallForPsHandoverToUtra
Parameter
tS1RelocOverallForPsHandoverToUtra
Object
Enb/ S1AccessGroup/ S1Timers/ PsHoToUtraTimersConf
Range & Unit
Integer ms
[1 10000] step = 1
Class/Category
Value
5000
Feature
FRS 105474
This timer is defined in 3GPP 36.413 as TS1-RELOCoverall.
If the S1 HANDOVER COMMAND also contains at least one E-RAB subject to

forwarding with a DL Transport Layer Address, then data is forwarded either over the
S1-U (indirect forwarding) or directly towards the RNC (direct forwarding) depending
on the parameter setting of RncAccess:: directFwdPathAvailability.
Upon reception of the RRC MOBILITY FROM EUTRA COMMAND message, the UE
switches from the old LTE cell and sends the RRC HANDOVER to UTRAN
COMPLETE message. The target RNC requests the target SGSN to perform the path
switch by sending the RANAP RELOCATION COMPLETE message which ends the
execution phase.
3. Handover Completion:
The target SGSN propagates the end of PS handover to the Source MME by sending
the S1 UE CONTEXT RELEASE COMMAND message. At this point, timer
S1RelocOverallForPsHandoverToUtra is stopped. Once the user plane conditions
are met, the Source eNB confirms the PS handover completion by sending the S1 UE
CONTEXT RELEASE COMPLETE message.
Page 213/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.3.3.1 FAILURE CASES
Failure cases result from the triggers described in this section.
- reception of HANDOVER PREPARATION FAILURE:
The handover procedure is aborted in the eNB and the UE call context is returned to
the
state
before
the
handover
trigger
was
received.
Timer
tS1RelocPrepForPsHandoverToUtra is stopped.
- expiry of timer tS1RelocPrepForPsHandoverToUtra:
When the source eNB sends the S1 HANDOVER REQUIRED message to the serving
MME, it starts timer tS1RelocPrepForPsHandoverToUtra. If the timer expires before a
response is received, then the source eNB sends the S1 HANDOVER CANCEL
message to the MME and cancels the handover preparation procedure. The UE call
context is retured to the state before the handover trigger was received.
-
partial failure of Handover Preparation:
The Target RNC may accept some E-RABs but reject others. At the Source eNB, if at
least one non-GBR E-RAB succeeds, the handover execution will be performed.
Rejected E-RABs will be contained in the E-RABs To Release List IE. VoIP bearers
are expected to be contained in the E-RABs to Release List IE in TLA2.1.3. Rejected
E-RABs will not be subject to data forwarding and will be released (along with the
other E-RABs) in the Source eNB upon reception of the S1 UE CONTEXT RELEASE
COMMAND.
- UE MEASUREMENT REPORT received during preparation, abort PS handover
In TLA2.1.3, an intra-eNB or inter-eNB X2 handover can abort inter-RAT PS handover
preparation because intra-LTE mobility is favored over inter-RAT PS handover. If a
UE Measurement Report related to measurement purpose Intra-frequency-handover
trigger is received from the UE during blind inter-RAT PS handover preparation, then
the inter-RAT PS handover to UTRAN is aborted and the intra-eNB or inter-eNB X2
handover is triggered.
- expiry of timer tS1RelocOverallForPsHandoverToUtra:
The handover preparation and execution phases are performed, but this timer expires
before reception of the S1 UE Context Release Command message.
When the source eNb sends the S1 HANDOVER COMMAND, it starts timer
tS1RelocOverallForPsHandoverToUtra. If the S1 UE CONTEXT RELEASE
COMMAND message is not received from the MME before the timer expires, then the
eNB will send the S1 UE CONTEXT RELEASE COMMAND message to the MME to
start the release of the UE context by sending the S1 UE CONTEXT RELEASE
REQUEST message to the MME.
Page 214/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
5.3.4 MIM MODEL FOR EUTRAN-TO-UTRAN-TDD PS

HANDOVER
Enb
utraTddNeighboring
CellRelationIdList
[0..1]
[1..3]
UtranAccessGroup
(new MO)
isPsHoToUtraTddAllowed
isBlindPsHoToUtraTddAllowed
ActivationService
[1..8]
(modified MO)
RncAccess
(new MO)
rdnId
uniqueName
administrativeState
availabilityStatus
operationalState
rncId
extendedRncId
psHandoverUtraTddEnabled
psHoToUtraTimersConfId
LteCell
(modified MO)
1...3
utraFddNeighboringCellRelationIdList
psHoToUtraFddTimersConfId
S1AccessGroup
S1Timers
(modified MO)
rdnId
tS1RelocPrepForPsHandoverToUtra
tS1RelocOverallForPsHandoverToUtra
[0..2]
DedicatedConf
PsHoToUtra
TimersConf
(new MO)
rncAccessId
dataForwardingForPsHoToUtraTddEnabled
psHoToUtraTddEnabled
rdnId
uniqueName
RadioBearerConf
physCellIdUTRA
(modified MO)
utraTddNeighboringFreqConfId
lac
rac
voiceOverIpEnabled
rncAccessId
UtraTddNeighboring
rdnId
carrierFreq
[0..1] UtraTddNeighboring
[0..64]
CellRelation
priorityOfFreq
(modified MO)
bandUtraTdd
[0..16]
utraFddNeighboringFreqConfId
UtraTddNeighboring
FreqConf
(modified MO)
[0...1]
CellReselectionConf
UtraTdd
Figure 41: MIM Model for EUTRAN-to-UTRAN-TDD PS Handover
Page 215/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
dataForwardingForPsHoToUtraTddEnabled:This flag enables or not the DL data

forwarding for this Radio Bearer in case of PS HO to UTRA-TDD. If set to true on
source eNB, DL data forwarding will be performed. If set to False on source eNB,
there will be no DL data forwarding.
RADIOBEARERCONF::dataForwardingForPsHoToUtraTddEnabled
Parameter
dataForwardingForPsHoToUtraTddEnabled
Object
Enb/DedicatedConf/RadioBearerConf
Range & Unit
Boolean
[True, False]
Class/Category
Value
False
Feature
FRS 105474
Restriction:
Parameter dataForwardingForPsHoToUtraTddEnabled is not used in TLA2.1.
dataForwardingForPsHoToUtraTddEnabled: This flag enables or not the PS

handover to UTRA TDD for this Radio Bearer. If set to true on source eNB, PS
handover to UTRA TDD will be performed. If set to False on source eNB, there will
be no PS handover to UTRA TDD for this Radio Bearer.
RADIOBEARERCONF::psHoToUtraTddEnabled
Parameter
psHoToUtraTddEnabled
Object
Enb/DedicatedConf/RadioBearerConf
Range & Unit
Boolean
[True, False]
Class/Category
Value
N.A
Feature
FRS 105474
Restriction:
Parameter psHoToUtraTddEnabled is not used in TLA2.1
Page 216/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
6 EUTRAN TO GERAN INTER-RAT MOBILITY

FOR LTE (USE CASES & CONTROL
PROCEDURES)
The feature PM84807 provides the basic mobility capability to ensure cell reselection
and packet service continuity for a dual-mode UE moves away from LTE coverage
area to a GERAN coverage area. The feature PM84807 covers LTE to GERAN
mobility capability for a dual-mode UE in both RRC idle and connected modes.
6.1 RRC IDLE MODE MOBILITY:
The feature PM84807 provides basic mobility capability for UE moving from LTE radio
coverage to GERAN radio coverage. The benefit from the LTE-to-GERAN mobility in
RRC_IDLE is to allow a LTE/GERAN capable user to recover GERAN coverage, as
soon as it gets available, i.e. radio conditions are sufficiently good.
GSM_Connected
CELL_DCH
Handover
E-UTRA
RRC_CONNECTED
CELL_FACH
Reselection
GPRS Packet
transfer mode
CCO with
optional
NACC
CELL_PCH
URA_PCH
CCO,
Reselection
Connection
establishment/release
Connection
UTRA_Idle
Handover
Reselection
Reselection
E-UTRA
RRC_IDLE
Connection
Reselection
GSM_Idle/GPRS
Packet_Idle
CCO, Reselection
Figure 42 : Reselection from eUTRAN to GERAN
Cell reselection E-UTRA-TDD to GERAN is internal to the UE and controlled by

system information parameters provided in SystemInformationBlockType7 and
SystemInformationBlockType3. The UE applies inter-RAT cell reselection criteria as
Page 217/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
described in 6.1.2.1 (3GPP 36.304). The UE selects a GERAN cell that fulfills criteria
defined in 6.1.2.4 (3GPP 36.304 section 5.2.4.5)
From eNodeB perspective, cell reselection to GERAN is supported with SIB7. Cell
reselection to GERAN is enhanced with SIB3 (RRC IE speedStateReselectionPars).
6.1.1 CELL RESELECTION ACTIVATION

Like in 4.1.2.1, at the same place in the data model, the parameter below is in the
scope of mobility activation and information options. Be careful, it is mandatory to
activate it, for mobility related to. It is Fixed category and it is C class parameter:
ActivationService:: isCellReselectionToGeranAllowed
Parameter
isCellReselectionToGeranAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
false
Feature
This parameter is an activation flag to set whether the EUTRAN to GERAN cell
reselection is enabled or disabled.
Parameters above are used to control feature licensing
These parameters are used to manage testing and release upgrade of a new
base (i.e., non-optional) feature and therefore the parameter should be deleted in the
next release (assuming the feature is successfully introduced in this release!)
6.1.2 CELL RESELECTION ALGORITHM DESCRIPTION

SIB7 parameters.
Page 218/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
SystemInformationBlockType7 field descriptions
carrierFreqsInfoList
Provides a list of neighbouring GERAN carrier frequencies, which may be monitored for
neighbouring GERAN cells. The GERAN carrier frequencies are organised in groups and
the cell reselection parameters are provided per group of GERAN carrier frequencies.
carrierFreqs
The list of GERAN carrier frequencies organised into one group of GERAN carrier
frequencies.
commonInfo
Defines the set of cell reselection parameters for the group of GERAN carrier frequencies.
t-ReselectionGERAN
Parameter TreselectionGERAN in TS 36.304.
t-ReselectionGERAN-SF
Parameter Speed dependent ScalingFactor for TreselectionGERAN in TS 36.304 [4]. If the
field is not present, the UE behaviour is specified in TS 36.304 .
ncc-Permitted
Field encoded as a bit map, where bit N is set to "0" if a BCCH carrier with NCC = N-1 is
not permitted for monitoring and set to "1" if the BCCH carrier with NCC = N-1 is permitted
for monitoring; N = 1 to 8; bit 1 of the bitmap is the leading bit of the bit string.
q-RxLevMin
Parameter Qrxlevmin in TS 45.008. The actual value of Qrxlevmin in dBm = (IE value * 2)
115.
p-MaxGERAN
Maximum allowed transmission power for GERAN on an uplink carrier frequency, see TS
45.008 [28]. Value in dBm. Applicable for the neighbouring GERAN cells on this carrier
frequency. If pmaxGERAN is absent, the maximum power according to the UE capability is
used.
threshX-High
Parameter "Threshx,high" in TS 36.304.
threshX-Low
Parameter "Threshx,low" in TS 36.304.
6.1.2.1 CELL SELECTION CRITERION

The cell selection criterion S (Calculated by the UE) is fulfilled when:
Srxlev > 0
Where:
Where:
Page 219/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Srxlev
Qrxlevmeas
Qrxlevmin
Qrxlevmino
ffset
Pcompe
nsation
Pemax
Pumax
Calclated by
the UE
Measured by
the UE
Cell Selection RX level value (dB).
CellReselection
ConfGERAN::q
RxLevMin
CellSelectionR
eselectionConf
::qRxlevminoff
set
Minimum required RX level in the cell (dBm).

Broadcasted in SIB 7
Measured cell RX level value (RSRP).
0 if E-UTRA cell,
Calculated by
the UE for
GERAN cell
Inhibited if EUTRA cell,
CellReselection
ConfGERAN::p
MaxGeran for
GERAN cell
The value is
different for DCS
bands and GSM
bands

Srxlev evaluation as a result of a periodic search for a
higher priority PLMN while camped normally in a
VPLMN [R15].
Broadcasted in SIB1
max(Pemax Pumax, 0) (dB).
Maximum TX power level an UE may use when

transmitting on the uplink in the cell (dBm) defined as
MS_TXPWR_MAX_CCH in [3GPP TS 45.008].
Maximum RF output power of the UE (dBm) according

to the UE power class as defined in [3GPP TS 45.005,
section 4.1.1].
When camped normally, the UE shall perform the following tasks [R14]:
select and monitor the indicated Paging Channels of the cell according to
information sent in system information;
monitor relevant System Information;
perform necessary measurements for the cell reselection evaluation procedure;
execute the cell

occasions/triggers:
reselection
evaluation
process
on
the
following
UE internal triggers;
When information on the BCCH used for the cell reselection

evaluation procedure has been modified.
Rule: To limit GERAN Measurements

The GERAN carrier frequencies are organised in groups and the cell reselection
parameters are provided per group of GERAN carrier frequencies.
In order to further restrict the amount of measurement carried out by the UE in
RRC-Idle mode, The UE shall apply the following rules for inter-RAT Geran groups
of frequencies, which are indicated in in SystemInformationBlockType7 and for
which the UE has cellReselectionPriority:
For inter-RAT Geran groups of frequencies, with a cellReselectionPriority higher
Page 220/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
than the cellReselectionPriority of the current E-UTRA frequency, the UE shall
perform measurements of higher priority inter-RAT Geran groups of
frequencies.
For inter-RAT Geran groups of frequencies, with cellReselectionPriority lower
than the cellReselectionPriority of the current E-UTRAN frequency:
If SServingCell > Snonintrasearch, UE may choose not to perform measurements of
inter-RAT frequency cells of equal or lower cellReselectionPriority
measurements of inter-RAT frequency cells of equal or lower
qRxLevMin : 3GPP 36.331[R08] Minimum required RX level in the GERAN cell

(dBm).This parameter configures the IE q-RxLevMin included in IE
SystemInformationBlockType7.The value sent over the RRC interface is
computed by adding 115 to the configured value and dividing by 2 (the UE
performs the opposite computation, i.e. IE vale * 2 -115) TS 45.008
CellReselectionConfGERAN::qRxLevMin
Parameter
qRxLevMin
Object
Enb/ LteCell/ GeranNeighboring/ GeranNeighboringFreqsConf/

CellReselectionConfGeran
Range & Unit
dBm
[-115..-25] step = 2
Class/Category
Value
N.A see Engineering Recommendation
Feature
84807
Parameter qRxLevMin in TS 45.008. Actual value Qrxlevmin = IE value * 2-115

[dBm]. Specifies the minimum required Rx RSRP level in the cell. ( Where IE specify
the DLU database value)
Changing this value will affect cell size in terms of re-selection area toward GERAN.
Increasing this value will lead the mobile to start cell-selection/re-selection procedure
sooner and then will artificially decrease cell size in idle mode.
Page 221/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: CellReselectionConfGERAN::qRxLevMin
regarding the apply value. The current value is -102.
Rule: Regarding TLA2.1 : qRxlevminoffset MO CellSelectionReselectionConf

The same Offset used for inter-LTE mobility is used whatever is the target cell,
indeed the qRxlevminoffset parameter is unique in the database.4.1.1.3.1
pMaxGeran : TS36.331: this parameter configures the p-MaxGERAN included in

CellReselectionConfGERAN::pMaxGeran
Parameter
pMaxGeran
Object
Enb/ LteCell/ GeranNeighboring/ GeranNeighboringFreqsConf/

CellReselectionConfGeran
Range & Unit
dBm
[0..39] step = 1
Class/Category
Value
See table below
Feature
84807
Pcompensation is a compensation factor to penalize the low power mobiles.
Pcompensation = max(PEMAX - PUMAX, 0)

Where:
PEMAX = pMaxGERAN
Operating Band
Power (dBm)
II
DCS 1900 MHz
+30
III
DCS 1800 MHz
+30
VIII
GSM 900 MHz
+33
Table 15: Maximum TX power level

Page 222/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
PUMAX = maximum UE output power (dBm) according to its power class in 2g and
operating band. [3GPP 45005, section 4.1.1]
Power (dBm)
Operating Band
Class 1
Class 2
Class 3
Class 4
II
DCS 1900 MHz
+30
+24
+33
N.A
III
DCS 1800 MHz
+30
+24
+36
N.A
VIII
GSM 900 MHz
N.A
+39
+37
+33
GSM 850 MHz
N.A
+39
+37
+33
GSM 700 MHz
N.A
+39
+37
+33
GSM 400 MHz
N.A
+39
+37
+33
shall trigger inter-frequency and inter-RAT measurements for cell
reselection. The value sent over the RRC interface is half the value configured
(the UE then multiplies the received value by 2). For more details consult
TS36.304. Defined in TS 36.331. Broadcast in SystemInformationBlockType3
Parameter
sNonIntraSearch
Object
Range & Unit
dB
[0..62] step = 2
Class/Category
Value
Feature
96760
Page 223/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
cellReselectionPriority: Relative priority for cell reselection (0 means lowest

CellSelectionReselectionConf::cellReselectionPriority
Parameter
Object
Range & Unit
Integer
[0..7] step = 1
Class/Category
Value
0 in TLA2.1 MIM 6.3.3
Feature
96760,97933
nccPermitted: This parameter configures the IE ncc-Permitted included in IE

SystemInformationBlockType7. (3GPP 44060: NCC_Permitted)
CellReselectionConfGERAN::nccPermitted
Parameter
nccPermitted
Object
Enb/ LteCell/ GeranNeighboring/

GeranNeighboringFreqsConf/ CellReselectionConfGeran
Range & Unit
BitString
stringMinLength = 8
string Length = 8
Class/Category
C / Fixed
Value
N.A
Feature
84807
Note: nccPermitted is specific to inter-RAT GERAN management. This field is a

bitmap of NCCs for which the mobile station is permitted to report measurement; this
bitmap relates to NCC part of BSIC.This parameter not existing for inter-RAT UMTS
Management. Better defined in MO MeasObjectGERAN.
6.1.2.2 CELL RESELECTION PRIORITIES HANDLING

Absolute priorities of different E-UTRAN frequencies ([R14] in 5.2.4.1) or inter-RAT
frequencies may be provided to the UE with different way:
Please report you to section 5.1.3.2
Page 224/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
6.1.2.3 UE SPEED MANAGEMENT

SIB3 parameters and algorithms working to speed state measurements configuration
in case of intra-LTE mobility, work also to speed state measurements configuration in
case of GERAN inter-RAT mobility, except parameters in the MO object
GeranSpeedConf and tReselectionGERAN, which are specific: Then you can report
to section 4.1.1.3.3 with this latest restriction.
tEvaluation: TS36.331: this parameter contributes to the configuration of the

SystemInformationBlockType3. This parameter configures the IE t-Evaluation
included in the IE MobilityStateParameters. The duration for evaluating criteria to
enter mobility states. Corresponds to TCRmax in TS 36.304. Value in seconds,
s30 corresponds to 30 s and so on.

the SystemInformationBlockType3. This parameter configures the IE nCellChangeHigh included in the IE MobilityStateParameters. The number of cell
changes to enter high mobility state. Corresponds to NCR_H in TS 36.304.

of the SystemInformationBlockType3. This parameter configures the IE nCellChangeMedium included in the IE MobilityStateParameters. The number of
cell changes to enter medium mobility state. Corresponds to NCR_M in TS
36.304.
tHystNormal: TS36.331: this parameter contributes to the configuration of the

SystemInformationBlockType3. This parameter configures the IE t-HystNormal
included in the IE MobilityStateParameters. The additional duration for evaluating
criteria to enter normal mobility state. Corresponds to TCRmaxHyst in TS 36.304.
Value in seconds, s30 corresponds to 30 s and so on.
Scaling rules:
-

-

- Add qHystSfHigh to Qhyst (to see section 4.1.1.3.2) for high mobility state if
- For GERAN cells multiply tReselectionGERAN by
tReselectionGERANSfHigh if sent on system information.
Page 225/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
- Add qHystSfMedium to Qhyst (to see section 4.1.1.3.2) for medium mobility
state, if sent on system information.
- For GERAN cells multiply tReselectionGERAN by
tReselectionGERANSfMedium, if sent on system information.
In case scaling is applied to any TreselectionRAT parameter the UE shall round up the
result after all scalings to the nearest second.
qHystSfHigh: TS36.331: this parameter contributes to the configuration of the IE

SystemInformationBlockType3.This parameter configures the IE sf-High
included in the IE SpeedStateReselectionPars. Parameter Speed dependent
ScalingFactor for Qhyst in TS 36.304. The sf-High concerns the additional
hysteresis to be applied, in High Mobility state, to Qhyst as defined in TS
36.304 and in 4.1.1.3.2. In dB. Value dB-6 corresponds to -6dB, dB-4
corresponds to -4dB and so on.

reselection.
Decreasing qHystSfHigh leads to do cell-reselection earlier
tReselectionGERANSfHigh : TS36.331v850: this parameter contributes to the

configuration of the IE SystemInformationBlockType7 if the UE is in High
Mobility state. TS36.331v850: this parameter configures the tReselectionGERAN-SF included in the IE SystemInformationBlockType7. The
UE is in High Mobility state as defined in TS 36.304. Value oDot25 corresponds
to 0.25, oDot5 corresponds to 0.5 , oDot75 corresponds to 0.75 and so on.
GeranSpeedConf::tReselectionGERANSfHigh
Parameter
tReselectionGERANSfHigh
Object

GeranSpeedConf
Range & Unit
Enumerate
Class/Category
Value
N.A
Feature
84807
mobility.
Page 226/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
qHystSfMedium: TS36.331: this parameter contributes to the configuration of

the IE SystemInformationBlockType3.This parameter configures the IE sfMedium included in the IE SpeedStateReselectionPars. Parameter Speed
dependent ScalingFactor for Qhyst in TS 36.304. The sf-Medium concerns the
additional hysteresis to be applied, in Medium Mobility state, to Qhyst as
defined in TS 36.304 and in 4.1.1.3.2. In dB. Value dB-6 corresponds to -6dB,
dB-4 corresponds to -4dB and so on.

reselection.
Decreasing qHystSfMedium leads to do cell-reselection earlier
tReselectionGERANSfMedium : TS36.331v850: this parameter contributes to the

configuration of the IE SystemInformationBlockType7 if the UE is in High
Mobility state. TS36.331v850: this parameter configures the tReselectionGERAN-SF included in the IE SystemInformationBlockType7. The
UE is in Medium Mobility state as defined in TS 36.304. Value oDot25
corresponds to 0.25, oDot5 corresponds to 0.5 , oDot75 corresponds to 0.75 and
so on.
GeranSpeedConf::tReselectionGERANSfMedium
Parameter
tReselectionGERANSfMedium
Object

GeranSpeedConf
Range & Unit
Enumerate
Class/Category
Value
N.A
Feature
84807
mobility.
6.1.2.4 E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL

Criteria 1: the SnonServingCell,x of a cell on evaluated frequency is greater than

threshXHigh during a time interval tReselectionRAT[3GPP 36304 section 5.2.4.6]
For UTRAN and E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated
cell.
Page 227/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Rule: Regarding TLA2.1 : tReselectionRAT matching with the type of mobility

tReselectionRAT : This specifies the cell reselection timer value. For each target
frequency/frequency group per RAT a specific value for the cell reselection timer is
defined, which is applicable when evaluating reselection within E-UTRAN or towards
other RAT (i.e. tReselectionRAT for E-UTRAN is tReselectionEUTRAN, for
UTRAN tReselectionUtra, for GERAN tReselectionGERAN, for
tReselectionCdmaHrpd, and for TreselectionCDMA_1xRTT).
Note: tReselectionRAT is not sent on system information, but used in reselection
rules by the UE for each RAT.
Cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT
-
A cell of a higher priority E-UTRAN frequency or inter-RAT frequency fulfils

criteria 1; and
cell.
Cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT

-
No cell on serving frequency or on an equal priority E-UTRAN frequency or on

a higher priority E-UTRAN frequency or inter-RAT frequency than serving
frequency fulfills the criteria 1; and
SservingCell < threshServingLow and the SnonServingCell,x of a cell of a

lower priority E-UTRAN frequency or inter-RAT frequency is greater than
threshXLow during a time interval tReselectionRAT; and
cell.
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based

on ranking for Intra-frequency Cell Reselection as defined in section 4.1.1.3.2 or in
[R14] section 5.2.4.6.
In all the above criteria the value of tReselectionRAT is scaled when the UE is in the
medium or high mobility state as defined in section 5.1.3.3 or in subclause [R14]
5.2.4.3.1.
to criteria defined in 4.1.1.3.2 or in [R14] section 5.2.4.6.
For GERAN, SnonServingCell,x is the Srxlev-value of an evaluated cell.
Page 228/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
tReselectionGERAN : This parameter configures the t-ReselectionGERAN

included in the IE SystemInformationBlockType7
GeranNeighboring::tReselectionGERAN
Parameter
tReselectionGERAN
Object
Enb/ LteCell/ GeranNeighboring
Range & Unit
s
[0..7] step = 1
Class/Category
Value
N.A
Feature
84807
mobility.
Engineering Recommendation: GeranNeighboring::tReselectionGERAN
regarding the apply value. The current value is 2 sec.
threshServingLow: Threshold for serving cell reception level used in reselection

evaluation towards lower priority E-UTRAN frequency or RAT. The value sent
received
value
by
2)
Defined
in
TS
36.331
Broadcast
in
Please report you to section 5.1.3.4
Page 229/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
threshXHigh: TS36.331: this parameter configures the threshX-High included in

CellReselectionConfGERAN::threshXHigh
Parameter
threshXHigh
Object

Range & Unit
Integer, dB
[0..31] step = 1
Class/Category
Value
N.A is the current value
Feature
84807
Engineering Recommendation: CellReselectionConfGERAN:: threshXHigh

One possible value is 0 dB but not yet a lot of tests results. Please keep you
informed about any new recommended value.
threshXLow: TS36.331: this parameter configures the threshX-Low included in

CellReselectionConfGERAN::threshXLow
Parameter
threshXLow
Object

Range & Unit
Integer, dB
[0..31] step = 1
Class/Category
Value
N.A is the current value
Feature
84807
For GERAN, SnonServingCell,x is the Srxlev-value of an evaluated cell.

Note: If some selected cell reach this threshold, when Sserving cell <
threshServingLow, then treselectionGERAN is start.
Page 230/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Engineering Recommendation: threshXLow
To favor the reselection, we can set this parameter to 0.
RSRP
Qrxlevmin(SIB3)+
sNonIntraSearch
sNonIntraSearch=
threshServingLow=16
Source Cell
UE
-104 dBm
RSSI
Target
GERAN Cell
treselectionGERAN: 2s
Qrxlevmin +Qrxlevminoffset
+max[( pMaxGeran -Pumax ), 0]
+threshXLow
UE
-102dBm
-102+0
+max[(37-39), 0]
+0 = -102 dBm
P-CCPCH RSCP
TD-SCDMA Cell.
Priority between
Source Cell
and GERAN Cell
Qrxlevmin +Qrxlevminoffset
+max[(pMaxUTRA -Pumax), 0]
+threshXHigh
-115 dBm
-115+0
+max[(24-24), 0]
+0 = -115 dBm
Chronologic state
of the target GERAN cell
Measures
Cell
Selected
Cell
Reselected
Figure 43 : User Case, with UE Class3 and in the same PLMN,

showing reselection towards lower priority GERAN cell.
Comments related to the diagram just above:
1 : Serving cell become less good and the RSRP level decrease under
[Qrxlevmin(SIB3)+sNonIntraSearch]. Then cell detection of better cell is
possible twice more frequently in average towards all cells, and we can detect
and measured lower priority cells than the serving.
2 : Serving cell becomes worse and the RSRP level decrease under
[Qrxlevmin(SIB3)+threshServingLow]. Cell reselection would be possible, but
not
yet
candidate
cell,
not
reaching
[Qrxlevmin+Qrxlevminoffset
+Pcompensation+threshXLow]. In this user case 1 and 2 occur at the same time
because we have chosen to implement sNonIntraSearch= threshServingLow.
3 :
The situation just above is still reached and also, in the target cell,
threshold [Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXLow] is reached.
tReselectionGERAN is started.
During
tReselectionGERAN,
NO
higher
cell
priority
[Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXHigh]
4 :
reaches
tReselectionGERAN is achieved, reselection is triggered.
Page 231/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
6.1.2.5 ALGORITHM FOR CELL RESELECTION PRIORITY
The
eNodeB
CallP
may
send
IE
freqPriorityListGERAN
in
IdleModeMobilityControlInfo
of
RRCConnectionRelease.
IE
freqPriorityListGERAN specifies the reselection priority for each group of
GERAN carrier frequencies.
The content of IE freqPriorityListGERAN depends on:
o UE capability: supported GERAN bands as indicated in [RRC] UE-EUTRACapability as specified in SupportedBandGERAN.
o GERANNeigboringFreqsConf {bandIndicatorGERAN, GERANarfcnList}
o LteCell GERANNeigboring GERANNeigboringFreqsConf
priorityOfFreqs for the group of GERAN carrier frequencies.
In order to fill the IE freqPriorityListGERAN of IE IdleModeMobilityControlInfo,
eNodeB CallP processing is as follow:
(1.) ENodeB CallP retrieves the GERANNeigbouringFreqsConf instances for the
bandIndicatorGERAN supported by the UE.
(2.) ENodeB CallP retrieves the corresponding priorityOfFreqs from the instance.
2. Case Meas-Redirection-To-UTRA-TDD: the eNB receives a MeasReport that

corresponds to a measurement purpose Meas-Redirection-To-UTRA-TDD
The eNB sends the idleModeMobilityControlInfo
The eNB shall builds the RRC IE
1>IdleModeMobilityControlInfo and 2>freqPriorityListGERAN and
2>freqPriorityListUTRA-TDD
o takes the MiM configuration as entered by the Operator in
UtraTddNeighboringFreqConf MO and GeranNeighboringFreqsConf MO.
o gives the highest priority to the UTRAN Freq or GERAN Freqs received in
MeasReport
o builds all the other priorities by following the order configured in
UtraTddNeighboringFreqConf and GeranNeighboringFreqsConf
During t320, the UE will follow the cell reselection priorities provided by
IdleModeMobilityControlInfo.
After t320, the UE will follow the SIB6 and SIB7 (as specified by 36.304
section[36304-860] 5.2.4.1)
3. Case Meas-Redirection-To-GERAN: the eNB receives a MeasReport that
corresponds to a measurement purpose Meas-Redirection-To-GERAN
Like 2. Case Meas-Redirection-To-UTRA-TDD
4. Optional sending of this IE idleModeMobilityControlInfo: depens on the presence
of optional MiM parameter "t320" (see definition of attribute t320)
priorityOfFreqs: [36331]: this parameter contributes to the configuration of the

IE IdleModeMobilityControlInfo: freqPriorityListGERAN (Optional). This
Page 232/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
attribute is used by the Algorithm for RRC Measurement Configuration,
and/or for Control Procedure for Mobility (RAT chosen for the blind redirection).
Parameter
priorityOfFreqs
Object
ENBEquipment/Enb/LteCell/GeranNeighboring/
GeranNeighboringFreqsConf
Range & Unit
Integer
[0..7] step = 1
Class/Category
Value
N.A
Feature
84807
Note: The lowest priority is 0, the proposal setting is 2 for this parameter.
BandIndicatorGERAN: This attribute corresponds to the GERAN band indicator

of the group. This IE is optional as not always useful to understand the ARFCN.
GeranNeighboringFreqsConf::BandIndicatorGERAN
Parameter
BandIndicatorGERAN
Object
Range & Unit
Enumerate
[dcs1800, pcs1900]
Class/Category
C / Fixed
Value
N.A
Feature
84807
Page 233/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
GeranARFCNList: This attribute corresponds to a list of GERAN ARFCN
GeranNeighboringFreqsConf::GeranARFCNList
Parameter
GeranARFCNList
Object
Range & Unit
Integer
[0..1023] step = 1
listSizeMin = 1
listSizeMax = 32
Class/Category
Value
N.A
Feature
84807
bandGERAN: This indicates the GERAN band for the ARFCN list.
GeranNeighboringFreqsConf::bandGERAN
Parameter
bandGERAN
Object
Range & Unit
Enumerate
[gsm450, gsm480, gsm710, gsm750, gsm810, gsm850, gsm900P,
gsm900E, gsm900R, gsm1800, gsm1900]
Class/Category
C / Fixed
Value
N.A
Feature
84807
Note: The parameter bandGERAN is used for UE caps checking. Callp use
bandGERAN to fill the RRC messages.
6.1.2.6 LTE TO GERAN RESELECTION CONFIGURATION
Page 234/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ENBEquipment
CellSelectionReselectionConf(SIB1 or SIB3)
qRxLevMin
ActivationService
Enb
qRxlevminoffset
isCellReselectionToGeranAllowed
sNonIntraSearch
(isRedirectionToGERANAllowed)
cellReselectionPriority (LTE)
isIntraFreqMobilityAllowed
threshServingLow
LTECell
SpeedDependentBroadcastConf
GeranNeighboring
Optional subtree
tReselectionGERAN
(SIB7-GERAN)
LteSpeedConf
CellReselectionConfGERAN(SIB7)
priorityOfFreqs (SIB7-GERAN)
qRxLevMin
BandIndicatorGERAN (OD)
pMaxGeran
GeranARFCNList(OD)
threshXLow
GeranSpeedConf
bandGERAN(OD)
threshXHigh
tReselectionGERANSfHigh
nccPermitted (OD)
tReselectionGERANSfMedium
Figure 44 : LTE to GERAN reselection MIM configuration.
6.2 RRC CONNECTED MODE MOBILITY:
The feature PM84807 enables the LTE-to-GERAN mobility in RRC connected mode
with a redirection to GERAN based on radio measurements. Radio measurement
includes the intra-frequency EUTRA radio conditions and the inter-RAT GERAN radio
conditions. The inter-RAT GERAN radio conditions shall be better than a
configured threshold while the radio conditions in the serving EUTRA cell are
lower than another threshold.
The benefit from the LTE-to-GERAN mobility in RRC_CONNECTED with data
communication is the seamless continuity of data communication, while the user is
moving and leaving an LTE island or hot-spot.
Inter-RAT mobility functionality shall provide UE mobility while its packet session is
on-going. The packet session is kept maintained even in case of mobility between
LTE and GERAN.
Page 235/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
GSM_Connected
CELL_DCH
CELL_FACH
CELL_PCH
URA_PCH
Handover
RRC Connection
Establishment
Reselection
Connection
UTRA_Idle
E-UTRA
RRC_CONNECTED
Reselection
Reselection
Handover
GPRS Packet
transfer mode
CCO with
optional
NACC
CCO,
Reselection
RRC Connection
Release (with
redirection info)
E-UTRA
RRC_IDLE
Connection
Reselection
GSM_Idle/GPRS
Packet_Idle
CCO, Reselection
Figure 45 : Redirection from eUTRAN to GERAN
In TLA2.1 and for the UE in RRC connected mode, the inter-RAT mobility to GERAN
is supported with the RRC connection release and redirection from E-UTRA-TDD to
GERAN.
The redirection is driven by the eNodeB based on radio criteria. The required
control procedures are covered by this document in section XXX.
The decision to redirect a UE to the GERAN coverage is because the radio conditions
are degraded in the serving cell and the UE reports good radio conditions on a
neighboring GERAN coverage.
The following call flows describe the main scenario that leads the eNodeB to release
the RRC connection with the UE and to indicate the redirection information.
To see diagram in section 4.3.1.3 for A2 blind configuration.
Restriction: TLA2.1
Page 236/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
source eNB
source MME
target SGSN
target BSS
SGW
uplink user plane

downlink user plane
RRC-MeasurementReport(event A2) UE sends A2 when radio condition
has degraded in the serving cell
RRC-ConnectionReconfiguration
RRC-ConnectionReconfComplete
eNodeB may configure measurement

event B2 and measurement gap
UE may send event B2 if a target GERAN
RRC-MeasurementReport(event B2) cell becomes better while conditions in

serving cell are degraded
RRC-ConnectionRelease(redirect information)
eNodeB decides to redirect the UE to

GERAN
S1-AP- UE Context Release Request

Redirect information
to GERAN. UE
leaves the LTE cell
and access GERAN
S1 connection released by MME and

S1-U bearers removed in SGW
S1-AP- UE Context Release Command

S1-AP- UE Context Release Complete
cell selection
Routing Area Update
uplink user plane
downlink user plane
Event B2 and gap configuration for UE needing measurement gap and redirection to
GERAN
Page 237/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
source eNB
source MME
target SGSN
target RNC
SGW
uplink user plane

downlink user plane
RRC-ConnectionReconfiguration
RRC-ConnectionReconfComplete
eNodeB configure measurement

event B2.
UE may send event B2 if a target GERAN
RRC-MeasurementReport(event B2) cell becomes better while conditions in

serving cell are degraded
eNodeB decides to redirect the UE to
RRC-ConnectionRelease(redirect information) GERAN
S1-AP- UE Context Release Request

Redirect information
to GERAN. UE
leaves the LTE cell
and access GERAN
S1 connection released by MME and

S1-U bearers removed in SGW
S1-AP- UE Context Release Command

S1-AP- UE Context Release Complete
cell selection
Routing Area Update
uplink user plane
downlink user plane
Event B2 configuration for UE not needing measurement gap and redirection to

GERAN
6.2.1 REDIRECTION ACTIVATION

Like in 4.1.2.1, at the same place in the data model, the parameter below is in the
scope of mobility activation and information options. Be careful, it is mandatory to
activate it, for mobility related to. It is Fixed category and it is C class parameter:
Page 238/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ActivationService:: isRedirectionToGERANAllowed
Parameter
isRedirectionToGERANAllowed
Object
ActivationService
Range & Unit
[false, true]
Class/Category
C / Fixed
Value
O.D.
Feature
This parameter is an activation flag to set whether the EUTRAN to GERAN redirection
is enabled or disabled globally.
Engineering Recommendation: isRedirectionToGERANAllowed

If you want to implement redirection towards GERAN, set this parameter to true
6.2.2 CONTROL PROCEDURES FOR RADIO MEASUREMENTS

CONFIGURATION AND MOBILITY TRIGGER
MANAGEMENT
The TLA2.1 redirection EUTRA-to-GERAN relies entirely on measurement reports
from the UE. The UE reports to the source ENB when the serving radio quality is
sufficiently degraded and an inter-RAT neighbor is a good candidate.
In TLA2.1, one specific measurement purpose can trigger EUTRA-TDD-to-GERAN
inter-RAT mobility.
The next sections specify the triggers to transmit successive RRC messages for RRC
measurement configuration. The measurements are set-up upon transition to the RRC
connected mode; setup/released upon receipt of measurement reports indicating the
radio level quality of an intra-frequency EUTRA cell or an inter-RAT GERAN cell. The
measurements can be updated upon completion of an intra-frequency intra-ENB
handover or an intra-frequency X2 handover (inter-ENB).
6.2.2.1 MEASUREMENTS CONFIGURATION AT CALL SETUP

The eNodeB call processing distinguishes many phases of RRC measurements:
Page 239/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
-
Phase No.1: high priority measurements are configured for the intra-LTE intrafrequency handover. At call setup, such a measurement is configured just after
RRC Connection Setup procedure and before configuration of security mode. Any
measurement report received before completion of security mode configuration
and SRB2 + default bearer (+ optional bearers) is ignored and discarded by the
eNodeB. Because intra-LTE intra-frequency mobility cannot be performed while
security mode and SRB2 + default bearer are not configured successfully.
Phase No.2: one configures low priority measurements i.e. measurements not
dedicated for the intra-LTE intra-frequency handover. At call setup, these
measurements are configured only once security mode and SRB2 + default
bearer are configured successfully.
Phase No.3: subsequent low priority measurements are configured upon the
evolution of the radio quality as described in this document.
If the attribute isRedirectionToGERANAllowed is set to TRUE, a measurement

control RRCConnectionReconfiguration message with the IE MeasConfig may be
(depending on MiM configuration) sent to the UE during Phase No.2 (low priority
measurement).
The message RRCConnectionReconfiguration includes the IE MeasConfig to
configure the inter-RAT (UTRAN/GERAN) measurement profile described below in
section algorithm for RRC Measurement configuration. This RRC Measurement
Configuration is applied in the serving cell on which the call is established.
In TLA2.1 up to maxMeasId INTEGER=32 measurements could be setup including
the mobility triggering measurement. The failure of the measurement set-up is
The next figure hereafter describes the measurement setup at call setup.
Page 240/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
UE
eNodeB
MME

Algorithm for RRC

Phase No.1
Algorithm for RRC

Measurement Gap
RRC Measurement


(Optional)
Algorithm for

Algorithm for RRC

Phase No.2
Algorithm for RRC

Measurement Gap

RRC Measurement
Configuration
UE
eNodeB
MME
Figure 46 : Measurement setup at call setup
6.2.2.2 ALGORITHM FOR RRC MEASUREMENT CONFIGURATION

To see section 5.2.2.4
Page 241/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
6.2.2.3 SPEED STATE MEASUREMENTS CONFIGURATION
tEvaluation: TS36.331: this parameter contributes to the configuration of the IE

MeasConfig. This parameter configures the IE t-Evaluation included in the IE
MobilityStateParameters. The duration for evaluating criteria to enter mobility
states. Corresponds to TCRmax in TS 36.304. Value in seconds, s30
corresponds to 30 s and so on.

the IE MeasConfig. This parameter configures the IE n-CellChangeHigh included
in the IE MobilityStateParameters. The number of cell changes to enter high
mobility state. Corresponds to NCR_H in TS 36.304.

of the IE MeasConfig.This parameter configures the IE n-CellChangeMedium
included in the IE MobilityStateParameters. The number of cell changes to enter
medium mobility state. Corresponds to NCR_M in TS 36.304.
tHystNormal: TS36.331: this parameter contributes to the configuration of the IE

MeasConfig. This parameter configures the IE t-HystNormal included in the IE
MobilityStateParameters. The additional duration for evaluating criteria to enter
normal mobility state. Corresponds to TCRmaxHyst in TS 36.304. Value in
seconds, s30 corresponds to 30 s and so on.
6.2.3 LTE TO GERAN MEASUREMENT REPORTING SETTING
6.2.3.1 LTE TO GERAN MEASUREMENT REPORTING SETING:

MeasObjectGERAN MO is used to configure a measurement when the associated
measurement purpose is set to a new value introduced in TLA2.1: MeasRedirection-To-GERAN.
The MeasObjectGERAN MO is a child of the MeasObject MO: before TLA2.1, each
instance of MeasObject MO had only a child MeasObjectEUTRA.
Page 242/266
02.06 / EN
EXTERNAL
LTE/DCL/APP/031549
27 Apr 2011
Volume 6 : Mobility
Enb
[1..3]
RrmServices
LteCell
RadioCacConf
[1..32]
UeMeasurement
Conf
TrafficBased
ReleaseConf
[1..3]
[1..32]
[1..32]
[1..32]
RrcMeasurement
Conf
Measurement
IdentityConf
ReportConfig
MeasObject
[0..1]
[0..1]
reportConfigId
measObjectId
LteNeighboring
CellRelation
ReportConfig
EUTRA
[0..1]
[0..1]
UtraFddNeighboring
[0..1]
ReportConfig
UTRA
GERANNeighboringFreqsConfId
offsetFreqGERAN
nccPermitted
GeranNeighboring
[0..16]
GeranNeighboringF
reqsConf
MeasObject
UTRA
[0..1]
[0..1]
[0..1]
MeasObject
EUTRA
ReportConfig
GERAN
MeasObject
GERAN
GERANNeighboringFreqsConfId
Figure 47 : Data model for MeasObjectGERAN
Page 243/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
offsetFreqGERAN: offsetFreq is used to indicate a frequency specific offset to

be applied when evaluating triggering conditions for measurement reporting. The
value in dB.
MeasObjectGERAN::offsetFreqGERAN
Parameter
offsetFreqGERAN
Object
ENBEquipment/Enb/RrmServices/UeMeasurementConf/MeasObjec
t/ MeasObjectGERAN
Range & Unit
Integer in dB
[-15..15] step = 1
Class/Categor
y
Value
N.A
Feature
FRS 84807
Note: This offset is used to favor or not the redirection towards GERAN
nccPermitted: This parameter configures the IE ncc-Permitted included in the IE

MeasObjectGERAN in the IE MeasConfig. This field is a bitmap of NCCs for
which the mobile station is permitted to report measurement; this bitmap relates
to NCC part of BSIC (see TS44.060)
MeasObjectGERAN::nccPermitted
Parameter
nccPermitted
Object
ENBEquipment/Enb/RrmServices/UeMeasurementConf/MeasObjec
t/ MeasObjectGERAN
Range & Unit
BitString
stringMinLength = 8
string Length = 8
Class/Categor
y
C / Fixed
Value
N.A
Feature
84807
Note: nccPermitted is specific to inter-RAT GERAN management.
6.2.4 LTE TO GERAN MEASUREMENTS CONFIGURATION
Page 244/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Inter-RAT Measurements have been configured in UE. According to the UE
measurement capabilities, the provisioned inter-RAT neighbouring and the inter-RAT
mobility feature flags, the event B2 with measurement purpose "Meas Redirection to
UTRA-TDD via event B2" has been configured.
A RRC Measurement Report is received with measurement purpose:

- Meas Redirection to UTRA-TDD via event B2
UE leaves the E-UTRAN, UE context is released.

A RRC Connection Release message with the RedirectionInfo IE is sent to the UE.
The UE goes idle and reselects an UTRA-TDD cell based on the RedirectionInfo IE
Restriction: TLA2.1
Page 245/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Page 246/266
02.06 / EN
EXTERNAL
LTE/DCL/APP/031549
27 Apr 2011
Volume 6 : Mobility
UE
xCCM
xCCM
xCCM
xCEM
xCCM or xCEM
xCCM
UeCall
UBM
SCTP Access
BRC
L2 and/or L1
IP Stack
MME
SCTP PDU
S1AP UE CONTEXT RELEASE COMMAND
Association ID
Stream ID
S1AP Payload Size
S1AP Payload
(S1AP UE CONTEXT RELEASE COMMAND)
1. UeCall invokes S1Call

2. S1Call decodes ASN1 msg
3. S1Call returns msg to UeCall
S1AP UE
CONTEXT
RELEASE
COMMAND
SCTP PDU
SCTP_DATA_IND
MME UE S1AP ID
eNB UE S1AP ID
Cause=normal
With eNB S1-AP UE Identity

UECall retrieves UE Context ID
Uecall reset the UeRelReqT1 timer
UE_UBEARER_DELETE_REQUEST
UBM Context Deletion
UE_UBEARER_DELETE_RESPONSE
UE_RLC_MAC_L1_CONTEXT_DELETE_REQUEST
BRC Context Deletion
UE_RLC_MAC_L1_CONTEXT_DELETE_RESPONSE
1. UeCall invokes S1Call

2. Based on current call context,
S1Call builds and encodes msg
3. S1Call sends msg
SCTP_DATA_REQ
SCTP PDU
Association ID
Stream ID
S1AP Payload Size
S1AP Payload(S1AP UE CONTEXT RELEASE COMPLETE)
SCTP PDU
S1AP UE CONTEXT RELEASE COMPLETE
S1AP UE
CONTEXT
RELEASE
COMPLETE
MME S1AP UE Identity

eNB S1AP UE Identity
UE Context Deletion
UE
UeCall
UBM
SCTP Access
BRC
L2 and/or L1
IP Stack
MME
1.
UE sends a RRC MEASUREMENT REPORT message with measId
corresponding to a purpose Meas Redirection to GERAN via event B2
2.
Uecall decodes the RRC message by invoking the UeRRC
Uecall calls UeRrm to decide or not for redirection and retrieve the frequency
carrier (here a GERAN carrier) from the MIM thanks to the measId.
3.
If UeRrm decides for redirection, it generates inter-RAT redirection in
UeRrmOutput.
4.
RRC CONNECTION RELEASE with RedirectionInformation IE is sent to UE
with releaseCause=Other.
5.
PEGCounter(UEContextReleaseRequest, InterRATRedirection, LteCell Id, 1)
6.
if the reportConfigInterRat.eventB2.b2-Threshold1
reportConfigid associated to the measid in the UE context is
referenced
by
the
threshold-RSRP -> PEGCounter(RedirectionToGeran, MeasurementViaEvent

B2AndThreshold1RSRPThreshold2GERAN, LteCell Id, 1)
Page 247/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
threshold-RSRQ -> PEGCounter(RedirectionToGeran, MeasurementViaEvent

B2AndThreshold1RSRQThreshold2GERAN, LteCell Id, 1)
7.
Then UeCall trigger S1AP UE CONTEXT RELEASE with cause= Inter-RAT
redirection.
8.
Normal
E-RAB
release
counter
is
pegged
by
using
PEGCounter(NormalERABRelease, Associated screening according to QCI , LTECell
Index, Released Number of E-RABs)
The MME triggers the UE Context Release procedure.
The rules are the same as in 5.2.3.1
measQuantityGERAN: Configures the IE QuantityConfigGERAN in IE

QuantityConfig. It is proposed to include this attribute in the MIM model for
global
consistency
between
measQuantityUtraTdd
and
measQuantityGERAN parameters. But the value is set to {rssi} by MIM checks.
RrcMeasurementConf::measQuantityGERAN
Parameter
measQuantityGERAN
Object
ENBEquipment/Enb/RrmServices/UeMeasurementConf/
RrcMeasurementConf
Range & Unit
Enumerate
[rssi]
Class/Category
C / Fixed
Value
rssi
Feature
FRS 84807
filterCoefficientOfQuantityConfigGERAN:
filterCoefficientOfQuantityConfigGERAN is
filterCorefficient of QuantityConfigGERAN
used
to
configure
the
IE
RrcMeasurementConf::filterCoefficientOfQuantityConfigGERAN
Parameter
filterCoefficientOfQuantityConfigGERAN
Object
ENBEquipment/Enb/RrmServices/UeMeasurementConf/
RrcMeasurementConf
Range & Unit
Enumerate
fc17, fc19]
Class/Category
Value
(Default:fc2)
Feature
FRS 84807
Page 248/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
RrcMeasurementConf::transmissionGapRepetitionPeriod
6.2.4.2 REPORTCONFIGGERAN:
maxReportCells: This IE indicates max number of cells, excluding the serving

cell, to include in the measurement report. This is used to provision IE
MaxReportCells in IE ReportConfigInterRAT, in IE MeasConfig.
ReportConfigGERAN::maxReportCells
Parameter
maxReportCells
Object

ReportConfigGERAN
Range & Unit
integer
[1..8] step = 1
Class/Category
Value
N.A (Default:1)
Feature
FRS 84807

measurement report
Engineering Recommendation: maxReportCells
The first proposal value is 1 , like default value. Please keep you informed because
tests on going and this value is subject to modifications.
Page 249/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
ReportConfigInterRAT field descriptions
eventId
Choice of inter-RAT event triggered reporting criteria.
bN-ThresholdM
Threshold to be used in inter RAT measurement report triggering condition for event number
bN. If multiple thresholds are defined for event number bN, the thresholds are differentiated
by M.
timeToTrigger
measurement report.
Purpose
reportStrongestCellsForSON applies only in case reportConfig is linked to a measObject set
to measObjectUTRA or measObjectCDMA2000.
maxReportCells
Max number of cells, excluding the serving cell, to include in the measurement report. In case
purpose is set to reportStrongestCellsForSON only value 1 applies.
reportAmount
periodical. In case purpose is set to reportCGI or reportStrongestCellsForSON only value
1 applies.
ThresholdUTRA
utra-RSCP corresponds to CPICH_RSCP in TS 25.133 for FDD and P-CCPCH_RSCP in
TS 25.123 for TDD. utra-EcN0 corresponds to CPICH_Ec/No in TS 25.133 for FDD, and is
not applicable for TDD.
For utra-RSCP: The actual value is IE value 115 dBm. Integer value according to mapping
table in TS 25.133 and TS 25.123 , for FDD and TDD, respectively.
For utra-EcN0: The actual value is (IE value 49)/2 dB. Integer value according to mapping
table in TS 25.133.
ThresholdGERAN
The actual value is IE value 110 dBm. . Integer value according to mapping table in TS
45.008 .
triggerTypeInterRAT: This parameter configures the RRC IE triggerType

included in the IE reportConfigInterRAT in the MeasurementConfiguration IE.
ReportConfigGERAN::triggerTypeInterRAT
Parameter
triggerTypeInterRAT
Object

ReportConfigGERAN
Range & Unit
Enumerate
[eventB1, eventB2 ]
Class/Category
C / Fixed
Value
N.A
Feature
FRS 84807
Engineering Recommendation: triggerTypeInterRAT

We recommend to set this parameter to eventB2 if you want trigger any
measurement, for LTE to GERAN mobility, because only this on is supported in
TLA2.1
Page 250/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
hysteresis: This IE is a parameter used within the entry and leave condition of an
event triggered reporting condition. This is used to provision IE Hysteresis in IE
ReportConfigInterRAT, in IE MeasConfig
This parameter defines the hysteresis used by the UE to trigger an intra-frequency

event-triggered measurement report.
ReportConfigGERAN::hysteresis
Parameter
hysteresis
Object

ReportConfigGERAN
Range & Unit
Float in dB
[0.0..15.0] step = 0.5
Class/Category
Value
N.A see Engineering Recommendation
Feature
FRS 84807
Margin for HO Value to be confirmed.
Rule: Regarding hysteresis parameter

hysteresis is used in the following process: Event B2 (Serving becomes worse than
threshold1 and inter RAT neighbour becomes better than threshold2). The 3GPP
name is Hys in [R08].
Note: In TLA2.1, we only support Event B2 based LTE to GERAN redirection for UE
that does not require measurement Gap.
Engineering Recommendation: hysteresis
Be careful: Value is subject to modification according tests case results. Please keep
up to date regarding the apply value.
Restriction: TLA2.1
Page 251/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
timeToTrigger : This IE indicates the time during which specific criteria for the
event needs to be met in order to trigger a measurement report. This is used to
provision IE TimeToTrigger in IE ReportConfigInterRAT, in IE MeasConfig
triggered mode
ReportConfigGERAN::timeToTrigger
Parameter
timeToTrigger
Object

ReportConfigGERAN
Range & Unit
Enumerate in ms
[0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024,
1280, 2560, 5120]
Class/Category
Value
N.A
Feature
FRS 84807
Rule: Regarding timeToTrigger parameter


Page 252/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility

RSRP
Target Cell
Serving Cell
8
7
6
5
4
3
2
1
0
5
timeToTrigger
10
15
20
reportingInterval
25
30
hysteresis
Time
35
Figure 48: Hysteresis used to tuning HO decision, reportAmount = 4
reportInterval: The ReportInterval indicates the interval between periodical

reports.This is used to provision IE ReportInterval in IE ReportConfigInterRAT, in
IE MeasConfig.
ReportConfigGERAN::reportInterval
Parameter
reportInterval
Object

ReportConfigGERAN
Range & Unit
[ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120,
Class/Category
Value
N.A
Feature
FRS 84807

periodical.[R08]
Engineering Recommendation: reportInterval

Page 253/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
reportAmount: This indicates the Number of measurement reports. This is used

to provision IE ReportAmount in IE ReportConfigInterRAT, in IE MeasConfig.
ReportConfigGERAN::reportAmount
Parameter
reportAmount
Object

ReportConfigGERAN
Range & Unit
Enumerate
Class/Category
Value
N.A
Feature
FRS 84807
This parameter configures the number of periodical reports the UE has to transmits

Rule: Regarding reportInterval & reportAmount parameter

2>
start the periodical reporting timer with the value of reportInterval as defined
6.2.4.3 THRESHOLDS FOR INTER-RAT MOBILITY:

The function is the same as for UTRAN mobility, please refer to section 5.2.2.8.1 for
the explanation.
At the level of the diagram, the thresholds match with the following parameters:
B2_threshold1 => threshold1EutraRsrp or threshold1EutraRsrq (under MO
ReportConfigGERAN) for serving cell.
B2_threshold2 => B2thresholdGERAN (under MO ReportConfigGERAN) for target cell.
Note: GERAN measurement must be based on RSRP measurement
Page 254/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: Regarding TLA2.1 and EventB2

Currently, at our knowledge, none UE is able to manage these
measurements and EventB2 is not applicable as long as we havent UE in interworking with this feature
threshold1EutraRsrp: This is used to provision IE b2-Threshold1in IE

ReportConfigGERAN::threshold1EutraRsrp
Parameter
threshold1EutraRsrp
Object

ReportConfigGERAN
Range & Unit
Enumerate in dBm
more_than_minus44 ]
Class/Category
Value
N.A
Feature
FRS 84807
Page 255/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
threshold1EutraRsrq: This is used to provision IE b2-Threshold1in IE

ReportConfigGERAN::threshold1EutraRsrq
Parameter
threshold1EutraRsrq
Object

ReportConfigGERAN
Range & Unit
Enumerate in dB
more_than_minus3]
Class/Category
Value
N.A
Feature
FRS 84807
B2ThresholdGERAN : This is the threshold GERAN defined for event B2. This is
used to provision IE b2-Threshold2GERAN in IE ReportConfigInterRAT, in IE
MeasConfig.
ReportConfigGERAN::B2ThresholdGERAN
Parameter
B2ThresholdGERAN
Object

ReportConfigGERAN
Range & Unit
Enumerate in dBm
more_than_minus48]
Class/Category
C / Fixed
Value
N.A
Feature
FRS 84807
Page 256/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
Restriction: TLA2.1
ActivationService:: isGeranCcoAllowed
ActivationService:: isDSIMallowed
BscAccess::rimForNaccEnabled
Page 257/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
8 ANNEX:
8.1 ABBREVIATIONS
All terms, definitions and abbreviations used in the present document, that are
common across 3GPP TSs, are defined in the 3GPP Vocabulary
For the purposes of the present document, the abbreviations given in following apply.
ACK
ACLR
AM
AMBR
ANR
ARQ
AS
BCCH
BCH
BSR
C/I
CAZAC
CMC
CP
C-plane
C-RNTI
CQI
CRC
CSG
DCCH
DL
DFTS
DRB
DRX
DTCH
DTX
DwPTS
ECGI
ECM
EMM
eNB
EPC
EPS
E-RAB
ETWS
E-UTRA
E-UTRAN
FDD
FDM
Acknowledgement
Adjacent Channel Leakage Ratio
Acknowledge Mode
Aggregate Maximum Bit Rate
Automatic Neighbour Relation
Automatic Repeat Request
Access Stratum
Broadcast Control Channel
Broadcast Channel
Buffer Status Reports
Carrier-to-Interference Power Ratio
Constant Amplitude Zero Auto-Correlation
Connection Mobility Control
Cyclic Prefix
Control Plane
Cell RNTI
Channel Quality Indicator
Cyclic Redundancy Check
Closed Subscriber Group
Dedicated Control Channel
Downlink
DFT Spread OFDM
Data Radio Bearer
Discontinuous Reception
Dedicated Traffic Channel
Discontinuous Transmission
Downlink Pilot Time Slot
E-UTRAN Cell Global Identifier
EPS Connection Management
EPS Mobility Management
E-UTRAN NodeB
Evolved Packet Core
Evolved Packet System
E-UTRAN Radio Access Bearer
Earthquake and Tsunami Warning System
Evolved UTRA
Evolved UTRAN
Frequency Division Duplex
Frequency Division Multiplexing
Page 258/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
GERAN
GNSS
GSM
GBR
GP
HARQ
HO
HRPD
HSDPA
ICIC
IP
LB
LCR
LTE
MAC
MBMS
MBR
MBSFN
MCCH
MCE
MCH
MCS
MIB
MIMO
MME
MO
MTCH
MSAP
N.A
NACK
NAS
NCC
NH
NR
NRT
N.S
O.D
configuration)
OFDM
OFDMA
OMC
P-GW
P-RNTI
PA
PAPR
PBCH
PBR
PCCH
PCFICH
PCH
PCI
PDCCH
PDSCH
PDCP
PDU
PHICH
PHY
PLMN
GSM EDGE Radio Access Network

Global Navigation Satellite System
Global System for Mobile communication (Groupe Spcial Mobile )
Guaranteed Bit Rate
Guard Period
Hybrid ARQ
Handover
High Rate Packet Data
High Speed Downlink Packet Access
Inter-Cell Interference Coordination
Internet Protocol
Load Balancing
Low Chip Rate
Long Term Evolution
Medium Access Control
Multimedia Broadcast Multicast Service
Maximum Bit Rate
Multimedia Broadcast multicast service Single Frequency Network
Multicast Control Channel
Multi-cell/multicast Coordination Entity
Multicast Channel
Modulation and Coding Scheme
Master Information Block
Multiple Input Multiple Output
Mobility Management Entity
Managed Object
MBMS Traffic Channel
MCH Subframe Allocation Pattern
Not Applicable
Negative Acknowledgement
Non-Access Stratum
Next Hop Chaining Counter
Next Hop key
Neighbour cell Relation
Neighbour Relation Table
Not Significant
Operator Dependent (depends on operator network specific
Orthogonal Frequency Division Multiplexing
Orthogonal Frequency Division Multiple Access
Operations and Maintenance Center
PDN Gateway
Paging RNTI
Power Amplifier
Peak-to-Average Power Ratio
Physical Broadcast CHannel
Prioritised Bit Rate
Paging Control Channel
Physical Control Format Indicator CHannel
Paging Channel
Physical Cell Identifier
Physical Downlink Control CHannel
Physical Downlink Shared CHannel
Packet Data Convergence Protocol
Protocol Data Unit
Physical Hybrid ARQ Indicator CHannel
Physical layer
Public Land Mobile Network
Page 259/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
PMCH
PRACH
PRB
PSC
PUCCH
PUSCH
QAM
QCI
QoS
RA-RNTI
RAC
RACH
RAT
RB
RBC
RBG
RF
RIM
RLC
RNC
RNL
RNTI
ROHC
RRC
RRM
RSRP
RU
S-GW
S1-MME
SC-RNTI
SI
SIB
SI-RNTI
S1-U
SAE
SAP
SC-FDMA
SCH
SDF
SDMA
SDU
SFN
SPID
SR
SRB
SU
TA
TB
TCP
TDD
TFT
TM
TNL
TTI
UE
UL
UM
UMTS
Physical Multicast CHannel

Physical Random Access CHannel
Physical Resource Block
Packet Scheduling
Physical Uplink Control CHannel
Physical Uplink Shared CHannel
Quadrature Amplitude Modulation
QoS Class Identifier
Quality of Service
Random Access RNTI
Radio Admission Control
Random Access Channel
Radio Access Technology
Radio Bearer
Radio Bearer Control
Radio Bearer Group
Radio Frequency
RAN Information Management
Radio Link Control
Radio Network Controller
Radio Network Layer
Radio Network Temporary Identifier
Robust Header Compression
Radio Resource Control
Radio Resource Management
Reference Signal Received Power
Resource Unit
Serving Gateway
S1 for the control plane
System Information Change RNTI
System Information
System Information Block
System Information RNTI
S1 for the user plane
System Architecture Evolution
Service Access Point
Single Carrier Frequency Division Multiple Access
Synchronization Channel
Service Data Flow
Spatial Division Multiple Access
Service Data Unit
System Frame Number
Subscriber Profile ID for RAT/Frequency Priority
Scheduling Request
Signalling Radio Bearer
Scheduling Unit
Tracking Area
Transport Block
Transmission Control Protocol
Time Division Duplex
Traffic Flow Template
Transparent Mode
Transport Network Layer
Transmission Time Interval
User Equipment
Uplink
Un-acknowledge Mode
Universal Mobile Telecommunication System
Page 260/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
U-plane
UTRA
UTRAN
UpPTS
VRB
X2-C
X2-U
User plane
Universal Terrestrial Radio Access
Universal Terrestrial Radio Access Network
Uplink Pilot Time Slot
Virtual Resource Block
X2-Control plane
X2-User plane
Page 261/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
8.2
INTRA-FREQUENCY INTRA-ENB CALL FLOW:
Page 262/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
8.3
INTRA-FREQUENCY INTER-ENB CALL FLOW
Page 263/266
LTE/DCL/APP/031549
02.06 / EN
EXTERNAL
27 Apr 2011
Volume 6 : Mobility
END OF VOLUME
Page 264/266

TLA2.1 LPUG 02.06 Volume 6 Mobility Approved Preliminary External

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TLA2.1 LPUG 02.06 Volume 6 Mobility Approved Preliminary External

Hochgeladen von

Copyright:

Verfügbare Formate

LTE/DCL/APP/031549

TDD ENODEB LTE PARAMETERS USER GUIDE

LTE PARAMETERS USER GUIDE

TDD eNodeB LTE Parameters User Guide

Copyright 2010 by Alcatel-Lucent. All Rights Reserved.

TDD eNodeB LTE Parameters User Guide

CONTENTS AND PARAMETER GUIDE

SCOPE OF THIS VOLUME ........................................................................................................10

LIST OF RELATED FEATURES ............................................................................................11

RELATED DOCUMENTS AND PREREQUISITES.........................................................................12

LPUG VOLUMES ......................................................................................................................12

PREREQUISITES FOR READING THIS VOLUME ...............................................................13

INTRA-RAT MOBILITY FOR LTE ...................................................................................................14

INTRA-FREQUENCY MOBILITY FOR LTE .....................................................................................14

PLMN Selection & CELL RESERVATION and CELL RESTRICTION: .......................16

UE SPEED MANAGEMENT ............................................................................................25

4.1.1.3.3.1 .......... MIM MODEL

INTRA-FREQUENCY INTRA-eNB MOBILITY ............................................................37

TDD eNodeB LTE Parameters User Guide

Failure Cases .......................................................................................................................48

INTRA-FREQUENCY MEASUREMENT REPORTING SETTING ..............................62

Measurement setup upon transition to RRC-Connected state .............................................65

EventA3 and HO Measurement: ALGORITHM and CONFIGURATION ........................70

TARGET CELL SELECTION ...........................................................................................78

SYSTEM INFORMATION BLOCK TYPE5 ..................................................................89

TDD eNodeB LTE Parameters User Guide

EQUAL PRIORITY INTER-FREQUENCY CELL RESELECTION CRITERIA ............91

E-UTRAN INTER-FREQUENCY CELL RESELECTION CRITERIA ...........................93

INTER-FREQUENCY INTer-eNB HO..........................................................................95

THRESHOLDS FOR INTER-RAT MOBILITY WITH INTRA-LTE MEASUREMENTS:

SPEED STATE MEASUREMENTS CONFIGURATION ...........................................123

AUTOMATIC NEIGHBOUR RELATION (ANR) CONFIGURATION AND OPTIMISATION ............126

TDD eNodeB LTE Parameters User Guide

ANR Overview ................................................................................................................126

ANR MEASUREMENT CONFIGURATION .................................................................132

DRX Configuration for ECGI Retrieving .........................................................................137

Set Up X2 links .................................................................................................................138

Receiving Neighbor Relation through X2 Messages .................................................142

ANR in Dormant/Wake-up Phase ..............................................................................144

ANR Neighbor Relation Maintenance Function - Garbage Collection.......................146

RRC IDLE MODE MOBILITY: ..............................................................................................148

CELL RESELECTION ACTIVATION..............................................................................148

MIM MODEL ...................................................................................................................156

UE SPEED MANAGMENT ........................................................................................159

E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL RESELECTION CRITERIA161

ALGORITHM FOR CELL RESELECTION PRIORITY ..............................................165

TDD eNodeB LTE Parameters User Guide

REDIRECTION ACTIVATION ........................................................................................171

NEIGHBOR CELL INFORMATION PROVIDED TO UES IN CONNECTED MODE.181

THRESHOLDS FOR INTER-RAT MOBILITY and MEASUREMENTS for EVENT B2196

EUTRAN-TO-UTRAN-TDD PS HANDOVER ........................................................................201

Blind PS Handover Activation and Measurement Configuration ....................................202

Blind PS Handover Triggering and Target Cell Selection...............................................204

Control of PS Handover ..................................................................................................205

TDD eNodeB LTE Parameters User Guide

RRC IDLE MODE MOBILITY: ..............................................................................................217

CELL RESELECTION ACTIVATION..............................................................................218

CELL RESELECTION PRIORITIES HANDLING ......................................................224

E-UTRAN INTER-FREQUENCY AND INTER-RAT CELL RESELECTION CRITERIA227

ALGORITHM FOR CELL RESELECTION PRIORITY ..............................................232

REDIRECTION ACTIVATION ........................................................................................238

TDD eNodeB LTE Parameters User Guide

THRESHOLDS FOR INTER-RAT MOBILITY:...........................................................254

INTRA-FREQUENCY INTRA-ENB CALL FLOW: ................................................................262