6.1.8 Feature Negotiation

29.5183GPP5G SystemAccess and Mobility Management ServicesRelease 18Stage 3TS

The feature negotiation mechanism specified in clause 6.6 of 3GPP TS 29.500 [4] shall be used to negotiate the optional features applicable between the AMF and the NF Service Consumer, for the Namf_Communication service, if any.

The NF Service Consumer shall indicate the optional features it supports for the Namf_Communication service, if any, by including the supportedFeatures attribute in payload of the HTTP Request Message for following service operations:

– N1N2MessgeTransfer, as specified in clause 5.2.2.3.1;

– N1N2MessageSubscribe, as specified in clause 5.2.2.3.3;

– NonUeN2InfoSubscribe, as specified in clause 5.2.2.4.2;

– UeContextTransfer, as specified in clause 5.2.2.2.1;

– CreateUEContext, as specified in clause 5.2.2.2.3

The AMF shall determine the supported features for the service operations as specified in clause 6.6 of 3GPP TS 29.500 [4] and shall indicate the supported features by including the supportedFeatures attribute in payload of the HTTP response for the service operation.

The syntax of the supportedFeatures attribute is defined in clause 5.2.2 of 3GPP TS 29.571 [6].

The following features are defined for the Namf_Communication service.

Table 6.1.8-1: Features of supportedFeatures attribute used by Namf_Communication service

Feature Number

Feature

M/O

Description

1

DTSSA

O

Deployments Topologies with specific SMF Service Areas.

An AMF that supports this feature shall support the procedures specified in clause 5.34 of 3GPP TS 23.501 [2] and in clause 4.23 of 3GPP TS 23.502 [3].

2

ENS

O

This feature bit indicates whether the AMF supports procedures related to Network Slicing (see 3GPP TS 23.501 [2] clause 5.15.7). This includes supporting the RelocateUEContext service operation (see clause 5.2.2.2.5).

3

CIOT

O

Cellular IoT

Support of this feature implies the support of all the CIoT features specified in clause 5.31 of 3GPP TS 23.501 [2], including in particular corresponding service’s extensions to support:

– NB-IoT and LTE-M RAT types;

– Control Plane CIoT 5GS Optimisation;

– Rate control of user data.

4

MAPDU

O

This feature bit indicates whether the AMF supports Multi-Access PDU session procedures related to Access Traffic Steering, Switching and Splitting (see clauses 4.2.10 and 5.32 of 3GPP TS 23.501 [2]).

5

NPN

O

Non-Public Network

Support of this feature implies support of NPN information and receipt of a Create UE context error response with a binary part during an Inter-AMF N2 Handover.

6

ELCS

O

This feature indicates supports of enhanced LCS, including the capability for the AMF to send an LCS message through the target access type requested by the LMF.

7

ES3XX

M

Extended Support of HTTP 307/308 redirection

An NF Service Consumer (e.g. SMF) that supports this feature shall support handling of HTTP 307/308 redirection for any service operation of the Namf_Communication service. An NF Service Consumer that does not support this feature does only support HTTP redirection as specified for 3GPP Release  15.

8

EAEA

O

EBI and ARP mapping update in EBIAssignment

Support of this feature implies support of updating the mapping of EBI and ARP in EBIAssignment for a QoS flow to which an EBI is already allocated.

9

ProSe

O

This feature indicates the support of UE policy and N2 information provisioning for 5G ProSe.

10

UAV

O

Uncrewed Aerial Vehicle

This feature indicates the support of UAV feature at AMF. When this feature is supported at the AMF, the AMF shall perform the UUAA-MM procedure defined in 3GPP TS 23.256 [56].

11

SPAE

O

SM Policy Association Events

This feature bit indicates whether the AMF supports the SM Policy Association establishment and termination event notification information handling, i.e. whereby the PCF for UE subscribes to SM Policy Association events to the PCF for SM Policy via the AMF and SMF, as specified in clause 4.3.2.2.1 and clause 4.3.3.2 of 3GPP TS 23.502 [3].

12

eNPN

O

Enhanced support of Non-Public Networks (eNPN)

This feature indicates the AMF supports UE registration for onboarding in an SNPN, see clause 5.30.2.10.2.6 and clause 5.30.2.10.2.7 in 3GPP TS 23.501 [2]).

13

3GA-N3GA-HO

O

Handover between 3GPP and non-3GPP accesses

An AMF and SMF that supports Handover between 3GPP and non-3GPP accesses shall support this feature, i.e. setting the targetAccess IE in N1N2MessageTransfer Request to the old access type when releasing the N2 PDU session resources in the old access (see clauses 5.2.2.3.1.1 and 6.1.6.2.18)

Feature number: The order number of the feature within the supportedFeatures attribute (starting with 1).

Feature: A short name that can be used to refer to the bit and to the feature.

M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").

Description: A clear textual description of the feature.