Deriving angle information in wireless network covering near field area

Abstract

Techniques for wireless sensing are disclosed. In an aspect, a transmitter device transmits one or more reference signals on each of a plurality of transmit beams to at least one receiver device, where the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value for a corresponding one of the plurality of transmit beams.

Description

TECHNICAL FIELD

[0001] Aspects of the present disclosure generally relate to wireless technology. BACKGROUND

[0002] Wireless communication systems have developed through several generations, including first-generation analog wireless telephones, second-generation (2G) digital wireless telephones, and third-generation (3G) high speed data / Internet-capable wireless telephones. The fourth generation (4G) and fifth generation (5G) wireless systems are also becoming more prevalent. These wireless communications systems operate in accordance with various standards, including standards promulgated by the Third Generation Partnership Project (3GPP) and the Third Generation Partnership Project 2 (3GPP2).

[0003] The fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage than previous standards. According to the Next Generation Mobile Networks Alliance, 5G technology should provide bitrates on the order of 100 megabits per second (Mbps) to 1 gigabit per second (Gbps), with reduced latency and increased efficiency, compared to previous standards. To achieve these goals, 5G systems should be deployed in frequencies from 6 GHz to 100 GHz, but also in lower frequencies, reusing the infrastructure of existing systems, and using new spectrum opportunities (e.g., the C-band, 3.5 GHz band, and 900 MHz band). SUMMARY

[0004] The following presents a simplified summary related to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects disclosed herein in a simplified form to precede the detailed description presented below.

[0005] In an aspect, a method of wireless sensing performed by a transmitter device includes transmitting one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of codepoints of a near-field codebook, and wherein each codepoint of the plurality of codepoints is parameterized with an angle value and a ranging value of a corresponding transmit beam of the plurality of transmit beams.

[0006] In one aspect, a method of wireless sensing performed by a receiver device includes: obtaining multiple signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the multiple signal strength measurements are obtained using corresponding multiple receive beams of the receiver device, wherein the multiple receive beams correspond to multiple channel steering vectors, and wherein each of the multiple channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the multiple receive beams; determining the angle of arrival (AoA) of the one or more reference signals as the angle value of the channel steering vector corresponding to the receive beam among the multiple receive beams that results in the highest signal strength measurement of the one or more reference signals; and determining the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0007] In one aspect, a transmitter device includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to transmit one or more reference signals to at least one receiver device via the one or more transceivers on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams.

[0008] In one aspect, a receiver device includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam in the plurality of receive beams; determine the angle of arrival (AoA) of the one or more reference signals as the angle value of the channel steering vector corresponding to the receive beam in the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and determine the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0009] In one aspect, a transmitter device includes components for transmitting one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams.

[0010] In one aspect, a receiver device includes: components for obtaining a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the plurality of receive beams; components for determining the angle of arrival (AoA) of the one or more reference signals as an angle value of a channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and components for determining the distance to the transmitter device as a ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0011] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a transmitter device, cause the transmitter device to: transmit one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points in a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams.

[0012] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a receiver device, cause the receiver device to: obtain multiple signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the multiple signal strength measurements are obtained using corresponding multiple receive beams of the receiver device, wherein the multiple receive beams correspond to multiple channel steering vectors, and wherein each of the multiple channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the multiple receive beams; determine the angle of arrival (AoA) of the one or more reference signals as the angle value of the channel steering vector corresponding to the receive beam among the multiple receive beams that results in the highest signal strength measurement of the one or more reference signals; and determine the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0013] 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

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

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

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

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

[0018] Figure 4 Examples of various positioning methods supported in new radios (NR) according to various aspects of this disclosure are illustrated.

[0019] Figure 5 This is a diagram illustrating communication between an example base station and an example UE according to various aspects of this disclosure.

[0020] Figure 6A and Figure 6B Different types of radars according to various aspects of this disclosure are illustrated.

[0021] Figure 7 This is a diagram illustrating various aspects of a single receiving antenna relative to a transmitter according to various aspects of this disclosure.

[0022] Figure 8 These are illustrations of various aspects of an array antenna according to various aspects of this disclosure.

[0023] Figure 9 This is a diagram illustrating an example receiver architecture for deriving Angle of Arrival (AoA) information according to various aspects of this disclosure.

[0024] Figure 10 This is an illustration of an example of a near-field codebook according to various aspects of this disclosure.

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

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

[0027] Various aspects are involved in wireless sensing as a whole. Some aspects are more specifically involved in determining the angle of origin (AoD) and / or angle of arrival (AoA) information. In some examples, distance is added as a dimension of beam scanning for near-field users. For example, regarding AoD determination, a transmitter device (e.g., a base station or user equipment (UE)) may transmit one or more reference signals to at least one receiver device on each of a plurality of transmit beams. The plurality of transmit beams may correspond to a plurality of code points in a near-field codebook. Each of the plurality of code points may be parameterized using the angle value and ranging value of the corresponding transmit beam in the plurality of transmit beams.

[0028] Regarding AoA determination, a receiver device (e.g., a base station or UE) can obtain multiple signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam. These multiple signal strength measurements can be obtained using corresponding multiple receive beams of the receiver device. The multiple receive beams may correspond to multiple channel steering vectors, and each of the multiple channel steering vectors can be parameterized using the angle and ranging values ​​of the corresponding receive beams. The receiver device can also determine the AoA of the one or more reference signals as the angle value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals. The receiver device can also determine the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0029] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by providing a near-field codebook, the described techniques can be used to derive angle information (AoA / AoD) in a network covering both the near-field and far-field service areas.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] 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.

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

[0059] On one hand, the sidelink 160 can operate via a wireless communication medium of interest that can be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. "Medium" can include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. On another hand, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently expanded their operation to unlicensed frequency bands such as those used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include various variants of CDMA, TDMA, FDMA, orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and so on.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 280. The CU 280 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 280 can be implemented to communicate with the DU 285 for network control and signaling, as needed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] NR supports various cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and positioning methods based on both downlink and uplink. 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. Figure 4Examples of various positioning methods according to aspects of this disclosure are illustrated. In the OTDOA or DL-TDOA positioning process illustrated in scenario 410, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurement) and reports these differences 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 (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0111] For the DL-AoD positioning illustrated in scenario 420, the positioning entity uses measurement reports from the UE regarding the received signal strength measurements of multiple downlink transmitted beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's position based on the determined angle and the known location of the transmitting base station.

[0112] 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 to multiple base stations. Specifically, the UE transmits one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the received-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use the TDOA to estimate the UE's location.

[0113] 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 station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0114] 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" and "Multi-RTT"). During RTT, a first entity (e.g., a base station or a UE) sends a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or a base station), which then sends a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the time of transmission of the transmitted RTT-related signal. This time difference is called the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities can then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can transmit its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For the multi-RTT positioning illustrated in scenario 430, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined based on the distance to the second entities and the known location of the second entities (e.g., using polygonal measurements). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy, as illustrated in scenario 440.

[0115] 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), identifiers of detected neighboring base stations, estimated timing, and signal strength. The UE's location is then estimated based on this information and the known locations of the base stations.

[0116] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may 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., including the number of consecutive time slots of the PRS, the periodicity of consecutive time slots of the PRS, silence sequences, frequency hopping sequences, reference signal identifier, 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 without using auxiliary data.

[0117] In the case of OTDOA or DL-TDOA positioning procedures, auxiliary data may also 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 of the resources used for positioning measurements is 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.

[0118] Location estimates can be referred to by other names, such as location estimation, location, positioning, fixed location, etc. Location estimates can be geodesic and include coordinates (e.g., latitude, longitude, and possible elevation), or they can be municipal and include street addresses, postal addresses, or some other verbal description of the location. Location estimates can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimates can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to include with a specified or default confidence level).

[0119] Figure 5 This is a diagram 500 illustrating communication between a base station (BS) 502 (which may correspond to any of the base stations described herein) and a UE 504 (which may correspond to any of the UEs described herein). Reference Figure 5Base station 502 may transmit beamforming signals to UE 504 on one or more transmit beams 512a, 512b, 512c, 512d, 512e, 512f, 512g, 512h (collectively referred to as beams 512), each of which has a beam identifier that can be used by UE 504 to identify the respective beam. When base station 502 performs beamforming toward UE 504 using a single antenna array (e.g., a single TRP / cell), base station 502 may perform a “beam scan” by transmitting a first beam 512a, then beam 512b, and so on, until finally transmitting beam 512h. Alternatively, base station 502 may transmit beams 512 in a pattern, such as beam 512a, then beam 512h, then beam 512b, then beam 512g, and so on. In the case where base station 502 uses multiple antenna arrays (e.g., multiple TRPs / cells) to perform beamforming toward UE 504, each antenna array may perform beam scanning of a subset of beams 512. Alternatively, each beam in beams 512 may correspond to a single antenna or antenna array.

[0120] Figure 5 Further examples illustrate the paths 522c, 522d, 522e, 522f, and 522g followed by beamforming signals transmitted on beams 512c, 512d, 512e, 512f, and 512g, respectively. Each path 522c, 522d, 522e, 522f, and 522g may correspond to a single "multipath," or may consist of multiple "multipaths" ("multipath" clusters) due to the propagation characteristics of radio frequency (RF) signals through the environment. It should be noted that although only paths 522c-522g for beams 512c-512g are shown for simplicity, signals transmitted on each beam in beam 512 will follow a certain path. In the example shown, paths 522c, 522d, 522e, and 522f are straight lines, while path 522g reflects from an obstacle 520 (e.g., a building, vehicle, terrain feature, etc.).

[0121] UE 504 can receive beamforming signals from base station 502 on one or more receive beams 514a, 514b, 514c, 514d (collectively referred to as beams 514). Note that, for simplicity... Figure 5 The illustrated beams represent either transmit or receive beams, depending on which of the base station 502 and UE 504 is transmitting and which is receiving. Therefore, UE 504 may also transmit beamforming signals to base station 502 on one or more of the beams 514, and base station 502 may receive beamforming signals from UE 504 on one or more of the beams 512.

[0122] On one hand, base station 502 and UE 504 can perform beam training to align their transmit and receive beams. For example, depending on environmental conditions and other factors, base station 502 and UE 504 can determine optimal transmit and receive beams as 512d and 514b, or as 512e and 514c, respectively. The direction of the optimal transmit beam of base station 502 may be the same as or different from the direction of the optimal receive beam, and similarly, the direction of the optimal receive beam of UE 504 may 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 angle of arrival (DL-AoD) or uplink angle of arrival (UL-AoA) positioning procedures.

[0123] To perform the DL-AoD positioning process, base station 502 may transmit reference signals (e.g., PRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UE 504 on one or more beams in beam 512, each beam having a different transmission angle. The different transmission angles of the beams will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) at UE 504. Specifically, the received signal strength will be lower for transmission beams 512 that are farther from the line-of-sight (LOS) path 510 between base station 502 and UE 504 than for transmission beams 512 that are closer to the LOS path 510.

[0124] exist Figure 5 In the example, if base station 502 transmits reference signals to UE 504 on beams 512c, 512d, 512e, 512f, and 512g, then transmit beam 512e is optimally aligned with LOS path 510, while transmit beams 512c, 512d, 512f, and 512g are not optimally aligned with that LOS path. Therefore, beam 512e is likely to have a higher received signal strength at UE 504 than beams 512c, 512d, 512f, and 512g. It should be noted that reference signals transmitted on some beams (e.g., beams 512c and / or 512f) may not reach UE 504, or the energy reaching UE 504 from these beams may be too low to be detected or at least negligible.

[0125] UE 504 may report to base station 502 the received signal strength of each measured transmit beam 512c-512g, and optionally, the associated measurement quality, or alternatively, the identifier of the transmit beam with the highest received signal strength (in Figure 5In the example, beam 512e is used. Alternatively or additionally, if UE 504 also participates in round-trip time (RTT) or time difference of arrival (TDOA) positioning sessions with at least one base station 502 or multiple base stations 502, UE 504 may report received transmit (Rx-Tx) time difference or reference signal time difference (RSTD) measurements (and optionally associated measurement quality) to the serving base station 502 or other positioning entity. In any case, the positioning entity (e.g., base station 502, location server, third-party client, UE 504, etc.) may estimate the angle from base station 502 to UE 504 as the AoD of the transmit beam (here, transmit beam 512e) with the highest received signal strength at UE 504.

[0126] In one aspect of DL-AoD-based positioning, when only one involved base station 502 exists, base station 502 and UE 504 can perform a round-trip time (RTT) procedure to determine the distance between base station 502 and UE 504. Therefore, the positioning entity can determine both the direction to UE 504 (using DL-AoD positioning) and the distance to UE 504 (using RTT positioning) to estimate the location of UE 504. It should be noted that the AoD with the highest received signal strength is not necessarily along the LOS path 510, such as... Figure 5 As shown. However, for the purposes of DL-AoD-based positioning, this is assumed.

[0127] In another aspect of DL-AoD-based positioning, in the presence of multiple involved base stations 502, each involved base station 502 can report the determined AoD or RSRP measurement from the corresponding base station 502 to the serving base station 502. The serving base station 502 can then report the AoD or RSRP measurements from the other involved base stations 502 to the positioning entity (e.g., the UE 504 for UE-based positioning or a location server for UE-assisted positioning). Using this information, along with knowledge of the geographic locations of the base stations 502, the positioning entity can estimate the location of the UE 504 as the intersection of the determined AoDs. For a two-dimensional (2D) positioning solution, at least two involved base stations 502 should be present; however, as will be understood, the more base stations 502 involved in the positioning process, the more accurate the estimated location of the UE 504 will be.

[0128] To perform the UL-AoA positioning procedure, UE 504 transmits uplink reference signals (e.g., UL-PRS, SRS, DMRS, etc.) to base station 502 on one or more uplink transmit beams 514. Base station 502 receives the uplink reference signals on one or more uplink receive beams 512. Base station 502 determines the angle of the optimal receive beam 512 for receiving one or more reference signals from UE 504 as the AoA from UE 504 to itself. Specifically, each receive beam in the receive beams 512 will result in a different received signal strength (e.g., RSRP, RSRQ, SINR, etc.) for one or more reference signals at base station 502. Furthermore, the channel impulse response of one or more reference signals will be smaller for receive beams 512 that are further away from the actual LOS path 510 between base station 502 and UE 504 than for receive beams 512 that are closer to the LOS path 510. Similarly, for the receive beam 512 further away from the LOS path 510, the received signal strength will be lower than that of the receive beam 512 closer to the LOS path 510. Therefore, base station 502 identifies the receive beam 512 that results in the highest received signal strength and, optionally, the strongest channel impulse response, and estimates its AoA from its angle to UE 504. It should be noted that, as with DL-AoD-based positioning, the AoA of the receive beam 512 that results in the highest received signal strength (and, in the case of measurement, the strongest channel impulse response) is not necessarily along the LOS path 510. However, in FR2, this can be assumed for UL-AoA-based positioning purposes.

[0129] It should be noted that although UE 504 is illustrated as capable of beamforming, this is not necessary for DL-AoD and UL-AoA positioning procedures. Instead, UE 504 can perform both reception and transmission on an omnidirectional antenna.

[0130] 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). By knowing the distance to base station 502 (based on RTT or timing advance), the angle between base station 502 and UE 504 (based on the UL-AoA of the optimal receive beam 512), and the known geographic location of base station 502, UE 504 can estimate its location.

[0131] 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 the receive beam 512 that results in the highest received signal strength (and optionally the strongest channel impulse response) of the reference signal received from UE 504, or all received signal strengths and channel impulse responses for all receive beams 512 (this allows the positioning entity to determine the optimal receive beam 512). Base station 502 may additionally report the Rx-Tx time difference to UE 504. The positioning entity can then estimate the location of UE 504 based on the distance from UE 504 to base station 502, the AoA of the identified receive beam 512, and the known geographic location of base station 502.

[0132] Wireless communication signals transmitted between the UE and the base station (e.g., radio frequency (RF) signals configured to carry orthogonal frequency division multiplexing (OFDM) symbols according to wireless communication standards such as LTE, NR, etc.) can be used for environmental sensing (also known as "RF sensing" or "radar"). Environmental sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, enabling contactless / device-free interaction with devices / systems, etc. Wireless communication signals can be cellular communication signals, such as LTE or NR signals, WLAN signals such as Wi-Fi signals, etc. As a specific example, wireless communication signals can be OFDM waveforms as utilized in LTE and NR. High-frequency communication signals, such as millimeter-wave (mmW) RF signals, are particularly advantageous for use as radar signals because higher frequencies provide at least more accurate ranging (distance) detection.

[0133] Potential use cases for RF sensing include: health monitoring use cases, such as heart rate detection and respiratory rate monitoring; gesture recognition use cases, such as human activity recognition, keystroke detection, and sign language recognition; context information acquisition use cases, such as location detection / tracking, direction finding, and distance estimation; and automotive radar use cases, such as intelligent cruise control and collision avoidance.

[0134] There are different types of sensing, including single-station sensing (also known as "active sensing") and dual-station sensing (also known as "passive sensing"). Figure 6A and Figure 6B These different types of sensing are illustrated. Specifically, Figure 6A This is illustration 600 illustrating a single-station sensing scenario, and Figure 6B This is illustration 630, illustrating a dual-station sensing scenario. Figure 6AIn this configuration, the transmitter (Tx) and receiver (Rx) are co-located in the same sensing device 604 (e.g., a UE). The sensing device 604 transmits one or more RF sensing signals 634 (e.g., uplink or sidelink location reference signals (PRS) in the case of a UE), and some of the RF sensing signals 634 are reflected from a target object 606. The sensing device 604 can measure various properties (e.g., ToA, AoA, phase shift, etc.) of the reflection 636 of the RF sensing signals 634 to determine characteristics of the target object 606 (e.g., size, shape, speed, motion state, etc.).

[0135] exist Figure 6B In this architecture, the transmitter (Tx) and receiver (Rx) are not co-located; that is, they are separate devices (e.g., the UE and the base station). It should be noted that although... Figure 6B The example illustrates the use of a downlink RF signal as the RF sensing signal 632, but uplink or sidelink RF signals can also be used as the RF sensing signal 632. In the downlink scenario, as shown in the figure, the transmitter is the base station and the receiver is the UE, while in the uplink scenario, the transmitter is the UE and the receiver is the base station.

[0136] For more detailed information, please refer to [link / reference]. Figure 6B Transmitter device 602 sends RF sensing signals 632 and 634 (e.g., PRS) to sensing device 604, but some of the RF sensing signal 634 is reflected from target object 606. Sensing device 604 (also referred to as "sensing device") can measure the ToA of the RF sensing signal 632 received directly from the transmitter device and the ToA of the reflection 636 of the RF sensing signal 634 reflected from target object 606.

[0137] More specifically, as described above, a transmitter device (e.g., a base station) may transmit a single RF signal or multiple RF signals to a sensing device (e.g., a UE). 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. Each path may be associated with a cluster of one or more channel taps. Generally, the time when the receiver detects the first channel tap cluster is considered to be the ToA of the RF signal on the LOS path (i.e., the shortest path between the transmitter and receiver). Subsequent channel tap clusters are considered to have been reflected from the object between the transmitter and receiver and therefore follow a non-LOS (NLOS) path between the transmitter and receiver.

[0138] Therefore, return to the reference. Figure 6BRF sensing signal 632 follows a LOS path between transmitter device 602 and sensing device 604, while RF sensing signal 634 follows an NLOS path between transmitter device 602 and sensing device 604 due to reflection from target object 606. Transmitter device 602 may have transmitted multiple RF sensing signals 632 and 634, some of which follow the LOS path while others follow the NLOS path. Alternatively, transmitter device 602 may have transmitted a single RF sensing signal in a sufficiently wide beam, a portion of which follows the LOS path (RF sensing signal 632) and a portion of which follows the NLOS path (RF sensing signal 634).

[0139] Based on the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, sensing device 604 can determine the distance to a target object. For example, sensing device 604 can calculate the distance to the target object as the difference between the ToA of the LOS path and the ToA of the NLOS path multiplied by the speed of light. Furthermore, if sensing device 604 is capable of receiving beamforming, it can determine the approximate direction to the target object as the direction (angle) of the receiving beam that receives the RF sensing signal following the NLOS path. That is, sensing device 604 can determine the direction to the target object as the AoA of the RF sensing signal, which is the angle of the receiving beam used to receive the RF sensing signal. Sensing device 604 can then optionally report this information to transmitter device 602, its serving base station, application server associated with the core network, external client, third-party application, or some other sensing entity. Alternatively, the sensing device 604 may report the ToA measurement to the transmitter device 602 or other sensing entity (e.g., if the sensing device 604 itself does not have the processing capability to perform the calculation), and the transmitter device 602 may determine the distance to the target object 606 and optionally determine the direction to the target object.

[0140] It should be noted that if the RF sensing signal is an uplink RF signal sent by the UE to the base station, the base station will perform object detection based on the uplink RF signal, just as the UE does based on the downlink RF signal.

[0141] Similar to conventional radar, radar signals based on wireless communication can be used to estimate the range (distance), velocity (Doppler), and angle (AoA) of a target. However, performance (e.g., resolution, and the maximum values ​​of range, velocity, and angle) can depend on the design of the reference signal.

[0142] Joint communication and sensing technologies that combine wireless communication and radar sensing have been introduced. (See above, for example, reference...) Figure 6A and Figure 6B As described, the radar system transmits detection signals to a non-cooperative target (e.g., target object 606) and infers useful information from the target echo. Conversely, the communication system exchanges information between two or more cooperative transceivers (e.g., UE and TRP). Joint Communication and Sensing (JCS) is an integrated system capable of simultaneously performing both wireless communication and long-range radar sensing, thus providing a cost-effective deployment for both radar and communication systems. In a JCS system, time, frequency, and / or spatial RF resources are allocated to support both objectives: communication and sensing.

[0143] One of the main trends in wireless networks is equipping base stations with a greater number of antenna elements to achieve improved beamforming gain and higher multi-user MIMO orders. However, with large antenna arrays on the transmitter and / or receiver sides, wireless networks will need to cover a larger area of ​​the near-field channel. Therefore, this disclosure provides techniques for enabling base stations, UEs, and sensing servers in a JCS system to collaborate in deriving angular information (e.g., AoA and / or AoD) in a network covering both the near-field and far-field service areas.

[0144] The near field and far field are regions of electromagnetic field surrounding an object, such as a transmitting antenna. The near field typically refers to the region near the antenna conductor or inside any polarizable medium surrounding the antenna, where the generation and emission of electromagnetic waves may be disturbed, while field lines remain electrically attached to the antenna. Conversely, the far field is the region where the field has stabilized into “normal” electromagnetic radiation.

[0145] Figure 7 Figure 700 illustrates various aspects of a single receiving antenna relative to a transmitter according to various aspects of this disclosure. For example... Figure 7 As shown, a single receiving antenna has a diagonal dimension D and is located at a distance z from the transmitter. The electric field at a distance z from the point source (e.g., the transmitter) can be expressed as: Referring to the above equation, the near-field response is the maximum distance (z), where the last two terms can be neglected when studying the electric field. For a single-point source, z = lambda(λ) (the wavelength of the received RF signal). For a large antenna with a maximum length D, Only the propagation distance beyond the reactive near field is considered.

[0146] Reference far-field distance, by taking into account the phase difference between the center and corner of a single antenna panel (e.g., The Fraunhofer distance is used to determine the far-field distance. The Fraunhofer distance represents the transition between the near-field and far-field distances and is expressed as: It should be noted that when and At that time, .

[0147] An additional lower limit for the far-field region is that z should be greater than or equal to 1.2D, which means that the angular difference between the center and edge of a single antenna panel is at most 1.2D. Fresnel regions (areas) are represented as (Note that amplitude changes can be ignored, but phase changes cannot.) Only in Fresnel regions only exist under certain conditions.

[0148] The near-field characteristics of a single antenna have already been described. The following are the various near-field characteristics of an array antenna. For a Fraunhofer array of a planar square array with N identical antennas, the distance is... (integers), maximum length is the diagonal To ensure that the curvature of the spherical surface causes a negligible phase change, the following equation must be satisfied: Fraunhofer Array Distance It's not that they're unrelated, but rather that they characterize the type of receiver processing required and the resulting depth of focus (DF). If Therefore, the plane wave approximation used to determine the array response vector is based solely on the incident angle. For When calculating the weights of the matched filter, the curvature of the sphere needs to be considered.

[0149] Figure 8 Figure 800 illustrates various aspects of an array antenna according to various aspects of this disclosure. Figure 8 In the example, the base station (BS)'s array antennas (represented as a series of circles along the y-axis, where circles represent antenna elements) are receiving uplink transmissions from the UE. Figure 8 As shown, some uplink transmissions follow the LOS path to the array antenna, while other uplink transmissions are reflected / scattered from the object and follow the NLOS path to the array antenna.

[0150] The far-field channel model can be expressed as: The channel can be represented by a sparse angular domain channel with a discrete Fourier transform (DFT) matrix: in It is an N×N unitary matrix, and ,in .

[0151] Referring to the near-field channel model, the channel can be represented by a weighted sum of finite near-field steering vectors. This means that it depends not only on the channel angle, but also on the channel distance: The table below illustrates example Fraunhofer distances (in meters (m)) for different numbers of antenna elements (N) at different frequencies (f).

[0152] Table 1 Now, referring to the AoA / AoD estimation at the far-field distance, the far-field channel can be represented by a sparse angle-domain channel with a DFT matrix, as shown above. The far-field AoD estimation is based on a codebook constructed from the DFT matrix. More specifically, the transmitter (e.g., a base station or UE) applies a transmission beam scan to the codebook constructed from the DFT matrix (possibly utilizing oversampling to obtain better AoD resolution and leveraging Kronecker operations to determine two-dimensional angle information). The transmitter can then acquire AoD information based on a beam measurement report provided by the receiver. The measurement report may include the beam index and the corresponding RSRP.

[0153] For far-field AoA estimation, assuming the use of DFT-type steering vectors, the receiver (e.g., a base station or UE) can estimate AoA information by post-processing the received signal derived under the assumption that the channel can be represented by a DFT-type steering vector. For example, the receiver can use spatial power spectrum or multiple signal classification (MUSIC) algorithms to estimate AoA information.

[0154] Figure 9 This is a diagram 900 illustrating an example receiver architecture for deriving AoA information according to various aspects of this disclosure. Figure 9 In this context, the weight unit is ,and .

[0155] Currently, codebooks used for far-field AoD estimation can only determine the angle. However, for near-field AoD estimation, knowing the distance between the transmitter and receiver is also beneficial. Therefore, this disclosure provides a technique for AoD estimation in the near field.

[0156] To enable a transmitter (e.g., a base station or UE) to estimate the Area of ​​Distance (AoD) of a target in the near-field region, the transmitter can apply beam scanning to a codebook, where each code point (beam) is parameterized by its angle and distance from the transmitter. This codebook used for near-field AoD estimation will differ from the codebook used for far-field estimation. For example, in the far-field codebook, each beam is associated with each AoD direction, meaning that each beam vector can be represented as shown above: However, for the near-field codebook, each beam is associated with the AoD direction and the distance between the transmitter and receiver, meaning that each beam vector can be represented as: Therefore, if the base station or UE obtains the optimal near-field beam index, it can be converted into AoD direction and ranging information.

[0157] Figure 10 Figure 1000 illustrates an example of a near-field codebook according to various aspects of this disclosure. Figure 10 In the example, the near-field codebook consists of many near-field steering vectors Composition, in which distance and angle It is sampled from the entire angle-distance domain.

[0158] On one hand, the sensing server (e.g., location server 230, LMF 270) can indicate to the transmitter which codebook should be used for AoD estimation between the codebook used for the near field and the codebook used for the far field.

[0159] On the receiver side, the receiver measures the signal strength (e.g., RSRP) of each detected transmitted beam and reports the beam index and corresponding signal strength to the transmitter (or location / sensing server). The transmitter (or location / sensing server) determines the AoD information based on this beam measurement report, as referenced above. Figure 5 As described.

[0160] Figure 11 An example method 1100 for wireless sensing according to various aspects of this disclosure is illustrated. In one aspect, method 1100 may be performed by a transmitter device (e.g., either a UE or a base station as described herein).

[0161] At 1110, the transmitter device transmits one or more reference signals (e.g., PRS or SRS) to at least one receiver device (e.g., any other UE or base station described herein) on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points in a near-field codebook, and wherein each of the plurality of code points is parameterized using an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams. In one aspect, when the transmitter device is a UE, operation 1110 may be performed by one or more WWAN transceivers 310, one or more short-range transceivers 320, one or more processors 342, a memory 340, and / or a positioning component 348, any or all of these components may be considered as parts for performing the operation. On the one hand, when the transmitter device is a base station, operation 1110 can be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386 and / or positioning components 388, any or all of these components can be considered as parts for performing the operation.

[0162] On one hand, the multiple code points can be multiple steering vectors for the multiple transmit beams (e.g., ,like Figure 10 (As shown).

[0163] On the one hand, the angle values ​​corresponding to these multiple code points ( ) and distance measurement value ( It can be sampled from the entire angle-distance domain, as referenced above. Figure 10 As described.

[0164] In one aspect, method 1100 may further include (not shown) receiving at least one measurement report from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements (e.g., RSRP measurements) associated with the one or more beam indices. In this case, method 1100 may further include (not shown) determining at least one AoD between the transmitter device and each of the at least one receiver device based on the at least one measurement report. Method 1100 may further include (not shown) reporting the at least one AoD to a sensing server (e.g., location server 230, LMF 270).

[0165] This disclosure also provides techniques for AoA estimation in the near-field region. In this case, the receiver (e.g., UE or base station) applies post-processing derived under the assumption that the channel steering vector can be parameterized by the distance and angle from the target. The post-processing algorithm for near-field AoA estimation differs from that for far-field. For example, the near-field algorithm applies a joint estimate of parameters related to distance and angle, rather than simply applying the angle.

[0166] On one hand, the sensing server can indicate to the receiver which post-processing algorithm should be used for AoA estimation, i.e., the near-field algorithm or the far-field algorithm.

[0167] For base stations or UEs that support near-field AoD sensing, additional implementation or computational complexity may be required. For example, for near-field AoD estimation, it may be necessary to additionally implement a codebook specified for the near field in the transmitter device.

[0168] Therefore, return to the reference. Figure 11 Method 1100 may further include (not shown) receiving from a sensing server (e.g., location server 230, LMF 270) an indication to transmit the one or more reference signals on each of the plurality of transmit beams based on the near-field codebook. It should be noted that, prior to any actual sensing operation, during the deployment phase, the near-field (and far-field) codebooks may be known or specified between the sensing server and the transmitter device. For example, when the transmitter device is first attached to the network or enters a new tracking area, the sensing server may (pre-)configure the near-field (and far-field) codebooks to the transmitter device. Therefore, the sensing server may not provide the codebooks to the transmitter device in real time or at the time of the expected sensing operation. However, the sensing server can provide an indication of which codebook (near-field or far-field) is used for a given sensing procedure.

[0169] Figure 12 An example method 1200 for wireless sensing according to various aspects of this disclosure is illustrated. In one aspect, method 1200 may be performed by a receiver device (e.g., either a UE or a base station as described herein).

[0170] At 1210, the receiver device obtains multiple signal strength measurements (e.g., RSRP measurements) of one or more reference signals (e.g., PRS or SRS) transmitted by the transmitter device (e.g., the UE and any other UE and base station described herein) on a first transmit beam, wherein the multiple signal strength measurements are obtained using corresponding multiple receive beams of the receiver device, wherein the multiple receive beams correspond to multiple channel steering vectors (e.g., ... ,like Figure 10 As shown), and each of the plurality of channel steering vectors is the angle value of the corresponding receiving beam in the plurality of receiving beams (as shown). ) and distance measurement value ( ) is used for parameterization.

[0171] In one aspect, when the receiver device is a UE, operation 1210 can be performed by one or more WWAN transceivers 310, one or more short-range radio transceivers 320, one or more processors 342, memory 340, and / or positioning components 348, any or all of these components can be considered as parts for performing the operation. In another aspect, when the receiver device is a base station, operation 1210 can be performed by one or more WWAN transceivers 350, one or more short-range radio transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any or all of these components can be considered as parts for performing the operation.

[0172] At 1220, the receiver device determines the AoA of the one or more reference signals as the angle value of the channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals. In one aspect, when the receiver device is a UE, operation 1220 can be performed by one or more WWAN transceivers 310, one or more short-range transceivers 320, one or more processors 342, memory 340, and / or positioning component 348, any or all of these components can be considered as parts for performing the operation. In another aspect, when the receiver device is a base station, operation 1220 can be performed by one or more WWAN transceivers 350, one or more short-range transceivers 360, one or more processors 384, memory 386, and / or positioning component 388, any or all of these components can be considered as parts for performing the operation.

[0173] For receiver devices that support near-field AoA sensing, additional implementation or computational complexity may be required. For example, it may be necessary to implement advanced post-processing algorithms for near-field sensing in the receiver device, which may have significant computational complexity to enable the receiver device to jointly acquire distance- and angle-related parameters.

[0174] Therefore, at 1230, the receiver device determines the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the received beam that causes the highest signal strength measurement of the one or more reference signals. In one aspect, when the receiver device is a UE, operation 1230 can be performed by one or more WWAN transceivers 310, one or more short-range transceivers 320, one or more processors 342, memory 340, and / or positioning component 348, any or all of these components can be considered as parts for performing the operation. In another aspect, when the receiver device is a base station, operation 1230 can be performed by one or more WWAN transceivers 350, one or more short-range transceivers 360, one or more processors 384, memory 386, and / or positioning component 388, any or all of these components can be considered as parts for performing the operation.

[0175] In one aspect, method 1200 may further include (not shown) receiving from a sensing server (e.g., location server 230, LMF270) an indication of an algorithm to be used to determine the AoA of the one or more reference signals and the distance to the transmitter device.

[0176] This disclosure also provides techniques related to capability reporting and on-demand sensing. To enable a base station or UE to determine its implementation of AoA and / or AoD estimations, the JCS system may support base station and / or UE capability signaling to indicate whether the base station and / or UE can perform near-field sensing. The sensing server may collect capability information regarding near-field sensing capabilities and allocate network resources to cover the entire network sensing area. In one aspect, such capability signaling may be associated with a region identifier (ID) to identify which specific area the base station / UE can cover with near-field sensing.

[0177] The zone ID (represented as "Zone_id") is calculated as follows: x1 = Floor(x / L) Mod 64; y1 = Floor(y / L) Mod 64; Zone_id=y1 64+x1 The parameters of the above equation are defined as follows: L is the value of the region length, x is the longitude geodesic distance (in meters) between the current location of the UE (or base station) and the geographic coordinates (0, 0), and y is the latitude geodesic distance (in meters) between the current location of the UE (or base station) and the geographic coordinates (0, 0).

[0178] Therefore, method 1100 may further include (not shown) sending a capability message to a sensing server indicating that the transmitter device is capable of performing near-field sensing. The capability message may identify one or more areas in which the transmitter device is capable of performing the near-field sensing.

[0179] Similarly, method 1200 may further include (not shown) sending a capability message to a sensing server indicating that the receiver device is capable of performing near-field sensing. The capability message may identify one or more areas in which the receiver device is capable of performing the near-field sensing.

[0180] On one hand, based on base station / UE capability signaling regarding near-field sensing, a sensing server can request a network node (base station or UE) to perform on-demand sensing for a specific area. Such on-demand sensing requests can be associated with one or more area IDs to identify the areas for which the network node should perform sensing.

[0181] Therefore, method 1100 may further include (not shown) receiving a request from a sensing server to perform near-field sensing. The request may identify one or more areas for which the transmitter device is requesting the near-field sensing to be performed.

[0182] Similarly, method 1200 may further include (not shown) receiving from a sensing server a request to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device. The request may identify one or more areas in which the receiver device is requested to perform the near-field sensing.

[0183] As will be understood, the technical advantage of methods 1100 and 1200 is that they enable the UE or base station to derive angle information (AoA / AoD) in a network covering both the near-field service area and the far-field service area.

[0184] 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 regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations unless expressly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0185] Specific implementation examples are described in the following numbered clauses: Clause 1. A method of wireless sensing performed by a transmitter device, the method comprising: transmitting one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of a corresponding transmit beam in the plurality of transmit beams.

[0186] Clause 2. The method according to Clause 1, the method further comprising: receiving from a sensing server an instruction to transmit the one or more reference signals on each of the plurality of transmit beams based on the near-field codebook.

[0187] Clause 3. The method according to any one of Clauses 1 to 2, wherein the plurality of code points are plurality of steering vectors for the plurality of transmit beams.

[0188] Clause 4. The method according to any one of Clauses 1 to 3, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

[0189] Clause 5. The method according to any one of Clauses 1 to 4, the method further comprising: receiving at least one measurement report from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements associated with the one or more beam indices.

[0190] Clause 6. The method according to Clause 5, the method further comprising: determining at least one angle of origin (AoD) between the transmitter device and each of the at least one receiver device based on the at least one measurement report.

[0191] Clause 7. The method according to Clause 6, the method further comprising: reporting the at least one AoD to a sensing server.

[0192] Clause 8. The method according to any one of Clauses 1 to 7, the method further comprising: sending a capability message to a sensing server indicating that the transmitter device is capable of performing near-field sensing.

[0193] Clause 9. The method according to Clause 8, wherein the capability message identifies one or more areas in which the transmitter device is capable of performing the near-field sensing.

[0194] Clause 10. The method according to any one of Clauses 1 to 9, the method further comprising: receiving a request from a sensing server to perform near-field sensing.

[0195] Clause 11. The method according to Clause 10, wherein the request identifies one or more areas in which the transmitter device is requesting to perform the near-field sensing.

[0196] Clause 12. The method according to any one of Clauses 1 to 11, wherein the near-field codebook is configured to the transmitter device by a sensing server.

[0197] Clause 13. The method according to any one of Clauses 1 to 12, wherein: the transmitter device is a base station, and the receiver device is a user equipment (UE).

[0198] Clause 14. The method according to any one of Clauses 1 to 12, wherein: the transmitter device is a UE, and the receiver device is a base station.

[0199] Clause 15. The method according to any one of Clauses 1 to 12, wherein: the transmitter device is a first UE, and the receiver device is a second UE.

[0200] Clause 16. A method of wireless sensing performed by a receiver device, the method comprising: obtaining a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the plurality of receive beams; determining the angle of arrival (AoA) of the one or more reference signals as the angle value of a channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and determining the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0201] Clause 17. The method according to Clause 16, the method further comprising: receiving from a sensing server an indication of an algorithm for determining the AoA of the one or more reference signals and the distance to the transmitter device.

[0202] Clause 18. The method according to any one of Clauses 16 to 17, the method further comprising: sending a capability message to a sensing server indicating that the receiver device is capable of performing near-field sensing.

[0203] Clause 19. The method according to Clause 18, wherein the capability message identifies one or more areas in which the receiver device is capable of performing the near-field sensing.

[0204] Clause 20. The method according to any one of Clauses 16 to 19, the method further comprising: receiving from a sensing server a request to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device.

[0205] Clause 21. The method according to Clause 20, wherein the request identifies one or more areas in which the receiver device is requested to perform the near-field sensing.

[0206] Clause 22. The method according to any one of Clauses 16 to 21, the method further comprising: obtaining a second plurality of signal strength measurements of the one or more reference signals transmitted by the transmitter device on a second transmit beam, wherein the second plurality of signal strength measurements are obtained using the plurality of receive beams; determining a second AoA of the one or more reference signals as the angle value of a second channel steering vector corresponding to a second receive beam among the plurality of receive beams that results in the highest second signal strength measurement of the one or more reference signals; and determining a second distance to the transmitter device as the ranging value of the second channel steering vector corresponding to the second receive beam that results in the highest second signal strength measurement of the one or more reference signals.

[0207] Clause 23. The method according to any one of Clauses 16 to 22, wherein: the receiver device is a user equipment (UE), and the transmitter device is a base station.

[0208] Clause 24. The method according to any one of Clauses 16 to 22, wherein: the receiver device is a base station, and the transmitter device is a UE.

[0209] Clause 25. The method according to any one of Clauses 16 to 22, wherein: the receiver device is a first UE, and the transmitter device is a second UE.

[0210] Clause 26. A transmitter device comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to transmit one or more reference signals to at least one receiver device via the one or more transceivers on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of a corresponding transmit beam in the plurality of transmit beams.

[0211] Clause 27. The transmitter device according to Clause 26, wherein the one or more processors are further configured individually or in combination to: receive from a sensing server via the one or more transceivers an instruction to transmit the one or more reference signals on each of the plurality of transmission beams based on the near-field codebook.

[0212] Clause 28. The transmitter device according to any one of Clauses 26 to 27, wherein the plurality of code points are a plurality of steering vectors for the plurality of transmit beams.

[0213] Clause 29. The transmitter device according to any one of Clauses 26 to 28, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

[0214] Clause 30. A transmitter device according to any one of Clauses 26 to 29, wherein the one or more processors are further configured individually or in combination to receive, via the one or more transceivers, at least one measurement report from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements associated with the one or more beam indices.

[0215] Clause 31. The transmitter device according to Clause 30, wherein the one or more processors are further configured individually or in combination to determine at least one angle of origin (AoD) between the transmitter device and each of the at least one receiver device based on the at least one measurement report.

[0216] Clause 32. The transmitter device according to Clause 31, wherein the one or more processors are further configured individually or in combination to report the at least one AoD to a sensing server via the one or more transceivers.

[0217] Clause 33. The transmitter device according to any one of Clauses 26 to 32, wherein the one or more processors are further configured individually or in combination to: transmit a capability message indicating that the transmitter device is capable of performing near-field sensing to a sensing server via the one or more transceivers.

[0218] Clause 34. The transmitter device according to Clause 33, wherein the capability message identifies one or more areas in which the transmitter device is capable of performing the near-field sensing.

[0219] Clause 35. The transmitter device according to any one of Clauses 26 to 34, wherein the one or more processors are further configured individually or in combination to receive, via the one or more transceivers, a request to perform near-field sensing from a sensing server.

[0220] Clause 36. The transmitter device according to Clause 35, wherein the request identifies one or more regions in which the transmitter device performs the near-field sensing.

[0221] Clause 37. The transmitter device according to any one of Clauses 26 to 36, wherein the near-field codebook is configured to the transmitter device by a sensing server.

[0222] Clause 38. A transmitter device according to any one of Clauses 26 to 37, wherein: the transmitter device is a base station, and the receiver device is a user equipment (UE).

[0223] Clause 39. A transmitter device according to any one of Clauses 26 to 37, wherein: the transmitter device is a UE, and the receiver device is a base station.

[0224] Clause 40. A transmitter device according to any one of Clauses 26 to 37, wherein: the transmitter device is a first UE, and the receiver device is a second UE.

[0225] Clause 41. A receiver device comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the plurality of receive beams; determine the angle of arrival (AoA) of the one or more reference signals as an angle value of a channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and determine the distance to the transmitter device as a ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0226] Clause 42. The receiver device according to Clause 41, wherein the one or more processors are further configured individually or in combination to receive, via the one or more transceivers, from a sensing server an indication of an algorithm for determining the AoA of the one or more reference signals and the distance to the transmitter device.

[0227] Clause 43. The receiver device according to any one of Clauses 41 to 42, wherein the one or more processors are further configured individually or in combination to send a capability message to a sensing server via the one or more transceivers, indicating that the receiver device is capable of performing near-field sensing.

[0228] Clause 44. The receiver device according to Clause 43, wherein the capability message identifies one or more areas in which the receiver device is capable of performing the near-field sensing.

[0229] Clause 45. The receiver device according to any one of Clauses 41 to 44, wherein the one or more processors are further configured individually or in combination to receive, via the one or more transceivers, a request from a sensing server to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device.

[0230] Clause 46. The receiver device as described in Clause 45, wherein the request identifies one or more areas in which the receiver device performs the near-field sensing.

[0231] Clause 47. The receiver device according to any one of Clauses 41 to 46, wherein the one or more processors are further configured individually or in combination to: obtain a second plurality of signal strength measurements of the one or more reference signals transmitted by the transmitter device on a second transmit beam, wherein the second plurality of signal strength measurements are obtained using the plurality of receive beams; determine a second AoA of the one or more reference signals as the angle value of a second channel steering vector corresponding to a second receive beam among the plurality of receive beams that results in the highest second signal strength measurement of the one or more reference signals; and determine a second distance to the transmitter device as the ranging value of the second channel steering vector corresponding to the second receive beam that results in the highest second signal strength measurement of the one or more reference signals.

[0232] Clause 48. The receiver device according to any one of Clauses 41 to 47, wherein: the receiver device is a user equipment (UE), and the transmitter device is a base station.

[0233] Clause 49. A receiver device according to any one of Clauses 41 to 47, wherein: the receiver device is a base station, and the transmitter device is a UE.

[0234] Clause 50. A receiver device according to any one of Clauses 41 to 47, wherein: the receiver device is a first UE, and the transmitter device is a second UE.

[0235] Clause 51. A transmitter device comprising: means for transmitting one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of a corresponding transmit beam in the plurality of transmit beams.

[0236] Clause 52. The transmitter device according to Clause 51, the transmitter device further comprising: a component for receiving from a sensing server an indication to transmit the one or more reference signals on each of the plurality of transmission beams based on the near-field codebook.

[0237] Clause 53. The transmitter device according to any one of Clauses 51 to 52, wherein the plurality of code points are a plurality of steering vectors for the plurality of transmit beams.

[0238] Clause 54. The transmitter device according to any one of Clauses 51 to 53, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

[0239] Clause 55. The transmitter device according to any one of Clauses 51 to 54, the transmitter device further comprising: a component for receiving at least one measurement report from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements associated with the one or more beam indices.

[0240] Clause 56. The transmitter device according to Clause 55, the transmitter device further comprising: a component for determining at least one angle of origin (AoD) between the transmitter device and each of the at least one receiver device based on the at least one measurement report.

[0241] Clause 57. The transmitter device according to Clause 56, the transmitter device further comprising: a component for reporting the at least one AoD to a sensing server.

[0242] Clause 58. The transmitter device according to any one of Clauses 51 to 57, the transmitter device further comprising: a component for sending a capability message to a sensing server indicating that the transmitter device is capable of performing near-field sensing.

[0243] Clause 59. The transmitter device according to Clause 58, wherein the capability message identifies one or more areas in which the transmitter device is capable of performing the near-field sensing.

[0244] Clause 60. The transmitter device according to any one of Clauses 51 to 59, the transmitter device further comprising: a component for receiving a request from a sensing server to perform near-field sensing.

[0245] Clause 61. The transmitter device according to Clause 60, wherein the request identifies one or more regions in which the transmitter device performs the near-field sensing.

[0246] Clause 62. The transmitter device according to any one of Clauses 51 to 61, wherein the near-field codebook is configured to the transmitter device by a sensing server.

[0247] Clause 63. A transmitter device according to any one of Clauses 51 to 62, wherein: the transmitter device is a base station, and the receiver device is a user equipment (UE).

[0248] Clause 64. A transmitter device according to any one of Clauses 51 to 62, wherein: the transmitter device is a UE, and the receiver device is a base station.

[0249] Clause 65. A transmitter device according to any one of Clauses 51 to 62, wherein: the transmitter device is a first UE, and the receiver device is a second UE.

[0250] Clause 66. A receiver device comprising: means for obtaining a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the plurality of receive beams; means for: determining the angle of arrival (AoA) of the one or more reference signals as an angle value of a channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and means for: determining the distance to the transmitter device as a ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0251] Clause 67. The receiver device according to Clause 66, the receiver device further comprising: a component for receiving from a sensing server an indication of an algorithm for determining the AoA of the one or more reference signals and the distance to the transmitter device.

[0252] Clause 68. The receiver device according to any one of Clauses 66 to 67, the receiver device further comprising: a component for sending a capability message to a sensing server indicating that the receiver device is capable of performing near-field sensing.

[0253] Clause 69. The receiver device according to Clause 68, wherein the capability message identifies one or more areas in which the receiver device is capable of performing the near-field sensing.

[0254] Clause 70. The receiver device according to any one of Clauses 66 to 69, the receiver device further comprising: a component for receiving from a sensing server a request to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device.

[0255] Clause 71. The receiver device according to Clause 70, wherein the request identifies one or more areas in which the receiver device performs the near-field sensing.

[0256] Clause 72. The receiver device according to any one of Clauses 66 to 71, the receiver device further comprising: means for obtaining a second plurality of signal strength measurements of the one or more reference signals transmitted by the transmitter device on a second transmit beam, wherein the second plurality of signal strength measurements are obtained using the plurality of receive beams; means for determining a second AoA of the one or more reference signals as the angle value of a second channel steering vector corresponding to a second receive beam that results in the highest second signal strength measurement of the one or more reference signals; and means for determining a second distance to the transmitter device as the ranging value of the second channel steering vector corresponding to the second receive beam that results in the highest second signal strength measurement of the one or more reference signals.

[0257] Clause 73. The receiver device according to any one of Clauses 66 to 72, wherein: the receiver device is a user equipment (UE), and the transmitter device is a base station.

[0258] Clause 74. A receiver device according to any one of Clauses 66 to 72, wherein: the receiver device is a base station, and the transmitter device is a UE.

[0259] Clause 75. A receiver device according to any one of Clauses 66 to 72, wherein: the receiver device is a first UE, and the transmitter device is a second UE.

[0260] Clause 76. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a transmitter device, cause the transmitter device to: transmit one or more reference signals to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points of a near-field codebook, and wherein each of the plurality of code points is parameterized with an angle value and a ranging value of a corresponding transmit beam in the plurality of transmit beams.

[0261] Clause 77. The non-transitory computer-readable medium according to Clause 76 further includes computer-executable instructions that, when executed by the transmitter device, cause the transmitter device to: receive from a sensing server an instruction to transmit the one or more reference signals on each of the plurality of transmission beams based on the near-field codebook.

[0262] Clause 78. A non-transitory computer-readable medium according to any one of Clauses 76 to 77, wherein the plurality of code points are plurality of steering vectors for the plurality of transmit beams.

[0263] Clause 79. A non-transitory computer-readable medium according to any one of Clauses 76 to 78, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

[0264] Clause 80. A non-transitory computer-readable medium according to any one of Clauses 76 to 79, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the transmitter device, cause the transmitter device to: receive at least one measurement report from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements associated with the one or more beam indices.

[0265] Clause 81. The non-transitory computer-readable medium according to Clause 80 further includes computer-executable instructions that, when executed by the transmitter device, cause the transmitter device to: determine at least one angle of departure (AoD) between the transmitter device and each of the at least one receiver device based on the at least one measurement report.

[0266] Clause 82. The non-transitory computer-readable medium according to Clause 81, the non-transitory computer-readable medium further includes computer-executable instructions that, when executed by the transmitter device, cause the transmitter device to: report the at least one AoD to the sensing server.

[0267] Clause 83. The non-transitory computer-readable medium according to any one of Clauses 76 to 82, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the transmitter device, cause the transmitter device to: send a capability message to a sensing server indicating that the transmitter device is capable of performing near-field sensing.

[0268] Clause 84. The non-transitory computer-readable medium as described in Clause 83, wherein the capability message identifies one or more areas in which the transmitter device is capable of performing the near-field sensing.

[0269] Clause 85. A nontransitory computer-readable medium according to any one of Clauses 76 to 84, the nontransitory computer-readable medium further comprising computer-executable instructions that, when executed by the transmitter device, cause the transmitter device to: receive a request from a sensing server to perform near-field sensing.

[0270] Clause 86. The non-transitory computer-readable medium as described in Clause 85, wherein the request identifies one or more regions in which the transmitter device performs the near-field sensing.

[0271] Clause 87. A non-transitory computer-readable medium according to any one of Clauses 76 to 86, wherein the near-field codebook is configured to the transmitter device by a sensing server.

[0272] Clause 88. A non-transitory computer-readable medium pursuant to any one of Clauses 76 to 87, wherein: the transmitter device is a base station, and the receiver device is a user equipment (UE).

[0273] Clause 89. A non-transitory computer-readable medium pursuant to any one of Clauses 76 to 87, wherein: the transmitter device is a UE, and the receiver device is a base station.

[0274] Clause 90. A non-transitory computer-readable medium pursuant to any one of Clauses 76 to 87, wherein: the transmitter device is a first UE, and the receiver device is a second UE.

[0275] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a receiver device, cause the receiver device to: obtain a plurality of signal strength measurements of one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the plurality of signal strength measurements are obtained using corresponding plurality of receive beams of the receiver device, wherein the plurality of receive beams correspond to a plurality of channel steering vectors, and wherein each of the plurality of channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam among the plurality of receive beams; determine the angle of arrival (AoA) of the one or more reference signals as the angle value of a channel steering vector corresponding to the receive beam among the plurality of receive beams that results in the highest signal strength measurement of the one or more reference signals; and determine the distance to the transmitter device as the ranging value of the channel steering vector corresponding to the receive beam that results in the highest signal strength measurement of the one or more reference signals.

[0276] Clause 92. The non-transitory computer-readable medium according to Clause 91 further includes computer-executable instructions that, when executed by the receiver device, cause the receiver device to: receive from a sensing server an instruction for an algorithm for determining the AoA of the one or more reference signals and the distance to the transmitter device.

[0277] Clause 93. The non-transitory computer-readable medium according to any one of Clauses 91 to 92, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the receiver device, cause the receiver device to: send a capability message to a sensing server indicating that the receiver device is capable of performing near-field sensing.

[0278] Clause 94. The non-transitory computer-readable medium as described in Clause 93, wherein the capability message identifies one or more areas in which the receiver device is capable of performing the near-field sensing.

[0279] Clause 95. The non-transitory computer-readable medium according to any one of Clauses 91 to 94, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the receiver device, cause the receiver device to: receive from a sensing server a request to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device.

[0280] Clause 96. The non-transitory computer-readable medium as described in Clause 95, wherein the request identifies one or more areas in which the receiver device performs the near-field sensing.

[0281] Clause 97. A nontransitory computer-readable medium according to any one of Clauses 91 to 96, the nontransitory computer-readable medium further comprising computer-executable instructions, which, when executed by the receiver device, cause the receiver device to: obtain a second plurality of signal strength measurements of the one or more reference signals transmitted by the transmitter device on a second transmit beam, wherein the second plurality of signal strength measurements are obtained using the plurality of receive beams; determine a second AoA of the one or more reference signals as the angle value of a second channel steering vector corresponding to a second receive beam among the plurality of receive beams that results in the highest second signal strength measurement of the one or more reference signals; and determine a second distance to the transmitter device as the ranging value of the second channel steering vector corresponding to the second receive beam that results in the highest second signal strength measurement of the one or more reference signals.

[0282] Clause 98. A non-transitory computer-readable medium according to any one of Clauses 91 to 97, wherein: the receiver device is a user equipment (UE), and the transmitter device is a base station.

[0283] Clause 99. A non-transitory computer-readable medium according to any one of Clauses 91 to 97, wherein: the receiver device is a base station, and the transmitter device is a UE.

[0284] Clause 100. A non-transitory computer-readable medium pursuant to any one of Clauses 91 to 97, wherein: the receiver device is a first UE, and the transmitter device is a second UE.

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

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

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

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

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

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

Claims

1. A method for wireless sensing performed by a transmitter device, the method comprising: One or more reference signals are transmitted to at least one receiver device on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points in a near-field codebook, and wherein each of the plurality of code points is parameterized using an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams.

2. The method according to claim 1, further comprising: Receive from the sensing server an instruction to transmit one or more reference signals on each of the plurality of transmission beams based on the near-field codebook.

3. The method of claim 1, wherein the plurality of code points are plurality of steering vectors for the plurality of transmit beams.

4. The method according to claim 1, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

5. The method according to claim 1, further comprising: At least one measurement report is received from the at least one receiver device, the at least one measurement report including one or more beam indices and one or more signal strength measurements associated with the one or more beam indices.

6. The method according to claim 5, further comprising: Based on the at least one measurement report, at least one angle of origin (AoD) is determined between the transmitter device and each of the at least one receiver device.

7. The method according to claim 6, further comprising: Report at least one AoD to the sensing server.

8. The method according to claim 1, further comprising: Send a message to the sensing server indicating that the transmitter device is capable of performing near-field sensing.

9. The method of claim 8, wherein the capability message identifies one or more areas in which the transmitter device is capable of performing the near-field sensing.

10. The method according to claim 1, further comprising: Receive a request from the sensing server to perform near-field sensing.

11. The method of claim 10, wherein the request identifier requests the transmitter device to perform the near-field sensing in one or more areas.

12. The method of claim 1, wherein the near-field codebook is configured by a sensing server to the transmitter device.

13. The method according to claim 1, wherein: The transmitter device is a base station, and The receiver device is a user equipment (UE).

14. The method of claim 1, wherein: The transmitter device is a UE, and The receiver device is a base station.

15. The method of claim 1, wherein: The transmitter device is the first UE, and The receiver device is the second UE.

16. A method of wireless sensing performed by a receiver device, the method comprising: Multiple signal strength measurements are obtained for one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the multiple signal strength measurements are obtained using corresponding multiple receive beams of the receiver device, wherein the multiple receive beams correspond to multiple channel steering vectors, and wherein each of the multiple channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam in the multiple receive beams; The angle of arrival (AoA) of the one or more reference signals is determined as the angle value of the channel steering vector corresponding to the receiving beam among the plurality of receiving beams that results in the highest signal strength measurement of the one or more reference signals; as well as The distance to the transmitter device is determined as the ranging value of the channel steering vector corresponding to the receiving beam that causes the highest signal strength measurement of the one or more reference signals.

17. The method according to claim 16, further comprising: Receive from the sensing server an instruction for an algorithm used to determine the AoA of the one or more reference signals and the distance to the transmitter device.

18. The method according to claim 16, further comprising: Send a message to the sensing server indicating that the receiver device is capable of performing near-field sensing.

19. The method of claim 18, wherein the capability message identifies one or more areas in which the receiver device is capable of performing the near-field sensing.

20. The method of claim 16, further comprising: Receive a request from the sensing server to perform near-field sensing to determine the AoA of the one or more reference signals and the distance to the transmitter device.

21. The method of claim 20, wherein the request identifier requests the receiver device to perform the near-field sensing in one or more areas.

22. The method according to claim 16, further comprising: A second plurality of signal strength measurements are obtained of the one or more reference signals transmitted by the transmitter device on a second transmit beam, wherein the second plurality of signal strength measurements are obtained using the plurality of receive beams; The second AoA of the one or more reference signals is determined as the angle value of the second channel steering vector corresponding to the second receive beam among the plurality of receive beams that results in the highest second signal strength measurement of the one or more reference signals; as well as The second distance to the transmitter device is determined as the ranging value of the second channel steering vector corresponding to the second received beam that causes the highest signal second strength measurement of the one or more reference signals.

23. The method of claim 16, wherein: The receiver device is a user equipment (UE), and The transmitter device is a base station.

24. The method of claim 16, wherein: The receiver device is a base station, and The transmitter device is a UE.

25. The method of claim 16, wherein: The receiver device is the first UE, and The transmitter device is the second UE.

26. A transmitter device, the transmitter device comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: One or more reference signals are transmitted to at least one receiver device via the one or more transceivers on each of a plurality of transmit beams, wherein the plurality of transmit beams correspond to a plurality of code points in a near-field codebook, and wherein each of the plurality of code points is parameterized using an angle value and a ranging value of the corresponding transmit beam in the plurality of transmit beams.

27. The transmitter device of claim 26, wherein the plurality of code points are plurality of steering vectors for the plurality of transmit beams.

28. The transmitter device of claim 26, wherein the angle values ​​and ranging values ​​corresponding to the plurality of code points are sampled from the entire angle-distance domain.

29. A receiver device, the receiver device comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: Multiple signal strength measurements are obtained for one or more reference signals transmitted by a transmitter device on a first transmit beam, wherein the multiple signal strength measurements are obtained using corresponding multiple receive beams of the receiver device, wherein the multiple receive beams correspond to multiple channel steering vectors, and wherein each of the multiple channel steering vectors is parameterized with an angle value and a ranging value of a corresponding receive beam in the multiple receive beams; The angle of arrival (AoA) of the one or more reference signals is determined as the angle value of the channel steering vector corresponding to the receiving beam among the plurality of receiving beams that results in the highest signal strength measurement of the one or more reference signals; as well as The distance to the transmitter device is determined as the ranging value of the channel steering vector corresponding to the receiving beam that causes the highest signal strength measurement of the one or more reference signals.

30. The receiver device of claim 29, wherein the one or more processors are further configured individually or in combination to: Instructions are received from the sensing server via the one or more transceivers regarding the algorithm for determining the AoA of the one or more reference signals and the distance to the transmitter device.

Images