Content for  TS 23.272  Word version:  19.0.0

The MSC receives an incoming voice call and responds by sending a Paging Request (IMSI or TMSI, optional Caller Line Identification and Connection Management information, eMLPP priority level indication) to the MME over a SGs interface. The MSC only sends a CS Page for an UE that provides location update information using the SGs interface. In active mode the MME has an established S1 connection and if the MME did not return the "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME reuses the existing connection to send the CS Service Notification to the UE. If the MME returned the "SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME shall not send the CS Page to the UE and sends CS Paging Reject towards MSC to stop CS Paging procedure, and this CSFB procedure stops. If the X2-based or S1-based handover procedure is ongoing when the MME receives a Paging Request over the SGs interface, the MME shall follow the procedures as specified in clause 5.5.1.1.1 of TS 23.401 and clause 5.5.1.2.1 of TS 23.401 for X2-based handover and S1-based handover respectively. If the Inter RAT handover procedure is ongoing when the MME receives a Paging Request over the SGs interface, the MME shall simply discard this message and no further action is performed by MME. In this case, mobile terminating call can be continued by the MSC retransmitting Paging message as specified in TS 29.118. The eNodeB forwards the CS Service Notification message to the UE. The message contains CN Domain indicator and, if received from the MSC, the Caller Line Identification. The MME sends the SGs Service Request message to the MSC containing an indication that the UE was in connected mode. The MSC uses this connected mode indication to start the Call Forwarding on No Reply timer for that UE and the MSC should send an indication of user alerting to the calling party. Receipt of the SGs Service Request message stops the MSC retransmitting the SGs interface Paging message. If the MME receives paging request message with eMLPP priority level indication from the MSC, then the MME determines based on its configuration whether this priority level requires CSFB priority call handling.

UE sends an Extended Service Request (Reject or Accept) message to the MME for mobile terminating CS fallback. Extended Service Request message is encapsulated in RRC and S1-AP messages. The UE may decide to reject CSFB based on Caller Line Identification.

Upon receiving the Extended Service Request (Reject) for mobile terminating CS fallback, the MME sends Paging Reject towards MSC to stop CS Paging procedure and this CSFB procedure stops.

The MME sends an S1-AP UE Context Modification Request (CS Fallback Indicator, LAI) message to eNodeB. This message indicates to the eNodeB that the UE should be moved to UTRAN/GERAN. The registered PLMN for CS domain is identified by the PLMN ID included in the LAI, which is allocated by the MME. If MME determined in Step 1a that CSFB priority call handling shall apply, the MME sends S1-AP UE Context Modification Request message to the eNodeB with priority indication, i.e. "CSFB High Priority", as specified in TS 36.413.

The eNodeB shall reply with S1-AP UE Context Modification Response message.

The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN/UTRAN cell to which the redirection procedure will be performed.

If the UE and network support inter-RAT cell change order to GERAN and the target cell is GERAN: The eNodeB can trigger an inter-RAT cell change order (optionally with NACC) to a GERAN neighbour cell by sending an RRC message to the UE. The inter-RAT cell change order may contain a CS Fallback Indicator which indicates to UE that the cell change order is triggered due to a CS fallback request. If the inter-RAT cell change order contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then the UE considers that CS fallback has failed. Service Request procedure is considered to be successfully completed when cell change order procedure is completed successfully. The eNodeB selects the target cell considering the PLMN ID and possibly the LAC for CS domain provided by the MME in step 1d for CCO/NACC purpose.

If the UE or the network does not support inter-RAT PS handover from E-UTRAN to GERAN/UTRAN nor inter-RAT cell change order to GERAN: The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN instead of PS HO or NACC.

If the UE and network support "RRC connection release with redirection and Multi Cell System Information to GERAN/UTRAN": The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN and include one or more physical cell identities and their associated System Information. In step 3b or step 3c, the eNodeB includes the redirection control information into the RRC Connection Release message based on the PLMN ID for CS domain and the RAT/frequency priority configured in the eNodeB, so that the UE registered PLMN for CS domain can be preferably selected. Also in Steps 3b or 3c, the eNB sets the "CS Fallback High Priority" indication in the RRC Release message, if the S1AP message in Step 1d contains the "CSFB High Priority" indication.

The eNodeB sends an S1-AP UE Context Release Request message to the MME. If the target cell is GERAN and either the target cell or the UE does not support DTM the message includes an indication that the UE is not available for PS service.

The MME releases the UE Context in the eNodeB as well as all eNodeB related information in the S-GW as specified in TS 23.401. In case the Cause indicates that RRC was released due to abnormal conditions, e.g. radio link failure, the MME suspends the EPS bearers (Step 8).

(Step 6a is performed if step 3a, Cell Change Order to GERAN, was performed). The UE moves to the new cell in GERAN. The UE uses the NACC information and/or the broadcast System Information and when it has the necessary information to access the GERAN cell, establishes a radio signalling connection.

(Step 6b is performed if step 3b, RRC release with redirection, was performed). The UE moves to the target RAT, identifies a suitable cell preferably of the same PLMN as received in LAI IE of combined EPS/IMSI Attach/TAU Accept message,, receives the broadcast System Information and when it has the necessary information to access GERAN/UTRAN, establishes a radio signalling connection.

(Step 6c is performed if step 3c, RRC connection release with redirection and Multi Cell System Information, was performed) The UE moves to the target RAT and identifies a suitable cell preferably of the same PLMN as received in LAI IE of combined EPS/IMSI Attach/TAU Accept message. The UE uses the Multi Cell System Information and/or the broadcast System Information and when it has the necessary information to access GERAN/UTRAN, the UE establishes the radio signalling connection. If the UE receives the "CS Fallback High Priority" indication in the RRC Release message in Step 3b or 3c and the target is UTRAN, the UE sets the establishment cause value to "Terminating High Priority Signalling" in the RRC Connection Request in Steps 6b and 6c. If the target is GERAN, no special establishment cause value is set by the UE.

If the LA of the new cell is different from the one stored in the UE, the UE shall initiate a Location Area Update regardless of the different Network Modes of Operation (NMO). The UE shall set the "CSMT" flag in the LAU Request. The "CSMT" flag is used to avoid missing MT call in roaming retry case. In NMO I, the UE in GERAN may perform LA update over the RR connection instead of combined RA/LA update over the packet access as defined in clause 4.7.5.2.5 of TS 24.008, unless enhanced CS establishment in DTM is supported. Further the UE performs any Routing Area Update procedure as specified in TS 23.060. In NMO I a CSFB UE shall perform LAU (and if it does so, shall set the "CSMT" flag) and RAU procedures instead of a Combined RA/LA Update procedure to speed up the CSFB procedure. When the MSC receives a LA Update Request, it shall check for pending terminating CS calls and, if the "CSMT" flag is set, maintain the CS signalling connection after the Location Area Update procedure for pending terminating CS calls. If the eNodeB indicated UE to go to GERAN in step 3 but the UE finally camps on an UTRAN cell of the same RA that the UE is registered with and ISR active, the UE shall locally deactivate ISR.

If the target RAT is GERAN and DTM is not supported or the UE does not support DTM, the UE starts the Suspend procedure specified in TS 23.060. This triggers the (serving) SGSN to send a Suspend Request (TLLI, RAI) message to the old CN node identified by the RAI and TLLI. If ISR is not active, the RAI and TLLI refer to an MME. The MME returns a Suspend Response to the SGSN even though GUTI cannot be derived from the P-TMSI and RAI pair. If ISR is active, the RAI and TLLI refer to the old S4-SGSN, In this case, if the serving SGSN is different from the old SGSN which has ISR association with MME, the old SGSN returns a Suspend Response to the serving SGSN.

If the S1-AP UE Context Release Request message, received from the eNodeB in step 4, indicates that the UE is not available for the PS services in the target cell, the MME deactivates GBR bearers towards S-GW and P-GW(s) by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401, and starts the preservation and suspension of non-GBR bearers by sending Suspend Notification message to the S-GW. If ISR is active, the (old) S4-SGSN deactivates GBR bearers towards S-GW and P-GW(s) by initiating MS-and SGSN initiated Bearer Deactivation procedure as specified in TS 23.060, and starts the preservation and suspension of non-GBR bearers by sending the Suspend Notification message to the S-GW, which is all triggered by the Suspend procedure in step 7. The S-GW sends Suspend Notification message to the P-GW(s) when it receives the Suspend Notification message from MME or S4-SGSN. If the S-GW receives two Suspend Notification messages for the same UE, it ignores the second one except for sending response. The MME stores in the UE context that the UE is in suspended status. If ISR is active, the (old) S4-SGSN stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW(s). The P-GW should discard packets if received for the suspended UE.

If the UE does not initiate a LAU procedure, the UE responds to the paging by sending a Paging Response message as specified in TS 44.018 or TS 25.331. When received at the BSS/RNS, the Paging Response is forwarded to the MSC.

If UE is registered in the MSC serving the 2G/3G cell and the UE is allowed in the LA the MSC shall establish the CS call.

If the UE is not registered in the MSC that receives the Paging Response or the UE is not allowed in the LA, the MSC shall reject the Paging Response by releasing the A/Iu-cs connection. The BSS/RNS in turn releases the signalling connection for CS domain.

The signalling connection release shall trigger the UE to obtain the LAI, which causes the initiation of a Location Area Update or a Combined RA/LA procedure as specified in TS 23.060 for the different Network Modes of Operation (NMO). The Location Area Update triggers the Roaming Retry for CS Fallback procedure as defined in clause 7.5. After performing the LAU procedure the MSC shall establish the CS call if the UE is allowed in the LA.