Content for TS 23.502 Word version: 19.1.0

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.2.7 N2 procedures 4.2.7.1 N2 Configuration 4.2.7.2 NGAP UE-TNLA-binding related procedures 4.2.7.2.1 Creating NGAP UE-TNLA-bindings during Registration and Service Request 4.2.7.2.2 Creating NGAP UE-TNLA-bindings during handovers 4.2.7.2.3 Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release 4.2.7.2.4 NGAP UE-TNLA-binding update procedure 4.2.7.2.5 NGAP UE-TNLA-binding per UE Release procedure 4.2.7.3 AMF Failure or Planned Maintenance handling procedure 4.2.7.4 Additional User Location Information with Mobile Base Station Relay (MBSR) 4.2.8a UE Capability Match Request procedure
...

4.2.7 N2 procedures p. 98

4.2.7.1 N2 Configuration p. 98

At power up, restart and when modifications are applied, the 5G-AN node and AMF use non-UE related N2 signalling to exchange configuration data. Full details of this configuration data are specified in TS 38.413, but the following highlights some aspects.

The AMF supplies the 5G-AN node with information about:

the AMF Name and the GUAMI(s) configured on that AMF Name;
the set of TNL associations to be established between the NG-RAN node and the AMF;
weight factor associated with each of the TNL association within the AMF; and
weight factor for each AMF Name within the AMF Set; and
(optional) for each GUAMI(s) configured on that AMF the corresponding backup AMF Name.

The weight factors are used for load distribution of the initial N2 messages. The AMF chooses whether or not to use the same TNL association for the initial N2 message and subsequent messages for that UE. TNL associations configured with a weight factor set to zero are not permitted for the initial N2 message, but can be used for subsequent N2 messages.

Deployments that rely solely on 5GC-based load balancing can set the weight factors associated with TNL associations that are permitted for the initial N2 message to the same value.

The 5G-AN supplies over N2 the AMF with information about the Tracking Area(s) it serves and the S-NSSAI(s) it supports in each of these Tracking Areas. See clause 5.3.2.3 of TS 23.501.

4.2.7.2 NGAP UE-TNLA-binding related procedures p. 98

4.2.7.2.1 Creating NGAP UE-TNLA-bindings during Registration and Service Request p. 98

When a UE connects to the 5GC via a 5G-AN node without providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate to any of its connected AMFs, the following steps are performed:

The 5G-AN node selects an AMF as defined in clause 6.3.5 of TS 23.501.
The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial message e.g. N2 INITIAL UE MESSAGE for the selected AMF, as defined in clause 5.21.1.3 of TS 23.501 and forwards the UE message to the AMF via the selected TNL association.
The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.

NOTE 1:
This process could take place during the Registration procedure (for Initial Registration, Mobility Registration Update).
The AMF may decide to modify the NGAP UE-TNLA-binding toward other 5G-AN nodes such as N3IWF. This is done if the AMF is changed and old AMF have existing NGAP UE-TNLA-bindings toward other 5G-AN nodes.

When a UE connects to the 5GC via a 5G-AN node with a 5G-S-TMSI or GUAMI associated with the AMF usable by the 5G-AN node, the following steps are performed:

The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's 5G-S-TMSI or GUAMI.
The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.

NOTE 2:
This process could take place during the Registration procedure or Service Request procedure.

4.2.7.2.2 Creating NGAP UE-TNLA-bindings during handovers p. 99

During an Xn-based inter NG-RAN node handover, the following applies

If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node supplies the target 5G-AN node with the corresponding TNL address of the AMF for the currently used TNL association.
If the target 5G-AN does not have a TNL association towards the TNL address of the AMF received from the source 5G-AN node, the target 5G-AN node establishes a TNL association towards the TNL address received from the source 5G-AN node, creates an NGAP UE-TNLA-binding to this TNL association and sends the N2 Path Switch Request via this TNL association.
Otherwise, the target 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations towards the TNL address, permitted for the initial N2 message for the AMF identified by the UE's GUAMI.
The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.

During an inter NG-RAN node handover without Xn interface (i.e. during an N2 handover) the following applies:

If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node sends the N2 Handover Required message using the corresponding TNL address of the AMF.
Otherwise the 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's GUAMI.
The target AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 Handover Request message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the target AMF.

4.2.7.2.3 Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release p. 99

If the AMF has released the NGAP UE-TNLA-binding in the 5G-AN node for a UE and the 5G-AN node needs to send an N2 message for this UE, the following applies:

The 5G-AN node checks the GUAMI stored in the UE context and the associated AMF:
- If the GUAMI is available, 5G-AN selects the AMF which owns that GUAMI.
- If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) but one corresponding target AMF has been indicated, 5G-AN selects that target AMF even if the GUAMI has not been updated as available by the target AMF.
- If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) and no corresponding target AMF has been indicated, the 5G-AN selects an AMF from the AMF Set based on AMF Set ID of the GUAMI, as defined in clause 6.3.5 of TS 23.501.
- The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message with the selected AMF, as defined in clause 5.21.1.3 of TS 23.501,and sends the N2 message to the AMF via the selected TNL association.
The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.

If the NGAP UE-TNLA-binding has been released for a UE and the AMF needs to send an N2 message for this UE, the following applies:

The AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the AMF.

The TNL association chosen by the AMF always takes precedence.

4.2.7.2.4 NGAP UE-TNLA-binding update procedure p. 100

At any time the AMF may decide to re-bind the NGAP UE association to a new TNL association:

by sending a UE-specific NGAP message on a new TNL association (triangular redirection), if:
- AMF responds to the 5G-AN node initiated NGAP message (i.e. triangular redirection) as described in clauses 4.2.7.2.1, 4.2.7.2.2 and 4.2.7.2.3; or
- AMF initiated UE-specific NGAP message needs to be sent to 5G-AN node;
by sending a UE-specific NGAP UE-TNLA binding release message to 5G-AN and the 5G-AN node updates the NGAP UE-TNLA binding with the new TNL association.

4.2.7.2.5 NGAP UE-TNLA-binding per UE Release procedure p. 100

At any time the AMF may decide to release the NGAP UE-TNLA binding while keeping the UE in CM-CONNECTED state while keeping the corresponding N3 interface. The AMF releases the NGAP UE-TNLA binding by sending a UE-specific NGAP UE-TNLA binding release message on the current TNL association.

If the AMF releases the NGAP UE-TNLA-binding without sending AMF unavailable status indication, then the AN may immediately trigger creation of a new NGAP-UE-TNLA-binding with the same AMF for subsequent N2 messages or may leave the NGAP UE association without NGAP UE-TNLA-binding. In the latter case the new NGAP UE-TNLA-binding is re-created upon the subsequent AN-initiated or AMF-initiated UE-specific N2 signalling as specified in clause 4.2.7.2.3.

If the AMF releases the NGAP UE-TNLA-binding after AMF unavailable status indication, then the AN has to re-create the NGAP-UE-TNLA-binding with a different AMF. The 5G-AN re-creates N2AP UE-TNLA-binding for subsequent N2 messages for the given UE as specified in clause 4.2.7.2.3.

4.2.7.3 AMF Failure or Planned Maintenance handling procedure p. 100

For UE(s) in CM-CONNECTED state:

If AMF failure is detected by 5G-AN, all NGAP UE TNLA binding for UEs served by that AMF are released.
If AMF becomes unavailable due to planned maintenance, the AMF notifies the 5G-AN about the unavailable GUAMI(s) and provides optionally a target AMF Name corresponding to each unavailable GUAMI. The 5G-AN releases all NGAP UE TNLA binding of the UEs related to the indicated unavailable GUAMI(s) unless the notification from the AMF includes an indicator that the AMF will rebind or release the NGAP UE TNLA binding on a per UE-basis. In that case, if 5G-AN supports, the 5G-AN waits the release until the timer expires so that the AMF may release or rebind the N2AP UE-TNLA binding on per UE-basis.
For the release NGAP TNLA binding, the affected UE is kept in CM-CONNECTED state and the corresponding N3 interface is also kept.

For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI, the 5G-AN uses 5G S-TMSI or GUAMI to select the target AMF, the 5G-AN forwards N2 message.

4.2.7.4 Additional User Location Information with Mobile Base Station Relay (MBSR) |R18| p. 101

As described in clause 5.35A of TS 23.501, when a UE is being served by an MBSR, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 parameters shall also include the additional ULI of this MBSR.

When the AMF provides user location information to other NFs (e.g. LMF as specified in clause 5.9 of TS 23.273) for a UE connected via MBSR, the AMF may also send the Additional ULI received via N2 messages.

4.2.8 Void

4.2.8a UE Capability Match Request procedure p. 101

If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3 of TS 23.501), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used during the registration procedure or when AMF has not received the Voice Support Match Indicator (as part of the 5GMM Context).

Reproduction of 3GPP TS 23.502, Fig. 4.2.8a-1: UE Capability Match Request

Figure 4.2.8a-1: UE Capability Match Request

Step 1.

The AMF indicates whether the AMF wants to receive Voice support match indicator. The AMF may include the UE radio capability information it has previously received from NG-RAN.

Step 2.

Upon receiving the UE Capability Match Request message, if the NG-RAN has not already received the UE radio capabilities from the UE or from AMF in step 1, the NG-RAN requests the UE to upload the UE radio capability information.

Step 3.

The UE provides the NG-RAN with its UE radio capabilities sending the RRC UE Capability Information.

Step 4.

The NG-RAN checks whether the UE radio capabilities are compatible with the network configuration for ensuring voice service continuity of voice calls initiated in IMS.

For determining the appropriate UE Radio Capability Match Response, the NG-RAN is configured by the operator to check whether the UE supports certain capabilities required for Voice continuity of voice calls using IMS PS. In a shared network, the NG-RAN keeps a configuration separately per PLMN.

The NG-RAN provides a Voice Support Match Indicator to the AMF to indicate whether the UE capabilities and networks configuration are compatible for ensuring voice service continuity of voice calls initiated in IMS.

The AMF stores the received Voice support match indicator in the 5GMM Context and uses it as an input for setting the IMS voice over PS Session Supported Indication.

Step 5.

If NG-RAN requested radio capabilities from UE in step 2 and 3, the NG-RAN also sends the UE radio capabilities to the AMF. The AMF stores the UE radio capabilities without interpreting them for further provision to the NG-RAN according to clause 5.4.4.1 of TS 23.501.