Flash CSFB:

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it sends an
RRC Connection Release message to release the UE. The message contains information about a target
UTRAN frequency, as well as one or more physical cell identities and their associated system
information. In this way
the UE can quickly access the target UTRAN without The need to perform the procedure for acquiring
system information of the target UTRAN cell. Then, the UE can directly initiate a CS service in the
UTRAN cell.

NOTE
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP
Release 9 or later.

CSFB Procedure for Mobile-originated Calls

This section describes the procedure for flash CSFB to UTRAN for mobile-originated calls, as
Shown in Figure 3-5.
ERAN
CS Fallback Feature Parameter Description 3 End-to-End Procedures for CSFB
Issue Draft A (2013-01-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
16
Figure 3-5 Flash CSFB to UTRAN for mobile-originated calls
The procedure is described as follows:
1. The UE sends the MME an NAS message Extended Service Request to initiate a CS service.
2. The MME sends an S1-AP Request message to instruct the eNodeB to initiate a CSFB
Procedure. If the MME supports the LAI-related feature, the MME also delivers the LAI
to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section Choosing Between a
Blind Handover and a Measurement-based Handover.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a
redirection. The message contains information about a target UTRAN frequency, as well
as one or more physical cell identities and their associated system information. Then, the
eNodeB initiates an S1 UE context release procedure.
NOTE
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details,
see chapter 4 CSFB at the eNodeB.
The system information of the target cell is acquired during the RIM procedure. For details, see
section 3.1.6 RAN Information Management Procedure.
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in the
target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.
CSFB Procedure for Mobile-terminated Calls
In a mobile-terminated call, the MSC sends a Paging Request message from the CS domain to
the MME over the SGs interface. Then, the MME or the eNodeB initiates a paging procedure
eRAN
CS Fallback Feature Parameter Description 3 End-to-End Procedures for CSFB
Issue Draft A (2013-01-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
17
for the UE, as shown in Figure 3-3. The subsequent steps are the same as the steps in the
procedure for flash CSFB to UTRAN for mobile-originated calls.
3.1.3 CSFB Procedure for SMS
SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS
messages. During interworking with the UTRAN, SMS messages are exchanged between the
MME and the MSC over the SGs interface. Because a UE does not require fallback to the
UTRAN to perform an SMS service, the SMS over SGs function can be used in a place covered
only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this document.
For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
3.1.4 CSFB Procedure for Emergency Calls
The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal
mobile-originated voice service. The UE sends an RRC Connection Request message over the
Uu interface or the MME sends an Initial Context Setup Request or UE Context Modification
Request message, which contains an IE to inform the eNodeB of the service type. Emergency
calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in
the handover restriction list when selecting the target cell. The eNodeB sends the RNC a
handover request with the IE CSFB high priority in the IE Source to Target Transparent
Container. This request informs the RNC that a CSFB procedure is required for an emergency
call. Upon receiving the information, the RNC preferentially processes this call when using
related algorithms such as admission control.
If redirection is used for CSFB for emergency calls, the RRC Connection Request message that
the UE sends when accessing the UTRAN contains the indication of an emergency call. The
UTRAN will treat this call as a common CS emergency call.
For details about admission and preemption of emergency calls, see Emergency Call Feature
Parameter Description.
3.1.5 CSFB Procedure for LCS
After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU
procedure to inform the UE of the LCS capability of the EPS. If the EPS does not support LCS,
the UE falls back to the UTRAN to initiate LCS under the control of the EPS. The CSFB
procedure is the same as the procedure for CSFB to UTRAN for mobile-originated calls.
If the UTRAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the MSC
sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs the eNodeB
to perform CSFB for the UE. The CSFB procedure is the same as the procedure for CSFB to
UTRAN for mobile-terminated calls. The UE performs the LCS service after the fallback to the
UTRAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0 and