5.49.3.3 MWAB-gNB authorization

The authorization of the MWAB-gNB is managed by the OAM system of the MWAB-Broadcasted PLMN/SNPN as specified in TS 38.401 [42]. The MWAB-gNB establishes a secure and trusted connection to the OAM server using the IP connectivity provided by the MWAB-UE via the Backhaul PDU Session(s) as specified in clause 5.49.1.

The OAM of the MWAB Broadcasted PLMN/SNPN determines when/where the MWAB-gNB is authorized to operate or when/where it is not authorized and needs to shut down. The OAM of the MWAB Broadcasted PLMN/SNPN may pre-configure the MWAB-gNB to turn on/shut down the operations of respective MWAB Broadcasted PLMN/SNPN part. When the MWAB-gNB is no longer authorized to operate by OAM of the MWAB Broadcasted PLMN/SNPN, the MWAB-gNB should handover the UE(s) of the MWAB Broadcasted PLMN/SNPN to other cells. The MWAB-gNB should release the UE(s) which could not be handed over. After the UEs have been handed over or released, the cell(s) of the MWAB-gNB are shut down, and the N2 and Xn connections of the MWAB-gNB are removed.

NOTE: It is expected the HPLMN/Subscribed SNPN network ensures that the BH PDU sessions authorization for MWAB UE does not interfere with the ability of the OAM of the MWAB Broadcasted PLMN/SNPN to manage the MWAB-gNB, e.g. the S-NSSAI(s) for the BH PDU session(s) of the MWAB-UE is(are) maintained long enough in the MWAB-UE subscription and are available for the MWAB-UE for a location and time that is sufficient for the MWAB-UE, so that the BH PDU sessions are available for the MWAB-gNB to be able to perform OAM-controlled shut down, which may include handing over or releasing the UEs it serves and the removal of N2 and Xn connections of the MWAB-gNB.

When the MWAB-gNB stops operating based on the OAM control, the MWAB-gNB may trigger the MWAB-UE to release the BH PDU sessions.