PFCP session-related messages

PFCP Session Establishment Request

The PFCP Session Establishment Request message is initiated from the MAG-c function to create a new PFCP session on the BNG-UP.

Table 1. IEs in a PFCP Session Establishment Request
Information elements	P	Description
Node ID	M	This IE contains the unique identifier of the sending node.
F-SEID	M	This IE uniquely identifies the session. The ID is allocated by the MAG-c.
Create PDR See Create PDR IE	M	This IE includes a PDR to be associated with the PFCP session. Several IEs with this IE type may be present to represent a list of PDRs to create.
Create FAR See Create FAR IE	M	This IE includes one or more FARs to be associated with the PFCP session.
Create URR See Create URR IE	C	This IE is present if a measurement action is applied to packets matching one or more PDRs of this PFCP session. Only one Create URR IE may be present on the SCi interface.
Create QER See Create QER IE	C	This IE is present if a QoS enforcement action is applied to packets matching one or more PDRs of this PFCP session. Only one Create QER IE may be present on the SCi interface.
Create Traffic Endpoint See Create Traffic Endpoint IE	C	When present, this IE contains the information associated with the traffic endpoint to be created.
PDN Type	C	This IE is present if the PFCP session is set up for an individual PDN connection or a PDU session. For SCi sessions, this must be Ethernet. For default IBCP sessions, this IE must not be present.
(BBF) PPP LCP connectivity	C	This IE is present if periodic LCP echo hello is required.
Nokia UP Aggregate Route See Nokia UP Aggregate Route IE	C	This IE is present if any aggregate routes need to be installed on the BNG-UP.
Nokia SAP Template See Nokia SAP Template IE	C	This IE is present if a specific SAP template needs to be used to construct SAP structures on the BNG-UP.
Nokia Group Interface Template See Nokia Group Interface Template IE	C	This IE is present if a specific group interface template needs to be used to construct group interface structures on an SR OS BNG-UP.
Nokia Create Filter Override See Nokia Create Filter Override IE	C	This IE is present if a Nokia-specific filter needs to be installed. This is signaled as out of scope of any PDR or FAR because Nokia filters are installed per session.
Nokia Intermediate Destination See Nokia Intermediate Destination IE	C	This IE is present if an intermediate destination identifier (for example, access line ID) needs to be signaled to the BNG-UP. This is signaled as out of scope of any PDR or FAR because this can apply to both QoS (for example, vport) and access identification (for example, mc-ring).
Nokia State ID See Nokia State ID IE	C	This IE is present if the BNG-UP indicated support for the bulk audit feature. It must be stored unmodified by the BNG-UP.

Create PDR IE

Table 2. Create PDR IE
Octet 1 and 2	Create PDR IE Type = 1 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
PDR ID	M	This IE uniquely identifies the PDR among all the PDRs configured for the PFCP session.
Precedence	M	This IE indicates the precedence of the PDR among all PDRs of the PFCP session. The BNG-UP applies the precedence when looking for a PDR matching an incoming packet.
PDI See PDI IE	M	This IE specifies the match criteria for incoming packets. It also contains a reference to a traffic endpoint.
Outer Header Removal	C	This IE is present if the BNG-UP is required to remove one or more outer headers from the packets matching this PDR.
FAR ID	C	This IE is 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. When present, this IE contains the FAR ID to be associated with the PDR.
QER ID	C	This IE is present if a QoS enforcement action is applied to packets matching the PDR. When present, this IE contains the QER ID to be associated with the PDR.
URR ID	C	This IE is present if a measurement action is applied to packets matching this PDR. When present, this IE contains the URR ID to be associated with the PDR.
Activate Predefined Rules See Nokia format for QoS policy in the Activate Predefined Rules IE	C	This IE is present if predefined rules are activated for the PDR. When present, this IE contains one predefined rules name. Several IEs with the same IE type may be present to represent multiple predefined rules names.
(BBF) BBF Outer Header Removal	C	This IE is present if the BNG-UP must remove one or more headers from the packets matching the PDR.

Table 3. PDI IE
Octet 1 and 2	PDI IE Type = 2 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Source Interface	M	This IE identifies the source interface of the incoming packet.
Traffic Endpoint ID	C	This IE is present if the BNG-UP indicated the support of PDI optimization. If present, this IE uniquely identifies the traffic endpoint for the PFCP session.
Ethernet Packet Filter See Ethernet Packet Filter IE	O	If present, this IE identifies the Ethernet PDU to match for the incoming packet. Several IEs with the same IE type may be present to provision a list of Ethernet packet filters. When present, the full set of applicable Ethernet packet filters is provided during the creation or modification of the PDI.
SDF Filter	O	If present, this IE identifies the SDF filter to match for the incoming packet. Several IEs with the same IE type may be present to represent a list of SDF filters.

Table 4. Ethernet Packet Filter IE
Octet 1 and 2	Ethernet Packet Filter IE Type = 132 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Ethernet Filter ID	C	This IE identifies the source interface of the incoming packet.
MAC address	O	If present, this IE identifies the MAC address. The IE may be present up to 16 times.
Ethertype	O	If present, this IE identifies the Ethertype.
C-TAG	O	If present, this IE identifies the Customer-VLAN tag.
S-TAG	O	If present, this IE identifies the Service-VLAN tag.
SDF Filter	O	If packet filtering is required, this IE describes the IP packet filter set for Ethernet frames with Ethertype indicating IPv4 or IPv6 payload. Several IEs with the same IE type may be present to represent a list of SDF filters.
(BBF) PPP Protocol	O	If present, this IE identifies the PPP protocol to match for the incoming packet.

Create FAR IE

Table 5. Create FAR IE
Octet 1 and 2	Create FAR IE Type = 3 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
FAR ID	M	This IE uniquely identifies the FAR among all the FARs configured for the PFCP session.
Apply Action	M	This IE indicates the action to apply to the packets.
Forwarding Parameters See Forwarding Parameters IE	C	This IE is present if the Apply Action IE requests the packets to be forwarded. For other values of the Apply Action IE, it may be present. When present, this IE contains the forwarding instructions to be applied by the BNG-UP when the Apply Action IE requests the packets to be forwarded.

Table 6. Forwarding Parameters IE
Octet 1 and 2	Forwarding Parameters IE Type = 4 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Destination Interface	M	This IE identifies the destination interface of the outgoing packet.
Network Instance	O	When present, this IE identifies the network instance where the outgoing packet is sent to.¹
Outer Header Creation	C	This IE is present if the BNG-UP is required to add one or more outer headers to the outgoing packet. If present, it contains the F-TEID of the remote GTP-U peer when adding a GTP-U/UDP/IP header, or the destination IP address and port number when adding a UDP/IP header.
Linked Traffic Endpoint ID	C	This IE is present if the BNG-UP indicated support of the PDI optimization feature. When present, it identifies the traffic endpoint ID allocated for the PFCP session to receive the traffic in the reverse direction. A BBF Outer Header Creation IE indicating Traffic-Endpoint indicates which fields must be added. In this case, any SRC/DST fields must be reversed before creating the header.
(BBF) BBF Outer Header Creation	C	This IE is present if the BNG-UP is required to add one or more outer headers to the outgoing packet.
(BBF) MTU	O	When present, this IE enforces an MTU on outgoing packets. In the case of PPPoE, this may be based on the negotiated MRU value.

¹ The following are examples of the need for a Network Instance IE.

The PGW/TDF UP function supports multiple PDNs with overlapping IP addresses.
The SGW UP function is connected to PGWs in different IP domains (S5/S8).
The SGW UP function is connected to eNodeBs in different IP domains.

Create URR IE

Table 7. Create URR IE
Octet 1 and 2	Create URR IE Type = 6 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
URR ID	M	This IE uniquely identifies the URR among all the URRs configured for this PFCP session.
Measurement Method	M	This IE indicates the method for measuring the network resources usage; that is, whether the data volume, duration (time), or combined volume and duration are measured.
Reporting Triggers	M	This IE indicates the triggers for reporting network resources usage to the MAG-c; for example, periodic reporting.
Measurement Period	C	This IE is present if periodic reporting is required. When present, it indicates the period for generating and reporting usage reports.
Measurement Information	C	This IE contains the Measurement of Number of Packets flag. This IE is only included if that flag is set to 1. The Measurement of Number of Packets flag is set to 1 when packet-based measurement applies. For packet-based measurement, the BNG-UP reports the number of packets in the uplink direction, the number of packets in the downlink direction, and the total number of packets. The BNG-UP sends the packet-based measurements as well as the measurements in bytes, which apply by default.
Nokia Measurement Information See Nokia Measurement Information IE	C	This IE is present if any of the flags in this IE are set to 1.

Create QER IE

Table 8. Create QER IE
Octet 1 and 2	Create QER IE Type = 7 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
QER ID	M	This IE uniquely identifies the QER among all the QERs configured for the PFCP session.
QER Correlation ID	C	This IE is present if the BNG-UP is required to correlate the QERs of several PFCP sessions. For the SCi interface, this IE is used to encode a subscriber ID.
Gate Status	M	This IE indicates whether the packets are allowed to be forwarded (the gate is open) or discarded (the gate is closed) in the uplink and, or downlink directions.
Nokia QoS Override See Nokia QoS Override IE	C	This IE is present if a Nokia-specific QoS override is required. Multiple IEs may be present in case multiple overrides are required.

Create Traffic Endpoint IE

Table 9. Create Traffic Endpoint IE
Octet 1 and 2	Create Traffic Endpoint IE Type = 127 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Traffic Endpoint ID	M	This IE uniquely identifies the traffic endpoint for the PFCP session.
Local F-TEID	O	If present, this IE identifies the local F-TEID to match for an incoming packet. The MAG-c sets the CHOOSE (CH) bit to 1 if the BNG-UP supports the allocation of F-TEID and if the MAG-c requests the BNG-UP to assign a local F-TEID to the traffic endpoint. For the SCi interface, this IE is only valid for IBCP sessions.
Network Instance	O	This IE is present if the MAG-c requests the BNG-UP to allocate a UE IP address/prefix. If present, this IE identifies the network instance to match for the incoming packet.
UE IP address	O	If present, this IE identifies the source or destination IP address to match for the incoming packet.
Framed-Route	O	This IE may be present for a DL PDR if the BNG-UP indicated support of framed routing (see clause 8.2.5 of 3GPP TS 29.244). When present, this IE describes a framed route. Several IEs with the same IE type may be present to provision a list of framed routes.
Framed-IPv6-Route	O	This IE may be present for a DL PDR if the BNG-UP indicated support of framed routing (see clause 8.2.25 of 3GPP TS 29.244). When present, this IE describes a framed IPv6 route. Several IEs with the same IE type may be present to provision a list of framed IPv6 routes.
MAC address	O	If present, this IE identifies the MAC address.
C-TAG	O	If present, this IE identifies the Customer-VLAN tag. The PCP and DEI values are not specified.
S-TAG	O	If present, this IE identifies the Service-VLAN tag. The PCP and DEI values are not specified.
(BBF) Logical Port	O	If present, this IE provides an opaque value obtained from the NSH header to indicate the logical port for the subscriber.
(BBF) PPPoE Session ID	O	If present, this IE identifies the PPPoE session ID of the subscriber.
Nokia L2TP Tunnel Group Assignment ID See Nokia L2TP Assignment ID IE	C	A name for the group of L2TP tunnels this session belongs to. It is used to correlate sessions connecting to the same set of LNS servers and to apply server selection and load-balancing. It is also used to assist in operational commands such as state retrieval and debugging.
Nokia L2TP Client Endpoint See Nokia L2TP Client Endpoint IE	C	The endpoint IP address to be used by the BNG-UP to set up a tunnel. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Client Auth ID See Nokia L2TP Client Auth ID IE	C	An identifier for the L2TP LAC, sent to the LNS using the L2TP Host Name AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Server Auth ID See Nokia L2TP Server Auth ID IE	C	An identifier for the L2TP LNS. It is compared to the Host Name AVP as received from the LNS in L2TP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Init Rx LCP Conf Request See Nokia L2TP Init Rx LCP Conf Request IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the initial PPP LCP configure request as received by the MAG-c from the PPPoE client. It is sent to the LNS using the L2TP Initial Received LCP CONFREQ AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Last Rx LCP Conf Request See Nokia L2TP Last Rx LCP Conf Request IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the last PPP LCP configure request as received by the MAG-c from the PPPoE client. It is sent to the LNS using the L2TP Last Received LCP CONFREQ AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Last Tx LCP Conf Request See Nokia L2TP Last Tx LCP Conf Request IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the last PPP LCP configure request as sent by the MAG-c to the PPPoE client. It is sent to the LNS using the L2TP Last Sent LCP CONFREQ AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Authentication Type See Nokia L2TP Authentication Type IE	C	Used to proxy PPP negotiated information to the LNS. This IE indicates which authentication type (for example, PAP or CHAP) was performed toward the MAG-c. It is sent to the LNS using the Proxy Authen Type AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Authentication Name See Nokia L2TP Authentication Name IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the username that was used during authentication toward the MAG-c. It is sent to the LNS using the Proxy Authen Name AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Authentication ID See Nokia L2TP Authentication ID IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the authenticator ID used during authentication. It is sent to the LNS using the Proxy Authen ID AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Authentication Challenge See Nokia L2TP Authentication Challenge IE	C	Used to proxy PPP negotiated information to the LNS. This IE is included if the client performed CHAP authentication and contains the challenge used toward the MAG-c. It is sent to the LNS using the Proxy Authen Challenge AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Authentication Response See Nokia L2TP Authentication Response IE	C	Used to proxy PPP negotiated information to the LNS. This IE contains the password or challenge response that was used during authentication toward the MAG-c. It is sent to the LNS using the Proxy Authen Response AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Password See Nokia L2TP Password IE	C	Indicates that the BNG-UP needs to do CHAP based tunnel authentication, using the shared secret in this IE. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Private Group ID See Nokia L2TP Private Group ID IE	C	An identifier that the LNS can use to correlate sessions of a particular customer group. It is sent to the LNS in the L2TP Private Group ID AVP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Parameters See Nokia L2TP Parameters IE	C	L2TP Parameters that are common for all L2TP tunnels. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia Access Line Circuit ID See Nokia Access Line Circuit ID IE	C	Circuit ID as learned by the MAG-c, to be reflected in L2TP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia Access Line Remote ID See Nokia Access Line Remote ID IE	C	Remote ID as learned by the MAG-c, to be reflected in L2TP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia Access Line Parameters See Nokia Access Line Parameters IE	C	TR 101 Access Line Characteristics as learned by the MAG-c, to be reflected in L2TP. This IE requires at least one Nokia L2TP Tunnel IE to be present.
Nokia L2TP Tunnel See Nokia L2TP Tunnel IE	C	When present, indicates that the BNG-UP must initiate an L2TP tunnel to an L2TP LNS and forward the PPP traffic to the LNS. Multiple IEs of this type can be present to indicate a set of tunnels from which the BNG-UP can choose. Tunnel selection is subject to BNG-UP configuration and a preference as indicated in the L2TP Params IE.

Table 10. Nokia L2TP Tunnel IE
Octet 1 and 2	Nokia L2TP Tunnel IE Type = 32808 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Nokia L2TP Server Endpoint See Nokia L2TP Server Endpoint IE	M	The endpoint IP address toward which the L2TP tunnel is set up.
Nokia L2TP Tunnel Assignment ID See Nokia L2TP Assignment ID IE	C	A name for the L2TP tunnel, for operational commands on the BNG-UP.
Nokia L2TP Client Endpoint See Nokia L2TP Client Endpoint IE	C	In a Create Traffic Endpoint context, indicates the IP address that the BNG-UP must use to set up a tunnel. This value has precedence over the same IE on Traffic Endpoint level, if both are present. In a Created Traffic Endpoint context, indicates the IP address that the BNG-UP used to set up the tunnel.
Nokia L2TP Client Auth ID See Nokia L2TP Client Auth ID IE	C	In a Create Traffic Endpoint context, sent to the LNS using the L2TP Host Name AVP. This value has precedence over the same IE on Traffic Endpoint level, if both are present. In a Created Traffic Endpoint context, indicates the Host Name that the BNG-UP used to set up the tunnel.
Nokia L2TP Server Auth ID See Nokia L2TP Server Auth ID IE	C	In a Create Traffic Endpoint context, this value is compared to the Host Name AVP as received from the LNS in L2TP. This value has precedence over the same IE on Traffic Endpoint level, if both are present. In a Created Traffic Endpoint context, indicates the Host Name that the LNS sent.
Nokia L2TP Private Group ID See Nokia L2TP Private Group ID IE	C	An identifier that the LNS can use to correlate sessions of a customer group. It is sent to the LNS in the L2TP Private Group ID AVP. This value has precedence over the same IE on Traffic Endpoint level, if both are present. This IE may only be present in a Create Traffic Endpoint IE context.
Nokia L2TP Parameters See Nokia L2TP Parameters IE	C	L2TP parameters for tunnel setup. Any parameter specified in this IE overrides that parameter’s value in the Traffic Endpoint IE, if present. This IE may only be present in a Create Traffic Endpoint IE context.
Nokia L2TP IDs See Nokia L2TP IDs IE	C	Identifiers of the created tunnel. This IE contains the remote (LNS) tunnel and session IDs, the local (LAC) tunnel and session IDs, and the CSN. This IE may only be present in a Created Traffic Endpoint IE context.

Nokia UP Aggregate Route IE

Table 11. Nokia UP Aggregate Route IE
Octet 1 and 2	Nokia UP Aggregate Route IE Type = 32774 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Network Instance	O	If present, this IE identifies the network instance for the IP prefix.
Framed-Route	O	If present, this IE describes an IP prefix assigned to the BNG-UP. Optionally, the prefix may contain a /32 address that may be used as a local address on the BNG-UP and that must be used to answer ARPs for this session. Several IEs with the same IE type may be present to provision a list of framed routes.
Framed IPv6-Route	O	If present, this IE describes an IPv6 prefix assigned to the BNG-UP. Several IEs with the same IE type may be present to provision a list of framed IPv6 routes.

PFCP Session Establishment Response

The PFCP Session Establishment Response message is sent from the BNG-UP to the MAG-c as a reply to the PFCP Session Establishment Request.

Table 12. IEs in PFCP Session Establishment Response
Information elements	P	Condition/Comment
Node ID	M	This IE contains the unique identifier of the sending node.
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
Offending IE	C	This IE is included if the rejection is caused by a conditional or a mandatory missing or faulty IE.
UP F-SEID	M	This IE contains the unique identifier allocated by the BNG-UP identifying the session.
Failed Rule ID	C	This IE is included if the Cause IE indicates a rejection because of a rule creation failure or a rule modification failure.
Created Traffic Endpoint See Create Traffic Endpoint IE	C	This IE is present if the Cause IE is set to success and the BNG-UP was requested to allocate a local F-TEID or a UE IP address/prefix in a Create Traffic Endpoint IE. When present, this IE contains the local F-TEID or UE IP address/prefix to be used for this traffic endpoint. Several instances of this IE may be present.
Nokia Detailed Error See Nokia Detailed Error IE	C	This IE is present if the Cause IE indicates an error.

Created Traffic Endpoint IE

Table 13. Created Traffic Endpoint IE
Octet 1 and 2	Created Traffic Endpoint IE Type = 128 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Traffic Endpoint ID	M	This IE uniquely identifies the traffic endpoint for the PFCP session.
Local F-TEID	C	This IE is present if the BNG-UP allocates the F-TEID. When present, this IE contains the local F-TEID to be used for the traffic endpoint.
Nokia L2TP Tunnel See Nokia L2TP Tunnel IE	C	When present, indicates that the BNG-UP successfully initiated an L2TP connection to this tunnel. Only one IE of this type can be present.

PFCP Session Modification Request

The PFCP Session Modification Request message is initiated from the MAG-c to request the BNG-UP to modify the PFCP session.

Table 14. IEs in a PFCP Session Modification Request
Information elements	P	Condition/Comment
CP F-SEID	C	This IE is present if the MAG-c decides to change its F-SEID for the PFCP session. The BNG-UP uses the new CP F-SEID for subsequent PFCP session messages related to this PFCP session.
Remove PDR See Remove PDR IE (PFCP Session Modification Request)	C	When present, this IE contains the PDR rule that is requested to be removed. Several IEs with this IE type may be present to represent a list of PDRs to remove.
Remove FAR See Remove FAR IE (PFCP Session Modification Request)	C	When present, this IE contains the FAR rule that is requested to be removed. Several IEs with this IE type may be present to represent a list of FARs to remove.
Remove URR See Remove URR IE (PFCP Session Modification Request)	C	When present, this IE contains the URR rule that is requested to be removed.
Remove QER See Remove QER IE (PFCP Session Modification Request)	C	When present, this IE contains the QER rule that is requested to be removed. Several IEs with this IE type may be present to represent a list of QERs to remove.
Remove Traffic Endpoint See Remove Traffic Endpoint IE (PFCP Session Modification Request)	C	This IE is present if the BNG-UP indicated support for PDI optimization and the MAG-c requests to remove a traffic endpoint. When present, this IE contains the traffic endpoint ID of the traffic endpoint to be removed. All PDRs referring to the removed traffic endpoint are deleted as well.
Create PDR	C	This IE is present if the MAG-c requests the BNG-UP to create a new PDR. Several IEs with this IE type may be present to represent a list of PDRs to create.
Create FAR	C	This IE is present if the MAG-c requests the BNG-UP function to create a new FAR. Several IEs with this IE type may be present to represent a list of FARs to create.
Create URR	C	This IE is present if the MAG-c requests the BNG-UP to create a new URR.^²
Create QER	C	This IE is present if the MAG-c requests the BNG-UP to create a new QER.
Create Traffic Endpoint	C	This IE is present if the BNG-UP indicated support for PDI optimization and the MAG-c requests the BNG-UP to create a new traffic endpoint. When present, this IE contains the information associated with the traffic endpoint to be created.
(BBF) PPP LCP Connectivity	C	This IE is present if periodic LCP echo hello is required.
Update PDR See Update PDR IE (PFCP Session Modification Request)	C	This IE is present if a PDR previously created for the PFCP session needs to be modified. Several IEs with this IE type may be present to represent a list of PDRs to update.
Update FAR See Update FAR IE (PFCP Session Modification Request)	C	This IE is present if a FAR previously created for the PFCP session needs to be modified. Several IEs with this IE type may be present to represent a list of FARs to update.
Update URR See Update URR IE (PFCP Session Modification Request)	C	This IE is present if the URR previously created for the PFCP session needs to be modified.^²
Update QER See Update QER IE (PFCP Session Modification Request)	C	This IE is present if QERs previously created for the PFCP session need to be modified. Several IEs with this IE type may be present to represent a list of modified QERs. Previously created QERs that are not modified are not included.
Update Traffic Endpoint See Update Traffic Endpoint IE (PFCP Session Modification Request)	C	This IE is present if the MAG-c requests the BNG-UP to update a traffic endpoint. When present, this IE contains the information associated with the traffic endpoint to be updated. All the PDRs that point to the traffic endpoint use updated traffic endpoint information.
PFCPSMReq-Flags	C	This IE is included if the QAURR (Query All URRs) flag in this IE is set to 1. The QAURR flag indicates that the MAG-c requests immediate usage reports for the URRs provisioned for this PFCP session.^²^,
Query URR See Query URR IE (PFCP Session Modification Request)	C	This IE is present if the MAG-c requests immediate usage reports from the BNG-UP for the specified URR.^²^,^³
Nokia UP Aggregate Route See Nokia UP Aggregate Route IE	C	This IE is present if any aggregate routes need to change. When present, all routes must be included. When absent, no changes to aggregate routes are done.
Nokia SAP Template See Nokia SAP Template IE	C	This IE is present if a specific SAP template needs to be used to construct SAP structures on a BNG-UP.
Nokia Group Interface Template See Nokia Group Interface Template IE	C	This IE is present if a specific group interface template needs to be used to construct group interface structures on a BNG-UP.
Nokia Create Filter Override See Nokia Create Filter Override IE	C	This IE is present if a new override has to be created or an existing override needs to be changed. Multiple IEs may be present, as long as they indicate distinct filter types and the filter types are not present in the Nokia Delete Filter Override IE.
Nokia Delete Filter Override See Nokia Delete Filter Override IE	C	This IE is present if an override has to be removed. Multiple IEs may be present, as long as they indicate distinct filter types and the filter types are not present in the Nokia Create Filter Override IE.
Nokia Intermediate Destination See Nokia Intermediate Destination IE	C	This IE is present if the intermediate destination changed.
Nokia State ID See Nokia State ID IE	C	This IE is included if the BNG-UP indicated support for the bulk audit feature. When present, the BNG-UP stores the state unmodified. The state overrides the last signaled value for this session. When not present, the last value is kept.
Nokia PFCPSMReq-Flags See Nokia PFCPSMReq-Flags IE	C	This IE is present if any of the flags in the IE is set to 1.

¹ Only one URR may be active for a PFCP session.

² The QAURR (Query All URRs) flag in the PFCPSMReq-Flags IE and the Query URR IE are mutually exclusive in a PFCP Session Modification Request.

Update PDR IE

Table 15. Update PDR IE (PFCP Session Modification Request)
Octet 1 and 2	Update PDR IE Type = 9 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
PDR ID	M	This IE uniquely identifies the PDR among all the PDRs configured for that PFCP session.
Outer Header Removal	C	This IE is present if it needs to be changed.
Precedence	C	This IE is present if there is a change in the precedence of the PDR among all PDRs of the PFCP session. The BNG-UP applies the precedence when matching an incoming packet.
PDI	C	This IE is present if there is a change within the PDI against which incoming packets are matched. When present, this IE replaces the PDI previously stored in the BNG-UP for this PDR.
FAR ID	C	This IE is present if it needs to be changed.
QER ID	C	This IE is present if a QoS enforcement action is applied or no longer applied to packets matching this PDR. When present, this IE contains the QER ID to be associated with the PDR.
URR ID	C	This IE is present if a measurement action is applied or no longer applied to packets matching this PDR. When present, this IE contains the URR ID to be associated with the PDR.
Activate Predefined Rules	C	This IE is present if a new predefined rule needs to be activated for the PDR. When present, this IE contains one predefined rule name. Several IEs with the same IE type may be present to represent multiple predefined rule names.
Deactivate Predefined Rules	C	This IE is present if a predefined rule needs to be deactivated for the PDR. When present, this IE contains one predefined rule name. Several IEs with the same IE type may be present to represent multiple predefined rule names.
(BBF) BBF Outer Header Removal	C	This IE is present if it needs to be changed. When present, this IE requests the BNG-UP to remove one or more headers from the packets matching this PDR.

Note: The IEs that do not need to be modified are not included in the Update PDR IE. The BNG-UP continues to behave according to the values previously received for IEs not present in the Update PDR IE.

Update FAR IE

Table 16. Update FAR IE (PFCP Session Modification Request)
Octet 1 and 2	Update FAR IE Type = 10 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
FAR ID	M	This IE identifies the FAR to be updated.
Apply Action	C	This IE is present if it is changed.
Update Forwarding Parameters See Update Forwarding Parameters IE	C	This IE is present if it is changed.

Table 17. Update Forwarding Parameters IE
Octet 1 and 2	Update Forwarding Parameters IE Type = 11 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Destination Interface	C	This IE is present if it is changed. When present, it indicates the destination interface of the outgoing packet.
Network Instance	C	This IE is present if it is changed.
Outer Header Creation	C	This IE is present if it is changed.
Linked Traffic Endpoint ID	C	This IE is present if it is changed.
(BBF) BBF Outer Header Creation	C	This IE is present if it is changed. When present, the BNG-UP is required to add one or more outer headers to the outgoing packet.
(BBF) MTU	O	This IE is present to enforce an MTU on outgoing packets. In the case of PPPoE, the MTU may be based on the negotiated MRU value.

Update URR IE

Table 18. Update URR IE (PFCP Session Modification Request)
Octet 1 and 2	Update URR IE Type = 13 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
URR ID	M	This IE uniquely identifies the URR among all the URRs configured for the PFCP session.
Measurement Method	C	This IE is present if the measurement method is modified. When present, this IE indicates the method for measuring the network resources usage; that is, whether the data volume, the duration (time), or the combined volume and duration are measured.
Reporting Triggers	C	This IE is present if the reporting triggers are modified. When present, this IE indicates the triggers for reporting network resources usage to the MAG-c; for example, periodic reporting.
Measurement Period	C	This IE is present if the measurement period is modified. When present, it indicates the period for generating and reporting usage reports.

Update QER IE

Table 19. Update QER IE (PFCP Session Modification Request)
Octet 1 and 2	Update QER IE Type = 14 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
QER ID	M	This IE uniquely identifies the QER among all the QERs configured for the PFCP session.
QER Correlation ID	C	This IE is present if the QER correlation ID in this QER needs to be modified.
Gate Status	C	This IE is present if the gate status needs to be modified. When present, it indicates whether the packets are allowed to be forwarded (the gate is open) or discarded (the gate is closed) in the uplink, the downlink, or both directions.
Nokia QoS Override See Nokia QoS Override IE	C	This IE is present if changed. When not present, no change is done to previous QoS overrides. When present, any previous QoS overrides are removed and only the new overrides are retained. When an empty IE is present (n = 2), any previous QoS overrides are removed. Only one empty IE of this IE type may be present. Multiple non-empty IEs of this IE type may be present.

Update Traffic Endpoint IE

Table 20. Update Traffic Endpoint IE (PFCP Session Modification Request)
Octet 1 and 2	Update Traffic Endpoint IE Type = 129 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Traffic Endpoint ID	M	This IE uniquely identifies the traffic endpoint for the PFCP session.
Local F-TEID	C	This IE is present if it needs to be changed. When present, this IE identifies the local F-TEID to match for an incoming packet. The MAG-c sets the CHOOSE (CH) bit to 1 if the BNG-UP supports the allocation of F-TEID and if the MAG-c requests the BNG-UP to assign a local F-TEID to the traffic endpoint. For the SCi interface, this IE is only valid for IBCP sessions.
Network Instance	O	When present, this IE identifies the network instance to match for the incoming packet.
UE IP address	C	This IE is present if it needs to be changed.
Framed-Route	C	This IE is present for a DL PDR if it needs to be changed. When present, this IE describes a framed route. Several IEs with the same IE type may be present to provision a list of framed routes.
Framed-IPv6-Route	C	This IE is present for a DL PDR if it needs to be changed. When present, this IE describes a framed IPv6 route. Several IEs with the same IE type may be present to provision a list of framed IPv6 routes.
MAC address	O	This IE is present if it needs to be changed.
C-TAG	O	This IE is present if it needs to be changed.
S-TAG	O	This IE is present if it needs to be changed.
(BBF) Logical Port	O	This IE is present if it needs to be changed. When present, this IE provides an opaque value obtained from the NSH header to indicate the logical port for the subscriber.
(BBF) PPPoE Session ID	O	This IE is present if it needs to be changed. When present, this IE identifies the PPPoE session ID of the subscriber.

Remove PDR IE

Table 21. Remove PDR IE (PFCP Session Modification Request)
Octet 1 and 2	Remove PDR IE Type = 15 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
PDR ID	M	This IE identifies the PDR to be deleted.

Remove FAR IE

Table 22. Remove FAR IE (PFCP Session Modification Request)
Octet 1 and 2	Remove FAR IE Type = 16 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
FAR ID	M	This IE identifies the FAR to be deleted.

Remove URR IE

Table 23. Remove URR IE (PFCP Session Modification Request)
Octet 1 and 2	Remove URR IE Type = 17 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
URR ID	M	This IE identifies the URR to be deleted.

Remove QER IE

Table 24. Remove QER IE (PFCP Session Modification Request)
Octet 1 and 2	Remove QER IE Type = 18 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
QER ID	M	This IE identifies the QER to be deleted.

Remove Traffic Endpoint IE

Table 25. Remove Traffic Endpoint IE (PFCP Session Modification Request)
Octet 1 and 2	Remove Traffic Endpoint IE Type = 130 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
Traffic Endpoint ID	M	This IE identifies the traffic endpoint to be deleted.

Query URR IE

Table 26. Query URR IE (PFCP Session Modification Request)
Octet 1 and 2	Query URR IE Type = 77 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
URR ID	M	This IE identifies the URR to be queried.

PFCP Session Modification Response

The PFCP Session Modification Response message is sent from the BNG-UP to the MAG-c as a reply to the PFCP Session Modification Request message.

Table 27. IEs in a PFCP Session Modification Response
Information elements	P	Condition/Comment
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
Offending IE	C	This IE is included if the rejection is caused by a conditional or mandatory IE that is missing or faulty.
Usage Report See Usage Report IE (PFCP Session Modification Response)	C	This IE is present if the Query URR IE was present in the PFCP Session Modification Request and traffic usage measurements for that URR are available at the BNG-UP. Several IEs with the same IE type may be present to represent a list of usage reports.
Failed Rule ID	C	This IE is present if the Cause IE indicates a rejection because of a rule creation failure or a rule modification failure.
Created Traffic Endpoint	C	This IE is present if the cause is set to success, traffic endpoints were created, and the BNG-UP allocated a local F-TEID for the traffic endpoints. When present, this IE contains the traffic endpoint information associated with the PFCP session.
Updated Traffic Endpoint	C	This IE is present if the cause is set to success, traffic endpoints were updated, and the BNG-UP allocated a local F-TEID for the traffic endpoints. When present, this IE contains the traffic endpoint information associated with the PFCP session.
Nokia Detailed Error See Nokia Detailed Error IE	C	This IE is present if the Cause IE indicates a failure.
Nokia State ID See Nokia State ID IE	C	This IE is present if the BNG-UP knows its value.

Usage Report IE

Table 28. Usage Report IE (PFCP Session Modification Response)
Octet 1 and 2	Usage Report IE Type = 78 (decimal)
Octet 3 and 4	Length = n
Information elements	P	Condition/Comment
URR ID	M	This IE identifies the URR for which usage is reported.
UR-SEQN	M	This IE uniquely identifies the usage report for the URR.
Usage Report Trigger	M	This IE identifies the trigger for this report.
Start Time	C	This IE is always present, except if the Usage Report Trigger IE indicates START (Start of Traffic) or STOPT (Stop of Traffic). When present, this IE provides the timestamp when the collection of the information in this report was started.
End Time	C	This IE is always present, except if the Usage Report Trigger indicates START (Start of Traffic) or STOPT (Stop of Traffic). When present, this IE provides the timestamp when the collection of the information in this report was generated.
Volume Measurement	C	This IE is present if a volume measurement needs to be reported.
UE IP address	O	This IE is present if the start or stop of an application was detected and no UE IP address was provisioned in the PDI. On the SCi interface, this IE is included to indicate any learned addresses for shared prefixes. This IE may only contain IPv6 addresses with IP6PL bit set and prefix-length equal to 128.
Vendor Specific	C	This IE can be any vendor-specific IE related to usage reports.

PFCP Session Deletion Request

The PFCP Session Deletion Request message is initiated from the MAG-c to request the BNG-UP to delete the PFCP session. It uses the F-SEID in the PFCP header and does not include any IEs.

PFCP Session Deletion Response

The PFCP Session Deletion Response message is sent from the BNG-UP to the MAG-c as a reply to the PFCP Session Deletion Request message.

Table 29. IEs in a PFCP Session Deletion Response
Information elements	P	Condition/Comment
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
Offending IE	C	This IE is included if the rejection is caused by a conditional or mandatory IE that is missing or faulty.
Nokia Detailed Error See Nokia Detailed Error IE	C	This IE is included if the Cause IE indicates a failure.

PFCP Session Report Request

The PFCP Session Report Request message is initiated from the BNG-UP to the MAG-c to report information related to a PFCP session.

Table 30. IEs in a PFCP Session Report Request
Information elements	P	Condition/Comment
Report Type	M	This IE indicates the type of the report.
Usage Report	C	This IE is present if the Report Type IE indicates a usage report. Several IEs with the same IE type may be present to represent a list of usage reports.
Nokia State ID See Nokia State ID IE	C	This IE is present if the BNG-UP knows its value.

PFCP Session Report Response

The PFCP Session Report Response message is sent from the MAG-c to the BNG-UP as a reply to the PFCP Session Report Request.

Table 31. IEs in a PFCP Session Report Response
Information elements	P	Condition/Comment
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
Offending IE	C	This IE is included if the rejection is caused by a conditional or mandatory IE that is missing or faulty.