name: UAVC
full_form: UAV Controller
context: USS/UTM): based on bound UAV-ID and UAVC-ID to determine whether pairing request from UAV (with UAV-ID and GPSI) or UAVC (with UAVC-ID and GPSI) can be authorized. b. Case 2 (UAV-ID and UAVC-ID are paired and bound): based on bound information sent from UAV or UAVC to determine whether pairing request from UAV (with UAV-ID and GPSI) or UAVC (with UAVC-ID and GPSI) can be authorized. USS/UTM may need to verify the certificates presented by UAV/UAVC. NOTE 3: UAV (or UAVC) does not send GPSI to AMF. Instead, it sends UE ID (e.g. GUTI or SUCI) as a normal UE and AMF will convert the UE ID into GPSI. 3-1. UAV sends a pairing request message, e.g. in a PDU Establishment Request message to USS through the network (e.g. AMF or SMF and UFES). The message will include UAV-ID and its UE ID (e.g. GUTI). For Case 2, it includes UAV-ID (and UE ID if available) of the paired UAVC as well. 3-2. USS determines whether to authorize the pairing of UAV and UAVC 3-3. USS informs PLMN and UAV the
description: A UAV Controller (UAVC) is a device that controls and manages Unmanned Aerial Vehicles (UAVs), also known as drones, within telecommunications networks. It plays a crucial role in authorizing pairing requests between UAVs and UAVCs, ensuring secure communication and operation.
explanation: The context describes the UAVC as a device responsible for controlling and managing UAVs, emphasizing its hardware nature and function within the network.
section_title: 6.11.2.1	UAV and UAVC pairing authorization
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,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,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,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,B-Parameter,O,O,O,O,O,B-Device,B-Parameter,O,B-Parameter,O,O,O,O,O,B-Device,O,B-Network Function,O,O,O,B-Device,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,B-Parameter,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Device,O,B-Device,O,B-Parameter,O,B-Network,O,B-Device,O
biotag_Description: O,B-Device,I-Device,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,O,O,O,O,O,O,O