5.49.2.2 Configuration of the MWAB-gNB

The MWAB-gNB's configuration is managed by the OAM of the MWAB Broadcasted PLMN/SNPN and the address (or FQDN) of the OAM server per MWAB Broadcasted PLMN/SNPN may be configured at the MWAB-gNB. The OAM server of the MWAB Broadcasted PLMN/SNPN provides (re-)configuration parameters considering location of MWAB as specified in TS 38.401 [42], e.g. for the purpose including the access stratum operation of the MWAB-gNB, the N2, N3 and Xn interface management, activating/deactivating the MWAB-gNB operation and to assist the MWAB-gNB providing traffic descriptor information (see clause 5.49.1.2) used by MWAB-UE for the BH PDU Session(s) management via URSP processing.

NOTE 1: It is expected the OAM of the MWAB Broadcasted PLMN/SNPN is aware of location in which the MWAB operation can be authorized and also can obtain MWAB's current location. Only when the MWAB is authorized successfully, the configuration information can be provisioned to the MWAB-gNB. Alternatively, the OAM can also provision configuration parameters related to different areas, as defined in TS 38.401 [42].

The MWAB-gNB shall be configured with the supported S-NSSAI(s) in the MWAB Broadcasted PLMN/SNPN.

NOTE 2: A MWAB-gNB is not expected to be configured to support any dedicated S-NSSAI for BH PDU Session(s) used by MWAB-UEs for MWAB operation in the MWAB Broadcasted PLMN/SNPN as specified in TS 38.401 [42]. The support at a MWAB-gNB of S-NSSAIs dedicated to MWAB-UE BH PDU Session(s) in the MWAB Broadcasted PLMN/SNPN would mean that the MWAB-gNB could support serving the MWAB-UEs BH-PDU Session(s) in the broadcasted PLMN/SNPN.

NOTE 3: The OAM of the MWAB Broadcasted PLMN/SNPN is expected to co-ordinate with HPLMN/subscribed SNPN of the MWAB-UE to configure the traffic descriptors related information in the MWAB-gNB if it is needed. The co-ordination between OAM and HPLMN/subscribed SNPN is outside the scope of 3GPP.