Content for  TS 37.340  Word version:  18.2.0

The 5GC provides two UL TEID addresses during PDU Session Resource Setup, to be applied as the first UL tunnel on the NG-U interface and the additional NG-U tunnel in case the MN decides to split the PDU session.

The MN decides to setup two tunnels. The MN uses the SN Addition procedure (as described in clause 10.2.2) or the MN-initiated SN Modification procedure (as described in clause 10.3.2) up to step 6.

The MN provides a DL TEID address to be applied as the first and an additional DL tunnel address on the NG-U interface. The MN also provides which QoS flows are associated with which tunnel.

The 5GC provides an additional UL TEID address during PDU Session Resource Modify, to be applied as the additional NG-U tunnel in case the MN decides to split the PDU session.

The MN decides to setup two tunnels. If the new tunnel is to be setup at the SN, the MN uses the SN Addition procedure (as described in clause 10.2.2) or the MN-initiated SN Modification procedure (as described in clause 10.3.2) up to step 6, or up to step 8 if a QoS flow is moved to the SN and data forwarding applies.

The MN provides a DL TEID address to be applied as the additional DL tunnel address on the NG-U interface and the QoS flows associated with that tunnel.

If the MN decides to split a PDU session, it uses the SN Addition procedure or the MN-initiated SN Modification procedure, including current UPF UL NG-U tunnel used at the MN. If in-order delivery is required for some QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage.

If in-order delivery is required, the SN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the MN has delivered all UL packets from the source side to UPF for that QoS flow. Then the SN starts delivering UL packets to UPF for that QoS flow using the UPF UL TEID address used at the MN received at step 1.

The MN uses the PDU Session Resource Modify Indication message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the PDU Session Resource Modify Confirm message and allocates corresponding uplink tunnels. After receiving the End Marker packet(s) from UPF at step 7a, the MN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the MN shall continue transmiting DL packets for the not offloaded QoS flows, if any.

After receiving the DL end marker from 5GC at step 7a, the MN may generate at step 7b DL End Marker packets without QFI tag towards the SN.

If the MN receives a new UL TEID in the PDU Session Resource Modify Confirm message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated SN Modification procedure (i.e., step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets.

When the MN requests to offload some QoS flows from the SN to the MN for a PDU session, it sends the SN Modification Request message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the Xn-U Address Indication message.

When the SN requests to offload some QoS flows to the MN for a PDU session, the SN sends the SN Modification Required message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the SN Modification Confirm message.

If in-order delivery is required, the MN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the SN has delivered all UL packets from the source side to UPF for that QoS flow.

The MN uses the PDU Session Resource Modify Indication message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the PDU Session Resource Modify Confirm message and allocates corresponding uplink tunnels. After receiving the End Marker packet(s) from UPF at step 7a, the SN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the SN shall continue transmiting DL packets for the not offloaded QoS flows, if any.

After receiving the DL end marker from 5GC at step 7a, the SN may generate at step 7b DL End Marker packets without QFI tag towards the MN.

If the MN receives a new UL TEID in the PDU Session Resource Modify Confirm message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated SN Modification procedure (i.e., the step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets.