Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.502  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H… 
4.11.1.2.3 Handover Cancel 
...

 

4.11.1.2.3  Handover Cancel  p. 292
Instead of completing the handover procedure, the source RAN node (NG-RAN, E-UTRAN) may at any time, during the handover procedure, up to the time when a handover command message is sent to the UE, cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the source RAN node and is initiated by sending a handover cancel message to the source CN node (AMF or MME).
A handover cancel message shall also be sent by the source RAN node after a handover command message is sent to the UE for the case where the handover fails and the UE returns to the old cell or radio contact with the UE is lost. This is done in order to release the resources reserved for the handover in the target system.
During EPS to 5GS handover when the initial AMF has invoked a target AMF (as described in step 8a in clause 4.11.1.2.2),
  • when the source MME has received a N26 Forward Relocation Response from the target AMF, the MME sends N26 Cancel Relocation Request directly to the target AMF and the initial AMF is not involved at all in the Cancel Relocation procedure.
  • When the source MME has not received a response from the target AMF, the MME sends N26 Cancel Relocation Request to the initial AMF:
    • if the initial AMF has already invoked the target AMF, the initial AMF indicates the Cancel Relocation to the target AMF and the target AMF becomes responsible of the Handover Cancellation (e.g. the target AMF initiates Nsmf_PDUSession_UpdateSMContext request indicating Handover Cancel towards the SMF+PGW-C(s) unless the target AMF has already indicated a Handover failure due to prior target NG RAN rejection of the Handover);
    • otherwise the initial AMF handles the relocation cancellation.
Reproduction of 3GPP TS 23.502, Fig. 4.11.1.2.3-1: Handover Cancel procedure
Figure 4.11.1.2.3-1: Handover Cancel procedure
Up
Step 1.
When the source RAN (NG-RAN, E-UTRAN) decides to cancel the handover to the target system, the source RAN initiates handover cancel message to the source CN node (AMF or MME).
Step 2.
After receiving the handover cancel message from the source RAN, if the source CN node or the target CN node is MME, it sends a Relocation Cancel Request message to the target CN node (MME or AMF). If both the source CN node and target CN node are AMF, the source AMF invokes (via initial AMF if AMF re-allocation is performed during preparation phase) the Namf_Communication_ReleaseUEContext Request (UE Context ID) toward the target AMF. During EPS to 5GS handover with AMF reallocation if the initial AMF has invoked a target AMF, the initial AMF invokes the Namf_Communication_CancelRelocateUEContext Request (UE Context ID) toward the target AMF.
Step 3.
The target CN node (MME or AMF) triggers release of resources towards target RAN node. The target RAN node releases the AN resources allocated for the handover.
Step 4.
If the target CN node is MME, the MME sends the Delete Session Request to the SGW/SGW-C (see clause 5.5.2.5.2 of TS 23.401).
Step 4a.
[Conditional] The SGW-C releases the corresponding resource in the SGW-U if allocated during the handover preparation.
Step 4b.
If the target CN node is AMF, the AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the SMF in non-roaming and local breakout roaming scenarios.
For home-routed roaming scenario, AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the (target) V-SMF and the V-SMF invokes the Nsmf_PDUSession_Update Request (Relocation Cancel Indication) towards the H-SMF.
Based on the Relocation Cancel Indication, the SMF(s) deletes the session resources established during handover preparation phase in SMF(s) and UPF(s).
Step 4c.
[Conditional] The (target) V-SMF releases the corresponding resource in the (target) V-UPF if allocated during the handover preparation.
Step 4d.
[Conditional] The (H-)SMF+PGW-C releases the corresponding resource in the (H-)UPF+PGW-U if allocated during the handover preparation.
Step 5.
The target CN node (MME or AMF) sends Relocation Cancel Response towards the source CN node (AMF or MME).
Step 6.
The source CN node (AMF or MME) responds with handover cancel ACK towards the source RAN.
Step 7.
[Conditional] If target CN node is AMF and the source CN is MME and indirect forwarding tunnel had been set up during handover preparation phase then cancellation of handover triggers the MME to release the temporary resources used for indirect forwarding.
Step 7b.
[Conditional] If the source CN is AMF and the target CN node is MME and if indirect forwarding tunnel had been setup during handover preparation phase, then cancellation of handover triggers the AMF to release the session resources established during handover preparation phase in SMF(s) and UPF(s).
  • The AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the SMF in non-roaming and local breakout roaming scenarios.
  • For home-routed roaming scenario, the AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the V-SMF and the V-SMF invokes the Nsmf_PDUSession_Update Request (Relocation Cancel Indication) towards the H-SMF.
Based on the Relocation Cancel Indication, the SMF(s) deletes the session resources established during handover preparation phase in SMF(s) and UPF(s).
Step 7c.
[Conditional] In home routed roaming case, the V-SMF releases the corresponding resource in the target V-UPF if allocated during the handover preparation.
Step 7d.
[Conditional] In non-roaming or LBO case, the SMF+PGW-C releases the corresponding resource in the UPF+PGW-U if allocated during the handover preparation.
Step 8.
[Conditional] If target CN node is MME and indirect forwarding tunnel is setup during handover preparation phase then cancellation of handover triggers the target MME to release the temporary resources used for indirect forwarding.
Step 8a.
[Conditional] The SGW-C releases the resources for indirect forwarding in the SGW-U if allocated during the handover preparation.
Up

Up   Top   ToC