School of Specs 38.300v19.3.0

3GPP 38.300 v19.3.0 — the document's own text

16.3.4.5 Mobility

To make mobility slice-aware in case of Network Slicing, S-NSSAI is introduced as part of the PDU session information that is transferred during mobility signalling. This enables slice-aware admission and congestion control.

NG handovers are allowed regardless of the slice support of the target NG-RAN node i.e. even if the target NG-RAN node does not support the same slices as the source NG-RAN node. Xn handovers are allowed only when at least one of the slices with active PDU sessions for the UE at the source gNB is supported at the target gNB. The source gNB performs this check as part of the Handover Preparation. An example for the case of connected mode mobility across different Registration Areas is shown in Figure 16.3.4.5-1 for the case of NG based handover and in Figure 16.3.4.5-2 for the case of Xn based handover.

Figure 16.3.4.5-1: NG based mobility across different Registration Areas
Figure 16.3.4.5-1: NG based mobility across different Registration Areas
Figure 16.3.4.5-2: Xn based mobility across different Registration Areas
Figure 16.3.4.5-2: Xn based mobility across different Registration Areas