RAN2264 Smart LTE Handover For NPI

You can setup the color/gradient and outline style of selected shapes with the “Shape_set_color_and_gradient” macro, or by clicking
RAN2717
RAN2264 Smart LTE Handover
For internal use

1 © Nokia Solutions and Networks 2014 Network Engineering / Marek Wojtyna / 27.02.2014
Smart LTE Handover
Introduction
1 Motivation and Feature Overview
Interdependancies
2 Interdependancies with other features or functions
Deployment Aspects
3 Activation, Trial Area
4 Configuration Management
Parameters and Parameterization Scenarios
Performance Aspects
5 Counters and KPIs
For internal use

Introduction Table of Contents

WCDMA – LTE Interworking from WCDMA perspective
• RAN2067 LTE Interworking (RU20 On Top) and

RAN3069 RSRQ based LTE Reselection (RU50)
WCDMA - LTE Interworking overview
• The UE, on operator’s preference, selects to camp on LTE
layer based on absolute layers’ priorities once coverage is
available.
• RAN3069 introduces quality criteria (Squal related)
andover
LTE PS H •
RAN2176 RAN2176 LTE PS Handover (RU20 On Top)
• Seamless handover of data services to WCDMA when leaving
RAN2435 SRVCC fro
Cell_DCH m LTE and CSFB wit
h HO RRC_CONNECTED the LTE coverage with minimal interruption time.
RAN2
• Multi-RAB handover is supported.
26 4 Sm
art LT
E Han
• RAN2435 SRVCC from LTE and CSFB with HO (RU40)
RA dove
Cell_FACH RA 2 N r • Single Radio Voice Call Continuity from LTE to WCDMA allows
N2 980 LTE VoIP call to be handed over to WCDMA as a normal CS
71 M
7 S ea
m sur voice call.
ar
Cell_PCH t L em e • CS Fallback support (if VoLTE call cannot be setup, for
RA TE nt
N2 L a ba
RA
0 67 ye sed realization of the voice call the UE is handed over to WCDMA
URA_PCH N3
LT
EI ri n
g LTE for CS connection setup)
0 69 nte
RS r w La
o
RQ
ba
r ki
ng
ye
ri n • RAN2717 Smart LTE Layering (RU40)
sed g
LT
ER
• Efficient mechanisms for moving active UEs to the LTE layer
ese (RRC Connection Release with Redirection command to LTE).
le c
tio
UTRA_IDLE RAN20
n
RRC_IDLE • RAN2264 Smart LTE Handover (RU50)
67 LTE
Interwo
rking • WCDMA-LTE outgoing PS handover once LTE coverage is
RAN306 available
9 RSRQ
based L
TE Rese
lection • RAN2980 Measurement based LTE Layering (RU50)
• Moving active UEs to the LTE layer (measurements of LTE
layer are done before redirection command)
For internal use


Smart LTE Handover
Brief Description:
• This mechanism is a next step on WCDMA – LTE interworking path.
• Inter-RAT handover from WCDMA to LTE starts if compressed mode (or non-compressed
mode) measurements indicate that LTE coverage is available.
• Measurements are triggered by the same events as for RAN2980 Measurement Based 3G
LTE
LTE Layering feature (Inactivity, CTS, CS RAB release, Periodic check)
• Target system can be FDD-LTE and TDD-LTE
„H
an C
UE in WCDMA
do om
Cell_DCH Benefits:
ve m
r f an
ro d ”
m
Load balancing End user experience

UT
RA
UE in LTE
• Support of traffic steering and network load balancing scenarios -
N
EMM_CONNECTED
offloading WCDMA network during high load states via seamless
handover to LTE
• Support of current strategy in initial phase of deployment of LTE
networks: move any LTE capable UE to LTE; let them only to
LTE coverage ov erage perform CS calls in 3G but then pushing back to LTE
MA c
WCD • Optimized end user experience by seamless RAT change from
loaded 3G network
For internal use


With and without RAN2264 Smart LTE Handover
RAN2264 RAN2264
Not activated Activated
• No possibility to move active UEs directly to LTE EMM_CONNECTED state • In UTRAN Cell_DCH state the UE performs Compressed Mode (or non-
• UEs are redirected to LTE via RRC Connection Release message containing compressed mode) measurements of LTE Layers and performs a handover
E-UTRA Target Info IE • No need to go to RRC_IDLE state
• UE connection is terminated and UE redirected to LTE in idle mode w/out • End user experience is optimized – seamless handover – resources are
guaranty that target LTE can serve UE reserved in advance on LTE side
There is no possibility to handover active UEs from WCDMA to LTE Seamless handover based on several triggers
Cell_DCH EMM_CONNECTED
Cell_DCH EMM_CONNECTED
RRC_IDLE RRC_IDLE
For internal use

Technical Details Table of Contents

Triggers for Smart LTE Handover
Using WCEL- LTEHandoverEnabled parameter, it can be set which triggers will be used for handover
Values of the parameter and respective trigger combinations are presented in following table:
Value “0” “1” “2” “3” “4” “5” “6” “7” “8”
Trigger All
T1 T1 T2 T1 T1 T2 T1 T1 T2 T1 T1 T2
Combinations triggers
disabled T3 T3 T4 T4 T3 T4 T3 T4
where:
Trigger 1 : T1 RRC State Change Cell_DCH to CCH
Trigger 2 : T2 HSDPA/HSPA to DCH/DCH CTS
Trigger 3 : T3 CS RAB Release with PS service ongoing
Trigger 4 : T4 Periodic trigger
• The feature and the trigger(s) are enabled if the WCEL-LTEHandoverEnabled parameter is enabled in the main cell (cell with best RSCP level)
• If LTE handover is not possible during the measurement or at the point when the LTE measurement is stopped, the possibility for the LTE redirection
(RAN2717 Smart LTE Layering or RAN2980 Mesurement based LTE Layering mechanisms) is not checked
For internal use

Interdependencies Table of Contents

Interdependencies with other features or functions
RAN2067 license must be installed

Interworking mechanism implemented
RAN2067 and feature must be activated RAN2136
LTE Interworking Fast Dormancy
No license needed for RAN2717 but Smart LTE Handover works

RAN2717 features share triggers irrespective of the RAN1276 RAN1276
HSDPA Inter-
Smart LTE Layering Frequency Handover
No license needed for RAN2980 but Feature allows seamless RAT

RAN2980 features share triggers RAN2264 change form LTE to WCDMA RAN2176
Measurement based
LTE Layering Smart LTE Handover LTE PS Handover
LTE measurements are prioritised

against WCDMA inter-frequency Feature allows seamless VoIP -> CS
RAN2172 measurements Handovers and CS FBs to WCDMA RAN2435
Multi-Band Load SRVCC from LTE
Balancing and CSFB with HO
RAN2451 Support for E-DCH

Interworking mechanism implemented Compressed Mode
RAN1668
Fast Dormancy HSUPA CM for LTE and
Profiling Inter-Frequency
Handover
Mandatory Interworking Optional Recommended Basic

For internal use

 RAN2067 LTE Interworking

 Cell reselection to LTE mechanism is a pre-requisite for Smart LTE Handover
 ADJL and HOPL objects (and respective parameters) introduced by the RAN2067 LTE Interworking feature, are needed for handover
 Activation of RAN2067 LTE Interworking is not required in the cell but the licence is enough in order to modify ADJL and HOPL parameters
 RAN2717 Smart LTE Layering / RAN2980 Measurement Based LTE Layering
 RAN2264 Smart LTE Handover feature is independent from the RAN2717 Smart LTE Layering and RAN2980 Measurement Based LTE Layering
 RAN2717 Smart LTE Layering or RAN2980 Measurement Based LTE Layering feature is not included in RAN2264 Smart LTE Handover feature ,
meaning it is not possible to redirect UE to LTE using RAN2264 Smart LTE Handover only
 However, features can work simultaneously
 LTE handover is prioritised to LTE redirection if an event triggers both redirection and handover, details are described here
 RAN2172 Multi-Band Load Balancing
 RAN2172 Multi-Band Load Balancing feature applies Cell_DCH state inactivity (Cell_DCH to CCH state transition) as a trigger to start WCDMA
inter-frequency measurements; also the Smart LTE Handover applies the same trigger to start LTE measurements
 If the Cell_DCH to CCH state transition triggers both LTE and WCDMA inter-frequency measurements at the same time, LTE measurements are
prioritised if other conditions for LTE handover are fulfilled
 After the decision to perform LTE measurements is done and results do not lead to LTE handover, WCDMA measurements due to the same
inactivity trigger are not started - UE is transferred to CCH state according to the legacy principles
 This behaviour is followed by other non-critical WCDMA inter-frequency measurements applying Cell_DCH to CCH state transition as trigger
(HSPA capability based handover).
For internal use


 LTE handover is prioritized over LTE redirection - if both LTE handover (WCEL-LTEHandoverEnabled) and LTE redirection, either w/
or w/o measurements, (WCEL-SmartLTELayeringEnabled) are simultaneously enabled
 Exceptions:
1. UE does not support LTE Inter-system HO
2. Streaming PS RAB is established (otherwise RAN2980 Measurement based LTE Layering can trigger LTE measurements in this case)
3. Handover is prohibited by the timer RNC/MCL-LTEMinMeasInterval (otherwise redirection w/o measurements is prioritized)
4. Handover is prohibited by the timer defined by the RNC/FMCL-LTEMinHoInterval parameter (otherwise redirection is prioritized)
1. 2. 3. 4.
Trigger Trigger Trigger
PS Streaming
Measurement
Minimum interval between a successful inter-RAT Measurement report
procedure is not started
handover from LTE to WCDMA and the following received
again within certain
inter-RAT handover attempt back to LTE
time period
No support for Time
LTE Inter-
RNC configures Measurement report RNC configures
system HO received
compressed mode compressed mode
Results not good enough
For internal use


 RAN2136 Fast Dormancy

 If UE sends RRC: SIGNALLING CONNECTION RELEASE INDICATION
message with cause value “UE Request PS Data Session End” while LTE
UE NodeB RNC
measurements are ongoing, measurement are continued
 If results does not lead to handover, UE is transferred to Cell_PCH/URA RRC: SIGNALING CONNECTION RELEASE
PCH state
UE Request PS Data Session End RAN2136
 The state transition trigger becomes effective if UE sends RRC: SIGNALLING
CONNECTION RELEASE INDICATION message with cause value “UE Request
RRC: SIGNALING CONNECTION RELEASE
PS Data Session End” while LTE measurements are not ongoing
 Thus, state change away from Cell_DCH is delayed; LTE measurement - RAN2451
are started and UE is handed over to LTE if results are good enough
 If results does not lead to handover, UE is transferred to Cell_PCH/URA
PCH state
 RAN2451 Fast Dormancy Profiling UTRAN Connected Mode
 If UE sends RRC: SIGNALLING CONNECTION RELEASE INDICATION Cell_DCH Cell_FACH
message without cause value, UE is transferred to Idle state despite of the
fact that LTE measurements are ongoing
 If the trigger in question is parametrisized not to use LTE handover and Cell_PCH URA_PCH
RAN2980 or RAN2717 uses this trigger to redirect UEs blindly to LTE, UE is
redirected to LTE in blind manner
Idle mode
For internal use


RAN1668 HSUPA CM for LTE and Inter-Frequency Handover
 RAN1668 HSUPA Compressed Mode for IF and LTE HO
 Smart LTE Handover is supported with any transport channel combination (SRB and RB mapping): DCH_UL compressed mode
 Radio Bearer (RB): EDCH_UL normal mode
 DCH/DCH UL throughput UL-SCH in LTE
 HS-DSCH/DCH
 HS-DSCH/E-DCH 90% or more uplink
HS-DSCH/
 Signalling Radio Bearer (SRB): throughput reduction
E-DCH
 DCH/DCH HS-DSCH /
1
 DCH/E-DCH DCH (RAN2264)
2 3
 HS-DSCH/E-DCH (F-DPCH) DL-SCH/UL-SCH
RAN2264 Smart LTE Handover 1 UE with HSPA service

license is enough
2 HO trigger appears; EDCH reconfigured to DCH to
start CM measurements of LTE carriers
3 UE with DCH UL executes LTE ISHO
HSUPA CM feature activation is required for UE with HSPA connection to start LTE measurements
 The necessary Compressed Mode (CM) transmission gap pattern parameters are implemented, allowing HSPA to LTE measurement based mobility
 Few times higher end user uplink throughput in handover areas (HSUPA sustained during the IS measurements)
 Optional UTRAN feature (separate license required)
For internal use

Deployment aspects Table of Contents

Activation
 Preconditions
 License for interdependent, mandatory feature RAN2067 LTE Interworking need to be
activated
 License Key: Cell Reselection to LTE License Name: Cell Reselection to LTE
 Feature Code: 1755 License
Long-term ON/OFF
 License Type: Long-term ON/OFF licence Type:
 License for RAN2264 Smart LTE Handove needs to be activated as well It is possible to create and modify ADJL and
HOPL objects (and respective parameters),
 License Key: Smart LTE Handover Description:
introduced by the RAN2067 LTE Interworking
 Feature Code: 3414 if the license exist and the state is ON.
 License Type: Long-term ON/OFF licence

 Licenses can be activated using MML commands:
 ZW7M: FEA=1755:ON; for Cell Reselection to LTE LK
 ZW7M: FEA=3414:ON; for Smart LTE Handover LK
 It is not possible to activate the RAN2264 Smart LTE Handover feature in a cell if the License Name: Smart LTE Handover
following parameters are not configured and attached to the WCDMA cell in question:
License
Long-term ON/OFF
 FMCL (Inter-RAT (LTE) measurement control parameter set) Type:
 LTEMinHoInterval (optional, default value exists) It is possible to enable the RAN2264 Smart
 LTEMeasAveWindow (optional, default value exists) LTE Handover on cell basis with the WCEL-
Description:
LTEHandoverEnabled parameter when the
 LTEMaxMeasPeriod (optional, default value exists) license exists and the state is ON.
 LTEMinMeasInterval (optional, default value exists)
 LTENcarrFreqSearchPeriod (optional, default value exists)
For internal use


Activation
 Preconditions (cont.)
 It is not possible to activate the RAN2264 Smart LTE Handover feature in a cell if the following parameters are not configured and attached
to the WCDMA cell in question:
 HOPL (Inter-RAT (LTE) neighbor frequency parameter set) RNC
LTEPeriodicTriggerTimer
 AdjLFreqPriority (optional, default value exists)
 AdjLMinRSRPLevel (optional, default value exists)
 AdjLMinRSRQLevel (optional, default value exists) WBTS
 ADJL (Inter-RAT (LTE) neighbor frequency definitions)

 AdjLEARFCN (mandatory) WCEL
 AdjLMeasBw (optional, default value exists) FMCL (up to 100)
LTEHandoverEnabled
ADJL (up to 8)
FMCLIdentifier
AdjLId
 ADJE (Inter-RAT (LTE) neighbor cell definitions) FMCLId
LTEMinHoInterval
LTELayerCellHSLoad
HopLIdentifier
SmartLTELayeringUA
 AdjePhysicalCellId (mandatory) LTEMeasAveWindow SmartLTELayeringTSysSel AdjLEARFCN
AdjLMeasBw
LTEMaxMeasPeriod
 AdjeMCC (mandatory) LTEMinMeasInterval
LTENcarrFreqSearchPeriod
 AdjeMNC (mandatory)
ADJE (up to 64)
 AdjeMNCLength (optional, default value exists for AdjEId
the 2 digit MNC) HOPL (up to 10) AdjLIdentifier
HopLId AdjePhysicalCellId
 AdjeENodeBId (mandatory) AdjLFreqPriority AdjeMCC
AdjLMinRSRPLevel AdjeMNC
 AdjeCellId (mandatory) AdjLMinRSRQLevel AdjeMNCLength
AdjeENodeBId
 AdjeTAC (mandatory) AdjeCellId
AdjeTAC
 AdjLIdentifier (mandatory)
RNMOBI (1)
SmartLTELayeringServ
For internal use


Activation
 Preconditions (cont.)
 Additionally, the following parameters can be used for tuning the Smart LTE Handover:
 RNC (RNC related parameters)
 LTEPeriodicTriggerTimer (optional, default value exists)
 RNMOBI (Mobility related parameters) RNC
LTEPeriodicTriggerTimer
 SmartLTELayeringServ (optional, default value exists)
 WCEL (WCDMA Cell related parameters)
WBTS
 LTELayerCellHSLoad (optional, default value exists)
 SmartLTELayeringUA (optional, default value exists)
 SmartLTELayeringTSysSel (optional, default value exists) WCEL
LTEHandoverEnabled
FMCL (up to 100) ADJL (up to 8)
 User must ensure the correctness of LTE neighbor and identifier FMCLId
FMCLIdentifier
LTELayerCellHSLoad AdjLId
parameters: LTEMinHoInterval SmartLTELayeringUA HopLIdentifier
LTEMeasAveWindow SmartLTELayeringTSysSel AdjLEARFCN
 ADJL-AdjLEARFCN  ADJE-AdjeMNCLength LTEMaxMeasPeriod AdjLMeasBw
LTEMinMeasInterval
 ADJL-AdjLMeasBw  ADJE-AdjeENodeBId LTENcarrFreqSearchPeriod
 ADJE-AdjePhysicalCellId  ADJE-AdjeCellId ADJE (up to 64)

 ADJE-AdjeMCC  ADJE-AdjeTAC AdjEId
HOPL (up to 10) AdjLIdentifier
 ADJE-AdjeMNC  ADJE-AdjLIdentifier HopLId AdjePhysicalCellId
AdjLFreqPriority AdjeMCC
RNC O&M is not able to verify the values of these parameters AdjLMinRSRPLevel AdjeMNC
AdjLMinRSRQLevel AdjeMNCLength
AdjeENodeBId
 Activation AdjeCellId
AdjeTAC
 Enable the RAN2264 Smart LTE Handover on cell basis with the
RNMOBI (1)
WCEL-LTEHandoverEnabled parameter SmartLTELayeringServ
For internal use


Trial Area
 Recommended trial area:

WCDMA-LTE
 In order to check whether RAN2264 Smart LTE Handover works coverage overlapped
appropriately, trial area should be selected, so that the WCDMA network
coverage and LTE network coverage is present
 at lest one EARFCN should be available
 In order to follow UE behaviour and Handover Decision algorithm (for
example: target cell selection based on frequency prioritization) with
multiple EARFCNs, more than one LTE carrier should be available
(configuration of neighbors should reflect that fact)
 Feature can be tested in the following environments: WCDMA coverage
 WCDMA – LTE coverage is fully overlapped LTE coverage

 In this case, user can be quickly moved back to LTE using for
example the Periodic Trigger
 WCDMA – LTE coverage is not fully overlapped (LTE coverage holes)
 Consider unnecessary frequent CM measurements if Periodic
Trigger is used and coverage holes are significant
 Additionally, it is beneficial to trial this feature together with RAN2980
Measurement based LTE Layering and RAN2172 Multi-band Load
WCDMA-LTE coverage
Balancing as theese features are interdependant non- overlapped
 Features use similar triggers
 Features share parameters
 Features can be used as complementary mechanisms
For internal use

Configuration Management Table of Contents

Parameterization Scenarios
Two parameterization scenarios are examined within this chapter
 Back to LTE as soon as possible  Back to LTE only if WCDMA is not good enough
LTE to WCDMA WCDMA to LTE LTE to WCDMA WCDMA to LTE LTE to WCDMA WCDMA to LTE
handover due to handover due to handover due to handover due to handover due to handover due to
coverage reasons Periodic Trigger coverage reasons Periodic Trigger coverage reasons CTS
WCDMA RSCP [dBm]

WCDMA RSCP [dBm]
LTE RSRP [dBm]

LTE RSRP [dBm]
-140 + threshold2Wcdma -140 + threshold2Wcdma

(LTE configuration) (LTE configuration)
Time [s] LTE RSRP WCDMA RSCP Time [s]

LTE RSRP WCDMA RSCP
For internal use


Parameterization Scenarios: Back to LTE as soon as possible
 This scenario best suits areas where WCDMA layer is well underlayed with LTE layer;  WCEL-LTELayerCellHSLoad = 0 (cell load is not checked)
small LTE coverage holes only
 WCEL-SmartLTELayeringUA = 0 (user amount not checked)
 Frequent periodic check of LTE layer availability and short interval between both
 RNC-LTEPeriodicTriggerTimer = 10 seconds
consecutive CM measurements and incoming-outgoing HOs ensures fast move to LTE
 WCEL-LTEHandoverEnabled = 8 (enabled for all triggers)
 WCDMA load criteria (delaying LTE HO) are not used
 FMCL- LTEMinHoInterval = 10 seconds
 CM measurements can be triggered by T1, T2, T3 or T4 events
 FMCL-LTEMinMeasInterval = 4 seconds
 Note that this scenario may cause rise of signaling traffic
 Please consider inter-RAT HO threshold values in both RANs
(LTE and WCDMA) to avoid unnecessary ping-pong effect
LTE to WCDMA WCDMA to LTE LTE to WCDMA WCDMA to LTE
handover due to handover due to handover due to handover due to
coverage reasons Periodic Trigger coverage reasons Periodic Trigger
WCDMA-LTE
coverage overlapped
WCDMA RSCP [dBm]

LTE RSRP [dBm]
-140 + threshold2Wcdma
(LTE configuration)
WCDMA coverage
LTE coverage
LTE RSRP WCDMA RSCP Time [s]

For internal use

Parameterization Scenarios: Back to LTE only if WCDMA is not good enough
 This scenario assumes WCDMA-LTE co-siting; additionally WCDMA-LTE coverage is  WCEL-LTELayerCellHSLoad = 31 dBm (default value)
not fully overlapped
 WCEL-SmartLTELayeringUA = 0 (user amount not checked)
 Periodic check is not used at all as UE can stay in WCDMA unless it is served with
 RNC-LTEPeriodicTriggerTimer = N/A since trigger is disabled
good quality; thus WCDMA load criteria (delaying LTE HO) are used – proposed
values should be further tuned in the field  WCEL-LTEHandoverEnabled = 4 (enabled for T1, T2 and T3)
 Note that this scenario limits CM measurement attemps and consequently signaling  FMCL- LTEMinHoInterval = 10 seconds
load  FMCL-LTEMinMeasInterval = 5 seconds
 Please consider inter-RAT HO threshold values in both RANs
(LTE and WCDMA) to avoid unnecessary ping-pong effect
LTE to WCDMA WCDMA to LTE
handover due to handover due to
coverage reasons CTS
WCDMA RSCP [dBm]

LTE RSRP [dBm]
(LTE configuration)
WCDMA coverage
LTE coverage

For internal use
Performance Aspects Table of Contents

Counters for detailed troubleshooting
 Monitoring WCDMA -> LTE Handover on a pair of cells basis:

 Detailed troubleshooting and optimization can be done with the use of these counters:
 M1019C0 LTE ISHO ATTEMPTS - the number of outgoing inter-system hard
handover attempts to LTE. If cells Cell 1, Cell 2 and Cell 3 are in the active set
and inter-system handover to LTE Cell 4 is attempted, this counter is updated
by 1 for each pair of source/target cells:
 Cell 1 – Cell 4 Cell 3
WCDMA coverage is
 Cell 2 – Cell 4 underlayed by LTE
coverage – not shown
 Cell 3 – Cell 4 for simplicity
Cell 1
 M1019C1 LTE ISHO SUCCESSFUL - the number of completed outgoing inter- Cell 2
system hard handovers to LTE. If cells Cell 1, Cell 2 and Cell 3 are in the active Active set
set and inter-system handover to LTE Cell 4 is attempted, this counter is
updated by 1 for each pair of source/target cells: Serving cell
 Cell 1 – Cell 4
 Cell 2 – Cell 4
 Cell 3 – Cell 4 LTE Target Cell
Cell 4
RNC Core Network RNC Core Network
RANAP: RELOCATION REQUIRED RANAP: IU RELEASE COMMAND

M1019C0 +1 M1019C1 +1
For internal use


Counters for relecation preparation related events
 M1036 LTE Relocation measurement type can be used to monitor WCDMA -> LTE
relocation preparation related events:
 Number of LTE PS HO preparation requests (M1036C0)
RNC Core Network
 Number of succesful LTE PS HO preparations (M1036C1)
 Number of LTE PS HO preparation failures (M1036C2-7) RANAP: RELOCATION REQUIRED
M1036C0 +1
 radio network layer cause
 transport layer cause M1036C2-7 +1
RANAP: RELOCATION COMMAND
 non-access stratum cause,

 protocol cause M1036C2-7 +1
RANAP: RELOCATION PREPARATION FAILURE
 miscellaneous cause radio network layer cause

transport layer cause
 non-standard cause non-access stratum cause
protocol cause
 Number of LTE PS HO preparation cancellations miscellaneous cause
 total number of cancellations (M1036C8) non-standard cause
 relocation cancel due to Trelocoverall timer expiration (M1036C9)

M1036C9 +1 RANAP: RELOCATION CANCEL
 relocation cancel due to Trelocprep timer expiration (M1036C10) M1036C8 +1
TrelocOverall expiry
M1036C10 +1 RANAP: RELOCATION CANCEL

M1036C8 +1
TrelocPrep expiry
For internal use


Counters for relecation preparation related events
 M1010 counters can be used for regular success rate monitoring of the outgoing LTE Active set
PS HO (per 3G source cell)
 Total duration of LTE frequency band measurements in SRNC (M1010C239)
 Number of measurements with CM caused by the specific trigger (M1010C240-243)
 Number of measurements without CM caused by the specific trigger (M1010C244-247)
 Number of measurements not allowing LTE HO per specific trigger (M1010C248-251)
 Number of LTE PS HO preparation requests per specific trigger (M1010C252-255)
 Number of completed outgoing LTE PS HOs per specific trigger (M1010C256-259) LTE Target Cell
 Number of events where UE sends RRC: HANDOVER FROM UTRAN FAILURE after
being commanded to LTE per specific trigger (M1010C260-263)
 UE fails to establish the physical channel(s) indicated in the handover command.
UE reverts to the old configuration (before receiving RRC: HANDOVER FROM
UTRAN COMMAND ) and transmits a failure message to the source RNC. The
hard handover procedure ends and the UE resumes the normal operation as if
UE Source RNC
no hard handover attempt had occurred.
 Number of connection drops during LTE PS HO per specific trigger (M1010C264-267
 When the UE does not respond to RRC: HANDOVER FROM UTRAN FAILURE RRC: Handover from UTRAN Command
and timer expires in the RNC, or the UE responds with RRC: CELL UPDATE and
therefore the call is dropped out of Cell_DCH state. FAILURE during establishing the physical
channel(s) indicated in handover command
 Number of PS LTE HO preparation failures for NRT calls (M1010C268)
RRC: Handover from UTRAN Failure
For internal use

Thank You.
22 ©2014 Nokia Solutions and Networks. All rights reserved.

Back-up
23 ©2014 Nokia Solutions and Networks. All rights reserved.


List of available counters
 M1010C239 DURATION OF LTE CARRIER MEASUREMENT  M1010C260 LTE NRT ISHO UE NACK DUE TO DCH TO CCH
 M1010C240 LTE NRT ISHO MEAS WITH CM DUE TO DCH TO CCH  M1010C261 LTE NRT ISHO UE NACK DUE TO HSPA TO DCH
 M1010C241 LTE NRT ISHO MEAS WITH CM DUE TO HSPA TO DCH  M1010C262 LTE NRT ISHO UE NACK DUE TO CS RAB RELEASE
 M1010C242 LTE NRT ISHO MEAS WITH CM DUE TO CS RAB RELEASE  M1010C263 LTE NRT ISHO UE NACK DUE TO PERIODIC TRIGGER
 M1010C243 LTE NRT ISHO MEAS WITH CM DUE TO PERIODIC TRIGGER  M1010C264 LTE NRT ISHO UE LOST DUE TO DCH TO CCH
 M1010C244 LTE NRT ISHO MEAS WITHOUT CM DUE TO DCH TO CCH  M1010C265 LTE NRT ISHO UE LOST DUE TO HSPA TO DCH
 M1010C245 LTE NRT ISHO MEAS WITHOUT CM DUE TO HSPA TO DCH  M1010C266 LTE NRT ISHO UE LOST DUE TO CS RAB RELEASE
 M1010C246 LTE NRT ISHO MEAS WITHOUT CM DUE TO CS RAB RELEASE  M1010C267 LTE NRT ISHO UE LOST DUE TO PERIODIC TRIGGER
 M1010C247 LTE NRT ISHO MEAS WITHOUT CM DUE TO PERIODIC TRIGGER  M1010C268 LTE NRT ISHO PREPARATION FAIL
 M1010C248 LTE NRT ISHO NO CELL FOUND DUE TO DCH TO CCH  M1019C0 LTE ISHO ATTEMPTS
 M1010C249 LTE NRT ISHO NO CELL FOUND DUE TO HSPA TO DCH  M1019C1 LTE ISHO SUCCESSFUL
 M1010C250 LTE NRT ISHO NO CELL FOUND DUE TO CS RAB RELEASE  M1036C0 LTE PS ISHO OUT PREP REQ
 M1010C251 LTE NRT ISHO NO CELL FOUND DUE TO PERIODIC TRIGGER  M1036C1 LTE PS ISHO OUT PREP SUCC
 M1010C252 LTE NRT ISHO ATTEMPTS DUE TO DCH TO CCH  M1036C2 LTE PS ISHO OUT PREP FAIL DUE TO RN LAYER CAUSE
 M1010C253 LTE NRT ISHO ATTEMPTS DUE TO HSPA TO DCH  M1036C3 LTE PS ISHO OUT PREP FAIL DUE TO TR LAYER CAUSE
 M1010C254 LTE NRT ISHO ATTEMPTS DUE TO CS RAB RELEASE  M1036C4 LTE PS ISHO OUT PREP FAIL DUE TO NAS CAUSE
 M1010C255 LTE NRT ISHO ATTEMPTS DUE TO PERIODIC TRIGGER  M1036C5 LTE PS ISHO OUT PREP FAIL DUE TO PROT CAUSE
 M1010C256 LTE NRT ISHO SUCCESS DUE TO DCH TO CCH  M1036C6 LTE PS ISHO OUT PREP FAIL DUE TO MISC CAUSE
 M1010C257 LTE NRT ISHO SUCCESS DUE TO HSPA TO DCH  M1036C7 LTE PS ISHO OUT PREP FAIL DUE TO NON STAN CAUSE
 M1010C258 LTE NRT ISHO SUCCESS DUE TO CS RAB RELEASE  M1036C8 LTE PS ISHO CANCEL TOTAL
 M1010C259 LTE NRT ISHO SUCCESS DUE TO PERIODIC TRIGGER  M1036C9 LTE PS ISHO FAIL DUE TO RELOC OVERALL TIMER EXPIRY
 M1036C10 LTE PS ISHO CANCEL DUE TO RELOC PREP TIMER EXPIRY
For internal use


Parameters
LTEMinHoInterval Minimum Interval Between LTE HOs

Object: RNC/FMCL The parameter determines the minimum interval between a successful inter-RAT handover from LTE
Range: 1...60 to WCDMA and the following inter-RAT handover attempt back to LTE related to the same RRC
connection.
Step: 1
Default (GUI): 10
Multiplicity: 1
Unit: sec
Category: ADVANCED
Handover from LTE Handover to LTE allowed Maximum Maximum

to WCDMA since timer expired measurement time measurement time
Trigger appears Trigger appears Trigger appears
LTE Neighbor Carrier LTE Neighbor Carrier 0,5 sec

Frquency Search Period Frquency Search Period
Measurement
Minimum interval between a successful inter-RAT Measurement report Measurement report
handover from LTE to WCDMA and the following received received
time period
Time
Sliding Averaging
RNC configures Sliding Averaging RNC configures Window
compressed mode Window compressed mode
For internal use


Parameters
LTENcarrFreqSearchPeriod LTE Neighbor Carrier Frequency Search Period

Object: RNC/FMCL This parameter determines the period of LTE measurement, during which redirection to LTE system is
Range: 0...6 not possible. This period allows UE to find and report all potential LTE neighbor carrier frequencies
before the redirection decision.
Step: 0.5
Note:
Default (GUI): 1.5
Too short period means that redirection to LTE system can be done after very short time (e.g. one
Multiplicity: 1 measurement report) which may lead to unsuccessful cell reselection.
Unit: sec Too high value of this parameter can cause too long time to hold the UEs from being redirected to LTE
Category: ADVANCED even though measurement received earlier, suggested positive decision for redirection.


Measurement
time period
Time
Sliding Averaging
For internal use


Parameters
LTEMaxMeasPeriod LTE Maximum Measurement Period

Object: RNC/FMCL This parameter defines maximum allowed period during which LTE measurements are performed. If
Range: 0.5...30 the RNC is not able to redirect the UE to LTE system during this period, then RNC asks UE to stop the
LTE measurements.
Step: 0.5
Note
Default (GUI): 6
Too short period means that only few measurement reports will be taken into account and results
Multiplicity: 1 could be not accurate.
Unit: sec If the period is too long, and RNC is not able to redirect UE to LTE, resources are wasted.
Category: ADVANCED The value of LTEMaxMeasPeriod must be higher than the value of LTENcarrFreqSearchPeriod.


Measurement
time period
Time
Sliding Averaging
For internal use


Parameters
LTEMeasAveWindow LTE Measurement Averaging Window

Object: RNC/FMCL This parameter determines the maximum period for averaging the received periodical LTE
Range: 0.5...16 measurement reports (maximum size of the sliding averaging window) from which the RNC calculates
the averaged LTE RSRP and RSRQ values for the redirection decision algorithm.
Step: 0.5
Note:
Default (GUI): 3
If the value of this parameter is too low, then averaged measurement results are not reliable.
Multiplicity: 1
If the value of this parameter is too high, then old measurements affects too heavily to the averaged
Unit: sec measurement results.
Category: ADVANCED


Measurement
time period
Time
Sliding Averaging
For internal use


Parameters
LTEMinMeasInterval LTE Minimum Measurement Interval

Object: RNC/FMCL This parameter determines the minimum interval between an unsuccessful Inter-RAT (LTE)
Range: 1...60 measurement and the following LTE measurement procedure related to the same RRC connection.
Step: 1 Note:
Default (GUI): 5 Too short period cause that measurements taken after unsuccessful ones will also be unsuccessful
because not much will change in the radio conditions.
Multiplicity: 1
Too long interval will unnecessarily block resources and introduce delays in redirection process.
Unit: sec Special value meaning: Repetitive LTE measurements are disabled.
Category: ADVANCED
Special Value: 0


Measurement
time period
Time
Sliding Averaging
For internal use


Parameters
AdjLMinRSRPLevel LTE Carrier frequency selection Minimum Rx Power level

Object: RNC/HOPL This parameter determines the minimum required RSRP power level which the measurement result of
Range: -144...-44 the cell under LTE carrier frequency must meet or exceed before the handover to LTE system
becomes possible.
Step: 2
If the value of parameter is set to too low , which represents very low received power, then UEs do not
Default (GUI): -112 end up in successful reselection of LTE cell every time.
Multiplicity: 1 If the value of parameter is set to too high, which represents high received power, then UEs do not
Unit: dBm come across such strong cell very often.
Category: ADVANCED Note:
This value must be aligned with the thresholds for WCDMA inter-system measurements and for
WCDMA inter-system handover on LTE side to avoid ping-pong behaviour.
It must be ensured that there is a reasonable margin

between the following thresholds:
• WCDMA inter-system measurements in LTE and
3dB margin
WCDMA RSCP [dBm]
• WCDMA inter-system handover to LTE in

WCDMA
LTE RSRP [dBm]

AdjLMinRSRPLevel
(WCDMA configuration)
Recommneded margin is 3dB (AdjLMinRSRPLevel
should have higher value)
RSRP_threshold_for_WCDMA_measurements
(LTE configuration)
For internal use


Parameters
AdjLMinRSRQLevel LTE Carrier frequency selection Minimum Rx qual level

Object: RNC/HOPL This parameter determines the minimum required RSRQ quality level which the measurement result of
Range: -19.5...-3 the E-UTRA carrier frequency must meet or exceed before the redirection to LTE system becomes
possible.
Step: 0.5
If the value of parameter is set to too low, which represents low received quality, then UEs do not end
Default (GUI): -12 up in successful reselection of LTE cell every time.
Multiplicity: 1 If the value of parameter is set to too high, which represents high received quality, then UEs do not
Unit: dBm come across such strong cell very often.
This value must be aligned with the threshold for WCDMA inter-system measurements on LTE side to
avoid ping-pong behaviour.
It must be ensured that there is a reasonable margin

between the following thresholds:
• WCDMA inter-system measurements in LTE and
3dB margin
WCDMA RSRP [dBm]
• WCDMA inter-system handover to LTE in

WCDMA
LTE RSRQ [dBm]

AdjLMinRSRQLevel
(WCDMA configuration)
Recommneded margin is 3dB (AdjLMinRSRQLevel
should have higher value)
RSRQ_threshold_for_WCDMA_measurements
(LTE configuration)
For internal use


Parameters
LTEPeriodicTriggerTimer LTE Periodic Trigger timer

Object: RNC This parameter defines the time during which UE remains in CELL_DCH for PS service(s), and at the expiry of
the timer measurement are started for LTE Handover. When LTE capable UE having PS RAB(s) enters in
Range: 10...100 CELL_DCH, and starts data activity, this timer is set. If the data activity continues and timer expires, then
Step: 1 measurements are initiated, and timer is set again. If the measurements are successful, then UE is handed
Default (GUI): 20 over to LTE system. If the measurements are unsuccessful, and UE's data activity continues, then at the expiry
of timer (periodic timer), measurements are started again. The triggers T1-T3 (as mentioned in WCEL-
Multiplicity: 1 SmartLTEHandoverEnabled) can happen any time.
Unit: sec
If the value of this parameter is set to too short, many LTE capable UEs after remaining for short time in
CELL_DCH, move to LTE system, even if they were experiencing good end-user experience.
Periodical LTE layer search
 Expiry of new supervisory timer set for PS RAB connections triggers LTE measurements followed by handover decision
You can measure LTE
 When LTE capable UE’s enter into CELL_DCH state, timer starts. After expiration, measurements are done. layers when timer expires
 UE do not need to wait neither for HSPA ->DCH Channel Type Switch nor Cell_DCH to CCH State Change in order to be handed over
to LTE layer
3
LTE c 1 One of 4 triggering event appeared
o verag
e 2 2 LTE measurments started Mr (10-100sec)
WCD Periodical Timer
MA c 3 LTE handover decision
overa
ge CELL_DCH 1
For internal use


Parameters
LTELayerCellHSLoad LTE Layer Cell HSDPA Load

Object: RNC/WBTS/WCEL This parameter defines threshold for WCDMA Cell HSDPA load in Measurement Based LTE Layering
Range: 1…50 or Smart LTE Handover.
Step: 1 If it is set to special value '0', then WCDMA cell load is not checked.
Default (GUI): 31 If this parameter is set to value other than 0, and the cell load determined through available HSDPA
power per NRT user, is equal or higher than value (no high load) of this parameter, then CM
Multiplicity: 1 measurements of LTE Layers are forbidden.
Unit: dBm If the available HSDPA power per NRT user is less than value (high load) of this parameter then
Category: ADVANCED measurements of LTE layers are possible.
Note:
If the value of parameter is set to too low value, then users may experience low throughputs in
WCDMA and still cannot be handed over to LTE.
If the value of parameter is set to too high value, user are handed over to LTE even if experienced
throughput is acceptable.
WCEL- LTELayerCellHSLoad
 The configured HSDPA power per user threshold must be exceeded before
measurements are initiated
HSDPA Power per User
Measurements not allowed  For this feature, CellWeightForHSDPALayering always equals 1

=1
WCDMA
Measurements allowed PNRTHSDPA  CellWeight ForHSDPALa yering
max( NumberOfNRTHSDPAuser s,1)
Time
For internal use

Parameters
SmartLTELayeringUA Smart LTE Layering NRT user amount threshold

Object: RNC/WBTS/WCEL The parameter defines a user amount threshold that must be exceeded before measurements of LTE
Range: 5…255 layers are possible. User amount is checked in cell level and just NRT users (Interactive and
Background) are counted. An user is counted in those cells where the user in question has DCH, HS-
Step: 1 DSCH or E-DCH.
Default (GUI): 0 If the NRT user amount check allows the LTE layer measurements, then they are not prevented again
Multiplicity: 1 right after NRT user amount becomes smaller than the parameter value, but there is a fixed hysteresis
Category: ADVANCED of 5 users. When the user amount fals below the [parameter value – 5], measurements are allowed.
Special Value: 0 Checking of user amount can be deactivated by setting the spacial value 0.
Note:
Real default value for this threshold cannot be defined, because it depends on radio network planning.
WCEL-SmartLTELayeringUE
 The configured NRT user amount threshold must be exceeded before measurements are initiated
Number of NRT users

 NRT user amount threshold of the SRNC main cell is checked Redirection/Measurements allowed
 Users utilizing Interactive or Background RABs are counted as NRT users
 The user amount criterion is ignored if the special value „0” is set
Redirection/Measurements not allowed
Time
For internal use


Parameters
SmartLTELayeringTSysSel Smart LTE Layering Target System Selection

Object: RNC/WBTS/WCEL The parameter indicates if the redirection is allowed to FDD LTE, TDD LTE or to both of them. If
redirection to FDD or TDD is prevented, then neighbor frequencies in question are not given to UE at
Range: ｛ 0,1,2 ｝ all.
Step: 1
Multiplicity: 1
Category: ADVANCED
Values:
0 - redirection allowed to all neighbors
1 - redirection allowed just to FDD neighbors
2 - redirection allowed just to TDD neighbors
Value “0” “1” “2”
Target System
FDD FDD TDD
TDD
For internal use


Parameters
AdjsHCSpriority Cell Re-selection HCS Priority

Object: RNC/HOPS Defines the priority level of the neighboring cell in the hierarchical cell re-selection procedure. 0
Range: 0…7 indicates the lowest HCS priority and 7 indicates the highest HCS priority. Lower HCS priority values
are meant for larger macro cells and higher HCS priority values are meant for smaller pico/micro cells.
Step: 1
Default (GUI): 0 (lowest)
Multiplicity: 1
Category: ADVANCED
This parameter is used in RANAP: RELOCATION REQUIRED message

 When Handover decision is made, RNC sends RANAP message to Core Network with the following items:
 Relocation Type IE („UE involved in relocation of SRNS”)
 Cause IE („Network Optimization”) • RRC Container IE (contains E-UTRA capabilities of UE)
 Source ID • Target Cell ID IE (Cell Global Id = AdjeMCC + AdjeMNC + AdjeENodeBId
 Target ID + AdjeCellId)
 Source to Target Transparent Container • UE History Information IE - contains Last Visited Cell Information IE (a list
of last visited active set cells and type of that cells [macro/micro – info
taken from WCEL-HCS_PRIO for SRNC cells and HOPS-AdjsHCSpriority
for DRNC cells)
• E-RABs Info List – list of RABs to be replaced
For internal use


Parameters
HCS_PRIO HCS priority level for a cell

Object: RNC/WBTS/WCEL This parameter defines the HCS priority level for a cell. Value 0 indicates the lowest HCS priority and
Range: 0…7 value 7 indicates the highest HCS priority.
Step: 1 If HCS is not used, this parameter is not needed.
Default (GUI): 0 (lowest) The parameter is used for cell selection and re-selection in both idle and connected mode.
Multiplicity: 1
Category: ADVANCED

 When Handover decision is made, RNC sends RANAP message to Core Network with the following items:
 Cause IE („Network Optimization”) • RRC Container IE (contains E-UTRA capabilities of UE)
 Source ID • Target Cell ID IE (Cell Global Id = AdjeMCC + AdjeMNC + AdjeENodeBId
 Target ID + AdjeCellId)
 Source to Target Transparent Container • UE History Information IE - contains Last Visited Cell Information IE (a list
of last visited active set cells and type of that cells [macro/micro – info
taken from WCEL-HCS_PRIO for SRNC cells and HOPS-AdjsHCSpriority
for DRNC cells)
• E-RABs Info List – list of RABs to be replaced
For internal use


Parameters
MaxNumberUEHSPACmNCHO Max number of UEs in HSDPA CM due to NCHO

Object: RNC/WBTS/WCEL This parameter defines the maximum number of UEs that are simultaneously in an HSDPA
Range: 0…31 compressed mode in the cell due to a non-critical handover measurement reason.
Step: 1 Non-critical handovers can use only the capacity of this dedicated category. Non-critical handover
reasons are Service- and load-based handovers, HSPA capability based handovers and Multi-Band
Default (GUI): 5 Load Balancing Handovers with compressed mode. The capacity of this category can be taken by
Multiplicity: 1 critical handover reasons that are related to coverage, quality and immediate IMSI handover.
Category: ADVANCED This limit is allowed to exceed temporarily when a new soft handover branch added to this cell belongs
to the RRC connection that is in a compressed mode.
 This parameter is checked to deceide whether CM measurements for LTE layers are not prohibited:
 Measurements are prohibited if number of UEs that are simultaneously in HSDPA or HSPA compressed mode in the cell due to non-critical
handover reason is equal or exceeds the value of WCEL-MaxNumberUEHSPACmNCHO
For internal use


Parameters
MaxNumberUECmSLHO Max number of UEs in HSDPA CM due to SLHO

Object: RNC/WBTS/WCEL The parameter defines the maximum number of UEs that are simultaneously in a DCH compressed
Range: 0…32 mode in the cell due to a service- or load-based handover, HSPA capability based handover, Multi-
Band Load Balancing Handovers and LTE redirection / handover with compressed mode
Step: 1 measurement reason.
Default (GUI): 6 Service- and load-based handovers, the HSPA capability based handover, Multi-Band Load Balancing
Multiplicity: 1 Handovers and LTE redirection / handover with compressed mode can use only the capacity of this
Category: ADVANCED dedicated category. The capacity of this category can be taken by critical handover reasons that are
coverage, quality, fast moving UE in HCS, and immediate IMSI-based reasons.
This limit is allowed to exceed temporarily when a new soft handover branch added to this cell belongs
to the RRC connection that is in a compressed mode.
 This parameter is checked to deceide whether CM measurements for LTE layers are not prohibited:
 Measurements are prohibited if number of UEs that are simultaneously in HSDPA or HSPA compressed mode in the cell due to non-critical
handover reason is equal or exceeds the value of WCEL- MaxNumberUECmSLHO
For internal use


Parameters
LTEHandoverEnabled Name
Object: RNC/WBTS/WCEL The parameter enables the Smart LTE Handover (WCDMA to LTE handover) in the cell.
Range: 0...8 •T1: RRC state change Cell_DCH to CCH means the case where UE is transferred to CCH state.
Step: 1 •T2: HSDPA/HSPA to DCH/DCH CTS means the case where HS-DSCH is tried to be switched to
Category: BASIC DCH/DCH with higher bit rate than 0 kbps.
Values: •T3: CS RAB release trigger means the case where an UE has CS RAB and at least one active PS
RAB and then CS RAB is released.
0 (disabled), 1 (enabled for T1), 2 (enabled for
T1 and T2), 3 (enabled for T1 and T3), 4 •T4: Periodic Trigger means the case where the UE remains longer than the time specified by the
(enabled for T1, T2 and T3), 5 (enabled for T1 parameter RNC-LTEPeriodicTriggerTimer in the Cell_DCH state.
and T4), 6 (enabled for T1, T2 and T4), 7
(enabled for T1, T3 and T4), 8 (enabled for all
triggers)
Value “0” “1” “2” “3” “4” “5” “6” “7” “8”
Trigger All
T1 T1 T2 T1 T1 T2 T1 T1 T2 T1 T1 T2
Combinations triggers
disabled T3 T3 T4 T4 T3 T4 T3 T4
where:
Trigger 1 T1
: RRC State Change Cell_DCH to CCH Trigger 2 T2
: HSDPA/HSPA to DCH/DCH CTS Trigger 3 :T3 CS RAB Release with PS service ongoing Trigger 4 :T4 Periodic trigger
For internal use


Parameters
AdjLFreqPriority Adjacent LTE Frequency Priority

Object: RNC/HOPL This parameter defines the priority (0 lowest priority, and 7 highest priority) to LTE carrier frequencies.
Range: 0…7 The priority is used to define order of frequencies given to UE when LTE measurements are started .
This parametr is also used by Handover Control to choose the Target Cell for Handover.
Step: 1
Default (GUI): 0 (lowest)
Multiplicity: 1
Category: BASIC
Handover Control Actions

 The target cell is chosen from a group of the configured LTE neighbor cells - either under SRNC or DRNC
Step 1 Reported Cell
 Reported RSRP must be equal or higher than the threshold defined by the HOPL-AdjLMinRSRPLevel parameter Reported Cell 2
(main cell threshold is used) 1
 Reported RSRQ must be equal or higher than the threshold defined by the HOPL-AdjLMinRSRQLevel parameter
(main cell threshold is used)
3
 Cells with the highest priority EARFCN defined by HOPL-AdjLFreqPriority parameter is chosen (DRNC cells’ priority is
set to the lowest possible value [0])
 If there is more than one EARFCN with an equal priority, the EARFCN with the highest RSRQ cell is prioritised
Step 3
 The cell having the highest RSRQ ischosen the target cel for inter-RAT LTE handover.
For internal use Target LTE Cell


Parameters
AdjeMCC Mobile Country Code

Object: WCEL/ADJE E-UTRA (LTE) neighbor cells are identified with the Target eNB Identifier, which is composed of the
Range: 0…999 PLMN Identity, eNB-ID and Selected TAI. Furthermore, the PLMN Identity is composed of the Mobile
Country Code (MCC) and the Mobile Network Code (MNC).
Step: 1
The valid value between 0... 999 must be given to the parameter when creating ADJE-object for the
Multiplicity: 1 cell.
Category: BASIC
Target eNB ID
 When Handover decision is made, RNC sends RANAP message to Core PLMN Identity + eNB ID
Network with the following items:
 Relocation Type IE („UE involved in relocation of SRNS”) MCC + MNC
 Cause IE („Network Optimization”)
 Source ID AdjeMCC AdjeMNC Macro eNB ID + TAI
 Target ID
 Source to Target Transparent Container
AdjeENodeBId TAC + PLM Identity
• … AdjeTAC MCC + MNC

• Target Cell ID IE (Cell Global Id = AdjeMCC + AdjeMNC + AdjeENodeBId + AdjeCellId)
• … AdjeMCC AdjeMNC
For internal use


Parameters
AdjeMNC Mobile Network Code

Object: WCEL/ADJE E-UTRA (LTE) neighbor cells are identified with the Target eNB Identifier, which is composed of the
Range: 0…999 PLMN Identity, eNB-ID and Selected TAI. Furthermore, the PLMN Identity is composed of the Mobile
Country Code (MCC) and the Mobile Network Code (MNC).
Step: 1
The valid value between 0... 99 (AdjeMNCLength is 2) or 0... 999 (AdjeMNCLength is 3) must be
Multiplicity: 1 given to the parameter when creating ADJE-object for the cell.
Category: BASIC
Target eNB ID
 Target ID

For internal use


Parameters
AdjeMNCLength Mobile Network Code Length

Object: WCEL/ADJE The parameter defines whether 2 or 3 digits are used in Mobile Network Code.
Range: 2 digits (2), User must modify also the value of MNC (AdjeMNC) accordingly if the value of the AdjeMNCLength is
3 digits (3) modified.
Multiplicity: 1
Category: BASIC
Target eNB ID
MNC is used in RANAP: RELOCATION REQUIRED message
 Target ID

For internal use


Parameters
AdjeENodeBId Macro eNB ID

Object: WCEL/ADJE The parameter defines the Macro eNB Identifier of the E-UTRA (LTE) neighboring cell.
Range: 0...1048575 Value is equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (TS
Step: 1 36.413) of each cell served by the eNodeB.
Multiplicity: 1 The valid value between 0..1048575 must be given to the parameter when creating ADJE-object for
the cell.
Category: BASIC
Target eNB ID
 Target ID

For internal use


Parameters
AdjeTAC Tracking Area Code

Object: WCEL/ADJE The parameter defines the Tracking Area Code (TAC) of the E-UTRA (LTE) neighboring cell. TAC is
Range: 0... 65535 used for defining the Selected TAI of the target LTE cell needed for inter-RAT (LTE) relocation.
Selected TAI = PLMN Identity + TAC.
Step: 1
Multiplicity: 1
The valid value between 0... 65535 must be given to the parameter when creating ADJE-object for the
Category: BASIC cell.
Target eNB ID
 Target ID
AdjeTAC MCC + MNC
AdjeMCC AdjeMNC
For internal use


Parameters
AdjeCellId Cell ID
Object: WCEL/ADJE The parameter defines the Cell ID of the E-UTRA (LTE) neighboring cell. Cell ID corresponds with the
Range: 0...255 Local Cell Resource Identifier in eNodeB (LNCEL->lcrId in NSN LTE system)
Step: 1 Target Cell ID is transmitted to E-UTRAN in the Source eNB to target eNB Transparent Container IE
during inter-system handover from WCDMA to LTE. Target Cell ID = E-UTRAN CGI = PLMN + Cell
Multiplicity: 1 Identity (28 bits). Cell Identity = Macro eNB ID (20 most significant bits) + Cell ID (8 least significant
Category: BASIC bits). The valid value between 0... 255 must be given to the parameter when creating ADJE-object for
the cell.

 When Handover decision is made, RNC sends RANAP message to Core
 Source ID
 Target ID
• …
• …
For internal use


Parameters
AdjePhysicalCellId Inter-RAT LTE adjacent physical cell identifier

Object: WCEL/ADJE Physical Cell Identity of an inter-RAT LTE adjacent cell within LTE frequency.
Range: 0…503 UE reports inter-RAT measurements per Physical Cell Identity within EARFCN frequency.
Step: 1
Multiplicity: 1 The valid value between 0... 503 must be given to the parameter when creating ADJE-object for the
Category: BASIC cell.
 A physical cell ID determines the primary and secondary syncronization signal sequence
 It is similar to the Scrambling Codes in UMTS
 Cell ID is used for identify the cell within operator’s network while Physical Cell ID is used to transmit the data over that cell
For internal use


Parameters
AdjLMeasBw Measurement Bandwidth

Object: WCEL/ADJLo This parameter indicates the measurement bandwidth information common for all neighboring E-
Range: 6 (6), 15 (15), 25 UTRA cells on the carrier frequency. It is defined by the parameter Transmission Bandwidth
(25), 50 (50), 75 Configuration, NRB [36.104]. The values indicate the number of resource blocks over which the UE
(75), 100 (100) could measure.
Step: 1
Multiplicity: 1
Category: BASIC
 The values indicate the number of resource blocks over which the UE could measure
E-UTRA Frequency list
1…8
Channel Transmission  AdjLMeasBw is given to the UE in RRC: MEASUREMENT
Bandwidth Bandwidth
CONTROL message:
1.4 6 EARFCN_1
 …
Measurement bandwidth_1
3 15  Inter-RAT Measurement IE
5 25  E-UTRA frequency list (frequencies to be
EARFCN_2
10 50 measured together with their bandwidths)
…
15 75
…
20 100
[MHz] [NRB] EARFCN_3
For internal use


Parameters
AdjLEARFCN E-UTRA Absolute Radio Frequency Channel Number

Object: WCEL/ADJLo This parameter defines the E-UTRA Absolute Radio Frequency Channel Number of the neighboring
Range: 65535 E-UTRA frequency. This parameter defines the EARFCN of the downlink carrier frequency.
Step: 1
Multiplicity: 1
Category: BASIC
 AdjLEARFCN is given to the UE in RRC: E-UTRA Frequency list

MEASUREMENT CONTROL message: 1…8
 …
 Inter-RAT Measurement IE EARFCN_1
 E-UTRA frequency list Measurement bandwidth_1
(frequencies to be measured
together with their bandwidths) EARFCN_2
…
EARFCN_3
For internal use


Inter-system Measurements – measurements order
E-UTRA Frequency list:

Minimum number Maximum number
 LTE frequencies to be measured are based on the configured LTE neighbor frequencies and UE capabilities of configured LTE of E-UTRA
neighbors frequencies to be
 All frequencies where at least one LTE neighbor cell (WCEL/ADJE-object exists) is configured (value of WCEL/ADJL- PER EACH REQUENCY
measured
AdjLSelectFreq is ignored; it is used for redirection purposes only) RRC Measurement Control
 Maximum number of E-UTRA frequencies that can be given to UE in RRC: MEASUREMENT CONTROL message is 8.
The frequencies to be measured are put in the priority order in RRC: MEASUREMENT CONTROL message. The priority
order is determined by the RNC/HOPL-AdjLFreqPriority parameter. First, the priority ordered frequencies of the
1 8
strongest cell, then the second strongest cell and finally the third strongest cell, depending on the size of the active se t.
E-UTRA Frequency list Cell 1/ Cell2 neighbor

1…8 Priority 1
EARFCN_1
Measurement bandwidth_1 Cell 1/Cell 2 neighbor
Priority 2 Cell 3
WCDMA coverage is
underlayed by LTE
EARFCN_2 coverage – not shown
Measurement bandwidth_2 for simplicity
…
Cell 1
Cell 3 neighbor Priority 1 Cell 2
…
Active set
EARFCN_3
Measurement bandwidth_3 Serving cell
Cell 1 RSCP = -104dBm Cell 2 RSCP = -94dBm Cell 3 RSCP= -98dBm
For internal use


Inter-system Measurements – measurements order
Core Network
Cells in active set are under DRNC:
 Cell 3 neigbors are not present on the E-UTRA Frequency List IE send from SRNC to UE via RRC:
Iu Iu
MEASUREMENT CONTROL message
 This RRC message is based on SRNC neighbor frequencies only Iur
DRNC
SRNC
 However, neighbor of DRNC cell can become a target cell for Smart LTE HO if its EARFCN and
Measurement Bandwidth equals EARFCN and Measurement Bandwidth defined for neighbor of SRNC cell Iub Iub Iub Iub
NodeB
NodeB
NodeB
NodeB
 This is possible thanks to Neigboring E-UTRA Cell Information IE included in RNSAP: RADIO LINK
ADDITION/SETUP message received from DRNC over Iur (this IE is included only if DRNC cell in active
set has RAN2264 Smart LTE Handover license in state „On”) containing hadover path to LTE
E-UTRA Frequency list
RN
Cell 1 neighbor Priority 1
Sb
1…8
ord
er
EARFCN_1
Cell 3
Measurement bandwidth_1 WCDMA coverage is
Cell 1 neighbor Priority 2 underlayed by LTE
coverage – not shown
EARFCN_2 for simplicity
Cell 1
…
Cell 2
Active set
Cell 3 neighbor Priority 1
…
EARFCN_3 Serving cell
Cell 1 RSCP = -104dBm Cell 2 RSCP = -94dBm Cell 3 RSCP= -98dBm
For internal use


Inter-system Measurements - parameters
Parameters controling the IS LTE measurements:

 The timer RNC/FMCL-LTEMinHoInterval (default 10sec) determines the minimum interval between a successful inter-RAT handover from LTE to WCDMA
and the following inter-RAT handover attempt back to LTE related to the same RRC connection
 Neighbor frequency search period (FMCL/LTENCarrFreqSearchPeriod [default 1.5sec]) allows UE to find and report all potential LTE neighbor carrier
frequencies before the handover decision; During this period of LTE measurements, handover to LTE system is forbidden
 Measurement Reporting Interval is fixed (similarly to the RAN2980 Measurement Based LTE Layering). Thus, UE sends RRC: MEASUREMENT REPORT
message to RNC every 500ms
 RNC/FMCL- LTEMeasAveWindow (default 3sec) determines the maximum number of measurement reports (maximum size of the sliding averaging
window) from which the RNC calculates the averaged LTE RSRP and RSRQ values for the handover decision
 Maximum allowed period during which LTE measurements are performed is defined by RNC/FMCL-LTEMaxMeasPeriod (default 6sec); If timer expires,
RNC asks UE to stop the LTE measurements
 RNC/FMCL- LTEMinMeasInterval (default 5sec) determines the minimum interval between an unsuccessful inter-RAT (LTE) measurement , and the
following LTE measurement procedure related to the same RRC connection

Measurement
time period
Time
Sliding Averaging
For internal use

Inter-system Measurements – events during measurements
Events during measurements (cont.)

 If LTE measurement due to handover is ongoing and the last SRNC cell is deleted from the active set, the measurement are continued. However, LTE
handover shall not be started based on the measurement if all the cells of the active set are controlled by the DRNC. If an SRNC cell is added to the active
set during the LTE measurement so that UE is not anymore in anchoring mode, LTE handover shall be initiated if other criteria, including measurement
results, do not prohibit LTE handover. This follows the principles of GSM ISHO and RAN2980 Measurement based LTE Layering.
 This makes it possible to do handover if SRNC cell is first deleted and then added back to the active set during the ongoing measurements.
Core Network Core Network Core Network
Iu Iu Iu Iu Iu Iu
Iur Iur Iur

DRNC
DRNC
DRNC
SRNC
SRNC
SRNC
Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
Anchoring mode
Measurement period
RNC/FMCL-
LTEMaxMeasPeriod
Time
Handover started
For internal use Trigger appears

Inter-system Measurements – events during measurements
Events during measurements (cont.)

 If LTE measurement due to handover is ongoing and the last SRNC cell is deleted from the active set, the measurement are continued. However, LTE
handover shall not be started based on the measurement if all the cells of the active set are controlled by the DRNC. If an SRNC cell is added to the active
set during the LTE measurement so that UE is not anymore in anchoring mode, LTE handover shall be initiated if other criteria, including measurement
results, do not prohibit LTE handover. This follows the principles of GSM ISHO and RAN2980 Measurement based LTE Layering.
 This makes it possible to do handover if SRNC cell is first deleted and then added back to the active set during the ongoing measurements.
Core Network Core Network Core Network
Iu Iu Iu Iu Iu Iu
Iur Iur Iur

DRNC
DRNC
DRNC
SRNC
SRNC
SRNC
Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub Iub
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
Anchoring mode Anchoring mode
Measurement period
RNC/FMCL-
LTEMaxMeasPeriod
Time
Handover prohibited
For internal use Trigger appears

Handover Control
Handover Control Actions

 RNC uses RRC: MEASUREMENT REPORT messages to calculate particular cells’ RSRQ and RSRP levels
 This is used by Handover Control algorithm to decide the target cell for inter-RAT LTE handover
 The target cell is chosen from a group of the configured LTE neighbor cells - either under SRNC or DRNC

 Reported RSRP must be equal or higher than the threshold defined by the HOPL-AdjLMinRSRPLevel parameter Reported Cell 2
(main cell threshold is used) 1
 Reported RSRQ must be equal or higher than the threshold defined by the HOPL-AdjLMinRSRQLevel parameter
(main cell threshold is used)
Reported Cell
Step 2 3
 Cells with the highest priority EARFCN defined by HOPL-AdjLFreqPriority parameter is chosen (DRNC cells’
priority is set to the lowest possible value [0])
 If there is more than one EARFCN with an equal priority, the EARFCN with the highest RSRQ cell is prioritised
Step 3
 The cell having the highest RSRQ is chosen for the target cel for inter-RAT LTE handover.
Target LTE Cell
The RNC prevents handover to the target cell for which previous attempt was unsuccessful. Timer is defined as follows:
Time_interval = (1 + Number_of_LTE_HO_fails) * RNC/FMCL- LTEMinMeasInterval
For internal use


Handover Control
Handover Control Target LTE Cell Selection No supprot for 3G MOCN – HO to subscribers own
network is not guaranteed as UE measures all defined
Layer 1,2,3 - MOCN Operator 1 frequency layers (no layer filtering by PLMN ID before
Layer 4 - MOCN Operator 2 sending them in RRC: MEASUREMENT CONTROL)
1. RSRP/RSRQ Must be equal or
higher than the threshold
HOPL-AdjLMinRSRPLevel= -128 dBm
HOPL-AdjLMinRSRQLevel= -18 dB Reported Cell
Reported Cell 2
EARFCN 1 2. Highest priority EARFCN
HOPL-AdjLFreqPriority
1
EARFCN_Priority 5
Cell1.1 RSRP/RSRQ -129/-15
Cell1.2 RSRP/RSRQ -112/-9 EARFCN 1
Cell1.3 RSRP/RSRQ -102/-6 EARFCN_Priority 5 Reported Cell
Cell1.4 RSRP/RSRQ -106/-7 Cell1.2 RSRP/RSRQ -112/-9 3
EARFCN 2
EARFCN_Priority 7
3. Best RSRQ cell
Cell2.2 RSRP/RSRQ -129/-14 EARFCN 2
EARFCN_Priority 7 EARFCN 3
EARFCN 3
Cell2.1 RSRP/RSRQ -112/-9 EARFCN_Priority 7
EARFCN 3 EARFCN_Priority 7
EARFCN_Priority 7 Cell3.1 RSRP/RSRQ -102/-6
EARFCN 3 Cell3.2 RSRP/RSRQ -101/-7
Cell3.2 RSRP/RSRQ -101/-7 EARFCN_Priority 7
EARFCN 4 Cell3.2 RSRP/RSRQ -101/-7
EARFCN_Priority 6
For internal use


Message Flow
 As usual, Smart LTE Handover consists of the

UE Source NodeB Source RNC Core Network LTE
following sub-procedures:
 Handover Decision
Active radio link  Handover Preparation
Trigger appears  Handover Execution
NBAP: Radio Link Rec. Prep.  Handover Completion
 At the begining UE has an active radio link(s)
NBAP: Radio Link Rec. Ready
 The Handover Decision is made based on trigger:
RRC: Physical/Transport Channel Reconfiguration Compressed Mode
activation  Using WCEL- LTEHandoverEnabled parameter,
RRC: Physical/Transport Channel Reconfiguration Compl. (10 slot transmission gap; it can be set which triggers will be used for
E-UTRA Frequency List) handover
NBAP: Radio Link Rec. Commit
 Compressed Mode Measurements
RRC: Measurement Control  LTE frequencies to be measured are based on the
RRC: Measurement Report
configured LTE neighbor frequencies and
UE capabilities
Handover decision made in RNC
 TGPSI (Transmission Gap Pattern Sequence Identifier)
Handover decidion
 TGSN (Transmission Gap Starting Slot Number)
Handover preparation  TGL1 (Transmission Gap Lenght)
RANAP: Relocation Required  TGPL1 (Transmission Gap Pattern Lenght)
 TGMP (Transmission Gap pattern sequence
Measurement Purpose)
For internal use


Message Flow
 Handover Preparation
UE Source NodeB Source RNC Core Network LTE
 This phase is started once the Source NodeB
receives measurement results that meet HO to LTE
thresholds
RANAP: Relocation Required
 RNC sends Relocation Required message
towards the Core Network
Resource allocation on LTE
 Relocation Type IE („UE involved in relocation of
RANAP: Relocation Command SRNS”)
Handover execution  Source ID
RRC: Handover from UTRAN Command  Target ID
Handover access; Handover detection on LTE side  Source to Target Transparent Container
 LTE side allocates resources according to receivied
Handover completion Source to Target Transparent Container
LTE side send relocation complete mesage to Core Network
 Once LTE side is ready, Core Network sends
Relocation Command to Source RNC
RANAP: Iu Release Command
Handover Execution
RANAP: Iu Release Complete
 RNC order UE to move to LTE via Handover from
UTRAN Command including E-UTRA Message
RNC releases resources on Handover Completion
NodeB via NBAP
 Resources on source side (WCDMA) are released if
a UE has been successfully handed over to LTE
For internal use


Example
 User scenario presenting typical WCMDA – LTE Interworking procedures:

 First, UE is handed over to WCDMA due to coverage reasons; measurements of target layer are done in advance
 After timer expiration (minimum time interval in WCDMA) one of the Smart LTE Handover triggers appears; RNC orders UE to perform
measurements; Handover Control deceides to start handover procedure based on received reports and configured thresholds
 Finally, UE is back in LTE network
Coverage based handover Smart trigger based measurements Smart trigger based handover
A2 event B2 event T1, T2, T3 or T4 trigger Handover decision T1, T2, T3 or T4 trigger Handover decision
WCDMA RSCP
LTEMinHoInterval LTEMinMeasI
nterval
a1TimeToTriggerDeactInterMeasm
LTE RSRP
WCDMA RSCP [dBm]

-140 + threshold2a RNC/HOPL-AdjLMinRSRPLevel
LTE RSRP [dBm]
RNC/HOPL-AdjLMinRSRPLevel
-140 + b2Threshold1Utra
a2TimeToTriggerActWcdmaMeas
LTEMaxMeasPeriod LTEMaxMeasPeriod
b2TimeToTriggerUtraMeas
-115 + b2Threshold2UtraRscp
procedure
procedure
Handover
Handover
UE measures WCDMA UE measures LTE UE measures LTE

according to the list of the according to the list and according to the list
measurement objects sends reports to RNC and sends reports to
every 500ms RNC every 500ms
UE in LTE UE in WCDMA UE in LTE Time [s]
*For simplicity reasons, only one LTE frequency RSRP (without other frequency RSRP and RSRQ) are shown in graph
**On LTE side, hystereses equlas 0 assumed
For internal use


Fine-tuners - There are additional parameters that tunes triggering measurements for Smart LTE Handover:
Cell load
 Load criterion for triggering measurements is applied:

 If the cell is highly loaded, LTE is preferred, i.e. measurements and handover can be initiated
 If the cell is not highly loaded, WCDMA is preferred, i.e. measurements and handover cannot be initiated
 There are two load criteria:

 HSDPA power per user, originating from RAN2980 Measurement Based LTE Layering (WCEL-LTELayerCellHSLoad) WCDMA
HSDPA PPU
• Measured power per user must be lower than the parameter value in order =1
to enable LTE measurements
• The HSDPA power per user criterion is ignored if the special value „0” is set PNRTHSDPA  CellWeight ForHSDPALa yering
• For this feature, CellWeightForHSDPALayering always equals 1 max( NumberOfNRTHSDPAuser s,1)
 NRT user amount, originating from RAN2717 Smart LTE Layering (WCEL-SmartLTELayeringUA)
WCEL-SmartLTELayeringUE
#NRT users
• The configured NRT user amount threshold must be exceeded before measurements are initiated
Number of NRT users

Measurements allowed
• NRT user amount threshold of the SRNC main cell is checked
• Users utilizing Interactive or Background RABs are counted as NRT users
• The user amount criterion is ignored if the special value „0” is set Measurements not allowed
Time
For internal use


Service restrictions
 Inter-RAT handover from WCDMA to LTE is supported for the following services:
 PS Interactive (NRT) QoS class - request response pattern (e.g. web browsing)
 PS Background (NRT) QoS class - destination is not expecting the data within a RNMOBI-SmartLTELayeringServ
certain time (e.g. E-mails)
3 (0011) 01 –– redirection
redirection
not allowed
allowed
 Multi-RAB combinations: 1…3 NRT PS (Interactive/Background only) RABs
 Operator can choose which services can be handed over to LTE via RNMOBI-
SmartLTELayeringServ parameter; handover is allowed only if every PS RAB of
the UE is allowed to be handed over;
Bit 2 (PS Streaming) and Bit 3 (PS Conversational) of the RNMOBI- Bit 2 Bit 0
SmartLTELayeringServ parameter is ignored for the need of handover as PS Bit 3
Bit 1
Conversational and PS Streaming RABs cannot be handed over to LTE
 Inter-RAT handover from WCDMA to LTE is not supported for the following services:
 PS Conversational (RT) QoS class – I-RAT handover for multi-RABs containing this QoS class is also not supported
 PS Streaming (RT) QoS class – I-RAT handover for multi-RABs containing this QoS class is also not supported
 Push-To-Talk RABs - if UE has PTT RAB established, the measurements for inter-RAT WCDMA to LTE handover
cannot be be started; PTT identification is done by RAN2300 Optimized Push-To-Talk Experience via comparing RAB
parameters of the new RAB to values set to the RNP parameter PTTUEMapping – if parameters match, RAB is
considered as PTT
 CS RABs – if UE has any CS RAB established, the measurements for inter-RAT WCDMA to LTE handover cannot be
started
For internal use


RAN2264 Smart LTE Handover For NPI

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RAN2264 Smart LTE Handover For NPI

Uploaded by

Copyright:

Available Formats

You can setup the color/gradient and outline style of selected shapes with the “Shape_set_color_and_gradient” macro, or by clicking

For internal use

Smart LTE Handover

For internal use

Introduction Table of Contents

• RAN2067 LTE Interworking (RU20 On Top) and

For internal use

Introduction Table of Contents

Load balancing End user experience

For internal use

Introduction Table of Contents

For internal use

Technical Details Table of Contents

Trigger 2 : T2 HSDPA/HSPA to DCH/DCH CTS

Trigger 3 : T3 CS RAB Release with PS service ongoing

Trigger 4 : T4 Periodic trigger

For internal use

Interdependencies Table of Contents

RAN2067 license must be installed

No license needed for RAN2717 but Smart LTE Handover works

No license needed for RAN2980 but Feature allows seamless RAT

LTE measurements are prioritised

RAN2451 Support for E-DCH

Mandatory Interworking Optional Recommended Basic

Interdependencies Table of Contents

 RAN2067 LTE Interworking

For internal use

Interdependencies Table of Contents

No support for Time

For internal use

Interdependencies Table of Contents

 RAN2136 Fast Dormancy

For internal use

Interdependencies Table of Contents

 RAN1668 HSUPA Compressed Mode for IF and LTE HO

RAN2264 Smart LTE Handover 1 UE with HSPA service

For internal use

Deployment aspects Table of Contents

 License Type: Long-term ON/OFF licence

For internal use

Deployment aspects Table of Contents

 ADJL (Inter-RAT (LTE) neighbor frequency definitions)

For internal use

Deployment aspects Table of Contents

 ADJE-AdjePhysicalCellId  ADJE-AdjeCellId ADJE (up to 64)

For internal use

Deployment aspects Table of Contents

 Recommended trial area:

 WCDMA – LTE coverage is fully overlapped LTE coverage

For internal use

Configuration Management Table of Contents

Two parameterization scenarios are examined within this chapter

WCDMA RSCP [dBm]

LTE RSRP [dBm]

-140 + threshold2Wcdma -140 + threshold2Wcdma

Time [s] LTE RSRP WCDMA RSCP Time [s]

For internal use

Configuration Management Table of Contents

WCDMA RSCP [dBm]

LTE RSRP WCDMA RSCP Time [s]

Configuration Management Table of Contents

WCDMA RSCP [dBm]

LTE RSRP WCDMA RSCP Time [s]