Base station antenna array orientation calibration for cellular positioning

Abstract

A technique for wireless communication is disclosed. In one aspect, a network entity determines the location of a target base station and the location of at least one reference device (710), determines the angle of arrival (AoA) measurement of one or more reference signals received by at least one antenna array of the target base station from at least one reference device (720), determines the expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device (730), and determines the azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement (740).

Description

[0001] Cross-reference to related applications

[0002] This application claims the rights to U.S. Provisional Application No. 63 / 053,447, filed July 17, 2020, entitled “BASE STATIONANTENNA ARRAY ORIENTATION CALIBRATION FOR CELLULAR POSITIONING,” and U.S. Non-Provisional Application No. 17 / 376,873, filed July 15, 2021, entitled “BASE STATIONANTENNA ARRAY ORIENTATION CALIBRATION FOR CELLULAR POSITIONING,” both of which have been assigned to the assignee of this application and are expressly incorporated herein by reference in their entirety. Technical Field

[0003] The various aspects of this disclosure generally relate to wireless communications. Background Technology

[0004] Wireless communication systems have been developed through various generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including temporary 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS) and 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), etc.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to deliver data rates of tens of megabits per second to each of tens of thousands of users, including 1 gigabits per second to dozens of workers on an office floor. To support large-scale sensor deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency should be significantly reduced compared to the current standard. Summary of the Invention

[0006] The following is a simplified overview relating to one or more aspects disclosed herein. Therefore, the following summary should not be considered a broad overview relating to all anticipated aspects, nor should it be considered an identification of key or essential elements relating to all anticipated aspects or a depiction of the scope associated with any particular aspect. Thus, the sole purpose of the following summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the specific implementations given below.

[0007] In one aspect, a method for wireless communication performed by a network entity includes: determining the location of a target base station and the location of at least one reference device; determining angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from at least one reference device; determining an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and determining an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0008] In one aspect, a network entity 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 being configured to: determine the location of a target base station and the location of at least one reference device; determine angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from at least one reference device; determine an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and determine an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0009] In one aspect, a network entity includes: components for determining the location of a target base station and the location of at least one reference device; components for determining angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from at least one reference device; components for determining an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and components for determining an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0010] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: determine the location of a target base station and the location of at least one reference device; determine angle of arrival (AoA) measurements of one or more reference signals received from at least one reference device by at least one antenna array of the target base station; determine an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and determine an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

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

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

[0013] Figure 1 The illustration shows an example wireless communication system according to various aspects of this disclosure.

[0014] Figure 2A and Figure 2B The diagram illustrates an example wireless network architecture based on various aspects of this disclosure.

[0015] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several sample aspects of components that can be adopted and configured to support communications as taught herein in user equipment (UE), base stations, and network entities, respectively.

[0016] Figure 4 This is a diagram illustrating an example base station communicating with an example UE according to various aspects of this disclosure.

[0017] Figure 5 and Figure 6 The illustration shows an example of a positioning procedure based on uplink angle of arrival (UL-AoA) according to various aspects of this disclosure.

[0018] Figure 7 The illustration shows an example wireless communication method according to various aspects of this disclosure. Detailed Implementation

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

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

[0021] Those skilled in the art will recognize that the information and signals described below can be represented using any of a wide variety of different techniques and methods. For example, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, the data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

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

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

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

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

[0026] In some implementations that support UE positioning, the base station may not support the UE's radio access (e.g., it may not support the UE's data, voice, and / or signaling connections), but may alternatively send reference signals to the UE for measurement by the UE, and / or may receive and measure signals sent by the UE. This base station may be referred to as a positioning beacon (e.g., when sending signals to the UE) and / or as a location measurement unit (e.g., when receiving and measuring signals from the UE).

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

[0028] Figure 1The illustration shows an example wireless communication system 100 according to various aspects of this disclosure. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB and / or ng-eNB corresponding to an LTE network, or a gNB corresponding to an NR network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

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

[0030] In addition to other functions, base station 102 may also perform functions related to one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) via backhaul link 134, which may be wired or wireless.

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

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

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

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

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

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

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

[0038] Transmit beams can be quasi-co-located, meaning 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. Specifically, a given type of QCL relationship means that certain parameters about a second reference RF signal on a second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

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

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

[0041] Note that a "downlink" beam can be either a transmit or receive beam, depending on the entity forming it. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, then it is a receive beam used to receive downlink reference signals. Similarly, an "uplink" beam can be either a transmit or receive beam, depending on the entity forming it. For example, if a base station is forming an uplink beam, then it is an uplink receive beam, and if a UE is forming an uplink beam, then it is an uplink transmit beam.

[0042] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into several frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). The mmW band typically includes the FR2, FR3, and FR4 frequency ranges. Therefore, the terms "mmW" and "FR2" or "FR3" or "FR4" are often used interchangeably.

[0043] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and on the cell in which UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and may be (but not necessarily) a carrier in a licensed frequency. The secondary carrier is the carrier operating on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between UE 104 and the anchor carrier, and can 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; for example, UE-specific signaling information and signals may not be present in the secondary carrier because the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier on which a base station is communicating, the terms "cell," "serving cell," "component carrier," and "carrier frequency" are used interchangeably.

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

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

[0046] exist Figure 1 In the example, any of the UEs shown (for simplicity) Figure 1 A UE 104 (shown as a single UE 104) may receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system, which the UE 104 may use as a separate source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on a positioning signal (e.g., signal 124) received from a transmitter. Such transmitters typically transmit signals of repeating pseudo-random noise (PN) codes marked with a predetermined number of chips. While the transmitter is typically located in SV 112, it may sometimes be located at a ground-based control station, base station 102, and / or other UE 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 used to derive geographic location information from SV 112.

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

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

[0049] The wireless communication system 100 may further include one or more UEs, such as UE 190, indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In the example, UE 190 has D2D P2P links 192 and 194. In D2D P2P link 192, one of UEs 104 is connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through D2D P2P link 192). In D2D P2P link 194, WLAN STA 152 is connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through D2D P2P link 194). In this example, D2D P2P links 192 and 194 can use any known method such as LTE Direct (LTE-D) or WiFi Direct (WiFi-D). It is supported by D2D RAT, etc.

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

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

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

[0053] The functions of UPF 262 include acting as an anchor point for intra / inter-RAN mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point for interconnection 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, user plane Quality of Service (QoS) processing (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages via the user plane between UE204 and location servers such as SLP 272.

[0054] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic routing at UPF 262 to route traffic to appropriate destinations, control of policy enforcement and a portion of QoS, and downlink data notification. The interface between SMF266 ​​and AMF 264 is called the N11 interface.

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

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

[0057] The functionality of gNB 222 is divided between gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, location, and session management, in addition to those functions specifically allocated to gNB-DU 228. More specifically, gNB-CU 226 hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 222. gNB-DU 228 is a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of gNB 222. Its operation is controlled by gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. Therefore, UE 204 communicates with gNB-CU226 via RRC, SDAP, and PDCP layers, and with gNB-DU 228 via RLC, MAC, and PHY layers.

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

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

[0060] UE 302 and base station 304 also include, at least in some cases, one or more short-range radio transceivers 320 and 360, respectively. The short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access via at least one designated RAT (e.g., WiFi, LTE-D, etc.). Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for suppressing transmission, etc.) that communicate with other network nodes such as other UEs, access points, base stations, etc., via a wireless communication medium of interest (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for suppressing transmission, etc.). According to the specified RAT, short-range transceivers 320 and 360 can be configured differently for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely, are configured differently for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively. Specifically, short-range transceivers 320 and 360 include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, transceiver and / or Transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

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

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

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

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

[0065] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, for example, to provide functions related to wireless communication and to provide other processing functions. Thus, processors 332, 384, and 394 can provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, 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, field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0066] UE 302, base station 304, and network entity 306 include memory circuitry that respectively implements memories 340, 386, and 396 (e.g., all including memory devices) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may respectively include positioning components 342, 388, and 398. Positioning components 342, 388, and 398 may be part of processors 332, 384, and 394, or hardware circuitry coupled to processors 332, 384, and 394, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functions described herein. In other respects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functions described herein. Figure 3A The diagram illustrates possible locations of the positioning component 342, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a separate component. Figure 3B The diagram illustrates possible locations of the positioning component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a separate component. Figure 3C The diagram illustrates possible locations of the positioning component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a separate component.

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

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

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

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

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

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

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

[0074] Transmitter 314 can use channel estimates derived from a reference signal transmitted by base station 304 or feedback by a channel estimator to select appropriate coding and modulation schemes, and facilitate spatial processing. The spatial stream generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can utilize the corresponding spatial stream to modulate an RF carrier for transmission.

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

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

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

[0078] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces for UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are embodied in the same device (e.g., gNB and location server functions incorporated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

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

[0080] In some designs, network entity 306 can be implemented as a core network component. In other designs, network entity 306 may be a different network operator or operation from the cellular network infrastructure (e.g., NG RAN220 and / or 5GC210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0081] NR supports various cellular network-based positioning technologies, including downlink-based, uplink-based, 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 Angle of Departure (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (TOA) of a reference signal (e.g., a Positioning Reference Signal (PRS)) received from a base station pair, referred to as the Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurement, and reports them to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and the RSTD measurement, the positioning entity is able to estimate the UE's location.

[0082] For DL-AoD positioning, the positioning entity uses beam reports, obtained from measurements of received signal strength from multiple downlink transmitted beams of the UE, to determine the angle between the UE and the transmitting base station. The positioning entity is then able to estimate the UE's location based on the determined angle and the known location of the transmitting base station.

[0083] 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 the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurement and the angle of the receive beam to determine the angle between the UE and the base stations. Based on the determined angle and the known location of the base stations, the positioning entity is then able to estimate the location of the UE.

[0084] Downlink and uplink-based positioning methods include Enhanced Cell ID (E-CID) positioning and Multiple Round Trip Time (RTT) positioning (also known as "Multi-Cell RTT"). In an RTT procedure, the initiator (base station or UE) sends an RTT measurement signal (e.g., PRS or SRS) to the responder (UE or base station), and the responder sends an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response signal, which is called the receive-to-transmit (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, called the transmit-to-receive (Tx-Rx) time difference. The propagation time (also known as "time of flight") between the initiator and the responder can be calculated based on 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 can be combined with other positioning technologies such as UL-AoA and DL-AoD to improve location accuracy.

[0085] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and identifiers, estimated timings, and signal strengths of detected neighboring base stations. The UE's location is then estimated based on this information and the known locations of the base stations.

[0086] To assist in the positioning operation, a location server (e.g., location server 230, LMF 270, SLP272) can provide auxiliary data to the UE. For example, auxiliary data may include the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive positioning subframes, the periodicity of the positioning subframes, the silence sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes themselves without using auxiliary data.

[0087] In the case of OTDOA or DL-TDOA positioning procedures, auxiliary data may further include the expected RSTD value and the associated uncertainty or search window around the expected RSTD. In some cases, the expected RSTD value may range from + / - 500 microseconds (μs). In some cases, when any resources used for positioning measurements are in FR1, the uncertainty of the expected RSTD may range from + / - 32 μs. In other cases, when all resources used for positioning measurements are in FR2, the uncertainty of the expected RSTD may range from + / - 8 μs.

[0088] Location estimation can be referred to by other names, such as location estimate, location, positioning, fixed location, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), or it can be urban and include street addresses, postal addresses, or some other verbal description of the location. Location estimation can also be defined relative to some other known location, or in absolute terms (e.g., using latitude, longitude, and possible altitude). Location estimation can include expected errors or uncertainties (e.g., by including the area or volume of the location where it is expected to be included at some specified or default confidence level).

[0089] Figure 4 Figure 400 illustrates a base station (BS) 402 (which may correspond to any of the UEs described herein) communicating with UE 404 (which may correspond to any of the UEs described herein). Reference Figure 4 Base station 402 can transmit beamformed signals to UE 404 on one or more transmit beams 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h, each transmit beam having a beam identifier that can be used by UE 404 to identify the corresponding beam. When base station 402 performs beamforming toward UE 404 using a single antenna array (e.g., a single TRP / cell), base station 402 can perform "beam sweeping" by transmitting the first beam 402a, then beam 402b, and so on until the last beam 402h is transmitted. Alternatively, base station 402 can transmit beams 402a-402h in a certain pattern, such as beam 402a, then beam 402h, then beam 402b, then beam 402g, and so on. In the case where base station 402 uses multiple antenna arrays (e.g., multiple TRPs / cells) to beamform toward UE 404, each antenna array can perform beam sweeping of a subset of beams 402a-402h. Alternatively, each of beams 402a-402h can correspond to a single antenna or antenna array.

[0090] Figure 4Further illustration shows the paths 412c, 412d, 412e, 412f, and 412g followed by beamforming signals transmitted on beams 402c, 402d, 402e, 402f, and 402g, respectively. Each path 412c, 412d, 412e, 412f, and 412g may correspond to a single "multipath," or may include clusters of multiple "multipaths" due to the propagation characteristics of radio frequency (RF) signals through the environment. Note that although only the paths of beams 402c-402g are shown, this is for simplicity, and signals transmitted on each of beams 402a-402h will follow a certain path. In the example shown, paths 412c, 412d, 412e, and 412f are straight lines, while path 412g reflects obstacles 420 (e.g., buildings, vehicles, terrain features, etc.).

[0091] UE 404 can receive beamforming signals from base station 402 on one or more receive beams 404a, 404b, 404c, 404d. Note that, for simplicity, Figure 4 The beams shown in the diagram represent either transmit or receive beams, depending on which of the base station 402 and UE 404 is transmitting and which is receiving. Therefore, UE 404 can also transmit beamforming signals to base station 402 on one or more of the beams 404a-404d, and base station 402 can receive beamforming signals from UE 404 on one or more of the beams 402a-402h.

[0092] On one hand, base station 402 and UE 404 can perform beam training to align their transmit and receive beams. For example, depending on environmental conditions and other factors, base station 402 and UE 404 can determine that the optimal transmit and receive beams are 402d and 404b, or 402e and 404c, respectively. The direction of the optimal transmit beam for base station 402 can be the same as or different from the direction of the optimal receive beam, and similarly, the direction of the optimal receive beam for UE 404 can be the same as or different from the direction of the optimal transmit beam. However, it should be noted that aligning the transmit and receive beams is not necessary for performing downlink departure angle (DL-AoD) or uplink arrival angle (UL-AoA) positioning procedures.

[0093] exist Figure 4In the example, if base station 402 transmits reference signals to UE 404 on beams 402c, 402d, and 402e, then transmit beam 402d is optimally aligned with the line-of-sight (LOS) path 410, while transmit beams 402c and 402e are not. Thus, beam 402d will have a stronger and / or earlier channel impulse response and a higher received signal strength at UE 404 than beams 402c and 402e. UE 404 can report to base station 402 the channel impulse response and received signal strength of each measured transmit beam 402c, 402d, and 402e, or alternatively, report the transmit beam with the strongest / earliest channel impulse response and highest received signal strength. Figure 4 The example is identified by beam 402d. In either case, base station 402 is able to estimate the angle of the transmit beam that has the highest received signal strength and the strongest / earliest channel impulse response at UE 404 from its own angle to UE 404, which is transmit beam 402d in this case.

[0094] Figure 5 Figure 500 illustrates an example UL-AoA positioning procedure based on various aspects of this disclosure. Figure 5 In the example, base station (BS) 502 (e.g., any of the base stations described herein) receives one or more reference signals (e.g., UL-PRS, SRS, DMRS, etc.) from UE 504 (e.g., any of the UEs described herein) on multiple uplink receive beams 512, 514, and 516. Base station 502 determines the angle of the optimal receive beam 512, 514, or 516 for receiving one or more reference signals from UE 504 as the angle from itself to UE 504. The angle of the receive beam on which base station 502 receives one or more reference signals from UE 504 is referred to as the “angle of arrival” or “AoA” between base station 502 and UE 504.

[0095] More specifically, each of the receive beams 512, 514, and 516 will likely result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) for one or more reference signals at base station 502. Furthermore, for the receive beams further away from the actual LOS path between base station 502 and UE 504, the channel impulse response of one or more reference signals may be smaller and / or later than for the receive beams closer to the LOS path. Similarly, the received signal strength may be lower for the receive beams further away from the LOS path than for the receive beams closer to the LOS path. Figure 5In the example, the receive beam 514 is closest to the LOS path between base station 502 and UE 504, and therefore will likely have the strongest and / or earliest channel impulse response and the highest received signal strength. Therefore, base station 502 will estimate the angle of the receive beam 514 from its own AoA to UE 504.

[0096] Note that the AoA of the receive beam that results in the highest received signal strength and the strongest / earliest channel impulse response is not necessarily along the LOS path. However, for AoA-based positioning purposes, this is assumed to be true.

[0097] When UE 504 is estimating its location (i.e., the UE is the location entity), it needs to obtain the geographic location of base station 502. UE 504 can obtain its location from, for example, base station 502 itself or a location server (e.g., location server 230, LMF 270, SLP272). Given the distance to base station 502 (based on RTT or timing advance), the angle between base station 502 and UE 504 (based on the AoA of the optimal receive beam 510), and the known geographic location of base station 502, UE 504 is able to estimate its location.

[0098] Alternatively, when a positioning entity, such as base station 502 or a location server, is estimating the location of UE 504, base station 502 reports the AoA of receive beam 514, which results in the highest received signal strength and strongest / earliest channel impulse response of the reference signal received from UE 504, or all received signal strengths and channel impulse responses of all receive beams 512, 514, and 516 (which allows the positioning entity to determine the optimal receive beam). Base station 502 may additionally estimate its distance to UE 504 by performing an RTT positioning procedure with UE 504 and report that distance to UE 504 or the positioning entity (if not UE 504). The positioning entity can then estimate the location of UE 504 based on the distance from UE 504 to base station 502 (if available), the AoA of the identified receive beam 514, and the known geographic location of base station 502.

[0099] Figure 6 Figure 600 illustrates an example UL-AoA positioning procedure based on various aspects of this disclosure. Figure 6In the example, there are two base stations involved, 602-1 and 602-2 (collectively referred to as base station 602), and each base station (BS) 602 has determined the optimal uplink receive beam on which it receives one or more reference signals (e.g., UL-PRS, SRS, DMRS, etc.) from UE 604 (e.g., any UE described herein). As shown, the optimal receive beam for base station 602-1 is receive beam 612, and the optimal receive beam for base station 602-2 is receive beam 614.

[0100] Base station 602 can report its determined AoA (i.e., the angles of receive beams 612 and 614) between itself and UE 604 to a positioning entity (e.g., a location server, serving base station, or UE). Using this information and knowing the geographic location of base station 602, the positioning entity can estimate the location of UE 604 as the intersection of the receive AoA. In this case, an RTT positioning procedure is not required between base station 602 and UE 604.

[0101] It should be noted that for a two-dimensional (2D) positioning solution, at least two involved base stations 602 should be present; however, as will be understood, the more base stations 602 involved in the positioning procedure, the more accurate the estimated location of the UE 604 will be. Therefore, although Figure 6 The diagram shows two base stations 602, but it should be understood that there can be more than two base stations 602.

[0102] The angle between the base station and the UE, determined by the angle of the uplink receive beam used for UL-AoA positioning, can be reported as AoA (and denoted as "φ") and the vertical angle of arrival (ZoA) (and denoted as "θ"). AoA and ZoA define estimated angles relative to a reference direction to the UE, which is determined by the base station receiving reference signals from the UE. The reference direction can be defined according to a global coordinate system (GCS) or a local coordinate system (LCS).

[0103] For the Global Crossroads (GCS), the reference direction relative to the GCS is defined as follows. For AoA, the reference direction (i.e., φ = 0 degrees) is geographic north, and the angle increases counterclockwise. Thus, for example, φ = 90 degrees points to geographic west. For ZoA, the reference direction (i.e., θ = 0 degrees) is the vertex / vertical direction. Thus, for example, θ = 90 degrees points to the horizon.

[0104] For LCS, the reference direction is defined in 3GPP Technical Specification (TS) 38.901 (which is publicly available and incorporated herein by reference in its entirety) as follows: For AoA, the reference direction is the x-axis of the antenna array, and the angle increases counterclockwise. Thus, for example, φ = 0 degrees points along the x-axis, and φ = 90 degrees points along the yz plane. For ZoA, the reference direction is the z-axis of the antenna array. Thus, for example, θ = 0 degrees points along the z-axis, and θ = 90 degrees points along the xy plane.

[0105] The conversion from LCS to GCS of an antenna array is based on the known azimuth of the antenna array in the GCS. Specifically, the azimuth of the antenna array can be represented by a set of angles α (azimuth), β (downtilt), and γ (tilt) in the GCS. These angles can be reported along with AoA (φ) and ZoA (θ) in the LCS (if the location entity is not yet known) and can be used to convert LCS AoA to GCS AoA.

[0106] The reference orientation reported in the AoA / ZoA of the antenna array's LCS is based on the antenna array's azimuth (i.e., relative to the antenna array's azimuth definition). Each base station should have been calibrated (e.g., at installation) so that the antenna array's azimuth in the GCS is known. However, the antenna array's azimuth may change during its lifespan. For example, weather or natural disasters (e.g., earthquakes) can cause changes in the antenna array's azimuth. Some residual calibration errors may also exist during the initial antenna array setup.

[0107] The network (e.g., location server 230, LMF 270, SLP 272) may be unaware of changes in the orientation of the antenna array, which, as will be understood, can lead to positioning errors when using angle-based positioning techniques such as UL-AoA or DL-AoD. Even if the network is aware of the problem, dispatching technicians to manually recalibrate the antenna array would be quite expensive, especially if access to the antenna array is difficult. Therefore, this disclosure provides a technique for calibrating antenna arrays using over-the-air NR positioning technology.

[0108] The first technique described in this paper is base station-assisted azimuth calibration of airborne antenna arrays. In this technique, reference signals received at the target base station from one or more neighboring base stations can be used to calibrate one or more antenna arrays of the target base station. The location of the base stations (and, where possible, the location of each antenna array of the base station) is known to the network and should be fixed unless there are any drastic environmental changes. However, in cases where the location of the base stations has changed since it was last determined, the initial stage of the calibration method is to measure the location of each involved base station using, for example, GPS, and report that location to the network. The location of the base station can be the center point of the base station, the center point of each antenna array, or both. Here, the base stations involved can be all base stations in the network, or a set of base stations expected to be near the target base station based on their currently stored locations plus the target base station (i.e., the base stations to be calibrated).

[0109] Once the location of the base stations involved is confirmed or updated, the network can select the base station closest to the target base station or the base station with the best channel conditions for positioning. For example, a base station with the best channel conditions for positioning could be one that is expected to be able to communicate with the target base station via a LOS path / channel. Such base stations can be identified based on their known locations relative to each other and knowledge of their surrounding environment (e.g., terrain, street maps, building layouts, etc.).

[0110] Selection can also be based on the target base station's measurements of reference signals received from neighboring base stations. For example, the target base station can identify a set of neighboring base stations with signal strengths above a certain threshold or channel impulse responses indicating that the reference signal follows a LOS path. The target base station can then recommend the identified set of neighboring base stations to the network as the set of base stations to be used for calibration.

[0111] The network can then coordinate the configuration of reference signals to be used between the selected base stations. This configuration can specify the type of reference signal, such as PRS, CSI-RS, SRS (in this case, transmitted by the base station), etc. It can also specify the time / frequency configuration of the reference signal (e.g., which resource elements, resource blocks, time slots, subframes, etc.) and the system frame number to begin reference signal transmission. Furthermore, since the spatial relationship (e.g., direction and distance) between each selected base station and the target base station can be derived based on the location of each base station (at least in azimuth), the network can also configure base stations to beamform the reference signal in that direction to reduce the impact of potential NLOS paths on subsequent AoA measurements.

[0112] Once configured, the selected base station (which can be just one base station) transmits the configured reference signal to the target base station, and the target base station measures the AoA of the reference signal received by one or more of its antenna arrays. For example, the selected base stations can be chosen such that they are clustered to one side of the target base station, thus facing an antenna array (typically configured as a panel) of the target base station. In this case, the antenna array will most likely receive the reference signal and measure the AoA. As another example, the selected base stations can surround the target base station, and therefore, the reference signal can be received and the AoA measured by all the antenna arrays of the target base station.

[0113] Subsequently, the reference orientation of the receiving antenna array can be calibrated based on the AoA measurements. For example, the target base station can report each AoA measurement of the antenna array relative to its existing reference orientation. The network can then deduce what the AoA between the antenna array and each measured base station should be (called the "genie" AoA or "expected" AoA) based on the base station's known location. The difference between the measured AoA and the corresponding "genie" AoA is the azimuth offset of the target base station's receiving antenna array. The network can then use this offset to calibrate the reference orientation associated with that antenna array of the target base station and any AoA measurements reported by the target base station for that antenna array.

[0114] Alternatively, if the target base station is provided with the location of a selected base station, the target base station can calculate the offset locally. The target base station can then deliver the calculated azimuth offset or the now-calibrated reference direction to the network or any UE participating in the DL-AoA positioning procedure. In this case, any AoA measurements reported by the target base station will not need to be calibrated on the network side, as the reference direction will already be calibrated.

[0115] The second technique described in this paper is UE-assisted azimuth calibration of an over-the-air base station antenna array. In this technique, reference signals received from one or more UEs at a target base station can be used to calibrate one or more antenna arrays of the target base station. This technique is similar to the first technique, except that a neighboring UE (which may be served by the target base station) sends a reference signal to the target base station, rather than a neighboring base station sending a reference signal to the target base station.

[0116] As described above with reference to the first technique, the location of the target base station should be known to the network via some RAT (e.g., NR) or RAT-independent (e.g., GPS) technology. The location of the involved UE also needs to be determined, and this location can be estimated using GPS or NR positioning techniques. To improve positioning accuracy, the involved UE should be in a LOS condition relative to the target base station. Furthermore, where possible, the involved UE should be in open space to receive reference signals (e.g., NR or GPS) with less attenuation and multipath propagation.

[0117] Where possible, other means exist to enhance UE positioning accuracy. For example, if NR positioning is used, the UE should be configured to transmit reference signals using high bandwidth (e.g., 100MHz at FR1 and 400MHz at FR2). The UE should also report its maximum capabilities related to positioning accuracy, such as its maximum supported bandwidth, group delay calibration error, etc. In some cases, the UE may have the capability to perform hybrid positioning (i.e., both RAT and RAT-independent positioning) to achieve greater positioning accuracy. This capability can also be reported to the network through the UE's capability report.

[0118] The UEs involved can be all UEs served by the target base station, all UEs within a certain proximity of the target base station capable of participating in calibration (e.g., based on user permission, device capabilities, etc.), or a set of UEs with previously estimated locations within a certain threshold distance of the target base station. For example, each capable UE served by the target base station can perform a location procedure and report its location to the network. The network can then select a set of these UEs. For example, where possible, UEs can be selected such that they are clustered to one side of the target base station, thus facing an antenna array / panel of the target base station. In this case, the antenna array will likely receive a reference signal and measure the AoA. As another example, the UEs involved can be around the target base station, and therefore, the reference signal can be received and the AoA measured by all antenna arrays of the target base station.

[0119] The reference signal transmitted by the involved UE can be the Location-Specific Reference Signal (SRS) defined in the NR (also known as the UL-PRS). Other reference signals specifically designed for antenna array calibration can also be used, but reusing existing Location-Specific Reference Signals will allow for backward compatibility with existing equipment. Given that the approximate spatial relationship between the target base station and the UE is known to the network (based on the location procedure performed in Phase 1), the Location-Specific Reference Signal can be configured to beamform toward the target base station to reduce the effects of potential multipath propagation.

[0120] Typically, the transmission of uplink reference signals (e.g., SRS for positioning) is configured by the serving base station. Therefore, if the target base station is the serving base station for the involved UEs, it will configure uplink resources (in time and frequency) for those UEs to transmit reference signals. If the target base station is not the serving base station for all involved UEs, the serving base station will need to coordinate with the target base station to notify it of the uplink resources on which the involved UEs will transmit reference signals.

[0121] Similar to the current UL-AoA positioning procedure, each involved UE sends its configured SRS for positioning to the target base station. The target base station measures the AoA associated with each UE (as referenced above). Figure 5 As described above (and then able to perform antenna array azimuth calibration, as described with reference to the first technique above). Specifically, the target base station reports each AoA measurement relative to the existing reference direction of the receiving antenna array. The network is able to derive a "sprite" AoA between each UE and the target base station (specifically, the receiving antenna array) based on the known locations of the target base station and the involved UEs determined in the first phase. The difference between the measured AoA and the corresponding "sprite" AoA is the azimuth offset of the receiving antenna array.

[0122] Once the azimuth offset of the target base station's antenna array is known, the network can use this offset to calibrate any AoA measurements reported from the target base station for that antenna array. Alternatively, as described above, the target base station can calculate the offset locally and inform the network or the involved UE of the calibration reference direction of the antenna array. In this case, it is not necessary to calibrate any AoA reported by the target base station on the network side, since the reference direction has already been calibrated.

[0123] The antenna array azimuth calibration technique disclosed herein does not need to be performed frequently, as changes to the antenna array azimuth are not expected to occur frequently during normal operation. Therefore, having a mechanism to trigger the calibration process would be beneficial.

[0124] The first technique involves configuring a long period for antenna array azimuth calibration. This period can be days, weeks, months, or even years. The second technique, if the network supports integrity and reliability measurements for positioning (e.g., UL-AoA, DL-AoD), allows the network to trigger azimuth calibration for the antenna array (or all antenna arrays of the base station) once the integrity and reliability of the AoA measurement for the antenna array drops below a certain threshold. The third technique allows one or more UEs served by the base station to perform location estimation using measurements other than AoA (whether RAT or RAT-independent measurements). The base station or network can determine the offset between the "ghost" AoA (as determined by the UE's location estimation) and the actual AoA measurement of the uplink reference signal transmitted by the UE. If the offset exceeds a threshold during multiple AoA measurements, the network can trigger antenna array azimuth calibration.

[0125] On the one hand, while the different techniques described herein have described antenna array azimuth calibration using neighboring base stations or UEs, as will be understood, a combination of neighboring base stations and UEs can be used for calibration.

[0126] Figure 7 The illustration depicts an example method 700 of wireless communication according to various aspects of this disclosure. In one aspect, method 700 can be performed by a network entity, such as a location server (e.g., location server 230, LMF 270, SLP 272) or other entities in the core network (e.g., core network 170, 5GC 210, 5GC 260). Alternatively, the network entity can be a base station, such as any base station described herein. Alternatively, the network entity can be a UE, such as any UE described herein.

[0127] At 710, the network entity determines the location of a target base station (e.g., any of the base stations described herein) and the location of at least one reference device (e.g., any of the base stations or UEs described herein). In one aspect, when the network entity is a UE, operation 710 can be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any one or all of which can be considered components for performing the operation. In another aspect, when the network entity is a base station, operation 710 can be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which can be considered components for performing the operation. In another aspect, when the network entity is a core network entity, operation 710 can be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which can be considered components for performing the operation.

[0128] At 720, the network entity determines the AoA measurement of one or more reference signals received by at least one antenna array of the target base station from at least one reference device. In one aspect, when the network entity is a UE, operation 720 can be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any one or all of which can be considered as components for performing the operation. In another aspect, when the network entity is a base station, operation 720 can be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning component 388, any one or all of which can be considered as components for performing the operation. In another aspect, when the network entity is a core network entity, operation 720 can be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any one or all of which can be considered as components for performing the operation.

[0129] At 730, the network entity determines the expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device. In one aspect, when the network entity is a UE, operation 730 can be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any one or all of which can be considered as components for performing the operation. In another aspect, when the network entity is a base station, operation 730 can be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning component 388, any one or all of which can be considered as components for performing the operation. In another aspect, when the network entity is a core network entity, operation 730 can be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any one or all of which can be considered as components for performing the operation.

[0130] At 740, the network entity determines the azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement. In one aspect, when the network entity is a UE, operation 740 can be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any one or all of which can be considered components for performing the operation. In another aspect, when the network entity is a base station, operation 740 can be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which can be considered components for performing the operation. In another aspect, when the network entity is a core network entity, operation 740 can be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which can be considered components for performing the operation.

[0131] On one hand, when the network entity is the UE, the determination operations at points 710 to 730 may include receiving these values ​​(i.e., the location of the target base station, the location of at least one reference device (if not the UE), AoA measurement, and expected AoA) from a third-party server such as a crowdsourcing server. In this way, the UE can determine the azimuth offset and report it back to the crowdsourcing server. The crowdsourcing server is not a network entity.

[0132] As will be understood, the technical advantage of method 700 is that it uses air signaling to calibrate the orientation of the antenna array.

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

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

[0135] Clause 1. A method for wireless communication performed by a network entity, comprising: determining the location of a target base station and the location of at least one network node; determining angle of arrival (AoA) measurements of one or more reference signals received from at least one network node by at least one antenna array of the target base station; determining an expected AoA between the at least one antenna array and the at least one network node based on the location of the target base station and the location of the at least one network node; and determining an azimuth offset of the at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0136] Clause 2. The method described in Clause 1 further includes: calibrating AoA measurements associated with at least one antenna array based on azimuth offset.

[0137] Clause 3. The method according to any one of Clauses 1 to 2 further includes: storing the azimuth offset in the memory of the network entity.

[0138] Clause 4. The method according to any one of Clauses 1 to 3, wherein at least one network node is at least one base station.

[0139] Clause 5. The method described in Clause 4, wherein the location of the target base station and the location of at least one network node are determined using a satellite positioning system (SPS).

[0140] Clause 6. The method according to any one of Clauses 4 to 5, wherein the one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

[0141] Clause 7. The method according to any one of Clauses 1 to 6, wherein the network entity includes the core network entity.

[0142] Clause 8. The method according to Clause 7, wherein determining the location of the target base station and the location of at least one network node includes obtaining the location of the target base station and the location of at least one network node from the target base station, at least one network node, a user equipment (UE) involved in a downlink AoA location session with the target base station, a memory of a network entity, or any combination thereof, and determining the AoA measurement includes obtaining the AoA measurement from the target base station, at least one network node, the UE, a memory of a network entity, or any combination thereof.

[0143] Clause 9. The method according to any one of Clauses 7 to 8, wherein determining the expected AoA includes obtaining the expected AoA from a target base station, at least one network node, a UE involved in a downlink AoA positioning session with the target base station, a memory of a network entity, or any combination thereof.

[0144] Clause 10. The method according to any one of Clauses 7 to 9 further includes: transmitting configuration for one or more reference signals to a target base station and at least one network node.

[0145] Clause 11. The method according to Clause 10, wherein the configuration instructs at least one network node to transmit time and / or frequency resources of one or more reference signals thereon.

[0146] Clause 12. The method according to any one of Clauses 10 to 11, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0147] Clause 13. The method according to any one of Clauses 7 to 12 further includes: selecting at least one network node from a plurality of network nodes.

[0148] Clause 14. The method according to Clause 13, wherein at least one network node is selected based on: at least one network node being within a threshold distance of the target base station; channel conditions between at least one network node and the target base station indicating that at least one network node and the target base station are within each other's site lines; a recommendation for at least one network node being received from the target base station; or any combination thereof.

[0149] Clause 15. The method according to any one of Clauses 1 to 6, wherein the network entity includes the target base station.

[0150] Clause 16. The method according to Clause 15, wherein: determining the location of at least one network node includes obtaining the location of at least one network node from at least one network node, a UE involved in a downlink AoA positioning session with a target base station, a core network entity, a memory of a network entity, or any combination thereof, and determining the AoA measurement includes measuring the AoA measurement.

[0151] Clause 17. The method according to any one of Clauses 15 to 16 further includes: sending configuration for one or more reference signals to at least one network node.

[0152] Clause 18. The method according to Clause 17, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0153] Clause 19. The method according to any one of Clauses 1 to 18, wherein the AoA measurement is relative to a reference direction of at least one antenna array.

[0154] Clause 20. The method according to Clause 19, wherein determining the azimuth offset comprises: determining the difference between the expected AoA and the AoA measurement; and determining the azimuth offset of at least one antenna array based on a reference direction and the difference between the expected AoA and the AoA measurement.

[0155] Clause 21. The method according to any one of Clauses 19 to 20, wherein the reference direction is in the local coordinate system of the target base station.

[0156] Clause 22. The method according to any one of Clauses 1 to 3 and 7 to 21, wherein at least one network node is at least one user equipment (UE).

[0157] Clause 23. The method described in Clause 22, wherein the location of at least one network node is determined using a satellite positioning system (SPS) or a cellular-based positioning method.

[0158] Clause 24. The method according to any one of Clauses 22 to 23, wherein one or more reference signals include one or more SRS for positioning.

[0159] Clause 25. The method according to any one of Clauses 22 to 24 further includes: receiving a capability report from at least one network node, the capability report indicating the capability of at least one network node in relation to transmitting uplink reference signals for positioning.

[0160] Clause 26. The method according to any one of Clauses 1 to 25, wherein the network entity periodically determines the azimuth offset of at least one antenna array.

[0161] Clause 27. The method according to any one of Clauses 1 to 26, wherein the network entity determines the azimuth offset of at least one antenna array based on the integrity and reliability of the AoA measurement being below a threshold.

[0162] Clause 28. The method according to any one of Clauses 1 to 27, wherein the network entity determines the azimuth offset of at least one antenna array based on the expected difference between the AoA and the AoA measurement being greater than a threshold.

[0163] Clause 29. The method pursuant to any one of Clauses 1 to 6 and 19 to 28, wherein the network entity includes the UE.

[0164] Clause 30. The method according to Clause 29, wherein determining the location of the target base station and the location of at least one network node includes obtaining the location of the target base station and the location of at least one network node from the target base station, at least one network node, a third-party server, or any combination thereof; determining the AoA measurement includes obtaining the AoA measurement from the target base station, at least one network node, a third-party server, or any combination thereof; and determining the expected AoA includes obtaining the expected AoA from the target base station, at least one network node, a third-party server, or any combination thereof.

[0165] Clause 31. An apparatus comprising a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, the memory, at least one transceiver, and at least one processor being configured to perform a method according to any one of Clauses 1 to 30.

[0166] Clause 32. An apparatus comprising components for performing the method according to any one of Clauses 1 to 30.

[0167] Clause 33. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions including at least one instruction for causing a computer or processor to perform a method according to any one of Clauses 1 to 30.

[0168] Additional implementation examples are described in the following numbered clauses:

[0169] Clause 1. A method for wireless communication performed by a network entity, comprising: determining the location of a target base station and the location of at least one reference device; determining angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from at least one reference device; determining an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and determining an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0170] Clause 2. The method described in Clause 1 further includes: calibrating AoA measurements associated with at least one antenna array based on azimuth offset.

[0171] Clause 3. The method according to any one of Clauses 1 to 2, wherein at least one reference device is at least one base station.

[0172] Clause 4. The method according to Clause 3, wherein one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

[0173] Clause 5. The method according to any one of Clauses 1 to 4, wherein the network entity includes the core network entity.

[0174] Clause 6. The method of claim 5, wherein determining the location of the target base station and the location of at least one reference device comprises obtaining the location of the target base station and the location of at least one reference device from the memory of the target base station, the at least one reference device, the user equipment (UE) involved in the uplink AoA positioning session with the target base station, the memory of the network entity, or any combination thereof; determining the AoA measurement comprises obtaining the AoA measurement from the memory of the target base station, the at least one reference device, the UE, the memory of the network entity, or any combination thereof; and determining the expected AoA comprises obtaining the expected AoA from the memory of the target base station, the at least one reference device, the UE, the memory of the network entity, or any combination thereof.

[0175] Clause 7. The method according to any one of Clauses 5 to 6 further includes: transmitting a configuration for one or more reference signals to a target base station and at least one reference device.

[0176] Clause 8. The method according to Clause 7, wherein the configuration indicates that at least one reference device will transmit one or more reference signals thereon time and / or frequency resources.

[0177] Clause 9. The method according to any one of Clauses 7 to 8, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0178] Clause 10. The method according to any one of Clauses 5 to 9 further includes: selecting at least one reference device from a plurality of reference devices.

[0179] Clause 11. The method according to Clause 10, wherein at least one reference device is selected based on: at least one reference device being within a threshold distance of the target base station; channel conditions between at least one reference device and the target base station indicating that at least one reference device and the target base station are within each other's site lines; a recommendation for at least one reference device being received from the target base station; or any combination thereof.

[0180] Clause 12. The method according to any one of Clauses 1 to 4, wherein the network entity is the target base station.

[0181] Clause 13. The method according to Clause 12, wherein: determining the location of at least one reference device includes obtaining the location of at least one reference device from at least one reference device, a UE involved in an uplink AoA positioning session with a target base station, a core network entity, a memory of a network entity, or any combination thereof, and determining the AoA measurement includes measuring the AoA of one or more reference signals.

[0182] Clause 14. The method according to any one of Clauses 12 to 13 further includes: transmitting a configuration for one or more reference signals to at least one reference device.

[0183] Clause 15. The method according to Clause 14, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0184] Clause 16. The method according to any one of Clauses 1 to 15, wherein the AoA measurement is relative to a reference direction of at least one antenna array.

[0185] Clause 17. The method according to Clause 16, wherein determining the azimuth offset comprises: determining the difference between the expected AoA and the AoA measurement; and determining the azimuth offset of at least one antenna array based on a reference direction and the difference between the expected AoA and the AoA measurement.

[0186] Clause 18. The method according to any one of Clauses 1, 2 and 4 to 17, wherein at least one reference device is at least one user equipment (UE).

[0187] Clause 19. The method according to any one of Clauses 1 to 18, wherein the location of the target base station and the location of at least one reference device are determined using a satellite positioning system (SPS) or a cellular-based positioning method.

[0188] Clause 20. The method according to any one of Clauses 1 to 19, wherein the azimuth offset of at least one antenna array is determined periodically.

[0189] Clause 21. The method according to any one of Clauses 1 to 20, wherein the azimuth offset of at least one antenna array is determined based on the integrity and reliability of the AoA measurement being below a threshold.

[0190] Clause 22. The method according to any one of Clauses 1 to 21, wherein the azimuth offset of at least one antenna array is determined based on the expected difference between the AoA and the AoA measurement being greater than a threshold.

[0191] Clause 23. A network entity 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 being configured to: determine the location of a target base station and the location of at least one reference device; determine angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from the at least one reference device; determine an expected AoA between the at least one antenna array and the at least one reference device based on the location of the target base station and the location of the at least one reference device; and determine an azimuth offset of the at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0192] Clause 24. The network entity as described in Clause 23, wherein at least one processor is further configured to: calibrate AoA measurements associated with at least one antenna array based on azimuth offset.

[0193] Clause 25. A network entity pursuant to any one of Clauses 23 to 24, wherein at least one reference device is at least one base station.

[0194] Clause 26. A network entity as described in Clause 25, wherein one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

[0195] Clause 27. A network entity pursuant to any one of Clauses 23 to 26, wherein a network entity includes a core network entity.

[0196] Clause 28. The network entity as described in Clause 27, wherein at least one processor is configured to: determine the location of a target base station and the location of at least one reference device, including at least one processor being configured to obtain the location of the target base station and the location of at least one reference device from the target base station, at least one reference device, a user equipment (UE) involved in an uplink AoA positioning session with the target base station, a memory of the network entity, or any combination thereof; determine an AoA measurement, including at least one processor being configured to obtain an AoA measurement from the target base station, at least one reference device, the UE, a memory of the network entity, or any combination thereof; and determine a anticipated AoA, including at least one processor being configured to obtain a anticipated AoA from the target base station, at least one reference device, the UE, a memory of the network entity, or any combination thereof.

[0197] Clause 29. A network entity pursuant to any one of Clauses 27 to 28, wherein at least one processor is further configured to transmit configuration for one or more reference signals to a target base station and at least one reference device via at least one transceiver.

[0198] Clause 30. A network entity as described in Clause 29, wherein the configuration indicates that at least one reference device will transmit one or more reference signals thereon using time and / or frequency resources.

[0199] Clause 31. A network entity according to any one of Clauses 29 to 30, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0200] Clause 32. A network entity pursuant to any one of Clauses 27 to 31, wherein at least one processor is further configured to: select at least one reference device from a plurality of reference devices.

[0201] Clause 33. A network entity as described in Clause 32, wherein at least one reference device is selected based on: at least one reference device being within a threshold distance of a target base station; channel conditions between at least one reference device and the target base station indicating that at least one reference device and the target base station are within each other's site lines; a recommendation for at least one reference device being received from the target base station; or any combination thereof.

[0202] Clause 34. A network entity pursuant to any one of Clauses 23 to 26, wherein the network entity is the target base station.

[0203] Clause 35. The network entity as described in Clause 34, wherein at least one processor is configured to: determine the location of at least one reference device, including at least one processor being configured to obtain the location of at least one reference device from at least one reference device, a UE involved in an uplink AoA positioning session with a target base station, a core network entity, a memory of the network entity, or any combination thereof; and determine AoA measurement, including at least one processor being configured to measure the AoA of one or more reference signals.

[0204] Clause 36. A network entity pursuant to any one of Clauses 34 to 35, wherein at least one processor is further configured to transmit configuration for one or more reference signals to at least one reference device via at least one transceiver.

[0205] Clause 37. A network entity as described in Clause 36, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0206] Clause 38. A network entity pursuant to any one of Clauses 23 to 37, wherein the AoA measurement is relative to a reference direction of at least one antenna array.

[0207] Clause 39. The network entity as described in Clause 38, wherein at least one processor configured to determine azimuth offset includes at least one processor configured to: determine the difference between the expected AoA and the AoA measurement; and determine the azimuth offset of at least one antenna array based on a reference direction and the difference between the expected AoA and the AoA measurement.

[0208] Clause 40. A network entity pursuant to any one of Clauses 23, 24 and 26 to 39, wherein at least one reference device is at least one user equipment (UE).

[0209] Clause 41. A network entity pursuant to any one of Clauses 23 to 40, wherein the location of the target base station and the location of at least one reference device are determined using a satellite positioning system (SPS) or a cellular-based positioning method.

[0210] Clause 42. A network entity according to any one of Clauses 23 to 41, wherein the azimuth offset of at least one antenna array is periodically determined.

[0211] Clause 43. A network entity pursuant to any one of Clauses 23 to 42, wherein the azimuth offset of at least one antenna array is determined based on the integrity and reliability of AoA measurements being below a threshold.

[0212] Clause 44. A network entity according to any one of Clauses 23 to 43, wherein the azimuth offset of at least one antenna array is determined based on the expected difference between the AoA and the AoA measurement being greater than a threshold.

[0213] Clause 45. A network entity comprising: components for determining the location of a target base station and the location of at least one reference device; components for determining angle of arrival (AoA) measurements of one or more reference signals received by at least one antenna array of the target base station from at least one reference device; components for determining an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and components for determining an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0214] Clause 46. The network entity as described in Clause 45 further includes: a component for calibrating AoA measurements associated with at least one antenna array based on azimuth offset.

[0215] Clause 47. A network entity pursuant to any one of Clauses 45 to 46, wherein at least one reference device is at least one base station.

[0216] Clause 48. A network entity as described in Clause 47, wherein one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

[0217] Clause 49. A network entity pursuant to any one of Clauses 45 to 48, wherein a network entity includes a core network entity.

[0218] Clause 50. The network entity as described in Clause 49, wherein the components for determining the location of a target base station and the location of at least one reference device include components for obtaining the location of the target base station and the location of at least one reference device from the target base station, at least one reference device, a user equipment (UE) involved in an uplink AoA positioning session with the target base station, a memory of the network entity, or any combination thereof; the components for determining an AoA measurement include components for obtaining an AoA measurement from the target base station, at least one reference device, the UE, a memory of the network entity, or any combination thereof; and the components for determining a desired AoA include components for obtaining a desired AoA from the memory of the target base station, at least one reference device, the UE, a memory of the network entity, or any combination thereof.

[0219] Clause 51. The network entity according to any one of Clauses 49 to 50 further includes: a component for transmitting configuration for one or more reference signals to a target base station and at least one reference device.

[0220] Clause 52. A network entity as described in Clause 51, wherein the configuration indicates that at least one reference device will transmit one or more reference signals thereon using time and / or frequency resources.

[0221] Clause 53. A network entity according to any one of Clauses 51 to 52, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0222] Clause 54. The network entity pursuant to any one of Clauses 49 to 53 further includes: a component for selecting at least one reference device from a plurality of reference devices.

[0223] Clause 55. A network entity as described in Clause 54, wherein at least one reference device is selected based on: at least one reference device being within a threshold distance of a target base station; channel conditions between at least one reference device and the target base station indicating that at least one reference device and the target base station are within each other's site lines; a recommendation for at least one reference device being received from the target base station; or any combination thereof.

[0224] Clause 56. A network entity pursuant to any one of Clauses 45 to 48, wherein the network entity is the target base station.

[0225] Clause 57. The network entity as described in Clause 56, wherein: the component for determining the location of at least one reference device includes a component for obtaining the location of at least one reference device from at least one reference device, a UE involved in an uplink AoA positioning session with a target base station, a core network entity, a memory of the network entity, or any combination thereof, and the component for determining AoA measurements includes a component for measuring the AoA of one or more reference signals.

[0226] Clause 58. The network entity according to any one of Clauses 56 to 57 further includes: a component for transmitting configuration for one or more reference signals to at least one reference device.

[0227] Clause 59. A network entity as described in Clause 58, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0228] Clause 60. A network entity according to any one of Clauses 45 to 59, wherein the AoA measurement is a reference direction relative to the at least one antenna array.

[0229] Clause 61. The network entity as described in Clause 60, wherein the component for determining the azimuth offset comprises: a component for determining the difference between the expected AoA and the AoA measurement; and a component for determining the azimuth offset of at least one antenna array based on a reference direction and the difference between the expected AoA and the AoA measurement.

[0230] Clause 62. A network entity pursuant to any one of Clauses 45, 46 and 48 to 61, wherein at least one reference device is at least one user equipment (UE).

[0231] Clause 63. A network entity pursuant to any one of Clauses 45 to 62, wherein the location of the target base station and the location of at least one reference device are determined using a satellite positioning system (SPS) or a cellular-based positioning method.

[0232] Clause 64. A network entity according to any one of Clauses 45 to 63, wherein the azimuth offset of at least one antenna array is periodically determined.

[0233] Clause 65. A network entity pursuant to any one of Clauses 45 to 64, wherein the azimuth offset of at least one antenna array is determined based on the integrity and reliability of AoA measurements being below a threshold.

[0234] Clause 66. A network entity pursuant to any one of Clauses 45 to 65, wherein the azimuth offset of at least one antenna array is determined based on the expected difference between the AoA and the AoA measurement being greater than a threshold.

[0235] Clause 67. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: determine the location of a target base station and the location of at least one reference device; determine angle of arrival (AoA) measurements of one or more reference signals received from at least one reference device by at least one antenna array of the target base station; determine an expected AoA between at least one antenna array and at least one reference device based on the location of the target base station and the location of at least one reference device; and determine an azimuth offset of at least one antenna array based on the difference between the expected AoA and the AoA measurement.

[0236] Clause 68. The non-transitory computer-readable medium as described in Clause 67, wherein the computer-executable instructions further enable the network entity to: calibrate AoA measurements associated with at least one antenna array based on azimuth offset.

[0237] Clause 69. A non-transitory computer-readable medium pursuant to any one of Clauses 67 to 68, wherein at least one reference device is at least one base station.

[0238] Clause 70. The non-transitory computer-readable medium as described in Clause 69, wherein one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

[0239] Clause 71. A non-transitory computer-readable medium pursuant to any one of Clauses 67 to 70, wherein the network entity includes a core network entity.

[0240] Clause 72. The non-transitory computer-readable medium as described in Clause 71, wherein the computer-executable instructions for causing a network entity to determine the location of a target base station and the location of at least one reference device include computer-executable instructions for causing the network entity to obtain the location of the target base station and the location of at least one reference device from the target base station, at least one reference device, a user equipment (UE) involved in an uplink AoA positioning session with the target base station, the memory of the network entity, or any combination thereof; the computer-executable instructions for causing the network entity to determine an AoA measurement include computer-executable instructions for causing the network entity to obtain the AoA measurement from the target base station, at least one reference device, the UE, the memory of the network entity, or any combination thereof; and the computer-executable instructions for causing the network entity to determine a desired AoA include computer-executable instructions for causing the network entity to obtain the desired AoA from the target base station, at least one reference device, the UE, the memory of the network entity, or any combination thereof.

[0241] Clause 73. A non-transitory computer-readable medium pursuant to any one of Clauses 71 to 72, wherein the computer-executable instructions further cause a network entity to transmit configuration for one or more reference signals to a target base station and at least one reference device.

[0242] Clause 74. The non-transitory computer-readable medium as described in Clause 73, wherein the configuration indicates time and / or frequency resources on which at least one reference device will transmit one or more reference signals.

[0243] Clause 75. A non-transitory computer-readable medium according to any one of Clauses 73 to 74, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0244] Clause 76. A non-transitory computer-readable medium pursuant to any one of Clauses 71 to 75, wherein the computer-executable instructions further cause a network entity to: select at least one reference device from a plurality of reference devices.

[0245] Clause 77. The non-transitory computer-readable medium as described in Clause 76, wherein at least one reference device is selected based on: at least one reference device being within a threshold distance of a target base station; channel conditions between at least one reference device and the target base station indicating that at least one reference device and the target base station are within each other's site lines; a recommendation for at least one reference device being received from the target base station; or any combination thereof.

[0246] Clause 78. A non-transitory computer-readable medium pursuant to any one of Clauses 67 to 70, wherein the network entity is the target base station.

[0247] Clause 79. The non-transitory computer-readable medium as described in Clause 78, wherein computer-executable instructions causing a network entity to determine the location of at least one reference device include computer-executable instructions causing the network entity to obtain the location of at least one reference device from at least one reference device, a UE involved in an uplink AoA positioning session with a target base station, a core network entity, the network entity's memory, or any combination thereof, and computer-executable instructions causing the network entity to determine AoA measurements include computer-executable instructions causing the network entity to measure the AoA of one or more reference signals.

[0248] Clause 80. A non-transitory computer-readable medium pursuant to any one of Clauses 78 to 79, wherein the computer-executable instructions further cause a network entity to transmit configuration for one or more reference signals to at least one reference device.

[0249] Clause 81. The non-transitory computer-readable medium as described in Clause 80, wherein the configuration indicates the direction of beamforming of one or more reference signals.

[0250] Clause 82. A non-transitory computer-readable medium according to any one of Clauses 67 to 81, wherein the AoA measurement is relative to a reference direction of at least one antenna array.

[0251] Clause 83. The non-transitory computer-readable medium according to Clause 82, wherein the computer-executable instructions that, when executed, cause a network entity to determine an azimuth offset include computer-executable instructions that, when executed, cause the network entity to: determine the difference between the expected AoA and the AoA measurement; and determine the azimuth offset of at least one antenna array based on a reference direction and the difference between the expected AoA and the AoA measurement.

[0252] Clause 84. A non-transitory computer-readable medium pursuant to any one of Clauses 67, 68 and 70 to 83, wherein at least one reference device is at least one user equipment (UE).

[0253] Clause 85. A non-transitory computer-readable medium according to any one of Clauses 67 to 84, wherein the location of the target base station and the location of at least one reference device are determined using a satellite positioning system (SPS) or a cellular-based positioning method.

[0254] Clause 86. A non-transitory computer-readable medium according to any one of Clauses 67 to 85, wherein the azimuth offset of at least one antenna array is periodically determined.

[0255] Clause 87. A non-transitory computer-readable medium according to any one of Clauses 67 to 86, wherein the azimuth offset of at least one antenna array is determined based on the integrity and reliability of AoA measurements being below a threshold.

[0256] Clause 88. A non-transitory computer-readable medium according to any one of Clauses 67 to 87, wherein the azimuth offset of at least one antenna array is determined based on the expected difference between the AoA and the AoA measurement being greater than a threshold.

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

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

[0259] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, 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. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

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

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

[0262] While the foregoing disclosure illustrates illustrative aspects of this disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of this disclosure described herein do not need to be performed in any particular order. Furthermore, although elements of the invention may be described or claimed in the singular, the plural form is also contemplated unless explicitly limited to the singular.

Claims

1. A method for wireless communication performed by a network entity, comprising: Determine the location of the target base station and the locations of at least two reference devices selected from a plurality of reference devices; For each of the at least two reference devices, the angle of arrival (AoA) of one or more reference signals received from that reference device by the antenna array of the target base station is determined; For each of the at least two reference devices, the expected AoA between the antenna array and the reference device is determined based on the location of the target base station and the location of the reference device; as well as The azimuth offset of the antenna array is determined based on the difference between the expected AoA and the AoA measurement for each of the at least two reference devices; as well as The AoA measurements associated with the antenna array are calibrated based on the azimuth offset. The at least two reference devices are base stations and / or user equipment (UEs) selected from the plurality of reference devices, such that the selected at least two reference devices are clustered to one side of the antenna array facing the target base station, wherein the antenna array is one of the plurality of antenna arrays of the target base station.

2. The method according to claim 1, wherein, The at least two reference devices are base stations, and the one or more reference signals include one or more positioning reference signals (PRS), one or more channel state information reference signals (CSI-RS), or one or more sounding reference signals (SRS).

3. The method according to claim 1, wherein, The network entities include core network entities.

4. The method according to claim 3, wherein: Determining the location of the target base station and the locations of the at least two reference devices includes obtaining the location of the target base station and the locations of the at least two reference devices from the target base station, the at least two reference devices, a user equipment (UE) involved in an uplink AoA positioning session with the target base station, the memory of the network entity, or any combination thereof. Determining the AoA measurement includes obtaining the AoA measurement from the target base station, the at least two reference devices, the UE, the memory of the network entity, or any combination thereof, and Determining the expected AoA includes obtaining the expected AoA from the target base station, the at least two reference devices, the UE, the memory of the network entity, or any combination thereof.

5. The method according to claim 3, further comprising: The configuration for the one or more reference signals is sent to the target base station and the at least two reference devices.

6. The method according to claim 5, wherein, The configuration indicates that the at least two reference devices will use time and / or frequency resources to transmit the one or more reference signals thereon.

7. The method according to claim 5, wherein, The configuration indicates the direction of beamforming for the one or more reference signals.

8. The method according to claim 1, wherein, The at least two reference devices are also selected based on the following: The at least two reference devices are within a threshold distance of the target base station. The channel conditions between each of the at least two reference devices and the target base station indicate that each of the at least two reference devices and the target base station are within each other's line of sight. Recommendations for the at least two reference devices are received from the target base station, or Any combination thereof.

9. The method according to claim 1, wherein, The network entity is the target base station.

10. The method according to claim 9, wherein: Determining the locations of the at least two reference devices includes obtaining the locations of the at least two reference devices from the at least two reference devices, a UE involved in an uplink AoA positioning session with the target base station, a core network entity, the memory of the network entity, or any combination thereof. Determining the AoA measurement includes measuring the AoA of the one or more reference signals.

11. The method of claim 9, further comprising: The configuration for the one or more reference signals is sent to the at least two reference devices.

12. The method according to claim 11, wherein, The configuration indicates the direction of beamforming for the one or more reference signals.

13. The method according to claim 1, wherein, The AoA measurement is relative to a reference direction of the antenna array.

14. The method according to claim 13, wherein, Determining the azimuth offset includes: Determine the difference between the expected AoA and the measured AoA; and The azimuth offset of the antenna array is determined based on the reference direction and the difference between the expected AoA and the measured AoA.

15. The method according to claim 1, wherein, The at least two reference devices are user equipment (UEs).

16. The method according to claim 1, wherein, The location of the target base station and the location of the at least two reference devices are determined using a satellite positioning system (SPS) or a cellular-based positioning method.

17. The method according to claim 1, wherein, The azimuth offset of the antenna array is determined periodically.

18. The method according to claim 1, wherein, The azimuth offset of the antenna array is determined based on the integrity and reliability of the AoA measurement being below a threshold.

19. The method according to claim 1, wherein, The azimuth offset of the antenna array is determined based on the difference between the expected AoA and the measured AoA being greater than a threshold.

20. A network entity, comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: Determine the location of the target base station and the locations of at least two reference devices selected from a plurality of reference devices; For each of the at least two reference devices, the angle of arrival (AoA) of one or more reference signals received from that reference device by the antenna array of the target base station is determined; For each of the at least two reference devices, the expected AoA between the antenna array and the reference device is determined based on the location of the target base station and the location of the reference device; as well as The azimuth offset of the antenna array is determined based on the difference between the expected AoA and the AoA measurement for each of the at least two reference devices; as well as The AoA measurements associated with the antenna array are calibrated based on the azimuth offset. The at least two reference devices are base stations and / or user equipment (UEs) selected from the plurality of reference devices, such that the selected at least two reference devices are clustered to one side of the antenna array facing the target base station, wherein the antenna array is one of the plurality of antenna arrays of the target base station.

21. The network entity according to claim 20, wherein, The at least one processor is further configured to: The location of the target base station and the location of the at least two reference devices are obtained from the target base station, the at least two reference devices, the user equipment (UE) involved in the uplink AoA positioning session with the target base station, the memory of the network entity, or any combination thereof. The AoA measurement is obtained from the target base station, the at least two reference devices, the UE, the memory of the network entity, or any combination thereof. The expected AoA is obtained from the target base station, the at least two reference devices, the UE, the memory of the network entity, or any combination thereof.

22. The network entity according to claim 20, wherein, The at least one processor is further configured to: The configuration for the one or more reference signals is transmitted to the target base station and the at least two reference devices via the at least one transceiver.

23. The network entity according to claim 22, wherein, The configuration indicates that the at least two reference devices will use time and / or frequency resources to transmit the one or more reference signals thereon.

24. The network entity according to claim 20, wherein, The at least two reference devices are also selected based on the following: The at least two reference devices are within a threshold distance of the target base station. The channel conditions between each of the at least two reference devices and the target base station indicate that each of the at least two reference devices and the target base station are within each other's line of sight. Recommendations for the at least two reference devices are received from the target base station, or Any combination thereof.

25. The network entity according to claim 20, wherein, The network entity is the target base station.

26. The network entity according to claim 25, wherein, The at least one processor is further configured to: The locations of the at least two reference devices are obtained from the at least two reference devices, the UE involved in the uplink AoA positioning session with the target base station, the core network entity, the memory of the network entity, or any combination thereof. Measure the AoA of the one or more reference signals.

27. The network entity according to claim 25, wherein, The at least one processor is further configured to: The configuration for the one or more reference signals is transmitted to the at least two reference devices via the at least one transceiver.

28. The network entity according to claim 20, wherein, The AoA measurement is relative to a reference direction of the antenna array.

29. The network entity according to claim 28, wherein, The at least one processor configured to determine the azimuth offset includes the at least one processor configured to: Determine the difference between the expected AoA and the measured AoA; and The azimuth offset of the antenna array is determined based on the reference direction and the difference between the expected AoA and the measured AoA.

30. The network entity according to claim 20, wherein, The azimuth offset of the antenna array is determined based on the difference between the expected AoA and the measured AoA being greater than a threshold.

31. A network entity, comprising: Components for determining the location of a target base station and the locations of at least two reference devices selected from a plurality of reference devices; A component for determining, for each of the at least two reference devices, the angle of arrival (AoA) of one or more reference signals received from the antenna array of the target base station from that reference device; Components for determining the expected AoA between the antenna array and the reference device based on the location of the target base station and the location of the reference device for each of the at least two reference devices; as well as Components for determining the azimuth offset of the antenna array based on the difference between the expected AoA and the AoA measurement for each of the at least two reference devices; as well as Components for calibrating AoA measurements associated with the antenna array based on the azimuth offset. The at least two reference devices are base stations and / or user equipment (UEs) selected from the plurality of reference devices, such that the selected at least two reference devices are clustered to one side of the antenna array facing the target base station, wherein the antenna array is one of the plurality of antenna arrays of the target base station.

32. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a network entity, cause the network entity to: Determine the location of the target base station and the locations of at least two reference devices selected from a plurality of reference devices; For each of the at least two reference devices, the angle of arrival (AoA) of one or more reference signals received from that reference device by the antenna array of the target base station is determined; For each of the at least two reference devices, the expected AoA between the antenna array and the reference device is determined based on the location of the target base station and the location of the reference device; as well as The azimuth offset of the antenna array is determined based on the difference between the expected AoA and the AoA measurement for each of the at least two reference devices; as well as The AoA measurements associated with the antenna array are calibrated based on the azimuth offset. The at least two reference devices are base stations and / or user equipment (UEs) selected from the plurality of reference devices, such that the selected at least two reference devices are clustered to one side of the antenna array facing the target base station, wherein the antenna array is one of the plurality of antenna arrays of the target base station.

33. A program product comprising instructions that, when executed by a network entity, cause the network entity to perform the method according to any one of claims 1-19.

Images