5.44.3.4 Non-3GPP delay budget between PINE and PEGC

For PIN indirect communication and PIN-DN communication of a PINE via a PEGC and 5G network, non-3GPP delay is the delay between the PEGC and the PINE. 5GC may need to be aware of the non-3GPP delay and compensate for this delay in 5GS. The compensation is achieved by adjusting the dynamic CN PDB for the 3GPP network by the non-3GPP delay (i.e. the network determined original PDB value is unchanged, but it needs to cover non-3GPP delay, besides the AN PDB and CN PDB).

If the PEGC supports providing of the non-3GPP delay budget for a specific QoS flow of the PIN traffic, the PEGC may provide a non-3GPP delay budget to SMF by using the UE requested PDU Session Modification procedure. Based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may, according to operator policy and implementation, consider the non-3GPP delay budget when signalling the dynamic CN PDB to NG-RAN. The dynamic CN PDB signalled to the NG-RAN may be calculated as the sum of the value of dynamic CN PDB for the related GBR QoS flow and the requested non-3GPP delay budge. If the dynamic CN PDB changes in the SMF (e.g. when an I-UPF is inserted by the SMF), based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may apply the non-3GPP delay budget again before signalling the dynamic CN PDB to NG-RAN. The non-3GPP delay budget does not impact the QoS flow binding in SMF.

NOTE: For deployments that support a PEGC to request a non-3GPP delay budget it is assumed that RAN is locally configured to give precedence to the CN PDB value received via N2 signalling as specified in clause 5.7.3.4.

It is assumed that the PEGC will limit the frequency of triggering the UE-initiated PDU Session Modification request to provide the non-3GPP delay budget to the network to avoid unnecessary signalling.