WO2022000323A1

WO2022000323A1 - Data decoding information sharing for multi-node passive sensing

Info

Publication number: WO2022000323A1
Application number: PCT/CN2020/099502
Authority: WO
Inventors: Qiaoyu Li; Hao Xu; Yu Zhang; Min Huang; Chao Wei; Jing Dai
Original assignee: Qualcomm Incorporated
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2022-01-06

Abstract

Aspects of the disclosure relate to receiving, by a user equipment (UE), a message comprising data decoding information relating to data that is not scheduled for purposes of communication with the UE; and monitoring for encoded signals based on the data decoding information. Other aspects, embodiments, and features are also claimed and described.

Description

DATA DECODING INFORMATION SHARING FOR MULTI-NODE PASSIVE SENSING

TECHNICAL FIELD

The technology described below relates generally to wireless communication systems, and more particularly, to explicitly sharing data decoding information for multiple transmitters to facilitate multi-node passive sensing using signals transmitted for other receivers.

INTRODUCTION

As the demand for mobile broadband access continues to increase, research and development continue to advance wireless communication technologies not only to meet the growing demand for mobile broadband access, but to advance and enhance the user experience with mobile communications.

BRIEF SUMMARY OF SOME EXAMPLES

The following presents a simplified summary of one or more aspects of the present disclosure, in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

Aspects of the disclosure relate to receiving, by a user equipment (UE) , a message comprising data decoding information relating to data that is not scheduled for the UE to receive; and monitoring for encoded signals based on the data decoding information.

Aspects of the disclosure relate to receiving, by a scheduling entity, data decoding information comprising information relating to data decoding of one or more channels; receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information relating data decoding of one or more channels that are not for any one or more of: reference in relation to transmission or reception of information by the UE, channel characterization by the UE, or synchronization by the UE; and in response to the request from the UE, transmitting a message comprising the data decoding information to the UE.

These and other aspects of the invention will become more fully understood upon a review of the detailed description, which follows. Other aspects, features, and embodiments will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary embodiments in conjunction with the accompanying figures. While the following description may described various advantages and features relative to certain embodiments and figures below, all embodiments can include one or more of the advantageous features described herein. In other words, while this description may described one or more embodiments as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments described herein. In similar fashion, while this description may describe exemplary embodiments as device, system, or method embodiments it should be understood that such exemplary embodiments can be implemented in various devices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a wireless communication system in accordance with some aspects of the disclosed subject matter.

FIG. 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects of the disclosed subject matter.

FIG. 3 is a conceptual illustration of passive sensing with a single transmitter and a flow chart illustrating an example process for passive sensing in accordance with some aspects of the disclosed subject matter.

FIG. 4 is a conceptual illustration of multi-node passive sensing using both multiple transmitters and multiple receivers, and flow charts illustrating example processes for multi-node passive sensing in accordance with some aspects of the disclosed subject matter.

FIG. 5 is a block diagram illustrating a signal processing pipeline for estimating frequency domain channel responses in accordance with some aspects of the disclosed subject matter.

FIG. 6 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) in accordance with some aspects of the disclosed subject matter.

FIG. 7 is a schematic illustration of resource allocations of wireless resources in an air interface utilizing OFDM in accordance with some aspects of the disclosed subject matter.

FIG. 8 is a schematic illustration of resource allocation patterns for reference signal transmission segmented in a plot of frequency domain and time domain in accordance with some aspects of the disclosed subject matter.

FIG. 9 is a schematic illustration of resource allocation patterns for reference signal transmission segmented in a plot of frequency domain, time domain, and a space/coding domain in accordance with some aspects of the disclosed subject matter.

FIG. 10 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some aspects of the disclosure.

FIG. 11 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some aspects of the disclosure.

FIG. 12 is a flow chart illustrating an example process for sharing Reference Signal (RS) configuration information for multiple entities in accordance with some aspects of the disclosed subject matter.

FIG. 13 is a flow chart illustrating an example process for an entity sharing RS configuration information associated with its own RS transmissions in accordance with some aspects of the disclosed subject matter.

FIG. 14 is a flow chart illustrating an example process for using RS configuration information to facilitate multi-node passive sensing in accordance with some aspects of the disclosed subject matter.

FIG. 15 is a schematic illustration of resource allocation patterns for encoded data segmented in a plot of frequency domain and time domain in accordance with some aspects of the disclosed subject matter.

FIG. 16 is a schematic illustration of resource allocation patterns for encoded data segmented in a plot of frequency domain, time domain, and a space/coding domain in accordance with some aspects of the disclosed subject matter.

FIG. 17 is a flow chart illustrating an example process for sharing data decoding information for multiple entities in accordance with some aspects of the disclosed subject matter.

FIG. 18 is a flow chart illustrating an example process for an entity sharing data decoding information associated with its own transmissions in accordance with some aspects of the disclosed subject matter.

FIG. 19 is a flow chart illustrating an example process for using data decoding information to facilitate multi-node passive sensing in accordance with some aspects of the disclosed subject matter.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, those skilled in the art will readily recognize that these concepts can be practiced without these specific details. In some instances, this description provides well known structures and components in block diagram form in order to avoid obscuring such concepts.

While this description describes aspects and embodiments by illustration to some examples, those skilled in the art will understand that additional implementations and use cases can come about in many different arrangements and scenarios. Innovations described herein can be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses can come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence-enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations can occur. Implementations can range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features can also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . It is intended that innovations described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.

The disclosure that follows presents various concepts that can be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.

FIG. 1 is a schematic illustration of a wireless communication system 100 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. In some aspects, wireless communication system 100 can include three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. In some aspects, by virtue of wireless communication system 100, UE 106 can be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.

In some aspects, RAN 104 can implement any suitable wireless communication technology or combination of technologies to provide radio access to UE 106. For example, RAN 104 can operate according to 3 ^rd Generation Partnership Project (3GPP) New Radio (NR) specifications, which is sometimes referred to as 5G NR or simply 5G. As another example, RAN 104 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, which is sometimes referred to as LTE. The 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Of course, many other examples can be utilized in connection with the subject matter disclosed herein without departing from the scope of the present disclosure.

As illustrated in the example of FIG. 1, RAN 104 includes various base stations 108. Broadly, a base station can be used to implement a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE, such as UE 106. In different technologies, standards, and/or contexts, various terminology has been used to refer to a network elements that act as a base station. For example, a base station can also be referred to by those skilled in the art using various terminology to refer to a network element that connects one or more UE apparatuses to one or more portions of core network 102, such as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.

In some aspects, as illustrated in FIG. 1, RAN 104 can support wireless communication for multiple mobile apparatuses. A mobile apparatus can be referred to as user equipment (UE) in 3GPP standards, but can also be referred to by those skilled in the art using various terminology to refer to a network element that provides a user with access to one or more network services, such as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. In general, a UE can be an apparatus (e.g., a mobile apparatus) that provides a user with access to network services.

Within the present document, a "mobile" apparatus need not necessarily have a capability to move, and may be stationary. The term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies. UEs can include a number of hardware structural components sized, shaped, and arranged to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of a mobile apparatus include a mobile, a cellular (cell) phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an "Internet of things" (IoT) . A mobile apparatus can additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health and/or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc. A mobile apparatus can additionally be a digital home device or smart home device such as a home audio device, a home video device, and/or a home multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc. A mobile apparatus can additionally be a smart energy device, a security device, a solar panel and/or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , a municipal infrastructure device controlling lighting, a municipal infrastructure device controlling water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weaponry, etc. Still further, a mobile apparatus can provide for connected medicine or telemedicine support, e.g., health care at a distance. Telehealth devices can include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information (e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data) .

In some aspects, wireless communication between RAN 104 and UE 106 illustrated in FIG. 1 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmission. In accordance with some aspects of the disclosed subject matter, the term downlink can refer to a point-to-multipoint transmission originating at a scheduling entity (e.g., base station 108) . For example, a downlink can be implemented using one or more broadcast channel multiplexing techniques. In some aspects, transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. In accordance with some aspects of the disclosed subject matter, the term uplink can refer to a point-to-point transmission originating at a scheduled entity (e.g., UE 106) .

In some aspects, access to the air interface can be scheduled, wherein a scheduling entity (e.g., a base station of RAN 104, such as base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. For example, as described below in connection with FIGS. 9 and 10, the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. In such an example, for scheduled communication scheduled entities (e.g., UEs 106) can utilize resources allocated by a scheduling entity (e.g., base station 108) .

In some aspects, base stations 108 are not the only entities that can function as scheduling entities. For example, in some aspects, a UE can function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .

As illustrated in FIG. 1, in some aspects, a scheduling entity (e.g., base station 108) can broadcast downlink traffic 112 to one or more scheduled entities (e.g., UEs 106) . Broadly, in some aspects, a scheduling entity (e.g., base station 108) can act as a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities (e.g., UEs 106) to the scheduling entity (e.g., base station 108) . Additionally, a scheduled entity (e.g., UE 106) can act a node or device that receives downlink control information 114, which can include (but is not limited to) scheduling information (e.g., a grant) , synchronization or timing information, and/or other control information from another entity in the wireless communication network such as the scheduling entity (e.g., base station 108) .

In general, in some aspects, base stations 108 can include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system. In some aspects, backhaul 120 can provide a link between a particular base station and core network 102. Further, in some examples, a backhaul network (e.g., including backhaul 120) can provide interconnection between various base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, and/or any other suitable connection, using any suitable transport network.

In some aspects, core network 102 can be a part of the wireless communication system 100, and can be independent of the radio access technology used in RAN 104. In some aspects, core network 102 can be configured according to 5G standards (e.g., 5GC) . Additionally or alternatively, in some aspects, core network 102 can be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.

In some aspects, UE 106 can simultaneously connect to multiple base stations 108 and/or can connect to a single base station 108 using multiple component carriers (e.g., at different frequencies) to increase the bandwidth available for communications to and/or from UE 106. Additionally, in some aspects, UE 106 can receive signals transmitted by multiple transmitters that may not be base stations, such as other UEs, road side units (RSUs) , and/or any other transmitter. In some aspects, such signals can be used in a multi-node passive sensing process (which is sometimes referred to as passive radar, passive radar sensing, bistatic radar, or multistatic radar sensing) . For example, passive radar sensing can include object detection, ranging, or other similar object characterization based on signals transmitted from another entity other than the one performing the passive radar sensing, where those signals are at least partially reflected from an object before being received.

In some examples, scheduled entities such as a first scheduled entity 106 and a second scheduled entity 106a can utilize sidelink signals for direct D2D communication. Sidelink signals may include sidelink traffic 132 and sidelink control 134. In some aspects, sidelink control information 134 can include a request signal. For example, sidelink control information 134 can include a request-to-send (RTS) , a source transmit signal (STS) , a direction selection signal (DSS) , and/or any other suitable request signal (s) . A request signal can provide a mechanism for a particular scheduled entity 106 to request a duration of time to keep a sidelink channel available for a sidelink signal. In some aspects, sidelink control information 134 can include a response signal. For example, sidelink control information 134 can include a clear-to-send (CTS) signal, a destination receive signal (DRS) , and/or any other suitable response signal (s) . A response signal can provide a mechanism for a particular scheduled entity 106 to indicate the availability of the sidelink channel (e.g., for a requested duration of time) . In some aspects, an exchange of request and response signals (e.g., a handshake) can facilitate different scheduled entities performing sidelink communications to negotiate the availability of the sidelink channel prior to communication of the sidelink traffic information 132.

FIG. 2 is a conceptual illustration of an example of a radio access network 200 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. In some aspects, RAN 200 can be an implementation of RAN 104 described above in connection with, and illustrated in, FIG. 1. In some aspects, the geographic area covered by RAN 200 can be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station. FIG. 2 illustrates

macrocells

202, 204, and 206, and a small cell 208, each of which can include one or more sectors (not shown) . For example, a sector can be defined as a sub-area of a cell, and all sectors within one cell can be served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.

In FIG. 2, two base stations 210 and 212 are illustrated in

cells

202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables. In the illustrated example,

cells

202, 204, and 206 can be referred to as macrocells, as

base stations

210, 212, and 214 support cells having a relatively large size. Further, a base station 218 is shown in small cell 208 (which can be referred to, for example, as a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc. ) which can overlap with one or more macrocells. In the example illustrated in FIG. 2, cell 208 can be referred to as a small cell, as base station 218 supports a cell having a relatively small size. In some aspects, cell sizing can be done according to system design as well as component constraints.

It is to be understood that radio access network 200 can include any number of wireless base stations and cells. Further, a relay node can be deployed to extend the size or coverage area of a given cell. Additionally,

base stations

210, 212, 214, 218 can provide wireless access points to a core network for any number of mobile apparatuses. In some examples,

base stations

210, 212, 214, and/or 218 can be particular implementations of base station 108 described above in connection with, and illustrated in, FIG. 1.

FIG. 2 further includes a quadcopter 220 (which is sometimes referred to as a drone) , which can be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station such as quadcopter 220.

Within RAN 200, the cells may include UEs that may be in communication with one or more sectors of each cell. Further, each

base station

210, 212, 214, 218, and 220 can be configured to provide an access point to a core network 102 (e.g., as described above in connection with FIG. 1) for all the UEs in the respective cells. For example,

UEs

222 and 224 can be in communication with base station 210;

UEs

226 and 228 can be in communication with base station 212;

UEs

230 and 232 can be in communication with base station 214 by way of RRH 216; UE 234 can be in communication with base station 218; and UE 236 can be in communication with mobile base station 220. In some examples,

UEs

222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 can be particular implementations of UE 106 described above in connection with, and illustrated in, FIG. 1.

In some examples, a mobile network node (e.g., quadcopter 220) can be configured to function as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

In some aspects, sidelink signals can be used between UEs without necessarily relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using peer to peer (P2P) or sidelink signals without relaying that communication through a base station (e.g., base station 212) . In another example, UE 238 is illustrated communicating with

UEs

240 and 242. In such an example, UE 238 can function as a scheduling entity or a primary sidelink device, and

UEs

240 and 242 can function as scheduled entities or a non-primary (e.g., secondary) sidelink device. In yet another example, a UE can function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , vehicle-to-vehicle (V2V) network, and/or in a mesh network. In a mesh network example,

UEs

240 and 242 can optionally communicate directly with one another in addition to communicating with a scheduling entity (e.g., UE 238) . Thus, in a wireless communication system with scheduled access to time–frequency resources and having a cellular configuration, a P2P configuration, and/or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.

The air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, 5G NR specifications provide multiple access for UL transmissions from

UEs

222 and 224 to base station 210, and for multiplexing for DL transmissions from base station 210 to one or

more UEs

222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) . In addition, for UL transmissions, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) . However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes. For example, a UE may provide for UL multiple access utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes. Further, a base station 210 may multiplex DL transmissions to UEs 222 and 224 utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.

FIG. 3 is a conceptual illustration 310 of passive sensing with a single transmitter (which can sometimes be referred to as an illuminator of opportunity) and a flow chart illustrating an example process 300 for passive sensing in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 3, in a passive sensing process a transmitter and a receiver can be located in different physical locations, whereas in a conventional mono-static sensing process the transmitter and receiver are co-located. In the example shown in FIG. 3 only a single object is illustrated for simplicity, however, there may be many more obstructions in the environment of the transmitter and receiver, creating multiple objects that can be detected.

In some aspects, when the transmitter transmits a signal, both a line-of-sight (LoS) signal and a signal that has been backscattered from the object can be received at the receiver. As shown in FIG. 3, because the LoS signal takes a straight path, and the backscattered signal takes a longer path to the object, then to the receiver. In some aspects, the receiver can correlate the LoS signal and the backscattered signal, and use a delay between arrival of the two signals to define an ellipse describing possible positions of the object relate to the transmitter and the receiver, with the transmitter and receiver located at the foci of the ellipse.

As shown in FIG. 3, the receiver (e.g., a UE 106, a BS 108, another device) can execute an example process 300 for passive sensing in accordance with some aspects of the disclosed subject matter. In some aspects, process 300 can begin at "A" and can proceed to 302. At 302, the receiver can receive a LoS signal and a backscattered signal with a time delay Δt between the two signals. In some aspects, the receiver can use any suitable technique or combination of techniques to receive the LoS signal and the backscattered signal. For example, the receiver can sample and buffer a received wireless signal, and apply suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.

At 304, the receiver can use the LoS signal as a reference, and can calculate a correlation with the backscattered signal. Note that because the LoS signal has traveled to the receiver on a straight line, it is received prior to any backscattered signals. In some aspects, the receiver can determine the correlation using any suitable technique or combination of techniques. For example, techniques described below in connection with FIG. 5 can be used to determine the correlation between the LoS and backscattered signals over time. As another example, the receiver can convert received signals into the frequency domain (FD) (e.g., using a circuit for performing a fast Fourier transform (FFT) ) . The receiver can apply a filter (e.g., a matched filter) process to determine a correlation between the LoS signal and the backscattered signal. Because the distance to the object that reflected the LoS is unknown, the LoS can be correlated with received signals at various time delays. In a more particular example, a correlation between the LoS and a signal delayed by time τ can be determined by multiplying the conjugate of the FD components of the LoS

with the the FD components of the signal shifted by τ (S (f) ) . A correlation g (τ) between the two signals can then be determined using the relationship

by applying an inverse FFT (IFFT) to the result of the multiplication. In such an example, the FD signals can be filtered (e.g., using a rectangular windowing function) to reduce noise that falls outside of the baseband of the received signals. This can be repeated at various time delays (e.g., corresponding to a detection range of the passive radar sensing) . A subsequent IFFT can be applied to the correlation from a sequence of time delayed correlations (e.g., for τ= [0, i] , where 0 represents a time at which the LoS signal was received) to generate a range profile across delays τ.

At 306, the receiver can determine the delay Δt between the two signals based on the time delay at which the correlation between the two signals is maximized. In some aspects, there may be multiple maxima in the correlations corresponding to multiple objects that may have reflected the same signal. In some aspects, the receiver can determine the time delay Δt between LoS and a backscattered signal (note there may be multiple backscattered signals from different objects) by finding the maximum or maxima in the correlated data. Note that any particular range estimate can be affected by noise. In some aspects, the receiver can generate a Doppler matrix across the slow time axis. For example, each sample in slow time can represent a range profile generated based on a correlation between LoS and a backscattered signal (s) , with LoS transmitted periodically (at regular or irregular intervals) . This can be used to differentiate between moving objects and the environment. In a particular example, a Doppler matrix can be generated using an FFT filter bank with D inputs corresponding to the number of LoS transmissions used to generate the Doppler matrix. In some aspects, the delay Δt can be determined by finding the maximum or maxima in the Doppler matrix, which can correspond to objects that have been detected.

At 308, the receiver can determine the ellipse corresponding to possible locations of the object (s) based on delay Δt. In some aspects, the ellipse can be determined by determining the path length corresponding to the delay Δt by dividing the speed of light by Δt. In some aspects, the receiver can then use a known position of the transmitter and the position of the receiver to determine which locations in the environment around the receiver lie on the ellipse. For example, the receiver can draw an ellipse using the positions of the transmitter and the receiver as the foci, and finding all points that are at least a distance c*Δt from each transmitter. In a more particular example, the receiver can determine an ellipse that has the transmitter and the receiver as the foci, and a height 2b and width 2a such that each position of the ellipse lies a distance corresponding to time t _tran from the transmitter and a distance corresponding to time t _rec from the receiver with t _tran+t _rec=t _LoS+Δt, which can be represented by the relationship

In a particular example, the receiver can determine the width 2a using the relationship

and can determine the height 2b using the relationship

where c= (t+Δt) /2. In some aspects, after determining an ellipse based on the LoS and backscattered signals, process 300 can proceed to "B" at which process 300 can end.

FIG. 4 is a conceptual illustration of multi-node passive sensing using both multiple transmitters 410 (which can sometimes be referred to as illuminators of opportunity) and multiple receivers 460, and flow charts illustrating example processes 400 and 450 for multi-node passive sensing in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 4, in a multi-node passive sensing process multiple transmitters and/or multiple receivers can be located in different physical locations. In the examples shown in FIG. 4 only a single object is illustrated for simplicity, however, there may be many more obstructions in the environment of the transmitter and receiver, creating multiple objects that can be detected.

In some aspects, in multi-node passive sensing example 410 involving multiple transmitters and a receiver capable of receiving from the multiple transmitters, the receiver can more precisely determine a location of the object by generating multiple ellipses. In some aspects, the receiver can place the object at the intersection of the multiple ellipses.

As shown in FIG. 4, the receiver (e.g., a UE 106, a BS 108, another device) can execute example process 400 for multi-node passive sensing in accordance with some aspects of the disclosed subject matter. At 402, the receiver can go to "A" in process 300 described above in connection with FIG. 3, and at 404, the receiver can return from "B" in process 300 described above in connection with FIG. 3.

At 406, the receiver can return to 402 until 402 to 406 have been repeated N times, where N is the number of transmitters being used in the multi-node passive sensing process. In some aspects, when 402 to 406 have been repeated N times, process 400 can proceed to 408. Note that in each iteration of 402 to 406, multiple ellipses can be determined if there are multiple objects that backscatter the transmitted signals strongly enough.

At 408, the receiver can determine one or more points at which N ellipses intersect (or approximately intersect) as candidate locations of an object. In some aspects, the receiver can use any suitable technique or combination of techniques to select the location (s) of an object (s) among the points at which N ellipses intersect. For example, the receiver can plot each ellipse (e.g., using Cartesian coordinates with the receiver at the origin) , and determine at each point p of an ellipse whether points along N-1 other ellipses are present within a distance ∈ from point p. As another example, the receiver can estimate object positions by using clusters of ellipse intersections that represent object positions. As yet another example, the receiver can arrange the values associated with N ellipses in a matrix, and can attempt to solve a system of equations to find one or more points of intersection. In a more particular example, the receiver can use a filter, such as an extended Kalman filter or an unscented Kalman filter, to estimate points of intersection.

In some aspects, in multi-node passive sensing example 460 involving one transmitter and multiple receivers capable of receiving from the transmitter, a location of the object can be more precisely determined by generating multiple ellipses.

As shown in FIG. 4, each receiver (e.g., a UE 106, a BS 108, another device) can execute at least a portion of example process 450 for multi-node passive sensing in accordance with some aspects of the disclosed subject matter. At 452, a receiver can go to "A" in process 300 described above in connection with FIG. 3, and at 454, the receiver can return from "B" in process 300 described above in connection with FIG. 3.

At 456a, in some aspects, an entity executing at least a portion of process 450 can receive ellipse information defining the location (in the environment) and path of the ellipse (e.g., using the location of the two foci c, the height 2b, and the width 2a; using the location of one focus and a directrix, and/or any other information that can convey the shape of the ellipse) . In some aspects, any suitable entity can receive the ellipse information. For example, a receiver (e.g., a UE 106, a BS 108, another device) that is executing at least a portion of process 450 can receive ellipse information from N-1 other receivers. In a more particular example, the receiver can receive ellipse information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . As another example, an entity (e.g., a UE 106, a BS 108, another device) that is not a receiver that executed 452 and 454 can receive ellipse information from N receivers that did execute 452 and 454 of process 450.

Additionally or alternatively, in some aspects, at 456b, a receiver executing at least a portion of process 450 can transmit ellipse information to another entity (e.g., an entity executing 456a) . For example, the receiver can transmit ellipse information using one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . Note that in some aspects, a single entity can execute 456a. Alternatively, multiple entities can execute 456a (e.g., multiple receivers that executed 452 and 454) .

At 458, an entity that collected at least N ellipses (e.g., at 456a, or at 452 to 456a) can determine one or more points at which N ellipses intersect as candidate locations of an object using any suitable technique or combination of techniques, such as techniques described above in connection with 408. Note that if there are multiple objects, the entity may have collected more than N ellipses. In some aspects, the receiver can use any suitable technique or combination of techniques to select the location (s) of an object (s) among the points at which N ellipses intersect. In some aspects, the entity that determined the intersection points at 458 can send information related to the position of an object (s) to the receivers that executed 452 and 454, and/or to any other suitable devices.

In some aspects, a receiving device can use

processes

400 and 450 in conjunction with one another to further improve precision.

In some aspects, 5G signals can be used to perform multi-node passive sensing, which can have several benefits. For example, because operations of UEs (e.g., UEs 106) are coordinated via a RAN (e.g., RAN 104) , interference, congestions, and channel collisions can be avoided. As another example, when used in vehicles, some road users (e.g., vehicles, bicycles, pedestrians, etc. ) may not be capable of communicating using vehicle to everything (V2X) techniques, thus making it impossible for a UE configured to use V2X to be aware of such road users through V2X communications.

As yet another example, because many obstructions are transparent to certain 5G signals, the coverage provided via multi-node passive sensing using 5G signals can be larger than coverage of a mono-static system. As still another example, at least in DL radio nodes are synchronized, and radio resources can be adjusted according to location needs (e.g., for use in detecting objects in particular areas) . As a further example, V2X can be used to provide reference position, Doppler information, and/or speed information of the receivers and/or transmitters, which can facilitate improved precision of the location estimates.

At another further example, locally estimated parameters (e.g., locations, speeds, ellipses, etc. associated with objects that are detected) can be efficiently exchanged with other UEs (e.g., via V2X communications, via enhanced mobile broadband (eMBB) communications, etc. ) . As yet another further example, a network operator can collect and provide dedicated information related to objects in an environment of 5G infrastructure (e.g., via V2X applications) . In a more particular example, the operator can charge UEs for access to such information. As another more particular example, the operator can provides UEs with access to such information at a discount (e.g., including free) in exchange for the UEs providing estimated parameters and/or assistance with coordination. As yet another further example, estimated parameters can be collected by 5G infrastructure that is installed for other purposes (e.g., road side units (RSUs) , base stations, etc. ) .

FIG. 5 is a block diagram illustrating a signal processing pipeline for estimating frequency domain channel responses in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 5, a receiver can receive a time domain (TD) signal sent by a transmitter. The receiver can perform orthogonal frequency divisional multiple access (OFDMA) synchronization, cyclic prefix (CP) removal, and/or a serial to parallel (S2P) conversion. This can be followed by the receiver performing a fast Fourier transform (FFT) , a frequency domain (FD) channel estimation, and/or a cyclic FD equalization. This can be used to recover one or more transmitted symbols.

In some aspects, the transmitted symbols can be used to calculate a symbol-wise channel frequency response by inverse filtering. A subsequent inverse FFT (iFFT) can generate a channel impulse response that indicates the multipath time delay, which is sometimes referred to as "fast time. " An output of the iFFT can be filtered using a Doppler FFT filter bank (D-FFT) that provides an output that represents the temporal changes of the impulse response. Object detection can then be carried out based on the delay-Doppler spreading function output by the D-FFT, which is sometimes referred to as a scattering function. A window size of the Doppler-FFT can be limited by the moving speed of the detected object (s) , and the respective delay relative to the width of any delay-bin on the "fast-time" axis. Maximizing the Doppler-FFT window size can facilitate SNR gain and can facilitate detection of weak object returns.

In some aspects, in order to perform a FD channel estimation, the receiver needs information that it can use to identify signals it receives from a particular transmitter. For example, a receiver (e.g., a UE 106, a BS 108, etc. ) can use information about a reference signal (RS) transmitted by the transmitter to perform an FD channel estimation. As another example, a receiver can improve detection and FD channel estimation by decoding transport blocks. In a more particular example, the receiver can use cyclic redundancy check (CRC) -correct decoded data to refine a channel estimation. In such examples, the modulated symbols corresponding to the decoded (and CRC-correct) data can be used to refine the estimated channel response (e.g., using techniques similar to techniques for estimating the channel response based on the RS) . Using multiple estimates based on the decoded data and the RS, the channel can be more accurately estimated, improving resolution of a position estimation based on the channel response. In some aspects, a receiver (e.g., a UE 106 in DL, a BS 108 in UL, a UE 106 in SL, etc. ) that has established an active communication session with a transmitter (e.g., a BS 108 in DL, a UE 106 in UL, another UE 106a in SL, etc. ) can use information related to the active communication session to perform an FD channel estimation. For example, if a UE 106 uses a transmission from a BS 108 or another transmitter that is intended for that UE, the UE 106 has information needed to perform FD channel estimation and to decode data in the transmission (e.g., if the signal is encoded with data) . However, if the receiver relied only on connections in which it is an active participant, it can limit the amount of transmitters that can be used by the receiver in a multi-node passive sensing process, or require an increase in active communications between the receiver and other transmitters leading to an increase in interference and/or a decrease in capacity to carry out normal communications.

In some aspects, a receiver can use signals transmitted for other receivers in a multi-node passive sensing process. However, the receiver does not normally have the information required to perform FD channel estimation for signals intended for other receivers.

FIG. 6 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. It should be understood by those of ordinary skill in the art that the various aspects of the present disclosure can be applied to a DFT-s-OFDMA waveform in substantially the same way as described herein below. That is, while some examples of the disclosed subject matter may focus on an OFDM link for clarity, it should be understood that the same principles can be applied as well to DFT-s-OFDMA waveforms.

Within the present disclosure, a frame can refer to a duration of 10 milliseconds (ms) for wireless transmissions, with each frame including 10 subframes of 1 ms each. On a given carrier, there may be one set of frames in the UL, and another set of frames in the DL. Referring now to FIG. 6, an expanded view of an exemplary DL subframe 602 is illustrated, showing an OFDM resource grid 604. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application can vary from the example described here, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones.

Resource grid 604 can be used to schematically represent time–frequency resources for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding multiple number of resource grids 604 can be available for communication. Resource grid 604 can be divided into multiple resource elements (REs) 606. An RE, which is 1 subcarrier × 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more bits of information. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 608, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB can include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, unless otherwise stated, it is assumed that a single RB such as RB 608 entirely corresponds to a single direction of communication (either transmission or reception for a given device) .

A UE generally utilizes only a subset of resource grid 604. An RB can be the smallest unit of resources that can be allocated to a UE. Thus, as more RBs are scheduled for a particular UE, the modulation scheme chosen for the air interface increases, and data rates that can be achieved by the UE also increase.

In FIG. 6, RB 608 is shown as occupying less than the entire bandwidth of subframe 602, with some subcarriers illustrated above and below RB 608. In a given implementation, subframe 602 can have a bandwidth corresponding to any number of one or more RBs 608. Further, in FIG. 6, RB 608 is shown as occupying less than the entire duration of subframe 602, although this is merely one possible example.

Each subframe 602 (e.g., a 1 ms subframe) can include one or multiple adjacent slots. In the example of FIG. 6, one subframe 602 includes four slots 610, as an illustrative example. In some examples, a slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot can include 7 or 14 OFDM symbols with a nominal CP. Additional examples can include mini-slots having a shorter duration (e.g., 1, 2, 4, or 7 OFDM symbols) . Such mini-slots can in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.

An expanded view of one of the slots 610 illustrates slot 610 including a control region 612 and a data region 614. In general, control region 612 can carry control channels (e.g., PDCCH) , and data region 614 can carry data channels (e.g., PDSCH or PUSCH) . Additionally or alternatively, a slot can contain various combinations of DL and UL, such as all DL, all UL, or at least one DL portion and at least one UL portion. The simple structure illustrated in FIG. 6 is merely an example, and different slot structures can be utilized, and can include one or more of each of the control region (s) and data region (s) .

Although not illustrated in FIG. 6, various REs 606 within an RB 608 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 606 within RB 608 can also carry pilot signals and/or reference signals. These pilot signals and/or reference signals can facilitate performance of channel estimation of the corresponding channel by a receiving device, which can enable coherent demodulation/detection of the control and/or data channels within RB 608. For example, reference signals can be used to convey information that a receiving device (e.g., a UE 106, a base station 108, an RSU) can use as a reference in relation to transmission or reception of information that is intended for the receiving device. In a particular example, a transmitter (e.g., base station 108) can transmit a demodulation reference signal (DMRS) for use by a particular UE (or other receiving device) in channel characterization (e.g., for use in estimating the channel over which the DMRS was sent) . As another example, a transmitter (e.g., base station 108, etc. ) can transmit a phase tracking reference signal (PTRS) for use by a particular receiver (e.g., over a particular channel associated with the transmitter and/or receiver) in tracking the phase of the local oscillator in the transmitter. As yet another example, a transmitter (e.g., UE 106) can transmit a sounding reference signal (SRS) for use by a receiver (e.g., base station 108) in channel characterization (e.g., for use in estimating the channel over which the SRS was sent) . As still another example, a transmitter (e.g., base station 108, etc. ) can transmit a channel state information reference signal (CSI-RS) for use by a particular receiver (e.g., UE 106) in channel characterization.

In a DL transmission, the transmitting device (e.g., base station 108) can allocate one or more REs 606 (e.g., within a control region 612) to carry DL control information (e.g., downlink control information 114 described above in connection with FIG. 1) including one or more DL control channels that generally carry information originating from higher layers, such as a physical broadcast channel (PBCH) , a physical downlink control channel (PDCCH) , etc., to one or more scheduled entities (e.g., a particular UE 106) . In addition, DL REs can be allocated to carry DL physical signals that generally do not carry information originating from higher layers. These DL physical signals can include a primary synchronization signal (PSS) ; a secondary synchronization signal (SSS) ; demodulation reference signals (DM-RS) ; phase-tracking reference signals (PT-RS) ; channel-state information reference signals (CSI-RS) ; etc.

The synchronization signals PSS and SSS (collectively referred to as SS) , and in some examples, the PBCH, can be transmitted in an SS block that includes 4 consecutive OFDM symbols (e.g., numbered via a time index in increasing order from 0 to 3) . In the frequency domain, the SS block can extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239. Of course, the disclosed subject matter is not limited to this specific SS block configuration. Other nonlimiting examples can utilize greater or fewer than two synchronization signals; can include one or more supplemental channels in addition to the PBCH; can omit a PBCH; and/or can utilize nonconsecutive symbols for an SS block, without departing from the scope of the present disclosure.

The PDCCH can carry downlink control information (DCI) for one or more UEs in a cell. This can include, but is not limited to, power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.

In a UL transmission, a transmitting device (e.g., UE 106) can utilize one or more REs 606 to carry UL control information (UCI) (e.g., uplink control information 118 described above in connection with FIG. 1) . The UCI can originate from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH) , a physical random access channel (PRACH) , etc., to the scheduling entity (e.g., base station 108) . Further, UL REs may carry UL physical signals that generally do not carry information originating from higher layers, such as demodulation reference signals (DM-RS) , phase-tracking reference signals (PT-RS) , sounding reference signals (SRS) , etc. In some examples, the control information (e.g., uplink control information 118) can include a scheduling request (SR) , i.e., a request for the scheduling entity 108 to schedule uplink transmissions. Here, in response to the SR transmitted on a control channel (e.g., over which uplink control information 118 is transmitted) , the scheduling entity (e.g., base station 108) can transmit downlink control information (e.g., downlink control information 114) that can schedule resources for uplink packet transmissions.

UL control information can also include hybrid automatic repeat request (HARQ) feedback such as an acknowledgment (ACK) or negative acknowledgment (NACK) , channel state information (CSI) , and/or any other suitable UL control information. HARQ is a technique well-known to those of ordinary skill in the art, in which the integrity of packet transmissions can be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) . If the integrity of the transmission confirmed, an ACK can be transmitted, whereas if not confirmed, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement chase combining, incremental redundancy, etc.

In addition to control information, one or more REs 606 (e.g., within the data region 614) can be allocated for user data or traffic data. Such traffic can be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH) ; or for an UL transmission, a physical uplink shared channel (PUSCH) .

In order for a UE to gain initial access to a cell, the RAN (e.g., RAN 104, 200) can provide system information (SI) characterizing the cell. This system information can be provided utilizing minimum system information (MSI) , and other system information (OSI) . The MSI can be periodically broadcast over the cell to provide the most basic information required for initial cell access, and for acquiring any OSI that may be broadcast periodically or sent on-demand. In some examples, the MSI can be provided over two different downlink channels. For example, the PBCH can carry a master information block (MIB) , and the PDSCH can carry a system information block type 1 (SIB1) , which is sometimes referred to as the remaining minimum system information (RMSI) .

OSI can include any SI that is not broadcast in the MSI. In some examples, the PDSCH can carry multiple SIBs, not limited to SIB1, described above. Here, the OSI can be provided in these SIBs, e.g., SIB2 and/or above.

The channels or carriers described above and illustrated in FIGS. 1 and 6 are not necessarily all the channels or carriers that can be utilized between a scheduling entity (e.g., base station 108) and scheduled entities (e.g., UEs 106) , and those of ordinary skill in the art will recognize that other channels or carriers can be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

These physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TB) . The transport block size (TBS) , which can correspond to a number of bits of information, can be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

FIG. 7 is a schematic illustration of resource allocations of wireless resources in an air interface utilizing OFDM in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 7, different portions of the OFDM resource grid can be allocated to different UEs. In DL, signals targeted toward different UEs can be jointly processed to cover a large portion of the resource grid in frequency if they all originate from the same transmitter because all of the different signals would have the same multipath propagation for each object. This can improve precision when calculating ellipses corresponding to an object (e.g., as described above in connection with FIGS. 3-5) . In UL and/or SL transmissions, however, the different parts of the resource grid that are associated with different UEs (and/or other transmitters that are not scheduling entities) need to be separately processed by the receiver, because the different transmitters are not co-located. This causes the multipath propagation to be different from each transmitter. This can degrade performance due to the sparse occupation of each signal in the frequency-time plane.

FIG. 8 is a schematic illustration of resource allocation patterns segmented in a plot of frequency domain and time domain in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 8, in some aspects, RS configuration information can, among other things, include an indication of a pattern of resources in the time domain (TD) and/or frequency domain (FD) that a particular transmitter expects (e.g., has been assigned) to use to transmit one or more RSs. As described in connection with FIG. 8, and below in connection with FIGS. 9 and 12 to 14, RS configuration information can more generally include any suitable information that a device (e.g., a UE, a base station, an RSU, etc. ) can use to detect a reference signal that was transmitted between two other devices for a purpose other than passive radar sensing. In some aspects, a pattern of resources can correspond to a set of resources for a receiver to monitor for one or more RSs. For example, each set of resources can include one or more FD properties and/or one or more TD properties for the receiver to potentially monitor. In some aspects, each pattern can correspond to a set of resources.

In some aspects, RS configuration information can include information about a portion of FD resources that the transmitter expects to use. For example, RS configuration information associated with a transmitter can include an indication of a group of one or more physical resource blocks (PRBs) within a particular bandwidth part (BWP) . In such an example, the BWP may or may not be an active BWP used by the receiver (e.g., by a UE during a DL) . In a particular example, the BWP designated by the transmitter can be in a non-active BWP for the receiver.

As another example, RS configuration information associated with a transmitter can include an indication of a BWP or multiple BWPs that the transmitter expects to use to transmit an RS. In such an example, the BWP or BWPs may or may not correspond to an active BWP used by the receiver (e.g., by a UE during a DL) . In a particular example, at least a portion of the BWP designated by the transmitter can be in a non-active BWP for the receiver.

As yet another example, RS configuration information associated with a transmitter can include an indication of a component carrier (CC) or multiple CCs that the transmitter expects to use to transmit an RS. In such an example, the CC or CCs may or may not correspond to an active CC used by the receiver (e.g., by a UE during a DL) . In a particular example, at least one of the CCs designated by the transmitter can be a CC that is not used by the receiver.

As still another example, RS configuration information associated with a transmitter can include an indication of a radio access technology (RAT) or multiple RATs that the transmitter expects to use to transmit an RS. In such an example, at least one RAT associated with the transmitter may not correspond to a RAT used by the receiver (e.g., by a UE during a DL) .

In some aspects, RS configuration information can include information about a portion of TD resources that the transmitter expects to use. For example, RS configuration information associated with a transmitter can include one or more symbols (e.g., OFDM symbols) that the transmitter expects to use to transmit an RS. As another example, RS configuration information associated with a transmitter can include one or more slots (e.g., OFDM slots) that the transmitter expects to use to transmit an RS. As yet another example, RS configuration information associated with a transmitter can include one or more subframes (e.g., OFDM subframes) that the transmitter expects to use to transmit an RS. As still another example, RS configuration information associated with a transmitter can include one or more frames (e.g., OFDM frames) that the transmitter expects to use to transmit an RS. As another example, RS configuration information associated with a transmitter can include one or more time domain units that the transmitter expects to use to transmit an RS.

In some aspects, the RS configuration information can indicate multiple FD-TD blocks (e.g., as shown in FIG. 8) , corresponding to different combinations of FD and TD resources. For example, in different FD-TD blocks provided by a transmitter (e.g., a UE, a RSU, etc. ) , the same or different RS patterns can be identified (e.g., the different blocks can correspond to the same pattern of resources or different patterns of resources) . In a particular example, a transmitter can specify a first FD-TD block for a first type of RS (e.g., a demodulation reference signal (DMRS) used to demodulate a physical downlink shared channel (PDSCH) ) can be different from an FD-TD block for a second type of RS (e.g., a positioning reference signal (PRS) ) .

In some aspects, an FD-TD block can be identified using any suitable information, such as information that can be used to identify and/or use a DMRS associated with the transmitter. For example, RS configuration information shared by a transmitter can include a UE-specific ID needed to identify a DMRS-sequence (e.g., a DMRS scrambling ID) . As another example, RS configuration information shared by a transmitter can include an OFDM symbol index or indices of the DMRS symbol (s) . As yet another example, RS configuration information shared by a transmitter can include a comb type corresponding to one or more RSs (e.g., comb-2, comb-4) . As still another example, RS configuration information shared by a transmitter can include a DMRS port ID or multiple DMRS port IDs. As a further example, RS configuration information shared by a transmitter can include a code division multiplexing (CDM) -group ID associated with the transmitter. As another further example, RS configuration information shared by a transmitter can include an energy per resource element (EPRE) -ratio with data symbols. As yet another further example, RS configuration information shared by a transmitter can include quasi co-location (QCL) information. In some aspects, such information can correspond to one or more resource parameters corresponding to resources for the UE to monitor for one or more RSs.

FIG. 9 is a schematic illustration of resource allocation patterns segmented in a plot of frequency domain, time domain, and a space/coding domain in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 9, in some aspects, multiple RS resources can overlap in the FD-TD plane, and can be multiplexed via spatial and/or code multiplexing. As shown in FIG. 9, multiple RS resources can be fully overlapping the FD-TD plane, or partially overlapping. In some aspects, overlapping FD-TD resources can be differentiated from each other based on information related to the DMRS. For example, different overlapping FD-TD patterns can be differentiated through the use of different DMRS port IDs. As another example, different overlapping FD-TD patterns can be differentiated through the use of different DMRS scrambling IDs. In some aspects, RS configuration information can include information relating to one or more port IDs and/or one or more scrambling IDs for the UE to monitor for RSs (e.g., for use in passive sensing) .

FIG. 10 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity 1000 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation... For example, scheduling entity 1000 can be a user equipment (UE) as illustrated in any one or more of FIGS. 1 and/or 2. In another example, scheduling entity 1000 can be a base station as illustrated in any one or more of FIGS. 1 and/or 2.

In some aspects, scheduling entity 1000 can be implemented with a processing system 1014 that includes one or more processors 1004. Examples of processors 1004 include central processing units (CPUs) , microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , graphics processing units (GPUs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. In various examples, scheduling entity 1000 can be configured to perform any one or more of the functions described herein. That is, processor 1004, as utilized in scheduling entity 1000, can be used to implement any one or more of the processes and procedures described below in connection with FIGS. 12 to 14 and 17 to 19.

In this example, processing system 1014 can be implemented with a bus architecture, represented generally by the bus 1002. Bus 1002 can include any number of interconnecting buses and bridges depending on the specific application of processing system 1014 and the overall design constraints. Bus 1002 can communicatively couple together various circuits including one or more processors (represented generally by processor 1004) , memory 1005, and computer-readable media (represented generally by computer-readable medium 1006) . Bus 1002 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface 1008 can provide an interface between bus 1002 and a transceiver 1010. Transceiver 1010 can provide a communication interface or means for communicating with various other apparatus over a transmission medium. Depending upon the nature of the apparatus, a user interface 1012 (e.g., keypad, display, speaker, microphone, joystick) can also be provided. Of course, such a user interface 1012 can be omitted in some examples, such as a base station.

In some aspects of the disclosed subject matter, processor 1004 can include data decoding information sharing circuitry 1040 configured for various functions, including, for example, collecting and sharing data decoding information received from one or more transmitters. Data decoding information can include any suitable information that a device (e.g., a scheduling device 1000, or a scheduled device as described below in connection with FIG. 11) can use to decode at least a portion of an encoded signal that was transmitted by another device for a purpose other than passive radar sensing. For example, such an encoded signal can include information (e.g., an encrypted packet) that is intended for a remote endpoint (e.g., a server, a remote UE, etc. ) . As another example, such an encoded signal can include information that is intended for receipt by a local scheduling entity or scheduled entity for the purposes of scheduling communications over a RAN (e.g., as described above in connection with FIG. 6) . Examples of information that can be included in data decoding information, and examples of techniques that can be used to provide data decoding information are described below in connection with FIGS. 15-19. For example, data decoding information sharing circuitry 1040 can be configured to implement one or more of the functions described below in connection with FIGS. 17 and 18, such as functions described in connection with 1702, 1704, and/or 1706, and/or in connection with 1802 and/or 1804. Additionally, in some aspects, processor 1004 can include encoded data monitoring circuitry 1042 configured for various functions, including, for example, monitoring resources (e.g., a portion of an FD-TD resource grid) for encoded signals transmitted by one or more transmitters for use in multi-node passive sensing. For example, encoded data monitoring circuitry 1042 can be configured to implement one or more of the functions described below in connection with FIG. 19, such as functions described in connection with 1504 and/or 1506.

Processor 1004 can manage bus 1002 and can perform general processing, including the execution of software stored on computer-readable medium 1006, which, when executed by processor 1004, causes processing system 1014 to perform the various functions described below (e.g., in connection with FIGS. 12 to 14) for any particular apparatus. In some aspects, computer-readable medium 1006 and memory 1005 can also be used for storing data that is manipulated by processor 1004 when executing software.

One or more processors 1004 in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software can reside on a computer-readable medium 1006. The computer-readable medium 1006 can be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1006 can reside in the processing system 1014, external to the processing system 1014, or distributed across multiple entities including the processing system 1014. The computer-readable medium 1006 can be embodied in a computer program product. By way of example, a computer program product can include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

In one or more examples, computer-readable storage medium 1006 can include data decoding information sharing software 1052 configured for various functions, including, for example, collecting and sharing data decoding information received from one or more transmitters. For example, data decoding information sharing software 1052 can be configured to implement one or more of the functions described below in connection with FIGS. 17 and 18, such as functions described in connection with 1702, 1704, and/or 1706, and/or in connection with 1802 and/or 1804. Additionally, in some aspects, computer-readable storage medium 1006 can include encoded data monitoring software 1054 configured for various functions, including, for example, monitoring resources (e.g., a portion of an FD-TD resource grid) for encoded signals transmitted by one or more transmitters for use in multi-node passive sensing. For example, encoded data monitoring software 1054 can be configured to implement one or more of the functions described below in connection with FIG. 19, such as functions described in connection with 1904 and/or 1906.

FIG. 11 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity 1100 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. For example, scheduled entity 1100 can be a user equipment (UE) as illustrated in any one or more of FIGS. 1 and/or 2. In accordance with some aspects of the disclosure, an element, or any portion of an element, or any combination of elements can be implemented with a processing system 1114 that includes one or more processors 1104.

In some aspects, processing system 1114 can be substantially the same as the processing system 1014 illustrated in FIG. 10, including a bus interface 1108, a bus 1102, memory 1105, processor 1104, and a computer-readable medium 1106. Furthermore, scheduled entity 1100 can include a user interface 1112 and a transceiver 1110 substantially similar to those described above in FIG. 10. That is, processor 1104, as utilized in a scheduled entity 1100, can be used to implement any one or more of the processes described below in connection with, and illustrated in, FIGS. 12 to 14 and 17 to 19.

In some aspects of the disclosure, processor 1104 can includedata decoding information receiving circuitry 1140 configured for various functions, including, for example, receiving data decoding information associated with one or more transmitters shared by a transmitter (which may or may not be in the group of one or more transmitters) . For example, data decoding information receiving circuitry 1140 can be configured to implement one or more of the functions described below in connection with FIGS. 17 and/or 19, such as functions described below in connection with 1702 and/or 1904. Additionally, in some aspects, processor 1104 can include encoded data monitoring circuitry 1142 configured for various functions, including, for example, monitoring resources (e.g., a portion of an FD-TD resource grid) for encoded signals transmitted by one or more transmitters for use in multi-node passive sensing. For example, encoded data monitoring circuitry 1142 can be configured to implement one or more of the functions described below in connection with FIG. 19, such as functions described in connection with 1904 and/or 1906.

In one or more examples, computer-readable storage medium 1106 can include data decoding information receiving software 1152 configured for various functions, including, for example, receiving data decoding information associated with one or more transmitters shared by a transmitter (which may or may not belong to the one or more transmitters) . For example, data decoding information receiving software 1152 can be configured to implement one or more of the functions described below in connection with FIGS. 17 and/or 19, such as functions described below in connection with 1702 and/or 1904. Additionally, in some aspects, computer-readable storage medium 1106 can include encoded data monitoring software 1154 configured for various functions, including, for example, monitoring resources (e.g., a portion of an FD-TD resource grid) for encoded signals transmitted by one or more transmitters for use in multi-node passive sensing. For example, encoded data monitoring software 1154 can be configured to implement one or more of the functions described below in connection with FIG. 19, such as functions described in connection with 1904 and/or 1906.

FIG. 12 is a flow chart illustrating an example process 1200 for sharing Reference Signal (RS) configuration information for one or more entities in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1200 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1200 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1202, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive reference signal (RS) configuration information associated with one or more transmitters (e.g., transmitters that form part of a multi-node passive sensing system) . In some aspects, the entity can receive the RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the RS configuration information can include an explicit indication that the RS configuration information can be used by receivers for purposes other than decoding, transmitting, channel characterization, or synchronization (e.g., receivers that utilize the multi-node passive sensing system) . Note that there may not be any preexisting relationship between devices that together form the multi-node passive sensing system. In some aspects, the entity can receive RS configuration from different transmitters at different times (e.g., when a transmitter, such as a UE, enters a cell associated with the entity) . In some aspects, the RS configuration information received at 1202 can be a portion (e.g., less than all) RS configuration information associated with the one or more transmitters. For example, the RS configuration information received at 1202 can be a portion of RS configuration information that can be used for passive sensing. In some aspects, 1202 can be omitted. For example, a device executing process 1200, such as a base station, can maintain RS configuration information associated with scheduled entities, such that 1202 may be unnecessary. Note that the entity executing process 1200 may or may not identify a particular RS with a specific transmitter. For example, the information received by the entity executing the process can be information relating to an antenna port, QCL information, and/or an RS without specifically identifying a transmitter associated the antenna port, the QCL information, and/or the RS.

At 1204, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive a request from a UE (or other receiver) for RS configuration information associated with one or more nearby transmitters. In some aspects, the entity can receive the request for RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the request for RS configuration information can be associated with an explicit indication that the requested RS configuration information is for use in a multi-node passive sensing process. Note that the entity that receives the RS configuration information at 1202 can be the same or different from the entity that receives the request at 1204. For example, an RSU can collect RS configuration information and provide that information to nearby base stations, which can receive the request 1204. In some aspects, 1204 can be omitted. For example, RS configuration information can be broadcast periodically (e.g., at regular and/or irregular intervals) .

At 1206, an entity can determine that sharing of the RS configuration information is permitted. For example, in some aspects, the entity can determine that the RS configuration information can be shared for the purpose of multi-node passive sensing. In a more particular example, the entity can determine that the RS configuration information can be shared for the purpose of multi-node passive sensing based on an explicit indication received from the transmitter (s) that provided the RS configuration information at 1202. As another more particular example, the entity can determine that the RS configuration information can be shared for the purpose of multi-node passive sensing based on the RS configuration information being received at 1202. In some aspects, process 1200 can end if the request at 1204 was not associated with an explicit indication that the requested RS configuration information is for use in a multi-node passive sensing process and/or if the RS configuration information was not associated with an explicit indication that the RS configuration information can be used by receivers that utilize the multi-node passive sensing system. Additionally or alternatively, in some aspects, the entity can determine not to share requested RS configuration information for any other suitable reason.

At 1208, an entity can transmit RS configuration information for one or more nearby transmitters to the UE (or other receiver) that requests RS configuration information at 1204. In some aspects, the entity can transmit the RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the RS configuration information can include an indication that RSs associated with the RS configuration information can only be used for limited or restricted purposes, such as passive sensing. Additionally or alternatively, in some aspects, the RS configuration information can include an indication that the RSs associated with the RS configuration information can be used for purposes other than decoding or transmitting data, such as passive sensing. For example, the RS configuration information can include an indication that at least a certain part of the RS configuration information is for use by the UE (or other receiver) to carry out a passive sensing process. As another example, the RS configuration information can include an indication that at least a certain part of the RS configuration information is not to be used by the UE (or other receiver) to decode or transmit any signals. As yet another example, the RS configuration information can include an indication that no HARQ-ACK feedback is needed from the UE (or other receiver) in connection with the RS configuration information.

In some aspects, the entity can transmit only RS configuration information that is not already targeted at the UE (or other receiver) that requested RS configuration information at 1204. In some aspects, an RS can be targeted at a particular receiver if the RS is scheduled for the purpose of that particular receiver using the RS as a reference to conduct further communications. For example, an RS can be targeted at a particular receiver that is expected to use the RS for the purpose of properly receiving and/or decoding communications from a transmitter that is scheduled to (and/or has already) transmitted the RS. In a more particular example, a base station can target a particular UE with an RS that the UE uses as a reference to receive other signals transmitted to that particular UE. In another more particular example, a UE can target one or more base stations with an RS that the base station (s) uses as a reference to receive other signals transmitted by that particular UE. As yet another example, a first UE can target a second UE (neither of which is the UE that requested RS configuration information at 1204) with an RS that the second UE uses as a reference to receive other signals transmitted by the first UE to the second UE. As described above an RS can be used to estimate a channel response of a channel used to transmit information to the receiver characterizing the channel. As another example, an RS can be targeted at a particular receiver that is expected to use the RS for the purpose of synchronizing transmission of signals with the device that transmitted the RS. As yet another example, if the UE that requested the RS configuration information at 1204 is requesting the RS configuration only for purposes other than transmission of information, reception of information directed to the UE (e.g., the RS may be used for reception of information directed to another receiver for use in a multi-node passive sensing process, but are not used to receive messages and/or information elements directed to the UE) , channel characterization for reception of information directed to the UE, or synchronization of communications to/from the UE to another device.

In some aspects, the RS configuration information can be transmitted using any suitable channel, format, technique, or combination of techniques. For example, the RS configuration information can be transmitted using one or more of the following: a radio resource control (RRC) message; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a dedicated physical sidelink shared channel (PDSCH) message; a message transmitted using a dedicated physical (PHY) layer channel (e.g., a PHY RS-Info Indication Channel (PRICH) ) ; and/or a CORESET ID and a corresponding search space. Note that if a CORESET ID is used to convey RS configuration information the UE (or other receiver) may already be configured with one or more search spaces and CORESETs for physical downlink control channel (PDCCH) monitoring. In some aspects, the additional CORESET and SS can be used by the UE (or other receiver) to identify the DMRS for sensing purposes, and the UE can inhibit them from being used for PDCCH monitoring.

In a particular example, for RS configuration information conveyed via DCI, the DCI can be a group-common DCI (GC-DCI) , can be conveyed via PDCCH and/or PDSCH, and/or can be one part or both parts of a 2-stage DCI.

In another particular example, for RS configuration information conveyed via SCI, the SCI can be conveyed via PSCCH and/or PSSCH, and/or can be one part or both parts of a 2-stage SCI.

In some aspects, an indication associated with the RS configuration information can indicate if the RS configuration information is associated with a DL RS, a UL RS, and/or a SL RS.

In some aspects, an RS associated with the RS configuration information can be one or more of the following types of RS: a demodulation reference signal (e.g., for physical uplink shared channel (PUSCH) , PDSCH, physical uplink control channel (PUCCH) , PDCCH, etc. ) ; channel state information (CSI) -RS; CSI tracking reference signal (CSI-TRS) ; positioning reference signal (PRS) ; phase tracking reference signal (PTRS) ; sounding reference signal (SRS) ; and/or any other suitable reference signal.

FIG. 13 is a flow chart illustrating an example process 1300 for an entity sharing RS configuration information associated with its own RS transmissions in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1300 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1300 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1302, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive a request from a UE (or other receiver) for RS configuration information. In some aspects, the entity can receive the request for RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the request for RS configuration information can be associated with an explicit indication that the requested RS configuration information is for use in a multi-node passive sensing process.

At 1304, the entity can determine that sharing of the RS configuration information is permitted. For example, in some aspects, the entity can determine that the RS configuration information can be shared for the purpose of multi-node passive sensing. In a more particular example, the entity can determine that the RS configuration information can be shared for the purpose of multi-node passive sensing based on an explicit indication (e.g., in memory) that the RS configuration information can be shared for the purpose of multi-node passive sensing. In some aspects, process 1300 can end if the request at 1302 was not associated with an explicit indication that the requested RS configuration information is for use in a multi-node passive sensing process and/or if the RS configuration information cannot be shared with receivers for multi-node passive sensing. Additionally or alternatively, in some aspects, the entity can determine not to share the RS configuration information for any other suitable reason.

At 1306, the entity can transmit RS configuration information associated with the entity's RS transmissions to the UE (or other receiver) that requested RS configuration information at 1302. In some aspects, the entity can transmit the RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the RS configuration information can be associated with one or more dependencies that restrict the use of the RS configuration as described above in connection with 1208. In some aspects, the RS configuration information can be transmitted using any suitable technique or combination of techniques, such as techniques described above in connection with FIG. 12. In some aspects, an indication associated with the RS configuration information can indicate if the RS configuration information is associated with a DL RS, a UL RS, and/or a SL RS.

In some aspects, the RS associated with the RS configuration information can be one or more of the following types of RS: a demodulation reference signal (e.g., for physical uplink shared channel (PUSCH) , PDSCH, physical uplink control channel (PUCCH) , PDCCH) ; channel state information (CSI) -RS; CSI tracking reference signal (CSI-TRS) ; positioning reference signal (PRS) ; phase tracking reference signal (PTRS) ; sounding reference signal (SRS) ; and/or any other suitable reference signal.

FIG. 14 is a flow chart illustrating an example process 1400 for using RS configuration information to facilitate multi-node passive sensing in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1400 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1400 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1402, a receiver (e.g., a UE, a base station, a RSU, etc. ) can request reference signal (RS) configuration information associated with one or more nearby transmitters (e.g., one or more UEs, base stations, RSUs, etc. ) . In some aspects, the receiver can request the RS configuration information using one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the receiver can request the RS configuration information from any suitable transmitter or transmitters. For example, the receiver can request the RS configuration information from a base station during UL. As another example, the receiver can request the RS configuration information from a UE during DL (e.g., if the receiver is a base station) . As yet another example, the receiver can request the RS configuration information from another entity via a sidelink connection. In some aspects, 1402 can be omitted. For example, a transmitter can provide RS configuration information that is not sent in response to an explicit request from the receiver (e.g., a request can come from another entity, such as a base station, or from the core network) .

At 1404, the receiver can receive RS configuration information associated with one or more transmitters. In some aspects, the receiver can receive RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the RS configuration information can include information about multiple RSs used by a particular transmitter. In some aspects, the RS configuration information can be associated with one or more dependencies that restrict the use of the RS configuration as described above in connection with 1208. In some aspects, the RS configuration information can be received using any suitable technique or combination of techniques, such as techniques described above in connection with FIG. 12. In some aspects, an indication associated with the RS configuration information can indicate if the RS configuration information is associated with a DL RS, a UL RS, and/or a SL RS.

At 1406, the receiver can monitor resources specified by RS configuration information associated with one or more nearby transmitters. For example, the receiver can monitor FD-TD resources associated with the RS configuration information using one or more transceivers. In a more particular example, the receiver can attempt to detect RSs corresponding to FD-TD resources associated with the RS configuration information by sampling and buffering a received wireless signal, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.

At 1408, the receiver can receive reference signals (RSs) originating from one or more nearby transmitters. As described above in connection with FIGS. 3 to 5, the same RS transmitted by a particular transmitter can be received multiple times, including a line of sight signal and one or more multipath reflected signals. For example, because the receiver has access to the RS configuration information, the receiver can detect an RS associated with the RS configuration information by using information about the RS as a pilot signal (e.g., as described above in connection with FIGS. 3 and 5) . Without RS configuration information (e.g., without having access to the DMRS associated with the receiver for which the RS was intended) , the receiver cannot properly detect an RS intended for another device, and hence cannot properly estimate the channel response.

At 1410, the receiver can estimate a frequency domain (FD) channel response of the received signals using the received RS configuration information. In some aspects, the receiver can estimate the FD channel response using any suitable technique or combination of techniques. For example, the receiver can estimate the frequency domain channel response using techniques described above in connection with FIGS. 3 and 5. In some aspects, the receiver can estimate the FD channel response for RSs received from multiple transmitters.

At 1412, the receiver can determine ellipses associated with an object based on the estimated frequency domain channel response of various RSs. In some aspects, the receiver can determine ellipses using any suitable technique or combination of techniques. For example, the receiver can determine ellipses associated with RSs received from various transmitters using techniques described above in connection with FIGS. 3 and 5.

At 1414, the receiver can act as a transmitter, and can transmit an RS using RS configuration information that has been shared with at least one other transmitter for use in multi-node passive sensing. For example, the receiver can act as a portion of a multi-node passive sensing system that can be used by other receivers to locate objects in the environment. In some aspects, the receiver can transmit the RS configuration information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) .

FIG. 15 is a schematic illustration of resource allocation patterns for encoded data segmented in a plot of frequency domain and time domain in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 15, in some aspects, data decoding information can be indicative of a pattern of resources in the time domain (TD) and/or frequency domain (FD) that a particular transmitter expects (e.g., has been assigned) to use to transmit data that can be used in a multi-node passive sensing process. In some aspects, a pattern of resources can correspond to a set of resources for a receiver to monitor for one or more encoded signals. For example, each set of resources can include one or more FD properties and/or one or more TD properties for the receiver to potentially monitor. In some aspects, each pattern can correspond to a set of resources.

In some aspects, data decoding information can include information about a portion of FD resources that the transmitter expects to use. For example, data decoding information associated with a transmitter can include an indication of a group of one or more physical resource blocks (PRBs) within a particular bandwidth part (BWP) . In such an example, the BWP may or may not be an active BWP used by the receiver (e.g., by a UE during a DL) . In a particular example, the BWP that the transmitter designates in the data decoding information can be in a non-active BWP for the receiver.

As another example, data decoding information associated with a transmitter can include an indication of a BWP or multiple BWPs that the transmitter expects to use to transmit an RS. In such an example, the BWP or BWPs may or may not correspond to an active BWP used by the receiver (e.g., by a UE during a DL) . In a particular example, at least a portion of the BWP designated by the transmitter can be in a non-active BWP for the receiver.

As another example, data decoding information associated with a transmitter can include an indication of a component carrier (CC) or multiple CCs that the transmitter expects to use to transmit an RS. In such an example, the CC or CCs may or may not correspond to an active CC used by the receiver (e.g., by a UE during a DL) . In a particular example, at least one of the CCs designated by the transmitter can be a CC that is not used by the receiver.

As still another example, data decoding information associated with a transmitter can include an indication of a radio access technology (RAT) or multiple RATs that the transmitter expects to use to transmit an RS. In such an example, at least one RAT associated with the transmitter may not correspond to a RAT used by the receiver (e.g., by a UE during a DL) .

In some aspects, data decoding information can include information about a portion of TD resources that the transmitter expects to use. For example, data decoding information associated with a transmitter can include information that identifies one or more symbols (e.g., OFDM symbols) that the transmitter expects to use to transmit encoded data (e.g., encoded data that can be used in a multi-node sensing process) . As another example, data decoding information associated with a transmitter can include information that identifies one or more slots (e.g., OFDM slots) that the transmitter expects to use to transmit encoded data. As yet another example, data decoding information associated with a transmitter can include information that identifies one or more subframes (e.g., OFDM subframes) that the transmitter expects to use to transmit encoded data. As still another example, data decoding information associated with a transmitter can include information that identifies one or more frames (e.g., OFDM frames) that the transmitter expects to use to transmit encoded data. As another example, data decoding information associated with a transmitter can include information that identifies one or more time domain units that the transmitter expects to use to transmit encoded data.

In some aspects, the data decoding information can indicate multiple FD-TD blocks (e.g., as shown in FIG. 15) , corresponding to different combinations of FD and TD resources. For example, in data decoding information that a transmitter (e.g., a UE, a RSU, etc. ) provides, within different FD-TD blocks, the same or different patterns of resources can be identified (e.g., the different blocks can correspond to the same pattern of resources or different patterns of resources) . In a particular example, a transmitter can specify a first FD-TD block for data sent from and/or for a particular UE, which can be different from an FD-TD block for data sent from and/or for a different UE.

In some aspects, an FD-TD block can be identified using any suitable information, such as information that can be used to decode encoded data transmitted by a transmitter. For example, data decoding information shared by a transmitter can include a radio network temporary identifier (RNTI) associated with the transmitter. As another example, data decoding information shared by a transmitter can include a scrambling ID associated with the transmitter. As yet another example, data decoding information shared by a transmitter can include rate-matching information associated with the transmitter. As a further example, data decoding information shared by a transmitter can include a UE-specific ID needed to identify a DMRS-sequence (e.g., a DMRS scrambling ID) . As another further example, data decoding information shared by a transmitter can include an OFDM symbol index or indices of the DMRS symbol (s) . As yet another further example, data decoding information shared by a transmitter can include a comb type corresponding to one or more encoded signals (e.g., comb-2, comb-4) . As still another example further example, data decoding information shared by a transmitter can include a DMRS port ID or multiple DMRS port IDs. As an additional example, data decoding information shared by a transmitter can include a code division multiplexing (CDM) -group ID associated with the transmitter. As another additional example, data decoding information shared by a transmitter can include an energy per resource element (EPRE) -ratio with data symbols. As yet another additional example, data decoding information shared by a transmitter can include quasi co-location (QCL) information. In some aspects, such information can correspond to one or more resource parameters corresponding to resources for the UE to monitor for one or more encoded signals. As still another additional example, data decoding information can include information in any suitable DCI format (e.g., a DCI forma 0_0, a DCI format 0_1, a DCI format 1_0, or a DCI format 1_1) that can identify a resource that may be used to transmit encoded data. As a further additional example, data decoding information can include information indicating an SCI format that may be used to transmit encoded data. As another further example, data decoding information can include information indicating information in a DCI format that may be used to transmit encoded data using a PSSCH. As another further additional example, data decoding information can include a frequency domain resource assignment (FDRA) . As another further additional example, data decoding information can include a time domain resource assignment (TDRA) .

FIG. 16 is a schematic illustration of resource allocation patterns for encoded data segmented in a plot of frequency domain, time domain, and a space/coding domain in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As shown in FIG. 16, in some aspects, multiple data decoding resource patterns can overlap in the FD-TD plane, and can be multiplexed via spatial and/or code multiplexing. As shown in FIG. 16, multiple data decoding resource patterns can be fully overlapping in the FD-TD plane, or partially overlapping. In some aspects, overlapping FD-TD resources can be differentiated from each other based on information related to DMRS information used to demodulate signals associated with resources corresponding to the pattern. For example, different overlapping FD-TD patterns can be differentiated through the use of different DMRS port IDs. As another example, different overlapping FD-TD patterns can be differentiated through the use of different DMRS scrambling IDs. In some aspects, RS configuration information can include information relating to one or more port IDs and/or one or more scrambling IDs for the UE to monitor for RSs (e.g., for use in passive sensing) .

FIG. 17 is a flow chart illustrating an example process for sharing data decoding information for one or more entities in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1700 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1700 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1702, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive data decoding information associated with one or more transmitters (e.g., transmitters that form part of a multi-node passive sensing system) . In some aspects, the entity can receive the data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the data decoding information can include an explicit indication that the data decoding information can be used by receivers for purposes other than decoding data that is scheduled for the entity to receive (e.g., receivers that utilize the multi-node passive sensing system) . Note that there may not be any preexisting relationship between devices that together form the multi-node passive sensing system. In some aspects, the entity can receive data decoding information from different transmitters at different times (e.g., when a transmitter, such as a UE, enters a cell associated with the entity) . In some aspects, the RS configuration information received at 1202 can be a portion (e.g., less than all) RS configuration information associated with the one or more transmitters. For example, the RS configuration information received at 1202 can be a portion of RS configuration information that can be used for passive sensing. In some aspects, 1202 can be omitted. For example, a device executing process 1200, such as a base station, can maintain RS configuration information associated with scheduled entities, such that 1202 may be unnecessary. Note that the entity executing process 1200 may or may not identify a particular RS with a specific transmitter. For example, the information received by the entity executing the process can be information relating to an antenna port, QCL information, and/or an RS without specifically identifying a transmitter associated the antenna port, the QCL information, and/or the RS.

At 1704, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive a request from a UE (or other receiver) for data decoding information associated with one or more nearby transmitters. In some aspects, the entity can receive the request for data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the request for data decoding information can be associated with an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process. Note that the entity that receives the data decoding information at 1702 can be the same or different from the entity that receives the request at 1704. For example, an RSU can collect data decoding information and provide that information to nearby base stations, which can receive the request 1704. In some aspects, 1704 can be omitted. For example, data decoding information can be broadcast periodically (e.g., at regular and/or irregular intervals) . In some aspects, the data decoding information can include only decoding information that can be used to decode signals at the physical layer, which can leave higher layer data transmitted to or from a UE encrypted and inaccessible to an entity in possession of the data decoding information.

At 1706, an entity can determine that sharing of the data decoding information is permitted. For example, in some aspects, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing. In a more particular example, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing based on an explicit indication received from the transmitter (s) that provided the data decoding information at 1702. As another more particular example, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing based on the data decoding information being received at 1202. In some aspects, process 1700 can end if the request at 1704 was not associated with an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process and/or if the data decoding information was not associated with an explicit indication that the data decoding information can be used by receivers that utilize the multi-node passive sensing system. Additionally or alternatively, in some aspects, the entity can determine not to share requested data decoding information for any other suitable reason.

At 1708, an entity can transmit data decoding information for one or more nearby transmitters to the UE (or other receiver) that requests data decoding information at 1704. In some aspects, the data decoding information can include an indication that encoded signals associated with the data decoding information can only be used for limited or restricted purposes. In some aspects, the entity can transmit the data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . Additionally or alternatively, in some aspects, the RS configuration information can include an indication that the RSs associated with the RS configuration information can be used for purposes other than decoding or transmitting data, such as passive sensing. For example, the data decoding information can include an indication that at least a certain part of the RS configuration information is for use by the UE (or other receiver) to carry out a passive sensing process. As another example, the data decoding information can include an indication that at least a certain part of the data decoding information is not to be used by the UE (or other receiver) to schedule the UE to receive the encoded data (e.g., encoded in one or more packets) . As yet another example, the data decoding information can include an indication that no HARQ-ACK feedback is needed from the UE (or other receiver) in connection with the data decoding information. As still another example, the data decoding information can be associated with an indication that no HARQ-ACK feedback is needed from the UE (or other receiver) when the UE has received and/or decoded the encoded data.

In some aspects, the data decoding information can be transmitted using any suitable channel, format, technique, or combination of techniques. For example, the data decoding information can be transmitted using one or more of the following: radio resource control (RRC) message; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) (e.g., scheduling physical sidelink shared channel (PUSCH) ) ; DCI and/or SCI included in a PDSCH, physical downlink control channel (PDCCH) , physical sidelink control channel (PDCCH) , and/or physical sidelink shared channel (PDSCH) message; a dedicated PDSCH message; a dedicated PDSCH message; a message transmitted using a dedicated physical (PHY) layer channel (e.g., a PHY RS-Info Indication Channel (PRICH) ) ; and/or a CORESET ID and a corresponding search space (SS) . Note that if a CORESET ID is used to convey data decoding information the UE (or other receiver) may already be configured with one or more SSs and CORESETs for physical downlink control channel (PDCCH) monitoring. In some aspects, the additional CORESET and SS can be used by the UE (or other receiver) to identify the encoded messages for sensing purposes, and the UE can inhibit them from being used for other purposes.

In a particular example, for data decoding information conveyed via DCI, the DCI can be conveyed via PDCCH and/or PDSCH, and/or can be one part or both parts of a 2-stage DCI.

In another particular example, for data decoding information conveyed via SCI, the SCI can be conveyed via PSCCH and/or PSSCH, and/or can be one part or both parts of a 2-stage SCI.

In some aspects, an indication associated with the data decoding information can indicate if the data decoding information is associated with a DL transmission, an UL transmission, and/or a SL transmission.

In some aspects, the encoded data (e.g., one or more packets) associated with the data decoding information can be data sent over one or more of the following channels: a PDSCH, a PUSCH, a PUCCH, a PDCCH, a PSSCH, a PSCCH; and/or any other suitable signal.

FIG. 18 is a flow chart illustrating an example process for an entity sharing data decoding information associated with its own transmissions in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1800 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1800 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1802, an entity (e.g., a UE, a Base Station, a RSU, etc. ) can receive a request from a UE (or other receiver) for data decoding information. In some aspects, the entity can receive the request for data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the request for data decoding information can be associated with an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process.

At 1804, the entity can determine that sharing of the data decoding information is permitted. For example, in some aspects, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing. In a more particular example, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing based on an explicit indication (e.g., in memory) that the data decoding information can be shared for the purpose of multi-node passive sensing. In some aspects, process 1800 can end if the request at 1802 was not associated with an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process and/or if the data decoding information cannot be shared with receivers for multi-node passive sensing. Additionally or alternatively, in some aspects, the entity can determine not to share the data decoding information for any other suitable reason.

At 1806, the entity can transmit data decoding information associated with the entity's encoded signal transmissions to the UE (or other receiver) that requested data decoding information at 1802. In some aspects, the entity can transmit the data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the data decoding information can be associated with one or more dependencies that restrict the use of the data decoding information as described above in connection with 1708. In some aspects, the data decoding information can be transmitted using any suitable technique or combination of techniques, such as techniques described above in connection with FIG. 17. In some aspects, an indication associated with the data decoding information can indicate if the data decoding information is associated with a DL transmission, an UL transmission, and/or a SL transmission.

In some aspects, the encoded transmission (e.g., including one or more packets) associated with the data decoding information can be one or more of the following types of transmission: a PDSCH transmission, a PUSCH transmission, a PUCCH transmission, a PDCCH transmission, a PSSCH transmission, a PSCCH transmission, and/or any other suitable type of transmission.

FIG. 19 is a flow chart illustrating an example process for using data decoding information to facilitate multi-node passive sensing in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1900 can be carried out (e.g., executed) by a scheduled entity or a scheduling entity described above in connection with FIGS. 10 and 11, and/or by base station 108 or UE 106 described above in connection with FIG. 1. In some examples, process 1900 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At 1902, a receiver (e.g., a UE, a base station, a RSU, etc. ) can request data decoding information associated with one or more nearby transmitters (e.g., one or more UEs, base stations, RSUs, etc. ) . In some aspects, the receiver can request data decoding information using one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the receiver can request the data decoding information from any suitable transmitter or transmitters. For example, the receiver can request the data decoding information from a base station during UL. As another example, the receiver can request the data decoding information from a UE during DL (e.g., if the receiver is a base station) . As yet another example, the receiver can request the data decoding information from another entity via a sidelink connection. In some aspects, 1902 can be omitted. For example, a transmitter can provide data decoding information that is not sent in response to an explicit request from the receiver (e.g., a request can come from another entity, such as a base station, or from the core network) .

At 1904, the receiver can receive data decoding information associated with one or more transmitters. In some aspects, the receiver can receive data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) . In some aspects, the data decoding information can include information about multiple types of transmission sent by a particular transmitter. In some aspects, the data decoding information can be associated with one or more dependencies that restrict the use of the data decoding information as described above in connection with 1708. In some aspects, the data decoding information can be received using any suitable technique or combination of techniques, such as techniques described above in connection with FIG. 17.In some aspects, an indication associated with the data decoding information can indicate if the data decoding is associated with a DL transmission, an UL transmission, and/or a SL transmission.

In some aspects, the encoded transmission associated with the data decoding information can be one or more of the following types of transmission: a PDSCH transmission, a PUSCH transmission, a PUCCH transmission, a PDCCH transmission, a PSSCH transmission, a PSCCH transmission, and/or any other suitable type of transmission.

At 1906, the receiver can monitor resources specified by data decoding information associated with one or more nearby transmitters. For example, the receiver can monitor FD-TD resources associated with the data decoding information using one or more transceivers. In a more particular example, the receiver can attempt to detect encoded signals corresponding to FD-TD resources associated with the data decoding information by sampling and buffering a received wireless signal, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.

At 1908, the receiver can receive encoded transmissions (e.g., including one or more packets) originating from one or more nearby transmitters. As described above in connection with FIGS. 3 to 5, the same signal transmitted by a particular transmitter can be received multiple times, including a line of sight signal and one or more multipath reflected signals. For example, if the receiver has access to the RS configuration information and data decoding information, the receiver can estimate the channel over which the encoded signal is sent, and can decode the physical layer of the encoded signal associated with the data decoding information. Without data decoding information, the receiver cannot decode an encoded signal, even if it has received an RS associated with the channel and estimated the channel response.

At 1910, the receiver can estimate a frequency domain (FD) channel response of the received signals using the received data decoding information. In some aspects, the receiver can estimate the FD channel response using any suitable technique or combination of techniques. For example, the receiver can estimate the frequency domain channel response using techniques described above in connection with FIGS. 3 and 5. In some aspects, the receiver can estimate the FD channel response for encoded signals received from multiple transmitters.

At 1912, the receiver can determine ellipses associated with an object based on the estimated frequency domain channel response of various signals. In some aspects, the receiver can determine ellipses using any suitable technique or combination of techniques. For example, the receiver can determine ellipses associated with encoded signals received from various transmitters using techniques described above in connection with FIGS. 3 and 5.

At 1914, the receiver can act as a transmitter, and can transmit an encoded signal using data encoding information corresponding to data decoding information that has been shared with at least one other transmitter for use in multi-node passive sensing. For example, the receiver can act as a portion of a multi-node passive sensing system that can be used by other receivers to locate objects in the environment. In some aspects, the receiver can transmit the data decoding information in one or more messages and/or information elements transmitted using any suitable communication network (e.g., via a, such as RAN 104 or RAN 200, using one or more UL slots and/or one or more DL slots; or via one or more peer to peer connections utilizing any suitable technique or combination of techniques, such as sidelink communications, Bluetooth communications, vehicle to everything communications, etc. ) .

In one configuration, the apparatus 1000 and/or 1100 for wireless communication includes means for collecting and sharing data decoding information, means for monitoring resources for encoded signals, and/or means for receiving data decoding information. In some aspects, the aforementioned means can be the processor (s) 1004 and/or 1104 described above in connection with FIGS. 10 and 11 configured to perform the functions recited by the aforementioned means. Additionally or alternatively, in some aspects, the aforementioned means can be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.

Of course, in the above examples, the circuitry included in the processor 1004 and/or 1104 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1006 and/or 1106, or any other suitable apparatus or means described in any one of the FIGS. 1 and/or 2, and utilizing, for example, the processes and/or algorithms described below in connection with one or more of FIGS. 12 to 14 and 17 to 19.

Further Examples Having a Variety of Features:

Example 1: A method, apparatus, and non-transitory computer-readable medium for wireless communication, including: receiving, by a user equipment (UE) , data decoding information associated with a transmitter; monitoring resources based on the data decoding information; receiving an encoded signal transmitted by the transmitter, the encoded signal comprising one or more encoded packets; receiving a multipath reflection of the encoded signal transmitted by the transmitter; and determining a first ellipse corresponding to possible locations of an object based on a time delay between reception of encoded signal and reception of the multipath reflection of the encoded signal.

Example 2: A method, apparatus, and non-transitory computer-readable medium of Example 1, further including: receiving, by the UE, data decoding information associated with a second transmitter; monitoring resources based on the data decoding information associated with the second transmitter; receiving an encoded signal from the second transmitter; receiving a multipath reflection of the encoded signal from the second transmitter; determining a second ellipse corresponding to possible locations of the object based on time delays between reception of the encoded signal received from the second transmitter and reception of the multipath reflection of the of encoded signal received from the second transmitter; and estimating a location of the object based on the first ellipse and the second ellipse.

Example 3: A method, apparatus, and non-transitory computer-readable medium of Example 2, further including: receiving the data decoding information associated with the second transmitter from a scheduling entity.

Example 4: A method, apparatus, and non-transitory computer-readable medium of any of Examples 2 to 3, wherein the second transmitter comprises a road side unit.

Example 5: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 4, further including: receiving, by the UE, information about one or more ellipses determined by one or more transmitters; and estimating a location of the object based on the first ellipse and the one or more ellipses determined by the one or more transmitters.

Example 6: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 5, further including: receiving, by the UE, reference signal (RS) configuration information associated with the transmitter; monitoring resources based on the RS configuration information; receiving a RS transmitted by the transmitter; receiving a multipath reflection of the RS transmitted by the transmitter; and determining a second ellipse corresponding to possible locations of an object based on a time delay between reception of the RS and reception of the multipath reflection of the RS.

Example 7: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 6, wherein receiving, by the UE, the data decoding information associated with the transmitter comprises: receiving an indication that the UE omit HARQ-ACK feedback in connection with reception of an encoded signal associated with the data decoding information.

Example 8: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 7, wherein receiving, by the UE, the data decoding information associated with the transmitter comprises: receiving one or more of the following: radio resource control (RRC) configuration information; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message transmitted using a dedicated physical (PHY) layer channel; or a CORESET ID and a corresponding search space.

Example 9: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 8, wherein receiving, by the first UE, the data decoding information associated with the transmitter comprises: receiving an indication that the data decoding information is associated with an encoded signal transmitted by the transmitter utilizing one of the following: an uplink (UL) slot or a sidelink (SL) slot.

Example 10: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 9, wherein receiving, by the UE, the data decoding information associated with the transmitter comprises: receiving an indication that the data decoding information is associated with an encoded signal transmitted to the transmitter utilizing a downlink (DL) slot.

Example 11: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 10, wherein the encoded signal associated with the data decoding information is one of the following: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.

Example 12: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 11, wherein the data decoding information comprises: a pattern corresponding to a combination of frequency domain resources and time domain resources.

Example 13: A method, apparatus, and non-transitory computer-readable medium of Example 12, wherein the pattern corresponds to at least one physical resource block in the frequency domain, and at least one symbol in the time domain.

Example 14: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 13, wherein the data decoding information comprises one or more of the following: a radio network temporary identifier (RNTI) ; a scrambling ID; a frequency domain resource assignment (FDRA) ; a time domain resource assignment (TDRA) ; a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type used by the transmitter; a DMRS port ID; a code division multiplexing (CDM) -group ID associated with the transmitter; an energy per resource element (EPRE) -ratio with data symbols; or quasi co-location (QCL) information.

Example 15: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 14, wherein the data decoding information comprises one or more of the following: multiple DMRS port IDs; or multiple DMRS scrambling IDs.

Example 16: A method, apparatus, and non-transitory computer-readable medium, including: receiving, by a scheduling entity, data decoding information associated with one or more transmitters; receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information associated with one or more nearby transmitters; in response to the request from the UE for data decoding information associated with one or more nearby transmitters, transmitting the data decoding information associated with the one or more transmitters to the UE.

Example 17: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 15, further including: receiving, by a scheduling entity, data decoding information associated with one or more transmitters; receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information associated with one or more nearby transmitters; in response to the request from the UE for data decoding information associated with one or more nearby transmitters, transmitting the data decoding information associated with the one or more transmitters to the UE.

Example 18: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 17, further including: monitoring resources based on the data decoding information associated with the one or more transmitters; receiving an encoded signal transmitted by each of the one or more transmitters, the encoded signal comprising one or more encoded packets; receiving a multipath reflection of the encoded signal transmitted by each of the one or more transmitters; determining one or more ellipses corresponding to possible locations of an object based on a time delay between reception of the encoded signal transmitted by each of the one or more transmitters and reception of the multipath reflection of the encoded signal transmitted by each of the one or more transmitters; and estimating a location of an object based on the first ellipse and each of the one or more ellipses.

Example 19: A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 18, further including: receiving, by the scheduling entity, information about one or more ellipses determined by one or more receivers, including the UE; and estimating a location of an object based on the one or more ellipses.

Example 20: A method, apparatus, and non-transitory computer-readable medium, including: receiving, by a user equipment (UE) , a message comprising data decoding information relating to data that is not scheduled for purposes of communication with the UE to receive; and monitoring for encoded signals based on the data decoding information.

Example 21: A method, apparatus, and non-transitory computer-readable medium of Examples 20, further including: receiving an encoded signal based on the data decoding information; and determining information relating to a spatial location of an object proximate the UE by passive radar sensing based on the received encoded signal.

Example 22: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 or 21, wherein the data decoding information comprises an indication that the UE is permitted to omit HARQ-ACK feedback in connection with reception of one or both of the message comprising the data decoding information, or an encoded signal associated with the data decoding information.

Example 23: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 22, wherein the message comprising the data decoding information comprises one or more of the following: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message transmitted using a dedicated physical (PHY) layer channel; or a CORESET ID and a corresponding search space.

Example 24: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 23, wherein the data decoding information comprises an indication that corresponding data for decoding is transmitted utilizing one of the following: a downlink (DL) slot, an uplink (UL) slot or a sidelink (SL) slot.

Example 25: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 24, further including receiving an encoded signal based on the data decoding information, wherein the encoded signal is one of the following: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.

Example 26: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 25, wherein the data decoding information comprises information relating to a set of resources for the UE to monitor for the encoded signals.

Example 27: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 26, wherein the information relating to the set of resources for the UE to monitor for the encoded signals comprises at least one of: a frequency domain property of the set of resources; or a time domain property of the set of resources.

Example 28: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 27, wherein the frequency domain property of the set of resources comprises an indication of one or more of the following: one or more physical resource blocks (PRB) ; one or more bandwidth parts (BWP) ; one or more component carriers (CC) ; or at least one radio access technology (RAT) .

Example 29: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 28, wherein the time domain property of the set of resources comprises an indication of one or more of the following: one or more symbols; one or more slot; one or more subframes; or one or more frames.

Example 30: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 29, wherein the information relating to the set of resources for the UE to monitor for encoded signals comprises: the frequency domain property of the set of resources; and the time domain property of the set of resources.

Example 31: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 30, wherein the information relating to the set of resources for the UE to monitor for encoded signals on the one or more channels: a frequency domain property of each set of a plurality of sets of resources including the set of resources; and a time domain property of each set of a plurality of sets of resources including the set of resources.

Example 32: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 31, wherein at least one set of the plurality of sets of resources overlaps in frequency and/or time with at least one other set of the plurality of sets of resources.

Example 33: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 32, wherein the data decoding information comprises one or more resource parameters corresponding to resources for the UE to monitor for encoded signals.

Example 34: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 33, wherein the one or more resource parameters corresponding to the resources for the UE to monitor for encoded signals comprises one or more of the following: a radio network temporary identifier (RNTI) ; a scrambling ID; a frequency domain resource assignment (FDRA) ; a time domain resource assignment (TDRA) ; a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type corresponding to one or more encoded signals; a DMRS port ID; a code division multiplexing (CDM) -group ID associated with the one or more channels; an energy per resource element (EPRE) -ratio with data symbols; quasi co-location (QCL) information; a parameter specifying one or more DCI formats to monitor for the encoded signals; a parameters specifying a DCI format carried on PSSCH; or a parameter specifying SCI carried on PSSCH.

Example 35: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 34, wherein the information relating to the one or more channels comprises information relating to one or more port IDs or one or more scrambling IDs for the UE to monitor for encoded signals on the one or more channels.

Example 36: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 35, wherein the information relating to the one or more channels comprises information identifying a plurality of sets of resources, wherein a first set of the plurality of sets of resources at least partially overlaps in frequency and/or time with a second set of the plurality of sets of resources, and wherein the first set is associated with a different port ID or a different scrambling ID than that of the second set.

Example 37: A method, apparatus, and non-transitory computer-readable medium, including receiving, by a scheduling entity, data decoding information comprising information relating to data decoding of one or more channels; receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information relating data decoding of one or more channels that are not for any one or more of: reference in relation to transmission or reception of information by the UE, channel characterization by the UE, or synchronization by the UE; in response to the request from the UE, transmitting a message comprising the data decoding information to the UE.

Example 38: A method, apparatus, and non-transitory computer-readable medium, of any of Examples 20 to 36, further including: receiving, by a scheduling entity, data decoding information comprising information relating to data decoding of one or more channels; receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information relating data decoding of one or more channels that are not for any one or more of: reference in relation to transmission or reception of information by the UE, channel characterization by the UE, or synchronization by the UE; in response to the request from the UE, transmitting a message comprising the data decoding information to the UE.

Example 39: A method, apparatus, and non-transitory computer-readable medium of any of Examples 20 to 38, monitoring, by the scheduling entity, for encoded signals on the one or more channels based on the data decoding information.

Several aspects of a wireless communication network have been presented with reference to an exemplary implementation. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) . Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) . Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

Within the present disclosure, the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object. The terms “circuit” and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.

One or more of the components, steps, features and/or functions illustrated in FIGS. 1–14 may be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein. The apparatus, devices, and/or components illustrated in FIGS. 1–14 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.

It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

A method of wireless communication, comprising:

receiving, by a user equipment (UE) , a message comprising data decoding information relating to data that is not scheduled for purposes of communication with the UE; and

monitoring for encoded signals based on the data decoding information.
The method of claim 1, further comprising:

receiving an encoded signal based on the data decoding information; and

determining information relating to a spatial location of an object proximate the UE by passive radar sensing based on the received encoded signal.
The method of claim 1, wherein the data decoding information comprises an indication that the UE is permitted to omit HARQ-ACK feedback in connection with reception of one or both of the message comprising the data decoding information, or an encoded signal associated with the data decoding information.
The method of claim 1, wherein the message comprising the data decoding information comprises one or more of the following: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CEs) ;downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message transmitted using a dedicated physical (PHY) layer channel; or a CORESET ID and a corresponding search space.
The method of claim 1, wherein the data decoding information comprises an indication that corresponding data is transmitted utilizing one of the following: a downlink (DL) slot, an uplink (UL) slot or a sidelink (SL) slot.
The method of claim 1, further comprising receiving an encoded signal based on the data decoding information,

wherein the encoded signal is one of the following: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.
The method of claim 1, wherein the data decoding information comprises information relating to a set of resources for the UE to monitor for the encoded signals.
The method of claim 7, wherein the information relating to the set of resources for the UE to monitor for the encoded signals comprises at least one of:

a frequency domain property of the set of resources; or

a time domain property of the set of resources.
The method of claim 8, wherein the frequency domain property of the set of resources comprises an indication of one or more of the following: one or more physical resource blocks (PRB) ; one or more bandwidth parts (BWP) ; one or more component carriers (CC) ; or at least one radio access technology (RAT) .
The method of claim 8, wherein the time domain property of the set of resources comprises an indication of one or more of the following: one or more symbols; one or more slot; one or more subframes; or one or more frames.
The method of claim 8, wherein the information relating to the set of resources for the UE to monitor for encoded signals comprises:

the frequency domain property of the set of resources; and

the time domain property of the set of resources.
The method of claim 8, wherein the information relating to the set of resources for the UE to monitor for encoded signals on the one or more channels:

a frequency domain property of each set of a plurality of sets of resources including the set of resources; and

a time domain property of each set of a plurality of sets of resources including the set of resources.
The method of claim 12, wherein at least one set of the plurality of sets of resources overlaps in frequency and/or time with at least one other set of the plurality of sets of resources.
The method of claim 1, wherein the data decoding information comprises one or more resource parameters corresponding to resources for the UE to monitor for encoded signals.
The method of claim 14, wherein the one or more resource parameters corresponding to the resources for the UE to monitor for encoded signals comprises one or more of the following: a radio network temporary identifier (RNTI) ; a scrambling ID; a frequency domain resource assignment (FDRA) ; a time domain resource assignment (TDRA) ; a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type corresponding to one or more encoded signals; a DMRS port ID; a code division multiplexing (CDM) -group ID associated with the one or more channels; an energy per resource element (EPRE) -ratio with data symbols; quasi co-location (QCL) information; a parameter specifying one or more DCI formats to monitor for the encoded signals; a parameters specifying a DCI format carried on PSSCH; or a parameter specifying SCI carried on PSSCH.
The method of claim 1, wherein the information relating to the one or more channels comprises information relating to one or more port IDs or one or more scrambling IDs for the UE to monitor for encoded signals on the one or more channels.
The method of claim 16,

wherein the information relating to the one or more channels comprises information identifying a plurality of sets of resources,

wherein a first set of the plurality of sets of resources at least partially overlaps in frequency and/or time with a second set of the plurality of sets of resources, and

wherein the first set is associated with a different port ID or a different scrambling ID than that of the second set.
A method of wireless communication, comprising:

receiving, by a scheduling entity, data decoding information comprising information relating to data decoding of one or more channels;

receiving, by the scheduling entity, a request from a user equipment (UE) for data decoding information relating to data that is not scheduled for the purpose of communication with the UE; and

in response to the request from the UE, transmitting a message comprising the data decoding information to the UE.
The method of claim 18, further comprising:

monitoring, by the scheduling entity, for encoded signals on the one or more channels based on the data decoding information.
A wireless communication device, comprising:

a transceiver;

memory; and

a processor communicatively coupled to the transceiver and the memory, the processor configured to:

receive, via the transceiver, a message comprising data decoding information relating to data that is not scheduled for purposes of communication with the UE; and

monitor, using the transceiver, for encoded signals based on the data decoding information.
The wireless communication device of claim 20, wherein the processor is further configured to:

receive an encoded signal based on the data decoding information; and

determine information relating to a spatial location of an object proximate the UE by passive radar sensing based on the received encoded signal.
The wireless communication device of claim 20, wherein the data decoding information comprises an indication that the UE is permitted to omit HARQ-ACK feedback in connection with reception of one or both of the message comprising the data decoding information, or an encoded signal associated with the data decoding information.
The wireless communication device of claim 20, wherein the message comprising the data decoding information comprises one or more of the following: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message transmitted using a dedicated physical (PHY) layer channel; or a CORESET ID and a corresponding search space.
The wireless communication device of claim 20, wherein the data decoding information comprises an indication that corresponding data for decoding is transmitted utilizing one of the following: a downlink (DL) slot, an uplink (UL) slot or a sidelink (SL) slot.
The wireless communication device of claim 20, wherein the processor is further configured to receive an encoded signal based on the data decoding information,

wherein the encoded signal is one of the following: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.
The wireless communication device of claim 20, wherein the data decoding information comprises information relating to a set of resources for the UE to monitor for the encoded signals.
The wireless communication device of claim 26, wherein the information relating to the set of resources for the UE to monitor for the encoded signals comprises at least one of:

a frequency domain property of the set of resources; or

a time domain property of the set of resources.
The wireless communication device of claim 27, wherein the frequency domain property of the set of resources comprises an indication of one or more of the following: one or more physical resource blocks (PRB) ; one or more bandwidth parts (BWP) ; one or more component carriers (CC) ; or at least one radio access technology (RAT) .
The wireless communication device of claim 27, wherein the time domain property of the set of resources comprises an indication of one or more of the following: one or more symbols; one or more slot; one or more subframes; or one or more frames.
The wireless communication device of claim 27, wherein the information relating to the set of resources for the UE to monitor for encoded signals comprises:

the frequency domain property of the set of resources; and

the time domain property of the set of resources.
The wireless communication device of claim 20, wherein the information relating to the set of resources for the UE to monitor for encoded signals on the one or more channels:

a frequency domain property of each set of a plurality of sets of resources including the set of resources; and

a time domain property of each set of a plurality of sets of resources including the set of resources.
The wireless communication device of claim 31, wherein at least one set of the plurality of sets of resources overlaps in frequency and/or time with at least one other set of the plurality of sets of resources.
The wireless communication device of claim 20, wherein the data decoding information comprises one or more resource parameters corresponding to resources for the UE to monitor for encoded signals.
The wireless communication device of claim 33, wherein the one or more resource parameters corresponding to the resources for the UE to monitor for encoded signals comprises one or more of the following: a radio network temporary identifier (RNTI) ; a scrambling ID; a frequency domain resource assignment (FDRA) ; a time domain resource assignment (TDRA) ; a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type corresponding to one or more encoded signals; a DMRS port ID; a code division multiplexing (CDM) -group ID associated with the one or more channels; an energy per resource element (EPRE) -ratio with data symbols; quasi co-location (QCL) information; a parameter specifying one or more DCI formats to monitor for the encoded signals; a parameters specifying a DCI format carried on PSSCH; or a parameter specifying SCI carried on PSSCH.
The wireless communication device of claim 20, wherein the information relating to the one or more channels comprises information relating to one or more port IDs or one or more scrambling IDs for the UE to monitor for encoded signals on the one or more channels.
The wireless communication device of claim 20,

wherein the information relating to the one or more channels comprises information identifying a plurality of sets of resources,

wherein a first set of the plurality of sets of resources at least partially overlaps in frequency and/or time with a second set of the plurality of sets of resources, and

wherein the first set is associated with a different port ID or a different scrambling ID than that of the second set.
A scheduling entity for wireless communication, comprising:

a transceiver;

memory; and

a processor communicatively coupled to the transceiver and the memory, the processor configured to:

receive, via the transceiver, data decoding information comprising information relating to data decoding of one or more channels;

receive, via the transceiver, a request from a user equipment (UE) for data decoding information relating to data that is not scheduled for the purpose of communication with the UE; and

transmit, via the transceiver, a message comprising the data decoding information to the UE in response to the request from the UE.
The scheduling entity of claim 37, wherein the processor is further configured to monitor, using the transceiver, for encoded signals on the one or more channels based on the data decoding information.
A method of wireless communication, comprising:

means for receiving, by a user equipment (UE) , a message comprising data decoding information relating to data that is not scheduled for purposes of communication with the UE; and

means for monitoring for encoded signals based on the data decoding information.
The method of claim 39, further comprising:

means for receiving an encoded signal based on the data decoding information; and

means for determining information relating to a spatial location of an object proximate the UE by passive radar sensing based on the received encoded signal.
The method of claim 39, wherein the data decoding information comprises an indication that the UE is permitted to omit HARQ-ACK feedback in connection with reception of one or both of the message comprising the data decoding information, or an encoded signal associated with the data decoding information.
The method of claim 39, wherein the message comprising the data decoding information comprises one or more of the following: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CEs) ; downlink control information (DCI) ; sidelink control information (SCI) ; a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message transmitted using a dedicated physical (PHY) layer channel; or a CORESET ID and a corresponding search space.
The method of claim 39, wherein the data decoding information comprises an indication that corresponding data is transmitted utilizing one of the following: a downlink (DL) slot, an uplink (UL) slot or a sidelink (SL) slot.
The method of claim 39, further comprising means for receiving an encoded signal based on the data decoding information,

wherein the encoded signal is one of the following: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.
The method of claim 39, wherein the data decoding information comprises information relating to a set of resources for the UE to monitor for the encoded signals.
The method of claim 45, wherein the information relating to the set of resources for the UE to monitor for the encoded signals comprises at least one of:

a frequency domain property of the set of resources; or

a time domain property of the set of resources.
The method of claim 45, wherein the frequency domain property of the set of resources comprises an indication of one or more of the following: one or more physical resource blocks (PRB) ; one or more bandwidth parts (BWP) ; one or more component carriers (CC) ; or at least one radio access technology (RAT) .
The method of claim 45, wherein the time domain property of the set of resources comprises an indication of one or more of the following: one or more symbols; one or more slot; one or more subframes; or one or more frames.
The method of claim 45, wherein the information relating to the set of resources for the UE to monitor for encoded signals comprises:

the frequency domain property of the set of resources; and

the time domain property of the set of resources.
The method of claim 45, wherein the information relating to the set of resources for the UE to monitor for encoded signals on the one or more channels:

a frequency domain property of each set of a plurality of sets of resources including the set of resources; and

a time domain property of each set of a plurality of sets of resources including the set of resources.
The method of claim 50, wherein at least one set of the plurality of sets of resources overlaps in frequency and/or time with at least one other set of the plurality of sets of resources.
The method of claim 39, wherein the data decoding information comprises one or more resource parameters corresponding to resources for the UE to monitor for encoded signals.
The method of claim 52, wherein the one or more resource parameters corresponding to the resources for the UE to monitor for encoded signals comprises one or more of the following: a radio network temporary identifier (RNTI) ; a scrambling ID; a frequency domain resource assignment (FDRA) ; a time domain resource assignment (TDRA) ; a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type corresponding to one or more encoded signals; a DMRS port ID; a code division multiplexing (CDM) -group ID associated with the one or more channels; an energy per resource element (EPRE) -ratio with data symbols; quasi co-location (QCL) information; a parameter specifying one or more DCI formats to monitor for the encoded signals; a parameters specifying a DCI format carried on PSSCH; or a parameter specifying SCI carried on PSSCH.
The method of claim 39, wherein the information relating to the one or more channels comprises information relating to one or more port IDs or one or more scrambling IDs for the UE to monitor for encoded signals on the one or more channels.
The method of claim 54,

wherein the information relating to the one or more channels comprises information identifying a plurality of sets of resources,

wherein a first set of the plurality of sets of resources at least partially overlaps in frequency and/or time with a second set of the plurality of sets of resources, and

wherein the first set is associated with a different port ID or a different scrambling ID than that of the second set.
A method of wireless communication, comprising:

means for receiving data decoding information comprising information relating to data decoding of one or more channels;

means for receiving a request from a user equipment (UE) for data decoding information relating to data that is not scheduled for the purpose of communication with the UE; and

means for transmitting a message comprising the data decoding information to the UE responsive to the request from the UE.
The method of claim 56, further comprising:

means for monitoring for encoded signals on the one or more channels based on the data decoding information.
An apparatus for wireless communication, comprising:

one or more features described in the Specification and Claims provided above.
A non-transitory computer-readable medium storing computer-executable code, comprising code for causing a computer to:

carry out one or more processes described in the Specification and Claims provided above.
An apparatus for wireless communication, comprising:

a processor;

a transceiver communicatively coupled to the at least one processor; and

a memory communicatively coupled to the at least one processor,

wherein the processor is configured to:

carry out one or more processes described in the Specification and Claims provided above.