Section: 8.15.2.1 Inter-gNB-CU Mobility between MBS Supporting nodes
Content: Figure 8.15.2.1-1 shows the inter-gNB-CU multicast mobility procedure between MBS Supporting nodes during an active multicast session. Figure 8.15.2.1-1: Inter-gNB-CU Mobility for Multicast 1. The Source gNB-CU-CP sends MC BEARER CONTEXT MODIFICATION REQUEST message towards the Source gNB-CU-UP, to request the last delivered MRB Progress of an MBS Session related to a Multicast F1-U Context Reference E1. 2. The Source gNB-CU-UP responds to the gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message, providing the last delievered MRB Progress. 3. The source gNB-CU-CP sends the HANDOVER REQUEST message to the target gNB-CU-CP with the last delievered MRB progress for the Multicast sessions the UE has joined. 4. In case the Multicast session which the UE has joined was not established in the target cell, the target gNB-CU-CP triggers the Multicast MBS Session Context Establishment procedure as defined in section 8.15.1.2. 5. The target gNB-CU-CP triggers MC BEARER CONTET SETUP REQUEST message towards the target gNB-CU-UP. 6. The target gNB-CU-UP responds to the target gNB-CU-CP by sending the MC BEARER CONTET SETUP RESPONSE message. 7. The target gNB-CU-CP sends UE CONTEXT SETUP REQUEST towards the target gNB-DU. If the target gNB-CU-CP has decided to request a PTP Forwarding tunnel, the message contains the PTP Forwarding Tunnel Required indication and the last delivered MRB Progress for the MRBs requested to be configured. 8. The target gNB-DU sends UE CONTEXT SETUP RESPONSE towards the target gNB-CU-CP. 9. If a PTP Forwarding Tunnel was requested in step 7, the target gNB-DU shall, if supported, trigger the F1-U tunnel establishment via MULTICAST DISTRIBUTION SETUP REQUEST, including the F1-U DL UP TNL information and the last delievered MRB Progress for the each of the MRB. 10. The target gNB-CU-CP sends the MC BEARER CONTEXT MODIFICATION REQUEST towards the target gNB-CU-UP, including for each MRB a request for the oldest availiable MRB Progress information, the last delivered MRB Progress, and the F1-U DL UP TNL information. 11. Based on the information received in step 10, the target gNB-CU-UP determines whether the Xn-U data forwarding is needed or not, and in case it is needed, provide for each MRB the oldest available MRB Progress and the assigned XN-U DL Forwarding UP TNL Info to the target gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message. 12. In case step 9 was triggerred, the target gNB-CU-CP sends the MULTICAST DISTRIBUTION SETUP RESPONSE to the target gNB-DU. 13. The target gNB-CU-CP sends HANDOVER REQUEST ACKNOWLEDGE to the source gNB-CU-CP, including the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB. 14. The source gNB-CU-CP forwards the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB to the source gNB-CU-UP via MC BEARER CONTEXT MODIFICATION REQUEST message. 15. The source gNB-CU-UP sends the MC BEARER CONTEXT MODIFICATION RESPONSE message to the source gNB-CU-CP. 16. The source gNB-CU-UP starts to forward MBS data towards the target gNB-CU-UP. NOTE: step 16 may happen before or after or in parallel with step 15. 17. If a PTP Forwarding Tunnel was established, the target gNB-CU-UP sends the forwarding data to the target gNB-DU.