Enhanced reporting for user equipment

Abstract

Some examples of the technologies described herein relate to methods, systems, devices, and apparatuses that support reporting enhancements for user equipment (UE). An air-to-air UE can be configured to collect data based on air-to-air UE-specific events or based on a height-specific area range. For example, data collection can be triggered using air-to-air UE events or height-specific area ranges. Data can be collected when collection rules are met. In some methods, the air-to-air UE can collect data for a height-specific Automatic Neighbor Relationship (ANR) table. For example, a network entity can configure the UE to report the Cell Global Identifier (CGI) of cells detected at or within a specific altitude range. The air-to-air UE can use one or more data collection triggers to generate a Successful Handover Report (SHR) or a Successful Primary / Secondary Cell (PSCell) Report (SPR).

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 510,455, filed November 15, 2023, entitled “Reporting Enhancements for User Equipment”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following content relates to wireless communications, including reporting enhancements for user equipment. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] Some examples of the technologies described herein relate to methods, systems, devices, and apparatuses that support reporting enhancements for User Equipment (UE). An over-the-air UE can be configured to collect data based on over-the-air UE-specific events or based on a height-specific area range. For example, data collection can be triggered using over-the-air UE events or height-specific area ranges to enhance coverage and capacity at a specific altitude. Data (e.g., data for reporting, recorded Minimum Drive Test Time (MDT) data, etc.) can be collected when collection rules (e.g., altitude conditions), signal quality conditions, or when the UE is outside a restricted area. In some methods, the over-the-air UE can collect data for a height-specific Automatic Neighbor Relationship (ANR) table. For example, a network entity can configure the UE to report the Cell Global Identifier (CGI) of cells detected at or within an altitude range at a specific altitude. Additional data types can be provided in the report, such as a UE type indication with UE altitude or UE characteristics in an Ad Hoc Network (SON) report. For example, an over-the-air UE can use one or more data collection triggers (e.g., when the UE's altitude meets an altitude threshold) to generate a Successful Handover Report (SHR) or a Successful Primary / Secondary Cell Change Report (SPR). Some reports (e.g., random access reports, radio link failure (RLF) reports, SHR, SPR, etc.) can be enhanced to include data indicating UE altitude, UE characteristics (e.g., antenna type, antenna orientation, antenna installation) or the density of airborne UEs detected near the UE at the time of measurement.

[0006] A method for wireless communication by a UE is described. The method may include: receiving configuration information from a network entity for transmitting a report of data collected by the UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and transmitting the report to the network entity according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information of one or more network nodes in response to the satisfaction of the collection rules.

[0007] An apparatus for wireless communication is described. The apparatus may include a memory, a transceiver, and at least one processor of a UE, the at least one processor being coupled to the memory and the transceiver. The at least one processor may be configured to cause the UE to: receive configuration information from a network entity for transmitting a report of UE-collected data associated with relationship information and collection rules related to one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and transmit the report to the network entity according to the configuration information, wherein the report indicates UE-collected data associated with relationship information of one or more network nodes in response to the satisfaction of collection rules.

[0008] Another apparatus for wireless communication is described. The apparatus may include: components for receiving configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules related to one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and components for sending the report to the network entity according to the configuration information, wherein the report indicates data collected by the UE associated with relationship information of one or more network nodes in response to the satisfaction of the collection rules.

[0009] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: receive configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and send the report to the network entity according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information for one or more network nodes in response to the satisfaction of the collection rules.

[0010] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the altitude conditions of the UE include at least one altitude threshold for the UE's altitude, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the UE's altitude satisfying at least one altitude threshold.

[0011] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving configuration information may include operations, features, components, or instructions for receiving information indicating an area range based on altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to satisfaction of the area range.

[0012] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the configuration information also includes one or more cell indicators, and the data collected by the UE includes data collected by the UE for one or more cells associated with one or more cell indicators.

[0013] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the altitude conditions of the UE include at least one altitude threshold of the UE's altitude, and the methods, apparatuses, and nontransitory computer-readable media may also include operations, features, components, or instructions for collecting first data associated with one or more first cells in one or more cells in response to the satisfaction of a first threshold among at least one altitude threshold.

[0014] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the collection rules may also be based on signal quality conditions, altitude conditions including at least one altitude threshold of the UE's altitude, and the data collected by the UE includes data collected by the UE in response to the satisfaction of signal quality conditions and the UE's altitude satisfying at least one altitude threshold.

[0015] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more reference signals corresponding to one or more cells, wherein the satisfaction of signal quality conditions includes one or more metrics of the one or more reference signals satisfying a signal quality threshold.

[0016] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting UE entry into a restricted area, wherein the UE avoids collecting data when in the restricted area, and collecting data collected by the UE when outside the restricted area.

[0017] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the data collected by the UE includes first data indicating entry into a restricted area, second data indicating exit from a restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0018] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving configuration information may include operations, features, components, or instructions for: receiving cell report configuration information that instructs the UE to collect cell data associated with one or more cells in response to the satisfaction of altitude conditions, and sending the report includes sending a cell report that includes cell data associated with one or more cells.

[0019] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, cell data may be included in an ANR table.

[0020] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

[0021] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, the report may be a Random Access Report (RA report), a Connection Establishment Failure (CEF) report, an RLF report, an SHR, an SPR, or a report that includes secondary cell group (SCG) failure information.

[0022] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the data collected by the UE is recorded data, and the methods, apparatuses, and nontransitory computer-readable media may also include operations, features, components, or instructions for: sending an availability indication to a network entity indicating that the recorded data may be available; and receiving a request for the recorded data based on the availability indication, wherein sending the report to the network entity may be based on receiving a request for the recorded data.

[0023] A method for wireless communication by a network entity is described. The method may include: sending configuration information to a UE for sending a report of data collected by the UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information of one or more network nodes in response to the satisfaction of the collection rules.

[0024] An apparatus for wireless communication is described. The apparatus may include: a memory and at least one processor of a network entity coupled to the memory. The at least one processor may be configured to cause the network entity to: send configuration information to a UE for sending a report of data collected by the UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and receive the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with relationship information of one or more network nodes in response to the satisfaction of the collection rules.

[0025] Another apparatus for wireless communication is described. A network entity may include: components for sending configuration information to a UE for sending a report of data collected by the UE associated with relationship information and collection rules related to one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and components for receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with relationship information and one or more network nodes in response to the satisfaction of the collection rules.

[0026] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: send configuration information to a UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions; and receive the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information for one or more network nodes in response to the satisfaction of the collection rules.

[0027] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the altitude conditions of the UE include at least one altitude threshold for the UE's altitude, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the UE's altitude satisfying at least one altitude threshold.

[0028] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting configuration information may include operations, features, components, or instructions for transmitting information indicating an area range that may be based on altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the area range.

[0029] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the configuration information also includes one or more cell indicators, and the data collected by the UE includes data collected by the UE for one or more cells associated with one or more cell indicators.

[0030] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the altitude conditions of the UE include at least one altitude threshold for the altitude of the UE.

[0031] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the collection rules may also be based on signal quality conditions, altitude conditions including at least one altitude threshold of the UE's altitude, and the data collected by the UE includes data collected by the UE in response to the satisfaction of signal quality conditions and the UE's altitude satisfying at least one altitude threshold.

[0032] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving data indicating one or more reference signals corresponding to one or more cells, wherein the data indicating one or more reference signals may be collected by the UE in response to the satisfaction of a signal quality condition, the satisfaction of which includes one or more metrics of one or more reference signals satisfying a signal quality threshold.

[0033] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the data collected by the UE lacks data associated with the restricted area and includes data associated with one or more areas outside the restricted area.

[0034] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the data collected by the UE includes first data indicating entry into a restricted area, second data indicating exit from a restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0035] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting configuration information may include operations, features, components, or instructions for: transmitting cell report configuration information that instructs the UE to collect cell data associated with one or more cells in response to the satisfaction of altitude conditions, and receiving the report includes receiving a cell report that includes cell data associated with one or more cells.

[0036] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, cell data may be included in an ANR table.

[0037] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, receiving the report may include operations, features, components or instructions for receiving UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data or any combination thereof.

[0038] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, the report may be an RA report, a CEF report, an RLF report, an SHR, an SPR, or a report that includes SCG failure information.

[0039] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the data collected by the UE is recorded data, and the methods, apparatuses, and nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving from the UE an availability indication indicating that the recorded data may be available; and sending a request for the recorded data based on the availability indication, wherein receiving the report from the UE may be based on sending the request for the recorded data. Attached Figure Description

[0040] Figure 1 Examples of wireless communication systems that support reporting enhancements for user equipment (UE) according to one or more aspects of this disclosure are shown.

[0041] Figure 2An example of a wireless communication system that supports reporting enhancements for a UE according to one or more aspects of this disclosure is shown.

[0042] Figure 3 An example of a wireless communication system for altitude-based reporting that supports reporting enhancements for a UE according to one or more aspects of this disclosure is shown.

[0043] Figure 4 An example of a wireless communication system for over-the-air UE data collection that supports enhanced reporting for the UE according to one or more aspects of this disclosure is shown.

[0044] Figure 5 An example of a process flow supporting enhanced reporting for a UE in accordance with one or more aspects of this disclosure is shown.

[0045] Figure 6 and Figure 7 A block diagram of an apparatus supporting enhanced reporting for a UE, according to one or more aspects of this disclosure, is shown.

[0046] Figure 8 A block diagram is shown that supports enhanced reporting for a UE according to one or more aspects of this disclosure.

[0047] Figure 9 A diagram is shown of a system including a device that supports reporting enhancements for a UE, according to one or more aspects of this disclosure.

[0048] Figure 10 and Figure 11 A block diagram of an apparatus supporting enhanced reporting for a UE, according to one or more aspects of this disclosure, is shown.

[0049] Figure 12 A block diagram is shown that supports enhanced reporting for a UE according to one or more aspects of this disclosure.

[0050] Figure 13 A diagram is shown of a system including a device that supports reporting enhancements for a UE, according to one or more aspects of this disclosure.

[0051] Figures 14 to 17 A flowchart illustrating a method for supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. Detailed Implementation

[0052] Some wireless communication systems support airborne user equipment (UEs), which can be devices capable of flight or maneuvering in the air. Such airborne UEs may be referred to as unmanned aerial vehicles (UAVs) or drones. In some cases, dedicated spectrum may be available for airborne UEs (e.g., in a UAV-specific cellular network). As a complement or alternative to the availability of dedicated spectrum for a UAV-specific network, airborne UEs may operate in conventional cellular spectrum (e.g., using 4G or 5G communication). In some cases, for airborne UEs in the air, the signal from network entities may be less strong compared to UEs at the same location at ground level. For example, network entities configured for ground communication may have antenna panels that point to the ground level and therefore do not specifically point to higher elevations above ground level. In such cases, the main lobe of the antenna panel may point to a relatively low elevation or height, but side lobes may be generated at higher elevations or heights. However, such side lobes (and portions of the main lobe) may have relatively high signal strength variability at different altitudes and at various locations of the network entity relative to such different altitudes. This variable signal strength may result in less reliable or intermittent coverage for airborne UEs.

[0053] Network operators can use coverage maps for network management. Coverage maps can be generated based on measurements from different locations within the coverage area of ​​network entities. Network operators can use these measurements to identify coverage holes, weak coverage, pilot pollution, overshoot coverage, and provide cell boundary mapping. In some methods, a minimized drive test (MDT) procedure can be used to generate measurements for the coverage map. In these procedures, the UE records cell measurements of the serving cell and neighboring cells while in idle mode and reports the cell measurements to the serving cell. However, such MDT procedures are designed for ground-based UEs and may not be suitable for UAVs or airborne UEs because cell coverage varies significantly with the UE's altitude. Furthermore, having airborne UEs provide MDT reports based on measurements obtained while in the air may lead to inconsistencies between measurements provided by UEs on the ground (e.g., due to differences in signal strength from the main lobe and side lobes with altitude / elevation).

[0054] In some methods, MDT reports (e.g., real-time and recorded MDT reports) may indicate characteristics of the UE type (e.g., UE types with directional antennas, UE types with vehicle-mounted antennas, etc.), altitude information (e.g., for creating altitude-specific coverage maps), detected airborne UE density, or indications about measurements taken of the UE in the air. Some methods may provide limited data (e.g., signal strength measurements) or may lack airborne UE events for data collection.

[0055] Some examples of the technologies described herein relate to methods, systems, devices, and apparatuses that support enhanced reporting for UEs. An airborne UE can be configured to collect data (e.g., for reporting) based on airborne UE-specific events or based on a height-specific area range. For example, ad hoc network (SON) or medium-term reporting (MDT) can be enhanced for airborne UEs. In some methods, the collection of recorded MDT data can be triggered using airborne UE events or height-specific area ranges to enhance coverage and capacity at a specific altitude. MDT data can be collected when altitude conditions are met, when signal quality conditions are met, or when the UE is outside a restricted area. In some methods, an airborne UE can collect data for a height-specific automatic neighbor relationship (ANR) table. For example, a network entity can configure the UE to report the cell global identifier (CGI) of cells detected at or within an altitude range at a specific altitude. Additional data types can be provided in the reports, such as UE type indications in SON reports with UE altitude or UE characteristics. For example, an airborne UE can use one or more data collection triggers (e.g., when the UE's altitude meets an altitude threshold) to generate a Successful Handover Report (SHR) or a Successful Primary / Secondary Cell Change Report (SPR). Some reports (e.g., random access reports, radio link failure (RLF) reports, SHR, SPR, etc.) can be enhanced to include data indicating UE altitude, UE characteristics (e.g., antenna type, antenna orientation, antenna installation) or the density of airborne UEs detected near the UE at the time of measurement.

[0056] Various aspects of this disclosure provide techniques for enhancing reporting by over-the-air UEs, which can benefit communication efficiency and reliability, such as identifying areas where cell changes (e.g., handover) are more likely to succeed, identifying areas where radio link failures are more likely to occur, or providing SON data that varies according to altitude, to name just a few.

[0057] The aspects of this disclosure are initially described in the context of a wireless communication system. These aspects are further illustrated in the context of process flowcharts. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to reporting enhancements for a UE.

[0058] Figure 1Examples of wireless communication systems 100 supporting reporting enhancements for UEs according to one or more aspects of this disclosure are shown. Wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0059] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0060] UE 115 may be distributed throughout the entire coverage area 110 of wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. UE 115 may be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0061] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0062] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0063] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0064] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0065] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0066] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0067] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0068] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0069] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0070] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support reporting enhancements for the UE as described herein. For example, some operations described as being performed by the UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0071] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0072] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0073] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0074] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0075] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0076] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0077] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0078] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0079] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0080] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0081] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a Transmission Time Interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst form of a shortened TTI (sTTI)).

[0082] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0083] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0084] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0085] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0086] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0087] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0088] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0089] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0090] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0091] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0092] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0093] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0094] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0095] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0096] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0097] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0098] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0099] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0100] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0101] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0102] In some examples, transmissions performed by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0103] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0104] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0105] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0106] In some cases, one or more UEs 115 (such as airborne UE 115-a) may be configured to collect data (e.g., for reporting) based on airborne UE-specific events or based on height-specific area ranges. For example, SON or MDT reporting may be enhanced for UE 115. In some methods, the collection of recorded MDT data may be triggered using airborne UE events or height-specific area ranges to enhance coverage and capacity at a specific altitude. MDT data may be collected when altitude conditions are met, when signal quality conditions are met, or when UE 115 is outside a restricted area. In some methods, airborne UE 115-a may collect data for a height-specific ANR table. For example, network entity 105 may configure UE 115 to report CGIs of cells detected at or within an altitude range at a specific altitude. Additional data types may be provided in the report, such as UE type indications in SON reports with UE altitude or UE characteristics. For example, airborne UE 115-a may use one or more data collection triggers (e.g., when the UE's altitude meets an altitude threshold) to generate an SHR or SPR. Some reports (e.g., random access reports, RLF reports, SHR, SPR, etc.) can be enhanced to include data indicating the altitude of UE 115 (e.g., airborne UE 115-a), the characteristics of UE 115 (e.g., antenna type, antenna orientation, antenna mounting), or the density of UE 115 detected near the UE at the time of measurement.

[0107] In some cases, density data collection may be triggered as an immediate MDT report, where the over-the-air UE 115-a obtains measurements of neighboring cells and identifies the number of other detected UE 115s (e.g., based on broadcast signals or collision avoidance beacons, etc.). In other cases, the UE 115-a may not obtain neighboring cell measurements and may provide measurements recorded from previous measurement times, along with an indication of the number of detected UE 115s. In a further case, the over-the-air UE 115-a may not provide measurements and may only provide an indication of the number of other detected UE 115s.

[0108] Some examples of the techniques described herein can enhance SHR data collection for UE 115 (e.g., airborne UE 115-a). An SHR can be generated to identify one or more conditions during a successful handover (e.g., a successful normal handover, a successful Dual Active Stack (DAPS) handover, or a successful conditional handover). To analyze a successful handover, UE 115 (e.g., airborne UE 115-a) can generate an SHR based on configuration information received from network entity 105. UE 115 can send or provide an SHR to network entity 105. In some examples, UE 115 can store the SHR until network entity 105 requests it, or for a maximum of a time limit (e.g., 48 hours) after the SHR is recorded. After retrieving the SHR, it can be analyzed (e.g., by network entity 105) to determine whether to adjust the mobility configuration. For example, network entity 105 (e.g., the Mobility Robustness Optimization (MRO) function at network entity 105) can utilize SHR to adjust the handover trigger (e.g., the handover threshold) to increase the probability of a successful handover.

[0109] In some methods, the data collected for the SHR may include one or more timer values, or may be triggered based on one or more timer values. Some examples of timers include the T310 timer (which starts upon receiving a synchronization indication), the T312 timer (which starts upon a radio link failure), and the T304 timer (which starts upon receiving a handover command). Associated with the T310 timer, a radio link failure may occur if a threshold number of synchronization indications is reached. In some examples, the SHR may include data indicating one or more successful handovers when the T310 value is greater than the threshold, when the number of synchronization indications is within a threshold number of radio link failures, when the T312 value is greater than the threshold, when the T304 value is greater than the threshold, or when the T304 timer is within a certain period of time before expiration (where handover may fail upon expiration). Reference Figure 2 Further details regarding SHR data collection for airborne UE 115-a are provided.

[0110] Some examples of the techniques described herein can enhance SPR data collection for UE 115 (e.g., over-the-air UE 115-a). SPR enables the observability of detecting successful PSCell additions or changes (e.g., suboptimal but successful PSCell additions or changes). UE 115 can collect data for SPR based on a configuration provided by network entity 105. For example, UE 115 (e.g., over-the-air UE 115-a) can collect data for SPR and can send an SPR to network entity 105. UE 115 can send an SPR to network entity 105 or provide an SPR. In some examples, UE 115 can store an SPR until network entity 105 requests an SPR, or for a maximum of a time limit (e.g., 48 hours) after the SPR is recorded. After retrieving the SPR, it can be analyzed (e.g., by network entity 105) to determine whether to adjust the mobility configuration. For example, network entity 105 (e.g., the MRO function at network entity 105) can use SPR to adjust cell change triggering (e.g., cell change threshold) to increase the probability of successful cell change.

[0111] In some methods, the data collected for SPR may include one or more timer values, or may be triggered based on one or more timer values. Examples of timers include the T310 timer for secondary cell groups (SCGs), the T312 timer for SCGs, and the T304 timer for SCGs. The T310, T312, or T304 timers for SCGs may operate in a manner similar to the timers described herein with respect to handover. In some examples, SPR may include data indicating one or more successful cell changes when the T310 value for SCG is greater than a threshold, when the number of asynchronous indications is within a threshold number of radio link failures, when the T312 value for SCG is greater than a threshold, when the T304 value for SCG is greater than a threshold, or when the T304 timer for SCG is within a certain time period before expiration (where cell changes may fail upon expiration). Reference Figure 2 Further details regarding SPR data collection for airborne UE 115-a are provided.

[0112] Figure 2Examples of wireless communication system 200 supporting reporting enhancements for UEs according to one or more aspects of this disclosure are shown. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. For example, wireless communication system 200 may include serving network entity 105-a (which may also be referred to as serving cell) having a coverage area 110-a (e.g., for terrestrial coverage), multiple neighboring network entities 105-b to 105-d (which may also be referred to as neighboring cells), and UE 115-b, which may be examples of network entity 105 and UE 115 as described herein. Wireless communication system 200 may support a variety of radio access technologies, including 4G systems, such as LTE systems, LTE-A systems, or LTE-A Pro systems; 5G systems, which may be referred to as NR systems; sidelink communications, which may be referred to as PC5 communications; UAV-specific cellular networks; or any combination thereof.

[0113] exist Figure 2 In the example, airborne UE 115-b can establish a communication link 125-a with the serving cell at network entity 105-a (e.g., entering RRC connection mode or establishing Uu connectivity in an NR communication network, etc.). Communication link 125-a can be relative to... Figure 1 An example of the described communication link 125. Network entity 105-a and air UE 115-b can communicate with network entity 105-a via communication link 125-a to support various applications (e.g., video, remote command and control (C2), etc.). Communication link 125-a may include a bidirectional link that enables both uplink and downlink network communication. For example, air UE 115-b can use communication link 125-a to send one or more uplink transmissions 220, such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a can use communication link 125-a to send one or more downlink transmissions 225, such as downlink control signals or downlink data signals, to air UE 115-b.

[0114] In some cases, the airborne UE 115-b can also establish one or more other connections (e.g., PC5 connections) with another airborne UE, which can support various applications. Examples of such applications include User-to-Everything (U2X) Detection and Avoidance (U2X-DAA) applications and other applications that can be used for conflict control (e.g., using broadcast messages). In some examples, the airborne UE 115-b can also interact with regulatory agencies or services for identification and other purposes. As an example, the airborne UE 115-b can interact with regulatory agencies or services for U2X identification (ID) (e.g., remote identification) and can identify or receive flight information (e.g., using broadcast messages), establish remote C2 connections, and so on.

[0115] Network entity 105-a may send configuration information 230 to air UE 115-b. Configuration information 230 may configure air UE 115-b to send reports 235 of UE-collected data associated with relationship information and collection rules of one or more network nodes (e.g., air UE 115-b or one or more of network entities 105). For example, air UE 115-b may collect data based on collection rules to generate report 235. Air UE 115-b may send report 235 to network entity 105-a.

[0116] Report 235 may be associated with relationship information of one or more network nodes. As used herein, relationship information is information indicating one aspect of the relationship between network nodes (e.g., between air UE 115-b and one or more of network entities 105-a, 105-b, 105-c, 105-d, or between two or more of network entities 105-a, 105-b, 105-c, 105-d). For example, relationship information may indicate the relationship between network nodes during communication procedures (e.g., handover, cell change, link establishment, or cell group interaction, etc.). Relationship information may indicate the source and target nodes for handover or cell change, may indicate a random access procedure between air UE 115-b and network entity 105, may indicate that air UE 115-b establishes a link with network entity 105 or detects a link failure, may indicate a designated cell group for measurement, or may indicate that air UE 115-b and network entity 105 are prohibited from communicating in a restricted area, etc. In some methods, the data used for report 235 may indicate relational information, or the collection of data used for report 235 may be based on relational information. Examples of report 235 may include SHR, SPR, Random Access Report (RA report), Connection Establishment Failure (CEF) report, RLF report, or a report including SCG failure information. In some examples, report 235 may include an MDT report associated with an area range configured based on altitude conditions (e.g., the set of cells specified in configuration information 230), or an MDT report associated with a restricted area configured based on altitude conditions. In some examples, the data used for reports associated with relational information may include data that is supplementary or alternative to one or more signal strength measurements (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Code Power (RSCP), received energy per chip (Ec) of the pilot channel divided by total noise power density (No) (Ec / No), measured received signal level (Rxlev) of one or more cells, pilot Pn phase and pilot strength of one or more cells, or Received Signal Strength Indicator (RSSI), etc.).

[0117] Collection rules can be one or more criteria used to trigger the collection of data for reporting (by airborne UE 115-a). Collection rules can be based on altitude conditions used to collect the data for reporting. Altitude conditions can specify an altitude or altitude range to trigger data collection. For example, altitude conditions can specify the minimum altitude at which airborne UE 115-a can collect data above it, the maximum altitude at which airborne UE 115-a can collect data below it, or the altitude range at which airborne UE 115-a can collect data within it. In some examples, altitude conditions can be indicated in configuration information 230. For example, configuration information 230 can include explicit or implicit indicators of altitude conditions. In some examples, configuration information 230 can command airborne UE 115-b to collect data for reporting 235 for a specific set of cells, collecting data for that specific set of cells when the altitude conditions are met.

[0118] In some examples, the airborne UE 115-b can detect its altitude or receive information indicating its altitude. For example, the airborne UE 115-b can use Global Positioning System (GPS) data to determine its altitude. In some examples, the airborne UE 115-b can determine whether an altitude condition is met by determining whether its altitude is above, below, or within a certain range.

[0119] When collection rules (e.g., altitude conditions) are met, the airborne UE 115-b may collect data. Examples of data collected by the UE may include handover success or failure events, PSCell change or addition success or failure events, whether the random access procedure between the airborne UE 115-b and network entity 105 is successful, whether the connection establishment between the airborne UE 115-b and network entity 105 fails, whether the radio link between the airborne UE 115-b and network entity 105 fails, whether communication with a cell group fails, measurements of signals for a specified cell set (e.g., signals 210-a, 210-b, 210-c), or data collected outside a restricted area. The airborne UE 115-b may use the collected data to generate report 235.

[0120] The air UE 115-b can send a report 235 to the network entity 105-b according to the configuration information 230. The report 235 can indicate the data associated with the relationship information of one or more network nodes collected by the air UE 115-b in response to the satisfaction of the collection rules.

[0121] In some examples, the collection rules may include one or more conditions (e.g., triggers) for collecting SHR or SPR data. In some methods, the altitude conditions for collecting data may include one or more altitude thresholds for the altitude of the airborne UE 115-b, and the data for reporting 235 may include handover data or cell change data collected by the airborne UE 115-b in response to the airborne UE 115-b's altitude meeting the altitude thresholds. For example, altitude conditions may include a minimum threshold, a maximum threshold, an altitude threshold range, multiple thresholds for collecting data at different altitudes, or any combination thereof.

[0122] In some examples, if the airborne UE 115-b has exceeded the altitude threshold configured by the network, the airborne UE 115-b may perform altitude-based reporting based on collection rules. For example, collection rules may enable altitude-related configurations applied to specific altitude areas, interference detection based on measurement reports triggered when a number of cells (e.g., more than one) concurrently satisfy the collection rules, signaling of flight path information from the airborne UE 115-b to the Next Generation Radio Access Network (NG-RAN) and from the source network entity to the target network entity during handover, or location information reporting (e.g., the horizontal or vertical velocity of the airborne UE 115-b).

[0123] In some methods, the airborne UE 115-b can collect SHR or SPR statistics when the airborne UE 115-b's altitude meets the collection rules. Collection rules (e.g., altitude conditions or altitude thresholds) can help collect more useful data because when the airborne UE 115-b is above a certain altitude and when radio conditions are relatively poor, more handover near-failures may occur (e.g., handovers occurring within a threshold number of asynchronous indications or within a threshold time period before the timer indicating a handover failure expires).

[0124] Some aspects of the techniques described herein may include MDT enhancements for recordings of airborne UEs (e.g., airborne UE 115-b). For example, receiving configuration information 230 may include receiving information indicating a region range based on altitude conditions, and the data for reporting 235 may include data collected by airborne UE 115-b in response to satisfaction of the region range.

[0125] The area scope may indicate the region used to collect data from one or more cells (e.g., a spatial region, a geographic region, a region defined by latitude and longitude, etc.), where altitude conditions provide the altitude boundaries of the region. For example, configuration information 230 may include one or more cell indicators, and the data used for reporting 235 may include data collected by the air UE 115-b for one or more cells associated with one or more cell indicators. In some aspects, the altitude conditions used for collecting data may include one or more altitude thresholds for the altitude of the air UE 115-b, wherein the air UE 115-b may collect first data associated with one or more first cells in one or more cells in response to the satisfaction of a first threshold among the one or more altitude thresholds. For example, the air UE 115-b can be configured with an altitude-related area range in the recorded MDT configuration. If the altitude of the air UE 115-b is less than a first altitude threshold, the air UE 115-b collects the recorded MDT data of network entities 105-a and 105-b (e.g., cells 1 and 2). Alternatively, if the altitude of the air UE 115-b is between the first and second altitude thresholds, the air UE 115-b collects the recorded MDT data of network entities 105-a, 105-b, 105-c, and 105-d (e.g., cells 1, 2, 3, and 4).

[0126] In some respects, recorded MDTs can be collected based on altitude conditions of collection rules. For example, when the altitude of the airborne UE 115-b is greater than or less than an altitude threshold, the airborne UE 115-b can collect MDT data for one or more cells. In some cases, the MDT data collected by the airborne UE 115-b may include the physical cell identifier (PCID) of the recorded cell, the carrier frequency of one or more cells, RSRP, RSRQ, RSCP, Ec / No, Rxlev, pilot Pn phase and pilot strength of one or more cells, RSSI and round-trip time (RTT) of wireless local area network (WLAN) access points (APs), RSSI of Bluetooth beacons, or any combination thereof.

[0127] In some examples, the collection rules may be based on signal quality conditions, and the altitude conditions may include one or more altitude thresholds for the altitude of the airborne UE 115-b. The data used for reporting 235 may include data collected by the airborne UE 115-b in response to the satisfaction of signal quality conditions and the satisfaction of one or more altitude thresholds for the airborne UE 115-b's altitude. In some aspects, the airborne UE 115-b may receive one or more reference signals corresponding to one or more cells (where the reference signals may be...). Figure 2Examples of signals 210-a, 210-b, and 210-c shown herein), wherein satisfying signal quality conditions may include one or more metrics of one or more reference signals satisfying a signal quality threshold. For example, over-the-air UE 115-b may collect data (e.g., MDT data) when an altitude condition and RSRP threshold condition, RSRQ threshold condition, signal-to-interference-plus-noise ratio (SINR) threshold condition, or “Out of Coverage” condition are satisfied (e.g., if an “Out of Coverage” event is detected or the event persists for a threshold time period). In some examples, over-the-air UE 115-b may collect data (e.g., MDT data) when the metrics (e.g., RSRP) of a certain number (e.g., at least N) of neighboring cells' reference signals satisfy a signal quality threshold (e.g., greater than or less than the threshold).

[0128] Some examples of the techniques described herein involve data collection in relation to one or more restricted areas. The collection of recorded data (e.g., MDT data) may be based on whether the airborne UE 115-b is located within a restricted area. Examples of restricted areas may include “no-transmission zones” or “no-fly zones.” No-transmission zones may be established for geofencing or regulatory purposes. Within a no-transmission zone, the airborne UE 115-b (e.g., UAV) may be prohibited from transmitting power exceeding a threshold power within a given frequency band. In some examples, network entity 105-a may transmit signals to the airborne UE 115-b indicating a restricted area (e.g., a no-transmission zone or no-fly zone). For example, the restricted area may be indicated in a three-dimensional space with an area identifier via a System Information Block (SIB), dedicated signaling, configured signaling, or via subscription, etc. A no-fly zone may be an area where the airborne UE 115-b is prohibited from traveling.

[0129] In some aspects, the airborne UE 115-b can detect when it enters a restricted area. For example, the airborne UE 115-b can use GPS data or other positioning data to determine whether it has entered a restricted area indicated by network entity 105-a. The airborne UE 115-b can avoid collecting data while in a restricted area and can collect data for reporting 235 while outside the restricted area. For example, the data for reporting 235 may omit data associated with the restricted area and may include data collected by the airborne UE 115-b for reporting 235 while outside the restricted area. In some methods, the data for reporting 235 may include first data indicating entry into a restricted area, second data indicating exit from a restricted area, third data indicating that the airborne UE 115-b is within a certain distance from the restricted area, or any combination thereof. For example, the collection of recorded MDT data can be controlled in the context of a restricted area (e.g., a no-transmission zone or no-fly zone). The airborne UE 115-b can stop collecting recorded MDT data based on entering a prohibited transmission zone or no-fly zone, and can resume collecting recorded MDT data based on leaving a prohibited transmission zone or no-fly zone. The airborne UE 115-b can indicate in the recorded MDT report via flags that the airborne UE 115-b has entered a prohibited transmission zone, the airborne UE 115-b has left a prohibited transmission zone, or a zone identifier corresponding to a prohibited transmission zone or no-fly zone, or that the airborne UE 115-b is within a threshold distance (e.g., meters) from a prohibited transmission zone or no-fly zone.

[0130] In some examples, network entity 105-a may send cell report configuration information. For example, receiving configuration information 230 may include receiving cell report configuration information that instructs air UE 115-b to collect cell data associated with one or more cells in response to the satisfaction of altitude conditions. Sending a report 235 may include sending a cell report that includes cell data associated with one or more cells. For example, network entity 105-a may configure air UE 115-b to provide CGI reports when air UE 115-b is located at or within an altitude range. In some methods, cell data may be included in an ANR table. For example, air UE 115-b may provide cell data (by air UE 115-b or network entity 105-a) to generate an ANR table for cells available at or within an altitude range.

[0131] In some respects, the airborne UE 115-b may use characteristic data associated with the airborne UE 115-b, altitude data associated with the airborne UE 115-b, detected airborne UE density data, or any combination thereof to enhance one or more reports (e.g., RA report, CEF report, RLF report, SHR, SPR, MDT report, or a report that includes SCG failure information). For example, report 235 may indicate characteristics of the UE type (e.g., UE type with a directional antenna, UE type with a vehicle-mounted antenna, etc.), altitude information (e.g., for creating a altitude-specific coverage map), detected airborne UE density, or other information.

[0132] In some cases, the data used for report 235 may be recorded data. For recorded data, air-to-air UE 115-b may collect and store the data. Air-to-air UE 115-b may send an availability indication to network entity 105-b indicating the availability of the recorded data. Network entity 105-b may send a request for the recorded data based on the availability indication. Air-to-air UE 115-b may send report 235 to network entity 105-b upon receiving a request for the recorded data.

[0133] In some cases, as part of the connection establishment of communication link 125-a, the air UE 115-b can provide capability information. For example, the air UE 115-b can indicate its ability to collect and report one or more types of data (e.g., whether the air UE 115-b is able to record and report data for reports associated with relationship information of one or more network nodes, SHR, SPR, CGI reports, RLF reports, RA reports, or MDT reports for a configured set of cells, etc.). Based on the capability indication, the network or serving network entity 105-a can configure the air UE 115-b for data collection and reporting.

[0134] Figure 3 Examples of wireless communication systems supporting elevation-based reporting 300 for UEs, according to one or more aspects of this disclosure, are shown. In some examples, elevation-based reporting 300 may be implemented in aspects of wireless communication systems 100 or 200. For example, serving network entity 105-d may configure first air UE 115-c, second air UE 115-d, and third air UE 115-e to provide associated reports of relational information via link 305 (e.g., link 305-a, link 305-b, or link 305-c).

[0135] In this example, the reports associated with the relationship information can be configured such that each UE 115 can collect data based on the altitude of multiple regions (e.g., data from SHR, SPR, RLF reports, RA reports, CGI reports, or MDT reports for a configured set of cells, etc.). In some cases, UE 115 can be configured with one or more altitude thresholds 335 that trigger data collection or reporting. For example, these regions may include a first region within a first altitude range 310 below a first altitude threshold 335-a, in which, in this example, first-air UE 115-c can collect data. In some methods, the altitude of UE 115 can be inferred based on an altitude threshold rather than an explicit altitude parameter reported by UE 115. In some methods, UE 115 can explicitly indicate the altitude in its reports. These regions may also include a second region within a second altitude range 315 (e.g., between 50 meters and 60 meters) between the first altitude threshold 335-a and a second altitude threshold 335-b, in which second-air UE 115-d can collect data. Furthermore, these areas may also include a third region within a third altitude range 320 (e.g., between 60 meters and 75 meters) between the second altitude threshold 335-b and the third altitude threshold 335-c, where the third airborne UE 115-e can collect data. This altitude-based data collection may allow for adjustments to mobility configurations (e.g., handover or cell change thresholds), identification of UE 115s requiring adjustments to transmit power or coverage enhancements, or other technologies.

[0136] Figure 4 Examples of wireless communication systems for over-the-air UE data collection 400 that support enhanced reporting for UEs according to one or more aspects of this disclosure are shown. In some examples, over-the-air UE data collection 400 may be implemented in aspects of wireless communication systems 100 or 200. For example, serving network entity 105-e may configure over-the-air UE 115-f to provide reports associated with relationship information via connection 405, and may additionally or alternatively configure over-the-air UE 115-f to avoid collecting data in restricted areas 415 (e.g., no-transmission zones or no-fly zones).

[0137] In this example, network entity 105-e may transmit signals (e.g., coordinates, boundaries, or altitude range) indicating the restricted area 415 to the air UE 115-f. In some cases, the radius or parameters for the restricted area 415 may be predefined or configured by the network (e.g., via network entity 105-e), which may be provided via RRC, broadcast RRC (e.g., SIB), MAC control element (CE) signaling, or any combination thereof. Before entering or after leaving the restricted area 415, the air UE 115-f may collect data (e.g., data from SHR, SPR, RLF reports, RA reports, CGI reports, or MDT reports for a configured set of cells, etc.). In some examples, the air UE 115-f may provide an indicator (e.g., a flag) in the reported data indicating that the air UE 115-f is within a threshold distance from the restricted area 415. For example, the air UE 115-f may provide an indicator associated with the collected data, indicating that the data was collected when the air UE 115-f was within a threshold distance from the restricted area 415. In some examples, the air UE 115-f may provide an indicator (e.g., a flag) in the reported data, indicating that the air UE 115-f has entered or left the restricted area 415. For example, the air UE 115-f may provide an indicator associated with the collected data, indicating that data collection is being stopped or resumed when the air UE 115-f enters or leaves the restricted area 415.

[0138] Figure 5 An example of a process flow 500 supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. In some examples, process flow 500 may implement aspects of wireless communication system 100 or 200. Process flow 500 may be implemented by a UE 115-g (e.g., an airborne UE or UAV / drone) and network entity 105-f as described herein. In the following description of process flow 500, communication between UE 115-g and network entity 105-f may be transmitted in a different order than the example order shown, or operations performed by UE 115-g and network entity 105-f may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0139] In some examples, the operations illustrated in process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0140] At point 505, network entity 105-f may send configuration information to UE 115-g for reporting data collected by the UE in association with relationship information and collection rules associated with one or more network nodes. In some cases, the configuration information may indicate collection rules (e.g., altitude conditions, one or more altitude thresholds, information indicating area range, one or more cell indicators, one or more signal quality conditions, or information indicating restricted areas, etc.). In some examples, the configuration information may be sent in a LoggedMeasurementConfiguration message. In some examples, UE 115-g may be in an RRC connected state when the configuration information is received. For example, UE 115-g and network entity 105-f may have already established a link before network entity 105-f sends the configuration information.

[0141] At 510, UE 115-g can determine one or more collection conditions. For example, UE 115-g can store one or more aspects of collection rules (e.g., altitude conditions, one or more altitude thresholds, information indicating area range, one or more cell indicators, one or more signal quality conditions or information indicating restricted areas, etc.) to enable UE 115-g to enforce the collection rules.

[0142] At 515, UE 115-g can transition to idle mode (e.g., based on the inactivity of the connection with network entity 105-f). For example, UE 115-g can transition to RRC idle or RRC inactive state.

[0143] At point 520, UE 115-g can detect the fulfillment of collection rules. For example, UE 115-g can detect that UE 115-g has exceeded an altitude threshold, UE 115-g is within an altitude range, UE 115-g has left a restricted area, or one or more signal quality conditions are met, etc.

[0144] At 525, UE 115-g can collect data for reporting. For example, UE 115-g can collect handover success or failure data, cell change success or failure data, MDT data for the configured cell set, RLF failure data, or CGI data, etc. The collected data can be stored (e.g., recorded). The collected data can be recorded data collected when UE 115-g is in idle mode. In some examples, this data can be stored along with UE 115-g altitude data, indicators regarding UE 115-g's position within a restricted area threshold range, indicators regarding UE 115-g's departure from a restricted area, or timestamps, etc.

[0145] At 530, UE 115-g can switch to connected mode. For example, UE 115-g can switch to RRC connected mode based on the activity of UE 115-g or network entity 105-f (e.g., link).

[0146] At 535, UE 115-g can send an availability indication indicating the availability of logged data to network entity 105-f. For example, UE 115-g can send the logMeasAvailable parameter to network entity 105-f as part of an RRC connection establishment completion message.

[0147] At point 540, network entity 105-f may send a request for recorded data based on an availability indication. For example, network entity 105-f may transmit a UEInformationRequest indicating a request for recorded data.

[0148] At point 545, UE 115-g can send reports to network entity 105-f. For example, UE 115-g can send SHR, SPR, RLF, RA, CGI, or MDT reports for a configured set of cells, etc. This report can be sent in response to a request for recorded data.

[0149] In some examples, network entity 105-f may adjust mobility configurations based on the report. For instance, network entity 105-f may transmit a configuration message to UE 115-g to adjust handover or cell change thresholds, thereby increasing the probability of successful handover or cell change. In some methods, network entity 105-f may adjust one or more handover or cell change thresholds, transmit power, or beam directivity based on the report. In some examples, network entity 105-f may send messages to one or more other network entities to adjust transmit power or beam directivity based on the report.

[0150] Figure 6A block diagram 600 of a device 605 supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. Device 605 may be an example of aspects of a UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0151] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reporting enhancements for the UE). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0152] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reporting enhancements for the UE). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0153] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of reporting enhancements for the UE as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0154] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0155] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0156] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated in combination with the receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0157] For example, the communication manager 620 is capable of, configured to, or operable to support components for performing the following operations: receiving configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. The communication manager 620 is also capable of, configured to, or operable to support components for performing the following operations: sending the report to a network entity based on the configuration information, wherein the report indicates data collected by a UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0158] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption or utilizing communication resources more efficiently.

[0159] Figure 7 A block diagram 700 of a device 705 supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0160] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reporting enhancements for the UE). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0161] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reporting enhancements for the UE). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0162] Device 705 or its various components may be examples of parts for performing various aspects of reporting enhancements for the UE as described herein. For example, communication manager 720 may include configuration component 725, reporting component 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0163] Configuration component 725 is capable of, configured to, or operable to support components for performing the following operations: receiving configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. Reporting component 730 is capable of, configured to, or operable to support components for performing the following operations: sending the report to a network entity based on the configuration information, wherein the report indicates data collected by a UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0164] Figure 8 A block diagram 800 is shown of a communication manager 820 supporting reporting enhancements for a UE according to one or more aspects of this disclosure. The communication manager 820 may be an example of a communication manager 620, a communication manager 720, or aspects thereof as described herein. The communication manager 820 or its various components may be examples of parts for performing the various aspects of reporting enhancements for a UE as described herein. For example, the communication manager 820 may include a configuration component 825, a reporting component 830, a restriction zone component 835, an availability component 840, a recorded data component 845, a reference signal component 850, a collection component 855, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0165] Configuration component 825 is capable of, configured to, or operable to support components for performing the following operations: receiving configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. Reporting component 830 is capable of, configured to, or operable to support components for performing the following operations: sending the report to a network entity based on the configuration information, wherein the report indicates data collected by a UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0166] In some examples, the UE's altitude conditions include at least one altitude threshold for the UE's altitude, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the UE's altitude meeting at least one altitude threshold.

[0167] In some examples, in order to support receiving configuration information, configuration component 825 is configured to perform, or is operable to support components for performing: receiving information indicating an area range based on altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the area range.

[0168] In some examples, the configuration information also includes one or more cell indicators. In some examples, the data collected by the UE includes data collected by the UE for one or more cells associated with one or more cell indicators.

[0169] In some examples, the UE's altitude conditions include at least one altitude threshold for the UE's altitude, and the collection component 855 is configured to perform, or is operable to support components for performing, the following: collecting first data associated with one or more first cells in one or more cells in response to the satisfaction of a first threshold among at least one altitude threshold.

[0170] In some examples, the collection rules are also based on signal quality conditions, and altitude conditions include at least one altitude threshold for the UE's altitude. In some examples, the data collected by the UE includes data collected by the UE in response to the satisfaction of signal quality conditions and the UE's altitude satisfying at least one altitude threshold.

[0171] In some examples, the reference signal component 850 is capable of, configured to perform, or is operable to support components for performing: receiving one or more reference signals corresponding to one or more cells, wherein the satisfaction of signal quality conditions includes one or more metrics of one or more reference signals satisfying a signal quality threshold.

[0172] In some examples, the restricted area component 835 is capable of performing, configured to perform, or is operable to support components for performing: detecting UE entry into a restricted area, whereby data collection is avoided when the UE is in the restricted area, and data collected by the UE when it is outside the restricted area.

[0173] In some examples, the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0174] In some examples, in order to support receiving configuration information, configuration component 825 is configured to perform, or is operable to support components for performing, the following operations: receiving cell report configuration information that instructs the UE to collect cell data associated with one or more cells in response to the satisfaction of altitude conditions, and sending the report includes sending a cell report that includes cell data associated with one or more cells.

[0175] In some examples, cell data is included in the ANR table.

[0176] In some examples, in order to support the transmission of the report, the reporting component 830 is configured to perform, or is able to operate to support components for performing, the following operations: transmitting UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

[0177] In some examples, the report is an RA report, CEF report, RLF report, SHR, SPR, or a report that includes SCG failure information.

[0178] In some examples, the data collected by the UE is recorded data, and the availability component 840 is configured to, or is operable to support components for, sending an availability indication to a network entity indicating that the recorded data is available. In some examples, the recorded data component 845 is configured to, or is operable to support components for, receiving requests for recorded data based on the availability indication, wherein the report is sent to the network entity based on the receipt of the request for recorded data.

[0179] Figure 9 A diagram of a system 900 including device 905 supporting reporting enhancements for a UE, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

[0180] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0181] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 as described herein, or via a wired or wireless link. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0182] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0183] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., supporting various functions or tasks for reporting enhancements to the UE). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, at least one processor 940 and at least one memory 930 configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 930 or otherwise.

[0184] For example, the communication manager 920 is capable of, configured to, or operable to support components for performing the following operations: receiving configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. The communication manager 920 is also capable of, configured to, or operable to support components for performing the following operations: sending the report to a network entity based on the configuration information, wherein the report indicates data collected by a UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0185] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or increasing processing power.

[0186] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. For example, the communication manager 920 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 915. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause the device 905 to perform various aspects of reporting enhancements for the UE as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0187] Figure 10 A block diagram 1000 of a device 1005 supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0189] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0190] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of reporting enhancements for the UE as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0191] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0192] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0193] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with the receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in combination with the receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0194] For example, the communication manager 1020 is capable of, configured to, or operable to support components for performing the following operations: sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. The communication manager 1020 is also capable of, configured to, or operable to support components for performing the following operations: receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0195] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., controlling receiver 1010, transmitter 1015, communication manager 1020 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, reducing power consumption or utilizing communication resources more efficiently.

[0196] Figure 11 A block diagram 1100 of a device 1105 supporting reporting enhancements for a UE according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0197] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0198] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0199] Device 1105 or its various components may be examples of parts used to perform various aspects of reporting enhancements for the UE as described herein. For example, communication manager 1120 may include configuration manager 1125, reporting manager 1130, or any combination thereof. Communication manager 1120 may be an example of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0200] Configuration manager 1125 is capable of, configured to, or operable to support components for performing the following operations: sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. Report manager 1130 is capable of, configured to, or operable to support components for performing the following operations: receiving the report from the UE based on the configuration information, wherein the report indicates data collected by the UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0201] Figure 12A block diagram 1200 is shown of a communication manager 1220 supporting reporting enhancements for a UE according to one or more aspects of this disclosure. The communication manager 1220 may be an example of a communication manager 1020, a communication manager 1120, or aspects thereof as described herein. The communication manager 1220 or its various components may be examples of parts for performing the various aspects of reporting enhancements for a UE as described herein. For example, the communication manager 1220 may include a configuration manager 1225, a reporting manager 1230, an availability manager 1235, a request manager 1240, a reference signal manager 1245, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within a protocol layer of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0202] Configuration manager 1225 is capable of, configured to, or operable to support components for performing the following operations: sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. Report manager 1230 is capable of, configured to, or operable to support components for performing the following operations: receiving the report from the UE based on the configuration information, wherein the report indicates data collected by the UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0203] In some examples, the UE's altitude conditions include at least one altitude threshold for the UE's altitude, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the UE's altitude meeting at least one altitude threshold.

[0204] In some examples, in order to support the transmission of configuration information, the configuration manager 1225 is capable of, configured to perform, or is operable to support components for performing: transmitting information indicating an area range based on altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the area range.

[0205] In some examples, the configuration information also includes one or more cell indicators. In some examples, the data collected by the UE includes data collected by the UE for one or more cells associated with one or more cell indicators.

[0206] In some examples, the UE's altitude conditions include at least one altitude threshold for the UE's altitude.

[0207] In some examples, the collection rules are also based on signal quality conditions, and altitude conditions include at least one altitude threshold for the UE's altitude. In some examples, the data collected by the UE includes data collected by the UE in response to the satisfaction of signal quality conditions and the UE's altitude satisfying at least one altitude threshold.

[0208] In some examples, to support receiving the report, the reference signal manager 1245 is configured to perform, or is operable to support components for performing, the following operations: receiving data indicating one or more reference signals corresponding to one or more cells, wherein the data indicating one or more reference signals is collected by the UE in response to the satisfaction of signal quality conditions, the satisfaction of which includes one or more metrics of one or more reference signals satisfying a signal quality threshold.

[0209] In some examples, the data collected by the UE is missing data associated with the restricted area and includes data associated with one or more areas outside the restricted area.

[0210] In some examples, the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0211] In some examples, in order to support the transmission of configuration information, the configuration manager 1225 is capable of, configured to perform, or is operable to support components for performing the following operations: transmitting cell report configuration information that commands the UE to collect cell data associated with one or more cells in response to the satisfaction of altitude conditions, and receiving the report includes receiving a cell report that includes cell data associated with one or more cells.

[0212] In some examples, cell data is included in the ANR table.

[0213] In some examples, in order to support receiving the report, the report manager 1230 is configured to perform the following operations, or is able to operate to support components for performing the following operations: receiving UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

[0214] In some examples, the report is an RA report, CEF report, RLF report, SHR, SPR, or a report that includes SCG failure information.

[0215] In some examples, the data collected by the UE is recorded data, and the availability manager 1235 is configured to, or is operable to support components for, receiving from the UE an availability indication indicating that the recorded data is available. In some examples, the request manager 1240 is configured to, or is operable to support components for, sending a request for the recorded data based on the availability indication, wherein the UE receives a report based on the request for the recorded data.

[0216] Figure 13 A diagram of a system 1300 including device 1305 supporting reporting enhancements for UEs, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or a component including such devices or network entities. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support output and enable communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1340).

[0217] As described herein, transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0218] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by one or more processors of at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by one of the processors of at least one processor 1335, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0219] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., supporting various functions or tasks for reporting enhancements to the UE). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, wherein at least one processor 1335 and at least one memory 1325 are configured to perform the various functions described herein. At least one processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories in at least one memory 1325). In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1335 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1335 or a processing system including at least one processor 1335 may be configured, configured to, or operated to cause the device 1305 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1325 or otherwise.

[0220] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one component of different components or partitioned between different components).

[0221] In some examples, the communication manager 1320 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 may manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0222] For example, the communication manager 1320 is capable of, configured to, or operable to support components for performing the following operations: sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. The communication manager 1320 is also capable of, configured to, or operable to support components for performing the following operations: receiving the report from the UE based on the configuration information, wherein the report indicates data collected by the UE associated with relationship information for one or more network nodes in response to the satisfaction of collection rules.

[0223] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or increasing processing power.

[0224] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1310. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors of at least one processor 1335 to cause device 1305 to perform various aspects of reporting enhancements for the UE as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0225] Figure 14 A flowchart illustrating a method 1400 for supporting reporting enhancements for a UE according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be performed by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0226] At 1405, the method may include receiving configuration information from a network entity for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 8The configuration component 825 described is used to perform this action. Additionally or alternatively, the components used to perform 1405 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communications manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0227] At 1410, the method may include sending the report to a network entity based on the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of collection rules and associated with relationship information of one or more network nodes. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to... Figure 8 The report component 830 described herein is used to perform this action. Additionally or alternatively, components used to perform 1410 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communication manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0228] Figure 15 A flowchart illustrating a method 1500 for supporting reporting enhancements to a UE according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0229] At 1505, the method may include receiving configuration information from a network entity for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions, and wherein the data collected by the UE is recorded data. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 8 The configuration component 825 described is used to perform this action. Additionally or alternatively, the components used to perform 1505 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communication manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0230] At 1510, the method may include sending an availability indication to the network entity indicating that the recorded data is available. The operation of box 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 8The described availability component 840 is used to perform this action. Additionally or alternatively, the components used to perform 1510 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communication manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0231] At 1515, the method may include receiving a request for data on a record based on an availability indication. The operation of box 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 8 The described recorded data component 845 is used to perform the execution. Additionally or alternatively, the components used to perform 1515 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communication manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0232] At 1520, the method may include sending the report to a network entity based on the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of collection rules and associated with relationship information of one or more network nodes, and wherein sending the report to the network entity is based on receiving a request for recorded data. The operation of block 1520 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1520 may be provided by reference to [reference needed]. Figure 8 The report component 830 described herein is used to perform this action. Additionally or alternatively, components used to perform 1520 may (but are not required to) include, for example, an antenna 925, a transceiver 915, a communication manager 920, a memory 930 (including code 935), a processor 940, or a bus 945.

[0233] Figure 16 A flowchart illustrating a method 1600 for supporting reporting enhancements for a UE according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0234] At 1605, the method may include sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information with one or more network nodes and collection rules, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 12 The configuration manager 1225 described herein is used to perform this action. Additionally or alternatively, the components used to perform 1605 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communications manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0235] At 1610, the method may include receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of collection rules and associated with relationship information of one or more network nodes. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to... Figure 12 The report manager 1230 described herein is used to perform this action. Additionally or alternatively, the components used to perform 1610 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communications manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0236] Figure 17 A flowchart illustrating a method 1700 for supporting enhanced reporting for a UE according to various aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0237] At 1705, the method may include sending configuration information to the UE for sending a report of data collected by the UE associated with relationship information and collection rules for one or more network nodes, wherein the UE is an airborne UE and the collection rules are based on the UE's altitude conditions, and wherein the data collected by the UE is recorded data. The operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 12The configuration manager 1225 described herein is used to perform this action. Additionally or alternatively, the components used to perform 1705 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communications manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0238] At 1710, the method may include receiving an availability indication from the UE indicating the availability of recorded data. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be derived from references... Figure 12 The described availability manager 1235 is used to perform this. Additionally or alternatively, the components used to perform 1710 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communications manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0239] At 1715, the method may include sending a request for data on the record based on an availability indication. The operation of box 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 12 The request manager 1240 described is executed. Additionally or alternatively, the components used to execute 1715 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communication manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0240] At 1720, the method may include receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of collection rules and associated with relationship information of one or more network nodes, and wherein receiving the report from the UE is based on sending a request for recorded data. Operation of block 1720 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1720 may be provided by reference to [reference needed]. Figure 12 The report manager 1230 described herein is used to perform this action. Additionally or alternatively, the components used to perform 1720 may (but are not required to) include, for example, an antenna 1315, a transceiver 1310, a communications manager 1320, a memory 1325 (including code 1330), a processor 1335, or a bus 1340.

[0241] The following provides an overview of the various aspects of this disclosure:

[0242] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving configuration information from a network entity for transmitting a report of data collected by the UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on altitude conditions of the UE; and transmitting the report to the network entity according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information of the one or more network nodes in response to the satisfaction of the collection rules.

[0243] Aspect 2: According to the method of aspect 1, wherein the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the altitude of the UE satisfying the at least one altitude threshold.

[0244] Aspect 3: The method according to any one of Aspects 1 to 2, wherein receiving the configuration information includes: receiving information indicating a region range at least in part based on the altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the region range.

[0245] Aspect 4: According to the method of aspect 3, the configuration information further includes one or more cell indicators, and the data collected by the UE includes data collected by the UE for one or more cells associated with the one or more cell indicators.

[0246] Aspect 5: According to the method of aspect 4, wherein the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE, and the method further includes: collecting first data associated with one or more first cells in one or more cells in response to the satisfaction of a first threshold among the at least one altitude threshold.

[0247] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the collection rule is further based at least in part on signal quality conditions, the altitude conditions including at least one altitude threshold of the altitude of the UE, and the data collected by the UE includes data collected by the UE in response to the satisfaction of the signal quality conditions and the altitude of the UE satisfying the at least one altitude threshold.

[0248] Aspect 7: According to the method of aspect 6, the method further includes: receiving one or more reference signals corresponding to one or more cells, wherein the satisfaction of the signal quality condition includes one or more metrics of the one or more reference signals satisfying a signal quality threshold.

[0249] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: detecting that the UE enters a restricted area, wherein the UE avoids collecting data when in the restricted area, and collects data collected by the UE when outside the restricted area.

[0250] Aspect 9: According to the method of aspect 8, the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0251] Aspect 10: The method according to any one of Aspects 1 to 9, wherein receiving the configuration information includes: receiving cell report configuration information, the cell report configuration information instructing the UE to collect cell data associated with one or more cells in response to the satisfaction of the altitude condition, and sending the report includes sending a cell report including the cell data associated with the one or more cells.

[0252] Aspect 11: According to the method of aspect 10, the cell data is included in the ANR table.

[0253] Aspect 12: The method according to any one of Aspects 1 to 11, wherein sending the report comprises: sending UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

[0254] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the report is an RA report, a CEF report, an RLF report, an SHR, an SPR, or a report including SCG failure information.

[0255] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the data collected by the UE is recorded data, the method further comprising: sending an availability indication to the network entity indicating that the recorded data is available; and receiving a request for the recorded data based at least in part on the availability indication, wherein sending the report to the network entity is based at least in part on receiving the request for the recorded data.

[0256] Aspect 15: A method for wireless communication by a network entity, the method comprising: sending configuration information to a UE for sending a report of data collected by the UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on altitude conditions of the UE; and receiving the report from the UE according to the configuration information, wherein the report indicates data collected by the UE associated with the relationship information of the one or more network nodes in response to the satisfaction of the collection rules.

[0257] Aspect 16: According to the method of aspect 15, wherein the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the altitude of the UE satisfying the at least one altitude threshold.

[0258] Aspect 17: The method according to any one of Aspects 15 to 16, wherein sending the configuration information includes: sending information indicating a range of areas at least partially based on the altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the range of areas.

[0259] Aspect 18: According to the method of aspect 17, the configuration information further includes one or more cell indicators, and the data collected by the UE includes data collected by the UE for one or more cells associated with the one or more cell indicators.

[0260] Aspect 19: According to the method of aspect 18, the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE.

[0261] Aspect 20: The method according to any one of Aspects 15 to 19, wherein the collection rule is further based at least in part on signal quality conditions, the altitude conditions including at least one altitude threshold of the altitude of the UE, and the data collected by the UE includes data collected by the UE in response to the satisfaction of the signal quality conditions and the altitude of the UE satisfying the at least one altitude threshold.

[0262] Aspect 21: According to the method of aspect 20, receiving the report further includes: receiving data indicating one or more reference signals corresponding to one or more cells, wherein the data indicating one or more reference signals is collected by the UE in response to the satisfaction of the signal quality condition, the satisfaction of the signal quality condition including one or more metrics of the one or more reference signals satisfying a signal quality threshold.

[0263] Aspect 22: The method according to any one of Aspects 15 to 21, wherein the data collected by the UE lacks data associated with the restricted area and includes data associated with one or more areas outside the restricted area.

[0264] Aspect 23: According to the method of aspect 22, the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

[0265] Aspect 24: The method according to any one of Aspects 15 to 23, wherein sending the configuration information includes: sending cell report configuration information, the cell report configuration information instructing the UE to collect cell data associated with one or more cells in response to the satisfaction of the altitude condition, and receiving the report includes receiving a cell report including the cell data associated with the one or more cells.

[0266] Aspect 25: According to the method of aspect 24, the cell data is included in the ANR table.

[0267] Aspect 26: The method according to any one of Aspects 15 to 25, wherein receiving the report comprises: receiving UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

[0268] Aspect 27: The method according to any one of Aspects 15 to 26, wherein the report is an RA report, a CEF report, an RLF report, an SHR, an SPR, or a report including SCG failure information.

[0269] Aspect 28: The method according to any one of Aspects 15 to 27, wherein the data collected by the UE is recorded data, the method further comprising: receiving from the UE an availability indication indicating that the recorded data is available; and sending a request for the recorded data based at least in part on the availability indication, wherein receiving the report from the UE is based at least in part on sending the request for the recorded data.

[0270] Aspect 29: An apparatus for wireless communication, the apparatus comprising a memory, a transceiver, and at least one processor of a UE, the at least one processor being coupled to the memory and the transceiver, and the at least one processor being configured to cause the apparatus to perform a method according to any one of aspects 1 to 14.

[0271] Aspect 30: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 14.

[0272] Aspect 31: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 14.

[0273] Aspect 32: An apparatus for wireless communication, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to cause the apparatus to perform a method according to any one of aspects 15 to 28.

[0274] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 15 to 28.

[0275] Aspect 34: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 15 to 28.

[0276] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0277] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0278] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0279] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any 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, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor can be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0280] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0281] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0282] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0283] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0284] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0285] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0286] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0287] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication, the apparatus comprising: Memory; transceiver; and At least one processor of user equipment (UE), said at least one processor being coupled to the memory and the transceiver and configured to cause the device to: The transceiver receives configuration information from a network entity for sending a report of data collected by a UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on the UE's altitude conditions; as well as The transceiver sends the report to the network entity according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of the collection rules and associated with the relationship information of the one or more network nodes.

2. The apparatus of claim 1, wherein the altitude condition of the UE includes at least one altitude threshold of the UE's altitude, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the UE's altitude satisfying the at least one altitude threshold.

3. The apparatus according to claim 1, wherein, In order to receive the configuration information, the at least one processor is configured to cause the device to: The UE receives information indicating a region range based at least in part on the altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the region range.

4. The apparatus according to claim 3, wherein: The configuration information also includes one or more cell indicators, and The data collected by the UE includes data collected by the UE for one or more cells associated with the one or more cell indicators.

5. The apparatus of claim 4, wherein the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE, and wherein the at least one processor is further configured to cause the apparatus to: First data associated with one or more of the one or more cells is collected in response to the satisfaction of a first threshold among the at least one altitude threshold.

6. The apparatus according to claim 1, wherein: The collection rules are also based, at least in part, on signal quality conditions, including at least one altitude threshold for the UE's altitude. The data collected by the UE includes data collected by the UE in response to the satisfaction of the signal quality conditions and the UE's altitude satisfying the at least one altitude threshold.

7. The apparatus of claim 6, wherein the at least one processor is further configured to cause the apparatus to: Receive one or more reference signals corresponding to one or more cells, wherein the satisfaction of the signal quality condition includes one or more metrics of the one or more reference signals satisfying a signal quality threshold.

8. The apparatus of claim 1, wherein the at least one processor is further configured to cause the apparatus to: The UE is detected to enter a restricted area, wherein at least one processor is further configured to prevent the device from collecting data when it is in the restricted area, and to collect data collected by the UE when it is outside the restricted area.

9. The apparatus of claim 8, wherein the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

10. The apparatus according to claim 1, wherein: In order to receive the configuration information, the at least one processor is configured to cause the device to receive cell report configuration information, which instructs the UE to collect cell data associated with one or more cells in response to the satisfaction of the altitude conditions; and In order to send the report, the at least one processor is configured to cause the device to send a cell report including cell data associated with the one or more cells.

11. The apparatus of claim 10, wherein the cell data is included in an automatic neighbor relationship table.

12. The apparatus according to claim 1, wherein, In order to send the report, the at least one processor is configured to cause the device to: Send UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

13. The apparatus of claim 1, wherein the report is a random access report, a connection establishment failure report, a radio link failure report, a successful handover report, a successful primary / secondary cell change report, or a report including secondary cell group failure information.

14. The apparatus of claim 1, wherein the data collected by the UE is recorded data, and wherein the at least one processor is further configured to cause the apparatus to: Send an availability indication to the network entity indicating the availability of the data recorded; and The at least one processor is configured to receive a request for data on the record based at least in part on the availability indication, wherein the at least one processor is configured to send the report to the network entity based at least in part on the receipt of the request for data on the record.

15. An apparatus for wireless communication, the apparatus comprising: Memory; and At least one processor of the network entity, said at least one processor being coupled to the memory and configured to cause the device to: Send configuration information to the user equipment (UE) for sending a report of data collected by the UE in association with relationship information and collection rules associated with one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on the UE's altitude conditions; as well as The report is received from the UE according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of the collection rules and associated with the relationship information of the one or more network nodes.

16. The apparatus of claim 15, wherein the altitude condition of the UE includes at least one altitude threshold of the altitude of the UE, and the data collected by the UE includes handover data or cell change data collected by the UE in response to the altitude of the UE satisfying the at least one altitude threshold.

17. The apparatus according to claim 15, wherein, In order to send the configuration information, the at least one processor is configured to cause the device to: The system transmits information indicating a region range based at least in part on the altitude conditions, wherein the data collected by the UE includes data collected by the UE in response to the satisfaction of the region range.

18. The apparatus according to claim 17, wherein: The configuration information also includes one or more cell indicators, and The data collected by the UE includes data collected by the UE for one or more cells associated with the one or more cell indicators.

19. The apparatus according to claim 18, wherein: The altitude condition of the UE includes at least one altitude threshold of the UE's altitude.

20. The apparatus according to claim 15, wherein: The collection rules are also based, at least in part, on signal quality conditions, including at least one altitude threshold for the UE's altitude. The data collected by the UE includes data collected by the UE in response to the satisfaction of the signal quality conditions and the UE's altitude satisfying the at least one altitude threshold.

21. The apparatus according to claim 20, wherein, In order to receive the report, the at least one processor is configured to cause the device to: Receive data indicating one or more reference signals corresponding to one or more cells, wherein the data indicating one or more reference signals is collected by the UE in response to the satisfaction of a signal quality condition, the satisfaction of the signal quality condition including one or more metrics of the one or more reference signals satisfying a signal quality threshold.

22. The apparatus of claim 15, wherein the data collected by the UE lacks data associated with a restricted area and includes data associated with one or more areas outside the restricted area.

23. The apparatus of claim 22, wherein the data collected by the UE includes first data indicating entry into the restricted area, second data indicating exit from the restricted area, third data indicating that the UE is within a certain distance from the restricted area, or any combination thereof.

24. The apparatus according to claim 15, wherein: In order to send the configuration information, the at least one processor is configured to cause the device to send cell report configuration information, which instructs the UE to collect cell data associated with one or more cells in response to the satisfaction of the altitude conditions; and In order to receive the report, the at least one processor is configured to cause the device to receive a cell report that includes cell data associated with the one or more cells.

25. The apparatus of claim 24, wherein the cell data is included in an automatic neighbor relationship table.

26. The apparatus according to claim 15, wherein, In order to receive the report, the at least one processor is configured to cause the device to: Receive UE characteristic data associated with the UE, altitude data associated with the UE, detected airborne UE density data, or any combination thereof.

27. The apparatus of claim 15, wherein the report is a random access report, a connection establishment failure report, a radio link failure report, a successful handover report, a successful primary / secondary cell change report, or a report including secondary cell group failure information.

28. The apparatus of claim 15, wherein the data collected by the UE is recorded data, and wherein the at least one processor is further configured to cause the apparatus to: Receive from the UE an availability indication indicating the availability of the recorded data; and The at least one processor is configured to send a request for data on the record based at least in part on the availability indication, wherein the device receives the report from the UE based at least in part on the request for data on the record.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive configuration information from network entities for sending reports of data collected by a UE associated with relationship information and collection rules of one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on the UE's altitude conditions; as well as The report is sent to the network entity according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of the collection rules and associated with the relationship information of the one or more network nodes.

30. A method for wireless communication by a network entity, the method comprising: Send configuration information to the user equipment (UE) for sending a report of data collected by the UE in association with relationship information and collection rules associated with one or more network nodes, wherein the UE is an airborne UE and the collection rules are based at least in part on the UE's altitude conditions; as well as The report is received from the UE according to the configuration information, wherein the report indicates data collected by the UE in response to the satisfaction of the collection rules and associated with the relationship information of the one or more network nodes.

Images