Configuration sharing for multi-node passive sensing

Abstract

Aspects of the present disclosure relate to systems and methods for receiving, by a first user equipment (UE), a message comprising at least one of: reference signal information (RS-info) relating to one or more reference signals (RSs), the one or more reference signals (RSs) corresponding to line-of-sight (LoS) signals destined for a receiver different from the first UE, and / or data decoding information relating to data scheduled for communication with a second UE other than the first UE. The present disclosure also relates to systems and methods for monitoring at least one of: monitoring a coded signal based on the data decoding information, and / or monitoring one or more RSs based on the RS-info. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] Cross-reference to related applications

[0002] This application is a PCT application, which claims the priority benefit of PCT application No. PCT / CN2020 / 099491 filed with the National Intellectual Property Administration of China on June 30, 2020, and PCT application No. PCT / CN2020 / 099502 filed with the National Intellectual Property Administration of China on June 30, 2020, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques described below relate generally to wireless communication systems, and more particularly to explicitly sharing data decoding and / or reference signal information for multiple transmitters to facilitate multi-node passive sensing using signals transmitted for other receivers. Background Art

[0004] Generally speaking, radar technology is tailored to extract location-based information about an object, such as its distance, speed, angle, position, etc. In some cases, a device employing such radar technology may be able to locate an object early and initiate mitigation efforts, for example, to avoid a collision with the object while traveling on a path toward a detected object. In various cases, a device may utilize radar signals to detect such objects while utilizing other signals to communicate with other devices. As the number of devices capable of such detection increases, and the number of devices relying on such technology increases, the underlying radio access network (RAN) will require a combination of very high data rates, very high reliability, and very low latency. Next-generation wireless telecommunication systems (e.g., such as fifth-generation (5G) or new radio (NR) technologies) are being deployed using millimeter wave (mmW) signals, which may allow for efficient data sharing and communication and may be used to implement improved radar technology.

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

[0006] The following is a summary of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This summary is not an extensive overview of all anticipated features of the present disclosure and is neither intended to identify key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure as a prelude to the more detailed description that will be presented later.

[0007] Aspects of the present disclosure relate to a method for wireless communication. The method includes, for example, receiving, by a first user equipment (UE), a message comprising at least one of: (i) reference signal information (RS-info) indicating a set of resource parameters associated with a reference signal (RS) set corresponding to at least one line-of-sight (LoS) signal targeted at at least one UE other than the first UE, or (ii) data decoding information indicating a first set of data decoding parameters configured to at least partially decode a set of coded data items, the set of coded data items corresponding to a coded signal set configured for full decoding by a second UE via a second set of data decoding parameters; and performing, by the first UE, at least one of: (i) monitoring RSs based on the RS-info, or (ii) monitoring the set of coded signals on one or more channels based on the data decoding information.

[0008] Aspects of the present disclosure also relate to a wireless communication device. The wireless communication device includes, for example: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory. The processor is configured to: receive, via the transceiver, a message comprising at least one of: (i) a reference signal information (RS-info) parameter set associated with one or more reference signals (RS), the one or more reference signals (RS) corresponding to at least one line of sight (LoS) signal targeted at one or more receiving devices different and separate from the wireless communication device, or (ii) a data decoding information parameter set associated with data, the data being scheduled for the purpose of communicating with the one or more receiving devices via the at least one line of sight (LoS) signal targeted at the one or more receiving devices; and use the transceiver to perform at least one of the following: (i) monitor an RS set based on the RS-info parameter set, or (ii) monitor a coded signal set based on the data decoding information parameter set.

[0009] Aspects of the present disclosure also relate to an apparatus for wireless communication, comprising: a component for receiving, by a first user equipment (UE), a message comprising at least one of: (i) a set of reference signal information (RS-info) parameters relating to one or more reference signals (RS), the one or more reference signals (RS) corresponding to at least one line of sight (LoS) signal targeted at one or more other devices that are different and separate from the first UE, or (ii) a set of data decoding information parameters relating to data, the data being scheduled for the purpose of communicating with the one or more other devices via the at least one line of sight (LoS) signal targeted at the one or more other devices; and a component for performing at least one of: (i) monitoring an RS set based on the RS-info parameter set, or (ii) monitoring a coded signal set based on the data decoding information parameters.

[0010] Another aspect of the present disclosure relates to a scheduling entity for wireless communication. The scheduling entity includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor configured to: receive, via the transceiver, at least one of: (i) a reference signal information (RS-info) parameter set including a resource parameter set corresponding to one or more reference signals (RSs) targeted at multiple receiving devices, or (ii) a data decoding information parameter set including a decoding parameter set for decoding a coded signal set transmitted to the multiple receiving devices via one or more coded channels; receive, via the transceiver, from a first user equipment (UE) a request for at least one of: (i) the RS-info parameter set including information related to one or more reference signals (RSs) targeted at at least one second UE other than the first UE, or (ii) data decoding information parameters, wherein the data decoding information corresponds to data decoding for at least one data item scheduled for the at least one second UE; and send, via the transceiver, a message to the first UE, wherein the message includes at least one of: (i) the RS-info parameter set or (ii) the data decoding information parameter set.

[0011] Aspects of the present disclosure relate to receiving, by a user equipment (UE), a message including data decoding information related to data not scheduled for reception by the UE; and monitoring a coded signal based on the data decoding information.

[0012] Aspects of the present disclosure relate to receiving, by a user equipment (UE), a message including RS-info regarding one or more reference signals (RSs) targeted at a receiver other than the UE; and monitoring the RSs based on the RS information.

[0013] A method for receiving transmission configuration information is disclosed. The method includes receiving, by a first entity (e.g., a first user equipment), a configuration message including: reference signal information corresponding to a reference signal set transmitted between a plurality of other entities (e.g., at least two entities other than the first user equipment), and / or data decoding information (e.g., a first data decoding parameter set) indicating a first data decoding parameter set corresponding to data transmitted between the plurality of other entities. The method also includes monitoring, by the first entity, at least one of: (i) a reference signal set based on the reference signal information, and / or (ii) data transmitted between the plurality of other entities (e.g., at least two entities). The method further includes receiving a reference signal set, wherein the reference signal set is a reflected signal indicated by the reference signal information (e.g., indicating that the reference signal set is a reflection of a signal transmitted as a line-of-sight (LoS) signal from one of the plurality of other entities (e.g., to another of the two entities)). The first UE may receive coded data, wherein the coded data is transmitted together with the reference signal set, such as on a demodulation reference signal (DMRS)). In this case, the first UE can utilize transmission configuration information to at least partially decode the coded signal to determine a decoded subset of data items decoded from the complete set of coded data items. The complete set of coded data items includes a first subset of coded data items corresponding to the decoded subset of data items, and a second subset of coded data items corresponding to a remaining subset of coded data items of at least one of two other entities to be decoded. For example, these can be sent between a base station and a second UE. The second UE utilizes a second data decoding parameter set to monitor, receive and determine a complete set of decoded data items from the complete set of coded data items sent to the second UE. In some cases, the transmission configuration information may include additional or different data decoding information (e.g., relative to the first data decoding parameter set). In this case, the method includes utilizing transmission configuration information to receive different sets of coded data items intended for complete decoding by the first entity. In an example, the first UE utilizes transmission configuration information to determine a complete set of decoded data items from the set of coded data items sent to the first UE.

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

[0015] Various aspects of the present disclosure relate to: receiving, by a scheduling entity, reference signal (RS) information including information related to one or more reference signals (RS); receiving, by the scheduling entity, a request from a user equipment (UE) for RS-info related to one or more reference signals (RS) targeted at a receiver different from the UE; and sending a message including the RS-info to the UE in response to the request from the UE.

[0016] Disclosed is an apparatus (e.g., a base station, a roadside unit, a UE, etc.) comprising components for sharing configuration information with a first entity. The apparatus includes components for transmitting reference signal information indicating a set of reference signals (RSs) transmitted between a plurality of entities (including between a second entity and a third entity). In some cases, the plurality of entities may include an apparatus (e.g., a base station transmitting RSs to a remote UE (e.g., a second UE, a sidelink UE, etc.)). The reference signal information may indicate the RS set using resource parameters (e.g., one or more subcarriers, one or more symbols, etc.). In some examples, the apparatus includes components for transmitting data decoding information (e.g., a first data decoding parameter set) indicating a first set of data decoding parameters corresponding to data transmitted between at least two entities. In an additional example, the apparatus includes components for receiving a request for additional configuration information from a requesting entity. In such a case, the apparatus may include additional components for transmitting the configuration information to the requesting entity. The requesting entity may then monitor signal transmissions (e.g., coded signal transmissions) transmitted between the at least two other entities to be received as reflected signals corresponding to line-of-sight data transmissions transmitted between the at least two other entities.

[0017] These and other aspects of the technology discussed herein will be more fully understood by reading the detailed description below. Other aspects, features, and embodiments will become apparent to those of ordinary skill in the art when reading the following description of certain examples in conjunction with the accompanying drawings. Although the following description may discuss various advantages and features relative to certain embodiments and drawings, all embodiments can include one or more of the advantageous features described herein. In other words, although this specification may discuss one or more examples as having certain advantageous features, one or more of such features may also be used according to one or more of the various techniques disclosed herein. In a similar manner, although this specification may discuss exemplary embodiments as device, system, or method embodiments, it will be understood that such exemplary embodiments can be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a schematic diagram of a wireless communication system in accordance with one or more of the various techniques of this disclosure.

[0019] Figure 2 is a conceptual diagram of an example of a radio access network (RAN) in accordance with one or more of the various techniques of this disclosure.

[0020] Figure 3 is a conceptual diagram of passive sensing using a single transmitter, in accordance with one or more of the various techniques of this disclosure, and a flowchart illustrating an example process for passive sensing.

[0021] Figure 4 is a conceptual diagram of an example environment for multi-node passive sensing involving multiple transmitters, and a flowchart illustrating an example process for multi-node passive sensing, in accordance with one or more of the various techniques of this disclosure.

[0022] Figure 5 is a conceptual diagram of an example environment for multi-node passive sensing involving multiple receivers, and a flowchart illustrating an example process for multi-node passive sensing, in accordance with one or more of the various techniques of this disclosure.

[0023] Figure 6 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with one or more of the various techniques of this disclosure.

[0024] Figure 7 is a diagram illustrating a resource allocation pattern indicated via reference signal information (RS-info) and / or data decoding information according to one or more of the various techniques of this disclosure.

[0025] Figure 8 is a diagram illustrating a resource allocation pattern indicated via reference signal information (RS-info) segmented in graphs in the frequency and time domains according to one or more of the various techniques of this disclosure.

[0026] Figure 9 is a schematic diagram of a resource allocation pattern indicated by data decoding information segmented in graphs in the frequency domain and the time domain according to one or more of the various techniques of the present disclosure.

[0027] Figure 10 is a schematic diagram of a segmented resource allocation pattern in graphs in the frequency domain, time domain, and spatial / coding domain according to one or more of the various techniques of this disclosure.

[0028] Figure 11 is a block diagram conceptually illustrating an example of a hardware implementation of an example scheduling entity according to various aspects of the present disclosure.

[0029] Figure 12is a block diagram conceptually illustrating an example of a hardware implementation of an example scheduled entity according to various aspects of the present disclosure.

[0030] Figure 13 is a flow diagram illustrating an example process for sharing transport configuration information between entities in accordance with one or more of the various techniques of this disclosure.

[0031] Figure 14 is a flow diagram illustrating an example process for sharing reference signal information (RS-info) among multiple entities in accordance with one or more of the various techniques of this disclosure.

[0032] Figure 15 is a flow diagram illustrating an example process for an entity to share RS-info corresponding to transmission of the entity's own one or more reference signals (RSs) to one or more other entities, in accordance with one or more of the various techniques of this disclosure.

[0033] Figure 16 is a flow diagram illustrating an example process for facilitating multi-node passive sensing using RS-info, in accordance with one or more of the various techniques of this disclosure.

[0034] Figure 17 is a flow diagram illustrating an example process for sharing data decoding information among multiple entities in accordance with one or more of the various techniques of this disclosure.

[0035] Figure 18 is a flow diagram illustrating an example process for entities to share data decoding information corresponding to their own signal transmissions, in accordance with one or more of the various techniques of this disclosure.

[0036] Figure 19 is a flow diagram illustrating an example process for facilitating multi-node passive sensing using data decoding information, in accordance with one or more of the various techniques of this disclosure. DETAILED DESCRIPTION

[0037] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration that can practice the concepts described herein. The detailed description includes specific details used to provide a thorough understanding of the various concepts. However, those skilled in the art will readily recognize that these concepts can be practiced without these specific details. In some cases, this specification provides well-known structures and components in block diagram form to avoid obscuring these concepts.

[0038] Although this specification describes various aspects and embodiments by the explanation of some examples, it will be understood by those skilled in the art that additional implementations and use cases can occur in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes and / or packaging arrangements. In an example, embodiments and / or uses can be implemented via integrated chip (IC) embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabling devices, etc.). Although some examples may or may not be specifically for use cases or applications, a variety of applicability of the innovation described can occur. Implementation methods can span the range from chip-level or modular components to non-modular, non-chip-level implementation methods, and further span the aggregation, distribution or original equipment manufacturer (OEM) equipment or system incorporating one or more aspects of the described innovation. In some actual settings, the equipment incorporating the various aspects and features described can also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. In an example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The disclosed technology is intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0039] The following disclosure presents various concepts that can be implemented in a wide variety of telecommunication systems, network architectures, and communication standards.

[0040] Figure 1 1 is a schematic diagram of a wireless communication system 100 in accordance with one or more of the various techniques of the present disclosure and is described as an illustrative example rather than a limitation. In some aspects, the wireless communication system 100 includes several interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. In some aspects, by means of the wireless communication system 100, the UE 106 can perform data communications with an external data network 110 (such as, but not limited to, the Internet).

[0041] In some aspects, the RAN 104 can implement any suitable wireless communication technology or combination of technologies to facilitate communication between the UE 106 and the scheduling entity 108 (e.g., by providing radio access to the UE 106). In one example, the RAN 104 can operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications (commonly referred to as 5G or 5G NR). In some examples, the RAN 104 can operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, which are sometimes referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized in conjunction with the subject matter disclosed herein without departing from the scope of this disclosure.

[0042] NR access can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequency (e.g., 24 GHz to 53 GHz or higher), massive machine type communication (mMTC) targeting non-backward compatible MTC technology, and / or mission-critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding QoS requirements. In addition, these services can coexist in the same subframe.

[0043] like Figure 1 106 , a base station (BS) 108 is a radio base station that is used to connect one or more UEs to the core network 102. In the example shown in FIG. 104 , the RAN 104 includes various base stations (BSs) 108. Broadly speaking, a base station (BS) can be used to implement a network element in a radio access network that is responsible for radio transmission and reception in one or more cells to or from a UE, such as UE 106. Various terms have been used to refer to a network element that acts as a base station in different technologies, standards, and / or contexts. For example, one skilled in the art can also use various terms to refer to a base station to refer to a network element that connects one or more UE devices to one or more parts of the core network 102, such as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology.

[0044] The RAN 104 supports wireless communications for multiple mobile devices. Those skilled in the art may refer to the mobile devices as user equipment (UE), as in the 3GPP specifications, but may also refer to UE as a mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other appropriate terminology. A UE may be a device that provides access to network services. A UE may take many forms and can include a range of devices.

[0045] Within this document, a "mobile" device (also referred to as a UE) does not necessarily need to have the ability to move, and can be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE can include a plurality of hardware structural components sized, shaped, and arranged to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide array of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)). Mobile devices can additionally be cars or other transportation vehicles, remote sensors or actuators, robots or robotic devices, satellite radios, global positioning system (GPS) devices, object tracking devices, drones, multicopters, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses), wearable cameras, virtual reality devices, smart watches, health and / or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home devices or smart home devices, such as home audio devices, home video devices, and / or home multimedia devices, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels and / or solar arrays, municipal infrastructure devices that control electricity (e.g., smart grids), municipal infrastructure devices that control lighting, municipal infrastructure devices that control water, etc.; industrial automation and enterprise devices; logistics controllers; agricultural equipment, military defense equipment, vehicles, aircraft, ships, weaponry, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, such as remote healthcare. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, whose communications can be given priority treatment or priority access relative to other types of information (e.g., in terms of priority access for transmission of critical service data, and / or associated quality of service (QoS) for transmission of critical service data).

[0046] The wireless communications between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. In accordance with one or more of the various techniques of this disclosure, the term "downlink" may refer to point-to-multipoint transmissions initiated at a scheduling entity (e.g., base station 108). For example, DL can be implemented using one or more broadcast channel multiplexing techniques. In some aspects, transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. In accordance with one or more of the various techniques of this disclosure, the term "uplink" may refer to point-to-point transmissions initiated at a scheduled entity (e.g., UE 106). As Figure 1 As shown in , the scheduling entity 108 may manage DL traffic 112 to one or more scheduled entities 106 and UL traffic 116 from one or more scheduled entities 106 .

[0047] In some aspects, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station of the RAN 104, such as the base station 108) allocates radio resources for communication among some or all devices and apparatuses within its service area or cell. Within the present disclosure, the scheduling entity 108 may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities 106. In such an example, for scheduled communications, the scheduled entity (e.g., the UE 106) may utilize resources allocated by the scheduling entity (e.g., the base station 108). In one example, the scheduled entity 106 may include an entity (e.g., a UE) scheduled for communication that is configured to utilize resources allocated by the scheduling entity 108.

[0048] It should be noted that a base station (BS) is not the only entity that can serve as a scheduling entity. That is, in some examples, a UE can serve as a scheduling entity. Thus, in some cases, a UE can be configured to schedule resources for one or more scheduled entities (e.g., one or more other UEs) in the wireless communication system 100.

[0049] like Figure 1, in some aspects, a scheduling entity (e.g., base station 108) can broadcast downlink (DL) traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, in some aspects, a scheduling entity (e.g., base station 108) can serve as a node or device responsible for scheduling traffic in a wireless communication network, including DL traffic 112, and in some examples, including UL traffic 116 from one or more scheduled entities (e.g., UE 106) to the scheduling entity (e.g., base station 108). Additionally, a scheduled entity (e.g., UE 106) can serve as a node or device that receives DL control information (DCI) 114, including but not limited to scheduling information (e.g., grants), synchronization or timing information, and / or other control information from another entity in the wireless communication network, such as the scheduling entity (e.g., base station 108).

[0050] Generally, a scheduling entity (e.g., one or more base stations 108) can include a backhaul interface for communicating with a backhaul 120 of wireless communication system 100. In some examples, backhaul 120 can provide a link between a particular base station and core network 102. Furthermore, in some examples, a backhaul network (e.g., including backhaul 120) can provide interconnection between various base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, and / or any other suitable connection using any suitable transport network.

[0051] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology (RAT) used in the RAN 104. In some examples, the core network 102 may be configured according to NR specifications (e.g., 5GC). In another example, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

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

[0053] In some examples, scheduled entities, such as the first scheduled entity 106 and the second scheduled entity 106a, can communicate using sidelink (SL) signals. The sidelink (SL) signals can include sidelink traffic 132 and sidelink control information (SCI) 134. In some aspects, the SCI 134 can include a request signal. For example, the SCI 134 can include a request to send (RTS), a source send signal (STS), a direction select signal (DSS), and / or any other suitable request signal. The request signal can provide a mechanism for a particular scheduled entity 106 to request that a sidelink (SL) channel remain available for SL signaling for a duration. In some aspects, the SCI 134 can include a response signal. For example, the SCI 134 can include a clear to send (CTS) signal, a destination receive signal (DRS), and / or any other suitable response signal. The response signal can provide a mechanism for a particular scheduled entity 106 to indicate the availability of the SL channel (e.g., for a requested duration). In some aspects, an exchange of request and response signals (eg, a handshake) can facilitate different scheduled entities performing sidelink (SL) communications, such as to negotiate availability of SL channels prior to communication of sidelink traffic 132 .

[0054] It should be noted that the techniques described herein can be used for various wireless networks and radio technologies, and while some aspects of the disclosure may be described using terminology typically associated with 3G, 4G, and / or New Radio (e.g., 5G NR) wireless technologies, as those skilled in the art will appreciate, various aspects of the disclosed techniques are capable of being applied to communication systems based on other generations.

[0055] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. Those skilled in the art may variously refer to RATs as radio technologies, air interfaces, etc. Those skilled in the art may further refer to frequencies as carriers, subcarriers, frequency channels, component carriers, tones, subbands, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

[0056] Figure 2 A diagram of a radio access network (RAN) 200 is provided by way of example and not limitation, in accordance with one or more of the various techniques of this disclosure. In some examples, the RAN 200 can be a combination of the above Figure 1 Describe and Figure 1100. The RAN 104 is shown in FIG. For example, the RAN 200 may be an NR system (e.g., a 5G NR network). The RAN 200 may communicate with the core network 102. The core network 102 may communicate with one or more BSs 210, 212, 214, 218, and / or 220, and / or UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 in the RAN 200 via one or more interfaces.

[0057] The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that a user equipment (UE) may uniquely identify based on, for example, an identity broadcast from an access point or base station (BS). Figure 2 Macro cells 202, 204, and 206, and small cell 208 are shown, each of which can include one or more sectors (not shown). For example, a sector can be defined as a sub-area of a cell, and all sectors within a cell can be served by the same BS. Radio links within a sector can be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within the cell can be formed by antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0058] Figure 2 Two base stations (BSs) 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base stations can have integrated antennas or can be connected to antennas or RRHs by feeder cables. In the example shown, cells 202, 204, and 206 can be referred to as macro cells because BSs 210, 212, and 214 support cells with relatively large sizes. In addition, base station 218 is shown in a small cell 208 (which can be referred to as, for example, a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.), which can overlap with one or more macro cells. Figure 2 In the example shown in , cell 208 can be referred to as a small cell because base station 218 supports cells having a relatively small size. In some aspects, cell sizing can be accomplished based on system design and component constraints.

[0059] RAN 200 may include any number of wireless BSs and cells. In addition, the RAN may include relay nodes to extend the size or coverage area of a given cell. BSs 210, 212, 214, 218, 220 provide wireless access points to core network 102 for any number of mobile devices. In some examples, BSs 210, 212, 214, 218, and / or 220 may include, for example, reference Figure 1 A specific implementation of the scheduling entity 108 is described.

[0060] In some examples, Figure 2 Also included is a quadcopter 220 (sometimes referred to as a drone) that can be configured to serve as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of the cell can move depending on the location of a mobile base station such as quadcopter 220.

[0061] Within the RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (e.g., as described above in connection with the preceding description) for all UEs in the corresponding cell. Figure 1 For example, UEs 222 and 224 can communicate with base station 210; UEs 226 and 228 can communicate with base station 212; UEs 230 and 232 can communicate with base station 214 through RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can be, for example, reference Figure 1 A specific implementation of the UE 106 is described.

[0062] In some examples, a mobile network node (eg, quadcopter 220 ) can be configured to function as a UE. In one example, quadcopter 220 can operate within cell 202 by communicating with base station 210 .

[0063] In some aspects, sidelink (SL) signals can be utilized between UEs without having to rely on scheduling or control information from a base station (BS). For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink (SL) signals without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is shown communicating with UEs 240 and 242. In such an example, UE 238 can serve as a scheduling entity or a primary sidelink (SL) device, and UEs 240 and / or 242 can serve as scheduled entities and / or non-primary (e.g., secondary) sidelink (SL) devices.

[0064] In some examples, the UE can be used as a scheduling entity in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-infrastructure (V2I) network, a vehicle-to-everything (V2X) network, and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity (e.g., UE 238), UEs 240 and 242 can optionally communicate directly with each other. Therefore, in a wireless communication system 100 having scheduled access to frequency-time domain (FD-TD) resources and having a cellular configuration, a peer-to-peer (P2P) configuration, a vehicle-to-everything (V2X) network, and / or a mesh configuration, the scheduling entity 108 and one or more scheduled entities 106 can communicate using the scheduled resources.

[0065] The air interface in the RAN 200 is capable of utilizing one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for uplink (UL) transmissions from UEs 222 and 224 to a base station (BS) 210, and provides multiplexing for downlink (DL) transmissions from the BS 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform-spread-orthogonal frequency division multiple access (OFDMA) (DFT-s-OFDMA) (also known as single carrier FDMA (SC-FDMA)) with CP. However, within the scope of the present disclosure, multiplexing and multiple access are not limited to such schemes. For example, the UE may utilize time division multiple access (TDMA), time division synchronous code division multiple access (TD-SCDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes to provide UL multiple access. In addition, the BS may utilize time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes to multiplex DL transmissions to the UE.

[0066] Example of passive sensing of objects in the environment

[0067] Figure 3 is a conceptual diagram 310 of passive sensing utilizing a single transmitter (which can sometimes be referred to as an “illuminator of opportunity” (100)) and a flow chart showing an example process 300 for passive sensing in accordance with one or more of the various techniques of this disclosure and is described as an illustrative example and not as a limitation. Figure 3 As shown, in passive sensing processes (e.g., passive radar, passive coherent positioning (PCL), etc.), the transmitter (e.g., base station (BS) 108) and receiver (e.g., user equipment (UE) 106) may be located at different physical locations, whereas in conventional monostatic sensing processes, the transmitter and receiver are co-located (e.g., a single device both transmits radar signals and receives these signals after reflection from an object). Figure 3 In the example shown, for simplicity, only a single object (e.g., object 312) is shown. However, many more obstacles may exist in the environment of the transmitter (e.g., illuminator) and receiver (e.g., observer), thereby creating multiple objects, such as object 312, that can be detected using one or more of the various passive radar techniques disclosed herein.

[0068] In some aspects, when the transmitter transmits a signal, both a line-of-sight (LoS) signal 314 and a signal that has been reflected (eg, backscattered) from the object 312 can be received at the receiver. Figure 3 As shown, the LoS signal 314 can take a straight-line path to a receiver (e.g., UE 106). In such an example, a reflected signal (e.g., a backscattered signal) corresponding to the LoS signal (e.g., transmitted from the same transmitter using the same or similar resources) can take a relatively longer path to the receiver compared to the straight-line path of the LoS signal 314. To illustrate, the longer path of the reflected signal 316 can include at least one first path 318 to the object 312 and at least one second path 320 back toward the receiver. It should be understood that additional corresponding portions of the LoS signal 314 can propagate outward away from the transmitter and / or may not reflect from any object or may be scattered from objects such as the object 312 in various other directions away from the receiver. This is because the LoS signal 314, while being transmitted as shown to be targeted to a particular receiver, can still exhibit a wave-like characteristic of radiating outward in various directions, including in an intended direction toward the intended receiver, such that in various examples the receiver receives the LoS signal and corresponding portions of the LoS signal. Figure 3 In the illustrated example, a single reflected signal 316 (separate from the LoS signal 314 ) is shown as reflected from the example object 312 for simplicity.

[0069] In some aspects, the receiver can correlate LoS signal 314 (as a reference signal) and reflected signal 316 (e.g., a backscattered signal or wave). The receiver (or another entity such as a central node or server) can determine a time delay (Δt) from the correlation maximum to determine a possible location of object 312 (e.g., potentially along the outer portion of various geometric configurations, such as along the perimeter of ellipse 322).

[0070] In an illustrative example, the receiver may determine the time delay between the arrival of two signals (e.g., a LoS signal and its corresponding reflected signal) to determine an ellipse describing the likely location of object 312 relative to the transmitter and receiver. In such an example, the transmitter and receiver may be conceptually placed or located at the foci of ellipse 322 (e.g., Figure 3 shown).

[0071] Object 312 can theoretically be located at various positions along ellipse 322. This is because, for example, if object 312 is on the opposite side of the ellipse, object 312 can still reflect reflected signal 316 back to the receiver with a similar time delay. Therefore, in short, the use of ellipse 322 can describe the possible positions 312 of object 312 rather than providing a precise spatial location for object 312. As described herein, additional data (e.g., additional ellipse information received from other observers) can be useful in determining the exact spatial location of object 312.

[0072] like Figure 3 As shown, according to one or more of the various techniques of this disclosure, a receiver (e.g., user equipment (UE) 106, base station (BS) 108, another device) can perform an example process 300 for passive sensing. In some aspects, process 300 can start at "A" and can proceed to block 302.

[0073] At block 302, a receiver can receive a line-of-sight (LoS) signal 314. Additionally, the receiver can receive a reflected signal 316 (e.g., a backscattered signal) that has been reflected from one or more objects 312. In such an example, there can be a time delay Δt between when the receiver receives the LoS signal 314 and when the receiver receives the reflected signal 316. In some aspects, the receiver can use any suitable technique or combination of techniques to receive the LoS signal 314 and the reflected signal 316 (e.g., a multipath reflected signal). For example, the receiver can sample and buffer the received wireless signal and apply appropriate processing, such as energy detection, demodulation, decoding, etc., to the buffered signal.

[0074] At block 304, the receiver can use line-of-sight (LoS) signal 314 as a reference and can calculate a correlation with reflected signal 316. Note that because LoS signal 314 has traveled in a straight line to the receiver, the receiver may receive LoS signal 314 before receiving any reflected signal(s) corresponding to LoS signal 314. The receiver may determine the correlation between LoS signal 314 and reflected signal 316 using any suitable technique or combination of techniques.

[0075] In an illustrative example, a receiver of a line-of-sight (LoS) signal and corresponding reflected signal(s) may convert the received LoS and reflected signals from the time domain (TD) to the frequency domain (FD) (e.g., using circuitry for performing a fast Fourier transform (FFT)). In such an example, the receiver may then apply a filtering (e.g., a matched filter) process to determine the correlation between the LoS signal 314 and the reflected signal(s) 316.

[0076] In an illustrative example, a receiver (or other entity, such as a central node) may generate a signal by conjugating the FD component of the LoS signal 314 to the The correlation between the LoS signal 314 and the reflected signal 316 delayed by time τ can then be determined by multiplying the FD component of the reflected signal 316 shifted by τ(S(f)). The correlation between the LoS signal 314 and the reflected signal 316 delayed by time τ can then be determined by applying an inverse FFT (IFFT) to the result of the multiplication using the relationship to determine the correlation between the LoS signal 314 and the reflected signal 316. In such an example, the FD signal can be filtered (e.g., using a rectangular window function) to reduce noise that falls outside the baseband of the received signal. This can be repeated at various time delays (e.g., corresponding to the detection range of passive radar sensing). A subsequent IFFT can be applied to the correlations from the time-delayed correlation sequence (e.g., for τ = [0, i], where 0 represents the time when the LoS signal was received) to generate a range profile across the delay τ.

[0077] At block 306, the receiver can determine the delay Δt between the line-of-sight (LoS) signal 314 and the reflected signal 316 based on the time delay that maximizes the correlation between the two signals. In some aspects, the delay Δt is determined in the image corresponding to multiple objects ( Figure 3There may be multiple maxima in the correlation (not shown). In some aspects, the receiver can determine the time delay Δt between the LoS signal 314 and the reflected signal 316 by finding the maximum (or multiple maxima) in the correlation data (note that there may be multiple reflected signals from different objects). Note that any particular range estimate may be affected by noise. In some aspects, the receiver can generate a Doppler matrix across the slow time axis. For example, each sample in the slow time can represent a range distribution generated based on the correlation between the LoS signal 314 and one or more reflected signals 316, where the LoS signal 314 is transmitted periodically (at regular or irregular intervals). This can be used to distinguish between moving objects (e.g., object 312) and the environment. In a specific example, the Doppler matrix can be generated using an FFT filter bank with "D" inputs corresponding to the number of LoS signal transmissions used to generate the Doppler matrix. In some aspects, the delay Δt can be determined by finding the maximum (or multiple maxima) in the Doppler matrix, which can correspond to the detected object (e.g., object 312).

[0078] At block 308, the receiver can determine an ellipse 322 corresponding to one or more possible positions of an object(s) (e.g., object 312) based on the delay Δt. In an example, the receiver can determine the ellipse 322 by tracking the possible positions of the object 312 relative to the transmitter and the receiver. In some aspects, the ellipse 322 can be determined by determining a path length corresponding to the delay Δt. In an example, the path length can be determined by dividing the speed of light by Δt.

[0079] In some examples, the receiver can use its own location and the known location of the transmitter to determine which locations in the environment around the receiver are located on the ellipse 322. For example, the receiver can conceptually use the locations of the transmitter and receiver as foci and find all points that are at least a certain distance (e.g., corresponding to the speed of light times Δt) from each transmitter (e.g., luminaire(s)) to draw the ellipse 322, whether these points include base stations 108, roadside units (RSUs), user equipment (UEs) 106, etc. In a more specific example, the receiver can determine an ellipse 322 with the transmitter and receiver as foci and having a height 2b and a width 2a, such that each location of the ellipse 322 is located at a distance from the transmitter and time t tran Corresponding distance and distance receiver vs. time t rec The corresponding distance, where t tran +t rec =t Los +Δt, which can be determined by the relationship In an illustrative and non-limiting example, a receiver can use the relationship To determine the width 2a, and to be able to use the relationship In some aspects, after determining ellipse 322 based on line of sight (LoS) signal 314 and one or more reflected signals 316, process 300 can proceed to "B" where it can end.

[0080] Example of a multi-node passive sensing environment

[0081] Figure 4 is a conceptual diagram of an example multi-node passive sensing environment 410 involving multiple transmitters (which can sometimes be referred to as “opportunistic luminaires”) in accordance with one or more of the various techniques of this disclosure. Figure 4 A flow chart illustrating an example process 400 for multi-node passive sensing in accordance with one or more of the various techniques of this disclosure is also provided. Figure 4 It is described as an illustrative example and not as a limitation. Figure 4 As shown, in a multi-node passive sensing environment 410, multiple transmitters (e.g., base station (BS) 412 in this illustrative example) and / or one or more receivers (e.g., user equipment (UE) 414 in this example) may be located at different physical locations. Figure 4 In the example shown, for simplicity, only a single object (e.g., object 418) is shown. However, there may be many more obstacles in the environment of the transmitter and / or receiver, thereby creating multiple objects that can be detected.

[0082] In some examples, in a multi-node passive sensing example involving multiple transmitters (e.g., multiple base stations (BSs) 108) and a receiver (e.g., UE 414 via a transceiver of UE 414) capable of receiving signals (e.g., downlink (DL) transmissions) from the multiple transmitters (e.g., from base station 412a, base station 412b, base station 412c, etc.), receiver 414 can determine the location of object 418 by generating multiple ellipses (e.g., ellipses 416a, 416b, and / or 416c, etc.). In some aspects, receiver 414 can determine that object 418 is located at the intersection of the multiple ellipses (e.g., ellipses 416a, 416b, and / or 416c, etc.). In this manner, receiver 414 can place object 418 at the intersection of the multiple ellipses (e.g., ellipses 416a, 416b, and / or 416c, etc.).

[0083] In some examples, in accordance with one or more of the various techniques of this disclosure, a receiver (e.g., a UE 106 such as UE 414, a BS 108, and / or another device such as a roadside unit (RSU), etc.) can perform the example process 400 for multi-node passive sensing.

[0084] At block 402, the receiver 414 can go to the upper Figure 3 "A" in the described process 300. There, in various examples, the receiver 414 can perform Figure 3 The process 300 starts at "A" and proceeds through the process 300 to "B".

[0085] At block 404, process 400 (performed via receiver 414) may be combined with Figure 3 The process 300 described in "B" returns. That is, as shown in FIG. Figure 3 As depicted in block 308 of FIG. 1 , according to one or more of the various techniques of this disclosure, the receiver may track one or more objects (e.g., Figure 3 At least one ellipse 322 is determined from the possible positions of the object 312 in the image relative to the transmitter and receiver. When returning from "B", the corresponding Figure 3 The transmitter ellipse 322 may then be related to the corresponding Figure 4 Any one of the ellipses 416a, 416b, 416c, etc. of any one of the transmitters 412a, 412b, 412b, etc.

[0086] At block 406, process 400 (performed by receiver 414) may return to block 402 until blocks 402 through 406 have been repeated N times, where “N” may correspond to the number of transmitters (e.g., transmitters 412a, 412b, 412c, etc.) used in the multi-node passive sensing process (e.g., three in this particular example, as just one example of N transmitters).

[0087] When blocks 402 through 406 have been repeated N times, process 400 can proceed to block 408. Note that in each iteration of blocks 402 through 406, if there are multiple objects that reflect (e.g., backscatter) the transmitted signal sufficiently strongly and / or in a direction toward a particular receiver 414, multiple ellipses (e.g., corresponding to Figure 3 The first ellipse of the first object 312 in the first ellipse corresponds to the second object ( Figure 3 a second ellipse (not shown), etc.).

[0088] At box 408, the receiver 414 (or another entity, such as a central server) can determine one or more intersection points where the ellipses (e.g., ellipse 566a, ellipse 566b, ellipse 566c, etc.) effectively intersect as candidate locations for object 418. The receiver 414 can then use the one or more intersection points to estimate the spatial location(s) of one or more objects (e.g., for object 418). In an illustrative and non-limiting example, the receiver 414 (or other entity) can aggregate and / or draw each ellipse (e.g., ellipse 566a, ellipse 566b, ellipse 566c, etc.) using Cartesian coordinates. The entity can then determine whether certain points along the various ellipses are within one or more predetermined intersection distances from other points along various other ellipses to meet an intersection threshold (e.g., by way of example only, within feet of each other). In such an example, the entity can determine whether the ellipses 566a-566c and Figure 4 4. In some examples, receiver 414 (or other entity) can use the cluster of elliptical intersections to estimate an object position (eg, the position of object 418).

[0089] In some examples, receiver 414 (or other entity) may generate and / or receive ellipse information defining a plurality of ellipses (e.g., ellipse 566a, ellipse 566b, ellipse 566c, etc.). The ellipse information may include certain geometric shape values or other ellipse coordinates for effectively tracking a given ellipse corresponding to the ellipse information, at least in part. In such an example, receiver 414 (or other entity) may then arrange a set of such ellipse values (e.g., Cartesian coordinates, etc.) into a matrix or other mathematical construct. Receiver 414 (or other entity) may then solve the system of equations to determine one or more candidate intersection points. Additionally or alternatively, receiver 414 (or other entity) may use a filter (such as an extended Kalman filter or an unscented Kalman filter) to determine one or more candidate intersection points.

[0090] Figure 5 is a conceptual illustration of an example multi-node passive sensing environment 510 in accordance with one or more of the various techniques of this disclosure. Figure 5 A flow chart illustrating an example process 500 for multi-node passive sensing in accordance with one or more of the various techniques of this disclosure is also provided. Figure 5 It is described by way of illustrative examples and not limitation.

[0091] In this illustrative example, a multi-node passive sensing environment 510 involves at least one transmitter 562 (e.g., a base station 108 in this particular example) and a plurality of receivers (e.g., user equipment (UE) 564A, UE 564B, UE 564C, etc.) capable of receiving signals (e.g., downlink (DL) transmissions) from the at least one transmitter 562. In such an example, entities such as the at least one transmitter 562, one or more receivers 564, and / or any other suitable entity (e.g., a data server, a roadside unit (RSU), etc.) may determine one or more objects (e.g., Figure 5 Similar to one or more techniques previously described, an entity may do so by generating and / or fusing multiple ellipses (e.g., ellipse 566a, ellipse 566b, ellipse 566c, etc.) to determine the spatial locations corresponding to various objects (e.g., Figure 5 In some examples, each receiver (e.g., UE 106, BS 108, another device) can perform at least a portion of process 500 for multi-node passive sensing.

[0092] At block 502, a receiver (e.g., UE 564a, UE 564b, UE 564c, etc.) can combine the above Figure 3 The process 300 described goes to "A". Here, the receiver can perform Figure 3 3. Process 300, starting at "A" and proceeding to "B." In one example, the first UE may determine at least one ellipse defining possible positions of one or more objects relative to a transmitter and a receiver according to one or more of the various techniques of this disclosure.

[0093] At block 504, process 500 may be combined with Figure 3 "B" in the described process 300 returns. That is, when Figure 3 When process 300 reaches "B", the process may continue with one or a combination of processes 400 and / or 500. For example, when returning from "B" while executing "A" to "B", the receiver may have determined an ellipse (e.g., Figure 3 322), any one of the ellipses 566a, 566b, 566c, etc. corresponds to Figure 5 Any one of receivers 564a, 564b, 564b, etc.

[0094] At block 506a, in some aspects, an entity performing at least a portion of process 500 can receive ellipse information defining the location (in the environment) and path of the ellipse (e.g., using the location of two focal points c, height 2b, and width 2a; using the location and directrix of one focal point, and / or any other information capable of conveying the shape of the ellipse). In some aspects, any suitable entity can receive the ellipse information. For example, a receiver performing at least a portion of process 500 (e.g., UE 106, BS 108, another device) can receive the ellipse information from M-1 other receivers. In a more specific example, the receiver can receive the ellipse information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots, sidelink (SL) time slots, and / or downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.). In another example, an entity other than the receiver performing blocks 502 and 504 (eg, UE 106 , BS 108 , another device) can receive ellipse information from the M receivers performing blocks 502 and 504 of process 500 .

[0095] Additionally or alternatively, in some aspects, at block 506 b, the receiver performing at least a portion of process 500 can send ellipse information (e.g., an ellipse information parameter set) to another entity (e.g., an entity performing block 506 a, such as a central node or server, etc.). For example, the receiver (e.g., UE 564 a, UE 564 b, UE 564 c, etc.) can send the ellipse information using one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots, sidelink (SL) time slots, and / or downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0096] Note that in some aspects, a single entity can perform block 506a. Alternatively, multiple entities can perform block 506a (e.g., multiple receivers performing blocks 502 and 504). In an example, a data server can receive ellipse information from one or more receivers 564 and / or from a transmitter 562 to aggregate the ellipse information at a central node. In such an example, the data server can receive such information from one or more entities performing some other functionality of processes 300, 400, and / or 500, for example.

[0097] At block 508, the entity (e.g., base station 108, central server, roadside unit (RSU), user device 106, etc.) that collected the multiple ellipses corresponding to at least M receivers (e.g., at block 506a, or at blocks 502 through 506b) can use any suitable technique or combination of techniques (e.g., the techniques described above in connection with block 408) to determine one or more points where the multiple ellipses intersect as candidate locations for object 568. Note that if there are multiple objects, the entity may have collected more ellipses than the number of receivers M. In some aspects, the receiver can use any suitable technique or combination of techniques to select the location(s) of one or more objects (e.g., object 568) at the points where the ellipses 566 intersect. In some aspects, the entity that determined the intersection point at block 508 can send information regarding the location of the one or more objects to the receiver that performed blocks 502 and 504 and / or to any other suitable device.

[0098] It should be understood that a device or system can employ process 400 and process 500 in conjunction with one another (e.g., with process 300) to improve the accuracy of object detection (e.g., the relative spatial location of an object). In one example, a central node (e.g., a data server, base station 108, a roadside unit (RSU), etc.) can fuse multiple ellipses together. When doing so, the central node can apply bias weights to various aspects of the ellipse information to account for the speed of the object (e.g., if one receiver is traveling faster than another receiver and / or relative to a common transmitter at that time), or distance may also be important to bias the ellipse information when fusing the ellipse information from multiple receiving devices into one ellipse to detect the precise spatial location of the object.

[0099] Example of multi-node passive sensing using a communication network

[0100] In some aspects, 5G signals (e.g., millimeter wave (mmW), etc.) can be used to perform multi-node passive sensing, which can have several benefits. For example, because the operation of various network entities (e.g., scheduled entity 106, scheduling entity 108, etc.) is via the radio access network (RAN) (e.g., reference Figure 1In some embodiments, the RAN 104 described herein may be used to coordinate the traffic flow of the UE, so that signal interference, data traffic congestion, and communication channel conflicts can be avoided at the network level. As another example, when used in a vehicle, some road users (e.g., vehicles, bicycles, pedestrians, etc.) may not be able to communicate using vehicle-to-everything (V2X) technology. In such an example, the UE may not necessarily be able to be aware of such road users using V2X technology, and therefore, one or more multi-node passive sensing technologies may be utilized to detect such road users instead. As yet another example, because many obstacles are transparent to certain 5G signals, the coverage provided via multi-node passive sensing using 5G signals can be greater (e.g., in range and angle) than that of a single-station radar system.

[0101] As yet another example, at least in the downlink (DL), radio nodes are synchronized and can adjust radio resources based on location needs (e.g., for detecting objects in a particular area). As another example, V2X can be used to provide a reference position, Doppler information, and / or velocity information for a receiver and / or transmitter, which can help improve the accuracy of position estimates.

[0102] As another further example, locally estimated parameters (e.g., position, velocity, ellipse, etc. of a detected object) can be efficiently exchanged with other UEs (e.g., via V2X communication, via enhanced mobile broadband (eMBB) communication, etc.).

[0103] As yet another example, a network operator can collect and provide dedicated information related to objects in the environment of the 5G infrastructure (e.g., via a V2X application). In a more specific example, the operator can charge the UE for access to such information. As another more specific example, the operator can provide access to such information to the UE at a discount (e.g., including free) in exchange for the UE providing estimated parameters and / or assisting in coordination. As yet another example, the estimated parameters can be collected by 5G infrastructure installed for other purposes (e.g., roadside units (RSUs), base stations (BSs), etc.).

[0104] Sharing transport configuration information between multiple entities

[0105] In some aspects, to perform frequency domain (FD) channel estimation, a receiver may obtain information (e.g., reference signal information (RS-info), data decoding information, etc.) that the receiver may then utilize to identify the signal it is receiving from a particular transmitter. For example, a receiver (e.g., a UE 106, a BS 108, etc.) may be able to use information (e.g., RS-info) about a reference signal (RS) transmitted by a transmitter to perform FD channel estimation.

[0106] As another example, the receiver can improve detection and FD channel estimation by decoding transport blocks (TBs). In a more specific example, the receiver can use cyclic redundancy check (CRC) corrections on the decoded data to refine the channel estimate. In such an example, the modulation symbols corresponding to the decoded (and CRC-corrected) data can be used to refine the estimated channel response (e.g., using techniques similar to those used to estimate the channel response based on RSs). Using multiple estimates based on the decoded data and RSs, the channel can be estimated more accurately, thereby improving the resolution of the position estimate based on the channel response.

[0107] In some aspects, a receiver (e.g., UE 106 in downlink (DL), BS 108 in uplink (UL), UE 106 in sidelink (SL), etc.) that has established an active communication session with a transmitter (e.g., BS 108 in DL, UE 106 in UL, second UE 106a in SL, etc.) can use information related to the active communication session to perform FD channel estimation. For example, if UE 106 uses a transmission from BS 108 or another transmitter intended for the UE, then UE 106 has the information necessary to perform FD channel estimation and decode the data in the transmission (e.g., if the signal is encoded with data).

[0108] However, if a receiver relies only on connections in which it is an active participant, it can limit the number of transmitters that the receiver can use in a multi-node passive sensing process, or require increased active communication between the receiver and other transmitters, resulting in increased interference and / or a reduced ability to perform normal communications.

[0109] In some aspects, a receiver can use signals sent for other receivers in a multi-node passive sensing process. However, a receiver typically does not have the information required to perform FD channel estimation using signals intended for other receivers (e.g., other UEs, base stations, RSUs, etc. that are separate from the receiver).

[0110] Figure 6 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with one or more of the various techniques of the present disclosure and is described as an illustrative example and not a limitation. It will be appreciated by those skilled in the art that various aspects of the present disclosure can be applied to discrete Fourier transform-spread-orthogonal frequency division multiple access (OFDMA) (DFT-s-OFDMA) waveforms in substantially the same manner as described below. That is, while some examples of the disclosed subject matter may focus on OFDM links for clarity, it will be appreciated that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0111] Within the present disclosure, a frame can refer to a duration of 10 milliseconds (ms) used for wireless transmission, where each frame includes 10 subframes, each subframe is 1 ms. On a given carrier, there can be one frame set in the uplink (UL) and another frame set in the downlink (DL). Now referring to Figure 6 , shows an expanded view of an exemplary DL subframe 602 showing an OFDM resource grid 604. However, as will be readily appreciated by those skilled in the art, the physical (PHY) transmission structure for any particular application can differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers or tones.

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

[0113] A user equipment (UE) typically utilizes only a subset of the resource grid 604. A resource block (RB) can be the smallest unit of resources that can be allocated to a UE (e.g., the scheduled entity 106, another scheduled entity 106a, etc.). Thus, as more resource blocks (RBs) are scheduled for a particular UE, the modulation scheme selected for the air interface increases, and the data rate that the UE can achieve also increases.

[0114] exist Figure 6 , RB 608 is shown as occupying less than the entire bandwidth of subframe 602, with some subcarriers shown above and below RB 608. In a given embodiment, subframe 602 can have a bandwidth corresponding to any number of one or more RBs 608. Figure 6 6. In FIG. 6, RB 608 is shown as occupying less than the entire duration of subframe 602, but this is merely one possible example.

[0115] Each 1 ms subframe 602 may include one or more adjacent time slots (e.g., a series of consecutive time slots). Figure 6 , as an illustrative example, a subframe 602 includes four time slots 610. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples can include mini-slots with shorter durations (e.g., one or two OFDM symbols). In some cases, such mini-slots can be sent occupying resources scheduled for ongoing time slot transmissions of the same or different UEs. In some cases, the scheduling entity 108 can send these mini-slots occupying resources scheduled for ongoing time slot transmissions of the same or different UEs (e.g., scheduled entity 106).

[0116] An expanded view of one of the time slots 610 shows that the time slot 610 includes a control region 612 and a data region 614. Generally, the control region 612 can carry control channels (e.g., a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a physical sidelink control channel (PSCCH), etc.), and the data region 614 can carry data channels (e.g., a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), a physical sidelink shared channel (PSSCH), etc.). Additionally or alternatively, a time slot can contain various combinations of downlink (DL), uplink (UL), and sidelink (SL), such as all DL, all UL, all SL, or at least one DL portion, at least one UL portion, and / or at least one SL portion, etc. Figure 6 The simple structure shown in is merely an example, and different slot structures can be utilized and can include one or more control regions and data regions each in any number of various examples.

[0117] In some examples, a scheduling entity 108 (e.g., a base station (BS), a user equipment (UE), etc.) can schedule various resource elements (REs) 606 within a resource block (RB) 608 to carry one or more physical channels, including a control channel, a data channel (e.g., a shared channel), etc. Other REs 606 within the RB 608 can also carry reference signals (RSs) (e.g., pilot signals, etc.). These reference signals (RSs) can facilitate a receiving device (e.g., a receiver / UE) in performing channel estimation of the corresponding channels, which can enable coherent demodulation / detection of the control and / or data channels within the RB 608. For example, the reference signals (RSs) can be used to convey information that a receiving device (e.g., a UE 106, a second scheduled entity 106a, a base station 108, a roadside unit (RSU), etc.) can use as a reference for transmitting or receiving information intended for the receiving device.

[0118] In some examples, a transmitter (e.g., base station 108) can transmit a demodulation reference signal (DMRS) for use by a particular UE (or other receiver) in channel characterization (e.g., for estimating the channel on which the DMRS is transmitted). As another example, a transmitter (e.g., base station 108, etc.) can transmit a phase tracking reference signal (PTRS) for use by a particular receiver (e.g., on a particular channel associated with the transmitter and / or receiver) to track the phase of a local oscillator in the transmitter. As yet another example, a transmitter (e.g., UE 106) can transmit a sounding reference signal (SRS) for use by a receiver (e.g., base station 108) in channel characterization (e.g., for estimating the uplink (UL) channel on which the SRS is transmitted). As yet another example, a transmitter (e.g., base station 108, etc.) can transmit a channel state information reference signal (CSI-RS) for use by a particular receiver (e.g., UE 106) in channel characterization (e.g., for estimating the downlink (DL) channel on which the CSI-RS is transmitted).

[0119] In a downlink (DL) transmission, a transmitting device (e.g., base station 108) may allocate one or more resource elements (REs) 06 (e.g., within a control region 612) to carry DL control information (DCI), e.g., via one or more DL control channels (e.g., as described above in conjunction with Figure 1114). In one example, a DL control channel may include DCI 114, which generally carries information originating from higher layers (such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc.) to one or more scheduled entities (e.g., a specific UE 106). In one example, the PDCCH may carry DCI 114 for one or more UEs in a cell. This may include, but is not limited to, power control commands, scheduling information, grants, and / or RE allocations for downlink (DL) and / or uplink (UL) transmissions.

[0120] In addition, the scheduling entity 108 may allocate a portion of the resources of a time slot (e.g., one or more downlink (DL) resource elements (REs)) to carry DL physical signals that generally do not carry information originating from higher layers. These DL physical signals may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a demodulation reference signal (DMRS), a phase tracking reference signal (PT-RS), a channel state information (CSI) reference signal (CSI-RS), etc. In such an example, DL resources may be allocated to carry such DL physical signals (e.g., DMRS, etc.).

[0121] The scheduling entity 108 may send synchronization signals, and in some examples, PBCH, in a sync signal block comprising four consecutive OFDM symbols numbered in ascending order from 0 to 3 via a time index. In the frequency domain (FD), the sync signal block may be spread over 240 consecutive subcarriers, where the subcarriers are numbered in ascending order from 0 to 239 via a frequency index. It should be noted that although the present disclosure may sometimes refer to one or more specific synchronization signal block configurations as illustrative examples, the present disclosure is not limited thereto. One of ordinary skill in the art will understand that other example configurations may also apply according to one or more of the various techniques disclosed herein. For illustration, additional or alternative examples may utilize more or less than two synchronization signals, may include one or more supplemental channels in addition to the PBCH, may omit the PBCH, and / or may utilize non-contiguous symbols for this type of block, to name a few examples.

[0122] In an uplink (UL) transmission, a transmitting device (e.g., UE 106) can utilize one or more REs 606 to carry UL control information (UCI) (e.g., Figure 118). In one example, a transmitting device may utilize one or more REs to carry one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc., to a scheduling entity (e.g., a base station 108). In addition, the UL REs may carry UL physical signals, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc., that typically do not carry information originating from higher layers. In some examples, the control information (e.g., uplink control information (UCI) 118) may include a scheduling request (SR) (e.g., a request for the scheduling entity 108 to schedule an UL transmission). In such an example, the scheduling entity 108 (e.g., the base station 108) may transmit downlink control information (e.g., DCI 114) that may schedule resources for UL packet transmission in response to receiving the SR sent on the control channel (e.g., on which the UCI 118 is transmitted).

[0123] In some examples, the control information (e.g., UCI, DCI, SCI) can also include hybrid automatic repeat request (HARQ) feedback such as an acknowledgment (ACK) or a negative acknowledgment (NACK), channel state information (CSI), and / or any other appropriate control information. HARQ is a technology well known to those skilled in the art. In such an example, the receiving device can check the integrity of the packet transmission on its receiving side to obtain accuracy, for example, using any suitable integrity check mechanism (such as a checksum or a cyclic redundancy check (CRC)). If the receiving device (e.g., UE 106) confirms the integrity of the transmission, it can send an ACK to the transmitting device (e.g., scheduling entity 108). If the integrity of the transmission is not confirmed, the receiving device can send a NACK to the transmitting device. In response to the NACK, the transmitting device can send a HARQ retransmission, which can implement catch-up combining, incremental redundancy, etc.

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

[0125] refer to Figure 1 or Figure 6The channels or carriers described are not necessarily all channels or carriers that can be utilized between a scheduling entity (e.g., base station 108) and a scheduled entity (e.g., UE 106). One of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be used in addition to those shown.

[0126] In some examples, the physical (PHY) layer may typically multiplex and map these physical channels onto transport channels for processing at a medium access control (MAC) layer entity. The transport channels carry blocks of information called transport blocks (TBs). The size of the transport block size (which may correspond to the number of bits of information) may be a controlled parameter based on a modulation and coding scheme (MCS) and / or the number of resource blocks (RBs) in a given transmission.

[0127] In some examples, different portions of the OFDM resource grid can be allocated to different scheduled entities 106 (e.g., a first user equipment (UE), a second UE, a third UE, etc.). In some examples, a transmitting entity (e.g., a scheduling entity 108) can target multiple scheduled entities 106 to receive various downlink (DL) transmissions. In such examples, the transmitting entity can send one or more DL signals to one or more corresponding scheduled entities 106 that are scheduled to receive the DL signal(s). That is, the scheduling entity 108 can schedule a first DL transmission for a first scheduled entity 106 and can schedule a second DL transmission for a second scheduled entity 106a. In such an example, the first scheduled entity 106 can receive a first line of sight (LoS) signal corresponding to the first DL transmission, and the second scheduled entity 106 can receive a second line of sight (LoS) signal corresponding to the second DL transmission. In such examples, the LoS signal can correspond to one or more reflected signals that extend outward from the scheduling entity 108 to subsequently reflect from one or more objects, which in some examples can deflect the signal back toward the first scheduled entity 106 and / or the second scheduled entity 106.

[0128] In some examples, the transmitting entity (e.g., or another entity) may jointly process those DL transmission signals that are targeted at different scheduled entities 106. In such an example, when these DL transmission signals are reflected from one or more objects, they may have the same multipath propagation. In this way, the transmitting entity may cover a relatively large portion of the resource grid in frequency. This is because for each object, different signals will have the same multipath propagation. When calculating the ellipse corresponding to the object (e.g., as described herein, e.g., with reference to Figure 3-5 ), which can improve accuracy.

[0129] In uplink (UL) and / or sidelink (SL) transmissions, the receiver may separately process different portions of the resource grid corresponding to different scheduled entities 106 (e.g., UEs) (and / or other transmitters that are not scheduling entities). This is because the different transmitters for UL and / or SL transmissions are not co-located. This results in different multipath propagation from each transmitter. This can degrade performance due to the sparse occupancy of each signal in the frequency-time domain (FD-TD) plane.

[0130] Frequency and / or time domain segmentation

[0131] Figure 7 FIG7 is a diagram 700 of a segmented resource allocation pattern in a graph of the frequency domain (FD) and the time domain (TD) according to one or more of the various techniques of the present disclosure and is described as an illustrative example and not as a limitation. The resource allocation pattern may correspond to a resource allocation pattern obtained via a reference signal information (RS-info) parameter set (e.g., as referenced by Figure 8 ) and / or via a data decoding information parameter set (e.g., as further described in Figure 9 further described) indicated information.

[0132] In some examples, reference signal information (RS-info) can include, among other things, an indication of a resource pattern in the time domain (TD) and / or frequency domain (FD) that a particular transmitter desires (e.g., has been assigned) to use for transmitting one or more reference signals (RS). Figure 8 and / or reference Figure 10 and Figures 13 to 16 As described, RS-info (e.g., RS configuration information, resource parameter set) can more generally include any suitable information that a device (e.g., user equipment (UE), base station (BS), roadside unit (RSU), etc.) can use to detect a reference signal that is sent between two other devices for purposes other than passive radar sensing. In some aspects, a resource pattern can correspond to a resource set for a receiver to monitor one or more RSs. For example, each resource set can include one or more FD attributes and / or one or more TD attributes that a receiver potentially monitors. In some aspects, each pattern can correspond to a resource set.

[0133] In addition (and as reference Figure 10(further described), the data decoding information can indicate a resource pattern in the time domain (TD) and / or frequency domain (FD) that a particular transmitter expects (e.g., has been assigned) to use to send data that can be used in a multi-node passive sensing process. In some aspects, the resource pattern can correspond to a resource set for a receiver to monitor a coded signal set (e.g., one or more coded data items sent via the coded signal). For example, each resource set can include one or more FD attributes and / or one or more TD attributes that the receiver potentially monitors. In some aspects, each pattern can correspond to a resource set. In an illustrative example, the data decoding information can include information that can identify any suitable DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, or DCI format 1_1) that can be used to send coded data. As another additional example, the data decoding information can include information indicating an SCI format that can be used to send coded data. As another example, the data decoding information can include information indicating information in a DCI format that can be used to send coded data using a physical sidelink shared channel (PSSCH). As another additional example, the data decoding information can include a frequency domain resource allocation (FDRA). As another additional example, the data decoding information can include time domain resource allocation (TDRA).

[0134] Example of Reference Signal Mode

[0135] Figure 8 FIG800 is a diagram illustrating a segmented resource allocation pattern in a graph of the frequency domain (FD) and the time domain (TD) according to one or more of the various techniques of the present disclosure and is described as an illustrative example without limitation. The resource allocation pattern may correspond to information indicated via a reference signal information (RS-info) parameter set.

[0136] In some examples, the reference signal information (RS-info) can include an indication of a resource pattern in the time domain (TD) and / or frequency domain (FD) that a particular transmitter desires (e.g., has been assigned) to use for transmitting one or more reference signals (RS). Figure 7 And the following references Figure 9 and Figures 12 to 14Said RS-info can more generally include any suitable information that a device (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can use to detect a reference signal that is sent between two other devices for purposes other than passive radar sensing. In some aspects, a resource pattern can correspond to a resource set for a receiver to monitor one or more RSs. For example, each resource set can include one or more FD attributes and / or one or more TD attributes that a receiver potentially monitors. In some aspects, each pattern can correspond to a resource set.

[0137] In some examples, reference signal information (RS-info) can include information about a portion of frequency domain (FD) resources that a transmitter desires to use. In an example, RS-info corresponding to a transmitter can include an indication of a set of one or more physical resource blocks (PRBs) within a particular bandwidth part (BWP). In such an example, the BWP may or may not be an active BWP used by a receiver (e.g., by a UE during downlink (DL) transmissions). In a specific example, the BWP specified by the transmitter can be in an inactive BWP of the receiver.

[0138] As another example, RS-info corresponding to a transmitter can include an indication of a BWP or multiple bandwidth parts (BWPs) that the transmitter desires to use for transmitting RS. In such an example, one or more BWPs may or may not correspond to an active BWP used by a receiver (e.g., by a UE during downlink (DL)). In a specific example, at least a portion of the BWP specified by the transmitter can be in an inactive BWP of the receiver.

[0139] As another example, RS-info corresponding to a transmitter can include an indication of a component carrier (CC) or multiple component carriers (CCs) that the transmitter desires to use for transmitting a reference signal (RS). In such an example, one or more CCs may or may not correspond to active CCs used by a receiver (e.g., by a UE during downlink (DL)). In a specific example, at least one of the CCs specified by the transmitter can be a CC not used by the receiver.

[0140] As another example, the RS-info corresponding to the transmitter can include an indication of a radio access technology (RAT) or multiple RATs that the transmitter desires to use to transmit the RS. In such an example, at least one RAT corresponding to the transmitter may not correspond to a RAT used by the receiver (e.g., by the UE during downlink (DL)).

[0141] In some aspects, RS-info can include information about a portion of the TD resources that the transmitter expects to use. For example, the RS-info corresponding to the transmitter can include one or more symbols (e.g., OFDM symbols) that the transmitter expects to use to send RS. As another example, the RS-info corresponding to the transmitter can include one or more time slots (e.g., OFDM time slots) that the transmitter expects to use to send RS. As another example, the RS-info corresponding to the transmitter can include one or more subframes (e.g., OFDM subframes) that the transmitter expects to use to send RS. As another example, the RS-info corresponding to the transmitter can include one or more frames (e.g., OFDM frames) that the transmitter expects to use to send RS. As another example, the RS-info corresponding to the transmitter can include one or more time domain units that the transmitter expects to use to send RS.

[0142] In some aspects, reference signal information (RS-info) can indicate multiple frequency-time domain (FD-TD) blocks corresponding to different combinations of frequency domain (FD) and time domain (TD) resources (e.g., Figure 8 ). For example, in different FD-TD blocks provided by a transmitter (e.g., a UE, an RSU, etc.), the same or different RS patterns can be identified (e.g., different blocks can correspond to the same resource pattern or different resource patterns). In a specific example, the transmitter can specify a first FD-TD block for a first type of RS (e.g., a demodulation reference signal (DMRS) for demodulating a physical downlink shared channel (PDSCH)). In some examples, the first FD-TD block (for the first type of RS) and the second FD-TD block (for the second type of RS (e.g., a positioning reference signal (PRS), etc.)) can be different from each other.

[0143] In some examples, a first receiver (e.g., a first user equipment (UE) 106) can utilize any suitable information to identify a frequency-time domain (FD-TD) block corresponding to one or more signals (e.g., reference signals (RS)) transmitted from a first transmitter (e.g., a base station (BS) 108, a UE 106) to a second receiver (e.g., a second UE 106a, a second BS 108, etc.). In an example, the first receiver can receive reference signal information (RS-info) corresponding to one or more signals (e.g., at least one demodulation reference signal (DMRS), etc.) transmitted between the first transmitter and the second receiver from the first transmitter and / or the second receiver. In an illustrative and non-limiting example, the first receiver (e.g., the first UE 106) can utilize reference signal information (RS-info) of the FD-TD block corresponding to one or more signals (e.g., at least one DMRS) transmitted between the first transmitter and the second receiver. In such an example, the first receiver can utilize the FD-TD block to monitor the one or more signals (e.g., at least one DMRS) corresponding to the RS-info. In this way, the first receiver can use RS-info to monitor and / or identify one or more signals (e.g., at least one DMRS) transmitted between the first transmitter and the second receiver. In such an example, according to one or more of the various techniques of this disclosure, the first receiver can use RS-info to identify and / or use one or more signals (e.g., at least one DMRS) corresponding to the first transmitter.

[0144] In some examples, the reference signal information (RS-info) shared by the transmitter can include a UE-specific ID (e.g., a DMRS scrambling ID) required to identify a demodulation reference signal (DMRS)-sequence. As another example, the RS-info shared by the transmitter can include one or more OFDM symbol indices of a DMRS symbol (or multiple). As yet another example, the RS-info shared by the transmitter can include a comb type (e.g., comb-2, comb-4) corresponding to one or more RSs. As yet another example, the RS-info shared by the transmitter can include one DMRS port ID or multiple DMRS port IDs. As yet another example, the RS-info shared by the transmitter can include a code division multiplexing (CDM) group ID corresponding to the transmitter. As yet another example, the RS-info shared by the transmitter can include an energy per resource element (EPRE) ratio with data symbols. As yet another example, the RS-info shared by the transmitter can include quasi-co-location (QCL) information. In some aspects, such information can correspond to one or more resource parameters corresponding to resources for the UE to monitor one or more reference signals (RS).

[0145] Example of data decoding mode

[0146] Figure 9 Schematic diagram 900 of a resource allocation pattern for segmented coded data in a graph of a frequency domain (FD) and a time domain (TD) according to one or more of the various techniques of the present disclosure, and is described as an illustrative example without limitation thereto. In some aspects, data decoding information can indicate a resource pattern in the time domain (TD) and / or frequency domain (FD) that a particular transmitter desires (e.g., has been assigned) to use to send coded data that can be used in a multi-node passive sensing process. In some aspects, a resource pattern can correspond to a resource set for a receiver to monitor one or more coded signals. For example, each resource set can include one or more FD attributes and / or one or more TD attributes that a receiver potentially monitors. In some aspects, each pattern can correspond to a resource set.

[0147] In some examples, the data decoding information can include information about a portion of the FD resources that the transmitter desires to use. For example, the data decoding information corresponding to the transmitter can include an indication of a set of one or more physical resource blocks (PRBs) within a particular bandwidth part (BWP). In such an example, the BWP may or may not be an active BWP used by the receiver (e.g., by the UE during downlink (DL)). In a specific example, the BWP specified by the transmitter in the data decoding information can be in an inactive BWP of the receiver.

[0148] As another example, data decoding information corresponding to a transmitter can include an indication of a BWP or multiple bandwidth portions (BWPs) that the transmitter intends to use to transmit the encoded data. In such an example, the one or more BWPs may or may not correspond to an active BWP used by a receiver (e.g., by a UE during a downlink (DL)). In a specific example, at least a portion of the BWP specified by the transmitter can be in an inactive BWP of the receiver.

[0149] As another example, the data decoding information corresponding to the transmitter can include an indication of a component carrier (CC) or multiple component carriers (CCs) that the transmitter intends to use to transmit the encoded data. In such an example, one or more CCs may or may not correspond to active CCs used by the receiver (e.g., by the UE during downlink (DL)). In a specific example, at least one of the CCs specified by the transmitter can be a CC not used by the receiver.

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

[0151] In some aspects, the data decoding information can include information about a portion of the time domain (TD) resources that the transmitter expects to use. For example, the data decoding information corresponding to the transmitter can include information identifying one or more symbols (e.g., OFDM symbols) that the transmitter expects to use to send coded data (e.g., coded data that can be used in a multi-node sensing process). As another example, the data decoding information corresponding to the transmitter can include information identifying one or more time slots (e.g., OFDM time slots) that the transmitter expects to use to send coded data. As yet another example, the data decoding information corresponding to the transmitter can include information identifying one or more subframes (e.g., OFDM subframes) that the transmitter expects to use to send coded data. As yet another example, the data decoding information corresponding to the transmitter can include information identifying one or more frames (e.g., OFDM frames) that the transmitter expects to use to send coded data. As yet another example, the data decoding information corresponding to the transmitter can include information identifying one or more time domain units that the transmitter expects to use to send coded data.

[0152] In some aspects, the data decoding information can indicate multiple frequency-time domain (FD-TD) blocks corresponding to different combinations of frequency domain (FD) and time domain (TD) resources (e.g., Figure 9 ). For example, in the data decoding information provided by a transmitter (e.g., a UE, a roadside unit (RSU), etc.), the same or different resource patterns can be identified within different FD-TD blocks (e.g., different blocks can correspond to the same resource pattern or different resource patterns). In a specific example, the transmitter can specify a first FD-TD block for data transmitted from and / or for a specific UE, and the first FD-TD block can be different from FD-TD blocks for data transmitted from and / or for different UEs.

[0153] In some aspects, any suitable information can be used to identify the FD-TD block, such as information that can be used to decode the coded data sent by the transmitter. For example, the data decoding information shared by the transmitter can include a radio network temporary identifier (RNTI) corresponding to the transmitter. As another example, the data decoding information shared by the transmitter can include a scrambling ID corresponding to the transmitter. As yet another example, the data decoding information shared by the transmitter can include rate matching information corresponding to the transmitter. As yet another example, the data decoding information shared by the transmitter can include a UE-specific ID (e.g., a DMRS scrambling ID) required to identify a demodulation reference signal (DMRS) sequence. As yet another further example, the data decoding information shared by the transmitter can include one or more OFDM symbol indices of a DMRS symbol(s). As yet another example, the data decoding information shared by the transmitter can include a comb type (e.g., comb-2, comb-4) corresponding to one or more coded signals. As yet another further example, the data decoding information shared by the transmitter can include one or more DMRS port identifiers (ID). As an additional example, the data decoding information shared by the transmitters can include a code division multiplexing (CDM)-group ID corresponding to the transmitter. As another additional example, the data decoding information shared by the transmitters can include an energy per resource element (EPRE) ratio of data symbols. As yet another additional example, the data decoding information shared by the transmitters can include quasi-co-location (QCL) information. In some aspects, such information can correspond to one or more resource parameters corresponding to resources for the UE to monitor one or more coded signals.

[0154] As yet another additional example, the data decoding information can include information that can identify any suitable DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, or DCI format 1_1) that can be used to send coded data. As another additional example, the data decoding information can include information indicating an SCI format that can be used to send coded data. As another example, the data decoding information can include information indicating information in a DCI format that can be used to send coded data using the PSSCH. As another further additional example, the data decoding information can include frequency domain resource allocation (FDRA). As another further additional example, the data decoding information can include time domain resource allocation (TDRA).

[0155] Example of Overlapping Resource Pattern

[0156] Figure 10Schematic diagram 1000 of a segmented resource allocation pattern (e.g., reference signal information (RS-info) pattern, data decoding pattern, etc.) in a graph in the frequency domain, time domain, and space / coding domain according to one or more of the various techniques of the present disclosure, and is described as an illustrative example and not limited thereto.

[0157] In some examples, multiple reference signal (RS) resources and / or multiple data decoding resources can overlap in the frequency-time domain (FD-TD) plane and can be multiplexed via spatial and / or code multiplexing. Figure 10 As shown, multiple RS resources and / or multiple data decoding resources can be fully overlapped in the FD-TD plane and / or partially overlapped in the FD-TD plane. In an illustrative example, pattern #3 can correspond to a reference signal (RS) pattern (or data decoding pattern) that partially overlaps in the FD-TD plane, such as toward Figure 10 In another example, mode #2 may correspond to a fully overlapped RS mode (or data decoding mode) in the FD-TD plane, such as toward Figure 10 shown on the right-hand side.

[0158] In some examples, overlapping FD-TD resources can be distinguished from each other based on information related to a demodulation reference signal (DMRS). In an example, overlapping FD-TD resources can be distinguished from each other based on information related to RS-info for demodulating a signal corresponding to a resource corresponding to a pattern. For example, different overlapping FD-TD patterns can be distinguished by using different DMRS port identifiers (IDs). As another example, different overlapping FD-TD patterns can be distinguished by using different DMRS scrambling IDs. In some aspects, RS-info and / or data decoding information can include information related to one or more port IDs and / or one or more scrambling IDs used for UE monitoring RS and / or coded data (e.g., used in passive sensing).

[0159] Scheduling Entity

[0160] Figure 11 is a block diagram conceptually illustrating an example of a hardware implementation of an example scheduling entity 1100 according to various aspects of the present disclosure and is described as an illustrative example rather than a limitation. In some examples, the scheduling entity 1100 may represent a user equipment (UE) (such as, for example, a reference Figure 1 In another example, the scheduling entity 1100 may represent an example of a base station (BS), such as, for example, a UE as described in any one or more of the preceding claims. Figure 1 and / or any of those base stations described in 2.

[0161] In some aspects, the scheduling entity 1100 can be implemented using a processing system 1114 that includes one or more processors 1104. Examples of processors 1104 include a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a graphics processing unit (GPU), a state machine, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, the scheduling entity 1100 can be configured to perform any one or more of the functions described herein. In some examples, the processing system 1114 can utilize one or more processors 1104 to implement the reference Figures 3 to 5 and / or Figures 13 to 19 Any one or more of the processes and procedures described in any one or more of .

[0162] In this example, processing system 1114 can be implemented using a bus architecture generally represented by bus 1102. Depending on the specific application and overall design constraints of processing system 1114, bus 1102 can include any number of interconnecting buses and bridges. Bus 1102 can communicatively couple various circuits including one or more processors (generally represented by processor 1104), memory 1105, and computer-readable media (generally represented by computer-readable media 1106). Bus 1102 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1108 can provide an interface between bus 1102 and transceiver 1100. In some examples, transceiver 1110 can provide a communication interface or device for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1112 (e.g., a keyboard, display, speaker, microphone, joystick) can also be provided. Of course, in some examples, such a user interface 1112 can be omitted, such as a base station.

[0163] According to one or more of the various techniques of this disclosure, processor 1104 can include a reference signal information (RS-info) sharing circuit 1140 that is configured for various functions, including, for example, collecting and / or sharing RS-info received from one or more transmitters. In some examples, RS-info sharing circuit 1140 can be configured to implement the following in conjunction with Figure 14 and 15 One or more functions described, such as those described in connection with 1402 , 1404 , and / or 1406 , and / or in connection with 1502 and / or 1504 .

[0164] According to one or more of the various techniques of this disclosure, the processor 1104 can include a data decoding information sharing circuit 1142 configured for various functions, including, for example, collecting and / or sharing data decoding information received from one or more transmitters. The data decoding information can include a device (e.g., a scheduling device 1100 or as described below in conjunction with Figure 12 Any suitable information that may be used by a scheduled device (as described above) to decode at least a portion of an encoded signal sent by another device for purposes other than passive radar sensing. For example, such an encoded signal can include information (e.g., encrypted packets) intended for a remote endpoint (e.g., a server, a remote UE, etc.). As another example, such an encoded signal can include information intended for receipt by a local scheduling entity or a scheduled entity for the purpose of scheduling communications on the RAN (e.g., as described above in conjunction with Figure 6 described). This article refers to, for example, Figures 17 to 19 Examples of information that can be included in the data decoding information and examples of techniques that can be used to provide the data decoding information are described. In some examples, the data decoding information sharing circuitry 1042 can be configured to implement the following in conjunction with Figure 17 and 18 One or more functions described, such as those described in connection with block 1702 , block 1704 , and / or block 1706 , and / or in connection with block 1802 and / or block 1804 .

[0165] Additionally, in some aspects, the processor 1104 can include a reference signal (RS) monitoring circuit 1144 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid, which is indicated via an RS-info parameter set) for reference signals (RS) transmitted by one or more transmitters (e.g., one or more UEs and / or BSs) for use in multi-node passive sensing. For example, the RS monitoring circuit 1144 can be configured to implement the following in conjunction with Figure 16 One or more functions described herein, such as the functions described in conjunction with block 1604 and / or block 1606. In an example, the RS monitoring circuit 1144 may utilize RS-info (e.g., an RS-info parameter set) to determine a resource set to use when monitoring a reference signal (RS) set. In such an example, the RS monitoring circuit 1144 may monitor the RS set associated with the FD-TD resource grid based on RS-info received from at least one of the one or more transmitters, or in some cases, monitor the RS set associated with the FD-TD resource grid based on RS-info received from another entity other than the one or more transmitters.

[0166] Additionally, in some aspects, the processor 1104 can include a coded data monitoring circuit 1146 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for coded signals transmitted by one or more transmitters for multi-node passive sensing. In some examples, the coded data monitoring circuit 1146 can be configured to implement the following in conjunction with Figure 19 One or more functions described, such as the functions described in conjunction with block 1904 and / or block 1906.

[0167] In some examples, the processor 1104 can manage the bus 1102 and can perform general processing, including executing software stored on the computer-readable medium 1106, which, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described herein for any particular apparatus (e.g., with reference to FIG. Figures 13 to 19 In some aspects, the computer-readable medium 1106 and memory 1105 can also be used to store data that is manipulated by the processor 1104 when executing software.

[0168] One or more processors 1104 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software can reside on a computer-readable medium 1106. The computer-readable medium 1106 can be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disk, floppy disk, magnetic stripe), optical disks (e.g., compact disk (CD) or digital versatile disk (DVD)), smart cards, flash memory devices (e.g., card, stick, or key drive), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1106 can reside in processing system 1114, external to processing system 1114, or distributed across multiple entities including processing system 1114. Computer-readable medium 1106 can be embodied in a computer program product. For example, a computer program product can include a computer-readable medium in packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the entire system.

[0169] In one or more examples, the computer-readable storage medium 1106 can include reference signal information (RS-info) sharing software 1152 configured for various functions, including, for example, collecting and / or sharing RS-info (e.g., resource parameter sets, etc.) received from one or more transmitters. For example, the RS-info sharing software 1152 can be configured to implement the following in conjunction with Figure 14 and 15 One or more functions described, such as those described in conjunction with 1402 , 1404 , and / or 1406 and / or in conjunction with 1502 and / or 1504 .

[0170] In one or more examples, the computer-readable storage medium 1106 can include data decoding information sharing software 1154 configured for various functions, including, for example, collecting and / or sharing data decoding information received from one or more transmitters. In some examples, the data decoding information sharing software 1154 can be configured to implement the following in conjunction with Figure 17 and 18 One or more functions described, such as functions described in connection with block 1702, block 1704, block 1706, and / or block 1708, and / or functions described in connection with block 1802, block 1804, and / or block 1806.

[0171] Additionally, in some aspects, the computer-readable storage medium 1106 can include reference signal (RS) monitoring software 1156 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for one or more reference signals (RS) transmitted by one or more transmitters for use in multi-node passive sensing. In some examples, the RS monitoring software 1156 can be configured to implement the following in conjunction with Figure 16 One or more of the functions described, such as the functions described in conjunction with block 1604 and / or block 1606.

[0172] Additionally, in some aspects, the computer-readable storage medium 1106 can include coded data monitoring software 1158 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for coded signals transmitted by one or more transmitters for use in multi-node passive sensing. In some examples, the coded data monitoring software 1158 can be configured to implement the following in conjunction with Figure 19 One or more functions described, such as the functions described in conjunction with block 1904 and / or block 1906.

[0173] Scheduled Entity

[0174] Figure 12is a block diagram conceptually illustrating an example of a hardware implementation of an example scheduled entity 1200 according to various aspects of the present disclosure and is described as an illustrative example rather than a limitation. In some examples, Figure 11 The scheduled entity 1200 may represent a user equipment (UE) (such as for example reference Figure 1 and / or any one or more of the UEs described in 2. According to some aspects of the present disclosure, an element, or any portion of an element, or any combination of elements can be implemented using a processing system 1214 that includes one or more processors 1204.

[0175] In some aspects, the processing system 1214 can be Figure 11 The processing system 1114 shown in FIG. 1 is substantially the same, including a bus interface 1208, a bus 1202, a memory 1205, a processor 1204, and a computer readable medium 1206. In addition, the scheduled entity 1200 may include a user interface 1212, which may be substantially similar to, for example, the above reference Figure 11 Additionally, the scheduled entity 1200 may include a transceiver 1210, which may be substantially similar to, for example, the user interface described above with reference to Figure 11 Describe the transceiver.

[0176] In some examples, the processing system 1214 can utilize one or more processors 1204 to implement the embodiments described herein, for example, with reference to Figures 13 to 19 Any one or more of the processes described in any one or more of .

[0177] In some examples, the processor 1204 can include a reference signal information (RS-info) receiving circuit 1240 configured for various functions. Such functions can include, for example, receiving RS-info (e.g., RS configuration information) corresponding to a set of one or more transmitters (e.g., as shared by transmitters that may or may not be in the set of one or more transmitters, or may or may not belong to the set of one or more transmitters). In some examples, the RS-info receiving circuit 1240 can be configured to implement the following in combination Figure 14 and / or one or more functions described in block 16, such as the functions described below in conjunction with block 1402 and / or block 1604.

[0178] Additionally, in some aspects, the processor 1204 can include a reference signal (RS) monitoring circuit 1244 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for one or more reference signals (RS) transmitted by one or more transmitters for multi-node passive sensing. In some examples, the RS monitoring circuit 1244 can be configured to implement the following in conjunction with Figure 16 One or more functions described, such as the functions described in conjunction with block 1604 and / or block 1606.

[0179] In addition, the processor 1204 can be configured as a data decoding information receiving circuit 1242 for various functions, including, for example, receiving data decoding information corresponding to a set of one or more transmitters (e.g., as shared by transmitters that may or may not be in the set of one or more transmitters or may or may not belong to the set of one or more transmitters). In some examples, the data decoding information receiving circuit 1242 can be configured to implement the following, for example, in conjunction with Figure 17 and / or one or more functions described in connection with block 1702 and / or block 1904, such as the functions described below in connection with block 1702 and / or block 1904.

[0180] Additionally, in some aspects, the processor 1204 can include a coded data monitoring circuit 1246 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for coded signals transmitted by a set of one or more transmitters for use in multi-node passive sensing. In some examples, the coded data monitoring circuit 1146 can be configured to implement the following in conjunction with Figure 19 One or more functions described, such as the functions described in conjunction with block 1904 and / or block 1906.

[0181] In one or more examples, the computer-readable storage medium 1206 can include RS-info (RS-info) receiving software 1252 configured for various functions, including, for example, receiving RS-info (e.g., RS-info parameter sets, RS configuration information, resource parameter sets, etc.) corresponding to a set of one or more transmitters (e.g., shared by transmitters that may or may not be in the set of one or more transmitters or may or may not belong to the set of one or more transmitters). In some examples, the RS-info receiving software 1252 can be configured to implement the following in conjunction with Figure 14 and / or one or more of the functions described in block 16, such as the functions described below in conjunction with block 1402 and / or block 1604.

[0182] In one or more examples, the computer-readable storage medium 1206 can include data decoding information receiving software 1254 configured for various functions, including, for example, receiving data decoding information corresponding to a set of one or more transmitters (e.g., as shared by transmitters that may or may not be in or may or may not belong to the set of one or more transmitters). In some examples, the data decoding information receiving software 1254 can be configured to implement the following in conjunction with Figure 17 and / or one or more functions described in connection with block 1702 and / or block 1904, such as the functions described below in connection with block 1702 and / or block 1904.

[0183] Additionally, in some aspects, the computer-readable storage medium 1206 can include reference signal (RS) monitoring software 1256 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for one or more reference signals (RS) transmitted by a set of one or more transmitters for multi-node passive sensing. In some examples, the RS monitoring software 1256 can be configured to implement the following in conjunction with Figure 16 One or more of the described functionality, such as the functionality described in conjunction with block 1604 and / or block 1606 .

[0184] Additionally, in some aspects, the computer-readable storage medium 1206 can include coded data monitoring software 1258 configured for various functions, including, for example, monitoring resources (e.g., a portion of a frequency-time domain (FD-TD) resource grid) for coded signals transmitted by a set of one or more transmitters for use in multi-node passive sensing. In some examples, the coded data monitoring software 1258 can be configured to implement the following in conjunction with Figure 19 One or more functions described, such as the functions described in conjunction with block 1904 and / or block 1906.

[0185] Example of using reference signal information (RS-info) and data decoding information

[0186] Figure 13 is a flow chart illustrating an example process 1300 for sharing transmission configuration information between entities according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 1300 may be performed by Figure 12 In some examples, the process 1300 may be performed by the scheduled entity 1200 shown in FIG. 1 (e.g., the scheduled entity 106, including the UE 106a, the road side unit (RSU), etc.). Figure 11 The process 1300 is performed by the scheduling entity 1100 shown in FIG. 1 (eg, the scheduling entity 108, the UE, the RSU, etc.). In some examples, the process 1300 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0187] The shared transmission configuration information may include any one or more of a shared reference signal information (RS-info) parameter, a data decoding information parameter, or any other transmission configuration parameter. A receiving entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) may utilize such transmission configuration parameters to receive reference signals reflected from objects that the receiving entity may not otherwise be able to distinguish from static noise. The receiving entity may utilize such transmission configuration parameters to distinguish reflected signals, where the reflected signals correspond to line-of-sight (LoS) signals transmitted between a transmitting entity and a separate receiving entity (e.g., between a UE and a BS, between an RSU and a BS, between two BSs, etc.). The receiving entity may utilize such transmission configuration parameters to extract source and / or destination information from the reflected signals. In one example, the receiving entity may determine from the reflected signals the specific base station or UE that transmitted the corresponding signal, or the destination of the corresponding signal. Additionally, the UE may determine, based on limited data decoding of the reflected signals, the amount of time the reflected signals have been transmitted to the receiving entity to determine when the signal was transmitted, where the signal was transmitted, and other such information used to formulate the geometry discussed herein for identifying the likely location of the object.

[0188] At block 1302, a receiver (such as a first UE) may utilize a first set of transmission configuration parameters to receive: (i) a first line-of-sight (LoS) signal configured for the first UE, and (ii) a first set of reflection signals corresponding to the first LoS signal. Figure 3 In the example shown, the receiver UE may receive the LoS signal 314 and the reflected signal 316 using a first set of transmission configuration parameters.

[0189] At block 1304, the receiver may utilize the first set of transmission configuration parameters to decode a first set of encoded data items corresponding to the first LoS signal. In an example, the receiver may utilize the first set of data decoding parameters to decode data in LoS signal 314. The first set of data decoding parameters may enable the receiver to fully decode LoS signal 314 to determine a first amount of information from LoS signal 314.

[0190] At block 1306, the receiver may receive a second set of transmission configuration parameters related to a second set of reflection signals. The second set of reflection signals may correspond to at least one other LoS signal configured for one or more other entities. Figure 4 or Figure 5In the example shown in FIG5 , the second set of reflected signals may be reflected from object 418 or 568 and may be reflected signals corresponding to LoS signals transmitted between any of UE 414, UE 564b, UE 564a, UE 564c, BS 412a, BS 412b, BS 412c, or BS 562. The second set of transmission configuration parameters may include data decoding information and / or RS-info that enables the receiver to monitor the second set of reflected signals and / or partially decode the second set of reflected signals. In the illustrative example where the receiver is UE 564b, UE 564b may receive the transmission configuration parameters from BS 562 or from UE 654c.

[0191] In some aspects, the receiver can be capable of receiving RS-info (e.g., RS configuration information, resource parameter sets, etc.) in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0192] In some examples, reference signal information (RS-info) can include an explicit indication that RS-info (e.g., RS configuration information, resource parameter groups, etc.) can be used by a receiver (e.g., a receiver utilizing a multi-node passive sensing system) for purposes other than decoding, transmission, channel characterization, or synchronization. Note that there may not be any pre-existing relationship between the devices that together form the multi-node passive sensing system. In some aspects, an entity can receive RS configurations from different transmitters at different times (e.g., when a transmitter such as a UE enters a cell corresponding to the entity). In some aspects, the RS-info received at block 1306 can be a portion (e.g., less than all) of the RS-info corresponding to one or more transmitters. For example, the RS-info received at block 1306 can be a portion of RS-info that can be used for passive sensing.

[0193] At block 1308, the receiver may then monitor a second set of reflected signals based on a second set of transmission configuration parameters. The transmission configuration parameters may indicate a set of resource elements used to monitor a reference signal transmitted from BS 562 to UE 564c or information transmitted from UE 564c to BS 562. The transmission configuration parameters may include data decoding information that enables UE 564b to decode a portion of a signal carried on the reference signal to determine, for example, a timestamp indicating when the signal was transmitted from BS 562 to 564b or vice versa. In this manner, the UE may determine when it has received a reflected signal corresponding to a LoS signal transmitted between BS 562 and 564b.

[0194] At block 1310, the receiver may then utilize the second set of transmission configuration parameters to receive the second set of reflection signals. In an example, the receiver may identify the received signal set as the second set of reflection signals. The receiver may have already received the second set of reflection signals, but the second set of transmission configuration parameters enables the receiver to identify the second set of reflection signals. Otherwise, the received signal would be incomprehensible to the receiver because it would be mixed with background noise of other signal transmissions sent between many other entities. The receiver may use RS-info and / or data decoding information to receive the second set of reflection signals in order to separate the second set of reflection signals from other signals of the background noise. In an example, the receiver may monitor various resource elements (e.g., subcarriers and / or symbols) in the expectation that reflection signals corresponding to those particular resource elements may be received.

[0195] At block 1312, the receiver may utilize the second set of transmission configuration parameters to (optionally) decode a predetermined subset of coded data items corresponding to the second set of reflection signals. In an example, the receiver may utilize the second set of transmission configuration parameters to estimate a frequency domain (FD) channel response or received signal. Additionally, the predetermined subset of coded data items may correspond to less than the entirety of the second set of reflection signals. In an example, the receiver may decode less than the entirety of the coded data items relative to a higher percentage that the receiver is capable of decoding from the first LoS signal 314.

[0196] At block 1314, the receiver may determine a set of candidate spatial locations for the object based on one or more of: the second set of reflected signals, the decoded data item, the first LoS signal, and / or the first set of reflected signals. In an example, the receiver may determine an ellipse of the object based on estimated frequency domain (FD) channel responses of various reference signals (RS). In another example, the receiver may determine ellipse information for the object based on the reflected signal angle, information indicating how the reflected signal reflected from the object to the receiver. The receiver may calculate the amount of time the reflected signal has been in transit to determine the indicated candidate spatial locations based on how far the object is from the receiver and the source transmitter. The source transmitter may have transmitted the LoS signal to the remote UE at a specific time, and the receiver may determine the LoS signal based on the partially decoded data. Using this information, and based on the time at which the reflected signal was received at the receiver, the receiver may infer where the object may be spatially located (e.g., a set of candidate spatial locations) because the reflected signal may have reflected from the object in such a manner that the object is located in multiple places (e.g., along the perimeter of the ellipse).

[0197] In addition, a UE intended for the LoS signal (e.g., a second UE) may receive a LoS signal corresponding to the second set of reflected signals. This UE may also receive reflected signals corresponding to the LoS signal. This UE may also be impacted by other reflected signals corresponding to LoS signals sent to other UEs. Without appropriate transmission configuration information to monitor these reflected signals, the UE may be unable to distinguish these reflected signals from background noise.

[0198] At box 1316, the receiver may (optionally) request additional transmission configuration parameters. In an example, a receiver (e.g., a first UE) may request additional transmission configuration parameters so that the first UE can monitor additional reflected signals. In any case, the first UE receiver may continue to receive the LoS signal intended for its reception, as well as reflected signals related to the first UE's LoS signal that was reflected from the object to the first UE. For example, depending on the angle at which the signal collides with the object, the object may also reflect such a signal to other receivers. However, without specific transmission configuration information (e.g., RS-info, data decoding parameters, etc.), other receivers may not be able to use the reflected signal. In this case, the reflected signal will be mixed with the noise of the other signals, and other receivers will not be able to use such reflected signal to estimate the position of the object that reflected the signal.

[0199] Example of using reference signal information (RS-info)

[0200] Figure 14is a flow chart illustrating an example process 1400 for sharing reference signal (RS) information (RS-info) between one or more entities according to one or more of the various techniques of the present disclosure, and is described as an illustrative example and not as a limitation. As described below, some or all of the illustrated features can be omitted in certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1400 can be combined with the above Figure 11 The scheduling entity 1100 (eg, base station (BS) 108) described above (eg, using transceiver 1110, etc.), and / or Figure 12 The scheduled entity 1200 (eg, UE 106) described above (eg, using transceiver 1210, etc.), and / or Figure 1 In some examples, process 1400 can be performed (eg, executed) by base station 108 or UE 106 as described below. In some examples, process 1400 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0201] At block 1402, an entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can receive reference signal information (RS-info) corresponding to one or more transmitters (e.g., transmitters forming part of a multi-node passive sensing system). In some aspects, the entity can receive the RS-info (e.g., RS configuration information, resource parameter sets, etc.) in one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0202] In some examples, reference signal information (RS-info) can include an explicit indication that RS-info (e.g., RS configuration information, resource parameter sets, etc.) can be used by a receiver (e.g., a receiver utilizing a multi-node passive sensing system) for purposes other than decoding, transmission, channel characterization, or synchronization. Note that there may not be any pre-existing relationship between the devices that together form the multi-node passive sensing system. In some aspects, an entity can receive RS configurations from different transmitters at different times (e.g., when a transmitter such as a UE enters a cell corresponding to the entity). In some aspects, the RS-info received at block 1402 can be a portion (e.g., less than all) of the RS-info corresponding to one or more transmitters. For example, the RS-info received at block 1402 can be a portion of the RS-info that can be used for passive sensing. In some aspects, block 1402 can be omitted. For example, a device (such as a base station) performing process 1400 can maintain RS-info corresponding to a scheduled entity, such that block 1402 may be unnecessary. Note that an entity performing process 1400 may or may not recognize a specific RS with a specific transmitter. For example, the information received by the entity performing the process can be information related to antenna ports, QCL information, and / or RSs without specifically identifying transmitters associated with the antenna ports, QCL information, and / or RSs.

[0203] At block 1404, an entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can receive a request for RS-info corresponding to one or more nearby transmitters from a UE (or other receiver). In some aspects, the entity can receive the request for RS-info in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0204] In some examples, the request for reference signal information (RS-info) can correspond to an explicit indication that the RS-info (e.g., RS configuration information) is requested for a multi-node passive sensing process. Note that the entity receiving the RS-info at block 1402 can be the same or different from the entity receiving the request at block 1404. For example, the RSU can collect the RS configuration information and provide the information to a nearby base station, which can receive the request at block 1404. In some aspects, block 1404 can be omitted. For example, the RS-info can be broadcast periodically (e.g., at regular and / or irregular intervals).

[0205] At block 1406, the entity can determine that RS-info sharing is permitted. For example, in some aspects, the entity can determine that RS-info can be shared for the purpose of multi-node passive sensing. In a more specific example, the entity can determine that RS-info can be shared for the purpose of multi-node passive sensing based on an explicit indication received from the transmitter providing RS-info at block 1402. As another more specific example, the entity can determine that RS-info can be shared for the purpose of multi-node passive sensing based on the RS-info received at block 1402. In some aspects, if the request at block 1404 does not correspond to an explicit indication that the requested RS-info is for a multi-node passive sensing process and / or if the RS-info does not correspond to an explicit indication that a receiver utilizing a multi-node passive sensing system can use the RS-info, then process 1400 can end. Additionally or alternatively, in some aspects, the entity can determine not to share the requested RS-info for any other suitable reason.

[0206] At block 1408, the entity can send, to the UE (or other receiver) that requested RS-info (e.g., at block 1404), reference signal information (RS-info) parameter sets for one or more nearby transmitters of the UE (or other receiver) that requested (or requested) RS-info (e.g., RS configuration information) at block 1404. In some aspects, the entity can send the RS-info in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as the RAN 104 or the RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0207] In some examples, an entity (e.g., base station 108) can send to a UE only RS-info (RS-info) related to at least one RS transmission that has not been targeted to the UE (or other receiver) that requested RS-info in block 1404. In some aspects, a reference signal (RS) can be targeted to a specific receiver if the RS is scheduled for the purpose of that receiver using the RS as a reference for further communication. For example, the RS can be targeted to a specific receiver that is expected to use the RS for correctly receiving and / or decoding communications from a transmitter that is scheduled (and / or has already) transmitted the RS. In a more specific example, the base station can target a specific UE with an RS that the UE uses as a reference to receive other signals sent to the specific UE.

[0208] In another more specific example, a UE can target one or more base stations (BSs) that use RSs as a reference to receive other signals sent by the specific UE. As another example, a first UE can target a second UE (neither of which is the UE requesting RS-info in block 1404), where the second UE uses RSs as a reference to receive other signals sent by the first UE to the second UE. As described above, RSs can be used to estimate the channel response of a channel used to transmit information characterizing the channel to a receiver. As another example, RSs can be targeted to a specific receiver that is intended to use RSs for the purpose of synchronizing the transmission of a signal with the device transmitting the RSs. As another example, if the UE requesting RS-info in block 1404 is requesting RS configuration only for purposes other than transmission of information, reception of information for the UE (e.g., RSs can be used to receive information for another receiver for use in a multi-node passive sensing process, but not for receiving messages and / or information elements (IEs) for the UE), channel characterization for reception of information for the UE, or synchronization of communications to / from the UE to another device.

[0209] In some aspects, RS-info can include an indication that a reference signal (RS) set corresponding to the RS-info can only be used by a specific UE for limited or constrained purposes, such as passive sensing. Additionally or alternatively, in some aspects, RS-info can include an indication that the RS corresponding to the RS-info can be used for purposes other than decoding or sending data, such as for passive sensing. In an example, RS-info can include an indication that at least some portion of the RS-info is used by the UE (or other receiver) to perform a passive sensing process. As another example, RS-info can include an indication that the UE (or other receiver) will not use at least some portion of the RS-info to decode or send any signal. As yet another example, RS-info can include an indication that HARQ-ACK feedback related to the RS-info is not required from the UE (or other receiver).

[0210] In some aspects, an entity (e.g., a base station 108, a roadside unit (RSU), a central server, etc.) may send RS-info using any suitable channel, format, technique, or combination of techniques. In one example, an entity may send RS-info to one or more receiving entities (e.g., one or more scheduled entities 106, etc.) using one or more of the following: a radio resource control (RRC) message; one or more MAC control elements (MAC-CEs); downlink control information (DCI); sidelink (SL) control information (SCI); a dedicated physical downlink shared channel (PDSCH) message; a dedicated physical sidelink shared channel (PDSCH) message; a message sent using a dedicated physical (PHY) layer channel (e.g., a PHY RS-info indication channel (PRICH)); and / or a control resource set (CORESET) identifier (ID) and a corresponding search space (SS).

[0211] Note that if the CORESET ID is used to transmit RS-info, the UE (or other receiver) may already be configured with one or more search spaces (SSs) and CORESETs for physical downlink control channel (PDCCH) monitoring. In some aspects, the UE (or other receiver) can use additional CORESETs and SSs to identify demodulation reference signals (DMRS) for sensing purposes, and the UE can prohibit them from being used for PDCCH monitoring.

[0212] In a specific example, for reference signal information (RS-info) transmitted via downlink (DL) control information (DCI), the DCI can be group common DCI (GC-DCI), can be transmitted via PDCCH and / or PDSCH, and / or can be one part or both parts of a 2-stage DCI.

[0213] In another specific example, for RS-info transmitted via sidelink control information (SCI), the SCI can be transmitted via PSCCH and / or PSSCH, and / or can be part or both parts of a 2-stage SCI.

[0214] In some aspects, the indication corresponding to RS-info can indicate whether the RS-info corresponds to a DL RS, a UL RS, and / or a SLRS.

[0215] In some examples, the one or more reference signals (RS) corresponding to RS-info (RS-info) can be one or more of the following types of RS: (i) demodulation reference signal (DMRS) (e.g., for physical uplink (UL) shared channel (PUSCH), physical downlink (DL) shared channel (PDSCH), physical UL control channel (PUCCH), physical DL control channel (PDCCH), etc.); (ii) channel state information reference signal (CSI-RS); (iii) channel state information tracking reference signal (CSI-TRS); (iv) positioning reference signal (PRS); (v) phase tracking reference signal (PTRS); (vi) sounding reference signal (SRS); and / or (viii) any other suitable reference signal (RS).

[0216] Example for sharing reference signal information (RS-info)

[0217] Figure 15 1 is a flow chart illustrating an example process 1500 for an entity to share reference signal information (RS-info) corresponding to one or more reference signals (RS) transmitted by the entity to one or more other entities in accordance with one or more of the various techniques of the present disclosure, and is described as an illustrative example and not as a limitation. As described below, some or all of the illustrated features can be omitted in certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1500 can be performed by (combining the above with Figure 11 and Figure 12 The scheduled entity or scheduling entity (such as the one described above) Figure 1 In some examples, process 1500 can be performed by any suitable device or apparatus for performing one or more of the various techniques disclosed herein.

[0218] At block 1502, an entity (e.g., a base station (BS), a roadside unit (RSU), a user equipment (UE), a central node, or a server) can receive a request from a first UE (or other receiver) to share reference signal information (RS-info) with the first UE. In some aspects, the entity can receive the request for RS-info (e.g., RS configuration information, a set of resource parameters related to a reference signal (RS) set, etc.) in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots, sidelink (SL) time slots, and / or downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies such as a sidelink (SL) connection, Bluetooth communication, etc.). In some examples, the request for RS-info can correspond to an explicit indication that the requested RS-info (e.g., RS configuration information) is for use by the first UE in a multi-node passive sensing process.

[0219] At block 1504, the entity may determine whether sharing RS-info with the first UE is permissible so that the entity can fully or at least partially fulfill or comply with the request. In an example, the entity may determine that sharing RS-info with the first UE is permissible so that the first UE can utilize RS-info to perform one or more multi-node passive sensing techniques. In some examples, the entity may determine that RS-info can be shared for the purpose of multi-node passive sensing based on an explicit indication (e.g., in a memory) that RS-info can be shared for the purpose of multi-node passive sensing. In some examples, if the request received at block 1502 does not correspond to an explicit indication that the requested RS-info is for a multi-node passive sensing process and / or the entity determines that the requested RS-info cannot be shared with the first UE (and / or another receiver) (such as for multi-node passive sensing), process 1500 can end (e.g., at block 1504). Additionally or alternatively, in some aspects, the entity may determine not to share RS-info for any other suitable reason.

[0220] At block 1506, the entity can send a RS-info parameter set corresponding to the entity's own reference signal (RS) transmission to the UE (or other receiver) that requested RS-info at block 1502. In some aspects, any suitable technique or combination of techniques (such as the above in combination) can be used. Figure 14In some aspects, an entity can send RS-info in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots, sidelink time slots, and / or downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0221] In some examples, reference signal information (RS-info) may correspond to one or more dependencies that govern (eg, control) the use of RS-info, as described above in conjunction with Figure 14 In some aspects, the indication corresponding to RS-info can indicate whether the RS-info corresponds to a downlink (DL) reference signal (RS), an uplink (UL) RS, and / or a sidelink (SL) RS.

[0222] In some examples, the one or more reference signals (RS) corresponding to RS-info (RS-info) can be one or more of the following RSs: (i) a demodulation reference signal (DMRS) (e.g., for a physical uplink (UL) shared channel (PUSCH), a physical downlink (DL) shared channel (PDSCH), a physical UL control channel (PUCCH), a physical DL control channel (PDCCH), etc.); (ii) a channel state information reference signal (CSI-RS); (iii) a channel state information tracking reference signal (CSI-TRS); (iv) a positioning reference signal (PRS); (v) a phase tracking reference signal (PTRS); (vi) a sounding reference signal (SRS); and / or (vii) any other suitable reference signal (RS).

[0223] Example of providing reference signal information upon request

[0224] Figure 16 is a flow chart illustrating an example process 1600 for facilitating multi-node passive sensing using reference signal information (RS-info) configuration according to one or more of the various techniques of the present disclosure and is described as an illustrative example and not as a limitation. As described below, some or all of the illustrated features can be omitted in certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1600 can be combined with the above Figure 11 and Figure 12 The scheduled entity or scheduling entity described above, and / or Figure 1In some examples, process 1600 can be performed (eg, executed) by base station 108 or UE 106 as described. In some examples, process 1600 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0225] At block 1602, a receiver (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can request reference signal information (RS-info) corresponding to one or more nearby transmitters (e.g., one or more UEs, base stations (BSs), roadside units (RSUs), etc.). In some aspects, the receiver can request RS-info (e.g., an RS-info parameter set, etc.) using one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network such as the RAN 104 or the RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots, or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0226] In some examples, the receiver can request reference signal information (RS-info) from any suitable transmitter or transmitters. In an example, the receiver can request RS-info from a base station (BS) during an uplink (UL). In another example, the receiver can request RS-info from a user equipment (UE) during a downlink (DL) (e.g., where the receiver is a base station (BS)). As yet another example, the receiver can request RS-info from another entity via a sidelink (SL) connection.

[0227] In some examples, the entity performing process 1600 can omit (e.g., skip) block 1602 from process 1600. In an example, the transmitter can provide RS-info that is not sent in response to an explicit request from the receiver (e.g., the request can come from another entity, such as a base station, or from a core network).

[0228] At block 1604, the receiver can receive reference signal information (RS-info) corresponding to one or more transmitters. In some aspects, the receiver can receive RS-info in one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.). In some examples, the reference signal information (RS-info) can include information about multiple reference signals (RSs) used by a particular transmitter.

[0229] In some examples, RS-info can correspond to one or more dependencies that control (e.g., limit) and / or allow the use of RS-info, as described herein, for example, with reference to Figure 14 Frame 1408.

[0230] In some aspects, RS-info can be received using any suitable technique or combination of techniques, such as those described herein, e.g., with reference to Figure 14 In some examples, the indication corresponding to RS-info may indicate whether the RS-info corresponds to a downlink (DL) reference signal (RS), an uplink (UL) RS, and / or a sidelink (SL) RS.

[0231] In some examples, the one or more reference signals (RS) corresponding to the reference signal information (RS-info) can be one or more of the following reference signals: (i) a demodulation reference signal (DMRS) (e.g., for a physical uplink (UL) shared channel (PUSCH), a physical downlink (DL) shared channel (PDSCH), a physical UL control channel (PUCCH), a physical DL control channel (PDCCH), etc.); (ii) a channel state information reference signal (CSI-RS); (iii) a channel state information tracking reference signal (CSI-TRS); (iv) a positioning reference signal (PRS); (v) a phase tracking reference signal (PTRS); (vi) a sounding reference signal (SRS); and / or (vii) any other suitable reference signal (RS).

[0232] At block 1606, the receiver can monitor the resources specified by RS-info (e.g., RS-info corresponding to one or more nearby transmitters). For example, the receiver can monitor the frequency-time domain (FD-TD) resource set corresponding to the RS-info. The receiver can do so using one or more transceivers (e.g., using transceiver 1210). In a more specific example, the receiver can attempt to detect the RS corresponding to the FD-TD resource set corresponding to the RS-info by sampling and buffering the received wireless signal and applying appropriate processing (such as energy detection, demodulation, decoding, etc.) to the buffered signal.

[0233] At block 1608, the receiver can receive a reference signal (RS) originating from one or more nearby transmitters. Figures 3 to 5 A receiver can receive the same reference signal (RS) transmitted multiple times by a specific transmitter, including as a line-of-sight (LoS) signal and as one or more multipath reflection signals corresponding to the LoS reference signal. Because the receiver has access to RS-info (e.g., RS configuration information), the receiver can use RS-info to detect at least one reference signal (RS) corresponding to the RS-info.

[0234] Without RS-info, a receiver may not correctly detect a reference signal (RS) intended for another device (e.g., a second receiver, such as a second user equipment (UE)). That is, without access to a demodulation reference signal (DMRS) corresponding to the receiver for which the RS is intended, the receiver may not correctly detect the RS. In this case, the receiver may not correctly estimate the channel response of the channel.

[0235] At block 1610, the receiver can use the received RS-info to estimate the frequency domain (FD) channel response of the received signal. In some aspects, the receiver can use any suitable technique or combination of techniques to estimate the FD channel response. In an example, the receiver can estimate the channel by calculating the symbol-by-symbol channel frequency response using inverse filtering. The receiver can use this filtering to recover one or more transmitted symbols and can use these symbols to generate a channel impulse response indicating the multipath time delay. In some aspects, the receiver can estimate the FD channel response of RSs received from multiple transmitters.

[0236] At block 1612, the receiver can determine an ellipse of the object based on the estimated frequency domain (FD) channel responses of various reference signals (RS). In some aspects, the receiver can use any suitable technique or combination of techniques to determine the ellipse. For example, the receiver can use the techniques described herein (e.g., reference signals). Figures 3 to 5) to determine the ellipses corresponding to the RSs received from various transmitters.

[0237] At block 1614, the receiver can act as a transmitter and can transmit a reference signal (RS) using at least a portion of reference signal information (RS-info) shared with at least one other transmitter for multi-node passive sensing. For example, the receiver can be used as part of a multi-node passive sensing system that can be used by other receivers to locate objects in an environment. In some aspects, the receiver can transmit RS-info (e.g., RS configuration information, resource parameter sets, RS-info parameter sets, etc.) in one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0238] Example of using data to decode information

[0239] Figure 17 1700 is a flowchart illustrating an example process for sharing data decoding information of one or more entities according to one or more of the various techniques of the present invention, and is described as an illustrative example rather than a limiting example. As described below, some or all of the illustrated features can be omitted in certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1700 can be combined with the above. Figure 11 and Figure 12 The scheduled entity or scheduling entity described above, and / or Figure 1 In some examples, process 1700 can be performed (eg, executed) by base station 108 or UE 106 as described. In some examples, process 1700 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0240] At block 1702, an entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can receive data decoding information corresponding to one or more transmitters (e.g., transmitters forming part of a multi-node passive sensing system). In some aspects, the entity can receive the data decoding information in one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0241] In some examples, the data decoding information can include an explicit indication that the data decoding information can be used by the receiver for purposes other than decoding data scheduled for reception by an entity (e.g., a receiver utilizing a multi-node passive sensing system). Note that there may not be any pre-existing relationship between the devices that together form the multi-node passive sensing system. In some aspects, the entities can receive data decoding information from different transmitters at different times (e.g., when a transmitter such as a UE enters a cell corresponding to the entity). In some aspects, the data decoding information received at block 1702 can be a portion (e.g., less than all) of the data decoding information corresponding to one or more transmitters. For example, the data decoding information received at block 1702 can be a portion of the data decoding information that can be used for passive sensing. In some aspects, block 1702 can be omitted. For example, a device performing process 1700 (e.g., a scheduling entity 108 (e.g., a base station (BS))) can maintain and / or manage data decoding information corresponding to the scheduled entity 106, such that block 1702 may be unnecessary. Note that the entity performing process 1700 may identify a specific RS using a specific transmitter or may not identify a specific RS using a specific transmitter. For example, the information received by the entity performing the process may be information related to an antenna port, QCL information, and / or RS without specifically identifying the transmitter associated with the antenna port, QCL information, and / or RS.

[0242] At block 1704, an entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can receive a request for data decoding information corresponding to one or more nearby transmitters from a UE (or other receiver). In some aspects, the entity can receive the request for data decoding information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0243] In some examples, the request for data decoding information may correspond to an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process. Note that the entity receiving the data decoding information at block 1702 can be the same or different than the entity receiving the request at block 1704. In an example, a roadside unit (RSU) can collect the data decoding information and provide the information to a nearby base station (BS), which can receive the request at block 1704. In some aspects, block 1704 can be omitted. For example, the data decoding information can be broadcast periodically (e.g., at regular and / or irregular intervals). In some aspects, the data decoding information can include only decoding information that can be used to decode signals at the physical (PHY) layer, which can cause higher layer data sent to or from the UE to be encrypted and inaccessible to the entity possessing the data decoding information.

[0244] At block 1706, the entity can determine that sharing of the data decoding information is permitted. For example, in some aspects, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing. In a more specific example, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing based on an explicit indication received from the transmitter providing the data decoding information at block 1702. As another more specific example, the entity can determine that the data decoding information can be shared for the purpose of multi-node passive sensing based on receiving the data decoding information at block 1702.

[0245] In some examples, if the request at block 1704 does not correspond to an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process and / or if the data decoding information does not correspond to an explicit indication that a receiver utilizing a multi-node passive sensing system can use the data decoding information, process 1700 can end. Additionally or alternatively, in some aspects, an entity can determine not to share the requested data decoding information for any other suitable reason.

[0246] At block 1708, the entity can send data decoding information for one or more nearby transmitters to the UE (or other receiver) that requested the data decoding information at block 1704. In some aspects, the data decoding information can include an indication that the encoded signal corresponding to the data decoding information can only be used for a limited or restricted purpose. In some aspects, the entity can send the data decoding information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network (such as RAN 104 or RAN 200), using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies (such as sidelink (SL) communication, Bluetooth communication, etc.)).

[0247] In some examples, the data decoding information can include an indication that the data corresponding to the data decoding information can be used for purposes other than decoding or sending data (such as passive sensing). For example, the data decoding information can include an indication that at least some portion of the data decoding information is used by the UE (or other receiver) to perform a passive sensing process. As another example, the data decoding information can include an indication that at least some portion of the data decoding information will not be used by the UE (or other receiver) to schedule the UE to receive encoded data (e.g., encoded in one or more packets). As yet another example, the data decoding information can include an indication that HARQ-ACK feedback related to the data decoding information is not required from the UE (or other receiver). As yet another example, the data decoding information may correspond to an indication that HARQ-ACK feedback is not required from the UE (or other receiver) when the UE has received and / or decoded the encoded data.

[0248] In some aspects, data decoding information can be sent using any suitable channel, format, technique, or combination of techniques. For example, data decoding information can be sent using one or more of the following: a radio resource control (RRC) message; one or more medium access control (MAC) control elements (MAC-CEs); downlink (DL) control information (DCI); sidelink (SL) control information (SCI) (e.g., scheduling a physical sidelink shared channel (PUSCH)); DCI and / or SCI included in a PDSCH, physical downlink control channel (PDCCH), physical sidelink control channel (PSCCH), and / or physical sidelink shared channel (PDSCH) message; a dedicated PDSCH message; a dedicated PDSCH message; a message sent using a dedicated physical (PHY) layer channel (e.g., a PHY RS-info indicator channel (PRICH)); and / or a CORESET ID and corresponding search space (SS). Note that if a CORESET ID is used to convey data decoding information, the UE (or other receiver) may already be configured with one or more SSs and CORESETs for physical downlink control channel (PDCCH) monitoring. In some aspects, a UE (or other receiver) can use additional CORESETs and SSs to identify coded messages sent for sensing purposes. In accordance with one or more of the various techniques of this disclosure, a UE can prohibit the use of a particular set of coded messages for other purposes (e.g., fully decoding the message to decode the complete set of coded data signals).

[0249] In a particular example, for data decoding information transmitted via downlink (DL) control information (DCI) (e.g., to a first user equipment (UE)), the DCI can be transmitted via one or more downlink channels (e.g., a physical downlink DL control channel (PDCCH) and / or a physical DL shared channel (PDSCH), etc.), and / or can be part or both parts of a 2-stage DCI.

[0250] In another specific example, for data decoding information transmitted via sidelink (SL) control information (SCI) (e.g., to a first UE), the SCI can be transmitted via one or more sidelink channels (e.g., physical SL control channel (PSCCH) and / or physical SL shared channel (PSSCH), etc.) (e.g., via a second UE, a roadside unit, etc.), and / or can be part or both parts of a 2-stage SCI.

[0251] In some aspects, the indication corresponding to the data decoding information can indicate whether the data decoding information corresponds to a DL transmission, a UL transmission, and / or a SL transmission.

[0252] In some aspects, coded data items corresponding to data decoding information (e.g., one or more coded data packets, coded data signals, coded data, etc.) can be sent via one or more of the following channels: PDSCH, PUSCH, PUCCH, PDCCH, PSSCH, PSCCH; and / or any other suitable signal. Coded data items sent via a coded channel can be considered to be messages for that coded channel. In an illustrative and non-limiting example, the coded message sent via the PDSCH comprises a PDSCH message.

[0253] Figure 18 is a flow chart illustrating an example process for entities to share data decoding information corresponding to their own transmissions according to one or more of the various techniques of the present disclosure and is described as illustrative examples and not limiting. As described below, some or all of the illustrated features can be omitted in certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1800 can be combined with Figure 11 and Figure 12 The scheduled entity or scheduling entity described above, and / or Figure 1 In some examples, process 1800 can be performed (eg, executed) by base station 108 or UE 106 as described below. In some examples, process 1800 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0254] At 1802, an entity (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can receive a request for data decoding information from a UE (or other receiver). In some aspects, the entity can receive the request for data decoding information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies, such as sidelink (SL) communication, Bluetooth communication, etc.).

[0255] In some examples, the request for data decoding information may correspond to an explicit indication that the requested data decoding information is for use in a multi-node passive sensing process.

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

[0257] At 1806, the entity can send data decoding information corresponding to the entity's coded signal transmission to the UE (or other receiver) that requested the data decoding information at 1802. In some aspects, the entity can send the data decoding information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies such as sidelink (SL) communication, Bluetooth communication, etc.).

[0258] In some examples, the data decoding information may correspond to one or more dependencies that control the use of the data decoding information, as described above in conjunction with block 1708. In some aspects, any suitable technique or combination of techniques (such as described above in conjunction with Figure 17 In some aspects, the indication corresponding to the data decoding information can indicate whether the data decoding information corresponds to a downlink (DL) transmission, an uplink (UL) transmission, and / or a sidelink (SL) transmission.

[0259] In some aspects, the encoded transmission corresponding to the data decoding information (e.g., comprising one or more packets) can be one or more of the following types of transmissions: PDSCH transmissions, PUSCH transmissions, PUCCH transmissions, PDCCH transmissions, PSSCH transmissions, PSCCH transmissions, and / or any other suitable type of transmissions.

[0260] Example of using data to decode information

[0261] Figure 19is a flowchart illustrating an example process for facilitating multi-node passive sensing using data decoding information in accordance with one or more of the various techniques of the present disclosure and is described as an illustrative example and not as a limitation. As described below, some or all of the illustrated features can be omitted within certain implementations within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments. In some examples, process 1900 can be performed by combining the above Figure 11 and Figure 12 The scheduled entity or scheduling entity described above, and / or Figure 1 In some examples, process 1900 can be performed (eg, executed) by base station 108 or UE 106 as described. In some examples, process 1900 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0262] At block 1902, a receiver (e.g., a user equipment (UE), a base station (BS), a roadside unit (RSU), etc.) can request data decoding information corresponding to one or more nearby transmitters (e.g., one or more UEs, base stations, RSUs, etc.). In some aspects, the receiver can request the data decoding information using one or more messages and / or information elements (IEs) transmitted using any suitable communication network (e.g., via a network (such as RAN 104 or RAN 200), using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots, or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., using any suitable technology or combination of technologies (such as sidelink (SL) communication, Bluetooth communication, etc.)).

[0263] In some examples, the receiver can request data decoding information from any suitable one or more transmitters. For example, the receiver can request data decoding information from a base station (BS) during an uplink (UL). As another example, the receiver can request data decoding information from a UE during a downlink (DL) (e.g., if the receiver is a base station). As yet another example, the receiver can request data decoding information from another entity via a sidelink (SL) connection. In some aspects, the entity performing process 1900 can omit performing the function corresponding to box 1902. For example, the transmitter can provide data decoding information that is not sent in response to an explicit request from the receiver (e.g., the request can come from another entity, such as a base station, or from a core network).

[0264] At block 1904, the receiver can receive data decoding information corresponding to one or more transmitters. In some aspects, the receiver can receive data decoding information in one or more messages and / or information elements (IEs) sent using any suitable communication network (e.g., via a network such as RAN 104 or RAN 200, using one or more uplink (UL) time slots and / or one or more downlink (DL) time slots; or via one or more peer-to-peer (P2P) connections, vehicle-to-everything (V2X) connections, etc., utilizing any suitable technology or combination of technologies such as sidelink (SL) communication, Bluetooth communication, etc.).

[0265] In some examples, the data decoding information can include information about multiple types of transmissions sent by a particular transmitter. In some aspects, the data decoding information can correspond to one or more dependencies that control the use of the data decoding information as described above in conjunction with block 1708. In some aspects, any suitable technique or combination of techniques (such as those described above in conjunction with Figure 17 In some aspects, the indication corresponding to the data decoding information can indicate whether the data decoding corresponds to a downlink (DL) transmission, an uplink (UL) transmission, and / or a sidelink (SL) transmission.

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

[0267] At block 1906, the receiver can monitor resources specified by the data decoding information corresponding to one or more nearby transmitters. For example, the receiver can use one or more transceivers to monitor FD-TD resources corresponding to the data decoding information. In a more specific example, the receiver can attempt to detect a coded signal corresponding to the FD-TD resource corresponding to the data decoding information by sampling and buffering the received wireless signal and applying appropriate processing (such as energy detection, demodulation, decoding, etc.) to the buffered signal.

[0268] At block 1908, the receiver can receive an encoded transmission (e.g., comprising one or more packets, transport blocks (TBs), etc.) originating from one or more nearby transmitters. Figures 3 to 5As described, the same signal transmitted by a particular transmitter can be received multiple times, including as a line-of-sight (LoS) signal and as one or more multipath reflection signals (e.g., backscatter signals). If the receiver has access to RS-info and / or data decoding information, the receiver can estimate the channel on which the coded signal is transmitted and can decode the physical (PHY) layer of the coded signal corresponding to the data decoding information. In the absence of data decoding information, the receiver may not decode the coded signal even if it has received a reference signal corresponding to the channel and / or has estimated the channel response.

[0269] At block 1910, the receiver can use the received data decoding information to estimate a frequency domain (FD) channel response of the received signal. In some aspects, the receiver can use any suitable technique or combination of techniques to estimate the FD channel response. For example, the receiver can estimate the FD channel response, for example, by determining channel coefficients for multiple antenna ports. In some aspects, the receiver can estimate the FD channel response for coded signals received from multiple transmitters.

[0270] At block 1912, the receiver can determine an ellipse corresponding to the object based on the estimated frequency domain (FD) channel responses of the various signals. In some aspects, the receiver can determine the ellipse using any suitable technique or combination of techniques. For example, the receiver can use the techniques described herein, such as those described with reference to FIG. Figures 3 to 5 The described techniques determine ellipses corresponding to coded signals received from various transmitters.

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

[0272] In one configuration, the apparatus 1100 and / or 1200 for wireless communication includes means for collecting and / or sharing data decoding information and / or reference signal information (RS-info) (e.g., RS-info parameter sets, reference signal (RS) configuration information, RS monitoring and / or reception data, etc.), means for monitoring resources for one or more coded signals and / or one or more reference signals (RS), and / or means for receiving data decoding information and / or RS-info. In some aspects, the aforementioned means can be combined with the above. Figure 11 and 12 The processor(s) 1104 and / or 1204 are depicted as being configured to perform the functions recited by the aforementioned means. Additionally or alternatively, in some aspects, the aforementioned components can be circuitry or any apparatus configured to perform the functions recited by the aforementioned means.

[0273] Of course, in the above examples, the circuits included in the processor 1104 and / or the processor 1204 are provided only as examples, and other means for performing the described functions can be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1106 and / or 1206, or Figure 1 and / or Figure 2 Any other suitable apparatus or device described in any of the foregoing, and utilizing, for example, reference Figures 13 to 19 Any one or more of the described processes and / or algorithms.

[0274] Other examples with various characteristics:

[0275] Example 1: A method for receiving a transmission configuration message by a first entity (e.g., a first user equipment (UE)), the transmission configuration message comprising: (i) reference signal information (RS-info) corresponding to a reference signal (RS) set sent between a second entity (e.g., a base station, a sidelink UE, or a roadside unit) and a third entity (e.g., a second UE, a second base station, a second roadside unit), and / or (ii) data decoding information indicating a first data decoding parameter set corresponding to the second entity and / or the third entity; and monitoring, by the first entity, at least one of: (i) monitoring the RS set based on the RS-info, or (ii) monitoring a coded signal set on one or more coded channels based on the data decoding information.

[0276] Example 2: The method according to Example 1 further includes: receiving at least one of the following: (i) receiving an RS set based on RS-info, or (ii) receiving a coded signal set based on data decoding information; and determining information related to the spatial position of an object close to the UE based on at least one of the following: (i) a coded signal set, or (ii) an RS set.

[0277] Example 3: The method according to any one of Examples 1 or 2 further includes: omitting the transmission of hybrid automatic repeat request (HARQ) feedback associated with the reception of one or more of the following items: (i) RS-info, (ii) an RS set received using RS-info, (iii) data decoding information, or (iv) a coded signal set.

[0278] Example 4: The method according to Example 3 also includes: receiving a second RS set, the second RS set including at least one line of sight (LoS) signal and at least one corresponding reflected signal targeted at the first UE; and sending one or more feedback messages indicating that the second RS set has been received.

[0279] Example 5: A method according to any one or more of Examples 1 to 4, wherein the transmission configuration message includes one or more of the following items: a radio resource control (RRC) configuration message; one or more media access control (MAC) control elements (MAC-CE); downlink control information (DCI); a physical downlink shared channel (PDSCH) message; sidelink control information (SCI); a physical sidelink shared channel (PSSCH) message; a message sent using a physical (PHY) layer channel; a control resource set (CORESET) identifier (ID) and a corresponding search space (SS); a physical RS-info channel including RS-info; a physical data decoding channel including data decoding information; or a physical transmission configuration channel including data decoding information and RS-info.

[0280] Example 6: A method according to any one or more of Examples 1 to 5, wherein the RS-info indicates that at least one RS from a reference signal (RS) set corresponds to at least one first time slot, and wherein the data decoding information indicates that at least one coded signal from a coded signal set corresponds to the at least one first time slot or at least one second time slot.

[0281] Example 7: A method according to any one or more of Examples 1 to 6, wherein the monitoring of the RS set based on RS-info includes: using RS-info to determine a resource element set to monitor at least one of the following: (i) a demodulation reference signal (DMRS), (ii) a channel state information reference signal (CSI-RS), (iii) a channel state information tracking reference signal (CSI-TRS), (iv) a positioning reference signal (PRS), (v) a phase tracking reference signal (PTRS), or (vi) a sounding reference signal (SRS). And monitoring the coded signal set based on data decoding information includes: using data decoding information to decode at least one coded channel (e.g., one or more of the following: a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a physical sidelink shared channel (PSSCH), or a physical sidelink control channel (PSCCH)).

[0282] Example 8: A method according to any one or more of Examples 1 to 7, wherein the resource parameter set includes at least one of the following: (i) a frequency domain (FD) attribute indicating a resource parameter set for monitoring by the first UE; or (ii) a time domain (TD) attribute indicating a resource parameter set for monitoring by the first UE.

[0283] Example 9: A method according to Example 8, wherein the frequency domain (FD) attributes of the resource parameter set include an indication of one or more of the following: one or more physical resource blocks (PRBs), one or more bandwidth parts (BWPs), one or more component carriers (CCs), one or more subcarriers, or at least one radio access technology (RAT).

[0284] Example 10: A method according to any one or more of Examples 8 or 9, wherein the time domain (TD) attributes of the resource parameter set include an indication of one or more of the following: one or more symbols, one or more time slots, one or more subframes, or one or more frames.

[0285] Example 11: A method according to any one or more of Examples 1 to 8, wherein the RS-info includes information related to one or more port IDs or one or more scrambling IDs of the RS set monitored by the first UE, and wherein the data decoding information includes information related to one or more port IDs or one or more scrambling IDs of the coded signal set on one or more channels monitored by the first UE.

[0286] Example 12: A wireless communication device comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor being configured to: receive, via the transceiver, a message comprising at least one of: (i) a reference signal information (RS-info) parameter set relating to one or more reference signals (RS), the one or more reference signals (RS) corresponding to at least one line of sight (LoS) signal targeted at one or more receiving devices that are different and separate from the wireless communication device, or (ii) a data decoding information parameter set relating to data, the data being scheduled for the purpose of communicating with one or more receiving devices via at least one line of sight (LoS) signal targeted at the one or more receiving devices; and monitor, using the transceiver, at least one of: (i) monitoring an RS set based on the RS-info parameter set, or (ii) monitoring a coded signal set based on the data decoding information parameter set.

[0287] Example 13: A wireless communication device according to Example 12, wherein, in order to monitor the RS set, the processor is configured to: receive a first reference signal (RS) using an RS-info parameter set; and determine information related to the spatial position of an object close to the wireless communication device based on the first RS, and wherein, in order to monitor the coded signal set, the processor is configured to: receive a first coded signal using a data decoding information parameter set; and determine information related to the spatial position of an object close to the wireless communication device based on the first coded signal.

[0288] Example 14: A wireless communication device according to any one of Examples 12 or 13, wherein the processor is further configured to: omit the transmission of feedback related to the reception of an RS-info parameter set, or omit the transmission of feedback related to the reception of an RS set, and wherein the processor is further configured to: omit the transmission of feedback related to the reception of a data decoding information parameter set, or omit the transmission of feedback related to the reception of a coded signal set.

[0289] Example 15: A wireless communication device according to any one or more of Examples 12 to 14, wherein the RS-info parameter set includes an indication that the first RS in the RS set corresponds to one of the following items: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot, and wherein the data decoding information parameter set includes an indication that the first coded signal in the coded signal set corresponds to one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0290] Example 16: A wireless communication device according to any one or more of Examples 12 to 16, wherein, in order to monitor the RS set, the processor is configured to: utilize an RS-info parameter set to receive at least one first reference signal (RS) in the RS set, wherein the at least one first RS corresponds to at least one line of sight (LoS) signal targeted at one or more receiving devices, and wherein, in order to monitor the coded signal set, the processor is configured to: utilize a data decoding information parameter set to receive at least one first coded signal in the coded signal set, wherein the at least one first coded signal includes a multipath reflection signal corresponding to at least one line of sight (LoS) signal targeted at one or more receiving devices.

[0291] Example 17: A wireless communication device according to Example 16, wherein the at least one first RS includes at least one of the following: (i) a demodulation reference signal (DMRS), (ii) a channel state information reference signal (CSI-RS), (iii) a channel state information tracking reference signal (CSI-TRS), (iv) a positioning reference signal (PRS), (v) a phase tracking reference signal (PTRS), or (vi) a sounding reference signal (SRS); and wherein the at least one first coded signal includes at least one of the following: (i) a physical downlink shared channel (PDSCH) message; (ii) a physical uplink shared channel (PUSCH) message; (iii) a physical uplink control channel (PUCCH) message; (iv) a physical downlink control channel (PDCCH) message; (v) a physical sidelink shared channel (PSSCH) message; or (vi) a physical sidelink control channel (PSCCH) message.

[0292] Example 18: A wireless communication device according to any one or more of Examples 12 to 17, wherein the RS-info parameter set includes a resource parameter set corresponding to a resource set used for the wireless communication device to monitor one or more RSs, and wherein the data decoding information includes a resource parameter set corresponding to a resource set used for the wireless communication device to monitor a coded signal.

[0293] Example 19: The wireless communication device of Example 18, wherein the resource parameter set comprises at least one of: a frequency domain (FD) attribute corresponding to the resource parameter set; or a time domain attribute (TD) corresponding to the resource parameter set.

[0294] Example 20: A wireless communication device according to Example 19, wherein the FD attributes of the resource parameter set include an indication of one or more of the following: one or more physical resource blocks (PRBs); one or more bandwidth parts (BWPs); one or more component carriers (CCs); one or more subcarriers; or at least one radio access technology (RAT).

[0295] Example 21: A wireless communication device according to any one or more of Examples 18 to 20, wherein the TD attribute of the resource parameter set includes an indication of one or more of the following: one or more symbols; one or more time slots; one or more subframes; or one or more frames.

[0296] Example 22: A wireless communication device according to any one or more of Examples 18 to 21, wherein the resource parameter set includes one or more of the following: a UE-specific identifier (ID) for identifying a demodulation reference signal (DMRS) sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to the DMRS; a comb type; a DMRS port ID; a code division multiplexing (CDM) group ID; an energy per resource element (EPRE) ratio with data symbols; or quasi-co-location (QCL) information, or parameters specifying one or more DCI formats for monitoring coded signals; parameters specifying a DCI format carried on a PSSCH; or parameters specifying an SCI carried on a PSSCH, or a radio network temporary identifier (RNTI); a scrambling ID; a frequency domain resource allocation (FDRA); a time domain resource allocation (TDRA); or a UE-specific ID for identifying a DMRS sequence.

[0297] Example 23: A wireless communication device according to any one or more of Examples 12 to 22, wherein the RS-info parameter set includes information identifying multiple resource sets, wherein a first resource set in the multiple resource sets at least partially overlaps with a second resource set in the multiple resource sets in frequency and / or time, and wherein the first resource set in the multiple resource sets corresponds to a port ID or scrambling ID that is different from the port ID or scrambling ID of the second resource set in the multiple resource sets; and wherein the data decoding information parameter set includes information identifying multiple resources, wherein a first resource set in the multiple resources at least partially overlaps with a second resource set in the multiple resources in frequency and / or time, and wherein the first resource set in the multiple resources corresponds to a port ID or scrambling ID that is different from the port ID or scrambling ID of the second resource set in the multiple resources.

[0298] Example 24: A wireless communication device according to any one or more of Examples 12 to 23, wherein the RS-info parameter set includes information related to one or more port IDs or one or more scrambling IDs of one or more RSs monitored by the device, and wherein the data decoding information parameter set includes information related to one or more port IDs or one or more scrambling IDs of encoded signals on one or more channels monitored by the device.

[0299] Example 25: An apparatus for wireless communication, comprising: a component for receiving a message by a first user equipment (UE), the message comprising at least one of: (i) a reference signal information (RS-info) parameter set relating to one or more reference signals (RS), the one or more reference signals (RS) corresponding to at least one line of sight (LoS) signal targeted at one or more other devices different from and separated from the first UE, or (ii) a data decoding information parameter set relating to data, the data being scheduled for the purpose of communicating with the one or more other devices via the at least one line of sight (LoS) signal targeted at the one or more other devices; and a component for monitoring at least one of: (i) monitoring an RS set based on the RS-info parameter set, or (ii) monitoring a coded signal set based on the data decoding information parameters.

[0300] Example 26: The apparatus according to Example 25 further includes: a component for receiving at least one of: (i) a first reference signal (RS) based on a reference signal information (RS-info) parameter set, or (ii) a first coded signal based on a data decoding information parameter; and a component for determining information related to the spatial position of an object near the first UE based at least in part on at least one of: (i) the first RS, or (ii) the first coded signal.

[0301] Example 27: An apparatus according to any one or more of Examples 25 or 26, wherein the RS-info parameter set includes an indication that the first RS in the RS set corresponds to one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot, and wherein the data decoding information parameter set includes an indication that the first coded signal in the coded signal set corresponds to one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0302] Example 28: An apparatus according to any one or more of Examples 25 to 27, wherein the RS-info parameter group includes a resource parameter set corresponding to a resource set for monitoring one or more RSs by the first UE, and wherein the data decoding information includes a resource parameter set corresponding to a resource set for monitoring a coded signal by the first UE.

[0303] Example 29: A scheduling entity for wireless communication, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor configured to: receive, via the transceiver, at least one of: (i) a reference signal information (RS-info) parameter set, comprising a resource parameter set corresponding to one or more reference signals (RS) targeted at multiple receiving devices, or (ii) a data decoding information parameter set, comprising a decoding parameter set for decoding a coded signal set sent to the multiple receiving devices via one or more coded channels; receive, via the transceiver, from a first user equipment (UE) a request for at least one of: (i) an RS-info parameter set, wherein the RS-info parameters include information related to one or more reference signals (RS) targeted at at least one second UE other than the first UE, or (ii) data decoding information parameters, wherein the data decoding information corresponds to data decoding for at least one data item scheduled for the at least one second UE; and send, via the transceiver, a message to the first UE, wherein the message includes at least one of: (i) the RS-info parameter set, or (ii) the data decoding information parameter set.

[0304] Example 30: The scheduling entity of Example 29, wherein the processor is further configured to: monitor a corresponding RS set using an RS-info parameter set; or monitor a corresponding coded signal set on one or more coded channels using a data decoding information parameter set.

[0305] Example 31: An apparatus comprising means for receiving spatial location information (e.g., ellipse coordinates) related to one or more objects from a set of entities that perform multi-node passive sensing of objects in a network environment. The apparatus further comprises means for sending transmission configuration information to the set of entities that perform multi-node passive sensing of objects in the network environment. Additionally or alternatively, the apparatus further comprises means for storing the spatial location information in a memory (e.g., a memory of a server), and the apparatus may further comprise means for fusing the spatial location information to determine a location of a potential object relative to the set of entities in the network environment.

[0306] Example 1A: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, by a user equipment (UE), a first reference signal information (RS-info) parameter set (e.g., reference signal configuration information, resource monitoring information, etc.) corresponding to a first transmitter; monitoring resources based on RS-info; receiving a first reference signal (RS) sent by the first transmitter; receiving multipath reflections of the first RS sent by the first transmitter; and determining, based on a time delay between reception of the first RS and reception of the multipath reflections of the first RS, a first ellipse information parameter set (e.g., coordinate values) corresponding to a possible position of an object.

[0307] Example 2A: The method, apparatus, system and non-transitory computer-readable medium according to Example 1A further include: receiving a second RS-info parameter set corresponding to a second transmitter by a first UE; monitoring resources based on the second RS-info parameter set corresponding to the second transmitter; receiving a second RS from the second transmitter; receiving multipath reflections of the second RS; determining a second ellipse information parameter set corresponding to a possible position of the object based on a time delay between reception of the second RS received from the second transmitter and reception of the multipath reflections of the second RS; and estimating the position of the object based at least in part on a first ellipse corresponding to the first ellipse information parameter set and a second ellipse corresponding to the second ellipse information parameter set.

[0308] Example 3A: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1A to 2A, further comprising receiving a first RS-info parameter set and / or a second RS-info parameter set from one or more base stations (BSs).

[0309] Example 4A: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 2A to 3A, wherein the second transmitter comprises one or more of: a roadside unit (RSU) and / or a data server.

[0310] Example 5A: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 4A, further comprising: receiving, by the UE, information about one or more ellipses determined by one or more other transmitters (e.g., a second transmitter, a third transmitter, and / or a fourth transmitter, etc.); and estimating the position of an object based on the first ellipse information parameter set and the one or more ellipses.

[0311] Example 6A: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 5A, further comprising: decoding one or more transport blocks (TBs) corresponding to a reference signal (RS) sent by a transmitter; decoding one or more TBs of multipath reflections of the RS sent by the transmitter; and determining a time delay based on the decoded one or more TBs of the RS sent by the transmitter and the one or more TBs of multipath reflections of the RS sent by the transmitter.

[0312] Example 7A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 6A, wherein receiving RS-info corresponding to a first transmitter by a UE includes: receiving an indication that the UE omits HARQ-ACK feedback associated with receiving a reference signal (RS) corresponding to a first RS-info parameter set.

[0313] Example 8A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 7A, wherein receiving, by a UE, a first RS-info parameter set corresponding to a first transmitter includes receiving one or more of: radio resource control (RRC) configuration information; one or more media access control (MAC) control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a dedicated physical downlink shared channel (PDSCH) message; a dedicated physical sidelink shared channel (PDSCH) message; a message sent using a dedicated physical (PHY) layer channel (e.g., a PHY RS-info indication channel (PRICH)); and / or a control resource set (CORESET) identifier (ID) and a corresponding search space (SS).

[0314] Example 9A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 8A, wherein receiving RS-info corresponding to a transmitter by a UE includes: receiving an indication that the RS-info corresponds to a reference signal (RS) sent by the transmitter during an uplink (UL) time slot or one of a sidelink (SL) time slot.

[0315] Example 10A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 9A, wherein receiving RS-info corresponding to a transmitter by a UE includes: receiving an indication that the RS-info corresponds to a reference signal (RS) sent to the transmitter during a downlink (DL) time slot.

[0316] Example 11A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 10A, wherein the reference signal (RS) corresponding to RS-info includes: a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH); a DMRS for a physical downlink shared channel (PDSCH), a DMRS for a physical uplink control channel (PUCCH), and a DMRS for a physical downlink control channel (PDCCH); a channel state information (CSI)-RS; a CSI tracking reference signal (CSI-TRS); a positioning reference signal (PRS); a phase tracking reference signal (PTRS); or a sounding reference signal (SRS).

[0317] Example 12A: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1A to 11A, wherein the RS-info includes: an RS pattern corresponding to a combination of frequency domain resources and time domain resources.

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

[0319] Example 14A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 13A, wherein the RS-info includes one or more of: a UE-specific ID for identifying a demodulation reference signal (DMRS)-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to the DMRS; a comb type used by the transmitter; a DMRS port ID; a code division multiplexing (CDM)-group ID corresponding to the transmitter; an energy per resource element (EPRE) ratio with data symbols; and / or quasi-co-location (QCL) information.

[0320] Example 15A: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1A to 14A, wherein RS-info includes one or more of: a plurality of DMRS port IDs; and / or a plurality of DMRS scrambling IDs.

[0321] Example 16A: A method, apparatus, system, and non-transitory computer-readable medium, comprising: receiving, by a scheduling entity, reference signal information (RS-info) corresponding to one or more transmitters; receiving, by the scheduling entity, a request for RS-info corresponding to one or more nearby transmitters from a user equipment (UE); and sending, to the UE, RS-info corresponding to the one or more transmitters in response to the request for RS-info corresponding to the one or more nearby transmitters from the UE.

[0322] Example 17A: The method, apparatus, system and non-transitory computer-readable medium according to any one or more of Examples 1A to 15A, further comprising: receiving, by a scheduling entity, reference signal information (RS-info) corresponding to one or more transmitters; receiving, by the scheduling entity, a request for RS-info corresponding to one or more nearby transmitters from a user equipment (UE); and sending, to the UE, the RS-info corresponding to the one or more transmitters in response to the request for RS-info corresponding to the one or more nearby transmitters from the UE.

[0323] Example 18A: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1A to 17A, further comprising: monitoring resources based on RS-info corresponding to one or more transmitters; receiving RS sent by each of the one or more transmitters; receiving multipath reflections of the RS sent by each of the one or more transmitters; determining one or more ellipses corresponding to the possible location of the object based on a time delay between reception of the RS sent by each of the one or more transmitters and reception of the multipath reflections of the RS sent by each of the one or more transmitters; and determining the location of the object based on the first ellipse and the one or more ellipses.

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

[0325] Example 20A: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, by a user equipment (UE), a message including reference signal (RS) information (RS-info) related to one or more reference signals (RS) targeted at a receiver other than the UE; and monitoring the one or more RSs based on the RS-Info.

[0326] Example 21A: The method, apparatus, system, and non-transitory computer-readable medium of Example 20A, further comprising: receiving an RS based on RS-info; and determining information related to a spatial position of an object close to the UE through passive radar sensing based on the received RS.

[0327] Example 22A: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 20A to 21A, further comprising omitting transmission of HARQ-ACK feedback related to RS-info.

[0328] Example 23A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 22A, wherein the message includes one or more of: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message sent using a dedicated physical (PHY) layer channel; and / or a control resource set (CORESET) identifier (ID) and a corresponding search space (SS).

[0329] Example 24A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 23A, wherein the RS-info includes an indication that the RS-info corresponds to an RS sent using one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0330] Example 25A: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 24A, further comprising: receiving RS based on RS-info, wherein the RS is one of: a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH); a DMRS for a physical downlink shared channel (PDSCH), a DMRS for a physical uplink control channel (PUCCH), a DMRS for a physical downlink control channel (PDCCH); a channel state information (CSI)-RS; a CSI tracking reference signal (CSI-TRS); a positioning reference signal (PRS); a phase tracking reference signal (PTRS); and / or a sounding reference signal (SRS).

[0331] Example 26A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 25A, wherein the information related to the one or more RSs includes information related to a resource set for the UE to monitor the one or more RSs.

[0332] Example 27A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 26A, wherein the information related to a resource set of one or more RSs monitored by a UE includes at least one of: frequency domain (FD) properties of the resource set; and / or time domain (TD) properties of the resource set.

[0333] Example 28A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 27A, wherein the frequency domain attributes of the resource set include an indication of one or more of: one or more physical resource blocks (PRBs); one or more bandwidth parts (BWPs); one or more component carriers (CCs); one or more subcarrier components; and / or at least one radio access technology (RAT).

[0334] Example 29A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 28A, wherein the time domain attributes of the resource set include an indication of one or more of: one or more symbols; one or more time slots; one or more subframes; and / or one or more frames.

[0335] Example 30A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 29A, wherein information related to a resource set of one or more RSs monitored by a UE includes: frequency domain attributes of the resource set; and time domain attributes of the resource set.

[0336] Example 31A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 30A, wherein information related to resource sets of one or more RSs monitored by a UE includes at least one of: frequency domain attributes of each resource set in a plurality of resource sets including the resource set; or time domain attributes of each resource set in a plurality of resource sets including the resource set.

[0337] Example 32A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 31A, wherein at least one of the multiple resource sets overlaps in frequency and / or time with at least one other of the multiple resource sets.

[0338] Example 33A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 32A, wherein the information related to one or more RSs includes one or more resource parameters corresponding to resources monitored by the UE for the one or more RSs.

[0339] Example 34A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 33A, wherein one or more resource parameters corresponding to resources of one or more RSs monitored by a UE include one or more of: a UE-specific identifier (ID) for identifying a demodulation reference signal (DMRS) sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to the DMRS; a comb type corresponding to one or more RSs; a DMRS port ID; a code division multiplexing (CDM)-group ID corresponding to one or more RSs; an energy per resource element (EPRE) ratio with data symbols; or quasi-co-location (QCL) information.

[0340] Example 35A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 34A, wherein the information related to one or more RSs includes information related to one or more port IDs or one or more scrambling IDs of the RSs monitored by the UE.

[0341] Example 36A: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 35A, wherein the information related to one or more RSs includes information identifying multiple resource sets, wherein a first resource set in the multiple resource sets at least partially overlaps with a second resource set in the multiple resource sets in frequency and / or time, and wherein the first resource set corresponds to a port ID or scrambling ID that is different from the port ID or scrambling ID of the second resource set.

[0342] Example 37A: A method, apparatus, system, and non-transitory computer-readable medium, wherein the one or more RSs are not used for any one or more of: reference for transmission or reception of information by the UE, channel characterization by the UE, or synchronization by the UE.

[0343] Example 38A: A method, apparatus, system, and non-transitory computer-readable medium, comprising: receiving, by a scheduling entity, RS-info including information related to one or more reference signals (RSs); receiving, by the scheduling entity, a request from a user equipment (UE) for RS-info related to one or more RSs targeted at a receiver of the UE; and sending, in response to the request from the UE, a message including the RS-info to the UE.

[0344] Example 39A: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20A to 37A, further comprising: receiving, by a scheduling entity, reference signal (RS) information including information related to one or more reference signals (RS); receiving, by the scheduling entity, a request for RS-info related to one or more RSs targeted at a receiver different from the UE from a user equipment (UE); and sending, in response to the request from the UE, a message including RS-info to the UE.

[0345] Example 40A The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 20A to 39A, further comprising: monitoring, by the scheduling entity, the RS based on the RS-info.

[0346] Example 1B: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, by a user equipment (UE), data decoding information corresponding to a transmitter; monitoring resources based on the data decoding information; receiving a coded signal sent by the transmitter, the coded signal comprising one or more coded packets; receiving multipath reflections of the coded signal sent by the transmitter; and determining a first ellipse corresponding to a possible location of an object based on a time delay between reception of the coded signal and reception of the multipath reflections of the coded signal.

[0347] Example 2B: The method, apparatus, system, and non-transitory computer-readable medium according to Example 1B further include: receiving, by the UE, data decoding information corresponding to a second transmitter; monitoring resources based on the data decoding information corresponding to the second transmitter; receiving a coded signal from the second transmitter; receiving multipath reflections of the coded signal from the second transmitter; determining a second ellipse corresponding to a possible position of the object based on a time delay between reception of the coded signal received from the second transmitter and reception of the multipath reflections of the coded signal received from the second transmitter; and estimating the position of the object based on the first ellipse and the second ellipse.

[0348] Example 3B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 2B further includes: receiving data decoding information corresponding to the first transmitter and / or the second transmitter from one or more base stations (BSs).

[0349] Example 4B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 2B to 3B, wherein the second transmitter comprises one or more of: a roadside unit (RSU) and / or a data server.

[0350] Example 5B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 4B further include: receiving, by the UE, information about one or more ellipses determined by one or more transmitters; and estimating the position of the object based on the first ellipse and the one or more ellipses determined by the one or more transmitters.

[0351] Example 6B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 5B further include: receiving, by the UE, reference signal (RS) configuration information corresponding to a transmitter; monitoring resources based on RS-info; receiving the RS sent by the transmitter; receiving multipath reflections of the RS sent by the transmitter; and determining a second ellipse corresponding to a possible position of the object based on a time delay between reception of the RS and reception of the multipath reflections of the RS.

[0352] Example 7B: A method, apparatus, system, and non-temporary computer-readable medium according to any one or more of Examples 1B to 6B, wherein receiving data decoding information corresponding to a transmitter by a UE includes: receiving an indication that the UE omits HARQ-ACK feedback related to receiving a coded signal corresponding to the data decoding information.

[0353] Example 8B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 7B, wherein receiving data decoding information corresponding to a transmitter by a UE includes: receiving one or more of: radio resource control (RRC) configuration information; one or more MAC control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message sent using a dedicated physical (PHY) layer channel; or a control resource set (CORESET) identifier (ID) and a corresponding search space (SS).

[0354] Example 9B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 8B, wherein receiving data decoding information corresponding to a transmitter by a first UE includes: receiving an indication that the data decoding information corresponds to a coded signal sent by the transmitter using one of an uplink (UL) time slot or a sidelink (SL) time slot.

[0355] Example 10B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 9B, wherein receiving data decoding information corresponding to a transmitter by a UE includes: receiving an indication that the data decoding information corresponds to a coded signal sent to the transmitter using a downlink (DL) time slot.

[0356] Example 11B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 10B, wherein the encoded signal corresponding to the data decoding information includes: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.

[0357] Example 12B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1B to 11B, wherein the data decoding information includes a pattern corresponding to a combination of frequency domain resources and time domain resources.

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

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

[0360] Example 15B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1 to 14, wherein the data decoding information includes one or more of: multiple DMRS port identifiers (IDs); or multiple DMRS scrambling IDs.

[0361] Example 16B: A method, apparatus, system, and non-transitory computer-readable medium, comprising: receiving, by a scheduling entity, data decoding information corresponding to one or more transmitters; receiving, by the scheduling entity, a request for data decoding information corresponding to one or more nearby transmitters from a user equipment (UE); and sending, to the UE, data decoding information corresponding to the one or more transmitters in response to the request for data decoding information corresponding to the one or more nearby transmitters from the UE.

[0362] Example 17B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 15B further include: receiving, by a scheduling entity, data decoding information corresponding to one or more transmitters; receiving, by the scheduling entity, a request for data decoding information corresponding to one or more nearby transmitters from a user equipment (UE); and sending, to the UE, data decoding information corresponding to the one or more transmitters in response to the request for data decoding information corresponding to the one or more nearby transmitters from the UE.

[0363] Example 18B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1B to 17B further include: monitoring resources based on data decoding information corresponding to one or more transmitters; receiving a coded signal sent by each of the one or more transmitters, the coded signal comprising one or more coded packets; receiving multipath reflections of the coded signal sent by each of the one or more transmitters; determining one or more ellipses corresponding to a possible location of an object based on a time delay between receipt of the coded signal sent by each of the one or more transmitters and receipt of the multipath reflections of the coded signal sent by each of the one or more transmitters; and estimating the location of the object based on the first ellipse and each of the one or more ellipses.

[0364] Example 19B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1B to 18B further include: receiving, by a scheduling entity, information about one or more ellipses determined by one or more receivers including a UE; and estimating the position of an object based on the one or more ellipses.

[0365] Example 20B: A method, apparatus, system, and non-transitory computer-readable medium, comprising: receiving, by a user equipment (UE), a message comprising data decoding information relating to data that is not scheduled for the purpose of communicating with the UE; and monitoring a coded signal based on the data decoding information.

[0366] Example 21B: The method, apparatus, system, and non-transitory computer-readable medium of Example 20B further include: receiving a coded signal based on the data decoding information; and determining information related to the spatial position of an object near the UE through passive radar sensing based on the received coded signal.

[0367] Example 22B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 21B, wherein the data decoding information includes an indication allowing the UE to omit HARQ-ACK feedback related to receiving one or both of a message including the data decoding information or a coded signal corresponding to the data decoding information.

[0368] Example 23B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 22B, wherein the message including data decoding information includes one or more of: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message sent using a dedicated physical (PHY) layer channel; or a control resource set (CORESET) identifier (ID) and a corresponding search space (SS).

[0369] Example 24B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 23B, wherein the data decoding information includes an indication that corresponding data for decoding is sent using one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0370] Example 25B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 20B to 24B further includes receiving a coded signal based on data decoding information, wherein the coded signal is one of: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.

[0371] Example 26B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 20B to 25B, wherein the data decoding information includes information related to a set of resources for monitoring coded signals by the UE.

[0372] Example 27B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 26B, wherein the information related to the resource set for monitoring the coded signal by the UE includes at least one of: frequency domain properties of the resource set; or time domain properties of the resource set.

[0373] Example 28B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 27B, wherein the frequency domain attributes of the resource set include an indication of one or more of: one or more physical resource blocks (PRBs); one or more bandwidth parts (BWPs); one or more component carriers (CCs); one or more subcarrier components; and / or at least one radio access technology (RAT).

[0374] Example 29B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 28B, wherein the time domain attributes of the resource set include an indication of one or more of: one or more symbols; one or more time slots; one or more subframes; or one or more frames.

[0375] Example 30B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 29B, wherein the information related to the resource set for monitoring the coded signal by the UE includes: frequency domain properties of the resource set; and time domain properties of the resource set.

[0376] Example 31B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 30B, wherein information related to a resource set for a coded signal on one or more channels monitored by a UE includes: frequency domain properties of each resource set in a plurality of resource sets comprising the resource set; and time domain properties of each resource set in a plurality of resource sets comprising the resource set.

[0377] Example 32B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 31B, wherein at least one of the multiple resource sets overlaps in frequency and / or time with at least one other of the multiple resource sets.

[0378] Example 33B: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 20B to 32B, wherein the data decoding information includes one or more resource parameters corresponding to resources monitored by the UE for the coded signal.

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

[0380] Example 35B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 34B, wherein the information related to one or more channels includes information related to one or more port IDs or one or more scrambling IDs of coded signals monitored by the UE on the one or more channels.

[0381] Example 36B: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 35B, wherein the information related to one or more channels includes information identifying multiple resource sets, wherein a first resource set in the multiple resource sets at least partially overlaps with a second resource set in the multiple resource sets in frequency and / or time, and wherein the first resource set corresponds to a port ID or scrambling ID that is different from the port ID or scrambling ID of the second resource set.

[0382] Example 37B: A method, apparatus, system, and non-transitory computer-readable medium, comprising: receiving data decoding information by a scheduling entity, the data decoding information including information related to data decoding of one or more channels; receiving a request by the scheduling entity from a user equipment (UE) for data decoding information related to data decoding of one or more channels, the one or more channels not being directed to any one or more of: a reference to the sending or receiving of information by the UE, a channel characterization by the UE, or synchronization by the UE; and sending a message including the data decoding information to the UE in response to the request from the UE.

[0383] Example 38B: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 20B to 36B further include: receiving, by a scheduling entity, data decoding information including information related to data decoding of one or more channels; receiving, by the scheduling entity, a request for data decoding information related to data decoding of one or more channels from a user equipment (UE), the one or more channels not being directed to any one or more of: a reference to the sending or receiving of information by the UE, a channel characterization by the UE, or synchronization by the UE; and sending, in response to the request from the UE, a message including the data decoding information to the UE.

[0384] Example 39B: According to any one or more of the methods, apparatus, systems, and non-transitory computer-readable media of Examples 20B to 38B, the scheduling entity monitors the coded signals on one or more channels based on the data decoding information.

[0385] Example 1C: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, by a user equipment (UE), a message including reference signal information (RS-info) related to one or more reference signals (RS) targeted at a receiver other than the UE; and monitoring, by the UE, the one or more RSs based on the RS-info.

[0386] Example 2C: The method, apparatus, system, and non-transitory computer-readable medium of Example 1C further comprising: receiving an RS based on RS-info; and determining information related to a spatial position of an object close to the UE through passive radar sensing based on the received RS.

[0387] Example 3C: The method, apparatus, system, and non-transitory computer-readable medium of any one or more of Examples 1C to 2C, further comprising omitting transmission of HARQ-ACK feedback related to RS-info.

[0388] Example 4C: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1C to 3C, wherein the message includes one or more of: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message sent using a dedicated physical (PHY) layer channel; or a control resource set (CORESET) ID and a corresponding search space (SS).

[0389] Example 5C: A method, apparatus, system, and non-transitory computer-readable medium according to Examples 1C to 4C, wherein the RS-info includes an indication that the RS-info is associated with an RS transmitted using one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0390] Example 6C: The methods, apparatus, systems, and non-transitory computer-readable media of Examples 1C to 5C further include receiving RS based on RS-info, wherein the RS is one of: a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH); a DMRS for a physical downlink shared channel (PDSCH), a DMRS for a physical uplink control channel (PUCCH), a DMRS for a physical downlink control channel (PDCCH); a channel state information (CSI)-RS; a CSI tracking reference signal (CSI-TRS); a positioning reference signal (PRS); a phase tracking reference signal (PTRS); or a sounding reference signal (SRS).

[0391] Example 7C: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1C to 6C, wherein the information related to one or more RSs includes information related to a set of resources for the UE to monitor the one or more RSs.

[0392] Example 8C: The method, apparatus, system, and non-transitory computer-readable medium of Example 7C, wherein the information related to a resource set of one or more RSs monitored by a UE includes at least one of: frequency domain properties of the resource set; or time domain properties of the resource set.

[0393] Example 9C: A method, apparatus, system, and non-transitory computer-readable medium according to the method described in Example 8C, wherein the frequency domain attributes of the resource set include an indication of one or more of: one or more physical resource blocks (PRBs); one or more bandwidth parts (BWPs); one or more component carriers (CCs); one or more subcarrier components; and / or at least one radio access technology (RAT).

[0394] Example 10C: The method, apparatus, system, and non-transitory computer-readable medium of Example 8C, wherein the time domain attributes of the resource set include an indication of one or more of: one or more symbols; one or more time slots; one or more subframes; or one or more frames.

[0395] Example 11C: The method, apparatus, system, and non-transitory computer-readable medium of Example 8C, wherein the information related to resource sets for monitoring one or more RSs by the UE includes: frequency domain properties of the resource sets; and time domain properties of the resource sets.

[0396] Example 12C: A method, apparatus, system, and non-transitory computer-readable medium according to Example 8C, wherein information related to resource sets of one or more RSs monitored by a UE includes at least one of: frequency domain properties of each resource set in a plurality of resource sets including the resource sets; and / or time domain properties of each resource set in a plurality of resource sets including the resource sets.

[0397] Example 13C: The method, apparatus, system, and non-transitory computer-readable medium of Example 12C, wherein at least one of the plurality of resource sets overlaps in frequency and / or time with at least one other of the plurality of resource sets.

[0398] Example 14C: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1C to 13C, wherein the information related to one or more RSs includes one or more resource parameters corresponding to resources monitored by the UE for the one or more RSs.

[0399] Example 15C: A method, apparatus, system, and non-transitory computer-readable medium according to Example 14C, wherein one or more resource parameters corresponding to resources of one or more RSs monitored by a UE include one or more of the following: a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to the DMRS; a comb type corresponding to one or more RSs; a DMRS port ID; a code division multiplexing (CDM)-group ID associated with one or more RSs; an energy per resource element (EPRE) ratio with data symbols; or quasi-co-location (QCL) information.

[0400] Example 16C: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1C to 15C, wherein the information related to one or more RSs includes information related to one or more port IDs or one or more scrambling IDs of the RSs monitored by the UE.

[0401] Example 17C: A method, apparatus, system, and non-transitory computer-readable medium according to Example 16C, wherein the information related to one or more RSs includes information identifying multiple resource sets, wherein a first resource set in the multiple resource sets at least partially overlaps with a second resource set in the multiple resource sets in frequency and / or time, and wherein the first resource set is associated with a port ID or scrambling ID that is different from the port ID or scrambling ID of the second resource set.

[0402] Example 18C: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1C to 17C, wherein the one or more RSs are not used for any one or more of: reference to the sending or receiving of information by the UE, channel characterization by the UE, or synchronization by the UE.

[0403] Example 19C: An apparatus comprising means for sharing transmission configuration information to a first user equipment (UE), the first UE utilizing the transmission configuration information to perform multi-node passive sensing in a network environment. The transmission configuration information transmitting means is configured to receive a specific set of reference signals as reflection signals, the reflection signals corresponding to line-of-sight (LoS) signals transmitted between two other entities in the network environment. In some examples, the transmission configuration information transmitting means is configured to decode coded data transmitted between the two other entities in the network environment (e.g., to perform decoding of less than a complete set of coded data items targeted at another UE different from the first UE).

[0404] Example 1D: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, by a first user equipment (UE), a message including data decoding information relating to data that is not scheduled for a purpose of communicating with the first UE (e.g., for the purpose of communicating with a second UE in a network environment); and monitoring a coded signal based on the data decoding information.

[0405] Example 2D: The method, apparatus, system, and non-transitory computer-readable medium of Example 1D further include: receiving a coded signal based on data decoding information; and determining information related to the spatial position of an object near the UE through passive radar sensing based on the received coded signal.

[0406] Example 3D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of the methods of Examples 1D or 2D, wherein the data decoding information includes an indication allowing the UE to omit HARQ-ACK feedback associated with receiving a message including the data decoding information or one or both of the encoded signals associated with the data decoding information.

[0407] Example 4D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of the methods of Examples 1D to 3D, wherein the message including data decoding information includes one or more of: a radio resource control (RRC) configuration message; one or more MAC control elements (MAC-CE); downlink control information (DCI); sidelink control information (SCI); a dedicated physical downlink shared channel (PDSCH) message; a physical sidelink shared channel (PSSCH) message; a message sent using a dedicated physical (PHY) layer channel; or a control resource set (CORESET) ID and a corresponding search space (SS).

[0408] Example 5D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1D to 3D, wherein the data decoding information includes an indication of sending the corresponding data using one of the following: a downlink (DL) time slot, an uplink (UL) time slot, or a sidelink (SL) time slot.

[0409] Example 6D: The method, apparatus, system, and non-transitory computer-readable medium according to any one or more of the methods of Examples 1D to 3D further include receiving a coded signal based on data decoding information, wherein the coded signal is one of: a physical downlink shared channel (PDSCH) message; a physical uplink shared channel (PUSCH) message; a physical uplink control channel (PUCCH) message; a physical downlink control channel (PDCCH) message; a physical sidelink shared channel (PSSCH) message; or a physical sidelink control channel (PSCCH) message.

[0410] Example 7D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of Examples 1D to 3D, wherein the data decoding information includes information related to a resource set for monitoring the coded signal by the UE.

[0411] Example 8D: The method, apparatus, system, and non-transitory computer-readable medium of Example 7D, wherein the information related to the resource set for monitoring the coded signal by the UE includes at least one of: frequency domain properties of the resource set; or time domain properties of the resource set.

[0412] Example 9D: A method, apparatus, system, and non-transitory computer-readable medium according to Example 8D, wherein the frequency domain attributes of the resource set include an indication of one or more of: one or more physical resource blocks (PRBs); one or more bandwidth parts (BWPs); one or more component carriers (CCs); one or more subcarrier components; and / or at least one radio access technology (RAT).

[0413] Example 10D: The method, apparatus, system, and non-transitory computer-readable medium of Example 8D, wherein the time domain attributes of the resource set include an indication of one or more of: one or more symbols; one or more time slots; one or more subframes; or one or more frames.

[0414] Example 11D: The method, apparatus, system, and non-transitory computer-readable medium of Example 8D, wherein the information related to the resource set for the UE to monitor the coded signal includes: frequency domain properties of the resource set; and time domain properties of the resource set.

[0415] Example 12D: A method, apparatus, system, and non-transitory computer-readable medium according to Example 8D, wherein the information relating to a resource set for a coded signal on one or more channels monitored by a UE includes: frequency domain properties of each resource set in a plurality of resource sets comprising the resource set; and / or time domain properties of each resource set in a plurality of resource sets comprising the resource set.

[0416] Example 13D: The method, apparatus, system, and non-transitory computer-readable medium of Example 12D, wherein at least one of the plurality of resource sets overlaps in frequency and / or time with at least one other of the plurality of resource sets.

[0417] Example 14D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of the methods of Examples 1D to 13D, wherein the data decoding information includes one or more resource parameters corresponding to resources monitored by the UE for the encoded signal.

[0418] Example 15D: A method, apparatus, system, and non-transitory computer-readable medium according to Example 14D, wherein one or more resource parameters corresponding to resources for monitoring a coded signal by a UE include one or more of the following: a radio network temporary identifier (RNTI); a scrambling ID; a frequency domain resource allocation (FDRA); a time domain resource allocation (TDRA); a UE-specific ID for identifying a DMRS-sequence; at least one orthogonal frequency division multiplexing (OFDM) symbol index corresponding to a DMRS; a comb type corresponding to one or more coded signals; a DMRS port ID; a code division multiplexing (CDM)-group ID associated with one or more channels; an energy per resource element (EPRE) ratio with data symbols; quasi-co-location (QCL) information; parameters specifying one or more DCI formats to monitor the coded signal; parameters specifying a DCI format carried on a PSSCH; or parameters specifying an SCI carried on a PSSCH.

[0419] Example 16D: A method, apparatus, system, and non-transitory computer-readable medium according to any one or more of the methods of Examples 1D to 15D, wherein the information related to one or more channels includes information related to one or more port IDs or one or more scrambling IDs for a UE to monitor coded signals on one or more channels.

[0420] Example 17D: A method, apparatus, system, and non-transitory computer-readable medium according to Example 16D, wherein the information related to one or more channels includes information identifying multiple resource sets, wherein a first resource set in the multiple resource sets at least partially overlaps with a second resource set in the multiple resource sets in frequency and / or time, and wherein the first resource set is associated with a port ID or scrambling ID that is different from a port ID or scrambling ID of the second resource set.

[0421] Example 18D: An apparatus includes means for receiving transmission configuration information for multi-node passive sensing of an object in a network environment. The transmission configuration information transmitting means is configured to cause the apparatus to receive a specific set of reference signals as reflection signals corresponding to line-of-sight (LoS) signals transmitted between two other entities in the network environment. In some examples, the transmission configuration information includes means for decoding coded data transmitted on a coded channel (e.g., PSSCH, PSCCH, etc.) between the two other entities.

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

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

[0424] Within this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any embodiment or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other—even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the functions described in this disclosure to be performed, as well as software implementations of information and instructions that, when executed by a processor, enable the functions described in this disclosure to be performed, without limitation to types of electronic circuitry.

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

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

[0427] The previous description is provided to enable anyone skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but rather to the full scope consistent with the language of the claims, wherein, unless otherwise specified, references to elements in the singular are not intended to mean "one and only one," but rather "one or more." Unless otherwise specified, the term "some" refers to one or more. A phrase referring to "at least one" of a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. A method of wireless communication, comprising: A message including at least one of the following is received by a first user equipment UE: (i) reference signal information RS-info indicating a set of resource parameters associated with a reference signal RS set, the reference signal RS set corresponding to at least one line-of-sight (LoS) signal, the LoS signal being received by at least one entity other than the first UE, or (ii) data decoding information indicating a first data decoding parameter set configured for at least partially decoding a set of coded data items, the set of coded data items corresponding to a coded signal set configured for full decoding by a second UE via a second data decoding parameter set different from the first data decoding parameter set; as well as The first UE performs at least one of the following: (i) monitor the RS set based on RS-info, or (ii) Monitoring a set of coded signals on one or more channels based on the data decoding information.

2. The method according to claim 1, further comprising: Do at least one of the following: (i) Receive RS set based on RS-info, or (ii) receiving a coded signal set based on the data decoding information; as well as Determining information about a spatial location of an object proximate to the first UE based on at least one of the following: (i) a coded signal set, or (ii) RS set.

3. The method according to claim 1, further comprising: Omitting the transmission of hybrid automatic repeat request (HARQ) feedback associated with receiving one or more of the following: (i) RS-info, (ii) RS set received using RS-info, (iii) data decoding information, or (iv) Coded signal set.

4. The method according to claim 3, further comprising: receiving a second RS set, the second RS set including at least one line-of-sight LoS signal targeted at the first UE and at least one corresponding reflected signal; as well as One or more feedback messages are sent indicating receipt of the second set of RSs.

5. The method according to claim 1, wherein The message includes one or more of the following: Radio Resource Control RRC configuration message; One or more medium access control MAC control elements MAC-CE; Downlink control information DCI; Physical Downlink Shared Channel PDSCH message; Side link control information SCI; Physical side link shared channel PSSCH message; Messages sent using physical PHY layer channels; Control resource set CORESET identifier ID and corresponding search space SS; A physical RS-info channel including RS-info; a physical data decoding channel including data decoding information; or Physical transmission configuration channel, including data decoding information and RS-info.

6. The method according to claim 1, in, RS-info indicates that at least one RS of the reference signal RS set corresponds to at least one first time slot, and The data decoding information indicates that at least one coded signal in the coded signal set corresponds to at least one first time slot or at least one second time slot.

7. The method according to claim 1, in, RS-info-based monitoring of RS sets includes: Utilize RS-info to determine a set of resource elements to monitor at least one of the following: (i) Demodulation Reference Signal (DMRS), (ii) Channel State Information Reference Signal (CSI-RS), (iii) Channel State Information Tracking Reference Signal (CSI-TRS), (iv) Positioning Reference Signal (PRS), (v) Phase Tracking Reference Signal PTRS, or (vi) Sounding Reference Signal (SRS); and The step of monitoring the coded signal set based on the data decoding information includes: and utilizing the data decoding information to decode an encoded message sent via at least one of: (i) Physical Downlink Shared Channel PDSCH, (ii) Physical Downlink Control Channel PDCCH, (iii) Physical Uplink Shared Channel PUSCH, (iv) Physical Uplink Control Channel PUCCH, (v) Physical Sidelink Shared Channel PSSCH, or (vi) Physical Sidelink Control Channel PSCCH.

8. The method according to claim 1, in, The resource parameter set includes at least one of the following: (i) indicating a frequency domain FD attribute of a resource parameter set for monitoring by the first UE; or (ii) Indicates the time domain TD attribute of the resource parameter set for the first UE to monitor.

9. The method according to claim 8, wherein The FD attributes of a resource parameter set include indications of one or more of the following: One or more physical resource blocks (PRBs), One or more bandwidth parts BWP, One or more component carriers CC, One or more subcarriers, or At least one radio access technology, RAT.

10. The method according to claim 8, wherein The TD attributes of a resource parameter set include indications of one or more of the following: One or more symbols, One or more time slots, One or more subframes, or One or more frames.

11. The method according to claim 1, in, RS-info includes information related to one or more port IDs or one or more scrambling IDs for the first UE to monitor the RS set, and The data decoding information includes information related to one or more port IDs or one or more scrambling IDs used for the first UE to monitor a set of coded signals on one or more channels.

12. A wireless communication device comprising: transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, the processor configured to: Receiving, via the transceiver, a message comprising at least one of: (i) a reference signal information (RS-info) parameter set associated with one or more reference signals (RS), the one or more RS corresponding to at least one line-of-sight (LoS) signal targeted for reception by one or more receiving devices other than the wireless communication device, or (ii) a set of data decoding information parameters relating to data scheduled for communication with one or more receiving devices via at least one line-of-sight (LoS) signal; and Use the transceiver to do at least one of the following: (i) monitor the reference signal transmission set based on the RS-info parameter set, or (ii) Monitoring the coded data signal set based on the data decoding information parameter set.

13. The wireless communication device according to claim 12, in, To monitor the reference signal transmission set, the processor is configured to: Using the RS-info parameter set to receive the first reference signal RS in the reference signal transmission set, and Wherein, in order to monitor the set of coded data signals, the processor is configured to: receiving a first coded signal using a data decoding information parameter set; and Information related to a spatial location of an object proximate to the wireless communication device is determined based on the first coded signal.

14. The wireless communication device according to claim 12, wherein: The RS-info parameter set includes an indication that the first reference signal corresponds to a side link SL slot.

15. The wireless communication device according to claim 12, in, The processor is also configured to: omitting transmission of feedback associated with reception of an RS-info parameter set, or omitting transmission of feedback associated with reception of a reference signal transmission set, and The processor is further configured to: Transmission of feedback related to reception of a data decoding information parameter set is omitted, or transmission of feedback related to reception of a coded signal set is omitted.

16. The wireless communication device according to claim 12, in, To monitor the reference signal transmission set, the processor is configured to: receiving at least one first reference signal (RS) in a reference signal transmission set using an RS-info parameter set, wherein the at least one first RS corresponds to at least one LoS signal, and In order to monitor the coded signal set, the processor is configured to: At least one first coded signal in the coded signal set is received using a data decoding information parameter set, wherein the at least one first coded signal includes a multipath reflection signal.

17. The wireless communication device according to claim 16, in, The at least one first RS includes at least one of the following: (i) Demodulation Reference Signal (DMRS), (ii) Channel State Information Reference Signal (CSI-RS), (iii) Channel State Information Tracking Reference Signal (CSI-TRS), (iv) Positioning Reference Signal (PRS), (v) Phase Tracking Reference Signal PTRS, or (vi) Sounding Reference Signal SRS; as well as The at least one first coded signal includes at least one of the following: (i) Physical Downlink Shared Channel (PDSCH) message; (ii) Physical Uplink Shared Channel (PUSCH) message; (iii) Physical Uplink Control Channel (PUCCH) message; (iv) Physical Downlink Control Channel (PDCCH) message; (v) Physical Sidelink Shared Channel (PSSCH) message; or (vi) Physical Sidelink Control Channel PSCCH message.

18. The wireless communication device according to claim 12, in, The RS-info parameter set includes a resource parameter set corresponding to a resource set for monitoring by the wireless communication device, and The data decoding information includes a resource parameter set corresponding to a resource set of the coded signal.

19. The wireless communication device according to claim 18, wherein The message includes at least one of the following: Frequency domain FD properties; or Time domain TD attributes.

20. The wireless communication device according to claim 19, wherein The FD attributes include an indication of one or more of: one or more physical resource blocks, PRBs; one or more bandwidth parts, BWPs; one or more component carriers, CCs; one or more subcarriers; or at least one radio access technology, RAT.

21. The wireless communication device according to claim 19, wherein The TD attribute includes an indication of one or more of: one or more symbols; one or more time slots; one or more subframes; or one or more frames.

22. The wireless communication device of claim 18, wherein: A resource parameter set includes one or more of the following: UE-specific ID for identifying a demodulation reference signal (DMRS) sequence; at least one OFDM symbol index corresponding to the DMRS; comb type; DMRS port ID; code division multiplexing (CDM) group ID; energy per resource element (EPRE) ratio with data symbols; or quasi-co-site QCL information, or Specify one or more DCI formats to monitor the parameters of a coded signal; specify the parameters of a DCI format carried on the PSSCH; or specify the parameters of an SCI carried on the PSSCH, or Radio Network Temporary Identifier (RNTI); scrambling ID; frequency domain resource allocation (FDRA); time domain resource allocation (TDRA); or UE-specific ID for identifying a DMRS sequence.

23. The wireless communication device according to claim 12, in, The RS-info parameter set includes information identifying a plurality of resource sets, wherein a first resource set in the plurality of resource sets at least partially overlaps with a second resource set in the plurality of resource sets in frequency and / or time, and wherein the first resource set in the plurality of resource sets corresponds to a port ID or a scrambling ID that is different from a port ID or a scrambling ID of the second resource set in the plurality of resource sets; and wherein the data decoding information parameter set includes information identifying a plurality of resources, wherein a first set of resources among the plurality of resources at least partially overlaps with a second set of resources among the plurality of resources in frequency and / or time, and wherein the first set of resources among the plurality of resources corresponds to a port ID or a scrambling ID that is different from a port ID or a scrambling ID of the second set of resources among the plurality of resources.

24. The wireless communication device according to claim 12, in, The RS-info parameter set includes information related to one or more port IDs or one or more scrambling IDs for the wireless communication device to monitor one or more RSs, and The data decoding information parameter set includes information related to one or more port IDs or one or more scrambling IDs for the wireless communication device to monitor data, wherein the data is scheduled for communication with one or more receiving devices via at least one line-of-sight LoS signal.

25. An apparatus for wireless communication, comprising: means for receiving, by a first user equipment UE, a message comprising at least one of: (i) a reference signal information (RS-info) parameter set relating to one or more reference signals (RS) corresponding to at least one line-of-sight (LoS) signal targeted for reception by one or more other devices distinct and separate from the first UE, or (ii) a set of data decoding information parameters relating to data scheduled for the purpose of communicating with the one or more other devices via at least one line-of-sight LoS signal targeted to the one or more other devices; as well as Components for doing at least one of the following: (i) monitor the reference signal transmission set based on the RS-info parameter set, or (ii) Monitoring the coded channel set based on the data decoding information parameters.

26. The apparatus according to claim 25, further comprising: Components for doing at least one of the following: (i) receiving a first reference signal RS based on a reference signal information RS-info parameter set, or (ii) receiving a first coded signal based on the data decoding information parameter; as well as means for determining information related to a spatial location of an object proximate to the first UE based at least in part on at least one of: (i) the first RS, or (ii) First coded signal.

27. The device according to claim 25, in, The RS-info parameter set includes an indication that the first RS in the RS set corresponds to one of the following: a downlink DL slot, an uplink UL slot, or a sidelink SL slot, and The data decoding information parameter set includes an indication that data scheduled for the purpose of communication via at least one LoS signal corresponds to one of the following: a downlink DL time slot, an uplink UL time slot, or a sidelink SL time slot.

28. The device according to claim 25, in, The RS-info parameter set includes a resource parameter set corresponding to a resource set for the first UE to monitor one or more RSs, and The data decoding information includes a resource set used by the first UE to monitor the coded data channel.

29. A scheduling entity for wireless communication, comprising: transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, the processor configured to: Receiving, via the transceiver, at least one of: (i) a reference signal information RS-info parameter set, including a resource parameter set corresponding to one or more reference signals RS targeted at multiple receiving devices, or (ii) a data decoding information parameter set, comprising a decoding parameter set for decoding a set of coded signals transmitted to a plurality of receiving devices via one or more coded channels; Receiving, via the transceiver, from a first user equipment (UE), a request for at least one of: (i) an RS-info parameter set, wherein the RS-info parameter includes information related to one or more reference signals, RS, the one or more reference signals, RS, being targeted for reception by at least one second UE other than the first UE, or (ii) data decoding information parameters, wherein the data decoding information corresponds to data decoding of at least one data item scheduled for at least one second UE; and Sending a message to the first UE via the transceiver, wherein the message includes at least one of the following: (i) RS-info parameter set, or (ii) Data decoding information parameter set.

30. The scheduling entity according to claim 29, wherein: The processor is further configured to: Use the RS-info parameter set to monitor the corresponding RS set; or The data decoding information parameter set is utilized to monitor a corresponding set of coded signals on one or more coded channels.

31. A method performed by a scheduling entity, comprising: Receiving, via the transceiver, at least one of: (i) a reference signal information RS-info parameter set, including a resource parameter set corresponding to one or more reference signals RS targeted at multiple receiving devices, or (ii) a data decoding information parameter set, comprising a decoding parameter set for decoding a set of coded signals transmitted to a plurality of receiving devices via one or more coded channels; Receiving, via the transceiver, from a first user equipment (UE), a request for at least one of: (i) RS-info parameter set, where The RS-info parameter includes information related to one or more reference signals RS, the one or more reference signals RS being received by at least one second UE other than the first UE, or (ii) data decoding information parameters, wherein the data decoding information corresponds to data decoding of at least one data item scheduled for at least one second UE; and Sending a message to the first UE via the transceiver, wherein the message includes at least one of the following: (i) RS-info parameter set, or (ii) Data decoding information parameter set.

32. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a wireless device, cause the wireless device to perform the method according to any one of claims 1-11.

33. A computer product comprising instructions which, when executed by a processor of a wireless device, cause the wireless device to perform the method according to any one of claims 1-11.

34. An apparatus for wireless communication, comprising: Means for performing the steps of the method according to claim 31.

35. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a scheduling entity, cause the scheduling entity to perform the method of claim 31.

36. A computer product comprising instructions which, when executed by a processor of a scheduling entity, cause the scheduling entity to perform the method of claim 31.

Images