Aerial user equipment data collection

Abstract

Certain aspects of the present disclosure provide techniques for aerial user equipment (AUE) data collection. An example method by a network data analytics function (NWDAF) entity includes sending, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs), receiving, from the RAN, the data associated with the one or more AUEs, analyzing the data, and sending one or more reports including the analyzed data to a third-party entity.

Description

AERIAL USER EQUIPMENT DATA COLLECTIONCROSS-REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims priority to Indian Patent Application No. 202441009670, filed February 13, 2024, which is hereby incorporated by reference herein.BACKGROUNDField of the Disclosure

[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for aerial user equipment data collection.Description of Related Art

[0003] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.

[0004] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY

[0005] One aspect provides a method for communication by a network data analytics function (NWDAF) entity. The method includes sending, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs); receiving, from the RAN, the data associated with the one or more AUEs; analyzing the data; and sending one or more reports including the analyzed data to a third- party entity.

[0006] Another aspect provides a method for communication by a radio access network (RAN). The method includes receiving, from a network data analytics function (NWDAF) a reporting request for data associated with one or more aerial user equipments (AUEs); collecting the data associated with the one or more AUEs based on the reporting request; and sending, to the NWDAF entity, the data associated with the one or more AUEs.

[0007] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and / or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.

[0008] The following description and the appended figures set forth certain features for purposes of illustration.

[0009] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS

[0010] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.

[0011] FIGS. 1A and IB depicts an example wireless communications network.

[0012] FIG. 2 depicts an example disaggregated base station architecture.

[0013] FIG. 3 depicts aspects of an example base station and an example user equipment.

[0014] FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.

[0015] FIG. 5 illustrates different interfaces between a network data analytics function (NDWAF) and a network function (NF).

[0016] FIG. 6 illustrates an example of radio aspects of aerial UE communications in accordance with aspects of the present disclosure.

[0017] FIG. 7 illustrates a wireless communications network that may be used for collecting data associated with one or more aerial UEs.

[0018] FIG. 8 depicts a process flow for communications in a network between different network entities.

[0019] FIG. 9 depicts a method for wireless communications.

[0020] FIG. 10 depicts a method for wireless communications.

[0021] FIG. 11 depicts aspects of an example communications device.

[0022] FIG. 12 depicts aspects of an example communications device.DETAILED DESCRIPTION

[0023] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for aerial user equipment (AUE) data collection.

[0024] In 5G New Radio (NR) core (5GC) networks, a network data analytics function (NWDAF) holds a pivotal role in enhancing network management and optimization. For example, this role includes collecting data from various data sources,analyzing the data based on artificial intelligence (AI) / machine learning (ML), and providing analytics-based statistics and predictive insights into network functions based on the analyzed data, such as abnormal UE behavior, expected UE behavior, network performance, NF load, observed service experience, QoS sustainability, slice load level, LE communication, LE mobility, user data congestion, and the like.

[0025] Wireless communication networks encompass various devices, such as terrestrial-based LEs with predictable mobility patterns and aerial-based LEs (e.g., ALEs) that may not have predictable mobility patterns. For example, aerial LEs, unlike their terrestrial counterparts, possess the capability to move in any direction, posing challenges for optimal network coverage planning. To address these challenges, the NWDAF may be positioned as a solution for collecting comprehensive information about aerial UEs, such as real-time mobility data, precise location information, dynamic flight paths, anomalous or abnormal activity or flight patterns, among other information, that may be leveraged by the NWDAF to generate insightful analytics, facilitating informed decision-making for network entities responsible for managing or setting up the network.

[0026] This data may be readily available to one or more network entities of a radio access network (RAN), including base stations that communicate directly with the aerial LEs. However, while the one or more entities of the RAN may have useful data regarding these aerial LEs, these entities of the RAN are currently not capable of providing this data to the NWDAF within the 5GC for analysis.

[0027] Accordingly, aspects of the present disclosure include techniques for enabling one or more entities of the RAN to provide data associated with aerial LEs to an NWDAF of a wireless communications network. In some cases, these techniques may include establishing a new type of interface between the one or more entities of the RAN and the NWDAF, such as a RAN-to-NWDAF interface. Aspects of the present disclosure also provide signaling aspects for facilitating the configuration of data reporting, the data reporting / collection, and the analysis of the data associated with aerial UEs.Introduction to Wireless Communications Networks

[0028] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of thepresent disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.

[0029] FIGS. 1A and IB depict an example of a wireless communications network 100, in which aspects described herein may be implemented.

[0030] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102), and non-terrestrial aspects, such as satellite 140, aircraft 145, and aerial UE (AUE) 146 illustrated in FIG. IB, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.

[0031] As will be described in more detail below, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) network 160 and 5G Core (5GC) network 190 illustrated in FIG. IB, which interoperate to provide communications services over various communications links, including wired and wireless links.

[0032] As shown in FIG. 1A, the wireless communications network 100 includes a radio access network (RAN) 130, one or more core networks 134, and one or more packet data networks.

[0033] RAN 130 may include base stations (BSs) 102, which may enable UEs 104 to communicate with the one or more core networks 134. BSs 102 may be configured for one or more Radio Access Technology (RAT) types. For example, BSs 102 may include a 5G New Radio (NR) base station (e.g., a gNodeB) and / or a 4G Long Term Evolution (LTE) base station (e.g., an eNodeB). Each BS 102 may include devices and / or components configured to enable cellular wireless communication with UEs 104. For example, BS 102 may cover a set of base station cells, each cell covering a sector (e.g., a 120° sector, etc.) and include a radio frequency (RF) transceiver configured to send and receive wireless signals in the direction of the sector and be configured to communicatewith UE 104 using a 5G NR air interface, a 4G LTE air interface, and / or using another type of cellular air interface.

[0034] The one or more core networks 134 may be managed by a provider of cellular wireless communication services and may manage communication sessions of subscribers connecting to the one or more core networks 134 via RAN 130. For example, the one or more core networks 134 may establish an Internet Protocol (IP) connection between UEs 104 and one or more PDNs 136, allowing the UEs 104 to receive IP services from the one or more PDNs 136, such as IP Services 176 and 197 illustrated in FIG. IB. In some implementations, the one or more core networks 134 may include a 5G core network 190 illustrated in FIG. IB. In other implementations, the one or more core networks 134 may include a 4G core network, such as an Evolved Packet Core (EPC) network 160 illustrated in FIG. IB.

[0035] The components of the one or more core networks 134 may be implemented as dedicated hardware components or as virtualized functions implemented on top of a common shared physical infrastructure using SDN. For example, an SDN controller may implement one or more of the components of the one or more core networks 134 using an adapter implementing a VNF virtual machine, a CNF container, an event driven serverless architecture interface, and / or another type of SDN component. Exemplary components of the one or more core networks 134 are described below with reference to FIGs. IB and 2

[0036] The one or more PDNs 136 may be associated with a Data Network Name (DNN) in 5G, and / or an Access Point Name (APN) in 4G, and a UE 104 may request a connection to the one or more PDNs 136 using the DNN or APN. The one or more PDNs 136 may include, and / or be connected to and enable communication with, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), an autonomous system (AS) on the Internet, an optical network, a cable television network, a satellite network, another wireless network (e.g., a CDMA network, a general packet radio service (GPRS) network, and / or an LTE network), an ad hoc network, a telephone network (e.g., the Public Switched Telephone Network (PSTN) or a cellular network), an intranet, or a combination of networks. The one or more PDNs 136 may include one or more application servers 138 for providing services for an application running on a UE 104 and establishing an application session with the UE 104 via the one or more core networks 134.

[0037] FIG. IB depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA), satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (loT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0038] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0039] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell). A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area), a pico cell (covering relatively smaller geographic area, such as a sports stadium), a femto cell (relatively smaller geographic area (e.g., a home)), and / or other types of cells.

[0040] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU),one or more distributed units (DUs), one or more radio units (RUs), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.

[0041] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN)) may interface with the EPC network 160 through first backhaul links 132 (e.g., an SI interface). BSs 102 configured for 5G (e.g., 5GNR or Next Generation RAN (NG-RAN)) may interface with 5GC network 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC network 160 or 5GC network 190) with each other over third backhaul links 135 (e.g., X2 interface), which may be wired or wireless.

[0042] Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz - 7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz”. Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz - 71,000 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 may be further defined in terms of sub-ranges, such as a first sub-range FR2-1 including 24,250 MHz - 52,600 MHz and a second sub-rangeFR2-2 including 52,600 MHz - 71,000 MHz. A base station configured to communicate using mmWave / near mmWave radio frequency bands (e.g., a mmWave base station such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0043] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz), and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL).

[0044] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. IB) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182”. UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182”. BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.

[0045] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0046] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), aphysical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0047] EPC network 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC network 160. Generally, MME 162 provides bearer and connection management.

[0048] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0049] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0050] 5GC network 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, a Network Data Analytics Function (NWDAF) 193, a Session Management Function (SMF) 194, a User Plane Function (UPF) 195, one or more Network Functions (NFs) 198, and a Data Collection Application Function (DCAF). The one or more NFs may include, for example, a Charging Function (CHF), a Network Repository Function (NRF), a Network Exposure Function (NEF), a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), or other network functions.

[0051] AMF 192 is a control node that processes signaling between UEs 104 and 5GC network 190. AMF 192 provides, for example, quality of service (QoS) flow and session management. Additionally, as shown, AMF 192 may be in communication with Unified Data Management (UDM) 196.

[0052] Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC network 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0053] In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0054] FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both). A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an Fl interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.

[0055] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signalsover a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0056] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an 0-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0057] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rdGeneration Partnership Project (3GPP). In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.

[0058] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture,the RU(s) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0059] The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an 01 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an 01 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.

[0060] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.

[0061] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from nonnetwork data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0062] FIG. 3 depicts aspects of an example BS 102 and a UE 104.

[0063] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.

[0064] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively 352), transceivers 354a-r (collectively 354), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360). UE 104 includes controller / processor 380, which may be configured to implement various functions described herein related to wireless communications.

[0065] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or others. The data may be for the physical downlink shared channel (PDSCH), in some examples.

[0066] Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

[0067] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a- 332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.

[0068] In order to receive the downlink transmission, UE 104 includes antennas 352a- 352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0069] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0070] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)).The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0071] At BS 102, the uplink signals from UE 104 may be received by antennas 334a- t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.

[0072] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0073] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0074] In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0075] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.

[0076] In some aspects, one or more processors may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.

[0077] FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIGS. 1A and IB.

[0078] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5GNR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

[0079] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.

[0080] A wireless communications frame structure may be frequency division duplex (FDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

[0081] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling). In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than anentire slot. Other wireless communications technologies may have a different frame structure and / or different channels.

[0082] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerol ogies (p) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe. For slot configuration 1, different numerol ogies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology p, there are 14 symbols / slot and 2p slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2^ X 15 kHz, where p is the numerology 0 to 6. As such, the numerology p = 0 has a subcarrier spacing of 15 kHz and the numerology p = 6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology p = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps.

[0083] As depicted in FIGS. 4A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0084] As illustrated in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3). The RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0085] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol.

[0086] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe / symbol timing and a physical layer identity.

[0087] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.

[0088] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and / or paging messages.

[0089] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS). The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0090] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.Introduction to Data Collection and Analytics

[0091] As noted above, the wireless communications network 100 includes the NWDAF 193. The NWDAF 193 may be configured to provide machine intelligence anda centralized, predictive analytics platform for the 5GC network 190, allowing the 5GC network 190 to deliver the performance required for complex 5G network slices.

[0092] The main functions of the NWDAF 193 may include collecting data from various data sources, analyzing the data based on an artificial intelligence (AI) / machine learning (ML) model, and providing analytics-based statistics and predictive insights into 5GC network functions based on the analyzed data, such as abnormal UE behavior, expected UE behavior, network performance, NF load, observed service experience, QoS sustainability, slice load level, UE communication, UE mobility, user data congestion, and the like.

[0093] The various data sources may include the one or more NFs 198, one or more application functions (AFs) (e.g., DCAF 199), a network operation and maintenance system (e.g., operation, administration and maintenance (0AM)), and other data sources. In some cases, data types that may be collected by the NWDAF 193 may include 5GC service-based interface (SBI) data, control or user plane data, logs, and data from UE.

[0094] In some cases, the DCAF 199 may be configured to receive the data from the one or more UEs 104 in the wireless communications network 100 and to provide this data to the NWDAF 193. In some cases, the data may include a variety of useful information logged by the one or more UEs 104, such as quality of experience (QoE) metrics, usage measurements, dynamic quality of service (QoS) / charging policy invocations, content delivery network (CDN) access logs, and other information.

[0095] After collecting the data from the various data sources, the NWDAF 193 may then analyze the data based on the AI / ML model and provide a metadata exposure service, a data analysis service, and the like for the one or more NFs or the one or more AFs based on the collected data. The NWDAF 193 is introduced mainly for automatic and intelligent network operation and maintenance, network performance and service experience optimization, end-to-end service level agreement (SLA) assurance, and the like. In some cases, the AI / ML model may be applied to various network functions such as mobility management, session management, and network automation. In some cases, the NWDAF 193 may be responsible for AI / ML model training (e.g., based on the collected data), including serving as a central service unit in federated training.

[0096] As shown in FIG. 5, there are two types of interfaces between the NWDAF 193 and the one or more NFs 198: an Nnf interface and an Nnwdaf interface. The Nnfinterface may be used by the NWDAF 193 to request one or more of the following from the one or more NFs 198: a subscription to data transfer of a specific context, cancellation of the subscription to the data transfer, a specific report of data for the specific context, and the like. A 5G system architecture further allows the NWDAF 193 to obtain management data from an OAM by invoking an operation and maintenance system service of the OAM. The Nnwdaf interface may be used by the one or more NFs 198 to request one or more of the following from the NWDAF 193: a subscription to network analysis transfer of a specific context, cancellation of the subscription to the network analysis transfer, a specific report of network analysis of the specific context, and the like. Using these interfaces, the NWDAF 193 collects data from the one or more NFs 198, learns an AI / ML model through data analysis, and provides AI / ML optimization services such as performance and data analysis for the one or more NFs 198.Introduction to Aerial UEs

[0097] Some UEs in the wireless communications network 100 may be aerial UEs capable of flying or maneuvering through the air, such as aerial UE 146 depicted and described with respect to FIG. IB. Such aerial UEs may support uplink or downlink communications with one or more cells or sidelink communications with each other. To facilitate the uplink, downlink, and sidelink communications by aerial UEs, wireless communications network 100 may define a spectrum dedicated to aerial UEs. The dedicated spectrum may be for uplink and downlink communications between aerial UEs and one or more RAN entities (e.g., BS 102 over a Uu interface), or the dedicated spectrum may be for sidelink communications between aerial UEs (e.g., over a PC5 interface). In addition to the dedicated spectrum, aerial UEs may operate in other wireless spectrums. The wireless communications system may support efficient techniques for operation of aerial UEs in dedicated spectrum and other spectrums. An aerial UE may be, for example, a UAV or drone, or a UE installed in a UAV or drone.

[0098] FIG. 6 illustrates an example of radio aspects 600 of aerial UE communications in accordance with aspects of the present disclosure. In the example of FIG. 6, an aerial UE 605-a may establish a connection 625 (e.g., Uu connectivity) with a BS 610. The BS 610 may be an example of a BS 102 included within the RAN 130 illustrated in FIGS. 1A and IB. In some cases, the aerial UE 605-a may use the connection 625 to communicate with the BS 610 to support different applications (e.g., video, remote command and control (C2), etc.). The aerial UE 605-a may alsoestablish a connection 630 (e.g., PC5) connection with another aerial UE 605-Z>, and the aerial UE 605-a may communicate with the aerial UE 605-Z> to support other applications. Examples of such other applications include user-to-everything (U2X) detect and avoid (U2X-DAA) applications and other applications mainly used for collision control (e.g., using broadcast messages).

[0099] In some examples, the aerial UE 605-Z> may also interact (e.g., over a connection 635, such as a PC5 connection) with a law enforcement officer 615 or service for identification and other purposes. As an example, the aerial UE 605-Z> may interact with the law enforcement officer 615 or service for U2X identification (ID) (e.g., remote identification), and the aerial UE 605-Z> may identify or receive flight information from the law enforcement officer 615 or service (e.g., using broadcast messages). In other examples, the aerial UE 605-Z> may establish a connection 640 with a remote control 620 for remote command and control (C2). In some cases, the connection 640 may be within visual line of sight while in other cases the connection 640 may be beyond visual line of sight (e.g., up to 10 km or beyond). The connection 640 may be referred to as a U2X-C2 connection and may be, for example, a PC5, bidirectional connection.

[0100] In some cases, it may be appropriate for aerial UEs to support similar operations to non-aerial UEs when connected to a wireless network. For instance, it may be appropriate to enable 3 GPP technologies (e.g., New Radio (NR)) for aerial UEs operating in a spectrum dedicated to the aerial UEs (e.g., UAV dedicated spectrum). In such cases, there may be a number of challenges to solve to facilitate smooth operation of aerial UEs in the wireless network. Such challenges may include cell selection, PLMN selection, tracking area management, and paging management for aerial UEs. Further, because the communication requirements of an aerial UE may change depending on a mission status in which the aerial UE is operating (e.g., an aerial state, a ground state, a pre-flight state, or a post-flight state), it may not be feasible to adopt operations used by non-aerial UEs for aerial UEs.Aspects Related to Aerial UE Data Collection

[0101] In fifth generation (5G) new radio (NR) networks, such as the wireless communications network 100 illustrated in FIGS. 1A and IB, the NWDAF 193 is a pivotal component for improving network management and optimization. For example, as 5G NR networks strive to deliver unprecedented speed, capacity, and connectivity, theNWDAF 193 plays a crucial role in harnessing data from diverse sources for a multitude of applications, including network coverage and resource planning. This sophisticated analytics function acts as the brain behind informed decision-making, drawing insights from the vast pool of data available within the 5G network.

[0102] Such wireless communications networks may include various types of devices. One type of device may include terrestrial -based UEs, such as the UE 104 illustrated in FIGS. 1A and IB, which may present predictable mobility patterns as they navigate along established paths such as roads, highways, and pedestrian areas. This predictability enables efficient resource allocation and optimization strategies, enhancing the overall performance of the 5G network in terrestrial scenarios.

[0103] However, another type of device includes aerial-based UEs, such as the aerial UEs 605-a and 605-Z>, which introduce a paradigm shift in network dynamics. Unlike their terrestrial counterparts, aerial UEs possess the capability to move in any direction, including vertical trajectories, and may be capable of going places that no terrestrial -based UE is capable of going. This newfound freedom in movement poses a unique challenge for optimal network coverage planning and optimization.

[0104] To address these challenges, the NWDAF 193 is positioned as a solution for collecting comprehensive information about aerial UEs. This includes real-time mobility data, precise location information, and dynamic flight paths, among other information, that may vary during different times of the day or special events. By leveraging this data, the NWDAF 193 may generate insightful analytics, facilitating informed decisionmaking for network entities responsible for managing or setting up the network. These analytics prove invaluable for optimizing coverage not only for terrestrial UEs but also for their aerial counterparts.

[0105] Furthermore, the analytics information derived from NWDAF-collected data extends its utility beyond network management. It becomes a valuable resource for third parties involved in flight planning and monitoring of aerial UEs. By providing a comprehensive understanding of the aerial environment, the NWDAF 193 empowers network entities and third-party stakeholders alike to collaborate effectively, ensuring a harmonious integration of terrestrial and aerial UEs within the 5G ecosystem.

[0106] As noted above, the data associated with aerial UEs that may be helpful for network planning an optimization may include, among other information, real-timemobility data of the aerial UEs, precise location data of the aerial UEs, and dynamic flight paths of the aerial UEs, which may vary during different times of the day or special events. This data may be readily available to one or more network entities of a RAN of a wireless communications network, such as the BS 102 of RAN 130 of the wireless communications network 100 illustrated in FIGS. 1A and IB, as these aerial UEs maintain connectivity (e.g., Uu connectivity) with the one or more network entities of the RAN, as described above with respect to FIG. 6. However, while the one or more entities of the RAN may have useful data regarding these aerial UEs, these entities of the RAN are currently not capable of providing this data to the NWDAF 193 for analysis.

[0107] Accordingly, aspects of the present disclosure include techniques for enabling one or more entities of the RAN to provide data associated with aerial UEs to an NWDAF of a wireless communications network. In some cases, these techniques may include establishing a new type of interface between the one or more entities of the RAN and the NWDAF, such as a RAN-to-NWDAF interface.

[0108] For example, FIG. 7 illustrates a wireless communications network 700 that may be used for collecting data associated with one or more aerial UEs (AUEs) 704. For example, as shown, the one or more AUEs 704 may establish one or more connections 720 (e.g., communications links 120 illustrated in FIG. IB) with one or more network entities 702 of a RAN 730. The one or more network entities 702 may be examples of the BS 102 depicted and described with respect to FIGS. 1A, IB, and 3. Similarly, the RAN 730 may be an example of the RAN 130 depicted and described with respect to FIG. 1A.

[0109] The one or more network entities 702 may be configured to collect data associated with the one or more AUE 704, such as mobility information associated with the one or more AUEs 704, location information associated with the one or more AUEs 704, and / or quality of service information associated with one or more radio links or connections of the one or more AUEs 704 established with the one or more network entities 702 of the RAN 730. In some cases, as will be described in greater detail below, the one or more network entities 702 may be configured by an NWDAF 793 to collect and report the data associated with the one or more AUEs 704 based on a reporting request received from the NWDAF that includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on. The data associated with the one or more AUEs 704 collected by the one or more network entities 702 may then be provided to RAN 730.

[0110] Thereafter, unlike traditional wireless communications networks, the data associated with the one or more AUEs 704 may be provided by the RAN 730 (or the one or more network entities 702) to an NWDAF 793 for further processing and analysis before being provided to one or more third-party entities, such as one or more NFs or one or more AFs. For example, as noted above, in traditional wireless communications networks, the RAN may not be capable of providing the data associated with AUEs to an NWDAF. However, as shown in the wireless communications network 700 of FIG. 7, a new interface or logical connection may be established between the RAN 730 and the NWDAF 793, such as a RAN-to-NWDAF logical connection 750. For example, the RAN-to-NWDAF logical connection 750 may facilitate the transfer of the data associated with the one or more AUEs 704 from the RAN 730 to the NWDAF 793 for further processing and analysis. The RAN-to-NWDAF logical connection 750 may also facilitate the reporting request sent by the NWDAF 793 to the one or more network entities 702 of the RAN 730.[OHl] In some cases, in addition to receiving the data associated with the one or more AUEs 704 from the one or more network entities 702 of the RAN 730, the NWDAF 793 may also be configured to receive data associated with the one or more AUEs 704 from a DCAF 708. In some cases, while the data associated with the one or more AUEs 704 received from the one or more network entities 702 of the RAN 703 may include information generated by the one or more network entities 702, such as mobility information, location information, and or quality of service information, the information associated with the one or more AUEs 704 provided by the DCAF 708 for the NWDAF 793 may include information that is transmitted by the one or more AUEs 704 to the DCAF 708, such as QoE metrics, usage measurements, dynamic QoS / Charging policy invocations, CDN access logs, and other information.

[0112] In some cases, the RAN-to-NWDAF logical connection 750 may also be used for other purposes. For example, in some cases, the RAN 730 may utilize a number of applications to maximize operational efficiency of the RAN 730, such as xApps and rApps. xApps and rApps are applications that run machine learning models on the RAN 730 for RAN analytics and closed-loop decisions that need fast turn-around without having to go to the core network. Accordingly, in some cases, some of the analytics generated by these xApps and rApps can be sent to the NWDAF 793 using the RAN-to- NWDAF logical connection 750 and reused as distilled information for NWDAF 793.

[0113] Aspects of the present disclosure also provide techniques for facilitating the configuration of data reporting, the data reporting / collection, and the analysis of the data associated with aerial UEs. For example, FIG. 8 depicts a process flow including operations 800 for communications in a network between RAN entity 802, one or more AUEs 804, an NWDAF entity 806, a DCAF entity 808, and a third-party entity 810. The operations 800 may be performed for configuration and collection of data associated with the one or more AUEs 804.

[0114] In some aspects, the RAN entity 802 may be an example of the BS 102 depicted and described with respect to FIGS. 1A, IB, and 3, a disaggregated base station depicted and described with respect to FIG. 2, the one or more network entities 702 depicted and described with respect to FIG. 7, or the RAN 730 depicted and described with respect to FIG. 7. In some cases, the RAN entity 802 may be associated with or included within RAN 801, which may be an example of RAN 130 depicted and described with respect to FIG. 1A. The one or more AUEs 804 may be an example of the AUE 146 depicted and described with respect to FIGS. 1A, IB, and 3 or the one or more AUEs 704 depicted and described with respect to FIG. 7. Additionally, the NWDAF entity 806 may be an example of the NWDAF 193 depicted and described with respect to FIGS. IB and 5 or the NWDAF 793 depicted and described with respect to FIG. 7. Additionally, the DCAF entity 808 may be an example of the DCAF 199 depicted and described with respect to FIG. IB or the DCAF 708 depicted and described with respect to FIG. 7. As shown, the NWDAF entity 806 and the DCAF entity 808 may be part of a core network803, such as the 5GC network 190 depicted and described with respect to FIG. 1. The third-party entity 810 may be an example of the one or more NF(s) 198 depicted and described with respect to FIGS. IB, one or more AFs, or an unmanned aircraft system traffic management (UTM) of an unmanned aircraft system (UAS).

[0115] As shown, operations 800 begin at 812 with the NWDAF entity 806 receiving, from the third-party entity 810, a data reporting configuration for the one or more AUEs804. In some cases, the data reporting configuration may include one or more parameters specifying one or more types of data associated with the one or more AUEs 804 to be collected and reported on. In some cases, the data reporting configuration may be received from the third-party entity 810 via the DCAF entity 808, as shown.

[0116] Thereafter, as shown at 814, the NWDAF entity 806 may send, to the RAN entity 802 based on the data reporting configuration received from the third-party entity810, a reporting request for data associated with the one or more AUEs 804. In some cases, the reporting request may be sent by the NWDAF entity 806 to the RAN entity 802 using an NWDAF-to-RAN logical connection established between the NWDAF entity 806 and the RAN entity 802.

[0117] In some cases, the reporting request may include the one or more parameters specifying one or more types of data associated with the one or more AUEs 804 to be collected and reported on. In some cases, the one or more types of data specified by the one or more parameters include at least one of mobility information associated with the one or more AUEs 804, location information associated with the one or more AUEs 804, quality of service information associated with one or more radio links of the one or more AUEs 804 established with the RAN entity 802, radio resource management (RRM) parameters maintained between the one or more AUEs 804 and RAN entity 802, status information associated with the one or more AUEs 804, preferred RANs of the one or more AUEs 804, or RANs observed on respective scan lists of the one or more AUEs 804. In some cases, the mobility information may include information such as flight paths of the one or more AUEs 804 through an area of the RAN 801 or a duration of the flight paths of the one or more AUEs 804.

[0118] Thereafter, as shown at 816, the RAN entity 802 collects the data associated with the one or more AUEs 804. In some cases, collecting the data associated with the one or more AUEs at 816 may include collecting the specified one or more types of data associated with the one or more AUEs 804. In some cases, collecting the data associated with the one or more AUEs 804 may be based on one or more signals received from the one or more AUEs 804, as shown at 818. In some cases, the one or more signals may include, for example, reference signals that the RAN entity 802 may use to determine the data (e.g., mobility information, location information, quality of service information, etc. associated with the one or more AUEs). In some cases, the reference signals may include sounding reference signals (SRSs), positioning reference signals (PRS), demodulation reference signals (DMRS), or other reference signals. For example, the RAN entity 802 may receive and perform measurements on the one or more signals that may indicate the mobility information, the location information, or the quality of service information associated with the one or more AUEs 804.

[0119] In some cases, the data reporting configuration and the reporting request may be for one or more specific AUEs of the one or more AUEs 804 or may be for a non-specific group of AUEs of the one or more AUEs 804. In other words, the reporting request may request that the RAN entity 802 collect and report data associated with one or more specific AUEs. In other cases, rather than requesting data associated with the one or more specific AUEs of the one or more AUEs 804, the report request may request that the RAN entity 802 collect and report data on a non-specified group of AUEs, generally. Accordingly, when collecting the data associated with the one or more AUEs at 816, the RAN entity 802 may either collect the data associated with the one or more specific AUEs or may collect the data associated with the non-specific group of AUEss based on the reporting request.

[0120] Thereafter, as shown at 820, the NWDAF entity 806 may receive the data associated with the one or more AUEs 804 from the RAN entity 802. In some cases, the NWDAF entity 806 may receive the data associated with the one or more AUEs 804 from the RAN entity 802 using the NWDAF-to-RAN logical connection established between the NWDAF entity 806 and the RAN entity 802.

[0121] In some cases, when the data reporting configuration and the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs 804, the data that is sent to the NWDAF entity 806 by the RAN entity 802 may need to be identifiable to the one or more specific AUEs of the one or more AUEs 804 so that the NWDAF entity 806 knows to which specific AUEs the data corresponds.

[0122] Different options may exist for identifying the one or more specific AUEs to which the data, received by the NWDAF entity 806, corresponds. For example, in some cases, as shown at 822, the one or more AUEs 804, including the one or more specific AUEs, may each optionally be configured to separately provide a unique aerial identifier to the RAN entity 802 that identifies the AUE from which the unique aerial identifier is received. For example, a first specific AUE may provide a first aerial identifier to the RAN entity 802 that uniquely identifies that first specific AUE. Additionally, a second specific AUE of the one or more AUEs 804 may provide a second aerial identifier to the RAN entity 802 that uniquely identifiers that second specific AUE, and so on. In some cases, the one or more AUEs 804 may be configured to provide these aerial identifiers to the RAN entity 802 in radio resource control (RRC) signaling. In some cases, the aerial identifiers may include at least one of a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier, a CAA specific session ID (e.g., ASTM F38 Session Id for Remote ID), an identifier that is used specifically in a serving PLMN (e.g.generated by UAS NF and provided to the one or more AUEs 804) associated with the RAN 801 and that is typically shorter than the CAA-Level UAV identifier, or a combination thereof.

[0123] Accordingly, when the NWDAF entity 806 receives the data associated with the one or more AUEs 804 at 820 from the RAN entity 802, the data may include one or more aerial identifiers and each different aerial identifier of the one or more aerial identifiers may identify a different respective AUE of the one or more specific AUEs.

[0124] Another option for identifying the one specific AUE may involve determining an identifier of the one specific AUE based on another identifier. For example, in some cases, when the aerial identifier is not available in the RRC signaling (e.g., at the access stratum layer of the RAN entity 802), one or more 3 GPP -based identifiers (e.g., nonaviation related identifiers) may be used to identify the one or more specific AUEs. For example, in some cases, the one or more 3 GPP-based identifiers may be available to the RAN entity 802 and may be included in the data associated with the one or more AUEs 804 sent to the NWDAF entity 806 at 820. In such cases, each 3GPP -based identifier of the one or more 3 GPP -based identifiers may be associated to a different respective AUE of the one or more specific AUEs. In some cases, the one or more 3 GPP -based identifiers may include one or more of an international mobile subscriber identity (IMSI), a temporary mobile subscriber identity (TMSI), a 5G globally unique temporary identity (5G-GUTI), an international mobile equipment identity (IMEI), a subscription permanent identifier (SUPI), a subscription concealed identifier (SUCI), or other identifiers that may be used to identify a UE in 3 GPP network.

[0125] Thereafter, the NWDAF entity 806 may send the one or more 3 GPP -based identifiers to a UAS NF entity to retrieve, from the UAS NF, a mapping between the one or more 3GPP -based identifiers and one or more aerial identifiers (e.g. CAA-level UAV IDs). In such cases, each different aerial identifier of the one or more aerial identifiers identifies a different respective AUE of the one or more specific AUEs. In other words, the NWDAF entity 806 may receive, from the UAS NF entity based on the one or more 3 GPP -based identifiers, one or more aerial identifiers and each different aerial identifier may uniquely identify a respective specific AUE of the one or more specific AUEs. In some cases, the NWDAF entity 806 may send the one or more 3 GPP -based identifiers to the UAS NF entity using a service-based logical connection established between the NWDAF entity 806 and the UAS NF entity.

[0126] In some cases, the RAN entity 802may report the data associated with the one or more AUEs (e.g., including the one or more specific AUEs) to an AMF entity of the core network 803, such as the AMF 192 depicted and described with respect to FIG. IB. Further, in some cases, the AMF entity may be configured to attach the one or more 3 GPP -based identifiers to the data from the RAN entity 802 before forwarding the data associated with the one or more specific AUEs to the UAS NF serving the one or more specific AUEs. Thereafter, the UAS NF may be configured to determine the one or more aerial identifiers of the one or more specifics AUE based on a mapping between the one or more 3 GPP -based identifiers and the one or more aerial identifiers. The UAS NF may then push the data associated with the one or more specific AUEs to the NWDAF entity 806 including the one or more aerial identifiers for the one or more specific AUEs.

[0127] In some cases, in addition to receiving data associated with the one or more AUEs 804 collected and sent by the RAN entity 802, the NWDAF entity 806 may also receive data associated with the one or more AUEs 804 from the DCAF entity 808. For example, as shown at 824, the one or more AUEs 804 may be configured to report (e.g., send) AUE-direct data to the DCAF entity 808. In some cases, this AUE-to-DCAF direct reporting was traditionally configured based on a DCAF-specific data reporting configuration. However, in some cases, the one or more AUEs 804 may instead be configured for the AUE-to-DCAF direct reporting based on one or more AUE-specific data reporting configurations that include parameters (e.g., application service provider (ASP) parameters) configuring the types of data to be reported by the one or more AUEs 804 to the DCAF entity 808. In some cases, the types of data that may be reported by the one or more AUEs 804 directly to the DCAF entity 808 may include information, such as QoE metrics, usage measurements, dynamic QoS / Charging policy invocations, CDN access logs, and other information.

[0128] In some cases, the AUE-direct data may be sent in a generic ASP container or may be sent in multiple containers, each container having a unique container ID. In some cases, the DCAF entity 808 may use the container IDs of the multiple containers to determine which information of the AUE-direct data to send to the NWDAF entity 806 and which information of the AUE-direct data to send to the third-party entity 810 directly.

[0129] As shown at 826, the DCAF entity 808 may send the AUE-direct data to the NWDAF entity 806.

[0130] Thereafter, as shown at 828, the NWDAF entity 806 may analyze the data associated with the one or more AUEs 804, including the data received from the RAN entity 802 and AUE-direct data from the DCAF entity 808. In some cases, to analyze the data associated with the one or more AUEs 804, the NWDAF entity 806 may process the data with a machine learning (ML) model trained to produce one or more outputs based on the data. In other words, the NWDAF entity 806 my input the data associated with the one or more AUEs 804 into the ML model, which may be configured to make inferences about the data and produce the one or more outputs based on the inferences about the data. In some cases, the NWDAF entity 806 may also be configured to train or refine the ML model based on the data associated with the one or more AUEs 804.

[0131] In some cases, the one or more outputs may include an indication of one or more cells of the RAN 801 that need an AUE-based radio frequency (RF) performance retuning.

[0132] In some cases, the one or more outputs may include an indication of frequent flight patterns of the one or more AUEs associated with the RAN over a period of time. In some cases, this information may be output to the RAN entity 802 an / or 0AM entity of the RAN 801 for handover planning of AUEs in the one or more AUEs 804 and / or a UTM entity associated with the one or more AUEs 804 for flight planning.

[0133] In some cases, the one or more outputs may include a classification of tracking area identifiers (TAIs) over time based on AUE density over time. For example, in some cases, the NWDAF entity 806 may identify usage of cells in TAIs with respect to actual volume or type of AUE traffic to identify TAIs that may need retuning for load balancing and congestion control. In some cases, this information may be output to the AMF entity of the core network 803 and to the RAN entity 802 for better planning for mobility management.

[0134] In some cases, the one or more outputs may include a prediction of resource usage in the RAN associated with the one or more AUEs for a period of time versus resource usage associated with terrestrial-based UEs. In some cases, this information may be used for RAN capacity planning, antenna orientation (e.g., knowing where to point antennas of the RAN entity 802 based on the predicted resource usage associated with the AUEs), and the like. In some cases, this information may be output to the network entityof the RAN 801 for MM and / or to a UTM associated with the one or more AUEs 804 for flight planning.

[0135] In some cases, the one or more outputs may include the one or more outputs include at least one of an indication of abnormal AUE patterns associated with the one or more AUEs, an indication of a denial-of-service attack on the one or more AUEs, an indication of a predicted behavior for the one or more AUEs in real-time, or an indication of optimal radio frequency (RF) coverage zones for flight paths associated with the one or more AUEs.

[0136] Thereafter, as shown at 826, the NWDAF entity 806 sends one or more reports to the third-party entity 810 including the analyzed data associated with the one or more AUEs 804. Additionally, in some cases, as shown at 828, the NWDAF entity 806 may also send the analyzed data associated with the one or more AUEs 804 to the RAN entity 802 and / or one or more other network entities, such as the AMF entity and / or 0AM entity.Example Operations of an NWDAF Entity

[0137] FIG. 9 shows an example of a method 900 of communication by a network data analytics function (NWDAF) entity, such as the NWDAF 193 of FIG. IB, the NWDAF 793 of FIG. 7, and / or the NWDAF entity 806 of FIG. 8.

[0138] Method 900 begins at step 905 with sending, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs). In some cases, the operations of this step refer to, or may be performed by, circuitry for sending and / or code for sending as described with reference to FIG. 11.

[0139] Method 900 then proceeds to step 910 with receiving, from the RAN, the data associated with the one or more AUEs. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 11.

[0140] Method 900 then proceeds to step 915 with analyzing the data. In some cases, the operations of this step refer to, or may be performed by, circuitry for analyzing and / or code for analyzing as described with reference to FIG. 11.

[0141] Method 900 then proceeds to step 920 with sending one or more reports including the analyzed data to a third-party entity. In some cases, the operations of thisstep refer to, or may be performed by, circuitry for sending and / or code for sending as described with reference to FIG. 11.

[0142] In some aspects, the method 900 further includes receiving a data reporting configuration for the one or more AUEs from a third-party entity, wherein sending the reporting request is based on the data reporting configuration. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 11.

[0143] In some aspects, the reporting request is sent to the RAN using an NWDAF - to-RAN logical connection established between the NWDAF entity and the RAN; and the data associated with the one or more AUEs is received from the RAN using the NWDAF -to-R AN logical connection.

[0144] In some aspects, the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs.

[0145] In some aspects, the data received from network entity of the RAN includes one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

[0146] In some aspects, the one or more first identifiers comprise one or more aerial identifiers.

[0147] In some aspects, the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CAA specific session ID; or a combination thereof.

[0148] In some aspects, the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; and each 3 GPP-based identifier of the one or more 3GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs.

[0149] In some aspects, the method 900 further includes sending the one or more 3 GPP -based identifiers to an unmanned aerial system (UAS) network function (NF) entity. In some cases, the operations of this step refer to, or may be performed by, circuitry for sending and / or code for sending as described with reference to FIG. 11.

[0150] In some aspects, the method 900 further includes receiving, from the UAS NF entity based on 3 GPP -based identifier, one or more second identifiers, wherein each different second identifier of the one or more second identifiers identifies a different respective AUE of the one or more specific AUEs. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 11.

[0151] In some aspects, the one or more second identifiers are each respectively an aerial identifier that corresponds to a respective 3 GPP-based identifier of the one or more 3GPP -based identifiers sent to the UAS NF entity.

[0152] In some aspects, the one or more 3 GPP -based identifiers are sent and the one or more second identifiers are received using a logical connection established between the NWDAF entity and the UAS NF entity.

[0153] In some aspects, the reporting request is for the data associated with a nonspecific group of AUEs.

[0154] In some aspects, the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on.

[0155] In some aspects, one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN; radio resource management (RRM) parameters maintained between the one or more AUEs and the RAN; status information associated with the one or more AUEs; preferred RANs of the one or more AUEs; or RANs observed on respective scan lists of the one or more AUEs.

[0156] In some aspects, the one or more types of data include the mobility information associated with the one or more AUEs; and the mobility information includes at least one of: flight paths of the one or more AUEs through an area of the RAN; or a duration of flight paths of the one or more AUEs.

[0157] In some aspects, analyzing the data comprises processing the data with a machine learning (ML) model trained to produce one or more outputs based on the data;and the analyzed data sent to the third-party entity in the one or more reports includes the one or more outputs.

[0158] In some aspects, the one or more outputs include at least one of: an indication of one or more cells of the RAN that need an AUE-based radio frequency (RF) performance retuning; an indication of frequent flight patterns of the one or more AUEs associated with the RAN over a period of time; a classification of tracking area identifiers (TAIs) over time; or a prediction of resource usage in the RAN associated with the one or more AUEs for a period of time.

[0159] In some aspects, the one or more outputs include at least one of: an indication of abnormal AUE patterns associated with the one or more AUEs; an indication of a denial-of-service attack on the one or more AUEs; an indication of a predicted behavior for the one or more AUEs in real-time; or an indication of optimal radio frequency (RF) coverage zones for flight paths associated with the one or more AUEs.

[0160] In some aspects, the NWDAF entity is part of a core network associated with the RAN.

[0161] In one aspect, method 900, or any aspect related to it, may be performed by an apparatus, such as communications device 1100 of FIG. 11, which includes various components operable, configured, or adapted to perform the method 900. Communications device 1100 is described below in further detail.

[0162] Note that FIG. 9 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Operations of a RAN Entity

[0163] FIG. 10 shows an example of a method 1000 of communication by a radio access network (RAN), such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

[0164] Method 1000 begins at step 1005 with receiving, from a network data analytics function (NWDAF) a reporting request for data associated with one or more aerial user equipments (AUEs). In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 12

[0165] Method 1000 then proceeds to step 1010 with collecting the data associated with the one or more AUEs based on the reporting request. In some cases, the operations of this step refer to, or may be performed by, circuitry for collecting and / or code for collecting as described with reference to FIG. 12.

[0166] Method 1000 then proceeds to step 1015 with sending, to the NWDAF entity, the data associated with the one or more AUEs. In some cases, the operations of this step refer to, or may be performed by, circuitry for sending and / or code for sending as described with reference to FIG. 12.

[0167] In some aspects, the reporting request is based on a data reporting configuration associated with a third-party entity.

[0168] In some aspects, the reporting request is received from the NWDAF using an NWDAF-to-RAN logical connection established between the NWDAF entity and the RAN; and the data associated with the one or more AUEs is sent to the NWDAF entity using the NWDAF-to-RAN logical connection.

[0169] In some aspects, the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs; and the collecting the data associated with the one or more AUEs comprises collecting the data for the one or more specific AUEs.

[0170] In some aspects, the data received sent to the NWDAF entity includes a one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

[0171] In some aspects, the one or more first identifiers comprise one or more aerial identifiers.

[0172] In some aspects, the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CSS specific session ID; or a combination thereof.

[0173] In some aspects, the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; each different 3 GPP -based identifier of the one or more 3GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs; and each different 3 GPP -based identifier of the one or more 3 GPP-based identifiers respectivelycorresponds to a different second identifier of one or more second identifiers associated to the different respective AUE of the one or more specific AUEs.

[0174] In some aspects, each different second identifier of the one or more second identifiers is each respectively a different aerial identifier.

[0175] In some aspects, the reporting request is for the data associated with a nonspecific group of AUEs; and the collecting the data associated with the one or more AUEs comprises collecting the data for the non-specific group of AUEs.

[0176] In some aspects, the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on; and the collecting the data associated with the one or more AUEs comprises collecting the specified one or more types of data associated with the one or more AUEs.

[0177] In some aspects, one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN.

[0178] In some aspects, the one or more types of data include the mobility information associated with the one or more AUEs; and the mobility information includes at least one of: flight paths of the one or more AUEs through an area of the RAN; or a duration of flight paths of the one or more AUEs.

[0179] In one aspect, method 1000, or any aspect related to it, may be performed by an apparatus, such as communications device 1200 of FIG. 12, which includes various components operable, configured, or adapted to perform the method 1000. Communications device 1200 is described below in further detail.

[0180] Note that FIG. 10 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Communications Devices

[0181] FIG. 11 depicts aspects of an example communications device 1100. In some aspects, communications device 1100 is a network data analytics function (NWDAF) entity, such as the NWDAF 193 of FIG. IB, the NWDAF 793 of FIG. 7, and / or the NWDAF entity 806 of FIG. 8.

[0182] The communications device 1100 includes a processing system 1105 coupled to the transceiver 1155 (e.g., a transmitter and / or a receiver) and / or a network interface 1165. The transceiver 1155 is configured to transmit and receive signals for the communications device 1100 via the antenna 1160, such as the various signals as described herein. The network interface 1165 is configured to obtain and send signals for the communications device 1100 via communication link(s), such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The processing system 1105 may be configured to perform processing functions for the communications device 1100, including processing signals received and / or to be transmitted by the communications device 1100.

[0183] The processing system 1105 includes one or more processors 1110. In various aspects, one or more processors 1110 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors l l lO are coupled to a computer-readable medium / memory 1130 via abus 1150. In certain aspects, the computer-readable medium / memory 1130 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1110, cause the one or more processors 1110 to perform the method 900 described with respect to FIG. 9, or any aspect related to it. Note that reference to a processor of communications device 1100 performing a function may include one or more processors 1110 of communications device 1100 performing that function.

[0184] In the depicted example, the computer-readable medium / memory 1130 stores code (e.g., executable instructions), such as code for sending 1135, code for receiving 1140, and code for analyzing 1145. Processing of the code for sending 1135, code for receiving 1140, and code for analyzing 1145 may cause the communications device 1100 to perform the method 900 described with respect to FIG. 9, or any aspect related to it.

[0185] The one or more processors 1110 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1130, including circuitry such as circuitry for sending 1115, circuitry for receiving 1120, and circuitry for analyzing 1125. Processing with circuitry for sending 1115, circuitry for receiving 1120, and circuitry for analyzing 1125 may cause the communications device 1100 to perform the method 900 described with respect to FIG. 9, or any aspect related to it.

[0186] Various components of the communications device 1100 may provide means for performing the method 900 described with respect to FIG. 9, or any aspect related to it. Means for transmitting, sending or outputting for transmission may include the transceiver 1155 and the antenna 1160 of the communications device 1100 in FIG. 11. Means for receiving or obtaining may include the transceiver 1155 and the antenna 1160 of the communications device 1100 in FIG. 11.

[0187] FIG. 12 depicts aspects of an example communications device 1200. In some aspects, communications device 1200 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

[0188] The communications device 1200 includes a processing system 1205 coupled to the transceiver 1255 (e.g., a transmitter and / or a receiver) and / or a network interface 1265. The transceiver 1255 is configured to transmit and receive signals for the communications device 1200 via the antenna 1260, such as the various signals as described herein. The network interface 1265 is configured to obtain and send signals for the communications device 1200 via communication link(s), such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The processing system 1205 may be configured to perform processing functions for the communications device 1200, including processing signals received and / or to be transmitted by the communications device 1200.

[0189] The processing system 1205 includes one or more processors 1210. In various aspects, one or more processors 1210 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 1210 are coupled to a computer-readable medium / memory 1230 via a bus 1250. In certain aspects, the computer-readable medium / memory 1230 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1210,cause the one or more processors 1210 to perform the method 1000 described with respect to FIG. 10, or any aspect related to it. Note that reference to a processor of communications device 1200 performing a function may include one or more processors 1210 of communications device 1200 performing that function.

[0190] In the depicted example, the computer-readable medium / memory 1230 stores code (e.g., executable instructions), such as code for receiving 1235, code for collecting 1240, and code for sending 1245. Processing of the code for receiving 1235, code for collecting 1240, and code for sending 1245 may cause the communications device 1200 to perform the method 1000 described with respect to FIG. 10, or any aspect related to it.

[0191] The one or more processors 1210 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1230, including circuitry such as circuitry for receiving 1215, circuitry for collecting 1220, and circuitry for sending 1225. Processing with circuitry for receiving 1215, circuitry for collecting 1220, and circuitry for sending 1225 may cause the communications device 1200 to perform the method 1000 described with respect to FIG. 10, or any aspect related to it.

[0192] Various components of the communications device 1200 may provide means for performing the method 1000 described with respect to FIG. 10, or any aspect related to it. Means for transmitting, sending or outputting for transmission may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or the transceiver 1255 and the antenna 1260 of the communications device 1200 in FIG. 12. Means for receiving or obtaining may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or the transceiver 1255 and the antenna 1260 of the communications device 1200 in FIG. 12.Example Clauses

[0193] Implementation examples are described in the following numbered clauses:

[0194] Clause 1 : A method for communication by a network data analytics function (NWDAF) entity, comprising: sending, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs); receiving, from the RAN, the data associated with the one or more AUEs; analyzing the data; and sending one or more reports including the analyzed data to a third-party entity.

[0195] Clause 2: The method of Clause 1, further comprising receiving a data reporting configuration for the one or more AUEs from a third-party entity, wherein sending the reporting request is based on the data reporting configuration.

[0196] Clause 3: The method of any one of Clauses 1-2, wherein: the reporting request is sent to the RAN using an NWDAF-to-RAN logical connection established between the NWDAF entity and the RAN; and the data associated with the one or more AUEs is received from the RAN using the NWDAF-to-RAN logical connection .

[0197] Clause 4: The method of any one of Clauses 1-3, wherein the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs.

[0198] Clause 5: The method of Clause 4, wherein: the data received from network entity of the RAN includes one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

[0199] Clause 6: The method of Clause 5, wherein the one or more first identifiers comprise one or more aerial identifiers.

[0200] Clause 7: The method of Clause 6, wherein the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CAA specific session ID; or a combination thereof.

[0201] Clause 8: The method of Clause 5, wherein: the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; and each 3GPP-based identifier of the one or more 3GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs.

[0202] Clause 9: The method of Clause 8, further comprising: sending the one or more 3 GPP -based identifiers to an unmanned aerial system (UAS) network function (NF) entity; and receiving, from the UAS NF entity based on 3GPP -based identifier, one or more second identifiers, wherein each different second identifier of the one or more second identifiers identifies a different respective AUE of the one or more specific AUEs.

[0203] Clause 10: The method of Clause 9, wherein the one or more second identifiers are each respectively an aerial identifier that corresponds to a respective 3 GPP -based identifier of the one or more 3GPP-based identifiers sent to the UAS NF entity.

[0204] Clause 11 : The method of Clause 9, wherein the one or more 3GPP -based identifiers are sent and the one or more second identifiers are received using a logical connection established between the NWDAF entity and the UAS NF entity.

[0205] Clause 12: The method of any one of Clauses 1-11, wherein the reporting request is for the data associated with a non-specific group of AUEs.

[0206] Clause 13: The method of any one of Clauses 1-12, wherein the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on.

[0207] Clause 14: The method of Clause 13, wherein one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN; radio resource management (RRM) parameters maintained between the one or more AUEs and the RAN; status information associated with the one or more AUEs; preferred RANs of the one or more AUEs; or RANs observed on respective scan lists of the one or more AUEs.

[0208] Clause 15: The method of Clause 14, wherein: the one or more types of data include the mobility information associated with the one or more AUEs; and the mobility information includes at least one of: flight paths of the one or more AUEs through an area of the RAN; or a duration of flight paths of the one or more AUEs.

[0209] Clause 16: The method of any one of Clauses 1-15, wherein: analyzing the data comprises processing the data with a machine learning (ML) model trained to produce one or more outputs based on the data; and the analyzed data sent to the third- party entity in the one or more reports includes the one or more outputs.

[0210] Clause 17: The method of Clause 16, wherein the one or more outputs include at least one of: an indication of one or more cells of the RAN that need an AUE-based radio frequency (RF) performance retuning; an indication of frequent flight patterns of the one or more AUEs associated with the RAN over a period of time; a classification of tracking area identifiers (TAIs) over time; or a prediction of resource usage in the RAN associated with the one or more AUEs for a period of time.

[0211] Clause 18: The method of Clause 16, wherein the one or more outputs include at least one of: an indication of abnormal AUE patterns associated with the one or more AUEs; an indication of a denial-of-service attack on the one or more AUEs; an indication of a predicted behavior for the one or more AUEs in real-time; or an indication of optimal radio frequency (RF) coverage zones for flight paths associated with the one or more AUEs.

[0212] Clause 19: The method of any one of Clauses 1-18, wherein the NWDAF entity is part of a core network associated with the RAN.

[0213] Clause 20: A method for communication by a radio access network (RAN), comprising: receiving, from a network data analytics function (NWDAF) a reporting request for data associated with one or more aerial user equipments (AUEs); collecting the data associated with the one or more AUEs based on the reporting request; and sending, to the NWDAF entity, the data associated with the one or more AUEs.

[0214] Clause 21 : The method of Clause 20, wherein the reporting request is based on a data reporting configuration associated with a third-party entity.

[0215] Clause 22: The method of any one of Clauses 20-21, wherein: the reporting request is received from the NWDAF using an NWDAF-to-RAN logical connection established between the NWDAF entity and the RAN; and the data associated with the one or more AUEs is sent to the NWDAF entity using the NWDAF-to-RAN logical connection.

[0216] Clause 23: The method of any one of Clauses 20-22, wherein: the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs; and the collecting the data associated with the one or more AUEs comprises collecting the data for the one or more specific AUEs.

[0217] Clause 24: The method of Clause 23, wherein: the data received sent to the NWDAF entity includes a one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

[0218] Clause 25: The method of Clause 24, wherein the one or more first identifiers comprise one or more aerial identifiers.

[0219] Clause 26: The method of Clause 25, wherein the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CSS specific session ID; or a combination thereof.

[0220] Clause 27: The method of Clause 24, wherein: the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; each different 3GPP -based identifier of the one or more 3GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs; and each different 3 GPP -based identifier of the one or more 3 GPP -based identifiers respectively corresponds to a different second identifier of one or more second identifiers associated to the different respective AUE of the one or more specific AUEs.

[0221] Clause 28: The method of Clause 27, wherein each different second identifier of the one or more second identifiers is each respectively a different aerial identifier.

[0222] Clause 29: The method of any one of Clauses 20-28, wherein: the reporting request is for the data associated with a non-specific group of AUEs; and the collecting the data associated with the one or more AUEs comprises collecting the data for the nonspecific group of AUEs.

[0223] Clause 30: The method of any one of Clauses 20-29, wherein: the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on; and the collecting the data associated with the one or more AUEs comprises collecting the specified one or more types of data associated with the one or more AUEs.

[0224] Clause 31 : The method of Clause 30, wherein one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN.

[0225] Clause 32: The method of Clause 31, wherein: the one or more types of data include the mobility information associated with the one or more AUEs; and the mobility information includes at least one of: flight paths of the one or more AUEs through an area of the RAN; or a duration of flight paths of the one or more AUEs.

[0226] Clause 33: An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any one of Clauses 1-32.

[0227] Clause 34: An apparatus, comprising means for performing a method in accordance with any one of Clauses 1-32.

[0228] Clause 35: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any one of Clauses 1-32.

[0229] Clause 36: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-32.Additional Considerations

[0230] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0231] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0232] As used herein, “a processor,” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory,” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.

[0233] Means for sending, means for receiving, means for analyzing, and means for collecting may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 11, and FIG. 12.

[0234] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0235] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receivinginformation), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0236] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.

[0237] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for”. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

WHAT IS CLAIMED IS:

1. An apparatus for communication by a network data analytics function (NWDAF) entity, comprising: one or more processors configured to execute instructions stored on one or more memories and to cause the NWDAF entity to: send, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs); receive, from the RAN, the data associated with the one or more AUEs; analyze the data; and send one or more reports including the analyzed data to a third-party entity.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the NWDAF entity to receive a data reporting configuration for the one or more AUEs from a third-party entity, wherein sending the reporting request is based on the data reporting configuration.

3. The apparatus of claim 1, wherein: the reporting request is sent to the RAN using an NWDAF-to-RAN logical connection established between the NWDAF entity and the RAN; and the one or more processors are configured to cause the NWDAF entity to receive the data associated with the one or more AUEs from the RAN using the NWDAF-to-RAN logical connection .

4. The apparatus of claim 1, wherein the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs.

5. The apparatus of claim 4, wherein: the data received from network entity of the RAN includes one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

6. The apparatus of claim 5, wherein the one or more first identifiers comprise one or more aerial identifiers.

7. The apparatus of claim 6, wherein the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CAA specific session ID; or a combination thereof.

8. The apparatus of claim 5, wherein: the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; and each 3GPP -based identifier of the one or more 3GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs.

9. The apparatus of claim 8, wherein the one or more processors are further configured to cause the NWDAF entity to: send the one or more 3 GPP -based identifiers to an unmanned aerial system (UAS) network function (NF) entity; and receive, from the UAS NF entity based on 3 GPP -based identifier, one or more second identifiers, wherein each different second identifier of the one or more second identifiers identifies a different respective AUE of the one or more specific AUEs.

10. The apparatus of claim 9, wherein the one or more second identifiers are each respectively an aerial identifier that corresponds to a respective 3 GPP -based identifier of the one or more 3GPP-based identifiers sent to the UAS NF entity.

11. The apparatus of claim 9, wherein the one or more 3 GPP -based identifiers are sent and the one or more second identifiers are received using a logical connection established between the NWDAF entity and the UAS NF entity.

12. The apparatus of claim 1, wherein the reporting request is for the data associated with a non-specific group of AUEs.

13. The apparatus of claim 1, wherein the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on.

14. The apparatus of claim 13, wherein one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN; radio resource management (RRM) parameters maintained between the one or more AUEs and the RAN; status information associated with the one or more AUEs; preferred RANs of the one or more AUEs; orRANs observed on respective scan lists of the one or more AUEs.

15. The apparatus of claim 14, wherein: the one or more types of data include the mobility information associated with the one or more AUEs; and the mobility information includes at least one of: flight paths of the one or more AUEs through an area of the RAN; or a duration of flight paths of the one or more AUEs.

16. The apparatus of claim 1, wherein: in order to analyze the data, the one or more processors are configured to cause the NWDAF entity to process the data with a machine learning (ML) model trained to produce one or more outputs based on the data; and in order to send the one or more reports including the analyzed data, the one or more processors are configured to cause the NWDAF entity to send the one or more outputs in the one or more reports.

17. The apparatus of claim 16, wherein the one or more outputs include at least one of: an indication of one or more cells of the RAN that need an AUE-based radio frequency (RF) performance retuning; an indication of frequent flight patterns of the one or more AUEs associated with the RAN over a period of time; a classification of tracking area identifiers (TAIs) over time; or a prediction of resource usage in the RAN associated with the one or more AUEs for a period of time.

18. The apparatus of claim 16, wherein the one or more outputs include at least one of: an indication of abnormal AUE patterns associated with the one or more AUEs; an indication of a denial-of-service attack on the one or more AUEs; an indication of a predicted behavior for the one or more AUEs in real-time; or an indication of optimal radio frequency (RF) coverage zones for flight paths associated with the one or more AUEs.

19. An apparatus for communication by a radio access network (RAN), comprising: one or more processors configured to execute instructions stored on one or more memories and to cause the RAN to: receive, from a network data analytics function (NWDAF) a reporting request for data associated with one or more aerial user equipments (AUEs); collect the data associated with the one or more AUEs based on the reporting request; and send, to the NWDAF entity, the data associated with the one or more AUEs.

20. The apparatus of claim 19, wherein the reporting request is based on a data reporting configuration associated with a third-party entity.

21. The apparatus of claim 19, wherein: the reporting request is received from the NWDAF using an NWDAF-to-RAN logical connection established between the NWDAF entity and the RAN; andthe data associated with the one or more AUEs is sent to the NWDAF entity using the NWDAF-to-RAN logical connection.

22. The apparatus of claim 19, wherein: the reporting request is for the data associated with one or more specific AUEs of the one or more AUEs; and in order to collect the data associated with the one or more AUEs, the one or more processors are configured to cause the RAN to collect the data for the one or more specific AUEs.

23. The apparatus of claim 22, wherein: the data received sent to the NWDAF entity includes a one or more first identifiers; and each different first identifier of the one or more first identifiers identifies a different respective AUE of the one or more specific AUEs.

24. The apparatus of claim 23, wherein: the one or more first identifiers comprise one or more aerial identifiers; and the one or more aerial identifiers are each respectively one of: a civil aviation administration (CAA)-level unmanned aerial vehicle (UAV) identifier; a CSS specific session ID; or a combination thereof.

25. The apparatus of claim 23, wherein: the one or more first identifiers comprise one or more third generation partnership project (3GPP)-based identifiers; each different 3 GPP-based identifier of the one or more 3 GPP -based identifiers is available in the RAN and associated to a different respective AUE of the one or more specific AUEs; each different 3 GPP-based identifier of the one or more 3 GPP -based identifiers respectively corresponds to a different second identifier of one or more second identifiers associated to the different respective AUE of the one or more specific AUEs; andeach different second identifier of the one or more second identifiers is each respectively a different aerial identifier.

26. The apparatus of claim 19, wherein: the reporting request is for the data associated with a non-specific group of AUEs; and in order to collect the data associated with the one or more AUEs, the one or more processors are configured to cause the RAN to collect the data for the non-specific group of AUEs.

27. The apparatus of claim 19, wherein: the reporting request includes one or more parameters specifying one or more types of data associated with the one or more AUEs to be collected and reported on; and in order to collect the data associated with the one or more AUEs, the one or more processors are configured to cause the RAN to collect the specified one or more types of data associated with the one or more AUEs.

28. The apparatus of claim 27, wherein one or more types of data specified by the one or more parameters include at least one of: mobility information associated with the one or more AUEs including at least one of flight paths of the one or more AUEs through an area of the RAN or a duration of flight paths of the one or more AUEs; location information associated with the one or more AUEs; or quality of service information associated with one or more radio links of the one or more AUEs established with the RAN.

29. A method for communication by a network data analytics function (NWDAF) entity, comprising: sending, to a radio access network (RAN), a reporting request for data associated with one or more aerial user equipments (AUEs); receiving, from the RAN, the data associated with the one or more AUEs; analyzing the data; and sending one or more reports including the analyzed data to a third-party entity.

30. A method for communication by a radio access network (RAN), comprising: receiving, from a network data analytics function (NWDAF) a reporting request for data associated with one or more aerial user equipments (AUEs); collecting the data associated with the one or more AUEs based on the reporting request; and sending, to the NWDAF entity, the data associated with the one or more AUEs.

Images