06 RA41336EN60GLA1 LTE Mobility Connected Mode

Mobility measurements
RA41336EN60GLA1 1
RA41336EN60GLA1 4
RA41336EN60GLA1 5
RA41336EN60GLA1 6
RA41336EN60GLA1 7
RA41336EN60GLA1 8
RA41336EN60GLA1 9
• A Handover will be initiated by a measurement report sent via the RRC

protocol
• Upon the reception of this measurement report, the handover algorithm
will decide whether a handover should take place
• In response to the handover decision, the handover execution will be
carried out using the corresponding procedures
• After the handover execution, the handover algorithm will be informed,
whether the handover was successful or not
• The Handover procedure is composed of a number of single functions:
- Measurements
- Filtering of measurements
- Reporting of measurement results
- Hard handover algorithm
- Execution of handover
RA41336EN60GLA1 10
RA41336EN60GLA1 11
RA41336EN60GLA1 12
RA41336EN60GLA1 13
RA41336EN60GLA1 14
RA41336EN60GLA1 15
RA41336EN60GLA1 16
RA41336EN60GLA1 17
RA41336EN60GLA1 18
RA41336EN60GLA1 19
RA41336EN60GLA1 20
RA41336EN60GLA1 21
A Late Handover is a sequence of a missed HO attempt (instead of HO: RLF on UE

side and optionally recoverable RLF on eNB side) in one cell followed by RRC
connection re-establishment request in another cell.
An Early Handover Type 1 is a sequence of a failed HO attempt followed by RRC
connection re-establishment in the HO source cell.
An Early Handover Type 2 is recognized in the following cases: Case 1: An Early
Handover Type 2 is a sequence of a successful connection establishment in HO target
cell (attempted HO completed) followed by RRC connection re-establishment in
another cell a short time after 'HO completion'. Case 2: An Early Handover Type 2 is a
sequence of a successful random access in HO target followed by failed Msg3
reception (attempted HO not completed) followed by re-establishment request in
another cell.
As output MRO may calculate updated values for:

•cell-individual Offset (CIO) of the neighbor cell in the identified neighbor relation of
the serving cell - in the LNREL object of the serving cell containing this NR
•TimeToTrigger (TTT) of all neighbor cells in the serving cell carrier frequency - in the
LNCEL object of the serving cell
RA41336EN60GLA1 22
RA41336EN60GLA1 23
RA41336EN60GLA1 24
RA41336EN60GLA1 25
RA41336EN60GLA1 26
RA41336EN60GLA1 27
RA41336EN60GLA1 28
RA41336EN60GLA1 29
RA41336EN60GLA1 30
RA41336EN60GLA1 31
RA41336EN60GLA1 32
RA41336EN60GLA1 33
RA41336EN60GLA1 34
RA41336EN60GLA1 35
RA41336EN60GLA1 36
RA41336EN60GLA1 37
RA41336EN60GLA1 38
RA41336EN60GLA1 39
RA41336EN60GLA1 40
RA41336EN60GLA1 41
RA41336EN60GLA1 42
RA41336EN60GLA1 43
RA41336EN60GLA1 44
RA41336EN60GLA1 45
-The feature may be used when the X2 interface between

Source and Target eNB may be not existing, not operable or the
usage for handover may be forbidden by O&M.
-Source eNodeB will decide whether a handover is executed via
X2-Interface or via S1-interface. Core Network has no possibility
to influence this decision.
-In opposite to the X2-based Intra and inter eNB handover (see
LTE53), the S1-based handover is routed via the Core Network
and therefore provides the possibility to the Core to change the
serving MME and/or the serving S-GW.
-In addition the S1-based handover can perform handover
between different vendor's eNB even if an open X2-Interface is
not supported.
RA41336EN60GLA1 46
RA41336EN60GLA1 47
RA41336EN60GLA1 48
RA41336EN60GLA1 49
RA41336EN60GLA1 50
RA41336EN60GLA1 51
RA41336EN60GLA1 52
RA41336EN60GLA1 53
RA41336EN60GLA1 54
RA41336EN60GLA1 55
RA41336EN60GLA1 56
RA41336EN60GLA1 57
RA41336EN60GLA1 58
RA41336EN60GLA1 59
RA41336EN60GLA1 60
Load Supervision and Exchange

Each cell measures DL GBR, DL non-GBR and PDCCH load periodically and
exchanges load information between cells of the same eNB
eNB decides whether the cell enters or exits active inter-frequency load
balancing (iF-LB) state
Candidate UE Selection for measurement solicitation
UEs entering Connected state are considered candidates for measurement
solicitation hence avoiding further increase in existing cell load
Already connected UEs are NOT offloaded to neighbor cells via load-based HOs
UEs with QCI1 bearers established may be excluded from offloaded UEs
depending on parameterization
Measurement Solicitation
A4 measurements is activated if candidate UE’s serving cell is in active iF-LB state
iF-LB Execution
Target cell list (TCL) is created based on received RSRP, RSRQ and load
measurements
TCL is then sorted and highest ranked neighbor cell is chosen as target cell for
offloading
Load-blind HO is supported if load information is not available (ex. Inter-eNB
target cells)
RA41336EN60GLA1 61
RA41336EN60GLA1 62
RA41336EN60GLA1 63
RA41336EN60GLA1 64
RA41336EN60GLA1 65
RA41336EN60GLA1 66
•CS Fallback related features in RL20

CS Fallback to UTRAN or GSM via Redirect (LTE562) – introduces service-
based redirection from LTE to UTRAN or GERAN whenever CS voice
call is to be set-up
Emergency Call Handling (LTE22) – introduces means for special
handling of emergency calls in the context of CS Fallback procedure
CS Fallback to UTRAN with System Information – CSFB towards UTRAN
via redirection has been enhanced with provisioning of System
Information of potential target cells (only towards 3GPP R9
compliant UEs)
CS Fallback to UTRAN via PS HO (LTE736) – CSFB towards UTRAN
realized via PS HO mechanism
GSM Redirect with System Information (LTE984) – CS Fallback to GERAN
via redirection will be enhanced with provisioning of System
Information of potential target cells (only towards 3GPP R9
compliant UEs) this enhancement applies also to RRC Connection
Release with Redirection (LTE423)
RA41336EN60GLA1 67
RA41336EN60GLA1 68
• Please note that hysteresis is used to prevent ping-pong effect between entering
and leaving conditions; parameter common both for serving and neigbour cell
RA41336EN60GLA1 69
• Please note that hysteresis is used to prevent ping-pong effect between entering
and leaving conditions; parameter common both for serving and neigbour cell
RA41336EN60GLA1 70
Requirements:
• License: Pool license - Long-term ON/OFF BTS license
RA41336EN60GLA1 71
RA41336EN60GLA1 72
RA41336EN60GLA1 73
RA41336EN60GLA1 74
RA41336EN60GLA1 75
RA41336EN60GLA1 76
*This functionality is only applicable for multimode devices supporting both

LTE and CDMA2000 eHRPD technologies and given frequency band
RA41336EN60GLA1 77
*data forwarding isn’t applied for eHRPD HO so no S103 interface is needed

(this interface is used in User Plane interface to forward DL data to minimize
packet losses in mobility from E-UTRAN to eHRPD)
RA41336EN60GLA1 78
RA41336EN60GLA1 79
RA41336EN60GLA1 80
RA41336EN60GLA1 81
RA41336EN60GLA1 82
RA41336EN60GLA1 83
RA41336EN60GLA1 84
NVS – Nokia Mobile VoIP Server

SCC AS - Service Centralization and Continuity Application Server
RA41336EN60GLA1 85
After handover completion, UE performs RAU to established the PS bearers (which

could not be established together with the CS-handover) via the Iu-PS
RA41336EN60GLA1 86
After HO data ig going from SGSN to PGW and vice versa

VoIP connection is handed over to UTRAN CS while other PS bearers are
simultaneously handed over to UTRAN PS
RA41336EN60GLA1 87
UE runs out of LTE coverage, GSM measurements are activated and SRVCC to GSM is
triggered (in the same way as for eNACC to GSM).
eNodeB initiates S1-HO towards GSM indicating SRVCC for CS only and sets
indication „PS Service Not Available“
CS-Handover (incl. SRVCC) towards GSM is executed. MME suspends PS services
UE is served in GERAN connected via CS domain only
VoIP connection is handed over to GSM CS but other PS bearers are suspended and
they could be resumed only after performing Routing Area Update – after the CS call
end!
RA41336EN60GLA1 88
UE is served in GERAN connected via CS domain only (no suspension of PS by

MME)
PS bearers are established again after performing Routing Area Update – during
the CS call (with the help of DTM mode)
RA41336EN60GLA1 89
RA41336EN60GLA1 90
RA41336EN60GLA1 91
RA41336EN60GLA1 92
RA41336EN60GLA1 93
RA41336EN60GLA1 94
RA41336EN60GLA1 95
RA41336EN60GLA1 96
UDP: User Datagram Protocol ( L4 Transport Layer) . Similar to TCP but only
provides connectionless service.
RA41336EN60GLA1 97
RA41336EN60GLA1 98
RA41336EN60GLA1 99
RA41336EN60GLA1 100
RA41336EN60GLA1 101
RA41336EN60GLA1 102
HeNB = femto
The access to HeNB may be open, or closed (Closed Subscriber Group – CSG), when
only selected users can connect to it
LTE1442 feature supports only Open Access HeNBs
A single range of PCI can be configured in the Macro eNB for HeNB usage per
frequency  up to 503 PCI’s
RA41336EN60GLA1 103
- LTE BTS sets the cause value of the S1AP UE Context Release Request message to
"Radio Network Layer (Inter-RAT redirection)"
RA41336EN60GLA1 104
RA41336EN60GLA1 105

06 RA41336EN60GLA1 LTE Mobility Connected Mode

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

06 RA41336EN60GLA1 LTE Mobility Connected Mode

Diunggah oleh

Hak Cipta:

Format Tersedia

Mobility measurements

• A Handover will be initiated by a measurement report sent via the RRC

A Late Handover is a sequence of a missed HO attempt (instead of HO: RLF on UE

As output MRO may calculate updated values for:

-The feature may be used when the X2 interface between

Load Supervision and Exchange

•CS Fallback related features in RL20

*This functionality is only applicable for multimode devices supporting both

*data forwarding isn’t applied for eHRPD HO so no S103 interface is needed

NVS – Nokia Mobile VoIP Server

After handover completion, UE performs RAU to established the PS bearers (which

After HO data ig going from SGSN to PGW and vice versa

UE is served in GERAN connected via CS domain only (no suspension of PS by

Anda mungkin juga menyukai