1

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 SMF PDUSession service’s extensions to support:

– NB-IoT and LTE-M RAT types;

– Control Plane CIoT 5GS Optimisation;

– Rate control of user data;

– Idle mode mobility with data forwarding between EPS and 5GS using N26 interface.

The SMF shall indicate its support of this feature in supportedFeatures attribute in its profile registered in NRF.

A NF service consumer (e.g. AMF) shall only select SMF(s) that supports this feature for PDU sessions with Control Plane CIoT 5GS Optimisation enabled.

2

MAPDU

O

Multi-Access PDU Session

An SMF that supports this feature shall support the procedures specified in3GPP TS 23.501 [2] and 3GPP TS 23.502 [3] related to Access Traffic Steering, Switching and Splitting.

3

DTSSA

O

Deployments Topologies with specific SMF Service Areas

A NF Service Consumer and an SMF that support 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].

4

CARPT

O

SMF derived CN Assisted RAN parameters Tuning.

A NF Service Consumer (e.g. AMF) and an SMF that support this feature shall support exchanging SMF derived CN assisted RAN parameters in Notify SM Context Status service operation (see clause 5.2.2.5.1).

5

CTXTR

O

This feature bit indicates whether the NF Service Consumer (e.g. AMF) and SMF supports Network Function/NF Service Context Transfer Procedures specified in clause 4.26 of 3GPP TS 23.502 [3].

The SMF shall only trigger these context transfer procedures if the NF Service Consumer has indicated support of this feature.

6

VQOS

O

VPLMN QoS

An SMF that supports this feature shall support:

– the handling of QoS constraints from the VPLMN during a HR PDU session establishment as specified in clause 4.3.2.2.2 of 3GPP TS 23.502 [3]; and

– QoS modification requests initiated by the VPLMN, as specified in clause 4.3.3.3 of 3GPP TS 23.502 [3].

7

HOFAIL

M

This feature bit indicates whether the NF Service Consumer (e.g. AMF, V-SMF, I-SMF) and SMF supports the Notify (SM Context) Status procedure to indicate a handover failure with the ResourceStatus set to "UPDATED" between 3GPP access and non-3GPP access as specified in clauses 5.2.2.5.1 and 5.2.2.10.1.

The SMF shall only trigger such a resource status notify procedure if the NF Service Consumer has indicated support of this feature.

8

ES3XX

M

Extended Support of HTTP 307/308 redirection

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

9

DCE2ER

O

Dual Connectivity based end to end Redundant User Plane Paths

An NF service consumer (e.g. I-SMF) and SMF that supports this feature shall support the procedures specified in clause 5.33.2.1 of 3GPP TS 23.501 [2].

10

AASN

M

This feature bit indicates whether the NF Service Consumer (e.g. AMF) and the SMF support the Notify SM Context Status procedure to indicate that the PDU session is established towards an alternative anchor SMF, as specified in clause 5.2.2.5.1.

The SMF shall only trigger such a Notify SM Context Status procedure if the NF Service Consumer has indicated support of this feature.

18

ACSCR

O

Absence of smfUri and hSmfUri attributes in Create SM Context Request for procedures with I-SMF/V-SMF insertion/change other than PDU session establishment and EPS to 5GS mobility procedures.

This feature bit indicates that the NF Service Consumer (e.g. AMF) supports not including, and the I-SMF/V-SMF supports not receiving, the smfUri and hSmfUri attributes in the Create SM Context request in procedures with I-SMF/V-SMF insertion/change other than PDU session establishment and EPS to 5GS mobility procedures.

The support of this feature may remove the need for the AMF to fetch the smfUri or hsmfUri from the NRF where the anchor SMF profile is registered, and accordingly, to fasten the execution of mobility (e.g. handover) scenarios.

19

PSETR

O

This feature bit indicates that the SMF is able to (re)select an alternative peer SMF (when available) when it detects the peer SMF has failed. See also clause 6.8 in 3GPP TS 23.527 [24].

20

DLSET

O

This feature bit indicates that the PDU session resources served by the SMF are not exclusively bound to a SMF service instance, i.e. they are shared by multiple SMF service instances. See also clause 6.8 in 3GPP TS 23.527 [24].

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.