Sxa

Sxb

Sxc

N4

N4mb

Node ID

M

This IE shall contain the unique identifier of the sending Node.

X

X

X

X

X

Node ID

CP F-SEID

M

This IE shall contain the unique identifier allocated by the CP function identifying the session.

X

X

X

X

X

F-SEID

Create PDR

M

This IE shall be present for at least one PDR to be associated to the PFCP session.

Several IEs with the same IE type may be present to represent multiple PDRs.

See Table 7.5.2.2-1.

X

X

X

X

X

Create PDR

Create FAR

M

This IE shall be present for at least one FAR to be associated to the PFCP session.

Several IEs with the same IE type may be present to represent multiple FARs.

See Table 7.5.2.3-1.

X

X

X

X

X

Create FAR

Create URR

C

This IE shall be present if a measurement action shall be applied to packets matching one or more PDR(s) of this PFCP session.

Several IEs within the same IE type may be present to represent multiple URRs.

See Table 7.5.2.4-1.

X

X

X

X

–

Create URR

Create QER

C

This IE shall be present if a QoS enforcement or QoS marking action shall be applied to packets matching one or more PDR(s) of this PFCP session.

Several IEs within the same IE type may be present to represent multiple QERs.

See Table 7.5.2.5-1.

–

X

X

X

X

Create QER

Create BAR

O

When present, this IE shall contain the buffering instructions to be applied by the UP function to any FAR of this PFCP session set with the Apply Action requesting the packets to be buffered and with a BAR ID IE referring to this BAR. See table 7.5.2.6-1.

X

–

–

X

–

Create BAR

Create Traffic Endpoint

C

This IE may be present if the UP function has indicated support of PDI optimization.

Several IEs within the same IE type may be present to represent multiple Traffic Endpoints.

See Table 7.5.2.7-1.

X

X

X

X

X

Create Traffic Endpoint

PDN Type

C

This IE shall be present if the PFCP session is setup for an individual PDN connection or PDU session (see clause 5.2.1).

When present, this IE shall indicate whether this is an IP or non-IP PDN connection/PDU session or, for 5GC, an Ethernet PDU session. See NOTE 3.

X

X

–

X

–

PDN Type

SGW-C FQ-CSID

C

This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24].

X

X

–

–

–

FQ-CSID

MME FQ-CSID

C

This IE shall be included when received on the S11 interface or on S5/S8 interface according to the requirements in clause 23 of 3GPP TS 23.007 [24].

X

X

–

–

–

FQ-CSID

PGW-C/SMF FQ-CSID

C

This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24] and clause 4.6 of 3GPP TS 23.527 [40].

X

X

–

X

–

FQ-CSID

ePDG FQ-CSID

C

This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24].

–

X

–

–

–

FQ-CSID

TWAN FQ-CSID

C

This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24].

–

X

–

–

–

FQ-CSID

User Plane Inactivity Timer

O

This IE may be present to request the UP function to send a User Plane Inactivity Report when no user plane packets are received for this PFCP session for a duration exceeding the User Plane Inactivity Timer.

When present, it shall contain the duration of the inactivity period after which a User Plane Inactivity Report shall be generated.

–

X

X

X

X

User Plane Inactivity Timer

User ID

O

This IE may be present, based on operator policy. It shall only be sent if the UP function is in a trusted environment.

See NOTE 1.

X

X

X

X

–

User ID

Trace Information

O

When present, this IE shall contain the trace instructions to be applied by the UP function for this PFCP session.

X

X

X

X

–

Trace Information

APN/DNN

O

This IE may be present, if related functionalities in the UP function require the APN/DNN information. See NOTE 2.

X

X

–

X

X

APN/DNN

Create MAR

C

This IE shall be present for a N4 session established for a MA PDU session.

Several IEs with the same IE type may be present to represent multiple MARs.

See Table 7.5.2.8-1.

–

–

–

X

–

Create MAR

PFCPSEReq-Flags

C

This IE shall be included if at least one of the flags is set to "1".

– RESTI (Restoration Indication): this bit shall be set to "1" if the CP function re-establishes an existing PFCP session and the allocation of GTP-U F-TEID and/or UE IP address is performed by the UP function. (NOTE 4)

– SUMPC (Stop Usage Measurement to Pause Charging): the CP function, e.g. PGW-C or (H-)SMF, shall set this flag if the usage measurement for the URRs which are applicable for charging (i.e. with the "ASPOC" flag set to "1") shall be stopped in the UP function.

X

X

–

X

–

PFCPSEReq-Flags

Create Bridge Info for TSC

C

This IE shall be present for a PFCP session established for TSC to request the UPF to provide Bridge information for TSC.

–

–

–

X

–

Create Bridge Info for TSC

Create SRR

O

This IE may be present to request the UPF to detect and report events not related to specific PDRs.

Several IEs within the same IE type may be present to represent multiple SRRs.

See Table 7.5.2.9-1.

–

–

–

X

–

Create SRR

Provide ATSSS Control Information

C

This IE shall be present for N4 session establishment for a MA PDU session.

When present, this IE shall contain the required ATSSS functionalities for this MA PDU session.

See Table 7.5.2.10-1.

–

–

–

X

–

Provide ATSSS Control Information

Recovery Time Stamp

O

This IE may be included to contain the time stamp when the CP function was started. (See clause 19A of 3GPP TS 23.007 [24].)

X

X

X

X

–

Recovery Time Stamp

S-NSSAI

O

This IE may be present, if related functionalities in the UP function require the S-NSSAI information. (NOTE 2, NOTE 5)

When present, it shall indicate the S-NSSAI of the PDU session or MBS session.

–

–

–

X

X

S-NSSAI

Provide RDS configuration information

O

When present, this IE shall contain the RDS configuration information to be applied by the UP function for this PFCP session.

–

X

–

X

–

Provide RDS configuration information

RAT Type

O

This IE may be present to provide the UP Function the current RAT Type for the PDN connection/PDU session to which this PFCP Session is corresponding for statistics purpose if the PFCP session is not established for a MA PDU session.

X

X

–

X

–

RAT Type

L2TP Tunnel Information

C

This IE shall be present if L2TP tunnel information is received from an AAA server, e.g. Radius/Diameter server or if it is configured in the CP function.

Several IE with the same IE type may be present to provide L2TP Tunnel Information for alternative LNS.

–

X

–

X

–

L2TP Tunnel Information

L2TP Session Information

C

This IE shall be present to include the information to establish a L2TP session, if an L2TP session needs to be established for this PFCP session.

–

X

–

X

–

L2TP Session Information

Group Id

O

This IE may be included by the CP function to indicate the group identifier to which the PFCP session pertains (see clause 5.22).

–

X

–

X

–

Group Id

MBS Session N4mb Control Information

M

This IE shall identify the MBS session, or the MBS session and Area Session ID for a location dependent MBS service, and it may contain further control information for the MB-UPF.

–

–

–

–

X

MBS Session N4mb Control Information

MBS Session N4 Control Information

C

This IE shall be included if the correspond PDU session shall be associated with an MBS session, or with an MBS session and Area Session ID for a location dependent MBS service.

Several IEs with the same IE type may be present to provide N4 control information for several MBS sessions, e.g., when the UE requests to join several MBS sessions.

–

–

–

X

–

MBS Session N4 Control Information

DSCP to PPI Control Information

O

This IE may be present if the UPF is required to insert the Paging Policy Indicator (PPI) in the GTP-U PDU Session Container extension header of outgoing GTP-U packets (encapsulating payload packets) based on the DSCP in the TOS/Traffic Class field in the IP header of payload packet and if the UPF supports the EPPPI feature as specified in clause 5.36.2.

Several IEs with the same IE type may be present to provide different DSCP to PPI Control Information for different set of QFI(s).

–

–

–

X

–

DSCP to PPI Control Information

NOTE 1: This can be used for troubleshooting problems in the UP function affecting a subscriber.

NOTE 2: The CP function may provide additional information (e.g. APN/DNN, S-NSSAI) to the UP function, e.g. used by the forwarding rules pre-defined in UP function (some forwarding rules are APN specific), used by the UP function for performance measurement, used by the UP function for resource management, or used by the UPF to include a proper User plane node/Bridge ID in the response message during a PFCP session establishment for a PDU session for TSC.

NOTE 3: The SGW-C may set PDN type as Non-IP for an Ethernet PDN to allow interworking with a legacy SGW-U.

NOTE 4: The UP function shall accept the CP function allocated GTP-U F-TEID and/or UE IP address in the PFCP Session Establishment Request message with the RESTI flag set to "1", if the requested GTP-U F-TEID and/or UE IP address are available. If the GTP-U F-TEID or UE IP address provided by the CP function is not available at the UP function, the UP function shall reject the PFCP Session Establishment Request with the cause "PFCP session restoration failure due to requested resource not available" (see clause 8.2.1).

NOTE 5: A UPF shall support allocating resources using the Network Instance IE and the UPF may additionally support allocating resources using the Network Instance IE and S-NSSAI IE (see clause 5.35).

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

LNS Address

M

This IE shall be present to include the Tunnel Server Endpoint, i.e. LNS IP address.

–

X

–

X

–

LNS Address

Tunnel Password

O

This IE may be present to include the password to be used to authenticate to a remote server.

–

X

–

X

–

Tunnel Password

Tunnel Preference

C

This IE shall be present if multiple L2TP Tunnel Information IEs are included in the message.

If present this IE indicates the order in which the L2TP Tunnel Information IEs shall be used when trying to establish the L2TP session.

–

X

–

X

–

Tunnel Preference

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Calling Number

O

This IE may be present, e.g. to include an MSISDN of the UE.

–

X

–

X

–

Calling Number

Called Number

O

This IE may be present, e.g. to include an APN/DNN.

–

X

–

X

–

Called Number

Maximum Receive Unit

O

This IE may be present to include Maximum Receive Unit for LCP/PPP which may be set to the value of the MTU received from the UE or may be configured in the CP function.

–

X

–

X

–

Maximum Receive Unit

L2TP Session Indications

C

This IE shall be present if the CP function requests the UP function to get a UE IP Address, and/or DNS server information, and/or NBNS server information from the LNS.

–

X

–

X

–

L2TP session Indications

L2TP User Authentication

O

This IE may be present to include the authentication information to be used during L2TP session establishment.

–

X

–

X

–

L2TP User Authentication

NOTE: The Tunnel Password and L2TP User Authentication IE are transferred with plain text, a Network Domain Security/IP based security mechanism may be deployed between the CP function and the UP function if required by the local policies.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MBS Session Identifier

M

–

–

–

–

X

MBS Session Identifier

Area Session ID

C

This IE shall be present for a location dependent MBS service. When present, it shall contain the Area Session ID, which together with the MBS Session Identifier, uniquely identify the service area part of the content data of the MBS service.

–

–

–

–

X

Area Session ID

MBSN4mbReq-Flags

C

This IE shall be included if at least one of the flags is set to "1".

– PLLSSM (Provide Lower Layer SSM): the MB-SMF shall set this flag to "1" to request the MB-UPF to allocate a LL SSM (i.e. multicast destination address and related source IP address) and a GTP-U Common Tunnel EndPoint Identifier (C-TEID), if multicast transport is used over N3mb and/or N19mb. See clause 5.34.2.2.

– JMBSSM (Join MBS Session SSM): the MB-SMF shall set this flag to "1" to request the MB-UPF to join the multicast tree towards the Source Specific Multicast (SSM) address information provided by AF/AS for the MBS Session, if multicast transport is used over N6mb.

– MBS RESTI (MBS Restoration Indication): this bit shall be set to "1" if the MB-SMF re-establishes an existing PFCP session. (NOTE)

–

–

–

–

X

MBSN4mbReq-Flags

Multicast Transport Information for N3mb and/or N19mb

C

This IE shall be present during the restoration of a PFCP session of an MBS session after an MB-UPF restart, as defined in clause 8.2.2 of 3GPP TS 23.527 [40].

When present, it shall include the low layer source specific multicast address information (i.e. multicast destination address and related source IP address) and the GTP-U Common Tunnel EndPoint Identifier (C-TEID) that the MB-SMF requests the MB-UPF to allocate for multicast transport over N3mb and/or N19mb, if possible.

(NOTE)

–

–

–

–

X

Multicast Transport Information

NOTE: The MB-UPF shall accept the MB-SMF allocated N3mb/N19mb and/or the N6mb/Nmb9 address in the PFCP Session Establishment Request message with the MBS RESTI flag set to "1", if the requested addresses are available. If one requested address is not available at the MB-UPF, the MB-UPF shall reject the PFCP Session Establishment Request with the cause "PFCP session restoration failure due to requested resource not available" (see clause 8.2.1).

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MBS Session Identifier

M

–

–

–

X

–

MBS Session Identifier

Area Session ID

C

This IE shall be present for a location dependent MBS service. When present, it shall contain the Area Session ID, which together with the MBS Session Identifier, uniquely identify the service area part of the content data of the MBS service.

–

–

–

X

–

Area Session ID

Multicast Transport Information

C

This IE shall be present to include a low layer source specific multicast address information (i.e. multicast destination address and related source IP address) and a GTP-U Common Tunnel EndPoint Identifier (C-TEID) which was allocated by the MB-UPF, if IP multicast transport is used over N19mb.

–

–

–

X

–

Multicast Transport Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

DSCP to PPI Mapping Information

M

This IE shall be present to instruct the UPF to insert the corresponding PPI for the downlink GTP-U packet, where the DSCP of its payload packet is matching one of DSCP codes in the DSCP to PPI Mapping Information.

Several IEs with the same IE type may be present to provide different DSCP to PPI mapping information.

–

–

–

X

–

DSCP to PPI Mapping Information

QFI

O

This IE may be present to request the UPF to only insert PPI for those packets pertain to the requested QoS flow(s).

Several IEs with the same IE type may be present to provide a list of QFIs.

(NOTE 1)

–

–

–

X

–

QFI

NOTE 1: The absence of QFI(s) indicates that insertion of the corresponding PPI shall be applied for all DL packets (matching the DSCP(s) of the DSCP to PPI Mapping Information IE) pertaining to all QoS flows of the PFCP session.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

PDR ID

M

This IE shall uniquely identify the PDR among all the PDRs configured for that PFCP session.

X

X

X

X

X

PDR ID

Precedence

M

This IE shall indicate the PDR’s precedence to be applied by the UP function among all PDRs of the PFCP session, when looking for a PDR matching an incoming packet.

–

X

X

X

X

Precedence

PDI

M

This IE shall contain the PDI against which incoming packets will be matched.

See Table 7.5.2.2-2.

X

X

X

X

X

PDI

Outer Header Removal

C

This IE shall be present if the UP function is required to remove one or more outer header(s) from the packets matching this PDR.

X

X

–

X

X

Outer Header Removal

FAR ID

C

This IE shall be present if the Activate Predefined Rules IE is not included or if it is included but it does not result in activating a predefined FAR, and if the MAR ID is not included. This IE may be present if the CP function activated a predefined rule name with a predefined FAR but the CP function wishes to overwrite the predefined FAR by another FAR. (NOTE 2)

When present this IE shall contain the FAR ID to be associated to the PDR.

X

X

X

X

X

FAR ID

URR ID

C

This IE shall be present if a measurement action shall be applied to packets matching this PDR.

When present, this IE shall contain the URR IDs to be associated to the PDR.

Several IEs within the same IE type may be present to represent a list of URRs to be associated to the PDR.

X

X

X

X

–

URR ID

QER ID

C

This IE shall be present if a QoS enforcement or QoS marking action shall be applied to packets matching this PDR.

When present, this IE shall contain the QER IDs to be associated to the PDR. Several IEs within the same IE type may be present to represent a list of QERs to be associated to the PDR.

–

X

X

X

X

QER ID

Activate Predefined Rules

C

This IE shall be present if Predefined Rule(s) shall be activated for this PDR. When present this IE shall contain one Predefined Rules name.

Several IEs with the same IE type may be present to represent multiple "Activate Predefined Rules" names.

–

X

X

X

–

Activate Predefined Rules

Activation Time

O

This IE may be present if the PDR activation shall be deferred. (NOTE 1)

–

X

X

X

–

Activation Time

Deactivation Time

O

This IE may be present if the PDR deactivation shall be deferred. (NOTE 1)

–

X

X

X

–

Deactivation Time

MAR ID

C

This IE shall be present if the PDR is provisioned to match the downlink traffic of non-GBR QoS flows towards the UE for a PFCP session established for a MA PDU session.

–

–

–

X

–

MAR ID

Packet Replication and Detection Carry-On Information

C

This IE shall be present if the PDR is provisioned to match a broadcast packet. When present, it contains the information to instruct the UPF to replicate the packet and to carry-on the look-up of other PDRs of other PFCP sessions matching the packet (see clause 5.2.1).

–

–

–

X

–

Packet Replication and Detection Carry-On Information

IP Multicast Addressing Info

O

This IE may be present in an UL PDR controlling UL IGMP/MLD traffic (see 5.25).

When present, it shall contain a (range of) IP multicast address(es), and optionally source specific address(es), identifying a set of IP multicast flows. See Table 7.5.2.2-4.

Several IEs with the same IE type may be present to represent multiple IP multicast flows.

–

–

–

X

–

IP Multicast Addressing Info

UE IP address Pool Identity

O

This IE may be present if UE IP Addresses Pools are configured in the UPF.

When present, this IE shall contain the identity of a UE IP address Pool configured in the UPF.

Two IEs with the same IE type shall be present to represent UE IPv4 Address Pool Identity and UE IPv6 Address Pool Identity if different pool identities are used for UE IPv4 address and UE IPv6 address and both an UE IPv4 and an UE IPv6 address are requested to be assigned for the PFCP session. In this case, the UE IPv4 Address Pool Identity shall be encoded before the UE IPv6 Address Pool Identity.

–

X

–

X

–

UE IP address Pool Identity

MPTCP Applicable Indication

C

This IE shall be present if the PDR is used to detect UL user plane traffic for which MPTCP is applicable.

–

–

–

X

–

MPTCP Applicable Indication

Transport Delay Reporting

C

This IE shall be present to request the UPF to add the delay of the GTP-U path with the preceding uplink GTP-U entity to the "N3/N9 Delay Result received in the GTP-U PDU Session Container extension header (see 3GPP TS 38.415 [34]) of the uplink packet, when monitoring the QoS of a PDU session based on GTP-U path monitoring (see clause 5.24.5.3). See Table 7.5.2.2-6.

–

–

–

X

–

Transport Delay Reporting

RAT Type

O

This IE may be present to provide the UP Function the current RAT Type for the UL PDR for statistics purpose if the PFCP session is established for a MA PDU session.

–

–

–

X

–

RAT Type

NOTE 1: When the Activation Time and Deactivation Time are not present, the PDR shall be activated immediately at receiving the message.

NOTE 2: If a predefined FAR is or has been activated using a predefined rule name, it is UP function implementation specific whether this predefined FAR can be overwritten by a FAR ID pointing to another predefined FAR (i.e. with the most significant bit set to 1). If not, the UP function shall reject such a request if received from the CP function.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Source Interface

M

This IE shall identify the source interface of the incoming packet.

X

X

X

X

X

Source Interface

Local F-TEID

O

This IE shall not be present if Traffic Endpoint ID is present.

If present, this IE shall identify the local F-TEID to match for an incoming packet.

The CP function shall set the CHOOSE (CH) bit to 1 if the CP function requests the UP function to assign a local F-TEID to the PDR.

X

X

–

X

–

F-TEID

Local Ingress Tunnel

C

This IE shall not be present if Traffic Endpoint ID is present.

If present, this IE shall identify the IP address and the UDP port for a UDP/IP tunnel.

The CP function shall set the CHOOSE (CH) bit to 1 if the CP function requests the UP function to assign a local ingress tunnel to the PDR.

–

–

–

–

X

Local Ingress Tunnel

Network Instance

O

This IE shall not be present if Traffic Endpoint ID is present. It shall be present if the CP function requests the UP function to allocate a UE IP address/prefix and the Traffic Endpoint ID is not present.

If present, this IE shall identify the Network instance to match for the incoming packet. See NOTE 1, NOTE2.

X

X

X

X

X

Network Instance

Redundant Transmission Detection Parameters

O

If present, this IE shall contain the information used for the reception of redundant uplink packets on N3/N9 interfaces.

–

–

–

X

–

Redundant Transmission Detection Parameters

UE IP address

O

This IE shall not be present if Traffic Endpoint ID is present.

If present, this IE shall identify the UE IP address as the source or destination IP address to match for the incoming packet. (NOTE 5).

The CP function shall set the CHOOSE IPV4 (CHV4) and/or the CHOOSE IPV6 (CHV6) bits to 1 if the UP function supports the allocation of UE IP address/ prefix and the CP function requests the UP function to assign a UE IP address/prefix to the PDR.

This IE may also present to identify the IP address of the CP function as the destination IP address to match for the incoming packet, e.g. Radius, Diameter or DHCP signalling packet. (NOTE 8).

In the 5GC, several IEs with the same IE type may be present to represent multiple UE IP addresses, if the UPF indicated support of the IP6PL feature (see clause 5.21).

–

X

X

X

–

UE IP address

Traffic Endpoint ID

C

This IE may be present if the UP function has indicated the support of PDI optimization.

If present, this IE shall uniquely identify the Traffic Endpoint for that PFCP session.

Several IEs with the same IE type may be present to provision several Traffic Endpoints with different Traffic Endpoint IDs, from which the UPF may receive packets pertaining to the same service data flow, which is subject for the same FAR, QER and URR, if the UPF has indicated it supports MTE feature as specified in clause 8.2.25. See NOTE 6.

X

X

X

X

X

Traffic Endpoint ID

SDF Filter

O

If present, this IE shall identify the SDF filter to match for the incoming packet. Several IEs with the same IE type may be present to provision a list of SDF Filters. The full set of applicable SDF filters, if any, shall be provided during the creation or the modification of the PDI.

See NOTE 3.

–

X

X

X

X

SDF Filter

Application ID

O

If present, this IE shall identify the Application ID to match for the incoming packet.

–

X

X

X

X

Application ID

Ethernet PDU Session Information

O

This IE may be present to identify all the (DL) Ethernet packets matching an Ethernet PDU session (see clause 5.13.1).

–

–

–

X

–

Ethernet PDU Session Information

Ethernet Packet Filter

O

If present, this IE shall identify the Ethernet PDU to match for the incoming packet.

Several IEs with the same IE type may be present to represent a list of Ethernet Packet Filters.

The full set of applicable Ethernet Packet filters, if any, shall be provided during the creation or the modification of the PDI.

–

–

–

X

–

Ethernet Packet Filter

QFI

O

This IE shall not be present if Traffic Endpoint ID is present and the QFI(s) are included in the Traffic Endpoint.

If present, this IE shall identify the QoS Flow Identifier to match for the incoming packet.

Several IEs with the same IE type may be present to provision a list of QFIs. When present, the full set of applicable QFIs shall be provided during the creation or the modification of the PDI.

–

–

–

X

–

QFI

Framed-Route

O

This IE may be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe a framed route.

Several IEs with the same IE type may be present to provision a list of framed routes. (NOTE 5)

–

X

–

X

–

Framed-Route

Framed-Routing

O

This IE may be present for a DL PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe the routing method for the UP function for the IP route related to Framed-Routes or Framed-IPv6-Routes. (NOTE 7)

–

X

–

X

–

Framed-Routing

Framed-IPv6-Route

O

This IE may be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe a framed IPv6 route.

Several IEs with the same IE type may be present to provision a list of framed IPv6 routes. (NOTE 5)

–

X

–

X

–

Framed-IPv6-Route

Source Interface Type

O

This IE may be present to indicate the 3GPP interface type of the source interface, if required by functionalities in the UP Function, e.g. for performance measurements.

X

X

–

X

X

3GPP Interface Type

IP Multicast Addressing Info

O

This IE may be present in a DL PDR controlling DL IP multicast traffic (see clause 5.25).

When present, it shall contain a (range of) IP multicast address(es), and optionally source specific address(es), identifying a set of IP multicast flows. See Table 7.5.2.2-4.

This IE shall be present over N4mb, if multicast transport is used over N6mb and if Traffic Endpoint ID is not present.

Several IEs with the same IE type may be present to represent multiple IP multicast flows.

–

–

–

X

X

IP Multicast Addressing Info

DNS Query Filter

O

This IE may be present for an UL PDR if the UPF indicated support of DNS traffic steering based on FQDN in the DNS Query message.

If present, this IE shall identify the DNS Query filter to match for the incoming DNS Query packets. Several IEs with the same IE type may be present to provision a list of DNS Query Filters. The full set of applicable DNS Query filters, if any, shall be provided during the creation or the modification of the PDI.

–

–

–

X

–

DNS Query Filter

MBS Session Identifier

C

This IE shall be present when the PDR is created to receive MBS session data. (NOTE 9)

–

–

–

X

–

MBS Session Identifier

Area Session ID

C

This IE shall be present for a location dependent MBS service. When present, it shall contain the Area Session ID, which together with the MBS Session Identifier, uniquely identify the service area part of the content data of the MBS service. (NOTE 9)

–

–

–

X

–

Area Session ID

NOTE 1: The Network Instance parameter is needed e.g. in the following cases:

– PGW/TDF UP function supports multiple PDNs with overlapping IP addresses;

– SGW UP function is connected to PGWs in different IP domains (S5/S8);

– PGW UP function is connected to SGWs in different IP domains (S5/S8);

– SGW UP function is connected to eNodeBs in different IP domains;

– UPF is connected to 5G-ANs in different IP domains;

– Separation of multiple 5G VN groups communication in the UPF;

– Indirect data forwarding.

NOTE 2: When a Local F-TEID is provisioned in the PDI, the Network Instance shall relate to the IP address of the F-TEID. Otherwise, the Network Instance shall relate to the UE IP address if provisioned or the destination IP address in the SDF filter if provisioned

NOTE 3: SDF Filter IE(s) shall not be present if Ethernet Packet Filter IE(s) is present.

NOTE 4: When several SDF filter IEs are provisioned, the UP function shall consider that the packets are matched if matching any SDF filter. The same principle shall apply for Ethernet Packet Filters and QFIs.

NOTE 5: If both the UE IP Address and the Framed-Route (or Framed-IPv6-Route) are present, the packets which are considered being matching the PDR shall match at least one of them.

NOTE 6: Maximum two Traffic Endpoint ID containing different Local TEIDs per PDI may be provisioned over the N4 interface for a PFCP session which is established for a PDU session subject for 5G to EPS mobility with N26 supported. Several Traffic Endpoint ID containing different UE IP Addresses may be provisioned over the N4 interface for a PFCP session if the UPF also indicated support of the IP6PL feature (see clause 5.21.1).

NOTE 7: In this release of specification, the UP function shall announce the IP route(s) for Framed-Route(s) or Framed-IPv6-Route(s) to the PDN regardless of the value of the Framed-Routing.

NOTE 8: The IP address of the CP function is needed e.g. perform Router Advertisements and match the destination IP address of the incoming packet if the Radius, Diameter or DHCP signaling packets between the SMF and the external DN is forwarded by the UPF.

NOTE 9: The Inclusion of the MBS Session Identifier, or MBS Session Identifier and Area Session ID for a location dependent MBS session, enables the UPF to allocate the same N19mb tunnel for the same MBS Session, or for the same MBS session and Area Session ID for a location dependent MBS session, when receiving multiple PFCP Session Establishment or Modification Request messages for different PFCP sessions being associated with the same MBS session, or with the same MBS session and Area Session ID for a location dependent MBS session, and also helps the UPF to identify the PFCP sessions associated with a MBS Session, or with the same MBS session and Area Session ID for a location dependent MBS session.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Ethernet Filter ID

C

This shall be present if Bidirectional Ethernet filter is required. This IE shall uniquely identify an Ethernet Filter among all the Ethernet Filters provisioned for a given PFCP session.

–

–

–

X

–

Ethernet Filter ID

Ethernet Filter Properties

C

This IE shall be present when provisioning a bidirectional Ethernet Filter the first time (see clause 5.13.4).

–

–

–

X

–

Ethernet Filter Properties

MAC address

O

If present, this IE shall identify the MAC address.

This IE may be present up to 16 times.

–

–

–

X

–

MAC address

Ethertype

O

If present, this IE shall identify the Ethertype.

–

–

–

X

–

Ethertype

C-TAG

O

If present, this IE shall identify the Customer-VLAN tag.

–

–

–

X

–

C-TAG

S-TAG

O

If present, this IE shall identify the Service-VLAN tag.

–

–

–

X

–

S-TAG

SDF Filter

O

If packet filtering is required, for Ethernet frames with Ethertype indicating IPv4 or IPv6 payload, this IE shall describe the IP Packet Filter Set.

Several IEs with the same IE type may be present to represent a list of SDF filters.

–

–

–

X

–

SDF Filter

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

IP Multicast Address

M

This IE shall contain the IP multicast address(es) of the DL multicast flow(s) or indicate "any" IP multicast address.

For N4mb, the IP Multicast Address shall be set to the value of IP Multicast Address in the SSM for the MBS Session.

–

–

–

X

X

IP Multicast Address

Source IP Address

O

When present, this IE shall contain the source specific IP address of the DL multicast flow.

Several IEs with the same IE type may be present to represent multiple source specific addresses.

If this IE is not present, this indicates "any" source IP address.

–

–

–

X

Source IP Address

M

This IE shall be set to the value of the IP Source Address in the SSM for the MBS Session.

–

–

–

–

X

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Local F-TEID for Redundant Transmission

M

This IE shall identify the local F-TEID to match for an incoming packet for redundant transmission.

The CP function shall set the CHOOSE (CH) bit to 1 if it requests the UP function to assign a local F-TEID to the PDR.

–

–

–

X

–

F-TEID

Network Instance for Redundant Transmission

C

This IE shall be included if the Local F-TEID for Redundant Transmission uses a different network Instance than the Network Instance used for the Local F-TEID for the primary GTP-U tunnel.

–

–

–

X

–

Network Instance

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Preceding UL GTP-U Peer

M

This IE shall identify the preceding UL GTP-U peer.

–

–

–

X

–

Remote GTP-U Peer

DSCP

O

If present, this IE shall contain the DSCP to use to measure the GTP-U path delay with the preceding UL GTP-U peer.

–

–

–

X

–

Transport Level Marking

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

FAR ID

M

This IE shall uniquely identify the FAR among all the FARs configured for that PFCP session.

X

X

X

X

X

FAR ID

Apply Action

M

This IE shall indicate the action to apply to the packets, See clauses 5.2.1 and 5.2.3.

X

X

X

X

X

Apply Action

Forwarding Parameters

C

This IE shall be present when the Apply Action requests the packets to be forwarded. It may be present otherwise.

When present, this IE shall contain the forwarding instructions to be applied by the UP function when the Apply Action requests the packets to be forwarded.

See table 7.5.2.3-2.

X

X

X

X

–

Forwarding Parameters

Duplicating Parameters

C

This IE shall be present when the Apply Action requests the packets to be duplicated. It may be present otherwise.

When present, this IE shall contain the forwarding instructions to be applied by the UP function for the traffic to be duplicated, when the Apply Action requests the packets to be duplicated.

Several IEs with the same IE type may be present to represent to duplicate the packets to different destinations. See NOTE 1.

See table 7.5.2.3-3.

X

X

–

–

–

Duplicating Parameters

BAR ID

O

When present, this IE shall contain the BAR ID of the BAR defining the buffering instructions to be applied by the UP function when the Apply Action requests the packets to be buffered.

X

–

–

X

–

BAR ID

Redundant Transmission Forwarding Parameters

C

This IE shall be present when the Apply Action requests the packets to be duplicated for redundant transmission and the Forwarding Parameters IE is included. It may be present otherwise.

When present, this IE shall contain the forwarding instructions to be applied by the UP function for the traffic to be duplicated, when the Apply Action requests the packets to be duplicated for redundant transmission. Except for the parameters included in the Redundant Transmission Parameters IE, the duplicated packets shall apply the same parameters as those indicated in the Forwarding Parameters IE.

See table 7.5.2.3-4.

–

–

–

–

–

Redundant Transmission Forwarding Parameters

MBS Multicast Parameters

C

This IE shall be present when the Apply Action is set to "FSSM". This requests the MB-UPF to forward the MBS session data to a Low Layer SSM.

–

–

–

–

X

MBS Multicast Parameters

Add MBS Unicast Parameters

C

This IE shall be present when the Apply Action is set to "MBSU". This requests the MB-UPF to forward the MBS session data to a remote GTP-U peer for unicast transport.

Several IEs with the same IE type may be present to request the MB-UPF to forward the MBS session data to multiple remote GTP-U peers.

–

–

–

–

X

Add MBS Unicast Parameters

NOTE 1: The same user plane packets may be required, according to operator’s policy and configuration, to be duplicated to different SX3LIFs.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Destination Interface

M

This IE shall identify the destination interface of the outgoing packet.

X

X

X

X

–

Destination Interface

Network Instance

O

When present, this IE shall identify the Network instance towards which to send the outgoing packet. See NOTE 1.

X

X

X

X

–

Network Instance

Redirect Information

C

This IE shall be present if the UP function is required to enforce traffic redirection towards a redirect destination provided by the CP function.

–

X

X

X

–

Redirect Information

Outer Header Creation

C

This IE shall be present if the UP function is required to add one or more outer header(s) to the outgoing packet. If present, it shall contain the F-TEID of the remote GTP-U peer when adding a GTP-U/UDP/IP header, or the Destination IP address and/or Port Number when adding a UDP/IP header or an IP header or the C-TAG/S-TAG (for 5GC). See NOTE 2.

X

X

–

X

–

Outer Header Creation

Transport Level Marking

C

This IE shall be present if the UP function is required to mark the IP header with the DSCP marking as defined by IETF RFC 2474 [22]. When present for EPC, it shall contain the value of the DSCP in the TOS/Traffic Class field set based on the QCI, and optionally the ARP priority level, of the associated EPS bearer, as described in clause 5.10 of 3GPP TS 23.214 [2]. When present for 5GC, it shall contain the value of the DSCP in the TOS/Traffic Class field set based on the 5QI, the Priority Level (if explicitly signalled), and optionally the ARP priority level, of the associated QoS flow, as described in clause 5.8.2.7 of 3GPP TS 23.501 [28],

X

X

–

X

–

Transport Level Marking

Forwarding Policy

C

This IE shall be present if a specific forwarding policy is required to be applied to the packets. It shall be present if the Destination Interface IE is set to SGi-LAN / N6-LAN. It may be present if the Destination Interface is set to Core, Access, or CP-Function. See NOTE 2.

When present, it shall contain an Identifier of the Forwarding Policy locally configured in the UP function.

–

X

X

X

–

Forwarding Policy

Header Enrichment

O

This IE may be present if the UP function indicated support of Header Enrichment of UL traffic. When present, it shall contain information for header enrichment.

–

X

X

X

–

Header Enrichment

Linked Traffic Endpoint ID

C

This IE may be present, if it is available and the UP function indicated support of the PDI optimisation feature, (see clause 8.2.25). When present, it shall identify the Traffic Endpoint ID allocated for this PFCP session to receive the traffic in the reverse direction (see clause 5.2.3.1).

X

X

–

X

–

Traffic Endpoint ID

Proxying

C

This IE shall be present if proxying is to be performed by the UP function.

When present, this IE shall contain the information that the UPF shall respond to Address Resolution Protocol and / or IPv6 Neighbour Solicitation based on the local cache information for the Ethernet PDUs.

–

–

–

X

–

Proxying

Destination Interface Type

O

This IE may be present to indicate the 3GPP interface type of the destination interface, if required by functionalities in the UP Function, e.g. for performance measurements.

X

X

–

X

–

3GPP Interface Type

Data Network Access Identifier

C

This IE shall be present over N16a to link the UL FAR in an UL CL or BP towards a specific local PSA, if more than one local PSA has been inserted by an I-SMF. It may be present over N16a otherwise. This IE shall not be sent over N4.

When present, it shall be set to the DNAI associated to the local PSA towards which the UL traffic shall be forwarded.

–

–

–

–

–

Data Network Access Identifier

IP Address and Port Number Replacement

C

This IE shall be present if the UP function indicated support of replacing the source and destination IP address and Port Number of an (inner) IP packet, and if the source or destination IP address and/or port number of the (Inner) IP packet shall be modified, e.g. for Edge Relocation using EAS IP address and Port number Replacement (see clause 5.33.3).

This IE shall also be present if the destination IP address and/or port number of the (Inner) IP packet shall be modified, e.g. for EAS Discovery procedure with Local DNS Server/Resolver using Local DNS Server/Resolver IP address and Port number Replacement (see clause 5.33.4).

(NOTE 3)

–

–

–

X

–

IP Address and Port Number Replacement

NOTE 1: The Network Instance parameter is needed e.g. in the following cases:

– PGW/TDF UP function supports multiple PDNs with overlapping IP addresses;

– SGW UP function is connected to PGWs in different IP domains (S5/S8);

– PGW UP function is connected to SGWs in different IP domains (S5/S8);

– SGW UP function is connected to eNodeBs in different IP domains;

– UPF is connected to 5G-ANs in different IP domains;

– Separation of multiple 5G VN groups communication in the UPF;

– Indirect data forwarding.

NOTE 2: If the Outer Header Creation and Forwarding Policy are present, the UP function shall put the user plane packets in the user plane tunnel by applying Outer Header Creation, after enforcing the required Forwarding Policy.

NOTE 3: As opposed to the Outer Header Creation IE, this IE does not result in adding any outer header to the outgoing packet.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Destination Interface

M

This IE shall identify the destination interface of the outgoing packet.

X

X

–

–

–

Destination Interface

Outer Header Creation

C

This IE shall be present if the UP function is required to add one or more outer header(s) to the outgoing packet. If present, it shall contain the F-TEID of the remote GTP-U peer. See NOTE 1.

X

X

–

–

–

Outer Header Creation

Transport Level marking

C

This IE shall be present if the UP function is required to mark the IP header with the DSCP marking as defined by IETF RFC 2474 [22]. When present, it shall contain the value of the DSCP in the TOS/Traffic Class field.

X

X

–

–

–

Transport Level Marking

Forwarding Policy

C

This IE shall be present if a specific forwarding policy is required to be applied to the packets. When present, it shall contain an Identifier of the Forwarding Policy locally configured in the UP function.

X

X

–

–

–

Forwarding Policy

NOTE 1: If the Outer Header Creation and Forwarding Policy are present, the UP function shall put the user plane packets in the user plane tunnel by applying Outer Header Creation, after enforcing the required Forwarding Policy.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Outer Header Creation

M

This IE shall be present if the UP function is required to perform the redundant transmission of the outgoing packet.

If present, it shall contain the F-TEID of the remote GTP-U peer for redundant transmission.

–

–

–

X

–

Outer Header Creation

Network Instance for Redundant Transmission

C

This IE shall be included if the GTP-U tunnel used for redundant transmission uses a different network Instance than the Network Instance used for the primary GTP-U tunnel.

–

–

–

X

–

Network Instance

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Destination Interface

M

This IE shall identify the destination interface of the outgoing packet.

–

–

–

–

X

Destination Interface

Network Instance

O

When present, this IE shall identify the Network instance towards which to send the outgoing packet.

–

–

–

–

X

Network Instance

Outer Header Creation

M

This IE shall instruct the MB-UPF to create a GTP-U header using the Low Layer SSM and the C-TEID allocated to the MBS session.

–

–

–

–

X

Outer Header Creation

Transport Level marking

C

This IE shall be present if the UP function is required to mark the IP header with the DSCP marking as defined by IETF RFC 2474 [22]. When present, it shall contain the value of the DSCP in the TOS/Traffic Class field.

–

–

–

–

X

Transport Level Marking

Destination Interface Type

O

This IE may be present to indicate the 3GPP interface type of the destination interface, if required by functionalities in the UP Function, e.g. for performance measurements.

Several IEs with the same IE type may be present to represent multiple destination interface types (e.g. N3mb and N19mb).

–

–

–

–

X

3GPP Interface Type

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Destination Interface

M

This IE shall identify the destination interface of the outgoing packet.

–

–

–

–

X

Destination Interface

MBS Unicast Parameters ID

M

This IE shall identify the MBS Unicast Parameters IE.

–

–

–

–

X

MBS Unicast Parameters ID

Network Instance

O

When present, this IE shall identify the Network instance towards which to send the outgoing packet.

–

–

–

–

X

Network Instance

Outer Header Creation

M

This IE shall be present to request the MB-UPF to add one outer header to the outgoing packet. It shall contain the F-TEID of the remote GTP-U peer when adding a GTP-U/UDP/IP header.

–

–

–

–

X

Outer Header Creation

Transport Level marking

C

This IE shall be present if the UP function is required to mark the IP header with the DSCP marking as defined by IETF RFC 2474 [22]. When present, it shall contain the value of the DSCP in the TOS/Traffic Class field.

–

–

–

–

X

Transport Level Marking

Destination Interface Type

O

This IE may be present to indicate the 3GPP interface type of the destination interface, if required by functionalities in the UP Function, e.g. for performance measurements.

–

–

–

–

X

3GPP Interface Type

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

URR ID

M

This IE shall uniquely identify the URR among all the URRs configured for this PFCP session.

X

X

X

X

–

URR ID

Measurement Method

M

This IE shall indicate the method for measuring the network resources usage, i.e. whether the data volume, duration (i.e. time), combined volume/duration, or event shall be measured.

X

X

X

X

–

Measurement Method

Reporting Triggers

M

This IE shall indicate the trigger(s) for reporting network resources usage to the CP function, e.g. periodic reporting or reporting upon reaching a threshold, or envelope closure, or when an SMF instructs an UPF to report the reception of the End Marker packet from the old I-UPF during a Service Request procedure (see clauses 4.2.3.2 and 4.23.4.3 in 3GPP TS 23.502 [29]).

X

X

X

X

–

Reporting Triggers

Measurement Period

C

This IE shall be present if periodic reporting is required. When present, it shall indicate the period for generating and reporting usage reports.

X

X

X

X

–

Measurement Period

Volume Threshold

C

This IE shall be present if volume-based measurement is used and reporting is required upon reaching a volume threshold. When present, it shall indicate the traffic volume value after which the UP function shall report network resources usage to the CP function for this URR.

X

X

X

X

–

Volume Threshold

Volume Quota

C

This IE shall be present if volume-based measurement is used and the CP function needs to provision a Volume Quota in the UP function (see clause 5.2.2.2)

When present, it shall indicate the Volume Quota value.

–

X

X

X

–

Volume Quota

Event Threshold

C

This IE shall be present if event-based measurement is used and reporting is required upon reaching an event threshold. When present, it shall indicate the number of events after which the UP function shall report to the CP function for this URR.

–

X

X

X

–

Event Threshold

Event Quota

C

This IE shall be present if event-based measurement is used and the CP function needs to provision an Event Quota in the UP function (see clause 5.2.2.2)

When present, it shall indicate the Event Quota value.

–

X

X

X

–

Event Quota

Time Threshold

C

This IE shall be present if time-based measurement is used and reporting is required upon reaching a time threshold. When present, it shall indicate the time usage after which the UP function shall report network resources usage to the CP function for this URR.

X

X

X

X

–

Time Threshold

Time Quota

C

This IE shall be present if time-based measurement is used and the CP function needs to provision a Time Quota in the UP function (see clause 5.2.2.2)

When present, it shall indicate the Time Quota value

–

X

X

X

–

Time Quota

Quota Holding Time

C

This IE shall be present, for a time, volume or event-based measurement, if reporting is required and packets are no longer permitted to pass on when no packets are received during a given inactivity period.

When present, it shall contain the duration of the inactivity period.

–

X

X

X

–

Quota Holding Time

Dropped DL Traffic Threshold

C

This IE shall be present if reporting is required when the DL traffic being dropped exceeds a threshold.

When present, it shall contain the threshold of the DL traffic being dropped.

X

–

–

X

–

Dropped DL Traffic Threshold

Quota Validity Time

C

This IE shall be present if reporting is required when the Quota Validity time for a given Quota is over.

–

X

–

X

–

Quota Validity Time

Monitoring Time

O

When present, this IE shall contain the time at which the UP function shall re-apply the volume or time threshold.

X

X

X

X

–

Monitoring Time

Subsequent Volume Threshold

O

This IE may be present if the Monitoring Time IE is present and volume-based measurement is used.

When present, it shall indicate the traffic volume value after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time.

X

X

X

X

–

Subsequent Volume Threshold

Subsequent Time Threshold

O

This IE may be present if the Monitoring Time IE is present and time-based measurement is used.

When present, it shall indicate the time usage after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time.

X

X

X

X

–

Subsequent Time Threshold

Subsequent Volume Quota

O

This IE may be present if Monitoring Time IE is present and volume-based measurement is used (see clause 5.2.2.2).

When present, it shall indicate the Volume Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Volume Quota

Subsequent Time Quota

O

This IE may be present if Monitoring Time IE is present and time-based measurement is used (see clause 5.2.2.2)

When present, it shall indicate the Time Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Time Quota

Subsequent Event Threshold

O

This IE may be present if the Monitoring Time IE is present and event-based measurement is used.

When present, it shall indicate the number of events after which the UP function shall report to the CP function for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Event Threshold

Subsequent Event Quota

O

This IE may be present if Monitoring Time IE is present and event-based measurement is used (see clause 5.2.2.2).

When present, it shall indicate the Event Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Event Quota

Inactivity Detection Time

C

This IE shall be present if time-based measurement is used and the time measurement need to be suspended when no packets are received during a given inactivity period. When present, it shall contain the duration of the inactivity period.

–

X

X

X

–

Inactivity Detection Time

Linked URR ID

C

This IE shall be present if linked usage reporting is required. When present, this IE shall contain the linked URR ID which is related with this URR (see clause 5.2.2.4).

Several IEs with the same IE type may be present to represent multiple linked URRs which are related with this URR.

–

X

X

X

–

Linked URR ID

Measurement Information

C

This IE shall be included if any of the following flag is set to "1".

Applicable flags are:

– Measurement Before QoS Enforcement Flag: this flag shall be set to "1" if the traffic usage before any QoS Enforcement is requested to be measured.

– Inactive Measurement Flag: this flag shall be set to "1" if the measurement shall be paused (inactive). The measurement shall be performed (active) if the bit is set to "0" or if the Measurement Information IE is not present in the Create URR IE.

– Reduced Application Detection Information Flag: this flag may be set to "1", if the Reporting Triggers request to report the start or stop of application, to request the UP function to only report the Application ID in the Application Detection Information, e.g. for envelope reporting.

– Immediate Start Time Metering Flag: this flag may be set to "1" if time-based measurement is used and the UP function is requested to start the time metering immediately at receiving the flag. .

– Measurement of Number of Packets Flag: this flag may be set to "1" when the Volume-based measurement applies, to request the UP function to report the number of packets in UL/DL/Total in addition to the measurement in octet.

– Send Start Pause of Charging Flag: this flag may be set to "1" by the CP function if the UP Function is requested to send a Start Pause of Charging indication to the upstream GTP-U entity(s) when the Dropped DL Traffic Threshold is reached.

– Applicable for Start of Pause of Charging Flag: this flag may be set to "1" if the URR is applicable for Start of Pause of Charging, so that the UP function shall stop the usage measurement for the URR when receiving Start Pause of Charging indication from the peer downstream GTP-U entity.

– Control of Inactive Measurement Flag: the flag shall be set to "1" if the CP function requests the UP function to stop or resume the usage measurement for the URR with the "ASPOC" flag set to "1" according to the value of Inactive Measurement Flag.

–

–

–

–

X

X

–

–

X

X

X

X

X

–

X

X

X

–

–

X

X

–

–

–

X

X

X

X

X

X

X

X

–

–

–

–

–

–

–

–

Measurement Information

Time Quota Mechanism

C

This IE shall be present if time-based measurement based on CTP or DTP is used.

–

X

–

–

–

Time Quota Mechanism

Aggregated URRs

C

This IE shall be included if the URR is used to support a Credit Pool.

Several IEs with the same IE type may be present to provide multiple aggregated URRs.

–

X

–

–

–

Aggregated URRs

FAR ID for Quota Action

C

This IE may be present if the Volume Quota IE and/or the Time Quota IE and/or Event Quota IE is provisioned in the URR and the UP Function indicated support of the Quota Action feature.

When present, it shall contain the identifier of the substitute FAR the UP function shall apply, for the traffic associated to this URR, when exhausting any of these quotas. See NOTE 1, NOTE 3.

–

X

X

X

–

FAR ID

Ethernet Inactivity Timer

C

This IE shall be present if Ethernet traffic reporting is used and the SMF requests the UP function to also report inactive UE MAC addresses.

When present, it shall contain the duration of the Ethernet inactivity period.

–

–

–

X

–

Additional Monitoring Time

O

When present, this IE shall contain the time at which the UP function shall re-apply the volume or time or event threshold/quota provisioned in the IE.

Several IEs with the same IE type may be present to provide multiple Monitoring Times.

X

X

X

X

–

Additional Monitoring Time

Number of Reports

O

This IE may be present if the UP function supports the NORP feature. When present, it shall indicate the number of usage reports to be generated by the URR. See also clauses 5.2.2.2.1 and 5.2.2.3.1. See NOTE 2.

X

X

X

X

–

Number of Reports

Exempted Application ID for Quota Action

O

This IE may be present if the Volume Quota IE and/or the Time Quota IE and/or Event Quota IE is provisioned in the URR and the UP Function has indicated support of the QUASF feature as specified in clause 8.2.25.

When present, it shall contain an Application ID matching packets that shall be exempted from applying the FAR ID for Quota Action when the quota has been exhausted.

Several IEs with the same IE type may be present to provide multiple Application IDs.

See NOTE 4.

–

X

X

X

–

Application ID

Exempted SDF Filter for Quota Action

O

This IE may be present if the Volume Quota IE and/or the Time Quota IE and/or Event Quota IE is provisioned in the URR and the UP Function has indicated support of the QUASF feature as specified in clause 8.2.25.

When present, it shall contain an SDF Filter matching packets that shall be exempted from applying the FAR ID for Quota Action when the quota has been exhausted.

Several IEs with the same IE type may be present to provide multiple SDF Filters.

See NOTE 4.

–

X

X

X

–

SDF Filter

User Plane Inactivity Timer

C

This IE shall be present, for a time, volume or event-based measurement, if reporting is required when no packets are received for any PDR(s) associated with the URR during a given inactivity period. See clause 5.11.3.

When present, it shall contain the duration of the inactivity period.

–

–

–

X

–

User Plane Inactivity Timer

NOTE 1: The substitute FAR used when exhausting a Volume Quota or Time Quota may be set to drop the packets or redirect the traffic towards a redirect destination as specified in clause 5.4.7.

NOTE 2: This IE may be provisioned and set to "1" e.g. for a URR with the Dropped DL Traffic Threshold used for the Pause of Charging feature, if the UP function supports the NORP feature.

NOTE 3: If the FAR as indicated in the FAR ID for Quota Action is removed after being provisioned, the UP function shall behave as if the FAR ID for Quota Action is not provisioned and shall apply the default behaviour per local configuration when the quota is exhausted.

NOTE 4: The Exempted Application ID for Quota Action IE or Exempted Filter ID for Quota Action IE may be provisioned as the Restricted-Filter-Rule AVP or Filter ID AVP which is included in Final-Unit-Indication AVP from the online charging system when the Final-Unit-Action AVP is set to "REDIRECT" or "RESTRICT_ACCESS". See also 3GPP TS 32.299 [18].

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Aggregated URR ID

M

This IE shall be present for the aggregated URR ID of the URR sharing the credit pool.

–

X

–

–

–

Aggregated URR ID

Multiplier

M

This IE shall be included to measure the abstract service units the traffic of the corresponding aggregated URR consumes from the credit pool.

–

X

–

–

–

Multiplier

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Monitoring Time

M

This IE shall be present and contain the time at which the UP function shall re-apply the volume or time threshold/quota.

X

X

X

X

–

Monitoring Time

Subsequent Volume Threshold

O

This IE may be present if the Monitoring Time IE is present and volume-based measurement is used.

When present, it shall indicate the traffic volume value after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time.

X

X

X

X

–

Subsequent Volume Threshold

Subsequent Time Threshold

O

This IE may be present if the Monitoring Time IE is present and time-based measurement is used.

When present, it shall indicate the time usage after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time.

X

X

X

X

–

Subsequent Time Threshold

Subsequent Volume Quota

O

This IE may be present if Monitoring Time IE is present and volume-based measurement is used (see clause 5.2.2.2).

When present, it shall indicate the Volume Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Volume Quota

Subsequent Time Quota

O

This IE may be present if Monitoring Time IE is present and time-based measurement is used (see clause 5.2.2.2)

When present, it shall indicate the Time Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Subsequent Time Quota

Subsequent Event Threshold

O

This IE may be present if the Monitoring Time IE is present and event-based measurement is used.

When present, it shall indicate the number of events after which the UP function shall report to the CP function for this URR for the period after the Monitoring Time.

–

X

X

X

–

Event Threshold

Subsequent Event Quota

O

This IE may be present if Monitoring Time IE is present and event-based measurement is used (see clause 5.2.2.2).

When present, it shall indicate the Event Quota value which the UP function shall use for this URR for the period after the Monitoring Time.

–

X

X

X

–

Event Quota

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

QER ID

M

This IE shall uniquely identify the QER among all the QER configured for that PFCP session

–

X

X

X

X

QER ID

QER Correlation ID

C

This IE shall be present if the UP function is required to correlate the QERs of several PFCP sessions, for APN-AMBR enforcement/APN rate control of multiple UE’s PDN connections to the same APN.

–

X

–

X

–

QER Correlation ID

Gate Status

M

This IE shall indicate whether the packets are allowed to be forwarded (the gate is open) or shall be discarded (the gate is closed) in the uplink and/or downlink directions.

–

X

X

X

X

Gate Status

Maximum Bitrate

C

This IE shall be present if an MBR enforcement action shall be applied to packets matching this PDR. When present, this IE shall indicate the uplink and/or downlink maximum bit rate to be enforced for packets matching the PDR.

For EPC, this IE may be set to the value of:

– the APN-AMBR, for a QER that is referenced by all the PDRs of the non-GBR bearers of a PDN connection;

– the TDF session MBR, for a QER that is referenced by all the PDRs of a TDF session;

– the bearer MBR, for a QER that is referenced by all the PDRs of a bearer;

– the SDF MBR, for a QER that is referenced by all the PDRs of a SDF.

For 5GC, this IE may be set to the value of:

– the Session-AMBR, for a QER that is referenced by all the PDRs of the non-GBR QoS flows of a PDU session;

– the QoS Flow MBR, for a QER that is referenced by all the PDRs of a QoS Flow;

– the SDF MBR, for a QER that is referenced by all the PDRs of a SDF.

–

X

X

X

X

MBR

Guaranteed Bitrate

C

This IE shall be present if a GBR has been authorized to packets matching this PDR. When present, this IE shall indicate the authorized uplink and/or downlink guaranteed bit rate.

This IE may be set to the value of:

– the aggregate GBR, for a QER that is referenced by all the PDRs of a GBR bearer;

– the QoS Flow GBR, for a QER that is referenced by all the PDRs of a QoS Flow (for 5GC);

– the SDF GBR, for a QER that is referenced by all the PDRs of a SDF.

–

X

X

X

X

GBR

Packet Rate

C

This IE shall be present if a Packet Rate enforcement action (in terms of number of packets per time interval) shall be applied to packets matching this PDR.

When present, this IE shall indicate the uplink and/or downlink maximum packet rate to be enforced for packets matching the PDR.

This IE may be set to the value of:

– downlink packet rate for Serving PLMN Rate Control, for a QER that is referenced by all PDRs of the UE belonging to the PDN connection, or belonging to the PDU session (5GC) using CIoT EPS Optimizations as described in 3GPP TS 23.401 [2] and 3GPP TS 23.501 [28], respectively;

– uplink and/or downlink packet rate for APN Rate Control, for a QER that is referenced by all the PDRs of the UE belonging to all PDN connections to the same APN, or for Small Data Rate Control (5GC) for a QER related to the PDU session using CIoT EPS Optimizations as described in 3GPP TS 23.401 [2] and 3GPP TS 23.501 [28], respectively.

–

X

–

X

–

Packet Rate

Packet Rate Status

C

This IE may be present during the UE requested PDU session establishment, or UE requested PDN connection establishment.

When present, the UP function shall first enforce these rules. Only after that shall the UP function enforce the rules in the Packet Rate IE.

–

X

–

X

–

Packet Rate Status

DL Flow Level Marking

C

This IE shall be set if the UP function is required to mark the packets for QoS purposes:

– by the TDF-C, for DL flow level marking for application indication (see clause 5.4.5);

– by the PGW-C, for setting the GTP-U Service Class Indicator extension header for service indication towards GERAN (see clause 5.4.12).

–

X

X

–

–

DL Flow Level Marking

QoS flow identifier

C

This IE shall be present if the QoS flow identifier shall be inserted or modified by the UPF or shall be inserted by the MB-UPF. (NOTE 2)

–

–

–

X

X

QFI

Reflective QoS

C

This IE shall be present if the UP function is required to insert a Reflective QoS Indicator to request reflective QoS for uplink traffic.

–

–

–

X

–

RQI

Paging Policy Indicator

C

This IE shall be present if the UPF is required to set the Paging Policy Indicator (PPI) in outgoing packets (see clause 5.4.3.2 of 3GPP TS 23.501 [28]).

When present, it shall be set to the PPI value to set.

–

–

–

X

–

Paging Policy Indicator

Averaging Window

O

This IE may be present if the UP function is required to use a different Averaging window than the default one. (NOTE 1)

–

–

–

X

–

Averaging Window

QER Control Indications

C

This IE shall be included if the CP function needs to provide the QoS enforcement control information:

– RCSR (Rate Control Status Reporting): the CP function shall set this bit "1" to request the UP function to report the rate control status when the PFCP session is released.

–

X

–

X

–

QER Control Indications

QER Indications

C

This IE shall be included if at least one of the flags is set to "1".

– IQFISN (Insert DL MBS QFI Sequence Number): this IE shall be set to "1" to request the MB-UPF to insert the DL MBS QFI Sequence Number in the PDU Session Container of the MBS data packets (see 3GPP TS 38.415 [34]).

–

–

–

–

X

QER Indications

NOTE 1: As 5QI is not signalled over N4, one default averaging window shall be pre-configured in the UPF.

NOTE 2: The SMF may request the UPF to modify the QFI of downlink packets of a multicast QoS flow received from the MB-UPF to the QFI assigned by the SMF for the Associated QoS flow. See clause 5.34.3.2.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

BAR ID

M

This IE shall uniquely identify the BAR provisioned for that PFCP session.

X

–

–

X

–

BAR ID

Downlink Data Notification Delay

C

This IE shall be present if the UP function indicated support of the Downlink Data Notification Delay parameter (see clause 8.2.28) and the UP function has to delay the notification to the CP function about the arrival of DL data packets.

When present, it shall contain the delay the UP function shall apply between receiving a downlink data packet and notifying the CP function about it, when the Apply Action parameter requests to buffer the packets and notify the CP function.

X

–

–

–

–

Downlink Data Notification Delay

Suggested Buffering Packets Count

C

This IE may be present if the UP Function indicated support of the feature UDBC.

When present, it shall contain the number of packets that are suggested to be buffered when the Apply Action parameter requests to buffer the packets. The packets that exceed the limit shall be discarded.

–

X

X

X

–

Suggested Buffering Packets Count

MT-EDT Control Information

O

This IE may be included to request the SGW-U to report the sum of DL Data Packets Size.

X

–

–

–

–

MT-EDT Control Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Traffic Endpoint ID

M

This IE shall uniquely identify the Traffic Endpoint for that PFCP session.

X

X

X

X

X

Traffic Endpoint ID

Local F-TEID

O

If present, this IE shall identify the local F-TEID to match for an incoming packet.

The CP function shall set the CHOOSE (CH) bit to 1 if the CP function requests the UP function to assign a local F-TEID to the Traffic Endpoint.

X

X

–

X

–

F-TEID

Network Instance

O

This IE shall be present if the CP function requests the UP function to allocate a UE IP address/prefix.

If present, this IE shall identify the Network instance to match for the incoming packet. See NOTE 1, NOTE 2.

X

X

X

X

X

Network Instance

Redundant Transmission Detection Parameters

O

If present, this IE shall contain the information used for the reception of redundant uplink packets on N3/N9 interfaces.

See Table 7.5.2.2-5.

–

–

–

X

–

Redundant Transmission Detection Parameters

UE IP address

O

If present, this IE shall identify the UE IP address as the source or destination IP address to match for the incoming packet. (NOTE 3).

The CP function shall set the CHOOSE IPV4 (CHV4) and/or CHOOSE IPV6 (CHV6) bits to 1 if the UP function supports the allocation of UE IP address/ prefix and the CP function requests the UP function to assign a UE IP address/prefix to the Traffic Endpoint.

This IE may also present to identify the IP address of the CP function as the destination IP address to match for the incoming packet, e.g. Radius, Diameter or DHCP signalling packet. (NOTE 6).

In the 5GC, several IEs with the same IE type may be present to represent multiple UE IP addresses, if the UPF indicated support of the IP6PL feature (see clause 5.21).

–

X

X

X

–

UE IP address

Ethernet PDU Session Information

O

This IE may be present to identify all the (DL) Ethernet packets matching an Ethernet PDU session (see clause 5.13.1).

–

–

–

X

–

Ethernet PDU Session Information

Framed-Route

O

This IE may be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe a framed route.

Several IEs with the same IE type may be present to provision a list of framed routes. (NOTE 3)

–

X

–

X

–

Framed-Route

Framed-Routing

O

This IE may be present for a DL PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe the routing method for the UP function for the IP route related to Framed-Routes or Framed-IPv6-Routes. (NOTE 5)

–

X

–

X

–

Framed-Routing

Framed-IPv6-Route

O

This IE may be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16). If present, this IE shall describe a framed IPv6 route.

Several IEs with the same IE type may be present to provision a list of framed IPv6 routes. (NOTE 3)

–

X

–

X

–

Framed-IPv6-Route

QFI

O

This IE may be present if the UPF has indicated it supports MTE feature as specified in clause 8.2.25.

If present, this IE shall identify the QoS Flow Identifier to match for the incoming packet received from the traffic endpoint.

Several IEs with the same IE type may be present to provision a list of QFIs. When present, the full set of applicable QFIs shall be provided.

–

–

–

X

–

QFI

Source Interface Type

O

This IE may be present to indicate the 3GPP interface type of the source interface, if required by functionalities in the UP Function, e.g. for performance measurements.

(NOTE 4)

X

X

–

X

X

3GPP Interface Type

Local Ingress Tunnel

C

This IE shall be present over N4mb, for Nmb9, or for N6mb if unicast transport is used over N6mb, if Traffic Endpoint ID is present in the DL PDR.

If present, this IE shall identify the IP address and the UDP port for a UDP/IP tunnel.

The CP function shall set the CHOOSE (CH) bit to 1 if the CP function requests the UP function to assign a local ingress tunnel to the PDR.

–

–

–

–

X

Local Ingress Tunnel

IP Multicast Addressing Info

C

This IE shall be present over N4mb, if multicast transport is used over N6mb, if Traffic Endpoint ID is present in the DL PDR.

See Table 7.5.2.2-4.

–

–

–

–

X

IP Multicast Addressing Info

MBS Session Identifier

C

This IE shall be present when the PDR is created to receive MBS session data. (NOTE 7)

–

–

–

X

–

MBS Session Identifier

Area Session ID

C

This IE shall be present for a location dependent MBS service. When present, it shall contain the Area Session ID, which together with the MBS Session Identifier, uniquely identify the service area part of the content data of the MBS service. (NOTE 7)

–

–

–

X

–

Area Session ID

RAT Type

O

This IE may be present to provide the UP Function the current RAT Type for the UL PDR(s) for statistics purpose if the PFCP session is established for a MA PDU session.

–

–

–

X

–

RAT Type

NOTE 1: The Network Instance parameter is needed e.g. in the following cases:

– PGW/TDF UP function supports multiple PDNs with overlapping IP addresses;

– SGW UP function is connected to PGWs in different IP domains (S5/S8);

– PGW UP function is connected to SGWs in different IP domains (S5/S8);

– SGW UP function is connected to eNodeBs in different IP domains;

– UPF is connected to 5G-ANs in different IP domains;

– Separation of multiple 5G VN groups communication in the UPF.

NOTE 2: When a Local F-TEID is provisioned in the Traffic Endpoint, the Network Instance shall relate to the IP address of the F-TEID. Otherwise, the Network Instance shall relate to the UE IP address.

NOTE 3: If both the UE IP Address and the Framed-Route (or Framed-IPv6-Route) are present, the packets which are considered being matching the PDR shall match at least one of them.

NOTE 4: If the Source Interface Type is provisioned at the traffic endpoint, it shall not be provisioned in individual PDRs associated to the traffic endpoint.

NOTE 5: In this release of specification, the UP function shall announce the IP route(s) for Framed-Route(s) or Framed-IPv6-Route(s) to the PDN regardless of the value of the Framed-Routing.

NOTE 6: The CP IP Address parameter is needed e.g. perform Router Advertisements and match the destination IP address of the incoming packet if the Radius, Diameter or DHCP signaling packets between the SMF and the external DN is forwarded by the UPF.

NOTE 7: The Inclusion of the MBS Session Identifier, or MBS Session Identifier and Area Session ID for a location dependent MBS session, enables the UPF to allocate the same N19mb tunnel for the same MBS Session, or for the same MBS Session Identifier and Area Session ID for a location dependent MBS session, when receiving multiple PFCP Session Establishment or Modification Request messages for different PFCP sessions being associated with the same MBS session, or with the same MBS session and Area Session ID for a location dependent MBS session, and also helps the UPF to identify the PFCP sessions associated with a MBS Session, or with the same MBS session and Area Session ID for a location dependent MBS session.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MAR ID

M

This IE shall uniquely identify the MAR among all the MARs configured for that PFCP session.

–

–

–

X

–

MAR ID

Steering Functionality

M

This IE shall be present to indicate the applicable traffic steering functionality.

–

–

–

X

–

Steering Functionality

Steering Mode

M

This IE shall be present to indicate the steering mode.

–

–

–

X

–

Steering Mode

3GPP Access Forwarding Action Information

C

This IE shall be present to provision 3GPP access specific forwarding action information if the UE is registered for 3GPP access, except when steering mode is set to "Active-Standby", Non-3GPP access is the active access and 3GPP access is not used as Standby access. In the latter case, this IE may be present.

(NOTE)

–

–

–

X

–

3GPP Access Forwarding Action Information

Non-3GPP Access Forwarding Action Information

C

This IE shall be present to provision non-3GPP access specific forwarding action information if the UE is registered for non-3GPP access, except when steering mode is set to "Active-Standby", 3GPP access is the active access and Non-3GPP access is not used as Standby access. In the latter case, this IE may be present.

(NOTE 1)

–

–

–

X

–

Non-3GPP Access Forwarding Action Information

Threshold Values

C

This IE shall be present if the steering mode is "Load Balancing" with fixed split percentages or "Priority-based" and if available.

When present, this IE shall contain the RTT and/or a Packet Loss Rate.

(NOTE 2)

–

–

–

X

–

Thresholds

Steering Mode Indicator

C

This IE shall be included if at least one of the flags is set to "1":

– ALBI (Autonomous Load Balancing Indicator): this flag shall be set to "1" if the SMF allows the UPF to apply autonomous load-balance when the Steering Mode is Load-Balancing;

– UEAI (UE Assistance Indicator): this flag shall be set to "1" if the SMF allows UE assistant load-balance when the Steering Mode is Load-Balancing.

(NOTE 2)

–

–

–

X

–

Steering Mode Indicator

NOTE 1: For the "Active-Standby" steering mode, if the network determines to not define a Standby access (as specified in clause 5.32.8 of 3GPP TS 23.501 [28]), the SMF shall either set the Priority IE within (Non-)3GPP Access Forwarding Action Information IE to the value "No Standby" or not include the (Non-)3GPP Access Forwarding Action Information IE for that access not defined as Standby access.

NOTE 2: The Threshold Values IE and the Steering Mode Indicator IE shall not be present together.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

FAR ID

M

This IE shall uniquely identify the FAR among all the FARs configured for this PFCP session.

–

–

–

X

–

FAR ID

Weight

C

This IE shall be present if steering mode is set to "Load Balancing" to identify the weight of the FAR.

(NOTE 1)

–

–

–

X

–

Weight

Priority

C

This IE shall be present if the steering mode is set to "Active-Standby" or "Priority-based". (NOTE 2)

–

–

–

X

–

Priority

URR ID

C

This IE shall uniquely identify the URR among all the URRs configured for the PFCP session. This enables the SMF to request separate usage reports for different FARs (i.e. different accesses) (NOTE 3)

Several IEs within the same IE type may be present to represent a list of URRs to be associated to the FAR.

–

–

–

X

–

URR ID

RAT Type

O

This IE may be present to provide the UP Function the current RAT Type for the DL FAR for statistics purpose.

–

–

–

X

–

RAT Type

NOTE 1: The weights for all FARs included in both 3GPP Access Forwarding Action Information and Non 3GPP Access Forwarding Action Information need to sum up to 100. If the autonomous load balance operation is allowed, the Weights shall be treated as the default percentages.

NOTE 2: The Priority value shall be set to "Active", "Standby" or "No Standby" if the Steering Mode is set to "Active-Standby"; the Priority value shall be set to "High" or "Low" if the Steering Mode is set to "Priority-based". The 3GPP Access Forwarding Action Information and Non 3GPP Access Forwarding Action Information shall set different values.

NOTE 3: One or more URRs may still be provisioned in the Create PDR IE when an MAR ID is present, while the URR(s) provisioned in this IE shall present a different set of URR(s) to request separate usage reports.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Same IEs and requirements as defined in Table 7.5.2.8-2

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

SRR ID

M

This IE shall uniquely identify the SRR among all the SRRs configured for this PFCP session.

–

–

–

X

–

SRR ID

Access Availability Control Information

C

This IE shall be present if the UPF needs to report when an access type becomes available or not available (see clause 5.20.4.2).

–

–

–

X

–

Access Availability Control Information

QoS Monitoring per QoS flow Control Information

C

This IE shall be present if the per QoS Flow per UE QoS monitoring reporting is triggered.

Several IEs within the same IE type may be present to represent a list of QoS Monitoring per QoS flow Control Information for different QoS flows.

–

–

–

X

–

QoS Monitoring per QoS flow Control Information

Direct Reporting Information

C

This IE shall be present if the UPF indicated support of the DRQOS feature and if the QoS monitoring events shall be reported by the UPF directly to a Local NEF or AF, or both to the SMF and Local NEF/AF (see clause 5.33.5).

(NOTE)

–

–

–

X

–

Direct Reporting Information

NOTE: In this release of the specification, the Direct Reporting Information shall only be used for direct reporting of QoS monitoring per QoS flow.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Requested Access Availability Information

M

This IE shall indicate the requested information to be reported.

–

–

–

X

–

Requested Access Availability Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

QFI

M

This IE shall identify the QoS Flow Identifier for which QoS monitoring is required.

Several IEs within the same IE type may be present to represent different QoS flows.

–

–

–

X

–

QFI

Requested QoS Monitoring

M

This IE shall indicate whether the uplink, downlink and/or round trip packet delay between the UE and the UPF (PSA) shall be monitored, and whether QoS monitoring is performed based on GTP-U path monitoring.

–

–

–

X

–

Requested QoS Monitoring

Reporting Frequency

M

This IE shall indicate the frequency for the reporting, i.e. event triggered, periodic, or when the PDU Session is released.

–

–

–

X

–

Reporting Frequency

Packet Delay Thresholds

C

This IE shall be present if event triggered QoS monitoring reporting is used and reporting is required upon reaching a delay threshold. When present, it shall indicate the packet delay after which the UP function shall report QoS monitoring result to the CP function or Local NEF or AF for this SRR.

(NOTE 1)

–

–

–

X

–

Packet Delay Thresholds

Minimum Wait Time

C

This IE shall be present if event triggered QoS monitoring reporting is required. When present, it shall indicate the minimum waiting time between two consecutive reports after which the UP function may report new QoS monitoring result to the CP function or Local NEF or AF for this SRR.

–

–

–

X

–

Minimum Wait Time

Measurement Period

C

This IE shall be present if the periodic QoS monitoring reporting is required. When present, it shall indicate the period for generating and reporting QoS monitoring reports.

(NOTE 2)

–

–

–

X

–

Measurement Period

NOTE 1: If no time stamp is received in uplink packet for a delay exceeding the Packet Delay Thresholds, the UP function shall generate a QoS monitoring report indicating a packet delay measurement failure to the CP function or Local NEF or AF.

NOTE 2: If no time stamp is received in uplink packet for a delay exceeding the Measurement Period, the UP function shall generate a QoS monitoring report indicating a packet delay measurement failure to the CP function or Local NEF or AF.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Event Notification URI

M

This IE shall contain the notification URI to be used for sending the UPF event notifications.

–

–

–

X

–

Event Notification URI

Notification Correlation ID

C

This IE shall indicate the notification correlation id to be included in the UPF event notifications. It shall be present if it is available.

–

–

–

X

–

Notification Correlation ID

Reporting Flags

This IE shall be included if at least one of the flags is set to "1".

– DUPL (Duplicate notification): this IE shall be set to "1" if event notifications shall be sent over N4 and directly to the notification URI indicated in the Event Notification URI IE. When this flag is set to "0", this indicates that the UPF shall only send the event notifications directly to the notification URI indicated in the Event Notification URI IE.

–

–

–

X

–

Reporting Flags

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MPTCP Control Information

C

This IE shall be present if the PDU session is an MA PDU session and the MPTCP functionality is required.

–

–

–

X

–

MPTCP Control Information

ATSSS-LL Control Information

C

This IE shall be present if the PDU session is an MA PDU session and the ATSSS-LL functionality is required.

–

–

–

X

–

ATSSS-LL Control Information

PMF Control Information

C

This IE shall be present if the PDU session is an MA PDU session and the PMF functionality is required.

–

–

–

X

–

PMF Control Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

RDS Configuration Information

O

When present, this IE indicates if the RDS mechanism is supported.

–

X

–

X

–

RDS Configuration Information