DOPPLER ERROR GROUPS FOR CELLULAR-BASED RADIO FREQUENCY SENSING

In an aspect, a wireless entity may transmit a first indication of one or more Doppler error group (DEG) identifiers (IDs) corresponding to one or more DEGs supported by the wireless entity, where each of the one or more DEGs is associated with a hardware configuration or an operational state of the wireless entity. The wireless entity may transmit a first set of measurements associated with a DEG ID of the one or more DEG IDs.

TECHNICAL FIELD

The present disclosure relates generally to positioning systems, and more particularly, to positioning systems involving radio frequency sensing.

INTRODUCTION

BRIEF SUMMARY

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include memory and at least one processor coupled to the memory. The at least one processor, based at least in part on information stored in the memory may be configured to transmit a first indication of one or more Doppler error group (DEG) identifiers (IDs) corresponding to one or more DEGs supported by the wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, and to transmit a set of measurements associated with a DEG ID of the DEG ID(s).

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include memory and at least one processor coupled to the memory. The at least one processor, based at least in part on information stored in the memory may be configured to receive an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, to receive a set of measurements associated with a DEG ID of the DEG ID(s), and to derive a sensing result based at least partially on the DEG ID.

DETAILED DESCRIPTION

Various aspects relate generally to positioning systems. Some aspects more specifically relate to radio frequency (RF) sensing utilizing one or more Doppler error groups (DEGs). In some examples, a wireless entity (e.g., a sensing node) may provide an indication of one or more DEG identifiers (IDs) corresponding to DEG(s) supported by the wireless entity. Each of the DEG ID(s) indicates a particular hardware configuration (e.g., an indication of one or more oscillators utilized by the wireless entity) and/or an operational state supported by the wireless entity. The wireless entity may perform a set of measurements for a target entity. The wireless entity may provide the set of measurements to a network entity (e.g., a base station, a network node, a sensing management function (SnMF), etc.), along with a particular DEG ID that identifies the DEG (or hardware configuration and/or operational state) utilized when performing the set of measurements. The network entity may derive a sensing result (e.g., a position, a velocity, etc.) for a target entity based at least on the DEG ID (e.g., based on the DEG ID and the set of measurements).

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 deriving the sensing result based on the DEG ID, the network entity may determine the hardware configuration and/or operational state of the wireless entity and accurately remove the estimation bias caused by the oscillator error associated with the hardware configuration and/or operational state. By doing so, the network entity may more accurately estimate the Doppler shift of the target entity, and therefore, more accurately determine a sensing result for the target entity.

The SMO Framework105may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework105may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1interface). For virtualized network elements, the SMO Framework105may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud)190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2interface). Such virtualized network elements can include, but are not limited to, CUs110, DUs130, RUs140and Near-RT RICs125. In some implementations, the SMO Framework105can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB)111, via an O1interface. Additionally, in some implementations, the SMO Framework105can communicate directly with one or more RUs140via an O1interface. The SMO Framework105also may include a Non-RT RIC115configured to support functionality of the SMO Framework105.

The core network120may include an Access and Mobility Management Function (AMF)161, a Session Management Function (SMF)162, a User Plane Function (UPF)163, a Unified Data Management (UDM)164, one or more location servers168, and other functional entities. The AMF161is the control node that processes the signaling between the UEs104and the core network120. The AMF161supports registration management, connection management, mobility management, and other functions. The SMF162supports session management and other functions. The UPF163supports packet routing, packet forwarding, and other functions. The UDM164supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers168are illustrated as including a Gateway Mobile Location Center (GMLC)165and a Location Management Function (LMF)166, and a Sensing Management Function (SnMF)167. However, generally, the one or more location servers168may include one or more location/positioning servers, which may include one or more of the GMLC165, the LMF166, the SnMF167, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC165, the LMF166, and the SnMF167support UE location services. The GMLC165provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF166receives measurements and assistance information from the NG-RAN and the UE104via the AMF161to compute the position of the UE104. The SnMF167receives measurements and/or additional information from a sensing node and determines a sensing result (e.g., a position of a target entity) based on the measurements and/or additional information. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE104. Positioning the UE104may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE104and/or the base station102serving the UE104. The signals measured may be based on one or more of a satellite positioning system (SPS)170(e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.

Referring again toFIG.1, in certain aspects, the UE104may have a DEG transmission component198that may be configured to transmit a first indication of DEG ID(s) corresponding to DEG(s) supported by the wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, and to transmit a first set of measurements associated with a DEG ID of the DEG ID(s). In certain aspects, the base station102and/or the SnMF167may have a DEG reception component199that may be configured to receive an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, to receive a set of measurements associated with a DEG ID of the DEG ID(s), and to derive a sensing result based at least partially on the DEG ID.

FIG.4is a diagram400illustrating an example of a UE positioning based on reference signal measurements. The UE404may transmit UL-SRS412at time TSRS_TXand receive DL positioning reference signals (PRS) (DL-PRS)410at time TPRS_RX. The TRP406may receive the UL-SRS412at time TSRS_RXand transmit the DL-PRS410at time TPRS_TX. The UE404may receive the DL-PRS410before transmitting the UL-SRS412, or may transmit the UL-SRS412before receiving the DL-PRS410. In both cases, a positioning server (e.g., location server(s)168) or the UE404may determine the RTT414based on ∥TSRS_RX−TPRS_TX|−|TSRS_TX−TPRS_RX∥. Accordingly, multi-RTT positioning may make use of the UE Rx-Tx time difference measurements (i.e., |TSRS_TX−TPRS_RX|) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP) of downlink signals received from multiple TRPs402,406and measured by the UE404, and the measured TRP Rx-Tx time difference measurements (i.e., |TSRS_RX−TPRS_TX|) and UL-SRS-RSRP at multiple TRPs402,406of uplink signals transmitted from UE404. The UE404measures the UE Rx-Tx time difference measurements (and optionally DL-PRS-RSRP of the received signals) using assistance data received from the positioning server, and the TRPs402,406measure the gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP of the received signals) using assistance data received from the positioning server. The measurements may be used at the positioning server or the UE404to determine the RTT, which is used to estimate the location of the UE404. Other methods are possible for determining the RTT, such as for example using DL-TDOA and/or UL-TDOA measurements.

DL-AoD positioning may make use of the measured DL-PRS-RSRP of downlink signals received from multiple TRPs402,406at the UE404. The UE404measures the DL-PRS-RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with the azimuth angle of departure (A-AoD), the zenith angle of departure (Z-AoD), and other configuration information to locate the UE404in relation to the neighboring TRPs402,406.

DL-TDOA positioning may make use of the DL reference signal time difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received from multiple TRPs402,406at the UE404. The UE404measures the DL RSTD (and optionally DL-PRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE404in relation to the neighboring TRPs402,406.

UL-TDOA positioning may make use of the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) at multiple TRPs402,406of uplink signals transmitted from UE404. The TRPs402,406measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE404.

UL-AoA positioning may make use of the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) at multiple TRPs402,406of uplink signals transmitted from the UE404. The TRPs402,406measure the A-AoA and the Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE404.

Additional positioning methods may be used for estimating the location of the UE404, such as for example, UE-side UL-AoD and/or DL-AoA. Note that data/measurements from various technologies may be combined in various ways to increase accuracy, to determine and/or to enhance certainty, to supplement/complement measurements, and/or to substitute/provide for missing information.

In addition to network-based UE positioning technologies, a wireless device (e.g., a UE, an access point (AP), etc.) may also be configured to include sensing capabilities, where the wireless device may be able to sense (e.g., detect and/or track) one or more objects of an area or in an environment based on radio frequencies. An environment may refer to a particular geographical area or place, especially as affected by human activity, or the circumstances, objects, or conditions by which one is surrounded. For example, a wireless device may include a radar capability (which may be referred to as “RF sensing” and/or “cellular-based RF sensing), where the wireless device may transmit reference signals (e.g., radar reference signals (RRSs)) and measure the reference signals reflected from one or more objects (e.g., structures, walls, living objects, and/or things in an environment, etc.). Based on the measurement, the wireless device may determine or estimate a distance between the wireless device and the one or more objects and/or obtain environmental information associated with its surrounding. In another example, a first wireless device may receive signals transmitted from a second wireless device, where the first wireless device may determine or estimate a distance between the first wireless device and the second wireless device based on the received signals. For example, a tracking device (e.g., a Bluetooth tracker, an item tracker, an asset tracking device, etc.) may be configured to regularly transmit signals (e.g., beacon signals) or small amounts of data to a receiving device, such that the receiving device may be able to monitor the location or the relative distance of the tracking device. As such, a user may be able to track the location of an item (e.g., a car key, a wallet, a remote control, etc.) by attaching the tracking device to the item. For purposes of the present disclosure, a device/apparatus that is capable of performing sensing (e.g., transmitting and/or receiving signals for detecting at least one object or for estimating the distance between the device and the at least one object) may be referred to as a “sensing device” or a “sensing node.” For example, a sensing device may be a UE, an AP device (e.g., a Wi-Fi router), a base station, a component of the base station, a TRP, a device capable of performing radar functions, etc. In addition, a device/apparatus that is capable of transmitting signals to a sensing device for the sensing device to determine the location or the relative distance of the device/apparatus may be referred to as a “tracking device,” a “tracker,” or a “tag.”

In practice, the transmitting device and/or receiving device in a sensing system may include an oscillator error. For example, oscillators in such devices are typically not temperature controlled, and therefore, may introduce sizable errors in the generated frequency, which varies throughout the day depending on the temperature. Other sources may also contribute to oscillator errors. Accordingly, when a frequency offset of an RF sensing signal received by a device, such as a UE, is measured by the UE, the frequency offset includes not just the Doppler shift induced by the target object, but also a sizable oscillator error. Similarly, the frequency offset of an RF sensing signal that was transmitted by a UE and received by another device, such as a base station, will also include not just the Doppler shift induced by the target object, but also the oscillator error caused by the oscillator of the base station.

In wireless communications, the receiving device does not attempt to distinguish the Doppler shift from the oscillator errors. In wireless communications, the sum of the Doppler shift and oscillator error are estimated and compensated for by employing frequency tracking loop (FTL), which leads to satisfactory modem performance.

However, for RF sensing, it is desirable to accurately determine the Doppler shift introduced by the target object in order to determine the motion of the target object itself. Aspects of the present disclosure are directed to mitigating the Doppler measurement error in RF sensing, for example, by removing the estimation bias caused by the oscillator error from the total frequency offset estimate (including both Doppler shift and oscillator error) in order to obtain accurate Doppler shift estimates.

Sensing nodes may use different groups of transmit chains (that utilize a first set of one or more oscillators) and receive chains (that utilize a second set of one or more oscillators). For example, a first sensing node may include a first transmit chain that utilizes a first set of oscillator(s) and may include a first receive chain that utilizes a second set of oscillator(s), and a second sensing node may include a second transmit chain that utilizes a third set of oscillator(s) and may include a second receive chain that utilizes a fourth set of oscillator(s). In some aspects, a sensing node may utilize the same oscillators for both its transmit chain and receive chain. In other aspects, a sensing node may utilize different oscillators for its transmit chain and receive chain.

A sensing node may perform measurements based on reference signal(s) received thereby. From the measurements, the sensing node may identify clustered Doppler measurements utilizing the same received samples. This is mainly due to utilizing different hardware (e.g., of its receive chain) to process the same received samples.

The hardware difference may be from the usage of different oscillators. For instance, some hardware architectures may be designed/utilized for particular purposes or as a cost-savings measure. Even if the same set of hardware is utilized, the clustered Doppler measurement error may vary over different operational states. For example, if the sensing node switches form a power savings mode to a regular (or normal) mode, the hardware configuration may change. For instance, the sensing node may switch from utilizing a power efficient oscillator to a standard oscillator (e.g., when switching to the normal mode), or vice versa (e.g., when switching to the power savings mode).

In accordance with various aspects of the present disclosure, one or more Doppler error groups (DEGs) may be defined and utilized in cellular systems for RF sensing purposes. The DEGs may be motivated by the strong correlation between the hardware architecture and configurations and/or the operational state of the sensing node. Each of the DEGs represent a Doppler error attributed to particular hardware configuration and/or operational state of a sensing node utilized when performing positioning and/or sensing measurements. In some aspects, the hardware configuration corresponds to the oscillators for the transmit chain and the receive chain of the sensing node. In some aspects, the operational state may correspond to at least one of a power state (e.g., a power on state (or mode), a low power state (or power savings mode), a standby state (or mode)) of the sensing node or a temperature (or temperature range) of the sensing node.

A sensing node may be associated with one or more DEGs. For example, a sensing node may be associated with a transmit DEG. The transmit DEG may be correlated to the hardware configuration selection (e.g., selection of hardware components) for the transmit chain of the sensing node. In another example, a sensing node may be associated with a receive DEG. The receive DEG may be correlated to the hardware configuration selection (e.g., selection of hardware components) for the receive chain of the sensing node. In a further example, a sensing node may be associated with a transmit-receive DEG. The transmit-receive DEG may be correlated to the hardware configuration selection (e.g., selection of hardware components) for both the transmit chain and the receive chain of the sensing node. In yet a further example, a sensing node may be associated with a temperature-based DEG, where the DEG is correlated with one or more operating temperatures of the sensing node (e.g., if the sensing node is equipped with a temperature sensor). In a further example, a sensing node may be associated with a carrier component-based DEG, where the DEG corresponds to a carrier component by which the DEG transmits and/or receives signals. A carrier component-based DEG may be per carrier component. That is, a sensing node may be associated with a plurality of carrier component-based DEGs, where each such DEG corresponds to a particular carrier component utilized by the sensing node.

A sensing node may be configured to indicate the DEG(s) associated therewith, for example, to a network node or a UE. By indicating its DEG(s), the sensing node may not need to disclose its particular hardware implementation. However, it is noted that a sensing node may disclose (e.g., signal) its particular hardware implementation, which may be utilized by the core network, a network node, or a UE to implement certain advance features for Doppler measurement error mitigation.

In accordance with various aspects of the present disclosure, enhancements to RF sensing measurement reports are also provided. For example, in some aspects, if the sensing measurement is channel estimation-based (e.g., the sensing node reports the sensing results with a subset of channel taps), multiple channel estimation-based sensing measurements may be reported in a measurement report. Each measurement report may be associated with a particular DEG identifier (ID). The DEG ID may identify the DEG corresponding to the hardware configuration and/or operational state of the sensing node when performing positioning and/or sensing measurements.

In some aspects, if the sensing measurement is per target (e.g., the sensing node reports the sensing results with (e.g., using) target IDs that identify target entities), multiple per target-based sensing measurements may be reported. The sensing node may provide a measurement report for each target entity. Each target-based sensing measurement report may be associated with a particular DEG ID. For example, a measurement report for a particular target entity may be associated with a particular DEG ID of the sensing node.

In some aspects, a network node or UE may determine a sensing result for a target entity based on an analysis of the measurement reports received by one or more sensing nodes. The sensing result may indicate at least one of a change of an environment in which the target entity is included, at least one physiological characteristic of a target entity (e.g., a heart rate, a respiration rate, body temperature, etc.), a location of the target entity, a velocity of the target entity, a heading of the target entity, etc. A target entity may be any object (e.g., a person, a vehicle, a UE, etc.) for which a positioning or sensing session is performed, for example, to determine a location thereof, a velocity thereof, a heading thereof, a physiological characteristic thereof, etc.

In some aspects, a sensing node may report its capability to support a maximum number of DEGs. That is, the sensing node may support a maximum number of DEGs and report the maximum number via capability signaling. To reduce the overhead of the measurement report, the sensing node may down-select to a subset of the supported DEGs to be reported. That is, the sensing node may provide measurement reports for a subset of DEGs supported by the sensing node.

In some aspects, the network may have the minimum amount of DEGs to be reported. That is, the network may be signal to a sensing node a minimum number of DEGs to be reported. The minimum amount of DEGs may be less than the maximum number of DEGs supported by the sensing node.

In some aspects, the sensing node may maintain the coherency of DEGs for a sequence of measurement reports. For example, the sensing node may have different DEGs within particular time window. That is, a particular DEG may be associated with a particular hardware configuration for measurements reported within a particular time window. The sensing node may ensure coherency by not changing (e.g., maintaining) its association between the DEG and the hardware configuration. This is to support certain advanced processing algorithms, such as differential Doppler-based sensing.

In accordance with various aspects of the present disclosure, a DEG-based measurement report may trigger some advanced schemes to mitigate the Doppler measurement error. For example, based on the DEG report, the network may utilize some advanced schemes to mitigate the Doppler measurement. One example advanced scheme may be Doppler-based RF sensing (e.g., frequency difference of arrival (FDOA)-based RF sensing), where the location of a target entity is based on measurements or observations from multiple points. The observation points are in relative motion with respect to each other and the target entity. This relative motion results in different Doppler shift observations of the target entity at each location. The network may trigger this scheme by requesting the sensing node to report the sensing measurement with a particular DEG. This implicitly requests the sensing node to use the same hardware configuration for certain sensing measurement reports. Because each DEG is associated with a certain clustered Doppler measurement error, the different Doppler-based sensing method may remove such common bias.

Another example advanced scheme may be downlink and uplink (i.e., DL+UL) RF bistatic sensing. In accordance with such a scheme, a sensing node may transmit a downlink sensing signal that is reflected by the target object and received by a second sensing node, which measures a first frequency offset that includes an oscillator error from the transmission of the sensing signal and a Doppler shift from the target object. The sensing node may also receive and measure a second frequency offset of a sensing signal transmitted by the second sensing node, reflected by the target object, and received by the sensing node (e.g., as an uplink sensing signal), which includes a second frequency offset that includes an oscillator error from the reception of the sensing signal and a Doppler shift from the target object. The velocity of the object may be estimated based on a combination of the first and second frequency offsets, which cancels the oscillator error caused by the sensing entity.

The RF bistatic sensing may be utilized so long as the sensing node utilizes the same oscillator for its transmit chain and receive chain when performing RF sensing measurements. The RF bistatic sensing scheme may be triggered in many ways. For example, in some aspects, this scheme may be triggered by the sensing node signaling a value of one for the maximum number of DEGs that it supports. This implicitly indicates that a single hardware configuration is supported by the sensing node (i.e., that the same oscillator is used for transmit chain and the receive chain of the sensing node). In some aspects, this scheme may be triggered by defining a particular transmit-receive DEG, which is used when the sensing node uses the same oscillator for its transmit chain and receive chain. That is, the sensing node may signal to the network a particular transmit-receive DEG ID that indicates to the network that the sensing node utilizes the same oscillator for its transmit chain and receive chain. When the sensing node signals such a transmit-receive DEG ID, it implicitly indicates to the network that the RF bistatic sensing technique may be applied for such a sensing node.

FIG.5is a call flow diagram500illustrating a method of wireless communication in accordance with various aspects of this present disclosure. As shown inFIG.5, the diagram500includes a network node502and a sensing node504. The network node502may be an example of the base station310, the TRP402, the TRP406, or the SnMF167. The sensing node504may be an example of the UE104, the UE350, or the UE404. Although aspects are described for the network node502, the aspects may be performed by a network node in aggregation and/or by one or more components of the network node502(e.g., such as a CU110, a DU130, and/or an RU140). As shown inFIG.5, at506, the sensing node504may transmit, to the network node502, capability information that indicates the maximum number of DEGs, supported by the sensing node504.

At508, the sensing node504may transmit, to the network node502, an indication of DEG ID(s) corresponding to DEG(s) supported by the sensing node504. Each of the DEG(s) may be associated with a hardware configuration or an operational state supported by the sensing node504. In some aspects, the network node502may provide, to the sensing node504, an indication of a minimum number of DEGs to be reported. In such aspects, the number of DEG ID(s) indicated by the sensing node504may be less than the maximum number of DEGs supported by the sensing node504. That is, the sensing node504may down-select to a subset of DEGs to report.

In some aspects, the hardware configuration may correspond to at least one of a first oscillator utilized by the sensing node504for a transmission of sensing signals or a second oscillator utilized by the sensing node504for a reception of the sensing signals. In some aspects, the first and second oscillators may be the same oscillator. In other aspects, the first and second oscillators are different oscillators.

In some aspects, the operational state may correspond to at least one of a power state (e.g., a power on state (or mode), a low power state (or power savings mode), a standby state (or mode)) of the sensing node504or a temperature (or temperature range) of the sensing node504.

At510, the sensing node504may perform a set of measurements with respect to a target entity. For example, the sensing node504may receive a sensing signal (e.g., non-line-of-sight (NLOS) signal) that is transmitted from another sensing node (e.g., a UE, a TRP, or the network node502) and reflected off of the target entity. The sensing node504may measure the frequency offset of the reflected signal. As described above, the frequency offset of the sensing signal may include an oscillator error due to transmission of the sensing signal by the sensing node and/or the reception of the sensing signal by the sensing node504, as well as the Doppler shift caused by the velocity of the target entity. In some implementations, additional parameters may be measured, such as the differential delay, e.g., the ToA difference between a line of sight (LOS) path and echo path.

At512, the sensing node504may associate a sensing node ID, a DEG ID, and/or a target ID with the set of measurements. The sensing node ID may uniquely identify the sensing node504. Examples of the sensing node ID include, but are not limited to, an international mobile subscriber identity (IMSI), an international mobile equipment identity (IMEI), a radio network temporary identifier (RNTI), a globally-unique temporary identifier (GUTI), etc. The DEG ID(s) may identify DEG(s) associated with the hardware configuration and/or the operational state(s) of the sensing node504when performing the measurements. In some aspects, each measurement of the set of measurements is associated with a target ID of a target entity associated with the measurement. For example, the target ID of the target entity for which the measurement is performed may be associated with the measurement. In some aspects, the set of measurements includes a set of channel estimation-based sensing measurements, where the set of measurements are associated with a subset of channel taps.

At514, the sensing node504may transmit, to the network node502, the set of measurements associated with the sensing node ID and/or DEG ID. For example, the sensing node504may transmit a measurement report including the set of measurements.

At516, the network node502may derive a sensing result based at least on the DEG ID. For example, the network node502may derive a sensing results based on the frequency offset measurement and the DEG ID associated with the measurement received from the sensing node504. The sensing result may include cancelling (e.g., removing) the oscillator error associated with the sensing node504generated during the frequency offset determination by the sensing node504.

In some aspects, based on the DEG ID(s) reported by the sensing node504, the network node502may perform one or more advanced schemes to cancel the oscillator error. One advanced scheme is differential Doppler-based RF sensing. For example, at516, the network node502may transmit, to the sensing node504, a request that indicates a particular DEG ID of the DEG ID(s) reported by the sensing node504(e.g., the same DEG ID that was utilized to perform the measurements at512). This implicitly requests the sensing node504to use the same hardware configuration and/or operational state for performing measurements and providing a measurement report. Based on the request, the sensing node504performs a second set of measurements utilizing the same hardware configuration and/or operational state and provides a second set of measurements associated with the requested DEG ID to the network node502. The network node502calculates a FDOA based on the second set of measurements and the first set of measurements received at514. For example, the network node502may derive the sensing result by averaging a normalized version of the frequency offset provided via the first set of measurements (provided at514) and a normalized version of the frequency offset provided via the second set of measurements, which cancels the oscillator error of the sensing node504.

In some aspects, another advanced scheme is RF bistatic sensing. For example, at516, the network node502may identify that the DEG ID for which the set of measurements was received at514indicates that the sensing node504utilizes the same oscillator for a transmission of sensing signals and a reception of the sensing signals. In response to identifying such a DEG ID, the network node502may derive the sensing result based on a first frequency offset measurement of the set of measurements and a second frequency offset measurement of the set of measurements, where the first frequency offset measurement is based on a downlink sensing signal of the sensing node504(e.g., a sensing signal transmitted by the sensing node504) and the second frequency offset measurement is based on an uplink sensing signal of the sensing node504(e.g., a sensing signal received by the sensing node504). For instance, the sensing node may transmit a downlink sensing signal that is reflected by the target entity and received by a second sensing node, which measures a first frequency offset that includes an oscillator error from the transmission of the sensing signal and a Doppler shift from the target entity. The sensing node504may also receive and measure a second frequency offset of a sensing signal transmitted by the second sensing node, reflected by the target object, and received by the sensing node504(e.g., as an uplink sensing signal), which includes a second frequency offset that includes an oscillator error from the reception of the sensing signal and a Doppler shift from the target entity. The sensing result of the target entity may be estimated based on a combination (e.g., average) of the first and second frequency offsets (e.g., normalized versions of the first and second frequency offsets), which cancels the oscillator error caused by the sensing node504.

In some aspects, the sensing result includes information indicative of at least one of a change of an environment associated with the set of measurements, at least one physiological characteristic of a target entity (e.g., a heart rate, a respiration rate, body temperature, etc.) associated with the set of measurements, a location of the target entity, a velocity of the target entity, or a heading of the target entity.

FIG.6is a flowchart600illustrating methods of wireless communication at a wireless entity in accordance with various aspects of the present disclosure. In some aspects, the wireless entity may be the UE104,350, or404, the sensing node504, or the apparatus804in the hardware implementation ofFIG.8.

At602, the wireless entity may transmit a first indication of DEG ID(s) corresponding to DEG(s) supported by the wireless entity, each of the DEG(s) being associated with a hardware configuration or an operational state of the wireless entity. For example, referring toFIG.6, the sensing node504, at508, may transmit an indication of DEG ID(s) corresponding to DEG(s) supported by the sensing node504, each of the DEG(s) being associated with a hardware configuration or an operational state of the sensing node504. In an aspect,602may be performed by the DEG transmission component198.

In some aspects, the hardware configuration may correspond to at least one of a first oscillator utilized by the wireless entity for a transmission of sensing signals or a second oscillator utilized by the wireless entity for a reception of the sensing signals. For example, referring toFIG.8, the hardware configuration of the sensing node504may correspond to at least one of a first oscillator utilized by the sensing node504for a transmission of sensing signals or a second oscillator utilized by the sensing node504for a reception of the sensing signals.

In some aspects, the operational state may correspond to at least one of a power state of the wireless entity or a temperature of the wireless entity. For example, referring toFIG.5, the operational state of the sensing node504may correspond to at least one of a power state of the sensing node504or a temperature of the sensing node504.

In some aspects, the wireless entity may transmit a second indication of a maximum number of DEGs supported by the wireless entity. For example, referring toFIG.5, the sensing node504, at506, may transmit an indication of a maximum number of DEGs supported by the sensing node504.

In some aspects, a number of the DEG ID(s) may be less than the maximum number of DEGs supported by the wireless entity. For example, referring toFIG.5, the number of the DEG ID(s) transmitted at508by the sensing node504may be less than the maximum number of DEGs supported by the sensing node504.

At604, the wireless entity may transmit a first set of measurements associated with a DEG ID of the DEG ID(s). For example, referring toFIG.5, the sensing node504, at514, may transmit a first set of measurements associated with a DEG ID of the DEG ID(s). In an aspect,604may be performed by the DEG transmission component198. In some aspects, the wireless entity may associate a wireless entity ID of the wireless entity with the first set of measurements. For example, referring toFIG.5, the sensing node504, at512, may associate an ID of the sensing node504with the first set of measurements.

In some aspects, the wireless entity may associate each measurement of the first set of measurements with a target ID of a target entity associated with the measurement. For example, referring toFIG.5, the sensing node504, at512, may associate each measurement of the first set of measurements with a target ID of a target entity associated with the measurement.

In some aspects, the first set of measurements may include a set of channel estimation-based sensing measurements. For example, referring toFIG.5, the first set of measurements transmitted at514may include a set of channel estimation-based sensing measurements.

In some aspects, the wireless entity may receive, from a network entity, a request that indicates a particular DEG ID of the DEG(s). The wireless entity may transmit, for the network entity, a second set of measurements associated with the particular DEG ID. For example, referring toFIG.5, as part of516, the sensing node504may receive, from the network node502, a request that indicates a particular DEG ID of the DEG(s). The request may be to trigger differential Doppler based RF sensing at the network node502. In response to the request, the sensing node504may transmit, to the network node502, a second set of measurements associated with the particular DEG ID. The network node502may, at516, derive the sensing result based on the set of measurements received at514and the set of measurements received in response to the request transmitted by the network node502.

In some aspects, the network entity may be a network node, a base station, or a SnMF. For example, referring toFIGS.1and3-5, the network entity may be the base station102, the SnMF167, the base station310, the TRP402, the TRP406, or network node502.

In some aspects, the DEG ID of the DEG ID(s) may indicate that the wireless entity utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals. The first set of measurements may include a first frequency offset measurement of the first set of measurements and a second frequency offset measurement of the first set of measurements, the first frequency offset measurement being based on a downlink sensing signal transmitted by the wireless entity and the second frequency offset measurement being based on an uplink sensing signal received by the wireless entity. For example, referring toFIG.5, the DEG ID transmitted at508may indicate that the sensing node504utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals. Such a DEG may trigger RF bistatic sensing at the network node502. The set of measurements transmitted at514may include a first frequency offset measurement of the set of measurements and a second frequency offset measurement of the set of measurements, the first frequency offset measurement being based on a downlink sensing signal transmitted by the sensing node504and the second frequency offset measurement being based on an uplink sensing signal received by the sensing node504. The network node502may, at516, derive the sensing result based on the first frequency offset measurement and the second frequency offset measurement.

FIG.7is a flowchart700illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure. In some aspects, the network entity may be the base station102, the SnMF167, the base station310, the TRP402, the TRP406, the network node502, the network entity902in the hardware implementation ofFIG.9, or the network entity1060in the hardware implementation ofFIG.10.

At702, the network entity may receive an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, each of the DEG(s) being associated with a hardware configuration or an operational state of the wireless entity. For example, referring toFIG.5, the network node502, at508, may receive an indication of DEG ID(s) corresponding to DEG(s) supported by the sensing node504, each of the DEG(s) being associated with a hardware configuration or an operational state of the sensing node504. In an aspect,702may be performed by the DEG reception component199.

In some aspects, the wireless entity may be a sensing node. For example, referring toFIG.5, the wireless entity may be the sensing node504.

In some aspects, the hardware configuration may correspond to at least one of a first oscillator utilized by the wireless entity for a transmission of sensing signals or a second oscillator utilized by the wireless entity for a reception of the sensing signals. For example, referring toFIG.5, the hardware configuration of the sensing node504may correspond to at least one of a first oscillator utilized by the sensing node504for a transmission of sensing signals or a second oscillator utilized by the sensing node504for a reception of the sensing signals.

In some aspects, the operational state may correspond to at least one of a power state of the wireless entity or a temperature of the wireless entity. For example, referring toFIG.5, the operational state of the sensing node504may correspond to at least one of a power state of the sensing node504or a temperature of the sensing node504.

In some aspects, the network entity may receive a second indication of a maximum number of DEGs supported by the wireless entity. For example, referring toFIG.5, the network node502, at506may receive an indication of a maximum number of DEGs supported by the sensing node504.

At704, the network entity may receive a first set of measurements associated with a DEG ID of the DEG ID(s). For example, referring toFIG.5, the network node502, at514, may receive, from the sensing node504, a first set of measurements associated with a DEG ID of the DEG ID(s). In an aspect,704may be performed by the DEG reception component199.

In some aspects, the first set of measurements may be further associated with a wireless entity ID of the wireless entity. For example, referring toFIG.5, the first set of measurements received at514may be further associated with an ID of the sensing node504. The sensing node504, at512, may associate the ID of the sensing node504with the first set of measurements.

In some aspects, each measurement of the first set of measurements may be associated with a target ID of a target entity associated with the measurement. For example, referring toFIG.5, each measurement of the first set of measurements received at514may be associated with a target ID of a target entity associated with the measurement. The sensing node504, at516, may associate the target ID with the measurement.

In some aspects, the first set of measurements may include a set of channel estimation-based sensing measurements. For example, referring toFIG.5, the first set of measurements received at514may include a set of channel estimation-based sensing measurements.

At706, the network entity may derive a sensing result based at least partially on the DEG ID. For example, referring toFIG.5, the network node502, at516, may derive a sensing result based at least partially on the DEG ID. In an aspect,706may be performed by the DEG reception component199.

In some aspects, the network entity may transmit, for a wireless entity, a request that indicates a particular DEG ID of the DEG(s). The network entity may receive a second set of measurements associated with the particular DEG ID. The network entity may calculate a frequency difference of an arrival of the second set of measurements associated with the particular DEG ID. For example, referring toFIG.5, as part of516, the network node502may transmit, to the sensing node504a request that indicates a particular DEG ID of the DEG(s). The request may be to trigger differential Doppler based RF sensing at the network node502. The network node502may receive a second set of measurements associated with the particular DEG ID. The network node502may, at516, derive the sensing result based on the set of measurements received at514and the set of measurements received in response to the request transmitted by the network node502. For example, the network node502may, at516, calculate a frequency difference of an arrival of the second set of measurements associated with the particular DEG ID.

In some aspects, the network entity may identify that the DEG ID of the DEG ID(s) indicates that the wireless entity utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals. The network entity may derive, in response to the identification, the sensing result based on a first frequency offset measurement of the first set of measurements and a second frequency offset measurement of the first set of measurements, the first frequency offset measurement being based on a downlink sensing signal of the wireless entity and the second frequency offset measurement being based on an uplink sensing signal of the wireless entity. For example, referring toFIG.5, the DEG ID received at508may indicate that the sensing node504utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals. Such a DEG may trigger RF bistatic sensing at the network node502. The set of measurements received at514may include a first frequency offset measurement of the set of measurements and a second frequency offset measurement of the set of measurements, the first frequency offset measurement being based on a downlink sensing signal transmitted by the sensing node504and the second frequency offset measurement being based on an uplink sensing signal received by the sensing node504. The network node502may, at516, derive, in response to the identification, the sensing result based on the first frequency offset measurement and the second frequency offset measurement.

In some aspects, the sensing result may include information indicative of at least one of a change of an environment associated with the first set of measurements, at least one physiological characteristic of a target entity associated with the first set of measurements, a location of the target entity, a velocity of the target entity, or a heading of the target entity. For example, referring toFIG.5, the sensing result derived at516may include information indicative of at least one of a change of an environment associated with the first set of measurements, at least one physiological characteristic of a target entity associated with the first set of measurements, a location of the target entity, a velocity of the target entity, or a heading of the target entity.

FIG.8is a diagram800illustrating an example of a hardware implementation for an apparatus804. The apparatus804may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus804may include a cellular baseband processor824(also referred to as a modem) coupled to one or more transceivers822(e.g., cellular RF transceiver). The cellular baseband processor824may include on-chip memory824′. In some aspects, the apparatus804may further include one or more subscriber identity modules (SIM) cards820and an application processor806coupled to a secure digital (SD) card808and a screen810. The application processor806may include on-chip memory806′. In some aspects, the apparatus804may further include a Bluetooth module812, a WLAN module814, an SPS module816(e.g., GNSS module), one or more sensor modules818(e.g., barometric pressure sensor/altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and/or other technologies used for positioning), additional memory modules826, a power supply830, and/or a camera832. The Bluetooth module812, the WLAN module814, and the SPS module816may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module812, the WLAN module814, and the SPS module816may include their own dedicated antennas and/or utilize the antennas880for communication. The cellular baseband processor824communicates through the transceiver(s)822via one or more antennas880with the UE104, the core network120, and/or with an RU associated with a network entity802. The cellular baseband processor824and the application processor806may each include a computer-readable medium/memory824′,806′, respectively. The additional memory modules826may also be considered a computer-readable medium/memory. Each computer-readable medium/memory824′,806′,826may be non-transitory. The cellular baseband processor824and the application processor806are each responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor824/application processor806, causes the cellular baseband processor824/application processor806to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor824/application processor806when executing software. The cellular baseband processor824/application processor806may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus804may be a processor chip (modem and/or application) and include just the cellular baseband processor824and/or the application processor806, and in another configuration, the apparatus804may be the entire UE (e.g., see UE350ofFIG.3) and include the additional modules of the apparatus804.

As discussed supra, the component198may be configured to transmit a first indication of DEG ID(s) corresponding to DEG(s) supported by the wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, and to transmit a first set of measurements associated with a DEG ID of the DEG ID(s). The component198may be configured to perform any of the aspects described in connection with the flowchart inFIG.6and/or the aspects performed by the sensing node504in the communication flow inFIG.5. The component198may be within the cellular baseband processor824, the application processor806, or both the cellular baseband processor824and the application processor806. The component198may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus804may include a variety of components configured for various functions. In one configuration, the apparatus804, and in particular the cellular baseband processor824and/or the application processor806, may include means for transmitting a first indication of DEG ID(s) corresponding to DEG(s) supported by the wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, and means for transmitting a first set of measurements associated with a DEG ID of the DEG ID(s). The means may be the component198of the apparatus804configured to perform the functions recited by the means. As described supra, the apparatus804may include the TX processor368, the RX processor356, and the controller/processor359. As such, in one configuration, the means may be the TX processor368, the RX processor356, and/or the controller/processor359configured to perform the functions recited by the means.

FIG.9is a diagram900illustrating an example of a hardware implementation for a network entity902. The network entity902may be a BS, a component of a BS, or may implement BS functionality. The network entity902may include at least one of a CU910, a DU930, or an RU940. For example, depending on the layer functionality handled by the component199, the network entity902may include the CU910; both the CU910and the DU930; each of the CU910, the DU930, and the RU940; the DU930; both the DU930and the RU940; or the RU940. The CU910may include a CU processor912. The CU processor912may include on-chip memory912′. In some aspects, the CU910may further include additional memory modules914and a communications interface918. The CU910communicates with the DU930through a midhaul link, such as an F1interface. The DU930may include a DU processor932. The DU processor932may include on-chip memory932′. In some aspects, the DU930may further include additional memory modules934and a communications interface938. The DU930communicates with the RU940through a fronthaul link. The RU940may include an RU processor942. The RU processor942may include on-chip memory942′. In some aspects, the RU940may further include additional memory modules944, one or more transceivers946, antennas980, and a communications interface948. The RU940communicates with the UE104. The on-chip memory912′,932′,942′ and the additional memory modules914,934,944may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the processors912,932,942is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

As discussed supra, the component199may be configured to receive an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, to receive a set of measurements associated with a DEG ID of the DEG ID(s), and to derive a sensing result based at least partially on the DEG ID. The component199may be configured to perform any of the aspects described in connection with the flowchart inFIG.7and/or the aspects performed by the network node502in the communication flow inFIG.5. The component199may be within one or more processors of one or more of the CU910, DU930, and the RU940. The component199may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity902may include a variety of components configured for various functions. In one configuration, the network entity902may include means for receiving an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, means for receiving a set of measurements associated with a DEG ID of the DEG ID(s), and means for deriving a sensing result based at least partially on the DEG ID. The means may be the component199of the network entity902configured to perform the functions recited by the means. As described supra, the network entity902may include the TX processor316, the RX processor370, and the controller/processor375. As such, in one configuration, the means may be the TX processor316, the RX processor370, and/or the controller/processor375configured to perform the functions recited by the means.

FIG.10is a diagram1000illustrating an example of a hardware implementation for a network entity1060. In one example, the network entity1060may be within the core network120. The network entity1060may include a network processor1012. The network processor1012may include on-chip memory1012′. In some aspects, the network entity1060may further include additional memory modules1014. The network entity1060communicates via the network interface1080directly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU1002and the sensing node1004, which is an example of the sensing node504. The on-chip memory1012′ and the additional memory modules1014may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. The processor1012is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

As discussed supra, the component199may be configured to receive an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, to receive a set of measurements associated with a DEG ID of the DEG ID(s), and to derive a sensing result based at least partially on the DEG ID. The component199may be configured to perform any of the aspects described in connection with the flowchart inFIG.7and/or the aspects performed by the network node502in the communication flow inFIG.5. The component199may be within the processor1012. The component199may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity1060may include a variety of components configured for various functions. In one configuration, the network entity1060may include means for receiving an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, means for receiving a set of measurements associated with a DEG ID of the DEG ID(s), and means for deriving a sensing result based at least partially on the DEG ID. The means may be the component199of the network entity1060configured to perform the functions recited by the means.

Various aspects relate generally to positioning systems. Some aspects more specifically relate to RF sensing utilizing one or more Doppler error groups (DEGs). In some examples, a wireless entity (e.g., a sensing node) may provide an indication of one or more DEG identifiers (IDs) corresponding to DEG(s) supported by the wireless entity. Each of the DEG ID(s) indicates a particular hardware configuration (e.g., an indication of one or more oscillators utilized by the wireless entity) and/or an operational state supported by the wireless entity. The wireless entity may perform a set of measurements for a target entity. The wireless entity may provide the set of measurements to a network entity (e.g., a base station, a network node, a sensing management function (SnMF), etc.), along with a particular DEG ID that identifies the DEG (or hardware configuration and/or operational state) utilized when performing the set of measurements. The network entity may derive a sensing result (e.g., a position, a velocity, etc.) for a target entity based at least on the DEG ID (e.g., based on the DEG ID and the set of measurements).

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 deriving the sensing result based on the DEG ID, the network entity may determine the hardware configuration and/or operational state of the wireless entity and accurately remove the estimation bias caused by the oscillator error associated with the hardware configuration and/or operational state. By doing so, the network entity may more accurately estimate the Doppler shift of the target entity, and therefore, more accurately determine a sensing result for the target entity.

Aspect 1 is a method of wireless communication at a network entity, including receiving an indication of DEG ID(s) corresponding to DEG(s) supported by a wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity, receiving a first set of measurements associated with a DEG ID of the DEG ID(s), and deriving a sensing result based at least partially on the DEG ID.

Aspect 2 is the method of aspect 1, further including: transmitting, for the wireless entity, a request that indicates a particular DEG ID of the DEG ID(s), receiving a second set of measurements associated with the particular DEG ID, and calculating a frequency difference of an arrival of the second set of measurements associated with the particular DEG ID.

Aspect 3 is the method of any of aspects 1 and 2, further including: identifying that the DEG ID of the DEG ID(s) indicates that the wireless entity utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals.

Aspect 4 is the method of any of aspects 1 to 3, where the first set of measurements is further associated with a wireless entity ID of the wireless entity.

Aspect 5 is the method of any of aspects 1 to 4, where the sensing result includes first information indicative of at least one of: a change of an environment associated with the first set of measurements; at least one physiological characteristic of a target entity associated with the first set of measurements; a location of the target entity; a velocity of the target entity; or a heading of the target entity.

Aspect 6 is the method of any of aspects 1 to 5, where the hardware configuration corresponds to: at least one of a first oscillator utilized by the wireless entity for a transmission of sensing signals or a second oscillator utilized by the wireless entity for a reception of the sensing signals.

Aspect 7 is the method of any of aspects 1 to 6, where the operational state corresponds to at least one of: a power state of the wireless entity; or a temperature of the wireless entity.

Aspect 8 is the method of any of aspects 1 to 7, where the first set of measurements includes a set of channel estimation-based sensing measurements.

Aspect 9 is the method of any of aspects 1 to 8, where each measurement of the first set of measurements is associated with a target ID of a target entity associated with the measurement.

Aspect 10 is the method of any of aspects 1 to 9, further including: receiving a second indication of a maximum number of DEGs supported by the wireless entity.

Aspect 11 is the method of any of aspects 1 to 10, where the network entity is a network node, a base station, or a sensing management function, and where the wireless entity is a sensing node.

Aspect 12 is a method of wireless communication at a wireless entity, including: transmitting a first indication of DEG ID(s) corresponding to DEG(s) supported by the wireless entity, where each of the DEG(s) is associated with a hardware configuration or an operational state of the wireless entity; and transmit a first set of measurements associated with a DEG ID of the DEG ID(s).

Aspect 13 is the method of aspect 12, further including: receiving, from a network entity, a request that indicates a particular DEG ID of the DEG(s); and transmitting, for the network entity, a second set of measurements associated with the particular DEG ID.

Aspect 14 is the method of aspect 13, where the network entity is a network node, a base station, or a sensing management function, and where the wireless entity is a sensing node.

Aspect 15 is the method of any of aspects 12 to 14, where the DEG ID of the DEG ID(s) indicates that the wireless entity utilizes a same oscillator for a transmission of sensing signals and a reception of the sensing signals, and where the first set of measurements includes a first frequency offset measurement of the first set of measurements and a second frequency offset measurement of the first set of measurements, where the first frequency offset measurement is based on a downlink sensing signal transmitted by the wireless entity and the second frequency offset measurement is based on an uplink sensing signal received by the wireless entity.

Aspect 16 is the method of any of aspects 12 to 15, further including: associating a wireless entity ID of the wireless entity with the first set of measurements.

Aspect 17 is the method of any of aspects 12 to 16, where the hardware configuration corresponds to: at least one of a first oscillator utilized by the wireless entity for a transmission of sensing signals or a second oscillator utilized by the wireless entity for a reception of the sensing signals.

Aspect 18 is the method of any of aspects 12 to 17, where the operational state corresponds to at least one of: a power state of the wireless entity; or a temperature of the wireless entity.

Aspect 19 is the method of any of aspects 12 to 18, where the first set of measurements includes a set of channel estimation-based sensing measurements.

Aspect 20 is the method of any of aspects 12 to 19, further including: associating each measurement of the first set of measurements with a target ID of a target entity associated with the measurement.

Aspect 21 is the method of any of aspects 12 to 20, further including: transmitting a second indication of a maximum number of DEGs supported by the wireless entity.

Aspect 22 is the method of aspect 21, where a number of the DEG ID(s) is less than the maximum number of DEGs supported by the wireless entity.

Aspect 23 is an apparatus for wireless communication at a network entity. The apparatus includes memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to implement any of aspects 1 to 11.

Aspect 24 is the apparatus of aspect 23, further including at least one of a transceiver or an antenna coupled to the at least one processor.

Aspect 25 is an apparatus for wireless communication at a wireless entity. The apparatus includes memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to implement any of aspects 12 to 22.

Aspect 26 is the apparatus of aspect 25, further including at least one of a transceiver or an antenna coupled to the at least one processor.

Aspect 27 is an apparatus for wireless communication including means for implementing any of aspects 1 to 11.

Aspect 28 is an apparatus for wireless communication including means for implementing any of aspects 12 to 22.