Methods and systems for doppler estimation and reporting in location and radio frequency sensing

Abstract

Disclosed are techniques for radio frequency (RF) sensing. In an aspect, a user equipment (UE) may send, to a network entity, information indicating Doppler reporting capability. The UE may receive, from the network entity, a Doppler reporting request. The UE may determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request. The UE may calculate a Doppler estimate of a received signal according to the Doppler measurement parameters. The UE may report the Doppler estimate to the network entity according to the Doppler reporting parameters.

Description

Qualcomm Ref. No. 2402142WO1METHODS AND SYSTEMS FOR DOPPLER ESTIMATION AND REPORTING IN LOCATION AND RADIO FREQUENCY SENSINGTECHNICAL FIELD

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

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TOMA), the Global System for Mobile communications (GSM), etc.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), radio frequency (RF) sensing, and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high -density deployments for 5G, enable highly accurate 5G-based sensing and positioning.SUMMARY

[0004] The following presents a simplified summary relating 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 toQC2402142WOQualcomm Ref. No. 2402142WO2identify 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 relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0005] In an aspect, a sensing node 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, either alone or in combination, configured to: cause the sensing node to send, via the one or more transceivers, to a network entity, information indicating Doppler reporting capability; receive, from the network entity via the one or more transceivers, a Doppler reporting request; determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculate a Doppler estimate of a received signal according to the Doppler measurement parameters; and cause the sensing node to report, to the network entity via the one or more transceivers, the Doppler estimate according to the Doppler reporting parameters.

[0006] In an aspect, a network entity includes one or more memories, one or more transceivers, and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, from a sensing node via the one or more transceivers, first information indicating Doppler reporting capability of the sensing node; determine, based on the first information, Doppler measurement and reporting parameters; and cause the network entity to send, to the sensing node via the one or more transceivers, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0007] In an aspect, a method of radio frequency (RF) sensing performed by a sensing node includes: sending, to a network entity, information indicating Doppler reporting capability; receiving, from the network entity, a Doppler reporting request; determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculating a Doppler estimate of a received signal according to the Doppler measurement parameters; and reporting the Doppler estimate to the network entity according to the Doppler reporting parameters.QC2402142WOQualcomm Ref. No. 2402142WO

[0008] In an aspect, a method of RF sensing performed by a network entity includes: receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node; determining, based on the first information, Doppler measurement and reporting parameters; and sending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0009] In an aspect, a sensing node includes means for sending, to a network entity, information indicating Doppler reporting capability, means for receiving, from the network entity, a Doppler reporting request, means for determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request, means for calculating a Doppler estimate of a received signal according to the Doppler measurement parameters, and means for reporting the Doppler estimate to the network entity according to the Doppler reporting parameters.

[0010] In an aspect, a network entity includes means for receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node, means for determining, based on the first information, Doppler measurement and reporting parameters, and means for sending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0011] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sensing node, cause the sensing node to: send, to a network entity, information indicating Doppler reporting capability; receive, from the network entity, a Doppler reporting request; determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculate a Doppler estimate of a received signal according to the Doppler measurement parameters; and report the Doppler estimate to the network entity according to the Doppler reporting parameters.

[0012] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: receive, from a sensing node, first information indicating Doppler reporting capability of the sensing node; determine, based on the first information, Doppler measurement and reporting parameters; and send, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0013] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. QC2402142WOQualcomm Ref. No. 2402142WOBRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0015] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0016] FIGS. 2A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure.

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

[0018] FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure.

[0019] FIG. 5 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the disclosure.

[0020] FIG. 6 is a graph representing a radio frequency (RF) channel impulse response over time, according to aspects of the disclosure.

[0021] FIG. 7 is a graph of an example Doppler measurement of a signal having three paths, according to aspects of the disclosure.

[0022] FIG. 8 is a signaling and event diagram illustrating a method for Doppler estimation and reporting, according to aspects of the disclosure.

[0023] FIG. 9 is a flowchart of an example process, performed by a sensing node, associated with RF sensing, according to aspects of the disclosure.

[0024] FIG. 10 is a flowchart of an example process, performed by a network entity, associated with RF sensing, according to aspects of the disclosure.DETAILED DESCRIPTION

[0025] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.QC2402142WOQualcomm Ref. No. 2402142WO5

[0026] Various aspects relate generally to radio frequency (RF) sensing in 5G. Some aspects more specifically relate to methods and systems for Doppler estimation and reporting in location and RF sensing. In some examples, a location management function (LMF) or other network entity receives information describing a capability of a UE or other sensing node to report on Doppler measurements, and based on that information, sends a Doppler reporting request to the sensing node. The Doppler reporting request includes suggested parameters for Doppler measurements. The sensing node may adopt the suggested parameters. The sensing node then takes Doppler measurements and reports the results to the network entity.

[0027] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by knowing the capabilities and limitations of a particular sensing node, the network entity can provide a customized Doppler measurement and reporting framework that meets Doppler accuracy requirements within the capabilities of the sensing node.

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

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

[0030] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set QC2402142WOQualcomm Ref. No. 2402142WOof computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

[0031] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “’mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on.

[0032] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an QC2402142WOQualcomm Ref. No. 2402142WO7uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a. paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink / reverse or downlink / forward traffic channel,

[0033] The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

[0034] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., w'hen receiving and measuring signals from UEs).

[0035] An “’RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through QC2402142WOQualcomm Ref. No. 2402142WO8multipath channels. 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 it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0036] FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications 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. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0037] " Die base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. A location server 172 may be integrated with a base station 102. A UE 104 may communicate with a location server 172 directly or indirectly. For example, a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104. A UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on. For signaling purposes, communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.

[0038] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load QC2402142WOQualcomm Ref. No. 2402142WObalancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0039] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0040] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' (labeled “SC” for “small cell”) may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneousQC2402142WOQualcomm Ref. No. 2402142WOnetwork may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

[0041] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).

[0042] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

[0043] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MULTEFIRE®.

[0044] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the QC2402142WOQualcomm Ref. No. 2402142WOmmW / near mmW radio frequency band have high path ioss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) overammW communication link 184 to compensate for the extremely high path ioss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[6045] Transmit beamforming is a technique for focusing an RF signal 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 (omni-directionally). With 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, thereby providing a faster (in teams of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array" or an “antenna array”) that creates abeam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF' current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0046] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Tirus, 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 a 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 a second reference RF signal transmitted on the QC2402142WOQualcomm Ref. No. 2402142WO12same 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 a second reference RF signal transmited on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

[0047] In receive beamfonning, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain seting and / or adjust the phase setting of an array of antennas m a particular direction to amplify (e.g., to increase the gam level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received qualify (RSRQ), signal-to- interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.

[8048] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[8049] Note that a "‘downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0050] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been QC2402142WOQualcomm Ref. No. 2402142WO13identified as frequency range designations FR1 (410 MHz -- 7.125 GHz) and FR2. (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION'® as a “millimeter wave” band.

[8051] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies.Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, 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 frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or tire like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0053] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary’ carrier” or “anchor carrier” or “primaiy serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary’ carriers” or “secondary’ serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primaiy frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a earner QC2402142WOQualcomm Ref. No. 2402142WO14in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary earner may be a carrier in an unlicensed frequency. Hie secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary' carrier, since both primary' uplink and downlink carriers are typically UE- specific. This means that different UEs 104 / 182 in a cell may have different downlink primary’ earners. The same is true for the uplink primary' carriers. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.

[0054] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may' be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary' carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly' increase its data transmission and / or reception rates. For example, two 20 MHz aggregated earners in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[6055] 'The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 12.0 and / or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for tire UE 164 and the mmW base station 180 may' support one or more SCells for the UE 164.

[0056] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication.Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and abase station). SL-UEs (e.g., UE 164, UE 182) may' also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core QC2402142WOQualcomm Ref. No. 2402142WOcellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicie (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to recei ve transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1: M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates tire scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between SL-UEs without the involvement of a base station 102.

[8057] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.1 lx WLAN technologies generally referred to as "‘Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.QC2402142WOQualcomm Ref. No. 2402142WO16

[0058] Note that although FIG. 1 only illustrates two of tire UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamfonning, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160.

[0059] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0060] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi¬ functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and / or the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0061] In an aspect, SVs 112 may additionally or alternatively be part of one or more non¬ terrestrial networks (NTNs). In an NTN, an SV 112 is connected to an earth station (also QC2402142WOQualcomm Ref. No. 2402142WO17referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.

[6062] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device -to-device (D2D) peer-to-peer (P2P) links (referred to as “si delinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of die base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN ST A 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on.

[0063] FIG. 2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally 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 function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222 or ng-eNB 2.24 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).QC2402142WOQualcomm Ref. No. 2402142WO

[0064] Another optional aspect may include a location server 230. which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services tor UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and / or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).

[0065] FIG. 2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the LIE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). Hie AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulator}' services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 QC2402142WOQualcomm Ref. No. 2402142WOand the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.

[0066] Functions of the UPF 262 include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (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 sending and forwarding of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

[0067] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 2.62 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the Ni l interface.

[6068] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF 270 can be configured to support, one or more location sendees tor UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 2.70, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients QC2402142WOQualcomm Ref. No. 2402142WO(e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and / or data like the transmission control protocol (TCP) and / or IP).

[0069] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g,, a location estimate) for the UE 204, As such, in some cases, the third-party' server 274 may be referred to as a location services (LC-S) client or an external client. The third- party server 274 can be implemented as a plurality' of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.

[0070] User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222. and / or ng-eNBs 224 in the NG-RAN 220. The interface between gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2'’ interface, and the interface between gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the£<N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223, referred to as the “Xn-C” interface. One or more of gNBs 22.2 and / or ng-eNBs 2.24 may communicate with one or more UEs 2.04 over a wireless interface, referred to as the “Uu” interface.

[0071] Tire functionality of a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. A gNB-CU 22.6 is a logical node that includes the base station functions of transferring user data, mobility' control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, tire gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. A gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “Fl” interface. The physical (PHY’) layer functionality of a gNB 222 is generally QC2402142WOQualcomm Ref. No. 2402142WOhosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between a gNB-DU 228 and a gNB-RU 229 is referred to as the “Fx” interface. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.

[0072] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP3, cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0073] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (V CU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0074] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN ALLIANCE®:1)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of theQC2402142WOQualcomm Ref. No. 2402142WOdisaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0075] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. 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 a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through 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). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an Fl interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 2.2.9) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

[0076] Each of the units, i.e., the CUs 2.80, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium, Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0077] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU¬ LT)), control plane functionality (i.e.. Central Unit - Control Plane (CU-CP)), or a QC2402142WOQualcomm Ref. No. 2402142WOcombination 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. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

[0078] The DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP®). In some aspects, the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280.

[0079] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0080] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 255 may be configured to interact QC2402142WOQualcomm Ref. No. 2402142WOwith a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an 01 interface. The SMO Framework 2.55 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0081] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an Al interface) the Near- RT RIC 2.59. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with tire Near-RT RIC 259.

[0082] 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 external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. 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 for performance and employ AI / ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

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

[0084] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means fortuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and / or the like. The WAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[8085] The UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and QC2402142WOQualcomm Ref. No. 2402142WO366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest. The short- range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 32.8 and 368 (e.g., messages, indications, information, and so on), respectively, and conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 32.0 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 32.0 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everythmg (V2X) transceivers.

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

[0087] The satellite signal receivers 332 and 372 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal receivers) 332 and 372. are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou QC2402142WOQualcomm Ref. No. 2402142WO27signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, etc. Where the satellite signal receiver(s) 332 and 372 are non¬ terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signal receivers) 332 and 372 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0088] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitters) 334 and 374 are NTN transmitters, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitter) s) 334 and 374 may request information and operations as appropriate from the other systems.

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

[0090] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 32.4, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry7and receiver circuitry' in a single device) in some implementations, may comprise separate transmitter circuitry' and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry' and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) 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 a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (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 a plurality of antennas (e.g,, antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry' and receiver circuitry may share the same plurality' of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only' receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., the WWAN transceivers 310 and 350, the short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0091] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 m some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as "a transceiver,” "‘at least one transceiver,” or "‘one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and aQC2402142WOQualcomm Ref. No. 2402142WObase station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0092] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 342, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the 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 circuitry, or various combinations thereof.

[0093] The UE 302. the base station 304, and the network entity 306 include memory' circuitry' implementing memories 340, 386, and 396 (e.g,, each including a memory' device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity' 306 may include measurement / sensing module 348, 388, and 398, respectively. The measurement / sensing module 348, 388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity' 306 to perform the functionality described herein. In other aspects, the measurement / sensing module 348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the measurement / sensing module 348, 388, and 398 may be memory' modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause tire UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the measurement / sensing module 348, which may be, for example, part of the one or more WWAN transceivers 310, tire memory 340, the one or QC2402142WOQualcomm Ref. No. 2402142WO30more processors 342, or any combination thereof, or may be a standalone component. FIG, 3B illustrates possible locations of the measurement / sensing module 388, which may be, tor example, part of the one or more AN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG. 3C illustrates possible locations of the measurement / sensing module 398, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.

[8094] The UE 302 may include one or more sensors 344 coupled to the one or more processors 342 to provide means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by the one or more WAV AN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal interface 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and / or any other Ape of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0095] In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0096] Referring to the one or more processors 384 m more detail, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC QC2402142WOQualcomm Ref. No. 2402142WO31connection 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation 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 prioritization.

[0097] The transmitter 354 and the receiver 352 may implement Layer-1 (LI) functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations 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 coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

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

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

[0100] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 342 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation 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 through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0101] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the QC2402142WOQualcomm Ref. No. 2402142WO33appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.

[0102] The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384.

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

[0104] For convenience, the UE 302, the base station 304, and / or the network entity 306 are shown in FIGS. 3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG. 3 A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and / or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal interface 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.QC2402142WOQualcomm Ref. No. 2402142WO34

[0105] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 308, 382, and 392, respectively. In an aspect, the data buses 308, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g,, gNB and location server functionality incorporated into the same base station 304), the data buses 308, 382, and 392 may provide communication between them.

[0106] The components of FIGS. 3 A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3A, 3B, and 3C may be implemented in one or more circuits such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Also, some or all of tire functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processors 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the measurement / sensing module 348, 388, and 398, etc.

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

[0108] FIG. 4 is a time / frequency diagram 400 illustrating an example frame structure, according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communications technologies may have different frame structures and / or different channels. Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs).

[0109] LIE, and in some cases NR, utilizes orthogonal frequency-division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0110] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (p), for example, subcarrier spacings of 15 kHz (p-0), 30 kHz ( p 1 ), 60 kHz (p-2), 120 kHz (p-3), and 240 kHz (p-4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (p=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (ps), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (µ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (p=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 ps, and the maximum QC2402142WOQualcomm Ref. No. 2402142WO36nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS i;ithere are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (µ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 us, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0111] In the example of FIG. 4, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIG. 4, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the ¥ axis) with frequency increasing (or decreasing) from bottom to top.

[0112] A resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. Tire resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 4, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0113] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell -specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. FIG. 4 illustrates example locations of REs carrying a reference signal (labeled “R”).

[0114] Reference signals such as PRS and SRS are used for RF positioning, which is the determination of the location of a network entity having RF communication capabilities, e.g., a UE. RF sensing, on the other hand, is the determination of the presence, location, and / or count of target objects that do not have RF communication capabilities. RF sensing QC2402142WOQualcomm Ref. No. 2402142WO37may also be referred to as a type of radar. One type of signal that may be used for RF sensing is frequency modulated continuous wave (FMCW) signal, also called a “chirp.” When OFDM signals are used for RF sensing, this is referred to as OFDM radar. OFDM radar can use any transmitted signals with known characteristics, but reference signals generally have constant transmit power and thus are preferred over data signals, for example.

[0115] FIG. 5 is a time / frequency diagram 500 illustrating an example OFDM radar configuration, according to aspects of the disclosure. In the example shown in FIG. 5, certain time / frequency resources within the OFDM frame, such as the shaded resource elements in FIG. 5, are used for OFDM radar. In some aspects, an OFDM-based reference signal has a bandwidth of B and an effective subcarrier spacing of Af, and is transmitted every ATsym, for an entire duration of. If the sensing signal being used is a PRS, for example, Tfrmis the nominal / effective length of a PRS sample. 'The table below illustrates how B, f, Trm, and ATsymaffect the performance of the OFDM radar.Table 1OFDM radarDetermined by P arameter(s) characteristicRange resolution AR = — Bandwidth B2BMaximum measurable Eftective subcarrier range 2Af spacing A fA Frame duration ifrmvelocity resolutiont rm Carrier frequency frMaximum measurable A Symbol spacing Ar,;velocity 4A7 Gamer frequency / ,- Frame duration 7<rmDoppler resolution A t.Garner frequency Maximum measurablermax ■ 2 ■ / cSymbol spacing A 7 Doppler shift Carrier frequency / ,•QC2402142WOQualcomm Ref. No. 2402142WO38Where λ = wavelength and c = the speed of light.

[0116] Note that if {A ', fc, & Tsym} are fixed, {B, Tfrm] determines the radar characteristic. It can be seen from the table above that:• as the bandwidth increases, range resolution improves;• as the effective subcarrier spacing is reduced, maximum measurable range increases;• as the frame duration 7}™ increases, velocity resolution improves but Doppler resolution gets worse; and• as the symbol spacing is reduced, maximum measurable velocity and maximum measurable Doppler shift both increase.Thus, there is a trade-off between velocity resolution and Doppler resolution.

[0117] FIG. 6 is a graph 600 representing an example channel estimate of a multipath channel between a receiver device (e.g., any of tire UEs or base stations described herein) and a transmitter device (e.g., any other of the UEs or base stations described herein), according to aspects of the disclosure. The channel estimate represents the intensity of a radio frequency (RF) signal, which may be a sensing signal, transmitted during one symbol over one or more subcarriers and received through a multipath channel as a function of time delay, and may be referred to as the channel energy response (CER), channel impulse response (CIR), or power delay profile (PDP) of the channel. Thus, the horizontal axis represents time (e.g., milliseconds) and the vertical axis represents signal strength (e.g., decibels). Note that a multipath channel is a channel between a transmitter and a receiver over which an RF signal follows multiple paths, or multipaths, due to transmission of the RF signal on multiple beams and / or to the propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).

[0118] In the example of FIG. 6, the receiver detects / measures multiple (four) channel taps of the RF signal. Each channel tap is a cluster of one or more rays and corresponds to a multipath that the RF signal followed between the transmitter and the receiver. Thus, a channel tap represents the time of arrival and signal strength of an RF signal over a multipath. There may be multiple channel taps due to the RF signal being transmited on different transmit beams (and therefore at different angles), or because of the propagation characteristics of RF’ signals (e.g., potentially following different paths due to reflections).QC2402142WOQualcomm Ref. No. 2402142WO39or both. Note that although FIG. 6 illustrates channel taps of two to five rays, as will be appreciated, the channel taps may have more or fewer than the illustrated number of rays.

[0119] In the example of FIG. 6, the channel tap detected at time T3 is composed of stronger rays than the channel tap detected at time T 1. This may be due to an obstruction on the LOS path between the transmitter and the receiver. Alternatively or additionally, there may be a strong reflector along the NLOS path corresponding to the channel tap detected at time T3.

[0120] FIG. 7 is a graph 700 of an example Doppler measurement of a signal having three paths:a first path detected at time To, a second path detected at time Ti, and a third path detected at time T2 on the “Time” axis. In FIG. 7, the channel taps are shown as a single bar for simplicity'. The graph 700 shows the relative strengths of the three paths shown on the “power” axis and the Doppler component of each path shown on the “Doppler frequency” axis. The Doppler component measured may be the mean Doppler shift of the path, the center of mass of the Doppler spectrum of the path, or other Doppler measurement. In the example shown in FIG. 7, the path detected at time To has a center of mass of the Doppler spectrum at frequency Fo, the path detected at time Ti has a center of mass of the Doppler spectrum at frequency Fi, and the path detected at time T₂ has a center of mass of the Doppler spectrum at frequency F₂.

[0121] FIG. 7 also illustrates a time window for identifying channel paths / taps (TW) 702. for identifying channel paths / taps. In some aspects, the start time of the TW 702 is based on a downlink reference time, first arriving path. In some aspects, the length of the TW 702 is configured via RRC messages (referred to herein as being “RRC configured”), and may be based on the tracking reference signal (TRS) configuration.

[0122] A sensing node, which may be a UE, RSU, BS, etc., may be configured to take a single measurement (“a single shot”) or to take multiple measurements over time (“multiple shots”) and average the measured values. In some aspects, a measurement window is defined during which the sensing node can coherently average the measurements. In some aspects, coherent averaging may be enabled or disabled via some RRC configuration. For example, if a time restriction value is specified, then the sensing node performs a single shot, and thus performs no Doppler estimation averaging, but if no time restriction value is specified, the sensing node performs multi-shot measurements, and thus is allowed to enhance the estimated Doppler frequency values using values from previous measurements.QC2402142WOQualcomm Ref. No. 2402142WO40

[0123] Reporting metrics specify what information the sensing node should include in its report.In some aspects, the sensing node should report at least one of the following for each tap: the Doppler shift or the center of mass of the Doppler spectrum; the maximum Doppler frequency; multiple Doppler frequency values per tap; an empirical correlation between multiple observations of channel path / tap, such as defined by the equation £’ h; (7’)£(0)], where T is time spacing between the observations (T=4 for TRS).

[0124] In preparation for sensing, a UE or other sensing node will receive measurement configuration information from a network. The measurement configuration may specify various parameters, such as the type of measurements to make, the resources to be measured, the period of time in which to take the measurements, etc. For location and sensing tasks, the sensing node may be expected to report on different aspects of the measured signals. For example, the sensing node may issue a time and RSRP report or a Doppler and velocity report, etc. The length of the measurement period configured by the network may be determined at least in part based on the type of report that the sensing node will issue. For example, a sensing node may need to take more measurements for a Doppler / velocity report than are needed for a time / RSRP-only report, and thus the minimum number of samples (e.g., via a measurement configuration parameter nrofSamples) may be set accordingly, e.g., set to a lower number for time / RSRP-only reports and set to a higher number for Doppl er / vel oci ty reports.

[0125] The length of the measurement period may also depend on the capability of the sensing node. Typically, calculating Doppler / velocity results is more resource and time intensive than calculating time / RSRP results, and the number of positioning resources that a sensing node can process within a given duration of time may be limited by the sensing node’s hardware and / or processing capabilities. For example, during a duration of T milliseconds, a UE may be able to process X number of positioning resources for Rx-Tx measurements, but only Y number of positioning resources for Doppler estimations (including Rx-Tx measurements), where X > Y. The different values for X and Y may be due to different processing implementations. For example, a time domain implementation of Doppler processing may need more processing power than a frequency domain implementation of Doppler processing. Likewise, a high-end UE may have more processing capability generally than a low -end UE, causing the low-end UE to take longer to perform certain calculations compared to the high-end UE. Another factor that may affect the length of the measurement period needed is how many channel taps the sensing QC2402142WOQualcomm Ref. No. 2402142WO41node is expected to analyze, and what specifically the sensing node is expected to report (e.g., the reporting metric).

[0126] Thus, a sensing node may receive a measurement configuration having various parameters. Example parameters include, but are not limited to, the time window for identifying channel taps / paths, the number of taps to measure for Doppler reporting, one-shot versus multi-shot measurements, a coherency time window, etc. In some aspects, an LFM may send location request information that includes the following parameters:• timingReportingGranularityFactor-. this field specifies the recommended reporting granularity for the DLRSTD measurements. Value (0..5) corresponds to (k()..k5) used for field nr-RSTD and field nr-RSTD-ResuliDiff\n NR-DL- TDOA-MeasElement. The UE may select a different granularity value for nr- RSTD and nr-RSTD-ResultDiff.» addilionalPaths-. this field, if present, indicates that the target device is requested to provide the nr-AddiftonalPathList in information element NR-DL-TDOA- SignalMeasurementlnformation. If this field is present, the field additionalPathsExt shall be absent.® nr-AdditionalPathList'. this field specifies one or more additional detected path timing values for the TRP or resource, relative to the path timing used for determining the nr-RSTD value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. If this field is present, the field nr-AdditionalPathListExt shall be absent.

[0127] FIG. 8 is a signaling and event diagram 800 illustrating a method for Doppler estimation and reporting, according to aspects of the disclosure. FIG. 8 illustrates an interaction between a network entity 802 (e.g., an LMF) and a sensing node 804 (e.g., a UE).

[0128] In the example illustrated in FIG. 8, at 806, the sensing node 804 sends, to the network entity 802, information indicating the sensing node’s Doppler reporting capability. In some aspects, the sensing node 804 indicates that it can report up to V Doppler frequency values for a given measurement (RSTD, or Rx-Tx, or path-RSRP) or for an additional path reported relative to the RSTD or Rx-Tx measurement. In some aspects, this capability is reported per frequency band.

[0129] In the example illustrated in FIG. 8, at 808, the sensing node 804 receives, from the network entity 802, a Doppler reporting request comprising at least one recommendedQC2402142WOQualcomm Ref. No. 2402142WO42Doppler measurement or reporting parameter. In some aspects, the network entity 802 requests the sensing node 804 to report up to M Doppler frequencies values for each reported path, e.g., where M = 1 means the sensing node is requested to report a single Doppler frequency value per path / measurement, and M >1 means the sensing node is requested for multiple measured Doppler freq, values per path. In some aspects, the multiple Doppler frequency values can be reported in a differential manner relative to the first Doppler value for the given path, relative to the center Doppler value for the given path, or relative to the first / center doppler value of the first path.

[0130] In some aspects, the Doppler reporting request may specify that sensing node 804 use the same RF chain (e.g., Rx antenna), the same transmission timing element group (RxTEG), or the same reception and transmission timing element group (RxTxTEG), for each measurement. In some aspects, the Doppler reporting request may specify that the sensing node 804 use different RF chains, different RxTEGs, or different RxTxTEGs, for each measurement. For example, if the sensing node 804 has two Rx antennas, the network entity 802 may request that the sensing node 804 report M Doppler frequencies for each of the two Rx antennas, for each path measured.

[0131] In some aspects, the Doppler reporting request may indicate a recommended reporting granularity for the Doppler frequency values. The recommended reporting granularity is related to velocity resolution and Doppler resolution, and thus is a function of frame duration Tfrm. In some aspects, the Doppler reporting request may indicate a recommended maximum and minimum Doppler frequency value.

[0132] In some aspects, the Doppler reporting request may indicate or suggest that the sensing node 804 be able to measure a Doppler value at least as large as value VI. In some aspects, the Doppler reporting request may indicate or suggest that the sensing node 804 does not need to measure a Doppler value larger than value V2. The maximum Doppler frequency value is related to maximum measurable velocity and Doppler shift, and thus is a function of symbol spacing ATsym.

[0133] In the example illustrated in FIG. 8, at block 810, the sensing node 804 determines the Doppler measurement parameters that it will use. For example, the sensing node 804 may select a different reporting granularity value than what was recommended / requested by the network entity 802, and the sensing node 804 may select a different maximum and minimum values tor reported Doppler frequencies. In some aspects, the sensing node 804 may use the same measurement parameters for all transmission / reception points (TRPs). QC2402142WOQualcomm Ref. No. 2402142WO43In some aspects, the sensing node 804 may use one set of measurement parameters for on TRP or TRP group and another set of measurement param eters for another TRP or TRP group. In some aspects, the sensing node 804 may choose to use a different set of measurement parameters for each separate measurement.

[0134] The chosen reporting granularity, and tire limits on the range of Doppler values that tire sensing node 804 should measure, allow the sensing node 804 to decide, for example, whether it needs to take measurements using all of the shaded resource elements shown in FIG. 5, for example, or whether it can meet the reporting requirements using only a subset of those shaded resource elements.

[0135] In the example illustrated in FIG. 8, at block 812, the sensing node 804 calculates Doppler estimates of a received signal according to the Doppler measurement parameters. Again using FIG. 5 as an example, the sensing node 804 may take measurements for every shaded resource element in FIG, 5, or for only a subset of those shaded resources.

[0136] In the example illustrated in FIG. 8, at block 814, the sensing node 804 reports to the network entity 802 the Doppler estimates according to the Doppler reporting parameters, e.g., using the selected minimum / maximum / granularity values. In some aspects, the granularity of the reported estimates is at least the same or smaller than the one requested by the network entity 802. In some aspects, the maximum estimated velocity / Doppler measurement is equal or larger than tire minimum measurable velocity / Doppler that was requested by the network entity 802. In some aspects, the Doppler estimates reported by the sensing node 804 are wdthin the range of values - larger than VI and smaller than V2 - that were specified by the network entity 802. In some aspects, if the sensing node 804 measures Doppler values less than VI or greater than F2, the sensing node 804 does not report them to the network entity 802.

[0137] When the network entity 802 provides Doppler measurement and reporting parameters for the sensing node 804, the network entity 802. may need to take into account the particular capabilities of the sensing node 804 that it received as part of the Doppler reporting capability message at 806.

[0138] For example, the accuracy of a Doppler estimate measurement may be required to be within ± A'* ty, where Fc= 1 / Tfrm, where Tfrma nommal / effective length of a PRS sample frmthat is being measured, and where k > 1 is an implementation factor representing a sensing node capability, which may depend on the band. X is defined for a specificQC2402142WOQualcomm Ref. No. 2402142WO44channel, e.g., based on additive white Gaussian noise (AWGN) for a given number of PRS samples being used for averaging. Thus, the network entity 802 may specify a Tfrm sufficient to meet a Doppler estimate accuracy requirement.

[0139] However, a sensing node may have a maximum time 7 max, length that the sensing node can perform Doppler or other processing, e.g., due to hardware, processing, or memory storage limitations. Thus, with regards to the nominal / effective length of a PRS sample, for a PRS instance spanning Tinstone, the network entity 802 may specify a Tfrm = Tinstone* if T instance is less than or equal to Tmax, length, and otherwise set 7}™ = Tmaxjength, assuming Rx coherent processing is preserved within theduration.

[0140] In some aspects, Tma^could be a sensing node capability that depends on the band.In some aspects, when the sensing node derives a single Doppler measurement based on multiple PRS resources that have different duration, then the Doppler measurement accuracy is defined as the accuracy corresponding to the least accurate of the different PRS resources (or, in other words, the shortest PRS duration).

[0141] Thus, the accuracy requirements for the Doppler estimate measurement are proportional to an implementation factor / c, a nominal / effective length of the signal being measured Tfrm, and a specific channel factor A, and thus the network entity 802 should consider tire sensing node -specific implementation factor k when preparing the Doppler reporting request.

[0142] In another example, the maximum reported value measurable Doppler may be required to be within ± X * Fr,ax, where J?r, where AT',a nominal / effective time-domain distance between two PRS symbols of a PRS sample in a slot that is being measured, and where k is tin implementation factor and can be a sensing node capability which may depend on the band. X is defined for a specific channel (e.g.. AWGN), for a given number of PRS samples being used for averaging. However, the sensing node 804 may require a minimum distance between consecutive PRS symbols to be measured Nmin. Thus, with regards to the nominal / effective time-domain distance of two PRS symbols of a PRS sample in a slot, for time-domain comb-N, the network entity 802 may specify a value for AT.,,,™ = N • T^,,mhnlfor N > Nmitl. and may specify a value for AT-,,™ =' ^symbol f'oiN ^min- [1)143 ] FIG. 9 is a flowchart of an example process 900 associated with RF sensing, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. QC2402142WOQualcomm Ref. No. 2402142WO459 may be performed by a user equipment (UE) (e.g., UE 104). In some implementations, one or more process blocks of FIG. 9 may be performed by another device or a group of devices separate from or including the UE. Additionally, or alternatively, one or more process blocks of FIG. 9 may be performed by one or more components of UE 302, such as the processor(s) 332, the memory 340, the WWAN transceiver(s) 310, the short-range wireless transceiver(s) 320, the satellite signal receiver 330, the sensor(s) 344, the user interface 346, and the measurement / sensing module(s) 342, any or all of which may be means for performing the operations of process 900.

[0144] As shown in FIG. 9, process 900 may include, at block 910, sending, to a network entity, information indicating Doppler reporting capability. Means for performing the operation of block 910 may include the processor(s) 332, the memory 340, the WWAN transceiver(s) 310, the short-range wireless transceiver(s) 320, the satellite signal interface 330, or the measurement / sensing module(s) 348 of the UE 302. For example, the UE 302 may send the information indicating Doppler reporting capability, using the transniitter(s) 314, the transmitter(s) 324, or the transmitter(s) 334.

[0145] As further shown in FIG. 9, process 900 may include, at block 920, receiving, from the network entity, a Doppler reporting request. Means for performing the operation of block 920 may include the processor(s) 332, the memory'- 340, the WWAN transceiver(s) 310, the short-range wireless transceiver(s) 320, the satellite signal interface 330, or the measurement / sensing module(s) 348 of the UE 302. For example, the UE 302 may' receive the Doppler reporting request, using the receiver(s) 312, the receiver(s) 322, or the receiver) s) 332.

[0146] As further shown in FIG. 9, process 900 may include, at block 930, determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request. Means for performing the operation of block 930 may include the processor(s) 332, the memory 340, or the measurement / sensing module(s) 348 of the UE 302. For example, the UE 302 may' determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request, using the processor) s) 342 or the measurement / sensing module(s) 348.

[0147] As further shown in FIG. 9, process 900 may' include, at block 940, calculating a Doppler estimate of a received signal according to the Doppler measurement parameters. Means for performing the operation of block 940 may include the processor(s) 332, the memory QC2402142WOQualcomm Ref. No. 2402142WO46340, or WWAN transceivers) 310, the short-range wireless transceivers) 320, the satellite signal interface 330, or the measurement / sensing module(s) 348 of the UE 302, For example, the UE 302 may measure the received signal using the receiver(s) 312, the receiver(s) 322, or the receiver(s) 332 and the measurement / sensing module 348 and may calculate a Doppler estimate of a received signal according to the Doppler measurement parameters, using the processor(s) 342 or the measurement / sensing module 348.

[0148] As further shown m FIG. 9, process 900 may include, at block 950, reporting the Doppler estimate to the network entity according to the Doppler reporting parameters. Means for performing the operation of block 950 may include the processor(s) 332, the memory 340, the WWAN transceiver(s) 310, the short-range wireless transceiver(s) 320, the satellite signal interface 330, or tire measurement / sensing module(s) 348 of the UE 302. For example, the UE 302 may report the Doppler estimate to the network entity using the transmitter] s) 314, the transmitter(s) 324, or the transmitters) 334.

[0149] In some aspects, the network entity comprises a location management function (LMF).[015O] In some aspects, the Doppler reporting capability specifies that N number of Doppler frequency values can be calculated for a given measurement type or for an additional path reported relative to the given measurement type. In some aspects, the given measurement type comprises one of a reference signal time delay (RSTD) measurement, a reception and transmission timing difference (Rx-Tx) measurement, or a path reference signal received power (RSRPP) measurement. In some aspects, the Doppler reporting capability is specified for each of a plurality of frequency bands.

[0151] In some aspects, the Doppler reporting request requests that M number of Doppler frequencies should be measured by the UE for each reported path. In some aspects, M = 1. In some aspects, M> 1. In some aspects, the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner to a first Doppler value for a given path, to a center Doppler value for a given path, or to a first / center doppler value of a first path.

[0152] In some aspects, the Doppler reporting request requests that, for each measurement, the UE use a same RF chain, a same reception timing element group (RxTEG), or a same reception and transmission timing element group (RxTxTEG).QC2402142WOQualcomm Ref. No. 2402142WO47

[0153] In some aspects, the Doppler reporting request indicates at least one of a recommended reporting granularity for Doppler frequency values, a minimum Doppler frequency value to be reported, or a maximum Doppler frequency value to be reported.

[0154] In some aspects, calculating the Doppler estimate of the received signal according to the Doppler measurement parameters comprises using same Doppler measurement parameters for all transmission / reception points (TRPs), using a different set of Doppler measurement parameters for each TRP or TRP group, or using a different set of Doppler measurement parameters for each separate measurement. In some aspects, calculating the Doppler estimate of the received signal according to the Doppler measurement parameters comprises using a Doppler measurement parameter specified by the Doppler reporting request. In some aspects, reporting the Doppler estimate to the network entity according to the Doppler reporting parameters comprises using a Doppler reporting parameter specified by the Doppler reporting request,

[0155] Process 900 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG. 9 shows example blocks of process 900, in some implementations, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.9. Additionally, or alternatively, two or more of tire blocks of process 900 may be performed in parallel.

[0156] FIG. 10 is a flowchart of an example process 1000 associated RF sensing, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG.10 may be performed by a network entity (e.g., LMF 270). In some implementations, one or more process blocks of FIG. 10 may be performed by another device or a group of devices separate from or including the network entity. Additionally, or alternatively, one or more process blocks of FIG. 10 may be performed by one or more components of network entity 306, such as the processor(s) 394, the memory 396, the network transcei ver(s) 390, and the measurement / sensing module(s) 398, any or all of which may be means for performing the operations of process 1000.

[0157] As shown in FIG. 10, process 1000 may include, at block 1010, receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node. Means for performing the operation of block 1010 may include the processor(s) 394, the memory 396, the network transceiver(s) 390, or the measurement / sensing module(s) 398 of the QC2402142WOQualcomm Ref. No. 2402142WO48network entity 306. For example, the network entity 306 may receive the first information, using the network transceiver(s) 390.

[0158] As further shown in FIG. 10, process 1000 may include, at block 1020, determining, based on the first information, Doppler measurement and reporting parameters. Means for performing the operation of block 1020 may include the processor(s) 394, the memory 396, the network transceiver(s) 390, or the measurement / sensing module(s) 398 of the network entity 306. For example, the network entity 306 may determine the Doppler measurement and reporting parameters, using tire processor(s) 394 or the measurement / sensing module(s) 398.

[0159] As further shown in FIG. 10, process 1000 may include, at block 1030, sending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters. Means for performing the operation of block 1030 may include tire processor! s) 394, the memory 396, the network transceiver(s) 390, or the measurement / sensing module(s) 398 of the network entity 306. For example, the network entity 306 may send the Doppler reporting request, using the network transceiver! s) 390.

[0160] In some aspects, the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured. In some aspects, determining the effective length of the reference signal to be measured comprises setting the effective length of the reference signal to be measured as the lesser of the actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal. In some aspects, determining the Doppler measurement and reporting parameters comprises determining an accuracy of a Doppler estimate measurement as a factor of at least one of the effective length of tire reference signal to be measured, a signal characteristic of the reference signal to be measured, a processing capacity of the sensing node, or a processing capacity of the sensing node per frequency band. In some aspects, the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0161] In some aspects, the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and reporting parameters comprises determining a minimum QC2402142WOQualcomm Ref. No. 2402142WO49duration of time between symbols of the reference signal to be measured. In some aspects, determining the minimum duration of time between symbols of the reference signal to be measured comprises setting the minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node. In some aspects, determining the Doppler measurement and reporting parameters comprises determining a. maximum measurable Doppler value as a factor of at least one of the minimum duration of time between symbols of the reference signal to be measured, a signal characteristic of the reference signal to be measured, a processing capacity of the sensing node, or a. processing capacity of the sensing node per frequency band. In some aspects, the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0162] Process 1000 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG, 10 shows example blocks of process 1000, in some implementations, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0163] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. Tire various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that QC2402142WOQualcomm Ref. No. 2402142WO50a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

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

[0165] Clause 1. A sensing node, 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, either alone or in combination, configured to: send, via the one or more transceivers, to a network entity, information indicating Doppler reporting capability; receive, from the network entity via the one or more transceivers, a Doppler reporting request; determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculate a Doppler estimate of a received signal according to the Doppler measurement parameters; and report, to the network entity via the one or more transceivers, the Doppler estimate according to the Doppler reporting parameters.

[0166] Clause 2. The sensing node of clause 1, wherein the one or more processors configured to send information indicating Doppler reporting capability to a network entity, comprises the one or more processors, either alone or in combination, configured to send information indicating Doppler reporting capability to a location management function (LMF).

[0167] Clause 3. The sensing node of any of clauses 1 to 2, wherein the Doppler reporting capability specifies that N number of Doppler frequency values can be calculated for a given measurement type or for an additional path reported relative to the given measurement type.

[0168] Clause 4. The sensing node of clause 3, wherein the given measurement type comprises one of: a reference signal time delay (RSTD) measurement; a reception and transmission timing difference (Rx-Tx) measurement; or a path reference signal received power (RSRPP) measurement.

[0169] Clause 5. The sensing node of any of clauses 1 to 4, wherein the Doppler reporting capability is specified for each of a plurality of frequency bands.

[0170] Clause 6. The sensing node of any of clauses 1 to 5, wherein the Doppler reporting request requests that M number of Doppler frequencies should be measured by the sensing node for each reported path.QC2402142WOQualcomm Ref. No. 2402142WO51

[0171] Clause 7. The sensing node of clause 6, wherein M~-= 1.

[0172] Clause 8. The sensing node of any of clauses 6 to 7, wherein M> 1.

[0173] Clause 9. The sensing node of clause 8, wherein the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner, to a first Doppler value for a given path; to a center Doppler value for a given path; or to a firsv’center doppler value of a first path.

[0174] Clause 10. Tire sensing node of any of clauses 1 to 9, wherein the Doppler reporting request requests that, for each measurement, the sensing node use: a same RF chain; a same reception timing element group (RxTEG); or a same reception and transmission timing element group (RxTxTEG).

[0175] Clause 11. Tire sensing node of any of clauses 1 to 10, wherein the Doppler reporting request indicates at least one of: a recommended reporting granularity for Doppler frequency values; a minimum Doppler frequency value to be reported; or a maximum Doppler frequency value to be reported.

[0176] Clause 12. The sensing node of any of clauses 1 to 11, wherein the one or more processors configured to calculate the Doppler estimate of the received signal according to the Doppler measurement parameters comprises the one or more processors, either alone or in combination, configured to: use same Doppler measurement parameters for all transmission / reception points (TRPs); use a different set of Doppler measurement parameters for each TRP or TRP group; or use a different set of Doppler measurement parameters for each separate measurement.

[0177] Clause 13. The sensing node of any of clauses 1 to 12, wherein the one or more processors configured to calculate the Doppler estimate of the received signal according to the Doppler measurement parameters comprises the one or more processors, either alone or in combination, configured to use a Doppler measurement parameter specified by the Doppler reporting request.

[0178] Clause 14. The sensing node of any of clauses I to 13, wherein the one or more processors configured to report the Doppler estimate to the network enti ty according to the Doppler reporting parameters comprises the one or more processors, either alone or in combination, configured to use a Doppler reporting parameter specified by the Doppler reporting request.

[0179] Clause 15. A network entity, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more QC2402142WOQualcomm Ref. No. 2402142WO52memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, from a sensing node via the one or more transceivers, first information indicating Doppler reporting capability of the sensing node; determine, based on the first information, Doppler measurement and reporting parameters; and send, to the sensing node via the one or more transceivers, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0180] Clause 16. The network entity of clause 15, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

[0181] Clause 17. The network entity of clause 16, wherein the one or more processors configured to determine the effective length of the reference signal to be measured comprises the one or more processors, either alone or in combination, configured to set the effective length of the reference signal to be measured as the lesser ofthe actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal.

[0182] Clause 18. The network entity of any of clauses 16 to 17, wherein the one or more processors configured to determine the Doppler measurement and reporting parameters comprises the one or more processors, either alone or in combination, configured to determine an accuracy of a Doppler estimate measurement as a factor of at least one of: the effective length of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity ofthe sensing node per frequency band.

[0183] Clause 19. The network entity of clause 18, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0184] Clause 20. The network entity of any of clauses 15 to 19, wherein the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and reporting parameters comprises determining a minimum duration of time between symbols of the reference signal to be measured.QC2402142WOQualcomm Ref. No. 2402142WO53

[0185] Clause 21. The network entity of clause 20, wherein the one or more processors configured to determine the minimum duration of time between symbols of the reference signal to be measured comprises the one or more processors, either alone or in combination, configured to set the minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node.

[0186] Clause 22. The network entity of any of clauses 20 to 21, wherein the one or more processors configured to determine the Doppler measurement and reporting parameters comprises the one or more processors, either alone or in combination, configured to determine a maximum measurable Doppler value as a factor of at least one of: the minimum duration of time between symbols of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0187] Clause 23. The network entity of clause 22, wherein the signal characteristic of the reference signal to be measured comprises an additive white Csaussian noise (AWGN) value.

[0188] Clause 24. The network entity of any of clauses 15 to 23, wherein the network entity comprises a location management function (LMF) or location server (LS).

[0189] Clause 25. The network entity of any of clauses 15 to 24, wherein the sensing node comprises a user equipment (UE).

[0190] Clause 26. A method of radio frequency (RF) sensing performed by a sensing node, the method comprising: sending, to a network entity, information indicating Doppler reporting capability; receiving, from the network entity, a Doppler reporting request; determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculating a Doppler estimate of a received signal according to the Doppler measurement parameters; and reporting the Doppler estimate to the network entity according to the Doppler reporting parameters.

[0191] Clause 27. The method of clause 26, wherein the network entity comprises a location management function (LMF).

[0192] Clause 28. The method of any of clauses 26 to 27, wherein the Doppler reporting capability specifies that N number of Doppler frequency values can be calculated for a QC2402142WOQualcomm Ref. No. 2402142WO54given measurement type or for an additional path reported relative to the given measurement type.

[0193] Clause 29. The method of clause 28, wherein the given measurement type comprises one of: a reference signal time delay (RSTD) measurement; a reception and transmission timing difference (Rx-Tx) measurement; or a path reference signal received power (RSRPP) measurement.

[0194] Clause 30. Tire method of any of clauses 26 to 29, wherein the Doppler reporting capability is specified for each of a plurality of frequency bands.

[0195] Clause 31. The method of any of clauses 26 to 30, wherein the Doppler reporting request requests that M number of Doppler frequencies should be measured by the sensing node for each reported path.

[0196] Clause 32. The method of clause 31, wherein M = 1.

[0197] Clause 33, The method of any of clauses 31 to 32, wherein M > 1.

[0198] Clause 34. The method of clause 33, wherein the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner: relative to a first Doppler value for a given path; relative to a center Doppler value for a given path; or relative to a first / center doppler value of a first path.

[0199] Clause 35. The method of any of clauses 26 to 34, wherein the Doppler reporting request requests that, for each measurement, the sensing node use: a same RF chain; a same reception timing element group (RxTEG); or a same reception and transmission timing element group (RxTxTEG).

[0200] Clause 36. The method of any of clauses 26 to 35, wherein the Doppler reporting request indicates at least one of: a recommended reporting granularity for Doppler frequency values; a minimum Doppler frequency value to be reported; or a maximum Doppler frequency value to be reported.

[0201] Clause 37. The method of any of clauses 26 to 36, wherein calculating the Doppler estimate of the received signal according to the Doppler measurement parameters comprises: using same Doppler measurement parameters for all transmission / reception points (TRPs); using a different set of Doppler measurement parameters for each TRP or TRP group; or using a different set of Doppler measurement parameters for each separate measurement.

[0202] Clause 38. Tire method of any of clauses 26 to 37, wherein calculating the Doppler estimate of the received signal according to the Doppler measurement parameters QC2402142WOQualcomm Ref. No. 2402142WO55comprises using a Doppler measurement parameter specified by the Doppler reporting request.

[0203] Clause 39. The method of any of clauses 26 to 38, wherein reporting the Doppler estimate to the network entity according to the Doppler reporting parameters comprises using a Doppler reporting parameter specified by the Doppler reporting request.

[0204] Clause 40. A method of radio frequency (RF) sensing performed by a network entity, the method comprising: receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node: determining, based on the first information, Doppler measurement and reporting parameters; and sending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0205] Clause 41. The method of clause 40, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

[0206] Clause 42. The method of clause 41, wherein determining the effective length of the reference signal to be measured comprises setting the effective length of the reference signal to be measured as the lesser of the actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal.

[0207] Clause 43. The method of any of clauses 41 to 42, wherein determining the Doppler measurement and reporting parameters comprises determining an accuracy of a Doppler estimate measurement as a factor of at least one of the effective length of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0208] Clause 44. The method of clause 43, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0209] Clause 45. The method of any of clauses 40 to 44, wherein the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and reportingQC2402142WOQualcomm Ref. No. 2402142WO56parameters comprises determining a minimum duration of time between symbols of the reference signal to be measured.

[0210] Clause 46. The method of clause 45, wherein determining the minimum duration of time between symbols of the reference signal to be measured comprises setting the minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node.

[0211] Clause 47. The method of any of clauses 45 to 46, wherein determining the Doppler measurement and reporting parameters comprises determining a maximum measurable Doppler value as a factor of at least one of: the minimum duration of time between symbols of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0212] Clause 48. The method of clause 47, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0213] Clause 49. The method of any of clauses 40 to 48, wherein the network entity comprises a location management function (LMF) or location server (LS).

[0214] Clause 50. The method of any of clauses 40 to 49, wherein the sensing node comprises a user equipment (UE).

[0215] Clause 51. A sensing node, comprising: means for sending, to a network entity, information indicating Doppler reporting capability; means for receiving, from the network entity, a Doppler reporting request; means for determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; means for calculating a Doppler estimate of a received signal according to the Doppler measurement parameters; and means for reporting the Doppler estimate to the network entity according to the Doppler reporting parameters.

[0216] Clause 52. The sensing node of clause 51, wherein the network entity comprises a location management function (LMF).

[0217] Clause 53. The sensing node of any of clauses 51 to 52, wherein the Doppler reporting capabili ty specifies that N number of Doppler frequency values can be calculated for aQC2402142WOQualcomm Ref. No. 2402142WO57given measurement type or for an additional path reported relative to the given measurement type.

[0218] Clause 54. The sensing node of clause 53, wherein the given measurement type comprises one of: a reference signal time delay (RSTD) measurement; a reception and transmission timing difference (Rx-Tx) measurement; or a path reference signal received power (RSRPP) measurement.

[0219] Clause 55. The sensing node of any of clauses 51 to 54, wherein the Doppler reporting capability is specified for each of a plurality of frequency bands.

[0220] Clause 56. The sensing node of any of clauses 51 to 55, wherein the Doppler reporting request requests that M number of Doppler frequencies should be measured by the sensing node for each reported path.

[0221] Clause 57. lire sensing node of clause 56, wherein1.

[0222] Clause 58, The sensing node of any of clauses 56 to 57, wherein M> 1.

[0223] Clause 59. The sensing node of clause 58, wherein the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner: means for to a first Doppler value for a given path; means for to a center Doppler value for a given path; or means for to a first / center doppler value of a first path.

[0224] Clause 60. The sensing node of any of clauses 51 to 59, wherein the Doppler reporting request requests that, for each measurement, the sensing node use: a same RF chain; a same reception timing element group (RxTEG); or a same reception and transmission timing element group (RxTxTEG).

[0225] Clause 61. The sensing node of any of clauses 51 to 60, wherein the Doppler reporting request indicates at least one of: a recommended reporting granularity' for Doppler frequency values; a minimum Doppler frequency value to be reported; or a maximum Doppler frequency value to be reported.

[0226] Clause 62. The sensing node of any of clauses 51 to 61, wherein tire means for calculating the Doppler estimate of the received signal according to the Doppler measurement parameters comprises: means for using same Doppler measurement parameters for all transmission / reception points (TRPs); means for using a different set of Doppler measurement parameters for each TRP or TRI’ group; or means for using a different set of Doppler measurement parameters for each separate measurement.

[0227] Clause 63. Tire sensing node of any of clauses 51 to 62, wherein the means for calculating the Doppler estimate of the received signal according to the Doppler measurement QC2402142WOQualcomm Ref. No. 2402142WO58parameters comprises means for using a Doppler measurement parameter specified by the Doppler reporting request.

[0228] Clause 64. The sensing node of any of clauses 51 to 63, wherein the means for reporting the Doppler estimate to the network entity according to the Doppler reporting parameters comprises means for using a Doppler reporting parameter specified by the Doppler reporting request.

[0229] Clause 65. A network entity, comprising: means for receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node: means for determining, based on the first information, Doppler measurement and reporting parameters; and means for sending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0230] Clause 66. lire network entity of clause 65, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

[0231] Clause 67. The network entity of clause 66, wherein the means for determining the effective length of the reference signal to be measured comprises means for setting the effective length of the reference signal to be measured as the lesser of the actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal.

[0232] Clause 68. The network entity of any of clauses 66 to 67, wherein the means for determining the Doppler measurement and reporting parameters comprises means for determining an accuracy of a Doppler estimate measurement as a factor of at least one of the effective length of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0233] Clause 69. The network entity of clause 68, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0234] Clause 70. The network entity of any of clauses 65 to 69, wherein the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and QC2402142WOQualcomm Ref. No. 2402142WO59reporting parameters comprises determining a minimum duration of time between symbols of the reference signal to be measured.

[0235] Clause 71. The network entity of clause 70, wherein the means for determining the minimum duration of time between symbols of the reference signal to be measured comprises means for setting tire minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node.

[0236] Clause 72. The network entity of any of clauses 70 to 71, wherein the means for determining the Doppler measurement and reporting parameters comprises means for determining a maximum measurable Doppler value as a factor of at least one of: the minimum duration of time between symbols of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0237] Clause 73. The network entity of clause 72, wherein the signal characteristic of the reference signal to be measured comprises an additive white Csaussian noise (AWGN) value.

[0238] Clause 74. The network entity of any of clauses 65 to 73, wherein the network entity comprises a location management function (LMF) or location server (LS).

[0239] Clause 75. The network entity of any of clauses 65 to 74, wherein the sensing node comprises a user equipment (UE).

[0240] Clause 76. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sensing node, cause the sensing node to: send, to a network entity, information indicating Doppler reporting capability; receive, from the network entity, a Doppler reporting request; determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request; calculate a Doppler estimate of a received signal according to the Doppler measurement parameters; and report the Doppler estimate to the network entity according to the Doppler reporting parameters.

[0241] Clause 77. The non-transitory computer-readable medium of clause 76, wherein the network entity comprises a location management function (LMF).

[0242] Clause 78. The non-transitory computer-readable medium of any of clauses 76 to 77, wherein the Doppler reporting capability specifies that N number of Doppler frequency QC2402142WOQualcomm Ref. No. 2402142WO60values can be calculated for a given measurement type or for an additional path reported relative to the given measurement type.

[0243] Clause 79. The non-transitory computer-readable medium of clause 78, wherein the given measurement type comprises one of: a reference signal time delay (RSTD) measurement; a reception and transmission timing difference (Rx-Tx) measurement; or a path reference signal received power (RSRPP) measurement.

[0244] Clause 80. The non-transitory computer-readable medium of any of clauses 76 to 79, wherein the Doppler reporting capability is specified for each of a plurality of frequency bands.

[0245] Clause 81. The non-transitory computer-readable medium of any of clauses 76 to 80, wherein the Doppler reporting request requests that M number of Doppler frequencies should be measured by the sensing node for each reported path.

[0246] Clause 82, The non-transitory computer-readable medium of clause 81, wherein M= 1.

[0247] Clause 83. The non-transitory computer-readable medium of any of clauses 81 to 82, wherein M> 1.

[0248] Clause 84. The non-transitory computer-readable medium of clause 83, wherein the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner: to a first Doppler value for a given path; to a center Doppler value for a given path; or to a first / center doppler value of a first path.

[0249] Clause 85. The non-transitory computer-readable medium of any of clauses 76 to 84, wherein the Doppler reporting request requests that, for each measurement, the sensing node use: a same RF chain; a same reception timing element group (RxTEG); or a same reception and transmission timing element group (RxTxTEG).

[0258] Clause 86. The non-transitory computer-readable medium of any of clauses 76 to 85, wherein the Doppler reporting request indicates at least one of: a recommended reporting granularity for Doppler frequency values; a minimum Doppler frequency value to be reported; or a maximum Doppler frequency value to be reported.

[0251] Clause 87. The non-transitory computer-readable medium of any of clauses 76 to 86, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to calculate the Doppler estimate of the received signal according to the Doppler measurement parameters comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to: use same Doppler measurement parameters for all transmission / reception points (TRPs); use a different set QC2402142WOQualcomm Ref. No. 2402142WO61of Doppler measurement parameters for each TRP or TRP group; or use a different set of Doppler measurement parameters for each separate measurement,

[0252] Clause 88. The non-transitory computer-readable medium of any of clauses 76 to 87, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to calculate the Doppler estimate of the received signal according to the Doppler measurement parameters comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to use a Doppler measurement parameter specified by the Doppler reporting request.

[0253] Clause 89. The non-transitory computer-readable medium of any of clauses 76 to 88, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to report the Doppler estimate to the network entity according to the Doppler reporting parameters comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to use a Doppler reporting parameter specified by the Doppler reporting request.

[0254] Clause 90. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity’ to: receive, from a sensing node, first information indicating Doppler reporting capability of the sensing node; determine, based on the first information, Doppler measurement and reporting parameters; and send, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

[0255] Clause 91. The non-transitory computer-readable medium of clause 90, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

[0256] Clause 92. Hie non-transitory computer-readable medium of clause 91, wherein the computer-executable instructions that, when executed by the network entity’, cause the network entity to determine the effective length of the reference signal to be measured comprise computer-executable instructions that, when executed by the network entity, cause the network entity to set the effective length of tire reference signal to be measured as the lesser of the actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal.QC2402142WOQualcomm Ref. No. 2402142WO

[0257] Clause 93. 'The non-transitory computer-readable medium of any of clauses 91 to 92, wherein the computer-executable instructions that, when executed by the network entity7, cause the network entity to determine the Doppler measurement and reporting parameters comprise computer-executable instructions that, when executed by the network entity, cause the network entity to determine an accuracy of a Doppler estimate measurement as a factor of at least one of: the effective length of the reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.

[0258] Clause 94. The non-transitory computer-readable medium of clause 93, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0259] Clause 95. The non-transitory computer-readable medium of any of clauses 90 to 94, wherein the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and reporting parameters comprises determining a minimum duration of time between symbols of the reference signal to be measured,

[0260] Clause 96. The non-transitory computer-readable medium of clause 95, wherein the computer-executable instructions that, when executed by the network entity, cause the network entity to determine the minimum duration of time between symbols of the reference signal to be measured comprise computer-executable instructions that, when executed by the network entity, cause the network entity to set the minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node.

[0261] Clause 97. The non-transitory computer-readable medium of any of clauses 95 to 96, wherein the computer-executable instructions that, when executed by the network entity, cause the network entity to determine the Doppler measurement and reporting parameters comprise computer-executable instructions that, when executed by the network entity, cause the network entity to determine a maximum measurable Doppler value as a factor of at least one of: the minimum duration of time between symbols of tire reference signal to be measured; a signal characteristic of the reference signal to be measured; a processing capacity of the sensing node; or a processing capacity of the sensing node per frequency band.QC2402142WOQualcomm Ref. No. 2402142WO63

[0262] Clause 98. The non-transitory computer-readable medium of clause 97, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

[0263] Clause 99. The non-transitory computer-readable medium of any of clauses 90 to 98, wherein the network entity comprises a location management function (LMF) or location server (LS).

[0264] Clause 100. The non-transitory' computer-readable medium of any of clauses 90 to 99, wherein the sensing node comprises a user equipment (UE).

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

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

[0267] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-progra.ma.ble gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing QC2402142WOQualcomm Ref. No. 2402142WO64devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0268] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory', read-only memory' (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

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

[0270] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. For example, the functions, steps and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Further, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination.QC2402142WO

Claims

Qualcomm Ref. No. 2402142WO66CLAIMSWhat is claimed is:

1. A sensing node, comprising:one or more memories;one or more transceivers; andone or more processors commu icatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to:cause the sensing node to send, via the one or more transceivers, to a network entity, information indicating Doppler reporting capability;receive, from the network entity via the one or more transceivers, a Doppler reporting request;determine Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request;calculate a Doppler estimate of a received signal according to the Doppler measurement parameters; andcause the sensing node to report, to the network entity via the one or more transceivers, tire Doppler estimate according to tire Doppler reporting parameters.

2. The sensing node of claim 1, wherein the one or more processors configured to send information indicating Doppler reporting capability to a network entity, comprises the one or more processors, either alone or in combination, configured to send information indicating Doppler reporting capability to a location management function (LMF).

3. The sensing node of claim 1, wherein the Doppler reporting capability specifies that N number of Doppler frequency values can be calculated for a given measurement type or for an additional path reported relative to the given measurement type.

4. The sensing node of claim 3, wherein the given measurement type comprises one of:QC2402142WOQualcomm Ref. No. 2402142WO67a reference signal time delay (RSTD) measurement;a reception and transmission timing difference (Rx-Tx) measurement; or a path reference signal received power (RSRPP) measurement.

5. The sensing node of claim 1, wherein the Doppler reporting capability is specified for each of a plurality of frequency bands.

6. lire sensing node of claim 1, wherein the Doppler reporting request requests that M number of Doppler frequencies should be measured by the sensing node for each reported path, wherein M= 1 orM > 1.

7. The sensing node of claim 6. wherein M> 1 and wherein the Doppler reporting request requests that multiple Doppler frequency values be reported in a differential manner:to a first Doppler value for a given path;to a center Doppler value for a given path; orto a first / center doppler value of a first path.

8. The sensing node of claim 1, wherein the Doppler reporting request requests that, for each measurement, the sensing node use:a same RF chain;a same reception timing element group (RxTEG); ora same reception and transmission timing element group (RxTxTEG).

9. The sensing node of claim 1, wherein the Doppler reporting request indicates at least one of:a recommended reporting granularity for Doppler frequency values;a minimum Doppler frequency value to be reported; ora maximum Doppler frequency value to be reported.

10. The sensing node of claim 1, wherein the one or more processors configured to calculate the Doppler estimate of the received signal according to the DopplerQC2402142WOQualcomm Ref. No. 2402142WO68measurement parameters comprises the one or more processors, either aione or in combination, configured to:use same Doppler measurement parameters for all transmission / reception points (TRPs );use a different set of Doppler measurement parameters for each TRP or TRP group; oruse a different set of Doppler measurement parameters tor each separate measurement.

11. The sensing node of claim 1, wherein the one or more processors configured to calculate the Doppler estimate of the received signal according to the Doppler measurement parameters comprises the one or more processors, either alone or in combination, configured to use a Doppler measurement parameter specified by the Doppler reporting request.

12. The sensing node of claim 1, wherein the one or more processors configured to report the Doppler estimate to the network entity according to the Doppler reporting parameters comprises the one or more processors, either alone or in combination, configured to use a Doppler reporting parameter specified by the Doppler reporting request.

13. A netw ork entity, comprisin:one or more memories;one or more transceivers; andone or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or m co bination, configured to:receive, from a. sensing node via the one or more transceivers, first information indicating Doppler reporting capability of the sensing node;determine, based on the first information, Doppler measurement and reporting parameters; andQC2402142WOQualcomm Ref. No. 2402142WO69cause the network entity to send, to the sensing node via the one or more transceivers, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

14. The network entity of claim 13, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

15. The network entity of claim 14, wherein the one or more processors configured to determine the effective length of the reference signal to be measured comprises the one or more processors, either alone or in combination, configured to set the effective length of the reference signal to be measured as the lesser of the actual length of the reference signal to be measured and the maximum duration of time during which the sensing node can process Doppler measurements for each reference signal.

16. Ttie network entity of claim 14, wherein the one or more processors configured to determine the Doppler measurement and reporting parameters comprises the one or more processors, either alone or in combination, configured to determine an accuracy of a Doppler estimate measurement as a factor of at least one of:the effective length of the reference signal to be measured;a signal characteristic of the reference signal to be measured;a processing capacity of the sensing node; ora processing capacity of the sensing node per frequency band.17, The network entity’ of claim 16, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

18. lire network entity of claim 13, wherein the first information comprises a minimum duration of time required between symbols of a signal to be measured by the sensing node and wherein determining the Doppler measurement and reportingQC2402142WOQualcomm Ref. No. 2402142WO70parameters comprises determining a minimum duration of time between symbols of the reference signal to be measured.

19. The network entity of claim 18, wherein the one or more processors configured to determine the minimum duration of time between symbols of the reference signal to be measured comprises the one or more processors, either alone or in combination, configured to set the minimum duration of time between symbols of the reference signal to be measured to the greater of a default duration of time between symbols of the reference signal and the minimum duration of time required between symbols of a signal to be measured by the sensing node.

20. The network entity of claim 18, wherein the one or more processors configured to deter ine the Doppler measurement and reporting parameters comprises the one or more processors, either alone or in combination, configured to determine a maximum measurable Doppler value as a factor of at least one of:the minimum duration of time between symbols of the reference signal to be measured;a signal characteristic of the reference signal to be measured;a processing capacity of the sensing node; ora processing capacity' of the sensing node per frequency- band.

21. The network entity of claim 20, wherein the signal characteristic of the reference signal to be measured comprises an additive white Gaussian noise (AWGN) value.

22. The network entity of claim 13, wherein the network entity comprises a location management function (LMF) or location server (LS).

23. The netw'ork entity of claim 13, wherein the sensing node comprises a user equipment (UE).

24. A method of radio frequency- (RF) sensing performed by a sensing node, the method comprising:QC2402142WOQualcomm Ref. No. 2402142WOsending, to a network entity, information indicating Doppler reporting capability;receiving, from the network entity, a Doppler reporting request; determining Doppler measurement parameters and Doppler reporting parameters to be used based on the Doppler reporting capability and the Doppler reporting request;calculating a Doppler estimate of a received signal according to the Doppler measurement parameters; andreporting the Doppler estimate to the network entity according to the Doppler reporting parameters.

25. The method of claim 24, wherein at least one of:the Doppler reporting capability specifies that N number of Doppler frequency values can be calculated for a given measurement type or for an additional path reported relative to the given measurement type; orthe Doppler reporting capability is specified for each of a plurality of frequency bands.

26. The method of claim 24, wherein at least one of:the Doppler reporting request requests that, for each measurement, the sensing node use at least one of a same RF chain, a same reception timing element group (RxTEG), or a same reception and transmission timing element group (RxTxTEG); or the Doppler reporting request indicates at least one of a recommended reporting granularity for Doppler frequency values, a minimum Doppler frequency value to be reported, or a maximum Doppler frequency value to be reported.

27. The method of claim 24, wherein calculating the Doppler estimate of the received signal according to the Doppler measurement parameters comprises:using same Doppler measurement parameters for all transmission / reception points (TRPs);using a different set of Doppler measurement parameters for each TRI’ or TRP group; orusing a different set of Doppler measurement parameters for each separate measurement.QC2402142WOQualcomm Ref. No. 2402142WO28. A method of radio frequency (RF) sensing performed by a network entity; the method comprising:receiving, from a sensing node, first information indicating Doppler reporting capability of the sensing node;determining, based on the first information, Doppler measurement and reporting parameters; andsending, to the sensing node, a Doppler reporting request comprising the Doppler measurement and reporting parameters.

29. The method of claim 28, wherein the first information comprises a maximum duration of time during which the sensing node can process Doppler measurements for each reference signal and wherein determining the Doppler measurement and reporting parameters comprises determining an effective length of a reference signal to be measured.

30. The method of claim 28, wherein determining the Doppler measurement and reporting parameters comprises determining an accuracy of a Doppler estimate measurement as a factor of at least one of:an effective length of the reference signal to be measured;a signal characteristic of the reference signal to be measured;a processing capacity of the sensing node; ora processing capacity of the sensing node per frequency band.QC2402142WO

Images