Vertical sensing capability for integrated sensing and communication

Abstract

Techniques for sensing are disclosed. In some aspects, an unmanned aerial vehicle user equipment (UAV-UE) can transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE. The UAV-UE can receive configuration information to perform one or more sensing operations within a target altitude range. The UAV-UE can perform the one or more sensing operations within the target altitude range. The UAV-UE can transmit a sensing report indicating one or more results of the one or more sensing operations.

Description

Background Technology 1. Technical Field

[0002] All aspects of this disclosure relate to wireless technology.

[0003] 2. Relevant Technical Descriptions

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data transfer speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Positioning Reference Signals (RS-P), such as downlink, uplink, or sidelink Positioning Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in the PRS process and technology, and the high-density deployment of 5G, enable high-accuracy positioning based on 5G. Summary of the Invention

[0006] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0007] In one aspect, a method performed at an unmanned aerial vehicle user equipment (UAV-UE) includes: transmitting capability information indicating one or more vertical sensing capabilities of the UAV-UE; receiving configuration information to perform one or more sensing operations within a target altitude range; performing the one or more sensing operations within the target altitude range; and transmitting a sensing report indicating one or more results of the one or more sensing operations.

[0008] In one aspect, a method performed at a network entity includes: receiving capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); sending configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receiving one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0009] In one aspect, an unmanned aerial vehicle user equipment (UAV-UE) includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE via the one or more transceivers; receive configuration information via the one or more transceivers to perform one or more sensing operations within a target altitude range; perform the one or more sensing operations within the target altitude range; and transmit sensing reports indicating one or more results of the one or more sensing operations via the one or more transceivers.

[0010] In one aspect, a network entity includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive capability information via the one or more transceivers indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); transmit configuration information via the one or more transceivers to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receive one or more sensing reports via the one or more transceivers, the one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0011] In one aspect, an unmanned aerial vehicle user equipment (UAV-UE) includes: components for transmitting capability information indicating one or more vertical sensing capabilities of the UAV-UE; components for receiving configuration information to perform one or more sensing operations within a target altitude range; components for performing the one or more sensing operations within the target altitude range; and components for transmitting a sensing report indicating one or more results of the one or more sensing operations.

[0012] In one aspect, a network entity includes: components for receiving capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); components for transmitting configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and components for receiving one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0013] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by an unmanned aerial vehicle user equipment (UAV-UE), cause the UAV-UE to: transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE; receive configuration information to perform one or more sensing operations within a target altitude range; perform the one or more sensing operations within the target altitude range; and transmit a sensing report indicating one or more results of the one or more sensing operations.

[0014] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to: receive capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); send configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receive one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0015] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0016] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0017] Figure 1 Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0018] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0019] Figure 3A , Figure 3B and Figure 3CIt is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0020] Figure 4A and Figure 4B Different types of wireless sensing according to various aspects of this disclosure are illustrated.

[0021] Figure 5 This illustrates an example channel estimation of a multipath channel between a receiver device and a transmitter device according to various aspects of this disclosure.

[0022] Figure 6 An example call flow for an NR-based sensing process is illustrated according to various aspects of this disclosure.

[0023] Figure 7 Example sensing environments are illustrated according to various aspects of this disclosure.

[0024] Figure 8A and Figure 8B Example sensing environments and example processes for sensing one or more target objects are illustrated according to various aspects of this disclosure.

[0025] Figure 9A and Figure 9B Example sensing environments and example processes for sensing one or more target objects are illustrated according to various aspects of this disclosure.

[0026] Figure 10A and Figure 10B Example sensing environments and example processes for sensing one or more target objects are illustrated according to various aspects of this disclosure.

[0027] Figure 11A An example positioning environment for round-trip time (RTT) based positioning is illustrated according to various aspects of this disclosure.

[0028] Figure 11B An example positioning environment for positioning based on direction of arrival (DoA) and real-time time (RTT) according to various aspects of this disclosure is illustrated.

[0029] Figure 12 and Figure 13 Example methods of sensing according to various aspects of this disclosure are illustrated. Detailed Implementation

[0030] Various aspects of this disclosure are provided in the following description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0031] The overall scope involves sensing technology. Some aspects are more specifically related to the vertical sensing capabilities of unmanned aerial vehicle user equipment (UAV-UE). In some examples, the UAV-UE sends capability information to one or more network entities. The UAV-UE receives configuration information from one or more network entities and can perform sensing operations based on that configuration information. In some aspects, capability information is sent before the configuration information is received, while in others, capability information is sent after the configuration information is received.

[0032] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. Aspects of this disclosure enable the accurate localization of target objects located above the ground plane. Generally, established localization techniques can be used to locate objects at or near the ground plane. However, determining the three-dimensional localization of the sensing entity can be challenging in order to perform accurate sensing of objects located above the ground plane. Furthermore, since different UAV-UEs may have different antenna types, the vertical sensing capability of a particular UAV-UE to sense a target object may be constrained by both its height and the antenna sensing direction. In some examples, by providing capability information, the described techniques can be used to achieve efficient sensing of objects located above the ground using UAV-UEs capable of performing sensing operations. One or more network entities can provide configuration information to a capable UAV-UE, or provide configuration to the UAV-UE such that if the UAV-UE's vertical sensing capability matches the configured sensing, the UAV-UE performs a sensing operation.

[0033] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0034] Those skilled in the art will understand that any of the various techniques and skills available can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, and in part on the corresponding technology, etc.

[0035] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered to be entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect can be described herein as, for example, "logic configured to perform the described actions."

[0036] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Overall, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

[0037] A base station may operate according to one of several RATs to communicate with the UE, depending on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0038] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of a base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of the base station.

[0039] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections for the UE), but may instead transmit reference signals to the UE for measurement and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0040] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0041] Figure 1 An example wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In some aspects, macro cell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0042] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 (e.g., location management function (LMF) or secure user plane location (SUPL) location platform (SLP)) via core network 170. Location server 172 can be part of core network 170 or can be external to core network 170. Location server 172 can be integrated with base station 102. UE 104 can communicate with location server 172 directly or indirectly. For example, UE 104 can communicate with location server 172 via base station 102 currently serving UE 104. UE 104 can also communicate with location server 172 via another path, such as via application server (not shown), via another network, such as via wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For signaling purposes, communication between UE 104 and location server 172 can be represented as an indirect connection (e.g., via core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), wherein intermediate nodes (if present) are omitted from the signaling diagram for clarity.

[0043] In addition to other functions, base station 102 may perform functions associated with one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) on backhaul link 134, which may be wired or wireless.

[0044] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In some aspects, one or more cells can be supported by base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., via a frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0045] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in a handover area), some areas within geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0046] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0047] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) or listen-before-talk (LBT) process before communication to determine whether the channel is available.

[0048] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MULTEFIRE. ® .

[0049] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that, in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing examples are merely illustrative and should not be construed as limiting the various aspects disclosed herein.

[0050] Transmit beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster and stronger RF signal (in terms of data rate). To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (called a "phased array" or "antenna array") that forms RF beams that can be "guided" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship, such that radio waves from the individual antennas add up in the desired direction to increase radiation, while canceling out in the undesired direction to suppress radiation.

[0051] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., the UE) as having the same parameters regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of a second reference RF signal on a second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0052] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is described as performing beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signal received from that direction.

[0053] The transmit and receive beams can be spatially correlated. Spatial correlation means that parameters for a second beam (e.g., transmit or receive beam) for a second reference signal can be derived based on information about a first beam (e.g., receive or transmit beam) for a first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0054] It is important to note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving the downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the designation used by the International Telecommunication Union. ® Extremely high frequency (EHF) bands (30 GHz to 300 GHz) are designated as “millimeter wave” bands.

[0056] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have identified the operating bands used for these IF bands as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0057] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0058] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial Radio Resource Control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only the necessary signaling information and signals. For example, since the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

[0059] For example, still refer to Figure 1One of the frequencies used by macro cell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to the data rate obtained by a single 20MHz carrier, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz).

[0060] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0061] In some cases, UE 164 and UE 182 may be able to communicate via sidelink. A sidelink-capable UE (SL-UE) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via radio sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). Radio sidelink (or simply "sidelink") is an adaptation of core cellular network (e.g., LTE, NR) standards that allows direct communication between two or more UEs without the need for communication through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communication may be located within the geographical coverage area 110 of base station 102. Other SL-UEs in this group may be outside the geographical coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources used for sidelink communication. In other cases, sidelink communication is performed between the individual SL-UEs without involving base station 102.

[0062] In some aspects, the sidelink 160 may operate via a wireless communication medium of interest that may be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. “Medium” may include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In some aspects, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently extended their operation to unlicensed frequency bands such as those used by unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as “Wi-Fi”). Examples of this type of system include different variations of CDMA, TDMA, FDMA, Orthogonal FDMA (OFDMA), and Single-Carrier FDMA (SC-FDMA) systems.

[0063] It should be noted that, although Figure 1 Only two of these UEs are exemplified as SL-UEs (i.e., UE 164 and UE 182), but any UE exemplified can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE exemplified (including UE 164) can be capable of beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base station 102, base station 180, small cell 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 can utilize beamforming via sidelink 160.

[0064] exist Figure 1 In the example, the UE shown (for simplicity, in) Figure 1Any UE (shown as a single UE 104) may receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In some aspects, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While typically located in SV 112, transmitters may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0065] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlap Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN). Therefore, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0066] In some respects, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). Within an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as a modified base station 102 (without a ground antenna) or a network node in a 5GC. This element, in turn, provides access to other elements within the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. Thus, as a replacement or supplement to communication signals from ground base station 102, UE 104 may receive communication signals (e.g., signal 124) from SV 112.

[0067] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations in base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can utilize any known D2DRAT (such as LTE Direct (LTE-D), Wi-Fi Direct). ® ,Bluetooth ® (etc.) to support.

[0068] Figure 2A An example wireless network architecture 200 is illustrated. For instance, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which work together to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either or both of the gNBs 222 or ng-eNBs 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0069] Another optional aspect may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0070] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can be used with...). Figure 2AThe 5GC 210 (corresponding to 5GC 210) can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Secure Anchoring Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulated services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) Access network functionality.

[0071] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful eavesdropping (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and location servers (such as SLP 272) on the user plane.

[0072] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service bootstrapping configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0073] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functions to LMF 270, but while LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to deliver signaling messages rather than voice or data), SLP 272 can communicate with UE 204 and external clients (e.g., third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmit Control Protocol (TCP) and / or IP).

[0074] Another optional aspect may include a third-party server 274, which can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0075] User plane interface 263 and control plane interface 265 connect 5GC 260, and specifically connect UPF 262 and AMF 264 to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0076] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0077] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5GNB, AP, TRP, cells, etc.) can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations.

[0078] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0079] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), etc. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0080] Figure 2C An example disaggregated base station architecture 250 according to various aspects of this disclosure is illustrated. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with the core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 via one or more disaggregated base station units (such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). CUs 280 may communicate with one or more duplex units (DUs) 285 (e.g., gNB-DU 228) via a corresponding midhaul link (e.g., an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via a corresponding fronthaul link. RU 287 can communicate with the corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RU 287s simultaneously.

[0081] Each of these units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO frame 255) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

[0082] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 280. The CU 280 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can 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 units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 280 can be implemented to communicate with the DU 285 for network control and signaling, as needed.

[0083] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially defined according to functional partitioning (such as by the 3rd Generation Partnership Project (3GPP)). ®The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some aspects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0084] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UE 204s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration allows the DU 285 and CU 280 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0085] SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 255 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 255 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 269 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, SMO framework 255 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 261, via the O1 interface. Additionally, in some implementations, SMO framework 255 can communicate directly with one or more RU 287s via the O1 interface. SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of SMO framework 255.

[0086] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

[0087] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 259 and can be received from non-network data sources or network functions at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0088] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding boxes) are illustrated, which can be incorporated into UE 302 (which may correspond to any UE described herein, including UAV-UE), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of UE 302). Figure 2A and Figure 2BThe NG-RAN 220 and / or 5GC 210 / 260 infrastructures depicted herein (such as dedicated networks) support the operations described herein. It should be understood that these components can be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0089] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively; and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0090] In at least some cases, UE 302 and base station 304 each further include one or more short-range radio transceivers 320 and 360, respectively. Short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access over a wireless communication medium of interest via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE ® Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) that enable communication between PC5, Dedicated Short Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, short-range wireless transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively; and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, short-range wireless transceivers 320 and 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0091] In at least some cases, UE 302 and base station 304 also include satellite signal interfaces 330 and 370, each satellite signal interface including one or more satellite signal receivers 332 and 372, and optionally including one or more satellite signal transmitters 334 and 374, respectively. In some cases, base station 304 may be a terrestrial base station that can communicate with a spacecraft (e.g., spacecraft 112) via satellite signal interface 370. In other cases, base station 304 may be a spacecraft (or other non-terrestrial entity) that uses satellite signal interface 370 to communicate with terrestrial networks and / or other spacecraft.

[0092] Satellite signal receivers 332 and 372 can be connected to one or more antennas 336 and 376 respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378 respectively. When satellite signal receivers 332 and 372 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, etc. When satellite signal receivers 332 and 372 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 332 and 372 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 332 and 372 may request appropriate information and operation from other systems, and in at least some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the locations of UE 302 and base station 304, respectively.

[0093] Optional satellite signal transmitters 334 and 374 (when present) can be connected to one or more antennas 336 and 376, respectively, and can be provided with components for transmitting satellite positioning / communication signals 338 and 378, respectively. When satellite signal transmitter 374 is a satellite positioning system transmitter, satellite positioning / communication signal 378 can be a GPS signal, GLONASS signal, etc. ® Signals include Galileo signals, BeiDou signals, NAVIC signals, and QZSS signals. When satellite signal transmitters 334 and 374 are NTN transmitters, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal transmitters 334 and 374 can include any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378 respectively. Satellite signal transmitters 334 and 374 can request appropriate information and operations from other systems.

[0094] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0095] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceiver 380 and network transceiver 390 in some embodiments) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming, as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In some aspects, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

[0096] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some specific embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some specific embodiments) may generally be described as "transceiver," "at least one transceiver," or "one or more transceivers." Therefore, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0097] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 342, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 342, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In some aspects, processors 342, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0098] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include sensing components 348, 388, and 398. Sensing components 348, 388, and 398 may be hardware circuitry that is part of or coupled to processors 342, 384, and 394, respectively, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, sensing components 348, 388, and 398 may be external to processors 342, 384, and 394 (e.g., as part of a modem processing system, integrated with another processing system, etc.). Alternatively, sensing components 348, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations of sensing component 348 are illustrated. The sensing component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 342, or any combination thereof, or may be a standalone component. Figure 3B Possible locations of sensing component 388 are illustrated. The sensing component may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for sensing component 398 are illustrated. This sensing component may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or it may be a standalone component. Sensing component 398 may implement a sensing management function (SnMF) that can communicate with the 5GC and provide sensing management for any UE in the UE described herein. SnMF may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0099] UE 302 may include one or more sensors 344 coupled to one or more processors 342 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal interfaces 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0100] In addition, UE 302 includes a user interface 346 that provides components for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0101] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel priority ordering.

[0102] Transmitter 354 and receiver 352 implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the decoding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can utilize the corresponding spatial stream to modulate an RF carrier for transmission.

[0103] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 342. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 304. These soft decisions can be based on a channel estimate calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 342, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0104] In the downlink, one or more processors 342 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. One or more processors 342 are also responsible for error detection.

[0105] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 342 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority processing, and logical channel priority ordering.

[0106] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0107] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

[0108] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0109] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe document is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® The short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal interface 330 can be omitted, or the sensor 344 can be omitted, etc. In another example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal interface 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0110] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 308, 382, ​​and 392, respectively. In some aspects, data buses 308, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 308, 382, ​​and 392 can provide communication between these logical entities.

[0111] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or combine at least one memory component for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functionalities represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionalities represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Furthermore, some or all of the functionalities represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it should be understood that such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as processors 342, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, sensing components 348, 388 and 398, etc.

[0112] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may operate differently from the network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link such as Wi-Fi).

[0113] Wireless communication signals transmitted between the UE and the base station (e.g., radio frequency (RF) signals configured to carry orthogonal frequency division multiplexing (OFDM) symbols according to wireless communication standards such as LTE, NR, etc.) can be used for environmental sensing (also known as "RF sensing" or "radar"). Environmental sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, enabling contactless / device-free interaction with devices / systems, etc. Wireless communication signals can be cellular communication signals, such as LTE or NR signals, WLAN signals such as Wi-Fi signals, etc. As a specific example, wireless communication signals can be OFDM waveforms as utilized in LTE and NR. High-frequency communication signals, such as millimeter-wave (mmW) RF signals, are particularly beneficial for use as sensing signals because higher frequencies provide at least more accurate ranging (distance) detection. Possible use cases for RF sensing include: health monitoring use cases, such as heart rate detection, respiratory rate monitoring, etc.; gesture recognition use cases, such as human activity recognition, keystroke detection, sign language recognition, etc.; context information acquisition use cases, such as location detection / tracking, direction finding, ranging estimation, etc.; and automotive sensing use cases, such as intelligent cruise control, collision avoidance, etc. There are different types of sensing, including single-station sensing (also known as "active sensing") and dual-station sensing (also known as "passive sensing"). Figure 4A and Figure 4B These different types of sensing are illustrated. Specifically, Figure 4A This is illustration 400 illustrating a single-station sensing scenario, and Figure 4B This is illustration 430, illustrating a dual-station sensing scenario. Figure 4A In this configuration, the transmitter (Tx) and receiver (Rx) are co-located in the same sensing device 404 (e.g., a UE). The sensing device 404 transmits one or more RF sensing signals 434 (e.g., uplink or sidelink positioning reference signals (PRS) in the case of a UE), and some of the RF sensing signals 434 are reflected from a target object 406 (e.g., an unmanned aerial vehicle (UAV)). The sensing device 404 can measure various properties of the reflected RF sensing signals 434 (e.g., time of arrival (ToA), angle of arrival (AoA), phase shift, etc.) to determine characteristics of the target object 406 (e.g., size, shape, speed, motion state, etc.). Figure 4B In this architecture, the transmitter (Tx) and receiver (Rx) are not co-located; that is, they are separate devices (e.g., the UE and the base station). It should be noted that although... Figure 4BAn example is shown using a downlink RF signal as the RF sensing signal 432, but uplink or sidelink RF signals can also be used as the RF sensing signal 432. In the downlink scenario, as shown, the transmitter device 402 is a base station (e.g., a gNB), and the receiver device 408 is a UE (e.g., a mobile phone, a V2X-enabled vehicle, a roadside unit (RSU), etc.), while in the uplink scenario, the transmitter device 402 is the UE, and the receiver device 408 is the base station. When the transmitter device 402 is the base station and the receiver device 408 is the UE, the sensing is referred to as UE-assisted sensing. In UE-assisted sensing, the location of the receiver device 408 should be known to the network (e.g., via GPS or other UE positioning methods). See more details in the reference section. Figure 4B Transmitter device 402 transmits RF sensing signals 432 and 434 (e.g., a location reference signal (PRS)) to receiver device 408, but some of the RF sensing signals 434 are reflected from target object 406. Receiver device 408 (also referred to as a “sensing device”) can measure the time of arrival (ToA) of the RF sensing signal 432 received directly from transmitter device 402 and the time of reflection 436 of the RF sensing signal 434 reflected from target object 406. More specifically, as described above, transmitter device (e.g., a base station) can transmit a single RF signal or multiple RF signals to receiver device (e.g., a UE). However, due to the propagation characteristics of RF signals through multipath channels, receiver can receive multiple RF signals corresponding to each transmitted RF signal. Each path can be associated with a cluster of one or more channel taps. Typically, the time when the receiver detects the first channel tap cluster is considered to be the time of arrival (ToA) of the RF signal on the site line (LOS) path (i.e., the shortest path between the transmitter and receiver). The subsequent channel tap clustering is considered to have been reflected from the object between the transmitter and receiver, and therefore along the non-LOS (NLOS) path between the transmitter and receiver. Therefore, refer back to the previous section. Figure 4BRF sensing signal 432 follows the LOS path between transmitter device 402 and receiver device 408, while RF sensing signal 434 follows the NLOS path between transmitter device 402 and receiver device 408 due to reflection from target object 406. Transmitter device 402 may have transmitted multiple RF sensing signals 432 and 434, some following the LOS path and others following the NLOS path. Alternatively, transmitter device 402 may have transmitted a single RF sensing signal in a sufficiently wide beam such that a portion of the RF sensing signal follows the LOS path (RF sensing signal 432) and a portion follows the NLOS path (RF sensing signal 434). Based on the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, receiver device 408 can determine the distance to the target object. For example, receiver device 408 can calculate the distance to the target object as the difference between the ToA of the LOS path and the ToA of the NLOS path multiplied by the speed of light. Furthermore, if receiver device 408 is capable of receiving beamforming, it can determine the approximate direction to target object 406 as the direction (angle) of the received beam that receives the RF sensing signal following the NLOS path. That is, receiver device 408 can determine the direction to target object 406 as the AoA of the RF sensing signal, where AoA is the angle of the received beam used to receive the RF sensing signal. Receiver device 408 can then optionally report this information to transmitter device 402, its serving base station, application server associated with the core network, external client, third-party application, or some other sensing entity. Alternatively, receiver device 408 can report the ToA measurement to transmitter device 402 or other sensing entities (e.g., if receiver device 408 itself does not have the processing capability to perform calculations), and transmitter device 402 can determine the distance to target object 406 and optionally determine the direction to that target object. It should be noted that if the RF sensing signal is an uplink RF signal transmitted by the UE to the base station, the base station will perform object detection based on the uplink RF signal, just as the UE does based on the downlink RF signal. Similar to conventional radar, wireless communication-based sensing signals can be used to estimate the range (distance), velocity (Doppler), and angle (AoA) of a target object. However, performance (e.g., resolution and maximum values ​​of range, velocity, and angle) can depend on the design of the reference signal.

[0114] Figure 5Figure 500 illustrates an example channel estimation of a multipath channel between a receiver device (e.g., any of the UEs or base stations described herein) and a transmitter device (e.g., any other of the UEs or base stations described herein) according to various aspects of this disclosure. The channel estimation expresses the strength of a radio frequency (RF) signal (e.g., a positioning reference signal (PRS)) received through the multipath channel as a function of time delay and may be referred to as the channel energy response (CER), channel impulse response (CIR), or power delay distribution (PDP) of the channel. Therefore, the horizontal axis represents time (e.g., milliseconds), and the vertical axis represents signal strength (e.g., decibels). It should be noted that a multipath channel is a channel between a transmitter and a receiver where the RF signal follows multiple paths or multipaths due to transmission of the RF signal across multiple beams and / or due to the propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).

[0115] exist Figure 5 In the example, the receiver detects / measures multiple (four) channel taps of the RF signal. Each channel tap is a cluster of one or more rays and corresponds to the multipath followed by the RF signal between the transmitter and receiver. Therefore, the channel tap represents the arrival time and signal strength of the RF signal on the multipath. Multiple channel taps may exist because the RF signal is transmitted on different transmit beams (and therefore at different angles), or due to the propagation characteristics of the RF signal (e.g., it may follow different paths due to reflection), or both. Note that although... Figure 5 Channel taps with two to five rays are illustrated, but it should be understood that a channel tap may have more or fewer rays than the illustrated number.

[0116] exist Figure 5 In the example, the channel tap detected at time T3 includes a stronger ray compared to the channel tap detected at time T1. This could be due to an obstacle on the LOS path between the transmitter and receiver. Alternatively or additionally, there may be a strong reflector along the NLOS path corresponding to the channel tap detected at time T3.

[0117] Figure 6 An example call flow 600 is illustrated, illustrating an NR-based sensing process (e.g., a dual-site sensing process) for configuring sensing parameters in a network, according to various aspects of this disclosure. Although Figure 6 The example illustrates a network-coordinated sensing process, but this sensing process can be coordinated via a sidelink channel.

[0118] At stage 605, sensing server 670 (e.g., inside or outside the core network) transmits a request for network (NW) information to gNB 622 (e.g., the serving gNB of UE 604). This request may be for a list of UE 604's serving cell and any neighboring cells. At stage 610, gNB 622 transmits the requested information to sensing server 670. At stage 615, sensing server 670 transmits a request for sensing capabilities to UE 604. At stage 620, UE 604 provides its sensing capabilities to sensing server 670.

[0119] At stage 625, the sensing server 670 transmits to the UE 604 a configuration indicating one or more reference signal (RS) resources to be transmitted for sensing. The reference signal resources may be transmitted by the serving cell and / or neighboring cells identified at stage 610. In some cases, Figure 6 The illustrated NR-based sensing process can be a sensing-only process or a Joint Communication and Sensing (JCS) process (sometimes called Integrated Communication and Sensing (ICAS)). In the case of a sensing-only process, the reference signal resource can be a reference signal resource specifically configured for sensing purposes. In the case of a JCS process, the reference signal resource can be a reference signal resource used for both communication and sensing purposes. Alternatively, the reference signal resource used for sensing can be multiplexed with the reference signal resource used for communication (e.g., time-division multiplexing). For example, the reference signal resource used for communication can be an orthogonal frequency division multiplexing (OFDM) waveform, while the reference signal resource used for sensing can be a frequency modulated continuous wave (FMCW) waveform.

[0120] At stage 630, the sensing server 670 transmits a request for sensing information to the UE 604. Then, the UE 604 measures the transmitted reference signal and, at stage 635, transmits the measurement or any sensing results determined based on the measurement to the sensing server 670.

[0121] In some respects, communication between the UE 604 and the sensing server 670 can be conducted via the LTE Positioning Protocol (LPP). Communication between the sensing server 670 and the gNB can be conducted via NR Positioning Protocol Type A (NRPPa).

[0122] Integrated Sensing and Communication (ISAC) technology, which combines wireless communication and wireless sensing, has been introduced. As mentioned above (for example, see reference...), Figure 4A and Figure 4BAs described, the sensing system transmits a probe signal to a non-cooperative target (e.g., target object 406) and infers useful information from the target echo. Conversely, the communication system exchanges information between two or more cooperating transceivers (e.g., UE and TRP). ISAC systems are integrated systems that enable both wireless communication and wireless sensing to be performed simultaneously, thus providing a cost-effective deployment for both sensing and communication systems. In an ISAC system, time, frequency, and / or spatial RF resources are allocated to support both objectives: communication and sensing.

[0123] The development and deployment of ISAC systems are driven by their cost efficiency (due to shared RF, and possibly baseband, hardware for sensing and communication) and spectral efficiency (due to the persistent availability of spectrum for both functions). Use cases for ISAC systems include (1) macro sensing, such as weather monitoring, autonomous driving, dynamic map building, low-altitude airspace and ground management (e.g., UAV, vehicle and pedestrian sensing), intrusion detection, etc.; (2) micro sensing, such as gesture recognition, life signal detection, high-resolution imaging, etc.; and (3) sensing-assisted communication, such as beam management.

[0124] As mentioned above, different entities can participate in sensing technologies. For example, RAN nodes (such as gNBs and different types of user equipment (UEs)) can perform single-site sensing, dual-site sensing, or multi-site sensing combining more than two entities. In some cases, different sensing modes can be identified by the entity type and direction of the sensed signal. For example, transmit-receive point (TRP) single-site sensing is performed by the TRP of the RAN node, while in a TRP-UE dual-site sensing mode, the TRP is the transmitting node and the UE is the receiving node, and in a TRP-TRP dual-site sensing mode, one TRP is the transmitting node and different TRPs are the receiving nodes. Similarly, UE single-site sensing is performed by the UE, in a UE-TRP dual-site sensing mode, the UE is the transmitting node and the TRP is the receiving node, and in a UE-UE dual-site sensing mode, the UE is the transmitting node and different UEs are the receiving nodes.

[0125] In some cases, different types of UEs can perform sensing technologies. Figure 7 A diagram illustrating a sensing environment 700 according to various aspects of this disclosure is shown. RAN nodes (such as gNB 702) and / or UEs (such as handheld device UE 704-a, vehicle UE 704-b, and / or UAV-UE 704-c) can be configured to perform sensing operations; for example, determining the location information, speed / rate information, etc., of a target object 706. Figure 7In the dual-site sensing example, gNB 702 transmits a sensing reference signal that is reflected from the target object 706 and detected by the handheld device UE 704-a, the vehicle UE 704-b, and / or the UAV-UE 704-c.

[0126] For integrated sensing and communication systems, ground-based UEs (such as handheld device UE 704-a and vehicle UE 704-b) typically sense objects on or near the ground plane, while UAV-UE 704-c can sense objects above the ground, such as other UAVs, balloons, birds, etc. The vertical sensing capability of UAV-UE 704-c depends on the antenna's sensing direction capability; for example, it depends on its antenna type (e.g., omnidirectional or directional). Antenna sensing direction capability information may include indications of the antenna type, angular coverage information, directional coverage information, or any combination thereof for one or more UAV-UE antennas.

[0127] For example, a first type of UAV may have one or more directional antennas positioned to receive signals from below the UAV and communicate with a ground station. The first type of UAV can communicate with network infrastructure using a Uu interface and does not require sidelink capability. Therefore, the first type of UAV can sense a target object 706 below but not above the UAV. A second type of UAV may have one or more antennas for omnidirectional coverage, allowing the UAV to receive signals from and transmit signals to other UAVs (e.g., using a sidelink communication protocol). The second type of UAV can sense target objects 706 below, above, and at the same height as the UAV.

[0128] According to some aspects of this disclosure, the UAV-UE can perform sensing operations based on one or more vertical sensing capabilities of the UAV-UE. Sensing operations may include transmitting sensing signals, receiving sensing signals, or both. The UAV-UE may receive configuration for performing sensing operations within a target height range, transmit capability information indicating one or more vertical sensing capabilities, and (if capable) perform the configured sensing operations. The configuration may be received before or after transmitting the capability information. The UAV-UE may report the results of the sensing operations to one or more network entities. Examples of vertical sensing capabilities include UAV-UE height, UAV-UE height uncertainty, antenna sensing direction, or any combination thereof. Configuration information may include indications of one or more target height ranges and sensing configurations, such as time and frequency resources for performing sensing operations, and other configuration information.

[0129] Figure 8A A diagram illustrating an example sensing environment 800 incorporating various aspects of this disclosure is shown. Figure 8B A process 850 for performing sensing of target object 806-1 and target object 806-2 according to some aspects of this disclosure is shown.

[0130] refer to Figure 8A and Figure 8B At 860, a RAN node (such as gNB 802) can send configuration information to UAV-UE 804-1 and UAV-UE 804-2 to perform sensing of target objects 806-1 and 806-2. In some implementations, the configuration can be initiated by gNB 802 or by different network entities 810 implementing sensing management functions (e.g., one or more sensing management devices / servers). Network entity 810 can be implemented by: the processor / memory circuitry of the RAN node, one or more devices implementing sensing management functions (SnMF), one or more devices implementing location management functions (LMF), one or more devices implementing core network functionality, and / or other network entities. The configuration information can indicate one or more target height ranges; for example, the target height range of target object 806-1 and the target height range of target object 806-2, where the target height range is the range within which a particular target object is estimated to be located.

[0131] At 870, UAV-UE 804-1 and UAV-UE 804-2 can transmit capability information indicating one or more vertical sensing capabilities, such as altitude, altitude uncertainty, antenna sensing direction, or any combination thereof.

[0132] In some cases, UAV-UE 804-1 or UAV-UE 804-2, or both, may send vertical sensing capability information after receiving configuration information, while in some specific implementations, UAV-UE 804-1 or UAV-UE 804-2, or both, may send capability information before receiving configuration information for performing sensing operations. Examples of these specific implementations are provided in... Figure 9A , Figure 9B , Figure 10A and Figure 10B It is shown in the figure and described below.

[0133] UAV-UE 804-1 is located at altitude h1 and has a downward-pointing directional antenna, while UAV-UE 804-2 is located at altitude h2 and has an omnidirectional antenna. UAV-UE 804-1 can only sense target 806-1, while UAV-UE 804-2 can sense target 806-2 and may also sense target 806-1, depending on its ability to sense the relevant target altitude range. At 880, UAV-UE 804-1 and UAV-UE 804-2 can perform one or more sensing operations according to configuration information. At 890, UAV-UE 804-1 and UAV-UE 804-2 can send a sensing report indicating one or more results of one or more sensing operations to gNB 802 and / or network entity 810.

[0134] Figure 9A An example sensing environment 900 is illustrated, in which a UAV-UE reports vertical sensing capability prior to sensing measurements, according to some aspects of this disclosure. Figure 9A The examples illustrate three different target altitude ranges and three different UAV-UEs (UAV-UE 904-1, 904-2, and 904-3). UAV-UE 904-1 is a first-type UAV with a downward-pointing directional antenna located at altitude h1. UAV-UE 904-2 is a second-type UAV located at altitude h2 with an omnidirectional antenna capable of transmitting and receiving signals above, below, and at the same altitude. UAV-UE 904-3 is a first-type UAV located at altitude h3 with a downward-pointing directional antenna.

[0135] Figure 9B An example method 950 is illustrated in which a UAV-UE reports vertical sensing capability prior to sensing measurements, according to some aspects of this disclosure. At 960-1, 960-2, and 960-3, UAV-UEs 904-1, 904-2, and 904-3 transmit vertical sensing capability information to one or more network entities 902 (e.g., RAN nodes, SnMF, LMF, core network devices, and / or other network entities) prior to sensing operations. The capability information may be transmitted in response to a request for capability information, according to a schedule (e.g., periodically scheduled using a pre-configured timer), based on one or more events, or otherwise triggered. Although transmission for each UAV-UE is illustrated sequentially, depending on the specific implementation (e.g., depending on the configuration), each UAV-UE may transmit at the same / similar / different times.

[0136] At point 965, network entity 902 determines whether one or more UAV-UEs can cover the target height range of the associated target object. For Figure 9A and Figure 9B For example, network entity 902 determines that UAV-UE 904-3 can sense target objects within a target height range 915-3 based on, for example, its altitude, altitude uncertainty, and antenna sensing direction. At 970, the network entity transmits a sensing request with configuration information to configure one or more sensing operations of UAV-UE 904-3. Although Figure 9B The example illustrates the configuration of a single UAV-UE, but in other cases, the network entity can configure different target height ranges for multiple UAV-UEs based on their vertical sensing capabilities. For instance, target height range 1 can be configured for UAV-UE 904-1, target height range 2 for UAV-UE 904-2, and target height range 3 for UAV-UE 904-3. At 980, UAV-UE 904-3 performs one or more sensing operations based on the configuration information, and at 990, reports the results of one or more sensing operations to network entity 902. The sensing results may include measurements of one or more first reference signals (when UAV-UE 904-3 is a receiving entity) and / or configuration / transmission information for one or more second reference signals (when UAV-UE 904-3 is a transmitting entity).

[0137] Figure 10A An example sensing environment 1000 is illustrated, in which a UAV-UE reports vertical sensing capability after receiving configuration information, according to some aspects of this disclosure. Figure 10A The example illustrates a target altitude range and two different UAV-UEs (UAV-UE 1004-1 and UAV-UE 1004-2). UAV-UE 1004-1 is a first-type UAV located at altitude h1 with a downward-pointing directional antenna. UAV-UE 1004-2 is a second-type UAV located at altitude h2 with an omnidirectional antenna capable of transmitting and receiving signals above, below, and at the same altitude.

[0138] Figure 10BAn example method 1050 is shown, illustrating a specific implementation of at least some UAV-UEs reporting vertical sensing capabilities after receiving configuration information according to various aspects of this disclosure. At 1060-1 and 1060-2, network entity 902 sends an indication of a target altitude range to UAV-UEs 1004-1 and 1004-2. For example, the gNB can broadcast / multicast configuration information including the target altitude range according to a protocol used for UAV-UE sensing. In some implementations, network entity 1002 may send sensing configuration information indicating whether it is applied to ground-based sensing or airborne sensing. One or more ground-based UEs can perform sensing operations based on ground-based sensing configuration information, while one or more UAV-UEs can perform airborne sensing based on regional sensing configuration information.

[0139] At 1070-1 and 1070-2, each UAV-UE in the UAV-UE determines whether to perform a sensing operation based on configuration information; for example, by determining whether the target height range is included in its vertical sensing capability. Figure 10A For example, UAV-UE 1004-2 can sense target objects above and below h2 (which includes the target height range), and therefore at 1080, UAV-UE 1004-2 performs one or more sensing operations based on configuration information. In contrast, UAV-UE 1004-1 can sense target objects below h1, and therefore cannot perform sensing within any target height range. At 1075, UAV-UE 1004-1 can send an indication that the target height range is not covered, which could be an indication of its vertical sensing capability.

[0140] At 1090, UAV-UE 1004-2 reports the sensing results and vertical sensing capabilities to network entity 1002 (if not previously provided).

[0141] As part of the ICAS UAV-UE sensing technology described above, the UAV-UE sends an indication of its altitude and altitude measurement accuracy (e.g., altitude uncertainty). The UAV-UE can use different methods that may have different levels of accuracy to measure its altitude.

[0142] Many UAVs are capable of Global Navigation Satellite System (GNSS) positioning. GNSS is very accurate in the horizontal plane, but often less accurate for vertical measurements. Additionally, GNSS positioning has a relatively low update rate and may not be very accurate in locating fast-moving objects. Several other technologies use sensors to measure the altitude of a UAV-UE; for example, barometric sensors, ultrasonic sensors, cameras, or other sensors. Barometric sensors can be used to estimate the altitude of a UAV-UE because atmospheric pressure varies with altitude. Ultrasonic sensors measure distance from the ground by sending / receiving ultrasonic signals, while cameras use image data to determine altitude information.

[0143] As mentioned above, the UAV-UE reports its vertical sensing capability to the network entity, including its height and accuracy level (e.g., uncertainty). If the uncertainty exceeds a threshold, the network entity can trigger different positioning technologies to obtain a more accurate height for the UAV-UE. For example, the network entity can trigger a new radio (NR) positioning technology to obtain a more accurate estimate of the UAV-UE's height. If the uncertainty is less than or equal to the threshold, the network entity can use the UAV-UE's height and accuracy level to adjust the margin of the target height range. For example, if the UAV-UE height is measured at 80m with an uncertainty of 5m, and the original target height range is 40m-80m, the modified target height range is 40m-75m. For a UAV-UE height measured at 80m and an uncertainty of 5m, and an original target height range of 40m-120m, the modified target height range is 45m-115m.

[0144] In some aspects of this disclosure, a UAV-UE can be instructed to perform altitude determination using different positioning methods in response to current altitude uncertainty. For example, the UAV-UE can use a first positioning method (such as a satellite positioning system positioning method) and report its current altitude and altitude uncertainty to the network entity. In response to altitude uncertainty exceeding a threshold amount, the network entity can instruct the UAV-UE to use a second, different positioning method, such as one or more new radio (NR) positioning techniques. Example NR positioning techniques include RTT-based positioning, Time Difference of Arrival (TDoA)-based positioning, Direction of Arrival (DoA)-based positioning, and combinations thereof.

[0145] UAV-UE can use different positioning methods (e.g., NR positioning method) to determine the updated altitude and can send capability information that at least indicates the updated altitude and the updated altitude uncertainty.

[0146] Figure 11AAn example positioning environment 1100 for RTT-based positioning according to various aspects of this disclosure is illustrated, showing three RAN nodes 1102-1, 1102-2 and 1102-3 at distances d1, d2 and d3 from the UAV-UE 1104, respectively. Figure 11B An example positioning environment 1150 for DoA-based and RTT-based positioning is illustrated according to various aspects of this disclosure.

[0147] For RTT-based positioning, multiple entities at different altitudes (e.g., other ground-based UEs, UAV-UEs, and / or TRPs at different altitudes) are used to measure the 3D positioning of the UAV-UE. Four or more entities may be required, although fewer devices may be used if some positioning information is available from other technologies. Larger altitude variations between measuring devices provide more accurate altitude measurements, as does increasing the number of measuring devices. However, due to the increased distance to the UAV-UE 1104, larger altitude variations between measuring devices for altitude accuracy can affect the signal-to-noise ratio (SNR).

[0148] In the example RTT-based localization process, the network entity determines at least three or four unequal-height gNBs and / or UEs closest to the UAV-UE's horizontal coordinates to measure the RTT between each gNB / UE and the UAV-UE; for Figure 11A The example shown illustrates TRPs for RAN nodes 1102-1, 1102-2, and 1102-3. Network entities can initiate Location Reference Signal (PRS) transmission and detection for UAV-UE 1104 and RAN nodes 1102-1, 1102-2, and 1102-3. The direction of PRS transmission can be from RAN nodes 1102-1, 1102-2, and 1102-3 to UAV-UE 1104, or from UAV-UE 1104 to RAN nodes 1102-1, 1102-2, and 1102-3. In some cases, RTT measurements can be reported to network entities (such as LMF, SnMF, or core network equipment) to determine the UAV-UE's altitude information.

[0149] Another NR positioning technology uses positioning based on DoA (Direction of Arrival) and RTT (Round-Trip Time). Figure 11BAn example positioning environment 1150 for RTT-based positioning according to various aspects of this disclosure is illustrated. In some cases, a single device can utilize a combination of DoA and RTT to estimate the three-dimensional positioning of the UAV-UE. In some aspects, the network device selects one or more gNBs and / or UEs, such as RAN node 1152 with DoA measurement capability. The network device can select the DoA-capable entity closest to the horizontal coordinates of UAV-UE 1154 to measure the DoA and RTT between RAN node 1152 and UAV-UE 1154. Each selected gNB / UE reports positioning measurements for the UAV-UE, and the network entity can merge the reported measurements to improve accuracy.

[0150] In some aspects of this disclosure, configuration signaling and reporting signaling can be managed in a variety of different ways. For example, configuration information sent from a RAN node (such as a gNB) to the UAV-UE can be indicated via Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Media Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling. Configuration information can be indicated in different ways depending on the circumstances; for example, configuration can be semi-statically configured at one time and dynamically configured at a second different time.

[0151] In some aspects of this disclosure, Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling can be used to instruct configuration signaling between core network functions (such as 5GC and / or one or more devices included in other core network devices) and UAV-UE or RAN nodes.

[0152] In some aspects of this disclosure, configuration signaling between one or more network entities implementing SnMF and / or LMF and the UAV-UE can be indicated via a Layer 3 RRC Information Element (IE) carried in the LTE Positioning Protocol (LPP) protocol directly between the UE and the Location Management Function (LMF) or in a dedicated Sensing Protocol directly between the UE and the Sensing Management Function (SnMF).

[0153] In some aspects of this disclosure, configuration signaling between one or more sensing servers and the gNB can be indicated via a New Radio Positioning Protocol Type A (NRPPa) protocol directly between the gNB and the LMF or in a dedicated sensing protocol directly between the gNB and the SnMF.

[0154] In some aspects of this disclosure, configuration signaling between one UE and another UE (one or both UEs may be UAV-UEs) can be indicated in the side link (SL) via SL layer 1 (SCI (PSCCH) and / or SL data (PSSCH)), SL layer 2 MAC-CE or SL layer 3 RRC (Direct Communication PC5).

[0155] In some aspects of this disclosure, configuration signaling between the UAV-UE and the gNB can be indicated via Layer 1 Uplink Control Information (UCI), Layer 2 MAC-CE, or Layer 3 RRC.

[0156] In some aspects of this disclosure, reporting signaling from measurement network nodes to control network nodes can be implemented in various ways. For example, for a UAV-UE sending reporting information to a gNB or other RAN node, the reporting information can be sent via Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC.

[0157] In some aspects of this disclosure, reporting information is sent from a UAV-UE or gNB to one or more devices that implement core network functions, and this reporting information may be transmitted via NAS / NGAP signaling.

[0158] In some aspects of this disclosure, the transmission of reporting information from the UAV-UE to one or more devices (such as one or more sensing / location servers) implementing SnMF and / or LMF can be done via Layer 3 transmission, such as RRC IE carried in the LPP protocol directly between the UAV-UE and the LMF-implementing device or in a dedicated sensing protocol directly between the UE and the SnMF-implementing device. For this aspect, one or more RAN nodes can provide the transmission capability.

[0159] In some aspects of this disclosure, reporting information from RAN nodes (such as gNBs) is transmitted to one or more sensing and / or location servers (e.g., implementing SnMF or LMF) via an NRPPa protocol directly between the gNB and the LMF (Location Server) or a dedicated sensing protocol directly between the gNB and the SnMF (Sensing Server). For this aspect, one or more RAN nodes may provide transmission capabilities.

[0160] In some aspects of this disclosure, reporting information sent from one UE to another is implemented using a side link (SL) via SL layer 1 (SCI (PSCCH) and / or SL data (PSSCH)), SL layer 2 MAC-CE, or SL layer 3 RRC. (PC5)

[0161] Figure 12 An example method 1200 for sensing according to various aspects of this disclosure is illustrated. In some aspects, method 1200 may be performed by user equipment, such as unmanned aerial vehicle user equipment (UAV-UE); for example, any UE described herein.

[0162] At 1210, the UAV-UE transmits capability information indicating one or more vertical sensing capabilities of the UAV-UE. In some aspects, operation 1210 may be performed, for example, using the WWAN transceiver 310, short-range transceiver 320, processor 342, sensing component 348, and / or memory 340 of the UE 302, which can be considered as parts (structures) for performing operation 1210.

[0163] At 1220, the UAV-UE receives configuration information to perform one or more sensing operations within the target altitude range. In some aspects, operation 1220 may be performed, for example, using the WWAN transceiver 310, short-range transceiver 320, processor 342, sensing components 348, and / or memory 340 of the UE 302, which can be considered as parts (structures) for performing operation 1220.

[0164] At 1230, the UAV-UE performs one or more sensing operations within the target altitude range. In some aspects, operation 1230 may be performed, for example, using the WWAN transceiver 310, short-range transceiver 320, processor 342, sensing components 348, and / or memory 340 of the UE 302, which can be considered as parts (structures) for performing operation 1230.

[0165] At 1240, the UAV-UE sends a sensing report indicating one or more results of one or more sensing operations. In some aspects, operation 1240 may be performed, for example, using the WWAN transceiver 310, short-range transceiver 320, processor 342, sensing component 348, and / or memory 340 of the UE 302, which can be considered as parts (structures) for performing operation 1240.

[0166] It should be understood that the technical advantage of method 1200 is its ability to accurately sense objects located above the ground plane. Additionally, since the vertical sensing capability of a particular UAV-UE to sense a target object may be constrained by both its height and the antenna sensing direction, providing / using capability information can provide efficient sensing of objects located above the ground through a UAV-UE capable of performing sensing operations.

[0167] Figure 13 An example method 1300 for sensing according to various aspects of this disclosure is illustrated. In some aspects, method 1300 can be performed by a network entity; for example, a RAN node, a sensing management function device / server, a location management device / server, a core network device, or other network entities, such as... Figure 3B Base station 304 Figure 3C Network entity 306 or any RAN node, core network 170, location server 172 or sensing server described herein.

[0168] At 1310, the network entity receives capability information indicative of one or more vertical sensing capabilities of the unmanned aerial vehicle user equipment (UAV-UE). In some aspects, when the network entity is a RAN node, operation 1310 may be performed by one or more WWAN transceivers 350, one or more short-range radio transceivers 360, one or more network transceivers 380, one or more processors 384, memory 386, and / or sensing components 388, any or all of which may be considered as components (structures) for performing the operation. In some aspects, when the network entity is a sensing server, operation 1310 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of which may be considered as components (structures) for performing the operation.

[0169] At 1320, the network entity sends configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE. In some aspects, when the network entity is a RAN node, operation 1320 may be performed by one or more WWAN transceivers 350, one or more short-range radio transceivers 360, one or more network transceivers 380, one or more processors 384, memory 386, and / or sensing components 388, any or all of these components can be considered as parts (structures) for performing the operation. In some aspects, when the network entity is a sensing server, operation 1320 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of these components can be considered as parts (structures) for performing the operation.

[0170] At 1330, the network entity receives one or more sensing reports indicating the results of one or more sensing operations obtained based on configuration information. In some aspects, when the network entity is a RAN node, operation 1330 may be performed by one or more WWAN transceivers 350, one or more short-range radio transceivers 360, one or more network transceivers 380, one or more processors 384, memory 386, and / or sensing components 388, any or all of which may be considered as components (structures) for performing the operation. In some aspects, when the network entity is a sensing server, operation 1330 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of which may be considered as components (structures) for performing the operation.

[0171] It should be understood that the technical advantage of method 1300 is its ability to accurately sense objects located above the ground plane. Network entities can provide configuration information and manage sensing across multiple UAV-UEs based on vertical sensing capabilities, thereby providing accurate location / velocity / rate determination for one or more target objects.

[0172] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein explicitly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0173] Specific implementation examples are described in the following numbered clauses:

[0174] Clause 1. A method performed at an unmanned aerial vehicle user equipment (UAV-UE), the method comprising: transmitting capability information indicating one or more vertical sensing capabilities of the UAV-UE; receiving configuration information to perform one or more sensing operations within a target altitude range; performing the one or more sensing operations within the target altitude range; and transmitting a sensing report indicating one or more results of the one or more sensing operations.

[0175] Clause 2. The method according to Clause 1, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction; or any combination thereof.

[0176] Clause 3. The method according to any one of Clauses 1 to 2, wherein: the configuration information is received after the capability information is sent; or the configuration information is received before the capability information is sent.

[0177] Clause 4. The method according to any one of Clauses 1 to 3, wherein the one or more sensing operations include: detecting one or more first reference signals; or transmitting one or more second reference signals, or both.

[0178] Clause 5. The method according to Clause 4, wherein the one or more sensing operations include one or more bi-station sensing operations, and wherein: the one or more first reference signals are received from a radio access network (RAN) node or from different UAV-UEs; or the one or more second reference signals are transmitted to a RAN node or different UAV-UEs.

[0179] Clause 6. The method according to any one of Clauses 1 to 5, wherein the one or more results include: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0180] Clause 7. The method according to any one of Clauses 1 to 6, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using a first positioning method, and the method further includes: receiving an indication for performing height determination using a second different positioning method; determining an updated height of the UAV-UE using the second different positioning method; and transmitting capability information, the capability information indicating at least the updated height of the UAV-UE based on the second different positioning method and the updated height uncertainty of the UAV-UE.

[0181] Clause 8. The method according to Clause 7, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) based positioning between the UAV-UE and a plurality of entities at different altitudes, wherein the plurality of entities includes one or more other UAV-UEs, one or more Transmit / Receive Points (TRPs), or a combination thereof.

[0182] Clause 9. The method according to any one of Clauses 7 to 8, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) and DoA positioning between the UAV-UE and at least one entity having direction of arrival (DoA) measurement capability.

[0183] Clause 10. The method according to any one of Clauses 1 to 9, wherein the capability information indicating the one or more vertical sensing capabilities of the UAV-UE includes an indication that the antenna sensing direction is omnidirectional or directional.

[0184] Clause 11. The method according to any one of Clauses 1 to 10, wherein the configuration information includes a target height range, and wherein performing one or more sensing operations includes: performing the one or more sensing operations to sense a target object within the target height range.

[0185] Clause 12. The method according to any one of Clauses 1 to 11, wherein the capability information is included in the sensing report.

[0186] Clause 13. The method according to any one of Clauses 1 to 12, wherein receiving the configuration information comprises: receiving the configuration information from one or more RAN nodes according to Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Media Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; receiving the configuration information from one or more core network devices according to Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; receiving the configuration information from one or more servers implementing Sensing Management Function (SnMF) or Location Management Function (LMF) or both according to a Layer 3 RRC Information Element (IE) of a Long Term Evolution (LTE) Positioning Protocol (LPP) or Dedicated Sensing Protocol; receiving the configuration information from one or more other UEs according to a sidelink protocol; or any combination thereof.

[0187] Clause 14. The method according to any one of Clauses 1 to 13, wherein sending the sensing report comprises: sending the sensing report to one or more RAN nodes according to Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; sending the sensing report to one or more core network devices according to NAS or NGAP signaling; sending the sensing report to one or more servers implementing SnMF or LMF or both according to Layer 3 RRC IE of LPP protocol or dedicated sensing protocol; sending the sensing report to one or more other UEs according to sidelink protocol; or any combination thereof.

[0188] Clause 15. A method performed at a network entity, the method comprising: receiving capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); transmitting configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receiving one or more sensing reports, the one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0189] Clause 16. The method according to Clause 15, wherein: the capability information is received before the configuration information is sent; or the capability information is received after the configuration information is sent.

[0190] Clause 17. The method according to any one of Clauses 15 to 16, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction of the UAV-UE; or any combination thereof.

[0191] Clause 18. The method of Clause 17, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the height uncertainty of the UAV-UE exceeds a threshold amount, and the method further comprises: sending an instruction to the UAV-UE for performing height determination using a second different positioning method; and receiving an updated height of the UAV-UE determined using the second different positioning method.

[0192] Clause 19. The method according to any one of Clauses 15 to 18, wherein the result of said one or more sensing operations includes: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0193] Clause 20. The method according to any one of Clauses 15 to 19, the method further comprising: determining the location of one or more target objects based on the one or more sensing reports.

[0194] Clause 21. The method according to any one of Clauses 15 to 20, wherein the network entity comprises: a radio access network (RAN) node; one or more core network devices; one or more sense management devices; one or more location management devices; one or more other UEs; or any combination thereof.

[0195] Clause 22. The method according to any one of Clauses 15 to 21, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes transmit the configuration information using Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; one or more core network devices, wherein the one or more core network devices transmit the configuration information using Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; one or more sensor management devices, wherein the one or more sensor management devices implement Sensor Management Function (SnMF) using a dedicated sensing protocol; one or more location management devices, wherein the one or more location management devices implement Location Management Function (LMF) using a Long Term Evolution (LTE) Positioning Protocol (LPP); one or more other UEs, wherein the one or more other UEs use a sidelink protocol; or any combination thereof.

[0196] Clause 23. The method according to any one of Clauses 15 to 22, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes receive the one or more sensing reports according to Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; one or more core network devices, wherein the one or more core network devices receive the one or more sensing reports according to NAS or NGAP signaling; one or more sensing management devices, wherein the one or more sensing management devices implement a sensing management function (SnMF), wherein the one or more sensing management devices use a dedicated sensing protocol to receive the one or more sensing reports; one or more location management devices, wherein the one or more location management devices implement a location management function (LMF), wherein the one or more location management devices use a Long Term Evolution (LTE) Positioning Protocol (LPP) to receive the one or more sensing reports; one or more other UEs, wherein the one or more other UEs receive the one or more sensing reports according to a sidelink protocol; or any combination thereof.

[0197] Clause 24. An unmanned aerial vehicle user equipment (UAV-UE) comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE via the one or more transceivers; receive configuration information via the one or more transceivers to perform one or more sensing operations within a target altitude range; perform the one or more sensing operations within the target altitude range; and transmit sensing reports indicating one or more results of the one or more sensing operations via the one or more transceivers.

[0198] Clause 25. The UAV-UE as described in Clause 24, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction; or any combination thereof.

[0199] Clause 26. The UAV-UE according to any one of Clauses 24 to 25, wherein: the configuration information is received after the capability information is transmitted; or the configuration information is received before the capability information is transmitted.

[0200] Clause 27. The UAV-UE according to any one of Clauses 24 to 26, wherein the one or more sensing operations include: detecting one or more first reference signals; or transmitting one or more second reference signals via the one or more transceivers, or both.

[0201] Clause 28. The UAV-UE according to Clause 27, wherein the one or more sensing operations include one or more bi-station sensing operations, and wherein: the one or more first reference signals are received from a radio access network (RAN) node or from a different UAV-UE; or the one or more second reference signals are transmitted to a RAN node or a different UAV-UE.

[0202] Clause 29. UAV-UE according to any one of Clauses 24 to 28, wherein said one or more results include: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0203] Clause 30. The UAV-UE according to any one of Clauses 24 to 29, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using a first positioning method, and wherein the one or more processors are further configured individually or in combination to: receive via the one or more transceivers an indication for performing height determination using a second different positioning method; determine the updated height of the UAV-UE using the second different positioning method; and transmit capability information via the one or more transceivers, the capability information indicating at least the updated height of the UAV-UE based on the second different positioning method and the updated height uncertainty of the UAV-UE.

[0204] Clause 31. The UAV-UE as described in Clause 30, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) based positioning between the UAV-UE and a plurality of entities at different altitudes, wherein the plurality of entities includes one or more other UAV-UEs, one or more Transmit / Receive Points (TRPs), or a combination thereof.

[0205] Clause 32. The UAV-UE according to any one of Clauses 30 to 31, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) and DoA positioning between the UAV-UE and at least one entity having direction of arrival (DoA) measurement capability.

[0206] Clause 33. The UAV-UE according to any one of Clauses 24 to 32, wherein the capability information indicating the one or more vertical sensing capabilities of the UAV-UE includes an indication that the antenna sensing direction is omnidirectional or directional.

[0207] Clause 34. The UAV-UE according to any one of Clauses 24 to 33, wherein the configuration information includes a target height range, and wherein performing one or more sensing operations includes: performing the one or more sensing operations to sense a target object within the target height range.

[0208] Clause 35. UAV-UE pursuant to any one of Clauses 24 to 34, wherein the capability information is included in the sensing report.

[0209] Clause 36. A UAV-UE according to any one of Clauses 24 to 35, wherein, in order to receive the configuration information, the one or more processors are individually or in combination configured to: receive the configuration information from one or more RAN nodes via the one or more transceivers according to Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Media Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; receive the configuration information from one or more core network devices via the one or more transceivers according to Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; receive the configuration information from one or more servers implementing Sensing Management Function (SnMF) or Location Management Function (LMF) or both via the one or more transceivers according to a Layer 3 RRC Information Element (IE) of a Long Term Evolution (LTE) Positioning Protocol (LPP) or Dedicated Sensing Protocol; receive the configuration information from one or more other UEs via the one or more transceivers according to a sidelink protocol; or any combination thereof.

[0210] Clause 37. A UAV-UE pursuant to any one of Clauses 24 to 36, wherein, in order to transmit the sensing report, the one or more processors are individually or in combination configured to: transmit the sensing report to one or more RAN nodes via the one or more transceivers based on Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; transmit the sensing report to one or more core network devices via the one or more transceivers based on NAS or NGAP signaling; transmit the sensing report to one or more servers implementing SnMF or LMF or both via the one or more transceivers based on the Layer 3 RRC IE of the LPP protocol or a dedicated sensing protocol; transmit the sensing report to one or more other UEs via the one or more transceivers based on a sidelink protocol; or any combination thereof.

[0211] Clause 38. A network entity comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive capability information via the one or more transceivers indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); transmit configuration information via the one or more transceivers to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receive one or more sensing reports via the one or more transceivers, the one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0212] Clause 39. A network entity as described in Clause 38, wherein: the capability information is received before the configuration information is sent; or the capability information is received after the configuration information is sent.

[0213] Clause 40. A network entity pursuant to any one of Clauses 38 to 39, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction of the UAV-UE; or any combination thereof.

[0214] Clause 41. The network entity as described in Clause 40, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the uncertainty of the height of the UAV-UE exceeds a threshold amount, and wherein the one or more processors are further configured individually or in combination to: send an instruction to the UAV-UE via the one or more transceivers to perform height determination using a second different positioning method; and receive, via the one or more transceivers, an updated height of the UAV-UE determined using the second different positioning method.

[0215] Clause 42. A network entity pursuant to any one of Clauses 38 to 41, wherein the result of said one or more sensing operations includes: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0216] Clause 43. A network entity pursuant to any one of Clauses 38 to 42, wherein the one or more processors are further configured individually or in combination to determine the location of one or more target objects based on the one or more sensing reports.

[0217] Clause 44. A network entity pursuant to any one of Clauses 38 to 43, wherein the network entity comprises: a radio access network (RAN) node; one or more core network devices; one or more sense management devices; one or more location management devices; one or more other UEs; or any combination thereof.

[0218] Clause 45. A network entity according to any one of Clauses 38 to 44, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes transmit the configuration information using Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; one or more core network devices, wherein the one or more core network devices transmit the configuration information using Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; one or more sensor management devices, wherein the one or more sensor management devices implement Sensor Management Function (SnMF) using a dedicated sensing protocol; one or more location management devices, wherein the one or more location management devices implement Location Management Function (LMF) using a Long Term Evolution (LTE) Positioning Protocol (LPP); one or more other UEs, wherein the one or more other UEs use a sidelink protocol; or any combination thereof.

[0219] Clause 46. A network entity according to any one of Clauses 38 to 45, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes receive the one or more sensing reports according to Layer 1 Uplink Control Information / Uplink Data (L1 UCI / UL Data), Layer 2 MAC-CE, or Layer 3 RRC; one or more core network devices, wherein the one or more core network devices receive the one or more sensing reports according to NAS or NGAP signaling; one or more sensing management devices that implement Sensing Management Function (SnMF), wherein the one or more sensing management devices use a dedicated sensing protocol to receive the one or more sensing reports; one or more location management devices that implement Location Management Function (LMF), wherein the one or more location management devices use a Long Term Evolution (LTE) Positioning Protocol (LPP) to receive the one or more sensing reports; one or more other UEs, wherein the one or more other UEs receive the one or more sensing reports according to a sidelink protocol; or any combination thereof.

[0220] Clause 47. An unmanned aerial vehicle user equipment (UAV-UE) comprising: components for transmitting capability information indicating one or more vertical sensing capabilities of the UAV-UE; components for receiving configuration information to perform one or more sensing operations within a target altitude range; components for performing the one or more sensing operations within the target altitude range; and components for transmitting a sensing report indicating one or more results of the one or more sensing operations.

[0221] Clause 48. The UAV-UE as described in Clause 47, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction; or any combination thereof.

[0222] Clause 49. The UAV-UE according to any one of Clauses 47 to 48, wherein: the configuration information is received after the capability information is transmitted; or the configuration information is received before the capability information is transmitted.

[0223] Clause 50. The UAV-UE according to any one of Clauses 47 to 49, wherein the one or more sensing operations include: a component for detecting one or more first reference signals; or a component for transmitting one or more second reference signals, or both.

[0224] Clause 51. The UAV-UE according to Clause 50, wherein the one or more sensing operations include one or more bi-station sensing operations, and wherein: the one or more first reference signals are received from a radio access network (RAN) node or from a different UAV-UE; or the one or more second reference signals are transmitted to a RAN node or a different UAV-UE.

[0225] Clause 52. UAV-UE according to any one of Clauses 47 to 51, wherein said one or more results include: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0226] Clause 53. The UAV-UE according to any one of Clauses 47 to 52, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using a first positioning method, and the UAV-UE further includes: means for receiving an indication for performing height determination using a second different positioning method; means for determining an updated height of the UAV-UE using the second different positioning method; and means for transmitting capability information, the capability information indicating at least the updated height of the UAV-UE based on the second different positioning method and the updated height uncertainty of the UAV-UE.

[0227] Clause 54. The UAV-UE as described in Clause 53, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) based positioning between the UAV-UE and a plurality of entities at different altitudes, wherein the plurality of entities includes one or more other UAV-UEs, one or more Transmit / Receive Points (TRPs), or a combination thereof.

[0228] Clause 55. The UAV-UE according to any one of Clauses 53 to 54, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) and DoA positioning between the UAV-UE and at least one entity having direction of arrival (DoA) measurement capability.

[0229] Clause 56. The UAV-UE according to any one of Clauses 47 to 55, wherein the capability information indicating the one or more vertical sensing capabilities of the UAV-UE includes an indication that the antenna sensing direction is omnidirectional or directional.

[0230] Clause 57. The UAV-UE according to any one of Clauses 47 to 56, wherein the configuration information includes a target height range, and wherein performing one or more sensing operations includes: performing the one or more sensing operations to sense a target object within the target height range.

[0231] Clause 58. UAV-UE pursuant to any one of Clauses 47 to 57, wherein the capability information is included in the sensing report.

[0232] Clause 59. The UAV-UE according to any one of Clauses 47 to 58, wherein the component for receiving the configuration information comprises: a component for receiving the configuration information from one or more RAN nodes according to Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; a component for receiving the configuration information from one or more core network devices according to Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; a component for receiving the configuration information from one or more servers implementing Sensing Management Function (SnMF) or Location Management Function (LMF) or both according to a Layer 3 RRC Information Element (IE) of a Long Term Evolution (LTE) Positioning Protocol (LPP) or Dedicated Sensing Protocol; a component for receiving the configuration information from one or more other UEs according to a sidelink protocol; or any combination thereof.

[0233] Clause 60. A UAV-UE according to any one of Clauses 47 to 59, wherein the components for transmitting the sensing report include: components for transmitting the sensing report to one or more RAN nodes based on Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; components for transmitting the sensing report to one or more core network devices based on NAS or NGAP signaling; components for transmitting the sensing report to one or more servers implementing SnMF or LMF or both based on Layer 3 RRC IE of LPP protocol or dedicated sensing protocol; components for transmitting the sensing report to one or more other UEs based on sidelink protocol; or any combination thereof.

[0234] Clause 61. A network entity comprising: components for receiving capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); components for transmitting configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and components for receiving one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0235] Clause 62. The network entity as described in Clause 61, wherein: the capability information is received before the configuration information is sent; or the capability information is received after the configuration information is sent.

[0236] Clause 63. A network entity pursuant to any one of Clauses 61 to 62, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction of the UAV-UE; or any combination thereof.

[0237] Clause 64. The network entity as described in Clause 63, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the uncertainty of the height of the UAV-UE exceeds a threshold amount, and the network entity further includes: components for sending an instruction to the UAV-UE for performing height determination using a second different positioning method; and components for receiving an updated height of the UAV-UE determined using the second different positioning method.

[0238] Clause 65. A network entity pursuant to any one of Clauses 61 to 64, wherein the result of said one or more sensing operations includes: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0239] Clause 66. The network entity according to any one of Clauses 61 to 65, the network entity further comprising: a component for determining the location of one or more target objects based on the one or more sensing reports.

[0240] Clause 67. A network entity pursuant to any one of Clauses 61 to 66, wherein the network entity comprises: a radio access network (RAN) node; one or more core network devices; one or more sense management devices; one or more location management devices; one or more other UEs; or any combination thereof.

[0241] Clause 68. A network entity according to any one of Clauses 61 to 67, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes transmit the configuration information using Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; one or more core network devices, wherein the one or more core network devices transmit the configuration information using Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; one or more sensor management devices, wherein the one or more sensor management devices implement Sensor Management Function (SnMF) using a dedicated sensing protocol; one or more location management devices, wherein the one or more location management devices implement Location Management Function (LMF) using a Long Term Evolution (LTE) Positioning Protocol (LPP); one or more other UEs, wherein the one or more other UEs use a sidelink protocol; or any combination thereof.

[0242] Clause 69. A network entity according to any one of Clauses 61 to 68, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes receive the one or more sensing reports according to Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; one or more core network devices, wherein the one or more core network devices receive the one or more sensing reports according to NAS or NGAP signaling; one or more sensing management devices that implement a sensing management function (SnMF), wherein the one or more sensing management devices use a dedicated sensing protocol to receive the one or more sensing reports; one or more location management devices that implement a location management function (LMF), wherein the one or more location management devices use a Long Term Evolution (LTE) Positioning Protocol (LPP) to receive the one or more sensing reports; one or more other UEs, wherein the one or more other UEs receive the one or more sensing reports according to a sidelink protocol; or any combination thereof.

[0243] Clause 70. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by an unmanned aerial vehicle user equipment (UAV-UE), cause the UAV-UE to: transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE; receive configuration information to perform one or more sensing operations within a target altitude range; perform the one or more sensing operations within the target altitude range; and transmit a sensing report indicating one or more results of the one or more sensing operations.

[0244] Clause 71. The non-transitory computer-readable medium pursuant to Clause 70, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction; or any combination thereof.

[0245] Clause 72. A non-transitory computer-readable medium according to any one of Clauses 70 to 71, wherein: the configuration information is received after the capability information is transmitted; or the configuration information is received before the capability information is transmitted.

[0246] Clause 73. A non-transitory computer-readable medium according to any one of Clauses 70 to 72, wherein the one or more sensing operations include: detecting one or more first reference signals; or transmitting one or more second reference signals, or both.

[0247] Clause 74. The non-transitory computer-readable medium according to Clause 73, wherein the one or more sensing operations include one or more bi-station sensing operations, and wherein: the one or more first reference signals are received from a radio access network (RAN) node or from different UAV-UEs; or the one or more second reference signals are transmitted to a RAN node or different UAV-UEs.

[0248] Clause 75. A non-transitory computer-readable medium according to any one of Clauses 70 to 74, wherein said one or more results include: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0249] Clause 76. A non-transitory computer-readable medium according to any one of Clauses 70 to 75, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using a first positioning method, and the non-transitory computer-readable medium further includes computer-executable instructions that, when executed by the UAV-UE, cause the UAV-UE to: receive an indication for performing height determination using a second different positioning method; determine an updated height of the UAV-UE using the second different positioning method; and transmit capability information, the capability information indicating at least the updated height of the UAV-UE based on the second different positioning method and the updated height uncertainty of the UAV-UE.

[0250] Clause 77. The non-transitory computer-readable medium as described in Clause 76, wherein the first positioning method or the second different positioning method comprises round-trip time (RTT) based positioning between the UAV-UE and a plurality of entities at different altitudes, wherein the plurality of entities includes one or more other UAV-UEs, one or more Transmit / Receive Points (TRPs), or a combination thereof.

[0251] Clause 78. A non-transitory computer-readable medium according to any one of Clauses 76 to 77, wherein the first positioning method or the second different positioning method comprises round-trip time (RTT) and DoA positioning between the UAV-UE and at least one entity having direction of arrival (DoA) measurement capability.

[0252] Clause 79. A non-transitory computer-readable medium according to any one of Clauses 70 to 78, wherein the capability information indicating the one or more vertical sensing capabilities of the UAV-UE includes an indication that the antenna sensing direction is omnidirectional or directional.

[0253] Clause 80. A non-transitory computer-readable medium according to any one of Clauses 70 to 79, wherein the configuration information includes a target height range, and wherein performing one or more sensing operations includes: performing the one or more sensing operations to sense a target object within the target height range.

[0254] Clause 81. A non-transitory computer-readable medium according to any one of Clauses 70 to 80, wherein the capability information is included in the sensing report.

[0255] Clause 82. A non-transitory computer-readable medium according to any one of Clauses 70 to 81, wherein the computer-executable instructions that, when executed by the UAV-UE, cause the UAV-UE to receive the configuration information, comprise: computer-executable instructions that, when executed by the UAV-UE, cause the UAV-UE to: receive the configuration information from one or more RAN nodes according to Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Media Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; receive the configuration information from one or more core network devices according to Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; receive the configuration information from one or more servers implementing Sensing Management Function (SnMF) or Location Management Function (LMF), or both, according to a Layer 3 RRC Information Element (IE) of a Long Term Evolution (LTE) Positioning Protocol (LPP) or Dedicated Sensing Protocol; receive the configuration information from one or more other UEs according to a sidelink protocol; or any combination thereof.

[0256] Clause 83. A non-transitory computer-readable medium according to any one of Clauses 70 to 82, wherein the computer-executable instructions that, when executed by the UAV-UE, cause the UAV-UE to send the sensing report comprise: computer-executable instructions that, when executed by the UAV-UE, cause the UAV-UE to: send the sensing report to one or more RAN nodes according to Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; send the sensing report to one or more core network devices according to NAS or NGAP signaling; send the sensing report to one or more servers implementing SnMF or LMF or both according to the Layer 3 RRC IE of the LPP protocol or a dedicated sensing protocol; send the sensing report to one or more other UEs according to a sidelink protocol; or any combination thereof.

[0257] Clause 84. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: receive capability information indicating one or more vertical sensing capabilities of an unmanned aerial vehicle user equipment (UAV-UE); transmit configuration information to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; and receive one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

[0258] Clause 85. A non-transitory computer-readable medium as described in Clause 84, wherein the capability information is received before the configuration information is transmitted; or the capability information is received after the configuration information is transmitted.

[0259] Clause 86. A non-transitory computer-readable medium pursuant to any one of Clauses 84 to 85, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: the height of the UAV-UE; the height uncertainty of the UAV-UE; the antenna sensing direction of the UAV-UE; or any combination thereof.

[0260] Clause 87. A non-transitory computer-readable medium as described in Clause 86, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the uncertainty of the height of the UAV-UE exceeds a threshold amount, and wherein the instruction further causes the network entity to: send an instruction to the UAV-UE to perform height determination using a second different positioning method; and receive an updated height of the UAV-UE determined using the second different positioning method.

[0261] Clause 88. A non-transitory computer-readable medium according to any one of Clauses 84 to 87, wherein the result of said one or more sensing operations includes: measurement of one or more first reference signals; or transmission information of one or more second reference signals.

[0262] Clause 89. A nontransitory computer-readable medium according to any one of Clauses 84 to 88, the nontransitory computer-readable medium further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine the location of one or more target objects based on the one or more sensing reports.

[0263] Clause 90. A nontransitory computer-readable medium pursuant to any one of Clauses 84 to 89, wherein the network entity comprises: a radio access network (RAN) node; one or more core network devices; one or more sense management devices; one or more location management devices; one or more other UEs; or any combination thereof.

[0264] Clause 91. A non-transitory computer-readable medium according to any one of Clauses 84 to 90, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes transmit the configuration information using Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Media Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling; one or more core network devices, wherein the one or more core network devices transmit the configuration information using Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling; one or more sensor management devices, wherein the one or more sensor management devices implement a Sensor Management Function (SnMF) using a dedicated sensing protocol; one or more location management devices, wherein the one or more location management devices implement a Location Management Function (LMF) using a Long Term Evolution (LTE) Positioning Protocol (LPP); one or more other UEs, wherein the one or more other UEs use a sidelink protocol; or any combination thereof.

[0265] Clause 92. A non-transitory computer-readable medium pursuant to any one of Clauses 84 to 91, wherein the network entity comprises: one or more RAN nodes, wherein the one or more RAN nodes receive the one or more sensing reports according to Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; one or more core network devices, wherein the one or more core network devices receive the one or more sensing reports according to NAS or NGAP signaling; one or more sensing management devices implementing a sensing management function (SnMF), wherein the one or more sensing management devices use a dedicated sensing protocol to receive the one or more sensing reports; one or more location management devices implementing a location management function (LMF), wherein the one or more location management devices use a Long Term Evolution (LTE) Positioning Protocol (LPP) to receive the one or more sensing reports; one or more other UEs, wherein the one or more other UEs receive the one or more sensing reports according to a sidelink protocol; or any combination thereof.

[0266] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and arts. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0267] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

[0268] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0269] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

[0270] In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disks and optical discs include: compact optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0271] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. For example, the functions, steps, and / or actions of the method claims according to aspects of this disclosure described herein need not be performed in any particular order. Furthermore, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly stated otherwise. Additionally, as used herein, the terms “set,” “group,” etc., are intended to include one or more of the stated elements. Furthermore, as used herein, the terms “having,” “comprising,” “including,” etc., do not exclude the presence of one or more additional elements (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”), or these alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Additionally, although components, functions, actions, and instructions may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “described” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” include “one” component, function, action, or instruction that performs or is capable of performing the described or claimed functionality, and also include “two or more” components, functions, actions, or instructions that perform or are capable of performing the described or claimed functionality in combination.

Claims

1. An unmanned aerial vehicle user equipment (UAV-UE), the UAV-UE comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: Transmit capability information indicating one or more vertical sensing capabilities of the UAV-UE via the one or more transceivers; Receive configuration information via the one or more transceivers to perform one or more sensing operations within the target height range; Perform the one or more sensing operations within the target height range; as well as A sensing report indicating one or more results of the one or more sensing operations is transmitted via the one or more transceivers.

2. The UAV-UE of claim 1, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of the following: The height of the UAV-UE; The high degree of uncertainty of the UAV-UE; Antenna sensing direction; or Any combination of them.

3. The UAV-UE according to claim 1, wherein: Receive the configuration information after sending the capability information; or The configuration information is received before the capability information is sent.

4. The UAV-UE according to claim 1, wherein the one or more sensing operations include: Detect one or more first reference signals; or One or more second reference signals may be transmitted via the one or more transceivers, or both.

5. The UAV-UE of claim 4, wherein the one or more sensing operations include one or more bi-station sensing operations, and wherein: Receive the one or more first reference signals from a radio access network (RAN) node or from different UAV-UEs; or The one or more second reference signals are sent to the RAN node or different UAV-UEs.

6. The UAV-UE according to claim 1, wherein one or more results include: Measurement of one or more first reference signals; or Transmission information of one or more second reference signals.

7. The UAV-UE of claim 1, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using the first positioning method, and wherein the one or more processors are further configured individually or in combination to: Receive instructions via the one or more transceivers for performing altitude determination using a second, different positioning method; The updated altitude of the UAV-UE is determined using the second different positioning method; and Capability information is transmitted via the one or more transceivers, the capability information indicating at least the updated altitude of the UAV-UE based on the second different positioning method and the updated altitude uncertainty of the UAV-UE.

8. The UAV-UE of claim 7, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) based positioning between the UAV-UE and a plurality of entities at different altitudes, wherein the plurality of entities includes one or more other UAV-UEs, one or more Transmit / Receive Points (TRPs), or a combination thereof.

9. The UAV-UE of claim 7, wherein the first positioning method or the second different positioning method includes round-trip time (RTT) and DoA positioning between the UAV-UE and at least one entity having direction of arrival (DoA) measurement capability.

10. The UAV-UE of claim 1, wherein the capability information indicating the one or more vertical sensing capabilities of the UAV-UE includes an indication that the antenna sensing direction is omnidirectional or directional.

11. The UAV-UE of claim 1, wherein the configuration information includes a target height range, and wherein performing one or more sensing operations includes: Perform one or more sensing operations to sense target objects within the target height range.

12. The UAV-UE according to claim 1, wherein the capability information is included in the sensing report.

13. The UAV-UE of claim 1, wherein, in order to receive the configuration information, the one or more processors are individually or in combination configured to: The configuration information is received from one or more RAN nodes via the one or more transceivers according to Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling. The configuration information is received from one or more core network devices via one or more transceivers according to Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling. The configuration information is received via one or more transceivers from one or more servers implementing Sensing Management Function (SnMF) or Location Management Function (LMF) or both, according to the Layer 3 RRC Information Element (IE) of the Long Term Evolution (LTE) Positioning Protocol (LPP) or Dedicated Sensing Protocol. According to the sidelink protocol, the configuration information is received from one or more other UEs via the one or more transceivers; or Any combination of them.

14. The UAV-UE of claim 1, wherein, in order to send the sensing report, the one or more processors are configured individually or in combination to: Based on Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC, the sensing report is sent to one or more RAN nodes via the one or more transceivers; Based on NAS or NGAP signaling, the sensing report is sent to one or more core network devices via the one or more transceivers; According to the LPP protocol or the Layer 3 RRC IE of a dedicated sensing protocol, the sensing report is sent via the one or more transceivers to one or more servers implementing SnMF or LMF or both. According to the sidelink protocol, the sensing report is sent to one or more other UEs via the one or more transceivers; or Any combination of them.

15. A network entity, the network entity comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: Receive capability information indicating one or more vertical sensing capabilities of unmanned aerial vehicle user equipment (UAV-UE) via the one or more transceivers; Configuration information is transmitted via the one or more transceivers to perform one or more sensing operations within one or more target altitude ranges of the UAV-UE; as well as One or more sensing reports are received via the one or more transceivers, the one or more sensing reports indicating the results of the one or more sensing operations obtained according to the configuration information.

16. The network entity according to claim 15, wherein: Receive the capability information before sending the configuration information; or The capability information is received after the configuration information is sent.

17. The network entity of claim 15, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: The height of the UAV-UE; The high degree of uncertainty of the UAV-UE; UAV-UE antenna sensing direction; or Any combination of them.

18. The network entity of claim 17, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the height uncertainty of the UAV-UE exceeds a threshold amount, and wherein the one or more processors are further configured individually or in combination to: Sending instructions to the UAV-UE via the one or more transceivers for performing altitude determination using a second, different positioning method; and The updated altitude determined by the UAV-UE using the second different positioning method is received via the one or more transceivers.

19. The network entity of claim 15, wherein the result of said one or more sensing operations includes: Measurement of one or more first reference signals; or Transmission information of one or more second reference signals.

20. The network entity of claim 15, wherein the one or more processors are further configured individually or in combination to: The location of one or more target objects is determined based on the one or more sensing reports.

21. The network entity according to claim 15, wherein the network entity comprises: Radio Access Network (RAN) node; One or more core network devices; One or more sensor management devices; One or more location management devices; One or more other UEs; Or any combination thereof.

22. The network entity according to claim 15, wherein the network entity comprises: One or more RAN nodes, wherein the one or more RAN nodes use Layer 1 Downlink Control Information (DCI) signaling, Layer 2 Medium Access Control-Control Element (MAC-CE) signaling, or Layer 3 Radio Resource Control (RRC) signaling to transmit the configuration information; One or more core network devices, wherein the one or more core network devices use Non-Access Layer (NAS) or Next Generation Application Protocol (NGAP) signaling to send the configuration information; One or more sensor management devices, wherein the one or more sensor management devices use a dedicated sensing protocol to implement sensor management functions (SnMF). One or more location management devices, which use the Long Term Evolution (LTE) Positioning Protocol (LPP) to implement Location Management Function (LMF); One or more other UEs, wherein the one or more other UEs use a sidelink protocol; or Any combination of them.

23. The network entity according to claim 15, wherein the network entity comprises: One or more RAN nodes, wherein the one or more RAN nodes receive the one or more sensing reports based on Layer 1 uplink control information / uplink data (L1 UCI / UL data), Layer 2 MAC-CE, or Layer 3 RRC; One or more core network devices, wherein the one or more core network devices receive the one or more sensing reports according to NAS or NGAP signaling; One or more sensing management devices implement a sensing management function (SnMF), wherein the one or more sensing management devices use a dedicated sensing protocol to receive the one or more sensing reports; One or more location management devices that implement location management function (LMF), wherein the one or more location management devices use the Long Term Evolution (LTE) Positioning Protocol (LPP) to receive the one or more sensing reports; One or more other UEs, wherein said one or more other UEs receive said one or more sensing reports according to a sidelink protocol; or Any combination of them.

24. A method performed at an unmanned aerial vehicle user equipment (UAV-UE), the method comprising: Send capability information indicating one or more vertical sensing capabilities of the UAV-UE; Receive configuration information to perform one or more sensing operations within the target height range; Perform the one or more sensing operations within the target height range; as well as Send a sensing report indicating one or more results of the one or more sensing operations.

25. The method of claim 24, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: The height of the UAV-UE; The high degree of uncertainty of the UAV-UE; Antenna sensing direction; or Any combination of them.

26. The method of claim 24, wherein the one or more sensing operations comprise one or more bi-station sensing operations, and wherein: Receive one or more first reference signals from a radio access network (RAN) node or from different UAV-UEs; or One or more second reference signals are sent to the RAN node or different UAV-UEs.

27. The method of claim 24, wherein the one or more vertical sensing capabilities of the UAV-UE include at least an indication of the height uncertainty of the UAV-UE and an indication of the height of the UAV-UE determined using a first positioning method, and the method further comprises: Receive instructions to perform altitude determination using a second, different positioning method; The updated altitude of the UAV-UE is determined using the second different positioning method; as well as Send capability information, which at least indicates the updated altitude of the UAV-UE based on the second different positioning method and the updated altitude uncertainty of the UAV-UE.

28. A method performed at a network entity, the method comprising: Receive capability information indicating one or more vertical sensing capabilities of the unmanned aerial vehicle user equipment (UAV-UE); Send configuration information to perform one or more sensing operations within one or more target height ranges of the UAV-UE; as well as Receive one or more sensing reports, which indicate the results of the one or more sensing operations obtained based on the configuration information.

29. The method of claim 28, wherein the one or more vertical sensing capabilities of the UAV-UE include one or more indications of: The height of the UAV-UE; The high degree of uncertainty of the UAV-UE; UAV-UE antenna sensing direction; or Any combination of them.

30. The method of claim 29, wherein a first positioning method is used to determine the height of the UAV-UE, wherein the height uncertainty of the UAV-UE exceeds a threshold amount, and the method further comprises: Send an instruction to the UAV-UE to perform altitude determination using a second, different positioning method; as well as The updated altitude determined by the UAV-UE using the second different positioning method is received.

Images