name: TPAE
full_form: Third Party Authorized Entity
context: TPAE refers to the Third Party Authorized Entity. It has been introduced as part of the Reference Architecture in TR 23.754 [3], as illustrated in the figure below. Figure 5.3.1-1 TPAE is one component of the Remote Identification framework, where TPAE can monitor UAVs, access and track UAV data, and make controls to UAVs, overruling UAVC if necessary. TPAE may be treated as a UE, NF, or third party entity, depending on application scenarios. The access based on 3GPP systems and interfaces to the 3GPP systems, e.g. so called UAV2, UAV4, and UAV 7 are being studied in TR 23.754 [3] (UAV2 semantics are outside SA2 study, but UAV identification information is within the scope). Since TPAE may take control of UAVs and potentially overrules UAVC, it is authenticated and authorized differently from a normal UAVC, UAV, or UE.
description: The Third Party Authorized Entity (TPAE) is a component within the Remote Identification framework that can monitor, access, track, and control Unmanned Aerial Vehicles (UAVs), potentially overruling UAV Control (UAVC). It may be treated as a User Equipment (UE), Network Function (NF), or third-party entity depending on application scenarios.
explanation: TPAE is classified as a Network Function due to its role in controlling and interacting with UAVs within the network, as well as its potential to overrule UAVC. This classification is justified by the context highlighting TPAE's capabilities and interactions within the Remote Identification framework.
section_title: 5.3.1	Key issue details
biotag_Context: B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,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,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,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
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,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,B-Device,I-Device,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O