You are on page 1of 46

Mobility Management in Connected

Mode
Serving Radio Conditions and UE Measurement Configurations
Serving Radio Conditions and UE Measurement Configurations

UE is configured to perform the following measurements for the life of the


call until UE moves out of the serving cell:

Event A3 intra-LTE intra-frequency measurement with


measurementPurpose = Mobility-Intra-Freq.

Event A2 measurements with measurementPurpose = Below-Serving-


Floor/Entering-Coverage-Alarm

Then it will configure or deconfigure events according to its new radio


condition
EX : when entering alarm radio condition, it will configure events for
mobility interfreq and/or interRAT
UE Measurement Report Trigger Types
• UE measurement report trigger types supported in eNB:
 Event A1 – UE sends measurement reports when serving is better than a
threshold value
 Event A2 – UE sends measurement reports when serving is worse than a
threshold value
 Event A3 – UE sends measurement reports when neighbor becomes offset
better than serving
 Event A5 – UE sends measurement reports when serving becomes worse
than threshold1 and neighbor becomes better than threshold2
 Event B1 – UE sends measurement report when Inter-RAT neighbor
becomes better than threshold
 Event B2 – UE sends measurement report when serving becomes worse
than threshold1 and inter-RAT neighbor becomes better than threshold2
Event A1
Conditions
• When event A1 is configured, UE will send measurement reports when the
serving cell becomes better than a threshold value.
• Event A1 is used for UE ‘Leaving-Coverage-Alarm’ monitoring
• Event A1 entering condition:
 Ms – hysteresis > thresholdEutraRsrp/thresholdEutraRsrq
• Event A1 leaving condition:
 Ms + hysteresis < thresholdEutraRsrp/thresholdEutraRsrq
Ms: measurement result of the serving cell
hysteresis: defined in reportConfigEUTRA::hysteresis
thresholdEutraRsrp: used if Rsrp is used for Ms. Defined in reportConfigEUTRA::thresholdEutraRsrp
(def -105dB).
thresholdEutraRsrq: used if Rsrq is used for Ms. Defined in reportConfigEUTRA::thresholdEutraRsrq.
Event A1
Ms
Diagram
conditions for Ms fulfilled

thresholdEutraRsrp/thresholdEutraRsrq hysteresis

reportAmount serving cell

reportQuantity time

reportOnLeave
timeToTrigger timeToTrigger
reportInterval

reportQuantity, reportAmount, timeToTrigger, reportInterval are defined in ReportConfigEutra MO


Event A2
Conditions
• When event A2 is configured, UE will send measurement reports when the
serving cell becomes worse than a threshold value.
• Event A2 is used for UE ‘Entering-Coverage-Alarm’ and ‘Below-Serving-Floor’
monitoring
• Event A2 entering condition:
 Ms + hysteresis < thresholdEutraRsrp/thresholdEutraRsrq
• Event A2 leaving condition:
 Ms - hysteresis > thresholdEutraRsrp/thresholdEutraRsrq
Ms: measurement result of the serving cell
hysteresis: defined in reportConfigEUTRA::hysteresis
thresholdEutraRsrp: used if Rsrp is used for Ms. Defined in reportConfigEUTRA::thresholdEutraRsrp.
Def -108 dB (Coverage Alm), -118 (below serving floor)
thresholdEutraRsrq: used if Rsrq is used for Ms. Defined in reportConfigEUTRA::thresholdEutraRsrq.
Event A2
Ms Diagram
conditions for Ms fulfilled

serving cell

thresholdEutraRsrp/thresholdEutraRsrq hysteresis

reportAmount

reportQuantity
time

reportOnLeave

timeToTrigger timeToTrigger
reportInterval

reportQuantity, reportAmount, timeToTrigger, reportInterval are defined in ReportConfigEutra MO


Event A3
Conditions
• When event A3 is configured, UE will send measurement reports when the
neighbor cell becomes offset better than the serving cell.
• Event A3 is used to trigger intra-frequency HO and inter-frequency
redirection/HO if UE does not support event A5 configuration.
• Event A3 entering condition:
 Mn > Ms + offset + hysteresis
• Event A3 leaving condition:
 Mn < Ms + offset – hysteresis
 offset = eventA3Offset + cellIndividualOffset_s + offsetFreq_s –
cellIndividualOffset_n – offsetFreq_n
Mn: measurement result of the neighbor cell.

Ms: measurement result of the serving cell.

hysteresis: defined in reportConfigEUTRA::hysteresis (def 2.5dB)

eventA3Offset: defined in reportConfigEUTRA::eventA3Offset (def 2dB)


Event A3
Mn
Ms Diagram
hysteresis

offset

serving cell

neighbor cell
reportAmount

reportQuantity time

reportOnLeave

timeToTrigger timeToTrigger
reportInterval

reportQuantity, reportAmount, timeToTrigger, reportInterval are defined in ReportConfigEutra MO


Event A5
Conditions
• When event A5 is configured, UE will send measurement reports when the
serving becomes worse than threshold1 and inter-frequency neighbor cell
becomes better than threshold2.
• Event A5 is used to trigger inter-frequency redirection/HO and intra-frequency
with ANR.
 Event A5 entering condition 1:
Ms + hysteresis < thresholdEutraRsrp/thresholdEutraRsrq
 Event A5 entering condition 2:
Mn + offset – hysteresis > threshold2EutraRsrp/threshold2EutraRsrq
 Event A5 leaving condition 1:
Ms – hysteresis > thresholdEutraRsrp/thresholdEutraRsrq
 Event A5 leaving condition 2:
Mn + offset + hysteresis < threshold2EutraRsrp/threshold2EutraRsrq
offset = cellIndividualOffset_n + offsetFreq_n
Event A5
Mn
Diagram
Ms conditions for Mn fulfilled

conditions for Ms fulfilled


threshold2EutraRsrp/threshold2EutraRsrq

hysteresis offset

serving cell
thresholdEutraRsrp/thresholdEutraRsrq

reportAmount hysteresis neighbor cell

reportQuantity time

reportOnLeave
timeToTrigger timeToTrigger
reportInterval

reportQuantity, reportAmount, timeToTrigger, reportInterval are defined in ReportConfigEutra MO


Event B1
Conditions
• When event B1 is configured, UE will send measurement reports when the
inter-RAT neighbor cell becomes better than a threshold value. Event B1 is
used for CS fallback to UTRAN and GERAN.
• Event B1 entering condition:
 Mn + offsetFreqInterRAT – hysteresis > thresholdInterRAT
• Event B1 leaving condition:
 Mn + offsetFreqInterRAT + hysteresis < thresholdInterRAT
 Mn: measurement result of the neighbor cell
hysteresis: defined in ReportConfigUTRA/ReportConfigGERAN/::hysteresis
offsetFreqInterRAT: defined in MeasObjectUTRA::offsetFreqUTRA or MeasObjectGERAN::offsetFreqGERAN
Depending on the type of iRAT network (UTRAN or GERAN), thresholdInterRAT corresponds to the following
parameter:
- GERAN: ReportConfigGERAN::thresholdGeran
- UTRAN: ReportConfigUTRA::thresholdUtraEcNo
ReportConfigUTRA::thresholdUtraRscp
Event B1
Mn
Diagram
conditions for Mn fulfilled

thresholdInterRAT hysteresis

reportAmount neighbor cell

reportQuantity time

reportOnLeave

timeToTrigger timeToTrigger
reportInterval

reportQuantity, reportAmount, timeToTrigger, reportInterval are defined in ReportConfigUTRA/ReportConfigGERAN MO


Event B2
Conditions
• When event B2 is configured, UE will send measurement reports when the
serving becomes worse than threshold1 and inter-RAT neighbor cell becomes
better than threshold2. Event B2 is used to trigger inter-RAT mobility
• Event B2 entering condition 1 (Serving cell):
 Ms + hysteresis < thresholdEutraRsrpB2/thresholdEutraRsrqB2
• Event B2 entering condition 2 (Neighboring cell):
 Mn + offsetInterRAT – hysteresis > thresholdInterRAT
• Event B2 leaving condition 1:
 Ms – hysteresis > thresholdEutraRsrpB2/thresholdEutraRsrqB2
• Event B2 leaving condition 2:
 Mn + offsetInterRAT + hysteresis < thresholdInterRAT
Depending on the type of iRAT network (UTRAN or GERAN), thresholdInterRAT corresponds to:
GERAN: ReportConfigGERAN::thresholdGeran
UTRAN: ReportConfigUTRA::thresholdUtraEcNo
ReportConfigUTRA::thresholdUtraRscp
Event B2 Diagram
conditions for Mn fulfilled
thresholdInterRAT
conditions for Ms fulfilled

offsetFreqInterRAT
hysteresis

thresholdEutraRsrpB2

serving cell
reportAmount hysteresis
neighbor cell
reportQuantity
time

reportOnLeave

timeToTrigger reportInterval timeToTrigger


RRC Measurements ALU Object Model
Ue
Measurement
Conf

[1..32] [1..32]

[1..48]
List of
ReportConfig MeasObject
Measurement
IdentityConf
[1..8] [0,1] [0,1]
ReportConfig MeasObject
[1..6] eUTRA
RrcMeasurement eUTRA
Conf

[0,1] [0,1]
ReportConfig MeasObject
UTRA UTRA

[0,1] [0,1]
ReportConfig MeasObject
GERAN GERAN

LteCell
RRC Measurements ALU Object Model

Example of basic RRC measurement :

Object eUTRAN, mobility_intra_freq (event A3)


Object eUTRAN, below_serving_floor(event A2)
Object eUTRAN, entering_coverage_alarm (event A2)
Object eUTRAN, leaving_coverage_alarm (event A1)
Object UTRAN, mobility inter RAT to UTRA (event B2)
Emcta overview
• eMCTA(evolved Multi-Carrier Traffic Allocation) is a proprietary feature located in
the eNB
• eMCTA aims at providing a sorted list of RAT/carriers for measurements or for
blind handover based on a flexible operator’s configuration. Following mobility is
supported by eMCTA:
 inter-frequency LTE neighboring carriers
 inter RAT GERAN neighboring carriers
 inter-RAT UTRAN neighboring carriers
• eMCTA can be invoked either by following events:
 serving radio monitoring via RRC Measurement
 CSFB indicator from the MME
 eNB Reactive Load Control
 eNB Preventive Load Control
 eNB ANR function
• eMCTA is invoked only in the RRC-connected mode
eMCTA role among other eNB processes
Preventive Load Control Configured neighbor RAT/carriers for
LTE or GERAN or UTRAN (Fdd or Tdd)
ANR inter RAT/carriers or HRPD
Reactive Load Control
Measurement Based Mobility
Meas. report for A2_CA
RRC Measured candidate RAT/
CS Fallback indicator
Measurement Carriers sorted list eMTCA
Meas. report for A2_floor Blind mobility
process Framework
Blind candidate RAT/carrier
Inter-freq/RAT Measurement Sorted list
configuration

Only one single best carrier is


Meas. Report for
selected for blind redirection
events A3,A4,A5, UE Capabilities
B1,B2 Mobility
procedures
Cell Change Order (LTE > GERAN)
Redirection
output
PS Handover (LTE > UTRAN)
Inter-Frequency HO intput
Focus on eMCTA Process
Preventive Load Control
ANR inter RAT/carriers
Reactive Load Control
Meas. report for A2_CA
Meas. report for A2_floor
CF Fallback Indicator

1 UE Capability
UE Capabilities
Filter 2 Mobility Path
Information
3 Network Capability
4 Service-based Policy
Neighbor RAT/Carrier List 5 QCI-based Policy
6 Frequency Load

- Candidate1 RAT/carrier Candidate RAT/carrier sorted list with for each candidate:
- Candidate2 RAT/carrier
- Candidate3 RAT/carrier
Target Measurement Configuration (B2/B1, A5/A3, A4 or none)

Priority (0-lowest to 7-highest)

Whether a Measurement Gap needs to be configured (yes/no)


Object Model for eMCTA
LteCell

[0..1] [0..1] [0..1] [0..1]

LteNeighboring UtraNeighboring GeranNeighboring HrpdNeighboring

[1..2]

HrpdBandClassConf

[1..9] [0..16] [0..16] [0..3]


LteNeighboring UtraFddNeighboring GeranNeighboring HrpdNeighboring
FreqConf FreqConf FreqConf FreqConf

MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable


Mobility Priority Table
Only for RAT supporting CSFB.
Applicable to Service-Based Policy MobilityPriorityTable Applicable to QCI-Based Policy
(CSFB) when (non-CSFB) when
isServiceBasedTrafficSegmentation isServiceBasedTrafficSegmentationAllowed =
Allowed = True True
defaultConnectedPriorityOfFreq

[0..4] [0..32]

Possible values:
ServiceTypePriorityConf qci1 to qci255 qciPriorityConf

serviceType qciHierarchyForMultiQciCallList
eMctaPriority qci
eMctaPriority

Possible values: Possible Values: Lists the QCIs in order of importance for
csfbByIdleUE, emergencyCsfbByIdleUE, serviceOrQci-not-allowed-in-RAT- carrier, mobility purpose. Up to 32 entries
csfbByConnectedUE, 0-lowest, 1, 2, 3, 4, 5, 6, 7
emergencyCsfbByConnectedUE
LTE TO LTE MOBILITY in Connected mode
LTE Handover
• According to the eNB involvement, there are intra-eNB or INTER-eNB (intra-
freq and INTER-freq) handovers
• The LTE intra frequency handovers are triggered by event A3
flag isIntraFreqMOBILITYAllowed
• The LTE INTER frequency handovers are triggered by event A5 or A3
flag isINTERFreqEutraSameFrameStructureMOBILITYAllowed

• X2 or S1 based handover can be defined for INTER-eNB; hence, data


forwarding(managed per bearer type) can be activated to improve the HO
performance if the X2 link is declared (flag dataForwardingForX2HOEnabled)

X2 MMESGW
S1

eNodeB eNodeB
eNodeB
Intra eNB MOBILITY Data Flow
MME/SGW

DL Data
RrcIntraEnbHo timer
Measurement Report
HO Decision  MeasurementConfiguration
 MOBILITYControlInformation
Setup UE associated resources TargetPCI, dlEARFCN,
in the target cell measurementBandwidth,
Target cell, pmax,
T304 timer RRC Connection Reconfiguration radioResourceConfigCommon.
 T304.
Detach from old Switch DL to Target
 rach-ConfigDedicated
cell and synchronize cell Start receiving UL
 RadioResourceConfigDedicated
to new cell in Target cell
DL Data
Random Access preamble

Random Access Response

Start transmitting
DL in target cell
RRCConnectionReconfigurationComplete

Release UE associated
resources in the source cell
INTER eNB MOBILITY over X2 Data Flow
SeNB teNB MME

Measurement Report
Handover Decision with
Target Cell Selection
X2 Handover Request

Setup UE context & associated

Handover Preparation
resources in the target cell
AS security algorithms selection
and key derivation
X2 Handover Request Acknowledge
DL Data

Start Forwarding DL
Packets to Target DL Data Forwarding
RRC Connection Reconfiguration Start Buffering DL
MeasurementConfiguration
Packets
RadioResourceConfigDedicated
MOBILITYControlInformation
UE Related Information
security information
INTER eNB MOBILITY over X2 Data Flow
MME/SGW
SeNB teNB

Handover Execution
Random Access Preamble
Random Access Response
RRCConnectionReconfigurationComplete

Start Transmitting
DL Packets
DL Data

S1 Path Switch Request


UE Security Capabilities

Handover Completion
S1 Path Switch Request Ack
Security Context

Start buffering
packets from S1
Transmit all DL X2
packets before S1 packets
X2 UE Context Release

Release UE context X2 Release


and associated resources resource
INTER eNB MOBILITY over S1 Data Flow
SeNB MME
teNB

Measurement Report
Handover Decision with
Target Cell Selection
S1 Handover Required
Handover Type & Target ID S1 HO Request
UE Context Information

Handover Preparation
Handover Type (Intra LTE)
AS Information E-RABs to Setup List
E-RABs List UE Security Capabilities
Setup UE Context & Security Context
Assoc Resources
Including UE Capabilities
S1 HO Request Acknowledge
E-RABs Admitted List
E-RABs Failed to Setup List
Start Buffering
Forwarded Packet
S1 Handover Command
Handover Type & Target ID
RRCConnectionReconfiguration
E-RABs Subject to
MOBILITY control information Forwarding List
securityConfigurationHO S1 eNB Status Transfer E-RABs to Release List
handoverType = LTE
S1 MME Status Transfer
INTER eNB MOBILITY over S1 Data Flow
SeNB teNB MME

Start Forwarding DL
Packet to Target eNB
DL Data Forwarding (direct or indirect through SGW)
Random Access Preamble

Handover Execution and Completion


Random Access Response
RRCConnectionReconfigurationComplete

Start Transmitting forwarded DL


Packet to UE
S1 HO Notification

Path
Start buffering packet from S1 Switch

DL Data
Start Transmitting forwarded DL Packet
before S1 packets to UE
S1 UE Context Release Command
Release UE context and Release data forwarding resources
associated resources
S1 UE Context Release Complete
LTE MOBILITY in connected mode:LTE to UTRAN
LTE TO UTRAN MOBILITY in connected
mode
• The aim of MOBILITY in connected mode is to enable UE move from an LTE
radio coverage to WCDMA radio coverage with an on-going packet data session

• The triggering condition is because of the LTE radio condition has degraded
below a pre-defined threshold and the neighboring WCDMA cell has become
better than a pre-defined threshold

• For UE in RRC Connected mode, there are two possibilities to go from LTE to
UTRAN : Redirection (may be enhanced) or PS HANDOVER

• Comparing to Release/redirection, PS Handover allows the target UTRAN cell


radio and network resources to be set-up prior to the handover, therefore
reduces service INTERruption time, and ensures better performance for delay
and packet loss sensitive services, such as VoIP and TCP based applications
LTE TO UTRAN MOBILITY in connected mode
iRat redirection
In RRC_Connected mode, the eNB may trigger a procedure of RRC Release with
Redirection Information (IE redirectedCarrierInfo):
– if this is enabled if isMOBILITYToUtraAllowed=TRUE and if
– the UE must also be eligible for redirection to UTRA-FDD i.e. support UTRA-FDD
– and if MOBILITY to UTRA not forbidden for UE in S1AP HandoverRestrictionlist
– the redirection can be blind or based on INTER RAT measurement to UTRA-FDD
Handover
CELL_DCH E-UTRA
RRC_CONNECTED
Redirection to UTRAN triggers:
Handover
- A MeasReport with event B2 and purpose CELL_FACH
RRC Connection
“MOBILITY INTER-RAT to UTRA”: this is the
Establishment
measurement Based Redirection when the CELL_PCH
PS HO cannot be performed URA_PCH RRC Connection
Reselection
Release (with
Connection redirection info)
- A MeasReport with event A2 and purpose establishment/releas
“Below Serving Floor”: Blind Redirection to e
RAT frequency with highest Reselection E-UTRA RRC_IDLE
UTRA_Idle
cellReselectionPriority
Reselection
LTE TO UTRAN MOBILITY in connected mode
iRat redirection
MME

Control Procedure for MOBILITY


Reception of event A2 or B2

Release/Cell redirection Execution Phase


RRC Connection Release

releaseCause:: Other S1-AP UE Context Release Request


redirectedCarrierInfo:: utra-FDD MME UE S1AP ID
idlemodeMOBILITYControlInfo::cellReselectionPriority eNB UE S1-AP ID
of utra-FDD carrier freq Cause=INTERRat Redirection

Redirection Information
To Target RAT with RRC Connection
Release: UE leaves EUTRAN Old Cell &
start Access Target RAT new cell

The target carrier in the redirectedCarrierInfo IE is set as


below:
- It is the highest priority carrier selected by eMCTA if
redirection is blind
- It is the measured carrier if the redirection is
measurement-based
LTE TO UTRAN MOBILITY in connected mode
iRat redirection
MME

S1-AP UE Context Release Command


Release/ Cell Redirection Completion Phase
MME UE S1AP ID
eNB UE S1-AP ID
Cause=Normal Release

S1-AP UE Context Release Complete


MME UE S1AP ID
eNB UE S1-AP ID

MME Keeps UE Context


eNB Releases UE context

eNB Releases associated MME releases associated


old resources S1 resources
LTE TO UTRAN MOBILITY in connected mode
PS handover
• PS handover to UTRA is activated when both
ActivationService::isMOBILITYToUTRANAllowed and
ActivationService::isPsHoToUtraAllowed are set to TRUE
• RNC should support PSHO
RncAccess::PsHandoverUtraEnabled
• PS handover is triggered when UE enters coverage alarm area and sends an
event B2 measurement report with
MeasurementIdentityConf ::measurementPurpose set to ‘MOBILITY-INTER-
RAT-to-UTRA’ in the appropriate MeasurementIdentityConf

• LTE to UTRAN PS handover procedure has the following two phases:


 Handover Preparation Phase
 Handover Execution Phase
LTE TO UTRAN MOBILITY in connected mode
PS handover Preparation phase
• PS handover is triggered by eNB receives event B2 measurement report with
measurement purpose set to ‘MOBILITY-INTER-RAT-to-UTRA’ or event B1
measurement report with measurement purpose set to ‘MOBILITY-INTER-RAT-
to-UTRA’ (for CS fallback)
• eNB sends Handover Required to MME and starts a timer with duration
PsHOToUtraTimersConf::tS1RelocPrepForPsHandoverToUtra waiting to
receive Handover Commend from MME
• If reservation of resources in the target UTRAN cell is successfully completed,
MME will send a Handover Command message to eNB. eNB will then stops the
timer TS1relocprep and enter the handover execution phase.
• If timer expires or MME sends S1 Handover Preparation Failure message,
handover preparation fails. In this case, if PS handover is triggered due to CS
fallback, eNB will trigger a measurement-based redirection to UTRAN;
otherwise, event B2 measurement report will be ignored
LTE TO UTRAN MOBILITY in connected mode
PS handover Preparation phase
MME

Triggers:
-a B2 measurement report is received
-a B1 measurement report is received

HO Required
MME-UE-S1AP-ID
eNB-UE ID
HandoverType=LTEtoUTRAN

Handover Preparation
Cause=handover-desirable-for-radio-Reason
TS1RELOCprep TargetIDDirect-Forwarding-Path-Availability
Source-ToTarget-TransparentContainer

HO Command
MME-UE-S1AP-IDeNB-UE-S1AP-
IDHandoverType=LTEtoUTRANNASSecurityParametersf
romE-UTRANE-RABSubjecttoDataForwardingListE-
RABtoReleaseListHOCmdTarget-ToSource-
TransparentContainer
LTE TO UTRAN MOBILITY in connected mode
PS handover execution phase
• Once a Handover Command is received from MME, eNB will will stop timer
TS1relocprep and start timer with duration
PsHoToUtraTimersConf::tS1RelocOverallForPsHandoverToUtra and sends a
MOBILITYFromEutraCommand to UE with purpose set to ‘handover’ and
targetRAT-Type set to ‘utra’;
• If ActivationService::isUtraDataForwardingAllowed is set to TRUE, eNB will
start data forwarding each E-RAB listed in E-RABSubjecttoDataForwardingList
received in the Handover Command message from MME
• If UE Context Release Command is received from MME before the timer expires,
PS handover is successful; eNB will send a UE Context Release Complete to MME;
eNB will stop timer TS1relocoverall and release UE context and associated
resources
• If timer TS1relocoverall expires, eNB considers the UE to have lost radio
coverage and will trigger the release of all UE associated resources by sending
an UE Context Release Request to MME and release all UE associated resources
in eNB
LTE TO UTRAN MOBILITY in connected mode
PS handover execution phase
MME

Handover Execution Handover Release


HANDOVER COMMANDMME-UE-S1AP-ID
RRC MOBILITY FROM EUTRA COMMAND eNB-UE-S1AP-ID
cs-FallbackIndicator = false HandoverType=LTEtoUTRAN
TS1RELOCoverall NASSecurityParametersfromE-UTRAN
purpose = handover E-RABSubjecttoDataForwardingList
 targetRAT-Type = utra E-RABtoReleaseListHOCmd
 targetRAT-MessageContainer Target-ToSource-TransparentContainer
 nas-SecurityParamFromEUTR

UE CONTEXT RELEASE COMMAND


MME-UE-S1AP-ID
The UE synchronizes to the ENB-UE-S1AP-ID
Indicated UTRAN cell and Cause=normal-release
completes the HO
UE CONTEXT RELEASE COMPLETE
MME-UE-S1AP-ID
ENB-UE-S1AP-ID

MME releases
eNB releases the UE
Associated S1
Context and associated
resources
resources
AGENDA

LTE MOBILITY in connected mode:LTE to GERAN


LTE to GERAN MOBILITY in connected mode
• EUTRAN to GERAN RRC connected mode MOBILITY procedures include blind
redirection and measurement based redirection procedures, enhanced
redirection procedures and Cell Change Order procedure
• When eNB receives an event A2 measurement report from UE with
measurementPurpose = Below-Serving-Floor (UE enters bad air condition
area), a blind redirection from LTE to GERAN can be triggered
• When eNB receives an event B2 measurement report from UE with
measurementPurpose = MOBILITY-INTER-RAT-to-GERAN, if the Cell Change
Order to GERAN is not supported by the UE or is not activated in eNB, a
measurement based redirection from LTE to GERAN is triggered
• LTE to GERAN enhanced redirection is supported also by ALU eNB. It provides
system information of the GERAN cells under the redirected carrier to the UE
when it is released from LTE and redirected to the GERAN carrier. This
functionality can be used for CSFB or non-CSFB redirection from LTE to
GEERAN. LTE to GERAN enhanced redirection is activated if
ActivationService::isCsfbEnhancedRedirectionAndPsHoAllowed is set to
‘True’
LTE TO GERAN MOBILITY in connected mode
iRat redirection
MME

Control Procedure for MOBILITY


Reception of event A2 or B2

Release/Cell redirection Execution Phase


RRC Connection Release

releaseCause:: Other S1-AP UE Context Release Request


redirectedCarrierInfo:: geran MME UE S1AP ID
startingARFCN eNB UE S1-AP ID
bandIndicator Cause=INTERRat Redirection
FollowingARFCN

The UE selects a suitable cell on


the GERAN frequency group
indicated by the RedirectedCarrierInfo

The target carrier in the redirectedCarrierInfo IE is set as


below:
- It is the highest priority carrier selected by eMCTA if
redirection is blind
- It is the measured carrier if the redirection is
measurement-based
LTE TO GERAN MOBILITY in connected mode
iRat redirection
MME

S1-AP UE Context Release Command


Release/ Cell Redirection Completion Phase
MME UE S1AP ID
eNB UE S1-AP ID
Cause=Normal Release

S1-AP UE Context Release Complete


MME UE S1AP ID
eNB UE S1-AP ID

MME Keeps UE Context


eNB Releases UE context

eNB Releases associated MME releases associated


old resources S1 resources
LTE to GERAN MOBILITY
Cell change order (CCo)
• ALU LTE LR13.3 portfolio supports measurement based LTE-to-GERAN MOBILITY
procedure – Cell Change Order (CCO)

• Cell Change Order is activated with both


 ActivationService::isMOBILITYToGeranAllowed
 ActivationService::isGeranCcoAllowed

• ALU implementation includes a procedure for eNB to retrieve system


information broadcasted in each of the neighbor GERAN cell through MME : CCO
is with NACC in this case.

• The information will be included in Cell Change Order sent to UE when it is


released from eNB and directed to GERAN. This is to speed up UE call setup in
GERAN.
LTE to GERAN MOBILITY
Cell change order (CCo)
MME

LTE to GERAN MOBILITY: CCO


Measurement Report (event B2)

eNB decides CCO (supported by UE)

eNB sends CCO indicating the target


MOBILITY From EUTRA Cmd (geran, phyCellId, carrier, SysInfo) GERAN and may include GERAN SysInfo
(retrieved from MME) for the target cell

eNB synchronizes with the


GERAN target cell

UE Context Release Command

UE Context Release Complete


LTE to GERAN MOBILITY
Cco procedure
• When eNB receives a UE event B2 or event B1 (for CS fallback) report with
measurement purpose set to ‘MOBILITY-INTER-RAT-to-GERAN’, if CCO is
activated in serving cell and UE supports CCO, CCO procedure will be triggered.
Otherwise, redirection to GERAN will be triggered
• eNB will send the MOBILITYFromEUTRACommand to UE with purpose set to
‘CellChangeOrder’. The message also includes target carrierFreq, phyCellId,
GeranNeighboringCellRelation::networkControlOrder,
UeTimer::t304CellChangeOrder, and target cell systemInformation if
available. At timer expiry the UE initiates the RRC connection re-establishment
procedure. eNB will start a timer with duration
NaccTimersConf::tMOBILITYFromEutraCCO
• If UE Context Release Command is received from MME before the timer
expired, CCO procedure is completed successfully; eNB will reply with a UE
Context Release Complete and release resources associated with the UE.
Otherwise (timer expires), eNB will send a UE Context Release Request to MME
to trigger the release of the resources

You might also like