ISR with CSFB - Feature Description
Call Flows
|
Step
|
Description
|
|---|---|
|
1.
|
The MSC receives an
incoming voice call and sends a CS page to the MME over a SGs interface.
|
|
2.
|
The MME uses the TMSI
(or IMSI) received from the MSC to find the S-TMSI (which is used
as the paging address on the LTE radio interface).
|
|
3.
|
The MME forwards the
paging request to the eNodeB in the TAs where the UE is registered.
The eNodeBs perform the paging procedures in all the cells in the
indicated TAs.
|
|
4.
|
The paging message
includes a special CS indicator that informs the UE that the incoming
paging is for a terminating CS call.
|
|
5.
|
On receiving the paging
message, the UE performs a service request procedure which establishes
the RRC connection and sends a Service Request to the MME. The Service Request
message includes a special CS Fall-back indicator that informs the
MME that the CS fallback is required.
|
|
6.
|
This triggers the
MME to activate the bearer context in the eNodeB with an indication to
perform fallback to GERAN or UTRAN.
|
|
7.
|
The eNodeB selects
a suitable target cell, by triggering the UE to send measurements on
the neighbour cells, and initiates a handover or cell change procedure.
The selection between handover or cell change procedure is based
on the target cell capabilities and is configured in the eNodeB.
Note: If the target cell
is a UTRAN cell, then MME can do subscriber context transfer using
Forward Relocation Req / Rsp / Complete / Complete
Ack messages and set up the radio contexts in UTRAN a-priori. However
if the target cell is GERAN, then the SGSN currently does not support
PS handover procedure and hence transfer of radio context from MME
to 2G SGSN through Fwd reloc req / rsp /complete/complete
ack procedure is not possible in the current release. In this scenario,
CSFB is performed through a RRC release at the eNodeB and then a
Suspend Request is sent to the SGSN.
|
|
8.
|
After a handover or
cell change procedure, the UE detects the new cell and establishes a
radio connection and sends a page response to the MSC, through the
target RAN.
|
|
9.
|
When the page response
arrives at the MSC, a normal mobile terminated call setup continues
and CS call is activated towards the UE.
|
How it Works
ISR CSFB Procedures
CS Paging Procedure
|
Step
|
Description
|
|---|---|
|
1.
|
A Mobile Terminating
call arrives at MSC/VLR (via the G-MSC) for a UE which
is camped on E-UTRAN.
|
|
2.
|
If the ISR is active
and the SGs interface is active between MSC and MME, then the MSC/VLR
sends a Page Request (SGsAP-PAGING-REQUEST) to the MME.
|
|
3.
|
As ISR is active and
the UE is in ECM_IDLE state, the MME forwards the CS paging message
received from the MSC/VLR to the associated SGSN. The MME
receives the SGSN information in the regular ISR activation process.
The MME builds a "CS Paging Indication" message, which is a GTPv2
message, from the SGsAP-PAGING_REQUEST to the correct SGSN.
|
|
4.
|
The SGSN receives
the CS Paging Indication message from the MME, and sends paging
messages to RNS/BSSs.
|
|
5.
|
The RNS/BSS
forwards the CS Paging Indication message to the UE.
|
|
6.
|
The CS fallback or
Cell re-selection process progresses.
|
|
7.
|
Once the process is
complete, the UE sends a CS Paging response to the RNS/BSS.
|
|
8.
|
The RNS/BSS
forwards the CS Paging Response to the MSC/VLR.
|
Alert and UE Notification Procedure
ISR De-activation Procedure
Detach Procedures for CSFB Capable UEs
MS Initiated Last PDN De-activation Procedure
PGW Initiated Last PDN De-activation Procedure
Configuring ISR with Circuit Switched Fallback
config
context <context_name>
iups-service <iups_service_name>
rnc id <rnc_id>
[default | no ] ranap
paging-cause-ie mme-signalling < paging_cause_value >
end
Monitoring and trouble-shooting the CSFB feature