Octets

8

7

6

5

4

3

2

1

1 to 2

Type = 43 (decimal)

3 to 4

Length = n

5 to 6

Supported-Features

7 to 8

Additional Supported-Features 1

9 to 10

Additional Supported-Features 2

11 to 12

Additional Supported-Features 3

13 to (n+4)

These octet(s) is/are present only if explicitly specified

5/1

BUCP

Sxa, N4

O

(NOTE 2)

Downlink Data Buffering in CP function is supported by the UP function.

5/2

DDND

Sxa, N4

O

The buffering parameter ‘Downlink Data Notification Delay’ is supported by the UP function.

5/3

DLBD

Sxa, N4

O

The buffering parameter ‘DL Buffering Duration’ is supported by the UP function.

5/4

TRST

Sxb, Sxc, N4

O

Traffic Steering is supported by the UP function.

5/5

FTUP

Sxa, Sxb, N4

M

F-TEID allocation / release in the UP function is supported by the UP function.

5/6

PFDM

Sxb, Sxc, N4

O

The PFD Management procedure is supported by the UP function.

5/7

HEEU

Sxb, Sxc, N4

O

Header Enrichment of Uplink traffic is supported by the UP function.

5/8

TREU

Sxb, Sxc, N4

O

(NOTE 3)

Traffic Redirection Enforcement in the UP function is supported by the UP function.

6/1

EMPU

Sxa, Sxb, N4

M

Sending of End Marker packets supported by the UP function.

6/2

PDIU

Sxa, Sxb, Sxc, N4, N4mb

O

(NOTE 4)

Support of PDI optimised signalling in UP function (see clause 5.2.1A.2).

6/3

UDBC

Sxb, Sxc, N4

O

Support of UL/DL Buffering Control

6/4

QUOAC

Sxb, Sxc, N4

O

The UP function supports being provisioned with the Quota Action to apply when reaching quotas.

6/5

TRACE

Sxa, Sxb, Sxc, N4

O

The UP function supports Trace (see clause 5.15).

6/6

FRRT

Sxb, N4

O

The UP function supports Framed Routing (see IETF RFC 2865 [37] and IETF RFC 3162 [38]).

6/7

PFDE

Sxb, N4

O

The UP function supports a PFD Contents including a property with multiple values.

6/8

EPFAR

Sxa, Sxb, Sxc, N4

O

The UP function supports the Enhanced PFCP Association Release feature (see clause 5.18).

7/1

DPDRA

Sxb, Sxc, N4

O

The UP function supports Deferred PDR Activation or Deactivation.

7/2

ADPDP

Sxa, Sxb, Sxc, N4

O

The UP function supports the Activation and Deactivation of Pre-defined PDRs (see clause 5.19).

7/3

UEIP

Sxb, N4

O

(NOTE 5)

The UP function supports allocating UE IP addresses or prefixes (see clause 5.21).

7/4

SSET

N4, N4mb

O

(MB-)UPF support of PFCP sessions successively controlled by different (MB-)SMFs of a same (MB-)SMF Set (see clause 5.22).

7/5

MNOP

Sxa, Sxb, Sxc, N4

O

The UP function supports measurement of number of packets which is instructed with the flag ‘Measurement of Number of Packets’ in a URR. See also clause 5.2.2.2.1.

7/6

MTE

N4

O

UPF supports multiple instances of Traffic Endpoint IDs in a PDI.

7/7

BUNDL

Sxa, Sxb, Sxc, N4, N4mb

O

PFCP messages bundling (see clause 6.5) is supported by the UP function.

7/8

GCOM

N4

O

UPF support of 5G VN Group Communication. (See clause 5.23)

8/1

MPAS

N4, N4mb

O

(MB-)UPF support for multiple PFCP associations to the (MB-)SMFs in an (MB-)SMF set (see clause 5.22.3).

8/2

RTTL

N4

O

UPF supports redundant transmission at transport layer.

8/3

VTIME

Sxb,N4

O

UP function support of quota validity time feature.

8/4

NORP

Sxa, Sxb, Sxc, N4

O

UP function support of Number of Reports as specified in clause 5.2.2.2.

8/5

IPTV

N4

O

UPF support of IPTV service (see clause 5.25)

8/6

IP6PL

N4

O

UPF supports:

– UE IPv6 address(es) allocation with IPv6 prefix length other than default /64 (including allocating /128 individual IPv6 addresses), as specified in clause 4.6.2.2 of of 3GPP TS 23.316 [57]; and

– multiple UE IPv6 addresses allocation using multiple instances of the UE IP Address IE in a same PDI or Traffic Endpoint, or using multiple PDIs or Traffic Endpoints with a different UE IP Address as specified in clause 5.21.1.

8/7

TSCU

N4

O

Time Sensitive Communication is supported by the UPF (see clause 5.26).

8/8

MPTCP

N4

O

UPF support of MPTCP Proxy functionality (see clause 5.20)

9/1

ATSSS-LL

N4

O

UPF support of ATSSS-LLL steering functionality (see clause 5.20)

9/2

QFQM

N4

O

UPF support of per QoS flow per UE QoS monitoring (see clause 5.24.4).

9/3

GPQM

N4

O

UPF support of per GTP-U Path QoS monitoring (see clause 5.24.5).

9/4

MT-EDT

Sxa

O

SGW-U support of reporting the size of DL Data Packets. (see clause 5.2.4.1).

9/5

CIOT

Sxb, N4

O

UP function support of CIoT feature, e.g. small data packet rate enforcement. (see 5.4.15)

9/6

ETHAR

N4

O

UPF support of Ethernet PDU Session Anchor Relocation (see clause 5.13.6).

9/7

DDDS

N4

O

UPF support of reporting the first buffered / first discarded downlink data after buffering / directly dropped downlink data for downlink data delivery status notification.

9/8

RDS

Sxb, N4

O

UP function support of Reliable Data Service (see clause 5.29).

10/1

RTTWP

N4

O

UPF support of RTT measurements towards the UE Without PMF.

10/2

QUASF

Sxb, Sxc, N4

O

The UP function supports being provisioned in a URR with an Exempted Application ID for Quota Action or an Exempted SDF Filter for Quota Action which is to be used when the quota is exhausted. See also clauses 5.2.2.2.1 and 5.2.2.3.1.

10/3

NSPOC

Sxa, Sxb, N4

O

UP function supports notifying start of Pause of Charging via user plane.

10/4

L2TP

Sxb, N4

O

UP function supports the L2TP feature as described in clause 5.31.

10/5

UPBER

N4

O

UP function supports the uplink packets buffering during EAS relocation.

10/6

RESPS

Sxb, N4

O

UP function supports Restoration of PFCP Sessions associated with one or more PGW-C/SMF FQ-CSID(s), Group Id(s) or CP IP address(es) (see clause 5.22.4)

10/7

IPREP

N4

O

UP function supports IP Address and Port number replacement (see clause 5.33.3).

10/8

DNSTS

N4

O

UP function support DNS Traffic Steering based on FQDN in the DNS Query message (see clause 5.33.4)

11/1

DRQOS

N4

O

UP function supports Direct Reporting of QoS monitoring events to Local NEF or AF (see clause 5.33.5).

11/2

MBSN4

N4

O

UPF supports sending MBS multicast session data to associated PDU sessions using 5GC individual delivery.

11/3

PSUPRM

N4, N4mb

O

UP function supports Per Slice UP Resource Management (see clause 5.35).

11/4

EPPPI

N4

O

UP function supports Enhanced Provisioning of Paging Policy Indicator feature as specified in clause 5.36.2.

11/5

RATP

Sxb, N4

O

UP function supports Redirection Address Types set to "Port", "IPv4 address and Port", "IPv6 address and Port", or "IPv4 and IPv6 addresses and Port".

11/6

UPIDP

N4

O

UP function supports User Plane Inactivity Detection and reporting per PDR feature as specified in clause 5.11.3.

NOTE 1: Features are defined as follows:

– Feature Octet / Bit: The octet and bit number within the Supported-Features IE, e.g. "5 / 1".

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

– Interface: A list of applicable interfaces to the feature.

– M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") for a UP function complying with this release of the specification.
A feature defined as mandatory in this release of the specification may not necessarily be defined or mandatory to support in earlier releases (see the respective specifications), therefore a CP function complying with this release of the specification shall be prepared to receive a UP Function Features IE with a mandatory feature bit set to "0".

– Description: A clear textual description of the feature.

NOTE 2: Downlink data should be buffered preferably in the UP function. Downlink data may be buffered in the CP function when desired, e.g. for UEs using power saving methods.

NOTE 3: If the traffic that the UP function can support may be subject to traffic redirection, traffic redirection enforcement in the UP function shall be supported by the UP function.

NOTE 4: CP and UP functions complying with this release of the specification should support this feature.

NOTE 5: A UPF that supports the SSET or MPAS feature shall support this feature.