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

Cause

M

This IE shall indicate the acceptance, partial acceptance or rejection of the corresponding request message.

X

X

X

X

X

Cause

Offending IE

C

This IE shall be included if the rejection is due to a conditional or mandatory IE missing or faulty.

X

X

X

X

X

Offending IE

UP F-SEID

C

This IE shall be present if the cause is set to "Request accepted (success)". When present, it shall contain the unique identifier allocated by the UP function identifying the session.

X

X

X

X

X

F-SEID

Created PDR

C

This IE shall be present if the cause is set to "success" and the UP function was requested to allocate a local F-TEID or a UE IP address/prefix for the PDR.

When present, this IE shall contain the PDR information associated to the PFCP session. There may be several instances of this IE.

See table 7.5.3.2-1.

X

X

–

X

X

Created PDR

Load Control Information

O

The UP function may include this IE if it supports the load control feature and the feature is activated in the network.

See Table 7.5.3.3-1.

X

X

X

X

X

Load Control Information

Overload Control Information

O

During an overload condition, the UP function may include this IE if it supports the overload control feature and the feature is activated in the network.

See Table 7.5.3.4-1.

X

X

X

X

X

Overload Control Information

PGW-U/SGW-U /UPF 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

Failed Rule ID

C

This IE shall be included if the Cause IE indicates a rejection due to a rule creation or modification failure.

X

X

X

X

X

Failed Rule ID

Created Traffic Endpoint

C

This IE shall be present if the cause is set to "success" and the UP function was requested to allocate a local F-TEID or a UE IP address/prefix in a Create Traffic Endpoint IE. When present, it shall contain the local F-TEID or UE IP address/prefix to be used for this Traffic Endpoint.

There may be several instances of this IE.

X

X

–

X

X

Created Traffic Endpoint

Created Bridge Info for TSC

C

This IE shall be present if the UPF was requested to provide Bridge information for TSC in the PFCP Session Establishment Request. When present, it shall contain the Bridge information for TSC for the PFCP session.

See Table 7.5.3.6-1.

–

–

–

X

–

Created Bridge Info for TSC

ATSSS Control Parameters

C

This IE shall be present if ATSSS functionality is required in the request message and the UPF allocates the resources and parameters corresponding to the required ATSSS functionality.

See Table 7.5.3.7-1.

–

–

–

X

–

ATSSS Control Parameters

RDS configuration information

O

When present, this IE shall contain the RDS configuration information the UP function supported for this PFCP session.

–

X

–

X

–

RDS configuration information

Partial Failure Information

C

This IE shall be present if the Cause IE indicates partial acceptance of the request to provide failure information related to a failed rule. See Table 7.5.3.1-2.

Several IEs within the same IE type may be present to report failures to apply multiple rules.

–

X

X

X

X

Partial Failure Information

Created L2TP Session

O

This IE may be present to include information for the Created L2TP session if the Cause IE indicates a success.

–

X

–

X

–

Created L2TP Session

MBS Session N4mb Information

C

This IE shall be present if any IE in this grouped IE needs to be included.

–

–

–

–

X

MBS Session N4mb Information

MBS Session N4 Information

C

This IE shall be included if any IE in this grouped IE needs to be included as specified in clause 5.34.1.

Several IE with the same IE type may be present to contain N4 Information for several MBS Sessions respectively.

–

–

–

X

–

MBS Session N4 Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Failed Rule ID

M

This IE shall indicate the rule that failed to be applied.

–

X

X

X

X

Failed Rule ID

Failure Cause

M

This IE shall indicate the reason why the rule could not be applied.

–

X

X

X

X

Cause

Offending IE Information

M

This IE shall be included to report the offending IE which caused the rule activation failure, e.g. an unknown predefined rule name included in Activate Predefined Rules IE or an unknown Application ID in the PDI.

Several IEs within the same IE type may be present to report multiple offending IEs.

–

X

X

X

X

Offending IE Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

DNS Server Address

O

This IE may be present to include a DNS server address.

Several IEs with the same IE type may be present to represent multiple DNS server addresses.

The order of the IEs in the message indicates the priority, i.e. the first IE shall contain the primary DNS server address and the second IE shall contain the secondary DNS server address.

–

X

–

X

–

DNS Server Address

NBNS Server Address

O

This IE may be present to include an NBNS server address.

Several IEs with the same IE type may be present to represent multiple NBNS server addresses.

The order of the IEs in the message indicates the priority, i.e. the first IE shall contain the primary NBNS server address and the second IE shall contain the secondary NBNS server address.

–

X

–

X

–

NBNS Server Address

LNS Address

O

This IE may be present to include the used Tunnel Server Endpoint, i.e., the LNS IP address, for the PFCP Session.

–

X

–

X

–

LNS Address

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

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) if the CP function has requested to allocate such information for multicast transport over N3mb and/or N19mb.

–

–

–

–

X

Multicast Transport Information

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

N19mb DL Tunnel ID

C

This IE shall be present when the SMF has requested the UPF to allocate a Local F-TEID in the PDI or in the Create Traffic Endpoint IE. (NOTE 1)

–

–

–

X

–

F-TEID

MBSN4Resp-Flags

C

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

– NN19DT (New N19mb Downlink Tunnel): the UPF shall set this flag if it has allocated a new N19mb DL TEID for the MBS session;

– JMTI (Joined N19mb Multicast Tree Indication): the UPF shall set this flag if it has joined the multicast tree from the MB-UPF;

– N19DTR (N19mb Downlink Tunnel Removal): the UPF shall set this flag if it is about to remove the N19mb DL Tunnel for receiving the MBS session data.

–

–

–

X

–

MBSN4Resp-Flags

NOTE 1: The UPF need not include Created PDR or Created Traffic Endpoint to return the newly allocated N19mb DL TEID.

NOTE 2: Clause 5.34.3.2 explains what is indicated by the absence of the MBSN4Resp-Flags.

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

PDR ID

M

X

X

–

X

X

PDR ID

Local F-TEID

C

If the UP function allocates the F-TEID, this IE shall be present and shall contain the local F-TEID to be used for this PDR.

X

X

–

X

–

F-TEID

Local F-TEID for Redundant Transmission

C

This IE shall be present and shall contain the local F-TEID used for this PDR for the reception of redundant uplink packets on N3/N9 interfaces, if the CP function requested a Local F-TEID to be assigned for redundant transmission.

–

–

–

X

–

F-TEID

UE IP Address

C

If the UP function allocates the UE IP address/prefix, this IE shall be present and shall contain the UE IP address/ prefix assigned by the UP function.

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

–

UE IP Address

Local Ingress Tunnel

C

If the UP function allocates the Local Ingress Tunnel, this IE shall be present and shall contain the Local Ingress Tunnel to be used for this PDR.

–

–

–

–

X

Local Ingress Tunnel

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Load Control Sequence Number

M

See clause 6.2.3.3.2 for the description and use of this parameter.

X

X

X

X

X

Sequence Number

Load Metric

M

See clause 6.2.3.3.2 for the description and use of this parameter.

X

X

X

X

X

Metric

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Overload Control Sequence Number

M

See 6.2.4.3.2 for the description and use of this parameter.

X

X

X

X

X

Sequence Number

Overload Reduction Metric

M

See clause 6.2.4.3.2 for the description and use of this parameter.

X

X

X

X

X

Metric

Period of Validity

M

See clause 6.2.4.3.2 for the description and use of this parameter.

X

X

X

X

X

Timer

Overload Control Information Flags

C

This IE shall be included if any of flag in this IE is set.

X

X

X

X

X

OCI Flags

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

Traffic Endpoint ID

Local F-TEID

C

If the UP function allocates the F-TEID, this IE shall be present and shall contain the local F-TEID to be used for this Traffic Endpoint.

X

X

–

X

–

F-TEID

Local F-TEID for Redundant Transmission

C

This IE shall be present and shall contain the local F-TEID to be used for this PDR for the reception of redundant uplink packets on N3/N9 interfaces, if the CP function requested a Local F-TEID to be assigned for redundant transmission.

–

–

–

X

–

F-TEID

UE IP Address

C

If the UP function allocates the UE IP address/prefix, this IE shall be present and shall contain the UE IP address/ prefix assigned by the UP function.

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

–

UE IP Address

Local Ingress Tunnel

C

If the UP function allocates the Local Ingress Tunnel, this IE shall be present and shall contain the Local Ingress Tunnel to be used for this PDR.

–

–

–

–

X

Local Ingress Tunnel

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

DS-TT Port Number

C

If the BII bit was set to "1" in the Create Bridge Info for TSC IE, this IE shall be present and shall contain the DS-TT Port Number assigned by the UP function.

–

–

–

X

–

DS-TT Port Number

5GS User Plane Node

C

If the BII bit was set to "1" in the Create Bridge Info for TSC IE, this IE shall be present and shall contain the 5GS User Plane Node assigned by the UP function.

–

–

–

X

–

5GS User Plane Node

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MPTCP Parameters

C

This IE shall be present if the TCI flag in the MPTCP Control Information IE is set to "1" in the Request message and the UPF allocated resources for MPTCP.

–

–

–

X

–

MPTCP Parameters

ATSSS-LL Parameters

C

This IE shall be present if the LLI flag in ATSSS-LL Control Information IE is set to "1" in the Request message and the UPF allocated resources for ATSSS-LL.

–

–

–

X

–

ATSSS-LL Parameters

PMF Parameters

C

This IE shall be present if the PMFI flag in the PFM Control Information IE is set to "1" in the Request message and the UPF allocated resources for PMF.

Several IEs with the same IE type may be present to provide multiple PMF Parameters.

–

–

–

X

–

PMF Parameters

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

MPTCP Address Information

M

This IE shall carry the information of allocated MPTCP address.

–

–

–

X

–

MPTCP Address Information

UE Link-Specific IP Address

M

This IE shall carry the information of allocated UE link-specific IP address for MPTCP.

–

–

–

X

–

UE Link-Specific IP Address

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

ATSSS-LL Information

M

This IE shall indicate that resources have been allocated to the ATSSS functionality.

–

–

–

X

–

ATSSS-LL Information

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

PMF Address Information

M

This IE shall contain the PMF Address Information.

–

–

–

X

–

PMF Address Information

QoS flow identifier

O

If present, this IE shall identify the QoS Flow Identifier of the QoS flow related to the PMF address information.

–

–

–

X

–

QFI