LTE eRAN15.1 CSFB

LTE eRAN15.
1 CS Fallback
Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN15.1 CS Fallback
 Over-the-top (OTT) mode (for instance, Skype is used to provide voice services): LTE
networks are all-IP-based, feature high bandwidth and low delay, and provide always-
online user experience. These characteristics are very beneficial to OTT development
with minimum obstacles for OTT voice services. Nevertheless, voice services are and
will still be one of the main revenue sources for mobile operators for a long time.
Allowing voice services to be fully provided by OTT applications remains as an
aggressive move, which does not gain much support from the telecommunications
industry.
 SVLTE (Simultaneous Voice and LTE) serves as a transition solution for CDMA
operators before IMS deployment. There is a commercial deployment case in North
America, with minimal network reconstruction involved. However, the difficulties of this
solution lie with terminals as it requires custom-made terminals, of which the battery
power consumption is high. Besides, these terminals are prone to issues during
international roaming.
 CSFB refers to the scenario where users attach to the LTE network, and the eNodeB
instructs users to fall back to a 2G network when users initiate CS service requests.
CSFB deployment requires shorter time and allows the utilization of existing 2G
networks. These make CSFB serve as a better transition voice solution.
 The IMS-based VoLTE solution is an ideal long-term solution for voice, but it requires
large-scale deployment of LTE sites and IMS deployment across the entire network.
 SGLTE: Simultaneous (voice over) GSM and LTE



 The SGs interface supports SMS services. This function is called SMS over SGs.

 TAU is short for tracking area update, and LAU is short for location area update.

 Improper TA-LA planning is prone to the following issues:

 During CSFB, if the LAC of the fallback location does not match the LAC for
the combined attach, the UE is required to perform an LAU within the
procedure, which increases fallback delay.
 If inter-MSC-pool processing is involved during the CSFB for a mobile-
terminated call, the call may fail if mobile terminated roaming forwarding
(MTRF) is not deployed.

 When VoLTE is deployed:

 If the IMS does not support emergency calls, UEs fall back to a CS network to
complete the emergency calls.
 Certain numbers are configured on the PCSCF. The IMS will signal the UE to
fall back to a CS network when these numbers are called.
 When the VoLTE signaling is abnormal, for example, when certain timers
expire, UEs decide to fall back to a CS network.
 Certain UEs may fall back to a CS network when the signal strength is weak.

 In the two scenarios, if the LAC of the coverage area for the fallback is different from
the LAC registered during attach to the 4G network, the UE needs to initiate an LAU,
which increases the CSFB delay.



Combined attach uses NAS messages, which are transparent to the eNodeB. A CSFB
UE initiates a combined attach procedure in the LTE network. (Whether a UE initiates a
combined attach is dependent on the UE itself. For example, a single-card dual-standby
UE will not initiate a combined attach request).
1. The UE initiates an attach request by sending an Attach Request message to the
MME, with the Attach Type parameter indicating a combined EPS/IMSI attach
procedure.
2. The MME identifies the combined attach request by Attach Type, and then acquires
the VLR number based on the TAI reported by the UE (TAI-LAI mapping and LAI-
VLR relationship have been configured in the MME). Upon receiving subscriber data
from the HSS, the MME sends an SGsAP-LOCATION-UPDATE-REQUEST
message to the selected MSC/VLR. The message includes the new LAI, IMSI, MME
name (MME domain name) and parameters such as Location Update Type.
3. The VLR stores the MME information, and creates an SGs association with the
MME.
4. A location update in the HLR is initiated based on the subscriber information in the
VLR.

5. The VLR returns an SGsAP-LOCATION-UPDATE-ACCEPT message to the MME

(the message includes LAI and TMSI if the VLR supports TMSI reallocation, or LAI
and IMSI if the VLR does not support TMSI reallocation), which marks the completion
of the EPS/IMSI attach. The MME sends an Attach Accept message to the UE. The
message includes the LAI and VLR TMSI, which indicates a successful CS domain
attach of the UE.
6. If TMSI reallocation is supported, VLR will receive an SGsAP-TMSI-REALLOCATION-
COMPLETE message from the MME after sending the SGsAP-LOCATION-UPDATE-
ACCEPT message.

 If a UE does not perform periodic TAU, the MME will detach this UE implicitly and
delete the association with the MSC.
 In this case, the MSC will page the UE over the Iu or A interface.

 A detach procedure can be initiated by a UE in the EPS. During the procedure, the MME sends
an IMSI Detach Indication message to the MSC over the SGs interface, instructing the VLR to
delete the SGs association of the UE. After IMSI detach, the EPS-attached UE is not allowed to
use CS services.
1. The MME sends an SGsAP-IMSI-DETACH-INDICATION message (including the IMSI,

MME name, IMSI Detach from non-EPS service type) or an SGsAP-EPS-DETACH-
INDICATION message (including the IMSI, MME name, and IMSI Detach from EPS service
type) to the VLR. Upon receiving the message, the VLR checks for the existence of the UE
SGs association, and then sends an SGsAP-IMSI-DETACH-ACK or SGsAP-EPS-DETACH-
ACK message directly without any other processing. If the VLR finds that the MME name
included in the SGsAP-IMSI-DETACH-INDICATION or SGsAP-EPS-DETACH-INDICATION
message is different from the MME name stored in the VLR, the VLR neither responds with
an ACK message nor performs other processing.
2. The VLR removes the UE-related SGs association upon receiving the SGsAP-EPS-
DETACH-INDICATION message. The VLR removes the UE-related SGs association and at
the same time changes UE status to Detach upon receiving the SGsAP-IMSI-DETACH-
INDICATION message.
3. The VLR sends an SGsAP-IMSI-DETACH-ACK or SGsAP-EPS-DETACH-ACK message to

the MME.


 The UE initiates a combined TA/LA update when it moves to a new location. During
the update over the SGs interface, authentication and encryption procedures are not
performed by the VLR. UE authentication is performed by the MME during the access
procedure.
1. The UE sends a TAU Request message (including Update Type and Mobile
Station Classmark 2) to the MME. The Update Type IE indicates a combined
Tracking Area/Location Area Update Request, or a combined Tracking Area/IMSI-
Associated Location Area Update Request (which is initiated if the UE did not
perform a combined attach earlier).
2. The MME decides to initiate a location update with the VLR (TAI-LAI mapping and
LAI-VLR relationship are configured in the MME), and then sends an SGsAP-
LOCATION-UPDATE-REQUEST message to the VLR. The message includes
parameters such as the new LAI, IMSI, MME address, and Location Update Type,
and the EPS location update type indicates a normal location update.
3. The VLR creates or updates the SGs association with the MME, and initiates
location update in the HLR based on the subscriber information in the VLR.

4. The VLR returns an SGsAP-LOCATION-UPDATE-ACCEPT message to the MME.

The message includes the LAI and TMSI if the VLR supports TMSI reallocation, or
the LAI and IMSI if the VLR does not support TMSI reallocation.
5. The MME sends a TAU Accept message to the UE. The message includes the LAI
and IMSI/TMSI. The LAI indicates that the UE is in the IMSI-attach state.
6. If the TAU Accept message includes TMSI, the MME sends an SGsAP-TMSI-
REALLOCATION-COMPLETE message to the VLR after receiving a TAU
Complete message from the UE.


 Answer to question 1: The UE will not perform an LAU. An LAU needs to be

performed only after the UE already falls back to the 2G or 3G network.
 Answer to question 2: After a UE on the 4G network reselects a 2G network, the MSC
does not send paging messages intended for the UE to the MME, and therefore the
UE will not receive paging messages from the MME. The MSC sends paging
messages intended for the UE to the MME after the UE camps on the 4G network
again. In this scenario, the UE will receive paging messages from the MME.
 Answer to question 3: LAI determined according to the mapping table.

 Upon receiving a CSFB instruction, the eNodeB releases the UE using an RRC Connection
Release message (with information about a target GERAN frequency group). Upon completing
GERAN network searching, the UE reads system information of the GERAN cell, initiates an
initial access procedure and a CS service request. This UE is considered as a new UE for
GERAN.
1. The UE initiates a CS service by sending the MME an Extended Service Request message
(a NAS message).
2. The MME instructs the eNodeB to start a CSFB procedure by sending an S1-AP Request
message to the eNodeB. The MME sends LAI information to the eNodeB if the MME
supports the LAI feature.
3. The eNodeB decides whether to trigger a blind handover based on the UE capability,
parameter configurations, and handover algorithm.
4. The eNodeB sends an RRC Connection Release message (including 2G frequency band
information) to the UE, instructing the UE to perform a redirection. The eNodeB then
initiates an S1 UE context release procedure.
5. The UE initiates an LA update, a combined RA/LA update, or LA and RA updates
simultaneously in the target cell.
6. If the GERAN or UE does not support Dual-Transmission Mode (DTM), that is, concurrent
CS and PS services, the PS service will be suspended.
7. The UE initiates a CS service setup procedure in the GERAN cell.



 The MME sends Suspend Notification for each bearer if there are multiple bearers.

 An RRC_IDLE UE needs to transfer to the RRC_CONNECTED state through an RRC

connection setup procedure with the eNodeB before the CSFB procedure can be
started. For an RRC_CONNECTED UE, the CSFB procedure can be immediately
started.

 Upon receiving an Initial Address Message (IAM), the MSC performs destination node
(called node) analysis and acquires the status of the called UE.
 The mobile-terminated CS call procedure is similar to the mobile-originated CS call

procedure, where both RRC_IDLE and RRC_CONNECTED scenarios exist. The
main difference lies in the PS service procedure over the Uu interface.

1. Upon receiving an incoming IAM message, the MSC sends an GsAP-PAGING-

REQUEST message (including the IMSI, TMSI, Service Indicator, CLI, and LAC) to
the MME based on the SGs association and MME information.
2. The MME sends a paging message to the eNodeB, and the eNodeB starts a paging
procedure over the air interface.
3. The UE establishes an RRC connection and sends an Extended Service Request
message to the MME.
4. The MME sends an SGs Service Request message to the MSC. The message
contains an indication that the UE was in idle mode. Upon receiving the SGs Service
Request message, the MCS stops retransmitting the Paging message over the SGs
interface. To prevent the calling party from experiencing a potentially long period of
silence, the MSC informs the calling party that the call is in progress.
5. The MME sends an Initial UE Context Setup message with an CSFB Indicator to the
eNodeB, instructing the eNodeB to enable the UE to fall back to UTRAN/GERAN.

6. The UE performs a redirection from E-UTRAN to UTRAN/GERAN.

7. With connections established over the air interface and A/Iu-CS interface, the UE
replies a paging response to the MSC. The RNC must be able to process the UE
paging response although the paging request was not sent by the RNC. If the
location area information included in the paging response does not match the
information stored in the VLR, the SGs association is set to be NULL after VLR
authentication.
8. Upon receiving the paging response from the UE, the MSC stops the paging
response timer and proceeds with CS connection setup. The scenario described
above is a common scenario. There is another scenario with roaming retry, which
was triggered when the VMSC accessed by the UE is different with the VMSC
sending the paging message. A location area update and a second SRI procedure
are added in the call setup flow, which increases call processing delay.

 The MME starts timer T3413 after sending the first paging message, and the paging
message will be retransmitted if there is no paging response from the UE after
expiration of T3413. The number of paging retransmissions is set by N3413. The
strategy used in each retransmission could be set dynamically. The MME replies the
SGW with a Downlink Data Notification Reject message if no paging response is
received after all retransmissions. Then, the SGW deletes messages in the buffer. For
the a Service Request procedure initiated by downlink signaling, the MME stores the
signaling messages in its buffer, and sends the messages to the UE after the paging
is completed successfully.


 The mobile-terminated CS call procedure is similar to the mobile-originated CS call

procedure. The main difference lies in the PS service procedure over the Uu interface.

 IdleCsfbRedirectOptSwitch: If this option is selected and the preferred CSFB policy

for RRC_IDLE UEs is redirection, the eNodeB no longer activates security mode or
performs RRC connection reconfiguration but directly sends a redirection message,
which shortens the delay.


 After a UE is powered on, the UE first checks whether there is a SIM card. If there is a
SIM card, the UE searches for a network and initiates a registration process. The UE
selects a proper network for registration and authentication based on the priority of the
SIM card until the registration succeeds or fails. The SIM card is involved in
authentication. The RF module of the UE works normally no matter whether a SIM
card is available. When the RF module of the UE works normally, the UE can detect
signals from the surrounding network and initiate calls at any time on the network to
which the UE is connected. However, to make a call on the network, network
operator's requirements must be met. The SIM card only enables the UE to identify
the base station but does not function as the communication module.
 Although the network search is successful, the UE without a SIM card cannot access
the network. Just like a door card, without which you cannot enter the room although
you have found the where the room is. Because emergency calls have a very high
priority, operators have few restrictions on emergency calls and do not require UEs
making emergency calls to register with the network. Therefore, a SIM card is not
required for the mutual authentication between the UE and the network, and
emergency numbers can be dialed without a SIM card.


Special handling of emergency calls in the CSFB procedure:

 Step 1a (Extended Service Request): the UE includes "mobile originating CS fallback
emergency call" or "1xCS fallback emergency call" as the value of the IE Service type
in Extended Service Request.
 Step 1 b (S1-AP Message): the MME includes "CS Fallback High Priority" as the
value of the IE CS Fallback Indicator in the S1 message INITIAL CONTEXT SETUP
REQUEST or UE CONTEXT MODIFICATION REQUEST.

 To save costs, an operator may deploy only one MSC in the MSC pool connected to
the MME over the SGs interface. After a UE falls back to the 2G network and initiates
a CM service request with the IMSI contained, the new MSC (in the MSC pool)
designated for the UE may not support Mobile Terminating Roaming Forwarding
(MTRF) and Mobile Terminating Roaming Retry (MTRR). As a result, the mobile-
terminated call fails.
 The fallback delay for a called UE in the RRC_CONNECTED state is shorter than that
for a called UE in the RRC_IDLE state.
 No.

 The SMS is encapsulated in NAS messages, and therefore the eNodeB is not aware
of the service. In the case of GERAN, the MME communicates with the MSC over the
SGs interface for originating or terminating SMS services. The UE is not required to
fall back for the SMS service, and therefore SMS over SGs services can be carried
out in the areas even with only E-UTRAN coverage.
 This procedure is transparent to the eNodeB.





 In section 5.5.1.1.1 of 3GPP TS 23.401, the procedure conflict between X2-based

handover and CSFB is described as follows:
 If the MME receives a rejection to a UE Context Modification Request
message with a CS Fallback indicator from the eNodeB with an indication that
an X2 handover is in progress, the MME shall resend a UE Context
Modification Request message with CS Fallback indicator to the target
eNodeB when the handover is complete or to the source eNodeB when the
handover is deemed to have failed.
 In section 5.5.1.2.1 of 3GPP TS 23.401, the procedure conflict between S1-based
 If the MME receives a rejection to a UE Context modification Request
message with a CS Fallback indication from the eNodeB with an indication that
an S1 handover is in progress, the MME shall resend a UE Context
eNodeB when either the handover is complete or to the source eNodeB when
the handover is deemed to have failed if the MME is still the serving MME.



 R8 PS Redirection: After receiving a CS Fallback Indicator, the eNodeB sends an

RRC Connection Release message containing frequency information about the target
UTRAN to the UE. Based on the received frequency information, the UE searches for
a UTRAN cell, obtains the system information of the UTRAN cell, and initiates initial
access and CS services.
 R8 PS Redirection (Flash CSFB): After receiving a CS Fallback Indicator, the eNodeB
sends an RRC Connection Release message containing information about a target
UTRAN frequency as well as system information about multiple target cells to the UE.
Based on the received frequency information, the UE searches for a UTRAN cell. As
the UE obtains system information about the target cell, the UE initiates initial access
and CS services in the target cell, thereby reducing voice delay.
 PS Handover: The UE is handed over to the UMTS network through the PS handover
procedure between the eNodeB and the UMTS network. After the handover, the UE
initiates CS services in the target cell.

 CSFB to UTRAN: This feature is controlled by the UtranCsfbSwitch option of cell-

level parameter CELLALGOSWITCH.HoAllowedSwitch.
 Flash CSFB to UTRAN: This feature is controlled by the UtranFlashCsfbSwitch
option of cell-level parameter CELLALGOSWITCH.HoAllowedSwitch.

 The settings of the following switches can be changed by running the MOD
CELLALGOSWITCH command.
 UtranCsfbSwitch
 Meaning: Indicates whether to enable CSFB for UTRAN.
 GUI value range: On, Off
 Actual value range: On, Off
 UtranFlashCsfbSwitch
 Meaning: This switch does not take effect if UtranCsfbSwitch is off. When the
UtranFlashCsfbSwitch is on, flash CSFB to UTRAN is enabled, and UTRAN
system information is carried during redirection. When the
UtranFlashCsfbSwitch is off, flash CSFB to UTRAN is disabled.

 If the BlindHoSwitch options are deselected and the UE supports measurements,

measurement-based handling is used.

 The setting of the following switch can be changed by running the MOD
ENODEBALGOSWITCH command.
 BlindHoSwitch (eNodeB-level)
 Meaning: This option specifies whether to enable blind handover for CSFB.
Blind handover for CSFB is enabled only if this option is selected. A blind
handover for CSFB can be triggered only if both this option and the
BlindHoSwitch option of the HoModeSwitch parameter in the
CELLHOPARACFG MO are selected.
CELLHOPARACFG command.
 BlindHoSwitch (Cell-level)
Blind handover for CSFB is enabled only if this option is selected. A blind
ENodeBAlgoSwitch MO are selected.



 ConnFreqPriority
 Meaning: Indicates the frequency priority based on which the eNodeB selects
a target frequency for blind redirection or contains a frequency in a
measurement configuration. If a blind redirection is triggered and the target
neighboring cell is not specified, the eNodeB selects a target frequency based
on this priority. If a measurement configuration is to be delivered, the eNodeB
preferentially delivers a frequency with the highest priority. If this priority is set
to 0 for a frequency, this frequency is not selected as the target frequency for a
blind redirection. A larger value indicates a higher priority.
 GUI value range: 0 to 8
 Actual value range: 0 to 8
 The setting of this parameter can be changed by running the MOD UTRANNFREQ
command.

 When selecting target frequencies for blind redirection, the eNodeB filters frequencies
based on the RATs supported by the UE and PLMN information corresponding to
frequencies.

 The blind handover priority of a neighboring UTRAN cell is specified by the

UtranNCell.BlindHoPriority parameter. A larger value indicates a higher priority.
 The priority of a neighboring UTRAN frequency is specified by the
UtranNFreq.ConnFreqPriority parameter. A larger value indicates a higher priority.

 BlindHoPriority
 Meaning: Indicates the priority of the neighboring cell during blind handovers. Blind
handover is a process in which the eNodeB hands over a to a specified neighboring cell.
The priority has a positive correlation with the value of this parameter. Note that the value
0 indicates that blind handovers to the neighboring cell are not allowed.
 This parameter can be set by running the ADD/MOD UTRANNCELL command.
 ConnFreqPriority
 Meaning: Indicates the frequency priority based on which the eNodeB selects a target
frequency for blind redirection or contains a frequency in a measurement configuration. If
a blind redirection is triggered and the target neighboring cell is not specified, the eNodeB
selects a target frequency based on this priority. If a measurement configuration is to be
delivered, the eNodeB preferentially delivers a frequency with the highest priority. If this
priority is set to 0 for a frequency, this frequency is not selected as the target frequency
for a blind redirection. A larger value indicates a higher priority.
 This parameter can be set by running the ADD/MOD UTRANNFREQ command.


 The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the

GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
 After the eNodeB receives an initial context setup request with a CS Fallback
Indicator from the MME, the eNodeB does not perform the UE capability query, Uu
security mode command, or RRC connection reconfiguration procedure with dashed
lines in the following figure:
These procedures
are skipped

 IdleCsfbRedirectOptSwitch
 Meaning: If this option is selected and the preferred CSFB policy for UEs in
idle mode is redirection, the eNodeB no longer activates security mode or
performs RRC connection reconfiguration, but sends a redirection message.
 The setting of this switch can be changed by running the MOD
GLOBALPROCSWITCH command.

 The RIM procedure involves the eNodeB, MME, SGSN, eCoordinator and RNC.
Among these NEs, the MME and the SGSN just transfer messages without extracting
information.
 In flash CSFB procedures, the eNodeB obtains the system information (SI) of cells
from RNCs through the RIM procedure.
 In CSFB procedures, the eNodeB obtains the load information of external UTRAN
cells from RNCs through the RIM procedure when the
GlobalProcSwitch.UtranLoadTransChan parameter is set to BASED_ON_RIM, the
eNodeB obtains UTRAN cell load information through the RIM procedure for target
cell selection.

 UtranLoadTransChan
 Meaning: Indicates the UMTS load transmission channel. The eNodeB sends
RAN-INFORMATION-REQUEST PDUs to UTRAN cells to request multiple
reports on the load status of UTRAN cells only when the parameter is set to
BASED_ON_RIM. The function specified by the parameter value
BASED_ON_ECO is temporarily unavailable.
 GUI value range: NULL, BASED_ON_RIM, BASED_ON_ECO
 Actual value range: NULL, BASED_ON_RIM, BASED_ON_ECO
 This parameter can be set by running the MOD GLOBALPROCSWITCH command.
 RimOnEcoSwitch
 Meaning: Indicates whether the RIM procedure is initiated by the eCoordinator.
If this parameter is set to ON, the RIM procedure is initiated by the
eCoordinator. If this parameter is set to OFF, the RIM procedure is initiated by
the core network.
 GUI value range: OFF(Off), ON(On)
 Actual value range: OFF, ON
 This parameter can be set by running the MOD ENODEBALGOSWITCH command.


 R8 PS Redirection: After receiving a CS Fallback Indicator, the eNodeB sends an RRC

Connection Release message containing frequency group information about the target GERAN
to the UE. Based on the received information, the UE searches for a GERAN cell, obtains the
system information of the GERAN cell, and initiates initial access and CS services.
 R8 PS Redirection (Flash CSFB): After receiving a CS Fallback Indicator, the eNodeB sends
an RRC Connection Release message containing information about a target GERAN
frequency as well as system information about multiple candidate target cells to the UE. Based
on the received frequency information, the UE searches for a GERAN cell. As the UE has
obtained system information about the target cell, the UE directly initiates initial access and CS
services in the target cell, thereby reducing voice delay.
 CCO: After receiving a CS Fallback Indicator, the eNodeB sends a
MobilityFromEUTRACommand message containing information about a target GERAN cell to
the UE, and instructs the UE to access the target cell. The UE needs to be synchronized to the
specified cell, obtains system information from the target cell, and accesses the cell to initiate
CS services.
 CCO with NACC: When the LTE-to-GSM RIM procedure is enabled, which indicates that
NACC is enabled, the eNodeB delivers system information of the target cell to the UE after
CCO is triggered. The UE directly initiates access and CS services to the target cell and does
not need to read system information from the target cell, thereby reducing delay.
 PS Handover: The UE is handed over to the GERAN through a PS handover procedure
between the eNodeB and the GERAN network. After the handover, the UE initiates CS
services in the target cell.

 CSFB to GERAN: This feature is controlled by GeranCsfbSwitch of the cell-level

parameter CELLALGOSWITCH.HoAllowedSwitch.
 Flash CSFB to GERAN: This feature is controlled by GeranFlashCsfbSwitch of the
cell-level parameter CELLALGOSWITCH.HoAllowedSwitch. The maximum number
of target GERAN cells to be included in the redirection message is specified by the
InterRatHoComm.CellInfoMaxGeranCellNum parameter on the eNodeB.

 The settings of these switches can be changed by running the MOD

CELLALGOSWITCH command.
 GeranCsfbSwitch
 Parameter name: GeranCsfbSwitch
 Unit: None
 Meaning: Indicates whether to enable CSFB to GERAN.
 GeranFlashCsfbSwitch
 Parameter name: GeranFlashCsfbSwitch
 Unit: None
 Meaning: This switch does not take effect if GeranCsfbSwitch is off. When
the GeranFlashCsfbSwitch is on, flash CSFB to GERAN is enabled, and
GERAN system information is carried during redirection. When the
GeranFlashCsfbSwitch is off, flash CSFB to GERAN is disabled.

 The setting of this parameter can be changed by running the MOD

INTERRATHOCOMM command.
 CellInfoMaxGeranCellNum
 Parameter name: Max Geran cell num in redirection
 Unit: None
 Meaning: Indicates the maximum number of GERAN cell system information
messages that can be transmitted during a flash redirection procedure.

 If the BlindHoSwitch options are deselected and the UE supports measurements,

measurement-based handling is used.

 BlindHoSwitch
 Parameter name: BlindHoSwitch
 Unit: none
 Meaning: If this option is selected, blind handovers for CSFB are enabled. If
this option is deselected, blind handovers for CSFB are disabled. If both this
option and the BlindHoSwitch option of the Handover Mode switch
parameter of the CellHoParaCfg managed object (MO) are selected, blind
CSFB handovers for CSFB are enabled.

CELLHOPARACFG command.
 BlindHoSwitch
 Parameter name: BlindHoSwitch
 Unit: none
Bind handover for CSFB is enabled only if this option is selected. A blind
ENodeBAlgoSwitch MO are selected.


 The threshold for event A1 is specified by the CSFallBackHo.BlindHoA1ThdRsrp

parameter. The event-A1-related mechanisms are the same as those for coverage-
based handovers from E-UTRAN to UTRAN.



 A PLMN list consists of three parts:

 The PLMN that the serving cell belongs to
 The PLMNs configured in InterPlmnHoList MOs, when the
InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter is selected
 The equivalent PLMNs whose IDs are obtained by the eNodeB from the
information element (IE) Handover Restriction List (sent by the MME), when
both the InterPlmnHoSwitch and EPlmnSwitch options of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter are selected.




 Neighboring GERAN frequencies are configured in GeranNfreqGroup MOs.

 The priorities of neighboring GERAN frequencies for RRC_CONNECTED UEs are
specified by the GeranNfreqGroup.ConnFreqPriority parameter.
 Neighboring GERAN cells are configured in GeranNCell MOs.
 The eNodeB selects a frequency group from the candidates based on blind-handover
priorities of neighboring cells as follows:
 If neighboring cells are assigned non-zero blind-handover priorities, which are
specified by GeranNcell.BlindHoPriority, the eNodeB selects the frequency
group that contains the operating frequency of the cell with the highest blind-
handover priority.
 If all blind-handover priorities are 0, the eNodeB considers frequency priorities
for RRC_CONNECTED UEs. It preferentially selects the frequency group with
the highest priority for RRC_CONNECTED UEs.
 If there is more than one frequency with the highest priority for RRC_CONNECTED
UEs or with the highest blind-handover priority during final frequency selection, the
eNodeB selects one at random.
 If the PLMN of a neighboring GERAN frequency is different from the PLMN that the
UE belongs to, and it is not included in the inter-PLMN list or equivalent PLMN list
during final frequency selection, the eNodeB starts frequency selection for a blind
redirection to the second-priority RAT.


 The RIM procedure between E-UTRAN and GERAN is enabled by default because
there is no switch for selecting a load information transfer channel.
 If the ENodeBAlgoSwitch.RimOnEcoSwitch parameter is set to OFF, the RIM
procedure is performed through the core network.
 The RIM procedure between EUTRAN and GERAN is controlled by the
GERAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.
 If this option is selected, the eNodeB uses the RIM procedure in Multiple
Report mode to obtain the system information of external GERAN cells. If
external GERAN cells do not support the Multiple Report mode, they do not
notify the eNodeB of any system information change after the initial request.
 If this option is cleared, the eNodeB uses the RIM procedure in Single Report
mode to obtain the system information of external GERAN cells.


 GERAN_RIM_SWITCH
 Parameter name: GERAN_RIM_SWITCH
 Meaning: Indicates the switch used to enable or disable the RIM procedure that
requests event-driven multiple reports from GERAN cells. If this switch is on, the
eNodeB can send RAN-INFORMATION-REQUEST PDUs to CERAN cells to
request multiple event-driven reports. If this switch is off, the eNodeB cannot
send RAN-INFORMATION-REQUEST PDUs to GERAN cells to request multiple
event-driven reports.
 Unit: none

 RimOnEcoSwitch
 Parameter name: Support RIM by eCoordinator Switch
 Meaning: Indicates whether the RAN information management (RIM) procedure
is initiated by the eCoordinator. If this parameter is set to ON, the RIM procedure
is initiated by the eCoordinator. If this parameter is set to OFF, the RIM
procedure is initiated by the core network.
 Value Range: ON, OFF
 Physical value range: ON, OFF
 Unit: none

 In section 5.5.1.1.1 of 3GPP TS 23.401, the procedure conflict between X2-based

 If the MME receives a rejection to a UE Context Modification Request
message with a CS Fallback indicator from the eNodeB with an indication that
an X2 handover is in progress, the MME shall resend a UE Context
eNodeB when the handover is complete or to the source eNodeB when the
handover is deemed to have failed.
 In section 5.5.1.2.1 of 3GPP TS 23.401, the procedure conflict between S1-based
 If the MME receives a rejection to a UE Context modification Request
message with a CS Fallback indication from the eNodeB with an indication that
an S1 handover is in progress, the MME shall resend a UE Context
eNodeB when either the handover is complete or to the source eNodeB .

 If the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message with

the CS Fallback Indicator IE before handover indication is transmitted over the air
interface, the eNodeB sends a HANDOVER CANCEL message to the MME to cancel
the handover procedure and prioritize the CSFB procedure.
 When a CSFB procedure conflicts with an inter-eNodeB reestablishment with no
context, the eNodeB preferentially processes the reestablishment procedure.

 The setting of this switch can be changed by running the MOD GLOBALPROCSWITCH
command.
 CsfbFlowFirstSwitch
 Parameter name: CsfbFlowFirstSwitch
 Meaning: This option specifies the policy for handling the conflicts between
handover and CSFB procedures. If this option is selected and the handover and
CSFB procedures conflict, the eNodeB processes the CSFB procedure first. If
this option is deselected in the preceding scenario, the eNodeB processes the
handover procedure first.
 Unit: none

 IdleCsfbRedirectOptSwitch: If this option is selected, the number of signaling

exchanges for CSFB decreases and the CSFB delay is also shortened.

 The CSFB to GERAN fails for both the calling party and called party.


 MOD ENODEBALGOSWITCH: HoModeSwitch=BlindHoSwitch-1;

 MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;

 MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=GeranCsfbSwitch-1;

 MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-

0&PS_HO-0;

 MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,

InterRatSecondPri=UTRAN;
 ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=0, InterRatHighestPri=GERAN,
InterRatSecondPri=UTRAN;

 MOD GERANNCELL: LocalCellId=0, Mcc="460“,Mnc="20", Lac=12,

GeranCellId=15,BlindHoPriority=32;


 The following figures show the measurement points. The number of times CSFB is
triggered is measured at point A, and the number of times CSFB is successfully
responded to is measured at point C. The figure on the left shows the CSFB
procedure for an RRC_IDLE UE, and the figure on the right shows the CSFB
procedure for an RRC_CONNECTED UE. The eNodeB measures the number of
times CSFB is triggered for emergency calls and the number of times CSFB for
emergency calls is successfully responded to at points A and C, respectively, only
when the eNodeB determines that CSFB is triggered for emergency calls.


华为技术有限公司版权所有未经许可不得扩散


LTE eRAN15.1 CSFB

Uploaded by

Document Information

Original Description:

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

LTE eRAN15.1 CSFB

Uploaded by

Copyright:

Available Formats

LTE eRAN15.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Improper TA-LA planning is prone to the following issues:

Confidential Information of Huawei. No Spreading Without Permission

 When VoLTE is deployed:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

5. The VLR returns an SGsAP-LOCATION-UPDATE-ACCEPT message to the MME

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

1. The MME sends an SGsAP-IMSI-DETACH-INDICATION message (including the IMSI,

3. The VLR sends an SGsAP-IMSI-DETACH-ACK or SGsAP-EPS-DETACH-ACK message to

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

4. The VLR returns an SGsAP-LOCATION-UPDATE-ACCEPT message to the MME.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Answer to question 1: The UE will not perform an LAU. An LAU needs to be

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 An RRC_IDLE UE needs to transfer to the RRC_CONNECTED state through an RRC

Confidential Information of Huawei. No Spreading Without Permission

 The mobile-terminated CS call procedure is similar to the mobile-originated CS call

Confidential Information of Huawei. No Spreading Without Permission

1. Upon receiving an incoming IAM message, the MSC sends an GsAP-PAGING-

Confidential Information of Huawei. No Spreading Without Permission

6. The UE performs a redirection from E-UTRAN to UTRAN/GERAN.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The mobile-terminated CS call procedure is similar to the mobile-originated CS call

Confidential Information of Huawei. No Spreading Without Permission

 IdleCsfbRedirectOptSwitch: If this option is selected and the preferred CSFB policy

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Special handling of emergency calls in the CSFB procedure:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 In section 5.5.1.1.1 of 3GPP TS 23.401, the procedure conflict between X2-based

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 R8 PS Redirection: After receiving a CS Fallback Indicator, the eNodeB sends an