7.5.8 PFCP Session Report Request
29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS
7.5.8.1 General
The PFCP Session Report Request shall be sent over the Sxa, Sxb, Sxc, N4 and N4mb interface by the UP function to report information related to a PFCP session to the CP function.
Table 7.5.8.1-1: Information Elements in a PFCP Session Report Request
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
||||
Report Type |
M |
This IE shall indicate the type of the report. |
X |
X |
X |
X |
X |
Report Type |
Downlink Data Report |
C |
This IE shall be present if the Report Type indicates a Downlink Data Report. |
X |
– |
– |
X |
X |
Downlink Data Report |
Usage Report |
C |
This IE shall be present if the Report Type indicates a Usage Report. Several IEs within the same IE type may be present to represent a list of Usage Reports. |
X |
X |
X |
X |
– |
Usage Report |
Error Indication Report |
C |
This IE shall be present if the Report Type indicates an Error Indication Report. |
X |
X |
– |
X |
X |
Error Indication Report |
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 |
Additional Usage Reports Information |
C |
This IE shall be included in one of the additional PFCP Session Report Request messages, if the PFCP Session Modification Response or the PFCP Session Deletion Response indicated that more usage reports would follow (i.e. if the AURI flag was set to "1") (see clause 5.2.2.3.1). When present, this IE shall indicate the total number of usage reports that need to be sent in all the additional PFCP Session Report Request messages. This IE may also be included in every additional PFCP Session Report Request message but the last one, with the AURI flag set to 1, to indicate that more usage reports will follow in additional PFCP Session Report Request message. |
X |
X |
X |
X |
– |
Additional Usage Reports Information |
PFCPSRReq-Flags |
C |
This IE shall be included if at least one of the flags is set to "1". – PSDBU (PFCP Session Deleted By the UP function): – the UP function shall also set this flag when sending the last PFCP Session Report Request message after having received a PFCP Session Deletion Request (see clause 5.2.2.3.1). |
X |
X |
X |
X |
– |
PFCPSRReq-Flags |
Old CP F-SEID |
C |
This IE shall be present if the UPF sends the PFCP Session Report Request to a different SMF in an SMF Set. See clauses 5.22.2 and 5.22.3. When present, it shall indicate the CP F-SEID assigned by the previous SMF to the PFCP session. |
– |
– |
– |
X |
X |
F-SEID |
Packet Rate Status Report |
C |
This IE shall be present if the EPFAR is used (see clause 5.18), UP function initiates a PFCP Session release and the CP function has requested in a QER to report the packet rate status when the PFCP session is released. See Table 7.5.7.1-1. |
– |
X |
– |
X |
– |
Packet Rate Status Report |
TSC Management Information |
C |
This IE shall be present if the Report Type indicates TSC Management Information Report. Several IEs within the same IE type may be present to transfer PMICs for different NW-TT ports. (NOTE). |
– |
– |
– |
X |
– |
TSC Management Information |
Session Report |
C |
This IE shall be present if the Report Type indicates a Session Report. See Table 7.5.8.6-1. Several IEs within the same IE type may be present to represent a list of Session Reports. |
– |
– |
– |
X |
– |
Session Report |
Cause |
O |
This IE may be present to provide additional reason for sending the PFCP Session Report Request message, e.g. for a UP function initiated PFCP session deletion due to the corresponding L2TP session being terminated. |
– |
X |
– |
X |
– |
Cause |
NOTE: When transferring port and user plane node management information between the TSN AF or the TSCTSF and NW-TT, since the NW-TT may support multiple ports, there may be several instances of the TSC Management Information IEs containing a Port Management Information Container together with a NW-TT Port Number, and only one instance of the TSC Management Information IE containing a User Plane Node Management Information Container that may also contain a Port Management Information Container together with a NW-TT Port Number. |
7.5.8.2 Downlink Data Report IE within PFCP Session Report Request
The Downlink Data Report grouped IE shall be encoded as shown in Table 7.5.8.2-1.
Table 7.5.8.2-1: Downlink Data Report IE within PFCP Session Report Request
Octet 1 and 2 |
Downlink Data Report IE Type = 83 (decimal) |
||||||||
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 identify the PDR for which downlink data packets have been received or discarded at the UP function. More than one IE with this type may be included to represent multiple PDRs having received or discarded downlink data packets. |
X |
– |
– |
X |
X |
PDR ID |
|
Downlink Data Service Information |
C |
This IE shall be included for a PFCP session with an IP PDN type, if the UP function supports the Paging Policy Differentiation feature (see clause 4.9 of 3GPP TS 23.401 [14]) and clause 5.4.3.2 of 3GPP TS 23.501 [28]). When present, for each PDR and for each packet that triggers a Downlink Data Notification, the UP function shall copy, into the Paging Policy Indication value within this IE, the value of the DSCP in TOS (IPv4) or TC (IPv6) information received in the IP payload of the GTP-U packet from the PGW (see IETF RFC 2474 [13]). For 5GC, this IE shall also be included over N4, for each PDR and for each packet that triggers a Downlink Data Notification, if the QFI of the downlink data packet is available. One IE with this type shall be included per PDR ID reported in the message. When multiple PDR ID IEs are present in the message, the Downlink Data Service Information IEs shall be reported according to the order of the PDR ID IEs. |
X |
– |
– |
X |
– |
Downlink Data Service Information |
|
DL Data Packets Size |
O |
This IE may be present if the SGW-U supports the MT-EDT feature and is requested to report the sum of the DL Data Packets Size. |
X |
– |
– |
– |
– |
DL Data Packets Size |
|
DL Data Status |
O |
This IE may be present if the first downlink data packet has been buffered or discarded at the UP function for downlink data delivery status notification. |
– |
– |
– |
X |
– |
Data Status |
7.5.8.3 Usage Report IE within PFCP Session Report Request
The Usage Report grouped IE shall be encoded as shown in Table 7.5.8.3-1.
Table 7.5.8.3-1: Usage Report IE within PFCP Session Report Request
Octet 1 and 2 |
Usage Report IE Type = 80 (decimal) |
||||||||
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 identify the URR for which usage is reported. |
X |
X |
X |
X |
– |
URR ID |
|
UR-SEQN |
M |
This IE shall uniquely identify the Usage Report for the URR (see clause 5.2.2.3). |
X |
X |
X |
X |
– |
UR-SEQN |
|
Usage Report Trigger |
M |
This IE shall identify the trigger for this report. |
X |
X |
X |
X |
– |
Usage Report Trigger |
|
Start Time |
C |
This IE shall be present, except if the Usage Report Trigger indicates ‘Start of Traffic’, ‘Stop of Traffic’ or ‘MAC Addresses Reporting’. When present, this IE shall provide the timestamp when the collection of the information in this report was started. |
X |
X |
X |
X |
– |
Start Time |
|
End Time |
C |
This IE shall be present, except if the Usage Report Trigger indicates ‘Start of Traffic’, ‘Stop of Traffic’ or ‘ MAC Addresses Reporting’. When present, this IE shall provide the timestamp when the collection of the information in this report was generated. |
X |
X |
X |
X |
– |
End Time |
|
Volume Measurement |
C |
This IE shall be present if a volume measurement needs to be reported. (NOTE 2) |
X |
X |
X |
X |
– |
Volume Measurement |
|
Duration Measurement |
C |
This IE shall be present if a duration measurement needs to be reported. (NOTE 2) |
X |
X |
X |
X |
– |
Duration Measurement |
|
Application Detection Information |
C |
This IE shall be present if application detection information needs to be reported. |
– |
X |
X |
X |
– |
Application Detection Information |
|
UE IP address |
C |
This IE shall be present if the start or stop of an application has been detected and no UE IP address was provisioned in the PDI. See NOTE 1. |
– |
– |
X |
X |
– |
UE IP address |
|
Network Instance |
C |
This IE shall be present if the start or stop of an application has been detected, no UE IP address was provisioned in the PDI and multiple PDNs with overlapping IP addresses are used in the UP function. See NOTE 1. |
– |
– |
X |
X |
– |
Network Instance |
|
Time of First Packet |
C |
This IE shall be present if available for this URR. |
– |
X |
X |
X |
– |
Time of First Packet |
|
Time of Last Packet |
C |
This IE shall be present if available for this URR. |
– |
X |
X |
X |
– |
Time of Last Packet |
|
Usage Information |
C |
This IE shall be present if the UP function reports Usage Reports before and after a Monitoring Time, or before and after QoS enforcement. When present, it shall indicate whether the usage is reported for the period before or after that time, or before or after QoS enforcement. |
X |
X |
X |
X |
– |
Usage Information |
|
Query URR Reference |
C |
This IE shall be present if this usage report is sent as a result of a query URR received in a PFCP Session Modification Request and the Query URR Reference IE was present in the PFCP Session Modification Request. When present, it shall be set to the Query URR Reference value received in the PFCP Session Modification Request. |
X |
X |
X |
X |
– |
Query URR Reference |
|
Event Time Stamp |
C |
This IE shall be present, if the report is related to an event. When present, it shall be set to the time when the event occurs. Several IEs with the same IE type may be present to report multiple occurrences for an event for this URR ID. |
– |
X |
X |
X |
– |
Time Stamp |
|
Ethernet Traffic Information |
C |
This IE shall be present if Ethernet Traffic Information needs to be reported. See Table 7.5.8.3-3. |
– |
– |
– |
X |
– |
Ethernet Traffic Information |
|
Join IP Muticast Information |
C |
This IE shall be present if the UPF needs to report that it has added the PDU session to the DL replication tree of a new IP multicast flow. Several IEs with the same IE type may be present to report multiple IP multicast flows added to the PDU session. |
– |
– |
– |
X |
– |
Join IP Multicast Information |
|
Leave IP Muticast Information |
C |
This IE shall be present if the UPF needs to report that it has removed the PDU session from the DL replication tree of an IP multicast flow. Several IEs with the same IE type may be present to report multiple IP multicast flows removed from the PDU session. |
– |
– |
– |
X |
– |
Leave IP Multicast Information |
|
Predefined Rules Name |
O |
This IE may be present to identify a predefined rule if the usage report is generated for a predefined URR which was activated via a Activate Predefined Rules IE in a Create PDR IE or an Update PDR IE. Several IEs with the same IE type may be present to represent multiple Predefined Rules with which the URR is associated. |
– |
X |
– |
X |
– |
Predefined Rules Name |
|
NOTE 1: This is the case for unsolicited application reporting by the TDF. The Network instance is required when the UE IP address cannot be used to determine the corresponding PDN connection. NOTE 2: The UP function may send a Usage Report with the Volume/Duration Measurement set to zero. |
Table 7.5.8.3-2: Application Detection Information IE within Usage Report IE
Octet 1 and 2 |
Application Detection Information IE Type = 68 (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 a start or stop of traffic is reported. |
– |
X |
X |
X |
– |
Application ID |
|
Application Instance ID |
C |
When present, this IE shall identify the Application Instance Identifier for which a start or stop of traffic is reported. It shall be present, when reporting the start of an application, if the Reduced Application Detection Information flag was not set in the Measurement Information and if the flow information for the detected application is deducible. It shall be present, when reporting the stop of an application, if the Reduced Application Detection Information flag was not set in the Measurement Information and if it was provided when reporting the start of the application. |
– |
X |
X |
X |
– |
Application Instance ID |
|
Flow Information |
C |
When present, this IE shall contain the flow information for the detected application. It shall be present, when reporting the start of an application, if the Reduced Application Detection Information flag was not set in the Measurement Information and if the flow information for the detected application is deducible. |
– |
X |
X |
X |
– |
Flow Information |
|
PDR ID |
O |
When present, it shall contain the PDR ID which the application traffic matches. |
– |
X |
X |
X |
– |
PDR ID |
Table 7.5.8.3-3: Ethernet Traffic Information IE within Usage Report IE
Octet 1 and 2 |
Ethernet Traffic Information IE Type = 143 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
MAC Addresses Detected |
C |
This IE shall be present if one or more new MAC addresses have been detected. When present, it shall identify the MAC (Ethernet) addresses newly detected as source address of frames sent UL by the UE. Several IEs with the same IE type may be present to to provision multiple lists of MAC addresses (e.g. with different V-LAN tags). |
– |
– |
– |
X |
– |
MAC Addresses Detected |
|
MAC Addresses Removed |
C |
This IE shall be present if one or more new MAC addresses have been removed. When present, it shall identify the MAC (Ethernet) addresses that have been inactive for a duration exceeding the Ethernet inactivity Timer. Several IEs with the same IE type may be present to to provision multiple lists of MAC addresses (e.g. with different V-LAN tags). |
– |
– |
– |
X |
– |
MAC Addresses Removed |
Table 7.5.8.3-4: Join IP Multicast Information IE within Usage Report IE
Octet 1 and 2 |
Join IP Multicast Information IE Type = 189 (decimal) |
||||||||
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 of the DL multicast flow added to the PDU session. |
– |
– |
– |
X |
– |
IP Multicast Address |
|
Source IP Address |
C |
This IE shall contain the source specific IP address of the DL multicast flow added to the PDU session, if available. Several IEs with the same IE type may be present to represent multiple source specific addresses. |
– |
– |
– |
X |
– |
Source IP Address |
Table 7.5.8.3-5: Leave IP Multicast Information IE within Usage Report IE
Octet 1 and 2 |
Leave IP Multicast Information IE Type = 190 (decimal) |
||||||||
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 of the DL multicast flow removed from the PDU session. |
– |
– |
– |
X |
– |
IP Multicast Address |
|
Source IP Address |
C |
This IE shall contain the source specific IP address of the DL multicast flow removed from the PDU session, if available. Several IEs with the same IE type may be present to represent multiple source specific addresses. |
– |
– |
– |
X |
– |
Source IP Address |
7.5.8.4 Error Indication Report IE within PFCP Session Report Request
The Error Indication Report grouped IE shall be encoded as shown in Table 7.5.8.4-1.
Table 7.5.8.4-1: Error Indication Report IE within PFCP Session Report Request
Octet 1 and 2 |
Error Indication Report IE Type = 99 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Remote F-TEID |
M |
This IE shall identify the remote F-TEID of the GTP-U bearer for which an Error Indication has been received at the UP function. More than one IE with this type may be included to represent multiple remote F-TEID for which an Error Indication has been received. |
X |
X |
– |
X |
X |
F-TEID |
7.5.8.5 TSC Management Information IE within PFCP Session Report Request
The TSC Management Information grouped IE shall be encoded as shown in Table 7.5.8.5-1.
Table 7.5.8.5-1: TSC Management Information IE within PFCP Session Report Request
Octet 1 and 2 |
TSC Management Information IE Type = 201 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Port Management Information Container |
O |
When present, this IE shall contain a Port Management Information container. |
– |
– |
– |
X |
– |
Port Management Information Container |
|
User Plane Node Management Information Container |
O |
When present, this IE shall contain an User Plane Node Management Information container. |
– |
– |
– |
X |
– |
User Plane Node Management Information Container |
|
NW-TT Port Number |
C |
When PMIC IE is present, this IE shall contain the related NW-TT Port Number. |
– |
– |
– |
X |
– |
NW-TT Port Number |
7.5.8.6 Session Report IE within PFCP Session Report Request
The Session Report grouped IE shall be encoded as shown in Table 7.5.8.6-1.
Table 7.5.8.6-1: Session Report IE within PFCP Session Report Request
Octet 1 and 2 |
Session Report IE Type = 214 (decimal) |
||||||||
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 identify the SRR for which usage is reported. |
– |
– |
– |
X |
– |
SRR ID |
|
Access Availability Report |
C |
This IE shall be present if change of access availability needs to be reported. When present, this IE shall indicate an access type and whether the access type has become available or unavailable. |
– |
– |
– |
X |
– |
Access Availability Report |
|
QoS Monitoring Report |
C |
This IE shall be present if the Report Type indicates a QoS Monitoring Report. Several IEs within the same IE type may be present to represent a list of QoS Monitoring Reports, e.g. for different QoS flows. |
– |
– |
– |
X |
– |
QoS Monitoring Report |
The Access Availability Report IE shall be encoded as shown in Table 7.5.8.2-2.
Table 7.5.8.6-2: Access Availability Report IE
Octet 1 and 2 |
Access Availability Report IE Type = 218 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Access Availability Information |
M |
This IE shall indicate an access type and whether the access type has become available or not available. Up to two IEs with the same IE type may be present to report access availability changes for 3GPP and non-3GPP accesses. |
– |
– |
– |
X |
– |
Access Availability Information |
The QoS Monitoring Report IE shall be encoded as shown in Table 7.5.8.6-3.
Table 7.5.8.6-3: QoS Monitoring Report IE
Octet 1 and 2 |
QoS Monitoring Report IE Type = 247 (decimal) |
||||||||
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 reported. |
– |
– |
– |
X |
– |
QFI |
|
QoS Monitoring Measurement |
M |
This IE shall contain the measured packet delay(s). |
– |
– |
– |
X |
– |
QoS Monitoring Measurement |
|
Time Stamp |
M |
This IE shall provide the timestamp when the collection of the information in this report was generated. |
– |
– |
– |
X |
– |
Time Stamp |
|
Start Time |
O |
When present, this IE shall provide the timestamp when the collection of the information in this report was started. |
– |
– |
– |
X |
– |
Start Time |