Sensing configuration for reference signal time difference or doppler difference measurements
A framework for TDoA and FDoA measurements in wireless communication networks addresses the challenge of moving targets, improving sensing and positioning accuracy by incorporating assistance information and reporting configurations.
Patent Information
- Application Number
- PCT/CN2025/104730
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-06-27
- Publication Date
- 2026-02-12
AI Technical Summary
Legacy positioning techniques in wireless communication networks do not effectively account for moving sensing targets, such as unmanned aerial vehicles (UAVs), and there is a need for improved techniques to perform time and Doppler difference-of-arrival measurements.
A procedural and configuration framework is developed to enable time difference-of-arrival (TDoA) and frequency difference-of-arrival (FDoA) measurements, including assistance information, capability exchange, and reporting configurations for accurate sensing and positioning of moving targets.
Enhances the accuracy of sensing and positioning operations by leveraging the motion of sensing targets, enabling joint positioning and tracking through TDoA-and/or FDoA-based measurements.
Smart Images

Figure CN2025104730_12022026_PF_FP_ABST
Abstract
Description
SENSING CONFIGURATION FOR REFERENCE SIGNAL TIME DIFFERENCE OR DOPPLER DIFFERENCE MEASUREMENTSTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to techniques for configuring a reference signal time difference (RSTD) measurement or a reference signal Doppler difference (RSDD) measurement, e.g., associated with a sensing target.BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, which may be known as a network equipment (NE) , supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like) . Additionally, the wireless communications system may support wireless communications across various radio access technologies (RATs) including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., 5G-Advanced (5G-A) , sixth generation (6G) radio access technology, etc. ) .SUMMARY
[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of"” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ” Further, as used herein, including in the claims, a “set” may include one or more elements.
[0004] A radio node for wireless communication is described. In some examples, the radio node may implement, or may be implemented by, a UE or an NE. The radio node may be configured to, capable of, or operable to receive a sensing configuration for performing a sensing measurement associated with a sensing target, the at least one sensing measurement comprising a RSTD measurement or a RSDD measurement; receive assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0005] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to receive, a sensing configuration for performing a sensing measurement associated with a sensing target, the at least one sensing measurement comprising a RSTD measurement or a RSDD measurement; receive, at the radio node, assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0006] A method performed or performable by a radio node for wireless communication is described. The method may include receiving a sensing configuration for performing a sensing measurement associated with a sensing target, the at least one sensing measurement comprising a RSTD measurement or a RSDD measurement; receiving assistance information for performing the sensing measurement; and performing the sensing measurement based at least in part on the assistance information.
[0007] A network node for sensing measurement is described. In some examples, the network node may implement, or may be implemented by, a UE or an NE or a sensing management function (SensMF) or sensing function (SF) . The network node may be configured to, capable of, or operable to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement; transmit assistance information for performing the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement.
[0008] A processor for sensing measurement is described. The processor may be configured to, capable of, or operable to transmit, to a radio node, a sensing configuration for performing a sensing measurement associated with a sensing target, the at least one sensing measurement comprising a RSTD measurement or a RSDD measurement; transmit, to the radio node, assistance information for performing the sensing measurement; and receive, from the radio node, a report indicating at least the RSTD measurement or the RSDD measurement.
[0009] A method performed or performable by a network node for sensing measurement is described. The method may include transmitting a sensing configuration for performing a sensing measurement associated with a sensing target, the at least one sensing measurement comprising a RSTD measurement or a RSDD measurement; transmitting, to the radio node, assistance information for performing the sensing measurement; and receiving a report indicating at least the RSTD measurement or the RSDD measurement.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0011] Figure 2A illustrates an example of a first set of sensing scenarios for a radio sensing operation, in accordance with aspects of the present disclosure.
[0012] Figure 2B illustrates an example of a second set of sensing scenarios for a radio sensing operation, in accordance with aspects of the present disclosure.
[0013] Figure 3A illustrates an example of a tight coupling Information Sharing and Analysis Center (ISAC) network architecture, in accordance with aspects of the present disclosure.
[0014] Figure 3B illustrates another example of a tight coupling ISAC network architecture, in accordance with aspects of the present disclosure.
[0015] Figure 3C illustrates an example of an ISAC network architecture where the SF is co-located with the location management function (LMF) , in accordance with aspects of the present disclosure.
[0016] Figure 3D illustrates an example of a loose coupling ISAC network architecture, in accordance with aspects of the present disclosure.
[0017] Figure 4 illustrates an example of a radar pulse and return echo for sensing, in accordance with aspects of the present disclosure.
[0018] Figure 5 illustrates an example of a sensing operation for determining monostatic measurements, in accordance with aspects of the present disclosure.
[0019] Figure 6 illustrates an example of another sensing operation for determining monostatic measurements, in accordance with aspects of the present disclosure.
[0020] Figure 7 illustrates an example of a sensing operation for determining bistatic measurements, in accordance with aspects of the present disclosure.
[0021] Figure 8 illustrates an example of another sensing operation for determining bistatic measurements, in accordance with aspects of the present disclosure.
[0022] Figure 9 illustrates an example of another sensing operation for determining bistatic measurements, in accordance with aspects of the present disclosure.
[0023] Figure 10 illustrates an example of another sensing operation for determining bistatic measurements, in accordance with aspects of the present disclosure.
[0024] Figure 11 illustrates an example of a procedure for exchanging sensing assistance data / configuration information, in accordance with aspects of the present disclosure.
[0025] Figure 12 illustrates an example of another procedure for exchanging sensing assistance data / configuration information, in accordance with aspects of the present disclosure.
[0026] Figure 13 illustrates an example of another procedure for exchanging sensing assistance data / configuration information, in accordance with aspects of the present disclosure.
[0027] Figure 14 illustrates an example of a procedure for report configuration and measurement reporting, in accordance with aspects of the present disclosure.
[0028] Figure 15 illustrates an example of another procedure for report configuration and measurement reporting, in accordance with aspects of the present disclosure.
[0029] Figure 16 illustrates an example of another procedure for report configuration and measurement reporting, in accordance with aspects of the present disclosure.
[0030] Figure 17 illustrates an example of a procedure for exchanging error cause values, reporting performance monitoring results, in accordance with aspects of the present disclosure.
[0031] Figure 18 illustrates an example of a procedure for exchanging sensing capability information, in accordance with aspects of the present disclosure.
[0032] Figure 19 illustrates an example of a UE, in accordance with aspects of the present disclosure.
[0033] Figure 20 illustrates an example of a processor, in accordance with aspects of the present disclosure.
[0034] Figure 21 illustrates an example of a NE, in accordance with aspects of the present disclosure.
[0035] Figure 22 illustrates a flowchart of a method performed by a radio node in accordance with aspects of the present disclosure.
[0036] Figure 23 illustrates a flowchart of a method performed by a configuration node in accordance with aspects of the present disclosure.
[0037] Figure 24 illustrates a flowchart of a method performed by a radio node in accordance with aspects of the present disclosure.
[0038] Figure 25 illustrates a flowchart of a method performed by a configuration node in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0039] A wireless communication network, including one or more wireless devices, nodes, network entities, etc., may support sensing (also referred to as radio frequency (RF) sensing) to improve reliability and performance of the wireless communication network. Additionally, the one or more wireless devices, nodes, network entities, etc. may support sensing to enable various applications or services based on obtained sensing information from the one or more wireless devices, nodes, network entities, etc. The one or more wireless devices, nodes, network entities, etc., may perform sensing according to a sensing procedure, which may include one or more of sensing an environment (e.g., a physical environment, space, area) , performing measurements according to the sensing, and generating (or obtaining) sensing information associated with a target entity (e.g., object, device, environment) . The sensing information (also referred to as “sensing results” ) may include, but is not limited to, a position of the target entity, a velocity of the target entity, a direction (e.g., heading) of the target entity, an orientation of the target entity, a radar cross-section (RCS) of the target entity, a geometric shape of the target entity, a characteristic (e.g., material, composite, attribute, feature, etc. ) of the target entity.
[0040] In some implementations, the sensing information may be obtained based on a sensing signal outputted (e.g., transmitted, reflected, backscattered) from one or more wireless devices, nodes, network entities. The sensing signal may be a reference signal (RS) , such as one or more of an uplink (UL) RS, a downlink (DL) RS, or a sidelink (SL) RS, or a combination thereof. For example, the sensing signal may be a channel state information reference signal (CSI-RS) , a positioning reference signal (PRS) , a sounding reference signal (SRS) , a synchronization set block (SSB) , or a sensing-dedicated RS, among other examples. A wireless device, radio node, network entity configured to or operable to output a sensing signal may be referred to herein as a “sensing transmitter node” or “sensing transmitting node. ”
[0041] Additionally, or alternatively, in some other implementations, the sensing information may be obtained based on an obtained (e.g., received) sensing signal via the environment (e.g., reflected, refracted, scattered, blocked / attenuated, etc. ) , for example, by one or more wireless devices, nodes, network entities. A wireless device, radio node, network entity configured to or operable to obtain (e.g., receive) a sensing signal may be referred to herein as “sensing receiver node” or “sensing receiving node. ” In other implementations, additionally or alternatively, the sensing information may be obtained based on processing a received reflection of a sensing signal and / or inferring relevant information from the environment.
[0042] The measurement (e.g., sensing measurement) may involve one or multiple (static or mobile) sensing transmitter nodes with known sensing information or with (partially) unknown sensing information (e.g., known or unknown position) . In some other implementations, the measurement (e.g., sensing measurement) may involve one or multiple (static or mobile) sensing receiver nodes with known or (partially) unknown sensing information (e.g., known / unknown position) . In other implementations, the measurement (e.g., sensing measurement) may involve one or multiple (static or mobile) objects / reflectors with known or (partially) unknown sensing information (e.g., known / unknown position, presence, RCS, etc.
[0043] Future wireless communication networks may implement integrated sensing and communication, for example to support human / object detection, weather monitoring and tracking, automated guided vehicle (AGV) monitoring and tracking, automotive sensing and exploitation of sensing and positioning information. In certain implementations, the integrated sensing and communication may involve signals on frequencies from 500 MHz to 52.6 GHz.
[0044] In general, sensing is required to fulfill different performance requirements (e.g., accuracy, resolution, latency, etc. ) based on the characteristics (e.g., RCS) of one or multiple sensing target (s) and / or the environment to be sensed in a target sensing service area. In some implementation, sensing support in wireless communication networks may include a number of scenarios involving different radio nodes, such as RAN entities (e.g., base stations, NEs) and / or multiple UEs. Legacy positioning techniques may be extended to enable sensing functionality, e.g., in terms of type measurements metrics to be collected. These legacy positioning techniques may include timing-based techniques (e.g., DL-TDoA, multiple round trip time (Multi-RTT) , UL-RToA) , phase-based techniques (e.g., DL reference signal carrier phase (RSCP) , UL RSCP, DL reference signal carrier phase difference (RSCPD) ) , angle-based techniques (e.g., DL angle-of-departure (DL-AoD) , UL angle-of-arrival (UL-AoA) ) , and / or power-based fingerprinting techniques (e.g., using DL-PRS, SSB, or CSI-RS reference signal received power (RSRP) , DL-PRS, SSB, or CSI-RS reference signal received path power (RSRPP) , SRS-RSRP, and / or SRS-RSRPP) .
[0045] However, the legacy positioning use cases do not account for a UE that is in motion, whereas in sensing the target of interest may be in motion, e.g., uncrewed aerial vehicle (UAV) , crewed vehicle, AGV, and so on. The motion of the sensing target can be leveraged to develop a new sensing technique, which relies on the Doppler difference-of-arrival (DDoA) (also known as frequency difference-of-arrival (FDoA) ) of the sensing target in motion relative to the sensing transmitter (Tx) node and / or a sensing receiver (Rx) node.
[0046] Accordingly, there is a need for a procedural and configuration framework by which both the sensing Tx node and sensing Rx node transmit and receive the reflected signals of one or more targets for TDoA-and / or FDoA / DDoA-based measurements.
[0047] For example, the TDoA-and / or FDoA / DDoA-based measurement may be derived in monostatic and bistatic settings, thus the procedural and configuration framework may enable joint positioning and tracking of a sensing target.
[0048] In some implementations, assistance information parameters may be provided to the measurement entity (e.g., sensing Rx node) to enable accurate determination of RSTD measurements and RSDD measurements.
[0049] In some implementations, capability information may be exchanged to determine capable measurement entities (e.g., sensing Rx nodes) supporting TDoA-and / or FDoA / DDoA-based measurements.
[0050] A first solution describes techniques and procedures for enabling time difference-of-arrival (TDoA) and / or FDoA positioning techniques for cases where the sensing target is equipped with or without a UE. Beneficially, TDoA and / or FDoA positioning techniques provide improved accuracy of sensing and positioning operations.
[0051] A second solution describes techniques and procedures to model and support time-of-arrival (ToA) and Doppler measurements and associated reporting from a sensing Tx node and / or a sensing Rx node to a centralized entity. Beneficially, the reporting of differenced measurements with respect to a reference node may enable one or more differencing operations at a centralized entity in monostatic scenarios with a selected reference sensing Tx node and / or Rx node. For a time-based differencing operation, the differenced measurements may be based on ToA differencing or time-of-flight (ToF) differencing. For a Doppler-based differencing operation, the differenced measurements may be based on one-way measured Doppler shifts of the RS or two-way measured Doppler shifts of the RS.
[0052] A third solution describes techniques and procedures to model and support ToA and Doppler measurements and associated reporting from a sensing Tx node to a selected reference sensing Rx node. Beneficially, the reporting of differenced measurements to a reference node may enable the differencing operation (s) at the selected reference sensing Rx node measurement entity, e.g., in bistatic scenarios.
[0053] A fourth solution describes techniques and procedures to provide assistance information to a measurement entity. Beneficially, the use of assistance information may enhance the measured RSTD or RSDD (also referred to as RS frequency difference (RSFD) ) and / or assist in mitigating the measurement impairments associated with the performed RSTD or RSDD measurements.
[0054] A fifth solution describes techniques and procedures to implement a reporting configuration to request the appropriate RSTD and / or RSDD measurement with any associated measurement report metrics. Beneficially, the reporting configuration allows for time-alignment and synchronization of measurement data for improved precision and efficient use of network resources (e.g., bandwidth) and power.
[0055] A sixth solution describes techniques and procedures to support the indication of any error causes associated with the sensing configuration entity and / or sensing measurement entity. Beneficially, the indication of error causes allows for adaptive technique selection and quality of service (QoS) monitoring.
[0056] A seventh solution describes techniques and procedures for capability exchange to support TDoA and FDoA for sensing operations in various sensing scenarios. Beneficially, the capability exchange allows for optimal selection of the sensing technique and compatibility assurance.
[0057] While presented as distinct solutions, one or more of the solutions described herein may be implemented in combination with each other. Aspects of the present disclosure are described in the context of a wireless communications system.
[0058] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies (RATs) . In some implementations, the wireless communications system 100 may be a 4G network, such as a long-term evolution (LTE) network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a new radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In some other implementations, the wireless communications system 100 may be a 6G radio (6GR) network, such as a 6G network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network and a 6G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6GR. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
[0059] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a wireless communication network entity, a radio access network (RAN) , a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0060] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) . In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
[0061] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples.
[0062] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0063] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N2, or network interface) . In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
[0064] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
[0065] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N2, or another network interface) . The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106) .
[0066] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0067] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing (SCS) value and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first SCS value (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first SCS value (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second SCS value (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third SCS value (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth SCS value (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth SCS value (e.g., 240 kHz) and a normal cyclic prefix.
[0068] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0069] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective SCS values of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz SCS) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first SCS value (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0070] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations frequency range #1 (FR1) (e.g., 410 MHz –7.125 GHz) , frequency range #2 (FR2) (e.g., 24.25 GHz –52.6 GHz) , frequency range #3 (FR3) (e.g., 7.125 GHz –24.25 GHz) , frequency range #4 (FR4) (e.g., 52.6 GHz –114.25 GHz) , frequency range #4a (FR4a) or frequency range #4-1 (FR4-1) (e.g., 52.6 GHz –71 GHz) , and frequency range #5 (FR5) (e.g., 114.25 GHz –300 GHz) . In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0071] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz SCS; a second numerology (e.g., μ=1) , which includes 30 kHz SCS; and a third numerology (e.g., μ=2) , which includes 60 kHz SCS. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz SCS; and a fourth numerology (e.g., μ=3) , which includes 120 kHz SCS.
[0072] According to implementations, one or more of the NEs 102 and the UEs 104 are operable to implement various aspects of the techniques described with reference to the present disclosure.
[0073] In some implementations, a sensing configuration node may transmit, e.g., to one or more NEs 102 and / or to one or more UEs 104, a sensing configuration for performing a sensing procedure that includes at least one sensing measurement associated with a sensing target. Here, the sensing measurement (s) may be based on one or more sensing techniques, such as a RSTD measurement and / or a RSDD measurement. In some examples, the sensing target may include a UE 104. In other examples, the sensing target is not associated with a UE 104.
[0074] In some examples, the NEs 102 and / or UEs 104 associated with the sensing procedure may additionally receive assistance for performing the sensing measurement. In some implementations, the assistance information comprises information for mitigating sensing measurement errors. Examples of measurement errors correctable using the assistance information include but are not limited to: 1) measurement noise / uncertainty, 2) timing clock offset / bias at the sensing Tx node, 3) timing error group information at the sensing Tx node, 4) frequency offset / bias at sensing Tx node, and / or 5) timing or frequency synchronization errors.
[0075] Upon receiving the sensing configuration (and optionally the assistance information) , the NEs 102 and / or UEs 104 associated with the sensing procedure may then perform the sensing measurement (s) for the sensing procedure in accordance with the sensing configuration (and based on the assistance information, if provided) .
[0076] Additionally, the sensing configuration node may transmit, e.g., to the one or more NEs 102 and / or the one or more UEs 104, a reporting configuration indicating one or more RS resources for performing the sensing measurement (s) and a reporting characteristic for transmitting a sensing measurement report. Here, the reporting characteristic may include an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting. The NEs 102 and / or UEs 104 associated with the sensing procedure may then transmit the sensing measurement report based on the sensing measurement and according to the received configuration.
[0077] In some examples, upon receiving the sensing measurement report, the sensing configuration node may determine a sensing result, e.g., based at least in part on the sensing measurement reports received from the one or more NEs 102 and / or the one or more UEs 104.
[0078] Regarding network-based and UE-based (e.g., SL-based) radio sensing operations, different scenarios for radio sensing are presented in Figures 2A and 2B. In some scenarios of radio sensing, the network configures the participating sensing entities, i.e., network nodes and UE acting as sensing Tx nodes, network nodes and UE acting as sensing Rx nodes, as well as the configuration of sensing RS and necessary measurements and reporting procedures from the nodes. In this regard, the functional split between the network nodes and the UE for a specific sensing task may take various forms, depending on the availability of sensing-capable devices and the requirements of the specific sensing operation.
[0079] Figure 2A depicts possibilities for sensing scenarios for a radio sensing operation 200 where a RAN entity performs a sensing RS transmission, according to embodiments of the disclosure. In the scenarios of Figure 2A, sensing RS reception is performed by one or more UEs, one or more RAN entities, or a combination thereof. The radio sensing operation 200 may involve a first RAN entity 202 (e.g., a gNB or network TRP node) , a second RAN entity 204 (e.g., a gNB or a network TRP node) , and / or a set of at least one UE (represented by the first UE 206) .
[0080] In various embodiments, the radio sensing operation 200 is used to detect and locate an object of interest 208. In general, a radio-based sensing transmission 210 is performed by the first RAN entity 202. While the below examples describe the radio-based sensing transmission 210 using a sensing RS 212, in other embodiments the radio-based sensing transmission 210 may be a transmission of another RS or instead may be a transmission of the data / control channels known to the network TRP nodes.
[0081] In a first sensing scenario (also referred to herein as “Case I” ) , the radio-based sensing transmission 210 is performed by a first network node (i.e., the first RAN entity 202) and the radio-based sensing reception 216 is performed by a separate network node (i.e., the second RAN entity 204) . In this case, the sensing RS 212 (or another RS used for sensing) is transmitted and a reflection / backscatter signal 214 is received by network entities. The network does not utilize the UEs for sensing assistance in this first sensing scenario. Rather, the involvement of UEs (i.e., first UE 206) is limited to the aspects of interference management, when necessary.
[0082] In a second sensing scenario (also referred to herein as “Case II” ) , the radio-based sensing transmission 210 is performed by a first network node (i.e., the first RAN entity 202) and the radio-based sensing reception 218 is performed by the same network node. In this case, the sensing RS 212 (or another RS used for sensing) is transmitted and a reflection / backscatter signal 214 is received by the same network entity. The network also does not utilize the UEs for sensing assistance in this second sensing scenario. Rather, the involvement of UEs (i.e., first UE 206) is limited to the aspects of interference management, when necessary.
[0083] In a third sensing scenario (also referred to herein as “Case III” ) , the radio-based sensing transmission 210 is performed by a first network node (i.e., the first RAN entity 202) and the radio-based sensing reception 220 is performed by a UE (i.e., the first UE 206) . In this case, the sensing RS 212 (or other RS used for sensing) is transmitted by a network entity and a reflection / backscatter signal 214 is received by one or multiple UEs, including the first UE 206. The network configures the one or multiple UEs to act as a sensing Rx node, e.g., according to the UE capabilities for sensing, as well as desired sensing task.
[0084] Figure 2B depicts possibilities for sensing scenarios for a radio sensing operation 230 where a UE performs a sensing RS transmission, according to embodiments of the disclosure. In the scenarios of Figure 2B, sensing RS reception is performed by one or more UEs, one or more RAN entities, or a combination thereof. The radio sensing operation 230 may involve the first UE 206, a set of at least one peer UE (represented by the second UE 232) , and / or a set of at least one TRP (represented by the first RAN entity 202) .
[0085] In various embodiments, the radio sensing operation 230 is used to detect and locate an object of interest 208. In general, a radio-based sensing transmission 234 is performed by the first UE 206. While the below examples describe the radio-based sensing transmission 234 using a sensing RS 236, in other embodiments the radio-based sensing transmission 234 may be a transmission of another RS or instead may be a transmission of the data / control channels.
[0086] In a fourth sensing scenario (also referred to herein as “Case IV” ) , the radio-based sensing transmission 234 is performed by a first UE 206 and the radio-based sensing reception 240 is performed by a RAN entity (i.e., the first RAN entity 202) . In this case, the sensing RS 236 (or another RS transmitted for sensing) is transmitted by a UE and a reflection / backscatter signal 238 is received by one or multiple network entities. The network configures the transmitting UE (i.e., the first UE 206) to act as a sensing Tx node, e.g., according to the capabilities of the UE for sensing, as well as the nature of the desired sensing task.
[0087] In a fifth sensing scenario (also referred to herein as “Case V” ) , the radio-based sensing transmission 234 is performed by a first UE 206 and the radio-based sensing reception 242 is performed by a separate UE (i.e., the second UE 232) . In this case, the sensing RS 236 (or another RS transmitted for sensing) is transmitted by a UE and a reflection / backscatter signal 238 is received by one or multiple UEs. The network, or potentially the first UE 206, may decide on configuration of the sensing scenario. In one instance, the network configures the one or multiple UEs to act as a sensing Tx node and / or sensing Rx nodes, e.g., according to the capabilities of the one or multiple UE for sensing, as well as the nature of the desired sensing task.
[0088] In a sixth sensing scenario (also referred to herein as “Case VI” ) , the radio-based sensing transmission 234 is performed by a first UE 206 and the radio-based sensing reception 244 is performed by the same UE. In this case, the sensing RS 236 (or another RS transmitted for sensing) is transmitted by a UE and a reflection / backscatter signal 238 is received by the same UE. The UE or the network configures the sensing scenario, e.g., according to the capabilities of the UE for sensing, as well as the nature of the desired sensing task.
[0089] The above radio sensing scenarios are described in further detail in U.S. Application 17 / 538,978 entitled “CONFIGURING A SENSING REFERENCE SIGNAL” and filed on November 30, 2021 for Seyedomid Taghizadeh Motlagh, Ali Ramadan Ali, Ankit Bhamri, Sher Ali Cheema, Razvan-Andrei Stoica, Hyejung Jung and Vijay Nangia, and also described in further detail in U.S. Application 17 / 538,998 entitled “SENSING REFERENCE SIGNAL CONFIGURATION” and filed on November 30, 2021 for Seyedomid Taghizadeh Motlagh, Ali Ramadan Ali, Ankit Bhamri, Sher Ali Cheema, Razvan-Andrei Stoica, Hyejung Jung and Vijay Nangia, which applications are incorporated herein by reference.
[0090] Moreover, the above scenarios are not intended to be restricted to a specific UE type, and may include any UE category. In any of the above scenarios, and of the roles elaborated for gNB and / or UE may be replaced (with equal validity for any example of a radio sensing scenario) with any UE or RAN node, e.g., a smart repeater node, an Integrated Access and Backhaul (IAB) node, a roadside unit (RSU) , etc. In some examples, the set of sensing Tx nodes of a sensing measurement process (and similarly, but may be independently, a sensing Rx nodes of a sensing measurement process) include one or more of a TRP associated with a gNB-CU / DU, a gNB distributed unit (gNB-DU) , a gNB control unit (gNB-CU) , a UE, a network controlled repeater (NCR) , an IAB node, an RSU, or a dedicated sensing radio. In some embodiments, a sensing Rx node may also be a non-3GPP sensor with capability of providing non-3GPP sensing data, or a 3GPP node (e.g., a UE or a RAN node) connected to the non-3GPP sensor and can obtain, process, and transfer the non-3GPP sensing data of the non-3GPP sensor to other 3GPP nodes / entities.
[0091] Integrated sensing and communication may enhance 5G core architecture by introducing a new SF. Figures 3A-5D present possible combinations leading to the network impact.
[0092] Figure 3A illustrates an example of a tight coupling ISAC network architecture 300 with a unified SF (i.e., where the SF is not split between the control plane (CP) and user plane (UP) domains. As depicted, the SF is communicatively coupled to the AMF, the unified data management node (UDM) , the network data analytics function (NWDAF) , the LMF, the policy control function (PCF) , the network exposure function (NEF) , and to the (radio) access network ( (R) AN) , optionally via the UPF.
[0093] In the tight coupling ISAC network architecture 300, the SF appears as a dedicated network function handling both: i) the sensing control plane aspects such as the interaction with the sensing consumer via NEF and information exchange with other network functions, for gathering UE information, (i.e., from the AMF, the UDM, the LMF) , for gathering UE related policies from the PCF, and for gathering analytics from the NWDAF; and ii) the sensing radio signals for performing the analysis or prediction for determining the sensing target.
[0094] Figure 3B illustrates another example of a tight coupling ISAC network architecture 310, where the SF is functionally split / distributed among the CP and UP domains. As depicted, a CP split of the SF (denoted “SF-C” ) is communicatively coupled to the AMF, the UDM, the NWDAF, the LMF, the PCF, and the NEF. Additionally, a UP split of the SF (denoted “SF-U” ) is communicatively coupled to the (R) AN, optionally via the UPF.
[0095] In the tight coupling ISAC network architecture 310 with CP / UP split, the SF has two dedicated network function counter parts: i) SF-C that handles the control plane aspects as described above and ii) SF-U that is responsible for collecting the sensing radio signals via the user plane, i.e., via the (R) AN and the UPF. The idea of this architecture is to split and offload heavy data volumes associated with sensing radio signals to the user plane to ensure light traffic, i.e., only signaling, in the control plane.
[0096] Figure 3C illustrates an example of an ISAC network architecture 320, where the SF is co-located with the LMF. The SF is communicatively coupled with the LMF, where the co-located nodes are also coupled with the Gateway Mobile Location Center (GMLC) and the AMF. As depicted, the GMLC is additionally coupled with the UDM, the AMF and the NEF. The AMF is additionally coupled with the UDM, the NEF, the (R)AN, and the UE. The NEF is additionally coupled with the application function (AF) . The (R) AN is additionally coupled with the UE. The inter-function interfaces (i.e., reference points) are labeled in Figure 3C. In the ISAC network architecture 320, the SF (i.e., co-located with the LMF) appears as a logical network function embedded in the LMF to perform sensing taking advantage of the knowledge of a UE location.
[0097] Figure 3D illustrates an example of a loose coupling ISAC network architecture 330, where the SF is communicatively coupled with the (R) AN and with the AF, optionally via the NEF. The SF may optionally be coupled with one or more of: the AMF (directly or via the (R) AN) , the NWDAF, the NEF, and the UE (via the (R) AN) . The inter-function interfaces (i.e., reference points) are labeled in Figure 3C.
[0098] In the loose coupling ISAC network architecture 330, the SF is independent of the core network, i.e., typically used for local field scenarios or private networks, and the interaction with the core network is minimal. The main idea is to use SF close to the RAN, i.e., collect and process the sensing radio signals locally, and interact with core network for the purpose of exposure via NEF, for getting the UE location from the AMF and for analytics (i.e., NWDAF interaction) .
[0099] In another description of controlling a sensing operation, in some example implementations, a sensing controller entity / function (e.g., SensMF or SF) is defined which comprises one or multiple of a UE, a RAN node, a gNB / gNB-CU, an LMF, an SF, a sensing management component (SMC) or a combination thereof, wherein the SensMF performs one or multiple of: A) Receives request for sensing information from a service consumer (e.g., a requesting third party application) ; B) Determines selection and / or configuration of a sensing operation, including configuration of one or more of a sensing Tx node, sensing Rx node; C) Selects and / or configures the involved nodes for sensing transmission and sensing reception and sensing measurement and reporting of the conducted measurements; D) Collects the sensing measurements; E) Performs or configures or requests computation of the sensing measurements and thereby determines the required sensing results or information based on the obtained sensing measurements; and / or F) Reports / exposes an obtained sensing information to the entity requesting the sensing information.
[0100] In some examples, the SensMF may be comprised of multiple nodes / entities, and a first part of the above-mentioned steps may be implemented by the first part of the SensMF, while a second part of the above steps may be implemented by the second part of the SensMF, e.g., implemented in the SF and gNB, e.g., as a SMC. In some examples, the SensMF may be comprised of multiple nodes / entities, and the communication among the SensMF entities may be transparent to the outside entities and also not discussed in the related sensing procedure embodiments; nevertheless, the communication among the SensMF entities is assumed to be implicit to the overall procedure.
[0101] In some examples, wherein a SensMF is comprised of an SF and a gNB (e.g., serving / head gNB of a related UE to the sensing task or a selected serving gNB for a sensing task) , the SF performs the steps A, F, E, D whereas the steps B, C are performed by the selected gNB node. In some other examples, the step B, D are jointly performed by the SF and the selected gNB, wherein a first part of the configuration / configuration determination are performed by the SF and a second part of the configuration / configuration determination is performed by the selected gNB. The SensMF may be a RAN node (e.g., a selected gNB node acting as serving gNB of a sensing task) , may be a SF residing in core network, may be a UE, or a combination thereof.
[0102] Figure 4 is a diagram illustrating one embodiment of time domain representation 400 of a radar pulse and return echo signal, according to embodiments of the disclosure. Communication and radar technologies have been traditionally deployed as separate / independent systems, each with a separate waveform. However, there may be use cases such as the automotive, smart factory, medical monitoring, etc., where joint radio communications and radar sensing using the same waveform are considered beneficial for efficient usage of the radio frequency (RF) spectrum as well usage of the same hardware to perform high data rate communications and precise ranging.
[0103] Radar systems may be classified into the following categories: 1) Monostatic radars: A radar system in which the transmitter and receiver are collocated; 2) Bistatic radar: A radar system that comprises of a transmitter and receiver that are separated by a distance comparable to the expected target distance; 3) Multi-static radar: A radar system which includes multiple spatially diverse monostatic radar or bistatic radar components within an overlapping coverage area.
[0104] Radar signals are characterized by pulses that are modulated onto an RF carrier and are used to detect single / multiple objects that may be resolved in the time domain. Figure 4 depicts a transmitted pulse 402 having a transmit time, τ (also referred to as “pulse width” ) . The reflected signal, referred to as echo pulse 404, is received some time later. In a basic scenario, for a single reflector, a pulse with measured round-trip time t allows the range (R) with respect to the object to be calculated as: while the range resolution (ΔR) is calculated as: where τ is the pulse width and c is the speed of light. The radar pulses 402 are usually transmitted periodically so that range information may be provided in real time and wait for the returning echo signal during the so-called rest time (or listening time) as shown in Figure 4. The time between successive radar pulse transmissions is referred to as the pulse repetition time (PRT) or pulse repetition period (PRP) . The PRT may be divided into a receiving time, during which monitoring for the echo pulse 404 occurs, and a rest time.
[0105] Regarding RAT-dependent Positioning Measurements, the different DL measurements including DL PRS RSRP, DL RSTD and UE Rx-Tx Time Difference required for the supported RAT-dependent positioning techniques are shown in Tables 1-4. The following measurement configurations may be specified: A) 4 Pair of DL RSTD measurements may be performed per pair of cells (each measurement is performed between a different pair of DL PRS resources / resource sets with a single reference timing) ; B) 8 DL PRS RSRP measurements may be performed on different DL PRS resources from the same cell. Table 1: DL PRS RSRP Table 2: DL RSTD Table 3: UE Rx-Tx time difference Table 4: DL PRS-RSRPP
[0106] Additionally, the UL-AoA is defined as the estimated azimuth angle (A-AoA) and vertical (zenith) angle (Z-AoA) of a UE with respect to a reference direction, wherein the reference direction is defined. The UL-AoA is determined at the gNB antenna for an UL channel corresponding to this UE.
[0107] In the global coordinate system, wherein estimated azimuth angle is measured relative to geographical North and is positive in a counterclockwise direction and estimated vertical angle is measured relative to zenith and positive to horizontal direction.
[0108] In the local coordinate system, wherein estimated azimuth angle is measured relative to x-axis of the local coordinate system and positive in a counterclockwise direction and estimated vertical angle is measured relative to z-axis of the local coordinate system and positive to x-y plane direction. The bearing, downtilt, and slant angles of the local coordinate system are defined (e.g., according to 3GPP technical specification (TS) 38.901) .
[0109] The UL relative time of arrival (UL-RToA) is the beginning of subframe i containing at least one SRS received in a RP j, relative to the relative time of arrival (RToA) reference time. The UL-RToA reference time (TUL-RTOA) is defined as T0 + tSRS, where T_0 T0 is the nominal beginning time of system frame number (SFN) 0 provided by SFN initialization time (e.g., defined in 3GPP TS 38.455) , and where tSRS = (10nf +nsf) ×10-3, where nf and nsf are the system frame number and the subframe number of the SRS, respectively. Multiple SRS resources may be used to determine the beginning of one subframe containing SRS received at a RP.
[0110] The reference point for TUL-RTOA shall be: the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; the Rx antenna (i.e., the center location of the radiating region of the Rx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
[0111] The gNB Rx-Tx time difference positioning measurement is defined as TgNB-RX –TgNB-TX, where TgNB-RX is the TRP received timing of UL subframe #i containing SRS associated with UE, defined by the first detected path in time, and where TgNB-TX is the TRP transmit timing of DL subframe #j that is closest in time to the subframe #i received from the UE. Multiple SRS resources may be used to determine the start of one subframe containing SRS.
[0112] The reference point for the TgNB-RX may be the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; or the Rx antenna (i.e., the center location of the radiating region of the Rx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) ; or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
[0113] Similarly, the reference point for the TgNB-TX may be the Tx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; or the Tx antenna (i.e., the center location of the radiating region of the Tx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) ; or the Tx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
[0114] The UL SRS-RSRPP positioning measurement is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry the received UL SRS signal configured for the measurement, where UL SRS-RSRPP for a first path delay is the power contribution corresponding to the first detected path in time.
[0115] The reference point for UL SRS-RSRPP shall be: the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; based on the combined signal from antenna elements corresponding to a given receiver branch for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
[0116] For FR1 and FR2, if receiver diversity is in use by the gNB for UL SRS-RSRPP measurements, then: 1) The reported UL SRS-RSRPP value for the first and additional paths shall be provided for the same receiver branch (es) as applied for UL SRS-RSRP measurements, or 2) The reported UL SRS-RSRPP value for the first path shall not be lower than the corresponding UL SRS-RSRPP for the first path of any of the individual receiver branches and the reported UL SRS-RSRPP for the additional paths shall be provided for the same receiver branch (es) as applied UL SRS-RSRPP for the first path.
[0117] The present disclosure provides a detailed conceptual solution for procedural, capability and configuration framework for joint measurement of RSTD and RSDD measurements according to a reference Tx node and the provisioning of assistance information to mitigate issues such as synchronization error and so forth.
[0118] Described below are solutions to various scenarios in which TDoA, FDoA, and / or DDoA techniques may be used for sensing measurements associated with a sensing target. While presented as distinct solutions, one or more of the solutions described herein may be implemented in combination with each other. Note that in the present disclosure, any reference made to device (e.g., UE) position information (or location information) may refer to either a 2D / 3D absolute position, 2D / 3D relative position, distance, relative direction with respect to another node / entity, ranging in terms of distance, ranging in terms of direction or combination thereof.
[0119] In some examples, a sensing result may be delivered to a consumer such as an application function or service consumer upon a triggered request. For the purposes of this disclosure, derivation of the final sensing information or result is based on the initial measurements and input parameters, which may be different from the generated / reported sensing radio measurements.
[0120] As used herein, FDoA and DDoA are terminology relating to a technique to perform Doppler shift differencing of the received signal, which may be used in an interchangeable manner for the purposes of the solutions described herein. In another case, FDoA may be referred to as the sensing technique, while DDoA refers to the generated measurement associated with the FDoA sensing technique.
[0121] As used herein, the SensMF or SF refers to the entity (e.g., network node) that manages the overall triggering, co-ordination and scheduling of resources, measurement collection, sensing result determination required for the sensing of an object / human. It also calculates or verifies a final sensing result and / or any velocity or Doppler estimates and may estimate the achieved sensing accuracy. The SensMF or SF receives sensing requests for a sensing target within a network area by a sensing client, which may be external or internal to a network or device, respectively. The SensMF interacts with the various network entities and UEs in order to exchange location information applicable to UE-assisted and UE-based sensing techniques and interacts with the next generation RAN (NG-RAN) to obtain sensing information. The SensMF and SF are examples of a sensing result computation entity.
[0122] As used herein, the SMC refers to a node that comprises all or part of the SensMF or SF. The SMC may reside in the NG-RAN. The SMC is another example of a sensing result computation entity.
[0123] As used herein, the term “5G wireless sensing” refers to a 5G system (5GS) feature providing capabilities to get information about characteristics of the environment and / or objects within the environment (e.g., shape, size, speed, location, distances or relative motion between objects, etc. ) using NR RF signals and, in some cases, previously defined information available in the EPC and / or the evolved universal mobile telecommunications system (UMTS) terrestrial radio access (E-UTRA) . As used herein, “6G wireless sensing” refers to a 6G system (6GS) feature providing capabilities to get information about characteristics of the environment and / or objects within the environment (e.g., shape, size, speed, location, distances or relative motion between objects, etc. ) using 6GR RF signals and, in some cases, previously defined information available in the 5GS and / or EPC and / or the E-UTRA and / or NR.
[0124] As used herein, the term “sensing measurement data” refers to data collected about radio / wireless signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes. As used herein, the term “sensing measurement process” refers to the process of collecting sensing measurement data.
[0125] As used herein, the term “sensing receiver” refers to an entity that receives the sensing signal which the sensing service will use in its operation. Exemplary sensing receivers may include a sensing Rx node, such as an NR RAN or 6G RAN node or a UE. A sensing receiver may be located in the same or different entity as the sensing transmitter.
[0126] As used herein, the term “sensing result” refers to the information derived from processing sensing measurement data.
[0127] As used herein, the term “sensing service area location” refers to an area location whether with or without obstacle, the 5GS can provide sensing service with certain quality.
[0128] As used herein, the term “sensing transmitter” refers to an entity that transmits (i.e., sends out) the sensing signal which the sensing service will use in its operation. Exemplary sensing transmitters may include a sensing Tx node, such as an NR RAN node or a UE. A sensing transmitter may be located in the same or different entity as the sensing receiver. For example, in a monostatic sensing arrangement, the sensing transmitter and the sensing receiver are located in the same entity, while in a monostatic sensing arrangement, the sensing transmitter and the sensing receiver are located in different entities.
[0129] As used herein, the term “transparent sensing” refers to the communication of sensing measurements such that they can be discerned and interpreted by the 5GS, e.g., the data is communicated using a standard protocol to an interface defined by the 5GS.
[0130] As used herein, the term “motion rate accuracy” describes the closeness of the measured magnitude of the sensing target object’s vibration frequency caused by part (s) of the sensing target object to the true magnitude of the sensing target object’s vibration frequency.
[0131] The sensing service area is a key performance indicator (KPI) applicable to the definition of the use cases on sensing qualitative requirements. A sensing service area refers to a service area where sensing services would solely rely on infrastructures and sensing technologies that may be assumed to be present anywhere where 5G or 6G is present. This includes both indoor and outdoor environments.
[0132] The following KPIs apply to the definition of the use cases on sensing quantitative requirements: accuracy of positioning estimate, accuracy of velocity estimate, confidence level, sensing resolution, range resolution, velocity resolution, missed detection, false alarm, maximum sensing service latency, and refreshing rate.
[0133] The accuracy of positioning estimate describes the closeness of the measured sensing result (i.e., position) of the sensing target object to its true position value. The accuracy of positioning estimate may be further derived into horizontal and vertical components: the horizontal sensing accuracy referring to the sensing result error in a 2D reference or horizontal plane, and the vertical sensing accuracy referring to the sensing result error on the vertical axis or altitude.
[0134] The accuracy of velocity estimate describes the closeness of the measured sensing result (i.e., velocity) of the sensing target object’s velocity to its true velocity. The velocity resolution denotes the minimum difference in velocity between target objects to have a measurably different velocity.
[0135] The confidence level describes the percentage of all the possible measured sensing results that can be expected to include the true sensing result considering the accuracy.
[0136] The sensing resolution describes the difference of the measured magnitude of two target objects, which is the magnitude needed to distinguish the two target objects. The range resolution denotes the minimum difference in distance between target objects to have a measurably different range.
[0137] The missed detection describes the probability of failing to acquire a sensing result when the 5GS or 6GS attempts to acquire a sensing result. In some implementations, the missed detection KPI applies only to binary sensing results.
[0138] The false alarm describes the probability of detecting a false sensing result that does not represent the characteristics of a target object (i.e., sensing target) or environment when the 5GS attempts to acquire a sensing result. In some implementations, the false alarm KPI applies only to binary sensing results.
[0139] The maximum sensing service latency describes the time elapsed between the event triggering the determination of the sensing result and the availability of the sensing result at the sensing system interface.
[0140] The refreshing rate describes the rate at which the sensing result is generated by the sensing system. The refreshing rate is the inverse of the time elapsed between two successive sensing results reporting to the application server.
[0141] As used herein, the terms “sensing configuration entity” or “sensing configuration node” refers to the entity (e.g., a network node or radio node) that determines and / or provides a configuration to another entity or node associated with a sensing operation. Exemplary sensing configuration entities / nodes may include a base station (e.g., gNB) , a location server (e.g., LMF) , a sensing server (e.g., SF) , a sensing management component (SMC) or the like.
[0142] As used herein, the terms “measurement entity” or “measurement node” refers to the entity (e.g., radio node) , which performs a measurement of a transmitted signal (e.g., RS) for the purposes of fulfilling a service, e.g., communication, sensing, positioning, or a combination thereof. Exemplary measurement entities / nodes may include a base station (gNB) , distributed units (DUs) , central units (CUs) , UEs, devices, positioning reference units (PRUs) , sensing reference units (SRUs) , customer premise equipments (CPEs) , or the like.
[0143] As used herein, a transmission point (TP) refers to a set of geographically co-located transmit antennas (e.g., antenna array (with one or more antenna elements) ) for one cell, part of one cell or one sensing RS-only TP or PRS-only TP. TPs can include base station (e.g., gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a PRS-only TP, etc. One cell can be formed by one or multiple TPs. For a homogeneous deployment, each TP may correspond to one cell.
[0144] As used herein, a reception point (RP) refers to a set of geographically co-located receive antennas (e.g., antenna array (with one or more antenna elements) ) for one cell, part of one cell or one UL-SRS-only RP. RPs can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a UL-SRS-only RP, etc. One cell can include one or multiple RPs. For a homogeneous deployment, each RP may correspond to one cell.
[0145] As used herein, a TRP refers to a set of geographically co-located antennas (e.g., antenna array (with one or more antenna elements) ) supporting TP and / or RP functionality.
[0146] As used herein, a “PRS-only TP” refers to a TP which only transmits PRS signals or DL-PRS for PRS-based terrestrial beacon system (TBS) positioning and is not associated with a cell. Similarly, a “sensing RS-only TP” refers to a TP which only transmits sensing RS signals (as described herein) and is not associated with a cell.
[0147] A positioning reference unit (PRU) at a known location can perform positioning measurements (e.g., RSTD, RSRP, UE Rx-Tx time difference measurements, etc. ) and report these measurements to a location server. In addition, the PRU can transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g., RToA, UL-AoA, gNB Rx-Tx time difference, etc. ) from PRU at a known location. The PRU measurements may be compared by a location server with the measurements expected at the known PRU location to determine correction terms for other nearby target devices. The DL-and / or UL location measurements for other target devices can then be corrected based on the previously determined correction terms. A PRU may also comprise of a TRP with a known location.
[0148] As used herein, the term “target device” refers to a radio node of interest (e.g., UE, gNB) whose position (e.g., absolute position or relative position) is to be obtained by the network or by the radio node itself, e.g., using one or more of the positioning techniques described herein.
[0149] The embodiments herein describe systematic procedures to determine Doppler difference of one or more targets in a wireless communication network. These embodiments aim to cover different use cases and scenarios in which sensing of one or more targets may be performed depending on the wireless communication entity / node configuring the RS for sensing and / or communication purposes, the wireless communication entity / node transmitting the said RS, the wireless communication entity / node receiving the RS and performing the measurement of the received RS, the wireless communication entity / node computing / determining the relevant sensing / radar metrics. Various combinations of wireless communication entities or nodes may be envisioned to perform the described tasks depending on the sensing operation, as illustrated in Table 5: Table 5: Sensing Operations
[0150] Additionally, it may be assumed that the one or more targets to be sensed may be categorized as follows: A) Device-free / Passive; or B) Device-based / Active. For the device-free / passive case, the sensing target comprises an object not associated with the 3GPP network. In contrast, for the device-based / active case, the sensing target is a human / object associated with a UE, e.g., a human holding a UE, a UE embedded with a UAV, a UE within automotive vehicles; thus, the sensing target is associated with the 3GPP network.
[0151] The solutions disclosed herein related to the configuration and reporting of TDoA based measurements (i.e., RSTD measurements) and / or FDoA (i.e., DDoA) based measurements (i.e., RSDD measurements) in wireless sensing systems, e.g., integrated sensing and communication (ISAC) . The solutions disclosed herein are also supported by the following frameworks:
[0152] According to a first framework (Framework#1) , the RS configuration, assistance information, reporting configuration, error reporting and measurement and sensing result reporting for FDoA is integrated with current DL-TDoA and / or UL-TDoA methods in positioning or sensing comprising resource configuration, reporting configuration, measurement definition, reporting and capability reporting. This supports examples where joint position and tracking estimation need to be supported, e.g., in the existing 3GPP positioning framework using LTE positioning protocol (LPP) signaling and the involvement of the location server, e.g., LMF. The applications include sensing-assisted positioning or positioning-assisted sensing.
[0153] According to a second framework (Framework#2) , the RS configuration, assistance information, reporting configuration, error reporting and measurement and sensing result reporting for FDoA is considered as a separate method under the sensing framework. However, this does not limit the use of the multiple sensing / positioning techniques such as Multi-RTT, DL-TDoA and / or UL-TDoA in combination with the FDoA method to derive a sensing result.
[0154] In some implementations, the sensing Tx / Rx nodes are stationary and the sensing target, STarget, is moving relative to the sensing Tx / Rx nodes. In one example, the sensing Tx / Rx nodes comprise a TRP-TRP monostatic arrangement. In another example, the sensing Tx / Rx nodes comprise a TRP-TRP bistatic arrangement.
[0155] In some implementations, the sensing Tx / Rx nodes are both mobile and sensing target, STarget, is moving relative to the sensing Tx / Rx nodes. In one example, the sensing Tx / Rx nodes comprise a UE-UE monostatic arrangement. In another example, the sensing Tx / Rx nodes comprise a UE-UE bistatic arrangement.
[0156] In some implementations, either the sensing Tx node or the sensing Rx node is stationary while the other node is mobile, and the sensing target, STarget, is moving relative to the stationary node. In one example, the sensing Tx / Rx nodes comprise a TRP-UE bistatic arrangement. In another example, the sensing Tx / Rx nodes comprise a UE-TRP bistatic arrangement.
[0157] According to aspects of the first solution, one or more sensing technique identifiers (IDs) may be associated with the TDoA and / or FDoA techniques as described below. In some implementations, upon the indication (or determination) of a sensing measurement (or sensing report, or sensing assistance information) associated with a sensing technique (indicated by the associated sensing technique ID) , a sensing Tx / Rx node (e.g., a measurement entity associated with a sensing operation) and / or a sensing configuration node (e.g., a configuration entity associated with the sensing operation) may assume a pre-defined set of configurations (e.g., a pre-defined structure) for measurement quantities, assistance information, reporting configurations, or a subset thereof, associated with the indicated sensing technique.
[0158] The TDoA positioning technique for sensing and positioning makes use of the following depending on the considered link between the entities / nodes associated with the positioning technique. In general, TDoA refers to the positioning technique and RSTD refers to the associated measurement.
[0159] For DL-based signal measurements (e.g., DL RSTD or DL-TDoA) between a sensing Tx node and a sensing target, if the sensing target is equipped with a UE, the DL-TDoA positioning technique (e.g., sensing operation) makes use of DL RSTD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP or RSRPP, DL RSDD, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of DL signals received from multiple sensing Tx nodes (e.g., TPs) , at the sensing target with the UE. All states of the UE are supported to perform the measurement including RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE state.
[0160] In some implementations, the sensing target with the UE (e.g., a UAV / vehicle equipped with a UE) measures the DL RSTD measurements (and optionally other positioning / sensing measurements, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signals using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) , and the resulting measurements are used (e.g., along with other configuration information) to locate (i.e., position) the sensing target in the N-dimensional plane (e.g., 2D, 3D) in relation to the neighboring TPs at (optionally) a specific observation instance. In this case the sensing Rx node is also the sensing target.
[0161] In some implementations, to identify whether the sensing target is equipped with a UE or not, inquiry signaling (e.g., an enhanced paging message) may be defined and used to page (i.e., discover) the UE of the sensing target, followed by an access procedure to configure the relevant resources (e.g., RS resources, reporting resources, etc. ) to derive the measurement results from the target UE.
[0162] In some implementations, the determination of a sensing target being accompanied by a UE device is included in the assistance information provided by the sensing service consumer (e.g., within the initial sensing request message issued by a third party application towards the network for sensing operation and provided to the AF or SF via the network exposure function (NEF) ) . In some examples, the assistance information includes one or more of such UE IDs associated with the said sensing target.
[0163] For UL-based signal measurements (e.g., UL RSTD or UL-RToA) between a sensing Rx node and a sensing target that is equipped with a UE, the UL-TDoA positioning technique (e.g., sensing operation) makes use of the UL-RToA measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP or RSRPP, UL RSDD, UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) at multiple sensing Rx nodes (e.g., RPs) of UL signals transmitted from the sensing target equipped with the UE.
[0164] All states of the UE are supported to perform the measurement including RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE state. In some examples, a UE may be in the RRC INACTIVE or RRC IDLE state, and upon identification of the UE being associated with the sensing target, the UE is first triggered into the RRC_CONNECTED state and thereafter performs UL transmissions for the sensing operation.
[0165] In some implementations, the sensing Rx nodes (e.g., RPs) measure the UL-RToA (and optionally UL-sensing-RS-RSRP / RSRPP, UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) of the received signals using sensing assistance and / or configuration data received from the sensing configuration node, e.g., a sensing server (or positioning server and / or location server) , and the resulting measurements are used (e.g., along with other configuration information) to estimate the location (i.e., position) of the sensing target in the N-dimensional plane (e.g., 2D, 3D) at (optionally) a specific observation instance.
[0166] In some implementations, to identify whether the sensing target is equipped with a UE or not, inquiry signaling (e.g., an enhanced paging message) may be defined and used to page (i.e., discover) the UE of the sensing target, followed by the access procedure to configure the relevant resources (e.g., RS resources, reporting resources, etc. ) to derive the measurement results from the target UE.
[0167] For UE-UE (e.g., device-to-device (D2D) ) links between the sensing Tx node and a sensing target equipped with a UE, the UE-UE link (e.g., SL) TDoA positioning technique (e.g., sensing operation) makes use of the UE-UE-RSTD measurements (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, UE-UE RSDD, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL RS carrier phase (SL-RSCP) or SL RS carrier phase difference (SL-RSCPD) ) received at the sensing target, e.g., UE.
[0168] All states of the UE are supported to perform the measurement including RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE state. In some examples, a UE may be in the RRC_INACTIVE or RRC IDLE state, and upon identification of the UE being associated with the sensing target, the UE is first triggered into the RRC_CONNECTED state and thereafter performs transmission towards the second UE / sensing target, e.g., transmission of a measurement report.
[0169] In some implementations, the sensing target measures the UE-UE-RSTD measurements (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP) or SL-RSCPD) transmitted by two or more peer sensing Tx nodes and using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . The UE-UE-RSTD measurements between a sensing target and multiple peer sensing Tx nodes may be used to determine the location (i.e., position) of the sensing target relative to the locations / positions of the sensing Tx node (e.g., anchor UEs) at (optionally) a specific observation instance. In this case the sensing Rx node is the sensing target.
[0170] The RToA positioning technique (e.g., sensing operation) for the UE-UE link (e.g., SL) makes use of the UE-UE-RToA / ToA (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, UE-UE RSDD, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / RSCPD) received at multiple peer UEs devices of UE-UE signals (e.g., SL signals) transmitted from the sensing target equipped with a UE.
[0171] In some implementations, the peer sensing Rx nodes (e.g., UEs / devices) measure the UE-UE-RToA / ToA (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / SL-RSCPD) of the signals received from the sensing target using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) , and the resulting measurements are used (e.g., along with other configuration information) to estimate the location (i.e., position) of the sensing target at (optionally) a specific observation instance.
[0172] In some implementations, to identify whether the sensing target is equipped with a UE or not, inquiry signaling (e.g., an enhanced paging message) may be defined and used to discover the UE of the sensing target, followed by the procedure to configure the relevant SL resources, e.g., RSs, report, to derive the measurement results from the target UE.
[0173] For a monostatic arrangement of sensing Tx node to sensing target to sensing Rx node, when the sensing target is not equipped with a UE and where the sensing Tx node and the sensing Rx node are the same entity / node, the TDoA positioning technique (e.g., sensing operation) may make use of monostatic RSTD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, DL RSDD, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of sensing-Tx-target-sensing-Rx signals received from A) ToA differencing performed based on ToAs received at the same observation instance with respect to a reference sensing Tx / Rx node; or B) ToA differencing performed based on ToAs received at the different observation instances with respect to a reference observation instance of the sensing target, at the sensing Rx node.
[0174] The sensing-Tx-target-sensing-Rx signals may comprise the sensing Tx node transmitting a RS to the sensing target, and thereafter the same transmitted signal resource is reflected from the sensing target and received by the sensing Rx node. In some implementations, the received signal at the sensing Rx node may be received as a set of specular or diffuse reflected paths in different domains, e.g., angle, delay, Doppler and so forth, and wherein the paths may be identifiable at the sensing Rx node based on an a priori known description, e.g., absolute or relative values for the expected margin of path delay, Doppler shift, AoA or zenith-of-arrival (ZoA) , path energy / power.
[0175] In some implementations, the monostatic RSTD measurements may be computed at the sensing result computation entity. For example, the sensing Rx node (e.g., an RP, a TRP, a base station, or a UE) may measure the round trip ToA relative to the same transmitted RS resource (and optionally other positioning / sensing measurements, sensing-RS-RSRP / RSRPP, DL RSDD, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signal using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . Then, the ToAs are reported to a centralized sensing computation result entity (e.g., a SF or LMF) and are utilized for derivation of the sensing results.
[0176] In some examples, the differencing operations to derive the monostatic RSTD measurements are performed based on the aligned ToAs with the observation instance and / or with respect to a reference sensing Tx node as part of the sensing results computation. The resulting RSTD measurements may be used (e.g., along with other configuration information) to locate (i.e., position) the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance.
[0177] In another implementation, the resulting monostatic RSTD measurements may be used along with DDoA-based measurements (e.g., RSDD measurements) to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance. Tracking the sensing target involves the determination of the velocity, the speed, and / or the bearing (i.e., direction) information.
[0178] In some implementations, the monostatic RSTD measurements may be computed at a reference sensing Tx / Rx node. For example, a reference sensing Rx node (e.g., an RP, a TRP, a base station, or a UE) may measure its own round trip ToA or ToF relative to the same transmitted RS resource (and optionally other positioning / sensing measurements, sensing-RS-RSRP / RSRPP, RSDD, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signal using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . Additionally, the ToAs of other sensing Rx nodes are reported to the reference sensing Rx node, and the differencing operations to derive the monostatic RSTD measurements are performed at the reference sensing Rx node based on the aligned ToAs with the observation instance and / or with respect to a reference sensing Tx node.
[0179] The reference sensing Rx node may be selected (e.g., by the network) according to some criterion or multiple sets of criteria. Exemplary criteria for selecting the reference sensing Rx node include, but are not limited to, the closest sensing Rx node to the sensing target or the sensing Rx node with the highest signal quality (e.g., based on measured RSRP, RSRPP, reference signal received quality (RSRQ) , reference signal strength indicator (RSSI) ) , the line-of-sight (LOS) or non-line-of-sight (NLOS) status of the sensing Rx node with respect to the sensing target, the type of support sensing technique and / or measurement at the sensing Rx node, the sensing processing capabilities at the sensing Rx node, etc. The resulting monostatic RSTD measurements are used (e.g., along with other configuration information) to locate (i.e., position) the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance.
[0180] In another implementation, the resulting monostatic RSTD measurements are used along with DDoA measurements to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance. Tracking the sensing target involves the determination of the velocity and / or speed and / or bearing / direction information.
[0181] For a bistatic arrangement of sensing Tx node to sensing target to sensing Rx node, when the sensing target is not equipped with a UE and where the sensing Tx node and the sensing Rx node are different entities / nodes, the TDoA positioning technique (e.g., sensing operation) makes use of bistatic RSTD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, RSDD, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of sensing-Tx-target-sensing-Rx signals reflected from the sensing target and received by the sensing Rx node. Here, the sensing-Tx-target-sensing-Rx signals may comprise the sensing Tx node transmitting an RS to the sensing target and thereafter the same transmitted signal resource is reflected from the sensing target and received by the sensing Rx node.
[0182] In some implementations, the ToA differencing to derive the bistatic RSTD may be performed at the sensing Rx node based on ToA pairs received at the same observation instance with respect to a selected reference sensing Tx node.
[0183] In some implementations, the relative ToA differencing is performed based at the sensing result computation entity based on received reported relative ToAs at the aligned observation instances from different sensing Rx nodes with respect to a reference time.
[0184] In another implementation, the resulting bistatic RSTD measurements may be used along with DDoA-based measurements (e.g., RSDD measurements) to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance. Tracking the sensing target involves the determination of the velocity and / or speed and / or bearing / direction information.
[0185] Moreover, the FDoA positioning technique for sensing and positioning measures the Doppler shift at the measurement entity. The measured Doppler shift of the sensing target is measured from a pair of stationery sensing Tx / Rx nodes or from a mobile or moving sensing Tx / Rx node. Thereafter, the determination of the difference of the measured Doppler shift is performed and makes use of the following depending on the considered link between the sensing entities / nodes. In general, FDoA (or DDoA) refers to the positioning technique and RSDD (or RSFD) refers to the associated measurement.
[0186] For DL-based signal measurements (e.g., DL RSDD) between a sensing Tx node and a sensing target, if the sensing target is equipped with a UE, the DL-FDoA positioning technique (e.g., sensing operation) makes use of DL RSDD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of downlink signals received from multiple sensing Tx nodes (e.g., TPs) , at the sensing target with the UE.
[0187] In some implementations, the sensing target with the UE (e.g., a UAV / vehicle equipped with a UE) measures the DL RSTD measurements (and optionally other positioning / sensing measurements, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signals using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) , and the resulting measurements are used (e.g., along with other configuration information) to locate (i.e., position) the sensing target in the N-dimensional plane (e.g., 2D, 3D) in relation to the neighboring TPs over a defined duration (e.g., configured observation instance (s) or window) . In this case the sensing Rx node is the sensing target.
[0188] For UL-based signal measurements (e.g., UL RSDD) between a sensing Rx node and a sensing target that is equipped with a UE, the UL-FDoA positioning technique (e.g., sensing operation) makes use of the UL reference signal Doppler (RSD) measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) at multiple sensing Rx nodes (RPs) of uplink signals transmitted from the sensing target equipped with a UE.
[0189] In some implementations, the sensing Rx nodes (RPs) measure the UL-RSDD (and optionally UL-sensing-RS-RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) of the received signals using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) , and the resulting Doppler measurements are used (e.g., along with other configuration information) to estimate the velocity and / or speed and / or bearing / direction of the sensing target in the N-dimensional plane (e.g., 2D, 3D) over a defined duration (e.g., configured observation instance (s) or window) .
[0190] For UE-UE (e.g., D2D) links between the sensing Tx node and a sensing target equipped with a UE, the UE-UE link (e.g., SL) FDoA / DDoA positioning technique (e.g., sensing operation) makes use of the UE-UE-RSDD measurements (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / SL-RSCPD) received at the sensing target, e.g., with UE.
[0191] In some implementations, the sensing target measures the UE-UE-RSDD measurements (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / RSCPD) transmitted by two or more peer sensing Tx nodes and using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . The UE-UE-RSDD measurements between a sensing target and multiple peer sensing Tx nodes may be used to determine the velocity and / or speed and / or bearing / direction of the sensing target relative to the locations (i.e., positions) and / or the velocity or speed and / or bearing of the sensing Tx node (e.g., anchor UEs) at (optionally) a specific observation instance. In this case the sensing Rx node is the sensing target.
[0192] The relative Doppler of arrival (RDoA) and Doppler of arrival (DoA) positioning techniques (e.g., sensing operation) for the UE-UE link (e.g., SL) makes use of the UE-UE-RDoA / DoA (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, sensing RSTD, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / RSCPD) received at multiple peer UEs devices of UE-UE signals transmitted from the sensing target equipped with a UE.
[0193] In some implementations, the peer sensing Rx nodes (e.g., UEs / devices) measure the UE-UE-RDoA / DoA (and optionally other positioning / sensing measurements, e.g., sensing UE-UE-RS-RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, SL-PRS-RSRP and / or SL-PRS-RSRPP and / or SL-RSCP / RSCPD) of the received signals from the sensing target using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) , and the resulting measurements are used (e.g., along with other configuration information) to estimate the locations (i.e., positions) and / or the velocity or speed and / or bearing of the sensing target, optionally over a defined duration (e.g., configured observation instance (s) or window) .
[0194] For a monostatic arrangement of sensing Tx node to sensing target to sensing Rx node, when the sensing target is not equipped with a UE and where the sensing Tx node and the sensing Rx node are the same entity / node, the FDoA / DDoA positioning technique (e.g., sensing operation) may make use of monostatic RSDD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of sensing-Tx-target-sensing-Rx signals received from A) DoA differencing performed based on DoAs received at the same observation instance with respect to a reference sensing Tx / Rx node; or B) DoA differencing performed based on DoAs received at the different observation instances with respect to a reference observation instance of the sensing target, at the sensing Rx node.
[0195] The sensing-Tx-target-sensing-Rx signals may comprise the sensing Tx node transmitting a RS to the sensing target and thereafter the same transmitted signal resource is reflected from the sensing target and received by the sensing Rx node.
[0196] In some implementations, the monostatic RSDD measurements may be computed at the sensing result computation entity. For example, the sensing Rx node (e.g., an RP, a TRP, a base station, or a UE) may measure the round trip Doppler (i.e., two-way Doppler) relative to the same transmitted RS resource (and optionally other positioning / sensing measurements, sensing-RS-RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signal using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . The round trip Doppler (s) are then reported to a centralized sensing computation result entity (e.g., a SF or LMF) and are utilized for derivation of the sensing results.
[0197] In some examples, the differencing operations to derive the monostatic RSDD measurements are performed based on the aligned round trip Doppler (s) with the observation instance and / or with respect to a reference sensing Tx node. The resulting RSDD measurements may be used (e.g., along with other configuration information) to determine the locations (i.e., positions) and / or the velocity or speed and / or bearing of the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance.
[0198] In another implementation, the resulting monostatic RSDD measurements may be used along with RSTD measurements to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific observation instance. Tracking the sensing target involves the determination of the velocity and / or speed and / or bearing / direction information optionally over a defined duration (e.g., configured observation instance (s) or window) .
[0199] In some implementations, the monostatic RSDD measurements may be computed at a reference sensing Tx / Rx node. For example, a reference sensing Rx node (e.g., an RP, a TRP, a base station, or a UE) may measure its own round trip Doppler relative to the same transmitted RS resource (and optionally other positioning / sensing measurements, sensing RSTD, sensing ToA / RTT, sensing-RS-RSRP / RSRPP, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) of the received signal using sensing assistance and / or configuration data received from the sensing configuration node, e.g., sensing server (or positioning server and / or location server) . Additionally, the DoAs and / or round trip Dopplers of other sensing Rx nodes are reported to the reference sensing Rx node, and the differencing operations to derive the monostatic RSDD are performed at the sensing Rx node based on the aligned round trip Dopplers with the observation instance and / or with respect to a reference sensing Tx node.
[0200] The reference sensing Rx node may be selected (e.g., by the network) according to some criterion or multiple sets of criteria. Exemplary criteria for selecting the reference sensing Rx node include, but are not limited to, the closest sensing Rx node to the sensing target or the sensing Rx node with highest signal quality (e.g., based on measured RSRP, RSRPP, RSRQ, RSSI) , the LOS or NLOS status of the sensing Rx node with respect to the sensing target, the type of support sensing technique and / or measurement at the sensing Rx node, the sensing processing capabilities at the sensing Rx node, etc. The resulting monostatic RSDD measurements are used (e.g., along with other configuration information) to locate (i.e., position) the sensing target in the N-dimensional plane (e.g., 2D, 3D) optionally over a defined duration (e.g., configured observation instance (s) or window) .
[0201] In another implementation, the resulting monostatic RSDD measurements are used along with RSTD measurements to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at optionally over a defined duration (e.g., configured observation instance (s) or window) . Tracking the sensing target involves the determination of the velocity and / or speed and / or bearing / direction information.
[0202] For a bistatic arrangement of sensing Tx node to sensing target to sensing Rx node, when the sensing target is not equipped with a UE and where the sensing Tx node and the sensing Rx node are different entities / nodes, the FDoA / DDoA positioning technique (e.g., sensing operation) makes use of bistatic RSDD measurements (and optionally other positioning / sensing measurements, e.g., sensing RSRP / RSRPP, sensing RSTD, sensing ToA / RTT, DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD (carrier phase difference) ) of sensing-Tx-target-sensing-Rx signals reflected from the sensing target and received by the sensing Rx node. Here, the sensing-Tx-target-sensing-Rx signals may comprise the sensing Tx node transmitting an RS to the sensing target and thereafter the same transmitted signal resource is reflected from the sensing target and received by the sensing Rx node.
[0203] In some implementations, the Doppler differencing to derive the bistatic RSDD is performed at the sensing Rx node based on Doppler pairs received at the same defined duration (e.g., configured observation instance (s) or window) with respect to a selected reference sensing Tx node.
[0204] In some implementations, the relative Doppler differencing is performed at the sensing result computation entity based on received relative DoAs at the aligned and defined duration (e.g., configured observation instance (s) or window) reported from different sensing Rx nodes with respect to a reference time.
[0205] In another implementation, the resulting bistatic RSDD measurements are used along with RSTD measurements to track the sensing target in the N-dimensional plane (e.g., 2D, 3D) at a specific over a defined duration (e.g., configured observation instance (s) or window) . Tracking the sensing target involves the determination of the velocity and / or speed and / or bearing / direction information.
[0206] According to aspects of the second solution, techniques and procedures for modeling TDoA and FDoA and supporting their estimation are described for the monostatic case.
[0207] Assuming that:
[0208] Let and be the known position and known velocity, respectively, of the qth sensing Tx node (where q = {1, …, Q} ) . Let and be the known position and known velocity, respectively, of the uth sensing Rx node (where u = {1, …, U} ) . For the monostatic case, and and q=u.
[0209] Let ptarget, 0 and vtarget, 0 be the unknown initial position and velocity of the sensing target. In some implementations, the velocity of the sensing target is constant.
[0210] During motion, the sensing target is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. At every mth observation time, the position of a sensing target (single target assumed) is determined to be:
[0211] This observation time may be defined / configured to the measurement entity in terms of a window, time duration, start and end time, periodicity, window length, measurement observation window ID or combination thereof.
[0212] Multiple round trip Doppler difference, or multiple round trip difference, or multiple ToA difference measurements models are described supporting following implementations: A) the first (i.e., earliest) delay LOS path between the sensing target and the sensing Rx node, or B) an additional delay path between the sensing target and the sensing Rx node relative to the first (i.e., earliest) delay LOS path.
[0213] Figure 5 illustrates an example of a sensing operation 500 for determining monostatic measurements, e.g., monostatic round-trip ToA and / or monostatic round-trip Doppler, in accordance with aspects of the present disclosure. The sensing operation 500 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 500 may include a sensing target 502, a first sensing Tx / Rx node 504, a second sensing Tx / Rx node 506, a third sensing Tx / Rx node 508, and a sensing result computation entity 510. The sensing Tx / Rx nodes may implement or be implemented by one or more NEs 102 and / or one or more UEs 104, and the sensing result computation entity 510 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0214] The sensing operation 500 may include ToA and / or DoA reporting by the sensing Tx / Rx nodes, with differencing performed at the sensing result computation entity 510 (i.e., a centralized entity) . In the depicted example, the second sensing Tx / Rx node 506 is the reference Tx / Rx node. In some implementations, the reference node (e.g., reference Tx node, reference Rx node, or reference Tx / Rx node) may change during an ongoing sensing session.
[0215] During motion, the sensing target 502 is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The first sensing Tx / Rx node 504, second sensing Tx / Rx node 506, and third sensing Tx / Rx node 508 each perform sensing measurements (e.g., monostatic round-trip delay / ToAs and / or monostatic round-trip / two-way Doppler shifts) and report the measurements for each observation to the sensing result computation entity 510. The sensing result computation entity 510 then performs differencing operations on the monostatic round-trip delay / ToA measurements and / or monostatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the second sensing Tx / Rx node 506) based on the reports received from each measurement entity according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0216] Figure 6 illustrates an example of a sensing operation 600 for determining monostatic measurements, such as monostatic round-trip TOA and / or monostatic round-trip Doppler, in accordance with aspects of the present disclosure. The sensing operation 600 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 600 may include a sensing target 602, a first sensing Tx / Rx node 604, a second sensing Tx / Rx node 606, a third sensing Tx / Rx node 608, and a sensing result computation entity 610. The sensing Tx / Rx nodes may implement or be implemented by one or more NEs 102 and / or one or more UEs 104, and the sensing result computation entity 610 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0217] The sensing operation 600 may include ToA and / or DoA reporting by the sensing Tx / Rx nodes, with differencing performed at a reference Tx / Rx node. In the depicted example, the second sensing Tx / Rx node 606 is the reference Tx / Rx node. In some implementations, the reference node may change during an ongoing sensing session.
[0218] During motion, the sensing target 602 is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The first sensing Tx / Rx node 604, second sensing Tx / Rx node 606, and third sensing Tx / Rx node 608 each perform sensing measurements (e.g., monostatic round-trip delay / ToAs and / or monostatic round-trip / two-way Doppler shifts) . The first sensing Tx / Rx node 604 and third sensing Tx / Rx node 608 report the measurements for each observation to the second sensing Tx / Rx node 606. The second sensing Tx / Rx node 606 then performs differencing operations on the monostatic round-trip delay / ToA measurements and / or monostatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the second sensing Tx / Rx node 606) according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0219] After the monostatic round-trip delay / ToAs and monostatic round-trip / two-way Doppler shifts are differenced at the second sensing Tx / Rx node 606, the second sensing Tx / Rx node 606 reports the RSTD and / or RSDD measurements to the sensing result computation entity 610, e.g., as list / index of RSDD and / or RSTD measurements at the aligned observations.
[0220] For the monostatic case, RSTD (based on multiple ToA differencing) may be defined as: RSTDq, ref, m=TOAq, m-TOA2, m, q=1, 3, 4, …Q c (RSTDq, ref, m) =c (TOAq, m) -c (TOA2, m) , q=1, 3, 4, …Q Δrq, ref, m=dq, m-d2, m, q=1, 3, 4, …Q where TDOAq, ref, m is the qth TDoA (e.g., RSTD measurement) in relation to the reference sensing Tx / Rx node, and where Δrq, m refers to the range / distance difference in relation to the reference sensing Tx / Rx node. In another implementation, the estimated velocity or speed of the sensing target at each mth observation time point / instance may be determined using the determined position based on the above ToAs and / or RSTD measurements and the time at each mth observation time point / instance. Accordingly, the sensing operation may include determining the rate of change of displacement or distance covered at each mth observation time point / instance.
[0221] The monostatic ToA measured at the measurement entity is the two-way travel time or round-trip time of the transmitted RS. The true distance (i.e., along a LOS path) between the sensing target and sensing Tx / Rx node may be calculated as:
[0222] The monostatic RSFD (i.e., RSDD) is given as: Δvq, m=vq, m-v2, m, q=1, 3, 4, …Q where FDOAq, ref, m is the qth FDoA (e.g., RSFD / RSDD measurement) in relation to reference sensing Tx / Rx node, and where λ is the carrier frequency wavelength. The Δvq, ref, m is referred to as the measured velocity difference in relation to a reference sensing Tx / Rx node. The fDoppler measured at the measurement entity is the two-way Doppler or round trip Doppler of the transmitted RS.
[0223] According to aspects of the third solution, techniques and procedures for modeling TDoA and FDoA and supporting their estimation are described for the bistatic case.
[0224] Assuming that:
[0225] Let and be the known position and known velocity, respectively, of the qth sensing Tx node (where q = {1, …, Q} ) . Let and be the known position and known velocity, respectively, of the uth sensing Rx node (where u = {1, …, U} ) . For the bistatic case, and and q≠u.
[0226] Let ptarget, 0 and vtarget, 0 be the unknown initial position and velocity of the sensing target. In some implementations, the velocity of the sensing target is constant.
[0227] While in motion, the sensing target is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. At every mth observation time, the position of a sensing target (single target assumed) is determined to be:
[0228] This observation time may be defined / configured to the measurement entity in terms of a window, time duration, start and end time, periodicity, window length, measurement observation window ID or combination thereof.
[0229] Multiple round trip Doppler difference, or multiple round trip difference, or multiple ToA difference measurements models are described supporting following implementations: A) the first (i.e., earliest) delay LOS path between the sensing target and the sensing Rx node, or B) an additional delay path between the sensing target and the sensing Rx node relative to the first (i.e., earliest) delay LOS path.
[0230] Figure 7 illustrates an example of a sensing operation 700 for determining bistatic measurements, such as bistatic round-trip ToA and / or bistatic round-trip Doppler, in accordance with aspects of the present disclosure. The sensing operation 700 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 700 may include a sensing target 702, a first sensing Tx node 704, a second sensing Tx node 706, a third sensing Tx node 708, a sensing Rx node 710, and a sensing result computation entity 712. The sensing Tx nodes 704, 706, 708 and the sensing Rx node 710 may implement or be implemented by one or more NEs 102 and / or one or more UEs 104, and the sensing result computation entity 712 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0231] The sensing operation 700 may include TRP-TRP bistatic ToAs or Rx-Tx time differences (i.e., round-trip delays) and / or two-way Doppler shift measurements differenced by the sensing Rx node 710 with respect to the stationary sensing Tx nodes 704, 706, 708. In the depicted example, the first sensing Tx node 704 is the reference node. In some implementations, the reference node may change during an ongoing sensing session.
[0232] During motion, the sensing target 702 is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The first sensing Tx node 704, second sensing Tx node 706, and third sensing Tx node 708 each transmit sensing signals (e.g., RS) and the sensing Rx node 710 performs measurements of the reflected sensing signals (e.g., bistatic round-trip delay / ToAs and / or bistatic round-trip / two-way Doppler shifts) . As depicted, each transmitted sensing signal and corresponding reflection is associated with a bistatic angle βn, which may include azimuth (αn) and elevation (θn) components.
[0233] In some implementations, the sensing Rx node 710 performs differencing operations on the bistatic round-trip delay / ToA measurements and / or bistatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the first sensing Tx node 704) according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0234] In some implementations, one or more of the first sensing Tx node 704, second sensing Tx node 706, and third sensing Tx node 708 may transmit assistance information (e.g., TRP assistance information) to the sensing Rx node 710. In certain implementations, the respective assistance information received from a sensing Tx node includes information for mitigating sensing measurement errors, such as measurement noise / uncertainty, timing clock offset / bias at the sensing Tx node, timing error group information at the sensing Tx node, frequency offset / bias at sensing Tx node, and / or timing or frequency synchronization errors.
[0235] In certain implementations, the respective assistance information received from a sensing Tx node may further include a real time difference between a set of sensing Tx nodes, a relative time difference between the set of sensing Tx nodes, quality information for the real time difference or relative time difference, sensing integrity information, sensing transmitter location information, sensing transmitter beam information, a real transmit frequency difference, a relative transmit frequency difference, time offset information, frequency offset information, quality information for the time offset information or the frequency offset information, expected sensing target LOS or NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , velocity information, and / or movement path information.
[0236] After the bistatic round-trip delay / ToAs and bistatic round-trip / two-way Doppler shifts are differenced at the sensing Rx node 710, the sensing Rx node 710 reports the RSTD and / or RSDD measurements to the sensing result computation entity 712, e.g., as list / index of RSDD and / or RSTD measurements at the aligned observations.
[0237] Figure 8 illustrates an example of a sensing operation 800 for determining the bistatic round-trip TOA and / or bistatic round-trip Doppler in accordance with aspects of the present disclosure. The sensing operation 800 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 800 may include a sensing target 802, a first sensing Tx node 804, a second sensing Tx node 806, a third sensing Tx node 808, a sensing Rx node 810, and a sensing result computation entity 812. The sensing Tx nodes 804, 806, 808 may implement or be implemented by one or more UEs 104, the sensing Rx node 810 may implement or be implemented by an NE 102, and the sensing result computation entity 812 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0238] The sensing operation 800 may include UE-TRP bistatic ToAs or Rx-Tx time differences (i.e., round-trip delays) and / or two-way Doppler shift measurements differenced by the stationary sensing Rx node 810 with respect to the mobile sensing Tx nodes 804, 806, 808. In the depicted example, the first sensing Tx node 804 is the reference node. In some implementations, the reference node may change during an ongoing sensing session.
[0239] During motion, the sensing target 802 is observed a total of M times, m={0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The first sensing Tx node 804, second sensing Tx node 806, and third sensing Tx node 808 each transmit sensing signals (e.g., RS) and the sensing Rx node 810 performs measurements of the reflected sensing signals (e.g., bistatic round-trip delay / ToAs and / or bistatic round-trip / two-way Doppler shifts) . As depicted, each transmitted sensing signal and corresponding reflection is associated with a bistatic angle βn, which may include azimuth (αn) and elevation (θn) components.
[0240] In some implementations, the sensing Rx node 810 performs differencing operations on the bistatic round-trip delay / ToA measurements and / or bistatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the first sensing Tx node 804) according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0241] In some implementations, one or more of the first sensing Tx node 804, second sensing Tx node 806, and third sensing Tx node 808 may transmit assistance information (e.g., UE assistance information) to the sensing Rx node 810.
[0242] After the bistatic round-trip delay / ToAs and bistatic round-trip / two-way Doppler shifts are differenced at the sensing Rx node 810, the sensing Rx node 810 reports the RSTD and / or RSDD measurements to the sensing result computation entity 812, e.g., as list / index of RSDD and / or RSTD measurements at the aligned observations.
[0243] Figure 9 illustrates an example of a sensing operation 900 for determining the bistatic round-trip TOA and / or bistatic round-trip Doppler in accordance with aspects of the present disclosure. The sensing operation 900 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 900 may include a sensing target 902, a first sensing Tx node 904, a second sensing Tx node 906, a third sensing Tx node 908, a sensing Rx node 910, and a sensing result computation entity 912. The sensing Tx nodes 904, 906, 908 may implement or be implemented by one or more NEs 102, the sensing Rx node 910 may implement or be implemented by a UE 104, and the sensing result computation entity 912 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0244] The sensing operation 900 may include TRP-UE bistatic ToAs or Rx-Tx time differences (i.e., round-trip delays) and / or two-way Doppler shift measurements differenced by the mobile sensing Rx node 910 with respect to the stationary sensing Tx nodes 904, 906, 908. In the depicted example, the first sensing Tx node 904 is the reference node. In some implementations, the reference node may change during an ongoing sensing session.
[0245] During motion, the sensing target 902 is observed a total of M times, m= {0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The first sensing Tx node 904, second sensing Tx node 906, and third sensing Tx node 908 each transmit sensing signals (e.g., RS) and the sensing Rx node 910 performs measurements of the reflected sensing signals (e.g., bistatic round-trip delay / ToAs and / or bistatic round-trip / two-way Doppler shifts) . As depicted, each transmitted sensing signal and corresponding reflection is associated with a bistatic angle βn, which may include azimuth (αn) and elevation (θn) components.
[0246] The sensing Rx node 910 performs differencing operations on the bistatic round-trip delay / ToA measurements and / or bistatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the first sensing Tx node 904) according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0247] In some implementations, one or more of the first sensing Tx node 904, second sensing Tx node 906, and third sensing Tx node 908 may transmit assistance information (e.g., TRP assistance information) to the sensing Rx node 910.
[0248] After the bistatic round-trip delay / ToAs and bistatic round-trip / two-way Doppler shifts are differenced at the sensing Rx node 910, the sensing Rx node 910 reports the RSTD and / or RSDD measurements to the sensing result computation entity 912, e.g., as list / index of RSDD and / or RSTD measurements at the aligned observations.
[0249] For the bistatic case, multiple-ToA differencing models (assuming the first LOS path) may be defined as: RSTDq, ref, m=TOAq, m-TOA1, m, q=1, 3, 4, …Q c (RSTDq, ref, m) =c (TOAq, m) -c (TOA1, m) , q=1, 3, 4, …Q where TDOAq, ref, m is the qth TDoA (e.g., RSTD measurement) in relation to the reference sensing Tx / Rx node, and where Δrq, m refers to the range / distance difference in relation to the reference sensing Tx / Rx node. In another implementation, the estimated velocity or speed of the sensing target at each mth observation time point / instance can determined using the determined position based on the above ToAs and / or RSTD measurements and the time at each mth observation time point / instance. Accordingly, the sensing operation may include determining the rate of change of displacement or distance covered at each mth observation time point / instance.
[0250] The bistatic ToA measured at the measurement entity is the two-way travel time or round-trip time of the transmitted RS. The true distance (i.e., along a LOS path) between the sensing Tx node and the sensing target and between the sensing target and sensing Rx node (i.e., a bistatic range) may be calculated as:
[0251] The bistatic RSFD (i.e., RSDD) is given as: Δvq, m=vq, m-v2, m, q=1, 3, 4, …Q where FDOAq, ref, m is the qth FDoA (e.g., RSFD / RSDD measurement) in relation to the reference sensing Tx node and a sensing Rx node, and where λ is the carrier frequency wavelength. The Δvq, ref, m is referred to as the measured velocity difference in relation to reference sensing Tx / Rx node. The fBi-Doppler measured at the measurement entity (sensing Rx node) is the bi-static Doppler of the transmitted RS taking into account the bistatic angle vector (β) and bistatic bisector angle vector
[0252] The bistatic angle vector comprises bistatic azimuth (α) and elevation (θ) angles and the bisector angle equally applies to these angles. δ is the vector angle (comprising also azimuth and elevation angles) of the velocity of the sensing target projected on to the bistatic bisector, where if δ=0
[0253] Figure 10 illustrates an example of a sensing operation 1000 for determining the bistatic round-trip TOA and / or bistatic round-trip Doppler in accordance with aspects of the present disclosure. The sensing operation 1000 may implement or be implemented by aspects of the wireless communication system 100. For example, the sensing operation 1000 may include a sensing target 1002, a sensing Tx node 1004, a first sensing Rx node 1006, a second sensing Rx node 1008, a third sensing Rx node 1010, and a sensing result computation entity 1012. The sensing Tx node 1004, may implement or be implemented by an NE 102, the first sensing Rx node 1006 may implement or be implemented by a UE 104, the sensing Rx node 1008, 1010 may implement or be implemented by one or more NEs 102, and the sensing result computation entity 1012 may implement or be implemented by a node in the CN 106 (e.g., a SF) as described herein.
[0254] The sensing operation 1000 may include TRP-UE and TRP-TRP bistatic ToAs or Rx-Tx time differences (i.e., round-trip delays) and / or two-way Doppler shift measurements with differencing performed at each sensing Rx node 1006, 1008, 1010 based on a single Tx source (multiple Tx sources are also supported by extension) with the aid of received ToAs and / or Two-way Doppler measurements of other sensing Rx node (s) . In the depicted example, the second sensing Rx node 1008 is the reference node. In some implementations, the reference node may change during an ongoing sensing session.
[0255] During motion, the sensing target 1002 is observed a total of M times, m= {0, 1, 2, …, M} (from measurement entity perspective) , with Δt time interval between each spacings. The sensing Tx node 1004 transmits sensing signals (e.g., RS) and the sensing Rx nodes 1006, 1008, and 1010 each perform measurements of the reflected sensing signal (e.g., bistatic round-trip delay / ToAs and / or bistatic round-trip / two-way Doppler shifts) . As depicted, the sensing signal transmitted by the single sensing Tx node 1004 and each of the corresponding reflections are associated with a bistatic angle βn, which may include azimuth (αn) and elevation (θn) components.
[0256] The sensing Rx nodes 1006, 1008, and 1010 each perform differencing operations on the bistatic round-trip delay / ToA measurements and / or bistatic round-trip / two-way Doppler shift measurements in relation to the reference node (i.e., the second sensing Rx node 1006) according to aligned / same observation instances or a reference observation instance. An example of a reference observation instance may be the start time of the observation window (initial position / velocity instance, m=0) .
[0257] The distributed sensing Rx nodes 1006, 1008, and 1010 are assumed to be mutually synchronized and can passively receive the signals backscattered / reflected from the sensing target 1002 and originating from a separate synchronous (or asynchronous) sensing transmit source (i.e., the sensing Tx node 1004) . While Figure 10 depicts the sensing Tx node 1004 as a TRP (e.g., base station or gNB) , in other implementations, the separate sensing transmit source may be a UE, a CPE, a PRU, or an SRU, or a similar device.
[0258] In some implementations, the sensing Tx node 1004 may transmit assistance information (e.g., Tx assistance information) to the sensing Rx nodes 1006, 1008, and 1010 to assist in the measurement of the backscattered / reflected signal as detailed in Tables 6-11 below. In addition, the sensing Rx nodes 1006, 1008, and 1010 may exchange further assistance information (e.g., Rx assistance information) to assist in performing accurate and robust RSTD and / or RSDD measurements. Examples of such assistance information may include synchronization information, clock / timing offset information, Doppler / frequency offset information, sensing Tx node interference information / mitigation information and so forth. In certain implementations, the sensing Rx nodes may be a TRP (e.g., base station, gNB, etc. ) In other implementations, the sensing Rx nodes may be a UE, or CPE, or PRU, or SRU, or a similar device.
[0259] The sensing Rx nodes 1006, 1008, and 1010 may exchange the measured ToAs and / or two-way Doppler measurements to aid in performing the differencing operation at each sensing Rx node. In other words, each sensing Rx node may determine the RSTD and / or RSDD with respect to the other sensing Rx nodes.
[0260] For example, at the first sensing Rx node 1006, the RSTD and / or RSDD would be based on the Rx measurement pair of [Rx1-Rx2] and [Rx1-Rx3] (e.g., referring to ToA and / or Doppler shift differences relative to the second sensing Rx node 1008 and the third sensing Rx node 1010, respectively) . Similarly at the second sensing Rx node 1008, the RSTD and / or RSDD would be based on the Rx measurement pair of [Rx2-Rx1] and [Rx2-Rx3] (e.g., referring to ToA and / or Doppler shift differences relative to the first sensing Rx node 1006 and the third sensing Rx node 1010, respectively) , and at the third sensing Rx node 1010, the RSTD and / or RSDD would be based on the Rx measurement pair of [Rx3-Rx1] and [Rx3-Rx2] (e.g., referring to ToA and / or Doppler shift differences relative to the first sensing Rx node 1006 and the second sensing Rx node 1008, respectively) .
[0261] After the bistatic round-trip delay / ToAs and bistatic round-trip / two-way Doppler shifts are differenced, each sensing Rx node may subsequently transmit its own measured RSTD and / or RSDD measurement report to the sensing result computation entity 1012, e.g., as list / index of RSDD and / or RSTD measurements at the aligned observations.
[0262] According to aspects of the fourth solution, a measurement entity (e.g., sensing Rx node) associated with a sensing operation may receive configuration and assistance information to enable accurate monostatic and / or bistatic measurements, such as RSTD measurements, RSDD measurements, round-trip delay measurements, ToA measurements, time-of-departure (ToD) measurements, monostatic round-trip Doppler shifts measurements, monostatic two-way Doppler shifts measurements, bistatic round-trip Doppler shifts measurements, and / or bistatic two-way Doppler shifts measurements.
[0263] In some implementations, a sensing configuration node (such as a sensing result computation entity) provides assistance data and / or configuration information to the sensing Rx node (e.g., as part of a sensing procedure or a joint sensing and positioning procedure) . In certain implementations, the sensing Rx node may request the sensing configuration node to provide sensing assistance data and / or configuration information, wherein the sensing configuration node transmits the assistance data and / or configuration information in response to the request.
[0264] In another implementation, the sensing configuration node may also provide the sensing Rx node with pre-configured sensing assistance data and / or configuration information (e.g., with associated validity criteria, such as at least one sensing area validity criterion and / or at least one time validity criterion) to be utilized for potential positioning, sensing measurements or combination thereof at future time instance (s) . In certain implementations, the pre-configured sensing assistance data and / or configuration information is provided to the sensing Rx node before or during an ongoing sensing session. The pre-configured sensing assistance data and / or configuration information may consist of multiple instances, where each instance is applicable to a different sensing or configuration area within the network. One or more instances of sensing assistance data and / or configuration information may be provided.
[0265] In one implementation, each instance of sensing assistance data and / or configuration information is provided in one sensing protocol message (e.g., a separate sensing protocol message for each instance) . In another implementation, multiple instances of the sensing assistance data and / or configuration information may be provided in a sensing protocol message (e.g., a sensing protocol message may combine data / information for multiple instances) .
[0266] In some implementations, if a sensing Rx node receives sensing assistance data and / or configuration information for a sensing Tx node for which it has already stored sensing assistance data and / or configuration information, then the sensing Rx node may overwrite the stored sensing assistance data and / or configuration information. In other implementations, if a sensing Rx node receives sensing assistance data and / or configuration information for a sensing Tx node for which it has not previously stored sensing assistance data and / or configuration information, then the sensing Rx node may store the sensing assistance data and / or configuration information for the sensing Tx node and maintain the already stored assistance data for other sensing Tx nodes.
[0267] In some implementations, the sensing Tx node may be uniquely identified using a combination of various identifiers including but not limited to sensing-RS-IDs (resource IDs, resource set IDs) and Cell-IDs such as PCI, ARFCN, cell global identity (CGI) (e.g., also including NR CGI (NCGI) , 6G CGI) . In certain implementations, the number of sensing Tx nodes for which the sensing Rx node can store sensing assistance data and / or configuration information is a sensing Rx node capability and may be indicated by the number of areas a UE can support.
[0268] In some implementations, the sensing assistance data and / or configuration information may be requested in an on-demand or dynamic manner based on an already received or stored sensing assistance data and / or configuration information. For example, this may be required when any of the sensing KPIs (or service requirements, or sensing QoS) changes for any given reason. In some implementations, the RS parameters for performing sensing may also be dynamically updated including bandwidth, number of sensing symbols, sensing time or frequency offset, sensing muting patterns, sensing transmit power, and so forth.
[0269] Figure 11 illustrates an example of a measurement entity-initiated procedure 1100 for exchanging sensing assistance data / configuration information in accordance with aspects of the present disclosure. The procedure 1100 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1100 may include a sensing configuration node and / or sensing result computation entity 1102, and a sensing measurement entity 1104, such as a RAN entity or UE. The sensing configuration node and / or sensing result computation entity 1102, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) . The sensing measurement entity 1104 may implement or be implemented by a NE 102 or a UE 104.
[0270] The procedure 1100 begins at Step 1, where the sensing measurement entity 1104 transmits a request for sensing assistance data and / or configuration information to the sensing configuration node and / or sensing result computation entity 1102 (see messaging 1106) . In some implementations, the request is transmitted via a sensing interface, such as a RAN-CN / RAN interface, a UE-RAN interface, or a UE-CN interface.
[0271] At Step 2, the sensing configuration node and / or sensing result computation entity 1102 transmits a response message to provide the sensing assistance data and / or configuration information to the sensing measurement entity 1104 (see messaging 1108) . In some implementations, the response is transmitted via the sensing interface.
[0272] In some implementations, the sensing assistance data and / or configuration information may be for the sensing measurement entity 1104 performing sensing measurements, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1100 may be extended for any sensing technique or joint sensing and positioning technique (s) .
[0273] At optional Step 3, the sensing configuration node and / or sensing result computation entity 1102 may periodically deliver sensing assistance data and / or configuration information to the sensing measurement entity 1104, e.g., in order to meet TDoA-and / or FDoA / DDoA-based measurement requirements (see messaging 1110) . In some implementations, the periodic message is transmitted via the sensing interface.
[0274] Figure 12 illustrates an example of a procedure 1200 for exchanging sensing assistance data / configuration information in accordance with aspects of the present disclosure. The procedure 1200 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1200 may include a first sensing measurement entity 1202, a second sensing measurement entity 1204, an n-th sensing measurement entity 1206, and a configuration node and / or sensing result computation entity 1208, such as a RAN entity or CN entity. The sensing measurement entities 1202, 1204, and 1206 may implement or be implemented by one or more NEs 102 and / or one or more UEs 104. The sensing configuration node and / or sensing result computation entity 1208, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) .
[0275] The procedure 1200 begins at Step 1, where the sensing configuration node and / or sensing result computation entity 1208 determines sensing assistance data and / or configuration information needed to be provided to the measurement entity (e.g., as part of a sensing / positioning procedure) and transmits a message to the sensing measurement entities 1202, 1204, and 1206 to provide the sensing assistance data and / or configuration information (see messaging 1210) . In some implementations, the message is transmitted via a sensing interface, such as a CN / RAN-RAN interface, a RAN-UE interface, or a CN-UE interface.
[0276] In some implementations, the sensing assistance data and / or configuration information may be for the sensing measurement entity 1204 performing sensing measurements, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1200 may be extended for any sensing technique or joint sensing and positioning technique (s) .
[0277] At optional Step 2, the sensing configuration node and / or sensing result computation entity 1208 may periodically deliver sensing assistance data and / or configuration information to the sensing measurement entities 1202, 1204, and 1206, e.g., in order to meet TDoA-and / or FDoA / DDoA-based measurement requirements (see messaging 1212) . In some implementations, the periodic message is transmitted via the sensing interface.
[0278] Figure 13 illustrates an example of a UE-UE procedure 1300 for exchanging sensing assistance data / configuration information in accordance with aspects of the present disclosure. The procedure 1300 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1300 may include a first sensing measurement entity 1302, a second sensing measurement entity 1304, an n-th sensing measurement entity 1306, and a configuration node and / or sensing result computation entity 1308. The sensing measurement entities 1302, 1304, and 1306 and the sensing configuration node and / or sensing result computation entity 1308, may each implement or be implemented by a UE 104.
[0279] The procedure 1300 begins at Step 1, where the sensing configuration node and / or sensing result computation entity 1308 determines sensing assistance data and / or configuration information needed to be provided to the measurement entity (e.g., as part of a sensing / positioning procedure) and transmits a message to the sensing measurement entities 1302, 1304, and 1306 to provide the sensing assistance data and / or configuration information (see messaging 1310) . In some implementations, the message is transmitted via a UE-UE sensing interface.
[0280] In some implementations, the sensing assistance data and / or configuration information may be for the sensing measurement entity 1304 performing sensing measurements, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1300 may be extended for any sensing technique or joint sensing and positioning technique (s) .
[0281] At optional Step 2, the sensing configuration node and / or sensing result computation entity 1308 may periodically deliver sensing assistance data and / or configuration information to the sensing measurement entities 1302, 1304, and 1306, e.g., in order to meet TDoA-and / or FDoA / DDoA-based measurement requirements (see messaging 1312) . In some implementations, the periodic message is transmitted via the UE-UE sensing interface.
[0282] In some other implementations, the sensing target of the sensing procedure may also be a measurement entity for the sensing procedure. In certain implementations, the sensing configuration node may therefore provide the sensing assistance data and / or configuration information to the sensing target. In certain implementations, the sensing target may provide sensing assistance data and / or configuration information to the sensing configuration node. In the case that the sensing target is equipped with a UE, the sensing target may provide assistance information in a solicited or unsolicited manner. Additionally, the sensing target may receive the sensing assistance data and / or configuration information based on a request sent to the sensing configuration node.
[0283] In various implementations, the sensing assistance data and / or configuration information may be provided in one of the following cases. In a first case, the sensing assistance data and / or configuration information may be sent from the sensing Tx node directly to a sensing Rx node via UE-specific signaling or sent directly to one or more sensing Rx nodes via group or broadcast signaling.
[0284] When the sensing Rx node is a TRP, the sensing assistance data and / or configuration information may be sent via TRP-TRP interface, e.g., using TRP-specific Xn or 6GXn signaling, or equivalent, or using a new broadcast signaling to multiple TRPs via a wired or wireless interface.
[0285] When the sensing Rx node is a UE, the sensing assistance data and / or configuration information may be sent via UE-TRP interface, e.g., using UE-specific signaling (such as lower layer (L1 or L2) signaling, UL medium access control (MAC) control element (CE) , radio resource control (RRC) , control plane, user plane, data plane protocol, or any access stratum (AS) signaling equivalent) or using broadcast signaling to multiple UEs (such as a sensingSIB, posSIB, normalSIB) , or a combination thereof.
[0286] In a second case, the sensing assistance data and / or configuration information may be sent from the sensing Tx node to a CN entity (e.g., SF) , and the CN entity forwards the sensing assistance data and / or configuration information to a sensing Rx node.
[0287] In some implementations, the sensing Tx node reports assistance information to the SF via UL NAS, UL LPP, or UL Data plane or UL new sensing protocol signaling. In some implementations, the SF provides the assistance information to the sensing Rx node (s) , e.g., UE (s) and / or TRP (s) . When the sensing Rx node is a UE, the SF may use DL NAS, or DL Data plane or DL sensing protocol signaling to forward the sensing assistance data and / or configuration information. When the sensing Rx node is a TRP, the SF may use a SF-TRP interface (e.g., next generation application protocol (NGAP) , 6G NGAP, NR positioning protocol A (NRPPa) ) or a new interface between SF-TRP to forward the sensing assistance data and / or configuration information.
[0288] Tables 6-11 depict some exemplary message contents of the assistance data and / or configuration information exchange. The contents in Tables 6-11 may be sent in a single message (e.g., a TRP / UE assistance information report) or in separate messages. Table 6: Relative Time Difference (RTD) Information Table 7: Real Frequency Difference (RFD) Information Table 8: Tx Assistance Information Table 9: RS Resource Information Table 10: Target and Path Assistance Information Table 11: Expected Measurement Information
[0289] In one implementation, the measured joint position and velocity may serve as assistance information to assist in supporting sensing operations along a pre-determined / predicted route or flight path of the sensing target. In one example of this implementation, depending on the determined 2D / 3D position, the velocity and the direction / bearing of the sensing target at a given time instance t0 based on one or more sensing or positioning measurements (e.g., including the above-described TDoA-and FDoA-based measurements) in a particular cell associated to one or more gNBs / TRPs along the route or flight path may be better provisioned from a sensing operational perspective.
[0290] One of the exemplary actions includes the setup of one or more sensing observation window (s) from one or more gNB (s) / TRP (s) along the predicted / pre-determined route in which to position and track the sensing target based on the expected arrival time of the sensing target within the coverage of the cell. The expected / predicted sensing target arrival time / velocity / location is derived from the 2D / 3D position, velocity and direction / bearing of the sensing target as determined in a previous time instance t0.
[0291] In some other embodiments, the description of the sensing target’s mobility pattern, movement path / route, and / or time-dependent description of heading / velocity is communicated to a sensing Rx node and / or sensing Tx node as an assistance information (e.g., sensing assistance data) for an indicated / configured measurement associated with the sensing target. In some such embodiments, the radio node utilizes the added information of the assistance information for the purpose of measurement optimization and / or transmission adjustments. In some embodiments, the assistance information is defined over a time-window / observation window for which the mobility pattern / pathway is expected to be valid.
[0292] In some embodiments, the measurement of a sensing measurement node includes determination of a deviation from the indicated pattern (e.g., upon determination of the target UAV has deviated from the indicated pathway) .
[0293] In some embodiments, the assistance information (e.g., sensing assistance data) is translated into the LCS of the participating radio node (e.g., sensing Rx node and / or sensing Tx node) and communicated to the participating radio node. In some other embodiments, the assistance information is communicated to the participating radio node in the GCS or another coordinate system known to the participating radio node.
[0294] According to aspects of the fifth solution, a measurement entity (e.g., sensing Rx node) associated with a sensing operation may receive a reporting configuration and thereafter the measurement entity may respond with a measurement report. In some implementations, the measurement report may include monostatic and / or bistatic measurements, such as RSTD measurements, RSDD measurements, round-trip delay measurements, ToA measurements, ToD measurements, monostatic round-trip Doppler shifts measurements, monostatic two-way Doppler shifts measurements, bistatic round-trip Doppler shifts measurements, and / or bistatic two-way Doppler shifts measurements, e.g., according to the received measurement configuration.
[0295] In some implementations, the measurement report may be transmitted from the measurement entity via an unsolicited request based on a prior event trigger or reporting. In another implementation, the sensing configuration node may build an association based on an ID of the above-described sensing measurement or sensing measurement object ID. This implies that for a specific sensing measurement ID / sensing measurement object ID / measurement report ID, the association may be made for the report for that requested ID.
[0296] In some implementations, the measurement report may comprise multiple measurement IDs based on the received requests. In another implementation, the sensing protocol or transport interface may define transaction IDs for a transaction may be initiated to collect one or more sensing / positioning measurements, the request and report of these measurements may be differentiated based on the transaction ID.
[0297] Figure 14 illustrates an example of a sensing configuration node-initiated procedure 1400 for report configuration and measurement reporting in accordance with aspects of the present disclosure. The procedure 1400 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1400 may include a sensing configuration node and / or sensing result computation entity 1402, and a sensing measurement entity 1404, such as a RAN entity or UE. The sensing configuration node and / or sensing result computation entity 1402, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) . The sensing measurement entity 1404 may implement or be implemented by a NE 102 or a UE 104.
[0298] The procedure 1400 begins at Step 1, where the sensing configuration node and / or sensing result computation entity 1402 transmits a request for sensing TDoA-and / or FDoA / DDoA-based measurements and a reporting configuration to the sensing measurement entity 1404 (see messaging 1406) . In some implementations, the request is transmitted via a sensing interface, such as a CN / RAN-RAN interface, a RAN-UE interface, or a CN-UE interface.
[0299] At Step 2, the sensing measurement entity 1404 transmits a response message to provide a sensing measurement report (e.g., comprising the requested TDoA-and / or FDoA / DDoA-based measurements) to the sensing configuration node and / or sensing result computation entity 1402 (see messaging 1408) . In some implementations, the response is transmitted via the sensing interface.
[0300] In some implementations, the sensing measurement report may include any of the sensing measurements performed by the sensing measurement entity 1404, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1400 may be extended to other sensing techniques or any joint sensing and positioning techniques. Additionally, any positioning / sensing results based on TDoA-and / or FDoA / DDoA-based measurements may also be provided in this step.
[0301] At optional Step 3, the sensing measurement entity 1404 may periodically deliver sensing TDoA-and / or FDoA / DDoA-based measurement reports to the sensing configuration node and / or sensing result computation entity 1402 (see messaging 1410) . In some implementations, the periodic message is transmitted via the sensing interface.
[0302] Figure 15 illustrates an example of a procedure 1500 for unsolicited measurement reporting in accordance with aspects of the present disclosure. The procedure 1500 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1500 may include a first sensing measurement entity 1502, a second sensing measurement entity 1504, an n-th sensing measurement entity 1506, and a configuration node and / or sensing result computation entity 1508, such as a RAN entity or CN entity. The sensing measurement entities 1502, 1504, and 1506 may implement or be implemented by one or more NEs 102 and / or one or more UEs 104. The sensing configuration node and / or sensing result computation entity 1508, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) .
[0303] The procedure 1500 begins at Step 1, where the sensing measurement entities 1502, 1504, and 1506 determine that sensing measurements, including but not limited to TDoA-and / or FDoA / DDoA-based measurements, need to be reported (e.g., as part of a sensing / positioning procedure) and transmits a measurement report to the sensing configuration node and / or sensing result computation entity 1508 containing the sensing measurements (see messaging 1510) .
[0304] In some implementations, the sensing measurement report may include any of the sensing measurements performed by the sensing measurement entities 1502, 1504, and 1506, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1500 may be extended to other sensing techniques or any joint sensing and positioning techniques. Additionally, any positioning / sensing results based on TDoA-and / or FDoA / DDoA-based measurements may also be provided in this step.
[0305] At optional Step 2, the sensing measurement entities 1502, 1504, and 1506 may periodically deliver sensing TDoA-and / or FDoA / DDoA-based measurement reports to the sensing configuration node and / or sensing result computation entity 1508 (see messaging 1512) . In some implementations, the periodic report is transmitted via the sensing interface.
[0306] Figure 16 illustrates an example of a UE-UE procedure 1600 for report configuration and measurement reporting in accordance with aspects of the present disclosure. The procedure 1600 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1600 may include a first sensing measurement entity 1602, a second sensing measurement entity 1604, an n-th sensing measurement entity 1606, and a configuration node and / or sensing result computation entity 1608. The sensing measurement entities 1602, 1604, and 1606 and the sensing configuration node and / or sensing result computation entity 1608, may each implement or be implemented by a UE 104.
[0307] The procedure 1600 begins at Step 1, where the sensing measurement entities 1602, 1604, and 1606 determine that sensing measurements, including but not limited to TDoA-and / or FDoA / DDoA-based measurements, need to be reported (e.g., as part of a sensing / positioning procedure) and transmits a measurement report to the sensing configuration node and / or sensing result computation entity 1608 containing the sensing measurements (see messaging 1610) . In some implementations, the report is transmitted via a UE-UE sensing interface.
[0308] In some implementations, the sensing measurement report may include any of the sensing measurements performed by the sensing measurement entities 1602, 1604, and 1606, including but not limited to TDoA-and / or FDoA / DDoA-based measurements. In another implementation, the exchange procedure 1600 may be extended to other sensing techniques or any joint sensing and positioning techniques. Additionally, any positioning / sensing results based on TDoA-and / or FDoA / DDoA-based measurements may also be provided in this step.
[0309] At optional Step 2, the sensing measurement entities 1602, 1604, and 1606 may periodically deliver sensing TDoA-and / or FDoA / DDoA-based measurement reports to the sensing configuration node and / or sensing result computation entity 1608 (see messaging 1612) . In some implementations, the periodic report is transmitted via the UE-UE sensing interface.
[0310] The reporting configuration depicted in Step 1 of Figure 14 may include one or more of the following information: A) a trigger to perform requested sensing measurements (e.g., an activation indication) ; B) an TRP-SF interface transaction ID; C) SF measurement ID; D) observation window information (e.g., including one or more of: 1) an observation window ID, 2) a window length, 3) a number of requested observations (M) , 4) an interval between observations (Δt) , 5) a granularity of observation) ; E) a TRP measurement request list (e.g., 1) TRP ID, 2) PCI ID, 3) ARFCN, 4) CGI (including NCGI / 6GCGI) ) ; F) sensing RS resource IDs (e.g., including one or more of: 1) a sensing RS type, e.g., new sensing RS, positioning RS, communication RS, e.g., CSI-RS, 2) a RS ID, 3) a RS resource set ID) ; G) reporting characteristics (e.g., including a reporting time domain type, such as: on-demand, periodic (periodicity) , aperiodic, triggered event) ; and / or H) one or more measurement quantities (e.g., 1) TRP sensing measurement type (e.g., ToA, Doppler) , 2) timing reporting granularity, 3) doppler reporting granularity, 4) RS configuration, 5) measurement beam information request, 6) time domain information (e.g., SFN, slot number, response time) , 7) measurement characteristics request including measurement beam information, additional path list, LOS / NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , RS resource type, timing error group information, multiple measurement instances. Can be implemented via flags or bitmaps, and / or 8) a choice between additional path-based or sample-based paths. In the case of both path-based or sample-based paths, the k timing reporting granularity may be requested. In the case of sample-based measurements, the additional desired values of Nt and / or Nt’ related to the sample-based measurement may also be requested) .
[0311] Some exemplary sensing measurement report content is shown in Table 12, below. In some implementations, the measurement report parameters in Table 12 support differencing operations of monostatic and / or bistatic measurements, such as round-trip delay measurements, ToA measurements, ToD measurements, monostatic round-trip Doppler shifts measurements, monostatic two-way Doppler shifts measurements, bistatic round-trip Doppler shifts measurements, and / or bistatic two-way Doppler shifts measurements. In some implementations, the measurement report supports the direct reporting of RSTD and / or RSFD / RSDD measurements. In some implementations, the reporting configuration depicted in Steps 2 and 3 of Figure 14, and / or Steps 1 and 2 of Figures 15 and 16 may include one or more of the parameters from Table 12. Table 12: Sensing TDoA-and / or FDoA / DDoA-based measurement Report
[0312] According to aspects of the sixth solution, an error cause reporting framework may be implemented, e.g., from both a sensing configuration entity perspective and from a sensing measurement entity perspective, for reporting errors related to TDoA and / or FDoA / DDoA techniques. The error cause values / indications may be provided in an unsolicited manner.
[0313] Figure 17 illustrates an example of a measurement entity-initiated error cause indication procedure 1700 for exchanging sensing error cause values, e.g., for a TDoA and / or FDoA sensing operation, in accordance with aspects of the present disclosure. The procedure 1700 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1700 may include a sensing configuration node and / or sensing result computation entity 1702, and a sensing measurement entity 1704, such as a RAN entity or UE. The sensing configuration node and / or sensing result computation entity 1702, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) . The sensing measurement entity 1704 may implement or be implemented by a NE 102 or a UE 104.
[0314] The procedure 1700 begins at Step A, where the sensing measurement entity 1704 may transmit, e.g., in an unsolicited manner, a message comprising error cause values / indications to the sensing configuration node and / or sensing result computation entity 1702 (see messaging 1706) . In some implementations, the message is transmitted via one sensing interface, such as a CN / RAN-RAN interface, a RAN-UE interface, or a CN-UE interface.
[0315] At Step B, the sensing configuration node and / or sensing result computation entity 1702 may independently transmit, e.g., in an unsolicited manner, a message comprising error cause values / indications to the sensing measurement entity 1704 (see messaging 1708) . In some implementations, the message is transmitted via another sensing interface, such as a RAN-CN / RAN interface, a UE-RAN interface, or a UE-CN interface. Steps A or B may be independently transmitted based on the observed issue (s) or error cause (s) .
[0316] Table 13 shows examples of possible error causes required from a sensing configuration entity perspective for sensing with an associated motivation behind the error cause. In some instances, the error cause values may be jointly structured under one sensing technique or separate TDoA or FDoA / DDoA techniques, or other sensing techniques. In some implementations, the message with configuration entity error cause (s) depicted in Step 1 of Figure 17 may include one or more of the values from Table 13. Table 13: Sensing Configuration Node / Entity Error Cause Values
[0317] Table 14 shows examples of possible error causes required from a measurement entity perspective for sensing with an associated motivation behind the error cause. In some instances, the error cause values may be jointly structured under one sensing technique, or separate TDoA or FDoA techniques, or other sensing techniques. In some implementations, the message with measurement entity error cause (s) depicted in Step 2 of Figure 17 may include one or more of the values from Table 14. Table 14: Sensing Measurement Entity Error Cause Values
[0318] According to aspects of the seventh solution, the capability reporting framework may be implemented, e.g., to enable the reporting of measurements from TDoA / FDoA or joint TDoA and FDoA techniques. In some implementations, these capabilities indicate whether the measurement entity is capable of performing sensing TDoA-and / or FDoA / DDoA-based measurements. In certain implementations, these capabilities can also comprise further measurement capabilities and / or sensing RS processing capabilities.
[0319] Figure 18 illustrates an example of a procedure 1800 for exchanging sensing capability information, e.g., for a TDoA and / or FDoA sensing operation, in accordance with aspects of the present disclosure. The procedure 1800 may implement or be implemented by aspects of the wireless communication system 100. For example, the procedure 1800 may include a sensing configuration node and / or sensing result computation entity 1802, and a sensing measurement entity 1804, such as a RAN entity or UE.The sensing configuration node and / or sensing result computation entity 1802, may implement or be implemented by an NE 102, a UE 104, or a node in the CN 106 (e.g., a SF) . The sensing measurement entity 1804 may implement or be implemented by a NE 102 or a UE 104.
[0320] The procedure 1800 begins at Step 1, where the sensing configuration node and / or sensing result computation entity 1802 transmits a request for TDoA-and / or FDoA / DDoA-based measurement capabilities to the sensing measurement entity 1804 (see messaging 1806) . In some implementations, the request is transmitted via a first sensing interface, such as a CN / RAN-RAN interface, a RAN-UE interface, or a CN-UE interface.
[0321] At Step 2, the sensing measurement entity 1804 transmits a response message to provide its capabilities for TDoA-and / or FDoA / DDoA-based measurements capabilities to the sensing configuration node and / or sensing result computation entity 1802 (see messaging 1808) . In some implementations, the response is transmitted via a second sensing interface, such as a RAN-CN / RAN interface, a UE-RAN interface, or a UE-CN interface.
[0322] At alternative Step 2a, the sensing measurement entity 1804 may independently deliver e.g., in an unsolicited manner, a reporting message with its capabilities for TDoA-and / or FDoA / DDoA-based measurements capabilities to the sensing configuration node and / or sensing result computation entity 1802 (see messaging 1810) . In some implementations, the request is transmitted via the second sensing interface. In another implementation, the exchange procedure 1800 may be extended to other sensing techniques or any joint sensing and positioning techniques.
[0323] Figure 19 illustrates an example of a UE 1900 in accordance with aspects of the present disclosure. The UE 1900 may include a processor 1902, a memory 1904, a controller 1906, and a transceiver 1908. The processor 1902, the memory 1904, the controller 1906, or the transceiver 1908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0324] The processor 1902, the memory 1904, the controller 1906, or the transceiver 1908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0325] The processor 1902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , an ASIC, a field programmable gate array (FPGA) , or any combination thereof) . In some implementations, the processor 1902 may be configured to operate the memory 1904. In some other implementations, the memory 1904 may be integrated into the processor 1902. The processor 1902 may be configured to execute computer-readable instructions stored in the memory 1904 to cause the UE 1900 to perform various functions of the present disclosure.
[0326] The memory 1904 may include volatile or non-volatile memory. The memory 1904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1902, cause the UE 1900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1904 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0327] In some implementations, the processor 1902 and the memory 1904 coupled with the processor 1902 may be configured to cause the UE 1900 to perform various functions (e.g., operations, signaling) described herein (e.g., executing, by the processor 1902, instructions stored in the memory 1904) . In some implementations, the processor 1902 may include multiple processors and the memory 1904 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may be individually or collectively, configured to perform various functions (e.g., operations, signaling) of the UE 1900 as described herein.
[0328] The processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to receive a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; receive assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0329] In some implementations, the assistance information may comprise information for mitigating sensing measurement errors. In certain implementations, the assistance information may further comprise: A) a real time difference between a set of sensing Tx nodes, B) a relative time difference between the set of sensing Tx nodes, C) quality information for the real time difference or relative time difference, D) sensing integrity information, E) sensing transmitter location information, F) sensing transmitter beam information, G) a real transmit frequency difference, H) a relative transmit frequency difference, I) time offset information, J) frequency offset information, K) quality information for the time offset information or the frequency offset information, L) expected sensing target LOS or NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , M) velocity information, or N) movement path information.
[0330] In some implementations, the sensing configuration may indicate one or more sensing techniques for performing the sensing measurement, the one or more sensing techniques comprising: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0331] In some implementations, the sensing measurement may comprise a monostatic RSTD or monostatic RSDD when the sensing configuration indicates a monostatic sensing of the sensing target. In some implementations, the sensing measurement may comprise a bistatic RSTD or bistatic RSDD when the sensing configuration indicates a bistatic sensing of the sensing target. In some implementations, the sensing target may include a UE.
[0332] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to report the sensing measurement to a management node or a sensing configuration node associated with the sensing measurement.
[0333] In a first scenario, the management node is located in the CN 106. In a second scenario, the management node may be located in the NG-RAN, such as a base station, gNB, or TRP node (e.g., the management node is implemented as a module in the NE 102) . In a third scenario, the management node may be a peer mobile device, such as a UE 104, a CPE, a PRU, or an SRU.
[0334] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) receive, from a second radio node, at least one second sensing measurement associated with the sensing target; B) perform a differencing operation between the performed sensing measurement and the at least one second sensing measurement; and C) report a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation.
[0335] In some implementations, the UE 1900 may comprise a transmitter of a sensing signal associated with the sensing measurement and a co-located receiver of the sensing measurement. In other words, the transceiver 1908 may both transmit the sensing signal and perform the RSTD measurement or the RSDD measurement based on the transmitted sensing signal.
[0336] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to transmit a request for the sensing technique configuration and the assistance information.
[0337] Additionally, or alternatively, in some other implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; transmit assistance information associated with the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement (or the joint RSTD and RSDD measurement) .
[0338] In some implementations, the assistance information may comprise information for mitigating sensing measurement errors. In certain implementations, the assistance information may further comprise: A) a real time difference between a set of sensing Tx nodes, B) a relative time difference between the set of sensing Tx nodes, C) quality information for the real time difference or relative time difference, D) sensing integrity information, E) sensing transmitter location information, F) sensing transmitter beam information, G) a real transmit frequency difference, H) a relative transmit frequency difference, I) time offset information, J) frequency offset information, K) quality information for the time offset information or the frequency offset information, L) expected sensing target LOS or NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , M) velocity information, or N) movement path information.
[0339] In some implementations, the sensing configuration may indicate one or more sensing techniques for performing the sensing measurement, the one or more sensing techniques comprising: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0340] In some implementations, the sensing measurement may comprise a monostatic RSTD or monostatic RSDD when the sensing configuration indicates a monostatic sensing of the sensing target. In some implementations, the sensing measurement may comprise a bistatic RSTD or bistatic RSDD when the sensing configuration indicates a bistatic sensing of the sensing target. In some implementations, the sensing target may include a UE.
[0341] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) receive, from a second radio node, at least one second RSTD measurement or at least one second RSDD measurement; B) perform a differencing operation between the RSTD measurement or the RSDD measurement and the at least one second RSTD measurement or at least one second RSDD measurement; and C) determine a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation.
[0342] Additionally, or alternatively, in some other implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to receive a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; perform the sensing measurement according to the one or more sensing techniques; and transmit a sensing measurement report based on the sensing measurement and according to the received configuration.
[0343] In some implementations, the one or more sensing techniques may comprise: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0344] In some implementations, the reporting configuration may comprise: A) a trigger for performing the sensing measurement, B) a set of sensing RS resource and TRP measurement identifiers, C) a sensing observation window, and D) one or more sensing measurement quantities, comprising a ToA measurement, a Doppler shift, a RSTD, or a RSDD.
[0345] In some implementations, the reporting characteristic may comprise an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.
[0346] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) transmit a capabilities indication for a sensing technique comprising TDoA or FDoA; and B) receive the configuration in response to transmitting the capabilities indication.
[0347] In certain implementations, the processor 1902 coupled with the memory 1904 may be further configured to, capable of, or operable to cause the UE 1900 to: A) receive a request to provide measurement capability information or processing capability information, and B) transmit the capabilities indication in response to the request.
[0348] In some implementations, the sensing measurement report may comprise: A) a timestamp, B) an observation number, C) a LOS measurement, D) a NLOS measurement, E) quality metrics, F) a path list, G) a RSTD measurement, H) an RSTD resolution, I) a RSDD measurement, or J) an RSDD resolution.
[0349] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to transmit an error cause or error indication associated with performing the sensing measurement.
[0350] Additionally, or alternatively, in some other implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to transmit a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; receive a sensing measurement report comprising the sensing measurement and according to the received configuration; and determine a sensing result based at least in part on the sensing measurement report.
[0351] In some implementations, the one or more sensing techniques may comprise: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0352] In some implementations, the reporting configuration may comprise: A) a trigger for performing the sensing measurement, B) a set of sensing RS resource and TRP measurement identifiers, C) a sensing observation window, and D) one or more sensing measurement quantities, comprising a ToA measurement, a Doppler shift, a RSTD, or a RSDD.
[0353] In some implementations, the reporting characteristic may comprise an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.
[0354] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) receive a capabilities indication for a sensing technique comprising TDoA or FDoA; and B) transmit the configuration in response to transmitting the capabilities indication.
[0355] In certain implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) transmit a request to provide measurement capability information or processing capability information; and B) receive the capabilities indication in response to the request.
[0356] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to: A) perform a differencing operation between a first sensing measurement and a second sensing measurement; and B) determine a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation. Here, the first sensing measurement and the second sensing measurement may include bistatic round-trip delay measurements, bistatic ToA measurements, monostatic round-trip measurements, or monostatic two-way Doppler shift measurements.
[0357] In some implementations, the sensing measurement report may comprise: A) a timestamp, B) an observation number, C) a LOS measurement, D) a NLOS measurement, E) quality metrics, F) a path list, G) a RSTD measurement, H) an RSTD resolution, I) a RSDD measurement, or J) an RSDD resolution.
[0358] In some implementations, the processor 1902 coupled with the memory 1904 may be configured to, capable of, or operable to cause the UE 1900 to receive an error cause or error indication associated with performing the sensing measurement.
[0359] The controller 1906 may manage input and output signals for the UE 1900. The controller 1906 may also manage peripherals not integrated into the UE 1900. In some implementations, the controller 1906 may utilize an operating system (OS) such as or other operating systems. In some implementations, the controller 1906 may be implemented as part of the processor 1902.
[0360] In some implementations, the UE 1900 may include at least one transceiver 1908. In some other implementations, the UE 1900 may have more than one transceiver 1908. The transceiver 1908 may represent a wireless transceiver. The transceiver 1908 may include one or more receiver chains 1910, one or more transmitter chains 1912, or a combination thereof.
[0361] A receiver chain 1910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1910 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 1910 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receiver chain 1910 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1910 may include at least one decoder for decoding / processing the demodulated signal to receive the transmitted data.
[0362] A transmitter chain 1912 may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmitter chain 1912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmitter chain 1912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0363] Figure 20 illustrates an example of a processor 2000 in accordance with aspects of the present disclosure. The processor 2000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 2000 may include a controller 2002 configured to perform various operations in accordance with examples as described herein. The processor 2000 may optionally include at least one memory 2004, which may be, for example, an L1, or L2, or L3 cache. Additionally, or alternatively, the processor 2000 may optionally include one or more arithmetic-logic units (ALUs) 2006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0364] The processor 2000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 2000) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
[0365] The controller 2002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 2000 to cause the processor 2000 to support various operations in accordance with examples as described herein. For example, the controller 2002 may operate as a control unit of the processor 2000, generating control signals that manage the operation of various components of the processor 2000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0366] The controller 2002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 2004 and determine subsequent instruction (s) to be executed to cause the processor 2000 to support various operations in accordance with examples as described herein. The controller 2002 may be configured to track memory address of instructions associated with the memory 2004. The controller 2002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 2002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 2000 to cause the processor 2000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 2002 may be configured to manage flow of data within the processor 2000. The controller 2002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 2000.
[0367] The memory 2004 may include one or more caches (e.g., memory local to or included in the processor 2000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 2004 may reside within or on a processor chipset (e.g., local to the processor 2000) . In some other implementations, the memory 2004 may reside external to the processor chipset (e.g., remote to the processor 2000) .
[0368] The memory 2004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 2000, cause the processor 2000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 2002 and / or the processor 2000 may be configured to execute computer-readable instructions stored in the memory 2004 to cause the processor 2000 to perform various functions. For example, the processor 2000 and / or the controller 2002 may be coupled with or to the memory 2004, the processor 2000, the controller 2002, and the memory 2004 may be configured to perform various functions described herein. In some examples, the processor 2000 may include multiple processors and the memory 2004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0369] The one or more ALUs 2006 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 2006 may reside within or on a processor chipset (e.g., the processor 2000) . In some other implementations, the one or more ALUs 2006 may reside external to the processor chipset (e.g., the processor 2000) . One or more ALUs 2006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 2006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 2006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 2006 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 2006 to handle conditional operations, comparisons, and bitwise operations.
[0370] In some implementations, the processor 2000 may support various functions (e.g., operations, signaling) of a UE, in accordance with examples as disclosed herein. For example, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to receive a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; receive assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0371] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; transmit assistance information associated with the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement (or the joint RSTD and RSDD measurement) .
[0372] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to receive a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; perform the sensing measurement according to the one or more sensing techniques; and transmit a sensing measurement report based on the sensing measurement and according to the received configuration.
[0373] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; receive a sensing measurement report comprising the sensing measurement and according to the received configuration; and determine a sensing result based at least in part on the sensing measurement report. Moreover, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to perform one or more functions (e.g., operations, signaling) of the UE as described herein.
[0374] In certain implementations, the processor 2000 may support various functions (e.g., operations, signaling) of a RAN node (e.g., base station or gNB) , in accordance with examples as disclosed herein. For example, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to receive a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; receive assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0375] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; transmit assistance information associated with the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement (or the joint RSTD and RSDD measurement) .
[0376] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to receive a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; perform the sensing measurement according to the one or more sensing techniques; and transmit a sensing measurement report based on the sensing measurement and according to the received configuration.
[0377] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; receive a sensing measurement report comprising the sensing measurement and according to the received configuration; and determine a sensing result based at least in part on the sensing measurement report. Moreover, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to perform one or more functions (e.g., operations, signaling) of the RAN node as described herein.
[0378] Additionally, or alternatively, in some other implementations, the processor 2000 may support various functions (e.g., operations, signaling) of a network node for managing a sensing operation (e.g., SensMF, SF, or sensing configuration node) , in accordance with examples as disclosed herein. For example, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; transmit assistance information associated with the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement (or the joint RSTD and RSDD measurement) .
[0379] Additionally, or alternatively, in some other implementations, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to transmit a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; receive a sensing measurement report comprising the sensing measurement and according to the received configuration; and determine a sensing result based at least in part on the sensing measurement report. Moreover, the controller 2002 coupled with the memory 2004 may be configured to, capable of, or operable to cause the processor 2000 to perform one or more functions (e.g., operations, signaling) of the network node for managing a sensing operation as described herein.
[0380] Figure 21 illustrates an example of a NE 2100 in accordance with aspects of the present disclosure. The NE 2100 may include a processor 2102, a memory 2104, a controller 2106, and a transceiver 2108. The processor 2102, the memory 2104, the controller 2106, or the transceiver 2108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0381] The processor 2102, the memory 2104, the controller 2106, or the transceiver 2108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0382] The processor 2102 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof) . In some implementations, the processor 2102 may be configured to operate the memory 2104. In some other implementations, the memory 2104 may be integrated into the processor 2102. The processor 2102 may be configured to execute computer-readable instructions stored in the memory 2104 to cause the NE 2100 to perform various functions of the present disclosure.
[0383] The memory 2104 may include volatile or non-volatile memory. The memory 2104 may store computer-readable, computer-executable code including instructions when executed by the processor 2102 cause the NE 2100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 2104 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0384] In some implementations, the processor 2102 and the memory 2104 coupled with the processor 2102 may be configured to cause the NE 2100 to perform various functions (e.g., operations, signaling) described herein (e.g., executing, by the processor 2102, instructions stored in the memory 2104) . In some implementations, the processor 2102 may include multiple processors and the memory 2104 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may be individually or collectively, configured to perform various functions (e.g., operations, signaling) of the NE 2100 as described herein.
[0385] The processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to receive a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; receive assistance information for performing the sensing measurement; and perform the sensing measurement based at least in part on the assistance information.
[0386] In some implementations, the assistance information may comprise information for mitigating sensing measurement errors. In certain implementations, the assistance information may further comprise: A) a real time difference between a set of sensing Tx nodes, B) a relative time difference between the set of sensing Tx nodes, C) quality information for the real time difference or relative time difference, D) sensing integrity information, E) sensing transmitter location information, F) sensing transmitter beam information, G) a real transmit frequency difference, H) a relative transmit frequency difference, I) time offset information, J) frequency offset information, K) quality information for the time offset information or the frequency offset information, L) expected sensing target LOS or NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , M) velocity information, or N) movement path information.
[0387] In some implementations, the sensing configuration may indicate one or more sensing techniques for performing the sensing measurement, the one or more sensing techniques comprising: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0388] In some implementations, the sensing measurement may comprise a monostatic RSTD or monostatic RSDD when the sensing configuration indicates a monostatic sensing of the sensing target. In some implementations, the sensing measurement may comprise a bistatic RSTD or bistatic RSDD when the sensing configuration indicates a bistatic sensing of the sensing target. In some implementations, the sensing target may include a UE.
[0389] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to report the sensing measurement to a management node or a sensing configuration node associated with the sensing measurement.
[0390] In a first scenario, the management node is located in the CN 106. In a second scenario, the management node may be located in the NG-RAN, such as a base station, gNB, or TRP node (e.g., the management node is implemented as a module in the NE 102) . In a third scenario, the management node may be a mobile device, such as a UE 104, a CPE, a PRU, or an SRU.
[0391] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) receive, from a second radio node, at least one second sensing measurement associated with the sensing target; B) perform a differencing operation between the performed sensing measurement and the at least one second sensing measurement; and C) report a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation.
[0392] In some implementations, the NE 2100 may comprise a transmitter of a sensing signal associated with the sensing measurement and a co-located receiver of the sensing measurement. In other words, the transceiver 2108 may both transmit the sensing signal and perform the RSTD measurement or the RSDD measurement based on the transmitted sensing signal.
[0393] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to transmit a request for the sensing technique configuration and the assistance information.
[0394] Additionally, or alternatively, in some other implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to transmit a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement (or a joint RSTD and RSDD measurement) ; transmit assistance information associated with the sensing measurement; and receive a report indicating at least the RSTD measurement or the RSDD measurement (or the joint RSTD and RSDD measurement) .
[0395] In some implementations, the assistance information may comprise information for mitigating sensing measurement errors. In certain implementations, the assistance information may further comprise: A) a real time difference between a set of sensing Tx nodes, B) a relative time difference between the set of sensing Tx nodes, C) quality information for the real time difference or relative time difference, D) sensing integrity information, E) sensing transmitter location information, F) sensing transmitter beam information, G) a real transmit frequency difference, H) a relative transmit frequency difference, I) time offset information, J) frequency offset information, K) quality information for the time offset information or the frequency offset information, L) expected sensing target LOS or NLOS information (e.g., a LOS / NLOS condition from sensing Tx node to sensing target, or from sensing target to sensing Rx node) , M) velocity information, or N) movement path information.
[0396] In some implementations, the sensing configuration may indicate one or more sensing techniques for performing the sensing measurement, the one or more sensing techniques comprising: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0397] In some implementations, the sensing measurement may comprise a monostatic RSTD or monostatic RSDD when the sensing configuration indicates a monostatic sensing of the sensing target. In some implementations, the sensing measurement may comprise a bistatic RSTD or bistatic RSDD when the sensing configuration indicates a bistatic sensing of the sensing target. In some implementations, the sensing target may include a UE.
[0398] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) receive, from a second radio node, at least one second RSTD measurement or at least one second RSDD measurement; B) perform a differencing operation between the RSTD measurement or the RSDD measurement and the at least one second RSTD measurement or at least one second RSDD measurement; and C) determine a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation.
[0399] Additionally, or alternatively, in some other implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to receive a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; perform the sensing measurement according to the one or more sensing techniques; and transmit a sensing measurement report based on the sensing measurement and according to the received configuration.
[0400] In some implementations, the one or more sensing techniques may comprise: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0401] In some implementations, the reporting configuration may comprise: A) a trigger for performing the sensing measurement, B) a set of sensing RS resource and TRP measurement identifiers, C) a sensing observation window, and D) one or more sensing measurement quantities, comprising a ToA measurement, a Doppler shift, a RSTD, or a RSDD.
[0402] In some implementations, the reporting characteristic may comprise an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.
[0403] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) transmit a capabilities indication for a sensing technique comprising TDoA or FDoA; and B) receive the configuration in response to transmitting the capabilities indication.
[0404] In certain implementations, the processor 2102 coupled with the memory 2104 may be further configured to, capable of, or operable to cause the NE 2100 to: A) receive a request to provide measurement capability information or processing capability information, and B) transmit the capabilities indication in response to the request.
[0405] In some implementations, the sensing measurement report may comprise: A) a timestamp, B) an observation number, C) a LOS measurement, D) a NLOS measurement, E) quality metrics, F) a path list, G) a RSTD measurement, H) an RSTD resolution, I) a RSDD measurement, or J) an RSDD resolution.
[0406] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to transmit an error cause or error indication associated with performing the sensing measurement.
[0407] Additionally, or alternatively, in some other implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to transmit a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic; receive a sensing measurement report comprising the sensing measurement and according to the received configuration; and determine a sensing result based at least in part on the sensing measurement report.
[0408] In some implementations, the one or more sensing techniques may comprise: A) an UL TDoA, B) a DL TDoA, C) a UL FDoA, D) a DL FDoA, E) a UL DDoA, or F) a DL DDoA.
[0409] In some implementations, the reporting configuration may comprise: A) a trigger for performing the sensing measurement, B) a set of sensing RS resource and TRP measurement identifiers, C) a sensing observation window, and D) one or more sensing measurement quantities, comprising a ToA measurement, a Doppler shift, a RSTD, or a RSDD.
[0410] In some implementations, the reporting characteristic may comprise an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.
[0411] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) receive a capabilities indication for a sensing technique comprising TDoA or FDoA; and B) transmit the configuration in response to transmitting the capabilities indication.
[0412] In certain implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) transmit a request to provide measurement capability information or processing capability information; and B) receive the capabilities indication in response to the request.
[0413] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to: A) perform a differencing operation between a first sensing measurement and a second sensing measurement; and B) determine a TDoA-based differential measurement or a DDoA-based differential measurement based on the differencing operation. Here, the first sensing measurement and the second sensing measurement may include bistatic round-trip delay measurements, bistatic ToA measurements, monostatic round-trip measurements, or monostatic two-way Doppler shift measurements.
[0414] In some implementations, the sensing measurement report may comprise: A) a timestamp, B) an observation number, C) a LOS measurement, D) a NLOS measurement, E) quality metrics, F) a path list, G) a RSTD measurement, H) an RSTD resolution, I) a RSDD measurement, or J) an RSDD resolution.
[0415] In some implementations, the processor 2102 coupled with the memory 2104 may be configured to, capable of, or operable to cause the NE 2100 to receive an error cause or error indication associated with performing the sensing measurement.
[0416] The controller 2106 may manage input and output signals for the NE 2100. The controller 2106 may also manage peripherals not integrated into the NE 2100. In some implementations, the controller 2106 may utilize an operating system such as or other operating systems. In some implementations, the controller 2106 may be implemented as part of the processor 2102.
[0417] In some implementations, the NE 2100 may include at least one transceiver 2108. In some other implementations, the NE 2100 may have more than one transceiver 2108. The transceiver 2108 may represent a wireless transceiver. The transceiver 2108 may include one or more receiver chains 2110, one or more transmitter chains 2112, or a combination thereof.
[0418] A receiver chain 2110 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 2110 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 2110 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receiver chain 2110 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 2110 may include at least one decoder for decoding / processing the demodulated signal to receive the transmitted data.
[0419] A transmitter chain 2112 may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmitter chain 2112 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmitter chain 2112 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 2112 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0420] Figure 22 illustrates a flowchart of a method 2200 in accordance with aspects of the present disclosure. The operations of the method 2200 may be implemented by a radio node, such as a UE or a NE as described herein. In some implementations, the radio node may execute a set of instructions to control the function elements of the radio node to perform the described functions.
[0421] At step 2202, the method 2200 may include receiving a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement including a RSTD measurement or a RSDD measurement. The operations of step 2202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2202 may be performed by a UE, as described with reference to Figure 19. In some other implementations, aspects of the operations of step 2202 may be performed by a NE, as described with reference to Figure 21.
[0422] At step 2204, the method 2200 may include receiving assistance information for performing the sensing measurement. The operations of step 2204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2204 may be performed by a UE, as described with reference to Figure 19.In some other implementations, aspects of the operations of step 2204 may be performed by a NE, as described with reference to Figure 21.
[0423] At step 2206, the method 2200 may include performing the sensing measurement based at least in part on the assistance information. The operations of step 2206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2206 may be performed by a UE, as described with reference to Figure 19. In some other implementations, aspects of the operations of step 2206 may be performed by a NE, as described with reference to Figure 21.
[0424] It should be noted that the method 2200 described herein describes one possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0425] Figure 23 illustrates a flowchart of a method 2300 in accordance with aspects of the present disclosure. The operations of the method 2300 may be implemented by a sensing configuration node, such as a UE, an NE, or a CN node as described herein. In some implementations, the sensing configuration node (e.g., a configuring radio node) may execute a set of instructions to control the function elements of the sensing configuration node to perform the described functions.
[0426] At step 2302, the method 2300 may include transmitting a sensing configuration for performing a sensing measurement associated with a sensing target, the sensing measurement comprising a RSTD measurement or a RSDD measurement. The operations of step 2302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2302 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2302 may be performed by a UE, as described with reference to Figure 19.
[0427] At step 2304, the method 2300 may include transmitting assistance information associated with the sensing measurement. The operations of step 2304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2304 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2304 may be performed by a UE, as described with reference to Figure 19.
[0428] At step 2306, the method 2300 may include receiving a report indicating at least the RSTD measurement or the RSDD measurement. The operations of step 2306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2306 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2306 may be performed by a UE, as described with reference to Figure 19.
[0429] It should be noted that the method 2300 described herein describes one possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0430] Figure 24 illustrates a flowchart of a method 2400 in accordance with aspects of the present disclosure. The operations of the method 2400 may be implemented by a radio node, such as a UE or a NE as described herein. In some implementations, the radio node may execute a set of instructions to control the function elements of the radio node to perform the described functions.
[0431] At step 2402, the method 2400 may include receiving a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic. The operations of step 2402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2402 may be performed by a UE, as described with reference to Figure 19. In some other implementations, aspects of the operations of step 2402 may be performed by a NE, as described with reference to Figure 21.
[0432] At step 2404, the method 2400 may include performing the sensing measurement according to the one or more sensing techniques. The operations of step 2404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2404 may be performed by a UE, as described with reference to Figure 19. In some other implementations, aspects of the operations of step 2404 may be performed by a NE, as described with reference to Figure 21.
[0433] At step 2406, the method 2400 may include transmitting a sensing measurement report based on the sensing measurement and according to the received configuration. The operations of step 2406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2406 may be performed by a UE, as described with reference to Figure 19. In some other implementations, aspects of the operations of step 2406 may be performed by a NE, as described with reference to Figure 21.
[0434] It should be noted that the method 2400 described herein describes one possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0435] Figure 25 illustrates a flowchart of a method 2500 in accordance with aspects of the present disclosure. The operations of the method 2500 may be implemented by a sensing configuration node, such as a UE, an NE, or a CN node as described herein. In some implementations, the sensing configuration node (e.g., a configuring radio node) may execute a set of instructions to control the function elements of the sensing configuration node to perform the described functions.
[0436] At step 2502, the method 2500 may include transmitting a reporting configuration for a sensing measurement based on a one or more sensing techniques, the reporting configuration indicating one or more RS resources for performing the sensing measurement and a reporting characteristic. The operations of step 2502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2502 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2502 may be performed by a UE, as described with reference to Figure 19.
[0437] At step 2504, the method 2500 may include receiving a sensing measurement report comprising the sensing measurement and according to the received configuration. The operations of step 2504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2504 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2504 may be performed by a UE, as described with reference to Figure 19.
[0438] At step 2506, the method 2500 may include determining a sensing result based at least in part on the sensing measurement report. The operations of step 2506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 2506 may be performed by a NE, as described with reference to Figure 21. In some other implementations, aspects of the operations of step 2506 may be performed by a UE, as described with reference to Figure 19.
[0439] It should be noted that the method 2500 described herein describes one possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0440] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A radio node for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the radio node to:receive a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more reference signal resources for performing the sensing measurement and a reporting characteristic;perform the sensing measurement according to the one or more sensing techniques; andtransmit a sensing measurement report based on the sensing measurement and according to the received configuration.2.The radio node of claim 1, wherein the one or more sensing techniques comprise:an uplink (UL) time difference of arrival (TDoA) ,a downlink (DL) TDoA,a UL frequency difference of arrival (FDoA) ,a DL FDoA,a UL Doppler difference of arrival (DDoA) , ora DL DDoA.3.The radio node of claim 1, wherein the reporting configuration comprises:a trigger for performing the sensing measurement,a set of sensing reference signal resource and transmission-reception point (TRP) measurement identifiers,a sensing observation window, andone or more sensing measurement quantities, comprising a time-of-arrival (ToA) measurement, a Doppler shift, a reference signal time difference (RSTD) , or a reference signal Doppler difference (RSDD) .4.The radio node of claim 1, wherein reporting characteristic comprises an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.5.The radio node of claim 1, wherein the at least one processor is configured to cause the radio node to:transmit a capabilities indication for a sensing technique comprising time difference of arrival (TDoA) or frequency difference of arrival (FDoA) ; andreceive the configuration in response to transmitting the capabilities indication.6.The radio node of claim 5, wherein the at least one processor is configured to cause the radio node to:receive a request to provide measurement capability information or processing capability information; andtransmit the capabilities indication in response to the request.7.The radio node of claim 1, wherein the sensing measurement report comprises:a timestamp,an observation number,a line-of-sight (LOS) measurement,a non-line-of-sight (NLOS) measurement,quality metrics,a path list,a reference signal time difference (RSTD) measurement,an RSTD resolution,a reference signal Doppler difference (RSDD) measurement, oran RSDD resolution.8.The radio node of claim 1, wherein the at least one processor is configured to cause the radio node to transmit an error cause or indication associated with performing the sensing measurement.9.The radio node of claim 1, wherein the radio node is a base station, a transmission-reception point (TRP) , a sensing management function, or a user equipment (UE) .10.A method performed by a radio node, the method comprising:receiving a reporting configuration for a sensing measurement based on one or more sensing techniques, the reporting configuration indicating one or more reference signal resources for performing the sensing measurement and a reporting characteristic;performing the sensing measurement according to the one or more sensing techniques; andtransmitting a sensing measurement report based on the sensing measurement and according to the received configuration.11.A radio node for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the radio node to:transmit a reporting configuration for a sensing measurement based on a one or more sensing techniques, the reporting configuration indicating one or more reference signal resources for performing the sensing measurement and a reporting characteristic;receive a sensing measurement report comprising the sensing measurement and according to the received configuration; anddetermine a sensing result based at least in part on the sensing measurement report.12.The radio node of claim 11, wherein the one or more sensing techniques comprise:an uplink (UL) time difference of arrival (TDoA) ,a downlink (DL) TDoA,a UL frequency difference of arrival (FDoA) ,a DL FDoA,a UL Doppler difference of arrival (DDoA) , ora DL DDoA.13.The radio node of claim 11, wherein the reporting configuration comprises:a trigger for performing the sensing measurement,a set of sensing reference signal resource and transmission-reception point (TRP) measurement identifiers,a sensing observation window, andone or more sensing measurement quantities, comprising a time-of-arrival (ToA) measurement, a Doppler shift, a reference signal time difference (RSTD) , or a reference signal Doppler difference (RSDD) .14.The radio node of claim 11, wherein the reporting characteristic comprises an on-demand reporting, a periodic reporting, an aperiodic reporting, or an event-triggered reporting.15.The radio node of claim 11, wherein the at least one processor is configured to cause the radio node to:receive a capabilities indication for a sensing technique comprising time difference of arrival (TDoA) or frequency difference of arrival (FDoA) ; andtransmit the configuration in response to transmitting the capabilities indication.16.The radio node of claim 15, wherein the at least one processor is configured to cause the radio node to:transmit a request to provide measurement capability information or processing capability information; andreceive the capabilities indication in response to the request.17.The radio node of claim 11, wherein the at least one processor is configured to cause the radio node to:perform a differencing operation between a first sensing measurement and a second sensing measurement; anddetermine a time difference of arrival (TDoA) based differential measurement or a Doppler difference of arrival (DDoA) based differential measurement based on the differencing operation,wherein the first sensing measurement and the second sensing measurement comprise bistatic round-trip delay measurements, bistatic time-of-arrival (ToA) measurements, monostatic round-trip measurements, or monostatic two-way Doppler shift measurements.18.The radio node of claim 11, wherein the sensing measurement report comprises:a timestamp,an observation number,a line-of-sight (LOS) measurement,a non-line-of-sight (NLOS) measurement,quality metrics,a path list,a reference signal time difference (RSTD) measurement,an RSTD resolution,a reference signal Doppler difference (RSDD) measurement, oran RSDD resolution.19.The radio node of claim 11, wherein the at least one processor is configured to cause the radio node to receive an error cause or indication associated with performing the sensing measurement.20.A method performed by a radio node, the method comprising:transmitting a reporting configuration for a sensing measurement based on a one or more sensing techniques, the reporting configuration indicating one or more reference signal resources for performing the sensing measurement and a reporting characteristic;receiving a sensing measurement report comprising the sensing measurement and according to the received configuration; anddetermining a sensing result based at least in part on the sensing measurement report.
Citation Information
Patent Citations
Configuring a sensing reference signal
US20230171060A1
Circuits and methods for data detection
US9136949B1
Sensing operation using measurements based on a circular directed graph
US20250123387A1
Passive sensing in wireless communications
US20250168685A1
Method and apparatus for integrated sensing and communication
WO2024082459A9