Ericsson CSFB features

and Redirect with System Information .

Presented by:
Ahmed El-Shenawy
 Agenda

 1-CS Fallback to GERAN and UTRAN

 2-Redirect with System Information

 3-Measurement-Based CSFB Target Selection

 4-PSHO-Based CS Fallback to UTRAN

 5-CSFB – Case Study

 6-Mobility Guide

1
1-CS Fallback to GERAN and
UTRAN-CXC4010956

2
Feature summary

• The CS Fallback to GERAN and UTRAN feature enables eNodeBs to

respond to Circuit Switched (CS) service requests from an LTE UE.

• When an eNodeB receives a request, it directs the UE to GERAN or

UTRAN frequencies.

• The primary CS service is traditional voice traffic.

• CS fallback is the only method to provide traditional voice services for

single radio UEs unless IMS VoIP services are available.

• The CS Fallback to GERAN and UTRAN feature supports the UE to

release from the LTE network and attach to the neighboring GERAN or
UTRAN with minimal disruption for the end user.

3
Dependencies of CS Fallback to
GERAN and UTRAN
At least one of these features must be active before introducing the CS
Fallback to GERAN and UTRAN feature.

-Coverage-Triggered GERAN Session Continuity (FAJ 121 0495)

-Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)

4
Operational Process
-The UE sends an NAS extended service request to the MME requesting a CS fallback.

-The UE requests the CS service either as a response to a user activity in RRC Connected
mode or as a response to a paging message with a CS fallback flag in RRC Idle mode.

-The MME sends an S1-AP message with a CS fallback indicator to the eNodeB. The S1-AP
message can be one of the following:

A UE context modification request in RRC Connected mode.

A UE context initialization request in RRC Idle mode.

-The eNodeB selects a frequency for the redirection.

-The selection is based on the following:

UE capabilities
CS fallback frequency priorities defined by the following parameters:

GeranFreqGroupRelation. csFallbackPrio
UtranFreqRelation.csFallbackPrio

5
 Operational Process-2

-When several possible target frequencies have the same priority, the eNodeB applies a round robin scheme
for the selection.

-The eNodeB initiates a blind RRC connection release with redirection by sending an RRC connection
release message directing the UE to the selected frequency.

-The node also sends an S1-AP UE context release request to the MME.

-The UE changes RAT and starts accessing the new RAT attaching to the indicated target frequency.

-The UE sends a CM service request to the BSC or RNC. Once the request is accepted, the UE starts the CS
session.

-Once the UE is attached to the target RAT, it can continue to request packet switched services if those are
available.

6
CSFB Signaling

7
CSFB Signaling-2

Context Modification Request

8
 Feature parameters
GeranFreqGroupRelation.csFallbackPrio
UtranFreqRelation.csFallbackPrio
csFallbackPrio=0{-1..7} Prioritizes GERAN Frequency group among all
frequencies related to the cell for UEs in connected mode.
---------------------------------------------------------------------.
The value -1 means the frequency is excluded.
The value 0 means the lowest priority.
The value 7 means the highest priority.
csFallbackPrio=0{-1..7} Prioritizes UTRAN frequencies among all frequencies
related to the cell for UEs in connected mode.
---------------------------------------------------------------------
The value -1 means the frequency is excluded.
The value 0 means the lowest priority.
The value 7 means the highest priority.
9
CSFB SR KPI

10
Feature activation
 To activate the feature:

1-licence should be installed .

2-feature should be activated.

11
Difference between License-service and
feature state

12
 2-Redirect with System
Information-CXC4010973

13
 Feature summary
 The Redirect with System Information feature improves outage time
when the UE is redirected from LTE to one of the following networks :
-GSM
-WCDMA

 This is important when performing a CS fallback, since the UE is able to

connect to the circuit switched domain faster.

 The following concepts apply to the operation and maintenance of the

Redirect with System Information feature:

External cell:
External cells in the eNodeB hold information about cells in the
UTRAN
E-UTRAN
GERAN

14
Feature summary-2

Cell relation :
Relations are established between cells in the eNodeB and in the following
networks:

-GERAN
-UTRAN
-E-UTRAN

RAN Information Management association:

A RAN Information Management association is created between the
serving BSS and the target BSS for redirecting the UE with system
information. The redirection with system information works between the
cell on the serving BSS (eNodeB) and the cell on the target BSS (BSC or
RNC node).

15
Dependencies of redirect with
system information.
At least one of below features must be activated.

Coverage-Triggered GERAN Session Continuity (FAJ 121 0495)

Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)

CS Fallback to GERAN and UTRAN (FAJ 121 0856)

Hint: RWR works in 2 scenarios:

1-due to coverage
2-due to CSFB

16
Related features to redirect with
system information.
PSHO-Based CS Fallback to UTRAN(FAJ 121 3072)

 When the PSHO-Based CS Fallback to UTRAN and Redirect with

System Information features are used together, NACC information
is included in RRC connection release message after
measurement timeout or handover preparation failure.

17
What is RIM and how it works?

 RIM: RAN Information Management: Functionality supporting the

exchange of information, via the Core Network (CN), between peer
application entities located in a GERAN, UTRAN or E-UTRAN access
networks.

 RIM association: link between a cell in the UTRAN

RNC/GERAN BTS and an eNB or E-UTRAN cell that has
initiated a information request related to that cell for the UTRA SI
application

18
RIM Support for System Information Transfer to
LTE- CXC 403 0128

This is a 3G feature which should be activated in Node B for

supporting LTE cell with it`s system information. For GERAN we
need to activate LTE to GSM With NACC to receive system
information of GERAN Cells.

Once a RIM association is established

in the eNodeB by the operator, the
eNodeB receives updates from the
RNC when SI for the UTRAN cell in
that RIM association changes. The
following SI updates result in a RIM
update: MIB, SIB1, SIB3, SIB5,
SIB5bis, SIB7, SIB11 and SIB12.
Optionally SIB11 and SIB12 can be
removed from the RIM update.

19
Feature operation of redirect with
system information.
 This feature supports the redirection of UEs by adding system information for cells.

 The Redirect with System Information feature extends the following features by including
system information for cells belonging to the target RAT when performing RRC connection
release with redirect to GSM, WCDMA
Coverage-Triggered GERAN Session Continuity
Coverage-Triggered WCDMA Session Continuity
CS Fallback to GERAN and UTRAN.

 The RAN Information Management function collects information from NACC

for GERAN and system information for UTRAN.

 The feature enables the UE to connect to the target cell faster because the
system information is directly supplied to it during release time. It is
unnecessary to read the system information from the target system

20
RAN Information Management Pool
Concept.
Priority Pools:

 To limit the load on a system, RAN Information Management

associations are set up to some external cells. These cells are then
subject to decision about redirection at UE release or CS Fallback.

 The prioritized external cells are selected based on the

GeranCellRelation.coverageIndicator or
UtranCellRelation.coverageIndicator

 For each E-UTRAN cell, two pools of prioritized external cells are
created, one for session continuity and one for CS Fallback purpose.
Different sets of two pools are created separately for GERAN and
UTRAN. An external cell can be present in both the session continuity
and CS Fallback pools.
21
 RAN Information Management Pool
Concept-2
Building Priority Pools:

 The priority pools are initially built at the eNodeB start up. All GERAN
and UTRAN neighboring cells are initially evaluated from a license and
RAN Information Management association capability point of view.

 Suitable external cells are subject to the prioritization algorithm to

create the pools. After the evaluation, necessary RAN Information
Management associations are created.

22
RAN Information Management Pool
Concept-3
Updating Priority Pools:

 The pools are updated dynamically when RAN Information Management conditions or coverage
conditions change.
 The eNodeB checks condition changes that affect pool prioritization of external cells.
 A given cell can be moved in or out of a pool depending on the circumstances.

Supervised conditions specifically concern the following points:

• The value of the GeranCellRelation.coverageIndicator or UtranCellRelation.coverageIndicator
attribute
• RAN Information Management capability
• Cell creation
• Cell removal
• Relation creation
• Relation removal

 The adaptation of the pool content can result in the creation or removal of RAN Information
Management associations, according to the current needs .

23
Configuration.

 For a coverage-triggered RRC connection release with redirect, the

system information is only included if the mobilityAction parameter is
set to RELEASE_WITH_REDIRECT_NACC for the specific RAT.

 For a CS fallback-triggered RRC connection release with redirect, the

system information is only included if the mobilityActionCsfb
parameter is set to RELEASE_WITH_REDIRECT_NACC for the
specific RAT.

 For UTRAN, the system information is also included for CS fallback-

triggered RRC connection release after measurement timeout or
handover preparation failure, if the mobilityActionCsfb parameter is
set to HANDOVER.

Hint: NO HO From LTE to 2G , only RWR, as mentioned in slide 34.

24
Prioritization of Cells.

 The prioritization of external cells is based on how the

GeranCellRelation.coverageIndicator or
UtranCellRelation.coverageIndicator attribute is configured.

 The CSFB and Session Continuity pools have their own level of
priority.

 Cell candidates with the same GeranCellRelation.coverageIndicator or

UtranCellRelation.coverageIndicator value are placed in the prioritized
list in a random order.

 If there are more than four cell candidates with the same
GeranCellRelation.coverageIndicator or
UtranCellRelation.coverageIndicator value placed in the top of the
prioritized list, only the first four cells from the list are used for pool
constitution.

25
Prioritization of Cells-2
 For the CSFB list, the eNodeB includes system information for cells with the
GeranCellRelation.coverageIndicator or UtranCellRelation.coverageIndicator
attribute set to the following values in this order:
COVERS
OVERLAP
CONTAINED_IN or NONE

 For the Session Continuity list, the eNodeB includes system information for
cells with the GeranCellRelation.coverageIndicator or
UtranCellRelation.coverageIndicator attribute set to the following values in this
order:
COVERS
NONE
OVERLAP
CONTAINED_IN

26
Possible values for coverage
indicator

27
prioritizing cells Examples.
Example-1

 Each pool contains the same candidates, and every candidate has the
GeranCellRelation.coverageIndicator or UtranCellRelation.coverageIndicator attribute set to COVERS. Four
active RAN Information Management associations are set up in the eNodeB.

 Since the Session Continuity and CSFB structures are the same in the internal cells, they add the same
external cells. However, each association is only added once, regardless of how many internal cells it is
used in. This is because the RAN Information Management associations are between the eNodeB and the
target cell.

28
prioritizing cells Examples-2
Example-2

The pools contain different candidates, and the candidates have the
GeranCellRelation.coverageIndicator or UtranCellRelation.coverageIndicator attribute set to
different values. Six active RAN Information Management associations are set up in the
eNodeB.

Each association is only added once, regardless of how many internal cells it is used in. This is
because the RAN Information Management associations are between the eNodeB and the
target cell

29
 Feature parameters
Parameter Description
AnrFunctionGeran.rimIntegrationEnabled This parameter indicates if ANR should be able to modify RIM associations to GERAN cells

AnrFunctionUtran.rimIntegrationEnabled This parameter indicates if ANR should be able to modify RIM associations to UTRAN cells.

ENodeBFunction.forcedSiTunnelingActive Specifies whether or not the functionality to send NACC information, regardless of UE capability,
is activated, provided that the feature Redirect with System Information is active.

maxNoCellsNaccSessionCont = 4 { 0..16 }
Maximum number of NACC elements, where one NACC element corresponds to one cell, that can be
included in an RRC Connection Release message triggered by Session Continuity (bad coverage).
ENodeBFunction.maxNoCellsNaccSessionCont

Dependencies: Only applicable if Redirect with System Information is active.

maxNoCellsNaccCsfb=4{0..16}
Max number of UTRAN/GERAN cells with system information. Can be included in an RRC connection
release message triggered by CS Fallback

Dependencies: Only applicable if Redirect with System Information is active.

ENodeBFunction.maxNoCellsNaccCSFB

30
Feature parameters-2
UtranCellRelation.coverageIndicator
GeranCellRelation.coverageIndicator
ExternalGeranCell.rimAssociationStatus
ExternalUtranCellFDD.rimAssociationStatus
ExternalGeranCell.rimCapable
ExternalUtranCellFDD.rimCapable
GeranFreqGroupRelation.mobilityAction
GeranFreqGroup.Relation.mobilityActionCsfb Fallback.
UtranFreqRelation.mobilityAction
UtranFreqRelation.mobilityActionCsfb
coverageIndicator//Following options are possible for coverage area of cell indicated by relation:
-(2) Whether coverage area has approximately same coverage area (overlap) as this cell.
-(1) Whether coverage area fully covers this cell.
-(3) Whether coverage area is fully contained in this cell.
-(4)There is no coverage relation (none)(e.g. the cells only partially overlap
Value influences SCell priority in Dynamic SCell Selection for Carrier Aggregation.
This parameter indicates the current status of the RIM association to this external cell.
This parameter indicates if the external GERAN cell is RIM capable. If the value is RIMIncapable,
no attempt will be made to create a RIM association to the external GERAN cell,
other values will result in a attempt to create a RIM association.
This parameter indicates if the external Utran cell is RIM capable. If the value is RIMIncapable,
no attempt will be made to create a RIM association to the external Utran cell,
other values will result in a attempt to create a RIM association.
mobilityAction
The preferred way to transfer a UE in connected mode to a GERAN frequency group in case of
coverage triggered mobility.
mobilityActionCsfb
The preferred way to transfer a UE in connected mode to a GERAN frequency group in case of CS
Hint: as mobility action is per freqrelation ,So no mobility due to CSFB/Coverage will occure to
frequencies which is not defined as freq relation to source cell.
The preferred way to transfer a UE in connected mode to a UTRAN TDD frequency in case of
coverage triggered mobility.
The preferred way to transfer a UE in connected mode to a UTRAN FDD frequency in case of CS
Fallback.
31
Feature parameters-3
 RimAssosiationstatus:

32
Feature parameters-4
 Rimcapability

33
Feature parameters-5
 Mobilityaction values.
 Possible Mobility action values to GERAN Cells:

 Possible Mobility action values to Utran Cells :

34
Feature activation

 To activate the feature:

1-licence should be installed .

2-feature should be activated.

35
Log analysis for CSFB WITH Rim and
Without Rim

 CSFB Without RIM.

As shown here, when not

using RIM,Enode B sent
the whole band 10767 in
RRC connection release
message , and UE will go
to this band and start
listening to system
information messages to
select cell and camp on it.

Note : both pictures were taken on different sites, that is why band on first pic is 10762
and on second pic is 10787 36
Log analysis for CSFB WITH Rim and
Without Rim-2
 CSFB With RIM

As show here, when RIM is

active, then no need to listen to
system information, and Enode
B sent 4 cells on RRC
connection release message
with their system information
and PCI

Hint: according to connectedmodepriority value , enode b will decide on which band it

will send RWR, then according to Coverage indicator and other RIM parameters , 37
Enode B will decide which cells to be on CSFB OR SC pool
 3-Measurement-Based CSFB
Target Selection-CXC4011664

38
Feature summary
 The ‘CS Fallback to GERAN and UTRAN’ : transfers a UE
requesting a CS service (a voice call) to another Radio Access Technology
(RAT) which can handle a CS connection using the Release with Redirect
(RwR) mechanism without the UE making measurements on the target RAT.

 The ‘Measurement-Based CSFB Target Selection

do the following:

1- enables the eNodeB to redirect the UE to the highest prioritized

frequency, based on measurements when a Circuit Switched (CS) fallback is
required.

2-This feature also allows the operator to define alterative target

frequencies if the measurement times out, or a Packet Switched (PS) handover
preparation fails.

Note: The Packet Switched handover is enabled by the PSHO-Based CS Fallback to UTRAN
feature.

39
Feature summary-2
 The ‘Measurement-Based CSFB Target Selection’ feature enables a
more robust RwR mechanism by using two lists to determine the target
frequency.

 The first list (List 1) is defined by the ‘csFallbackPrio’ parameter and is

the CSFB priority list, which gives the top priority frequencies for
measurement.

 The second list (List 2) is defined by the ‘altCsfbTargetPrio’ parameter

and is an alternative CSFB target list which is used when a configurable
measurement time-out expires.

 The ‘Measurement-Based CSFB Target Selection’ feature can also

improve the performance of the ‘PSHO-Based CS Fallback to UTRAN’
optional feature by using the List 2 to find a target frequency for RwR
when a handover preparation fails.

40
Feature summary-3

41
Dependencies of measurement
based CSFB target selection.
The feature has below requisites.

42
Feature operation
 The flow chart illustrated in below figure shows the operation of the
‘Measurement-Based CSFB Target Selection’ feature when it is used without
The ‘PSHO-Based CS Fallback to UTRAN’ optional feature.

43
Feature operation-2
1-The MME sends an S1-AP message with a CS fallback indicator to the
eNodeB. The S1-AP message can be one of the following:

- A UE context modification request.

- A UE context initialization request, when the ‘csfbMeasFromIdleMode’
parameter is set to ‘TRUE’.

Note:
When CS Fallback is requested for a UE in idle mode,
csfbMeasFromIdleMode’
controls if measurements for RwR and handover must be performed. If the
parameter is set to TRUE, the measurements are performed for UEs both
in idle and connected modes. If the parameter is set to FALSE, the
measurements are performed for UEs in connected mode only and a blind
release with redirect is done for this UE

44
Feature operation-3

2-If one of the following conditions is met, the eNodeB continues Step 3.

- The ‘ueMeasurementsActive’ parameter is set to ‘TRUE’.

- The ‘ueMeasurementsActiveUTRAN’ or ‘ueMeasurementsActiveGERAN’
parameters are set to ‘TRUE’ when the ‘Mobility Control at Poor Coverage’ feature
is activated.

Otherwise the eNodeB selects the RwR target as the ‘CS Fallback to
GERAN and UTRAN’ feature defines.

3-The eNodeB triggers the Event B1 (or B2, depending on UE capabilities)

measurements, starting from the highest prioritized frequency in the List 1.
When a UE measurement report is received, the eNodeB selects the first
frequency in the report as the target to do an RwR.

45
Feature operation-4
4-If no target frequency is found until the configurable time-out
expires (CsfbHoTargetSearchTimer), the eNodeB releases the
UE to a frequency that is selected from the List 2. This is based on
the following criteria

- UE capabilities
- Alterative CS fallback target frequency priorities defined with the
‘altCsfbTargetPrio’ parameter for each available frequency
relation

46
Feature parameters
thresholdEcNo=-240{-245..0}

Ratio of energy per modulation bit to noise spectral density used

in the ThresholdUTRA, the threshold value for Event B1 and
threshold2 value for Event B2.
ReportConfigCsfbUtra.thresholdEcNo
Unit: 0.1 dB

Resolution: 5
Dependencies: Only used when measQuantityUtraFDD is set to
ECN0

thresholdRscp=-115{-120..-24} Received Signal Code Power in

the ThresholdUTRA, the threshold value for Event B1 and
threshold2 value for Event B2.
ReportConfigCsfbUtra.thresholdRscp
Unit: 1 dBm
Dependencies: Used when measQuantityUtraFDD is set to
RSCP.
thresholdGeran=-110{-110..-47} The Signal Quality in the
ThresholdGERAN, threshold value for event B1 or B2.
ReportConfigCsfbGeran.thresholdGeran
Unit: 1 dBm
hysteresis=10{0..150} The hysteresis value for the event B1 and
event B2, threshold2, measurement.
ReportConfigCsfbUtra.hyteresis
Unit: 0.1 dB

Resolution: 5

Note: B2 threshold 1 is hardcoded and always

satisfied.
47
Feature parameters-2
ReportConfigCsfbGeran.hysteresis
ReportConfigCsfbGeran.timeToTrigger
ReportConfigCsfbUtra.timeToTrigger
ENodeBFunction.csfbMeasFromIdleMo
de
hysteresis=10{0..150} The hysteresis value for the event B1
and event B2, threshold2, measurement.
Unit: 0.1 dB
Resolution: 5
timeToTrigger=40{0, 40, 64, 80, 100, 128, 160, 256, 320, 480,
512, 640, 1024, 1280, 2560, 5120} The time to trigger value
for the event B1 or B2 measurement.
Unit: 1 ms
timeToTrigger=40{0, 40, 64, 80, 100, 128, 160, 256, 320, 480,
512, 640, 1024, 1280, 2560, 5120} The time to trigger value
for the event B1 or B2 measurement.
Unit: 1 ms
csfbMeasFromIdleMode
When CS Fallback is requested for a UE in idle mode this
parameter controls if measurements for release with redirect
and handover must be performed. If the parameter is set to
false a blind release with redirect is done.
Dependencies: This parameter is only relevant for features
'Measurement-Based CSFB Target Selection' and 'PSHO-
based CS Fallback to WCDMA' .
48
Feature parameters-3
UeMeasControl.csfbHoTargetSearchTime
r
GeranFreqGroupRelation.altCsfbTargetPr
io
UtranFreqRelation.altCsfbTargetPrio
csfbHoTargetSearchTimer=500{1..12000} Length of time the
eNodeB waits for reports from B1 and B2 measurements
configured in the UE for CS Fallback reasons.
Unit: 1 ms
altCsfbTargetPrio=0{-1..7} Prioritizes the GERAN frequency
group among all frequencies related to the cell for UEs in
connected mode.
Sets the priority to the alternative target frequency/frequency
group to which to make release with redirect, when
measurement or handover to selected target fails.
Value -1 means the frequency is excluded.
Value 0 means the lowest priority.
Value 7 means the highest priority.
altCsfbTargetPrio=0{-1..7} Prioritizes UTRAN frequencies
among all frequencies related to the cell for UEs in connected
mode.
Sets the priority to the alternative target frequency/frequency
group to which to make release with redirect when
measurement or handover to selected target fails.
Value -1 means the frequency is excluded.
Value 0 means the lowest priority.
Value 7 means the highest priority.
49
Feature activation
 To activate the feature:

1-licence should be installed .

2-feature should be activated.

Note: feature is not activated on this RBS 

50
4-PSHO-Based CS Fallback to
UTRAN-CXC4011663

51
Feature Summary
 The ‘CS Fallback to GERAN and UTRAN’ features transfers a
UE requesting a CS service (a voice call) to another Radio Access
Technology RAT) which can handle a CS connection using the Release with
Redirect (RwR) mechanism

 The ‘PSHO-Based CS Fallback to UTRAN allows the eNodeB to use

handover rather than RwR to transfer a UE to WCDMA when a Circuit
Switched (CS) fallback is required

 The ‘PSHO-Based CS Fallback to UTRAN’ feature supports blind handover

and handover to a WCDMA frequency based on UE measurements.

 Using handover instead of RwR gives a shorter interruption in the ongoing

PS data session . Also when blind handover is used the CS setup time is
shorter.

52
Feature Summary-2

 When receiving a voice call request from UE, the eNodeB initiates a blind
handover to transfer UE to the target cell on the highest prioritized frequency.
The CSFB priority list known as ‘List1’ is defined by the ‘csFallbackPrio’
parameter “in case blind HO was applicable”. If the blind handover is not
applicable, the eNodeB triggers measurement and transfers the UE to the first
cell reported

 When the feature is used in conjunction with the ‘Measurement-Based CSFB

Target Selection’ the second list (List 2) defined by the
‘altCsfbTargetPrio’ parameter is used to find an alternative CSFB target cell
when a configurable measurement time-out expires
(CsfbHoTargetSearchTimer).

Note:
RwR is always used to transfer the UE to GSM when a CS fallback is required
Mobility action is always RWR or RWR-NACC with GERAN FREQ Group relation
MO Refer to slide 34 .
53
Feature Summary-3

54
Feature Summary-4
 The following conditions must be met to allow the ‘PSHO-Based CS
Fallback to UTRAN’ feature to handover a UE to UTRAN when CS fallback
is triggered:

 Conditions for HO:

1. The target frequency is a WCDMA frequency.

2. The UE supports handover to the target frequency.

3. The preferred way to transfer a UE to a WCDMA frequency must be handover defined

with the ‘mobilityActionCsfb’ parameter set to ‘HANDOVER’.

4. The frequency relation has at least one cell relation which can be used for handover
with the value true for the attribute isHoAllowed.

 If these conditions are not met eNodeB transfers the UE using RwR in the
same way as the CS Fallback to GERAN and UTRAN features.

 Note : here we are talking about using PS HO based with (CSFB to Utran and Geran),
and we are not using measurement based target selection feature yet, so till now we
have only one list.
55
Feature Dependencies
 This feature has several prerequisites

 Coverage-Triggered WCDMA IRAT Handover (FAJ 121 0897)

 Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)

 CS Fallback to GERAN and UTRAN (FAJ 121 0856)

56
PSHO-Based CS Fallback to UTRAN Operation (without
Measurement-Based CSFB Target Selection)

57
PSHO-Based CS Fallback to UTRAN Operation (without
Measurement-Based CSFB Target Selection)-2

1-If the following conditions are met, a blind handover is initiated to transfer
UE to a target frequency, and Step 4 continues. Otherwise, go to Step 2.

 Conditions for Blind HO:

- A blind handover from the serving cell can be initiated with the
‘covTriggerdBlindHoAllowed’ parameter set to ‘TRUE’.

- There must be a cell that is covering the serving cell completely with
the ‘coverageIndicator’ parameter set to ‘COVERS’. Therefore, it is
safe to send the UE to the cell without measuring.

-For the blind handover, the target frequency to which the UE is transferred
with highest priority in List 1 is selected.

58
PSHO-Based CS Fallback to UTRAN Operation (without
Measurement-Based CSFB Target Selection)-3

2-If the blind handover is not applicable, the UE starts a B1 (or B2)
event measurement on the highest prioritized frequency selected in
List 1.

 Conditions for measurements:

one of the following conditions must be met.

-The ‘ueMeasurementsActive’ parameter is set to ‘TRUE’.

-The ‘Mobility Control at Poor Coverage’ feature is activated and the

‘ueMeasurementsActiveUTRAN’ or ‘ueMeasurementsActiveGERAN’
parameter is set to ‘TRUE’.

If the measurement cannot be started, the RwR is applied to transfer the UE

to one of the highest prioritized frequencies in List 1.

59
PSHO-Based CS Fallback to UTRAN Operation (without
Measurement-Based CSFB Target Selection)-4

3-The UE sends a measurement report to the eNodeB and a target cell is

selected for the following situations:

-If the ‘mobilityActionCsfb’ parameter is set to ‘HANDOVER’, the first

cell in the report having the parameter ‘isHoAllowed’ set to ‘TRUE’ is
selected. This cell becomes the target cell for handover.

-If all cells in the report do not allow handover with the ‘isHoAllowed’ parameter
set to ‘FALSE’, the target frequency becomes the target for RwR.

-if the ‘mobilityActionCsfb’ parameter is set to ‘RELEASE WITH

REDIRECT’, the target frequency becomes the target for RwR.

Notes:
• If the A2 critical measurement report is received before the B1 measurement
report, one of the highest prioritized frequencies in List 1 is selected as a
target frequency to do RwR.

• If the measurement times out, one of the highest prioritized frequencies in

List 1 is selected as a target frequency to do RwR.

60
PSHO-Based CS Fallback to UTRAN Operation (without
Measurement-Based CSFB Target Selection)-5

4-After a target cell is selected, a handover preparation starts and the handover
is executed.

5-If the preparation fails, the RwR is applied to transfer UE to the frequency
which is selected in one of the following ways:

- If the preparation for blind handover fails, one of the highest prioritized
frequencies in List 1 is selected.

- If the preparation for handover but not for blind handover fails, the
frequency in the measurement report from UE is selected as the target
frequency.

61
PSHO-Based CS Fallback to UTRAN Operation (with Measurement-
Based CSFB Target Selection)

62
PSHO-Based CS Fallback to UTRAN Operation (with
Measurement-Based CSFB Target Selection)-2

 The operation of the ‘PSHO-Based CS Fallback to UTRAN’ feature when it is

used with the ‘Measurement-Based CSFB Target Selection’ is the same but with
the following exceptions:

3: If the measurement procedure times out the UE is transferred to an

alternative frequency based on List 2 defined by the ‘altCsfbTargetPrio’
parameter.

4: If the handover fails, whether it is blind or not the UE is transferred to an

alternative frequency based on List 2 defined by the ‘altCsfbTargetPrio’
parameter.

Remember that :

When CS Fallback is requested for a UE in idle mode, ‘csfbMeasFromIdleMode’

controls if measurements for RwR and handover must be performed. If the
parameter is set to false, a blind release with redirect is done Refer
to slide 44/48.

63
Feature activation
 To activate the feature

1-licence should be installed .

2-feature should be activated.

Feature is not working here.

64
5-CSFB – Case Study

65
 Case Study-1-Activated CSFB features
To check all CSFB feature if activated.

66
 Case Study-2-Check redirect with system
information if activated.

Checking redirect with system information using invl command.

67
Case Study-3-Checking blind HO

68
Case Study-4-Mobility action
No Geranfreqgrouprelation on L5555

Using RWR-NACC for CSFB and HO for session continuity

69
 Case Study-5-Measurment status

Check if measurement is Active

Check if measurement is Active from Idle mode

70
Case Study-6-CSFB Prio-for Utran

71
Case Study-7-CSFB Prio-For GERAN

72
6-Mobility Guide

73
Mobility Guide
The aim of this part is just to organize and link parameters that control RWR/HO in case Poor coverage and CSFB.

74
Thank You

75