7.4 PFCP Node Related Messages

29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS

7.4.1 General

This clause specifies either node level or PFCP entity level messages used over the Sxa, Sxb, Sxc, N4 and N4mb reference points (see clause 6.2).

7.4.2 Heartbeat Messages

7.4.2.1 Heartbeat Request

Table 7.4.2.1-1: Information Elements in Heartbeat Request

Information

elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Recovery Time Stamp

M

This IE shall contain the time stamp when the PFCP entity was started see clause 19A of 3GPP TS 23.007 [24].

X

X

X

X

X

Recovery Time Stamp

Source IP Address

O

This IE may be included when a Network Address Translation device is deployed in the network. See clause 19a in 3GPP TS 23.007 [24].

X

X

X

X

X

Source IP Address

7.4.2.2 Heartbeat Response

Table 7.4.2.2-1: Information Elements in Heartbeat Response

Information

elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Recovery Time Stamp

M

This IE shall contain the time stamp when the PFCP entity was started see clause 19A of 3GPP TS 23.007 [24].

X

X

X

X

X

Recovery Time Stamp

7.4.3 PFCP PFD Management

7.4.3.1 PFCP PFD Management Request

Table 7.4.3.1-1: Information Elements in PFCP PFD Management Request

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Application ID’s PFDs

C

This IE shall contain an Application Identifier and the associated PFDs to be provisioned in the UP function.

Several IEs with the same IE type may be present to provision PFDs for multiple Application IDs.

The UP function shall delete all the PFDs received and stored earlier for all the Application IDs if this IE is absent in the message.

X

X

X

Application ID’s PFDs

Node ID

O

When present, this IE shall contain the unique identifier of the sending Node.

X

X

X

Node ID

Table 7.4.3.1-2: Application ID’s PFDs

Octet 1 and 2

Application ID’s PFDs IE Type = 58 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Application ID

M

This IE shall identify the Application ID for which PFDs shall be provisioned in the UP function.

X

X

X

Application ID

PFD context

C

This IE shall be present if the PFD needs to be provisioned in the UP function.

When present, it shall describe the PFD to be provisioned in the UP function.

Several IEs with the same IE type may be present to provision multiple PFDs for this Application ID.

When this IE is absent, the UP function shall delete all the PFDs received and stored earlier in the UP function for this Application ID.

X

X

X

PFD context

Table 7.4.3.1-3: PFD context

Octet 1 and 2

PFD context IE Type = 59 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

PFD Contents

M

This IE shall describe the PFD to be provisioned in the UP function. Several IEs with the same IE type may be present to provision multiple contents for this PFD. (NOTE 1)

X

X

X

PFD Contents

NOTE 1 The CP function shall only provision a PFD Contents including a property with multiple values if the UP function supports PFDE feature. See clauses 8.2.25 and 8.2.39.

7.4.3.2 PFCP PFD Management Response

Table 7.4.3.2-1: Information Elements in PFCP PFD Management Response

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Cause

M

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

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

Offending IE

Node ID

O

When present, this IE shall contain the unique identifier of the sending Node.

X

X

X

Node ID

7.4.4 PFCP Association messages

7.4.4.1 PFCP Association Setup Request

7.4.4.1.1 General

Table 7.4.4.1-1: Information Elements in a PFCP Association Setup Request

Information

elements

P

Condition / Comment

Appl.

IE Type

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

Recovery Time Stamp

M

This IE shall contain the time stamp when the CP or UP function was started, see clause 19A of 3GPP TS 23.007 [24]. (NOTE)

X

X

X

X

X

Recovery Time Stamp

UP Function Features

C

This IE shall be present if the UP function sends this message and the UP function supports at least one UP feature defined in this IE.

When present, this IE shall indicate the features the UP function supports.

X

X

X

X

X

UP Function Features

CP Function Features

C

This IE shall be present if the CP function sends this message and the CP function supports at least one CP feature defined in this IE.

When present, this IE shall indicate the features the CP function supports.

X

X

X

X

X

CP Function Features

Alternative SMF IP Address

O

This IE may be present if the (MB-)SMF advertises the support of the SSET and/or MPAS feature in the CP Function Features IE (see clause 8.2.58).

When present, this IE shall contain an IPv4 and/or IPv6 address of an alternative (MB-)SMF or an alternative PFCP entity in the same (MB-)SMF when SSET feature is used, or an alternative PFCP entity in the same (MB-)SMF when MPAS feature is used.

Several IEs with the same IE type may be present to represent multiple alternative (MB-)SMF IP addresses.

X

X

Alternative SMF IP Address

SMF Set ID

C

This IE shall be present if the (MB-)SMF advertises the support of the MPAS feature in the CP Function Features IE (see clause 5.22.3).

When present, this IE shall contain an FQDN representing the (MB-)SMF set to which the (MB-)SMF belongs.

X

X

SMF Set ID

PFCP Session Retention Information

O

This IE may be present to request the UP function to keep all or part of the existing PFCP sessions upon receipt of a PFCP association setup request with a Node ID for which a PFCP association was already established. See clause 6.2.6.2.1.

X

X

X

X

X

PFCP Session Retention Information

UE IP address Pool Information

O

This IE may be present when the UP function sends this message, if UE IP Address Pools are configured in the UP function.

Several IE with the same IE type may be present to represent multiple UE IP address Pool Information.

X

X

UE IP address Pool Information

GTP-U Path QoS Control Information

C

This IE may be present, if the CP function sends this message, to request the UPF to monitor the QoS on GTP-U paths (see clause 5.24.5).

Several IEs with the same IE type may be present to represent multiple GTP-U paths (with different parameters) to monitor.

X

GTP-U Path QoS Control Information

Clock Drift Control Information

O

This IE may be present, if the CP function sends this message, to request the UPF to report clock drift between the external time and 5GS time for working domains (see clause 5.26.4).

Several IEs with the same IE type may be present for multiple Time domains (with different parameters).

X

Clock Drift Control Information

UPF Instance ID

O

This IE may be present if the UP function is a 5G UP function and if available, and if the message is sent by the UP function.

X

X

NF Instance ID

PFCPASReq-Flags

O

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

– UUPSI (UPF configured for IPUPS): when the message is sent by a UPF, the UP function shall set this flag to "1" if the UPF is configured to be used for IPUPS. See clause 5.27.

X

PFCPASReq-Flags

NOTE: A PFCP function shall ignore the Recovery Timestamp received in the PFCP Association Setup Request message.

Table 7.4.4.1-2: PFCP Session Retention Information IE within PFCP Association Setup Request

Octet 1 and 2

PFCP Session Retention Information IE Type = 183 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

CP PFCP Entity IP Address

O

This IE may be present to indicate the IP address of a CP PFCP entity for which the UP function shall retain the existing PFCP sessions, upon receipt of a PFCP association setup request with a Node ID for which a PFCP association was already established. See clause 6.2.6.2.1

Several IEs with the same IE type may be present to represent multiple CP PFCP entities for which PFCP sessions shall be retained.

If no CP PFCP Entity IP Address IE is present in the PFCP Session Retention Information IE, all existing PFCP sessions shall be kept upon receipt of a PFCP association setup request with a Node ID for which a PFCP association was already established.

X

X

X

X

X

CP PFCP Entity IP Address

Table 7.4.4.1-3: UE IP address Pool Information IE within PFCP Association Setup Request

Octet 1 and 2

UE IP address Pool Information IE Type = 233 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

UE IP address Pool Identity

M

When present, this IE shall contain an UE IP address Pool Identity

Several IEs with the same IE type may be present to represent multiple UE IP address Pool Identities.

X

X

UE IP address Pool Identity

Network Instance

O

The IE may be present to indicate for which DNN/APN the UE IP Address Pool Identifies are configured.

X

X

Network Instance

S-NSSAI

O

The IE may be present to indicate for which S-NSSAI the UE IP Address Pool Identities are configured.

Several IEs with the same IE type may be present to represent multiple S-NSSAIs.

X

S-NSSAI

IP version

O

The IE may be present to indicate for which IP version the UE IP Address Pool Identities are configured.

X

IP version

7.4.4.1.2 Clock Drift Control Information IE within PFCP Association Setup Request

The Clock Drift Control Information grouped IE shall be encoded as shown in Table 7.4.4.1.2-1.

Table 7.4.4.1.2-1: Clock Drift Control Information within PFCP Association Setup Request

Octet 1 and 2

Clock Drift Control Information IE Type = 203 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Requested Clock Drift Information

M

This IE shall indicate the requested clock drift information.

X

Requested Clock Drift Information

Time Domain Number

C

When present, this IE shall identifiy the external time domain(s) for which clock drift information is requested.

More than one IE with this type may be included to represent multiple Time Domain Numbers.

This IE may be included if the Configured Time Domain IE is not included. (NOTE)

X

Time Domain Number

Configured Time Domain

C

When present with the CTDI (Configured Time Domain Indicator) flag set to "1", this IE indicates that the request targets the external time domain that is configured to the NW-TT(s) in the UPF.

This IE may be included if the Time Domain Number IE is not included. (NOTE)

X

Configured Time Domain

Time Offset Threshold

C

This IE shall be present if Time Offset Reporting is requested.

When present, it shall indicate the threshold to report the time offset, i.e. the offset shall be reported only when it exceeds the threshold compared to the previous report.

X

Time Offset Threshold

Cumulative rateRatio Threshold

C

This IE shall be present if Cumulative RateRatio Reporting is requested.

When present, it shall indicate the threshold to report the cumulative rateRatio, i.e. the cumative rateRatio shall be reported only when it exceeds the threshold compared to the previous report.

X

Cumulative rateRatio Threshold

NOTE: If neither the Time Domain Number IE nor the Configured Time Domain IE is included, this indicates that the request targets all the external time domains the UPF is connected to.

7.4.4.1.3 GTP-U Path QoS Control Information IE within PFCP Association Setup Request

The GTP-U Path QoS Control Information grouped IE shall be encoded as shown in Table 7.4.4.1.3-1.

Table 7.4.4.1.3-1: GTP-U Path QoS Control Information within PFCP Association Setup Request

Octet 1 and 2

GTP-U Path QoS Control Information IE Type = 239 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Remote GTP-U Peer

C

When present, this IE shall include the IP address of the remote GTP-U peer for which QoS information is to be reported, and the network instance used towards the remote GTP-U peer if available.

Several IEs with the same IE type may be present to represent multiple remote GTP-U peers.

(NOTE)

X

Remote GTP-U Peer

GTP-U Path Interface Type

C

When present, this IE shall include the Interface Type of the GTP-U paths for which QoS information is to be reported.

(NOTE)

X

GTP-U Path Interface Type

QoS Report Trigger

M

This IE shall indicate the trigger for reporting QoS information to the SMF.

X

QoS Report Trigger

DSCP

C

This IE shall be present, if available. When present, it shall contain the value of the DSCP in the TOS/Traffic Class field to measure the packet delay.

Several IEs with the same IE type may be present to represent multiple DSCP values to use for QoS monitoring.

X

Transport Level Marking

Measurement Period

C

This IE shall be present if the QoS Report Trigger indicates periodic reporting. When present, it shall contain the time period for the QoS reports towards the SMF.

X

Measurement Period

Average Packet Delay Threshold

C

This IE may be present if the QoS Report Trigger indicates reporting based on thresholds.

X

Average Packet Delay

Minimum Packet Delay Threshold

C

This IE may be present if the QoS Report Trigger indicates reporting based on thresholds.

X

Minimum Packet Delay

Maximum Packet Delay Threshold

C

This IE may be present if the QoS Report Trigger indicates reporting based on thresholds.

X

Maximum Packet Delay

Minimum Waiting Time

C

This IE may be present if the QoS Report Trigger indicates reporting based on thresholds. When present, it shall contain the minimum waiting time between two consecutive reports for the same type of measurement and the same remote GTP-U peer.

X

Timer

NOTE: At least one Remote GTP-U Peer IE or GTP-U Path Interface Type IE shall be present.

7.4.4.2 PFCP Association Setup Response

Table 7.4.4.2-1: Information Elements in a PFCP Association Setup Response

Information

elements

P

Condition / Comment

Appl.

IE Type

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 or the rejection of the corresponding request message.

X

X

X

X

X

Cause

Recovery Time Stamp

M

This IE shall contain the time stamp when the CP or UP function was started, see clause 19A of 3GPP TS 23.007 [24]. (NOTE)

X

X

X

X

X

Recovery Time Stamp

UP Function Features

C

This IE shall be present if the UP function sends this message and the UP function supports at least one UP feature defined in this IE.

When present, this IE shall indicate the features the UP function supports.

X

X

X

X

X

UP Function Features

CP Function Features

C

This IE shall be present if the CP function sends this message and the CP function supports at least one CP feature defined in this IE.

When present, this IE indicates the features the CP function supports.

X

X

X

X

X

CP Function Features

Alternative SMF IP Address

O

This IE may be present if the (MB-)SMF advertises the support of the SSET and/or MPAS feature in the CP Function Features IE (see clause 8.2.58).

When present, this IE shall contain an IPv4 and/or IPv6 address of an alternative (MB-)SMF or an alternative PFCP entity in the same (MB-)SMF when SSET feature is used, or an alternative PFCP entity in the same (MB-)SMF when MPAS feature is used.

Several IEs with the same IE type may be present to represent multiple alternative (MB-)SMF IP addresses.

X

X

Alternative SMF IP Address

SMF Set ID

C

This IE shall be present if the CP function sends this message and (MB-)SMF advertises the support of the MPAS feature in the CP Function Features IE (see clause 5.22.3).

When present, this IE shall contain an FQDN representing the (MB-)SMF set to which the (MB-)SMF belongs.

X

X

SMF Set ID

PFCPASRsp-Flags

O

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

– PSREI (PFCP Session Retained Indication): the UP function shall set this flag to "1" if the PFCP Session Retention Information IE was received in the Request, an existing PFCP association was already established for the same Node ID and the requested PFCP sessions have been retained. See clause 6.2.6.2.2.

– UUPSI (UPF configured for IPUPS): the UP function shall set this flag to "1" if the UPF is configured to be used for IPUPS. See clause 5.27.

X

X

X

X

X

X

PFCPASRsp-Flags

Clock Drift Control Information

C

This IE may be present, if the CP function sends this message, to request the UPF to report clock drift between the external time and 5GS time for external working domains (see clause 5.26.4).

Several IEs with the same IE type may be present to represent multiple external time domains (with different parameters).

See Table 7.4.4.1.2-1.

X

Clock Drift Control Information

UE IP address Pool Information

O

This IE may be present when the UP function sends this message, if UE IP Address Pools are configured in the UP function.

Several IE with the same IE type may be present to represent multiple UE IP address Pool Information.

The IE shall be encoded as in Table 7.4.4.1-3.

X

X

UE IP address Pool Information

GTP-U Path QoS Control Information

C

This IE may be present, if the CP function sends this message, to request the UPF to monitor the QoS on GTP-U paths (see clause 5.24.5).

Several IEs with the same IE type may be present to represent multiple GTP-U paths to monitor.

See Table 7.4.4.1.3-1.

X

GTP-U Path QoS Control Information

UPF Instance ID

O

This IE may be present if the UP function is a 5G UP function and if available, and if the message is sent by the UP function.

X

X

NF Instance ID

NOTE: A PFCP function shall ignore the Recovery Timestamp received in PFCP Association Setup Response message.

7.4.4.3 PFCP Association Update Request

Table 7.4.4.3-1: Information Elements in a PFCP Association Update Request

Information

elements

P

Condition / Comment

Appl.

IE Type

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

UP Function Features

O

If present, this IE shall indicate the supported Features when the sending node is the UP function.

X

X

X

X

X

UP Function Features

CP Function Features

O

If present, this IE shall indicate the supported Features when the sending node is the CP function.

X

X

X

X

X

CP Function Features

PFCP Association Release Request

C

This IE shall be present if the UP function requests the CP function to release the PFCP association.

X

X

X

X

X

PFCP Association Release Request

Graceful Release Period

C

This IE shall be present if the UP function requests a graceful release of the PFCP association.

X

X

X

X

X

Graceful Release Period

PFCPAUReq-Flags

O

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

– PARPS (PFCP Association Release Preparation Start): if both the CP function and UP function support the EPFAR feature, the CP or UP function may set this flag to "1" to indicate that the PFCP association is to be released and all non-zero usage reports for those PFCP Sessions affected by the release of the PFCP association shall be reported.

X

X

X

X

PFCPAUReq-Flags

Alternative SMF IP Address

O

This IE may be present if the (MB-)SMF advertises the support of the SSET and/or MPAS feature in the CP Function Features IE (see clause 8.2.58).

When present, this IE shall contain an IPv4 and/or IPv6 address of an alternative (MB-)SMF or an alternative PFCP entity in the same (MB-)SMF when SSET feature is used, or an alternative PFCP entity in the same (MB-)SMF when MPAS feature is used.

Several IEs with the same IE type may be present to represent multiple alternative (MB-)SMF IP addresses.

X

X

Alternative SMF IP Address

SMF Set ID

O

This IE may be present if the CP function sends this message and (MB-)SMF advertises the support of the MPAS feature in the CP Function Features IE (see clause 5.22.3), and there is a change in FQDN representing the (MB-)SMF set to which the (MB-)SMF belongs.

X

X

SMF Set ID

Clock Drift Control Information

C

This IE shall be present if the Clock Drift Control Information needs to be modified (see clause 5.26.4).

Several IEs with the same IE type may be present to represent TSN domains.

When present, the UPF shall replace any Clock Drift control information received earlier with the new received information.

A Clock Drift Control Information with a null length indicates that clock drift reporting shall be stopped.

See Table 7.4.4.1.2-1.

X

Clock Drift Control Information

UE IP address Pool Information

O

This IE may be present when the UP function sends this message, if UE IP Address Pools are configured in the UP function.

Several IE with the same IE type may be present to represent multiple UE IP address Pool Information.

The IE shall be encoded as in Table 7.4.4.1-3.

X

X

UE IP address Pool Information

GTP-U Path QoS Control Information

C

This IE shall be present if the GTP-U Path QoS Control Information needs to be modified (see clause 5.24.5).

Several IEs with the same IE type may be present to represent multiple GTP-U paths to monitor.

When present, the UPF shall replace any GTP-U path control information received earlier with the new received information.

A GTP-U Path QoS Control Information with a null length indicates that QoS monitoring of GTP-U paths shall be stopped.

See Table 7.4.4.1.3-1.

X

GTP-U Path QoS Control Information

UE IP Address Usage Information

O

The UP function may include this IE if both UP and CP functions support the UE IP Address Usage Reporting feature.

See Table 7.4.4.3.1-1

Several IEs with the same type may be present to represent UE IP Address Usage Information for different UE IP Address Pools and/or Network Instances.

See clause 5.21.3.

X

X

UE IP Address Usage Information

7.4.4.3.1 UE IP Address Usage Information IE within PFCP Association Update Request

The UE IP Address Usage Information grouped IE shall be encoded as shown in Figure 7.4.4.3.1-1.

Table 7.4.4.3.1-1: UE IP Address Usage Information IE within PFCP Association Update Request

Octet 1 and 2

UE IP Address Usage Information IE Type = 267 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

UE IP Address Usage Sequence Number

M

This IE shall be used by the CP function to properly collate out-of-order UE IP Address Usage Information received for a given network instance and/or UE IP Address pool, e.g. due to PFCP retransmissions. This IE shall also be used by the receiver to determine whether the newly received UE IP Address Usage Information has changed compared to UE IP Address Usage Information previously received from the same node earlier.

X

X

Sequence Number

UE IP Address Usage Metric

M

This IE shall represent the current ratio of occupied UE IP addresses in the UP function for the Network Instance indicated in the Network Instance IE, or for the Network Instance indicated in the Network Instance IE and the UE IP address Pool indicated by the UE IP Address Pool Id IE when this IE is present. The value shall be expressed as a percentage within the range of 0 to 100, where 0 means no or 0% usage and 100 means maximum or 100% usage reached (i.e. it is not desirable to receive further PFCP Session Establishment Requests).

X

X

Metric

Validity Timer

M

This IE shall represent the period of time during which the UE IP Address Usage Information shall be considered as valid.

X

X

Validity Timer

Number of UE IP Addresses

M

This IE shall indicate the total number of UE IP addresses configured for the Network Instance or also for the IP address Pool, when this IE is present. (NOTE)

X

X

Number of UE IP Addresses

Network Instance

M

This IE shall identify the associated Network instance.

X

X

Network Instance

UE IP Address Pool Id

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 the associated UE IP address Pool.

X

X

UE IP address Pool Identity

S-NSSAI

O

This IE may be present if the feature "Per slice UP resource management" is supported by the UP Function.

When present, it shall indicate the S-NSSAI for which the UE IP addresses usage information is reported.

X

X

S-NSSAI

NOTE: When reporting the number of IPv6 UE Addresses for a specific Network Instance and/or IP address pool, the number of default /64 prefixes is reported by default, unless configured otherwise.

7.4.4.4 PFCP Association Update Response

Table 7.4.4.4-1: Information Elements in a PFCP Association Update Response

Information

elements

P

Condition / Comment

Appl.

IE Type

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 or the rejection of the corresponding request message.

X

X

X

X

X

Cause

UP Function Features

O

If present, this IE shall indicate the supported Features when the sending node is the UP function.

X

X

X

X

X

UP Function Features

CP Function Features

O

If present, this IE shall indicate the supported Features when the sending node is the CP function.

X

X

X

X

X

CP Function Features

UE IP Address Usage Information

O

The UP function may include if both UP and CP functions support the UE IP Address Usage Reporting feature.

See Table 7.4.4.3.1-1.

Several IEs with the same type may be present to represent UE IP Address Usage Information for different UE IP Address Pools and/or Network Instances.

See clause 5.21.3.

X

X

UE IP Address Usage Information

7.4.4.5 PFCP Association Release Request

Table 7.4.4.5-1: Information Elements in a PFCP Association Release Request

Information

elements

P

Condition / Comment

Appl.

IE Type

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

7.4.4.6 PFCP Association Release Response

Table 7.4.4.6-1: Information Elements in a PFCP Association Release Response

Information

elements

P

Condition / Comment

Appl.

IE Type

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 or the rejection of the corresponding request message.

X

X

X

X

X

Cause

7.4.4.7 PFCP Version Not Supported Response

This message shall only contain the PFCP header. The PFCP protocol version in the PFCP header shall indicate the highest PFCP Version that the sending entity supports.

NOTE: The PFCP Version Not Supported Response message can be received by a PFCP entity when sending the very first message to a PFCP peer only supporting earlier version(s) of the protocol.

7.4.5 PFCP Node Report Procedure

7.4.5.1 PFCP Node Report Request

7.4.5.1.1 General

The PFCP Node Report Request shall be sent over the Sxa, Sxb, Sxc, N4 and N4mb interface by the UP function to report information to the CP function that is not specific to a PFCP session.

Table 7.4.5.1.1-1: Information Elements in PFCP Node Report Request

Information elements

P

Condition / Comment

Appl.

IE Type

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

Node Report Type

M

This IE shall indicate the type of the report.

X

X

X

X

X

Node Report Type

Vendor-Specific Node Report Type

C

This IE shall be present if the Node Report Type IE indicates a Vendor-Specific Report. When present, this IE shall indicate the type of the Vendor-Specific Report.

X

X

X

X

X

Vendor-Specific Node Report Type

User Plane Path Failure Report

C

This IE shall be present if the Node Report Type indicates a User Plane Path Failure Report.

X

X

X

X

User Plane Path Failure Report

User Plane Path Recovery Report

C

This IE shall be present if the Node Report Type indicates a User Plane Path Recovery Report.

X

X

X

X

User Plane Path Recovery Report

Clock Drift Report

C

This IE shall be present if the Node Report Type indicates a Clock Drift Report.

More than one IE with this type may be included to send Clock Drift Reports for different Time Domain Numbers.

X

Clock Drift Report

GTP-U Path QoS Report

C

This IE shall be present if the Node Report Type indicates a GTP-U Path QoS Report.

More than one IE with this type may be included to represent multiple remote GTP-U peers for which QoS information is reported.

X

GTP-U Path QoS Report

Peer UP Restart Report

C

This IE shall be present if the Node Report Type Indicates a Peer GTP-U entity has restarted as specified in clause 20.3.4a of 3GPP TS 23.007 [24] and in clause 5.5 of 3GPP TS 23.527 [40].

X

X

X

Peer UP Restart Report

7.4.5.1.2 User Plane Path Failure Report IE within PFCP Node Report Request

Table 7.4.5.1.2-1: User Plane Path Failure Report IE within PFCP Node Report Request

Octet 1 and 2

User Plane Path Failure Report IE Type = 102 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Remote GTP-U Peer

M

This IE shall include the IP address of the remote GTP-U peer towards which a user plane path failure has been detected.

More than one IE with this type may be included to represent multiple remote GTP-U peers towards which a user plane path failure has been detected.

X

X

X

X

Remote GTP-U Peer

7.4.5.1.3 User Plane Path Recovery Report IE within PFCP Node Report Request

Table 7.4.5.1.3-1: User Plane Path Recovery Report IE within PFCP Node Report Request

Octet 1 and 2

User Plane Path Recovery Report IE Type = 187 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Remote GTP-U Peer

M

This IE shall include the IP address of the remote GTP-U peer towards which user plane path failure was reported and then the path has recovered within an operator configurable maximum path failure duration (see clause 20.3.4 in 3GPP TS 23.007 [24] and clause 5.4 in 3GPP TS 23.527 [40]).

More than one IE with this type may be included to represent multiple remote GTP-U peers towards which a user plane path has recovered.

X

X

X

X

Remote GTP-U Peer

7.4.5.1.4 Clock Drift Report IE within PFCP Node Report Request

Table 7.4.5.1.4-1: Clock Drift Report IE within PFCP Node Report Request

Octet 1 and 2

Clock Drift Report IE Type = 205 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Time Domain Number

M

This IE shall identify the Time Domain Number for which measurements are reported.

X

Time Domain Number

Time Offset Measurement

O

When present, this IE shall contain the time offset measurement.

X

Time Offset Measurement

Cumulative rateRatio Measurement

O

When present, this IE shall contain the cumulative rateRatio measurement.

X

Cumulative rateRatio Measurement

Time Stamp

O

When present, this IE shall provide the timestamp when the collection of the information in this report was generated.

X

Time Stamp

Network Instance

C

This IE shall be present, when available (NOTE).

X

Network Instance

APN/DNN

C

This IE shall be present, when available (NOTE).

X

APN/DNN

S-NSSAI

C

This IE shall be present, when available (NOTE).

X

S-NSSAI

NOTE: The UPF shall provide the Network Instance and DNN/S-NSSAI (if available) to the CP function, to enable SMF to associate the report with the corresponding PFCP sessions and NW-TT, when the UPF supports more than one NW-TT.

7.4.5.1.5 GTP-U Path QoS Report IE within PFCP Node Report Request

Table 7.4.5.1.5-1: GTP-U Path QoS Report IE within PFCP Node Report Request

Octet 1 and 2

GTP-U Path QoS Report IE Type = 239 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Remote GTP-U Peer

M

This IE shall include the IP address of the remote GTP-U peer for which QoS information is reported, and the network instance used towards the remote GTP-U peer if available.

X

Remote GTP-U Peer

GTP-U Path Interface Type

C

This IE shall be present, if available. When present, it shall indicate the interface type of the GTP-U path towards the remote GTP-U peer.

X

GTP-U Path Interface Type

QoS Report Trigger

M

This IE shall indicate the trigger for this report.

X

QoS Report Trigger

Time Stamp

M

This shall shall provide the timestamp when the collection of the information in this report was generated.

X

Time Stamp

Start Time

C

This shall shall provide the timestamp when the collection of the information in this report was started.

X

Start Time

QoS Information

M

This IE shall contain the measured QoS information.

More than one IE with this type may be included to represent multiple QoS Information, e.g. for different DSCP values.

X

QoS Information

7.4.5.1.6 QoS Information in GTP-U Path QoS Report IE

Table 7.4.5.1.6-1: QoS Information in GTP-U Path QoS Report IE

Octet 1 and 2

QoS Information IE Type = 240 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Average Packet Delay

M

This IE shall indicate the average packet delay of the related GTP-U path.

X

Average Packet Delay

Minimum Packet Delay

C

This IE shall indicate the minimum packet delay of the related GTP-U path, if available.

X

Minimum Packet Delay

Maximum Packet Delay

C

This IE shall indicate the maximum packet delay of the related GTP-U path, if available.

X

Maximum Packet Delay

DSCP

C

This IE shall be present, if available. When present, it shall contain the value of the DSCP in the TOS/Traffic Class field used in Echo messages to measure the packet delay.

X

Transport Level Marking

7.4.5.1.7 Peer UP Restart Report IE within PFCP Node Report Request
7.4.5.1.7 Peer UP Restart Report IE within PFCP Node Report Request

Table 7.4.5.1.7-1: Peer UP Restart Report IE within PFCP Node Report Request

Octet 1 and 2

Peer UP Restart Report Type = 315 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Remote GTP-U Peer

M

This IE shall include the IP address of the remote GTP-U peer which has restarted.

More than one IE with this type may be included to represent that multiple peer GTP-U entities restart.

X

X

X

X

Remote GTP-U Peer

7.4.5.2 PFCP Node Report Response

7.4.5.2.1 General

The PFCP Node Report Response shall be sent over the Sxa, Sxb; Sxc, N4 and N4mb interface by the CP function to the UP function as a reply to the PFCP Node Report Request.

Table 7.4.5.2.1-1: Information Elements in PFCP Node Report Response

Information elements

P

Condition / Comment

Appl.

IE Type

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 or the rejection of the corresponding request message.

X

X

X

X

X

Cause

Offending IE

C

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

X

X

X

X

X

Offending IE

7.4.6 PFCP Session Set Deletion

7.4.6.1 PFCP Session Set Deletion Request

The PFCP Session Set Deletion Request shall be sent over the Sxa, Sxb or N4 interface by the CP function to request the UP function to delete the PFCP sessions affected by a partial failure.

The PFCP Session Set Deletion Request shall be also sent over the Sxa, Sxb or N4 interface by the UP function to request the CP function to delete the PFCP sessions affected by a partial failure.

Table 7.4.6.1-1: Information Elements in a PFCP Session Set Deletion Request

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Node ID

M

This IE shall contain the node identity of the originating node of the message.

X

X

X

Node ID

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

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

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

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

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

MME 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

7.4.6.2 PFCP Session Set Deletion Response

The PFCP Session Set Deletion Response shall be sent over the Sxa, Sxb or N4 interface by the UP function or the CP function as a reply to the PFCP Session Set Deletion Request.

Table 7.4.6.2-1: Information Elements in a PFCP Session Set Deletion Response

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Node ID

M

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

X

X

X

Node ID

Cause

M

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

X

X

X

Cause

Offending IE

C

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

X

X

X

Offending IE

7.4.7 PFCP Session Set Modification

7.4.7.1 PFCP Session Set Modification Request

The PFCP Session Set Modification Request shall be sent over the Sxb or N4 interface by the CP function to request the UP function to send any subsequent PFCP Session Report Request messages for the PFCP sessions which are identified by either FQ-CSID(s) or Group Id(s), or the CP IP Address in their F-SEIDs, towards an (alternative) SMF/PGW-C, e.g. when those PFCP sessions are affected by a partial PGW-C/SMF failure or are controlled by a PGW-C/SMF that is shutting down.

This procedure shall only be performed if the UP function indicated support of the RESPS feature (see clause 8.2.25).

Table 7.4.7.1-1: Information Elements in a PFCP Session Set Modification Request

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Node ID

M

This IE shall contain the node identity of the originating node of the message.

X

X

Node ID

PFCP Session Change Info

M

This IE shall identify the FQ-CSID(s), Group Id(s) or CP IP address(es) of the PFCP sessions for which the PGW-U/UPF shall send subsequent PFCP Session Report Request messages to an Alternative SMF/PGW-C IP Address.

Several IEs with the same IE type may be present to request the PGW-U/UPF to move PFCP sessions associated with different FQ-CSIDs, Group Ids or CP IP addresses to different PGW-C/SMFs.

X

X

PFCP Session Change Info

Table 7.4.7.1-2: PFCP Session Change Info IE within PFCP Session Set Modification Request

Octet 1 and 2

PFCP Session Change Info IE Type = 290 (decimal)

Octets 3 and 4

Length = n

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

PGW-C/SMF FQ-CSID

C

This IE shall identify the PGW-C/SMF FQ-CSID of the PFCP sessions for which the UPF shall send subsequent PFCP Session Report Request messages to the Alternative SMF/PGW-C IP Address.

See also clause 31.6 of 3GPP TS 23.007 [24] and clause 4.7 of 3GPP TS 23.527 [40].

Several IEs with the same IE type may be present to represent several FQ-CSIDs of PFCP sessions that need to be moved to the same Alternative SMF/PGW-C IP Address.

X

X

FQ-CSID

Group Id

C

This IE shall identify the Group Id of the PFCP sessions for which the UPF shall send subsequent PFCP Session Report Request messages to the Alternative SMF/PGW-C IP Address.

See also clause 31.6 of 3GPP TS 23.007 [24] and clause 4.7 of 3GPP TS 23.527 [40].

Several IEs with the same IE type may be present to represent several Group Ids of PFCP sessions that need to be moved to the same Alternative SMF/PGW-C IP Address.

X

X

Group-Id

CP IP Address

C

This IE shall identify the IP address in the CP F-SEID of the PFCP sessions for which the UPF shall send subsequent PFCP Session Report Request messages to the Alternative SMF/PGW-C IP Address.

Several IEs with the same IE type may be present to represent several CP IP addresses of PFCP sessions that need to be moved to the same Alternative SMF/PGW-C IP Address.

X

X

CP IP Address

Alternative SMF/PGW-C IP Address

M

This IE shall include the alternative SMF/PGW-C IP Address to be used by the UP function to send subsequent PFCP Session Report Request messages for the PFCP Sessions associated with the PGW-C/SMF FQ-CSID(s), Group Id(s) or CP IP address(es).

When present, this IE shall contain an IPv4 and/or IPv6 address of the same or an alternative SMF/PGW-C.

X

X

Alternative SMF IP Address

7.4.7.2 PFCP Session Set Modification Response

The PFCP Session Set Modification Response shall be sent over the Sxb or N4 interface by the UP function to the CP function as a reply to the PFCP Session Set Modification Request.

Table 7.4.2.2-1: Information Elements in a PFCP Session Set Modification Response

Information elements

P

Condition / Comment

Appl.

IE Type

Sxa

Sxb

Sxc

N4

N4mb

Node ID

M

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

X

X

Node ID

Cause

M

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

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

Offending IE