WO2025141555A1

WO2025141555A1 - Techniques for determining and reporting a path modification

Info

Publication number: WO2025141555A1
Application number: PCT/IB2025/051657
Authority: WO
Inventors: Seyedomid TAGHIZADEH MOTLAGH
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2024-02-17
Filing date: 2025-02-14
Publication date: 2025-07-03
Anticipated expiration: 2026-08-17

Abstract

Various aspects of the present disclosure relate to receiving (902) a configuration for sensing measurement and reporting, based on one or more sensing signals. Aspects of the present disclosure may relate to determining (904) a path based at least in part on a reception and measurement of the one or more sensing signals and storing context information associated with the path, where the context information includes a plurality of path parameters associated with different measurement instances. Aspects of the present disclosure may further relate to determining (906) a modification of one or more path characteristics, based at least in part on the context information, and transmitting (908) a report based at least in part on the modification.

Description

TECHNIQUES FOR DETERMINING AND REPORTING A PATH

MODIFICATION

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to techniques for determining and reporting a path modification.

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)).

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 a NE. The radio node may be configured to, capable of, or operable to receive a configuration for sensing measurement and reporting, based on one or more sensing signals; determine a path based at least in part on a reception and measurement of the one or more sensing signals; store context information associated with the path, the context information including a plurality of path parameters associated with different measurement instances; determine a modification of one or more path characteristics, based at least in part on the context information; and transmit a report based at least in part on the modification.

[0005] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to receive a configuration for sensing measurement and reporting, based on one or more sensing signals; determine a path based at least in part on a reception and measurement of the one or more sensing signals; store context information associated with the path, the context information including a plurality of path parameters associated with different measurement instances; determine a modification of one or more path characteristics, based at least in part on the context information; and transmit a report based at least in part on the modification.

[0006] A method performed or performable by a radio node is described. In some examples, the method may be implemented by a UE or a NE. The method may include receiving a configuration for sensing measurement and reporting, based on one or more sensing signals; determining a path based at least in part on a reception and measurement of the one or more sensing signals; storing context information associated with the path, where the context information includes a plurality of path parameters associated with different measurement instances; determining a modification of one or more path characteristics, based at least in part on the context information; and transmitting a report based at least in part on the modification.

[0007] A sensing management function (SensMF) for wireless communication is described. In some examples, the sensing management function (SensMF) may implement, or may be implemented by, a UE or a NE, or a core network function (NF). The SensMF may be configured to, capable of, or operable to transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, where the context information includes a plurality of path parameters associated with different measurement instances.

[0008] A processor for wireless communication by a SensMF is described. The processor may be configured to, capable of, or operable to transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, where the context information includes a plurality of path parameters associated with different measurement instances.

[0009] A method performed or performable by a SensMF for wireless communication is described. The method may include transmitting a configuration for sensing measurement and reporting, based on one or more sensing signals; receiving a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, where the context information includes a plurality of path parameters associated with different measurement instances.

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 2 illustrates an example of a protocol stack in accordance with aspects of the present disclosure.

[0012] Figure 3 illustrates an example of a receiver operating characteristic (ROC) curve for the detection of a blockage effect evaluated at different path signal-to-noise ratio (SNR) and at different blockage attenuation levels in accordance with aspects of the present disclosure. [0013] Figure 4A illustrates an example of a first set of sensing scenarios for a radio sensing operation , in accordance with aspects of the present disclosure.

[0014] Figure 4B illustrates an example of a second set of sensing scenarios for a radio sensing operation, in accordance with aspects of the present disclosure.

[0015] Figure 5A illustrates an example of a tight coupling Information Sharing and Analysis Center (ISAC) network architecture, in accordance with aspects of the present disclosure.

[0016] Figure 5B illustrates another example of a tight coupling ISAC network architecture, in accordance with aspects of the present disclosure.

[0017] Figure 5C illustrates an example of an ISAC network architecture where the sensing function (SF) is co-located with the location management function (LMF), in accordance with aspects of the present disclosure.

[0018] Figure 5D illustrates an example of a loose coupling ISAC network architecture, in accordance with aspects of the present disclosure.

[0019] Figure 6 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0020] Figure 7 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0021] Figure 8 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.

[0022] Figure 9 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0023] Figure 10 illustrates a flowchart of a method performed by an NE in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0024] Radio-based environment sensing allows for improved the network performance of the cellular wireless networks, as well as enabling the cellular wireless networks to serve vertical use-cases, e.g., where sensing information is obtained (and exposed to the requesting entity) by the wireless communication network. As such, a radio sensing measurement procedure intends to generate and collect measurements to obtain sensing information of the target objects/environment and/or the involved radio nodes. Examples of the acquired sensing information (also referred to as “sensing results”) includes, but is not limited to, information of position, velocity, direction/heading, orientation, radar cross-section (RCS), shape, material/composite, etc., of a target object and/or of a participating radio node.

[0025] Such sensing information may be obtained by means of a combination of the one or multiple of: z) the transmission of a sensing signal (e.g., an new radio (NR) downlink (DL) channel state information reference signal (CSI-RS) or an NR DL and/or sidelink (SL) positioning reference signal (PRS), uplink (UL) sounding reference signal (SRS) or a sensing-dedicated reference signal (RS), etc.) from a network or UE entity (hereafter referred to as the “sensing Tx node”); and ii) the reception of the transmitted sensing signal impacted by the environment (e.g., reflected, refracted, scattered, blocked/attenuated, etc.) by a network or a UE entity (hereafter referred to as “sensing Rx node”); and Hi) the processing of the received reflections and inferring relevant information from the environment.

[0026] Accordingly, the sensing measurement process may include: z) one or multiple (static or mobile) sensing Tx nodes with known sensing information or with (partially) unknown sensing information (e.g., known or unknown position); ii) one or multiple (static or mobile) sensing Rx nodes with known or (partially) unknown sensing information (e.g., known or unknown position); Hi) one or multiple (static or mobile) objects/reflectors with known or (partially) unknown sensing information (e.g., known or unknown position, presence, RCS, etc.); or a combination thereof.

[0027] Aspects of the present disclosure are described in the context of a wireless communications system.

[0028] 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. 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 aNew Radio (NR) network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.

[0029] In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology (RAT) 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, 6G. 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.

[0030] 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 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.

[0031] 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, anNE 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.

[0032] 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 intemet-of-things (loT) device, an intemet-of-everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0033] 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-de vice (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.

[0034] 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., SI, N2, N3, 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).

[0035] 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. [0036] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N3, 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 a PDN connection, 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).

[0037] 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.

[0038] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., ^=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., i =0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., i=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., i=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ju=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /1=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix. [0039] 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.

[0040] 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., jU=O, ju=l, ju=2, fi=3, ^=4) associated with respective subcarrier spacings 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.

[0041] Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency domain 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 subcarrier spacing), 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., i=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0042] 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 FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (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.

[0043] FR1 may be associated with one or multiple numerologies (e.g., at least three numeral ogies). For example, FR1 may be associated with a first numerology (e.g., i=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., i =l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., i=2), which includes 60 kHz subcarrier spacing. 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 subcarrier spacing; and a fourth numerology (e.g., i=3), which includes 120 kHz subcarrier spacing.

[0044] Wireless communication in unlicensed spectrum (also referred to as “shared spectrum”) in contrast to licensed spectrum offer some obvious cost advantages allowing communication to obviate overlaying operator’s licensed spectrum and rather use license free spectrum according to local regulation in specific geographies. From the third generation partnership project (3GPP) technology perspective, the unlicensed operation can be on the Uu interface (referred to as NR-U) or also on sidelink interface (e.g., SL-U).

[0045] For initial access, a UE 104 detects a candidate cell and performs downlink (DL) synchronization. For example, the gNB (e.g., an embodiment of the NE 102) may transmit a synchronization signal and physical broadcast channel (SS/PBCH) transmission, referred to as a synchronization signal block (SSB). In various embodiments, the SSB comprises the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the master information block (MIB). The synchronization signal (i.e., comprising the PSS and SSS) is a predefined data sequence known to the UE 104 (or derivable using information already stored at the UE 104) and is in a predefined location in time relative to frame/subframe boundaries, etc. The UE 104 searches for the SSB and uses the SSB to obtain DL timing information (e.g., symbol timing) for the DL synchronization. The UE 104 may also decode system information (SI) based on the SSB. Note that with beam -based communication, each DL beam may be associated with a respective SSB. [0046] After performing DL synchronization and acquiring essential system information, such as the MIB and the system information block type 1 (SIB1), the UE 104 performs uplink (UL) synchronization and resource request by performing a random -access procedure, referred to as “RACH procedure” by selecting and transmitting a preamble on the physical random access channel (PRACH). The PRACH preamble is transmitted during a random access channel (RACH) occasion, i.e., a predetermined set of time-frequency resources that are available for the reception of the PRACH preamble. Note that with beambased communication, the UE 104 may select a certain DL beam and transmit the PRACH preamble on a corresponding UL beam. In such embodiments, there may be a mapping between SSB and RACH occasion, allowing the network to determine which beam the UE 104 has selected.

[0047] In 3GPP New Radio (NR), the gNB may transmit the maximum 64 SSBs and the maximum 64 corresponding copies of physical downlink control channel (PDCCH) and/or physical downlink shared channel (PDSCH) for delivery of SIB1 in high frequency bands (e.g., 28 GHz). This may cause significant network energy consumption even for a very low traffic load condition. According to 3GPP Technical Report (TR) 38.864 (vl8.1.0), for network energy savings, on-demand SSB and/or SIB1 (SSB/SIB1) transmissions and a cell without SSB/SIB 1 transmission were considered. When a cell does not transmit SSB/SIB 1, for a UE 104 to access the cell, the UE 104 should obtain SI of the cell from other associated carriers/cells and synchronize from other associated carriers/cells. When a cell is in a long period of cell inactivity, a UE 104 served by the cell can trigger SSB/SIB 1 transmissions by sending a request to the cell.

[0048] Figure 2 illustrates an example of a protocol stack 200, in accordance with aspects of the present disclosure. While Figure 2 shows a UE 206, a RAN node 208, and a 5G core network (5GC) 210 (e.g., comprising at least an AMF), these are representative of a set of UEs 104 interacting with an NE 102 (e.g., base station) and a CN 106. As depicted, the protocol stack 200 comprises a user plane protocol stack 202 and a control plane protocol stack 204. The user plane protocol stack 202 includes a physical (PHY) layer 212, a medium access control (MAC) sublayer 214, a radio link control (RLC) sublayer 216, a packet data convergence protocol (PDCP) sublayer 218, and a service data adaptation protocol (SDAP) sublayer 220. The control plane protocol stack 204 includes a PHY layer 212, a MAC sublayer 214, a RLC sublayer 216, and a PDCP sublayer 218. The control plane protocol stack 204 also includes a radio resource control (RRC) layer 222 and a non- access stratum (NAS) layer 224.

[0049] The access stratum (AS) layer 226 (also referred to as “AS protocol stack”) for the user plane protocol stack 202 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer 228 for the control plane protocol stack 204 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The layer-1 (LI) includes the PHY layer 212. The layer-2 (L2) is split into the SDAP sublayer 220, PDCP sublayer 218, RLC sublayer 216, and MAC sublayer 214. The layer-3 (L3) includes the RRC layer 222 and the NAS layer 224 for the control plane and includes, e.g., an internet protocol (IP) layer and/or PDU Layer (not depicted) for the user plane. LI and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”

[0050] The PHY layer 212 offers transport channels to the MAC sublayer 214. The PHY layer 212 may perform a beam failure detection procedure using energy detection thresholds, as described herein. In certain embodiments, the PHY layer 212 may send an indication of beam failure to a MAC entity at the MAC sublayer 214. The MAC sublayer 214 offers logical channels to the RLC sublayer 216. The RLC sublayer 216 offers RLC channels to the PDCP sublayer 218. The PDCP sublayer 218 offers radio bearers to the SDAP sublayer 220 and/or RRC layer 222. The SDAP sublayer 220 offers QoS flows to the core network (e.g., 5GC). The RRC layer 222 provides for the addition, modification, and release of carrier aggregation and/or dual connectivity. The RRC layer 222 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs).

[0051] The NAS layer 224 is between the UE 206 and an AMF in the 5GC 210. NAS messages are passed transparently through the RAN. The NAS layer 224 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 206 as it moves between different cells of the RAN. In contrast, the AS layers 226 and 228 are between the UE 206 and the RAN (i.e., RAN node 208) and carry information over the wireless portion of the network. While not depicted in Figure 2, the IP layer exists above the NAS layer 224, a transport layer exists above the IP layer, and an application layer exists above the transport layer. [0052] The MAC sublayer 214 is the lowest sublayer in the L2 architecture of the NR protocol stack. Its connection to the PHY layer 212 below is through transport channels, and the connection to the RLC sublayer 216 above is through logical channels. The MAC sublayer 214 therefore performs multiplexing and demultiplexing between logical channels and transport channels: the MAC sublayer 214 in the transmitting side constructs MAC PDUs (also known as transport blocks (TBs)) from MAC service data units (SDUs) received through logical channels, and the MAC sublayer 214 in the receiving side recovers MAC SDUs from MAC PDUs received through transport channels.

[0053] The MAC sublayer 214 provides a data transfer service for the RLC sublayer 216 through logical channels, which are either control logical channels which carry control data (e.g., RRC signaling) or traffic logical channels which carry user plane data. On the other hand, the data from the MAC sublayer 214 is exchanged with the PHY layer 212 through transport channels, which are classified as UL or downlink (DL). Data is multiplexed into transport channels depending on how it is transmitted over the air.

[0054] The PHY layer 212 is responsible for the actual transmission of data and control information via the air interface, i.e., the PHY layer 212 carries all information from the MAC transport channels over the air interface on the transmission side. Some of the important functions performed by the PHY layer 212 include coding and modulation, link adaptation (e.g., adaptive modulation and coding (AMC)), power control, cell search and random access (for initial synchronization and handover purposes) and other measurements (inside the 3 GPP system (i.e., NR and/or LTE system) and between systems) for the RRC layer 222. The PHY layer 212 performs transmissions based on transmission parameters, such as the modulation scheme, the coding rate (i.e., the modulation and coding scheme (MCS)), the number of physical resource blocks (PRBs), etc.

[0055] In some embodiments, the protocol stack 200 may be a NR protocol stack used in a 5G NR system. Note that an LTE protocol stack comprises similar structure to the protocol stack 200, with the differences that the LTE protocol stack lacks the SDAP sublayer 220 in the AS layer 226, that an EPC replaces the 5GC 210, and that the NAS layer 224 is between the UE 206 and an MME in the EPC. Also note that the present disclosure distinguishes between a protocol layer (such as the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP sublayer 220, RRC layer 222 and NAS layer 224) and a transmission layer in multiple -input multiple -output (MIMO) communication (also referred to as a “MIMO layer” or a “data stream”).

[0056] In some identified sensing use-cases, e.g., involving variation of intruder detection in the indoor or outdoor scenarios, when a propagation path can be observed/distinguished at a sensing Rx node, the impact of blockage by a sensing target object is of significance, due to high observability while containing valuable presence information of an object/intruder at a given sensing area.

[0057] Figure 3 depicts a graph 300 of the probability of detection (PD) versus the probability of false alarm (PFA) for ROC curves related to the detection of a blockage effect evaluated at different path SNR (i.e., the perceived SNR from a path which is of interest for sensing) and at different blockage attenuation levels, in accordance with aspects of the present disclosure. In the depicted example, the ROC curves include a first curve 302 evaluated at the blockage attenuation level 10 dB and at the path SNR of 10 dB, a second curve 304 evaluated at the blockage attenuation level of 10 dB and at the path SNR of 15 dB, a third curve 306 evaluated at the blockage attenuation level of 20 dB and at the path SNR of 10 dB, a fourth curve 308 evaluated at the blockage attenuation level of 20 dB and at the path SNR of 15 dB, a fifth curve 310 evaluated at the blockage attenuation level of 30 dB and at the path SNR of 10 dB, and a sixth curve 312 evaluated at the blockage attenuation level of 30 dB and at the path SNR of 15 dB.

[0058] When detecting and measuring a path, the blockage level may vary and the 30 dB attenuation (e.g., a drop of reference signal received path power (RSRPP) due to the blockage) corresponds to a self-blockage condition. Accordingly, the blockage effect may be used to infer presence of an unexpected object at an area of interest for sensing.

[0059] In addition to the blockage effect, the continuous measurement of a detected path at a sensing Rx node is of interest, at least for the following scenarios: A) When a blockage event can be observed/detected from the path; B) For a higher accuracy measurement of a path with static characteristics via accumulated/combined measurements over time; and/or C) For tracking of a path associated with a moving target object.

[0060] To address the need for monitoring propagation paths via sensing procedure, the present disclosure describes techniques and procedures for facilitating the detection and/or identification of paths to be tracked (also referred to herein as “tracking paths”) and for which the path information shall be stored at the sensing Rx node.

[0061] Additionally, the present disclosure describes techniques and procedures for facilitating the necessary information exchange between a sensing Rx node and a controller entity of a sensing operation (referred to as the sensing management function (SensMF)), including the reporting of the path modifications and/or augmented measurements of a detected tracking path.

[0062] Regarding network-based and UE-based (i.e., SL-based) radio sensing operations, different scenarios for radio sensing are presented in Figures 4A and 4B. In some scenarios of radio sensing, the network configures the participating sensing entities, i.e., network and UE nodes acting as sensing Tx nodes, network and UE nodes 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 and the UE nodes 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.

[0063] Figure 4A depicts possibilities for sensing scenarios for a radio sensing operation 400 where a RAN entity performs a sensing RS transmission, according to embodiments of the disclosure. In the scenarios of Figure 4A, sensing RS reception is performed by one or more UEs, one or more RAN entities, or a combination thereof. The radio sensing operation 400 may involve a first RAN entity 402 (e.g., a gNB or network TRP node), a second RAN entity 404 (e.g., a gNB or a network TRP node), and/or a set of at least one UE (represented by the first UE 406).

[0064] In various embodiments, the radio sensing operation 400 is used to detect and locate an object of interest 408. In general, a Radio-based sensing transmission 410 is performed by the first RAN entity 402. While the below examples describe the Radiobased sensing transmission 410 using a sensing reference signal (“sensing RS”) 412, in other embodiments the Radio-based sensing transmission 410 may be a transmission of another RS or instead may be a transmission of the data/control channels known to the network TRP nodes. [0065] In a first sensing scenario (also referred to herein as “Case I”), the Radio-based sensing transmission 410 is performed by a first network node (i.e., the first RAN entity 402) and the Radio-based sensing reception 416 is performed by a separate network node (i.e., the second RAN entity 404). In this case, the sensing RS 412 (or another RS used for sensing) is transmitted and a reflection/backscatter signal 414 is received by network entities. The network does not utilize UEs for sensing assistance in this scenario. Rather, the involvement of UE nodes (i.e., first UE 406) is limited to the aspects of interference management, when necessary.

[0066] In a second sensing scenario (also referred to herein as “Case II”), the Radiobased sensing transmission 410 is performed by a first network node (i.e., the first RAN entity 402) and the Radio-based sensing reception 418 is performed by the same network node. In this case, the sensing RS 412 (or another RS used for sensing) is transmitted and a reflection/backscatter signal 414 is received by the same network entity. The network does not utilize UEs for sensing assistance in this scenario. Rather, the involvement of UE nodes (i.e., first UE 406) is limited to the aspects of interference management, when necessary.

[0067] In a third sensing scenario (also referred to herein as “Case III”), the Radiobased sensing transmission 410 is performed by a first network node (i.e., the first RAN entity 402) and the Radio-based sensing reception 420 is performed by a UE node (i.e., the first UE 406). In this case, the sensing RS 412 (or other RS used for sensing) is transmitted by a network entity and a reflection/backscatter signal 414 is received by one or multiple UE nodes, including the first UE 406. The network configures the UEs to act as a sensing Rx node, according to the UE capabilities for sensing, as well as desired sensing task.

[0068] Figure 4B depicts possibilities for sensing scenarios for a radio sensing operation 430 where a UE performs a sensing RS transmission, according to embodiments of the disclosure. In the scenarios of Figure 4B, sensing RS reception is performed by one or more UEs, one or more RAN entities, or a combination thereof. The radio sensing operation 430 may involve the first UE 406, a set of at least one peer UE (represented by the second UE 432), and/or a set of at least one TRP (represented by the first RAN entity 402).

[0069] In various embodiments, the radio sensing operation 430 is used to detect and locate an object of interest 408. In general, a Radio-based sensing transmission 434 is performed by the first UE 406. While the below examples describe the Radio-based sensing transmission 434 using a sensing RS 436, in other embodiments the Radio-based sensing transmission 434 may be a transmission of another RS or instead may be a transmission of the data/control channels.

[0070] In a fourth sensing scenario (also referred to herein as “Case IV”), the Radiobased sensing transmission 434 is performed by a first UE 406 and the Radio-based sensing reception 440 is performed by a RAN entity (i.e., the first RAN entity 402). In this case, the sensing RS 436 (or another RS transmitted for sensing) is transmitted by a UE node and a reflection/backscatter signal 438 is received by one or multiple network entities. The network configures the transmitting UE (i.e., the first UE 406) to function as a sensing Tx node, according to the UE nodes’ capabilities for sensing, as well as the nature of the desired sensing task.

[0071] In a fifth sensing scenario (also referred to herein as “Case V”), the Radio-based sensing transmission 434 is performed by a first UE 406 and the Radio-based sensing reception 442 is performed by a separate UE (i.e., the second UE 432). In this case, the sensing RS 436 (or another RS transmitted for sensing) is transmitted by a UE node and a reflection/backscatter signal 438 is received by one or multiple UE nodes. The network, or potentially the first UE 406, may decide on configuration of the sensing scenario. In one instance, the network configures the UEs to function as a sensing Tx node and/or sensing Rx nodes, according to the UE nodes capabilities for sensing, as well as the nature of the desired sensing task.

[0072] In a sixth sensing scenario (also referred to herein as “Case VI”), the Radiobased sensing transmission 434 is performed by a first UE 406 and the Radio-based sensing reception 444 is performed by the same UE. In this case, the sensing RS 436 (or another RS transmitted for sensing) is transmitted by a UE node and a reflection/backscatter signal 438 is received by the same UE node. The UE or the network configures the sensing scenario, according to the UE nodes capabilities for sensing, as well as the nature of the desired sensing task.

[0073] 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 Ah 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 fried on November 30, 2021 for Seyedomid Taghizadeh Motlagh, Ali Ramadan Ali, Ankit Bhamri, Sher Ah Cheema, Razvan-Andrei Stoica, Hyejung Jung and Vijay Nangia, which applications are incorporated herein by reference.

[0074] 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 as well 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.

[0075] Integrated sensing and communication may enhance 5G core architecture by introducing a new Sensing Function (SF). Figures 5A-5D present possible combinations leading to the network impact.

[0076] Figure 5A illustrates an example of a tight coupling ISAC network architecture 500 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 Access and Mobility management Function (AMF), the Unified Data Management node (UDM), the Network Data Analytics Function (NWDAF), the Location Management Function (LMF), the Policy Control Function (PCF), the Network Exposure Function (NEF), and to the (radio) access network ((R)AN), optionally via the User Plane Function (UPF).

[0077] In the tight coupling ISAC network architecture 500, the SF appears as a dedicated network function (NF) handling both: /) the sensing control plane aspects such as the interaction with the sensing consumer via NEF and information exchange with other NFs, 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.

[0078] Figure 5B illustrates another example of a tight coupling ISAC network architecture 510, where the SF is functionally split/distributed among the CP and UP domains. As depicted, a CP split of the SF (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 (SF-C) is communicatively coupled to the (R)AN, optionally via the UPF.

[0079] In the tight coupling ISAC network architecture 510 with CP/UP split, the SF has two dedicated NF counter parts: z) 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.

[0080] Figure 5C illustrates an example of an ISAC network architecture 520, 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 5C. In the network architecture 520, the SF (i.e., colocated with the LMF) appears as a logical NF embedded in the LMF to perform sensing taking advantage of the knowledge of a UE location.

[0081] Figure 5D illustrates an example of a loose coupling ISAC network architecture 530, 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 5C.

[0082] In the loose coupling ISAC network architecture 530, the SF is independent of the 5G core, i.e., typically used for local field scenarios or private networks, and the interaction with the 5G core 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 5G core for the purpose of exposure via NEF, for getting the UE location from the AMF and for analytics (i.e., NWDAF interaction).

[0083] In another description of controlling a sensing operation, in some example implementations, a sensing controller entity/function (SensMF) is defined which comprises one or multiple of a UE, a RAN node, a gNB/gNB-CU, an LMF, an SF, 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 information based on the obtained sensing measurements; and/or F) Reports/exposes an obtained sensing information to the entity requesting the sensing information.

[0084] In some examples wherein the SensMF is comprised of multiple nodes/entities, one part of the above-mentioned steps may be implemented by the first part of the SensMF, and the second part of the above steps may be implemented by the second part of the SensMF, e.g., implemented in the SF and gNB. In some examples wherein the SensMF is comprised of multiple nodes/entities, the communication among the SensMF entities is transparent to the outside entities and also not discussed in the related handover procedure embodiments, nevertheless, the communication among the SensMF entities is assumed to be implicit to the overall procedure.

[0085] 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 sensing function (SF) residing in core network, may be a UE, or a combination thereof.

[0086] The following LI measurements are relevant to sensing operation in accordance with the present disclosure: UE Rx-TX time difference; gNB Rx-Tx time difference, DL PRS RSRPP, UL SRS RSRPP.

[0087] The UE Rx-Tx time difference is defined as TUE-RX - TUE-TX, where TUE-RX is the UE received timing of downlink subframe #i from a Transmission Point (TP) , defined by the first detected path in time, and where TUE-TX is the UE transmit timing of uplink subframe #j that is closest in time to the subframe #i received from the TP. Note that multiple DL PRS or CSI-RS for tracking resources, as instructed by higher layers, can be used to determine the start of one subframe of the first arrival path of the TP.

[0088] For frequency range #1 (FR1), the reference point for TUE-RX measurement is the Rx antenna connector of the UE and the reference point for TUE-T measurement is the Tx antenna connector of the UE. For frequency range #2 (FR2), the reference point for TUE-RX measurement is the Rx antenna of the UE and the reference point for TUE-TX measurement is the Tx antenna of the UE. The UE Rx-Tx time difference is applicable to a UE in the RRC CONNECTED state and in the RRC INACTIVE state.

[0089] The gNB Rx-Tx time difference is defined as T_SNB-RX - T_SNB-TX, where T_SNB-RX is the Transmission and Reception Point (TRP) received timing of uplink 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 downlink subframe #j that is closest in time to the subframe #i received from the UE. Multiple SRS resources can be used to determine the start of one subframe containing SRS .

[0090] The reference point for the T_SNB-RX 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-0 or 2-0 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).

[0091] Similarly, the reference point for the T_SNB-TX shall be: the Tx antenna connector for atype 1-C base station (e.g., as described in 3GPP technical specification (TS) 38.104); the Tx antenna (i.e., the center location of the radiating region of the Tx antenna) for a type 1-0 or 2-0 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).

[0092] The DL PRS-RSRPP 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 DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time.

[0093] For FR1, the reference point for the DL PRS-RSRPP shall be the antenna connector of the UE. For FR2, DL PRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. The UE Rx-Tx time difference is applicable to a UE in the RRC CONNECTED state and in the RRC IN ACTIVE state.

[0094] The UL SRS-RSRPP is defined as the power of the linear average of the channel response at the z-th path delay of the resource elements that carry the received UL SRS signal configured for the measurement, where UL SRS-RSRPP for 1st path delay is the power contribution corresponding to the first detected path in time.

[0095] 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-0 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).

[0096] 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.

[0097] A detected path at the sensing Rx node is determined as a path to be monitored, hereafter called a tracking path, (by the sensing Rx node or by a SensMF or both) by storing the measurements of the path at different time instances (by the sensing Rx node or by a controller entity or both). Based on sensing measurements of multiple sensing signals at different time instances, modification of the path in one or more of the path parameters of power, or delay, or angle, or doppler is detected and reported by the sensing Rx node to the controller entity.

[0098] As used herein, the tracking path refers to a propagation path of interest to be monitored for certain path modification events (e.g., blockage, etc.). In one embodiment, the sensing Rx node determines that a particular path is a path of interest (i.e., tracking path), e.g., based on path characteristics and/or a modification/change to the path characteristics. In another embodiment, the SensMF determines that a particular path is a path of interest (i.e., tracking path) and indicates this to the sensing Rx node.

[0099] At the sensing Rx node, subsequent to a path being known as (or determined to be) a tracking path, the sensing Rx node: 1) initiates the context for the path (i.e., starts storing related path information over time) by which the sensing Rx node detects/measures path modification, or 2) delays forgetting the path information for an indicated or a preconfigured time or indefinitely (e.g., subject to a later indication/determination for deleting the path information), or both.

[0100] At the SensMF, upon a path being indicated as a tracking path (e.g., by the sensing Rx node to the SensMF or from the SensMF to the sensing Rx node) the SensMF may assume that: 1) the sensing Rx node stores a context information of the path which can be reported/transferred, and 2) the sensing Rx node is capable of reporting path measurements (including modifications) utilizing the measurement time window (e.g., also from one or more past measurements) where the path context (also referred to as “context information”)is stored/initiated.

[0101] Such indication of a path being a tracking path by the SensMF may be explicit, or implicit. An example of an implicit indication is indicating a path for a certain measurement quantity, which implies the indicated path being a tracking path and for which the context information shall be maintained (e.g., for a path indicated to be monitored for a blockage event over time).

[0102] Another example is the indication of a path as a static path for which the path parameters shall be measured with a high accuracy via accumulated measurements in time (e.g., by averaging of many sensing measurements at different time instances) or a path for which the path angle/delay/doppler parameters are expected to change and the change is requested by the SensMF to be monitored and reported by the sensing Rx node. For the case of such implicit indications, the sensing Rx node and/or the SensMF may assume the path being associated with a path context upon the indication. Hence the context information may be later indicated to be deleted, transfer to another node, or reported to the SensMF.

[0103] In some alternate implementation of the path being a tracking path, the indication of a tracking path includes a path of interest, for which the storage of the related/needed path information is up to sensing Rx node’s implementation. In some such embodiments, the SensMF may request for reporting/transfer of the context Information of a path without an explicit or implicit prior indication of a context information being present for the path, and for which the sensing Rx node may report (positively/negatively) on the availability of the context information, e.g., when the requested context Information is not available.

[0104] As used in the present disclosure, the indication, reporting, context information, and/or measurement of a path is not limited to a single interpretation of a path. Accordingly, a “path” (associated with a transmission point, e.g., sensing Tx, and a reception point, e.g., sensing Rx) can be interpreted as any of: [A] a propagation path comprising a ray; [B] a propagation path comprising a multipath component; [C] a propagation path associated at least with a ray cluster or the direct path; [D] a propagation path/ray or group of propagation paths/rays associated with a reflection from a reflector; [E] a propagation channel (comprising all associated rays) between a transmission and reception point; [F] a propagation channel between a transmission and reception point for a conditioned part of the channel (e.g., comprising all associated rays to a specific delay/angle/doppler range); or combinations thereof.

[0105] In one example of the above variations of interpretations, a path context can be generated/maintained for a path at a sensing Rx node, and subsequently a path modification can be detected/measured and reported by a sensing Rx node, in one embodiment, for the first interpretation of the path (e.g., interpretation [A]) and in another (non-exclusive) embodiment, for a second interpretation of the path (e.g., interpretation [F]). In one example, when a path context is generated with interpretation [F], the modification of the channel/path may comprise detection of a new ray/multi-path component within the channel, e.g., due to the emergence of a new reflector within the relevant area for the channel.

[0106] It is understood that the present disclosure is not limited to the single embodiment and/or implementation elements individually, and one or more elements from one or more implementations and/or embodiments may be combined to construct a new embodiment. Moreover, applicability /utilization of any of the proposed message exchange, architecture, configuration, measurement, capability information elements within this disclosure is not intended to be restricted to the particularly defined scenario and is intended to be interpreted as applicable for any alternate application/scenario, e.g., not being limited to a sensing measurement scenario and/or a positioning measurement scenario.

[0107] In accordance with aspects of a first solution, a sensing Rx node detects a path based on, at least in part, sensing measurements of a sensing signal of a first time instance (or plurality of first time instances). Upon detection of the path or upon determining the path as being a tracking path or upon indication of the SensMF of the detected path as being a tracking path for the sensing Rx node, the sensing Rx node stores context information associated with the path.

[0108] The context information may include one or more of: A) a path identifier (ID) (e.g., one or multiple path IDs); B) a path group ID; C) sensing measurements of different time instances and/or different sensing signals associated with the detected path; D) one or more time stamps associated with the stored sensing measurements; E) a set of one or more prior detected path modifications; F) one or more time stamps associated with a detected path modification (e.g., a time of detected blockage/RSRPP drop, doppler change etc.); G) a set of sensor measurements from one or more sensors associated with the radio node(e.g., a camera, a photosensor, a motion sensor, etc.); H) a set of spatial filters associated with the path; I) a set of beams associated with the path (e.g., one or multiple beams by which the sensing Rx node have detected/measured the path, the one or multiple beams by which the sensing Tx has transmitted the sensing signal by which the sensing Rx has detected/measured a path); J) one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value; K) a geometrical relation to another path; L) a transmit point location associated with the path (e.g., as indicated by the SensMF or detected by the sensing Rx node); M) one or more transmission characteristics of the path (e.g., angle-of-departure (AoD) and/or zenith-of-departure (ZoD), TP mobility pattern etc. associated with the path); N) a reflector entity associated with the path; or a combination thereof.

[0109] The sensing Rx node further detects and/or measures modification of the tracking path based on measurement of sensing signal of a subsequent time instance (or plurality of subsequent time instances), e.g., as compared to the stored measurements of a previous time instance (or plurality of previous time instances). When one or more reporting criteria are met, the sensing Rx node reports the detected/measured modification of the tracking path to the SensMF.

[0110] In some embodiments, the sensing Rx node receives a configuration for the reception of one or more sensing signals at one or more time instances. In certain embodiments, the configuration/parameters defining the sensing signal is received from the SensMF (e.g., the SF/LMF residing in core, a controller entity for sensing residing in RAN, a gNB assigned as a head gNB of a sensing task) or a UE/ RAN node (e.g., gNB) responsible for configuration of the sensing signal, etc. In certain embodiments, the sensing signal is a physical channel transmission for data or control signaling in the DL, the UL, and/or SL directions. For example, sending signal may be a PDCCH transmission, a PDSCH transmission, a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, and/or a physical sidelink shared channel (PSSCH) transmission. In one embodiment, the sensing signal is intended for the sensing Rx node or is expected to be decodable by the sensing Rx node. In another embodiment, the sensing signal is intended for a different node (i.e., not the sensing Rx node) or is not expected to be decodable by the sensing Rx node.

[0111] In some embodiments, the sensing signal is a reference signal (RS) transmitted in the DL, UL, SL or TRP-to-TRP directions, e.g., according to a known timing at the sensing Tx node and/or sensing Rx node. For example, the sensing signal may be a positioning reference signal (PRS), a sounding reference signal (SRS), or a sensing- dedicated RS. In such embodiments, the RS may be transmitted according to the time/frequency reference of the DL/UL/SL frame of the sensing Tx node or sensing Rx node. [0112] In some embodiments, the sensing Rx node performs sensing measurements based on the received one or more sensing signals (e.g., at different time instances) and further reports the obtained sensing measurements to the SensMF.

[0113] In various embodiments, the report of the sensing measurements comprises one or more of: A) the reporting of a detected path; B) the reporting of further information of a detected path; C) an indication of a path as a tracking path; D) an indication of a path as a candidate for being a tracking path; E) an indication of a tracking path modification; F) the context information of a tracking path; G) a time -stamp associated with a sensing measurement; or a combination thereof.

[0114] When reporting of a detected path, in some embodiments, the detection of the path is based on criteria prior indicated by the SensMF. For example, the prior indicated criteria may include a permissible range of the path parameters (e.g., direction-of-arrival (DoA), zenith-of-arrival (ZoA), time-of arrival (ToA), and/or doppler shift). The permissible range may be defined according to a power, or time, or frequency, or angle reference global known or locally known at the sensing Rx node.

[0115] In various embodiments, the sensing Rx node may receive (e.g., from the SensMF) a path description. In one embodiment, a path that matches the path description is considered to be a tracking path. In certain embodiments, the sensing Rx node may determine the path description, e.g., for reporting a detected path to the SensMF. The path description (and/or configuration information for detection of a path) may comprising all or subset of the following elements:

[0116] In some embodiments, the measurement of a sensing Rx node comprising indication and/or identification of one or multiple paths by the sensing Rx node, wherein the propagation paths may include: A) propagation paths associated with a sensing target and/or a sensing target area of interest; B) paths associated with a direct (i.e., line-of-sight (LOS)) propagation condition (e.g., blocked or non-blocked, 1^st detected path delay) from one or multiple sensing Tx nodes; and/or C) propagation paths associated with a reflection from a known (e.g., defined a priori) reflector (e.g., an NCR or RIS) or a known object (e.g., a metallic car with a known position and/or reflection characteristics).

[0117] In some embodiments, the identification of a path associated with a sensing target or target area of interest is performed by the sensing Rx node according to an indicated (by the SensMF to the sensing Rx measurement node) or a known (e.g., via the application information residing on sensing Rx node) description of the path, wherein the description comprising one or more of: A) propagation time/delay characteristics; B) propagation path direction; C) movement/mobility pattern associated with the propagation path; D) the energy/power associated with the propagation path; E) paths detected according to an RSRPP increase and/or decrease of above an indicated threshold; or F) a combination of one or multiple of the above.

[0118] Regarding the propagation time/delay characteristics, a path may be described according to the propagation delay of the path according to a known time reference by the sensing Rx node. Examples of known time references include, but are not limited to, a global or a local clock or time reference, a time reference generated from another local measurement (e.g., reception time of another known signal), and the like. For example, the path description may include paths arrived within 5 nanoseconds from the arrival of a LOS path, or another known time reference to the sensing Rx node.

[0119] Regarding the propagation path direction, a path may be described according to the reflection point position information according to a known coordinate system or location reference by the sensing Rx node. Additionally, or alternatively, a path may be described according to angular information (e.g., angle-of-arrival (AoA) and/or ZoA) based on a known coordinate system at the sensing node or based on a known reference direction at the sensing node (e.g., according to a reception angle of another known signal and/or another known path, e.g., received LOS path).

[0120] Regarding the movement/mobility pattern associated with the propagation path, a path may be described according to the doppler frequency shift/difference of the path compared to a known frequency reference at the sensing Rx node. Regarding the energy/power associated with the propagation path, a path may be described according to the RSRPP of the path or sum-RSRPP of group of paths associated with the sensing target/target area.

[0121] In certain embodiments, a path description may include a relative description of any of the above to a previous measurement and/or a previously measured or identified/detected path at the sensing Rx node (e.g., a reported path measurement ID) or object (an object ID) or object type (e.g., a human) or a known path (e.g., a LOS path associated with a sensing Tx node or sensing signal measurement known by the sensing Rx node). For example, the path description may include paths detected according to an RSRPP increase and/or decrease of above an indicated threshold relative to a previous measurement of the sensing Rx node (at a previous measurement snapshot and/or based on a different indicated/configured sensing signal) and/or within an indicated (e.g., +/- 30 degrees of) the angular distance (from the azimuth, zenith, or joint azimuth and elevation perspective) of the detected LOS path of a measurement at the sensing Rx node.

[0122] In some embodiments, the description of a path further including one or more of a signal based on which the path has been previously detected/measured or to be detected/measured at the sensing Rx node, a level/threshold of RSRPP or change of RSRPP values, etc.

[0123] In some embodiments, indication of a path for the sensing Rx node is done via indication of a previous measurement wherein the path has been detected/identified and/or measured at the sensing Rx node. In some embodiments, the indication of the path to the sensing Rx node may include a combination of one or more of a path ID/number/order (e.g., second strongest path), a RS resource (e.g., PRS resource or PRS resource set or CSI-RS, SRS resource) ID, a path description. In some embodiments, when a signal ID and a path number (or path description or path ID) is indicated together, the sensing Rx node shall determine the path according to a previous measurement conducted on the indicated RS resource together with the path detected/identified within the measurement of the indicated RS resource.

[0124] In some embodiments, an indicated path P may be the path corresponding to the /'-th path of a path group identified at the sensing Rx node according to a path group description (e.g., all paths detectable by the sensing Rx node satisfying a path description as described in the previous embodiments), and according to an ordering law. For example, the paths of the path group may be ordered in the increasing (or decreasing) direction of path arrival time/path delay, path doppler shift or path AoA/ZoA with respect to a reference arrival direction (e.g., an indicated direction according to the location service (LCS), group communication service (GCS), or a reference detected direction of the LOS/first arrival path). In one embodiment, the indicated path P may correspond to the /'-th path delay of the channel response between the TP and the sensing Rx node. [0125] In certain embodiments, an indicated path P may be the path associated with a label/ID P. In certain embodiments, an indicated path P may be the path detected based on a path description ID P.

[0126] When reporting the further information of a detected path (e.g., the indicated detected path), in some embodiments, the sensing Rx node reports measured power values of the detected path, such as a RSRPP value measured over a sensing signal (e.g., a sensing- dedicated RS, CSI-RS, PRS, etc.).

[0127] In some embodiments, the sensing Rx node reports measured AoA, ZoA, doppler shift, or ToA values, e.g., as an absolute value or as a relative value (i.e., subtraction or ratio of two values). For example, the sensing Rx node may report the RSRPP as an SNR or signal-to-interference-plus-noise ratio (SINR) value where the noise power is known. As another example, the sensing Rx node may report the RSRPP as the difference of AoA/ZoA/doppler shift/ToA of a detected path and a reference/known path.

[0128] When reporting the further information of a detected path (e.g., the indicated detected path), in some embodiments, the sensing Rx node reports all or subset of the available context information for the path (when available) at the sensing Rx node.

[0129] When reporting the indication of a path as a tracking path (e.g., subsequent to the path being determined as a tracking path by the sensing Rx node and/or subsequent to a context being initiated and/or context information being stored at the sensing Rx node), in some embodiments, the determination of the path as being a tracking path is done at the sensing Rx node according to one or more conditions/criteria indicated by the SensMF.

[0130] When reporting the indication of a path as a candidate for being a tracking path, in some embodiments, the sensing Rx node initiates storage of the context information of the candidate path upon determining that the path is a candidate tracking path by the sensing Rx node. In other embodiments, the sensing Rx node may initiate storage of the context information upon a determination and/or an indication by the SensMF of the path being a tracking path.

[0131] In some embodiments, the sensing Rx node may release the context information upon the sensing Rx node determining that the candidate path is not a tracking path. In certain embodiments, the sensing Rx node may release (i.e., delete/forget) the context information in response to feedback from the SensMF that the indicated path is not a tracking path. In other embodiments, the sensing Rx node may release the context information if feedback is not received from the SensMF within a known, indicated or preconfigured time window/duration (e.g., two subframes) from the sensing Rx node reporting the path to the SensMF.

[0132] In some examples, the sensing Rx node may initiate storage of the context information upon detection of the path at the sensing Rx node in response to the detected path satisfying one or more criteria for automatic storage of the context (e.g., upon the path associated with a power, AoA/ZoA/ToA/channel or carrier phase/doppler shift/vibration or micro-doppler of an indicated range/value). In some embodiments, the determination of the path as being a candidate tracking path is done at the sensing Rx node according to one or more conditions/criteria indicated by the SensMF.

[0133] When reporting the indication of a tracking path modification, in some embodiments, the modification of a tracking path may comprise a blockage/drop in RSRPP (or a normalized RSRPP by the signal time and/or frequency resources and/or transmission power of the signal over which the RSRPP is measured, etc.) of at least a pre-configured or indicated threshold. In certain embodiments, the modification of the tracking path may include an increase, a decrease, an absolute change of one or more of path parameters (e.g., of power, AoA, ZoA, ToA, channel or carrier phase, doppler shift, vibration, or micro- doppler) in accordance with one or more preconfigured or indicated thresholds (which may be defined differently for the different path parameters). In certain embodiments, the modification of the tracking path may be based upon the slope or a change of slope (second order derivative), and/or based upon of a modification pattern (defined by the SensMF or pre -configured at the sensing Rx node) over an observation time window of one or more of the mentioned parameters.

[0134] In some embodiments, the indication of tracking path modification further comprises an indication of a modification type (via an index from a known/pre-configured table/codebook of envisioned modification types). In further embodiments, the indication of tracking path modification may include values of parameters defining the modification type. Table 1 describes an exemplary table or codebook comprising different path modification possibilities and associated additional reporting parameters. In some embodiments, one or more (envisioned/possible/of interest) modification types are indicated by the SensMF to the sensing Rx node, according to which the potential modifications are examined and/or reported.

Table 1: Path modification table/codebook

[0135] When reporting the context information of a tracking path, in some embodiments, all or subset of the context information associated with a tracking path available at the sensing Rx node is reported to the SensMF . In one embodiment, the sensing Rx node reports the context information upon request of the SensMF. In another embodiment, the sensing Rx node reports the context information upon reporting a candidate tracking path or upon reporting of the determined tracking path by the sensing Rx node. In further embodiments, the sensing Rx node may report the context information upon determining and reporting of a tracking path modification by the sensing Rx node.

[0136] When reporting the time stamp for which an above-described measurement is obtained, in some embodiments, when a sensing signal is periodic or comprises multiple separable segments in time domain, the reporting of the sensing Rx node further comprising the indication of the one or multiple sensing signals by which a particular measurement/reported is generated. In some embodiments, when the sensing procedure comprises multiple signals with separately mapped physical resources of at least one domain of time, frequency, code, antenna port/beam domains, the reporting of the sensing Rx node further comprising the indication of the one or multiple sensing signals by which a particular measurement/reported is generated.

[0137] In some embodiments, a tracking path is detected/determined at the sensing Rx node the detected tracking path and/or the associated measurements are not reported initially to the SensMF, but the sensing Rx node still stores the context information of the detected tracking path and further measurements associated with a tracking path. In some such embodiments, upon detection of a modification of a tracking path by the sensing Rx node, the modification is reported to the SensMF, with the report comprising one or more of the path measurement/context information, as well as the modification type and associated parameter/values of the modification type. In other words, in such embodiments the sensing Rx node may autonomously track and store context information of one or more paths, but the sensing Rx node does not report the paths (and/or the context information) to the SensMF until the path modification is detected.

[0138] In some embodiments, the reporting of the detected (candidate) tracking paths and/or measurement/reporting of the tracking path modifications is done subsequent to receiving configuration information, by the SensMF, for performing sensing measurements and reporting based on the received one or more sensing signals. In some embodiments, the measurement and reporting configuration information may include one or more of the following: A) criteria for detection of a tracking path or a candidate tracking path; B) assistance information for detection/measurement of a tracking path at the sensing Rx node; or a combination thereof.

[0139] Regarding the criteria for detection of a tracking path or a candidate tracking path, one criterion may be that the RSRPP is above a threshold for measurement instances of at least a minimum measurement time (e.g., across min. N measurements of the sensing signals within 10 second). Another criterion may be that the path is associated with an object/reflector of interest, the path parameters (e.g., power, RSRPP/AoA/ZoA/ToA/channel or carrier phase/doppler shift/vibration) are within an indicated range of interest.

[0140] Regarding the assistance information for detection/measurement of a tracking path at the sensing Rx node, in certain embodiments the assistance information may include an indication of additional Tx signals illuminating the path, e.g., indication of CSI-RS-/ and an PRS-2 and SSB-J illuminating the same AoD/ZoD corresponding to a detected path ID, with a minimum transmission/radiation power along the AoD/ZoD of the detected path.

[0141] In certain embodiments, the assistance information may include a radiation pattern of the transmitted/indicated sensing signals, e.g., comprising beam direction, beamwidth, transmission power, etc. In certain embodiments, the assistance information may include AoD and/or ZoD information associated with the path.

[0142] In certain embodiments, the assistance information may include a transmission point (TP) location associated with the path. For example, the TP location may be an absolute location of the TP or a relative location (e.g., relative to the reception point). In certain embodiments, the assistance information may include a reflector location associated with the path. For example, the reflector location may be an absolute location of the reflector or a relative location (e.g., relative to the reception point).

[0143] In certain embodiments, the assistance information may include an indication of a path being a direct path or a first order reflection path. In certain embodiments, the assistance information may include an indication of a tracking path to the sensing Rx node.

[0144] Regarding the context information of a path, in some embodiments, the context information stores at the sensing Rx node may include a Path ID (or multiple Path IDs, or a path group ID) to which the context information is relevant. In some embodiments, the context information may include measurements of the path performed by the sensing Rx node (power, RSRPP, AoA, ZoA, ToA, channel or carrier phase, doppler shift, and/or vibration) of different sensing signals and/or of different time instances. In some embodiments, the context information may include time stamps corresponding to the measurement values.

[0145] In some embodiments, the context information may include information regarding one or more prior detected modifications of the path. In some embodiments, the context information may include a time stamp corresponding to a detected/measured path modification (e.g., a time of detected blockage, a time of RSRPP drop, a time of doppler change, etc.).

[0146] In some embodiments, the context information may include measurements from non-RAT dependent sensors, e.g., associated with an angle or viewpoint of the sensing Rx node associated with the path. As an example, the sensor measurements may include input from the camera or red-green-blue (RGB) sensors. As another example, the sensor measurements may infer an event from the camera/sensors (e.g., camera blockage, a motion sensor trigger) obtained from relevant viewpoints of the related AoA/ZoA to the path). [0147] In some embodiments, the context information may include one or more spatial filter/Rx beams utilized to observe the path signal reception. In some embodiments, the context information may include one or more spatial filter/Tx beams utilized to observe the path signal transmission.

[0148] In some embodiments, the context information may include an indication of one or multiple associated paths (i.e., other than the identified path). Here, a respective path may be an associated path based on a close path parameter (i.e., where a difference in measured values is less than a threshold), such as a doppler value, a delay value, an angle value (e.g., AoA, ZoA), a vibration value, a ToA value, etc.

[0149] In some embodiments, the context information may indicate a relation of the detected path with one or more other paths (e.g., a geometrical relation of the path to another path), as indicated by the SensMF or detected by the sensing Rx node.

[0150] In some embodiments, the context information may include a transmitter point/po sition associated with the path, when available (TRP or UE or a TP as the starting point of the path). In some embodiments, the context information may include a transmission characteristics of the path, when available (e.g., AoD and/or ZoD values, a TP mobility pattern associated with the path, etc.). In some embodiments, the context information may identify an associated reflector entity associated with the path (e.g., a reconfigurable intelligent surface (RIS), or an object ID associated with a reflection during the propagation path).

[0151] As used herein, a RIS refers to a programmable surface structure that can be used to control the reflection of electromagnetic (EM) waves by changing the electric and magnetic properties of the surface. RIS may be strategically placed in the radio channel between a transmitter and receiver to control the way the signal reflects off a surface in its propagation path. Accordingly, one or more RIS can be used to steer signals to the receiver resulting in better reception or link quality.

[0152] In some embodiments, SensMF indicates a tracking path to a sensing Rx node, e.g., upon reception of a sensing Rx report of detection of the path (with or without indication of the path as a candidate tracking path), or independent from reception of a sensing Rx report of the detected path (e.g., indicated by the SensMF to the sensing Rx node as part of the path description, that a detected path according to an indicated path description is a tracking path). Responsive to the indication by the SensMF, the sensing Rx node stores the related path information/measurement, e.g., as the path context.

[0153] In some embodiments, one or multiple time window/durations are indicated or preconfigured for the sensing Rx node, e.g., for which an obtained measurement/information of a path (i.e., detected or indicated) is to be stored and/or maintained. In certain embodiments, different durations may be indicated (or preconfigured) for different types of path parameters. In other embodiments, the same duration may be indicated (or preconfigured) for the different types of path parameters.

[0154] In certain embodiments, the one or multiple time window/durations are applicable to all detected paths. In certain embodiments, certain time window/durations are applicable to detected paths satisfying an indicated criteria (e.g., within a certain AoA/ZoA or doppler shift margin). In certain embodiments, certain time window/durations are applicable to paths detected as (candidate) tracking paths.

[0155] As such, a sensing Rx node, subsequent to having the capability for performing sensing measurements including storing of the path information, and further subsequent to detecting a path or detect a path compliant with the indicated parameters, may construct (e.g., initiate) a path context for the path and stores the related/available path parameter measurements. In some such embodiments, the initiation of the path context and storing of the related path information is implicitly indicated, via indication of a measurement type including detection/measurement of a path modification.

[0156] In one such example, upon detection and reporting of a path by the sensing Rx node, the SensMF indicates to the sensing Rx node for measurement of the path modifications of delay, doppler (e.g., over the span of an indicated time window or over multiple sensing signals of different time instances etc.). Responsive to receiving the indication, the sensing Rx node shall assume the detected/reported path as a tracking path and initiate a context information for the path and store relevant information for measurement of the path modification.

[0157] In some embodiments, the SensMF may indicate, to the sensing Rx node, the type of the tracking path and/or the type of the expected path modification measurement/ report to be conducted by the sensing Rx node. In certain embodiments, the indication to the sensing Rx node may be an index from a table/codebook, wherein the table/codebook comprises different possible path modifications and/or measurement/reporting quantities related to the path modification. Examples of the different possible path modifications include, but are not limited to, a modification of the path delay, a modification of a doppler shift, a modification of a path power or power drop/blockage, a modification of a path angle, or a combination thereof. Upon detection of the one or more indicated modifications at the sensing Rx node, in some embodiments, the sensing Rx node is requested to report the said modification, e.g., by detecting a closest reporting time/instance (as configured/indicated by the SensMF) to the said detection of path modification and transmit the report to the SensMF.

[0158] In some embodiments, the SensMF may use an index from a table/codebook to indicate different path context information types, time/memory requirements for the storage of path context information, and/or an accuracy/resolution of the information storage.

[0159] In some embodiments, upon detecting (and reporting) a path by the sensing Rx node (e.g., a path of at least an indicated RSRPP (measured from an indicated sensing signal) within an indicated range of AoA/ZoA of interest as indicated by the SensMF to the sensing Rx node), the SensMF determines whether the detected/reported path is a first- order reflection. For example, this determination may be based at least in part on the reported ToA of the path at the sensing Rx node and the time of transmission from the sensing Tx node. As another example, this determination may be based at least in part on the AoA/ZoA and position of the sensing Tx and sensing Rx nodes.

[0160] If the SensMF determines that the first order-reflection path is a tracking path (e.g., based on the path associated with a target or area of interest for a sensing task), then the SensMF may further indicate, to the sensing Rx node, that the detected path is a tracking path for which the sensing Rx is to initiate a context and store the related measurements (i.e., as context information). Additionally, or alternatively, the SensMF may indicate that the detected path includes a single reflection point between the sensing Tx and sensing Rx node.

[0161] In certain embodiments, upon indicating a plurality of the sensing signals (e.g., an SSB l, SSB 2, CSI-RS_1, CSI-RS_2, PRS_1, PRS_2, PRS_3, etc. with different/separate transmission times) the SensMF may further indicate a relation of the transmission radiation pattern between the sensing signal transmissions. For example, the SensMF may indicate (i.e., inform the sensing Rx node) of the transmission energy towards the AoD and/or ZoD related to an indicated path.

[0162] In some embodiments, the sensing Rx node may receive an indication to release (i.e., delete/forget) the context information of a tracking path. Additionally, or alternatively, the sensing Rx node may be pre-configured with one or more conditions triggering the release of context information (e.g., of a respective tracking path).

[0163] In one embodiment, the sensing Rx node may release the context information upon an indication by the SensMF to forget/release the information. In another embodiment, the sensing Rx node may release the context information upon an indicated/pre-configured time duration upon reporting of a detected path is expired.

[0164] In one embodiment, the sensing Rx node may release the context information upon an indicated time duration after reporting of a path modification of type blockage/RSRPP drop has been expired. In another embodiment, the sensing Rx node may release the context information upon RSRPP of a path is below an indicated threshold or remains below the threshold for an indicated period of time.

[0165] In some embodiments, the sensing Rx node may report the context information (or a subset of the context information) prior to releasing the context information. In one embodiment, the sensing Rx node reports the context information (or subset thereof) to the SensMF prior to the release. In another embodiment, the sensing Rx node may report the context information (or subset thereof) to a second sensing Rx node prior to the release. Here, the second sensing Rx node may be determined by the SensMF, and its identity indicated to the first sensing Rx node.

[0166] In one embodiment, the transfer of the context information from the first sensing Rx node to the second sensing Rx node is done indirectly and facilitated by the SensMF. For example, the first sensing Rx node may transfer the context information to the SensMF, which then transfers the context information to the second sensing Rx node. Alternatively, in another embodiment, the first sensing Rx node directly communicated from the first to the second sensing Rx node, e.g., via a direct logical interface between the two sensing Rx nodes. In both embodiments, the SensMF may configure the address/transmission parameters of the transfer of the context information. Alternatively, a gNB associated with the sensing task (or associated with the first and/or second sensing Rx node may configure the address/transmission parameters of the transfer of the context information.

[0167] In some embodiments, as additional information in the context information, the SensMF may maintain beam pairs for which a path, path group, object, is observable. In some embodiments, as additional information in the context information, the SensMF may maintain beam pairs which the sensing Rx node has a context information already.

[0168] In some embodiments, the SensMF and/or sensing Rx node may apply data compression when storing the path context information and/or path measurements. For example, the information/measurement instances may be stored using individual compression of the information point. As another example, the information/measurement instances may be stored using a displacement value relative to a previous related measurement (i.e., storing only the delta/difference compared to a previous measurement instance).

[0169] In some embodiment, when two or more paths are indicated to be associated/related with a geometrical relation, then a path modification on the two paths are reported jointly, e.g., indicating of the two related paths are blocked/modified jointly. In some such examples, when a blockage is reported jointly on the two related paths sharing a same reflector point/object towards the sensing Rx node (but different transmission points), the blocking object is inferred to be located between the shared reflector of the two paths and the sensing Rx node.

[0170] Geometrical path relations between a first and second path may be based on shared path properties, such as the AoA, ZoA, doppler shift, and/or time-of-flight (ToF)Zdelay, as described in further detail in U.S. Provisional Patent Application 63/551,966 entitled “TECHNIQUES FOR INDICATING GEOMETRICAL PATH RELATIONS” and filed on February 9, 2024, for Seyedomid Taghizadeh Motlagh and Ah Ramadan Ah. The geometrical path relation may be indicated using an index from a known/pre -configured table/codebook of envisioned geometrical path relations.

[0171] In some embodiments, when the sensing Rx node receives an indication to perform observation/monitoring of a group of paths/rays (e.g., corresponding to a group of the path context of a shared context of a group of paths/rays), then upon detection of a blockage (e.g., of an RSRPP drop) over a plurality of the paths, or upon observation of a path modification over a plurality of the paths of the path group, the sensing Rx node reports the observed modification of the group of path as a group modification report, e.g., reporting RSRPP drop of the paths of a path group or modification of the perceived ToA from a path group, or a doppler shift modification of a path group.

[0172] In some embodiments, a newly appeared/detected path by the sensing Rx may be indicated/reported as being relevant to a blocked/modified tracking path. For example, the sensing Rx node may indicate that the newly detected path is a moved version of the modified path or caused by a blocker object of the blocked path. In some embodiments, the geometrical path relations of the two or more paths are indicated by the SensMF to the sensing Rx node, for the geometrical path relations, e.g., as described in in U.S. Provisional Patent Application 63/551,966.

[0173] In certain embodiments, the sensing Rx node may further indicate (e.g., to the SensMF) the type of the path relation, e.g., via an index from a table including possible geometrical path relations or possible path modification relations. Examples of path relations include, but are not limited to, a path reflector of a newly observed path is a blocker of another path, two paths share the same blocking object etc. Table 2 describes an exemplary table or codebook comprising different path relation possibilities and associated additional parameters.

Table 2. Path relation table/codebook

[0174] In accordance with aspects of a second solution, based on the observation of being static, for at least an indicated duration of time, a tracking path may be identified as a static tracking path for which high-resolution measurements are to be collected. The determination of a static tracking path may be made by the sensing Rx node or at the SensMF. In some embodiments, the determination of a static tracking path may be based on observations with respect to one or more path parameters, such as at least one or more of the delay, angle, doppler, vibration parameters. In some embodiments, the determination of a static tracking path may be based on the observed path having an RSRPP (associated with the observed measurements) above an indicated threshold.

[0175] Subsequent to the determination that the tracking path exhibits static path characteristics, the sensing Rx node may store the path measurements (or may continue to store the related path measurements as part of the context information of the path), and generate estimates of the path parameters, e.g., of a higher accuracy/resolution, for all or a subset of the path parameters being indicated by the SensMF (or detected by the sensing Rx node) as being static. Here the generated estimates may be based on the collective measurement of the path over time.

[0176] In some embodiments, upon detection of the path being a static path in one or more of the path parameters, the sensing Rx node conducts further measurements and detects path modification of the static path parameters (e.g., when the observed ToA of the path or the observed doppler shift of the path has changed) and reports the detected path modification to the SensMF. For example, the sensing Rx node may monitor for blockage on the path associated with the static environment.

[0177] In one example, the sensing Rx node observes static paths with at least delay and angle parameters unchanged (below a threshold) over at least two subsequent measurement times (e.g., frames), relevant to an indicated sensing area of interest by the SensMF (within AoA of 20-45 degree of the radio node as indicated by the SensMF) and thereafter indicates the paths as candidate tracking paths to the SensMF, together with additional path parameters of e.g., delay, angle, doppler, power etc. The SensMF then determines the paths are then determined to be of interest for further monitoring (for a higher accuracy measurement or for blockage monitoring) and thereafter indicated to the radio node as tracking path, for which the sensing Rx node shall maintain the related path information for an at least a period of time, and reports upon a modification of blockage or modification of delay and/or AoA of the paths.

[0178] In accordance with aspects of a third solution, the tracking path may be determined at the sensing Rx node or at the SensMF based on the path being associated with a sensing target object/reflector. In certain embodiments, the target object may be associated with a sensing task/request, including tracking of the target. For example, the sensing Rx node may receive an indication from the SensMF of the path being associated with an object/target. As another example, the sensing Rx node may determine the detected path to be associated with an object/target based on the available higher layer information at the sensing Rx node.

[0179] In certain embodiments, the determination that a tracking path is associated with a sensing target object or reflector is based on RAT-independent data, e.g., sensor measurements. In certain embodiments, the determination that a tracking path is associated with a sensing target object or reflector is based on application information connected to/residing at a device associated with the sensing Rx node.

[0180] In some such embodiments, upon detection of the path being associated with a sensing target object, the sensing Rx node conducts further measurements and detects path modification of the path parameters (e.g., evolution of angle, doppler, delay information), and subsequently reported the detected modification to the SensMF.

[0181] Figure 6 illustrates an example of a UE 600 in accordance with aspects of the present disclosure. The UE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, 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.

[0182] The processor 602, the memory 604, the controller 606, or the transceiver 608, 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.

[0183] The processor 602 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 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the UE 600 to perform various functions of the present disclosure.

[0184] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602, cause the UE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 604 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.

[0185] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the UE 600 to perform various functions (e.g., operations, signaling) described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). In some implementations, the processor 602 may include multiple processors and the memory 604 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 600 as disclosed herein.

[0186] For example, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to receive, from a second device, a configuration for sensing measurement and reporting, based on one or more sensing signals. In certain implementations, the configuration further indicates information for the reception of the one or more sensing signals of one or plurality of time instance. The processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to determine a path based at least in part on a reception and measurement of the one or more sensing signals.

[0187] The processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to store context information associated with the determined path, wherein the context information includes a plurality of path parameters associated with different measurement instances. Here, the different measurement instances may correspond to path parameters measured at different times and/or measured using different signals.

[0188] The processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to determine a modification of one or more path characteristics based at least in part on the context information. Here, the path characteristics may be defined by the path parameters, such that the modification is detected when there is a change in measured path parameter or a change that exceeds a threshold amount. For example, detection of the modification may be associated with a time instance, such that the detection is based on the sensing measurement of a present time instance and the available context information (e.g., including stored values corresponding to one or more previous measurements). The processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to transmit a report based at least in part on the modification.

[0189] In some implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to determine that the determined path is a tracking path to be monitored over a period of time. In such implementations, the determination that the determined path may be based at least in part on: A) an assessment that one or more path parameters satisfies at least one criterion, or B) a reception of an indication that the determined path is the tracking path.

[0190] In certain implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to store the context information in response to the determination that the determined path is the tracking path. In certain implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to receive, from the second device, the indication that the determined path is the tracking path in response to the report.

[0191] In certain implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to transmit, to the second device, an indication that the determined path is the tracking path based at least in part on the assessment that one or more path parameters satisfies the at least one criterion. In such implementations, the configuration for sensing measurement may include the at least one criterion. [0192] In some implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to determine that the determined path is a candidate path for tracking over a period of time. In such implementations, the determination that the determined path is based at least in part on an assessment that one or more path parameters satisfies at least one criterion. In certain implementations, the configuration for sensing measurement includes the at least one criterion and the report includes an indication that the determined path is the candidate path. In certain implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to store the context information based at least in part upon the determination that the determined path is the candidate path.

[0193] In some implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to: A) start a timer in response to a transmission of the report (e.g., of a path detected with delay /angle of [X, Y] or a report with indication of a path being a candidate path); B) keep the context information in response to receiving, from the second device, an indication that the determined path is a tracking path to be monitored over a period of time; C) release the context information associated with the determined path in response to an expiration of the timer without receiving the indication that the determined path is the tracking path; and D) release the context information associated with the determined path in response to a received path power (e.g., RSRPP related to any RS or applicable sensing signal) not satisfying a threshold value for at least a predetermined time duration. Note that timer expiration time may be preconfigured or configured by the SensMF, may differ for a path determined as a candidate path or a path report, and/or may differ depending on the cycle/period over which the sensing signals are transmitted (e.g., 3 period of a sensing signal transmission).

[0194] In some implementations, the configuration for sensing measurement and reporting includes one or more of: A) a received path power threshold for measurement instances of at least a minimum measurement time (e.g., across a minimum of N measurements of the sensing signals within 10 secs); B) an object of interest or a reflector of interest; C) a range of interest for one or more path parameters; D) an indication of a tracking path; E) assistance information for detecting the tracking path; F) an indication of one or more additional signal transmissions associated with a respective path (e.g., indication of CSI-RS-1 and an PRS-2 and SSB-3 illuminating the same AoD/ZoD corresponding to a detected path ID, with a minimum transmission/radiation power along the AoD/ZoD of the detected path); G) a radiation pattern (e.g., including beam direction, beamwidth, transmission power, etc.) associated with the one or more sensing signals; H) azimuth-of-departure information or zenith-of-departure information, of both, associated with the respective path; I) a transmit point location relative to a reception point associated with the respective path; J) an indication that the respective path is a direct path; K) an indication that the respective path is a first order reflection path; L) a relative reflector location associated with the respective path; M) an absolute reflector location associated with the respective path; N) at least one criteria for determining that the respective path is the tracking path; O) at least one criteria for determining that the respective path is a candidate for tracking; P) a set of path parameters to store in the context information; Q) a time to store the context information; or a combination thereof.

[0195] In certain implementations, the configuration for sensing measurement and reporting further indicates a plurality of times to store the context information associated with the determined path. In such implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to select a respective time to store the context information based on a sensing measurement satisfying a threshold.

[0196] In some implementations, the context information associated with the determined path includes one or more of: A) a path ID (e.g., one or multiple path IDs); B) a path group ID; C) a first set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different sensing signals; D) a second set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different time instances; E) one or more time stamps associated with the first set of measurement values or the second set of measurement values; F) one or more time stamps associated with a detected path modification (e.g., a time of detected blockage, or RSRPP drop, or doppler change, etc.); G) a set of one or more prior detected path modifications; H) a set of sensor measurements from one or more sensors associated with the radio node (e.g., the one or more sensors including at least one of a camera, a photosensor, a motion sensor); I) a set of spatial filters associated with the determined path; J) a set of beams associated with the determined path; K) one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value (e .g ., of a path parameter close in doppler, delay, angle, vibration, and/or ToA to the determined path); L) a geometrical relation to another path; M) a transmit point location associated with the determined path (e.g., as indicated by the SensMF or detected by the sensing Rx node); N) one or more transmission characteristics of the determined path (e.g., AoD/ZoD, TP mobility pattern, etc. associated with the determined path); O) a reflector entity associated with the determined path (e.g., a RIS, or an object ID associated with a reflection during the propagation path); or a combination thereof.

[0197] In some implementations, the report includes one or more of: A) a path description; B) a set of measurement values associated with the determined path; C) the context information associated with the determined path; D) an indication that the determined path is a tracking path; E) an indication that the determined path is a candidate for tracking; F) an indication of the modification of the context information associated with the determined path; or a combination thereof.

[0198] In some implementations, the radio node includes a UE or a base station. In certain implementations, the second device includes a sensing measurement function in a mobile communication network.

[0199] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the UE 600 to perform one or more of the SensMF functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 coupled with the memory 1304 may be configured to, capable of, or operable to cause the UE 600 to transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, where the context information includes a plurality of path parameters associated with different measurement instances.

[0200] In some implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to transmit an indication that the identified path is a tracking path to be monitored over a period of time. In certain implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to transmit the indication that the identified path is the tracking path in response to the report. [0201] In some implementations, the report includes an indication that the identified path is a tracking path to be monitored over a period of time, and wherein the configuration for sensing measurement includes at least one criterion for assessing one or more path parameters to determine whether a respective path is the tracking path.

[0202] In some implementations, the report includes an indication that the identified path is a candidate path for tracking over a period of time, and wherein the configuration for sensing measurement includes at least one criterion for assessing one or more path parameters to determine whether a respective path is the candidate path.

[0203] In some implementations, the configuration for sensing measurement and reporting includes one or more of: A) a received path power threshold for measurement instances of at least a minimum measurement time (e.g., across a minimum of N measurements of the sensing signals within 10 secs); B) an object of interest or a reflector of interest; C) a range of interest for one or more path parameters; D) an indication of a tracking path; E) assistance information for detecting the tracking path; F) an indication of one or more additional signal transmissions associated with a respective path (e.g., indication of CSI-RS-1 and an PRS-2 and SSB-3 illuminating the same AoD/ZoD corresponding to a detected path ID, with a minimum transmission/radiation power along the AoD/ZoD of the detected path); G) a radiation pattern (e.g., including beam direction, beamwidth, transmission power, etc.) associated with the one or more sensing signals; H) azimuth-of-departure information or zenith-of-departure information, of both, associated with the respective path; I) a transmit point location relative to a reception point associated with the respective path; J) an indication that the respective path is a direct path; K) an indication that the respective path is a first order reflection path; L) a relative reflector location associated with the respective path; M) an absolute reflector location associated with the respective path; N) at least one criteria for determining that the respective path is the tracking path; O) at least one criteria for determining that the respective path is a candidate for tracking; P) a set of path parameters to store in the context information; Q) a time to store the context information; or a combination thereof.

[0204] In certain implementations, the configuration for sensing measurement and reporting further indicates a plurality of times to store the context information associated with the path. In such implementations, the processor 602 coupled with the memory 604 may be configured to, capable of, or operable to cause the UE 600 to select a respective time to store the context information based on a sensing measurement satisfying a threshold.

[0205] In some implementations, the context information associated with the path includes one or more of: A) a path ID (e.g., one or multiple path IDs); B) a path group ID; C) a first set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different sensing signals; D) a second set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different time instances; E) one or more time stamps associated with the first set of measurement values or the second set of measurement values; F) one or more time stamps associated with a detected path modification (e.g., a time of detected blockage, or RSRPP drop, or doppler change, etc.); G) a set of one or more prior detected path modifications; H) a set of sensor measurements from one or more sensors associated with a radio (i.e., sensing Rx) node (e.g., the one or more sensors including at least one of a camera, a photosensor, a motion sensor); I) a set of spatial filters associated with the path; J) a set of beams associated with the path; K) one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value (e.g., of a path parameter close in doppler, delay, angle, vibration, and/or ToA to the path); L) a geometrical relation to another path; M) a transmit point location associated with the path (e.g., as indicated by the SensMF or detected by the sensing Rx node); N) one or more transmission characteristics of the path (e.g., AoD/ZoD, TP mobility pattern, etc. associated with the path); O) a reflector entity associated with the path (e.g., a RIS, or an object ID associated with a reflection during the propagation path); or a combination thereof.

[0206] In some implementations, the report includes one or more of: A) a path description; B) a set of measurement values associated with the path; C) the context information associated with the path; D) an indication that the path is a tracking path; E) an indication that the path is a candidate for tracking; F) an indication of the modification of the context information associated with the path; or a combination thereof.

[0207] The controller 606 may manage input and output signals for the UE 600. The controller 606 may also manage peripherals not integrated into the UE 600. In some implementations, the controller 606 may utilize an operating system (OS) such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0208] In some implementations, the UE 600 may include at least one transceiver 608. In some other implementations, the UE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0209] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 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 610 may include at least one decoder for decoding/ processing the demodulated signal to receive the transmitted data.

[0210] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 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 612 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 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0211] Figure 7 illustrates an example of a processor 700 in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic -logic units (ALUs) 706. 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).

[0212] The processor 700 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 700) 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).

[0213] The controller 702 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 700 to cause the processor 700 to support various operations in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0214] The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction(s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of data within the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 700.

[0215] The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700). In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700).

[0216] The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 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 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 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.

[0217] The one or more ALUs 706 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700). In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700). One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 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 706 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

[0218] In various implementations, the processor 700 may support various functions (e.g., operations, signaling) of a radio node (e.g., a sensing Tx node and/or a sensing Rx node), in accordance with examples as disclosed herein. For example, the controller 702 coupled with the memory 704 may be configured to, capable of, or operable to cause the processor 700 may be configured to receive a configuration for sensing measurement and reporting, based on one or more sensing signals; determine a path based at least in part on a reception and measurement of the one or more sensing signals; store context information associated with the path, the context information including a plurality of path parameters associated with different measurement instances; determine a modification of one or more path characteristics, based at least in part on the context information; and transmit a report based at least in part on the modification. . In some implementations, the radio node includes, or is included in, a UE or a base station. In certain implementations, the second node includes, or is included in, a sensing measurement function in a mobile communication network.

[0219] Additionally, the controller 702 coupled with the memory 704 may be configured to, capable of, or operable to cause the processor 700 to perform one or more functions (e.g., operations, signaling) of the UE as described herein. Alternatively, the controller 702 coupled with the memory 704 may be configured to, capable of, or operable to cause the processor 700 to perform one or more functions (e.g., operations, signaling) of the base station as described herein.

[0220] In various implementations, the processor 700 may support various functions (e.g., operations, signaling) of the SensMF (e.g., a core NF, or NE), in accordance with examples as disclosed herein. For example, the controller 702 coupled with the memory 704 may be configured to, capable of, or operable to cause the processor 700 to transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, the context information including a plurality of path parameters associated with different measurement instances. Additionally, the controller 702 coupled with the memory 704 may be configured to, capable of, or operable to cause the processor 700 to perform one or more functions (e.g., operations, signaling) of the SensMF as described herein.

[0221] Figure 8 illustrates an example of a NE 800 in accordance with aspects of the present disclosure. The NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, 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.

[0222] The processor 802, the memory 804, the controller 806, or the transceiver 808, 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.

[0223] The processor 802 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 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the NE 800 to perform various functions of the present disclosure.

[0224] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the NE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 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. [0225] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the NE 800 to perform various functions (e.g., operations, signaling) described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). In some implementations, the processor 802 may include multiple processors and the memory 804 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 800 as disclosed herein.

[0226] For example, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to receive, from a second device, a configuration for sensing measurement and reporting, based on one or more sensing signals. In certain implementations, the configuration further indicates information for the reception of the one or more sensing signals of one or plurality of time instance. The processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to determine a path based at least in part on a reception and measurement of the one or more sensing signals.

[0227] The processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to store context information associated with the determined path, wherein the context information includes a plurality of path parameters associated with different measurement instances. Here, the different measurement instances may correspond to path parameters measured at different times and/or measured using different signals.

[0228] The processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to determine a modification of one or more path characteristics based at least in part on the context information. Here, the path characteristics may be defined by the path parameters, such that the modification is detected when there is a change in measured path parameter or a change that exceeds a threshold amount. For example, detection of the modification may be associated with a time instance, such that the detection is based on the sensing measurement of a present time instance and the available context information (e.g., including stored values corresponding to one or more previous measurements). The processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to transmit a report based at least in part on the modification.

[0229] In some implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to determine that the determined path is a tracking path to be monitored over a period of time. In such implementations, the determination that the determined path may be based at least in part on: A) an assessment that one or more path parameters satisfies at least one criterion, or B) a reception of an indication that the determined path is the tracking path.

[0230] In certain implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to store the context information in response to the determination that the determined path is the tracking path. In certain implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to receive, from the second device, the indication that the determined path is the tracking path in response to the report.

[0231] In certain implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to transmit, to the second device, an indication that the determined path is the tracking path based at least in part on the assessment that one or more path parameters satisfies the at least one criterion. In such implementations, the configuration for sensing measurement may include the at least one criterion.

[0232] In some implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to determine that the determined path is a candidate path for tracking over a period of time. In such implementations, the determination that the determined path is based at least in part on an assessment that one or more path parameters satisfies at least one criterion. In certain implementations, the configuration for sensing measurement includes the at least one criterion and the report includes an indication that the determined path is the candidate path. In certain implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to store the context information based at least in part upon the determination that the determined path is the candidate path. [0233] In some implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to: A) start a timer in response to a transmission of the report (e.g., of a path detected with delay /angle of [X, Y] or a report with indication of a respective path being a candidate path); B) keep the context information in response to receiving, from the second device, an indication that the determined path is a tracking path to be monitored over a period of time; C) release the context information associated with the determined path in response to an expiration of the timer without receiving the indication that the determined path is the tracking path; and D) release the context information associated with the determined path in response to a received path power (e.g., RSRPP related to any RS or applicable sensing signal) not satisfying a threshold value for at least a predetermined time duration. Note that timer expiration time may be preconfigured or configured by the SensMF, may differ for a path determined as a candidate path or a path report, and/or may differ depending on the cycle/period over which the sensing signals are transmitted (e.g., 3 period of a sensing signal transmission).

[0234] In some implementations, the configuration for sensing measurement and reporting includes one or more of: A) a received path power threshold for measurement instances of at least a minimum measurement time (e.g., across a minimum of N measurements of the sensing signals within 10 secs); B) an object of interest or a reflector of interest; C) a range of interest for one or more path parameters; D) an indication of a tracking path; E) assistance information for detecting the tracking path; F) an indication of one or more additional signal transmissions associated with a respective path (e.g., indication of CSI-RS-1 and an PRS-2 and SSB-3 illuminating the same AoD/ZoD corresponding to a detected path ID, with a minimum transmission/radiation power along the AoD/ZoD of the detected path); G) a radiation pattern (e.g., including beam direction, beamwidth, transmission power, etc.) associated with the one or more sensing signals; H) azimuth-of-departure information or zenith-of-departure information, of both, associated with the respective path; I) a transmit point location relative to a reception point associated with the respective path; J) an indication that the respective path is a direct path; K) an indication that the respective path is a first order reflection path; L) a relative reflector location associated with the respective path; M) an absolute reflector location associated with the respective path; N) at least one criteria for determining that the respective path is the tracking path; O) at least one criteria for determining that the respective path is a candidate for tracking; P) a set of path parameters to store in the context information; Q) a time to store the context information; or a combination thereof.

[0235] In certain implementations, the configuration for sensing measurement and reporting further indicates a plurality of times to store the context information associated with the determined path. In such implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to select a respective time to store the context information based on a sensing measurement satisfying a threshold.

[0236] In some implementations, the context information associated with the determined path includes one or more of: A) a path ID (e.g., one or multiple path IDs); B) a path group ID; C) a first set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different sensing signals; D) a second set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different time instances; E) one or more time stamps associated with the first set of measurement values or the second set of measurement values; F) one or more time stamps associated with a detected path modification (e.g., a time of detected blockage, or RSRPP drop, or doppler change, etc.); G) a set of one or more prior detected path modifications; H) a set of sensor measurements from one or more sensors associated with the radio node (e.g., the one or more sensors including at least one of a camera, a photosensor, a motion sensor); I) a set of spatial filters associated with the determined path; J) a set of beams associated with the determined path; K) one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value (e .g ., of a path parameter close in doppler, delay, angle, vibration, and/or ToA to the determined path); L) a geometrical relation to another path; M) a transmit point location associated with the determined path (e.g., as indicated by the SensMF or detected by the sensing Rx node); N) one or more transmission characteristics of the determined path (e.g., AoD/ZoD, TP mobility pattern, etc. associated with the determined path); O) a reflector entity associated with the determined path (e.g., a RIS, or an object ID associated with a reflection during the propagation path); or a combination thereof.

[0237] In some implementations, the report includes one or more of: A) a path description; B) a set of measurement values associated with the determined path; C) the context information associated with the determined path; D) an indication that the determined path is a tracking path; E) an indication that the determined path is a candidate for tracking; F) an indication of the modification of the context information associated with the determined path; or a combination thereof.

[0238] In some implementations, the radio node includes a UE or a base station. In certain implementations, the second device includes a sensing measurement function in a mobile communication network.

[0239] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the NE 800 to perform one or more SensMF functions as described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, the context information includes a plurality of path parameters associated with different measurement instances.

[0240] In some implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to transmit an indication that the identified path is a tracking path to be monitored over a period of time. In certain implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to transmit the indication that the identified path is the tracking path in response to the report.

[0241] In some implementations, the report includes an indication that the identified path is a tracking path to be monitored over a period of time, and wherein the configuration for sensing measurement includes at least one criterion for assessing one or more path parameters to determine whether a respective path is the tracking path.

[0242] In some implementations, the report includes an indication that the identified path is a candidate path for tracking over a period of time, and wherein the configuration for sensing measurement includes at least one criterion for assessing one or more path parameters to determine whether a respective path is the candidate path. [0243] In some implementations, the configuration for sensing measurement and reporting includes one or more of: A) a received path power threshold for measurement instances of at least a minimum measurement time (e.g., across a minimum of N measurements of the sensing signals within 10 secs); B) an object of interest or a reflector of interest; C) a range of interest for one or more path parameters; D) an indication of a tracking path; E) assistance information for detecting the tracking path; F) an indication of one or more additional signal transmissions associated with a respective path (e.g., indication of CSI-RS-1 and an PRS-2 and SSB-3 illuminating the same AoD/ZoD corresponding to a detected path ID, with a minimum transmission/radiation power along the AoD/ZoD of the detected path); G) a radiation pattern (e.g., including beam direction, beamwidth, transmission power, etc.) associated with the one or more sensing signals; H) azimuth-of-departure information or zenith-of-departure information, of both, associated with the respective path; I) a transmit point location relative to a reception point associated with the respective path; J) an indication that the respective path is a direct path; K) an indication that the respective path is a first order reflection path; L) a relative reflector location associated with the respective path; M) an absolute reflector location associated with the respective path; N) at least one criteria for determining that the respective path is the tracking path; O) at least one criteria for determining that the respective path is a candidate for tracking; P) a set of path parameters to store in the context information; Q) a time to store the context information; or a combination thereof.

[0244] In certain implementations, the configuration for sensing measurement and reporting further indicates a plurality of times to store the context information associated with the path. In such implementations, the processor 802 coupled with the memory 804 may be configured to, capable of, or operable to cause the NE 800 to select a respective time to store the context information based on a sensing measurement satisfying a threshold.

[0245] In some implementations, the context information associated with the path includes one or more of: A) a path ID (e.g., one or multiple path IDs); B) a path group ID; C) a first set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different sensing signals; D) a second set of measurement values (e.g., power, RSRPP, AoA/ZoA, ToA, channel or carrier phase, doppler shift, vibration, etc.) associated with different time instances; E) one or more time stamps associated with the first set of measurement values or the second set of measurement values; F) one or more time stamps associated with a detected path modification (e.g., a time of detected blockage, or RSRPP drop, or doppler change, etc.); G) a set of one or more prior detected path modifications; H) a set of sensor measurements from one or more sensors associated with a radio node (e.g., the one or more sensors including at least one of a camera, a photosensor, a motion sensor); I) a set of spatial filters associated with the path; J) a set of beams associated with the path; K) one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies athreshold value (e.g., of a path parameter close in doppler, delay, angle, vibration, and/or ToA to the path); L) a geometrical relation to another path; M) a transmit point location associated with the path (e.g., as indicated by the SensMF or detected by the sensing Rx node); N) one or more transmission characteristics of the path (e.g., AoD/ZoD, TP mobility pattern, etc. associated with the path); O) a reflector entity associated with the path (e.g., a RIS, or an object ID associated with a reflection during the propagation path); or a combination thereof.

[0246] In some implementations, the report includes one or more of: A) a path description; B) a set of measurement values associated with the path; C) the context information associated with the path; D) an indication that the path is a tracking path; E) an indication that the path is a candidate for tracking; F) an indication of the modification of the context information associated with the path; or a combination thereof.

[0247] The controller 806 may manage input and output signals for the NE 800. The controller 806 may also manage peripherals not integrated into the NE 800. In some implementations, the controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.

[0248] In some implementations, the NE 800 may include at least one transceiver 808. In some other implementations, the NE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0249] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 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 810 may include at least one decoder for decoding/ processing the demodulated signal to receive the transmitted data.

[0250] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 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 812 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 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0251] In some embodiments, the SensMF further maintains a context associated with a path and/or associated with a group of paths and/or associated with a sensing target object and/or associated with a sensing target area of interest, wherein the context includes one or multiple paths or one or multiple path groups initiating from a sensing Tx node and terminating at a sensing Rx node, further including: Reflection point of the paths, number of reflections for the paths, the one or multiple Tx beams at the sensing Tx node and the one or multipe beams at the sensing Rx node, as one or multiple beam pairs, for which the path has been observed/measured and/or the observed path/channel has been stored/known by the sensing Rx node [e.g., the SensMF stores the information that for transmission/reception of a sensing signal via beam q of the sensing Tx node and beam p of the sensing Rx node the associated paths to margin of interest of AoA/ZoA at the sensing Rx node has been stored/known by the sensing Rx node], information time stamp and/or validity time (e.g., a time duration for which the information is still stored/valid at the sensing Rx node), all or subset of the context information of the sensing Rx node (e.g., as described above) of one or multiple sensing Rx nodes, for the paths associated with an area/reflector of interest. [0252] In some embodiments, when the SensMF (e.g., SF residing in the core network or a controller entity residing in the RAN) of a sensing task (e.g., associated with a target being tracked and associated with one or more tracking paths of one or more sensing Rx nodes) needs to be changed (e.g., as it may no longer support the requested sensing operation or the target has moved to an area outside of the coverage of the SensMF), then the context information stored at the SensMF of the sensing target and/or the paths associated with the sensing target of one or multiple sensing Rx nodes is further transferred to a new SensMF determined to act as a new SensMF node for the sensing operation of the moving target.

[0253] In some embodiments, any of the configurations (of a sensing signal, a sensing transmission, sensing reception, detection and measurement) and/or indications and/or reporting information elements between a sensing Tx/Rx node and the SensMF or a subset thereof may be: A) received by the sensing Rx nodes, B) transmitted by the sensing Rx nodes, C) received by the sensing Tx nodes, D) transmitted by the sensing Tx nodes, E) transmitted and/or received by the SensMF node, or any combination thereof,

[0254] In some such embodiments, where the sensing Rx and/or the sensing Tx node is a UE, the configurations and/or indications and/or reporting information elements may be communicated via the UL, DL or SL physical data and/or control channels defined within the communication network, e.g., NR physical broadcast channel (PBCH), PDSCH, PDCCH, PUSCH, PUCCH, PSBCH, PSCCH, PSSCH, via a higher layer (MAC control element (MAC-CE) or RRC) signaling.

[0255] In some such embodiments, where the sensing Tx and/or the sensing Rx node is a UE, the configurations and/or indications and/or reporting information elements may be communicated via a logical interface between the SF and the Sensing nodes, e.g., as part of the LTE positioning protocol (LPP) or as modified/enhanced LPP message framework for sensing or as an interface defined for sensing message exchanges over the N 1 interface between the SF and a UE.

[0256] In some such embodiments, where the sensing Rx and/or the sensing Tx node is a TRP of RAN and the SensMF is a core network function (SF, LMF, etc.), the configurations and/or indications and/or reporting information elements may be communicated via a logical interface between the SensMF and the Sensing nodes, as part of the NR positioning protocol A (NRPPa) (or modified/enhanced NRPPa message framework for sensing) or as an interface defined over the next-generation application protocol (NGAP) interface.

[0257] In some such embodiments, where the sensing Rx and/or the sensing Tx node is a the SensMF is a serving gNB of a sensing task and the sensing node is a UE or a TRP of RAN, the configurations and/or indications and/or reporting information elements may be communicated via a logical interface between the SensMF and the Sensing nodes. In some examples, the interface utilizes (at least in part) the X2 interface between the associated gNB of the sensing node and the serving gNB of the sensing task.

[0258] In some embodiments, the sensing signal may comprise one or more of: physical data/control channels (e.g., in the DL, UL and/or SL direction); reference signals (e.g., demodulation reference signal (DMRS), PRS, SRS, sensing-dedicated RS, CSI-RS, phase tracking reference signal (PTRS), etc.) transmitted in the DL/UL/SL directions and according to the corresponding DL/UL/SL frame, or transmitted in a TRP-to-TRP directions (i.e., different than the DL/UL/SL directions), and may be transmitted/received according to the DL frame of the transmitting TRP, UL frame of the receiving TRP or combination thereof.

[0259] Figure 9 depicts one embodiment of a method 900 in accordance with aspects of the present disclosure. In various embodiments, the operations of the method 900 may be implemented by a radio node, such as the UE or NE, as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions. In other implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0260] At step 902, the method 900 may include receiving, from a second device, a configuration for sensing measurement and reporting, based on one or more sensing signals. The operations of step 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of step 902 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 902 may be performed by aNE, as described with reference to Figure 8. [0261] At step 904, the method 900 may include determining a path based at least in part on a reception and measurement of the one or more sensing signals. The operations of step 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of step 904 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 904 may be performed by a NE, as described with reference to Figure 8.

[0262] At step 906, the method 900 may include storing context information associated with the path, where the context information includes a plurality of path parameters associated with different measurement instances. The operations of step 906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of step 906 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 906 may be performed by a NE, as described with reference to Figure 8.

[0263] At step 908, the method 900 may include determining a modification of one or more path characteristics based at least in part on the context information. The operations of step 908 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of step 908 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 908 may be performed by a NE, as described with reference to Figure 8.

[0264] At step 910, the method 900 may include transmitting a report based at least in part on the modification. The operations of step 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of step 910 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 910 may be performed by a NE, as described with reference to Figure 8.

[0265] It should be noted that the method 900 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.

[0266] Figure 10 depicts one embodiment of amethod 1000 in accordance with aspects of the present disclosure. In various embodiments, the operations of the method 1000 may be implemented by a SensMF, such as the UE or NE, as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions. In other implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0267] At step 1002, the method 1000 may include transmitting a configuration for sensing measurement and reporting, based on one or more sensing signals. The operations of step 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1002 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 1002 may be performed by a NE, as described with reference to Figure 8.

[0268] At step 1004, the method 1000 may include receiving a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, where the context information includes a plurality of path parameters associated with different measurement instances. The operations of step 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1004 may be performed by a UE, as described with reference to Figure 6. In other implementations, aspects of the operations of step 1004 may be performed by a NE, as described with reference to Figure 8.

[0269] It should be noted that the method 1000 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.

[0270] 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

CLAIMS What is claimed is:

1. A radio node for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the radio node to: receive, from a second device, a configuration for sensing measurement and reporting, based on one or more sensing signals; determine a path based at least in part on a reception and measurement of the one or more sensing signals; store context information associated with the determined path, wherein the context information comprises a plurality of path parameters associated with different measurement instances; determine a modification of one or more path characteristics based at least in part on the context information; and transmit a report based at least in part on the modification.

2. The radio node of claim 1, wherein the at least one processor is configured to cause the radio node to determine that the determined path is a tracking path to be monitored over a period of time, wherein a determination that the determined path is based at least in part on: an assessment that one or more path parameters satisfies at least one criterion, or a reception of an indication that the determined path is the tracking path.

3. The radio node of claim 2, wherein the at least one processor is configured to cause the radio node to: transmit, to the second device, an indication that the determined path is the tracking path based at least in part on the assessment that one or more path parameters satisfies the at least one criterion, wherein the configuration for sensing measurement comprises the at least one criterion.

4. The radio node of claim 2, wherein the at least one processor is configured to cause the radio node to receive, from the second device, the indication that the determined path is the tracking path in response to the report.

5. The radio node of claim 2, wherein the at least one processor is configured to cause the radio node to store the context information in response to the determination that the determined path is the tracking path.

6. The radio node of claim 1, wherein the at least one processor is configured to cause the radio node to: start a timer in response to a transmission of the report; keep the context information in response to receiving, from the second device, an indication that the determined path is a tracking path to be monitored over a period of time; release the context information associated with the determined path in response to an expiration of the timer without receiving the indication that the determined path is the tracking path; and release the context information associated with the determined path in response to a received path power not satisfying a threshold value for at least a predetermined time duration.

7. The radio node of claim 1, wherein the configuration for sensing measurement and reporting comprises one or more of: a received path power threshold for measurement instances of at least a minimum measurement time; an object of interest or a reflector of interest; a range of interest for one or more path parameters; an indication of a tracking path; assistance information for detecting the tracking path; an indication of one or more additional signal transmissions associated with a respective path; a radiation pattern associated with the one or more sensing signals; azimuth-of-departure information or zenith-of-departure information, of both, associated with the respective path; a transmit point location relative to a reception point associated with the respective path; an indication that the respective path is a direct path; an indication that the respective path is a first order reflection path; a relative reflector location associated with the respective path; an absolute reflector location associated with the respective path; at least one criteria for determining that the respective path is the tracking path; at least one criteria for determining that the respective path is a candidate for tracking; a set of path parameters to store in the context information; a time to store the context information; or a combination thereof.

8. The radio node of claim 7, wherein the configuration for sensing measurement and reporting further indicates a plurality of times to store the context information associated with the determined path, and wherein the at least one processor is configured to cause the radio node to select a respective time to store the context information based on a sensing measurement satisfying a threshold.

9. The radio node of claim 1, wherein the context information associated with the determined path comprises one or more of: a path identifier (ID); a path group ID; a first set of measurement values associated with different sensing signals; a second set of measurement values associated with different time instances; one or more time stamps associated with the first set of measurement values or the second set of measurement values; one or more time stamps associated with a detected path modification; a set of one or more prior detected path modifications; a set of sensor measurements from one or more sensors associated with the radio node, wherein the one or more sensors comprise at least one of a camera, a photosensor, a motion sensor; a set of spatial filters associated with the determined path; a set of beams associated with the determined path; one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value; a geometrical relation to another path; a transmit point location associated with the determined path; one or more transmission characteristics of the determined path; a reflector entity associated with the determined path; or a combination thereof.

10. The radio node of claim 1, wherein the report comprises one or more of: a path description; a set of measurement values associated with the determined path; the context information associated with the determined path; an indication that the determined path is a tracking path; an indication that the determined path is a candidate for tracking; an indication of the modification of the context information associated with the determined path; or a combination thereof.

11. The radio node of claim 1, wherein the radio node comprises a user equipment (UE) or a base station, and wherein the second device comprises a sensing measurement function in a mobile communication network.

12. A method performed by a radio node, the method comprising: receiving, from a second node, a configuration for sensing measurement and reporting, based on one or more sensing signals; determining a path based at least in part on a reception and measurement of the one or more sensing signals; storing context information associated with the path, wherein the context information comprises a plurality of path parameters associated with different measurement instances; determining a modification of one or more path characteristics based at least in part on the context information; and transmitting a report based at least in part on the modification.

13. A network entity storing code for a sensing measurement function, comprising: at least one memory storing the code; and at least one processor coupled with the at least one memory and configured to execute the code to cause the sensing measurement function to: transmit a configuration for sensing measurement and reporting, based on one or more sensing signals; and receive a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, wherein the context information comprises a plurality of path parameters associated with different measurement instances.

14. The network entity of claim 13, wherein the at least one processor is configured to execute the code to cause the sensing measurement function to transmit an indication that the path is a tracking path to be monitored over a period of time.

15. The network entity of claim 14, wherein the at least one processor is configured to execute the code to cause the sensing measurement function to transmit the indication that the path is the tracking path in response to the report.

16. The network entity of claim 13, wherein the report comprises an indication that the path is a tracking path to be monitored over a period of time, and wherein the configuration for sensing measurement comprises at least one criterion for assessing one or more path parameters to determine whether a respective path is the tracking path.

17. The network entity of claim 13, wherein the report comprises an indication that the path is a candidate path for tracking over a period of time, and wherein the configuration for sensing measurement comprises at least one criterion for assessing one or more path parameters to determine whether a respective path is the candidate path.

18. The network entity of claim 13, wherein the context information associated with the path comprises one or more of: a path identifier (ID); a path group ID; a first set of measurement values associated with different sensing signals; a second set of measurement values associated with different time instances; one or more time stamps associated with the first set of measurement values or the second set of measurement values; one or more time stamps associated with a detected path modification; a set of one or more prior detected path modifications; a set of sensor measurements from one or more sensors associated with a radio node, wherein the one or more sensors comprise at least one of a camera, a photosensor, a motion sensor; a set of spatial filters associated with the path; a set of beams associated with the path; one or more related paths sharing at least one path parameter or having a difference in path parameter that satisfies a threshold value; a geometrical relation to another path; a transmit point location associated with the path; one or more transmission characteristics of the path; a reflector entity associated with the path; or a combination thereof.

19. The network entity of claim 13, wherein the report comprises one or more of: a path description; a set of measurement values associated with the path; the context information associated with the path; an indication that the path is a tracking path; an indication that the path is a candidate for tracking; an indication of the modification of the context information associated with the path; or a combination thereof.

20. A method performed by a sensing measurement function, the method comprising: transmitting a configuration for sensing measurement and reporting, based on one or more sensing signals; and receiving a report based at least in part on a modification of context information associated with a path identified based at least in part on a reception and measurement of the one or more sensing signals, wherein the context information comprises a plurality of path parameters associated with different measurement instances.