Section: 8.9.14 Mobile IAB-node authorization
Content: During the mobile IAB-node integration procedure, the RRC-terminating IAB-donor-CU receives the authorization status of the mobile IAB-node from the 5GC. If the authorization status is “not authorized”, the RRC-terminating IAB-donor-CU will neither establish any backhaul resources nor allocate any BAP address, TNL address or default BAP configuration for this mobile IAB-node. If the authorization status for the mobile IAB-node changes, the 5GC sends an updated authorization status to the RRC-terminating IAB-donor-CU. In case the mobile IAB-MT and its co-located mobile IAB-DU connect to same IAB-donor-CU, and the updated authorization status received from the 5GC is “not authorized”, the IAB-donor-CU will perform the following actions in this order: it will attempt to hand over the UEs served by the mobile IAB-node to other cell(s), release the F1 interface towards the mobile IAB-DU, and release all backhaul resources (including the BAP address, TNL address and default BAP reconfiguration) for this mobile IAB-node. In case the mobile IAB-MT and its co-located mobile IAB-DU connect to different IAB-donor-CUs, the RRC-terminating IAB-donor sends the updated authorization status to the F1-terminating IAB-donor-CU via the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The F1-terminating IAB-donor-CU confirms the reception of the updated authorization status via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. NOTE: In absence of Xn connectivity between the RRC-terminating IAB-donor-CU and the F1-terminating IAB-donor-CU, the passing of the authorization status is left up to implementation. If the updated authorization status for the mobile IAB-node is “not authorized”, the F1-terminating IAB-donor, attempts to hand over the UEs served by the mobile IAB-node to other cell(s), and then releases the F1 interface towards the mobile IAB-DU. After that, the F1-terminating IAB-donor requests from the RRC-terminating IAB-donor the release of all the offloaded traffic via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. The RRC-terminating IAB-donor releases the offloaded traffic and all backhaul resources (including BAP address, TNL address and default BAP reconfiguration) for this mobile IAB-node. The RRC-terminating IAB-donor may send an indication which indicates that the mobile IAB-MT can be deregistered, to AMF. If the authorization status is changed back from “not authorized” to “authorized”, the phase 2 and phase 3 of the mobile IAB-node integration procedure as defined in clause 8.12.3 are carried out.