Low Mobility Handover (Xn/N2)

Feature Summary and Revision History

Summary Data

Table 1. Summary Data

Applicable Product(s) or Functional Area

AMF

Applicable Platform(s)

SMI

Feature Default Setting

Enabled - Always-on

Related Documentation

Not Applicable

Revision History

Table 2. Revision History

Revision Details

Release

First introduced.

2022.01.0

Feature Description

The low mobility handover feature supports the following functions:

  • Handover cancel for N2 without AMF change

  • Handover cancel for N2 with source and target AMF change

  • Handover failure procedure with and without AMF change

AMF doesn't support the following:

  • Collision

  • Non-3GPP access

  • Trace

  • Event subscription

  • PCF interactions

How It Works

This section describes how this feature works.

Call Flows

This section describes the key call flows for this feature.

N2 Handover Cancel Call Flow

This section describes the N2 Handover cancel call flow.

The source NG-RAN sends the Handover Cancel Request to the source AMF, before sending the Handover command to the UE.

It sends this request when it observes the following:

  • Timer expiry

  • Internal failure within the source NG-RAN

  • UE return to source cell

The Handover Cancel Request releases the handover reserved resources in the target system.

Figure 1. N2 Handover Cancel Call Flow
Table 3. N2 Handover Cancel Call Flow Description

Step

Description

1

The S-gNB (source gNB) sends the Handover Cancel to the S-AMF (source AMF).

2

The S-AMF sends the Namf_Comm_ReleaseReq to the T-AMF (target AMF).

3, 4

The T-AMF sends the UE Context Release Command to the T-gNB (target gNB) and receives the UE Context Release Complete.

5

The T-AMF sends the Relocation Cancel Indication (Nsmf_Update_Req) to the SMF.

6

The SMF sends Nsmf_update_Rsp to the T-AMF.

7

The S-AMF receives Namf_Comm_ReleaseRsp from the T-AMF.

8

The S-AMF sends Handover Cancel ACK to the S-gNB.