CN117355882A

CN117355882A - Location assistance data associated with over-the-air user equipment

Info

Publication number: CN117355882A
Application number: CN202280035902.1A
Authority: CN
Inventors: A·里科阿尔瓦里尼奥; A·马诺拉科斯; C·萨哈; 刘乐; 武田一树; U·蒲亚尔
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-05-24
Filing date: 2022-04-01
Publication date: 2024-01-05
Also published as: US20240201309A1; EP4348623A1; WO2022251760A1; KR20240010463A

Abstract

Techniques for wireless communication are disclosed. In an aspect, a UE sends a message to a location server (e.g., a Location Management Function (LMF)) that includes information based on an over-the-air UE that the UE is configured to be capable of flying. The location server selects assistance data based in part on the information in the message and transmits the assistance data to the UE.

Description

Location assistance data associated with over-the-air user equipment

Technical Field

Aspects of the present disclosure relate generally to wireless communications.

Background

Wireless communication systems have experienced multiple generations of development including first generation analog radiotelephone services (1G), second generation (2G) digital radiotelephone services (including temporary 2.5G and 2.75G networks), third generation (3G) high speed data, internet-enabled wireless services, and fourth generation (4G) services (e.g., long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are used, including cellular and Personal Communication Services (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (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 the like.

The fifth generation (5G) wireless standard, known as New Radio (NR), requires, among other improvements, higher data transfer speeds, a greater number of connections, and better coverage. According to the next generation mobile network alliance, the 5G standard is designed to provide tens of megabits per second data rate to each of tens of thousands of users, and to provide 1 gigabit per second data rate to tens of workers on an office floor. To support large sensor deployments, hundreds of thousands of simultaneous connections should be supported. Therefore, the spectral efficiency of 5G mobile communication should be significantly improved compared to the current 4G standard. Furthermore, the signaling efficiency should be improved and the latency should be significantly reduced compared to the current standard.

Disclosure of Invention

The following presents a simplified summary in relation to one or more aspects disclosed herein. Accordingly, the following summary should not be considered an extensive overview of all contemplated aspects, nor should it be considered to identify key or critical elements of all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the sole purpose of the summary below is to present some concepts related to one or more aspects related to the mechanisms disclosed herein in a simplified form prior to the detailed description that is presented below.

In one aspect, a method of operating a User Equipment (UE) includes: transmitting a message to a location server including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server based in part on the information in the message.

In some aspects, the method includes receiving a capability request from the location server, wherein the message is sent in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information indicates that the UE is configured as an over-the-air UE.

In some aspects, the information indicates whether the UE is engaged in a flight state or a ground state.

In some aspects, the information indicates that the UE is engaged in a flight state, and the information also indicates an altitude or elevation of the UE.

In some aspects, the information includes flight path information.

In some aspects, the flight path information includes a sequence of waypoints and associated timestamps.

In some aspects, the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

In some aspects, the flight path information includes a trajectory and a speed of the UE.

In some aspects, the assistance data includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight, on-air UE.

In some aspects, the assistance data includes information associated with one or more base stations that are remote from the UE, wherein one or more other intermediate base stations that are closer to the UE are omitted from the assistance data.

In some aspects, the network entity includes a Location Management Function (LMF).

In one aspect, a method of operating a location server includes: receiving a message from a User Equipment (UE) comprising information based on an over-the-air UE the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting the assistance data to the UE.

In some aspects, the method comprises: a capability request is sent to the UE, wherein the message is received in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In an aspect, a User Equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmitting, via at least one transceiver, a message to a location server, the message including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server via the at least one transceiver based in part on the information in the message.

In some aspects, the at least one processor is further configured to: a capability request is received from a location server via at least one transceiver, wherein the message is sent in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receiving, via at least one transceiver, a message from a User Equipment (UE), the message including information based on an over-the-air UE the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting assistance data to the UE via the at least one transceiver.

In some aspects, the at least one processor is further configured to: a capability request is sent to the UE via the at least one transceiver, wherein the message is received in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In an aspect, a User Equipment (UE) includes: means for sending a message to a location server including information based on an over-the-air UE that the UE is configured to be capable of flying; and means for receiving assistance data from the location server based in part on the information in the message.

In some aspects, the method includes means for receiving a capability request from the location server, wherein the message is sent in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In one aspect, a location server includes: means for receiving a message from a User Equipment (UE) comprising information based on an over-the-air UE the UE is configured to be capable of flying; means for selecting assistance data based in part on the information in the message; and means for transmitting the assistance data to the UE.

In some aspects, the method comprises: means for sending a capability request to the UE, wherein the message is received in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to: transmitting a message to a location server including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server based in part on the information in the message.

In some aspects, the one or more instructions further cause the UE to: a capability request is received from the location server, wherein the message is sent in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: receiving a message from a User Equipment (UE) comprising information based on an over-the-air UE the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting the assistance data to the UE.

In some aspects, the one or more instructions further cause the location server to: a capability request is sent to the UE, wherein the message is received in response to the capability request.

In some aspects, the message corresponds to a request for assistance data.

In some aspects, the message corresponds to a capability indication.

In some aspects, the information includes flight path information.

Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the drawings and the detailed description.

Drawings

The accompanying drawings are provided to help describe various aspects of the disclosure and are provided solely for illustration of these aspects and not limitation thereof.

Fig. 1 illustrates an example wireless communication system in accordance with aspects of the present disclosure.

Fig. 2A and 2B illustrate example wireless network structures in accordance with aspects of the present disclosure.

Fig. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a User Equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

Fig. 4 illustrates a channel model 400 for a UAV in accordance with an aspect of the disclosure.

Fig. 5-6 illustrate example communication methods in accordance with aspects of the present disclosure.

Fig. 7 illustrates an example embodiment of the processes of fig. 5-6 in accordance with an aspect of the present disclosure.

Fig. 8 illustrates an example embodiment of the processes of fig. 5-6 in accordance with an aspect of the present disclosure.

Fig. 9 illustrates a communication system in accordance with an aspect of the disclosure.

Fig. 10 illustrates a communication system in accordance with an aspect of the disclosure.

Detailed Description

In the following description and related drawings, aspects of the disclosure are provided for various examples provided for purposes of illustration. Alternate aspects may be devised without departing from the scope of the disclosure. Furthermore, well-known elements in this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

The use of the words "exemplary" and/or "example" herein mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" and/or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the feature, advantage or mode of operation discussed.

Those of skill in the art will understand that information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, desired design, corresponding techniques, etc.

Further, aspects may be described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application Specific Integrated Circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Further, the sequence of action(s) described herein may be considered to be embodied entirely within any form of non-transitory computer readable storage medium having stored thereon a corresponding set of computer instructions that upon execution would cause or instruct an associated processor of a device to perform the functions described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. Moreover, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to" perform the described action.

As used herein, unless otherwise indicated, the terms "user equipment" (UE) and "base station" (BS) are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). In general, a UE may be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset location device, wearable device (e.g., smart watch, glasses, augmented Reality (AR)/Virtual Reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), internet of things (IoT) device, etc. The UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "access terminal" or "AT," "client device," "wireless device," "subscriber terminal," "subscriber station," "user terminal" or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect with external networks such as the internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or to the internet are possible for the UE, such as through a wired access network, a Wireless Local Area Network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), and so forth.

A base station may communicate with UEs according to one of several RATs, depending on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), a network Node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gndeb), etc. The base station may be primarily used to support wireless access for UEs, including supporting data, voice, and/or signaling connections for the supported UEs. In some systems, the base station may provide only edge node signaling functionality, while in other systems, the base station may provide additional control and/or network management functionality. The communication link through which a UE can signal to a base station is called an Uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which a base station can signal to a 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 or downlink/forward traffic channel.

The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be co-located. For example, in the case where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to the cell (or several cell sectors) of the base station. Where the term "base station" refers to a plurality of co-located physical TRPs, the physical TRPs may be an array of antennas of the base station (e.g., in a Multiple Input Multiple Output (MIMO) system or where the base station uses beamforming). In case the term "base station" refers to a plurality of non-co-located physical TRP, the physical TRP may be a Distributed Antenna System (DAS) (network of spatially separated antennas connected to a common source via a transmission medium) or a Remote Radio Head (RRH) (remote base station connected to a serving base station). Alternatively, the non-collocated physical TRP may be a serving base station receiving measurement reports from the UE and a neighbor base station whose reference Radio Frequency (RF) signal is being measured by the UE. Since TRP is the point through which a base station transmits and receives wireless signals, as used herein, reference to transmission from or reception at a base station will be understood to refer to a particular TRP of a base station.

In some implementations supporting UE positioning, a base station may not support wireless access for the UE (e.g., may not support data, voice, and/or signaling connections for the UE), but may instead send reference signals to the UE to be measured by the UE, and/or may receive and measure signals sent by the UE. Such base stations may be referred to as positioning beacons (e.g., when transmitting signals to the UE), and/or location measurement units (e.g., when receiving and measuring signals from the UE).

An "RF signal" comprises an electromagnetic wave of a given frequency that transmits information through a space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of the RF signal through the multipath channel, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and the 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 as a "signal," where the term "signal" refers to a wireless signal or an RF signal as is clear from the context.

Fig. 1 illustrates an example wireless communication system 100 in accordance with aspects of the present disclosure. 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 "BSs") and various UEs 104. Base station 102 may include a macrocell base station (high power cellular base station) and/or a small cell base station (low power cellular base station). In an aspect, the macrocell base station 102 may include an eNB and/or a ng-eNB (where the wireless communication system 100 corresponds to an LTE network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include a femtocell, a picocell, a microcell, and the like.

The base stations 102 may collectively form a RAN and connect with a core network 174 (e.g., an Evolved Packet Core (EPC) or a 5G core (5 GC)) through a backhaul link 122 and one or more location servers 172 (e.g., a Location Management Function (LMF) or a Secure User Plane Location (SUPL) location platform (SLP)) through the core network 174. The location server(s) 172 may be part of the core network 174 or may be external to the core network 174. Among other functions, the base station 102 may perform functions related to one or more of the following: transport user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC/5 GC) over a backhaul link 134, which may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may 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., through some frequency resources called carrier frequencies, component carriers, bands, etc.) and may be associated with an identifier (e.g., a Physical Cell Identifier (PCI), enhanced Cell Identifier (ECI), virtual Cell Identifier (VCI), cell Global Identifier (CGI), etc.) used to distinguish cells operating on the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine Type Communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that provide access to different types of UEs. Since a cell is supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., sector) of a base station, where carrier frequencies may be detected and used for communications within certain portions of geographic coverage area 110.

Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 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 macrocell base stations 102. A network comprising small cells and macro cell base stations may be referred to as a heterogeneous network. The heterogeneous network may also include home enbs (henbs) that may provide services to a restricted group called a Closed Subscriber Group (CSG).

The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use MIMO antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. Communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

The wireless communication system 100 may also include a Wireless Local Area Network (WLAN) Access Point (AP) 150 that communicates with WLAN Stations (STAs) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, WLAN STA 152 and/or WLAN AP 150 may perform Clear Channel Assessment (CCA) or Listen Before Talk (LBT) prior to communication to determine whether the channel is available.

The small cell base station 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5GHz unlicensed spectrum as used by the WLAN AP 150. The use of small cell base stations 102' of LTE/5G in unlicensed spectrum may improve coverage and/or increase capacity of the access network. NR in the 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 multewire.

The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which mmW base station 180 may communicate with the UE 182 at and/or near mmW frequencies. Extremely High Frequency (EHF) is a part of the RF in the electromagnetic spectrum. EHF ranges from 30GHz to 300GHz and has a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. The near mmW can be extended down to a 3GHz frequency of 100 mm wavelength. The ultra-high frequency (SHF) band extends between 3GHz and 30GHz, which is also known as a centimeter wave. Communications using mmW/near mmW radio bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) on the mmW communication link 184 to compensate for extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing description is merely exemplary and should not be construed as limiting the various aspects disclosed herein.

Transmit beamforming is a technique for focusing RF signals in a particular direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that particular direction, providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitted, the network node may control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a "phased array" or "antenna array") that generates beams that may be "steered" to RF waves directed in different directions without having to physically move the antennas. In particular, RF currents from the transmitters are fed to the respective antennas in an accurate phase relationship so that radio waves from the different antennas are superimposed together to increase radiation in the desired direction while canceling to suppress radiation in the undesired direction.

The transmit beams may be quasi-co-located, meaning that they appear to have the same parameters to the receiver (e.g., UE) regardless of whether the transmit antennas of the network nodes themselves are physically co-located. In NR, there are four types of quasi co-located (QCL) relationships. In particular, a QCL relationship of a given type means that certain parameters with respect to the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type a, the receiver may use the source reference RF signal to estimate the doppler shift, doppler spread, average delay and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver may use the source reference RF signal to estimate the doppler shift and doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver may use the source reference RF signal to estimate the doppler shift and the average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

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 the antenna array in a particular direction, and/or adjust the phase setting of the antenna array in a particular direction to amplify (e.g., increase the gain level of) an RF signal received from that direction. Thus, when the receiver is considered to be beamforming in a direction, this means that the beam gain in that direction is high relative to the beam gain in the other directions, or that the beam gain in that direction is highest compared to the beam gain in that direction of all other receive beams available to the receiver. 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.) for the RF signal received from that direction.

The transmit and receive beams may be spatially correlated. The spatial relationship means that parameters of the second beam (e.g., a transmit or receive beam) for the second reference signal can be derived from information about the first beam (e.g., a receive beam or a transmit beam) for the first reference signal. For example, the UE may receive a reference downlink reference signal (e.g., a Synchronization Signal Block (SSB)) from the base station using a particular receive beam. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a Sounding Reference Signal (SRS)) to the base station based on the parameters of the receive beam.

Note that the "downlink" beam may be either a transmit beam or a receive beam, depending on the entity forming the beam. For example, if the base station is forming a downlink beam to transmit reference signals to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, it is a reception beam for receiving a downlink reference signal. Similarly, an "uplink" beam may be either a transmit beam or a receive beam, depending on the entity that forms the beam. For example, if the base station is forming an uplink beam, it is an uplink reception beam, and if the UE is forming an uplink beam, it is an uplink transmission beam.

In 5G, the frequency spectrum in which the wireless node (e.g., base station 102/180, UE 104/182) operates is divided into multiple frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR 2). The mmW frequency band typically includes FR2, FR3 and FR4 frequency ranges. Thus, the terms "mmW" and "FR2" or "FR3" or "FR4" are generally used interchangeably.

In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR 1) used by the UE 104/182 and the cell in which the UE 104/182 either 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 may be a carrier in a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR 2), which may be configured once an RRC connection is established between the UE 104 and the anchor carrier, and which may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals, e.g. those specific to the UE, may not be present in the secondary carrier, since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104/182 in a cell may have different downlink primary carriers. The same is true for 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 the different carriers. Since a "serving cell" (which is a PCell or SCell) corresponds to a carrier frequency/component carrier on which some base stations are communicating, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

For example, still referring to fig. 1, one of the frequencies used by the macrocell base station 102 may be an anchor carrier (or "PCell") and the other frequencies used by the macrocell base station 102 and/or the mmW base station 180 may be secondary carriers ("scells"). The simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission rate and/or reception rate. For example, an aggregated carrier of two 20MHz in a multi-carrier system would theoretically typically result in a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate obtained by a single 20MHz carrier.

In the example of fig. 1, any of the UEs shown (shown as a single UE 104 in fig. 1 for simplicity) may receive signals 124 from one or more earth orbit Space Vehicles (SVs) 112 (e.g., satellites). In an aspect, SV 112 may be part of a satellite positioning system that UE 104 may use as a standalone location information source. Satellite positioning systems typically include a system of transmitters (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and/or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geolocation information from SV 112.

In satellite positioning systems, the use of signals 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. For example, SBAS may include augmentation system(s) providing integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), european Geostationary Navigation Overlay Service (EGNOS), multi-function satellite augmentation system (MSAS), global Positioning System (GPS) assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN), etc. Thus, 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.

In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as modified base station 102 (without a ground antenna) or a network node in a 5 GC. This element will in turn provide access to other elements in the 5G network and ultimately to entities outside the 5G network such as internet web servers and other user devices. In this manner, UE 104 may receive communication signals (e.g., signal 124) from SV 112 instead of or in addition to receiving communication signals from ground base station 102, from SV 112.

With increased data rates and reduced delays of NRs, etc., vehicle-to-everything (V2X) communication technologies are being implemented to support Intelligent Transport System (ITS) applications, such as wireless communication between vehicles (vehicle-to-vehicle (V2V)), wireless communication between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and wireless communication between vehicles and pedestrians (vehicle-to-pedestrian (V2P)). The goal is that the vehicle is able to sense its surrounding environment and communicate this information to other vehicles, infrastructure and personal mobile devices. Such vehicle communications would enable security, mobility and environmental advances not provided by current technology. Once fully implemented, this technique is expected to reduce undamaged vehicle collisions by 80%.

Still referring to fig. 1, the wireless communication system 100 may include a plurality of V-UEs 160, and the V-UEs 160 may communicate with the base station 102 over the communication link 120 (e.g., using a Uu interface). V-UEs 160 may also communicate directly with each other via wireless side-links 162, with roadside access points 164 (also referred to as "roadside units") via wireless side-links 166, or with UEs 104 via wireless side-links 168. The wireless side-link (or just "side-link") is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without requiring communication through a base station. The side-link communication may be unicast or multicast and may be used for device-to-device (D2D) media sharing, V2V communication, V2X communication (e.g., cellular V2X (cV 2X) communication, enhanced V2X (eV 2X) communication, etc.), emergency rescue applications, and the like. One or more of a group of V-UEs 160 utilizing side-link communication may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside of the geographic coverage area 110 of the base station 102 or otherwise unable to receive transmissions from the base station 102. In some cases, multiple sets of V-UEs 160 communicating via side-link communications may utilize a one-to-many (1:M) system, with each V-UE 160 transmitting to each other V-UE 160 in the set. In some cases, base station 102 facilitates scheduling resources for side-link communications. In other cases, side-uplink communications are performed between V-UEs 160 without involving base station 102.

In one aspect, the sidelines 162, 166, 168 may operate over a wireless communication medium of interest that may be shared with other wireless communications between other vehicles and/or infrastructure access points and other RATs. A "medium" may be comprised of one or more time, frequency, and/or spatial communication resources (e.g., including one or more channels spanning one or more carriers) associated with wireless communication between one or more transmitter/receiver pairs.

In an aspect, the side links 162, 166, 168 may be cV2X links. The first generation of cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the united states and europe, cV2X is expected to operate in the licensed ITS band in sub-6 GHz. Other frequency bands may be allocated in other countries. Thus, as a particular example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band of sub-6 GHz. However, the present disclosure is not limited to this band or cellular technology.

In an aspect, the side links 162, 166, 168 may be Dedicated Short Range Communication (DSRC) links. DSRC is a one-way or two-way short-to-medium range wireless communication protocol that uses the Wireless Access (WAVE) protocol for vehicular environments (also known as IEEE 802.11P) for V2V, V I and V2P communications. IEEE 802.11p is an approved revision to the IEEE 802.11 standard and operates in the U.S. licensed ITS band 5.9GHz (5.85-5.925 GHz). In Europe, IEEE 802.11p operates in the ITS G5A band (5.875-5.905 MHz). Other frequency bands may be allocated in other countries. The V2V communication briefly described above occurs over a secure channel, which in the united states is typically a 10MHz channel dedicated for security purposes. The remainder of the DSRC band (75 MHz total bandwidth) is intended for other services of interest to the driver, such as road regulation, tolling, parking automation, etc. Thus, as a particular example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS frequency band of 5.9 GHz.

Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared between the various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the united states), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed bands, such as the unlicensed national information infrastructure (U-NII) band used by Wireless Local Area Network (WLAN) technology, most notably IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi". Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

The communication between V-UEs 160 is referred to as V2V communication, the communication between V-UEs 160 and one or more roadside access points 164 is referred to as V2I communication, and the communication between V-UEs 160 and one or more UEs 104 (where the UEs 104 are P-UEs) is referred to as V2P communication. The V2V communication between V-UEs 160 may include information regarding, for example, the location, speed, acceleration, heading, and other vehicle data of V-UEs 160. The V2I information received at V-UE 160 from one or more roadside access points 164 may include, for example, road rules, parking automation information, and the like. The V2P communication between V-UE 160 and UE 104 may include information regarding, for example, the location, speed, acceleration, and heading of V-UE 160, as well as the location, speed, and heading of UE 104 (e.g., the location of UE 104 on a bicycle carried by the user).

Note that although fig. 1 shows only two of the UEs as V-UEs (V-UE 160), any of the UEs shown (e.g., UEs 104, 152, 182, 190) may be V-UEs. In addition, although only V-UE 160 and a single UE 104 have been shown as being connected through a side-link, any of the UEs shown in fig. 1, whether V-UE, P-UE, etc., may be capable of side-link communication. Furthermore, although only UE 182 is described as being capable of beamforming, any of the UEs shown (including V-UE 160) are capable of beamforming. Where V-UEs 160 are capable of beamforming, they may be beamformed toward each other (i.e., toward other V-UEs 160), toward roadside access point 164, toward other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on side links 162, 166, and 168.

The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to the one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelink"). In the example of fig. 1, the UE 190 has a D2D P P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) and a D2D P P link 194 with the WLAN STA 152 connected to the WLAN AP 150 (through which the UE 190 may indirectly obtain WLAN-based internet connectivity). In an example, the D2D P2P links 192 and 194 may be formed from, for example, LTE Direct (LTE-D), wiFi Direct (WiFi-D), Etc., and any well known D2D RAT support. As another example, DThe 2d p2p links 192 and 194 may be sidelines as described above with reference to sidelines 162, 166 and 168.

Fig. 2A illustrates an example wireless network structure 200. For example, the 5gc 210 (also referred to as a Next Generation Core (NGC)) may be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access data network, IP routing, etc.), which operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5gc 210 and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the NG-eNB 224 can also connect to the 5GC 210 via the NG-C215 to the control plane function 214 and the NG-U213 to the user plane function 212. Further, the ng-eNB 224 may communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, a next generation RAN (NG-RAN) 220 may have one or more gnbs 222, while other configurations include one or more of NG-enbs 224 and gnbs 222. Either (or both) of the gNB 222 or the ng-eNB 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

Another optional aspect may include a location server 230 that may communicate with the 5gc 210 to provide positioning assistance for the UE(s) 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 scattered over multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, and the UE 204 may connect to the location server 230 via a core network, the 5gc 210, and/or via the internet (not shown). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an Original Equipment Manufacturer (OEM) server or a service server).

Fig. 2B illustrates another example wireless network structure 250. The 5gc 260 (which may correspond to the 5gc 210 in fig. 2A) may be functionally viewed as a control plane function provided by an access and mobility management function (AMF) 264 and a user plane function provided by a User Plane Function (UPF) 262, which cooperate to form a core network (i.e., the 5gc 260). The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Session Management (SM) messages for use between one or more UEs 204 (e.g., any of the UEs described herein) and Session Management Function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMs) messages between UEs 204 and Short Message Service Function (SMSF) (not shown), and security anchor function (SEAF). AMF 264 also interacts with an authentication server function (AUSF) (not shown) and UE 204 and receives an intermediate key created as a result of the UE 204 authentication process. In the case of authentication based on UMTS (universal mobile telecommunications system) subscriber identity module (USIM), AMF 264 retrieves the security material from the AUSF. The functions of AMF 264 also include Security Context Management (SCM). The SCM receives from the SEAF the key it uses to derive access network specific keys. The functions of AMF 264 also include location service management for policing 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, EPS bearer identifier assignment for interworking with Evolved Packet System (EPS), and UE 204 mobility event notification. In addition, AMF 264 also supports functions for non-3 GPP (third generation partnership project) access networks.

The functions of UPF 262 include acting as anchor point for intra/inter RAT mobility (when applicable), acting as external Protocol Data Unit (PDU) session point interconnected to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (mapping of Service Data Flows (SDFs) to QoS flows), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and issuing and forwarding one or more "end marks" to the source RAN node. UPF 262 may also support transmission of location service messages on the user plane between UE 204 and a location server, such as SLP 272.

The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering on the UPF 262 for routing traffic to appropriate destinations, control of policy enforcement and portions of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.

Another optional aspect may include an LMF 270 that may communicate with the 5gc 260 to provide location assistance for the UE 204. The LMFs 270 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules dispersed across multiple physical servers, etc.), or alternatively each LMF 270 may correspond to a single server. The LMF 270 may be configured to support one or more location services for UEs 204 capable of connecting to the LMF 270 via the core network 5gc 260, and/or via the internet (not shown). SLP 272 may support similar functions as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols intended to communicate signaling messages instead of voice or data), while SLP 272 may communicate with UE 204 and external clients (not shown in fig. 2B) on the user plane (e.g., using protocols like Transmission Control Protocol (TCP) and/or IP intended to carry voice and/or data).

The user plane interface 263 and the control plane interface 265 connect the 5gc 260 (specifically, UPF 262 and AMF 264, respectively) to one or more of the gnbs 222 and/or NG-enbs 224 in the NG-RAN 220. The interface between the gNB(s) 222 and/or the ng-eNB(s) 224 and the AMF 264 is referred to as an "N2" interface, and the interface between the gNB(s) 222 and/or the ng-eNB(s) 224 and the UPF 262 is referred to as an "N3" interface. The gNB(s) 222 and/or the NG-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 (referred to as an "Xn-C" interface). One or more of the gNB 222 and/or the ng-eNB 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

The functionality of the gNB 222 is divided between a gNB central unit (gNB-CU) 226 and one or more gNB distributed units (gNB-DUs) 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the "F1" interface. gNB-CU 226 is a logical node that includes base station functions for transmitting user data, mobility control, radio access network sharing, positioning, session management, and the like, in addition to those functions specifically assigned to gNB-DU 228. More specifically, gNB-CU 226 hosts the Radio Resource Control (RRC), service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 222. The gNB-DU 228 is a logical node hosting the Radio Link Control (RLC), medium Access Control (MAC), and Physical (PHY) layers of gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP and PDCP layers, and with the gNB-DU 228 via the RLC, MAC and PHY layers.

Fig. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or include any network functionality described herein, including a location server 230 and an LMF 270, or alternatively may be independent of NG-RAN 220 and/or 5gc 210/260 infrastructure depicted in fig. 2A and 2B, such as a private network) to support file transfer operations taught herein. It will be appreciated that these components may be implemented in different types of components (e.g., in an ASIC, in a system on a chip (SoC), etc.) in different implementations. The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Likewise, a given component may contain one or more of the components. For example, an apparatus may comprise multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate through different technologies.

The UE 302 and the base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, respectively, that provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., enbs, gnbs), etc., over a wireless communication medium of interest (e.g., a set of time/frequency resources in a particular spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). Depending on the specified RAT, the WWAN transceivers 310 and 350 may be configured differently for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, etc.), respectively, and conversely for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, etc.), respectively. Specifically, WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

In at least some cases, UE 302 and base station 304 also each include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provided for communicating over a wireless communication medium of interest via at least one designated RAT (e.g., wiFi, LTE-D,PC5, dedicated Short Range Communication (DSRC), wireless Access for Vehicular Environments (WAVE), near Field Communication (NFC), etc.) with other network nodes (such as other UEs, access points, base stations, etc.), for example, means for transmitting, means for usingMeans for receiving, means for measuring, means for tuning, means for suppressing transmission, etc.). Short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively, according to a specified RAT. Specifically, short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, +. >Transceiver, < - > on>And/or +.>A transceiver, NFC transceiver, or a vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) transceiver.

In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be coupled to one or more antennas 336 and 376, respectively, and may provide a means for receiving and/or measuring satellite positioning/communication signals 338 and 378, respectively. In the case where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning/communication signals 338 and 378 may 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), or the like. In the case of satellite signal receivers 330 and 370 being non-terrestrial network (NTN) receivers, satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may appropriately request information and operations from other systems and, at least in some cases, perform calculations to determine the position of UE 302 and base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 can employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 through one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

The transceiver may be configured to communicate over a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., including the transmitter circuit and the receiver circuit in a single device), may include separate transmitter circuits and separate receiver circuits in some implementations, or may be otherwise included in other implementations. The transmitter circuitry and receiver circuitry of the wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that allows the respective devices (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, that allows respective devices (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366) such that the respective components can only receive or transmit at a given time and cannot receive or transmit simultaneously. The wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a Network Listening Module (NLM) or the like for performing various measurements.

As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally described as "transceivers," at least one transceiver, "or" one or more transceivers. In this way, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication being performed. For example, backhaul communication between network devices or servers will typically be associated with 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 be associated with signaling via a wireless transceiver.

The UE 302, base station 304, and network entity 306 also include other components that may be used with the operations disclosed herein. The UE 302, base station 304, and network entity 306 comprise one or more processors 332, 384, and 394, respectively, for providing functionality related to, e.g., wireless communication, and for providing other processing functionality. Processors 332, 384, and 394 may thus provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, and the like. In an aspect, the processors 332, 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 of the above.

The UE 302, base station 304, and network entity 306 comprise memory circuitry (e.g., each comprising a memory device) implementing memories 340, 386, and 396, respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Memories 340, 386, and 396 may thus provide means for storing, means for retrieving, means for maintaining, and the like. In some cases, the UE 302, the base station 304, and the network entity 306 may include location assistance modules 342, 388, and 398, respectively. The location assistance modules 342, 388, and 398 may be part of the processing systems 332, 384, and 394, respectively, or hardware circuits coupled to the processors 332, 384, and 394, respectively, that when executed, cause the UE 302, base station 304, and network entity 306 to perform the functions described herein. In other aspects, the location assistance modules 342, 388, and 398 may be located external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the location assistance modules 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. Fig. 3A illustrates a possible positioning of a location assistance module 342, which location assistance module 342 may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a stand-alone component. Fig. 3B illustrates a possible positioning of the location assistance module 388, which location assistance module 388 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 stand-alone component. Fig. 3C illustrates a possible positioning of a location assistance module 398, which location assistance module 398 may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

The UE 302 may include one or more sensors 344 coupled to the processing system 332 to provide means for sensing or detecting movement and/or position information independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and/or the satellite receiver 330. By way of example, sensor(s) 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., an barometric altimeter), and/or other types of movement detection sensors. Further, sensor(s) 344 may include a plurality of different types of devices and their outputs combined to provide motion information. For example, sensor(s) 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in a two-dimensional (2D) and/or three-dimensional (3D) coordinate system.

Further, the UE 302 includes a user interface 346 that provides means for providing an indication (e.g., an audible and/or visual indication) to a user and/or receiving user input (e.g., when a user activates a detection device (such as a keyboard, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

Referring in more detail to the one or more processors 384, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement the functions of an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions associated with broadcast of system information (e.g., master Information Block (MIB), system Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection setup, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) and handover support functions; RLC layer functions associated with transmission of upper layer PDUs, error correction by automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

The transmitter 354 and the receiver 352 implement layer 1 (L1) functions associated with various signal processing functions. Layer 1, which includes a Physical (PHY) layer, may include error detection on a transport channel, forward Error Correction (FEC) encoding/decoding of a transport channel, interleaving, rate matching, mapping onto a physical channel, modulation/demodulation of a physical channel, and MIMO antenna processing. The 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 encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to Orthogonal Frequency Division Multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying the time domain OFDM symbol stream. The OFDM symbol streams are spatially precoded to produce multiple spatial streams. Channel estimates from the channel estimator may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. Transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

At the UE 302, the receiver 312 receives signals through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functions associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams to the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which processing system 332 implements layer 3 (L3) and layer 2 (L2) functions.

In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection.

Similar to the functionality described in connection with the downlink transmission of base station 304, one or more processors 332 provide RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression/decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functions associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to Transport Blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), priority handling and logical channel priority.

The transmitter 314 may use channel estimates derived by the channel estimator from reference signals or feedback transmitted by the base station 304 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different(s) 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

Uplink transmissions are processed at base station 304 in a manner similar to that described in connection with the receiver functionality at UE 302. The receiver 352 receives signals via its corresponding antenna(s) 356. Receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the one or more processors 384 may be provided to a core network. The one or more processors 384 are also responsible for error detection.

For convenience, UE 302, base station 304, and/or network entity 306 are illustrated in fig. 3A, 3B, and 3C as including various components that may be configured according to various examples described herein. It will be appreciated, however, that the illustrated components may have different functions in different designs. In particular, the various components in fig. 3A-3C are optional in alternative configurations, and various aspects include configurations that may be different due to design choices, cost, use of equipment, or other considerations. For example, in the case of fig. 3A, particular implementations of UE 302 may omit WWAN transceiver(s) 310 (e.g., a wearable device or tablet or PC or notebook may have Wi-Fi and/or bluetooth capabilities without cellular capabilities), or may omit short-range wireless transceiver(s) 320 (e.g., cellular only, etc.), or may omit satellite receiver 330, or may omit sensor(s) 344, and so forth. In another example, in the case of fig. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., wi-Fi "hot spot" access points without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, and so on. For brevity, descriptions of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

The various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to each other via data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or may be part of the communication interfaces of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are implemented in the same device (e.g., the gNB and location server functionality are incorporated into the same base station 304), the data buses 334, 382, and 392 may provide communications therebetween.

The components of fig. 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of fig. 3A, 3B, and 3C may be implemented in one or more circuits, such as one or more processors and/or one or more ASICs (which may include one or more processors). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code that the circuit uses to provide the functionality. For example, some or all of the functions represented by blocks 310 through 346 may be implemented by a processor and memory component(s) of UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functions represented by blocks 350 through 388 may be implemented by the processor and memory component(s) of base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functions represented by blocks 390 through 398 may be implemented by a processor and memory component(s) of network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed by a UE, by a base station, by a network entity, etc. However, it will be understood that these operations, acts and/or functions may in fact be performed by specific components or combinations of components of the UE 302, the base station 304, the network entity 306, etc., such as the processors 332, 384, 394, the transceivers 310, 320, 350 and 360, the memories 340, 386 and 396, the location assistance modules 342, 388 and 398, etc.

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

NR supports a variety of cellular network-based positioning techniques including downlink-based positioning methods, uplink-based positioning methods, and downlink-and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink departure angle (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (TOAs) of received reference signals (e.g., positioning Reference Signals (PRSs)) from a base station, which is referred to as a Reference Signal Time Difference (RSTD) or time difference of arrival (TDOA) measurement, and reports it to the positioning entity. More specifically, the UE receives Identifiers (IDs) of a reference base station (e.g., a serving base station) and a plurality of non-reference base stations in the assistance data. The UE then measures RSTD between the reference base station and each non-reference base station. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity can estimate the location of the UE.

For DL-AoD positioning, the positioning entity uses beam reports from the UE of received signal strength measurements for multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity may then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding Reference Signals (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known position(s) of the base station(s), the positioning entity may then estimate the position of the UE.

Downlink and uplink based positioning methods include enhanced cell ID (E-CID) positioning and multi-Round Trip Time (RTT) positioning (also referred to as "multi-cell RTT"). In the RTT process, an initiator (base station or UE) transmits an RTT measurement signal (e.g., PRS or SRS) to a responder (UE or base station), which transmits an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes a difference between the ToA of the RTT measurement signal and a transmission time of the RTT response signal, which is referred to as a reception transmission (Rx-Tx) time difference. The initiator calculates the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response signal, referred to as the transmission-to-reception (Tx-Rx) time difference. The propagation time (also referred to as "time of flight") between the initiator and the responder may be calculated from the Tx-Rx and Rx-Tx time differences. Based on the propagation time and the known speed of light, the distance between the initiator and the responder can be determined. For multi-RTT positioning, the UE performs RTT procedures with multiple base stations to enable its location to be determined based on the known locations of the base stations (e.g., using multi-point positioning). RTT and multi-RTT methods may be combined with other positioning techniques (e.g., UL-AoA and DL-AoD) to improve position accuracy.

The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In the E-CID, the UE reports a serving cell ID, a Timing Advance (TA), and identifiers of detected neighbor base stations, estimated timing, and signal strength. The location of the UE is then estimated based on the information and the known location of the base station(s).

To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of the base station (or cell/TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., number of consecutive positioning subframes, periodicity of positioning subframes, muting sequence, hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and/or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect the neighbor network node itself without using assistance data.

In the case of an OTDOA or DL-TDOA positioning procedure, the assistance data may also include an expected RSTD value and associated uncertainty or search window around the expected RSTD. In some cases, the expected range of values for RSTD may be +/-500 microseconds (μs). In some cases, the range of values of uncertainty of the expected RSTD may be +/-32 μs when any resources for positioning measurements are in FR 1. In other cases, the range of values of uncertainty of the expected RSTD may be +/-8 μs when all resources for the positioning measurement(s) are in FR 2.

The position estimate may be referred to by other names, such as position estimate, position fix, fixed, etc. The location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be urban and include a street address, postal address, or some other verbal description of the location. The position estimate may also be defined relative to some other known position or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The location estimate may include an expected error or uncertainty (e.g., by including a region or volume that is expected to include the location with some specified or default confidence level).

As described above, the UE may be provided with location assistance data including an identifier of a base station (or cell/TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., number of consecutive positioning subframes, periodicity of positioning subframes, muting sequences, hopping sequences, reference signal identifiers, reference signal bandwidth, etc.), and/or other parameters applicable to a particular positioning method. Such location assistance data is typically provided under the assumption that the target UE is a ground or grounded UE (i.e., cannot fly).

A new class of UEs is known as aerial UEs or Unmanned Aerial Vehicles (UAVs). The airborne UAV may be engaged in an in-flight mode or flight state from time to time. In some designs, some components of the network (e.g., serving gNB, etc.) may identify the UE as an over-the-air UE or UAV (e.g., to improve communications, for beamforming, etc.). However, the LMF does not know the over-the-air state of the UE.

Fig. 4 illustrates a channel model 400 for a UAV in accordance with an aspect of the disclosure. In fig. 4, gNB 402 communicates with a terrestrial or ground UE 404 via beam 406, and gNB 402 communicates with an in-flight aerial UE (or UAV) 408 via beam 410. As shown in fig. 4, the respective antennas of the gNB 402, the UE 404, and the UE 408 may be at different heights. For example, the antenna height (h _BS ) May be about 25m, the antenna height (h _TUE ) May be about 1.5m, and the antenna height (H _AUE ) And may be anywhere between about 1.5 and 300 m. Furthermore, beam 410 is more likely to be an LOS than beam 406 because there is no physical obstruction at the higher elevation. For example, the LOS probability may increase with height. In general, if H _AUE >22m, the LOS probability may be close to 100%.

Aspects of the present disclosure relate to transmitting information based on an aerial UE that the UE is configured to be capable of flying (e.g., whether the UE is an aerial UE or a UAV, an in-flight or landing state of the UAV, flight path information indicating a future path of the UAV, etc.) to a location server (e.g., LMF). In some designs, a location server (e.g., LMF) may use this information to select assistance data (e.g., location assistance data) that is typically tailored to the UAV and/or tailored to a particular UAV (e.g., based on flight path, etc.). These aspects may provide various technical advantages, such as improved positioning of the UAV.

Fig. 5 illustrates an exemplary process 500 of wireless communication in accordance with aspects of the present disclosure. In an aspect, process 500 may be performed by a UE (such as UE 302). In particular, the UE performing process 500 is an airborne UE or UAV capable of flying.

Referring to fig. 5, at 510, UE 302 (e.g., transmitter 314 or 324, etc.) transmits a message including information based on an over-the-air UE that the UE is configured to be capable of flying to a location server (e.g., an LMF integrated in BS 304 or an LMF in network entity 306, etc.). As will be described in more detail below, this information may indicate whether the UE is an aerial UE or a UAV, an in-flight or landing state of the UAV, flight path information indicating a future path of the UAV, and so on. In some designs, the means for performing 510 transmission may include the transmitter 314 or 324 of the UE 302, as described above with respect to fig. 3A.

Referring to fig. 5, at 520, the UE 302 (e.g., receiver 312 or 322, etc.) receives assistance data (e.g., location assistance data) from a location server (e.g., LMF) based in part on information in the message. In other words, information based on the over-the-air UE that the UE is configured to be capable of flying may be used to customize or optimize assistance data (e.g., location assistance data) received at the UE 302 at 520. In some designs, the means for performing the receiving of 520 may include the receiver 312 or 322 of the UE 302, as described above with respect to fig. 3A.

Fig. 6 illustrates an exemplary process 600 of wireless communication in accordance with aspects of the present disclosure. In an aspect, the process 600 may be performed by a location server (e.g., LMF) such as LMF 270 (e.g., which may be integrated in BS 304, or may be integrated in network entity 306 such as a core network component or an external server, etc.).

Referring to fig. 6, at 610, a location server (e.g., LMF) (e.g., receiver 352 or 362, network transceiver(s) 380 or 390, etc.) receives a message from a UE that includes information based on an over-the-air UE that the UE is configured to be capable of flying. As will be described in more detail below, this information may indicate whether the UE is an aerial UE or a UAV, an in-flight or landing state of the UAV, flight path information indicating a future path of the UAV, and so on. In some designs, the means for performing the receiving of 610 may include the receiver 352 of 362 or the network transceiver(s) 380 as described above with respect to fig. 3B (e.g., where a location server (e.g., LMF) is integrated in BS 304) or may include the network transceiver(s) 390 as described above with respect to fig. 3C (e.g., where a location server (e.g., LMF) is integrated in network entity 306).

Referring to fig. 6, at 620, a location server (e.g., LMF) (e.g., processor(s) 384 or 394, location assistance module 388 or 398, etc.) selects assistance data (e.g., location assistance data) based in part on information in the message. As will be described in more detail below, in some designs, the selection at 620 may select a different configuration of beams, base stations, etc. that are more suitable for an on-air UE than a non-on-air UE or a grounded on-air UE. In some designs, the means for performing 620 selection may include the processor 384 or the location assistance module 388 as described above with respect to fig. 3B (e.g., where a location server (e.g., LMF) is integrated in BS 304), or may include the processor(s) 394 or the location assistance module 398 (e.g., where a location server (e.g., LMF) is integrated in network entity 306) as described above with respect to fig. 3C.

Referring to fig. 6, at 630, a location server (e.g., LMF) (e.g., transmitter 354 or 364, network transceiver(s) 380 or 390, etc.) transmits assistance data (e.g., location assistance data) to the UE. In some designs, the means for performing the sending of 630 may include the transmitter 354 or 364 or the network transceiver(s) 380 as described above with respect to fig. 3B (e.g., where a location server (e.g., LMF) is integrated in BS 304) or may include the network transceiver(s) 390 as described above with respect to fig. 3C (e.g., where a location server (e.g., LMF) is integrated in network entity 306).

Fig. 7 illustrates an example embodiment 700 of the processes 500-600 of fig. 5-6 in accordance with an aspect of the present disclosure. In fig. 7, the location server includes an LMF 270. At 702, the LMF 270 optionally sends a request for capability to the UE 302 (e.g., because UE information may be sent with or without a request from a location server). At 704, the UE 302 provides information regarding its capabilities to a location server (e.g., sends a capability indication in response to the request from 702). In particular, the capability indication includes over-the-air UE information and corresponds to a message from 510 of fig. 5 or 610 of fig. 6. At 706 (e.g., as at 520 of fig. 5 or 630 of fig. 6), LMF 270 sends assistance data (e.g., location assistance data) to UE 302 based on the capability indication from 704. Thus, in fig. 7, over-the-air UE information is sent in response to a request initiated from the network.

Referring to fig. 7, in some designs, the request at 702 may request whether the UE is a UAV, or may request flight path information, or the like. In some designs, the request at 702 may be a modified version of the capability request message. For example, the RequestCapabilities-r9-IEs message may be modified to include a new IE, such as, for example:

nr-requestFlightPath-r18 NR-requestFlightPath-r18 OPTIONAL

In other designs, the request at 702 may be included in a new message specific to the request for flight path information. In other designs, the request at 702 may be part of a request for location information, such as a RequestLocationInformation message.

Fig. 8 illustrates an example embodiment 800 of the processes 500-600 of fig. 5-6 in accordance with another aspect of the present disclosure. In fig. 8, the location server includes an LMF 270. At 802, the UE 302 sends a request for assistance data. Specifically, the request for assistance data includes over-the-air UE information and corresponds to a message from 510 of fig. 5 or 610 of fig. 6. At 804 (e.g., as at 520 of fig. 5 or 630 of fig. 6), the LMF 270 sends assistance data (e.g., location assistance data) to the UE 302 in response to the request from 802. Thus, in fig. 7, over-the-air UE information is sent via a request initiated from UE 302.

Referring to fig. 7-8, in some designs, the message providing UAV capability at 704 of fig. 7 or 802 of fig. 8 may correspond to a providencapabilities-r 9-IEs message. For example, the providencapabilities-r 9-IEs message may be modified to include new IEs, such as, for example:

nr-provideFlightPath-r18 NR-provideFlightPath-r18 OPTIONAL,

nr-provideUAVState-r18 NR-provideUAVState-r18 OPTIONAL,

in other designs, the information at 510 of fig. 5 or 610 of fig. 6 may be signaled via signaling of location information. For example, the UE may participate in a location estimation procedure (e.g., measure SL and/or DL PRS, transmit SRS-P for measurements of one or more other wireless nodes, etc.) and report (e.g., via LTE Positioning Protocol (LPP), RRC, etc.) location information associated with the location estimation procedure. In this case, the report with location information may also include 510 or 610 information (e.g., over-the-air UE or UAV related information may be piggybacked onto the location measurement report).

Referring to fig. 5-6, in some designs, the information in the message at 510 of fig. 5 or 610 of fig. 6 may indicate that the UE is configured as an on-air UE (e.g., a single bit indication indicating an on-air UE or an off-air UE). In some designs, the information in the message at 510 of fig. 5 or 610 of fig. 6 may indicate whether the UE is in a flight state or a ground state (e.g., one bit for indicating an on-air UE and a non-on-air UE, and in the case of an on-air UE, another bit for indicating a ground state and a flight state). In some designs, where the in-flight UE is in flight, supplemental information related to the in-flight UE's flight status, such as the UE's altitude or altitude, may be indicated.

Referring to fig. 5-6, in some designs, the information in the message at 510 of fig. 5 or 610 of fig. 6 may include flight path information. In some designs, the flight path information may include a sequence of waypoints and associated timestamps, similar to 3GPP Rel.15LTE RRC, for example:

in some designs, the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, polyhedrons, or ellipses. Thus, waypoints may be "volumes" rather than areas or discrete points or coordinates. One example of an ellipsoidal waypoint configuration is as follows:

Referring to fig. 5-6, in some designs, the flight path information includes the trajectory and speed of the UE. This may be indicated in various ways, such as two coordinates (e.g., current and future) and associated time stamps, or a direction/azimuth indication and a speed indication, etc.

Referring to fig. 5-6, in some designs, the selection of a node to participate in a positioning session may depend on the state of the UE. For example, for terrestrial UEs, it is often disadvantageous to signal nodes that are very far from the serving gNB. However, UAVs (particularly high-flying UAVs) may be connected to very remote gnbs, thus requiring corresponding adjustments to the assistance data.

Fig. 9 illustrates a communication system 900 in accordance with an aspect of the disclosure. In fig. 9, various base stations are deployed in a communication system 900. The ground-based aerial UAV or non-aerial UE 905 is served by a serving gNB 910. In this case, assistance data (e.g., location assistance data) may be sent to the UEs 905 having clustered base station groups 915. In other words, clustered base station packet 915 represents nodes referenced in assistance data (e.g., location assistance data). In the case of a grounded aerial UAV or non-aerial UE, it should be appreciated that clustered base station packet 915 typically includes a gNB that is closest to the UE 905, rather than a "remote" gNB, with an intervening (inter-planning) gNB omitted from clustered base station packet 915.

Fig. 10 illustrates a communication system 1000 in accordance with an aspect of the disclosure. In fig. 10, various base stations are deployed in a communication system 900. In-flight on-air UE 1005 is served by serving gNB 1010. In this case, assistance data (e.g., location assistance data) may be transmitted to the UE 1005 using the distributed base station packet 1015. In other words, distributed base station packet 1015 represents a node referenced in assistance data (e.g., location assistance data). In the case of an over-the-air UE, it should be appreciated that distributed base station packet 1015 may generally include a remote gNB due to the higher availability (and thus higher communication range) of the LOS link for the connection between UE 1005 and the gNB of communication system 1000. Accordingly, the assistance data (e.g., location assistance data) at 520 of fig. 5 or 620-630 of fig. 6 may include information associated with one or more base stations that are far from the UE, with one or more other intermediate base stations that are closer to the UE omitted from the assistance data (e.g., location assistance data), as shown in fig. 10.

Referring to fig. 5-6, in some designs, assistance data (e.g., location assistance data) includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight UE (e.g., as shown in fig. 4).

In the above detailed description, it can be seen that the different features are grouped together in an example. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly recited in each clause. Rather, aspects of the disclosure can include less than all of the features of the various example clauses disclosed. Accordingly, the following clauses are herein considered to be incorporated into the specification, each of which may itself be considered a separate example. Although each subordinate clause may refer to a particular combination with one of the other clauses in the clauses, the aspect(s) of the subordinate clause are not limited to this particular combination. It should be appreciated that other example clauses may also include combinations of subordinate clause aspect(s) with the subject matter of any other subordinate clause or independent clause, or combinations of any feature with other subordinate and independent clauses. The various aspects disclosed herein expressly include such combinations unless expressly stated or it can be readily inferred that no particular combination (e.g., contradictory aspects such as defining elements as both insulators and conductors) is intended. Furthermore, it is also intended that aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

An example of an embodiment is described in the following numbered clauses:

clause 1. A method of operating a User Equipment (UE), comprising: transmitting a message to a location server including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server based in part on the information in the message.

Clause 2. The method of clause 1, further comprising: a capability request is received from the location server, wherein the message is sent in response to the capability request.

Clause 3 the method of any of clauses 1 to 2, wherein the message corresponds to a request for the assistance data.

Clause 4. The method of any of clauses 1 to 3, wherein the message corresponds to a capability indication.

Clause 5 the method of any of clauses 1 to 4, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 6. The method of any of clauses 1 to 5, wherein the information indicates whether the UE is involved in a flight state or a ground state.

Clause 7. The method of clause 6, wherein the information indicates that the UE is engaged in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 8 the method of any of clauses 1 to 7, wherein the information comprises flight path information.

Clause 9. The method of clause 8, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

Clause 10. The method of clause 9, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 11. The method of any of clauses 8 to 10, wherein the flight path information comprises a trajectory and a speed of the UE.

The method of any of clauses 1-11, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

Clause 13 the method of any of clauses 1 to 12, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

Clause 14 the method of any of clauses 1 to 13, wherein the network entity comprises a Location Management Function (LMF).

Clause 15. A method of operating a location server, comprising: receiving a message from a User Equipment (UE) comprising information based on an over-the-air UE the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting the assistance data to the UE.

Clause 16 the method of clause 15, further comprising: a capability request is sent to the UE, wherein the message is received in response to the capability request.

Clause 17 the method of any of clauses 15 to 16, wherein the message corresponds to a request for the assistance data.

Clause 18 the method of any of clauses 15 to 17, wherein the message corresponds to a capability indication.

Clause 19 the method of any of clauses 15 to 18, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 20 the method of any of clauses 15 to 19, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

Clause 21 the method of clause 20, wherein the information indicates that the UE is engaged in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

The method of any of clauses 15 to 21, wherein the information comprises flight path information.

Clause 23 the method of clause 22, wherein the flight path information comprises a sequence of waypoints and associated time stamps.

Clause 24 the method of clause 23, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 25 the method of any of clauses 22 to 24, wherein the flight path information comprises a trajectory and a speed of the UE.

The method of any of clauses 15-25, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

The method of any of clauses 15 to 26, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

The method of any of clauses 15-27, wherein the network entity comprises a Location Management Function (LMF).

Clause 29, a User Equipment (UE) comprising: a memory; at least one transceiver; and at least one transceiver communicatively coupled to the processor and the at least one memory, the at least one processor configured to: transmitting, via at least one transceiver, a message to a location server, the message including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server via the at least one transceiver based in part on the information in the message.

The UE of clause 30, wherein the at least one processor is further configured to: a capability request is received from a location server via at least one transceiver, wherein the message is sent in response to the capability request.

Clause 31 the UE of any of clauses 29 to 30, wherein the message corresponds to a request for the assistance data.

Clause 32 the UE of any of clauses 29 to 31, wherein the message corresponds to a capability indication.

Clause 33 the UE of any of clauses 29 to 32, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 34 the UE of any of clauses 29 to 33, wherein the information indicates whether the UE is involved in a flight state or a ground state.

Clause 35 the UE of clause 34, wherein the information indicates that the UE is involved in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 36 the UE of any of clauses 29 to 35, wherein the information comprises flight path information.

Clause 37 the UE of clause 36, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

Clause 38 the UE of clause 37, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 39 the UE of any of clauses 36 to 38, wherein the flight path information comprises a trajectory and a speed of the UE.

Clause 40 the UE of any of clauses 29 to 39, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

Clause 41 the UE of any of clauses 29 to 40, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

Clause 42 the UE of any of clauses 29 to 41, wherein the network entity comprises a Location Management Function (LMF).

Clause 43. A location server comprising: a memory; at least one transceiver; and at least one transceiver communicatively coupled to the processor and the at least one memory, the at least one processor configured to: receiving, via at least one transceiver, a message from a User Equipment (UE), the message including information based on an over-the-air UE the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting assistance data to the UE via the at least one transceiver.

Clause 44 the location server of clause 43, wherein the at least one processor is further configured to: a capability request is sent to the UE via the at least one transceiver, wherein the message is received in response to the capability request.

Clause 45 the location server of any of clauses 43 to 44, wherein the message corresponds to a request for the assistance data.

Clause 46. The location server of any of clauses 43 to 45, wherein the message corresponds to a capability indication.

Clause 47 the location server of any of clauses 43 to 46, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 48. The location server of any of clauses 43 to 47, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

Clause 49 the location server of clause 48, wherein the information indicates that the UE is engaged in the flight status, and wherein the information also indicates the altitude or elevation of the UE.

Clause 50 the location server of any of clauses 43 to 49, wherein the information comprises flight path information.

Clause 51 the location server of clause 50, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

Clause 52. The location server of clause 51, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 53 the location server of any of clauses 50 to 52, wherein the flight path information comprises the trajectory and speed of the UE.

Clause 54 the location server of any of clauses 43 to 53, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

Clause 55. The location server of any of clauses 43 to 54, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

Clause 56 the location server of any of clauses 43 to 55, wherein the network entity comprises a Location Management Function (LMF).

Clause 57, a User Equipment (UE), comprising: means for sending a message to a location server, the message including information based on an over-the-air UE the UE is configured to be capable of flying; and means for receiving assistance data from the location server based in part on the information in the message.

Clause 58 the UE of clause 57, further comprising: means for receiving a capability request from the location server, wherein the message is sent in response to the capability request.

Clause 59 the UE of any of clauses 57 to 58, wherein the message corresponds to a request for the assistance data.

Clause 60. The UE of any of clauses 57 to 59, wherein the message corresponds to a capability indication.

Clause 61 the UE of any of clauses 57-60, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 62 the UE of any of clauses 57 to 61, wherein the information indicates whether the UE is involved in a flight state or a ground state.

Clause 63. The UE of clause 62, wherein the information indicates that the UE is involved in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 64 the UE of any of clauses 57 to 63, wherein the information comprises flight path information.

Clause 65. The UE of clause 64, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

Clause 66. The UE of clause 65, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 67 the UE of any of clauses 64 to 66, wherein the flight path information comprises a trajectory and a speed of the UE.

Clause 68 the UE of any of clauses 57 to 67, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with the in-flight air UE.

The UE of any of clauses 57-68, wherein the assistance data comprises information associated with one or more base stations that are remote from the UE, wherein one or more other intermediate base stations that are closer to the UE are omitted from the assistance data.

Clause 70 the UE of any of clauses 57 to 69, wherein the network entity comprises a Location Management Function (LMF).

Clause 71. A location server, comprising: means for receiving a message from a User Equipment (UE), the message including information based on an over-the-air UE the UE is configured to be capable of flying; means for selecting assistance data based in part on the information in the message; and means for transmitting the assistance data to the UE.

Clause 72 the location server of clause 71, further comprising: means for sending a capability request to the UE, wherein the message is received in response to the capability request.

Clause 73 the location server of any of clauses 71 to 72, wherein the message corresponds to a request for the assistance data.

Clause 74. The location server of any of clauses 71 to 73, wherein the message corresponds to a capability indication.

Clause 75 the location server of any of clauses 71 to 74, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 76 the location server of any of clauses 71 to 75, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

Clause 77 the location server of clause 76, wherein the information indicates that the UE is engaged in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 78 the location server of any of clauses 71 to 77, wherein the information comprises flight path information.

Clause 79 the location server of clause 78, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

Clause 80. The location server of clause 79, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons or ellipses.

Clause 81 the location server of any of clauses 78 to 80, wherein the flight path information includes the trajectory and speed of the UE.

Clause 82 the location server of any of clauses 71 to 81, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

Clause 83. The location server of any of clauses 71 to 82, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

Clause 84 the location server of any of clauses 71 to 83, wherein the network entity comprises a Location Management Function (LMF).

Clause 85, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to: transmitting a message to a location server including information based on an over-the-air UE that the UE is configured to be capable of flying; and receiving assistance data from the location server based in part on the information in the message.

Clause 86. The non-transitory computer-readable medium of clause 85, wherein the one or more instructions further cause the UE to: a capability request is received from the location server, wherein the message is sent in response to the capability request.

Clause 87 the non-transitory computer-readable medium of any of clauses 85 to 86, wherein the message corresponds to a request for the auxiliary data.

Clause 88 the non-transitory computer readable medium of any of clauses 85 to 87, wherein the message corresponds to a capability indication.

Clause 89 the non-transitory computer readable medium of any of clauses 85 to 88, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 90. The non-transitory computer readable medium of any of clauses 85 to 89, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

Clause 91. The non-transitory computer readable medium of clause 90, wherein the information indicates that the UE is engaged in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 92 the non-transitory computer readable medium of any of clauses 85 to 91, wherein the information comprises flight path information.

Clause 93 the non-transitory computer-readable medium of clause 92, wherein the flight path information includes a sequence of waypoints and associated timestamps.

Clause 94. The non-transitory computer-readable medium of clause 93, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

Clause 95 the non-transitory computer readable medium of any of clauses 92 to 94, wherein the flight path information comprises the trajectory and speed of the UE.

The non-transitory computer-readable medium of any one of clauses 85 to 95, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

Clause 97 the non-transitory computer-readable medium of any of clauses 85 to 96, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

The non-transitory computer-readable medium of any one of clauses 85 to 97, wherein the network entity comprises a Location Management Function (LMF).

Clause 99. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: receiving a message from a User Equipment (UE) that includes information based on an over-the-air UE that the UE is configured to be capable of flying; selecting assistance data based in part on the information in the message; and transmitting the assistance data to the UE.

Clause 100. The non-transitory computer-readable medium of clause 99, wherein the one or more instructions further cause the location server to: a capability request is sent to the UE, wherein the message is received in response to the capability request.

Clause 101 the non-transitory computer readable medium of any of clauses 99 to 100, wherein the message corresponds to a request for the assistance data.

Clause 102 the non-transitory computer readable medium of any of clauses 99 to 101, wherein the message corresponds to a capability indication.

Clause 103. The non-transitory computer readable medium of any of clauses 99 to 102, wherein the information indicates that the UE is configured as the over-the-air UE.

Clause 104. The non-transitory computer readable medium of any of clauses 99 to 103, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

Clause 105. The non-transitory computer readable medium of clause 104, wherein the information indicates that the UE is engaged in the flight status, and wherein the information further indicates an altitude or elevation of the UE.

Clause 106 the non-transitory computer readable medium of any of clauses 99 to 105, wherein the information comprises flight path information.

Clause 107. The non-transitory computer readable medium of clause 106, wherein the flight path information includes a waypoint sequence and an associated timestamp.

Clause 108. The non-transitory computer-readable medium of clause 107, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

Clause 109 the non-transitory computer readable medium of any of clauses 106 to 108, wherein the flight path information comprises a trajectory and a speed of the UE.

Clause 110 the non-transitory computer readable medium of any of clauses 99 to 109, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

Clause 111 the non-transitory computer readable medium of any of clauses 99 to 110, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

Clause 112 the non-transitory computer readable medium of any of clauses 99 to 111, wherein the network entity comprises a Location Management Function (LMF).

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Furthermore, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an ASIC, a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The methods, sequences, and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A 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 disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both storage media and communication media including any medium that can facilitate transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical, magnetic disk or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, discs (disks) and disks include Compact Disks (CDs), laser disks, optical disks, digital Versatile Disks (DVDs), floppy disks, and blu-ray disks where disks (disks) usually reproduce data magnetically, while disks (disks) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

While the foregoing disclosure illustrates illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claim (modification according to treaty 19)

1. A method of operating a User Equipment (UE), comprising:

transmitting a message to a location server, the message including information based on an over-the-air UE the UE is configured to be capable of flying; and

assistance data based in part on the information in the message is received from the location server.

2. The method of claim 1, further comprising:

a capability request is received from the location server,

wherein the message is sent in response to the capability request.

3. The method of claim 1, wherein the message corresponds to a request for the assistance data.

4. The method of claim 1, wherein the message corresponds to a capability indication.

5. The method of claim 1, wherein the information indicates that the UE is configured as the over-the-air UE.

6. The method of claim 1, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

7. The method according to claim 6, wherein the method comprises,

wherein the information indicates that the UE participates in the flight status, an

Wherein the information also indicates an altitude or elevation of the UE.

8. The method of claim 1, wherein the information comprises flight path information.

9. The method of claim 8, wherein the flight path information includes a sequence of waypoints and associated timestamps.

10. The method of claim 9, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

11. The method of claim 8, wherein the flight path information includes a trajectory and a speed of the UE.

12. The method of claim 1, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

13. The method of claim 1, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

14. The method of claim 1, wherein the location server comprises a Location Management Function (LMF).

15. A method of operating a location server, comprising:

receiving a message from a User Equipment (UE), the message including information based on an over-the-air UE the UE is configured to fly;

selecting assistance data based in part on the information in the message; and

and sending the auxiliary data to the UE.

16. The method of claim 15, further comprising:

a capability request is sent to the UE,

wherein the message is received in response to the capability request.

17. The method of claim 15, wherein the message corresponds to a request for the assistance data.

18. The method of claim 15, wherein the message corresponds to a capability indication.

19. The method of claim 15, wherein the information indicates that the UE is configured as the over-the-air UE.

20. The method of claim 15, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

21. The method according to claim 20,

Wherein the information also indicates an altitude or elevation of the UE.

22. The method of claim 15, wherein the information comprises flight path information.

23. The method of claim 22, wherein the flight path information includes a sequence of waypoints and associated timestamps.

24. The method of claim 23, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

25. The method of claim 22, wherein the flight path information includes a trajectory and a speed of the UE.

26. The method of claim 15, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

27. The method of claim 15, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

28. The method of claim 15, wherein the location server comprises a Location Management Function (LMF).

29. A User Equipment (UE), comprising:

a memory;

at least one transceiver; and

at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to:

transmitting, via the at least one transceiver, a message to a location server, the message including information based on an over-the-air UE the UE is configured to be capable of flying; and

assistance data based in part on the information in the message is received from the location server via the at least one transceiver.

30. The UE of claim 29, wherein the at least one processor is further configured to:

receiving a capability request from the location server via the at least one transceiver,

wherein the message is sent in response to the capability request.

31. The UE of claim 29,

wherein the message corresponds to a request for the assistance data, or

Wherein the message corresponds to a capability indication.

32. The UE of claim 29,

Wherein the information indicates that the UE is configured as the over-the-air UE, or

Wherein the information indicates whether the UE is involved in a flight state or a ground state, or

Wherein the information includes flight path information, or

A combination thereof.

33. The UE of claim 32,

wherein the flight path information includes a sequence of waypoints and associated time stamps, or

Wherein the flight path information includes the trajectory and speed of the UE, or

A combination thereof.

34. The UE of claim 29,

wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight, on-air UE, or

Wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data, or

A combination thereof.

35. A location server, comprising:

a memory;

at least one transceiver; and

Receiving a message from a User Equipment (UE) via the at least one transceiver, the message including information based on an over-the-air UE the UE is configured to fly;

selecting assistance data based in part on the information in the message; and

the assistance data is sent to the UE via the at least one transceiver.

36. The location server of claim 35, wherein the at least one processor is further configured to:

transmitting a capability request to the UE via the at least one transceiver,

wherein the message is received in response to the capability request.

37. The location server of claim 35,

wherein the message corresponds to a request for the assistance data, or

Wherein the message corresponds to a capability indication.

38. The location server of claim 35,

Wherein the information includes flight path information, or

A combination thereof.

39. The location server of claim 35,

A combination thereof.

40. The location server of claim 35, wherein the location server comprises a Location Management Function (LMF).

Claims

1. A method of operating a User Equipment (UE), comprising:

2. The method of claim 1, further comprising:

a capability request is received from the location server,

wherein the message is sent in response to the capability request.

7. The method according to claim 6, wherein the method comprises,

Wherein the information also indicates an altitude or elevation of the UE.

14. The method of claim 1, wherein the network entity comprises a Location Management Function (LMF).

15. A method of operating a location server, comprising:

selecting assistance data based in part on the information in the message; and

and sending the auxiliary data to the UE.

16. The method of claim 15, further comprising:

a capability request is sent to the UE,

wherein the message is received in response to the capability request.

21. The method according to claim 20,

Wherein the information also indicates an altitude or elevation of the UE.

28. The method of claim 15, wherein the network entity comprises a Location Management Function (LMF).

29. A User Equipment (UE), comprising:

a memory;

at least one transceiver; and

wherein the message is sent in response to the capability request.

31. The UE of claim 29, wherein the message corresponds to a request for the assistance data.

32. The UE of claim 29, wherein the message corresponds to a capability indication.

33. The UE of claim 29, wherein the information indicates that the UE is configured as the over-the-air UE.

34. The UE of claim 29, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

35. The UE of claim 34,

Wherein the information also indicates an altitude or elevation of the UE.

36. The UE of claim 29, wherein the information comprises flight path information.

37. The UE of claim 36, wherein the flight path information includes a sequence of waypoints and associated timestamps.

38. The UE of claim 37, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

39. The UE of claim 36, wherein the flight path information includes a trajectory and a speed of the UE.

40. The UE of claim 29, wherein the assistance data includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight UE.

41. The UE of claim 29, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

42. The UE of claim 29, wherein the network entity comprises a Location Management Function (LMF).

43. A location server, comprising:

a memory;

at least one transceiver; and

selecting assistance data based in part on the information in the message; and

the assistance data is sent to the UE via the at least one transceiver.

44. The location server of claim 43, wherein the at least one processor is further configured to:

transmitting a capability request to the UE via the at least one transceiver,

wherein the message is received in response to the capability request.

45. A location server as defined in claim 43, wherein the message corresponds to a request for the assistance data.

46. A location server as defined in claim 43, wherein the message corresponds to a capability indication.

47. The location server of claim 43, wherein the information indicates that the UE is configured as the over-the-air UE.

48. The location server of claim 43, wherein the information indicates whether the UE is participating in a flight state or a ground state.

49. The location server of claim 48,

Wherein the information also indicates an altitude or elevation of the UE.

50. The location server of claim 43 wherein the information comprises flight path information.

51. The location server of claim 50, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

52. The location server of claim 51, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

53. The location server of claim 50, wherein the flight path information comprises a trajectory and a speed of the UE.

54. The location server of claim 43, wherein the assistance data comprises information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with in-flight aerial UEs.

55. The location server of claim 43, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

56. A location server as defined in claim 43, wherein the network entity comprises a Location Management Function (LMF).

57. A User Equipment (UE), comprising:

means for sending a message to a location server, the message comprising information based on an over-the-air UE the UE is configured to be capable of flying; and

means for receiving assistance data from the location server based in part on the information in the message.

58. The UE of claim 57, further comprising:

means for receiving a capability request from the location server,

wherein the message is sent in response to the capability request.

59. The UE of claim 57, wherein the message corresponds to a request for the assistance data.

60. The UE of claim 57, wherein the message corresponds to a capability indication.

61. The UE of claim 57, wherein the information indicates that the UE is configured as the over-the-air UE.

62. The UE of claim 57, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

63. The UE of claim 62,

Wherein the information also indicates an altitude or elevation of the UE.

64. The UE of claim 57, wherein the information includes flight path information.

65. The UE of claim 64, wherein the flight path information includes a sequence of waypoints and associated timestamps.

66. The UE of claim 65, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

67. The UE of claim 64, wherein the flight path information includes a trajectory and a speed of the UE.

68. The UE of claim 57, wherein the assistance data includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight UE.

69. The UE of claim 57, wherein the assistance data includes information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

70. A UE as defined in claim 57, wherein the network entity comprises a Location Management Function (LMF).

71. A location server, comprising:

means for receiving a message from a User Equipment (UE), the message including information based on an over-the-air UE the UE is configured to fly;

means for selecting assistance data based in part on the information in the message; and

and means for transmitting the assistance data to the UE.

72. The location server of claim 71, further comprising:

means for sending a capability request to the UE,

wherein the message is received in response to the capability request.

73. The location server of claim 71, wherein the message corresponds to a request for the assistance data.

74. The location server of claim 71, wherein the message corresponds to a capability indication.

75. The location server of claim 71, wherein the information indicates that the UE is configured as the over-the-air UE.

76. The location server of claim 71, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

77. The location server of claim 76,

Wherein the information also indicates an altitude or elevation of the UE.

78. The location server of claim 71, wherein the information comprises flight path information.

79. The location server of claim 78, wherein the flight path information comprises a sequence of waypoints and associated timestamps.

80. The location server of claim 79, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

81. The location server of claim 78, wherein the flight path information comprises a trajectory and a speed of the UE.

82. The location server of claim 71, wherein the assistance data comprises information associated with one or more beams from one or more base stations angled upward to facilitate communication with an in-flight aerial UE.

83. The location server of claim 71, wherein the assistance data comprises information associated with one or more base stations remote from the UE, wherein one or more other intermediate base stations closer to the UE are omitted from the assistance data.

84. A location server as defined in claim 71, wherein the network entity comprises a Location Management Function (LMF).

85. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to:

86. The non-transitory computer-readable medium of claim 85, wherein the one or more instructions further cause the UE to:

a capability request is received from the location server,

wherein the message is sent in response to the capability request.

87. The non-transitory computer-readable medium of claim 85, wherein the message corresponds to a request for the assistance data.

88. The non-transitory computer-readable medium of claim 85, wherein the message corresponds to a capability indication.

89. The non-transitory computer-readable medium of claim 85, wherein the information indicates that the UE is configured as the over-the-air UE.

90. The non-transitory computer-readable medium of claim 85, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

91. The non-transitory computer readable medium of claim 90,

Wherein the information also indicates an altitude or elevation of the UE.

92. The non-transitory computer-readable medium of claim 85, wherein the information includes flight path information.

93. The non-transitory computer readable medium of claim 92 wherein the flight path information includes a sequence of waypoints and associated timestamps.

94. The non-transitory computer-readable medium of claim 93, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

95. The non-transitory computer-readable medium of claim 92, wherein the flight path information includes a trajectory and a speed of the UE.

96. The non-transitory computer-readable medium of claim 85, wherein the assistance data includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

97. The non-transitory computer-readable medium of claim 85, wherein the assistance data includes information associated with one or more base stations that are remote from the UE, wherein one or more other intermediate base stations that are closer to the UE are omitted from the assistance data.

98. A non-transitory computer-readable medium as recited in claim 85, wherein the network entity comprises a Location Management Function (LMF).

99. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to:

selecting assistance data based in part on the information in the message; and

and sending the auxiliary data to the UE.

100. The non-transitory computer-readable medium of claim 99, wherein the one or more instructions further cause the location server to:

a capability request is sent to the UE,

wherein the message is received in response to the capability request.

101. The non-transitory computer-readable medium of claim 99, wherein the message corresponds to a request for the assistance data.

102. The non-transitory computer-readable medium of claim 99, wherein the message corresponds to a capability indication.

103. The non-transitory computer-readable medium of claim 99, wherein the information indicates that the UE is configured as the over-the-air UE.

104. The non-transitory computer-readable medium of claim 99, wherein the information indicates whether the UE is engaged in a flight state or a ground state.

105. The non-transitory computer readable medium of claim 104,

Wherein the information also indicates an altitude or elevation of the UE.

106. The non-transitory computer-readable medium of claim 99, wherein the information includes flight path information.

107. The non-transitory computer readable medium of claim 106, wherein the flight path information includes a sequence of waypoints and associated timestamps.

108. The non-transitory computer readable medium of claim 107, wherein the sequence of waypoints corresponds to a sequence of points, coordinates, polygons, or ellipses.

109. The non-transitory computer-readable medium of claim 106, wherein the flight path information includes a trajectory and a speed of the UE.

110. The non-transitory computer-readable medium of claim 99, wherein the assistance data includes information associated with one or more beams from one or more base stations that are angled upward to facilitate communication with an in-flight aerial UE.

111. The non-transitory computer-readable medium of claim 99, wherein the assistance data includes information associated with one or more base stations that are remote from the UE, wherein one or more other intermediate base stations that are closer to the UE are omitted from the assistance data.

112. The non-transitory computer-readable medium of claim 99, wherein the network entity comprises a Location Management Function (LMF).