Huawei LTE CS Fallback Feature
Huawei LTE CS Fallback Feature
Huawei LTE CS Fallback Feature
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.
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.
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.
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.
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.
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.
Upon receiving an Initial Address Message (IAM), the MSC performs destination node
(called node) analysis and acquires the status of the called UE.
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.
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.
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.
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.
GUI value range: On, Off
Actual value range: On, Off
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.
GUI value range: On, Off
Actual value range: On, Off
The setting of the following switch can be changed by running the MOD
CELLHOPARACFG command.
BlindHoSwitch (Cell-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
ENodeBAlgoSwitch MO are selected.
GUI value range: On, Off
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.
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.
GUI value range: 0 to 32
Actual value range: 0 to 32
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.
GUI value range: 0 to 8
Actual value range: 0 to 8
This parameter can be set by running the ADD/MOD UTRANNFREQ command.
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.
GUI value range: On, Off
Actual value range: On, Off
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.
The setting of the following switch can be changed by running the MOD
ENODEBALGOSWITCH command.
BlindHoSwitch
Parameter name: BlindHoSwitch
GUI value range: On, Off
Actual value range: On, Off
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.
The setting of the following switch can be changed by running the MOD
CELLHOPARACFG command.
BlindHoSwitch
Parameter name: BlindHoSwitch
GUI value range: On, Off
Actual value range: On, Off
Unit: none
Meaning: This option specifies whether to enable blind handover for CSFB.
Bind 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
ENodeBAlgoSwitch MO are selected.
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.
The setting of the following switch can be changed by running the MOD
ENODEBALGOSWITCH command.
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.
GUI value range: On, Off
Actual value range: On, Off
Unit: none
The setting of the following switch can be changed by running the MOD
ENODEBALGOSWITCH command.
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
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.
GUI value range: On, Off
Actual value range: On, Off
Unit: none
The CSFB to GERAN fails for both the calling party and called party.
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.