Patent ID: 12213038

DETAILED DESCRIPTION

Wireless communications sometimes involve the use of wireless devices in a mobile context, such as a vehicular environment. Due to vehicular mobility and possibility of blockage from surrounding objects, such wireless devices may suffer reduction in communication capabilities or quality (e.g., intermittent outages or reduced data rate). For example, one vehicle may suddenly accelerate away from another vehicle with which the first vehicle is communication. In another example, another vehicle (e.g., a vehicle not equipped with vehicle to everything (V2X) communications) may move and interrupt or affect a communications channel between vehicles engaging in V2X communication. Some approaches attempt to resolve such issues through additional training for beamforming and communication channel sensing. This, however, may involve additional overhead and a possible reduction in the communication data rate. Additional approaches may include monostatic sensing in which a radio frequency (RF) sensing transmitter and receiver may be co-located (e.g., radar) or passive sensing in which an RF receiver receives a signal transmitted by a RF transmitter that is widely separated from the receiver. However, such approaches provide limited information (e.g., node-specific information or one-way channel information) and are subject to significant measurement path losses, power consumption, and increased interference.

The subject matter described herein includes the use of radio frequency (RF) multi-static sensing to aid in assisting V2X communications for increased throughput, higher reliability, and reduced latency. A roadside unit (RSU) may communicate with various network nodes within the RSU's coverage area, and the network nodes may be equipped with sensing nodes. The RSU may make or collect channel measurements associated with the coverage area (e.g., made at one or more selected remote or co-located network nodes) to assist communications at the network nodes. For example, the RSU may transmit a request for capability information (e.g., detailing RF sensing capabilities of the network node) from a network node, and the network node may response with the requesting capability information. The RSU may transmit parameters for performing multi-static sensing measurements to the network node, and the network node may respond with the multi-static sensing measurements. The RSU may then use the measurements to determine one or more channel estimates, and may transmit the channel estimates to one or more nodes that may utilize the channel estimates to adapt communication parameters with the channel estimates that the network nodes may not otherwise obtain. Such processes may be repeated with other network nodes and the information obtained from various different nodes may be analyzed and combined (e.g., by the RSU) to provide information to various network nodes in the coverage area. In this way, the RSU and the network nodes employ a multi-static sensing approach to improve data rates, latency, and reliability (e.g., due to better blockage predictions, line-of-sight or non-line-of-sight classifications, beam managements, MCS selection, resources allocations, reduced training overhead, or any combination thereof).

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of systems and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to multi-static sensing coordination.

FIG.1illustrates an example of a wireless communications system100that supports multi-static sensing coordination in accordance with examples described herein. The wireless communications system100may include one or more network entities105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities105may be dispersed throughout a geographic area to form the wireless communications system100and may include devices in different forms or having different capabilities. In various examples, a network entity105may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities105and UEs115may wirelessly communicate via one or more communication links125(e.g., a radio frequency (RF) access link). For example, a network entity105may support a coverage area110(e.g., a geographic coverage area) over which the UEs115and the network entity105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a network entity105and a UE115may support the communication of signals according to one or more radio access technologies (RATs).

The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115or network entities105, as shown inFIG.1.

As described herein, a node of the wireless communications system100, which may be referred to as a network node, or a wireless node, may be a network entity105(e.g., any network entity described herein), a UE115(e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE115. As another example, a node may be a network entity105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE115, the second node may be a network entity105, and the third node may be a UE115. In another aspect of this example, the first node may be a UE115, the second node may be a network entity105, and the third node may be a network entity105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE115, network entity105, apparatus, device, computing system, or the like may include disclosure of the UE115, network entity105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE115is configured to receive information from a network entity105also discloses that a first node is configured to receive information from a second node.

In some examples, network entities105may communicate with the core network130, or with one another, or both. For example, network entities105may communicate with the core network130via one or more backhaul communication links120(e.g., in accordance with an S1, N2, N3, or other interface protocol). In some examples, network entities105may communicate with one another over a backhaul communication link120(e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities105) or indirectly (e.g., via a core network130). In some examples, network entities105may communicate with one another via a midhaul communication link162(e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link168(e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links120, midhaul communication links162, or fronthaul communication links168may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE115may communicate with the core network130through a communication link155.

One or more of the network entities105described herein may include or may be referred to as a base station140(e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity105(e.g., a base station140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity105(e.g., a single RAN node, such as a base station140).

In some examples, a network entity105may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity105may include one or more of a central unit (CU)160, a distributed unit (DU)165, a radio unit (RU)170, a RAN Intelligent Controller (RIC)175(e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO)180system, or any combination thereof. An RU170may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities105in a disaggregated RAN architecture may be co-located, or one or more components of the network entities105may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities105of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

The split of functionality between a CU160, a DU165, and an RU175is flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU160, a DU165, or an RU175. For example, a functional split of a protocol stack may be employed between a CU160and a DU165such that the CU160may support one or more layers of the protocol stack and the DU165may support one or more different layers of the protocol stack. In some examples, the CU160may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU160may be connected to one or more DUs165or RUs170, and the one or more DUs165or RUs170may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU165and an RU170such that the DU165may support one or more layers of the protocol stack and the RU170may support one or more different layers of the protocol stack. The DU165may support one or multiple different cells (e.g., via one or more RUs170). In some cases, a functional split between a CU160and a DU165, or between a DU165and an RU170may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU160, a DU165, or an RU170, while other functions of the protocol layer are performed by a different one of the CU160, the DU165, or the RU170). A CU160may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU160may be connected to one or more DUs165via a midhaul communication link162(e.g., F1, F1-c, F1-u), and a DU165may be connected to one or more RUs170via a fronthaul communication link168(e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link162or a fronthaul communication link168may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities105that are in communication over such communication links.

In wireless communications systems (e.g., wireless communications system100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network130). In some cases, in an IAB network, one or more network entities105(e.g., IAB nodes104) may be partially controlled by each other. One or more IAB nodes104may be referred to as a donor entity or an IAB donor. One or more DUs165or one or more RUs170may be partially controlled by one or more CUs160associated with a donor network entity105(e.g., a donor base station140). The one or more donor network entities105(e.g., IAB donors) may be in communication with one or more additional network entities105(e.g., IAB nodes104) via supported access and backhaul links (e.g., backhaul communication links120). IAB nodes104may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs165of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs115, or may share the same antennas (e.g., of an RU170) of an IAB node104used for access via the DU165of the IAB node104(e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes104may include DUs165that support communication links with additional entities (e.g., IAB nodes104, UEs115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes104or components of IAB nodes104) may be configured to operate according to the techniques described herein.

For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB nodes104, and one or more UEs115. The IAB donor may facilitate connection between the core network130and the AN (e.g., via a wired or wireless connection to the core network130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network130. The IAB donor may include a CU160and at least one DU165(e.g., and RU170), in which case the CU160may communicate with the core network130over an interface (e.g., a backhaul link). IAB donor and IAB nodes104may communicate over an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally, or alternatively, the CU160may communicate with the core network over an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs160(e.g., a CU160associated with an alternative IAB donor) over an Xn-C interface, which may be an example of a portion of a backhaul link.

An IAB node104may refer to a RAN node that provides IAB functionality (e.g., access for UEs115, wireless self-backhauling capabilities). A DU165may act as a distributed scheduling node towards child nodes associated with the IAB node104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes104). Additionally, or alternatively, an IAB node104may also be referred to as a parent node or a child node to other IAB nodes104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes104may provide a Uu interface for a child IAB node104to receive signaling from a parent IAB node104, and the DU interface (e.g., DUs165) may provide a Uu interface for a parent IAB node104to signal to a child IAB node104or UE115.

For example, IAB node104may be referred to as a parent node that supports communications for a child IAB node, and referred to as a child IAB node associated with an IAB donor. The IAB donor may include a CU160with a wired or wireless connection (e.g., a backhaul communication link120) to the core network130and may act as parent node to IAB nodes104. For example, the DU165of IAB donor may relay transmissions to UEs115through IAB nodes104, and may directly signal transmissions to a UE115. The CU160of IAB donor may signal communication link establishment via an F1 interface to IAB nodes104, and the IAB nodes104may schedule transmissions (e.g., transmissions to the UEs115relayed from the IAB donor) through the DUs165. That is, data may be relayed to and from IAB nodes104via signaling over an NR Uu interface to MT of the IAB node104. Communications with IAB node104may be scheduled by a DU165of IAB donor and communications with IAB node104may be scheduled by DU165of IAB node104.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support multi-static sensing coordination as described herein. For example, some operations described as being performed by a UE115or a network entity105(e.g., a base station140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes104, DUs165, CUs160, RUs170, RIC175, SMO180).

A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the network entities105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1.

The UEs115and the network entities105may wirelessly communicate with one another via one or more communication links125(e.g., an access link) over one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity105and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity105, may refer to any portion of a network entity105(e.g., a base station140, a CU160, a DU165, a RU170) of a RAN communicating with another device (e.g., directly or via one or more other network entities105).

In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be positioned according to a channel raster for discovery by the UEs115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs115via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).

The communication links125shown in the wireless communications system100may include downlink transmissions (e.g., forward link transmissions) from a network entity105to a UE115, uplink transmissions (e.g., return link transmissions) from a UE115to a network entity105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., the network entities105, the UEs115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system100may include network entities105or UEs115that support concurrent communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) such that the more resource elements that a device receives and the higher the order of the modulation scheme, the higher the data rate may be for the device. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE115.

One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE115may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE115may be restricted to one or more active BWPs.

The time intervals for the network entities105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115.

A network entity105may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity105(e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell may also refer to a coverage area110or a portion of a coverage area110(e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs115with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity105(e.g., a lower-powered base station140), as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs115with service subscriptions with the network provider or may provide restricted access to the UEs115having an association with the small cell (e.g., the UEs115in a closed subscriber group (CSG), the UEs115associated with users in a home or office). A network entity105may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

In some examples, a network entity105(e.g., a base station140, an RU170) may be movable and therefore provide communication coverage for a moving coverage area110. In some examples, different coverage areas110associated with different technologies may overlap, but the different coverage areas110may be supported by the same network entity105. In some other examples, the overlapping coverage areas110associated with different technologies may be supported by different network entities105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the network entities105provide coverage for various coverage areas110using the same or different radio access technologies.

The wireless communications system100may support synchronous or asynchronous operation. For synchronous operation, network entities105(e.g., base stations140) may have similar frame timings, and transmissions from different network entities105may be approximately aligned in time. For asynchronous operation, network entities105may have different frame timings, and transmissions from different network entities105may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

Some UEs115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity105(e.g., a base station140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs115may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

Some UEs115may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs115include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs115may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC). The UEs115may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE115may be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs115of a group that are performing D2D communications may be within the coverage area110of a network entity105(e.g., a base station140, an RU170), which may support aspects of such D2D communications being configured by or scheduled by the network entity105. In some examples, one or more UEs115in such a group may be outside the coverage area110of a network entity105or may be otherwise unable to or not configured to receive transmissions from a network entity105. In some examples, groups of the UEs115communicating via D2D communications may support a one-to-many (1:M) system in which each UE115transmits to each of the other UEs115in the group. In some examples, a network entity105may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs115without the involvement of a network entity105.

In some systems, a D2D communication link135may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities105, base stations140, RUs170) using vehicle-to-network (V2N) communications, or with both.

The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the network entities105(e.g., base stations140) associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The wireless communications system100may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system100may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system100may support millimeter wave (mmW) communications between the UEs115and the network entities105(e.g., base stations140, RUs170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

The wireless communications system100may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating in unlicensed RF spectrum bands, devices such as the network entities105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity105(e.g., a base station140, an RU170) or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity105may be located in diverse geographic locations. A network entity105may have an antenna array with a set of rows and columns of antenna ports that the network entity105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

The network entities105or the UEs115may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

A network entity105or a UE115may use beam sweeping techniques as part of beam forming operations. For example, a network entity105(e.g., a base station140, an RU170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity105multiple times along different directions. For example, the network entity105may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity105, or by a receiving device, such as a UE115) a beam direction for later transmission or reception by the network entity105.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity105, a transmitting UE115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity105or a receiving UE115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE115may receive one or more of the signals transmitted by the network entity105along different directions and may report to the network entity105an indication of the signal that the UE115received with a highest signal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a network entity105or a UE115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity105to a UE115). The UE115may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity105may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE115may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity105(e.g., a base station140, an RU170), a UE115may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

The wireless communications system100may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate over logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and a network entity105or a core network130supporting radio bearers for user plane data. At the PHY layer, transport channels may be mapped to physical channels.

The UEs115and the network entities105may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link (e.g., a communication link125, a D2D communication link135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

A roadside unit (RSU) may transmit, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. In some examples, such a communication node may be an example of a UE115as described herein. In some examples, the RSU may be an example of a network entity105as described herein. The RSU may receive a report indicating the multi-static sensing capability information for the first communication node. Such capability information may describe one or more capability of the communication node to engage in sensing (e.g., monostatic sensing, bistatic sensing, multi-static sensing, or any combination thereof). The RSU may transmit, in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. Such parameters may indicate operations, configurations, information, or any combination thereof that the communication node is to use for obtaining sensing measurements. The RSU may receive one or more multi-static sensing measurements obtained based at least in part on the one or more multi-static sensing parameters. Such measurements may include information such as raw measurements, channel estimates, or any combination thereof. The RSU may transmit, to the first communication node, a second communication node, or both, one or more channel estimates determined based at least in part on the one or more multi-static sensing measurements. In this way the RSU may coordinate multi-static sensing operations with one or more communication nodes to provide additional information (e.g., channel estimates) to the communication nodes that may otherwise be unavailable to the communication nodes.

FIG.2illustrates an example of a system200that supports multi-static sensing coordination in accordance with examples described herein.

The system200may include an RSU, such as RSU215. The system200may include one or more communication nodes220, such as communication node220-a, communication node220-b, and communication node220-c. The communication nodes220-cmay transmit one or more sensing signals210(e.g., for multi-static sensing as described herein). The RSU215may communicate with one or more communication nodes220via one or more communication links205, which may include one or more uplink communication links, one or more downlink communication links, or any combination thereof.

In the course of wireless communications, wireless communication devices may encounter various elements that may influence such communications. A wireless propagation channel between a communications transmitter and a communications receiver may be influenced by one or more effects, including reflection, refraction, diffraction, scattering, or any combination thereof. Reflection or refraction may occur when a smooth object is encountered. An amount of reflected/refracted electromagnetic waves may be a function of the incident polarization, the angle of incidence, or both, as well as the type of the material. The angles and indices of reflection and refraction may be given by Snell's law. Diffraction may include the bending of waves around a corner of an obstacle or through an aperture into the region of geometrical shadow of the obstacle/aperture. Examples of diffraction may include waves bending over the tops of buildings, around street corners, through doorways, or any combination thereof. Scattering may occur when a rough object is encountered. The type and amount of scattering that occurs may depend on an amount of roughness, angle of incidence, wavelength, incident polarization, geometric shape, dielectric properties, or any combination thereof. Additionally or alternatively, some objects may block the propagation path between the communications transmitter and communications receiver. Such physical blockages may present a challenge to reliable communication, especially at higher carrier frequencies (e.g., in a mm wave band). Such wireless propagation channel information may be relevant to adapting communication transmit parameters and to perform received processing with superior channel state information at receive (CSIR). Such adjustments may in turn lead to improvements in throughput, reliability, and latency.

As discussed herein, wireless communications devices may be subject to such effects in a variety of circumstances. One such circumstance discussed in examples herein involves vehicular communications. For example, communication node220-aand communication node220-bmay have established a communications link (e.g., a high-data rate link, such as in mmWave communications) between them. Since, in this example, communication node220-aand communication node220-bare vehicles, they may have a degree of mobility, and surrounding objects (e.g., communication node220-c) may cause blockage, reflection, or other effects on the communication channel between communication node220-aand communication node220-b. For example, a surrounding vehicle (e.g., communication node220-c) may not have support for communications that communication node220-aand communication node220-bmay have. If communication node220-cmoves suddenly (e.g., makes a lane-change maneuver), which could possibly disrupt a line-of-sight link between communication node220-aand communication node220-b. Additionally or alternatively, communication node220-bmay suddenly accelerate, which may affect the quality of the communication link. As a result of such changes, communication node220-a, communication node220-b, or both, may make changes in one or more communications parameters as a result. In some cases, such changes may cause a significant reduction in communications capability (e.g., intermittent outage, reduced data rate, other effects, or any combination thereof). Some approaches may involve additional operations (e.g., beamforming and communication channel sensing), which may increase overhead and decrease a communication data rate.

To reduce or eliminate the deficiencies or limitations discussed herein, approaches for multi-static sensing may be employed, including the example depicted inFIG.2. In the system200, the RSU215may communicate with one or more communication nodes220(e.g., that are within the coverage area of the RSU215). Such communication nodes220may be equipped with communication devices, and may further be equipped with one or more sensing nodes. Such sensing nodes may include a sensing transmitter, a sensing receiver, or both. The system200may therefore include several co-located nodes, remote sensing nodes, or both, and such nodes may share a common coverage area with a coverage area associated with or covered by the communication nodes220s. The RSU215may make its own sensing measurements, collect sensing measurements provided by other nodes (e.g., communication nodes220), or both. For example, the RSU215, the communication nodes220, or both may transmit sensing signals210to determine or obtain one or more sensing measurements. The RSU215may use such information to assist nodes within the coverage area, such as the communication nodes220. For example, the RSU215may provide information related to resource allocation, space-time-frequency transmit precoding, beam management, selection between multiple sidelink interfaces, selection between a sidelink interface and a Uu interface, or any combination thereof. Additionally or alternatively, the communication nodes220may receive the multi-static sensing estimate(s) prepared by the RSU and may combine such information with sensing performed at the communication nodes220to adapt communication parameters (e.g., transmission parameters, reception parameters, processing parameters, or any combination thereof), thereby providing improved channel state information (e.g., channel state information at receive (CSIR)).

For example, the RSU215may transmit a request for multi-static sensing capability information to the communication nodes220. Since different communication nodes220may have different capabilities, the RSU215requests this information to take such capabilities into account for other operations (e.g., determining or transmitting multi-static sensing parameters to the communication nodes220). The communication nodes220may receive such a request and may further transmit one or more indications of their capabilities to the RSU215. For example, such capabilities may include transmission, reception, or both, of sensing signals. The RSU215may receive such capability indications, and may transmit (e.g., in a control message) an indication of one or more multi-static sensing parameters (e.g., for one or more of the communication nodes220). Such parameters may include parameters associated with the sensing operations (e.g., a signal strength, a signal direction, a signal type, or other parameters). The communication nodes220may receive such indications or control messages, and may obtain one or more measurements (e.g., based on the received parameters). For example, the communication nodes220may perform one or more sensing operations (e.g., transmitting a sensing signal, receiving a sensing signal, or both). The communication nodes may transmit one or more of these obtained measurements or other measurements to the RSU215for further processing. The RSU215may determine or obtain one or more channel estimates for one or more channels associated with the RSU215or an associated coverage area. For example, the RSU215may use the obtained measurements to determine channel estimates for a communication channel between two communications nodes220. In this way, the system200may engage in sensing operations for assisting communications (e.g., in vehicular or other environments).

FIG.3illustrates an example of a system300that supports multi-static sensing coordination in accordance with examples described herein. The system300may include the RSU215and one or more communication nodes220. As discussed herein, wireless devices (e.g., those included in the system300) may operate in various environments, and such environments may include objects that may affect communication or sensing channels. For example, the environment may include reflectors340, blockages345, or both.

Approaches to sensing (e.g., RF sensing) may involve different approaches. Some approaches may involve monostatic sensing, in which the transmitter325and the receiver330may be co-located (e.g., radar). For example, the communication node220at point A may transmit a sensing signal210using a transmitter325, and may determine that there is a blockage using its receiver330. Some approaches may involve bistatic sensing, in which a transmitter325and a receiver330may be widely separated (e.g., passive sensing). For example, the communication node220at point A may transmit a sensing signal210which may be received by the communication node210at point B (e.g., after being reflected by a reflector340). Some approaches may involve multi-static sensing or multi-static sensing networks, in which multiple transmitters325and receivers330may be co-located, widely separated, or both, within a shared area of coverage. Such an approach may involve spatially diverse monostatic and bistatic sensing components. The system300may be an example of a multi-static sensing approach. In some examples of such approaches, one or more communication nodes220may employ the use of low data rate nodes335. The communication nodes220may use such low data rate nodes for communications (e.g., with another communication node220or the RSU215).

Additionally or alternatively, in such multi-static sensing approaches, one point may be a coordinating point, such as the RSU215. The RSU215may collect measurements made throughout the system300and may determine one or more channel estimates for the various communications channels involved in the system300. The RSU215may transmit the channel estimates to the various communications nodes220. In this way, the communications nodes220may receive the benefit of measurements made by other communications nodes220and obtain information (e.g., channel estimates) that may not have been otherwise available.

Some approaches have employed sensing (e.g., monostatic sensing, in which a sensing node, such as radar, and a communications node are co-located) in attempts to resolve such situations. In such sensing approaches, a single node may obtain sensing results and may therefore obtain some understanding or information about a communications channel. Such information may be used to decrease overhead (e.g., training overhead) for communications beamforming.

However, such approaches may also bear limitations. For example, radar sensing provides monostatic sensing, while communications may employ bistatic channel state information. Additionally or alternatively, a co-located sensing unit may obtain line-of-sight target parameters thereby limiting usefulness in non line-of-sight applications. Additionally or alternatively, mono-static sensing (e.g., radar) includes a two-way path loss (e.g., both transmission of the initial signal, and then reception of the reflected or otherwise affected signal) and may suffer from a low signal-to-noise ratio. Additionally or alternatively, there may be low correlation between a monostatic radar cross section (RCS) and a bistatic RCS. This may lead to a loss in amplitude information of one or more channel taps and, in some cases, scattering elements present in the bistatic channel may not be detected. Additionally or alternatively, velocity estimation may be limited to a radial direction. Additionally or alternatively, a co-located radar may use active sensing, which may involve increased power consumption, increased radar interference, other adverse effects, or any combination thereof.

To reduce or eliminate such deficiencies, multi-static sensing may be employed. Such multi-static sensing network (e.g., the system300) may lead to denser point clouds, higher channel estimation accuracy, better classification, association, boundary detection, or any combination thereof. Further, such approaches may offer improved association and correlation with communication channels (e.g., a communication channel between the communication node220at point A and the communication node220at point B), which may be due at least in part on a larger coverage area, a spatially diverse radar cross section, rich scattering characteristics, a distributed radial velocity, less interference, less power consumption (e.g., due to the use of passive receivers, instead of using co-located radars in the network), other characteristics or improvements, or any combination thereof. Such approaches may further improve data rates, latency, reliability, other improvements, or any combination thereof due to improved blockage prediction, line-of-sight vs. non line-of-sight classification, beam management, MCS selection, resource allocation, reduced training overhead, other improvements, or any combination thereof.

For example, the RSU215may identify potential remote RF sensing nodes (e.g., communication nodes220, which may be monostatic transmit/receive, bistatic/multi static transmit, or bistatic/multi static receive) to assist in communications (e.g., V2X communications). The communication nodes220may transmit their capabilities (e.g., either periodically or event triggered) along with their request for information transfer (e.g., an aggregated multi static channel estimate) from RSU. The RSU215may determine to gather multi static sensing estimates either for global considerations or for specific considerations between a cluster of a few communication nodes220. In some examples, the RSU215may employ an optimization or improvement approach to choose locations, orientations, modes (e.g., monostatic, bistatic, or multi static), update rate, other parameters, or any combination thereof of RF sensing nodes.

The RSU215may transmit the sensor use request along with one or more suggested configurations, one or more required configurations, or any combination thereof to the chosen sensing nodes (e.g., via co located communicating UE nodes). One or more communications nodes220(e.g., those that receive the sensor use request) may configure one or more co-located sensors accordingly and may further transmit an acknowledgement (e.g., to the RSU215or other entity). Additionally or alternatively, the communications nodes220may transmit one or more specifications that the communications nodes220can provide (either individually or collectively).

The RSU215may receive the acknowledgement, the configurations, or both, and the RSU215may perform revised resource allocation for the sensor nodes. Additionally or alternatively, The RSU215may enter a “ready” mode to perform its own sensing operations. Such sensing operations may either employ its own co-located monostatic sensor or sensors or may act as a bistatic or multi-static transmitter (e.g., where the other remote sensing node(s) will act as bistatic or multi-static multi receiver), a bistatic multi-static receiver (e.g., where the other remote sensing node(s) will act as bistatic multi static transmitters), or any combination thereof.

The RSU215may gather the information from the chosen nodes (e.g., remote, co-located, or both). Then, the RSU215may process the information to extract one or more channel estimates (e.g., multi static sensing estimates), additional information (e.g., related to situational awareness), or any combination thereof. The RSU215may then transmit part or all of such information to one or more of the communication nodes220. For example, the RSU215may transmit a channel estimate to one or more communications nodes220that are using the associated communication channel.

FIG.4illustrates an example of a process flow400that supports multi-static sensing coordination in accordance with examples described herein. The process flow400may implement various aspects of the present disclosure described with reference toFIGS.1-3. The process flow400may include RSU410and communication nodes415, which may be examples of similarly named elements as described with reference toFIGS.1-3.

In the following description of the process flow400, the operations between the RSU410and the communication nodes415is performed in different orders or at different times. Some operations may also be left out of the process flow400, or other operations may be added. Although the RSU410and the communication nodes415are shown performing the operations of the process flow400, some aspects of some operations may also be performed by other elements of the process flow400or by elements that are not depicted in the process flow, or any combination thereof.

At420, the RSU410may select the first communication node as a node for multi-static sensing operations based on a coverage area, a location of the first communication node, an orientation of the first communication node, a communication node location density, a sensing mode to be used for the one or more multi-static sensing measurements, interference associated with the first communication node, or any combination thereof. Additionally or alternatively, the RSU410may select the first communication node as a node for multi-static sensing operations based on one or more sensing parameter estimates.

For example, the RSU410may identify potential remote RF sensing nodes. The RSU410may announce a sensing service request periodically in an associated coverage area. In some examples, events may also trigger such a discovery phase (e.g., an increase in congestion or mobility). Such remote RF sensing nodes (e.g., the communication nodes415) may be remote nodes, infrastructure radio-head nodes, mobile nodes (e.g., sensing nodes mounted on vehicles), RSU-mounted or associated co-located nodes.

In some examples, the RSU410may determine to gather multi static sensing estimates either for global considerations or for specific considerations between a cluster of a few communication nodes415. For example, a global sensing mode may be employed. Such a global sensing mode may be for communicating nodes in a coverage area (e.g., the communication nodes415). A global sensing mode may aid in reducing power consumption, use of space time frequency resources, or both, for RF sensing nodes. Such a global sensing mode may provide a coarse channel estimate and situational awareness to several communicating users within a coverage area (e.g., in dynamic vehicular environments). In some examples, measurements and reporting thereof may be done periodically. In such cases, an update rate may depend on or may be based on one or more factors, such as congestion, mobility, location (e.g., a traffic prone location vs. a location with little traffic that may be determined relative to a threshold), dense or sparse scattering (e.g., which may be determined relative to a threshold), day, time, or any combination thereof. In some examples, measurements and reporting thereof may be event triggered (e.g., when a vehicle enters or exists in a coverage area of the RSU410or when an accident occurs). Such global sensing information may produce an indication of a direction of traffic flow and may aid in proactively adapting space time frequency resource allocation.

In some examples, a specific or local sensing mode may be employed. Such an approach may involve a cluster of multiple nodes that may be related in some way (e.g., in a geographic area, in a coverage area of a RSU or a network entity, belonging to a grouping of nodes, other relationships, or any combination thereof). Such an approach may involve assisting communications between two communication nodes415. Such an approach may aid in estimating communication channel parameters, link establishment, adaptively adjusting transmit parameters, other operations, or any combination thereof).

In some examples, a global sensing mode and a specific or local sensing mode may be employed independently or may be employed cooperatively. For example, a specific sensing mode may be used after the use of a global sensing mode for a fine channel estimate and (more) accurate situational awareness that may be specific to one or more considerations of the few concerned communicating nodes. Additionally or alternatively, a global sensing mode may be triggered after specific sensing modes have been carried over for different clusters of a few communicating nodes. Such an approach may aid in addressing common sensing requests used by each of these communicating node clusters.

In some examples, the RSU410may determine to gather multi static sensing estimates either for global considerations or for specific considerations between a cluster of a few communication nodes415. In some approaches, the RSU410may employ an improvement or adjustment approach for selecting locations, orientations, modes (e.g., monostatic, bistatic, or multi-static), an update rate for sensing nodes, or any combination thereof.

In some examples, the improvement or adjustment approach may depend or be based on whether a collection mode being used is a global sensing mode or a specific/local mode. For a global sensing mode, locations, orientations, or both may be chosen to support coarse channel estimation and situational awareness, and may, additionally or alternatively, be chosen to support a wide coverage area (e.g., determined in relation to a threshold). In such an approach, the sensors' locations may be widely separated (e.g., low effective sensor network density) within a large coverage area (e.g., redundancy of sensing the same environment may be avoided). Transmit parameters, reception parameters, or both may be chosen to allow for coarse estimation (e.g., such as low update rate, small bandwidth, sweeping beams) with low power consumption and reduced space time frequency resources.

For a specific/local sensing mode, locations, orientations, or both may be chosen to support fine channel estimate and accurate situational aw awareness mode for a given cluster of a few communicating nodes. In some examples, the sensors' location (e.g., density, distribution, or both) may be chosen specific to the location, mobility, or both of the few concerned communicating nodes (e.g., such as the ones between their locations). In some examples, selection of the sensors may involve consideration of a trade-off or balance between detection (e.g., outage or diversity) and estimation (e.g., accuracy or redundancy) performance. In some cases, transmit parameters, reception parameters, or both may be chosen to allow for fine estimation. (e.g., high update rate, large bandwidth, other considerations, or any combination thereof).

In some examples, sensing nodes may be chosen to avoid causing unfavorable interference between sensing nodes (e.g., by emphasizing the use of multi-static sensing over separate monostatic sensing).

In some examples, improvement or adjustment may be based on one or more sensing parameter estimates (e.g., range, Doppler parameters, angle, other information, or any combination thereof), quality indications (e.g., key performance indicators, such as misdetection information, false alarm information, estimation accuracy information, latency information, or any combination thereof) of sensing parameter estimates, one or more types of information quantization or compression of channel estimates, other factors, or any combination thereof. In some examples, improvement or adjustment may also be based on mobility, congestion, a measure of how dynamic an environment may be, application requirements, event considerations, priority considerations, other factors, or any combination thereof. For example, in a situation with heavy local congestion with high communication needs in a complex and dynamic vehicular environment, the selection of the sensing nodes may be constrained by the high demand of space time frequency resources used for communication data transmission. In such a case, a specific sensing mode may be utilized more often, optionally with an intermittent global sensing mode for reduced overhead. Other combinations or configurations of sensing modes may also be employed, and are contemplated by the subject matter disclosed herein. In another example, if there is not much communication traffic, but lots of objects (e.g., pedestrians or bicyclists) are moving, then multi-static sensing needs may be increased with a higher update rate.

At425, the RSU410may transmit, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. In some examples, the RSU410may transmit the request for multi-static sensing capability information based on a trigger event associated with a coverage area of the RSU.

At430, the RSU410may receive, from the first communication node, a report that may indicate the multi-static sensing capability information for the first communication node. In some examples, the RSU410may receive, from the first communication node, node information that may include location information, mobility information, orientation information, availability information, or any combination thereof. In some examples, the one or more multi-static sensing parameters may be selected based on the node information. In some examples, the multi-static sensing capability information may include sensor capability information, availability information, coverage information, one or more transmission parameters, one or more reception parameters, a sensing mode, or any combination thereof.

For example, remote sensing nodes (e.g., the communication nodes415) with communication capability may respond back with their sensor capabilities, availability schedule, or other capabilities. Additionally or alternatively, the communication nodes4145may transmit a request for information transfer (e.g., such as aggregated multi-static channel estimates).

In some examples, the communication nodes415may transmit node information, such as a location (e.g., a GPS location description or other location description), mobility information, orientation information, availability information, or any combination thereof. In some examples, a communication node415may transmit a sensing capability (e.g., along with tag of whether it is reconfigurable or static). Such capability information may include coverage information, such as a field of view, a range (e.g., maximum, minimum, average, or both), a velocity (e.g., maximum, minimum, average, or any combination thereof). In some examples, the communication nodes415may transmit transmission/reception parameters (e.g., optionally along with a tag indicating whether one or more such parameters are reconfigurable or static), a transmit power, a duty cycle, a waveform, one or more beamforming parameters, an update rate, a scanning mode, a tracking mode, tracking mode, other capabilities, or any combination thereof.

In some examples, the communication nodes415may transmit a sensing capability mode. For example, the mode may be a monostatic mode in which the communication node415does its own sensing (e.g., with co located transmission and reception) and sends (e.g., to the RSU410) raw reception data, processed channel estimates, or any combination thereof. Additionally or alternatively, the mode may be a multi-static transmit sensing mode in which the communication node415acts as an active transmit node (e.g., with or without a co located reception node(s)). In some examples, a synchronization procedure might be used between one or more nodes for multi static sensing. Additionally or alternatively, the mode may be a multi-static sensing reception mode in which the communication node415may act as a passive or active receiver (e.g., with or without a co-located transmit node(s). In some examples, a synchronization procedure might be used between one or more nodes for multi static sensing. Further, a communication nodes415operating in such a manner may transmit raw reception data, one or more processed channel estimates, or any combination thereof (e.g., to the RSU410).

In some examples, the communication nodes415may transmit performance information, (e.g., key performance indicators) such as misdetection information, false alarm information, estimation accuracy information, latency information, or any combination thereof. In some examples, the communication nodes415may transmit communication capability information (e.g., information associated with a communication capability of a communication element of the communication node415), which may include a data rate, latency, a block error rate, other performance information, or any combination thereof.

In some examples, the communication nodes415may transmit RF sensing information. Such RF sensing information may be either raw or processed data and may be provided in a preconfigured format or in a format dynamically selected or defined by the RSU410.

In some examples, the communication nodes415may transmit a request for information transfer, which may include aggregated multi-static sensing channel estimates. Such requests may be made to the RSU410or may be made to another entity.

At435, the RSU410may store the multi-static sensing capability information in a database of multi-static sensing capability information. For example, the RSU410may register the interested RF sensing nodes for gathering multi multi-static channel estimates.

At440, the RSU410may transmit, to the first communication node and in response to receiving the multi-static sensing capability information, a control message that may indicate one or more multi-static sensing parameters for the first communication node. In some examples, the one or more multi-static sensing parameters include an indication of one or more communication nodes, a sequence of one or more communication nodes, one or more transmission parameters, one or more reception parameters, a data format for channel estimates, an update rate, or any combination thereof.

For example, the RSU410may indicate or specify a format for reporting back sensing parameter estimates or measurements. Such information may relate to the format, or may relate generally to the sensing measurements. Information transmitted from the communication nodes415to the RSU410may include sensing parameters (e.g., range, angle, Doppler parameters, object boundary boxes, or any combination thereof). Such information may further include an amount of quantization or compression, which may be associated with a sensing overhead. Additionally or alternatively, such information may include a data format to be used to send the sensing information.

In some examples, the RSU410may transmit a sensor use request along with one or more suggested configurations, one or more required configurations, or any combination thereof to the chosen sensing nodes (e.g., via co located communicating UE nodes). The RSU410may transmit an indication (e.g., an optional configuration) of which equipment (e.g., radio heads or locations of radio heads) may be employed for a given communication node415. For example, the RSU410may provide an activation sequence (e.g., on/off events over time) which may be based on the mobility of concerned remote communicating nodes. Additionally or alternatively, The RSU410may provide transmission parameters, reception parameters, or both for radio heads. Additionally or alternatively, The RSU410may transmit one or more reception configurations or indications. Additionally or alternatively, The RSU410may transmit an indication of a data format (e.g., for reporting back the sensing parameter estimates or measurements).

At445, the RSU410may receive, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. In some examples, the RSU410may receive, from the first communication node, the one or more multi-static sensing measurements at periodic intervals. In some examples, the RSU410may receive, from the first communication node, one or more communication channel parameters associated with a group of communication nodes, an indication of a scattering element associated with a communication channel, an indication of a blocking element associated with the communication channel, a line-of-sight indication associated with the communication channel, a travel direction indication, or any combination thereof.

For example, the RSU410may gather the information from the chosen nodes (e.g., remote, co-located, or both). Then, the RSU215may process the information to extract one or more channel estimates (e.g., multi static sensing estimates), additional information (e.g., related to situational awareness), or any combination thereof. Such processing may result in various types of information, including communication channel parameters (e.g., parameters associated with one or more communication nodes415, which may include a delay Doppler angular profile, scattering detection, a channel amplitude profile, or any combination thereof), information about scattering elements (e.g., location, orientation, mobility, or any combination thereof of potential scatterers, which may be beneficial for reflection operations optionally involving metallic objects with large surfaces that may aid better propagation), information about blocking elements (e.g., location, mobility, other information, or any combination thereof), a line-of-sight or non line-of-sight indication, a direction of traffic flow or movement (e.g., for objects both equipped or not equipped with communicating UE nodes), improvement or adjustment of RF sensing nodes to assist communications in vehicular environments (e.g., such as for tracking mode), additional information, or any combination thereof.

At450, the RSU410may transmit, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements.

At455, the RSU410may receive, from the first communication node, a report that may indicate updated multi-static sensing capability information. For example, registered RF sensing nodes (e.g., the communication nodes415) may update (either periodically or event event-triggered) their sensor capabilities, availability schedule, information requests, or any combination thereof.

At460, the RSU410may transmit, to the first communication node, control signaling that may indicate an update to the one or more multi-static sensing parameters.

FIG.5shows a block diagram500of a device505that supports multi-static sensing coordination in accordance with examples described herein. The device505may be an example of aspects of a roadside unit as described herein. The device505may include a receiver510, a transmitter515, and a communications manager520. The device505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver510may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). Information may be passed on to other components of the device505. The receiver510may utilize a single antenna or a set of multiple antennas.

The transmitter515may provide a means for transmitting signals generated by other components of the device505. For example, the transmitter515may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). In some examples, the transmitter515may be co-located with a receiver510in a transceiver module. The transmitter515may utilize a single antenna or a set of multiple antennas.

The communications manager520, the receiver510, the transmitter515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager520may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver510, the transmitter515, or both. For example, the communications manager520may receive information from the receiver510, send information to the transmitter515, or be integrated in combination with the receiver510, the transmitter515, or both to obtain information, output information, or perform various other operations as described herein.

Additionally, or alternatively, the communications manager520may support wireless communications at a roadside unit (RSU) in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The communications manager520may be configured as or otherwise support a means for receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The communications manager520may be configured as or otherwise support a means for transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The communications manager520may be configured as or otherwise support a means for receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The communications manager520may be configured as or otherwise support a means for transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements.

By including or configuring the communications manager520in accordance with examples as described herein, the device505(e.g., a processor controlling or otherwise coupled with the receiver510, the transmitter515, the communications manager520, or a combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or a combination thereof.

FIG.6shows a block diagram600of a device605that supports multi-static sensing coordination in accordance with examples described herein. The device605may be an example of aspects of a device505or a roadside unit115as described herein. The device605may include a receiver610, a transmitter615, and a communications manager620. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver610may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). Information may be passed on to other components of the device605. The receiver610may utilize a single antenna or a set of multiple antennas.

The transmitter615may provide a means for transmitting signals generated by other components of the device605. For example, the transmitter615may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). In some examples, the transmitter615may be co-located with a receiver610in a transceiver module. The transmitter615may utilize a single antenna or a set of multiple antennas.

The device605, or various components thereof, may be an example of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager620may include a sensing request component625, a capability information component630, a sensing parameter component635, a sensing measurement component640, a channel estimate component645, or any combination thereof. The communications manager620may be an example of aspects of a communications manager520as described herein. In some examples, the communications manager620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager620may support wireless communications at a roadside unit (RSU) in accordance with examples as disclosed herein. The sensing request component625may be configured as or otherwise support a means for transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The capability information component630may be configured as or otherwise support a means for receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The sensing parameter component635may be configured as or otherwise support a means for transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The sensing measurement component640may be configured as or otherwise support a means for receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The channel estimate component645may be configured as or otherwise support a means for transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements.

FIG.7shows a block diagram700of a communications manager720that supports multi-static sensing coordination in accordance with examples described herein. The communications manager720may be an example of aspects of a communications manager520, a communications manager620, or both, as described herein. The communications manager720, or various components thereof, may be an example of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager720may include a sensing request component725, a capability information component730, a sensing parameter component735, a sensing measurement component740, a channel estimate component745, a node information component750, a node selection component755, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Additionally, or alternatively, the communications manager720may support wireless communications at a roadside unit (RSU) in accordance with examples as disclosed herein. The sensing request component725may be configured as or otherwise support a means for transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The capability information component730may be configured as or otherwise support a means for receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The sensing parameter component735may be configured as or otherwise support a means for transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The sensing measurement component740may be configured as or otherwise support a means for receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The channel estimate component745may be configured as or otherwise support a means for transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements.

In some examples, the capability information component730may be configured as or otherwise support a means for receiving, from the first communication node, a report indicating updated multi-static sensing capability information. In some examples, the sensing parameter component735may be configured as or otherwise support a means for transmitting, to the first communication node, an update to the one or more multi-static sensing parameters.

In some examples, the node information component750may be configured as or otherwise support a means for receiving, from the first communication node, node information including location information, mobility information, orientation information, availability information, or any combination thereof, where the one or more multi-static sensing parameters are selected based on the node information.

In some examples, the sensing measurement component740may be configured as or otherwise support a means for receiving, from the first communication node, the one or more multi-static sensing measurements at periodic intervals.

In some examples, the sensing request component725may be configured as or otherwise support a means for transmitting the request for multi-static sensing capability information based on a trigger event associated with a coverage area of the RSU.

In some examples, the sensing measurement component740may be configured as or otherwise support a means for receiving, from the first communication node, one or more communication channel parameters associated with a group of communication nodes, an indication of a scattering element associated with a communication channel, an indication of a blocking element associated with the communication channel, a line of sight indication associated with the communication channel, a travel direction indication, or any combination thereof.

In some examples, the node selection component755may be configured as or otherwise support a means for selecting the first communication node as a node for multi-static sensing operations based on a coverage area, a location of the first communication node, an orientation of the first communication node, a communication node location density, a sensing mode to be used for the one or more multi-static sensing measurements, interference associated with the first communication node, or any combination thereof.

In some examples, the node selection component755may be configured as or otherwise support a means for selecting the first communication node as a node for multi-static sensing operations based on one or more sensing parameter estimates.

In some examples, the multi-static sensing capability information includes sensor capability information, availability information, coverage information, one or more transmission parameters, one or more reception parameters, a sensing mode, or any combination thereof.

In some examples, the one or more multi-static sensing parameters include an indication of one or more communication nodes, a sequence of one or more communication nodes, one or more transmission parameters, one or more reception parameters, a data format for channel estimates, an update rate, or any combination thereof.

In some examples, the capability information component730may be configured as or otherwise support a means for storing the multi-static sensing capability information in a database of multi-static sensing capability information.

FIG.8shows a diagram of a system800including a device805that supports multi-static sensing coordination in accordance with examples described herein. The device805may be an example of or include the components of a device505, a device605, or a roadside unit as described herein. The device805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager820, a network communications manager810, a transceiver815, an antenna825, a memory830, code835, a processor840, and an inter-station communications manager845. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus850).

The network communications manager810may manage communications with a core network130(e.g., via one or more wired backhaul links). For example, the network communications manager810may manage the transfer of data communications for client devices, such as one or more UEs115.

In some cases, the device805may include a single antenna825. However, in some other cases the device805may have more than one antenna825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver815may communicate bi-directionally, via the one or more antennas825, wired, or wireless links as described herein. For example, the transceiver815may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver815may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas825for transmission, and to demodulate packets received from the one or more antennas825. The transceiver815, or the transceiver815and one or more antennas825, may be an example of a transmitter515, a transmitter615, a receiver510, a receiver610, or any combination thereof or component thereof, as described herein.

The memory830may include RAM and ROM. The memory830may store computer-readable, computer-executable code835including instructions that, when executed by the processor840, cause the device805to perform various functions described herein. The code835may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code835may not be directly executable by the processor840but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory830may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor840may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor840may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor840. The processor840may be configured to execute computer-readable instructions stored in a memory (e.g., the memory830) to cause the device805to perform various functions (e.g., functions or tasks supporting multi-static sensing coordination). For example, the device805or a component of the device805may include a processor840and memory830coupled with or to the processor840, the processor840and memory830configured to perform various functions described herein.

The inter-station communications manager845may manage communications with other base stations or network entities105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other base stations or network entities105. For example, the inter-station communications manager845may coordinate scheduling for transmissions to UEs115for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager845may provide an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations or network entities105.

Additionally, or alternatively, the communications manager820may support wireless communications at a roadside unit (RSU) in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The communications manager820may be configured as or otherwise support a means for receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The communications manager820may be configured as or otherwise support a means for transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The communications manager820may be configured as or otherwise support a means for receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The communications manager820may be configured as or otherwise support a means for transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements.

By including or configuring the communications manager820in accordance with examples as described herein, the device805may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or a combination thereof.

In some examples, the communications manager820may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver815, the one or more antennas825, or any combination thereof. Although the communications manager820is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager820may be supported by or performed by the processor840, the memory830, the code835, or any combination thereof. For example, the code835may include instructions executable by the processor840to cause the device805to perform various aspects of multi-static sensing coordination as described herein, or the processor840and the memory830may be otherwise configured to perform or support such operations.

FIG.9shows a block diagram900of a device905that supports multi-static sensing coordination in accordance with examples described herein. The device905may be an example of aspects of a communication node as described herein. The device905may include a receiver910, a transmitter915, and a communications manager920. The device905may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver910may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). Information may be passed on to other components of the device905. The receiver910may utilize a single antenna or a set of multiple antennas.

The transmitter915may provide a means for transmitting signals generated by other components of the device905. For example, the transmitter915may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). In some examples, the transmitter915may be co-located with a receiver910in a transceiver module. The transmitter915may utilize a single antenna or a set of multiple antennas.

The communications manager920, the receiver910, the transmitter915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to obtain information, output information, or perform various other operations as described herein.

Additionally, or alternatively, the communications manager920may support wireless communications at a communication node in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The communications manager920may be configured as or otherwise support a means for transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The communications manager920may be configured as or otherwise support a means for receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The communications manager920may be configured as or otherwise support a means for transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters.

By including or configuring the communications manager920in accordance with examples as described herein, the device905(e.g., a processor controlling or otherwise coupled with the receiver910, the transmitter915, the communications manager920, or a combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or a combination thereof.

FIG.10shows a block diagram1000of a device1005that supports multi-static sensing coordination in accordance with examples described herein. The device1005may be an example of aspects of a device905or a communication node as described herein. The device1005may include a receiver1010, a transmitter1015, and a communications manager1020. The device1005may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1010may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). Information may be passed on to other components of the device1005. The receiver1010may utilize a single antenna or a set of multiple antennas.

The transmitter1015may provide a means for transmitting signals generated by other components of the device1005. For example, the transmitter1015may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-static sensing coordination). In some examples, the transmitter1015may be co-located with a receiver1010in a transceiver module. The transmitter1015may utilize a single antenna or a set of multiple antennas.

The device1005, or various components thereof, may be an example of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager1020may include a sensing request element1025, a capability information element1030, a sensing parameter element1035, a sensing measurement element1040, or any combination thereof. The communications manager1020may be an example of aspects of a communications manager920as described herein. In some examples, the communications manager1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1020may support wireless communications at a communication node in accordance with examples as disclosed herein. The sensing request element1025may be configured as or otherwise support a means for receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The capability information element1030may be configured as or otherwise support a means for transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The sensing parameter element1035may be configured as or otherwise support a means for receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The sensing measurement element1040may be configured as or otherwise support a means for transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters.

FIG.11shows a block diagram1100of a communications manager1120that supports multi-static sensing coordination in accordance with examples described herein. The communications manager1120may be an example of aspects of a communications manager920, a communications manager1020, or both, as described herein. The communications manager1120, or various components thereof, may be an example of means for performing various aspects of multi-static sensing coordination as described herein. For example, the communications manager1120may include a sensing request element1125, a capability information element1130, a sensing parameter element1135, a sensing measurement element1140, a channel estimate element1145, a node information element1150, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Additionally, or alternatively, the communications manager1120may support wireless communications at a communication node in accordance with examples as disclosed herein. The sensing request element1125may be configured as or otherwise support a means for receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The capability information element1130may be configured as or otherwise support a means for transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The sensing parameter element1135may be configured as or otherwise support a means for receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The sensing measurement element1140may be configured as or otherwise support a means for transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters.

In some examples, the channel estimate element1145may be configured as or otherwise support a means for receiving, from the RSU, one or more channel estimates determined based on the one or more multi-static sensing measurements.

In some examples, the capability information element1130may be configured as or otherwise support a means for transmitting, to the RSU, a report indicating updated multi-static sensing capability information. In some examples, the sensing parameter element1135may be configured as or otherwise support a means for receiving, from the RSU, an update to the one or more multi-static sensing parameters.

In some examples, the node information element1150may be configured as or otherwise support a means for transmitting, to the RSU, node information including location information, mobility information, orientation information, availability information, or any combination thereof, where the one or more multi-static sensing parameters are selected based on the node information.

In some examples, the sensing measurement element1140may be configured as or otherwise support a means for transmitting, to the RSU, the one or more multi-static sensing measurements at periodic intervals.

In some examples, the sensing measurement element1140may be configured as or otherwise support a means for transmitting, to the RSU, one or more communication channel parameters associated with a group of communication nodes, an indication of a scattering element associated with a communication channel, an indication of a blocking element associated with the communication channel, a line of sight indication associated with the communication channel, a travel direction indication, or any combination thereof.

In some examples, the multi-static sensing capability information includes sensor capability information, availability information, coverage information, one or more transmission parameters, one or more reception parameters, a sensing mode, or any combination thereof.

In some examples, the one or more multi-static sensing parameters include an indication of one or more communication nodes, a sequence of one or more communication nodes, one or more transmission parameters, one or more reception parameters, a data format for channel estimates, an update rate, or any combination thereof.

FIG.12shows a diagram of a system1200including a device1205that supports multi-static sensing coordination in accordance with examples described herein. The device1205may be an example of or include the components of a device905, a device1005, or a communication node as described herein. The device1205may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1220, an I/O controller1210, a transceiver1215, an antenna1225, a memory1230, code1235, and a processor1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1245).

The I/O controller1210may manage input and output signals for the device1205. The I/O controller1210may also manage peripherals not integrated into the device1205. In some cases, the I/O controller1210may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1210may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller1210may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1210may be implemented as part of a processor, such as the processor1240. In some cases, a user may interact with the device1205via the I/O controller1210or via hardware components controlled by the I/O controller1210.

In some cases, the device1205may include a single antenna1225. However, in some other cases, the device1205may have more than one antenna1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1215may communicate bi-directionally, via the one or more antennas1225, wired, or wireless links as described herein. For example, the transceiver1215may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1215may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1225for transmission, and to demodulate packets received from the one or more antennas1225. The transceiver1215, or the transceiver1215and one or more antennas1225, may be an example of a transmitter915, a transmitter1015, a receiver910, a receiver1010, or any combination thereof or component thereof, as described herein.

The memory1230may include RAM and ROM. The memory1230may store computer-readable, computer-executable code1235including instructions that, when executed by the processor1240, cause the device1205to perform various functions described herein. The code1235may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1235may not be directly executable by the processor1240but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1230may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1240may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1240may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1240. The processor1240may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1230) to cause the device1205to perform various functions (e.g., functions or tasks supporting multi-static sensing coordination). For example, the device1205or a component of the device1205may include a processor1240and memory1230coupled with or to the processor1240, the processor1240and memory1230configured to perform various functions described herein.

Additionally, or alternatively, the communications manager1220may support wireless communications at a communication node in accordance with examples as disclosed herein. For example, the communications manager1220may be configured as or otherwise support a means for receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The communications manager1220may be configured as or otherwise support a means for transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The communications manager1220may be configured as or otherwise support a means for receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The communications manager1220may be configured as or otherwise support a means for transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters.

By including or configuring the communications manager1220in accordance with examples as described herein, the device1205may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or a combination thereof.

In some examples, the communications manager1220may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1215, the one or more antennas1225, or any combination thereof. Although the communications manager1220is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1220may be supported by or performed by the processor1240, the memory1230, the code1235, or any combination thereof. For example, the code1235may include instructions executable by the processor1240to cause the device1205to perform various aspects of multi-static sensing coordination as described herein, or the processor1240and the memory1230may be otherwise configured to perform or support such operations.

FIG.13shows a flowchart illustrating a method1300that supports multi-static sensing coordination in accordance with examples described herein. The operations of the method1300may be implemented by a roadside unit or its components as described herein. For example, the operations of the method1300may be performed by a roadside unit as described with reference toFIGS.1through8. In some examples, a roadside unit may execute a set of instructions to control the functional elements of the roadside unit to perform the described functions. Additionally, or alternatively, the roadside unit may perform aspects of the described functions using special-purpose hardware.

At1305, the method may include transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by a sensing request component725as described with reference toFIG.7.

At1310, the method may include receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by a capability information component730as described with reference toFIG.7.

At1315, the method may include transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a sensing parameter component735as described with reference toFIG.7.

At1320, the method may include receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The operations of1320may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1320may be performed by a sensing measurement component740as described with reference toFIG.7.

At1325, the method may include transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements. The operations of1325may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1325may be performed by a channel estimate component745as described with reference toFIG.7.

FIG.14shows a flowchart illustrating a method1400that supports multi-static sensing coordination in accordance with examples described herein. The operations of the method1400may be implemented by a roadside unit or its components as described herein. For example, the operations of the method1400may be performed by a roadside unit as described with reference toFIGS.1through8. In some examples, a roadside unit may execute a set of instructions to control the functional elements of the roadside unit to perform the described functions. Additionally, or alternatively, the roadside unit may perform aspects of the described functions using special-purpose hardware.

At1405, the method may include selecting the first communication node as a node for multi-static sensing operations based on a coverage area, a location of the first communication node, an orientation of the first communication node, a communication node location density, a sensing mode to be used for the one or more multi-static sensing measurements, interference associated with the first communication node, or any combination thereof. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by a node selection component755as described with reference toFIG.7.

At1410, the method may include transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a sensing request component725as described with reference toFIG.7.

At1415, the method may include receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a capability information component730as described with reference toFIG.7.

At1420, the method may include transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node. The operations of1420may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1420may be performed by a sensing parameter component735as described with reference toFIG.7.

At1425, the method may include receiving, from the first communication node, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The operations of1425may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1425may be performed by a sensing measurement component740as described with reference toFIG.7.

At1430, the method may include transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based on the one or more multi-static sensing measurements. The operations of1430may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1430may be performed by a channel estimate component745as described with reference toFIG.7.

FIG.15shows a flowchart illustrating a method1500that supports multi-static sensing coordination in accordance with examples described herein. The operations of the method1500may be implemented by a communication node or its components as described herein. For example, the operations of the method1500may be performed by a communication node as described with reference toFIGS.1through4and9through12. In some examples, a communication node may execute a set of instructions to control the functional elements of the communication node to perform the described functions. Additionally, or alternatively, the communication node may perform aspects of the described functions using special-purpose hardware.

At1505, the method may include receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by a sensing request element1125as described with reference toFIG.11.

At1510, the method may include transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a capability information element1130as described with reference toFIG.11.

At1515, the method may include receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a sensing parameter element1135as described with reference toFIG.11.

At1520, the method may include transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The operations of1520may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1520may be performed by a sensing measurement element1140as described with reference toFIG.11.

FIG.16shows a flowchart illustrating a method1600that supports multi-static sensing coordination in accordance with examples described herein. The operations of the method1600may be implemented by a communication node or its components as described herein. For example, the operations of the method1600may be performed by a communication node as described with reference toFIGS.1through4and9through12. In some examples, a communication node may execute a set of instructions to control the functional elements of the communication node to perform the described functions. Additionally, or alternatively, the communication node may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by a sensing request element1125as described with reference toFIG.11.

At1610, the method may include transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a capability information element1130as described with reference toFIG.11.

At1615, the method may include transmitting, to the RSU, node information including location information, mobility information, orientation information, availability information, or any combination thereof, where the one or more multi-static sensing parameters are selected based on the node information. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a node information element1150as described with reference toFIG.11.

At1620, the method may include receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information. The operations of1620may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1620may be performed by a sensing parameter element1135as described with reference toFIG.11.

At1625, the method may include transmitting, to the RSU, one or more multi-static sensing measurements obtained based on the one or more multi-static sensing parameters. The operations of1625may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1625may be performed by a sensing measurement element1140as described with reference toFIG.11.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communications at a roadside unit (RSU), comprising: transmitting, to a first communication node, a request for multi-static sensing capability information associated with the first communication node; receiving, from the first communication node, a report indicating the multi-static sensing capability information for the first communication node; transmitting, to the first communication node and in response to receiving the multi-static sensing capability information, a control message indicating one or more multi-static sensing parameters for the first communication node; receiving, from the first communication node, one or more multi-static sensing measurements obtained based at least in part on the one or more multi-static sensing parameters; and transmitting, to the first communication node, a second communication node, or both, one or more channel estimates determined based at least in part on the one or more multi-static sensing measurements.

Aspect 2: The method of aspect 1, further comprising: receiving, from the first communication node, a report indicating updated multi-static sensing capability information; and transmitting, to the first communication node, an update to the one or more multi-static sensing parameters.

Aspect 3: The method of any of aspects 1 through 2, further comprising: receiving, from the first communication node, node information comprising location information, mobility information, orientation information, availability information, or any combination thereof, wherein the one or more multi-static sensing parameters are selected based at least in part on the node information.

Aspect 4: The method of any of aspects 1 through 3, further comprising: receiving, from the first communication node, the one or more multi-static sensing measurements at periodic intervals.

Aspect 5: The method of any of aspects 1 through 4, further comprising: transmitting the request for multi-static sensing capability information based on a trigger event associated with a coverage area of the RSU.

Aspect 6: The method of any of aspects 1 through 5, further comprising: receiving, from the first communication node, one or more communication channel parameters associated with a group of communication nodes, an indication of a scattering element associated with a communication channel, an indication of a blocking element associated with the communication channel, a line of sight indication associated with the communication channel, a travel direction indication, or any combination thereof.

Aspect 7: The method of any of aspects 1 through 6, further comprising: selecting the first communication node as a node for multi-static sensing operations based at least in part on a coverage area, a location of the first communication node, an orientation of the first communication node, a communication node location density, a sensing mode to be used for the one or more multi-static sensing measurements, interference associated with the first communication node, or any combination thereof.

Aspect 8: The method of any of aspects 1 through 7, further comprising: selecting the first communication node as a node for multi-static sensing operations based at least in part on one or more sensing parameter estimates.

Aspect 9: The method of any of aspects 1 through 8, wherein the multi-static sensing capability information comprises sensor capability information, availability information, coverage information, one or more transmission parameters, one or more reception parameters, a sensing mode, or any combination thereof.

Aspect 10: The method of any of aspects 1 through 9, wherein the one or more multi-static sensing parameters include an indication of one or more communication nodes, a sequence of one or more communication nodes, one or more transmission parameters, one or more reception parameters, a data format for channel estimates, an update rate, or any combination thereof.

Aspect 11: The method of any of aspects 1 through 10, further comprising: storing the multi-static sensing capability information in a database of multi-static sensing capability information.

Aspect 12: A method for wireless communications at a communication node, comprising: receiving, from a roadside unit (RSU), a request for multi-static sensing capability information associated with the communication node; transmitting, to the RSU, a report indicating the multi-static sensing capability information associated with the communication node; receiving, from the RSU, a control message indicating one or more multi-static sensing parameters in response to transmitting the multi-static sensing capability information; and transmitting, to the RSU, one or more multi-static sensing measurements obtained based at least in part on the one or more multi-static sensing parameters.

Aspect 13: The method of aspect 12, further comprising: receiving, from the RSU, one or more channel estimates determined based at least in part on the one or more multi-static sensing measurements.

Aspect 14: The method of any of aspects 12 through 13, further comprising: transmitting, to the RSU, a report indicating updated multi-static sensing capability information; and receiving, from the RSU, an update to the one or more multi-static sensing parameters.

Aspect 15: The method of any of aspects 12 through 14, further comprising: transmitting, to the RSU, node information comprising location information, mobility information, orientation information, availability information, or any combination thereof, wherein the one or more multi-static sensing parameters are selected based at least in part on the node information.

Aspect 16: The method of any of aspects 12 through 15, further comprising: transmitting, to the RSU, the one or more multi-static sensing measurements at periodic intervals.

Aspect 17: The method of any of aspects 12 through 16, further comprising: transmitting, to the RSU, one or more communication channel parameters associated with a group of communication nodes, an indication of a scattering element associated with a communication channel, an indication of a blocking element associated with the communication channel, a line of sight indication associated with the communication channel, a travel direction indication, or any combination thereof.

Aspect 18: The method of any of aspects 12 through 17, wherein the multi-static sensing capability information comprises sensor capability information, availability information, coverage information, one or more transmission parameters, one or more reception parameters, a sensing mode, or any combination thereof.

Aspect 19: The method of any of aspects 12 through 18, wherein the one or more multi-static sensing parameters include an indication of one or more communication nodes, a sequence of one or more communication nodes, one or more transmission parameters, one or more reception parameters, a data format for channel estimates, an update rate, or any combination thereof.

Aspect 20: An apparatus for wireless communications at a roadside unit (RSU), comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 11.

Aspect 21: An apparatus for wireless communications at a roadside unit (RSU), comprising at least one means for performing a method of any of aspects 1 through 11.

Aspect 22: A non-transitory computer-readable medium storing code for wireless communications at a roadside unit (RSU), the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 11.

Aspect 23: An apparatus for wireless communications at a communication node, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 12 through 19.

Aspect 24: An apparatus for wireless communications at a communication node, comprising at least one means for performing a method of any of aspects 12 through 19.

Aspect 25: A non-transitory computer-readable medium storing code for wireless communications at a communication node, the code comprising instructions executable by a processor to perform a method of any of aspects 12 through 19.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.