Flight path based user equipment autonomous timing advance compensation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send flight path information indicating a planned flight path for the UE to a network node. The UE may receive, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information. The UE may transmit uplink communications to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that the at least one application criterion is satisfied. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 365,672, filed on June 1, 2022, entitled “FLIGHT PATH BASED USER EQUIPMENT AUTONOMOUS TIMING ADVANCE COMPENSATION,” and U.S. Non-Provisional Patent Application No. 18 / 322,273, filed on May 23, 2023, entitled “FLIGHT PATH BASED USER EQUIPMENT AUTONOMOUS TIMING ADVANCE COMPENSATION,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for flight path based user equipment (UE) autonomous timing advance compensation. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to send flight path information indicating a planned flight path of the UE to a network node. The one or more processors may be configured to receive timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information from the network node. The one or more processors may be configured to send an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that the at least one application criterion is satisfied.

[0008] Some aspects described herein relate to a network node for wireless communications. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive flight path information indicating a planned flight path of the UE from a UE. The one or more processors may be configured to send to the UE timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information. The one or more processors may be configured to receive uplink communications from the UE using a timing advance based at least in part on the timing advance compensation configuration information and at least one application standard.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending flight path information indicating a planned flight path of the UE to a network node. The method may include receiving, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information. The method may include, in conjunction with a determination that the at least one application criterion is satisfied, sending an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving flight path information from a UE indicating a planned flight path of the UE. The method may include sending, to the UE, timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information. The method may include receiving an uplink communication from the UE using a timing advance based at least in part on the timing advance compensation configuration information and the at least one application standard.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send flight path information indicating a planned flight path of the UE to a network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information from the network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to send uplink communications to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that at least one application standard is satisfied.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive flight path information indicating a planned flight path of the UE from a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to send to the UE timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive uplink communications from the UE using a timing advance based at least in part on the timing advance compensation configuration information and at least one application standard.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending flight path information indicating a planned flight path to a network node. The apparatus may include means for receiving, from the network node, timing advance compensation configuration information associated with the planned flight path and an indication of at least one application criterion associated with the timing advance compensation configuration information. The apparatus may include means for sending an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that the at least one application criterion is satisfied.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving flight path information indicating a planned flight path of the UE from a UE. The apparatus may include means for sending, to the UE, timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information. The apparatus may include means for receiving uplink communications from the UE using a timing advance based at least in part on the timing advance compensation configuration information and the at least one application standard.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be implemented in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of an unmanned aerial vehicle (UAV) UE in a wireless communication network environment according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of downlink and uplink transmission between a network node and a UE in a wireless network according to the present disclosure.

[0024] Figure 6 to Figure 7 is a diagram illustrating an example associated with flight path-based UE autonomous timing advance compensation according to the present disclosure.

[0025] Figures 8 to 9 is a diagram illustrating an example process associated with flight path based UE autonomous timing advance compensation according to the present disclosure.

[0026] Figure 10 to Figure 11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0032] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0033] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0034] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0037] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles (UAVs) (e.g., drones), remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0042] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0043] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may send flight path information indicating a planned flight path for the UE to a network node; receive from the network node timing advance compensation configuration information associated with the planned flight path for the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information; and in conjunction with a determination that the at least one application criterion is satisfied, send an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0045] In some aspects, the network node 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may receive flight path information from the UE indicating a planned flight path for the UE; send to the UE timing advance compensation configuration information associated with the planned flight path for the UE and an indication of at least one application standard associated with the timing advance compensation configuration information; and receive uplink communications from the UE using a timing advance based at least in part on the timing advance compensation configuration information and the at least one application standard. In some aspects, the communications manager 150 may also send to the first UE and the second UE second level shared information for deriving a security key from the common sidelink information. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0047] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0048] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0052] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 6 to 11 ) any aspects of any of the methods described herein.

[0053] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform the functions described herein (e.g., reference 20). Figures 6 to 11 ) any aspects of any of the methods described herein.

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0055] In some aspects, a UE (e.g., UE 120) includes: means for sending flight path information indicating a planned flight path of the UE to a network node; means for receiving timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information from the network node; and / or means for sending an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that at least one application criterion is satisfied. Means for the UE to perform operations described herein may include, for example, one or more of the following: communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0056] In some aspects, a network node (e.g., network node 110) includes: means for receiving flight path information indicating a planned flight path of the UE from a UE; means for sending timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information to the UE; and / or means for receiving uplink communications from the UE using a timing advance based at least in part on the timing advance compensation configuration information and at least one application standard. In some aspects, means for the network node to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0057] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0059] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5GNR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0060] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0062] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0063] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, or to perform both.

[0064] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0065] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split, such as a functional split defined by 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0066] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0067] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0068] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0069] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0070] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0071] Figure 4 4 is a diagram illustrating an example 400 of a UAV UE in a wireless communication network environment according to the present disclosure. Figure 4 As shown, example 400 includes a network node 110 and a UAV UE 120 (also referred to herein as UAV 120 ).

[0072] UAV 120 includes an aircraft without a human pilot and may also be referred to as an unmanned aircraft (UA), a drone, a remotely piloted vehicle (RPV), a remotely piloted aircraft (RPA), a remotely operated aircraft (ROA), or an unmanned aerial vehicle. UAV 120 may have various shapes, sizes, configurations, characteristics, etc. for various purposes and applications. In some implementations, UAV 120 may include one or more sensors, such as electromagnetic spectrum sensors (e.g., visual spectrum, infrared or near infrared cameras, radar systems, etc.), biosensors, temperature sensors, and / or chemical sensors, etc. UAV 120-1 may include one or more components for communicating with one or more network nodes 110.

[0073] The UAV 120 may communicate with the network node 110 via a Uu interface. For example, the UAV 120-1 may send uplink communications to the network node 110 and / or receive downlink communications from the network node 110 via the Uu interface. Such Uu connectivity may be used to support different applications for the UAV 120-1, such as video transmission from the UAV 120-1 or C2 communications for remote command and control of the UAV 120-1, etc.

[0074] like Figure 4As shown, in some examples, network node 110 may send a request for flight path information to UAV 120. UAV 120 may receive the request for flight path information, and if the flight path information is available at UAV 120, UAV 120 may send the flight path information to network node 110. In some examples, to reduce unnecessary signaling, UAV 120 may indicate to network node 110 whether UAV 120 has available flight path information (e.g., when initiating an RRC connection between UAV 120 and network node 110). The flight path information may indicate a planned or expected flight path of UAV 120. In some examples, the flight path information may include a set of waypoints ( and the corresponding timestamp ( .Waypoint( Indicates the planned or estimated location of the UAV 120 and a timestamp ( Instructs the UAV 120 to move to the corresponding waypoint ( For example, if Figure 4 As shown, Indicates the location and expected arrival time of the first waypoint (waypoint 1), Indicates the location and expected arrival time of the second waypoint (waypoint 2), indicates the location and expected arrival time of the third waypoint (waypoint 3), and The location and expected arrival time of the fourth waypoint (Waypoint 4) is indicated. In some examples, the network can use the flight path information to track how many UAVs are to be serviced in the area at a given time.

[0075] As indicated above, Figure 4 is provided as an example 400 of a UAV. Other examples may be related to Figure 4 Different than described.

[0076] Figure 5 1 is a diagram illustrating an example 500 of downlink and uplink transmissions between a network node 110 and a UE 120 in a wireless network 100 according to the present disclosure. In some examples, the downlink and / or uplink transmissions are based at least in part on a timing advance and / or a protection period between communications. As an example, the network node 110 may configure the downlink transmission to end before the guard period begins. As another example, the UE 120 may advance the start time of the uplink transmission based at least in part on the timing advance.

[0077] As shown by reference numeral 502-1, the network node 110 may start downlink transmission 504-1 to the UE 120 at a first point in time. In some examples, the first point in time may be based at least in part on a timing scheme defined by a telecommunication system and / or a telecommunication standard. For illustration, a telecommunication standard may define various time divisions for scheduling transmissions between devices. As an example, a timing scheme may define radio frames (sometimes referred to as frames), wherein each radio frame has a predetermined duration (e.g., 10 milliseconds (msec)). Each radio frame may be further divided into a group of Z (Z ≥ 1) subframes, wherein each subframe may have a predetermined duration (e.g., 1 msec). Each subframe may be further divided into a group of time slots and / or each time slot may include a group of L symbol periods (e.g., fourteen symbol periods, seven symbol periods, or another number of symbol periods). Therefore, the first point in time shown by reference numeral 502-1 may be based at least in part on a time division (e.g., frame, subframe, time slot, mini-time slot, and / or symbol) defined by a telecommunication system.

[0078] In some examples, the network node 110 and the UE 120 may communicate with each other wirelessly based at least in part on the defined time division. However, each device may have a different timing reference for the time division. For illustration, and as shown by reference numeral 502-1, the network node 110 may start a downlink transmission 504-1 at a specific physical time point, which may be associated with the defined time division based at least in part on the time angle of the network node 110. For example, the network node 110 may associate a specific physical time point with a defined time division (such as the start of a symbol, the start of a time slot, the start of a subframe, and / or the start of a frame). However, the downlink transmission may cause a propagation delay 506 in physical time, such as a time delay of the downlink transmission traveling between the network node 110 and the UE 120 based at least in part. As shown by reference numeral 502-2, UE 120 may receive downlink transmission 504-2 (corresponding to downlink transmission 504-1 transmitted by network node 110) at a second physical point in time that is later in time relative to the first physical point in time. However, from the time perspective of UE 120, UE 120 may associate the second physical point in time shown by reference numeral 502-2 with a specific point in time of the same defined time partition as network node 110 (e.g., the start of the same symbol, the start of the same mini-slot, the start of the same slot, the start of the same subframe, and / or the start of the same frame). Therefore, as shown in example 500, the time perspective of UE 120 may be delayed in physical time from the time perspective of network node 110.

[0079] In wireless communication technologies such as 4G / LTE and 5G / NR, a timing advance (TA) value is used to control the timing of uplink transmissions of a UE (e.g., UE 120) so that a network node (e.g., network node 110) receives the uplink transmission at a time that is aligned with the internal timing of the network node. The network node may reduce or eliminate the time difference and align the timing between the UE and the network node by measuring the time difference between the uplink transmission received from the UE and the subframe timing used by the network node (e.g., by determining the difference between the time when the network node should receive the uplink transmission according to the subframe timing and the time when the uplink transmission is actually received) and indicating the TA value to the UE by sending a TA command (TAC) to instruct the UE to advance or postpone the transmission of future uplink communications. The TA command is used to offset the timing difference between the UE and the network node due to different propagation delays that occur when the UE is at different distances from the network node. If the TA command is not used, even if the uplink transmissions are scheduled for different subframes, uplink transmissions from different UEs (e.g., located at different distances from the network node) may collide due to mis-timing.

[0080] For illustration, without adjusting the start time of the uplink transmission, the UE 120 may be configured to start the uplink transmission at the scheduled time point based at least in part on the defined time division as described elsewhere herein. As shown by reference numeral 510-1, the start of the scheduled time point may occur at a third physical time point based at least in part on the timing angle of the UE 120. However, and as shown by reference numeral 510-2, the scheduled time point with reference to the timing angle of the network node 110 may occur at a fourth physical time point that occurs before the third physical time point as shown by reference numeral 510-1. Therefore, the network node 110 may instruct the UE 120 to apply the timing advance 508 to the uplink transmission to better align the reception of the uplink transmission with the timing angle of the network node 110. However, in some examples, the fourth time point shown by reference numeral 510-2 may occur at or near the same physical time point as the third time point shown by reference numeral 510-1, such that uplink transmission from UE 120 to network node 110 causes propagation delay 506. In such a scenario, network node 110 may instruct UE 120 to apply a timing advance having a duration corresponding to propagation delay 506.

[0081] As shown in example 500, UE 120 may adjust the start time of uplink transmission 512-1 based at least in part on timing advance 508 and the start of the scheduled time point (e.g., at a third physical time point shown by reference numeral 510-1). Based at least in part on the propagation delay, network node 110 may receive uplink transmission 512-2 (corresponding to uplink transmission 512-1 sent by UE 120) at a fourth physical time point shown by reference numeral 510-2.

[0082] In some examples, the timing advance value may be based at least in part on twice the estimated propagation delay (e.g., propagation delay 506) and / or may be based at least in part on a round trip time (RTT). The network node 110 may estimate the propagation delay and / or select the timing advance value based at least in part on communications with the UE 120. As an example, the network node 110 may estimate the propagation delay based at least in part on a network access request message from the UE 120. Additionally or alternatively, the network node 110 may estimate and / or select the timing advance value from a set of fixed timing advance values.

[0083] In some cases, such as in a random access response or an absolute TAC MAC control element to indicate Value, where the subcarrier spacing (SCS) is The time alignment of the TAG in kHz is In this case, the indicated The value may be relative to the SCS of the first uplink transmission from the UE after receiving a random access response (including TAC) or an absolute TAC MAC-CE. In other cases, the TAC of the TAG ( ) can indicate the current value( ) to New value( ). For example, TAC ( ) can be obtained by indexing the value to indicate the adjustment, where kHz SCS, .

[0084] In some examples, the UE may have the ability to track frame timing changes of a reference cell in a connected state. In this case, the UE's uplink transmission may occur before (in time) the first detected path of the corresponding downlink frame is received from the reference cell. ,in is the TA offset value, and Is the basic timing unit. TA offset value ( ) may be a constant having a value associated with the duplex mode and frequency range of the cell in which uplink transmissions occur. It can be defined as ,in Hz and .

[0085] In some examples, the telecommunications system and / or telecommunications standard may define a protection period 514 (e.g., duration) between transmissions to provide sufficient time for the device to switch between different transmission and / or reception modes, for transient stabilization, for timing misalignment between devices, and / or for providing margin for propagation delays. In some examples, a protection period is a period during which no transmission or reception is scheduled and / or allowed to occur. The protection period may provide the device with sufficient time to reconfigure hardware and / or allow the hardware to stabilize within a threshold to enable subsequent transmissions. The protection period 514 may sometimes be referred to as a gap, a switching protection period, or a guard interval.

[0086] In some examples, a transmitting device (e.g., network node 110) may select a start transmission time and / or a transmission duration based at least in part on a receiving device and / or a protection period. For example, network node 110 may select an amount of content (e.g., data and / or control information) to be transmitted in downlink transmission 504-1 based at least in part on starting transmission at a first physical time point shown by reference numeral 502-1 and / or UE 120 completing reception of downlink transmission 504-2 before a start point of protection period 514. Alternatively or additionally, UE 120 may select an amount of content (e.g., data and / or control information) to be transmitted in uplink transmission 512-1 based at least in part on timing advance 508, a third physical time point shown by reference numeral 510-1, and / or avoiding starting uplink transmission 512-1 until protection period 514 has ended.

[0087] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0088] In some cases, a network node may serve both terrestrial UEs (e.g., cellular phones, smart phones), wireless communication devices, vehicle components, or any other non-UAV UEs and UAV UEs. A terrestrial UE may be a UE other than a UAV UE, such as a cellular phone (e.g., smart phone), a wireless communication device, a vehicle component, or any other non-UAV UE. In some cases, an aerial cell providing coverage for a UAV UE may be larger than a terrestrial cell providing coverage for a terrestrial UE. However, the greater distance between a network node and a UAV UE compared to a terrestrial UE may result in a PRACH-based closed-loop TA control (e.g., as described above in conjunction with Figure 5 The PRACH-based closed-loop TA control described above is not effective for UAV UEs. For example, PRACH-based closed-loop TA control for terrestrial UEs may result in a UE transmit power limit that is too low for UAV UEs. In this case, if the same PRACH format configured for terrestrial UEs is reused for UAV UEs, the maximum ranging distance of the UAV UEs may be limited. In addition, using a separate PRACH format for UAV UEs would require large signaling overhead for TA updates (e.g., to cover a large beam coverage area and frequent TA updates), which would result in inefficient utilization of network resources.

[0089] Some techniques and apparatus described herein enable a network node to configure a UE (e.g., a UAV UE) to perform autonomous TA adjustments based at least in part on a planned flight path of the UE. In some aspects, the UE may send flight path information indicating the planned flight path of the UE to the network node. The UE may receive, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information. In conjunction with a determination that at least one application criterion is met, the UE may send uplink communications to the network node using a timing advance based at least in part on the timing advance compensation configuration information. Thus, once at least one application criterion is met, the UAV UE may autonomously adjust the TA value based on the flight of the UAV UE.

[0090] Figure 6 6 is a diagram illustrating an example 600 associated with UE autonomous TA compensation based on flight path according to the present disclosure. Figure 6 As shown in , example 600 includes communication between a network node 110 and a UE 120. In some aspects, the UE 120 may be a UAV UE. The network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0091] like Figure 6As shown, and by reference numeral 605, UE 120 may send flight path information indicating a planned flight path of UE 120 to network node 110. Network node 110 may receive the flight path information sent by UE 120. In some aspects, the flight path information may include waypoints ( A collection of waypoints ( A series of planned or projected locations of UE 120 may be indicated, which define a planned flight path for UE 120. In some aspects, the flight path information may also include corresponding waypoints ( Timestamp( . Timestamp( The corresponding waypoints ( The expected arrival time at the destination.

[0092] like Figure 6 As further shown in FIG. 1 and by reference numeral 610, the network node 110 may send TA compensation configuration information and an indication of at least one application criterion associated with the TA compensation configuration information to the UE 120. The UE 120 may receive the TA compensation configuration information and the indication of the at least one application criterion sent by the network node 110. The TA compensation configuration information may be associated with a planned flight path of the UE 120. For example, the network node 110 may determine the TA compensation configuration information based at least in part on the planned flight path of the UE 120.

[0093] The TA compensation configuration information may include a set of parameters for configuring the UE 120 to perform autonomous TA compensation. In some aspects, the TA compensation configuration information may indicate parameters for configuring the UE 120 to determine semi-open loop TA when at least one application criterion is met. For example, the TA compensation configuration information may indicate parameters of a polynomial or a set of values ​​to be used by the UE 120 to determine a configured TA compensation value when at least one application criterion is met.

[0094] At least one application criterion (hereinafter referred to as "application criterion") may include one or more criteria to be satisfied by UE 120 applying TA compensation configuration information when determining the TA for uplink communication. In some aspects, network node 110 may determine the application criterion based at least in part on the planned flight path of UE 120. In some aspects, the application criterion may include a reference altitude. In this case, the application criterion may be satisfied when UE 120 is at or above the reference altitude. For example, the reference altitude may be defined as a height above ground level, an altitude above sea level, or a height corresponding to a location (x, y, z) on the planned flight path of UE 120.

[0095] In some aspects, the application criteria may include a duration for applying the timing advance compensation configuration information. For example, the application criteria may include an indication of a validity timer having a duration that determines how long the parameters included in the TA compensation configuration information may be used by the UE 120 for autonomous TA compensation.

[0096] In some aspects, the application criteria may include a reference time to begin applying the timing advance compensation configuration information. For example, the reference time may correspond to the time at which the UE 120 is expected to arrive at a particular altitude (e.g., a reference altitude) or location on the planned flight path. In some aspects, the reference time may be an absolute time (e.g., Coordinated Universal Time (UTC)). In some aspects, the reference time may be an epoch time from a particular starting point (e.g., an epoch time from when the flight path information was sent by the UE 120).

[0097] In some aspects, the application criteria may include a reference location on the planned flight path of UE 120 at which to begin applying the timing advance compensation configuration information. For example, the reference location may be a location where UE 120 reaches a particular altitude (e.g., a reference altitude) on the planned flight path. In some aspects, where the application criteria include the reference location, the determination of whether the application criteria is met may be based at least in part on a comparison of the reference location with a location on the planned flight path of UE 120 that is closest to the current location of UE 120.

[0098] In some aspects, the application criteria may include a threshold for the distance of UE 120 from a reference location on the planned flight path along the planned flight path of UE 120. In this case, the determination of whether the application criteria is met may be based at least in part on the distance between the reference location and the location on the planned flight path of UE 120 that is closest to the current location of UE 120.

[0099] In some aspects, the application criteria may include a reference area along the planned flight path of the UE 120 at which to begin applying the timing advance compensation configuration information. For example, the reference area may be one of a plurality of configured areas (e.g., geographic areas) along the planned flight path of the UE 120.

[0100] In some aspects, the timing advance compensation configuration information indicates parameters of a polynomial used to determine configured TA values ​​for one or more uplink transmissions along a planned flight path of the UE 120 (e.g., when application criteria are met). In some aspects, the TA compensation configuration information may indicate a set of configured TA values ​​associated with the planned flight path of the UE 120. The configured TA values ​​( ) may be a TA value used by the UE 120 for autonomous TA compensation, and the configured TA value ( ) can also be called the "configured TA compensation value".

[0101] In some aspects, the TA compensation configuration information may indicate a TA compensation value used to determine the configuration For example, for feeder links in non-terrestrial networks, the same TA values ​​used to derive common TA values ​​can be used. The parameters are similar to the parameters used to determine the In some aspects, the TA compensation configuration information may indicate a time function to be used with the configured TA compensation value. For example, the reference feed may be configured by the network node 110 for the UE 120 based at least in part on a planned flight path of the UE 120. In this case, the UE 120 may determine the configured TA compensation value based at least in part on the reference speed using a time function. .

[0102] In some aspects, the TA compensation configuration information indicates a TA compensation value used to determine the configuration A function of the distance (e.g., in polynomial format or as a set of values) of the distance. For example, to determine the TA compensation value of the configuration The function of may be a function of the distance of UE 120 along the planned flight path. In some aspects, the function may be a function of the distance from a reference location on the planned flight path of UE 120 to a location on the planned flight path that is closest to the location of UE 120. In some aspects, the function may be a function of the integrated distance traveled by UE 120 on the planned flight path. In this case, the integrated distance at a particular time may be the integrated distance on the planned flight path to a location on the planned flight path that is closest to the actual location of UE 120 at that time.

[0103] In some aspects, the TA compensation configuration information may indicate a function of a location associated with the UE 120 for determining a configured TA compensation value. In some aspects, the TA compensation value for determining the configuration The function of may be based at least in part on a central location of an area in which the UE 120 is located among a plurality of areas along the planned flight path. In some aspects, the function used to determine the TA compensation value The function of may be based at least in part on the planned flight path closest to the location of UE 120. In some aspects, the TA compensation value used by UE 120 to determine the configuration at time slot N is The position (x, y, z) may be the distance from the UE 120 at time NT on the planned flight path (or preconfigured flight path). x The actual position of the nearest position (x, y, z). In this case, T x may be a non-zero value autonomously selected by UE 120 based at least in part on an expected flight speed of UE 120 .

[0104] In some aspects, the TA compensation configuration information may indicate a reference location of the network node 110, which may be used by the UE 120 to derive a propagation delay between the network node 110 and the UE 120. In this case, when the applicable criteria are met, the UE 120 may determine the autonomous TA compensation value based at least in part on the reference location of the network node 110. For example, UE 120 may derive a propagation delay between network node 110 and UE 120 based at least in part on a reference location of network node 110 and a location of UE 120, and UE 120 may determine based at least in part on the propagation delay between network node 110 and UE 120. . for determining using a reference location indicated by the network node 110 The application criteria may be based at least in part on a reference altitude, a reference time, a reference location on a planned flight path, a reference area, or any combination thereof. In some aspects, where the TA compensation configuration information indicates a reference location of the network node 110 and the application criteria is based at least in part on a reference area, the reference area may be defined using a distance and an azimuth / elevation angle from the reference location.

[0105] like Figure 6 As further shown in FIG. 1 and by reference numeral 615, the UE 120 may determine whether activation criteria (e.g., at least one activation criteria) are met. In some aspects, the UE 120 may determine whether the activation criteria are met in conjunction with calculating the TA for the scheduled uplink communication. For example, the UE 120 may determine whether the activation criteria are met before calculating the TA for the scheduled uplink communication.

[0106] As indicated by reference numeral 620, UE 120 may calculate a TA for uplink communications. In some aspects, UE 120 may calculate a TA for uplink communications based at least in part on a determination of whether application criteria are met.

[0107] In some aspects, in conjunction with determining that the application criteria are met, the UE 120 may calculate the TA based at least in part on the TA compensation configuration information. In this case, the UE 120 may determine the autonomous TA compensation value (e.g., or ), and UE 120 may determine the TA compensation value based at least in part on the autonomous TA compensation value (e.g., or ) adjust the closed loop TA value (for example, ).

[0108] In some aspects, the TA compensation configuration information may indicate a TA compensation value used to determine the configuration For example, to determine the TA compensation value for a configuration The function of may be a function of time, a function of the distance along the planned flight path traveled by the UE 120, or a function of the location of the UE 120, as described above. In this case, when the activation criteria are met, the UE 120 may calculate the total TA (e.g., combined semi-open-loop and closed-loop TA) as: ,in is a closed-loop TA value (e.g., based at least in part on one or more TACs, as described above in conjunction with Figure 5 described), is a configured TA compensation value determined by UE 120 based at least in part on the TA compensation configuration information, and is a constant / static TA offset value. Using the calculated TA, UE 120 can determine the uplink transmit (Tx) timing as: Uplink Tx timing = Downlink receive (Rx) timing - - - ,in is an open-loop (or semi-open-loop) TA, is a closed-loop TA, and is a static TA. In some aspects, UE 120 may perform loop control for semi-open-loop and closed-loop TAs as follows: a reset may be sent for each uplink ; The signal may be transmitted on multiple uplinks (e.g., based at least in part on The difference adjustment of can be accumulated); and Can remain constant.

[0109] In some aspects, the TA compensation configuration information may indicate a reference location of the network node 110, as described above. In this case, when the activation criteria are met, the UE 120 may calculate the total TA (e.g., combined semi-open loop and closed loop TA) as: ,in is the closed-loop TA value, is an autonomous TA compensation value determined by UE 120 based at least in part on a reference location indicated by the TA compensation configuration information, and is a constant / static TA offset value. Using the calculated TA, UE 120 can determine the uplink Tx timing as: Uplink Tx timing = Downlink Rx timing - - - ,in is an open-loop (or semi-open-loop) TA, is a closed-loop TA, and is a static TA. In some aspects, UE 120 may perform loop control for semi-open-loop and closed-loop TAs as follows: a reset may be sent for each uplink ; The signal may be transmitted on multiple uplinks (e.g., based at least in part on The difference adjustment of can be accumulated); and Can remain constant.

[0110] In some aspects, in conjunction with the determination that the application criteria are not met, UE 120 may use closed-loop TA ( ) and static TA ( ) to calculate TA without the need for open-loop (or semi-open-loop) TA (e.g., =0). In this case, the UE 120 may calculate the TA for uplink communication without using the autonomous TA compensation value determined by the TA compensation configuration information.

[0111] In some aspects, UE 120 may adjust loop control of TA calculation in conjunction with transitions between different states of the application criteria. In some aspects, for an uplink transmission that is the first uplink transmission after a transition from not meeting the application criteria to meeting the application criteria (e.g., having a non-zero ), UE 120 may reset the closed-loop TA ( ). In some aspects, for an uplink transmission that is the first uplink transmission after a transition from satisfying the application criteria to not satisfying the application criteria, the UE 120 may not update and applies the latest value updated before applying the standard state transition .

[0112] like Figure 6As further shown in FIG. 1 and by reference numeral 625, the UE 120 may send uplink communications to the network node 110 using the TA calculated by the UE 120 for the uplink communications. In some aspects, the UE 120 may use a TA (e.g., having a non-zero TA) determined at least in part based on the TA compensation configuration information if the application criteria are met. In some aspects, the uplink communication may be a PRACH transmission, and the UE 120 may compensate the TA determined at least in part based on the TA compensation configuration information (e.g., having a non-zero TA) in conjunction with a determination that the application criteria are met. In some aspects, if the application criteria are not met, the UE 120 may use a closed loop TA (e.g., where ) Determine the uplink Tx timing for uplink communication.

[0113] In some aspects, the UE 120 may be configured with a parameter indicating a maximum allowable deviation of the location of the UE 120 from the planned flight path indicated by the flight path information reported by the UE 120 to the network node 110. For example, the network node 110 may send, and the UE 120 may receive, an indication of a threshold for the deviation of the location of the UE 120 from the planned flight path. In some aspects, the network node 110 may send the indication of the threshold to the UE 120 along with the TA compensation configuration information and the indication of the applicable criteria. In some aspects, the UE 120 may determine whether the deviation between the actual location of the UE 120 (or the expected location of the UE 120) and the planned flight path meets the threshold (e.g., exceeds the threshold). For example, the UE 120 may determine the deviation as the distance between the location of the UE 120 and the nearest point on the planned flight path of the UE 120, or the UE 120 may determine the deviation as the distance between the location of the UE 120 at a particular time and the expected location (e.g., a waypoint or an interpolated point between waypoints) on the planned flight path at that time. In some aspects, in conjunction with a determination that a deviation between the location of the UE 120 and the planned flight path satisfies a threshold, the UE 120 may send a request to the network node 110 to reconfigure the TA compensation configuration information. In some aspects, in conjunction with a determination that a deviation between the location of the UE 120 and the planned flight path satisfies a threshold, the UE 120 may also send an updated flight path to the network node 110. In some aspects, in the event that the deviation between the location of the UE 120 and the planned flight path satisfies the threshold, the UE 120 may send a PRACH transmission to the network node 110 that applies a TA value derived at least in part based on the TA compensation configuration information (e.g., a configured TA compensation value) plus an additional offset value. In this case, the additional offset value may be applied to prevent the PRACH transmission from arriving at the network node 110 earlier than an ideal receive slot boundary. The additional offset value may be configured by the network node 110 for the UE 120 or defined in a wireless communication standard.

[0114] In some aspects, the UE 120 may be configured with multiple sets of parameters in the TA compensation configuration information. In some aspects, the TA compensation configuration information received from the network node 110 may include multiple sets of parameters, where different sets of parameters are associated with different cells and / or different synchronization signal blocks (SSBs). For example, the TA compensation configuration information may include at least first timing advance compensation configuration information associated with a first cell or a first SSB and second timing advance compensation configuration information associated with a second cell or a second SSB. In the case where the UE 120 performs a handover from one cell (e.g., a source cell) to another cell (e.g., a target cell), or in the case where the UE 120 is served by multiple cells and / or SSBs, the UE 120 may derive a TA value to be applied to the uplink transmission based at least in part on a cell identifier (ID) and / or SSB ID associated with the uplink transmission. In some aspects, in the case where the first uplink transmission to the new cell is a PRACH transmission, an additional offset value may be applied to the TA value (e.g., to prevent the PRACH transmission from arriving at the network node 110 before the slot boundary). In this case, the additional offset value may be a common value across cells, or the additional offset value may be specific to the PRACH format used. In some aspects, the UE may reset the accumulated closed-loop TA value (e.g., N ) when switching to a target cell. TA ). In some aspects, when an uplink transmission from UE 120 is intended to be received by multiple cells, selecting the TA among multiple values ​​of the target cell can be based at least in part on the signal strength of the cells and / or the distance from the UE 120 to the cells. For example, UE 120 can determine the TA value using TA compensation configuration information associated with the cell with the strongest RSRP and / or the cell with the closest distance to UE 120. In this case, the cumulative closed-loop TA value to be applied can be determined based at least in part on the cell corresponding to the selected TA.

[0115] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0116] Figure 7 is a diagram illustrating an example 700 associated with UE autonomous TA compensation based on flight path according to the present disclosure. Figure 7 As shown, example 700 includes a network node 110 and a UAV UE 120. The network node 110 may provide ground coverage for one or more ground UEs, and the network node 110 may provide aerial coverage for one or more UAV UEs, such as UAV UE 120. The UAV UE may send flight path information to the network node 110 indicating a planned flight path. Figure 7The planned flight path 702 of the UAV UE 120 and the boundary 704 of the actual flight path of the UAV UE 120 are shown.

[0117] In some aspects, the activation criteria may be based at least in part on a reference altitude 706 or a reference point 708 on the planned flight path 702. Figure 7 As shown, reference point 708 may be a point on planned flight path 702 where UAV UE 120 is expected to reach a reference altitude. In some aspects, activation criteria may be met when the UE is at or above reference altitude 706 (or when the UE passes through reference point 708 on planned flight path 702).

[0118] like Figure 7 As shown, when the UAV UE 120 is below the reference altitude 706, the UAV UE 120 may use a closed loop TA (e.g., wherein For example, in conjunction with a determination that the activation criteria are not met (eg, the UAV UE 120 is below the reference altitude 706), the UAV UE 120 may send a first uplink communication 710 using a closed-loop TA. Figure 7 As shown, when the UAV UE 120 is at or above the reference altitude 706, the UAV UE 120 may use semi-open loop and closed loop TA (e.g., a TA determined at least in part based on the TA compensation configuration information) for uplink communication. For example, when the UAV UE 120 is above the reference altitude, the UAV UE 120 may send a second uplink communication 712 and a third uplink communication 714 using respective TAs determined using semi-open loop and closed loop TA (e.g., based at least in part on the TA compensation configuration information).

[0119] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0120] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example of a UE (eg, UE 120) performing operations associated with flight path based UE autonomous timing advance compensation.

[0121] like Figure 8 As shown, in some aspects, process 800 may include sending flight path information indicating a planned flight path of the UE to a network node (block 810). For example, a UE (e.g., using Fig.10 The communication manager 140 and / or the sending component 1004 depicted in FIG. 1004 may send flight path information indicating a planned flight path of the UE to a network node, as described above.

[0122] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include receiving, from a network node, timing advance compensation configuration information associated with a planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information (block 820). For example, a UE (e.g., using Fig.10 The communications manager 140 and / or receiving component 1002 depicted in FIG. 1 may receive, from a network node, timing advance compensation configuration information associated with a planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information, as described above.

[0123] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include, in conjunction with a determination that at least one application criterion is satisfied, sending an uplink communication to a network node using a timing advance based at least in part on the timing advance compensation configuration information (block 830). For example, a UE (e.g., using Fig.10 The communication manager 140 and / or transmitting component 1004 depicted in FIG. 1 may transmit an uplink communication to a network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that at least one application criterion is satisfied, as described above.

[0124] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0125] In a first aspect, the at least one application criterion includes a reference altitude, and the determination that the at least one application criterion is met includes a determination that the UE is at or above the reference altitude.

[0126] In a second aspect, the reference altitude is a height from ground level, an altitude from sea level, or an altitude corresponding to a position along a planned flight path of the UE.

[0127] In a third aspect, the timing advance is based at least in part on: a cumulative closed-loop timing advance value, an open-loop timing advance value based at least in part on timing advance compensation configuration information, and a static timing advance offset value, and process 800 includes: in conjunction with the uplink communication being a first uplink communication, once at least one application criterion is met, resetting the cumulative closed-loop timing advance value before determining the timing advance of the uplink communication.

[0128] In a fourth aspect, at least one application criterion includes a duration for applying the timing advance compensation configuration information.

[0129] In a fifth aspect, at least one application criterion comprises a threshold value for a distance of the UE along the planned flight path of the UE from a reference location on the planned flight path.

[0130] In a sixth aspect, at least one application criterion includes a reference time for starting to apply the timing advance compensation configuration information.

[0131] In a seventh aspect, at least one application criterion includes a reference position on the UE's planned flight path, at which timing advance compensation configuration information is started to be applied, and a determination of whether at least one application criterion is met is based at least in part on a comparison of the reference position with a position on the UE's planned flight path that is closest to the UE's current position.

[0132] In an eighth aspect, at least one application criterion includes a reference area along a planned flight path of the UE, at which the timing advance compensation configuration information is applied.

[0133] In a ninth aspect, at least one application criterion is based at least in part on a planned flight path of the UE.

[0134] In a tenth aspect, timing advance compensation configuration information indicates a polynomial used to determine one or more configured timing advance values ​​associated with a planned flight path.

[0135] In an eleventh aspect, the timing advance compensation configuration information indicates a set of configured timing advance compensation values ​​associated with a planned flight path.

[0136] In a twelfth aspect, the timing advance compensation configuration information indicates a reference location of a network node.

[0137] In a thirteenth aspect, process 800 includes deriving a propagation delay between a network node and a UE based at least in part on a reference location of the network node in conjunction with a determination that at least one application criterion is satisfied, and the timing advance is based at least in part on the propagation delay.

[0138] In a fourteenth aspect, the timing advance compensation configuration information indicates a time function used to determine a configured timing advance compensation value, and the timing advance of the uplink communication is based at least in part on the configured timing advance compensation value determined using the time function.

[0139] In a fifteenth aspect, the configured timing advance compensation value is determined based at least in part on a reference speed associated with the UE using a time function.

[0140] In a sixteenth aspect, the timing advance compensation configuration information indicates a function of the distance of the UE along a planned flight path for determining a configured timing advance compensation value, and the timing advance of the uplink communication is at least partially based on the configured timing advance compensation value determined using the function of the distance of the UE along the planned flight path.

[0141] In a seventeenth aspect, the distance of the UE along the planned flight path is the distance from a reference position to the position on the planned flight path that is closest to the UE's position.

[0142] In an eighteenth aspect, the distance of the UE along the planned flight path is the integrated distance on the planned flight path to the location on the planned flight path that is closest to the UE's location.

[0143] In a nineteenth aspect, the timing advance compensation configuration information indicates a function of a location associated with the UE, used to determine a configured timing advance compensation value, and the timing advance of the uplink communication is at least partially based on the configured timing advance compensation value determined using the function of the location associated with the UE.

[0144] In a twentieth aspect, the location associated with the UE is a central location of an area in which the UE is located among a plurality of areas along a planned flight path.

[0145] In a twenty-first aspect, the location associated with the UE is the location on the planned flight path that is closest to the location of the UE.

[0146] In the twenty-second aspect, the timing advance compensation configuration information includes first timing advance compensation configuration information associated with the first cell or the first SSB and second timing advance compensation configuration information associated with the second cell or the second SSB.

[0147] In a twenty-third aspect, process 800 includes sending another uplink communication to the network node using a timing advance based at least in part on a previous open loop timing advance value determined according to the timing advance compensation configuration information in conjunction with a determination that at least one application criterion is no longer satisfied.

[0148] In a twenty-fourth aspect, process 800 includes receiving, from a network node, an indication of a threshold value of a deviation of a position of a UE from a planned flight path.

[0149] In a twenty-fifth aspect, process 800 includes sending a request to a network node to reconfigure timing advance compensation configuration information in conjunction with determining that a deviation of the UE's position from a planned flight path satisfies a threshold, and receiving updated timing advance compensation configuration information from the network node based at least in part on sending the request to reconfigure the timing advance compensation configuration information.

[0150] In a twenty-sixth aspect, process 800 includes, in conjunction with determining that a deviation of the UE's position from a planned flight path satisfies a threshold, sending updated flight path information indicating an updated planned flight path of the UE to a network node, and updated timing advance compensation configuration information is associated with the updated planned flight path of the UE.

[0151] In a twenty-seventh aspect, sending uplink communications includes, in conjunction with determining that a deviation of the UE's position from a planned flight path satisfies a threshold, sending PRACH uplink communications with a timing advance based at least in part on timing advance compensation configuration information adjusted by a configured offset value.

[0152] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0153] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network node in accordance with the present disclosure. Example process 900 is an example of a network node (eg, network node 110) performing operations associated with flight path based UE autonomous timing advance compensation.

[0154] like Fig. 9 As shown, in some aspects, process 900 may include receiving flight path information from a UE indicating a planned flight path for the UE (block 910). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or receiving component 1102 depicted in FIG. 10A may receive flight path information from a UE indicating a planned flight path for the UE, as described above.

[0155] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include sending to the UE timing advance compensation configuration information based at least in part on a planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information (block 920). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or transmitting component 1104 depicted in FIG. 1 may transmit to the UE timing advance compensation configuration information based at least in part on a planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information, as described above.

[0156] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include receiving an uplink communication from a UE using a timing advance based at least in part on the timing advance compensation configuration information and at least one application criterion (block 930). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or receiving component 1102 depicted in FIG. 1 may receive uplink communications from a UE using a timing advance based at least in part on the timing advance compensation configuration information and at least one application criterion, as described above.

[0157] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0158] In a first aspect, at least one application criterion includes a reference altitude.

[0159] In a second aspect, the reference altitude is a height from ground level, an altitude from sea level, or an altitude corresponding to a position along a planned flight path of the UE.

[0160] In a third aspect, at least one application criterion includes a duration for applying the timing advance compensation configuration information.

[0161] In a fourth aspect, at least one application criterion comprises a threshold value for a distance of the UE along the planned flight path of the UE from a reference location on the planned flight path.

[0162] In a fifth aspect, at least one application criterion includes a reference time for starting to apply the timing advance compensation configuration information.

[0163] In a sixth aspect, at least one application criterion comprises a reference location on a planned flight path of the UE at which to begin applying the timing advance compensation configuration information.

[0164] In a seventh aspect, at least one application criterion comprises a reference area along a planned flight path of the UE, at which the timing advance compensation configuration information is applied.

[0165] In an eighth aspect, at least one application criterion is based at least in part on a planned flight path of the UE.

[0166] In a ninth aspect, timing advance compensation configuration information indicates a polynomial for determining one or more configured timing advance compensation values ​​associated with a planned flight path.

[0167] In a tenth aspect, timing advance compensation configuration information indicates a set of configured timing advance compensation values ​​associated with a planned flight path.

[0168] In an eleventh aspect, the timing advance compensation configuration information indicates a reference location of a network node.

[0169] In a twelfth aspect, the timing advance compensation configuration information indicates a time function used to determine a configured timing advance compensation value.

[0170] In a thirteenth aspect, the timing advance compensation configuration information indicates a reference speed to be used with a time function for determining a configured timing advance compensation value.

[0171] In a fourteenth aspect, the timing advance compensation configuration information indicates a function of the distance of the UE along a planned flight path for determining a configured timing advance compensation value.

[0172] In a fifteenth aspect, the distance of the UE along the planned flight path is the distance from a reference position to the position on the planned flight path that is closest to the UE's position.

[0173] In a sixteenth aspect, the distance of the UE along the planned flight path is the integrated distance on the planned flight path to the location on the planned flight path that is closest to the UE's location.

[0174] In a seventeenth aspect, the timing advance compensation configuration information indicates a function of a location associated with the UE, used to determine a configured timing advance compensation value.

[0175] In an eighteenth aspect, the location associated with the UE is a central location of an area where the UE is located among a plurality of areas along a planned flight path.

[0176] In a nineteenth aspect, the location associated with the UE is the location on the planned flight path that is closest to the location of the UE.

[0177] In the twentieth aspect, the timing advance compensation configuration information includes first timing advance compensation configuration information associated with a first cell or a first SSB and second timing advance compensation configuration information associated with a second cell or a second SSB.

[0178] In a twenty-first aspect, process 900 includes sending to a UE an indication of a threshold value of a deviation of the UE's position from a planned flight path.

[0179] In a twenty-second aspect, process 900 includes receiving a request from a UE to reconfigure timing advance compensation configuration information, and sending updated timing advance compensation configuration information to the UE based at least in part on receiving the request to reconfigure the timing advance compensation configuration information.

[0180] In a twenty-third aspect, process 900 includes receiving updated flight path information from a UE indicating an updated planned flight path of the UE, and updated timing advance compensation configuration information is based at least in part on the updated planned flight path of the UE.

[0181] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0182] Fig.101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a sending component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and sending component 1004. As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include one or more of a determining component 1008 and / or an deriving component 1010, etc.

[0183] In some aspects, the apparatus 1000 may be configured to perform Figure 6 to Figure 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein (such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0184] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0185] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0186] The sending component 1004 can send flight path information indicating a planned flight path of the UE to the network node. The receiving component 1002 can receive, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information. The sending component 1004 can send an uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information in conjunction with a determination that the at least one application criterion is satisfied.

[0187] Determining component 1008 can determine whether at least one application criterion is satisfied.

[0188] Determining component 1008 can determine the timing advance based at least in part on the timing advance compensation configuration information.

[0189] The deriving component 1010 can derive a propagation delay between the network node and the UE based at least in part on a reference location of the network node in conjunction with a determination that at least one application criterion is satisfied, wherein the timing advance is based at least in part on the propagation delay.

[0190] Transmitting component 1004 can transmit another uplink communication to the network node using a timing advance based at least in part on a previous open loop timing advance value determined according to the timing advance compensation configuration information in conjunction with a determination that at least one application criterion is no longer satisfied.

[0191] Receiving component 1002 can receive, from a network node, an indication of a threshold value of a deviation of a position of the UE from a planned flight path.

[0192] The sending component 1004 can send a request to reconfigure the timing advance compensation configuration information to the network node in conjunction with the determination that the deviation between the UE's position and the planned flight path meets the threshold.

[0193] Receiving component 1002 can receive updated timing advance compensation configuration information from a network node based at least in part on sending a request to reconfigure the timing advance compensation configuration information.

[0194] The sending component 1004 can combine the determination that the deviation between the UE's position and the planned flight path meets the threshold, and send updated flight path information indicating the UE's updated planned flight path to the network node, wherein the updated timing advance compensation configuration information is associated with the UE's updated planned flight path.

[0195] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of components (one or more components) shown may be described as being executable by Fig.10 Another component shown may be a collection of components that perform one or more functions.

[0196] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include a determining component 1108, etc.

[0197] In some aspects, the apparatus 1100 may be configured to perform Figure 6 to Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein (such as Fig. 9 In some aspects, Fig.11 The apparatus 1100 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0198] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0199] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0200] Receiving component 1102 can receive flight path information from the UE indicating a planned flight path for the UE. Sending component 1104 can send, to the UE, timing advance compensation configuration information based at least in part on the planned flight path for the UE and an indication of at least one application standard associated with the timing advance compensation configuration information. Receiving component 1102 can receive uplink communications from the UE using the timing advance based at least in part on the timing advance compensation configuration information and the at least one application standard.

[0201] Determining component 1108 can determine timing advance compensation configuration information and / or at least one application criterion based at least in part on a planned flight path of the UE.

[0202] Transmitting component 1104 can transmit to the UE an indication of a threshold value of a deviation of the UE's position from the planned flight path.

[0203] Receiving component 1102 can receive a request from a UE to reconfigure timing advance compensation configuration information.

[0204] Transmitting component 1104 may transmit updated timing advance compensation configuration information to the UE based at least in part on receiving the request to reconfigure the timing advance compensation configuration information.

[0205] Receiving component 1102 can receive updated flight path information from the UE indicating an updated planned flight path of the UE, wherein the updated timing advance compensation configuration information is based at least in part on the updated planned flight path of the UE.

[0206] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The assembly of components (one or more components) shown may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

[0207] The following provides an overview of some aspects of the disclosure:

[0208] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: sending flight path information indicating a planned flight path of the UE to a network node; receiving timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information from the network node; and in combination with a determination that the at least one application standard is satisfied, sending uplink communication to the network node using a timing advance based at least in part on the timing advance compensation configuration information.

[0209] Aspect 2: The method according to aspect 1, wherein the at least one application criterion includes a reference altitude, and wherein the determination that the at least one application criterion is met includes a determination that the UE is at or above the reference altitude.

[0210] Aspect 3: The method according to aspect 2, wherein the reference altitude is a height from ground level, an altitude from sea level, or an altitude corresponding to a position along the planned flight path of the UE.

[0211] Aspect 4: A method according to any one of Aspects 1-3, wherein the timing advance is based at least in part on: a cumulative closed-loop timing advance value, an open-loop timing advance value based at least in part on the timing advance compensation configuration information, and a static timing advance offset value, and wherein the method further includes: in combination with the uplink communication being a first uplink communication, once the at least one application criterion is met, resetting the cumulative closed-loop timing advance value before determining the timing advance of the uplink communication.

[0212] Aspect 5: The method according to any one of aspects 1-4, wherein the at least one application criterion includes a duration for applying the timing advance compensation configuration information.

[0213] Aspect 6: The method according to any one of aspects 1-5, wherein the at least one application criterion comprises a threshold value of the distance of the UE along the planned flight path of the UE from a reference location on the planned flight path.

[0214] Aspect 7: The method according to any one of aspects 1-6, wherein the at least one application criterion includes a reference time for starting to apply the timing advance compensation configuration information.

[0215] Aspect 8: A method according to any one of Aspects 1-7, wherein the at least one application criterion includes a reference position on the planned flight path of the UE, and the timing advance compensation configuration information is applied starting at the reference position, wherein the determination of whether the at least one application criterion is met is at least partially based on a comparison of the reference position with a position on the planned flight path of the UE that is closest to the current position of the UE.

[0216] Aspect 9: The method according to any one of aspects 1-8, wherein the at least one application criterion comprises a reference area along the planned flight path of the UE, and the timing advance compensation configuration information is applied starting at the reference area.

[0217] Aspect 10: The method according to any one of aspects 1-9, wherein the at least one application criterion is based at least in part on the planned flight path of the UE.

[0218] Aspect 11: The method according to any one of aspects 1-10, wherein the timing advance compensation configuration information indicates a polynomial used to determine one or more configured timing advance values ​​associated with the planned flight path.

[0219] Aspect 12: The method according to any one of aspects 1-11, wherein the timing advance compensation configuration information indicates a set of configured timing advance compensation values ​​associated with the planned flight path.

[0220] Aspect 13: The method according to any one of aspects 1-10, wherein the timing advance compensation configuration information indicates a reference location of the network node.

[0221] Aspect 14: According to the method according to Aspect 13, the method also includes: in combination with the determination that the at least one application criterion is met, deriving a propagation delay between the network node and the UE at least partially based on the reference location of the network node, wherein the timing advance is at least partially based on the propagation delay.

[0222] Aspect 15: A method according to any one of Aspects 1-12, wherein the timing advance compensation configuration information indicates a time function for determining a configured timing advance compensation value, and wherein the timing advance of the uplink communication is at least partially based on the configured timing advance compensation value determined using the time function.

[0223] Aspect 16: The method according to aspect 15, wherein the configured timing advance compensation value is determined using the time function based at least in part on a reference speed associated with the UE.

[0224] Aspect 17: A method according to any one of Aspects 1-12 and 15-16, wherein the timing advance compensation configuration information indicates a function of the distance of the UE along the planned flight path, used to determine a configured timing advance compensation value, and wherein the timing advance of the uplink communication is at least partially based on the configured timing advance compensation value determined using the function of the distance of the UE along the planned flight path.

[0225] Aspect 18: The method according to aspect 17, wherein the distance of the UE along the planned flight path is the distance from a reference position to a position on the planned flight path that is closest to the position of the UE.

[0226] Aspect 19: The method according to aspect 17, wherein the distance of the UE along the planned flight path is an integrated distance on the planned flight path to a position on the planned flight path that is closest to the position of the UE.

[0227] Aspect 20: A method according to any one of Aspects 1-12 and 15-19, wherein the timing advance compensation configuration information indicates a function of a position associated with the UE, used to determine a configured timing advance compensation value, and wherein the timing advance of the uplink communication is at least partially based on the configured timing advance compensation value determined using the function of the position associated with the UE.

[0228] Aspect 21: The method according to aspect 20, wherein the location associated with the UE is a central location of an area where the UE is located among a plurality of areas along the planned flight path.

[0229] Aspect 22: The method according to aspect 20, wherein the location associated with the UE is the location closest to the location of the UE on the planned flight path.

[0230] Aspect 23: A method according to any one of Aspects 1-22, wherein the timing advance compensation configuration information includes first timing advance compensation configuration information associated with a first cell or a first synchronization signal block (SSB) and second timing advance compensation configuration information associated with a second cell or a second SSB.

[0231] Aspect 24: According to the method described in any one of Aspects 1-23, the method also includes: in combination with the determination that at least one application criterion is no longer met, sending another uplink communication to the network node using a timing advance that is at least partially based on a previous open-loop timing advance value determined according to the timing advance compensation configuration information.

[0232] Aspect 25: The method according to any one of aspects 1-24, the method further comprising: receiving an indication of a threshold value of a deviation of the position of the UE from the planned flight path from the network node.

[0233] Aspect 26: According to the method described in Aspect 25, the method also includes: sending a request to the network node to reconfigure the timing advance compensation configuration information in combination with determining that the deviation between the position of the UE and the planned flight path satisfies the threshold; and receiving updated timing advance compensation configuration information from the network node based at least in part on sending the request to reconfigure the timing advance compensation configuration information.

[0234] Aspect 27: According to the method described in Aspect 26, the method also includes: in combination with the determination that the deviation between the position of the UE and the planned flight path satisfies the threshold, sending updated flight path information indicating the updated planned flight path of the UE to the network node, wherein the updated timing advance compensation configuration information is associated with the updated planned flight path of the UE.

[0235] Aspect 28: A method according to any one of Aspects 25-27, wherein sending the uplink communication includes: in combination with determining that the deviation of the position of the UE from the planned flight path satisfies the threshold, sending a physical random access channel (PRACH) uplink communication with the timing advance, and the timing advance is at least partially based on the timing advance compensation configuration information adjusted by a configured offset value.

[0236] Aspect 29: A method of wireless communication performed by a network node, the method comprising: receiving flight path information indicating a planned flight path of a user equipment (UE) from the UE; sending to the UE timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application standard associated with the timing advance compensation configuration information; and receiving uplink communication from the UE using the timing advance based at least in part on the timing advance compensation configuration information and the at least one application standard.

[0237] Aspect 30: The method according to aspect 29, wherein the at least one application criterion includes a reference altitude.

[0238] Aspect 31: The method according to aspect 30, wherein the reference altitude is a height from ground level, an altitude from sea level, or an altitude corresponding to a position along the planned flight path of the UE.

[0239] Aspect 32: The method according to any one of aspects 29-31, wherein the at least one application criterion comprises a duration for applying the timing advance compensation configuration information.

[0240] Aspect 33: A method according to any one of aspects 29-32, wherein the at least one application criterion comprises a threshold value of a distance of the UE along the planned flight path of the UE from a reference location on the planned flight path.

[0241] Aspect 34: The method according to any one of aspects 29-33, wherein the at least one application criterion comprises a reference time for starting to apply the timing advance compensation configuration information.

[0242] Aspect 35: The method according to any one of aspects 29-34, wherein the at least one application criterion comprises a reference position on the planned flight path of the UE, at which the timing advance compensation configuration information is applied.

[0243] Aspect 36: The method according to any one of aspects 29-35, wherein the at least one application criterion comprises a reference area along the planned flight path of the UE, and the timing advance compensation configuration information is applied starting at the reference area.

[0244] Aspect 37: A method according to any one of aspects 29-36, wherein the at least one application criterion is based at least in part on the planned flight path of the UE.

[0245] Aspect 38: A method according to any one of aspects 29-37, wherein the timing advance compensation configuration information indicates a polynomial used to determine one or more configured timing advance compensation values ​​associated with the planned flight path.

[0246] Aspect 39: The method according to any one of aspects 29-38, wherein the timing advance compensation configuration information indicates a set of configured timing advance compensation values ​​associated with the planned flight path.

[0247] Aspect 40: The method according to any one of aspects 29-37, wherein the timing advance compensation configuration information indicates a reference location of the network node.

[0248] Aspect 41: The method according to any one of aspects 29-39, wherein the timing advance compensation configuration information indicates a time function used to determine the configured timing advance compensation value.

[0249] Aspect 42: The method according to aspect 41, wherein the timing advance compensation configuration information indicates a reference speed to be used with the time function for determining the configured timing advance compensation value.

[0250] Aspect 43: A method according to any one of aspects 29-39 and 41-42, wherein the timing advance compensation configuration information indicates a function of the distance of the UE along the planned flight path, used to determine the configured timing advance compensation value.

[0251] Aspect 44: The method according to aspect 43, wherein the distance of the UE along the planned flight path is the distance from a reference position to a position on the planned flight path that is closest to the position of the UE.

[0252] Aspect 45: The method according to aspect 43, wherein the distance of the UE along the planned flight path is an integrated distance on the planned flight path to a position on the planned flight path that is closest to the position of the UE.

[0253] Aspect 46: A method according to any one of aspects 29-39 and 41-45, wherein the timing advance compensation configuration information indicates a function of a location associated with the UE, used to determine a configured timing advance compensation value.

[0254] Aspect 47: The method according to aspect 46, wherein the location associated with the UE is a central location of an area where the UE is located among a plurality of areas along the planned flight path.

[0255] Aspect 48: The method according to aspect 46, wherein the location associated with the UE is the location on the planned flight path that is closest to the location of the UE.

[0256] Aspect 49: A method according to any one of Aspects 29-48, wherein the timing advance compensation configuration information includes first timing advance compensation configuration information associated with a first cell or a first synchronization signal block (SSB) and second timing advance compensation configuration information associated with a second cell or a second SSB.

[0257] Aspect 50: The method according to any one of aspects 29-49 further comprises: sending an indication of a threshold value of the deviation of the position of the UE from the planned flight path to the UE.

[0258] Aspect 51: According to the method described in Aspect 50, the method also includes: receiving a request to reconfigure the timing advance compensation configuration information from the UE; and sending updated timing advance compensation configuration information to the UE based at least in part on receiving the request to reconfigure the timing advance compensation configuration information.

[0259] Aspect 52: According to the method according to Aspect 51, the method also includes: receiving updated flight path information indicating an updated planned flight path of the UE from the UE, wherein the updated timing advance compensation configuration information is at least partially based on the updated planned flight path of the UE.

[0260] Aspect 53: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1-28.

[0261] Aspect 54: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1-28.

[0262] Aspect 55: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 1-28.

[0263] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1-28.

[0264] Aspect 57: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 1-28.

[0265] Aspect 58: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 29-52.

[0266] Aspect 59: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 29-52.

[0267] Aspect 60: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 29-52.

[0268] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 29-52.

[0269] Aspect 62: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 29-52.

[0270] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0271] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0272] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0273] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0274] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: sending flight path information indicating a planned flight path of the UE to a network node; receiving, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information; as well as In conjunction with a determination that the at least one application criterion is satisfied, an uplink communication is sent to the network node using a timing advance based at least in part on the timing advance compensation configuration information.

2. The UE of claim 1 , wherein the at least one application criterion comprises a reference altitude, wherein the determination that the at least one application criterion is satisfied comprises a determination that the UE is at or above the reference altitude, and wherein the reference altitude is an altitude above ground level, an altitude above sea level, or an altitude corresponding to a position along the planned flight path of the UE.

3. The UE of claim 1 , wherein the timing advance is based at least in part on: a cumulative closed-loop timing advance value, an open-loop timing advance value based at least in part on the timing advance compensation configuration information, and a static timing advance offset value, and wherein the one or more processors are further configured to: In conjunction with said uplink communication being a first uplink communication, upon satisfying said at least one application criterion, resetting said accumulated closed-loop timing advance value prior to determining said timing advance for said uplink communication.

4. The UE according to claim 1, wherein the at least one application criterion comprises at least one of the following: a duration for applying the timing advance compensation configuration information, a threshold value for the distance of the UE along the planned flight path of the UE from a reference position on the planned flight path, or The reference time for starting to apply the timing advance compensation configuration information.

5. A UE according to claim 1, wherein the at least one application criterion includes a reference position on the planned flight path of the UE, and the timing advance compensation configuration information is applied starting at the reference position, wherein the determination of whether the at least one application criterion is met is at least partially based on a comparison of the reference position with a position on the planned flight path of the UE that is closest to the current position of the UE. 6 . The UE of claim 1 , wherein the at least one application criterion comprises a reference area along the planned flight path of the UE, at which the timing advance compensation configuration information is applied.

7. The UE of claim 1, wherein the at least one application criterion is based at least in part on the planned flight path of the UE.

8. The UE of claim 1, wherein the timing advance compensation configuration information indicates a polynomial used to determine one or more configured timing advance values ​​associated with the planned flight path.

9. The UE of claim 1, wherein the timing advance compensation configuration information indicates a set of configured timing advance compensation values ​​associated with the planned flight path.

10. The UE of claim 1, wherein the timing advance compensation configuration information indicates a reference location of the network node, and wherein the one or more processors are further configured to: In conjunction with the determining that the at least one application criterion is satisfied, a propagation delay between the network node and the UE is derived based at least in part on the reference location of the network node, wherein the timing advance is based at least in part on the propagation delay.

11. The UE of claim 1 , wherein the timing advance compensation configuration information indicates a time function for determining a configured timing advance compensation value, wherein the timing advance of the uplink communication is based at least in part on the configured timing advance compensation value determined using the time function, and wherein the configured timing advance compensation value is determined using the time function based at least in part on a reference speed associated with the UE.

12. The UE of claim 1 , wherein the timing advance compensation configuration information indicates a function of a distance of the UE along the planned flight path for determining a configured timing advance compensation value, wherein the timing advance of the uplink communication is based at least in part on the configured timing advance compensation value determined using the function of the distance of the UE along the planned flight path, and wherein the distance of the UE along the planned flight path is: the distance from a reference position to the position on the planned flight path that is closest to the position of the UE, or The integrated distance on the planned flight path to the location on the planned flight path that is closest to the location of the UE.

13. The UE of claim 1 , wherein the timing advance compensation configuration information indicates a function of a location associated with the UE for determining a configured timing advance compensation value, wherein the timing advance of the uplink communication is based at least in part on the configured timing advance compensation value determined using the function of the location associated with the UE, and wherein the location associated with the UE is the central position of the area where the UE is located among the multiple areas along the planned flight path, or The location on the planned flight path that is closest to the location of the UE.

14. The UE of claim 1, wherein the timing advance compensation configuration information comprises first timing advance compensation configuration information associated with a first cell or a first synchronization signal block (SSB) and second timing advance compensation configuration information associated with a second cell or a second SSB.

15. The UE of claim 1, wherein the one or more processors are further configured to: In conjunction with determining that the at least one application criterion is no longer met, another uplink communication is sent to the network node using a timing advance based at least in part on a previous open loop timing advance value determined according to the timing advance compensation configuration information.

16. The UE of claim 1, wherein the one or more processors are further configured to: receiving from the network node an indication of a threshold value of a deviation of the position of the UE from the planned flight path; in conjunction with a determination that the deviation between the position of the UE and the planned flight path satisfies the threshold, sending a request to the network node to reconfigure the timing advance compensation configuration information; and Based at least in part on sending the request to reconfigure the timing advance compensation configuration information, updated timing advance compensation configuration information is received from the network node.

17. The UE of claim 16, wherein the one or more processors are further configured to: In conjunction with the determination that the deviation of the position of the UE from the planned flight path satisfies the threshold, updated flight path information indicating an updated planned flight path of the UE is sent to the network node, wherein the updated timing advance compensation configuration information is associated with the updated planned flight path of the UE.

18. The UE of claim 1, wherein to send the uplink communication, the one or more processors are configured to: receiving from the network node an indication of a threshold value of a deviation of the UE's position from the planned flight path; and In conjunction with determining that the deviation of the position of the UE from the planned flight path satisfies the threshold, sending a physical random access channel (PRACH) uplink communication with the timing advance based at least in part on the timing advance compensation configuration information adjusted by a configured offset value.

19. A network node for wireless communication, the network node comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to: receiving, from a user equipment (UE), flight path information indicating a planned flight path of the UE; sending, to the UE, timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information; as well as An uplink communication is received from the UE using a timing advance based at least in part on the timing advance compensation configuration information and the at least one application criterion.

20. The network node of claim 19, wherein the at least one application criterion comprises at least one of the following: Reference altitude, a duration for applying the timing advance compensation configuration information, a distance of the UE along the planned flight path of the UE from a reference position on the planned flight path, a reference time for starting to apply the timing advance compensation configuration information, a reference position on the planned flight path of the UE, starting to apply the timing advance compensation configuration information at the reference position, or A reference area along the planned flight path of the UE, wherein the timing advance compensation configuration information is applied starting at the reference area.

21. The network node according to claim 19, wherein the timing advance compensation configuration information indicates: a polynomial for determining one or more configured timing advance compensation values ​​associated with the planned flight path, or A set of configured timing advance compensation values ​​associated with the planned flight path.

22. The network node of claim 19, wherein the timing advance compensation configuration information indicates a reference location of the network node.

23. The network node according to claim 19, wherein the timing advance compensation configuration information indicates: a time function used to determine the configured timing advance compensation value, a function of the distance of the UE along the planned flight path for determining a configured timing advance compensation value, or A function of a location associated with the UE is used to determine a configured timing advance compensation value.

24. The network node of claim 23, wherein the timing advance compensation configuration information indicates a reference speed to be used with the time function for determining the configured timing advance compensation value.

25. The network node of claim 19, wherein the timing advance compensation configuration information comprises first timing advance compensation configuration information associated with a first cell or a first synchronization signal block (SSB) and second timing advance compensation configuration information associated with a second cell or a second SSB.

26. The network node of claim 19, wherein the one or more processors are further configured to: An indication of a threshold value of a deviation of the UE's position from the planned flight path is sent to the UE.

27. The network node of claim 26, wherein the one or more processors are further configured to: receiving a request to reconfigure the timing advance compensation configuration information from the UE; and Based at least in part on receiving the request to reconfigure the timing advance compensation configuration information, updated timing advance compensation configuration information is sent to the UE.

28. The network node of claim 27, wherein the one or more processors are further configured to: Updated flight path information is received from the UE indicating an updated planned flight path of the UE, wherein the updated timing advance compensation configuration information is based at least in part on the updated planned flight path of the UE.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: sending flight path information indicating a planned flight path of the UE to a network node; receiving, from the network node, timing advance compensation configuration information associated with the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information; as well as In conjunction with a determination that the at least one application criterion is satisfied, an uplink communication is sent to the network node using a timing advance based at least in part on the timing advance compensation configuration information.

30. A method of wireless communication performed by a network node, the method comprising: receiving, from a user equipment (UE), flight path information indicating a planned flight path of the UE; sending, to the UE, timing advance compensation configuration information based at least in part on the planned flight path of the UE and an indication of at least one application criterion associated with the timing advance compensation configuration information; as well as An uplink communication is received from the UE using a timing advance based at least in part on the timing advance compensation configuration information and the at least one application criterion.

Images