7.5.4 PFCP Session Modification Request
29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS
7.5.4.1 General
The PFCP Session Modification Request is used over the Sxa, Sxb, Sxc, N4 and N4mb interface by the CP function to request the UP function to modify the PFCP session.
Table 7.5.4.1-1: Information Elements in a PFCP Session Modification Request
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
||||
CP F-SEID |
C |
This IE shall be present if the CP function decides to change its F-SEID for the PFCP session. The UP function shall use the new CP F-SEID for subsequent PFCP Session related messages for this PFCP Session. See Note 2. |
X |
X |
X |
X |
X |
F-SEID |
Remove PDR |
C |
When present, this IE shall contain the PDR Rule which is requested to be removed. See Table 7.5.4-6-1. Several IEs within the same IE type may be present to represent a list of PDRs to remove. |
X |
X |
X |
X |
X |
Remove PDR |
Remove FAR |
C |
When present, this IE shall contain the FAR Rule which is requested to be removed. See Table 7.5.4-7-1. Several IEs within the same IE type may be present to represent a list of FARs to remove. |
X |
X |
X |
X |
X |
Remove FAR |
Remove URR |
C |
When present, this shall contain the URR Rule which is requested to be removed. See Table 7.5.4-8-1. Several IEs within the same IE type may be present to represent a list of URRs to remove. |
X |
X |
X |
X |
– |
Remove URR |
Remove QER |
C |
When present, this IE shall contain the QER Rule which is requested to be removed. See Table 7.5.4-9-1. Several IEs within the same IE type may be present to represent a list of QERs to remove. |
– |
X |
X |
X |
X |
Remove QER |
Remove BAR |
C |
When present, this IE shall contain the BAR Rule which is requested to be removed. See Table 7.5.4.12-1. |
X |
– |
– |
X |
– |
Remove BAR |
Remove Traffic Endpoint |
C |
When present, this IE shall contain the Traffic Endpoint ID identifying the traffic endpoint to be removed, if the UP function has indicated support of PDI optimization. All the PDRs that refer to the removed Traffic Endpoint shall be deleted. See Table 7.5.4.14-1. Several IEs within the same IE type may be present to represent a list of Traffic Endpoints to remove. |
X |
X |
X |
X |
X |
Remove Traffic Endpoint |
Create PDR |
C |
This IE shall be present if the CP function requests the UP function to create a new PDR. See Table 7.5.2.2-1. Several IEs within the same IE type may be present to represent a list of PDRs to create. |
X |
X |
X |
X |
X |
Create PDR |
Create FAR |
C |
This IE shall be present if the CP function requests the UP function to create a new FAR. See Table 7.5.2.3-1. Several IEs within the same IE type may be present to represent a list of FARs to create. |
X |
X |
X |
X |
X |
Create FAR |
Create URR |
C |
This IE shall be present if the CP function requests the UP function to create a new URR. See Table 7.5.2.4-1. Several IEs within the same IE type may be present to represent a list of URRs to create. |
X |
X |
X |
X |
– |
Create URR |
Create QER |
C |
This IE shall be present if the CP function requests the UP function to create a new QER. See Table 7.5.2.5-1. Several IEs within the same IE type may be present to represent a list of QERs to create. |
– |
X |
X |
X |
X |
Create QER |
Create BAR |
C |
This IE shall be present if the CP function requests the UP function to create a new BAR. See Table 7.5.2.6-1. |
X |
– |
– |
X |
– |
Create BAR |
Create Traffic Endpoint |
C |
When present this IE shall contain the information associated with the Traffic Endpoint to be created, if the UP function has indicated support of PDI optimization. See Table 7.5.2.7-1. Several IEs within the same IE type may be present to represent a list of Traffic Endpoints to create. |
X |
X |
X |
X |
X |
Create Traffic Endpoint |
Update PDR |
C |
This IE shall be present if a PDR previously created for the PFCP session need to be modified. See Table 7.5.4.2-1. Several IEs within the same IE type may be present to represent a list of PDRs to update. |
X |
X |
X |
X |
X |
Update PDR |
Update FAR |
C |
This IE shall be present if a FAR previously created for the PFCP session need to be modified. See Table 7.5.4.3-1. Several IEs within the same IE type may be present to represent a list of FARs to update. |
X |
X |
X |
X |
X |
Update FAR |
Update URR |
C |
This IE shall be present if URR(s) previously created for the PFCP session need to be modified. Several IEs within the same IE type may be present to represent a list of modified URRs. Previously URRs that are not modified shall not be included. See Table 7.5.4.4-1. |
X |
X |
X |
X |
– |
Update URR |
Update QER |
C |
This IE shall be present if QER(s) previously created for the PFCP session need to be modified. Several IEs within the same IE type may be present to represent a list of modified QERs. Previously created QERs that are not modified shall not be included. See Table 7.5.4.5-1. |
– |
X |
X |
X |
X |
Update QER |
Update BAR |
C |
This IE shall be present if a BAR previously created for the PFCP session needs to be modified. A previously created BAR that is not modified shall not be included. See Table 7.5.4.11-1. |
X |
– |
– |
X |
– |
Update BAR |
Update Traffic Endpoint |
C |
When present this IE shall contain the information associated with the traffic endpoint to be updated, if the UP function has indicated support of PDI optimization. All the PDRs that refer to the Traffic Endpoint shall use the updated Traffic Endpoint information. See Table 7.5.4.13-1. Several IEs within the same IE type may be present to represent a list of Traffic Endpoints to update. |
X |
X |
X |
X |
X |
Update Traffic Endpoint |
PFCPSMReq-Flags |
C |
This IE shall be included if at least one of the flags is set to "1". – DROBU (Drop Buffered Packets): the CP function shall set this flag if the UP function is requested to drop the packets currently buffered for this PFCP session (see NOTE 1). – QAURR (Query All URRs): the CP function shall set this flag if the CP function requests immediate usage report(s) for all the URRs previously provisioned for this PFCP session (see NOTE 3). – SUMPC (Stop Usage Measurement to Pause Charging): the CP function, e.g. PGW-C or (H-)SMF, shall set this flag if the usage measurement for the URRs which are applicable for charging (i.e. with the "ASPOC" flag set to "1") shall be stopped in the UP function. – RUMUC (Resume Usage Measurement to Un-pause Charging): the CP function, e.g. PGW-C or (H-)SMF, shall set this flag if the usage measurement for the URRs which are applicable for charging (i.e. with the "ASPOC" flag set to "1") shall be resumed in the UP function. – DETEID (Delete All DL N3mb and/or N19mb F-TEIDs): the MB-SMF shall set this flag to "1" if it requests the MB-UPF to delete all NG-RAN N3mb DL F-TEIDs and all UPF N19mb DL F-TEIDs for the MBS session when the Apply Action is changed from the "FSSM and/or MBSU" to the "BUFF" (with or without "NOCP"), or to "DROP" (see clause 5.34.2.4). |
X X – – |
– X X X |
– X – – |
X X X X |
– – – – |
PFCPSMReq-Flags |
Query URR |
C |
This IE shall be present if the CP function requests immediate usage report(s) to the UP function. Several IEs within the same IE type may be present to represent a list of URRs for which an immediate report is requested. See Table 7.5.4.10-1. See NOTE 3. |
X |
X |
X |
X |
– |
Query URR |
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 |
SGW-C FQ-CSID |
C |
This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24]. |
X |
X |
– |
– |
– |
FQ-CSID |
MME FQ-CSID |
C |
This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24]. |
X |
X |
– |
– |
– |
FQ-CSID |
ePDG FQ-CSID |
C |
This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24]. |
– |
X |
– |
– |
– |
FQ-CSID |
TWAN FQ-CSID |
C |
This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007 [24]. |
– |
X |
– |
– |
– |
FQ-CSID |
User Plane Inactivity Timer |
C |
This IE shall be present if it needs to be changed. |
– |
X |
X |
X |
X |
User Plane Inactivity Timer |
Query URR Reference |
O |
This IE may be present if the Query URR IE is present or the QAURR flag is set to "1". When present, it shall contain a reference identifying the query request, which the UP function shall return in any usage report sent in response to the query. |
X |
X |
X |
X |
– |
Query URR Reference |
Trace Information |
O |
When present, this IE shall contain the trace instructions to be applied by the UP function for this PFCP session. A Trace Information with a null length indicates that the trace session shall be deactivated. |
X |
X |
X |
X |
– |
Trace Information |
Remove MAR |
C |
When present, this IE shall contain the MAR Rule which is requested to be removed. See Table 7.5.4.15-1. Several IEs within the same IE type may be present to represent a list of MARs to remove. |
– |
– |
– |
X |
– |
Remove MAR |
Update MAR |
C |
This IE shall be present if an MAR previously created for the PFCP session needs to be modified. See Table 7.5.4.16-1. Several IEs within the same IE type may be present to represent a list of MARs to update. |
– |
– |
– |
X |
– |
Update MAR |
Create MAR |
C |
This IE shall be present if the CP function requests the UP function to create a new MAR for a new PDR. See Table 7.5.2.8-1. Several IEs within the same IE type may be present to represent a list of MARs to create. |
– |
– |
– |
X |
– |
Create MAR |
Node ID |
C |
This IE shall be present if a new SMF in an SMF Set, with one PFCP association per SMF and UPF (see clause 5.22.3), takes over the control of the PFCP session. When present, it shall contain the unique identifier of the new SMF. |
– |
– |
– |
X |
X |
Node ID |
TSC Management Information |
C |
This IE shall be present if the SMF needs to send TSC Management information to the UPF. Several IEs within the same IE type may be present to transfer PMICs for different NW-TT ports. (NOTE 6). |
– |
– |
– |
X |
– |
TSC Management Information |
Remove SRR |
C |
When present, this shall indicate the SRR Rule which is requested to be removed. See Table 7.5.4-19-1. Several IEs within the same IE type may be present to represent a list of SRRs to remove. |
– |
– |
– |
X |
– |
Remove SRR |
Create SRR |
C |
This IE shall be present if the CP function requests the UP function to create a new SRR. See Table 7.5.2.9-1. Several IEs within the same IE type may be present to represent a list of SRRs to create. |
– |
– |
– |
X |
– |
Create SRR |
Update SRR |
C |
This IE shall be present if SRR(s) previously created for the PFCP session need to be modified. Several IEs within the same IE type may be present to represent a list of modified SRRs. Previously SRRs that are not modified shall not be included. See Table 7.5.4.20-1. |
– |
– |
– |
X |
– |
Update SRR |
Provide ATSSS Control Information |
C |
This IE shall be present for PFCP session modification for an MA PDU session, if the ATSSS Control Information changes. When present, this IE shall contain the required ATSSS functionalities for this MA PDU session. The UPF shall replace any value received previously by the new information received in this IE. See Note 4. See Table 7.5.2.10-1. |
– |
– |
– |
X |
– |
Provide ATSSS Control Information |
Ethernet Context Information |
C |
This IE shall be present to update the list of MAC addresses associated to the PDU session during an Ethernet PDU session anchor relocation. |
– |
– |
– |
X |
– |
Ethernet Context Information |
Access Availability Information |
O |
This IE may be present for an MA PDU session to signal that an access type has become transiently unavailable or has become available again (see clause 5.20.5). Two IEs with the same IE type may be present to report changes of access availability for both 3GPP and non-3GPP accesses. |
– |
– |
– |
X |
– |
Access Availability Information |
Query Packet Rate Status |
C |
This IE shall be present if the CP function requests immediate packet rate status report(s) to the UP function. Several IEs within the same IE type may be present to represent a list of QERs for which an immediate packet rate status report is requested. See Table 7.5.4.22-1. |
– |
X |
– |
X |
– |
Query Packet Rate Status |
S-NSSAI |
O |
This IE may be present to indicate the S-NSSAI of the PDU session or MBS session, if the S-NSSAI of the PDU Session or MBS session has been provided previously to the UP function and the S-NSSAI has changed. (NOTE 5) |
– |
– |
– |
X |
X |
S-NSSAI |
RAT Type |
This IE shall be present if there is a RAT change and the CP function wants to inform the UP Function about the new RAT Type if the PFCP session is not established for a MA PDU session. |
X |
X |
– |
X |
– |
RAT Type |
|
Group Id |
C |
This IE shall be included by the CP function to indicate the new group identifier to which the PFCP session pertains, if it has been changed (see clause 5.22.4). When present, the UP function shall replace any earlier value associated to the PFCP session with the new value. |
– |
X |
– |
X |
– |
Group Id |
MBS Session N4 Control Information |
C |
This IE shall be included if: – the correspond PDU session is being associated with an MBS session, or with an MBS session and Area Session ID for a location dependent MBS service; or – the PDU session is already associated with an MBS session, or with an MBS session and Area Session ID for a location dependent MBS service, and the N19mb multicast transport information has changed. In this case, the Multicast Transport Information IE shall contain the new multicast transport information to use to receive MBS session data from the MB-UPF. Several IEs with the same IE type may be present to provide N4 control information for several MBS sessions, e.g. when the UE requests to join several MBS sessions. See Table 7.5.2.1-5 for encoding. |
– |
– |
– |
X |
– |
MBS Session N4 Control Information |
DSCP to PPI Control Information |
C |
This IE shall be present if the DSCP to PPI Control Information needs to be changed. The UPF shall replace any value received previously by the new information received in this IE. See Table 7.5.2.1-6 for encoding. |
– |
– |
– |
X |
– |
DSCP to PPI Control Information |
NOTE 1: The CP function may request the UP function to drop the packets currently buffered for the PFCP session when using extended buffering of downlink data packets, buffering is performed in the UP function and the DL Data Buffer Expiration Time is handled by the CP function. In this case, when the DL Data Buffer Expiration Time expires, the CP function shall send a PFCP Session Modification Request including the DROBU flag (to drop the downlink data packets currently buffered in the UP function) and updating the Apply Action within the FARs of this PFCP session to request the UP function to start buffering the downlink data packets with notifying the arrival of subsequent downlink data packets. See clause 5.9.3 of 3GPP TS 23.214 [2]. NOTE 2: When changing the CP F-SEID of an established PFCP Session, the CP function shall be able to handle any incoming PFCP Session related messages sent by the UP function with the previous CP F-SEID for a duration at least longer than twice the PFCP retransmission timer (N1xT1). NOTE 3: The QAURR (Query All URRs) flag in the PFCPSMReq-Flags IE and the Query URR IE are exclusive from each other in a PFCP Session Modification Request. NOTE 4: If the ATSSS resources have already been allocated to the PFCP session previously, e.g. during the PFCP session establishment, the UPF shall not allocate new values for such resources (e.g. UE Link-Specific IP Address). NOTE 5: S-NSSAI for the PDU session may be updated after PDU session establishment, i.e. during EPS to 5GS handover procedure, the initial AMF may use configured S-NSSAI for interworking to create the PDU session in 5GS. For home routed PDU session, if the S-NSSAI in serving PLMN (mapped from S-NSSAI in HPLMN) is different from the configured S-NSSAI for interworking and V-SMF reselection is not needed, the AMF will update V-SMF with S-NSSAI in serving PLMN for the PDU session, as specified in clause 4.11.1.3.3 of 3GPP TS 23.502 [29]. The S-NSSAI may also be updated by SMF+PGW-C during EPS to 5GS handover in non-roaming or roaming-with-LBO case. The S-NSSAI may be used by the UP function for performance measurement. NOTE 6: When transferring port and user plane node management information between the TSN AF or the TSCTSF and the 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.4.2 Update PDR IE within PFCP Session Modification Request
The Update PDR grouped IE shall be encoded as shown in Figure 7.5.4.2-1.
Table 7.5.4.2-1: Update PDR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update PDR IE Type = 9 (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 uniquely identify the PDR among all the PDRs configured for that PFCP session. |
X |
X |
X |
X |
X |
PDR ID |
|
Outer Header Removal |
C |
This IE shall be present if it needs to be changed. |
X |
X |
– |
X |
X |
Outer Header Removal |
|
Precedence |
C |
This IE shall be present if there is a change in the PDR’s precedence to be applied by the UP function among all PDRs of the PFCP session, when looking for a PDR matching an incoming packet. |
– |
X |
X |
X |
X |
Precedence |
|
PDI |
C |
This IE shall be present if there is a change within the PDI against which incoming packets will be matched. When present, this IE shall replace the PDI previously stored in the UP function for this PDR. See Table 7.5.2.2-2. |
X |
X |
X |
X |
X |
PDI |
|
FAR ID |
C |
This IE shall be present if it needs to be changed |
X |
X |
X |
X |
X |
FAR ID |
|
URR ID |
C |
This IE shall be present if a measurement action shall be applied or no longer applied to packets matching this PDR. When present, this IE shall contain the list of all the URR IDs to be associated to the PDR. |
X |
X |
X |
X |
– |
URR ID |
|
QER ID |
C |
This IE shall be present if a QoS enforcement action shall be applied or no longer applied to packets matching this PDR. When present, this IE shall contain the list of all the QER IDs to be associated to the PDR. |
– |
X |
X |
X |
X |
QER ID |
|
Activate Predefined Rules |
C |
This IE shall be present if new Predefined Rule(s) needs to be activated for the PDR. When present this IE shall contain one Predefined Rules name. Several IEs with the same IE type may be present to represent multiple "Activate Predefined Rules" names. |
– |
X |
X |
X |
– |
Activate Predefined Rules |
|
Deactivate Predefined Rules |
C |
This IE shall be present if Predefined Rule(s) needs to be deactivated for the PDR. When present this IE shall contain one Predefined Rules name. Several IEs with the same IE type may be present to represent multiple "Activate Predefined Rules" names. |
– |
X |
X |
X |
– |
Deactivate Predefined Rules |
|
Activation Time |
O |
This IE may be present if the PDR activation time shall be changed. (NOTE 2) |
– |
X |
X |
X |
– |
Activation Time |
|
Deactivation Time |
O |
This IE may be present if the PDR deactivation time shall be changed. (NOTE 2) |
– |
X |
X |
X |
– |
Deactivation Time |
|
IP Multicast Addressing Info |
O |
This IE may be present in an UL PDR controlling UL IGMP/MLD traffic (see clause 5.25), if it needs to be changed When present, it shall contain a (range of) IP multicast address(es), and optionally source specific address(es), identifying a set of IP multicast flows. See Table 7.5.2.2-4. Several IEs with the same IE type may be present to represent multiple IP multicast flows. When present, the UPF shall replace any IP multicast address(es) previously stored for this PDR by the IP multicast address(es) received in this IE. |
– |
– |
– |
X |
– |
IP Multicast Addressing Info |
|
Transport Delay Reporting |
C |
This IE shall be present if Transport Delay Reporting needs to be changed (e.g. transport delay reporting needs to be activated or deactivated). See Table 7.5.2.2-6. |
– |
– |
– |
X |
– |
Transport Delay Reporting |
|
RAT Type |
O |
This IE may be present if there is a RAT change for the UL PDR if the PFCP session is established for a MA PDU session. |
– |
– |
– |
X |
– |
RAT Type |
|
NOTE1: The IEs which do not need to be modified shall not be included in the Update PDR IE. The UP function shall continue to behave according to the values previously received for IEs not present in the Update PDR IE. NOTE2: When the Activation Time and Deactivation Time are not present, the PDR shall keep its current activation status, either active or inactive. |
7.5.4.3 Update FAR IE within PFCP Session Modification Request
The Update FAR grouped IE shall be encoded as shown in Figure 7.5.4.3-1.
Table 7.5.4.3-1: Update FAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update FAR IE Type = 10 (decimal) |
|||||||
Octets 3 and 4 |
Length = n |
|||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
||||
FAR ID |
M |
This IE shall identify the FAR to be updated. |
X |
X |
X |
X |
X |
FAR ID |
Apply Action |
C |
This IE shall be present if it is changed. |
X |
X |
X |
X |
X |
Apply Action |
Update Forwarding parameters |
C |
This IE shall be present if it is changed. See table 7.5.4.3-2. |
X |
X |
X |
X |
– |
Update Forwarding Parameters |
Update Duplicating Parameters |
C |
This IE shall be present if it is changed. See table 7.5.4.3-3. Several IEs with the same IE type may be present to request to duplicate the packets to different destinations. |
X |
X |
– |
– |
– |
Update Duplicating Parameters |
Redundant Transmission Forwarding Parameters |
C |
This IE shall be present if it is changed. See table 7.5.2.3-4. |
– |
– |
– |
X |
– |
Redundant Transmission Forwarding Parameters |
BAR ID |
C |
This IE shall be present if the BAR ID associated to the FAR needs to be modified. |
X |
– |
– |
X |
– |
BAR ID |
Add MBS Unicast Parameters |
C |
This IE shall be present when the Apply Action is set to "MBSU" to request the MB-UPF to forward the MBS session data to a remote GTP-U peer for unicast transport, if no remote GTP-U peers are provisioned yet in the MB-UPF, or if additional GTP-U peers need to be provisioned. (NOTE). Several IEs with the same IE type may be present to represent multiple remote GTP-U peers. See Table 7.5.2.3-6. |
– |
– |
– |
– |
X |
Add MBS Unicast Parameters |
Remove MBS Unicast Parameters |
C |
This IE shall be present when the MB-SMF to request the MB-UPF to delete a remote GTP-U peer to stop forwarding the MBS session data to that remote GTP-U peer for unicast transport. Several IEs with the same IE type may be present to represent to delete multiple remote GTP-U peers. |
– |
– |
– |
– |
X |
Remove MBS Unicast Parameters |
NOTE: When the Apply Action is changed to “MBSU” during an MBS session reactivation, remote GTP-U peers may already be provisioned in the MB-UPF if the MB-SMF did not request the MB-UPF to delete the N3mb/N19mb DL F-TEIDs when the MBS session was deactivated (see clause 5.34.2.4). |
Table 7.5.4.3-2: Update Forwarding Parameters IE in the Update FAR IE
Octet 1 and 2 |
Update Forwarding Parameters IE Type = 11 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Destination Interface |
C |
This IE shall only be provided if it is changed. When present, it shall indicate the destination interface of the outgoing packet. |
X |
X |
X |
X |
– |
Destination Interface |
|
Network instance |
C |
This IE shall only be provided if it is changed. |
X |
X |
X |
X |
– |
Network Instance |
|
Redirect Information |
C |
This IE shall be present if the instructions regarding the redirection of traffic by the UP function need to be modified. |
– |
X |
X |
X |
– |
Redirect Information |
|
Outer Header Creation |
C |
This IE shall only be provided if it is changed. See NOTE 1. |
X |
X |
– |
X |
– |
Outer Header Creation |
|
Transport Level Marking |
C |
This IE shall only be provided if it is changed |
X |
X |
– |
X |
– |
Transport Level Marking |
|
Forwarding Policy |
C |
This IE shall only be provided if it is changed. See NOTE 1. |
– |
X |
X |
X |
– |
Forwarding Policy |
|
Header Enrichment |
C |
This IE shall only be provided if it is changed |
– |
X |
X |
X |
– |
Header Enrichment |
|
PFCPSMReq-Flags |
C |
This IE shall be included if at least one of the flags is set to "1". – SNDEM (Send End Marker Packets): this IE shall be present if the CP function modifies the F-TEID of the downstream node in the Outer Header Creation IE and the CP function requests the UP function to construct and send GTP-U End Marker messages towards the old F-TEID of the downstream node. |
X |
X |
– |
X |
– |
PFCPSMReq-Flags |
|
Linked Traffic Endpoint ID |
C |
This IE may be present, if it is changed and the UP function indicated support of the PDI optimization feature, (see clause 8.2.25). When present, it shall identify the Traffic Endpoint ID allocated for this PFCP session to receive the traffic in the reverse direction (see clause 5.2.3.1). |
X |
X |
– |
X |
– |
Traffic Endpoint ID |
|
Destination Interface Type |
C |
This IE shall be present to indicate the 3GPP interface type of the destination interface, if the value has changed. |
X |
X |
– |
X |
– |
3GPP Interface Type |
|
Data Network Access Identifier |
C |
This IE shall be provided over N16a if it is changed. This IE shall not be sent over N4. |
– |
– |
– |
– |
– |
Data Network Access Identifier |
|
IP Address and Port Number Replacement |
C |
This IE shall only be provided if it is changed. |
– |
– |
– |
X |
– |
IP Address and Port Number Replacement |
|
NOTE 1: If the Outer Header Creation and Forwarding Policy are present, the UP function shall put the user plane packets in the user plane tunnel by applying Outer Header Creation, after enforcing the required Forwarding Policy. |
Table 7.5.4.3-3: Update Duplicating Parameters IE in the Update FAR IE
Octet 1 and 2 |
Update Duplicating Parameters IE Type = 105 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Destination Interface |
C |
This IE shall only be provided if it is changed. When present, it shall indicate the destination interface of the outgoing packet. |
X |
X |
– |
– |
– |
Destination Interface |
|
Outer Header Creation |
C |
This IE shall only be provided if it is changed. See NOTE 1. |
X |
X |
– |
– |
– |
Outer Header Creation |
|
Transport Level Marking |
C |
This IE shall only be provided if it is changed. |
X |
X |
– |
– |
– |
Transport Level Marking |
|
Forwarding Policy |
C |
This IE shall only be provided if it is changed. See NOTE 1. |
– |
X |
– |
– |
– |
Forwarding Policy |
|
NOTE 1: If the Outer Header Creation and Forwarding Policy are present, the UP function shall put the user plane packets in the user plane tunnel by applying Outer Header Creation, after enforcing the required Forwarding Policy. |
Table 7.5.4.3-4: Remove MBS Unicast Parameters IE in the Update FAR IE
Octet 1 and 2 |
Remove MBS Unicast Parameters Type = 304 (decimal) |
|||||||
Octets 3 and 4 |
Length = n |
|||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
||||
MBS Unicast Parameters ID |
M |
This IE shall identify the MBS Unicast Parameters IE to be removed. |
– |
– |
– |
– |
X |
MBS Unicast Parameters ID |
7.5.4.4 Update URR IE within PFCP Session Modification Request
The Update URR grouped IE shall be encoded as shown in Figure 7.5.4.4-1.
Table 7.5.4.4-1: Update URR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update URR IE Type = 13 (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 uniquely identify the URR among all the URRs configured for that PFCP session |
X |
X |
X |
X |
– |
URR ID |
|||||||||||
Measurement Method |
C |
This IE shall be present if the measurement method needs to be modified. When present, this IE shall indicate the method for measuring the network resources usage, i.e. whether the data volume, duration (i.e. time), combined volume/duration, or event shall be measured. |
X |
X |
X |
X |
– |
Measurement Method |
|||||||||||
Reporting Triggers |
C |
This IE shall be present if the reporting triggers needs to be modified. When present, this IE shall indicate the trigger(s) for reporting network resources usage to the CP function, e.g. periodic reporting or reporting upon reaching a threshold, or envelope closure, or when an SMF instructs an UPF to report the reception of the End Marker packet from the old I-UPF during a Service Request procedure (see clauses 4.2.3.2 and 4.23.4.3 in 3GPP TS 23.502 [29]). |
X |
X |
X |
X |
– |
Reporting Triggers |
|||||||||||
Measurement Period |
C |
This IE shall be present if the Measurement Period needs to be modified. When present, it shall indicate the period for generating and reporting usage reports. |
X |
X |
X |
X |
– |
Measurement Period |
|||||||||||
Volume Threshold |
C |
This IE shall be present if the Volume Threshold needs to be modified. When present, it shall indicate the traffic volume value after which the UP function shall report network resources usage to the CP function for this URR. |
X |
X |
X |
X |
– |
Volume Threshold |
|||||||||||
Volume Quota |
C |
This IE shall be present if the Volume Quota needs to be modified. When present, it shall indicate the Volume Quota value. |
– |
X |
X |
X |
– |
Volume Quota |
|||||||||||
Time Threshold |
C |
This IE shall be present if the Time Threshold needs to be modified. When present, it shall indicate the time usage after which the UP function shall report network resources usage to the CP function for this URR. |
X |
X |
X |
X |
– |
Time Threshold |
|||||||||||
Time Quota |
C |
This IE shall be present if the Time Quota needs to be modified. When present, it shall indicate the Time Quota value. |
– |
X |
X |
X |
– |
Time Quota |
|||||||||||
Event Threshold |
C |
This IE shall be present if Event Threshold needs to be modified. When present, it shall indicate the number of events after which the UP function shall report to the CP function for this URR. |
– |
X |
X |
X |
– |
Event Threshold |
|||||||||||
Event Quota |
C |
This IE shall be present if Event Quota needs to be modified. When present, it shall indicate the Event Quota value. |
– |
X |
X |
X |
– |
Event Quota |
|||||||||||
Quota Holding Time |
C |
This IE shall be present if the Quota Holding Time needs to be modified. When present, it shall contain the duration of the Quota Holding Time. |
– |
X |
X |
X |
– |
Quota Holding Time |
|||||||||||
Dropped DL Traffic Threshold |
C |
This IE shall be present if the Dropped DL Threshold needs to be modified. When present, it shall contain the threshold of the DL traffic being dropped. |
X |
– |
– |
X |
– |
Dropped DL Traffic Threshold |
|||||||||||
Quota Validity Time |
C |
This IE shall be present if Quota Validity time was not sent earlier or quota validity time value needs to be modified. |
– |
X |
– |
X |
– |
Quota Validity Time |
|||||||||||
Monitoring Time |
C |
This IE shall be present if the Monitoring Time needs to be modified. When present, this IE shall contain the time at which the UP function shall re-apply the volume or time threshold. |
X |
X |
X |
X |
– |
Monitoring Time |
|||||||||||
Subsequent Volume Threshold |
C |
This IE shall be present if the Subsequent Volume Threshold needs to be modified and volume-based measurement is used. When present, it shall indicate the traffic volume value after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time. |
X |
X |
X |
X |
– |
Subsequent Volume Threshold |
|||||||||||
Subsequent Time Threshold |
C |
This IE shall be present if the Subsequent Time Threshold needs to be modified. When present, it shall indicate the time usage value after which the UP function shall report network resources usage to the CP function for this URR for the period after the Monitoring Time. |
X |
X |
X |
X |
– |
Subsequent Time Threshold |
|||||||||||
Subsequent Volume Quota |
C |
This IE shall be present if the Subsequent Volume Quota needs to be modified. When present, it shall indicate the Volume Quota value which the UP function shall use for this URR for the period after the Monitoring Time. |
– |
X |
X |
X |
– |
Subsequent Volume Quota |
|||||||||||
Subsequent Time Quota |
C |
This IE shall be present if the Subsequent Time Quota needs to be modified. When present, it shall indicate the Time Quota value which the UP function shall use for this URR for the period after the Monitoring Time. |
– |
X |
X |
X |
– |
Subsequent Time Quota |
|||||||||||
Subsequent Event Threshold |
O |
This IE shall be present if the Subsequent Event Threshold needs to be modified. When present, it shall indicate the number of events after which the UP function shall report to the CP function for this URR for the period after the Monitoring Time. |
– |
X |
X |
X |
– |
Subsequent Event Threshold |
|||||||||||
Subsequent Event Quota |
O |
This IE shall be present if the Subsequent Event Quota needs to be modified. When present, it shall indicate the Event Quota value which the UP function shall use for this URR for the period after the Monitoring Time. |
– |
X |
X |
X |
– |
Subsequent Event Quota |
|||||||||||
Inactivity Detection Time |
C |
This IE shall be present if the Inactivity Detection Time needs to be modified. When present, it shall indicate the duration of the inactivity period after which time measurement needs to be suspended when no packets are received during this inactivity period. |
– |
X |
X |
X |
– |
Inactivity Detection Time |
|||||||||||
Linked URR ID |
C |
This IE shall be present if linked usage reporting is required. When present, this IE shall contain the linked URR ID which is related with this URR (see clause 5.2.2.4). Several IEs with the same IE type may be present to represent multiple linked URRs which are related with this URR. |
– |
X |
X |
X |
– |
Linked URR ID |
|||||||||||
Measurement Information |
C |
This IE shall be included if any of the following flag is set to "1" or if the change of flag(s) from "1" to "0" results in the IE becoming set to all zeros. Applicable flags are: – Inactive Measurement Flag: this flag shall be set to "1" if the measurement shall be paused (inactive). The measurement shall be performed (active) if the bit is set to "0" or if the Measurement Information IE is not present in the Update URR IE. – Reduced Application Detection Information Flag: this flag may be set to "1", if the Reporting Triggers request to report the start or stop of application, to request the UP function to only report the Application ID in the Application Detection Information, e.g. for envelope reporting. – Immediate Start Time Metering Flag: this flag may be set to "1" if time-based measurement is used and the UP function is requested to start the time metering immediately at receiving the flag. – Send Start Pause of Charging Flag: this flag may be set to "1" by the CP function if the UP Function is requested to send a Start Pause of Charging indication to the upstream GTP-U entity(s) when the Dropped DL Traffic Threshold is reached. – Applicable for Start of Pause of Charging Flag: this flag may be set to "1" if the URR is applicable for Start of Pause of Charging, so that the UP function shall stop the usage measurement for the URR when receiving Start Pause of Charging indication from the peer downstream GTP-U entity. – Control of Inactive Measurement Flag: the flag shall be set to "1" if the CP function requests the UP function to stop or resume the usage measurement for the URR with the "ASPOC" flag set to "1" according to the value of Inactive Measurement Flag. |
– – – X – – |
X X X – X X |
– – X – – – |
X X X X X X |
– – – X – – |
Measurement Information |
|||||||||||
Time Quota Mechanism |
C |
This IE shall be present if time-based measurement based on CTP or DTP needs to be modified. |
– |
X |
– |
– |
– |
Time Quota Mechanism |
|||||||||||
Aggregated URRs |
C |
This IE shall be included if the Aggregated URRs IE needs to be modified. See Table 7.5.2.4-2. Several IEs with the same IE type may be present to provision multiple aggregated URRs. When present, this IE shall provide the complete list of the aggregated URRs. |
– |
X |
– |
– |
– |
Aggregated URRs |
|||||||||||
FAR ID for Quota Action |
C |
This IE shall be present if the FAR ID for Quota Action IE needs to be modified. This IE may be present if the Volume Quota IE or the Time Quota IE or Event Quota IE is newly provisioned in the URR and the UP Function indicated support of the Quota Action. When present, it shall contain the identifier of the substitute FAR the UP function shall apply, for the traffic associated to this URR, when exhausting any of these quotas. See NOTE 1, NOTE 2. |
– |
X |
X |
X |
– |
FAR ID |
|||||||||||
Ethernet Inactivity Timer |
C |
This IE shall be present if the Ethernet Inactivity Timer needs to be modified. When present, it shall contain the duration of the Ethernet inactivity period. |
– |
– |
– |
X |
– |
Ethernet Inactivity Timer |
|||||||||||
Additional Monitoring Time |
O |
This IE shall be present if the additional Monitoring Time needs to be modified. When present, this IE shall contain the time at which the UP function shall re-apply the volume or time or event threshold/quota. See Table 7.5.2.4-3. The CP function shall provide the full set of Additional Monitoring Times IE(s). The UP function shall replace any Additional Monitoring Times IE(s) provisioned earlier by the new set of received IE(s). |
X |
X |
X |
X |
– |
Additional Monitoring Time |
|||||||||||
Number of Reports |
O |
This IE may be present if the Number of Reports need to be changed. When present, it shall indicate the number of usage reports to be generated by the URR. See also clauses 5.2.2.2.1 and 5.2.2.3.1. |
X |
X |
X |
X |
– |
Number of Reports |
|||||||||||
Exempted Application ID for Quota Action |
C |
This IE shall be present if Application ID for Quota Action needs to be changed. When present, it shall contain an Application ID matching packets that shall be exempted from applying the FAR ID for Quota Action when the quota has been exhausted. Several IEs with the same IE type may be present to provide multiple Application IDs. The CP function shall always provide a complete list of Application IDs. See NOTE 3. |
– |
X |
X |
X |
– |
Application ID |
|||||||||||
Exempted SDF Filter for Quota Action |
C |
This IE shall be present if the SDF Filter for Quota Action needs to be changed. When present, it shall contain a SDF Filter matching packets that shall be exempted from applying the FAR ID for Quota Action when the quota has been exhausted. Several IEs with the same IE type may be present to provide multiple SDF Filters. The CP function shall always provide a complete list of SDF Filters. See NOTE 3. |
– |
X |
X |
X |
– |
SDF Filter |
|||||||||||
User Plane Inactivity Timer |
C |
This IE shall be present if the User Plane Inactivity Timer needs to be modified. When present, it shall contain the duration of the User Plane Inactivity Timer. |
– |
– |
– |
X |
– |
User Plane Inactivity Timer |
|||||||||||
NOTE 1: The substitute FAR used when exhausting a Volume Quota or Time Quota may be set to drop the packets or redirect the traffic towards a redirect destination as specified in clause 5.4.7. NOTE 2: If the FAR as indicated in the FAR ID for Quota Action is removed after being provisioned, the UP function shall behave as if the FAR ID for Quota Action is not provisioned and shall apply the default behaviour per local configuration when the quota is exhausted. NOTE 3: The Exempted Application ID for Quota Action IE or Exempted Filter ID for Quota Action IE may be provisioned as the Restricted-Filter-Rule AVP or Filter ID AVP which is included in Final-Unit-Indication AVP from the online charging system when the Final-Unit-Action AVP is set to "REDIRECT" or "RESTRICT_ACCESS". See also 3GPP TS 32.299 [18]. |
7.5.4.5 Update QER IE within PFCP Session Modification Request
The Update QER grouped IE shall be encoded as shown in Figure 7.5.4.5-1.
Table 7.5.4.5-1: Update QER IE within PFCP Session Modification Request
Octet 1 and 2 |
Update QER IE Type = 14 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
QER ID |
M |
This IE shall uniquely identify the QER among all the QRs configured for that PFCP session |
– |
X |
X |
X |
X |
QER ID |
|
QER Correlation ID |
C |
This IE shall be present if the QER correlation ID in this QER needs to be modified. See NOTE 1. |
– |
X |
– |
X |
– |
QER Correlation ID |
|
Gate Status |
C |
This IE shall be present if the Gate Status needs to be modified. When present, it shall indicate whether the packets are allowed to be forwarded (the gate is open) or shall be discarded (the gate is closed) in the uplink and/or downlink directions. See NOTE 1. |
– |
X |
X |
X |
X |
Gate Status |
|
Maximum Bitrate |
C |
This IE shall be present if an MBR enforcement action applied to packets matching this PDR need to be modified. When present, this IE shall indicate the uplink and/or downlink maximum bit rate to be enforced for packets matching the PDR. For EPC, this IE may be set to the value of: – the APN-AMBR, for a QER that is referenced by all the PDRs of the non-GBR bearers of a PDN connection; – the TDF session MBR, for a QER that is referenced by all the PDRs of a TDF session; – the bearer MBR, for a QER that is referenced by all the PDRs of a bearer; – the SDF MBR, for a QER that is referenced by all the PDRs of a SDF. For 5GC, this IE may be set to the value of: – the Session-AMBR, for a QER that is referenced by all the PDRs of the non-GBR QoS flows of a PDU session; – the QoS Flow MBR, for a QER that is referenced by all the PDRs of a QoS Flow; – the SDF MBR, for a QER that is referenced by all the PDRs of a SDF. See NOTE 1. |
– |
X |
X |
X |
X |
MBR |
|
Guaranteed Bitrate |
C |
This IE shall be present if a GBR authorization to packets matching this PDR needs to be modified. When present, this IE shall indicate the authorized uplink and/or downlink guaranteed bit rate. This IE may be set to the value of: – the aggregate GBR, for a QER that is referenced by all the PDRs of a GBR bearer; – the QoS Flow GBR, for a QER that is referenced by all the PDRs of a QoS Flow (for 5GC); – the SDF GBR, for a QER that is referenced by all the PDRs of a SDF. See NOTE 1. |
– |
X |
X |
X |
X |
GBR |
|
Packet Rate |
C |
This IE shall be present if a Packet Rate enforcement action (in terms of number of packets per time interval) need to be modified for packets matching this PDR. |
– |
X |
– |
X |
– |
Packet Rate |
|
DL Flow Level Marking |
C |
This IE shall be set if the DL Flow Level Marking IE needs to be modified. See NOTE 1. |
– |
X |
X |
– |
– |
DL Flow Level Marking |
|
QoS flow identifier |
C |
This IE shall be present if it needs to be modified. |
– |
– |
– |
X |
X |
QFI |
|
Reflective QoS |
C |
This IE shall be present if the state of the Reflective QoS needs to be modified (activate if inactive, or deactivate the active Reflective QoS). |
– |
– |
– |
X |
– |
RQI |
|
Paging Policy Indicator |
C |
This IE shall be present if it needs to be modified. |
– |
– |
– |
X |
– |
Paging Policy Indicator |
|
Averaging Window |
O |
This IE may be present if the UP function is required to modify the Averaging Window. (NOTE 2) |
– |
– |
– |
X |
– |
Averaging Window |
|
QER Control Indications |
C |
This IE shall be included if the CP function need to provide the updated QoS enforcement control information: – RCSR (Rate Control Status Reporting): the CP function shall set this bit "1" to request the UP function to report the rate control status when the PFCP session is released. |
– |
X |
– |
X |
– |
QER Control Indications |
|
NOTE 1: The IEs which do not need to be modified shall not be included in the Update QER IE. The UP function shall continue to behave according to the values previously received for IEs not present in the Update QER IE. NOTE 2: As 5QI is not signalled over N4, one default averaging window shall be pre-configured in the UPF. |
7.5.4.6 Remove PDR IE within PFCP Session Modification Request
The Remove PDR grouped IE shall be encoded as shown in Figure 7.5.4.6-1.
R grouped IE shall be encoded as shown in Figure 7.5.4.6-1.
Table 7.5.4.6-1: Remove PDR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove PDR IE Type = 15 (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 to be deleted. |
X |
X |
X |
X |
X |
PDR ID |
7.5.4.7 Remove FAR IE within PFCP Session Modification Request
The Remove FAR grouped IE shall be encoded as shown in Figure 7.5.4.7-1.
Table 7.5.4.7-1: Remove FAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove FAR IE Type = 16 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
FAR ID |
M |
This IE shall identify the FAR to be deleted. |
X |
X |
X |
X |
X |
FAR ID |
7.5.4.8 Remove URR IE within PFCP Session Modification Request
The Remove URR grouped IE shall be encoded as shown in Figure 7.5.4.7-1.
Table 7.5.4.8-1: Remove URR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove URR IE Type = 17 (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 to be deleted. |
X |
X |
X |
X |
– |
URR ID |
7.5.4.9 Remove QER IE PFCP Session Modification Request
The Remove QER grouped IE shall be encoded as shown in Figure 7.5.4.9-1.
T Table 7.5.4.9-1: Remove QER IE PFCP Session Modification Request
Octet 1 and 2 |
Remove QER IE Type = 18 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
QER ID |
M |
This IE shall identify the QER to be deleted. |
– |
X |
X |
X |
X |
QER ID |
7.5.4.10 Query URR IE within PFCP Session Modification Request
The Query URR grouped IE shall be encoded as shown in Figure 7.5.4.10-1.
Table 7.5.4.10-1: Query URR IE within PFCP Session Modification Request
Octet 1 and 2 |
Query URR IE Type = 77 (decimal) |
||||||
Octets 3 and 4 |
Length = n |
||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||
Sxa |
Sxb |
Sxc |
N4 |
||||
URR ID |
M |
This IE shall identify the URR being queried. |
X |
X |
X |
X |
URR ID |
7.5.4.11 Update BAR IE within PFCP Session Modification Request
The Update BAR grouped IE shall be encoded as shown in Figure 7.5.4.11-1.
Table 7.5.4.11-1: Update BAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update BAR IE Type = 86 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
BAR ID |
M |
This IE shall identify the BAR Rule to be modified. |
X |
– |
– |
X |
– |
BAR ID |
|
Downlink Data Notification Delay |
C |
This IE shall be present if the UP function indicated support of the Downlink Data Notification Delay parameter (see clause 8.2.28) and the Downlink Data Notification Delay needs to be modified. When present, it shall contain the delay the UP function shall apply between receiving a downlink data packet and notifying the CP function about it, when the Apply Action parameter requests to buffer the packets and notify the CP function. |
X |
– |
– |
X |
– |
Downlink Data Notification Delay |
|
Suggested Buffering Packets Count |
C |
This IE may be present if the UP Function indicated support of the feature UDBC. When present, it shall contain the number of packets that are suggested to be buffered when the Apply Action parameter requests to buffer the packets. The packets that exceed the limit shall be discarded. |
X |
X |
X |
– |
Suggested Buffering Packets Count |
||
MT-EDT Control Information |
O |
This IE may be included to request the SGW-U to report the sum of DL Data Packets Size. |
X |
– |
– |
– |
– |
MT-EDT Control Information |
7.5.4.12 Remove BAR IE within PFCP Session Modification Request
The Remove BAR grouped IE shall be encoded as shown in Figure 7.5.4.12-1.
Table 7.5.4.12-1: Remove BAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove BAR IE Type = 87 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
BAR ID |
M |
This IE shall identify the BAR to be deleted. |
X |
– |
– |
X |
– |
BAR ID |
7.5.4.13 Update Traffic Endpoint IE within PFCP Session Modification Request
The Update Traffic Endpoint grouped IE shall be encoded as shown in Figure 7.5.4.13-1.
Table 7.5.4.13-1: Update Traffic Endpoint IE within PFCP Session Modification Request
Octet 1 and 2 |
Update Traffic Endpoint Type = 129 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Traffic Endpoint ID |
M |
This IE shall uniquely identify the Traffic Endpoint to be modified for that PFCP session. |
X |
X |
X |
X |
X |
Traffic Endpoint ID |
|
Local F-TEID |
C |
This IE shall be present if it needs to be changed. The CP function shall set the CHOOSE (CH) bit to 1 if the CP function requests the UP function to assign a local F-TEID to the PDR. See NOTE. |
X |
– |
– |
X |
– |
F-TEID |
|
Network Instance |
O |
If present, this IE shall identify the Network instance to match for the incoming packet. See NOTE. |
X |
X |
X |
X |
X |
Network Instance |
|
Redundant Transmission Detection Parameters |
C |
This IE shall be present if it needs to be changed See Table 7.5.2.2-5. See NOTE. |
– |
– |
– |
X |
– |
Redundant Transmission Detection Parameters |
|
UE IP address |
C |
This IE shall be present if it needs to be changed. In the 5GC, several IEs with the same IE type may be present to represent multiple UE IP addresses, if the UPF indicated support of the IP6PL feature (see clause 5.21). When present, the UE IP address(es) present in this IE shall replace the UE IP address(es) stored in the UP function for this traffic endpoint. See NOTE. |
– |
X |
X |
X |
– |
UE IP address |
|
Framed-Route |
C |
This IE shall be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16) and it needs to be changed. If present, this IE shall describe a framed route. Several IEs with the same IE type may be present to provision a list of framed routes. |
– |
X |
– |
X |
– |
Framed-Route |
|
Framed-Routing |
C |
This IE shall be present for a DL PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16) and it needs to be changed. If present, this IE shall describe the routing method for the UP function for the IP route related to Framed-Routes or Framed-IPv6-Routes. (NOTE 2) |
– |
X |
– |
X |
– |
Framed-Routing |
|
Framed-IPv6-Route |
C |
This IE shall be present for a PDR if the UPF indicated support of Framed Routing (see clauses 8.2.25 and 5.16) and it needs to be changed. If present, this IE shall describe a framed IPv6 route. Several IEs with the same IE type may be present to provision a list of framed IPv6 routes. |
– |
X |
– |
X |
– |
Framed-IPv6-Route |
|
QFI |
C |
This IE shall be present if QFI(s) applicable for the traffic endpoints need to be changed and if the UPF has indicated it supports MTE feature as specified in clause 8.2.25. If present, this IE shall identify the QoS Flow Identifier to match for the incoming packet. Several IEs with the same IE type may be present to provision a list of QFIs. When present, the full set of applicable QFIs shall be provided. |
– |
– |
– |
X |
– |
QFI |
|
Source Interface Type |
C |
This IE shall be present if the 3GPP interface type of the traffic endpoint needs to be changed. |
X |
X |
– |
X |
X |
3GPP Interface Type |
|
RAT Type |
O |
This IE may be present if there is a RAT change for the UL PDR(s) if the PFCP session is established for a MA PDU session. |
– |
– |
– |
X |
– |
RAT Type |
|
NOTE 1: The IEs which do not need to be modified shall not be included in the Update Traffic Endpoint IE. The UP function shall continue to behave according to the values previously received for IEs not present in the Update Traffic Endpoint IE. F-TEID may be changed if the SGW-C has received the "Change F-TEID support Indication" over the S11/S4 interface (for an IDLE state UE initiated TAU/RAU procedure to allow the SGW changing the GTP-U F-TEID). NOTE 2: In this release of specification, the UP function shall announce the IP route(s) for Framed-Route(s) or Framed-IPv6-Route(s) to the PDN regardless of the value of the Framed-Routing. |
7.5.4.14 Remove Traffic Endpoint IE within PFCP Session Modification Request
The Remove Traffic Endpoint grouped IE shall be encoded as shown in Figure 7.5.4.14-1.
Table 7.5.4.14-1: Remove Traffic Endpoint IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove Traffic Endpoint IE Type = 130 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Traffic Endpoint ID |
M |
This IE shall identify the Traffic Endpoint to be deleted. |
X |
X |
X |
X |
X |
Traffic Endpoint ID |
7.5.4.15 Remove MAR IE within PFCP Session Modification Request
The Remove MAR grouped IE shall be encoded as shown in Figure 7.5.4.15-1.
Table 7.5.4.15-1: Remove MAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove MAR IE Type = 168 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
MAR ID |
M |
This IE shall identify the MAR to be deleted. |
– |
– |
– |
X |
– |
MAR ID |
7.5.4.16 Update MAR IE within PFCP Session Modification Request
The Update MAR grouped IE shall be encoded as shown in Figure 7.5.4.16-1.
Table 7.5.4.16-1: Update MAR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update MAR IE Type = 169 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
MAR ID |
M |
This IE shall identify the MAR to be updated. |
– |
– |
– |
X |
– |
MAR ID |
|
Steering Functionality |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
Steering Functionality |
|
Steering Mode |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
Steering Mode |
|
Update 3GPP Access Forwarding Action Information |
C |
This IE shall be present if the 3GPP Access Forwarding Action Information was provisioned previously and if any of IEs is to be changed. This IE shall also be present to remove 3GPP Access Forwarding Action Information that was provisioned previously if the UE deregisters from the corresponding access. This shall be done by including this IE with a null length. |
– |
– |
– |
X |
– |
Update 3GPP Access Forwarding Action Information |
|
Update Non-3GPP Access Forwarding Action Information |
C |
This IE shall be present if the Non-3GPP Access Forwarding Action Information was provisioned previously and if any of IEs is to be changed. This IE shall also be present to remove the Non-3GPP Access Forwarding Action Information that was provisioned previously if the UE deregisters from the corresponding access. This shall be done by including this IE with a null length. |
– |
– |
– |
X |
– |
Update Non-3GPP Access Forwarding Action Information |
|
3GPP Access Forwarding Action Information |
C |
This IE shall be present to provision 3GPP access specific forwarding action information when this access is added, i.e. when the UE registers to 3GPP access. See Table 7.5.2.8-2. |
– |
– |
– |
X |
– |
3GPP Access Forwarding Action Information |
|
Non-3GPP Access Forwarding Action Information |
C |
This IE shall be present to provision Non-3GPP access specific forwarding action information when this access is added, i.e. when the UE registers to non-3GPP access. See Table 7.5.2.8-3. |
– |
– |
– |
X |
– |
Non-3GPP Access Forwarding Action Information |
|
Threshold values |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
Thresholds |
|
Steering Mode Indicator |
C |
This IE shall be included if any of the following flag is set to "1" or if the change of flag(s) from "1" to "0" results in the IE becoming set to all zeros. Applicable flags are: – ALBI (Autonomous Load Balancing Indicator): this flag shall be set to "1" if the SMF allows the UPF to apply autonomous load-balance when the Steering Mode is Load-Balancing; – UEAI (UE Assistance Indicator): this flag shall be set to "1" if the SMF allows UE assistant load-balance when the Steering Mode is Load-Balancing. |
– |
– |
– |
X |
– |
Steering Mode Indicator |
Table 7.5.4.16-2: Update 3GPP Access Forwarding Action Information IE in Update MAR IE
Octet 1 and 2 |
Update 3GPP Access Forwarding Action Information IE Type = 175 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
FAR ID |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
FAR ID |
|
Weight |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
Weight |
|
Priority |
C |
This IE shall be present if it is changed. |
– |
– |
– |
X |
– |
Priority |
|
URR ID |
C |
This IE shall be present if a measurement action shall be applied or no longer applied to packets for this access. When present, this IE shall contain the list of all the URR IDs to be associated to this access. |
– |
– |
– |
X |
– |
URR ID |
|
RAT Type |
O |
This IE may be present if it is changed. |
– |
– |
– |
X |
– |
RAT Type |
Table 7.5.4.16-3: Update Non-3GPP Access Forwarding Action Information IE in Update MAR IE
Octet 1 and 2 |
Update Non-3GPP Access Forwarding Action Information IE Type = 176 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
Same IEs and requirements as defined in Table 7.5.4.16-2 |
7.5.4.17 Create PDR/FAR/URR/QER/BAR/MAR IEs within PFCP Session Modification Request
PFCP Session Modification Request message may conditionally include Create PDR IE, Create FAR IE, Create URR IE, Create QER IE, Create BAR IE and Create MAR IE. The encoding of these IEs are specified within PFCP Session Establishment Request message (see clauses 7.5.2.2 – 7.5.2.8).
7.5.4.18 TSC Management Information IE within PFCP Session Modification Request
The TSC Management Information grouped IE shall be encoded as shown in Table 7.5.4.18-1.
Table 7.5.4.18-1: TSC Management Information IE within PFCP Session Modification Request
Octet 1 and 2 |
TSC Management Information IE Type = 199 (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.4.19 Remove SRR IE within PFCP Session Modification Request
The Remove SRR grouped IE shall be encoded as shown in Table 7.5.4.19-1.
Table 7.5.4.19-1: Remove SRR IE within PFCP Session Modification Request
Octet 1 and 2 |
Remove SRR IE Type = 211 (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 to be deleted. |
– |
– |
– |
X |
– |
SRR ID |
7.5.4.20 Update SRR IE within PFCP Session Modification Request
The Update SRR grouped IE shall be encoded as shown in Table 7.5.4.20-1.
Table 7.5.4.20-1: Update SRR IE within PFCP Session Modification Request
Octet 1 and 2 |
Update SRR IE Type = 213 (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 uniquely identify the SRR among all the SRRs configured for that PFCP session |
– |
– |
– |
X |
– |
SRR ID |
|
Access Availability Control Information |
C |
This IE shall be present if the Access Availability Control Information needs to be modified. See Table 7.5.2.9-2. The CP function shall provide the full Access Availability Control Information IE. The UP function shall replace the Access Availability Control Information IE provisioned earlier, if any, by the new received IE. |
– |
– |
– |
X |
– |
Access Availability Control Information |
|
QoS Monitoring per QoS flow Control Information |
C |
This IE shall be present if the QoS Monitoring per QoS flow Control Information needs to be modified. See Table 7.5.2.9-3. The CP function shall provide the full set of QoS Monitoring per QoS flow Control Information IE(s). The UP function shall replace any QoS Monitoring per QoS flow Control Information IE(s) provisioned earlier by the new set of received IE(s). Several IEs within the same IE type may be present to represent a list of QoS Monitoring per QoS flow Control Information for different QoS flows. |
– |
– |
– |
X |
– |
QoS Monitoring per QoS flow Control Information |
|
Direct Reporting Information |
C |
This IE shall be present if the Direct Reporting Information IE needs to be modified. See Table 7.5.2.9-4. |
– |
– |
– |
X |
– |
Direct Reporting Information |
7.5.4.21 Ethernet Context Information within PFCP Session Modification Request
The Ethernet Context Information grouped IE shall be encoded as shown in Table 7.5.4.21-1.
Table 7.5.4.21-1: Ethernet Context Information IE within PFCP Session Modification Request
Octet 1 and 2 |
Ethernet Context Information IE Type = 254 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
MAC Addresses Detected |
M |
This IE shall be present if one or more MAC addresses need to be associated to the PDU session. Several IEs with the same IE type may be present to provision multiple lists of MAC addresses (e.g. with different V-LAN tags). |
– |
– |
– |
X |
– |
MAC Addressed Detected |
7.5.4.22 Query Packet Rate Status IE within PFCP Session Modification Request
The Query Packet Rate Status grouped IE shall be encoded as shown in Table 7.5.4.22-1.
Table 7.5.4.22-1: Query Packet Rate Status IE within PFCP Session Modification Request
Octet 1 and 2 |
Query Packet Rate Status IE Type = 263 (decimal) |
||||||||
Octets 3 and 4 |
Length = n |
||||||||
Information elements |
P |
Condition / Comment |
Appl. |
IE Type |
|||||
Sxa |
Sxb |
Sxc |
N4 |
N4mb |
|||||
QER ID |
M |
This IE shall identify the QER being queried for its Packet Rate Status |
– |
X |
– |
X |
– |
QER ID |