Radio link management enhancements for integrated sensing and communication

Abstract

Disclosed are techniques for sensing. In an aspect, a sensing node may detect one or more failure events based on one or more sensing-specific parameters. The sensing node may identify a consistent failure event based at least on the one or more detected failure events. The sensing node may perform at least one action in response to identifying the consistent failure event.

Description

Qualcomm Ref. No.2403178WO 1 RADIO LINK MANAGEMENT ENHANCEMENTS FOR INTEGRATED SENSING AND COMMUNICATION TECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless technologies. BACKGROUND

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), radio frequency (RF) sensing, and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployments for 5G, enable highly accurate 5G-based sensing and positioning. SUMMARY

[0004] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview 1 QC2403178WOQualcomm Ref. No.2403178WO 2 relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0005] In an aspect, a method of wireless communication at a sensing node includes detecting one or more failure events based on one or more sensing-specific parameters; based at least on the one or more detected failure events, identifying a consistent failure event; and in response to identifying the consistent failure event, performing at least one action.

[0006] In an aspect, a method of communication at a network entity comprising includes receiving an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configuring the first sensing node to perform one or more actions in response to the received indication.

[0007] In an aspect, a sensing node includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to detect one or more failure events based on one or more sensing-specific parameters; identify, based at least on the one or more detected failure events, a consistent failure event; and in response to identifying the consistent failure event, perform at least one action.

[0008] In an aspect, a network entity includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to receive, via the one or more transceivers, an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configure the first sensing node to perform one or more actions in response to the received indication. 2 QC2403178WOQualcomm Ref. No.2403178WO

[0009] In an aspect, a sensing node includes means for detecting one or more failure events based on one or more sensing-specific parameters; means for identifying a consistent failure event based at least on the one or more detected failure events; and means for performing at least one action in response to identifying the consistent failure event.

[0010] In an aspect, a network entity includes means for receiving an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and means for configuring the first sensing node to perform one or more actions in response to the received indication.

[0011] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a sensing node, cause the sensing node to: detect one or more failure events based on one or more sensing-specific parameters; identify a consistent failure event based at least on the one or more detected failure events; and in response to identifying the consistent failure event, perform at least one action.

[0012] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to: receive an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configure the first sensing node to perform one or more actions in response to the received indication.

[0013] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0015] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0016] FIGS.2A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure. 3 QC2403178WOQualcomm Ref. No.2403178WO 4

[0017] FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0018] FIGS.4A and 4B illustrate different types of wireless sensing, according to aspects of the disclosure.

[0019] FIG.5 illustrates an example call flow for a New Radio (NR)-based sensing procedure in which the network configures the sensing parameters, according to aspects of the disclosure.

[0020] FIG. 6 is a diagram illustrating an example frame structure, according to aspects of the disclosure.

[0021] FIG. 7 is a diagram illustrating an example single stage sensing scenario, according to aspects of the disclosure.

[0022] FIG. 8 is a diagram illustrating an example two stage sensing scenario, according to aspects of the disclosure.

[0023] FIG. 9 is a diagram illustrating an example three stage sensing scenario, according to aspects of the disclosure.

[0024] FIG. 10 illustrates an example sensing management process, according to aspects of the disclosure.

[0025] FIG. 11 illustrates an example timeline of failure event detection for a set of example sensing-specific parameters, according to aspects of the disclosure.

[0026] FIGS. 12 and 13 illustrate example methods of sensing, according to aspects of the disclosure. DETAILED DESCRIPTION

[0027] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.

[0028] Various aspects relate generally to sensing radio link management (S-RLM) procedures. Some aspects more specifically relate to failure detection and mitigation in sensing systems. In some examples, a sensing node detects failure events based on one or more 4 QC2403178WOQualcomm Ref. No.2403178WO 5 sensing-specific parameters, which provide a mechanism for determination of whether sensing measurements indicate problems that may need to be mitigated. In some aspects, a failure event is identified based on one or more sensing metrics, according to sensing- specific parameters. A consistent failure event is triggered based on one or more failure events, and in response the sensing node may take one or more actions; for example, according to configuration / instructions from a network entity.

[0029] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by performing one or more actions in response to failure event(s), the described techniques can be used for improved sensing target detection and tracking performance. Sensing- specific parameters can be used to tailor the failure detection and mitigating action(s) to the circumstances and failure types. For example, sensing-specific parameters for less sensitive sensing applications such as adaptive cruise control may be less sensitive (e.g., less sensitive thresholds, counters, timers, etc.) so that resource allocation is not unduly impacted. For higher sensitivity applications such as collision avoidance, failure detection may be prioritized by using more sensitive thresholds, timers, and counters despite a greater impact on network resource allocation and associated overhead. The techniques may improve sensing performance in challenging circumstances, such as the proximity of interfering transmitters, multipath clutter, and / or other causes of link quality degradation.

[0030] The words “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

[0031] Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc. 5 QC2403178WOQualcomm Ref. No.2403178WO

[0032] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

[0033] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on. 6 QC2403178WOQualcomm Ref. No.2403178WO 7

[0034] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink / reverse or downlink / forward traffic channel.

[0035] The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station. 7 QC2403178WOQualcomm Ref. No.2403178WO 8

[0036] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0037] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0038] FIG.1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0039] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. A location server 172 may be integrated with a base station 102. A UE 104 may communicate with a location server 172 directly or indirectly. For example, 8 QC2403178WOQualcomm Ref. No.2403178WO a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104. A UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on. For signaling purposes, communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.

[0040] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0041] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because 9 QC2403178WOQualcomm Ref. No.2403178WO a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0042] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' (labeled “SC” for “small cell”) may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

[0043] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).

[0044] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

[0045] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed 10 QC2403178WOQualcomm Ref. No.2403178WO frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MULTEFIRE®.

[0046] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0047] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the 11 QC2403178WOQualcomm Ref. No.2403178WO transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while canceling to suppress radiation in undesired directions.

[0048] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

[0049] In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to- interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.

[0050] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a QC2403178WOQualcomm Ref. No.2403178WO 13 transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0051] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0052] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION® as a “millimeter wave” band.

[0053] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz – 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), 13 QC2403178WOQualcomm Ref. No.2403178WO 14 and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0054] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0055] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably. 14 QC2403178WOQualcomm Ref. No.2403178WO 15

[0056] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0057] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and / or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0058] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink 15 QC2403178WOQualcomm Ref. No.2403178WO communications are carried out between SL-UEs without the involvement of a base station 102.

[0059] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.11x WLAN technologies generally referred to as “Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

[0060] Note that although FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160.

[0061] In the example of FIG.1, any of the illustrated UEs (shown in FIG.1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned 16 QC2403178WOQualcomm Ref. No.2403178WO 17 to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0062] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi- functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and / or the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0063] In an aspect, SVs 112 may additionally or alternatively be part of one or more non- terrestrial networks (NTNs). In an NTN, an SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.

[0064] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular 17 QC2403178WOQualcomm Ref. No.2403178WO connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on.

[0065] FIG.2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0066] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and / or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server). 18 QC2403178WOQualcomm Ref. No.2403178WO

[0067] FIG. 2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.

[0068] Functions of the UPF 262 include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, 19 QC2403178WOQualcomm Ref. No.2403178WO reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

[0069] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.

[0070] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and / or data like the transmission control protocol (TCP) and / or IP).

[0071] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. As such, in some cases, the third-party server 274 may be referred to as a location services (LCS) client or an external client. The third- party server 274 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software 20 QC2403178WOQualcomm Ref. No.2403178WO modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.

[0072] User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223, referred to as the “Xn-C” interface. One or more of gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface.

[0073] The functionality of a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. A gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. A gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “F1” interface. The physical (PHY) layer functionality of a gNB 222 is generally hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between a gNB-DU 228 and a gNB-RU 229 is referred to as the “Fx” interface. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.

[0074] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, 21 QC2403178WOQualcomm Ref. No.2403178WO a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP, cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0075] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0076] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0077] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a 22 QC2403178WOQualcomm Ref. No.2403178WO Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

[0078] Each of the units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0079] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit – User Plane (CU- UP)), control plane functionality (i.e., Central Unit – Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling. 23 QC2403178WOQualcomm Ref. No.2403178WO 24

[0080] The DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP®). In some aspects, the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280.

[0081] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0082] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 24 QC2403178WOQualcomm Ref. No.2403178WO 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an O1 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an O1 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0083] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an A1 interface) the Near- RT RIC 259. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259.

[0084] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. In some examples, the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).

[0085] FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and / or 25 QC2403178WOQualcomm Ref. No.2403178WO 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0086] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and / or the like. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0087] The UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from 26 QC2403178WOQualcomm Ref. No.2403178WO 27 transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest. The short- range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.

[0088] The UE 302 and the base station 304 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively. In some cases, the base station 304 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370. In other cases, the base station 304 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and / or other space vehicles.

[0089] The satellite signal receivers 332 and 372 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal receiver(s) 332 and 372 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite QC2403178WOQualcomm Ref. No.2403178WO System (QZSS) signals, etc. Where the satellite signal receiver(s) 332 and 372 are non- terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signal receiver(s) 332 and 372 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0090] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitter(s) 334 and 374 are NTN transmitters, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.

[0091] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ the one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may employ the one or more network transceivers 390 to communicate with one or more base station 304 over one or more wired or wireless 28 QC2403178WOQualcomm Ref. No.2403178WO 29 backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0092] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0093] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “a transceiver,” “at least one transceiver,” or “one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and a 29 QC2403178WOQualcomm Ref. No.2403178WO 30 base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0094] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 342, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the processors 342, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.

[0095] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include sensing component(s) 348, 388, and 398, respectively. The sensing component(s) 348, 388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the sensing component(s) 348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the sensing component(s) 348, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the sensing component(s) 348, which may be, for example, part of the one or more WWAN 30 QC2403178WOQualcomm Ref. No.2403178WO 31 transceivers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component. FIG.3B illustrates possible locations of the sensing component(s) 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG.3C illustrates possible locations of the sensing component(s) 398, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.

[0096] The UE 302 may include one or more sensors 344 coupled to the one or more processors 342 to provide means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal interface 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and / or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0097] In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0098] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block 31 QC2403178WOQualcomm Ref. No.2403178WO (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0099] The transmitter 354 and the receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission. 32 QC2403178WOQualcomm Ref. No.2403178WO 33

[0100] At the UE 302, the receiver 312 receives a signal through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 342. The transmitter 314 and the receiver 312 implement Layer-1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the one or more processors 342, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

[0101] In the downlink, the one or more processors 342 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The one or more processors 342 are also responsible for error detection.

[0102] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 342 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of 33 QC2403178WOQualcomm Ref. No.2403178WO 34 MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0103] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.

[0104] The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384.

[0105] In the uplink, the one or more processors 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection.

[0106] For convenience, the UE 302, the base station 304, and / or the network entity 306 are shown in FIGS.3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG.3A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and / or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or 34 QC2403178WOQualcomm Ref. No.2403178WO 35 may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal interface 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.

[0107] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 308, 382, and 392, respectively. In an aspect, the data buses 308, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 308, 382, and 392 may provide communication between them.

[0108] The components of FIGS.3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3A, 3B, and 3C may be implemented in one or more circuits such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processors 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the Sensing Component(s) 348, 388, and 398, etc. 35 QC2403178WOQualcomm Ref. No.2403178WO 36

[0109] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as Wi-Fi).

[0110] Wireless communication signals (e.g., radio frequency (RF) signals configured to carry orthogonal frequency division multiplexing (OFIGFDM) symbols in accordance with a wireless communications standard, such as LTE, NR, etc.) transmitted between a UE and a base station can be used for environment sensing (also referred to as “RF sensing” or “radar”). Using wireless communication signals for environment sensing can be regarded as consumer-level radar with advanced detection capabilities that enable, among other things, touchless / device-free interaction with a device / system. The wireless communication signals may be cellular communication signals, such as LTE or NR signals, WLAN signals, such as Wi-Fi signals, etc. As a particular example, the wireless communication signals may be an OFDM waveform as utilized in LTE and NR. High- frequency communication signals, such as millimeter wave (mmW) RF signals, are especially beneficial to use as sensing signals because the higher frequency provides, at least, more accurate range (distance) detection.

[0111] Possible use cases of RF sensing include health monitoring use cases, such as heartbeat detection, respiration rate monitoring, and the like, gesture recognition use cases, such as human activity recognition, keystroke detection, sign language recognition, and the like, contextual information acquisition use cases, such as location detection / tracking, direction finding, range estimation, and the like, and automotive sensing use cases, such as smart cruise control, collision avoidance, and the like.

[0112] There are different types of sensing, including monostatic sensing (also referred to as “active sensing”) and bistatic sensing (also referred to as “passive sensing”). FIGS.4A and 4B illustrate these different types of sensing. Specifically, FIG.4A is a diagram 400 illustrating a monostatic sensing scenario and FIG. 4B is a diagram 430 illustrating a bistatic sensing scenario. In FIG. 4A, the transmitter (Tx) and receiver (Rx) are co- located in the same sensing device 404 (e.g., a UE). The sensing device 404 transmits 36 QC2403178WOQualcomm Ref. No.2403178WO 37 one or more RF sensing signals 434 (e.g., uplink or sidelink positioning reference signals (PRS) where the sensing device 404 is a UE), and some of the RF sensing signals 434 reflect off a target object 406 (e.g., an unmanned aerial vehicle (UAV)). The sensing device 404 can measure various properties (e.g., times of arrival (ToAs), angles of arrival (AoAs), phase shift, etc.) of the reflections 436 of the RF sensing signals 434 to determine characteristics of the target object 406 (e.g., size, shape, speed, motion state, etc.).

[0113] In FIG. 4B, the transmitter (Tx) and receiver (Rx) are not co-located, that is, they are separate devices (e.g., a UE and a base station). Note that while FIG.4B illustrates using a downlink RF signal as the RF sensing signal 432, uplink RF signals or sidelink RF signals can also be used as RF sensing signals 432. In a downlink scenario, as shown, the transmitter device 402 is a base station (e.g., a gNB) and the receiver device 408 is a UE (e.g., a mobile phone, a V2X-capable vehicle, a roadside unit (RSU), etc.), whereas in an uplink scenario, the transmitter device 402 is a UE and the receiver device 408 is a base station. Where the transmitter device 402 is a base station and the receiver device 408 a UE, the sensing is referred to as UE-assisted sensing. In UE-assisted sensing, the position of receiver device 408 should be known by the network (e.g., by GPS or other UE positioning method).

[0114] Referring to FIG. 4B in greater detail, the transmitter device 402 transmits RF sensing signals 432 and 434 (e.g., positioning reference signals (PRS)) to the receiver device 408, but some of the RF sensing signals 434 reflect off a target object 406. The receiver device 408 (also referred to as the “sensing device”) can measure the times of arrival (ToAs) of the RF sensing signals 432 received directly from the transmitter device 402 and the ToAs of the reflections 436 of the RF sensing signals 434 reflected from the target object 406.

[0115] More specifically, as described above, a transmitter device (e.g., a base station) may transmit a single RF signal or multiple RF signals to a receiver device (e.g., a UE). However, the receiver may receive multiple RF signals corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. Each path may be associated with a cluster of one or more channel taps. Generally, the time at which the receiver detects the first cluster of channel taps is considered the ToA of the RF signal on the line-of-site (LOS) path (i.e., the shortest path between the transmitter and the receiver). Later clusters of channel taps are considered to have QC2403178WOQualcomm Ref. No.2403178WO 38 reflected off objects between the transmitter and the receiver and therefore to have followed non-LOS (NLOS) paths between the transmitter and the receiver.

[0116] Thus, referring back to FIG. 4B, the RF sensing signals 432 followed the LOS path between the transmitter device 402 and the receiver device 408, and the RF sensing signals 434 followed an NLOS path between the transmitter device 402 and the receiver device 408 due to reflecting off the target object 406. The transmitter device 402 may have transmitted multiple RF sensing signals 432, 434, some of which followed the LOS path and others of which followed the NLOS path. Alternatively, the transmitter device 402 may have transmitted a single RF sensing signal in a broad enough beam that a portion of the RF sensing signal followed the LOS path (RF sensing signal 432) and a portion of the RF sensing signal followed the NLOS path (RF sensing signal 434).

[0117] Based on the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, the receiver device 408 can determine the distance to the target object(s). For example, the receiver device 408 can calculate the distance to the target object as the difference between the ToA of the LOS path and the ToA of the NLOS path multiplied by the speed of light. In addition, if the receiver device 408 is capable of receive beamforming, the receiver device 408 may be able to determine the general direction to a target object 406 as the direction (angle) of the receive beam on which the RF sensing signal following the NLOS path was received. That is, the receiver device 408 may determine the direction to the target object 406 as the AoA of the RF sensing signal, which is the angle of the receive beam used to receive the RF sensing signal. The receiver device 408 may then optionally report this information to the transmitter device 402, its serving base station, an application server associated with the core network, an external client, a third-party application, or some other sensing entity. Alternatively, the receiver device 408 may report the ToA measurements to the transmitter device 402, or other sensing entity (e.g., if the receiver device 408 does not have the processing capability to perform the calculations itself), and the transmitter device 402 may determine the distance and, optionally, the direction to the target object 406.

[0118] Note that if the RF sensing signals are uplink RF signals transmitted by a UE to a base station, the base station would perform object detection based on the uplink RF signals just like the UE does based on the downlink RF signals. 38 QC2403178WOQualcomm Ref. No.2403178WO 39

[0119] Like conventional radar, wireless communication-based sensing signals can be used to estimate the range (distance), velocity (Doppler), and angle (AoA) of a target object. However, the performance (e.g., resolution and maximum values of range, velocity, and angle) may depend on the design of the reference signal.

[0120] FIG. 5 illustrates an example call flow 500 for an NR-based sensing procedure (e.g., a bistatic sensing procedure) in which the network configures the sensing parameters, according to aspects of the disclosure. Although FIG.5 illustrates a network-coordinated sensing procedure, the sensing procedure could be coordinated over sidelink channels.

[0121] At stage 505, a sensing server 570 (e.g., inside or outside the core network) sends a request for network (NW) information to a gNB 522 (e.g., the serving gNB of a UE 504). The request may be for a list of the UE’s 504 serving cell and any neighboring cells. At stage 510, the gNB 522 sends the requested information to the sensing server 570. At stage 515, the sensing server 570 sends a request for sensing capabilities to the UE 504. At stage 520, the UE 504 provides its sensing capabilities to the sensing server 570.

[0122] At stage 525, the sensing server 570 sends a configuration to the UE 504 indicating one or more reference signal (RS) resources that will be transmitted for sensing. The reference signal resources may be transmitted by the serving and / or neighboring cells identified at stage 510. In some cases, the NR-based sensing procedure illustrated in FIG. 5 may be a sensing-only procedure or a joint communication and sensing (JCS) procedure (also referred to as an integrated sensing and communication (ISAC) procedure). In the case of a sensing-only procedure, the reference signal resources may be reference signal resources specifically configured for sensing purposes. In the case of a JCS procedure, the reference signal resources may be reference signal resources for communication that can also be used for sensing purposes. Alternatively, the reference signal resources for sensing may be multiplexed (e.g., time-division multiplexed) with reference signal resources for communication. For example, the reference signal resources for communication may be an orthogonal frequency division multiplexing (OFDM) waveform, while the reference signal resources for sensing may be a frequency modulation continuous wave (FMCW) waveform.

[0123] At stage 530, the sensing server 570 sends a request for sensing information to the UE 504. The UE 504 then measures the transmitted reference signals and, at stage 535, sends 39 QC2403178WOQualcomm Ref. No.2403178WO 40 the measurements, or any sensing results determined from the measurements, to the sensing server 570.

[0124] In an aspect, the communication between the UE 504 and the sensing server 570 may be via the LTE positioning protocol (LPP). The communication between the sensing server 570 and the gNB may be via NR positioning protocol type A (NRPPa).

[0125] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). FIG.6 is a diagram 600 illustrating an example frame structure, according to aspects of the disclosure. The frame structure may be a downlink, uplink, or sidelink frame structure. Other wireless communications technologies may have different frame structures and / or different channels.

[0126] LTE, and in some cases NR, utilizes orthogonal frequency-division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0127] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (μ), for example, subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (μ=1), 40 QC2403178WOQualcomm Ref. No.2403178WO 41 there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0128] In the example of FIG. 6, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIG. 6, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.

[0129] A resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 6, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0130] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending 41 QC2403178WOQualcomm Ref. No.2403178WO 42 on whether the illustrated frame structure is used for uplink or downlink communication. FIG.6 illustrates example locations of REs carrying a reference signal (labeled “R”).

[0131] ISAC is an increasingly important component of next generation cellular technologies and automotive use cases. Some Advanced Driver Assistance System (ADAS) implementations use radar sensing to detect target range, velocity, etc. In addition, autonomous and semi-autonomous vehicles need to operate at a high rate of communication while still being able to sense (detect) surrounding objects.

[0132] For automotive applications, UE sensing in which the UE is a transmitting entity can be an important aspect for sensing surrounding objects. In some cases, the vehicles themselves have one or more integrated / associated sensors, and 3GPP-based ISAC can supplement the sensors. In some aspects, automotive applications may determine sensing priority and / or performance requirements. In general, for ADAS, relative positioning may be more important than absolute position.

[0133] Sensing applications need not use a particular waveform. According to aspects of the disclosure, sensing waveforms such as Sounding Reference Signal (SRS) waveforms with some enhancements can be used. In some aspects, Frequency Modulated Continuous Wave (FMCW) waveforms can be used. In-band UE sensing using uplink resources may enable spectrum reuse; e.g., in UE monostatic sensing.

[0134] Automotive use cases call for high density radar signals with high-resolution and a high update rate. There are different types of sensing techniques that may be used for automotive sensing, specifically, single stage, two-stage, and three-stage sensing.

[0135] FIG. 7 is a diagram 700 illustrating an example single stage sensing scenario, according to aspects of the disclosure. Single stage sensing may not be sufficient to meet automotive needs, however, as it can suffer from large overhead and latency. In the example of FIG. 7, the sensing device (e.g., sensing device 404) beam sweeps over four coherent processing intervals (CPIs), also referred to as radar frames. Each CPI (per beam) may occupy, for example, 5 ms (40 slots at 120 kHz subcarrier spacing (SCS) at 28 GHz) and a bandwidth of 0.4 GHz / 400 MHz. Thus, for a 20 frames per second (fps) update rate (i.e., a 50 ms sensing period), the CPIs would occupy 5% of the system resources per beam and per user. For the desired field of view (FoV) (here, nine beams), the CPIs would occupy 45% of system resources per user in 45 ms. This is a significant overhead on communication and causes a large latency for transmitting data for communication. 42 QC2403178WOQualcomm Ref. No.2403178WO 43 Such overhead and latency can potentially disrupt communication assistance functionalities, such as beam management and synchronization.

[0136] FIG.8 is a diagram 800 illustrating an example two stage sensing scenario, according to aspects of the disclosure. In FIG. 8, each wide block represents a sensing slot (labeled “S-Slot”) and each narrow block represents a sensing symbol. A sensing slot may be an uplink (UL) slot, a flexible (F) slot, or a dedicated sensing slot.

[0137] Two stage sensing includes scan and track stages (or phases) in which the sensing device (e.g., sensing device 404) transmits narrow beams to reduce overhead. In the scanning stage, the sensing device performs narrow beam scanning over a small bandwidth (e.g., 50 MHz) to obtain coarse range, velocity, and angle estimations of any target objects. In the example of FIG. 8, the scanning stage transmissions are performed every fourth symbol per beam in two adjacent slots, enabling the sensing device to detect a maximum one-way velocity estimate of 75 m / s, a velocity resolution of 21 m / s, a maximum range of 300 m, and a range resolution of 3 m. In the scanning stage, the sensing device may detect, for example, nine target objects in different beams tracked with a 50 ms update rate and comb-4 transmission.

[0138] In the tracking stage, the sensing device performs narrow beam scanning over a large bandwidth (e.g., 400 MHz) to obtain fine range, velocity, and angle estimations of any target objects detected during the scanning stage. The tracking phase has a length of the number of detected target objects from the scanning phase multiplied by the length of the CPI (e.g., 5 ms). In the example of FIG. 8, the tracking stage transmissions are on one symbol every fourteenth symbol over 40 slots, enabling the sensing device to detect a maximum absolute velocity estimate of 21 m / s, a velocity resolution of 1 m / s, a maximum range of 300 m, and a range resolution of 37 cm.

[0139] Note that while FIG.8 illustrates the scanning stage as having two sets of two consecutive slots for two different beam directions, as will be appreciated, there may be more than two beam directions, and therefore, the number of sets of two consecutive sensing slots would correspond to the number of beam directions. In addition, there may be one or more slots between each set of two sensing slots. The same applies to the tracking phase. Further, there may be one or more slots between the scanning phase and the tracking phase. 43 QC2403178WOQualcomm Ref. No.2403178WO 44

[0140] Two stage sensing has a small resource overhead per sensing device (only sensing symbols are considered for overhead calculation). For example, two stage sensing may provide 0.02% resource utilization in the best-case scenario (i.e., no target objects detected), 0.11% resource utilization in the case that one target object is detected, and 0.82% resource utilization in the worst-case scenario (here, target objects detected in all nine beams). However, two stage sensing needs a large number of consecutive sensing (UL or F) slots to meet the high velocity resolution requirement.

[0141] FIG. 9 is a diagram 900 illustrating an example three stage sensing scenario, according to aspects of the disclosure. In FIG.9, as in FIG.8, each wide block represents a sensing slot (labeled “S-Slot”) and each narrow block represents a sensing symbol. A sensing slot may be an uplink (UL) slot, a flexible (F) slot, or a dedicated sensing slot.

[0142] Three stage sensing includes a wide scanning stage, a narrow scanning stage, and a tracking stage, which reduces the number of consecutive UL or F slots needed. For example, three stage sensing may decrease the number of consecutive S slots in the tracking stage by 0.25 times (one fourth) that of two stage sensing.

[0143] In the wide beam scanning stage (phase), the sensing device (e.g., sensing device 404) performs broad beam scanning over a small bandwidth (e.g., 50 MHz) to obtain coarse range, velocity, and angle estimations of any target objects. In the example of FIG.9, the wide scanning stage transmissions are performed every fourth symbol per beam in two adjacent slots, enabling the sensing device to detect a maximum one-way velocity estimate of 75 m / s and a velocity resolution of 21 m / s.

[0144] In the narrow beam scanning stage (phase), the sensing device performs narrow beam scanning over a small bandwidth (e.g., 50 MHz) to obtain fine angle, moderate velocity, and coarse range estimations of any target objects detected in the wide scanning stage. In the example of FIG. 9, the narrow scanning stage transmissions are performed every fourteenth symbol per beam over eight slots, enabling the sensing device to obtain a maximum absolute velocity estimate of 21m / s and a velocity resolution of 5 m / s.

[0145] In the narrow beam tracking stage (phase), the sensing device performs narrow beam tracking over a large bandwidth (e.g., 400 MHz) to obtain fine range, velocity, and angle estimations of any target objects detected during the narrow scanning stage. In the example of FIG. 9, the tracking stage transmissions are performed on one symbol every 44 QC2403178WOQualcomm Ref. No.2403178WO 45 fourth slot over 40 slots to obtain a maximum absolute velocity estimate of 5 m / s and a velocity resolution of 1 m / s.

[0146] Note that in the example of FIG.9, there may be one or more slots between the wide beam scanning stage sensing slots, one or more slots between the narrow beam scanning stage sensing slots, and / or one or more slots between the narrow beam tracking stage sensing slots. Further, there may be one or more slots between the wide beam scanning stage, the narrow beam scanning stage, and / or the narrow beam tracking phase.

[0147] For three stage sensing, signaling enhancements (e.g., the time division duplex (TDD) pattern) are needed to indicate the sensing slot pattern(s), due to the stringent velocity requirements. In some cases, three stage sensing may use beam interleaving to reduce latency and the required number of S slots.

[0148] As noted above, accurate sensing techniques (for example, integrated sensing and communication (ISAC) techniques) can enable emerging technologies, such as automotive applications. However, it may be challenging to meet sensing goals, especially when both sensing and communication need to be supported.

[0149] For the example of an automotive sensing application, a sensing receiver node at a vehicle detects and tracks surrounding targets for automotive application. The sensing target detection / tracking, however, can be interrupted, missed, or degraded in performance based on factors such as interference from neighboring transmit nodes. For example, detection of a weak target can be missed due to strong interference from a nearby vehicle (or other transmitter), false alarms may be generated based on multipath clutter (detection of non line-of-sight signals, generally found in environments with larger numbers of reflecting surfaces / objects), false alarms may be generated based on an increased noise floor caused by an interfering transmitter, and / or a target track path could be spotty with a low confidence measurement, which can lead to poor path prediction performance.

[0150] For communications applications, Radio Link Monitoring (RLM) and Radio Link Failure (RLF) techniques are supported to detect and mitigate problems with radio links. However, techniques for sensing-specific monitoring (referred to herein as Sensing Radio Link Management (S-RLM)) are not included in current RLM and RLF techniques.

[0151] Aspects of the disclosure provide sensing management techniques to detect sensing- specific events that may potentially affect sensing performance. The sensing-specific events are referred to herein as failure events, but the phrase embraces events that can 45 QC2403178WOQualcomm Ref. No.2403178WO 46 degrade performance and is not limited to events that cause actual failure of a sensing process. Implementations of S-RLM techniques can improve target detection and tracking performance, and the techniques can be adapted to particular applications and / or priorities to meet safety, latency, and / or performance goals. Aspects of the disclosure include signaling and additions / changes to existing protocol(s) to implement the techniques.

[0152] FIG. 10 illustrates an example sensing management process 1000, according to aspects of the disclosure. At 1010, a sensing node may be configured with one or more sensing- specific parameters, such as link quality parameters (e.g., parameters related to sensing metrics indicative of link quality), timing parameters, counter parameters, resource parameters, or combinations thereof. In some implementations, at least some of the parameters may be pre-determined (including one or more default parameter values to be used in the absence of associated configuration), configured / dynamically determined by a network entity, and / or otherwise provided. Network entities providing sensing-specific parameter(s) can include one or more RAN nodes (gNBs / base stations, TRPs, access points, etc.), one or more servers implementing a Sensing Management Function (SnMF) or other functionality, one or more other network or third party servers, one or more sensing transmit / receive / client nodes, etc.

[0153] At 1020, based on one or more sensing-specific parameters, the sensing node detects one or more failure events including at least a first failure event. For example, one or more sensing-specific metrics indicative of sensing quality may be calculated based on sensing measurement(s) and compared to one or more thresholds, compared to one or more counters, or both, to determine a first failure event. Non-exhaustive examples of sensing metrics and failure events are described below. Sensing-specific parameters used to detect failure events may be configured based on the types of failures, sensing stages, sensing applications, sensing priorities, target types, etc.

[0154] At 1030, the sensing node determines whether a consistent failure event is identified based at least on the one or more failure events. Identifying a consistent failure event refers to determining the consistent failure event at the sensing node (e.g., based on one or more counters), and / or identifying the consistent failure event based on information from a network entity (e.g., receiving configuration for mitigating action(s) based on a network entity determination of the consistent failure event). Sensing-specific parameters 46 QC2403178WOQualcomm Ref. No.2403178WO 47 such as the number and type of failure events triggering the consistent failure event may be different for different types of failures, sensing stages, sensing applications, sensing priorities, target types, etc. In some cases, the sensing node may transmit an indication of at least one of the detected failure events to a network entity and receive an indication of the consistent failure event from the network entity (an explicit indication, an implicit indication based on configuration of one or more mitigating actions, etc.). The sensing node may then identify the consistent failure event based on the indication. For the example illustrated in FIG.11 and described in more detail below, a failure event counter is incremented in response to each of the one or more detected failure events, and if the counter reaches a consistent failure event threshold prior to expiry of a failure event reset timer, a consistent failure event may be identified at the sensing node.

[0155] The sensing-specific parameters can be used to tailor failure detection and mitigation for improved sensing performance. For an example of a higher priority sensing application, the thresholds to detect failure events may be more sensitive, the failure event reset timers may be longer, the counters / other parameters for determining a consistent failure event may be less restrictive, etc. A less sensitive threshold / count / timer is less sensitive to detecting failure event(s), while a more sensitive threshold / count / timer is more sensitive to detecting failure event(s).

[0156] At 1040, in response to identifying a consistent failure event, the sensing node implements one or more actions to mitigate the consistent failure event. Actions to recover from a consistent failure event can include dropping or modifying transmissions, as well as retransmissions in all or a few selected sensing directions. In some aspects, the sensing node can transmit a request for updated resources to a network entity (e.g., using a Scheduling Request (SR)) and may include at least some information associated with the sensing-specific failure event in the request (e.g., an indication of the type of failure event). In response, the network entity may configure the sensing node according to the scheduling request. In some cases, the network entity can determine and configure the mitigation without a request from the sensing node, or may configure at least one different action than the requested action(s). At 1050, the consistent failure event is canceled; for example, in response to expiration of a cancelation timer, in response to completing one or more actions, in response to an instruction from a network entity, etc. 47 QC2403178WOQualcomm Ref. No.2403178WO 48

[0157] FIG. 11 illustrates an example timeline 1100 of failure event detection for a set of example sensing-specific parameters. The detected failure events are based on one or more sensing-specific parameters such as threshold(s) for sensing metric(s), counter(s) for sensing metric(s), etc., where the sensing-specific parameters can be selected to be more sensitive or less sensitive (e.g., a threshold can be set lower for higher sensitivity detection or lower for lower sensitivity detection). In FIG.11, a failure event counter is referred to as a Sense Before next Transmission (SBT) counter, analogous to an LBT counter in communication. For the example of FIG. 11, the threshold for detecting a consistent failure event is an SBT failure event counter value of four, and a Sensing-Radio Link Failure (S-RLF) failure event reset timer duration and a Consistent SBT Failure (C- SBT-F) cancelation timer duration are configured as shown. Although the two timers are shown with different durations, in some cases they may be configured with the same duration. Additionally, although FIG.11 shows an example with one set of counters and timers, multiple counters / timers may be used; for example, for different failure event types such as those described below. Further, when multiple targets are being sensed / tracked, counters can be used for each of the multiple targets.

[0158] At t0, the SBT counter value is equal to zero; for example, set to zero based on initiation of a sensing process, reset to zero in response to an S-RLF failure event reset timer expiring prior to detection of another failure event, or reset to zero based on cancelation of a consistent failure event (e.g., due to performance of one or more actions in response to identifying the consistent failure event, due to expiration of a C-SBT-F cancelation timer, etc.).

[0159] At t1, in response to detection of a first failure event, the SBT failure event counter is incremented by one and an S-RLF failure event reset timer with a duration of Tdetis started / initiated. In some aspects, the first failure event may be detected based on comparing one or more sensing metrics to one or more associated thresholds / counters. At t2, a second failure event is detected, and since the second failure event is detected prior to expiration of the timer (t2-t1< Tdet), the SBT failure event counter is again incremented, and the S-RLF failure event reset timer is restarted / reset. If the second subsequent failure event were to occur after expiration of the S-RLF failure event reset timer, the SBT failure event counter would be reset to zero and in response to the event at t2 the counter would increment to one. Similarly, the third and fourth failure events occur at times t3 and t4, 48 QC2403178WOQualcomm Ref. No.2403178WO 49 with t3-t2 < Tdet and t4-t3 < Tdet, so the SBT failure event counter is incremented for each of the events to three and then to four, indicating a consistent failure event.

[0160] In response to a consistent failure event being triggered at t4, the sensing node performs at least one action. In some cases, the sensing node can indicate the consistent failure event to a network entity (optionally including at least some information related to the consistent failure event trigger and / or one or more of the failure event(s)). The sensing node can request configuration of one or more actions (e.g., with a scheduling request), the network entity can configure / dynamically determine one or more actions, or both. In some aspects, the network entity can determine the consistent failure event has been triggered based on information about the failure events received from the sensing node and can configure the sensing node to perform the one or more actions. Example actions to recover from sensing failure events can include dropping transmissions, modifying transmissions, retransmissions in all sensing directions, retransmissions in fewer than all selected sensing directions, or combinations thereof.

[0161] At t5, the consistent failure event status is canceled, either based on expiration of a C- SBT-F timer, based on performance of one or more actions, based on instruction from a network entity (such as a gNB or other RAN node, sensing server, etc.), and / or based on one or more other conditions / events. For example, if the sensing node detects that the mitigation is insufficient, a C-SBT-F timer expiration may be overridden, and additional actions may be configured. As noted above, the duration of a C-SBT-F timer can be same as the S-RLF failure event reset timer duration or it can be different, and may differ across different circumstances, to enable appropriate sensing recovery action(s).

[0162] As noted above, one or more sensing metrics may be calculated based on one or more sensing measurements, and the sensing metric(s) used to determine whether a failure event is detected. For example, one or more sensing metrics can be compared to one or more thresholds to determine whether the metric is greater than, equal to, or less than a threshold value for the metric or whether the metric falls within a range, whether the metric can be used to increment a counter, or otherwise used to determine whether a failure event is identified.

[0163] A receiving sensing node can update one or more failure event counters in response to measurement(s) indicating sensing-specific failure events in one or more beam directions for a given period or a measurement instance. The sensing metrics can be calculated for 49 QC2403178WOQualcomm Ref. No.2403178WO 50 measurements obtained for a given period (e.g., based on one sensing measurement instance), or can be calculated based at least partially on prior measurements / metrics for earlier periods / measurement instances. For example, one or more metrics indicating a sensing-specific failure event can include an average value, a maximum or minimum value, a difference of consecutive sensing measurements, a probability, a covariance, etc. The measurements / metrics to update one or more counters can be measured / calculated periodically, in a pre-configured time-frequency pattern, in response to conditions, based on the sensing application, etc. For example, a period of measurement can be defined in terms of time duration, a number of CPIs etc.

[0164] The types of failure events and measurements / metrics used to identify the failure events may depend on the sensing application, target characteristics, latency and / or safety requirements, sensing environment, sensing device capabilities, etc. Example failure events are described below; however, other metrics and measurements may be used to identify failure event(s).

[0165] In some aspects of the disclosure, one or more detection-based failure events may be identified, based on one or more detection-based thresholds configured for target mis- detection and / or missed detection. Target mis-detection refers to an inaccurate sensing result, while missed detection refers to a failure to detect the target during a sensing instance / interval. Mis-detection and missed detection may be detected / predicted based on target tracks; for example, a spotty target track may indicated one or more target detections were missed based on detections prior to and / or subsequent to the missed detection(s). According to some aspects, a detection-based failure event may be identified based on counter information for every detected target in a track stage. For example, a detection-based failure counter may be based on a net counter for multiple targets being tracked; for example, a sum of counters for all targets, maximum of the counters, or could be a weighted average of counters for all targets. The weighting can depend on the Radar Cross Section (RCS), distance, or received SINR of the targets calculated based on the Constant False Alarm Rate (CFAR) detection. Based on the metric for detecting / predicting mis-detection or missing detections, a detection-based failure event can be determined and the SBT counter incremented.

[0166] In some aspects of the disclosure, one or more false alarm failure events may be identified, based on one or more thresholds configured for false alarm detection. In general, a false 50 QC2403178WOQualcomm Ref. No.2403178WO 51 alarm refers to a radar detection not associated with or generating tracks. According to some aspects, a false alarm may be detected based on comparing a probability one or more detections are false alarms (e.g., using previous detections) with a false alarm threshold, comparing a number of false alarms within a time period with a false alarm counter, etc.

[0167] In some aspects of the disclosure, one or more noise-based failure events may be identified, based on one or more noise-based thresholds configured based on noise level metric(s). A threshold may be associated with a noise level for a complete sensing profile or a portion, such as a range-only profile or range-angle profile (in general, a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or combinations thereof). For example, a noise level sensing metric can be a simple average of radar image data after peaks exceeding a CFAR threshold are removed (e.g., some data associated with the peaks is removed). In another example, a noise level sensing metric could be calculated CFAR thresholds from the radar image.

[0168] In some aspects of the disclosure, one or more error-based failure events may be identified based on one or more thresholds configured for actual / predicted error detection. For example, a threshold can be configured for predicted error covariance of radar parameters (such as for those predicted by a Kalman tracking filter), and a sensing-specific failure event can be determined in response to the predicted error covariance exceeding a threshold.

[0169] In some aspects of the disclosure, one or more thresholds may be configured for sensing- specific failure detection based on Intersection over Union (IoU) information. For example, a sensing-specific failure can be detected in response to a minimum IoU or a difference between consecutive IoU measured within a period (or between two measurement instances) exceeding a threshold.

[0170] According to some aspects of the disclosure, parameters for S-RLM sensing management / monitoring techniques may be different in different circumstances. For example, at least some parameters used to apply rules for detecting sensing-specific failure events, counter threshold parameter(s) for triggering S-RLF, timer durations such as one or more failure event reset timers, cancelation timers, and / or other parameters can vary based at least partially on the stage, priority, and / or other characteristics of a sensing process. 51 QC2403178WOQualcomm Ref. No.2403178WO 52

[0171] In aspects of the disclosure, at least some parameters can be different for a scanning stage and a tracking stage, or between different scanning or tracking stages. For the example shown in FIG.8, at least some parameters can be different for the scanning stage and the tracking stage, while in FIG.9, at least some parameters can be different for one or both of the first scanning stage and the second narrower beam scanning stage, and / or the tracking stage.

[0172] For the example of a sensing-specific failure event based on a false alarm sensing metric, one or more false alarm thresholds, false alarm failure counts, false alarm timer durations, or combinations thereof may be configured differently based on a sensing stage. For example, a first false alarm threshold can be configured for sensing during a scanning stage and a second different false alarm threshold can be configured for sensing during a tracking stage, where the first false alarm threshold is higher (less sensitive) than the second false alarm threshold. False alarm events not detected during the scanning stage based on a larger threshold can be filtered in the tracking stage, when a lower (more sensitive) threshold is implemented. Additionally or alternatively, different SBT failure count value thresholds may be configured to trigger a consistent failure event, a different S-RLF failure timer duration for resetting the SBT counter may be configured, a different cancelation time duration can be configured, different corrective actions can be requested / taken, etc. In some aspects, additional threshold(s) can be used for multiple scanning and / or tracking stages; for example, a third false alarm threshold can be configured, where the third false alarm threshold can be lower than the first false alarm threshold and the second false alarm threshold for more sensitive detection.

[0173] For the example of a sensing-specific failure event based on poor measurement accuracy, one or more measurement accuracy thresholds, measurement accuracy failure counts, measurement accuracy timer durations, or combinations thereof may be configured differently based on a sensing stage. For example, a first threshold can be configured for use during a scanning stage and a second different threshold can be configured for sensing during a tracking stage, where the first threshold is associated with a lower measurement accuracy (less sensitive) and the second threshold is associated with a higher measurement accuracy (more sensitive). Using a threshold corresponding to a higher measurement accuracy level during a tracking stage can provide enhanced accuracy with fewer or no consistent failure event triggers during the scanning stage. Additionally or 52 QC2403178WOQualcomm Ref. No.2403178WO 53 alternatively, different SBT failure event counter thresholds may be configured to trigger a consistent failure event S-RLF, a different S-RLF failure event reset timer duration for resetting the SBT failure event counter may be configured, a different cancelation timer duration can be configured, different corrective actions can be requested / taken, etc. In some aspects, additional threshold(s) can be used for multiple scanning and / or tracking stages; for example, a third threshold can be configured corresponding to a different measurement accuracy than the first or second threshold.

[0174] For the example of a sensing-specific failure event based on detection failure (e.g., mis- detection or missed detection), one or more detection-based thresholds, detection-based failure counts, detection-based timer durations, or combinations thereof may be configured differently based on a sensing stage. For example, a first threshold can be configured for use during a scanning stage and a second different threshold can be configured for sensing during a tracking stage, where the first threshold is more sensitive to missed detections or mis-detections and the second threshold is less sensitive. Additionally or alternatively, different SBT failure event counter thresholds may be configured to trigger a consistent failure event, a different S-RLF failure timer duration for resetting the SBT counter may be configured, a different cancelation timer duration can be configured, different corrective actions can be used, etc. For events based on detection failure, the scanning stage has no or limited prior information on targets present, and a target is missed during the scanning stage, the tracking stage cannot recover the target parameters. Therefore, using a more sensitive first threshold and / or a lower SBT counter value threshold can increase the probability that a tracking stage will encompass the targets of interest.

[0175] For the example of a sensing-specific failure event based on noise level, one or more noise-based thresholds, noise-based failure counts, noise-based timer durations, or combinations thereof may be configured differently based on a sensing stage. For example, a first threshold can be configured for use during a scanning stage and a second different threshold can be configured for sensing during a tracking stage, where the first threshold is associated with a higher noise level (less sensitive) and the second threshold is associated with a lower noise level (more sensitive). Additionally or alternatively, different SBT count value thresholds may be configured to trigger a consistent S-RLF, a different S-RLF failure timer duration for resetting the SBT counter may be configured, 53 QC2403178WOQualcomm Ref. No.2403178WO 54 a different cancelation time duration can be configured, different corrective actions can be requested / taken, etc. For events based on noise level, using a higher threshold (or higher count level) during the scanning stage can allow detection of the largest number of targets. Although this may be accompanied by a high level of false alarms in some circumstances, the false alarms can be filtered during the tracking stage.

[0176] In some aspects of the disclosure, at least some parameters can be based at least partially on a priority of failure events, which can depend on the sensing application. Sensing- specific parameters may include one or more rules for setting sensing priority and can be pre-determined, indicated at the receiving sensing node, or both.

[0177] In some aspects, the priority can be based on latency requirements, safety requirements, or both. For example, a high priority pre-crash application (a critical-safety application with have very low latency requirements) can trigger a failure event based on a lower counter threshold than a low priority adaptive cruise control application. In some aspects, the priority can be based on range, velocity, and / or direction to be sensed. For example, short-range targets with high-velocity can be given higher priority than long-range targets with low velocity. In some cases, priority can be based on a combination of different conditions.

[0178] In some aspects of the disclosure, one or more actions may be taken to recover from S- RLF. For example, a C-SBT-F event can be triggered in response to a failure event counter reaching / exceeding a threshold, and one or more actions may be taken in selected directions. As noted above, there may be more than one counter, with the counters tracking specific sensing-related events that meet / exceed the corresponding threshold(s).

[0179] Different techniques can be used to determine / implement one or more actions in response to a C-SBT-F consistent failure event. For example, a sensing node can indicate the C- SBT-F event, and a network entity can manage the corrective action(s). The sensing node can request a particular action, or the network entity may configure the action(s) based on information related to the failure event.

[0180] In some aspects of the disclosure, in response to the C-SBT-F event, a sensing transmit node drops at least some future sensing transmissions (similar to communication UEs dropping grants for RLF). For example, a sensing receive node may transmit an indication of a C-SBT-F event to a network entity, which may provide one or more 54 QC2403178WOQualcomm Ref. No.2403178WO 55 sensing transmit nodes with time / frequency / direction resources in which transmissions should be omitted.

[0181] In some aspects of the disclosure, a sensing transmit node requests retransmission resources from the network entity, either explicitly or implicitly. For example, the sensing transmit node may signal a network entity indicating a retransmission request (e.g., using signaling similar to Negative-Acknowledgment (NACK) signaling). In some aspects, the messaging may also include at least some information indicative of the event associated with the triggered C-SBT-F. In response, the sensing node may receive retransmission resources.

[0182] In some aspects, the action may include one or more modified sensing transmission parameters. For example, a sensing node may request one or more transmission parameter modifications, such as modified waveform parameter(s), transmit power modification, direction modification, frequency band modification, and / or other modification (e.g., within a set of prescribed transmit codebook). A sensing node may request particular modification(s), the network entity may determine appropriate modification(s), or a combination. For example, a sensing node can transmit a request to a network entity to operate in an interference robust safe mode, and the network entity may configure the sensing node accordingly. The safe mode may use a randomized start frequency offset amount, timing offset amount, or a combination thereof for increased robustness. The randomization may be performed at the sensing node or at a network entity such as a gNB; for example, the network entity may select a start frequency offset according to a uniform distribution between zero and a pre-determined value, may select a random backoff time according to a uniform distribution between 0 and a pre- determined value, etc. In some aspects, at least some randomization may be used outside of a particular mode.

[0183] In some aspects, a sensing node requests a new grant using a new Scheduling Request (SR). The SR may include at least some information indicative of the event associated with the triggered C-SBT-F. In response, the network can configure the sensing node according to the request.

[0184] In some aspects, the sensing node continues sensing as normal (e.g., without dropping transmissions, without NACK signaling, and / or without a scheduling request) and only reports detection of the consistent failure event (e.g., reporting a Boolean indicator, one 55 QC2403178WOQualcomm Ref. No.2403178WO 56 or more counter values, information about one or more failure events, etc.) and the network entity can determine and configure mitigating action(s). For example, the network entity can re-select and / or re-assign resources based on the indication of the consistent failure event. In some aspects, the signaling can be similar to UE reports of consistent LBT failure for New Radio-Unlicensed / Sidelink-Unlicensed (NR-U / SL-U) systems according to some standard protocols.

[0185] FIG. 12 illustrates an example sensing method 1200 at a sensing node, according to aspects of the disclosure. In an aspect, method 1200 may be performed by a sensing node (e.g., any of the user equipments or base stations described herein).

[0186] At 1210, the sensing node detects one or more failure events based on one or more sensing-specific failure parameters. In aspects where the sensing node is a user equipment, operation 1210 may be performed, for example, using WWAN transceiver(s) 310, short range transceiver(s) 320, processor(s) 342, sensing component(s) 348, and / or memory 340 of UE 302, which may be considered means (structure) for performing operation 1210. In aspects where the sensing node is a RAN node such as a TRP / base station, operation 1210 operation may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the one or more network transceivers 380, the one or more processors 384, memory 386, and / or sensing component(s) 388, any or all of which may be considered means (structure) for performing this operation.

[0187] At 1220, based at least on the one or more detected failure events, the sensing node may identify a consistent failure event. In aspects where the sensing node is a user equipment, operation 1220 may be performed, for example, using WWAN transceiver(s) 310, short range transceiver(s) 320, processor(s) 342, sensing component(s) 348, and / or memory 340 of UE 302, which may be considered means (structure) for performing operation 1220. In aspects where the sensing node is a RAN node such as a TRP / base station, operation 1220 operation may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the one or more network transceivers 380, the one or more processors 384, memory 386, and / or sensing component(s) 388, any or all of which may be considered means (structure) for performing this operation. 56 QC2403178WOQualcomm Ref. No.2403178WO 57

[0188] At 1230, in response to identifying the consistent failure event, the sensing node may perform at least one action. In aspects where the sensing node is a user equipment, operation 1230 may be performed, for example, using WWAN transceiver(s) 310, short range transceiver(s) 320, processor(s) 342, sensing component(s) 348, and / or memory 340 of UE 302, which may be considered means (structure) for performing operation 1230. In aspects where the sensing node is a RAN node such as a TRP / base station, operation 1230 operation may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the one or more network transceivers 380, the one or more processors 384, memory 386, and / or sensing component(s) 388, any or all of which may be considered means (structure) for performing this operation.

[0189] FIG. 13 illustrates an example sensing method 1300 at a network entity, according to aspects of the disclosure. In an aspect, method 1300 may be performed by a network entity (e.g., a network entity, one or more sensing servers implementing a sensing management function, a third-party server, or any of the network entities described herein).

[0190] At 1310, the network entity receives an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node. In some aspects, where the network entity is a sensing server, operation 1310 may be performed by the one or more network transceivers 390, the one or more processors 394, memory 396, and / or sensing component 398, any or all of which may be considered means (structure) for performing this operation.

[0191] At 1320, the network entity may configure the first sensing node to perform one or more actions in response to the received indication. In some aspects, where the network entity is a sensing server, operation 1320 may be performed by the one or more network transceivers 390, the one or more processors 394, memory 396, and / or sensing component 398, any or all of which may be considered means (structure) for performing this operation.

[0192] As will be appreciated, a technical advantage of methods 1200 and 1300 is enabling improved sensing target detection and tracking performance. Sensing-specific parameters can be used to tailor the failure detection and mitigating action(s) to the circumstances 57 QC2403178WOQualcomm Ref. No.2403178WO 58 and failure types. The techniques may improve sensing performance in challenging circumstances, such as the proximity of interfering transmitters, multipath clutter, and / or other causes of link quality degradation.

[0193] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0194] Implementation examples are described in the following numbered clauses:

[0195] Clause 1. A method of wireless communication at a sensing node, comprising: detecting one or more failure events based on one or more sensing-specific parameters; based at least on the one or more detected failure events, identifying a consistent failure event; and in response to identifying the consistent failure event, performing at least one action.

[0196] Clause 2. The method of clause 1, wherein the one or more sensing-specific parameters include a consistent failure event threshold, and further comprising: incrementing a failure event counter in response to detecting the one or more failure events; and identifying the consistent failure event based on comparing a value of the failure event counter to the consistent failure event threshold.

[0197] Clause 3. The method of clause 2, wherein the sensing-specific parameters include a failure event reset timer duration for a failure event reset timer, and further comprising: 58 QC2403178WOQualcomm Ref. No.2403178WO 59 initiating the failure event reset timer in response to detecting a first failure event of the one or more failure events; and resetting the failure event counter in response to expiration of the failure event reset timer prior to detecting a second subsequent failure event.

[0198] Clause 4. The method of any of clauses 1 to 3, further comprising: canceling the consistent failure event in response to expiration of a cancelation timer, performance of one or more actions, an indication from a network entity, an indication from another sensing node, or a combination thereof.

[0199] Clause 5. The method of any of clauses 1 to 4, wherein detecting the one or more failure events is further based on one or more sensing measurements in one or more beam directions, and further comprises calculating one or more sensing metrics based on a plurality of the one or more sensing measurements, wherein the one or more sensing metrics comprise an average of the plurality of sensing measurements, a maximum of the plurality of sensing measurements, a minimum of the plurality of sensing measurements, at least one difference between consecutive sensing measurements for the plurality of sensing measurements, or a combination thereof.

[0200] Clause 6. The method of any of clauses 1 to 5, wherein the one or more failure events comprises a mis-detection event, a missed detection event, or both and the sensing- specific parameters include one or more detection-based failure thresholds, one or more detection-based failure counters, or a combination thereof.

[0201] Clause 7. The method of clause 6, further comprising: calculating a probability of mis- detection for one or more targets, a number of mis-detections for the one or more targets, a probability of missed detection for the one or more targets, a number of missed detections for the one or more targets, or a combination thereof based on one or more sensing measurements; and wherein detecting the one or more failure events comprises comparing the probability of mis-detection for the one or more targets, the probability of missed detection for the one or more targets, or both to at least one of the one or more detection-based failure thresholds, comparing the number of mis-detections for the one or more targets, the number of missed detections for the one or more targets, or both to at least one of the one or more detection-based failure counters.

[0202] Clause 8. The method of any of clauses 1 to 7, wherein the one or more failure events comprise at least one false alarm failure event and wherein the sensing-specific 59 QC2403178WOQualcomm Ref. No.2403178WO 60 parameters include one or more false alarm thresholds, one or more false alarm counters, or a combination thereof.

[0203] Clause 9. The method of clause 8, further comprising: calculating a probability of a false alarm or a number of false alarms or a combination thereof based on one or more sensing measurements; and wherein detecting the one or more failure events comprises comparing the probability of a false alarm to at least one false alarm threshold of the one or more false alarm thresholds, comparing the number of false alarms to at least one false alarm counter of the one or more false alarm counters, or both.

[0204] Clause 10. The method of any of clauses 1 to 9, wherein the one or more failure events comprises at least one noise-based failure event and wherein the sensing-specific parameters include one or more noise-based thresholds, and further comprising: calculating a noise level associated with a radar image based on one or more sensing measurements, wherein the noise level associated with the radar image comprises a noise level of a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or a combination thereof; and wherein detecting the at least one noise-based failure event comprises comparing the noise level associated with the radar image to at least one noise-based threshold of the one or more noise-based thresholds.

[0205] Clause 11. The method of any of clauses 1 to 10, wherein the one or more sensing-specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0206] Clause 12. The method of clause 11, wherein the first sensing stage is a scanning stage and the second different sensing stage is a tracking stage.

[0207] Clause 13. The method of clause 12, wherein the one or more sensing-specific parameters further include at least a third sensing-specific parameter for the particular sensing metric associated with a third different sensing stage, and wherein the third different sensing stage is a different scanning stage.

[0208] Clause 14. The method of any of clauses 12 to 13, wherein the particular sensing metric is a false alarm sensing metric, and wherein: the first sensing-specific parameter is a first false alarm failure threshold, a first false alarm failure count, a first false alarm failure 60 QC2403178WOQualcomm Ref. No.2403178WO 61 timer duration, or a combination thereof; and the second different sensing-specific parameter is a second false alarm failure threshold more sensitive than the first false alarm failure threshold, a second false alarm failure count more sensitive than the first false alarm failure count, a second false alarm failure timer duration more sensitive than the first false alarm failure timer duration, or a combination thereof.

[0209] Clause 15. The method of any of clauses 12 to 14, wherein the particular sensing metric is a measurement accuracy sensing metric, and wherein: the first sensing-specific parameter is a first measurement accuracy failure threshold, a first measurement accuracy failure count, a first measurement accuracy failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second measurement accuracy failure threshold more sensitive than the first measurement accuracy failure threshold, a second measurement accuracy failure count more sensitive than the first measurement accuracy failure count, a second measurement accuracy failure timer duration more sensitive than the first measurement accuracy timer failure duration, or a combination thereof.

[0210] Clause 16. The method of any of clauses 12 to 15, wherein the particular sensing metric is a detection-based sensing metric, and wherein: the first sensing-specific parameter is a first detection-based failure threshold, a first detection-based failure count, a first detection-based failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second detection-based failure threshold less sensitive than the first detection-based failure threshold, a second detection-based failure count less sensitive than the first detection-based failure count, a second detection-based failure timer duration less sensitive than the first detection-based failure timer duration, or a combination thereof.

[0211] Clause 17. The method of any of clauses 12 to 16, wherein the particular sensing metric is a noise-related sensing metric, and wherein: the first sensing-specific parameter is a first noise-related failure threshold, a first noise-related failure count, a first noise-related failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second noise-related failure threshold more sensitive than the first noise- related failure threshold, a second noise-related failure count more sensitive than the first noise-related failure count, a second noise-related failure timer duration more sensitive than the first noise-related failure timer duration, or a combination thereof. 61 QC2403178WOQualcomm Ref. No.2403178WO

[0212] Clause 18. The method of any of clauses 1 to 17, wherein one or more sensing-specific parameters include at least one parameter based at least in part on a sensing priority.

[0213] Clause 19. The method of clause 18, wherein the sensing priority is associated with a sensing application and is based at least in part on a latency requirement of the sensing application, a safety requirement of the sensing application, or both.

[0214] Clause 20. The method of any of clauses 18 to 19, wherein the sensing priority is based at least in part on a range, a velocity, a direction, or a combination thereof to be sensed.

[0215] Clause 21. The method of any of clauses 1 to 20, wherein performing at least one action comprises: requesting one or more modified sensing transmission parameters.

[0216] Clause 22. The method of clause 21, wherein requesting the one or more modified sensing transmission parameters comprises transmitting a scheduling request to a network entity, and further comprising: receiving configuration information from the network entity, the configuration information configuring the sensing node to: transmit sensing signals with one or more modified waveform parameters, modified transmit power, modified transmit direction, modified frequency resources, or a combination thereof; retransmit at least some sensing transmissions; drop one or more scheduled sensing transmissions; or a combination thereof.

[0217] Clause 23. The method of any of clauses 1 to 22, wherein identifying the consistent failure event based at least one of the one or more detected failure events comprises: transmitting an indication of the at least one of the one or more detected failure events to a network entity; receiving an indication of the consistent failure event from the network entity; and identifying the consistent failure event and the at least one action based on the indication of the consistent failure event received from the network entity.

[0218] Clause 24. A method of communication at a network entity comprising: receiving an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configuring the first sensing node to perform one or more actions in response to the received indication.

[0219] Clause 25. The method of clause 24, further comprising: configuring the first sensing node with the one or more sensing-specific parameters based on a first sensing priority; receiving an indication of a second different sensing priority from the first sensing node; 62 QC2403178WOQualcomm Ref. No.2403178WO 63 and dynamically indicating at least one updated sensing-specific parameter based on the second different sensing priority.

[0220] Clause 26. The method of clause 25, wherein the indication of the second different sensing priority includes an indication of: one or more target ranges; one or more target velocities; one or more target directions relative to the first sensing node; one or more safety requirements; one or more latency requirements; one or more sensing applications; or a combination thereof.

[0221] Clause 27. The method of any of clauses 24 to 26, further comprising: configuring the first sensing node with the one or more sensing-specific parameters based on a sensing stage, wherein the one or more sensing-specific parameters include at least a first sensing- specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0222] Clause 28. The method of any of clauses 24 to 27, wherein receiving an indication of one or more failure events from at least the first sensing node comprises receiving an indication of a consistent failure event based on at least a first failure event of the one or more failure events detected at the first sensing node.

[0223] Clause 29. A sensing node, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: detect one or more failure events based on one or more sensing-specific parameters; identify, based at least on the one or more detected failure events, a consistent failure event; and in response to identifying the consistent failure event, perform at least one action.

[0224] Clause 30. The sensing node of clause 29, wherein the one or more sensing-specific parameters include a consistent failure event threshold, and wherein the one or more processors, either alone or in combination, are further configured to: increment a failure event counter in response to detecting the one or more failure events; and identify the consistent failure event based on comparing a value of the failure event counter to the consistent failure event threshold.

[0225] Clause 31. The sensing node of clause 30, wherein the sensing-specific parameters include a failure event reset timer duration for a failure event reset timer, and wherein the 63 QC2403178WOQualcomm Ref. No.2403178WO 64 one or more processors, either alone or in combination, are further configured to: initiate the failure event reset timer in response to detecting a first failure event of the one or more failure events; and reset the failure event counter in response to expiration of the failure event reset timer prior to detecting a second subsequent failure event.

[0226] Clause 32. The sensing node of any of clauses 29 to 31, wherein the one or more processors, either alone or in combination, are further configured to: cancel the consistent failure event in response to expiration of a cancelation timer, performance of one or more actions, an indication from a network entity, an indication from another sensing node, or a combination thereof.

[0227] Clause 33. The sensing node of any of clauses 29 to 32, wherein the one or more processors, either alone or in combination are further configured to: detect the one or more failure events based on one or more sensing measurements in one or more beam directions; and calculate one or more sensing metrics based on a plurality of the one or more sensing measurements, wherein the one or more sensing metrics comprise an average of the plurality of sensing measurements, a maximum of the plurality of sensing measurements, a minimum of the plurality of sensing measurements, at least one difference between consecutive sensing measurements for the plurality of sensing measurements, or a combination thereof.

[0228] Clause 34. The sensing node of any of clauses 29 to 33, wherein the one or more failure events comprises a mis-detection event, a missed detection event, or both, and wherein the sensing-specific parameters include one or more detection-based failure thresholds, one or more detection-based failure counters, or a combination thereof.

[0229] Clause 35. The sensing node of clause 34, wherein the one or more processors, either alone or in combination, are further configured to: calculate a probability of mis-detection for one or more targets, a number of mis-detections for the one or more targets, a probability of missed detection for the one or more targets, a number of missed detections for the one or more targets, or a combination thereof based on one or more sensing measurements; and wherein, to detect the one or more failure events, the one or more processors, either alone or in combination, are configured to: compare the probability of mis-detection for the one or more targets, the probability of missed detection for the one or more targets, or both to at least one of the one or more detection-based failure thresholds; compare the number of mis-detections for the one or more targets, the number 64 QC2403178WOQualcomm Ref. No.2403178WO 65 of missed detections for the one or more targets, or both to at least one of the one or more detection-based failure counters; or a combination thereof.

[0230] Clause 36. The sensing node of any of clauses 29 to 35, wherein the one or more failure events comprise at least one false alarm failure event and wherein the sensing-specific parameters include one or more false alarm thresholds, one or more false alarm counters, or a combination thereof.

[0231] Clause 37. The sensing node of clause 36, wherein the one or more processors, either alone or in combination, are further configured to: calculate a probability of a false alarm or a number of false alarms or a combination thereof based on one or more sensing measurements; and wherein, to detect the one or more failure events, the one or more processors, either alone or in combination, are configured to compare the probability of a false alarm to at least one false alarm threshold of the one or more false alarm thresholds, compare the number of false alarms to at least one false alarm counter of the one or more false alarm counters, or both.

[0232] Clause 38. The sensing node of any of clauses 29 to 37, wherein the one or more failure events comprises at least one noise-based failure event and wherein the sensing-specific parameters include one or more noise-based thresholds, and wherein the one or more processors, either alone or in combination, are further configured to: calculate a noise level associated with a radar image based on one or more sensing measurements, wherein the noise level associated with the radar image comprises a noise level of a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or a combination thereof; and wherein, to detect the at least one noise-based failure event, the one or more processors, either alone or in combination, are configured to compare the noise level associated with the radar image to at least one noise-based threshold of the one or more noise-based thresholds.

[0233] Clause 39. The sensing node of any of clauses 29 to 38, wherein the one or more sensing- specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0234] Clause 40. The sensing node of clause 39, wherein the first sensing stage is a scanning stage and the second different sensing stage is a tracking stage. 65 QC2403178WOQualcomm Ref. No.2403178WO 66

[0235] Clause 41. The sensing node of clause 40, wherein the one or more sensing-specific parameters further include at least a third sensing-specific parameter for the particular sensing metric associated with a third different sensing stage, and wherein the third different sensing stage is a different scanning stage.

[0236] Clause 42. The sensing node of any of clauses 40 to 41, wherein the particular sensing metric is a false alarm sensing metric, and wherein: the first sensing-specific parameter is a first false alarm failure threshold, a first false alarm failure count, a first false alarm failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second false alarm failure threshold more sensitive than the first false alarm failure threshold, a second false alarm failure count more sensitive than the first false alarm failure count, a second false alarm failure timer duration more sensitive than the first false alarm failure timer duration, or a combination thereof.

[0237] Clause 43. The sensing node of any of clauses 40 to 42, wherein the particular sensing metric is a measurement accuracy sensing metric, and wherein: the first sensing-specific parameter is a first measurement accuracy failure threshold, a first measurement accuracy failure count, a first measurement accuracy failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second measurement accuracy failure threshold more sensitive than the first measurement accuracy failure threshold, a second measurement accuracy failure count more sensitive than the first measurement accuracy failure count, a second measurement accuracy failure timer duration more sensitive than the first measurement accuracy timer failure duration, or a combination thereof.

[0238] Clause 44. The sensing node of any of clauses 40 to 43, wherein the particular sensing metric is a detection-based sensing metric, and wherein: the first sensing-specific parameter is a first detection-based failure threshold, a first detection-based failure count, a first detection-based failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second detection-based failure threshold less sensitive than the first detection-based failure threshold, a second detection-based failure count less sensitive than the first detection-based failure count, a second detection-based failure timer duration less sensitive than the first detection-based failure timer duration, or a combination thereof. 66 QC2403178WOQualcomm Ref. No.2403178WO 67

[0239] Clause 45. The sensing node of any of clauses 40 to 44, wherein the particular sensing metric is a noise-related sensing metric, and wherein: the first sensing-specific parameter is a first noise-related failure threshold, a first noise-related failure count, a first noise- related failure timer duration, or a combination thereof; and the second different sensing- specific parameter is a second noise-related failure threshold more sensitive than the first noise-related failure threshold, a second noise-related failure count more sensitive than the first noise-related failure count, a second noise-related failure timer duration more sensitive than the first noise-related failure timer duration, or a combination thereof.

[0240] Clause 46. The sensing node of any of clauses 29 to 45, wherein one or more sensing- specific parameters include at least one parameter based at least in part on a sensing priority.

[0241] Clause 47. The sensing node of clause 46, wherein the sensing priority is associated with a sensing application and is based at least in part on a latency requirement of the sensing application, a safety requirement of the sensing application, or both.

[0242] Clause 48. The sensing node of any of clauses 46 to 47, wherein the sensing priority is based at least in part on a range, a velocity, a direction, or a combination thereof to be sensed.

[0243] Clause 49. The sensing node of any of clauses 29 to 48, wherein, to perform at least one action, the one or more processors, either alone or in combination, are configured to: request one or more modified sensing transmission parameters.

[0244] Clause 50. The sensing node of clause 49, wherein, to request the one or more modified sensing transmission parameters, the one or more processors, either alone or in combination, are further configured to: transmit a scheduling request to a network entity; and receive, via the one or more transceivers, configuration information from the network entity, the configuration information configuring the sensing node to: transmit sensing signals with one or more modified waveform parameters, modified transmit power, modified transmit direction, modified frequency resources, or a combination thereof; retransmit at least some sensing transmissions; drop one or more scheduled sensing transmissions; or a combination thereof.

[0245] Clause 51. The sensing node of any of clauses 29 to 50, wherein, to identify the consistent failure event based at least one of the one or more detected failure events, the one or more processors, either alone or in combination, are configured to: transmit, via the one or more QC2403178WOQualcomm Ref. No.2403178WO 68 transceivers, an indication of the at least one of the one or more detected failure events to a network entity; receive, via the one or more transceivers, an indication of the consistent failure event from the network entity; and identify the consistent failure event and the at least one action based on the indication of the consistent failure event received from the network entity.

[0246] Clause 52. A network entity, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configure the first sensing node to perform one or more actions in response to the received indication.

[0247] Clause 53. The network entity of clause 52, wherein the one or more processors, either alone or in combination, are further configured to: configure the first sensing node with the one or more sensing-specific parameters based on a first sensing priority; receive, via the one or more transceivers, an indication of a second different sensing priority from the first sensing node; and dynamically indicate at least one updated sensing-specific parameter based on the second different sensing priority.

[0248] Clause 54. The network entity of clause 53, wherein the indication of the second different sensing priority includes an indication of: one or more target ranges; one or more target velocities; one or more target directions relative to the first sensing node; one or more safety requirements; one or more latency requirements; one or more sensing applications; or a combination thereof.

[0249] Clause 55. The network entity of any of clauses 52 to 54, wherein the one or more processors, either alone or in combination, are further configured to: configure the first sensing node with the one or more sensing-specific parameters based on a sensing stage, wherein the one or more sensing-specific parameters include at least a first sensing- specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage. 68 QC2403178WOQualcomm Ref. No.2403178WO 69

[0250] Clause 56. The network entity of any of clauses 52 to 55, wherein, to receive an indication of one or more failure events from at least the first sensing node, the one or more processors, either alone or in combination, are configured to receive an indication of a consistent failure event based on at least a first failure event of the one or more failure events detected at the first sensing node.

[0251] Clause 57. A sensing node, comprising: means for detecting one or more failure events based on one or more sensing-specific parameters; means for identifying a consistent failure event based at least on the one or more detected failure events; and means for performing at least one action in response to identifying the consistent failure event.

[0252] Clause 58. The sensing node of clause 57, wherein the one or more sensing-specific parameters include a consistent failure event threshold, and further comprising: means for incrementing a failure event counter in response to detecting the one or more failure events; and means for identifying the consistent failure event based on comparing a value of the failure event counter to the consistent failure event threshold.

[0253] Clause 59. The sensing node of clause 58, wherein the sensing-specific parameters include a failure event reset timer duration for a failure event reset timer, and further comprising: means for initiating the failure event reset timer in response to detecting a first failure event of the one or more failure events; and means for resetting the failure event counter in response to expiration of the failure event reset timer prior to detecting a second subsequent failure event.

[0254] Clause 60. The sensing node of any of clauses 57 to 59, further comprising: means for canceling the consistent failure event in response to expiration of a cancelation timer, performance of one or more actions, an indication from a network entity, an indication from another sensing node, or a combination thereof.

[0255] Clause 61. The sensing node of any of clauses 57 to 60, wherein the means for detecting the one or more failure events comprises means for detecting the one or more failure events based on one or more sensing measurements in one or more beam directions, and further comprises means for calculating one or more sensing metrics based on a plurality of the one or more sensing measurements, wherein the one or more sensing metrics comprise an average of the plurality of sensing measurements, a maximum of the plurality of sensing measurements, a minimum of the plurality of sensing measurements, at least 69 QC2403178WOQualcomm Ref. No.2403178WO one difference between consecutive sensing measurements for the plurality of sensing measurements, or a combination thereof.

[0256] Clause 62. The sensing node of any of clauses 57 to 61, wherein the one or more failure events comprises a mis-detection event, a missed detection event, or both and the sensing- specific parameters include one or more detection-based failure thresholds, one or more detection-based failure counters, or a combination thereof.

[0257] Clause 63. The sensing node of clause 62, further comprising: means for calculating a probability of mis-detection for one or more targets, a number of mis-detections for the one or more targets, a probability of missed detection for the one or more targets, a number of missed detections for the one or more targets, or a combination thereof based on one or more sensing measurements; and wherein the means for detecting the one or more failure events comprises: means for comparing the probability of mis-detection for the one or more targets, the probability of missed detection for the one or more targets, or both to at least one of the one or more detection-based failure thresholds; means for comparing the number of mis-detections for the one or more targets, the number of missed detections for the one or more targets, or both to at least one of the one or more detection- based failure counters, or both.

[0258] Clause 64. The sensing node of any of clauses 57 to 63, wherein the one or more failure events comprise at least one false alarm failure event and wherein the sensing-specific parameters include one or more false alarm thresholds, one or more false alarm counters, or a combination thereof.

[0259] Clause 65. The sensing node of clause 64, further comprising: means for calculating a probability of a false alarm or a number of false alarms or a combination thereof based on one or more sensing measurements; and wherein the means for detecting the one or more failure events comprises means for comparing the probability of a false alarm to at least one false alarm threshold of the one or more false alarm thresholds, comparing the number of false alarms to at least one false alarm counter of the one or more false alarm counters, or both.

[0260] Clause 66. The sensing node of any of clauses 57 to 65, wherein the one or more failure events comprises at least one noise-based failure event and wherein the sensing-specific parameters include one or more noise-based thresholds, and further comprising: means for calculating a noise level associated with a radar image based on one or more sensing 70 QC2403178WOQualcomm Ref. No.2403178WO measurements, wherein the noise level associated with the radar image comprises a noise level of a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or a combination thereof; and wherein the means for detecting the at least one noise-based failure event comprises means for comparing the noise level associated with the radar image to at least one noise-based threshold of the one or more noise-based thresholds.

[0261] Clause 67. The sensing node of any of clauses 57 to 66, wherein the one or more sensing- specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0262] Clause 68. The sensing node of clause 67, wherein the first sensing stage is a scanning stage and the second different sensing stage is a tracking stage.

[0263] Clause 69. The sensing node of clause 68, wherein the one or more sensing-specific parameters further include at least a third sensing-specific parameter for the particular sensing metric associated with a third different sensing stage, and wherein the third different sensing stage is a different scanning stage.

[0264] Clause 70. The sensing node of any of clauses 68 to 69, wherein the particular sensing metric is a false alarm sensing metric, and wherein: the first sensing-specific parameter is a first false alarm failure threshold, a first false alarm failure count, a first false alarm failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second false alarm failure threshold more sensitive than the first false alarm failure threshold, a second false alarm failure count more sensitive than the first false alarm failure count, a second false alarm failure timer duration more sensitive than the first false alarm failure timer duration, or a combination thereof.

[0265] Clause 71. The sensing node of any of clauses 68 to 70, wherein the particular sensing metric is a measurement accuracy sensing metric, and wherein: the first sensing-specific parameter is a first measurement accuracy failure threshold, a first measurement accuracy failure count, a first measurement accuracy failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second measurement accuracy failure threshold more sensitive than the first measurement accuracy failure threshold, a second measurement accuracy failure count more sensitive than the first 71 QC2403178WOQualcomm Ref. No.2403178WO measurement accuracy failure count, a second measurement accuracy failure timer duration more sensitive than the first measurement accuracy timer failure duration, or a combination thereof.

[0266] Clause 72. The sensing node of any of clauses 68 to 71, wherein the particular sensing metric is a detection-based sensing metric, and wherein: the first sensing-specific parameter is a first detection-based failure threshold, a first detection-based failure count, a first detection-based failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second detection-based failure threshold less sensitive than the first detection-based failure threshold, a second detection-based failure count less sensitive than the first detection-based failure count, a second detection-based failure timer duration less sensitive than the first detection-based failure timer duration, or a combination thereof.

[0267] Clause 73. The sensing node of any of clauses 68 to 72, wherein the particular sensing metric is a noise-related sensing metric, and wherein: the first sensing-specific parameter is a first noise-related failure threshold, a first noise-related failure count, a first noise- related failure timer duration, or a combination thereof; and the second different sensing- specific parameter is a second noise-related failure threshold more sensitive than the first noise-related failure threshold, a second noise-related failure count more sensitive than the first noise-related failure count, a second noise-related failure timer duration more sensitive than the first noise-related failure timer duration, or a combination thereof.

[0268] Clause 74. The sensing node of any of clauses 57 to 73, wherein one or more sensing- specific parameters include at least one parameter based at least in part on a sensing priority.

[0269] Clause 75. The sensing node of clause 74, wherein the sensing priority is associated with a sensing application and is based at least in part on a latency requirement of the sensing application, a safety requirement of the sensing application, or both.

[0270] Clause 76. The sensing node of any of clauses 74 to 75, wherein the sensing priority is based at least in part on a range, a velocity, a direction, or a combination thereof to be sensed.

[0271] Clause 77. The sensing node of any of clauses 57 to 76, wherein the means for performing at least one action comprises: means for requesting one or more modified sensing transmission parameters. 72 QC2403178WOQualcomm Ref. No.2403178WO

[0272] Clause 78. The sensing node of clause 77, wherein the means for requesting the one or more modified sensing transmission parameters comprises means for transmitting a scheduling request to a network entity, and wherein the sensing node further comprises: means for receiving configuration information from the network entity, the configuration information configuring the sensing node to: transmit sensing signals with one or more modified waveform parameters, modified transmit power, modified transmit direction, modified frequency resources, or a combination thereof; retransmit at least some sensing transmissions; drop one or more scheduled sensing transmissions; or a combination thereof.

[0273] Clause 79. The sensing node of any of clauses 57 to 78, wherein the means for identifying the consistent failure event based at least one of the one or more detected failure events comprises: means for transmitting an indication of the at least one of the one or more detected failure events to a network entity; means for receiving an indication of the consistent failure event from the network entity; and means for identifying the consistent failure event and the at least one action based on the indication of the consistent failure event received from the network entity.

[0274] Clause 80. A network entity, comprising: means for receiving an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and means for configuring the first sensing node to perform one or more actions in response to the received indication.

[0275] Clause 81. The network entity of clause 80, further comprising: means for configuring the first sensing node with the one or more sensing-specific parameters based on a first sensing priority; means for receiving an indication of a second different sensing priority from the first sensing node; and means for dynamically indicating at least one updated sensing-specific parameter based on the second different sensing priority.

[0276] Clause 82. The network entity of clause 81, wherein the indication of the second different sensing priority includes an indication of: one or more target ranges; one or more target velocities; one or more target directions relative to the first sensing node; one or more safety requirements; one or more latency requirements; one or more sensing applications; or a combination thereof. QC2403178WOQualcomm Ref. No.2403178WO 74

[0277] Clause 83. The network entity of any of clauses 80 to 82, further comprising: means for configuring the first sensing node with the one or more sensing-specific parameters based on a sensing stage, wherein the one or more sensing-specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0278] Clause 84. The network entity of any of clauses 80 to 83, wherein the means for receiving an indication of one or more failure events from at least the first sensing node comprises means for receiving an indication of a consistent failure event based on at least a first failure event of the one or more failure events detected at the first sensing node.

[0279] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sensing node, cause the sensing node to: detect one or more failure events based on one or more sensing-specific parameters; identify a consistent failure event based at least on the one or more detected failure events; and in response to identifying the consistent failure event, perform at least one action.

[0280] Clause 86. The non-transitory computer-readable medium of clause 85, wherein the one or more sensing-specific parameters include a consistent failure event threshold, and further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: increment a failure event counter in response to detecting the one or more failure events; and identify the consistent failure event based on comparing a value of the failure event counter to the consistent failure event threshold.

[0281] Clause 87. The non-transitory computer-readable medium of clause 86, wherein the sensing-specific parameters include a failure event reset timer duration for a failure event reset timer, and further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: initiate the failure event reset timer in response to detecting a first failure event of the one or more failure events; and reset the failure event counter in response to expiration of the failure event reset timer prior to detecting a second subsequent failure event.

[0282] Clause 88. The non-transitory computer-readable medium of any of clauses 85 to 87, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: cancel the consistent failure event in response to 74 QC2403178WOQualcomm Ref. No.2403178WO 75 expiration of a cancelation timer, performance of one or more actions, an indication from a network entity, an indication from another sensing node, or a combination thereof.

[0283] Clause 89. The non-transitory computer-readable medium of any of clauses 85 to 88, and further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: detect the one or more failure events further based on one or more sensing measurements in one or more beam directions; calculate one or more sensing metrics based on a plurality of the one or more sensing measurements, wherein the one or more sensing metrics comprise an average of the plurality of sensing measurements, a maximum of the plurality of sensing measurements, a minimum of the plurality of sensing measurements, at least one difference between consecutive sensing measurements for the plurality of sensing measurements, or a combination thereof.

[0284] Clause 90. The non-transitory computer-readable medium of any of clauses 85 to 89, wherein the one or more failure events comprises a mis-detection event, a missed detection event, or both and the sensing-specific parameters include one or more detection-based failure thresholds, one or more detection-based failure counters, or a combination thereof.

[0285] Clause 91. The non-transitory computer-readable medium of clause 90, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: calculate a probability of mis-detection for one or more targets, a number of mis-detections for the one or more targets, a probability of missed detection for the one or more targets, a number of missed detections for the one or more targets, or a combination thereof based on one or more sensing measurements; and wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to detect the one or more failure events comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to: compare the probability of mis-detection for the one or more targets, the probability of missed detection for the one or more targets, or both to at least one of the one or more detection- based failure thresholds; compare the number of mis-detections for the one or more targets, the number of missed detections for the one or more targets, or both to at least one of the one or more detection-based failure counters; or a combination thereof.

[0286] Clause 92. The non-transitory computer-readable medium of any of clauses 85 to 91, wherein the one or more failure events comprise at least one false alarm failure event and 75 QC2403178WOQualcomm Ref. No.2403178WO wherein the sensing-specific parameters include one or more false alarm thresholds, one or more false alarm counters, or a combination thereof.

[0287] Clause 93. The non-transitory computer-readable medium of clause 92, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: calculate a probability of a false alarm or a number of false alarms or a combination thereof based on one or more sensing measurements; and wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to detect the one or more failure events comprise computer- executable instructions that, when executed by the sensing node, cause the sensing node to compare the probability of a false alarm to at least one false alarm threshold of the one or more false alarm thresholds, compare the number of false alarms to at least one false alarm counter of the one or more false alarm counters, or both.

[0288] Clause 94. The non-transitory computer-readable medium of any of clauses 85 to 93, wherein the one or more failure events comprises at least one noise-based failure event and wherein the sensing-specific parameters include one or more noise-based thresholds, and further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: calculate a noise level associated with a radar image based on one or more sensing measurements, wherein the noise level associated with the radar image comprises a noise level of a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or a combination thereof; and compare the noise level associated with the radar image to at least one noise- based threshold of the one or more noise-based thresholds.

[0289] Clause 95. The non-transitory computer-readable medium of any of clauses 85 to 94, wherein the one or more sensing-specific parameters include at least a first sensing- specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

[0290] Clause 96. The non-transitory computer-readable medium of clause 95, wherein the first sensing stage is a scanning stage and the second different sensing stage is a tracking stage.

[0291] Clause 97. The non-transitory computer-readable medium of clause 96, wherein the one or more sensing-specific parameters further include at least a third sensing-specific 76 QC2403178WOQualcomm Ref. No.2403178WO parameter for the particular sensing metric associated with a third different sensing stage, and wherein the third different sensing stage is a different scanning stage.

[0292] Clause 98. The non-transitory computer-readable medium of any of clauses 96 to 97, wherein the particular sensing metric is a false alarm sensing metric, and wherein: the first sensing-specific parameter is a first false alarm failure threshold, a first false alarm failure count, a first false alarm failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second false alarm failure threshold more sensitive than the first false alarm failure threshold, a second false alarm failure count more sensitive than the first false alarm failure count, a second false alarm failure timer duration more sensitive than the first false alarm failure timer duration, or a combination thereof.

[0293] Clause 99. The non-transitory computer-readable medium of any of clauses 96 to 98, wherein the particular sensing metric is a measurement accuracy sensing metric, and wherein: the first sensing-specific parameter is a first measurement accuracy failure threshold, a first measurement accuracy failure count, a first measurement accuracy failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second measurement accuracy failure threshold more sensitive than the first measurement accuracy failure threshold, a second measurement accuracy failure count more sensitive than the first measurement accuracy failure count, a second measurement accuracy failure timer duration more sensitive than the first measurement accuracy timer failure duration, or a combination thereof.

[0294] Clause 100. The non-transitory computer-readable medium of any of clauses 96 to 99, wherein the particular sensing metric is a detection-based sensing metric, and wherein: the first sensing-specific parameter is a first detection-based failure threshold, a first detection-based failure count, a first detection-based failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second detection-based failure threshold less sensitive than the first detection-based failure threshold, a second detection-based failure count less sensitive than the first detection- based failure count, a second detection-based failure timer duration less sensitive than the first detection-based failure timer duration, or a combination thereof.

[0295] Clause 101. The non-transitory computer-readable medium of any of clauses 96 to 100, wherein the particular sensing metric is a noise-related sensing metric, and wherein: the 77 QC2403178WOQualcomm Ref. No.2403178WO 78 first sensing-specific parameter is a first noise-related failure threshold, a first noise- related failure count, a first noise-related failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second noise-related failure threshold more sensitive than the first noise-related failure threshold, a second noise- related failure count more sensitive than the first noise-related failure count, a second noise-related failure timer duration more sensitive than the first noise-related failure timer duration, or a combination thereof.

[0296] Clause 102. The non-transitory computer-readable medium of any of clauses 85 to 101, wherein one or more sensing-specific parameters include at least one parameter based at least in part on a sensing priority.

[0297] Clause 103. The non-transitory computer-readable medium of clause 102, wherein the sensing priority is associated with a sensing application and is based at least in part on a latency requirement of the sensing application, a safety requirement of the sensing application, or both.

[0298] Clause 104. The non-transitory computer-readable medium of any of clauses 102 to 103, wherein the sensing priority is based at least in part on a range, a velocity, a direction, or a combination thereof to be sensed.

[0299] Clause 105. The non-transitory computer-readable medium of any of clauses 85 to 104, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to perform at least one action comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to: request one or more modified sensing transmission parameters.

[0300] Clause 106. The non-transitory computer-readable medium of clause 105, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to request the one or more modified sensing transmission parameters comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to transmit a scheduling request to a network entity, and further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: receive configuration information from the network entity, the configuration information configuring the sensing node to: transmit sensing signals with one or more modified waveform parameters, modified transmit power, modified transmit direction, modified frequency resources, or a combination thereof; retransmit at least 78 QC2403178WOQualcomm Ref. No.2403178WO 79 some sensing transmissions; drop one or more scheduled sensing transmissions; or a combination thereof.

[0301] Clause 107. The non-transitory computer-readable medium of any of clauses 85 to 106, wherein the computer-executable instructions that, when executed by the sensing node, cause the sensing node to identify the consistent failure event based at least one of the one or more detected failure events comprise computer-executable instructions that, when executed by the sensing node, cause the sensing node to: transmit an indication of the at least one of the one or more detected failure events to a network entity; receive an indication of the consistent failure event from the network entity; and identify the consistent failure event and the at least one action based on the indication of the consistent failure event received from the network entity.

[0302] Clause 108. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: receive an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configure the first sensing node to perform one or more actions in response to the received indication.

[0303] Clause 109. The non-transitory computer-readable medium of clause 108, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: configure the first sensing node with the one or more sensing- specific parameters based on a first sensing priority; receive an indication of a second different sensing priority from the first sensing node; and dynamically indicate at least one updated sensing-specific parameter based on the second different sensing priority.

[0304] Clause 110. The non-transitory computer-readable medium of clause 109, wherein the indication of the second different sensing priority includes an indication of: one or more target ranges; one or more target velocities; one or more target directions relative to the first sensing node; one or more safety requirements; one or more latency requirements; one or more sensing applications; or a combination thereof.

[0305] Clause 111. The non-transitory computer-readable medium of any of clauses 108 to 110, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: configure the first sensing node with one or more sensing-specific parameters based on a sensing stage, wherein the one or more sensing- 79 QC2403178WOQualcomm Ref. No.2403178WO 80 specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a secothe nd different sensing stage.

[0306] Clause 112. The non-transitory computer-readable medium of any of clauses 108 to 111, wherein the computer-executable instructions that, when executed by the network entity, cause the network entity to receive an indication of one or more failure events from at least the first sensing node comprise computer-executable instructions that, when executed by the network entity, cause the network entity to receive an indication of a consistent failure event based on at least a first failure event of the one or more failure events detected at the first sensing node.

[0307] Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0308] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0309] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete 80 QC2403178WOQualcomm Ref. No.2403178WO 81 hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0310] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0311] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, 81 QC2403178WOQualcomm Ref. No.2403178WO 82 twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. For example, the functions, steps and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Further, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination. 82 QC2403178WO

Claims

Qualcomm Ref. No.2403178WO 83 CLAIMS What is claimed is:

1. A sensing node, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: detect one or more failure events based on one or more sensing-specific parameters; identify, based at least on the one or more detected failure events, a consistent failure event; and in response to identifying the consistent failure event, perform at least one action.

2. The sensing node of claim 1, wherein the one or more sensing-specific parameters include a consistent failure event threshold, and wherein the one or more processors, either alone or in combination, are further configured to: increment a failure event counter in response to detecting the one or more failure events; and identify the consistent failure event based on comparing a value of the failure event counter to the consistent failure event threshold.

3. The sensing node of claim 2, wherein the sensing-specific parameters include a failure event reset timer duration for a failure event reset timer, and wherein the one or more processors, either alone or in combination, are further configured to: initiate the failure event reset timer in response to detecting a first failure event of the one or more failure events; and reset the failure event counter in response to expiration of the failure event reset timer prior to detecting a second subsequent failure event. 83 QC2403178WOQualcomm Ref. No.2403178WO 84 4. The sensing node of claim 1, wherein the one or more processors, either alone or in combination, are further configured to: cancel the consistent failure event in response to expiration of a cancelation timer, performance of one or more actions, an indication from a network entity, an indication from another sensing node, or a combination thereof.

5. The sensing node of claim 1, wherein the one or more processors, either alone or in combination are further configured to: detect the one or more failure events based on one or more sensing measurements in one or more beam directions; and calculate one or more sensing metrics based on a plurality of the one or more sensing measurements, wherein the one or more sensing metrics comprise an average of the plurality of sensing measurements, a maximum of the plurality of sensing measurements, a minimum of the plurality of sensing measurements, at least one difference between consecutive sensing measurements for the plurality of sensing measurements, or a combination thereof.

6. The sensing node of claim 1, wherein the one or more failure events comprises a mis-detection event, a missed detection event, or both, and wherein the sensing-specific parameters include one or more detection-based failure thresholds, one or more detection-based failure counters, or a combination thereof.

7. The sensing node of claim 6, wherein the one or more processors, either alone or in combination, are further configured to: calculate a probability of mis-detection for one or more targets, a number of mis- detections for the one or more targets, a probability of missed detection for the one or more targets, a number of missed detections for the one or more targets, or a combination thereof based on one or more sensing measurements; and wherein, to detect the one or more failure events, the one or more processors, either alone or in combination, are configured to: 84 QC2403178WOQualcomm Ref. No.2403178WO 85 compare the probability of mis-detection for the one or more targets, the probability of missed detection for the one or more targets, or both to at least one of the one or more detection-based failure thresholds; compare the number of mis-detections for the one or more targets, the number of missed detections for the one or more targets, or both to at least one of the one or more detection-based failure counters; or a combination thereof.

8. The sensing node of claim 1, wherein the one or more failure events comprise at least one false alarm failure event and wherein the sensing-specific parameters include one or more false alarm thresholds, one or more false alarm counters, or a combination thereof.

9. The sensing node of claim 8, wherein the one or more processors, either alone or in combination, are further configured to: calculate a probability of a false alarm or a number of false alarms or a combination thereof based on one or more sensing measurements; and wherein, to detect the one or more failure events, the one or more processors, either alone or in combination, are configured to compare the probability of a false alarm to at least one false alarm threshold of the one or more false alarm thresholds, compare the number of false alarms to at least one false alarm counter of the one or more false alarm counters, or both.

10. The sensing node of claim 1, wherein the one or more failure events comprises at least one noise-based failure event and wherein the sensing-specific parameters include one or more noise-based thresholds, and wherein the one or more processors, either alone or in combination, are further configured to: calculate a noise level associated with a radar image based on one or more sensing measurements, wherein the noise level associated with the radar image comprises a noise level of a range profile of the radar image, an angle profile of the radar image, a velocity profile of the radar image, or a combination thereof; and wherein, to detect the at least one noise-based failure event, the one or more processors, either alone or in combination, are configured to compare the noise level 85 QC2403178WOQualcomm Ref. No.2403178WO 86 associated with the radar image to at least one noise-based threshold of the one or more noise-based thresholds.

11. The sensing node of claim 1, wherein the one or more sensing-specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

12. The sensing node of claim 11, wherein the first sensing stage is a scanning stage and the second different sensing stage is a tracking stage.

13. The sensing node of claim 12, wherein the one or more sensing-specific parameters further include at least a third sensing-specific parameter for the particular sensing metric associated with a third different sensing stage, and wherein the third different sensing stage is a different scanning stage.

14. The sensing node of claim 12, wherein the particular sensing metric is a false alarm sensing metric, and wherein: the first sensing-specific parameter is a first false alarm failure threshold, a first false alarm failure count, a first false alarm failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second false alarm failure threshold more sensitive than the first false alarm failure threshold, a second false alarm failure count more sensitive than the first false alarm failure count, a second false alarm failure timer duration more sensitive than the first false alarm failure timer duration, or a combination thereof.

15. The sensing node of claim 12, wherein the particular sensing metric is a measurement accuracy sensing metric, and wherein: 86 QC2403178WOQualcomm Ref. No.2403178WO 87 the first sensing-specific parameter is a first measurement accuracy failure threshold, a first measurement accuracy failure count, a first measurement accuracy failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second measurement accuracy failure threshold more sensitive than the first measurement accuracy failure threshold, a second measurement accuracy failure count more sensitive than the first measurement accuracy failure count, a second measurement accuracy failure timer duration more sensitive than the first measurement accuracy timer failure duration, or a combination thereof.

16. The sensing node of claim 12, wherein the particular sensing metric is a detection-based sensing metric, and wherein: the first sensing-specific parameter is a first detection-based failure threshold, a first detection-based failure count, a first detection-based failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second detection-based failure threshold less sensitive than the first detection-based failure threshold, a second detection-based failure count less sensitive than the first detection-based failure count, a second detection-based failure timer duration less sensitive than the first detection-based failure timer duration, or a combination thereof.

17. The sensing node of claim 12, wherein the particular sensing metric is a noise- related sensing metric, and wherein: the first sensing-specific parameter is a first noise-related failure threshold, a first noise-related failure count, a first noise-related failure timer duration, or a combination thereof; and the second different sensing-specific parameter is a second noise-related failure threshold more sensitive than the first noise-related failure threshold, a second noise- related failure count more sensitive than the first noise-related failure count, a second noise-related failure timer duration more sensitive than the first noise-related failure timer duration, or a combination thereof. 87 QC2403178WOQualcomm Ref. No.2403178WO 88 18. The sensing node of claim 1, wherein one or more sensing-specific parameters include at least one parameter based at least in part on a sensing priority.

19. The sensing node of claim 18, wherein the sensing priority is associated with a sensing application and is based at least in part on a latency requirement of the sensing application, a safety requirement of the sensing application, or both.

20. The sensing node of claim 18, wherein the sensing priority is based at least in part on a range, a velocity, a direction, or a combination thereof to be sensed.

21. The sensing node of claim 1, wherein, to perform at least one action, the one or more processors, either alone or in combination, are configured to: request one or more modified sensing transmission parameters.

22. The sensing node of claim 21, wherein, to request the one or more modified sensing transmission parameters, the one or more processors, either alone or in combination, are further configured to: transmit a scheduling request to a network entity; and receive, via the one or more transceivers, configuration information from the network entity, the configuration information configuring the sensing node to: transmit sensing signals with one or more modified waveform parameters, modified transmit power, modified transmit direction, modified frequency resources, or a combination thereof; retransmit at least some sensing transmissions; drop one or more scheduled sensing transmissions; or a combination thereof.

23. The sensing node of claim 1, wherein, to identify the consistent failure event based at least one of the one or more detected failure events, the one or more processors, either alone or in combination, are configured to: transmit, via the one or more transceivers, an indication of the at least one of the one or more detected failure events to a network entity; 88 QC2403178WOQualcomm Ref. No.2403178WO 89 receive, via the one or more transceivers, an indication of the consistent failure event from the network entity; and identify the consistent failure event and the at least one action based on the indication of the consistent failure event received from the network entity.

24. A network entity, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing-specific parameters and one or more sensing measurements of the first sensing node; and configure the first sensing node to perform one or more actions in response to the received indication.

25. The network entity of claim 24, wherein the one or more processors, either alone or in combination, are further configured to: configure the first sensing node with the one or more sensing-specific parameters based on a first sensing priority; receive, via the one or more transceivers, an indication of a second different sensing priority from the first sensing node; and dynamically indicate at least one updated sensing-specific parameter based on the second different sensing priority.

26. The network entity of claim 25, wherein the indication of the second different sensing priority includes an indication of: one or more target ranges; one or more target velocities; one or more target directions relative to the first sensing node; 89 QC2403178WOQualcomm Ref. No.2403178WO 90 one or more safety requirements; one or more latency requirements; one or more sensing applications; or a combination thereof.

27. The network entity of claim 24, wherein the one or more processors, either alone or in combination, are further configured to: configure the first sensing node with the one or more sensing-specific parameters based on a sensing stage, wherein the one or more sensing-specific parameters include at least a first sensing-specific parameter for a particular sensing metric associated with a first sensing stage and a second different sensing-specific parameter for the particular sensing metric associated with a second different sensing stage.

28. The network entity of claim 24, wherein, to receive an indication of one or more failure events from at least the first sensing node, the one or more processors, either alone or in combination, are configured to receive an indication of a consistent failure event based on at least a first failure event of the one or more failure events detected at the first sensing node.

29. A method of wireless communication at a sensing node, comprising: detecting one or more failure events based on one or more sensing-specific parameters; based at least on the one or more detected failure events, identifying a consistent failure event; and in response to identifying the consistent failure event, performing at least one action.

30. A method of communication at a network entity comprising: receiving an indication of one or more failure events from at least a first sensing node, wherein the one or more failure events are detected based on one or more sensing- 90 QC2403178WOQualcomm Ref. No.2403178WO 91 specific parameters and one or more sensing measurements of the first sensing node; and configuring the first sensing node to perform one or more actions in response to the received indication. 91 QC2403178WO

Images