name: IAB-UE
full_form: Integrated Access and Backhaul User Equipment
context: UE configuration may be updated by the network at any time using UE Configuration Update procedure. UE configuration includes: - Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs, the Partially Allowed NSSAI and its mapping to Subscribed S-NSSAIs, the list of S-NSSAI(s) rejected partially in the RA, the Service Gap time, the list of Rejected NSSAIs if the UE Configuration Update procedure is triggered by the AMF after Network Slice-Specific Authentication and Authorization of S-NSSAIs, the Truncated 5G-S-TMSI Configuration and a priority subscription indication (e.g. MPS). If the UE and the AMF support RACS, this may also include a PLMN-assigned UE Radio Capability ID or alternatively a PLMN-assigned UE Radio Capability ID deletion indication. If the UE and AMF supports Disaster Roaming service, this may also include the "list of PLMN(s) to be used in Disaster Condition", Disaster Roaming wait range information, Disaster Return wait range information and notifying UE that the disaster condition is no longer applicable, as specified in TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. The AMF may also update MBSR (IAB-UE) with MBSR authorization information as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2], S-NSSAI location availability information. The AMF may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network as specified in clause 5.4.13.5 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. - UE Policy provided by the PCF. When AMF wants to change the UE configuration for access and mobility management related parameters the AMF initiates the procedure defined in clause 4.2.4.2. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure defined in clause 4.2.4.3. If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly. The procedure in clause 4.2.4.2 may be triggered also when the AAA Server that performed Network Slice-Specific Authentication and Authorization for an S-NSSAI revokes the authorization.
description: Integrated Access and Backhaul User Equipment (IAB-UE) refers to a type of user equipment in the 5G system that integrates both access and backhaul capabilities. This allows for more efficient communication between the UE and the network, particularly in scenarios where traditional backhaul methods may not be feasible or optimal.
explanation: The IAB-UE is classified as a User Equipment because it represents an advanced form of user device that combines multiple functionalities to enhance connectivity and service delivery within the 5G system. The context provided highlights its role in receiving configuration updates from the network, specifically through interactions with the Access and Mobility Management Function (AMF) and Policy Control Function (PCF), further solidifying its categorization as a UE.
section_title: 4.2.4 UE Configuration Update 4.2.4.1 General
biotag_Context: B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Device,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,B-Network,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,B-Device,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,B-Network,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O
biotag_Description: B-Device,I-Device,I-Device,I-Device,I-Device,I-Device,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O