LTE Feature Training for Subcon

CSFB VoLTE and CA

Author/ Email : Jedsada 294469

Version : V1.0 (20151104)
HUAWEI TECHNOLOGIES CO., LTD.
Index
CS Fallback
VoLTE
CA (Carrier Aggregation)
CSFB Introduction

Principle Benefits
Voice fallback to GSM or UMTS in the overlay area of LTE and
GSM/UMTS
UE support multi-mode Quick Good
Two option for LTE data services: Deployment
Low cost
Experience
Handover to GSM or UMTS (UE supported)
Redirection to GSM or UMTS
CSFB Architecture and Functionalities
Need to be R8 ready
Maintaining SGs for the mobility
association with MME MSC/VLR management and paging
procedures between EPS
A and CS domain.

Iu-cs Gs Deriving a VLR number and LAI from the TAI of

GERAN Gb SGSN C/D the current cell, or using a default VLR number and
LAI.
Gr Maintaining SGs association with MSC/VLR for
HSS/HLR
EPS/IMSI Attached UE
SGs
UTRAN Iu-ps Triggering paging to eNodeB (when MSC-S pages
S3 the UE)
S6a
Initiating IMSI Detach at EPS Detach
S12
Multi-mode G/U/L
CSFB capable S4 PCRF
Support of procedures: MME
Combined EPS/IMSI Attach, S11
Update, Detach.
S7 Rx
S1-MME
S5 Internet / intranet /
SGi
Operators & 3rd Party
S1-U Applications
E-UTRAN S-GW PDN-GW
G/U/L handset

Forwarding paging request for CS

domain to the UE.
Directing the UE to the target CS
capable cell. (PS HO/redirection
with or without SIBs).
CSFB Procedure

MSC server
Terminating side
MME The MSC server sends a paging request to the MME over the
SGs interface.
CS SGs EPC The MME forwards the paging request instructing the UE to fall
back to the 2G or 3G network.
3
1
The UE falls back to the 2G or 3G network.
The UE sends a paging response to the MSC server and
answers the call based on the normal terminating flow.
2G/3G LTE
2
MSC server
Fallback MME
1

CS SGs EPC
Originating side 4
2
The UE sends a voice call request to the MME. The MME
then instructs the UE to fall back to the 2G or 3G network.
The UE falls back to the 2G or 3G network..
2G/3G 3
LTE
The UE initiates a call based on the normal originating flow
on the 2G or 3G network. Fallback
CSFB Mobile Originating Call

6 7

NodeB RNC MSC-VLR HSS/HLR

4 SGSN
Inter-system change

SGs
UMTS
LTE
Phase Flows
A 1. Ext Service Request (CSFB indicator)
4 MME 2. S1 AP Message (CSFB indicator)
1 3. Optional measurement
2 B
1 4. PS HO or PS redirection
3 5. eNodeB direct the UE to G/U
5 6. Resource located, UE initiate CS call
eNodeB SAE-GW C
7. MSC processes UEs calling(IAM)

CSFB MO procedure:
A: Voice service request is activated from UE.
B: MME indicates UE fall back to GERAN/UTRAN for voice service via eNodeB, UE sends service request to GERAN/UTRAN; in the mean
time, MME informs GSM/UMTS CS Core to prepare resource.
C: When resource in GSM/UMTS network is allocated, UE falls back to GERAN/UTRAN for voice service; And then UE will initiate the CS
voice call, MCS processes the UEs calling request and sends IAM(Initial Address Message) to CS core.
CSFB Mobile Terminating Call

9 1

NodeB RNC HSS/HLR

MSC-VLR
SGSN
Inter-system change

UMTS SGs

LTE Phase Flows

A 1.IAM: Initial Address Message
2.Paging Request (Domain indicator: CS)
MME 3.Ext Service Request (CSFB indicator)
2
3 4.S1AP Message (CSFB indicator)
4 B 5.Measurement
6
6.PS HO or PS Redirection
2
7.eNodeB direct the UE to G/U
3
5 eNodeB SAE-GW 8.Paging Response
7 C 9.Voice Call establishment

CSFB MT procedure:
A: GSM/UMTS MSC initiates CS paging to the called party (LTE UE), voice service is requested by LTE UE.
B: MME indicates UE fall back to GERAN/UTRAN for voice service via eNodeB, UE sends service request toGERAN/UTRAN; in the mean
time, MME informs GSM/UMTS CS Core to prepare resource.
C: When resource in GSM/UMTS network is allocated, UE falls back to GERAN/UTRAN for voice service.
CSFB Call Flow (PS Handover)

MO Call MT Call
UE eNodeB RNC MME MSC SGSN UE eNodeB RNC MME MSC SGSN S-GW
P-GW
1. Extended Service Request 1.Paging Request
(containing a CS Fallback Indicator)
Paging
2. S1-AP Message
(containing a CS Fallback Indicator) 2.Extended Service Request
(containing a CS Fallback Indicator)
S1-AP Response Message Service
Request

3. Optional measurement report

3. S1-AP message with CS Fallback indicator

4. PS handover preparation phase

Handover Command 4. Subsequent procedure similar to that in a mobile-originated case, with the CS
call establishment procedure replaced with a Paging Response message
Handover
Command

5.CS call establishment procedure with LAU or combined RAU/LAU

6.PS handover execution phase

CSFB Call Flow (PS Redirection)

MO call (R9: with RIM) MO call (R8: without RIM)

UE eNodeB RNC MME MSC SGSN UE eNodeB RNC MME MSC SGSN

1.Extended Service Request 1.Extended Service Request

(containing a CS Fallback Indicator) (containing a CS Fallback Indicator)

2.S1-AP Message with CS Fallback Indicator

2.S1-AP Message with CS Fallback Indicator
S1-AP Reponse Message
S1-AP Reponse Message
3.Optional measurement report

4. RRC Connection Release with UTRAN 3.Optional measurement report

frequency\cell id\cell System information
4. RRC Connection Release with UTRAN frequency

S1 UE context release
S1 UE context release
5. LAU, combined RAU/LAU, or RAU and LAU
5. LAU, combined RAU/LAU, or RAU and LAU

6.CS call establishment procedure

6.CS call establishment procedure
CSFB Comparison PS HO & Redirection

CSFB PS HO
Prepare resource for target
There is confirmation from target (Have OSS Counter)
Keep UE context till get confirmation
CSFB PS Redirection
No preparation before releasing UE
No UE context after releasing and no confirmation
Unable to measurement success rate
Flash CSFB ( R9 Redirection with SIB
RAN Information Management (RIM) Procedure
To support Flash CS Fallback, eNB requires exchange information between E-UTRAN and GERAN/UTRAN through the core networks.
Flash CS Fallback is defined in 3GPP R9 .With this function, SIB can be included into the RRC connection Release during the
redirection procedure. This is archived by the RIM procedure. with RIM, eNB can get information from GERAN/UMTS. It can reduce time
required for Ues to read SIBs.
GSM/UMTS Core RIM : LTE Core Core Network
RAN Information
Exchanging Support
Both GSM/UMTS
SGSN MME SGSN MME and LTE core
network support R9
RAN information RIM procedure
RRCConnectionRelease(
RAN information request Frequency and target
cell system information)
BSC/RNC eNodeB
Terminal Support
Terminal support R9
redirection with SIB (System
Info Block)
GSM/UMTS LTE
eNodeB saves UTRAN/GERAN neighbor cell
system information (RIM: MME&RNC) Latency Reduced
eNodeB receives command of CSFB from MME Saving 1s for UMTS compare with R8 CSFB

Saving 2s for GSM compare with R8 CSFB

eNodeB selects Redirection to CSFB based on capability and strategy

eNodeB fills out target frequency and related neighbor cell information in
RRCConnectionRelease messageU: 1 Freq, 16 Cell ID; G: 1 Freq Group, 32 Cell ID)
Index
CS Fallback
VoLTE
CA (Carrier Aggregation)
LTE Voice Solution Options

IMS/SR-VCC: Voice over IMS over LTE; IMS only*, 2012

handover & roaming to 2G/3G is supported IMS-SRVCC, 2013
Voice & Data
on LTE
OTT Mode: To rely on OTT applications for Not standardized
voice service offering Project specific

LTE Voice
Solution
CS Fallback: UE is attached on LTE, and
fallback to 2G/3G for voice calls (MTC and
MOC)
Data on LTE
Voice on 2G/3G CS
SVLTE (Dual Standby): Dual
simultaneously radio access running on
the same UE allowing data on LTE and
voice on 2G/3G CS in parallel

SRVCC: Single Radio Voice Call Continuity

SVLTE: Simultaneous Voice and LTE
VoLTE Introduction
Voice services that are set up between UEs and the IMS and carried
WHAT in the PS domain.
In the initial phase of LTE network deployment when the IMS is not
deployed, CS fallback is a transitional solution to provide voice services for
WHY LTE users. After the IMS is deployed, VoLTE is used as the ultimate
solution for voice services.
CSFB VoLTE

Benefits

Higher Lower Better

spectral Access Voice
efficiency delay Quality

IMS: IP Multimedia Subsystem

CSFB and VoLTE Comparison

Deployment
Solution Feature Advantage Disadvantage
Suggestion

The IMS and LTE

networks provide voice Low latency
services. The handover High Voice Quality The IMS network Large-scale LTE
VoLTE
between the LTE network HD voice/video. needs to be deployed. coverage
and 2G/3G network is E2E QoS
supported.

UEs attach to the LTE

Slight change is required Initial phase of
network. When a UE The call delay is long.
on live networks. the LTE network
CSFB initiates or receives a User experience is
New NEs do not need to (transition
call, the UE falls back to affected.
be deployed. solution)
the CS network.
Best Voice Experience - VoLTE Based on IMS

MME IMS

eRAN
IP Network

S-GW P-GW CS or VoIP

user
VoIP
Service

Seamless Coverage High Capacity Best Experience

LTE Voice Coverage Improvement 400 VoIP Users per Cell Average MOS > 4.0

LTE
G/U
TTI Bundling Robust Header Compression AMR-WB
RLC Segmentation Semi-Persistent Scheduling E2E QoS Control
Frequency Selective Scheduling Delay Based Scheduling Discontinuous Reception
VoLTE : Voice session setup process

1. In the RRC connection setup procedure, a radio connection is

set up between a UE and an eNodeB so that the UE can send
service requests and data packets to upper-layer NEs.

2. In the EPS bearer setup (QCI 5) procedure, a radio bearer with

a QCI of 5 is set up for signaling between the UE and the IMS.

3. In the negotiation phase, the UE and IMS negotiate with each

other in compliance with the Session Initiation Protocol (SIP).
The negotiation covers the information about the called UE,
speech codec scheme, IP address, and port number.

4. In the EPS bearer establishment (QCI 1) procedure, a radio

bearer with a QCI of 1 is setup to carry voice packets.
Voice Continuity Solution - SRVCC

When UE moving from

LTE coverage to
GSM/UMTS with voice Core network requirement:
service 1. IMS deployed
2. Enhanced MSC deployed

Principle
IMS supports voice and data service of LTE
subscribers
SRVCC to UTRAN
SRVCC for LTE VoIP to GSM/UMTS CS calls if
VoIP is not supported by G/U network
Benefit
LTE network can support both voice and data
services with IMS solution
To ensure service continuity, support handover
from LTE to 2G/3G
Future oriented Convergent solution

Single radio voice call continuity (SRVCC)

SRVCC Definition

Calls are set up in the LTE over VoIP / VoIMS.

When a subscriber moves to an area uncovered by the LTE network while
holding a call, the call is switched to the CS domain. SRVCC interprets a
switchover process.

SRVCC solution: The media handover

point is a peer device. Such as a peer UE.
E2E signaling and bearer are re-established.
The IMS network sends the updated media
information to the remote network, and a
session is interrupted around 1s.
SRVCC Continue VoLTE Service in UMTS Networks

EMSC
Uu Iu-cs/A

BS SGSN Sv
Iu/Gb MME HSS Voice & PS service continuity
Gn/S3 S6a
SRVCC based on inter-RAT mobility
IMS CN
S1-C S11 PS service handover to 3G networks (Optional)
Uu S1-U SGi

eNB SAE-GW
UE

Core Network Support Terminal Support

Sv interface between MME and 3GPP SRVCC UE is needed to perform
MSC-S enhanced for SRVCC. SRVCC, IPhone6,Note3 have
EMSC MME supported

Note: SRVCC is triggered by coverage, service, distance, load etc.

Solution Introduction - SRVCC Trigger Scenario & PS Service Continuity

SRVCC Trigger Scenario PS Service Continuity

Coverage Caused UE & UTRAN support CS+PS SRVCC.
Trigger in EUTRAN cell edge with B1 event. MME initiate the HO prepare procedure of voice
bearer and PS bearer to MSC and SGSN
Load Caused respectively.
EUTRAN is high load, and UTRAN neighbor cell is low load.
UE or UTRAN only support CS only SRVCC.
Service Caused MME only initiate the HO prepare procedure to
eNB will trigger SRVCC procedure once UE setup QCI1. MSC for voice bearer.

CSFB caused PS service will resume in UTRAN by RAU (Routing

This scenario is always used for VoIP emergency call with location Area Update) procedure.
service but LTE doesnt support LCS. In this scenario, in order to
satisfy LCS request, MME would send CSFB indication to eNB.
Because UE has already have set up QCI1 bearer, eNB will trigger
SRVCC procedure, and voice service will HO to CS to keep the
continuity.

3GPP 23.216
Performance Improvement Methods on LTE VoIP

IP head compression-RoHC
Semi-persistent scheduling
Capacity
+

eNB
RRC

PDCP-RoHC

RLC-UM Mode Good voice quality based on

Experience QCI=1 in QoS management
MAC
SPS Scheduling + Smart Pre-allocation
Smart Preallocation

PHY
TTI Bundling

Coverage
+ TTI bundling
RoHC
VoLTE Coverage Related Features - RLC Segmentation

High codec of 23.85kbps creates big

packets, which can not be transmitted at
D0 (~1000 bit) cell edge in uplink for the limitation of RB,
path loss and terminal power.

With intelligent Segment, a larger voice

packet can fragment into suitable smaller
size according to signal quality and delay
With RLC Seg. requirements of voice, obtaining the
D0 (~1000 bit)
coverage gain, while avoiding the voice
delay and loss.
..

1~2dB With Huawei intelligent RLC

Delay Based segment ,we can get 1~2 dB coverage
gain and with no terminal requirement.
VoLTE Enhanced Feature - TTI Bundling (Optional)

No RLC Segmentation, no TTI Bundling Packet size can be transmitted

D0 (~1000 bit)
vs. RLC Segmentation enable first In Cell edge
scenario.
RLC Segmentation and HARQ Retransmission
D1 D2 D3 D4 D1 D2 D3 D4

20 TTI TTI Bundling transmit same packets 4 times

in one scheduling to expand coverage by
increase uplink transmission reliability.
TTI Bundling

VoIP TTI Bundling with RLC Segmentation

D1 D1 D1 D1 D2 D2 D2 D2 D3 D3 D3 D3 D4 D4 D4 D4
TTI Bundling is only enabled at cell edge to
save TTIs, eNodeB makes the decision by UE
TTI_B & ROHC off SINR.
TTI_B & ROHC on
VoLTE Enhanced Feature - RoHC (Optional)

IP Header Voice Packtes

IP Header Voice Packtes
40~60 Bytes 32~60 Bytes
40~60 Bytes 32~60 Bytes

RTP header
UDP header
RoHC Voice Packtes RoHC Voice Packtes
1 Byte 32~60 Bytes IP header 1 Byte 32~60 Bytes
RoHC header
Payload Payload

Decompression Compression
Compression Original packet Compressed packet Decompression

As voice packets often have same source and

destination, RoHC can achieve compression to
as small as 1 byte.
TTI Bundling & RoHC together bring 3dB
Smaller header size on air interface expanded uplink gain thus increase 20% cell coverage.
uplink cell coverage and increase capacity.
VoLTE Enhanced Feature - Semi-Persistent Scheduling (Optional)

Scheduling grant

Voice packet SPS Simulation Result

(Unit:Mbps)
13.88
12.86
PDCCH
13.69 Gain>10
12.72 10.81
%
9.22
PUSCH 9.97
7.7
6.46
SPS Enable 7.22

4.55
PDCCH 3.25

PUSCH 40 80 120 160 200 240

23.85K DS 23.85K SPS

SPS period
Voice packet be sent periodically in a fixed period (20ms);
UE receive the regular RB resource in a fixed period with no
scheduling grant in PDCCH. (Save PDCCH, Cap increase)
SPS need UE support.
According to Huawei simulation , in data
& voice mixed scenario , with the increase
of voice user , the gain will be more and
more.
Index
CS Fallback
VoLTE
CA (Carrier Aggregation)
Carrier Aggregation (CA) Introduction

3rd Generation Partnership Project (3GPP) requires LTE-Advanced networks to provide a downlink peak data rate of 1 Gbit/s. However, radio
spectrum resources are so scarce that in most cases an operator owns only non-adjacent chunks of the spectrum. Due to the limited bandwidth
of a single chunk of the spectrum, the 1 Gbit/s data rate requirement is hard to meet.

To deal with this situation, 3GPP specifications Release 10 introduced carrier aggregation (CA) to LTE-Advanced networks, allowing
aggregation of contiguous or non-contiguous carriers. The aggregated carriers are called component carriers (CCs). CA achieves wider
bandwidths (a maximum of 100 MHz).
Carrier Aggregation (CA) Feature Benefits

CA achieves wider bandwidth and allows a CA-capable UE to use idle resource blocks (RBs) on
non-contiguous CCs. With CA enabled, a single UE can reach higher uplink and downlink peak
data rates.

Maximized
Resource
Utilization

Efficient Utilization
of Non-contiguous
Spectrum Chunks

Better User
Experience
Carrier Aggregation (CA) Usage Scenarios
Carrier Aggregation (CA) Inter - eNodeB CA (FDD)

1. Based on inter-BBU interconnection

2. Based on relaxed backhaul

Carrier Aggregation (CA) Configuration Mode
CA Group-Based Configuration CA Frequency-Based Configuration
Create a CA group, add cells to the group, and Add candidate PCCs and SCCs and CA
then set Pcell and Scell attributes for the cells attributes for them

This mode requires that cells be configured into a CA This mode requires that PCC and SCC attributes be set
group, only the cells in the group can be aggregated. for E-UTRAN frequencies, only the cells on these
frequencies can be aggregated.
Carrier Aggregation (CA) Principle Concepts
PCell
A primary serving cell (PCell) is the cell on which a CA UE camps. In the PCell, the CA UE works in the same way as it does in a 3GPP
Release 8 or Release 9 cell. The physical uplink control channel (PUCCH) of the UE exists only in the PCell.

SCell
A secondary serving cell (SCell) is a cell that works at a different frequency from the PCell. The eNodeB configures an SCell for a CA
UE through an RRC Connection Reconfiguration message. An SCell provides the CA UE with more radio resources. The CA UE can
have only downlink SCells or both downlink and uplink SCells.

CC
Component carriers (CCs) are the carriers that are aggregated for a CA UE.

PCC
The primary component carrier (PCC) is the carrier of the PCell.

SCC
A secondary component carrier (SCC) is the carrier of an SCell.

PCC Anchoring
During PCC anchoring, the eNodeB selects a high-priority cell as the PCell for the UE.

CA Group
A CA group is a logical set of cells. In CA-group-based configuration mode, only the cells in a CA group can be carrier-aggregated for a CA UE. It is
recommended that different Pcell priorities be assigned to different cells within a CA group. The eNodeB selects a PCell for a CA UE in descending order of
PCell priority. If the cell that the UE initially accesses has the highest PCell priority, the UE stays in the cell.
Carrier Aggregation (CA) Principle Concepts SCC Status

PDSCH
PDCCH
3 Status for CA UEs: SCC SCC
Single CC: same as a non-CA UE
PCC PCC
SCC_Activated
SCC_Deactivated ActivationDeactivation

Activation (by traffic)

RLC buffer length > max (RLC data rate * ActiveBufferDelayThd,
ActiveBufferLenThd)
Delay of the first RLC PDU > ActiveBufferDelayThd
Deactivate (by traffic)

Note: RLC data rate DeactiveThroughputThd

Only eNodeBs can deactivate or remove SCells (SCells can be RLC buffer length DeactiveBufferLenThd
deactivated, but PCells cannot). Deactivate (by CQI)
CQI SccDeactCqiThd
Carrier Aggregation (CA) Carrier Management : PCC Anchoring
During carrier management an eNodeB selects an appropriate Pcell and Scell for a CA UEs. These procedures are
called PCC anchoring and Scell selection.
PCC anchoring occurs only when a CA UE initially accesses a network. The
Pcell of a UE cannot be deactivated or removed It changes only at handover
Carrier Aggregation (CA) Carrier Management : Scell Selection
An eNodeB determines an Scell for a CA UE by Scell configuration, which is followed by Scell activation,
change, deactivation and removal procedures when their respective triggering conditions are met. After
the Scell is configured and activated, data transmission for the UE occurs in the Pcell and Scell
simultaneously.

Scell
Unconfigured
To prioritize certain frequencies as SCCs, an operator can set high SCell or SCC priorities so that the
eNodeB will select the highest-priority cell or carrier as an SCell or SCC for the UE.
Removal Configuration
eNodeB starts SCell configuration for a CA UE if all the following conditions are met:
The RRC connection of the UE has been set up in any of the following scenarios:
Activation Initial access (when PCC anchoring has finished)
RRC connection reestablishment
An incoming handover (if the UE is now served by only one carrier)
Scell Scell Scell Signaling radio bearer 2 (SRB2) and the default data radio bearer (DRB) have been set up.
Deactivated Configured Activated
No SCell has been configured for the UE.
The UE is not running an emergency call.

Deactivation The triggering of the SCell configuration procedure is also dependent on two factors:
Setting of CaTrafficTriggerSwitch
AMBR-based control over the number of UEs configured with SCells
Change

Scell
Change
CA Optimization - CA Proportion & Throughput Optimization

CA Proportion, Throughput Optimization

Coverage Threshold Traffic Threshold Algorithm Threshold Ping-Pong handover PCI Collision

Increase the A2 threshold Reduce the traffic activate Adjust the SCC Configuration Check the network handover Check the PCI collision and

and SCC Configuration threshold to improve the CA Interval to increase the CA activation threshold to reduce the ping- confusion, reduce the

Interval, to increase the CA activation ratio. ratio. pong handover events. probability of unable to

proportion. Reduce the traffic activation Set the PCC anchor configuration Resolve the ping-pong configure the CA due to PCI

Decrease the A4 threshold buffer threshold to improve the according to the field condition to handover issue due to the weak collision & confusion.

to make the UE enter CA CA activation ratio. increase the CA throughput. coverage, non pilot coverage,
state be quicker. Set the Differentiated Scheduling etc.
to increase the CA Throughput.
CA Optimization - Typical issues
The SCC is not able to be
configured after A4 reported due
to SCC PCI collision.
eNodeB did not configure SCC for
the UE due to inter frequency
neighbor cell missing.
SCC not able to be configured due
to UE version.
SCC measurement report not send
due to wrong parameters
configuration.
Scell is not
configured
issue
Enable the DRX, the CA
throughput is lower than
summary of two frequency
throughput at the near
point(SINR=20dB). After enable
the DRX Receive DTX Process
Switch, then issue resolved
UE compatibility issues
Throughput is
too low after
Scell activation
issue.
UE not able to make the
intra/inter frequency handover
due to PCC PCI collision. After
parameter optimization
CaUeChoseMode=ANR_UE_CAP
, then issue resolved.
UE compatibility issues.
DT KPI issue
Copyright2012 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product
portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive
statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time
without notice.
 CSFB and SRVCC Strategy
CSFB VoLTE and SRVCC
LTE2100
UE moving out of
LTE LTE 2100
2100/10MH
CSFB z
Reselection Priority=6
PSHO/ PSHO/
Fast Return Redirection Redire
CSFB Fast return
ction
U2100

SRVCC/PS HO U2100/5MHz
/Redirection Priority=4

U850 F1 SRVCC

U850 F2
UTRAN
850/15MHz
U850 F3 Priority=3

Idle Mode Reselection: CSFB:

Need SRVCC Steering to UTRAN feature to L2100 U2100, U850 F1/F2
separate SRVCC only to U850 F1, and keep current
L2U PS HO/Redirection:
CSFB strategy, and Normal PS to U2100 /U850 L2100 U850 F1/F2 by PS HO/Redirection
F1/F2. L2100 U2100 by PS HO/Redirection
U2100 L2100 by PS Redirection
L2100 U2100 by Blind HO or Redirection
U2100 L2100 by Fast Return
SRVCC:
L2100 U850 F1 by SRVCC
U850 F1/F2/F3 L2100 by Reselection