Dynamic switching of data transfer representation for sensing

Abstract

A method of wireless communication performed by a sensing node comprises sending, to a network entity, a list of data representation types supported by the sensing node; receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtaining one or more measurements of one or more reference signals; and sending, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

Description

Qualcomm Ref. No. 2406282WO1 / 94DYNAMIC SWITCHING OF DATA TRANSFER REPRESENTATION FOR SENSINGTECHNICAL 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)), RF sensing, and other technical enhancements. These enhancements, as well as the use of higher frequency bands, enable improved RF sensing and 5G-based 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 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 theQC2406282WOQualcomm Ref. No. 2406282WO2 / 94scope 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 performed by a sensing node includes sending, to a network entity, a list of data representation types supported by the sensing node; receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtaining one or more measurements of one or more reference signals; and sending, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0006] In an aspect, a method of w i re less communication performed by a network entity includes receiving, from a sensing node, a list of data representation types supported by the sensing node; sending, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receiving, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types,

[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: send, via the one or more transceivers, to a network entity, a list of data representation types supported by the sensing node; receive, via the one or more transceivers, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtain one or more measurements of one or more reference signals; and send, via the one or more transceivers, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[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 andQC2406282WOQualcomm Ref. No. 2406282WO3 / 94the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, from a sensing node, a list of data representation types supported by the sensing node; send, via the one or more transceivers, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receive, via the one or more transceivers, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0009] In an aspect, a sensing node includes means for sending, to a network entity, a list of data representation types supported by the sensing node; means for receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; means for obtaining one or more measurements of one or more reference signals; and means for sending, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0010] In an aspect, a netw ork entity includes means for receiving, from a sensing node, a list of data representation types supported by the sensing node; means for sending, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; means for receiving, from the sensing node a measurement report indicating one or more measurements, w herein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[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: send, to a network entity, a list of data representation types supported by the sensing node; receive, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtain one or more measurements of one or more reference signals; and send, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.QC2406282WOQualcomm Ref. No. 2406282WO4 / 94

[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, from a sensing node, a list of data representation types supported by the sensing node; send, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receive, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

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

[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 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) capability transfer procedure, assistance data transfer procedure, and location information transfer procedure between a target device and a location server, according to aspects of the disclosure.QC2406282WOQualcomm Ref. No. 2406282WO5 / 94

[0021] FIG. 7 illustrates an example of integrated sensing and communication (ISAC), in accordance with aspects of the disclosure.

[0022] FIG. 8 illustrates various types of data representation types (DRTs), in accordance with aspects of the disclosure.

[0023] FIG. 9 illustrates a call flow diagram for configuring, reconfiguring, activating, and / or deactivating one or more DRTs, in accordance with aspects of the disclosure.

[0024] FIGS. 10A and 10B illustrate example information elements (IES) in accordance with aspects of the disclosure.

[0025] FIGS. 11 and 12 illustrate example methods of wireless communication, according to aspects of the disclosure.DETAILED DESCRIPTION

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

[0027] Various aspects relate generally to wireless communication. Some aspects more specifically relate to indication of sensing node support for DRTs. In some examples, a sensing node (e.g., a user equipment (UE) or transmission-reception point (TRP)) sends, to a network entity, a list of DRTs supported by the sensing node. In some examples the network entity sends, to the sensing node, a configuration indicating one or more DRTs from the list of DRTs, In some examples, the sensing node obtains one or more measurements of one or more reference signals and sends, to the network entity, a measurement report indicating the one or more measurements. The one or more measurements are formatted, by the sensing node, according to at least one DRT of the one or more configured DRTs.

[0028] 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 indicating support for particular DRTs, the sensing node can ensure that it is configured with support DRTs, and thereby avoid malfunction or irresponsiveness to a network instruction. In some examples, a network entity can dynamically configure and / or activateQC2406282WOQualcomm Ref. No. 2406282WO6 / 94one or more particular DRTs that are supported by the sensing node, thereby improving network efficiency in response to, for example, evolving sensing requirements and / or emerging network conditions.

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

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

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

[0032] 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,QC2406282WOQualcomm Ref. No. 2406282WO7 / 94wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications netw ork. 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.

[0033] A base station may operate according to one of several RATs in communicati on 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.

[0034] The term “base station” may refer to a single phy sical 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 antennaQC2406282WOQualcomm Ref. No. 2406282WO8 / 94of 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.

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

[0036] 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 tire 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.

[0037] 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 baseQC2406282WOQualcomm Ref. No. 2406282WO9 / 94stations (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.

[0038] 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, 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 showm via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.

[0039] 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 connectivity7), 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 wdred or w ireless.QC2406282WOQualcomm Ref. No. 2406282WO10 / 94

[0040] 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 loT (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 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.

[0041] 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 (IleNBs), which may provide service to a restricted group knowm as a closed subscriber group (CSG).

[0042] The communication links 120 betw een 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,QC2406282WOQualcomm Ref. No. 2406282WO11 / 94including 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).

[0043] Tire 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.

[0044] Tire 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 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®.

[0045] Tire 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.QC2406282WOQualcomm Ref. No. 2406282WO12 / 94Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0046] 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 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 cancelling to suppress radiation in undesired directions.

[0047] 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 isQC2406282WOQualcomm Ref. No. 2406282WO13 / 94QCL 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.

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

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

[0050] 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 tire 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.

[0051] 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 thanQC2406282WOQualcomm Ref. No. 2406282WO14 / 946 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.

[0052] 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), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0053] 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 FR.5, or may be within the EHF band.

[0054] 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 aQC2406282WOQualcomm Ref. No. 2406282WO15 / 94carrier 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, lire 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 earner,” “carrier frequency,” and the like can be used interchangeably.

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

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

[0057] 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 coreQC2406282WOQualcomm Ref. No. 2406282WO16 / 94cellular (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 communications are carried out between SL-UEs without the involvement of a base station 102.

[0058] 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.1 lx WLAN technologies generally referred to as “Wi-Fi.” Example systems of this ty pe include different vanants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.QC2406282WOQualcomm Ref. No. 2406282WO17 / 94

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

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

[0061] 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 Multifunctional 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.QC2406282WOQualcomm Ref. No. 2406282WO18 / 94

[0062] In an aspect, SVs 112 may additionally or alternatively be part of one or more nonterrestrial 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.

[0063] 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 LIE 190 may indirectly obtain cellular 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 LEE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on.

[0064] 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)QC2406282WOQualcomm Ref. No. 2406282WO19 / 94gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0065] 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. Tire 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).

[0066] FIG. 2B illustrates another example wdreless 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. Tire 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 tire AMF 264 also includes locationQC2406282WOQualcomm Ref. No. 2406282WOiservices management for regulatory’ sendees, 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.

[0067] 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, 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 SUP 272.

[0068] 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 Nil interface.

[0069] 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 (notQC2406282WOQualcomm Ref. No. 2406282WO21 / 94illustrated). 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 cany’ voice and / or data like the transmission control protocol (TCP) and / or IP).

[0070] 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, lire 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 modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.

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

[0072] 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 thatQC2406282WOQualcomm Ref. No. 2406282WOurngenerally 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 “Fl” 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.

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

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

[0075] 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-RANQC2406282WOQualcomm Ref. No. 2406282WO23 / 94(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.

[0076] 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 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 Fl 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.

[0077] Each of the units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, tire 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.QC2406282WOQualcomm Ref. No. 2406282WO24 / 94

[0078] 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 El 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.

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

[0080] 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) 285QC2406282WOQualcomm Ref. No. 2406282WO25 / 94 in a cloud-based RAN architecture, such as a vRAN architecture.[0081J 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 01 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 02 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, tire SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly w'ith one or more RUs 287 via an 01 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0082] 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 Al 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.

[0083] 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-networkQC2406282WOQualcomm Ref. No. 2406282WO26data 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 01) or via creation of RAN management policies (such as Al policies).

[0084] 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 tire 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 5GC 210 / 260 infrastructure depicted in FIGS. 2 A 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.). Tire 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.

[0085] 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 andQC2406282WOQualcomm Ref. No. 2406282WOiiencoding 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.

[0086] 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 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®, PC.5, 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.

[0087] 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 334QC2406282WOQualcomm Ref. No. 2406282WO28 / 94. 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,

[0088] 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 System (QZSS) signals, etc. Where the satellite signal receiver(s) 332 and 372 are nonterrestrial 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.

[0089] 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 forQC2406282WOQualcomm Ref. No. 2406282WO29transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitters) 334 and 374 may request information and operations as appropriate from the other systems.

[0090] 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 backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0091] 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.,QC2406282WOQualcomm Ref. No. 2406282WOWWAN 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.

[0092] 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 base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

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

[0094] 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 memory7device), 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 348, 388, and 398, respectively. Tire sensing component 348, 388,QC2406282WOQualcomm Ref. No. 2406282WO31 / 94and 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 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 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 348, which may be, for example, part of the one or more WWAN 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 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 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.

[0095] 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.QC2406282WOQualcomm Ref. No. 2406282WO32 / 94

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

[0097] 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 (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.

[0098] The transmitter 354 and the receiver 352 may implement Layer-1 (LI) 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 parallelQC2406282WOQualcomm Ref. No. 2406282WO33streams. 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.

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

[0100] 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.QC2406282WOQualcomm Ref. No. 2406282WO34 / 94

[0101] 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., M1B, 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 MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

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

[0103] 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,

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

[0105] 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. InQC2406282WOQualcomm Ref. No. 2406282WO35 / 94particular, 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 LIE 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 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.

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

[0107] 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 tire 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 codeQC2406282WOQualcomm Ref. No. 2406282WO36and / 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 348, 388, and 398, etc.

[0108] 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).[01091 Wireless communication signals (e.g., radio frequency (RF) signals configured to carry orthogonal frequency division multiplexing (OFDM) 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 “wireless sensing”). Using wireless communication signals for environment sensing can be regarded as consumer-level wireless sensing 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.

[0110] 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 asQC2406282WOQualcomm Ref. No. 2406282WO37 / 94human 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.

[0111] 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 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)). Tire 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.).

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

[0113] 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) ofQC2406282WOQualcomm Ref. No. 2406282WO38 / 94the 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.

[0114] 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-sight (LOS) path (i.e., the shortest path between the transmitter and the receiver). Later clusters of channel taps are considered to have reflected off objects between the transmitter and the receiver and therefore to have followed non-LOS (NLOS) paths between the transmitter and the receiver.

[0115] 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, tire 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).

[0116] Based on the ToA of tire 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 tire 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, anQC2406282WOQualcomm Ref. No. 2406282WO39application 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.

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

[0118] Like conventional wireless sensing, 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 tire design of the reference signal.

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

[0120] 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 tire UE 504. At stage 520, the UE 504 provides its sensing capabilities to the sensing server 570.

[0121] 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. 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 forQC2406282WOQualcomm Ref. No. 2406282WO40 / 94sensing 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.

[0122] 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 the measurements, or any sensing results determined from the measurements, to the sensing server 570.

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

[0124] Long-Term Evolution (LTE) positioning protocol (LPP) is used point-to-point between a location server (e.g., LMF 270) and a target device (e.g., a UE) in order to position the target device using position-related measurements obtained by one or more reference sources (physical entities or parts of physical entities that provide signals that can be measured by a target device in order to obtain the location of the target device). An LPP session is used between a location server and a target device in order to obtain location- related measurements or a location estimate or to transfer assistance data. Currently, a single LPP session is used to support a single location request and multiple LPP sessions can be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions (or procedures), with each LPP transaction performing a single operation (capability exchange, assistance data transfer, or location information transfer). Each LPP transaction involves the exchange of one or more LPP messages between the location server and the target device. The general format of an LPP message consists of a set of common fields followed by a body. The body (which may be empty) contains information specific to a particular message type. Each message type contains information specific to one or more positioning methods and / or information common to all positioning methods.

[0125] An LPP session generally includes at least a capability transfer or indication procedure, an assistance data transfer or delivery procedure, and a location information transfer or delivery procedure. FIG. 6 illustrates an example LPP capability transfer procedure 610,QC2406282WOQualcomm Ref. No. 2406282WO41 / 94LPP assistance data transfer procedure 630, and LPP location information transfer procedure 650 between a target device (labeled “Target”) and a location server (labeled “Server”), according to aspects of the disclosure.

[0126] The purpose of an LPP capability transfer procedure 610 is to enable the transfer of capabilities from the target device (e.g., a UE 204) to the location server (e.g., an LMF 270). Capabilities in this context refer to positioning and protocol capabilities related to LPP and the positioning methods supported by LPP. In the LPP capability transfer procedure 610, the location server (e.g., an LMF 270) indicates the types of capabilities needed from the target device (e.g., UE 204) in an LPP Request Capabilities message. The target device responds with an LPP Provide Capabilities message. The capabilities included in the LPP Provide Capabilities message should correspond to any capability types specified in the LPP Request Capabilities message. Specifically, for each positioning method for which a request for capabilities is included in the LPP Request Capabilities message, if the target device supports this positioning method, the target device includes the capabilities of the target device for that supported positioning method in the LPP Provide Capabilities message. For an LPP capability indication procedure, the target device provides unsolicited (i.e., without receiving an LPP Request Capabilities message) capabilities to the location server in an LPP Provide Capabilities message.

[0127] The purpose of an LPP assistance data transfer procedure 630 is to enable the target device to request assistance data from the location server to assist in positioning, and to enable the location server to transfer assistance data to the target device in the absence of a request. In the LPP assistance data transfer procedure 630, the target device sends an LPP Request Assistance Data message to the location server. The location server responds to the target device with an LPP Provide Assistance Data message containing assistance data. The transferred assistance data should match or be a subset of the assistance data requested in the LPP Request Assistance Data. The location server may also provide any not requested information that it considers useful to the target device. The location server may also transmit one or more additional LPP Provide Assistance Data messages to the target device containing further assistance data. For an LPP assistance data delivery procedure, the location server provides unsolicited assistance data necessary’ for positioning. The assistance data may be provided periodically or non-periodically.QC2406282WOQualcomm Ref. No. 2406282WO42 / 94

[0128] The purpose of an LPP location information transfer procedure 650 is to enable the location server to request location measurement data and / or a location estimate from the target device, and to enable the target device to transfer location measurement data and / or a location estimate to a location server in the absence of a request. In an LPP location information transfer procedure 650, the location server sends an LPP Request Location Information message to the target device to request location information, indicating the type of location information needed and potentially the associated QoS. The target device responds with an LPP Provide Location Information message to the location server to transfer location information. The location information transferred should match or be a subset of the location information requested by the LPP Request Location Information unless the location server explicitly allows additional location information. More specifically, if the requested information is compatible with the target device’s capabilities and configuration, the target device includes the requested information in an LPP Provide Location Information message. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues to process the message as if it contained only information for the supported positioning methods and handles the signaling content of the unsupported positioning methods by LPP error detection. If requested by the LPP Request Location Information message, the target device sends additional LPP Provide Location Information messages to the location server to transfer additional location information. An LPP location information delivery procedure supports the delivery of positioning estimations based on unsolicited service.

[0129] LPP also defines procedures related to error indication for when a receiving endpoint (target device or location server) receives erroneous or unexpected data or detects that certain data are missing. Specifically, when a receiving endpoint determines that a received LPP message contains an error, it can return an Error message to the transmitting endpoint indicating the error or errors and discard the received / erroneous message. If the receiving endpoint is able to determine that the erroneous LPP message is an LPP Error or Abort Message, then the receiving endpoint discards the received message without returning an Error message to the transmitting endpoint.

[0130] LPP also defines procedures related to abort indication to allow a target device or location server to abort an ongoing procedure due to some unexpected event (e.g., cancellation of a location request by an LCS client). An Abort procedure can also be used to stop anQC2406282WOQualcomm Ref. No. 2406282WO43 / 94ongoing procedure (e.g., periodic location reporting from the target device). In an Abort procedure, a first endpoint determines that procedure P must be aborted and sends an Abort message to a second endpoint carrying the transaction ID for procedure P. The second endpoint then aborts procedure P.

[0131] FIG. 7 illustrates an example of information-level fusion in a system for integrated sensing and communication (ISAC), in accordance with aspects of the disclosure.

[0132] Systems that implement ISAC may have sensing functionalities. The sensing functionalities may facilitate detection of targets, estimation of target parameters, and execution of tasks, such as object classification and tracking. Sensing may involve several network entities and / or functions, for example, transmission-reception points (TRPs), user equipments (UEs), next generation node Bs (gNBs), core network sensing functions such as a sensing function (SF), sensing management function (SeMF or SnMF), location management function (LMF), etc.

[0133] In an example, sensing data is initially collected at a sensing node. An ISAC typically comprises a plurality of sensing nodes which facilitate sensing, illustrated in FIG, 7 as a Txl 711, a Tx2 712, aTx3 713, aRxl 721, a Rx2 722, and aRx3 723. The sensing nodes may be, for example, any combination of TRPs, UEs, or other suitable devices. As shown in FIG. 7, the transmitting sensing nodes (Txl 711, Tx2 712, and Tx3 713) may transmit reference signals. One or more objects (not shown) may reflect the reference signals. Receiving sensing nodes (Rxl 721, Rx2 722, and Rx3 723) may receive and measure the reference signals transmitted by the transmitting sensing nodes. Based on a combination of measurements of direct and reflected reference signals by multiple sensing nodes, the network may detect the one or more objects and sense a position and / or velocity thereof.

[0134] Some local processing of the data may occur at the sensing node. For example, information extraction may be performed at the sensing node, illustrated in FIG. 7 as an information extraction 731 corresponding to Rxl 721, an information extraction 732 corresponding to Rx2 722, and an information extraction 733 corresponding to Rx3 723. After processing, the sensing node may transmit the measurement data to a network entity in the core network, illustrated as a sensing management function (SeMF) 740. The SeMF 740 may include a fusion center 742, a control function 744, and a component for processing of measurement reports 746. The SeMF 740 may provide sensing results (e.g., objects detected, detected object position, location, etc.) via a network exposure functionQC2406282WOQualcomm Ref. No. 2406282WO44 / 94(NEF) 750 to an application function 760. The application function 760 may feed back further instructions or requests via NEF 750.

[0135] To perform target detection and localization in the context of multiple sensing nodes, the network entity has several possible approaches.

[0136] One approach, as illustrated in FIG. 7, is information-level fusion. In accordance with information-level fusion, preliminary detection and estimation is performed at a local station (e.g., at the sensing node). The local station may make local decisions (e.g., detection status of an object '0 / 1') and perform one or more position estimates ofthe object (e.g., angle of arrival (AoA), time of arrival (TOA), etc.). The data processed by the sensing node may be transmitted to a fusion center, illustrated in FIG. 7 as fusion center 742. Fusion center 742 may perform global detection using rules like 'M out of N' and localization through pairing and triangulation ofthe extracted parameters. This approach requires relatively low computational power and transmission bandwidth between local stations and fusion center 742. However, the performance may degrade due to the simplified extraction of raw data, leading to missed detections or estimation errors at some local stations.

[0137] Another approach is signal-level fusion. In accordance with signal-level fusion, local raw observations (e.g., raw baseband echoes or likelihood values) are directly and jointly processed at the fusion center 742 for target detection and localization. By leveraging the full signal information, signal-level fusion may reduce the need for local decision fusion or target-measurement association, resulting in more robust detection and localization performance, especially in low Signal-to-Noise Ratio (SNR) scenarios. However, the volume of data to be stored and exchanged may be substantial, posing significant challenges in an ISAC system where communication constraints must be respected.

[0138] It is conceivable for various approaches to use and transmit intermediate levels of information, typically processed signals. For example, through a channel estimation process, channel impulse response (CIR) or channel frequency response (CFR) coefficients may be sent to the fusion center 742. While channel estimation may be performed altogether at the fusion center 742 by observing the received pilots, performing the estimation locally at the sensing nodes may reduce the communication exchange requirements.QC2406282WOQualcomm Ref. No. 2406282WO45 / 94

[0139] FIG. 8 illustrates a sensing data signal processing flow, in accordance with aspects of the disclosure. A sensing node (similar to Rxl 721, Rx2 722, and / or Rx3 723) may receive one or more reference signals and obtain one or more measurements thereof. Based on the one or more reference signals, the sensing node may perform an analog-to-digital conversion. From this point, there are several possible sensing data signal processing flows. Toward the top of the figure are low-level data representation types (DRTs), associated with less local computation. Toward the bottom of the figure are high-level DRTs, associated with more local computation. There may be a tradeoff between the amount of local computation and the amount of data to be transmitted. For example, if the sensing node performs very little computation, then the sensing node will attempt to provide the network entity (illustrated in FIG. 8 as an SeMF) with a large amount of data (e.g., large or more frequent reports). The amount of data can be reduced if the sensing node performs more local processing. However, local processing capabilities may be limited.

[0140] A lowest level of DRT is a data quantization DRT 801. In an example, the sensing node performs sampling and quantization of a received signal (e.g., sensing reference signal). Various techniques may be used to process the resulting data. For example, compressed sensing exploits the sparsity of the signal to acquire the signal at a lower sampling rate. Other methods use low-bit quantization to reduce complexity and power consumption at the sensing node. Power consumption of analog-to-digital converters (ADCs) in hybrid architectures is known to grow exponentially relative to the number of quantization levels, thus elevating the importance of ADC quantization. In extreme cases, sampling is done with just one bit per sample, significantly reducing the data volume to be transmitted by the sensing node. It will be understood that data quantization can be combined with other representations, such as those described below. Data quantization may be selected as DRT to be exchanged in the case of signal-level fusion, where the sensing data is sent directly to a fusion center (e.g., fusion center 742) -without performing any further local processing.

[0141] Another level of DRT is a range-angle-doppler (RAD) tensor DRT 802. RAD tensor data may include fast Fourier transform (FFT) components corresponding to range, doppler, and / or angle. Range-angle and range-doppler maps may provide a structured way toQC2406282WOQualcomm Ref. No. 2406282WO46 / 94visualize and analyze spatial and velocity information of detected targets. In the context of ISAC, these maps may be used for tasks like target detection, localization, and tracking.

[0142] Another level of DRT is a point cloud DRT 803. In an example, point clouds may be derived using peak detection of RAD tensor data. Point clouds are a versatile and widely- used DRT in various sensing applications, including LiDAR and computer vision. In the context of ISAC, point clouds may provide a spatial representation of multiple targets by capturing discrete points in a three-dimensional space. Each point in the point cloud may contain information about the target's range, velocity, azimuth angle, and elevation angle,

[0143] Other DRTs 804, including voxel grids, neural network-based representation, and parametric object-based representation (as will be discussed in greater detail below). These other types are illustrated as involving greater computation than data quantization DRT 801, RAD tensor DRT 802, and point cloud DRT 803, but it will be understood that the particular continuum illustrated in the figure may be subject to implementation. Moreover, although there are several DRTs at level 804, suggesting that they have equal computational requirements, this too may be subject to implementation. It will be understood that FIG. 8 merely illustrates one possible continuum of computational complexity, and that different DRTs may be associated with the same or different computational complexities, depending on context and choice of implementation.

[0144] Voxel grids are a DRT wherein a three-dimensional space is divided into a grid of volumetric pixels (voxels). Each voxel may store information such as occupancy, intensity, or other attributes. In an example, voxel grids may be particularly useful for representing the environment in autonomous driving and robotics applications. Voxel grids provide a structured, memory-intensive representation that facilitates algorithmic processing.

[0145] Neural network (NN) or deep learning (DL)-based DRTs can facilitate object detection and classification. Measurement data can be transformed into images or tensors that are fed into, for example, convolutional neural networks (CNNs). NN and / or DL-based DRTs may extract high-level features from raw data, which may improve the accuracy and robustness of sensing systems. Variational Auto-Encoders (VAEs) may be used to project input data into a distribution over a latent space. Other forms of NN and / or DL-based DRTs may include embeddings, feature vectors (e.g., outputs of feature extraction layers), and / or layer weights.QC2406282WOQualcomm Ref. No. 2406282WO47 / 94

[0146] Parametric object-based DRTs may be based on object segmentation over obtained point clouds, thereby conveying scene information with less data. The parametric object DRT may involve employment of clustering algorithms to separate the point cloud into groups that correspond to different environment objects, and unification of the points of each group to a compact representation, therefore unveiling the shape of each object. To describe shapes of three-dimensional objects, multiple approaches may be taken, such as polygon representations (represented as convex hulls of each point cloud group), wireframes (interconnected sets of edges), or general parametric shapes, where each shape is represented by the set of its geometric parameters (e.g., center and radius for a sphere). Accurate representation of real objects with geometrical shapes may require high computation complexity, but once a representation is obtained, it can be conveyed with a very small amount of data.

[0147] It will be understood that although six particular DRTs are illustrated in FIG. 8, the teachings of the present disclosure may be extended to any number of DRTs, including variation thereof, and those not mentioned. Moreover, although these particular DRTs are illustrated as having relatively higher or lower computation complexities as other DRTs, and relatively higher or lower compression factors as other DRTs, it will be understood that such details may vary significantly depending on context and implementation.

[0148] An ISAC architecture may support a variety of DRTs, depending on a backhaul capacity, computational capabilities at the TRPs and fusion center, and service requirements. For example, an initial description of physical objects is included in terms of point cloud, parametric shapes, and other representations. For example, backhaul capacity, computational capabilities may chain dynamically as the system load changes or multiple entities become involved in the end-to-end system. There may be need for dynamic changes to DRTs during any session (e.g., positioning session, data session, sensing session, etc.), useful to have a more effective system.

[0149] FIG. 9 illustrates a call flow diagram for configuring, reconfiguring, activating, and / or deactivating one or more DRTs, in accordance with aspects of the disclosure. The figure includes a sensing node 901, a base station 905, a fusion entity 907, and a network entity 909. Sensing node 901 may be a TRP, UE, or any other device suitable to participate in sensing (e.g., able to receive a reference signal). Sensing node 901 may correspond to any of the sensing nodes described in the present disclosure. Base station 905 may be anQC2406282WOQualcomm Ref. No. 2406282WO48 / 94eNodeB (eNB), next generation node B (gNB), or any other device suitable to provide network access to the sensing node 901. Fusion entity 907 may perform data fusion as described herein, and may correspond to any of the fusion centers or fusion entities described in the present disclosure. Network entity 909 may correspond to any of the core network sensing functions described in the present disclosure, such as a sensing function (SF), a sensing management function (SeMF or SnMF), a location management function (LMF), or any other network component that participates in sensing.

[0150] Sensing node 901 may send a list 911 to network entity 909, List 911 may be sent via base station 905 and / or fusion entity 907. List 911 may indicate (e.g., comprise one or more fields indicating) one or more DRTs supported by sensing node 901. List 911 may correspond to a particular session (e.g., sensing session, data session, positioning session, etc.) or modem function.

[0151] List 911 may be included in a message. The message may be associated with a capability exchange, assistance data exchange protocol, LTE positioning protocol (LPP), NR positioning protocol (NRPP and / or NRPPa), or any combination thereof, The message may be analogous to, for example, the message illustrated at 520 in FIG. 5, the LPP Provide Capabilities message illustrated at 610 in FIG. 6, or any combination thereof. The sending of the message may be based on receiving, by sensing node 901, a request for capabilities (not shown). The request for capabilities may be analogous to, for example, the message illustrated at 515 in FIG. 5, the LPP Request Capabilities message illustrated at 610 in FIG. 6, or any combination thereof.

[0152] Base station 905 may send a list 912 to network entity 909. Analogous to list 911, list 912 may indicate one or more DRTs supported by base station 905.

[0153] Fusion entity 907 may send a list 913 to network entity 909. Analogous to list 911, list 913 may indicate one or more DRTs supported by fusion entity 907.

[0154] The characteristics of list 911, and the manner of its sending, will be described further below. However, it will be understood that without departing from the scope of tire present disclosure, the following descriptions involving list 911 may apply equally to list 912 and / or list 913.

[0155] The list 911 may indicate one or more supported DRTs that are associated with a particular session (e.g., sensing session, data session, positioning session, etc.) or modem function.QC2406282WOQualcomm Ref. No. 2406282WO49 / 94

[0156] The list 911 may comprise, for example, one or more DRT identifiers indicating the one or more supported DRTs. The DRT identifiers may be assigned by network entity 909, preconfigured to sensing node 901, base station 905, and fusion entity 907, or assigned by sensing node 901, base station 905, or fusion entity 907. The one or more DRT identifiers may enable each DRT to uniquely identified at all entities (e.g., sensing node 901, base station 905, fusion entity 907, etc.).

[0157] The sensing node 901 may send to network entity 909 an indication (e.g., a message comprising a field that indicates) one or more other capabilities of sensing node 901, The one or more capabilities may include a data width supported by sensing node 901, a data fusion capability (e.g., an information-level fusion capability and / or a signal-level fusion capability) of sensing node 901, a reporting period of sensing node 901, a measurement period of sensing node 901, a response time of sensing node 901, or any combination thereof. The indication of support for data width, data fusion capability, etc., may be indicated at a per-device level (e.g., for the sensing node 901 generally) or at a per-DRT level (e.g., specific and potentially different formats and capabilities may be supported for each of the one or more supported DRTs).

[0158] Data width may refer to a data amount. As an example, data width may correspond to a number of bytes that sensing node 901 is able to provide. As another example, data width may correspond to a number of bytes per sample that sensing node 901 is able to provide. For example, sensing node 901 may indicate that it is able to provide one hundred bytes of data, two bytes per sample, etc.

[0159] Data fusion capability may refer to an ability of the sensing node 901 to perform data fusion. For example, sensing node 901 may perform data fusion of one or more sets of measurement data. The one or more sets of measurement data may be generated by sensing node 901 and / or received from other sensing nodes. Sensing node 901 may indicate that it supports one or more particular types of data fusion. For example, sensing node 901 may indicate that it supports information-level data fusion, signal-level data fusion capability, or both. Data fusion capability may be defined for a positioning method, a positioning function, and / or a radio resource management (RRM) function.

[0160] Reporting period may refer to how often sensing node 901 is able to provide a report. For example, reporting period may indicate an amount of time between reports. For example,QC2406282WOQualcomm Ref. No. 2406282WO50 / 94sensing node 901 may indicate that it is able to provide at least one report every five milliseconds, or every ten milliseconds, or every twenty milliseconds.

[0161] Measurement period may refer to how often sensing node 901 is able to perform measurements. For example, measurement period may indicate an amount of time between measurements (or sets of measurements). For example, sensing node 901 may indicate that it is able to provide at least one measurement (or at least one set of measurements) every five milliseconds, or every ten milliseconds, or every twenty milliseconds.

[0162] Response time may refer to how quickly sensing node 901 can format measurement data.For example, response time may indicate an amount of time to generate a data representation based on a measurement (or a set of measurements). For example, sensing node 901 may indicate that it is able to generate a data representation of a measurement (or a set of measurements) within five milliseconds, or ten milliseconds, or twenty milliseconds.

[0163] As noted above, each of the foregoing capabilities may be indicated as a general capability of sensing node 901, or as a DRT-specific capability of sensing node 901 when providing data corresponding to a specific DRT.

[0164] For example, sensing node 901 may indicate DQ FMT1, which indicates that sensing node 901 supports the provision of data of the data quantization DRT in a specific format (format one) corresponding to a first data width. Additionally or alternatively, sensing node 901 may indicate DQ FMT2, which indicates that sensing node 901 supports the provision of data of the data quantization DRT in a specific format (format two) corresponding to a second data width.

[0165] For example, sensing node 901 may support shorter reporting periods (i.e., higher reporting frequency) if less data is being reported. Accordingly, sensing node 901 may support, for example, a shorter reporting period for a high-computation, low-data DRT, relative to a low-computation, high-data DRT.

[0166] The sensing node 901 may send to network entity 909 an indication of a preference, priority and / or rank of one or more DRTs supported by sensing node 901. The indication may be provided as part of the list 911, or may be provided in the message that includes the list 911. The indication may be provided in response to a request from network entity 909 to provide an indication of preference, priority, and / or rank. In an example, sensingQC2406282WOQualcomm Ref. No. 2406282WO51 / 94node 901 may indicate that data quantization, RAD tensors, and point clouds are supported DRTs, and that RAD tensors are the preferred DRT. In another example, sensing node 901 may indicate an ordinal for each supported DRT (e.g., RAD tensors are ‘1’ most preferred, data quantization is ‘2’ second-most preferred, and point cloud is ‘3’ least preferred).

[0167] Tire sensing node 901 may send to network entity 909 an indication of a maximum number of DRTs supported by sensing node 901 (e.g., a maximum number of DRT identifiers supported by sensing node 901). Tire indication may be provided as part of the list 911, or may be provided in the message that includes the list 911.

[0168] At 920, network entity 909 determines to configure one or more DRTs. The determining at 920 may be based on list 911. For example, network entity 909 may avoid malfunction or irresponsiveness of sensing node 901 by configuring one or more DRTs that are supported by sensing node 901. List 911 indicates the DRT(s) that are supported by sensing node 901, so the determining at 920 may comprise selecting for configuration one or more DRT(s) from list 911.

[0169] Additionally or alternatively, the determining at 920 may be based on list 912 and / or list 913. For example, list 912 may indicate that base station 905 supports data fusion for data corresponding to the RAD tensor DRT. If list 911 indicates that sensing node 901 supports the RAD tensor DRT, then network entity 909 may configure sensing node 901 to provide data formatted according to the RAD tensor DRT, thereby enabling base station 905 to perform data fusion on the data received from sensing node 901.

[0170] As another example, list 913 may indicate that fusion entity 907 also supports data fusion for data corresponding to the RAD tensor DRT, Network entity’ 909 may determine to configure sensing node 901 to provide data of the RAD tensor DRT, and may further determine at 920 whether base station 905 should perform the data fusion or whether fusion entity’ 907 should perform the data fusion. The latter determination may be based on respective backhaul capacities associated with base station 905 and / or fusion entity 907, respective system loads associated with base station 905 and / or fusion entity 907, respective computation capabilities associated with base station 905 and / or fusion entity 907, service requirements of the sensing session, or any other suitable factors.

[0171] The network entity 909 may send a configuration 921 to sensing node 901. Configuration 921 may configure one or more DRTs. The one or more DRTs indicated in configurationQC2406282WOQualcomm Ref. No. 2406282WO51 / 94921 may be determined at 920. Configuration 921 may be sent via fusion entity 907 and / or base station 905. Configuration 921 may correspond to a particular session (e.g., sensing session, data session, positioning session, etc.) or modem function. Configuration 921 may be included in a message. The message may be associated with a capability exchange, assistance data exchange protocol, LPP, NRPP, NRPPa, or any combination thereof. Tire message may be analogous to, for example, the message illustrated at 525 in FIG. 5, either of the LPP Provide Assistance Data messages illustrated at 630 in FIG. 6, the LPP Request Location Information message illustrated at 650 in FIG. 6, or any combination thereof.

[0172] The network entity 909 may send a configuration to fusion entity 907 (not shown) and / or base station 905 (not shown). The configurations of the fusion entity 907 and / or the base station 905 may be analogous to configuration 921.

[0173] In an example, fusion entity 907, base station 905, and / or sensing node 901 receive one or more messages from network entity 909. The one or more messages may comprise the fusion entity configuration, the base station configuration, and / or configuration 921. In an example, fusion entity 907 relays the one or more messages, or components thereof, to base station 905 and / or sensing node 901 (e.g., via base station 905). In an example, base station 905 relays the one or more messages, or components thereof, to sensing node 901, The one or more messages may be sent and / or relayed using any suitable messaging protocol, for example, assistance data exchange protocol, LTE positioning protocol (LPP), NR positioning protocol (NRPP and / or NRPPa), or any combination thereof. In an example, sensing node 901 receives configuration 921 from base station 905 in one or more radio resource control (RRC) messages (e.g., RRC configuration messages and / or RRC reconfiguration messages).

[0174] Hie configuration 921 will be described in greater detail below. However, it will be understood that without departing from the scope of the present disclosure, the following descriptions of configuration 921 may apply equally to the configurations received by base station 905 and / or fusion entity 907.

[0175] The configuration 921 may indicate one or more configured DRTs that are associated with a particular session (e.g., sensing session, data session, positioning session, etc.) or modem function. Tire configuration 921 may comprise one or more DRT identifiers indicating the one or more configured DRTs.QC2406282WOQualcomm Ref. No. 2406282WO53 / 94

[0176] The configuration 921 may indicate one or more configuration parameters, for example, a data width configured to sensing node 901, a data fusion parameter configured to sensing node 901, a reporting period configured to sensing node 901, a measurement period configured to sensing node 901, a response time configured to sensing node 901, or any combination thereof. The configuration parameters may be configured on a perdevice basis (e.g., for the sensing node 901 generally) or on a per-DRT basis (e.g., a specific and potentially different configuration parameters for a specific DRT).

[0177] The configuration 921 may indicate a preference, priority and / or rank of the one or more configured DRTs. In an example, network entity 909 may indicate that data quantization, RAD tensors, and point clouds are configured DRTs, and that RAD tensors are the preferred DRT. In another example, network entity 909 may indicate an ordinal for each configured DRT (e.g., RAD tensors is ‘ 1 ’ most preferred, data quantization is ‘2’ second- most preferred, and point cloud is ‘3’ least preferred).

[0178] The configuration 921 may indicate one or more conditions for data formatting. The one or more conditions may be configured on a per-device basis or on a per-DRT basis,

[0179] One or more conditions may be associated with a signal-to-noise ratio (SNR), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of sensing node 901 (e.g., a cell of base station 905). For example, if cell conditions are good, then sensing node 901 may be able to transmit more data, and computational load can be offloaded to the network. Accordingly, the configuration 921 may indicate that if RSRP, for example, is above a threshold, then a high-data DRT is preferred (e.g., a data quantization type).

[0180] One or more conditions may be associated with a triggering of an event. For example, sensing node 901 may format data based on a first DRT. If a particular event is triggered, then sensing node 901 may switch to a second DRT.

[0181] One or more conditions may be associated with a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in sensing node 901. For example, if sensing node 901 has high processing capacity, then sensing node 901 may be able to process more data, resulting in a smaller report (e.g., opportunistic savings of radio resources). Accordingly, the configuration 921 may indicate that if MIPS availability is above a threshold, then a low-data DRT is preferred (e.g., a voxel grid type).QC2406282WOQualcomm Ref. No. 2406282WO54 / 94

[0182] One or more conditions may be associated with a radio resource control (RRC) state of sensing node 901. For example, if sensing node 901 is in an RRC active state, then sensing node 901 may accommodate a high-computation DRT. For example, if sensing node 901 is in an RRC inactive state or RRC idle state (e.g., a power savings state), then sensing node 901 may prefer a low-computation DRT.

[0183] One or more conditions may be associated with a power level, power consumption rate, or any combination thereof, of sensing node 901. For example, low-computation DRTs may be preferred if power resources become scarce. Alternatively, high -computation DRTs may be accommodated as the sensing node 901 recharges.

[0184] One or more conditions may be associated with one or more radio resources available to sensing node 901. For example, if sensing node 901 does not have uplink resources available, then a low-data DRT may be preferred.

[0185] One or more conditions may be associated with one or more latency requirements of sensing node 901. For example, if sensing node 901 is not able to process data in accordance with latency requirements, then a low-computation DRT may be preferred.

[0186] One or more conditions may be associated with one or more modem functions of sensing node 901. For example, if a modem function of sensing node 901 has high processing and / or memory requirements (e.g., if sensing node 901 is performing mobility measurements), then a low-computation DRT may be preferred.

[0187] One or more conditions may be associated with one or more data requirements of sensing node 901. For example, if sensing node 901 is required to send and / or receive a large quantity of data (e.g., in a carrier aggregation configuration), then a low-computation DRT may be preferred.

[0188] At 925, network entity 909 determines to activate one or more DRTs. The determining at 925 may comprise selecting for activation one or more of the configured DRTs associated with the configuration 921,

[0189] Tire network entity 909 may send an activation 926 to the sensing node 901. The activation 926 may activate one or more DRTs. The one or more DRTs indicated in activation 926 may be determined at 925. Hie activation 926 may be sent via fusion entity 907 and / or base station 905, Tire activation 926 may correspond to a particular session (e.g., sensing session, data session, positioning session, etc.) or modem function. The activation 926 may be included in a message. The message may be associated with aQC2406282WOQualcomm Ref. No. 2406282WO55 / 94capability exchange, assistance data exchange protocol, LPP, NRPP, NRPPa, or any combination thereof. The message may be analogous to, for example, the message illustrated at 525 in FIG. 5, either of the LPP Provide Assistance Data messages illustrated at 630 in FIG. 6, the LPP Request Location Information message illustrated at 650 in FIG.6, or any combination thereof,

[0190] Tire network entity 909 may send a activation to base station 905 and / or fusion entity 907 (not shown). The activations may be analogous to activation 926.

[0191] In an example, fusion entity 907, base station 905, and / or sensing node 901 receive one or more messages from network entity 909. The one or more messages may comprise the fusion entity activation, the base station activation, and / or activation 926. In an example, fusion entity 907 relays the one or more messages, or components thereof, to base station 905 and / or sensing node 901 (e.g., via base station 905), In an example, base station 905 relays the one or more messages, or components thereof, to sensing node 901. Tire one or more messages may be sent and / or relayed using any suitable messaging protocol, for example, assistance data exchange protocol, LTE positioning protocol (LPP), NR positioning protocol (NRPP and / or NRPPa), or any combination thereof. In an example, sensing node 901 receives activation 926 from base station 905 in one or more radio resource control (RRC) messages (e.g., RRC configuration messages and / or RRC reconfiguration messages), one or more medium access control (MAC) control elements, one or more downlink control information (DCIs), one or more sidelink control information (SCIs), or any combination thereof.

[0192] In an example, sensing node 901 may format data based on the one or more configured DRTs, and activation of one or more particular configured DRTs is not necessary. Additionally or alternatively, activation is implicit in configuration 921 and the separate sending of activation 926 is not necessary.

[0193] In an example, one or more configured DRTs may be deactivated (not shown). Similar to activation 926, sensing node 901 may receive an indication of deactivation of one or more DRTs in one or more RRC messages, one or more MAC control elements, one or more DCIs, one or more SCIs, or any combination thereof. Activation and deactivation may be indicated simultaneously (e.g., in a same message or by a same field). For example, activation of one DRT may indicate deactivation of a previously-active DRT.QC2406282WOQualcomm Ref. No. 2406282WO56 / 94

[0194] It will be understood that configuration and activation of one or more particular DRTs enables dynamic adjustment of data formatting. The adjustment may occur mid-session or between sessions. As a result, network entity 909 can quickly react to changing circumstances to improve network efficiency.

[0195] At 930, sensing node 901 evaluates one or more conditions. Tire one or more conditions may be received from network entity 909 in configuration 921, as noted above. The sensing node 901 may perform the evaluating at 930 based on the one or more conditions configured in the configuration 921. Additionally or alternatively, the one or more conditions may be determined by sensing node 901 (e.g., based on device-specific implementation of the sensing node 901), orthe evaluating at 930 may be omitted entirely.

[0196] At 935, sensing node 901 obtains one or more measurements. The measurements obtained at 935 may be measurements of one or more reference signals (e.g,, sensing reference signals) received by the sensing node 901. The reference signals may be configured in the configuration 921. The measurements obtained at 935 and / or the one or more reference signals may be associated with a session (e.g., a positioning session, a data session, a sensing session, etc.).

[0197] At 940, sensing node 901 formats data (e.g., measurement data associated with the one or more measurements obtained at 935) based on one or more DRTs. The one or more DRTs may be one or more configured DRTs indicated by configuration 921. Tire one or more DRTs may be one or more activated DRTs indicated by activation 926. The one or more DRTs may be determined (e.g., selected by the sensing node 901) based on one or more conditions (e.g., the one or more conditions evaluated at 930). The one or more conditions may be determined by the sensing node 901 or configured by the network entity 909 (e.g., indicated by configuration 921 and / or activation 926).

[0198] At 950, sensing node 901 performs data fusion. Support for the data fusion performed at 950 may have been indicated by sensing node 901 in list 911. If sensing node 901 is not capable of data fusion, then the data fusion at 950 may not be performed. The performing of the data fusion at 950 may be based on data fusion being configured in configuration 921 and / or activated in activation 926. Hie performing of the data fusion at 950 may be based on data fusion being configured for the DRT associated with the formatting at 940, The data fusion at 950 may fuse data associated with the obtaining at 935 and / or theQC2406282WOQualcomm Ref. No. 2406282WO57 / 94formatting at 940. Additionally or alternatively, the data fusion at 950 may fuse data obtained from another source (e.g., one or more other sensing nodes).

[0199] Sensing node 901 may send a measurement report 951. The measurement report 951 may be sent to base station 905, fusion entity 907 (e.g., via base station 905), and / or network entity 909 (e.g., via base station 905 and / or fusion entity 907),

[0200] In an example, base station 905 and / or fusion entity 907 may combine components of the measurement report 951 with one or more oilier components of one or more other measurement reports (e.g,, received from another sensing node, received from another base station, etc.). The network entity 909 may receive the combination of measurement report 951 with other data.

[0201] In an example, base station 905 and / or the fusion entity 907 may reformat components of the measurement report 951. The reformatting may be based on the base station 905 and / or the fusion entity 907 being configured to and / or activated for the reformatting. For example, sensing node 901 may provide a measurement report 951 containing data formatted in accordance with a first DRT (e.g., RAD tensor data). Base station 905 may be configured to preferentially provide data formatted in accordance w ith a second DRT (e.g., point cloud data). The base station 905 may reformat the measurement report 951 based on the second DRT and send the reformatted data to network entity 909.

[0202] In an example, base station 905 and / or the fusion entity 907 may perform data fusion on components of the measurement report 951. The data fusion may be based on the base station 905 and / or the fusion entity 907 being configured to and / or activated for the data fusion. For example, fusion entity 907 may receive measurement report 951 and / or components thereof. Fusion entity 907 may receive other measurement reports and / or components thereof (e.g., from other base stations and / or other sensing nodes). Fusion entity 907 may be configured to fuse data from measurement report 951 with other data from other measurement reports (e.g,, data of the same DRT). The network entity 909 may receive the fused data (e.g., components of the measurement report 951 fused with other components of one or more other measurement reports).

[0203] At 960, network entity 909 detects and / or senses one or more objects. The detecting at 960 may be based on the measurement report 951, components of the measurement report 951, reformatted components of the measurement report 951, fused data based on data fusion of components of the 951, or any combination thereof. The detecting at 960 mayQC2406282WOQualcomm Ref. No. 2406282WO58 / 94be based on other data associated with other sensing nodes, base stations, and / or fusion entities.

[0204] At 980, network entity 909 determines to configure, reconfigure, activate, and / or deactivate one or more DRTs. lire determining at 980 may be based on the determining at 920, the determining at 925, the measurement report 951, the detecting at 960, or any combination thereof. Tire determining at 980 may be based on one or more conditions of the network (e.g., radio resource scarcity at base station 905, computational overload at fusion entity 907, changing service requirements of sensing functionalities, etc.).

[0205] The determining at 980 may comprise, for example, determining to de-configure (e.g., release or remove the configuration of) a DRT indicated by configuration 921, determining to configure a DRT that was not previously configured in configuration 921, and / or determining to reconfigure one or more parameters associated with configuration 921.

[0206] The reconfiguring may comprise modifying a preference order of the one or more DRTs.The reconfiguring may comprise modifying a configuration parameter (e.g., data width, measurement period, etc.) at a device-level or at a DRT-level. The reconfiguring may comprise modifying one or more conditions for formatting in accordance w ith a particular DRT. Hie reconfiguring may comprise instructing the sensing node 901, base station 905, and / or fusion entity 907 to perform data fusion, or to perform data fusion on particular DRTs.

[0207] The determining at 980 may comprise, for example, determining to deactivate a DRT indicated by activation 926, and / or determining to activate a DRT that w as configured in configuration 921 and not previously activated in activation 926.

[0208] Network entity 909 may send a message 981 indicating to configure, reconfigure, activate, and / or deactivate one or more DRTs. Hie message 981 may be sent to fusion entity 907, base station 905 (e.g,, via fusion entity 907), and / or sensing node 901 (e.g., via fusion entity 907 and / or base station 905). Tire message 981 may indicate a result of the determining at 980.

[0209] In an example, the network entity 909 and / or base station 905 has a capability to request data with multiple DRT identifiers for a given function. For example, the request and / or the DRT identifiers may be associated with a session (e.g., positioning session, data session, sensing session, etc.). For example, network entity 909 can request a particularQC2406282WOQualcomm Ref. No. 2406282WO59DRT and / or indicate a particular DRT identifier and / or format (e.g., DQ FMTl indicating data quantization, format one; RAD FMT2 indicating RAD tensor data, format two).

[0210] In an example, sensing node 901 may indicate capabilities of sensing node 901 (e.g., UE capabilities) for which data representation is used for a given report type, position method, and / or sensing method.

[0211] FIG. 10A illustrates example information elements (IES) in accordance with aspects of the disclosure. As noted above, a sensing node (e.g., sensing node 901) may send an indication of one or more supported DRTs (e.g., in list 911). FIG. 10A illustrates an example of one possible data structure that could be used to convey some or all of the information included in list 911.

[0212] Tire data structure may include one or more IEs 1010. Tire one or more IEs 1010 comprise one or more fields indicating one or more DRTs supported by the sensing node. In the illustrated example, four fields respectively contain four DRT identifiers corresponding to four DRTs supported by the sensing node: ‘1’ corresponding to the data quantization DRT; ‘2’ corresponding to the RAD tensor DRT; ‘4’ corresponding to the voxel grid DRT; and ‘6’ corresponding to the parametric object DRT.

[0213] Hie one or more IEs 1010 comprise a field indicating a maximum number of DRT identifiers supported by the sensing node. In the illustrated example, the field comprises ‘3’ indicating that the sensing node supports a maximum of three DRT identifiers.

[0214] The one or more IEs 1010 may comprise one or more IEs 1012. The one or more IEs 1012 may correspond to a particular field in the one or more IEs 1010. In the illustrated example, six fields correspond to capabilities associated with the RAD tensor DRT.

[0215] The first field indicates one or more data widths that the sensing node supports when formatting data based on the RAD tensor DRT (e.g., RAD FMT1, RAD FMT2, RAD FMT3).

[0216] Tire second field indicates one or more data fusion capabilities that tire sensing node supports when formatting based on the RAD tensor DRT (e.g., information-level data fusion is supported; signal-level data fusion is supported).

[0217] The third field indicates one or more reporting periods that the sensing node supports when formatting based on the RAD tensor DRT (e.g., five milliseconds; ten milliseconds; twenty milliseconds).QC2406282WOQualcomm Ref. No. 2406282WO60 / 94

[0218] The fourth field indicates one or more measurements periods that the sensing node supports when formating based on the RAD tensor DRT (e.g., five milliseconds; ten milliseconds; twenty milliseconds).

[0219] The fifth field indicates one or more response times that the sensing node supports when formatting based on the RAD tensor DRT (e.g., five milliseconds; ten milliseconds; twenty milliseconds).

[0220] The sixth field indicates a preference of the sensing node for formatting based on the RAD tensor DRT (e.g., ‘1’ indicates first preference),

[0221] It will be understood that the sensing node may indicate capabilities corresponding to each of the other supported DRTs (data quantization, voxel grid, and parametric object) using IEs similar to the one or more IEs 1012 illustrated in FIG. 10A.

[0222] FIGS 10B illustrates example information elements (IEs) in accordance with aspects of the disclosure. As noted above, a sensing node (e.g., sensing node 901) may receive an indication of one or more configured DRTs (e.g., configuration 921). FIG. 10B illustrates an example of one possible data structure that could be used to convey some or all of the information included in configuration 921.

[0223] The data structure may include one or more IEs 1050. The one or more IEs 1050 comprise one or more fields indicating one or more DRTs configured by the network entity. In the illustrated example, three fields respectively contain three DRT identifiers corresponding to three DRTs supported by the sensing node: ‘corresponding to the data quantization DRT; ‘2’ corresponding to the RAD tensor DRT; and "6’ corresponding to the parametric object DRT.

[0224] If the sensing node indicates support for a maximum of three DRTs (as in the example of FIG. 10A), then it will be understood that the network entity may indicate a number of configured DRT s no greater than the maximum (as in the example of FIG. 10B).

[0225] If the sensing node indicates four supported DRTs (as in FIG. 10A), then it will be understood that the network entity may select the configured DRTs from among the supported DRTs (as in FIG. 10B).

[0226] The one ormore IEs 1050 may comprise one ormore IEs 1052 and one ormore IEs 1053.The one or more IEs 1052 may correspond to the configuration of the RAD tensor DRT (the second field of the one ormore IEs 1050). The one ormore IEs 1053 may correspondQC2406282WOQualcomm Ref. No. 2406282WO61 / 94to the configuration of the parametric object DRT (the third field of the one or more IES 1050).

[0227] The one or more IEs 1052 and the one or more IEs 1053 may have a similar structure to the one or more IEs 1012, described above. For example, the configuration parameters configured for the RAD tensor DRT (as in FIG. 10B) may be selected from the configuration parameters supported by the sensing node (as in FIG. 10A). Although the sensing node may support data fusion associated with the RAD tensor DRT (as in FIG. 10A), the network entity may not configure the sensing node for data fusion (as in FIG. 10B). Although the sensing node indicates a preference for the RAD tensor DRT (e.g., first preference ‘ 1’, as in FIG. 10A), the netw ork entity may indicate a different preference (e.g., second preference ‘2’, as in FIG. 10B).

[0228] The one or more IEs 1052 and the one or more IEs 1053 may further include a field that indicates one or more conditions for formatting in accordance w ith the DRT. For example, the one or more IEs 1053 indicate that the netw ork entity prefers to receive data formatted in accordance with a parametric object-based (PO) DRT (e.g., first preference ‘1’, as in FIG. 10B). The one or more IEs 1053 further indicate that the formatting based on the PO DRT may be conditional on a high processing capacity at the sensing node. For example, the one or more IEs 1053 may indicate a MIPS threshold, wherein if MIPS availability is above the MIPS threshold, the sensing node provides data formatted in accordance with the PO DRT (e.g., first preference ‘ 1’ of the network entity), and if the MIPS availability drops below the MIPS threshold, the sensing node provides data formatted in accordance with the RAD tensor DRT (e.g., second preference ‘2’ of the network entity).

[0229] FIG. 11 illustrates an example method 1100 of wireless communication, according to aspects of the disclosure. In an aspect, method 1100 may be performed by a sensing node (e.g., any of the sensing nodes, TRI’s, or UEs described herein).

[0230] At 1110, the sensing node sends, to a network entity, a list of data representation types (DRTs) supported by the sensing node. In an aspect, the sensing node may be a UE, and the operation 1110 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the one or more processors 342, memory 340, and / or sensing component 348, any or all of which may be considered means for performing this operation. In an aspect, the sensing node may be a TRP, and the operation 1110 may be performed by the one or more WWAN transceivers 350, theQC2406282WOQualcomm Ref. No. 2406282WOione or more short-range wireless transceivers 360, the one or more processors 384, memory 386, and / or sensing component 388, any or all of which may be considered means for performing this operation.

[0231] At 1120, the sensing node receives, from the network entity, a configuration indicating one or more DRTs from the list of DRTs In an aspect, the sensing node may be a UE, and the operation 1120 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the one or more processors 342, memory 340, and / or sensing component 348, any or all of which may be considered means for performing this operation. In an aspect, the sensing node may be a TRP, and the operation 1120 may be performed by the one or more WAM transceivers 350, the one or more short-range wireless transceivers 360, the one or more processors 384, memory 386, and / or sensing component 388, any or all of which may be considered means for performing this operation.

[0232] At 1130, the sensing node obtains one or more measurements of one or more reference signals. In an aspect, the sensing node may be a UE, and the operation 1130 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the one or more processors 342, memory 340, and / or sensing component 348, any or all of which may be considered means for performing this operation. In an aspect, the sensing node may be a TRP, and the operation 1130 may be performed by the one or more WWAN transceivers 350, the one or more short-range wireless transceivers 360, the one or more processors 384, memory 386, and / or sensing component 388, any or all of which may be considered means for performing this operation.

[0233] At 1140, the sensing node sends, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one DRT of the one or more DRTs. In an aspect, the sensing node may be a UE, and the operation 1140 may be performed by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, the one or more processors 342, memory 340, and / or sensing component 348, any or all of which may be considered means for performing this operation. In an aspect, the sensing node may be a TRP, and the operation 1140 may be performed by the one or more WAN transceivers 350, the one or more short-range wireless transceivers 360, the one or more processorsQC2406282WOQualcomm Ref. No. 2406282WO63 / 94384, memory 386, and / or sensing component 388, any or all of which may be considered means for performing this operation.

[0234] FIG. 12 illustrates an example method 1200 of communication, according to aspects of the disclosure. In an aspect, method 1200 may be performed by a network entity (e.g., any of the network entities, sensing functions, or sensing management functions described herein).

[0235] At 1210, the network entity receives, from a sensing node, a list of data representation types (DRTs) supported by the sensing node. In an aspect, operation 1210 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 for performing this operation.

[0236] At 1220, the network entity sends, to the sensing node, a configuration indicating one or more DRTs from the list of DRTs. In an aspect, operation 1220 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 for performing this operation.

[0237] At 1230, the network entity receives, from the sensing node, a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one DRT of the one or more DRTs. In an aspect, operation 1230 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 for performing this operation.

[0238] As will be appreciated, a technical advantage of the methods 1100, 1200 is that a network entity can dynamically configure and / or activate one or more particular DRTs that are supported by the sensing node, thereby improving network efficiency in response to, for example, evolving sensing requirements and / or emerging network conditions.

[0239] 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 separateQC2406282WOQualcomm Ref. No. 2406282WO64 / 94example. 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.

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

[0241] Clause 1. A method of wireless communication performed by a sensing node, comprising:sending, to a network entity, a list of data representation types supported by the sensing node; receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtaining one or more measurements of one or more reference signals; and sending, to tlie network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0242] Clause 2. The method of clause 1, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

[0243] Clause 3. The method of clause 2, wherein the data representation type identifier is assigned by the network entity, assigned by the sensing node, or preconfigured to the sensing node.

[0244] Clause 4. The method of any of clauses 1 to 3, wherein the list of data representation types supported by the sensing node comprises: a data quantization (DQ) data representation type, wherein the measurement report comprises one or more samples of the one or more measurements; a range-angle-doppler (RAD) tensor data representation type, wherein the measurement report comprises a range bin, an azimuth angle, a velocity, or any combination thereof, based on the one or more measurements; a point cloud dataQC2406282WOQualcomm Ref. No. 2406282WO65 / 94representation type, wherein the measurement report comprises a range, a velocity, an azimuth angle, an elevation angle, or any combination thereof, for one or more discrete points in a three-dimensional space, based on the one or more measurements; a voxel grid data representation type, wherein the measurement report comprises information associated with one or more voxels, based on the one or more measurements; a deep learning-based data representation type, wherein the measurement report comprises one or more features, one or more classifications, or any combination thereof, for one or more detected objects, based on the one or more measurements; a parametric object-based data representation type, wherein the measurement report comprises one or more geometric parameters of one or more shapes of one or more detected objects, based on the one or more measurements; or any combination thereof.

[0245] Clause 5. The method of any of clauses 1 to 4, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, one or more support indications comprising: a data width supported by the sensing node, indicating that the sensing node supports reporting a data amount associated with the data representation type that is less than or equal to a threshold data amount; an informationlevel data fusion capability supported by the sensing node, indicating that the sensing node supports information-level data fusion associated with the data representation type; a signal-level data fusion capability supported by the sensing node, indicating that the sensing node supports signal-level data fusion associated with the data representation type; a reporting period supported by the sensing node, indicating that the sensing node can transmit the measurement report formatted according to tire data representation type with a periodicity less than or equal to a threshold reporting periodicity; a measurement period supported by the sensing node, indicating that the sensing node can obtain the one or more measurements to be formatted according to the data representation type with a periodicity less than or equal to a threshold measuring periodicity; a response time supported by the sensing node, indicating that the sensing node can format the one or more measurements according to the data representation type with a response time less than or equal to a threshold response time; or any combination thereof.

[0246] Clause 6. The method of any of clauses 1 to 5, further comprising: receiving, from the network entity, a request for a sensing node order of preference; and sending, to the network entity, the sensing node order of preference, wherein the sensing node order ofQC2406282WOQualcomm Ref. No. 2406282WO66 / 94preference indicates that the sensing node prefers a first data representation type in the list of data representation types over a second data representation type in the list of data representation types.

[0247] Clause 7. The method of any of clauses 1 to 6, further comprising sending, to the network entity, a maximum number of data representation type identifiers supported by the sensing node.

[0248] Clause 8. The method of any of clauses 1 to 7, wherein the configuration is associated with a session of the sensing node, and the session comprises a positioning session, a data session, a sensing session, or any combination thereof.

[0249] Clause 9. The method of any of clauses 1 to 8, wherein the configuration is: received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof; activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; or any combination thereof,

[0250] Clause 10. The method of any of clauses 1 to 9, wherein the configuration comprises a network entity order of preference, wherein the network entity order of preference indicates that the network entity prefers a first data representation type of the one or more data representation ty pes over a second data representation type of the one or more data representation types.

[0251] Clause 11. The method of clause 10, further comprising determining to format the one or more measurements based on: a first data representation type, based on the first data representation type being first in the network entity order of preference; or a second data representation type that is not the first in the network entity order of preference, based on one or more conditions detected by the sensing node.

[0252] Clause 12. The method of clause 11, wherein the one or more conditions comprise: a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions ofQC2406282WOQualcomm Ref. No. 2406282WO67 / 94the sensing node; one or more data requirements of the sensing node; or any combination thereof.

[0253] Clause 13. The method of any of clauses 1 to 12, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration: a measuring periodicity for obtaining the one or more measurements; a reporting periodicity for sending the measurement report; or any combination thereof.

[0254] Clause 14. The method of any of clauses 1 to 13, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

[0255] Clause 15. The method of clause 14, wherein the one or more conditions for formatting, or not formatting, according to the data representation type comprise: a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof,

[0256] Clause 16. The method of any of clauses 1 to 15, wherein the sensing node is a user equipment (UE), a transmission-reception point (TRP), or any combination thereof.

[0257] Clause 17. The method of any of clauses 1 to 16, wherein the sending to the network entity, the receiving from the network entity, or any combination thereof, is via a base station, a next generation node b (gNB), a fusion entity, or any combination thereof.

[0258] Clause 18. The method of any of clauses 1 to 17, wherein the network entity is a location management function (LMF), a sensing management function (SeMF), or any combination thereof.

[0259] Clause 19. A method of wireless communication performed by a network entity, comprising: receiving, from a sensing node, a list of data representation types supported by the sensing node; sending, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receiving, from the sensing node a measurement report indicating one or more measurements, wherein theQC2406282WOQualcomm Ref. No. 2406282WO68 / 94one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0260] Clause 20. The method of clause 19, further comprising selecting, based on the list of data representation types supported by the sensing node, tire one or more data representation types indicated by the configuration.

[0261] Clause 21. The method of any of clauses 19 to 20, further comprising: receiving, from a base station associated with the sensing node, a list of data representation types supported by the base station; receiving, from a fusion entity associated with the sensing node, a list of data representation types supported by the fusion entity; or any combination thereof.

[0262] Clause 22. The method of clause 21, further comprising selecting, based on the list of data representation types supported by the base station, the list of data representation types supported by the fusion entity, or any combination thereof, the one or more data representation types indicated by the configuration.

[0263] Clause 23. The method of any of clauses 19 to 22, further comprising determining the one or more data representation types based on a backhaul capacity of a network, a computation capability of the sensing node, a computation capability of a fusion centre, a service requirement, or any combination thereof.

[0264] Clause 24. The method of any of clauses 19 to 23, further comprising: determining, based on the one or more measurements formatted according to the at least one data representation type, to send a reconfiguration to the sensing node; and sending, to the sensing node, a reconfiguration indicating one or more second data representation types from the list of data representation types.

[0265] Clause 25. 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: send, via the one or more transceivers, to a network entity, a list of data representation types supported by the sensing node; receive, via the one or more transceivers, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtain one or more measurements of one or more reference signals; and send, via the one or more transceivers, to the network entity, a measurement report indicating the one or moreQC2406282WOQualcomm Ref. No. 2406282WO69measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0266] Clause 26. The sensing node of clause 25, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

[0267] Clause 27. The sensing node of clause 26, wherein the data representation type identifier is assigned by the network entity, assigned by the sensing node, or preconfigured to the sensing node.

[0268] Clause 28. The sensing node of any of clauses 25 to 27, wherein the list of data representation types supported by the sensing node comprises: a data quantization (DQ) data representation type, wherein the measurement report comprises one or more samples of the one or more measurements; a range-angle-doppler (RAD) tensor data representation type, wherein the measurement report comprises a range bin, an azimuth angle, a velocity, or any combination thereof, based on the one or more measurements; a point cloud data representation type, wherein the measurement report comprises a range, a velocity, an azimuth angle, an elevation angle, or any combination thereof, for one or more discrete points in a three-dimensional space, based on the one or more measurements; a voxel grid data representation type, wherein the measurement report comprises information associated with one or more voxels, based on the one or more measurements; a deep learning-based data representation type, wherein the measurement report comprises one or more features, one or more classifications, or any combination thereof, for one or more detected objects, based on the one or more measurements; a parametric object-based data representation type, wherein the measurement report comprises one or more geometric parameters of one or more shapes of one or more detected objects, based on the one or more measurements; or any combination thereof.

[0269] Clause 29. The sensing node of any of clauses 25 to 28, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, one or more support indications comprising: a data width supported by the sensing node, indicating that the sensing node supports reporting a data amount associated with the data representation type that is less than or equal to a threshold data amount; an information-level data fusion capability supported by the sensing node, indicating that the sensing node supports information-level data fusion associated with the dataQC2406282WOQualcomm Ref. No. 2406282WOrepresentation type; a signal-level data fusion capability’ supported by the sensing node, indicating that the sensing node supports signal-level data fusion associated with the data representation type; a reporting period supported by the sensing node, indicating that the sensing node can transmit the measurement report formatted according to the data representation type with a periodicity less than or equal to a threshold reporting periodicity; a measurement period supported by the sensing node, indicating that the sensing node can obtain the one or more measurements to be formatted according to the data representation type with a periodicity’ less than or equal to a threshold measuring periodicity; a response time supported by the sensing node, indicating that the sensing node can format the one or more measurements according to the data representation type with a response time less than or equal to a threshold response time; or any combination thereof.

[0270] Clause 30. The sensing node of any of clauses 25 to 29, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the network entity, a request for a sensing node order of preference; and send, via the one or more transceivers, to the network entity, the sensing node order of preference, wherein the sensing node order of preference indicates that the sensing node prefers a first data representation type in the list of data representation types over a second data representation type in the list of data representation types,

[0271] Clause 31. The sensing node of any of clauses 25 to 30, wherein the one or more processors, either alone or in combination, are further configured to send, via the one or more transceivers, to the network entity, a maximum number of data representation type identifiers supported by the sensing node.

[0272] Clause 32. The sensing node of any of clauses 25 to 31, wherein the configuration is associated with a session of the sensing node, and the session comprises a positioning session, a data session, a sensing session, or any combination thereof.

[0273] Clause 33. The sensing node of any of clauses 25 to 32, wherein the configuration is:received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof; activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; or any combination thereof.QC2406282WOQualcomm Ref. No. 2406282WO

[0274] Clause 34. The sensing node of any of clauses 25 to 33, wherein the configuration comprises a network entity order of preference, wherein the network entity order of preference indicates that the network entity prefers a first data representation type of the one or more data representation types over a second data representation type of the one or more data representation types.

[0275] Clause 35. The sensing node of clause 34, wherein the one or more processors, either alone or in combination, are further configured to determine to format the one or more measurements based on: a first data representation type, based on the first data representation type being first in the network entity order of preference; or a second data representation type that is not the first in the network entity order of preference, based on one or more conditions detected by the sensing node.

[0276] Clause 36. The sensing node of clause 35, wherein the one or more conditions comprise:a signal -to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof.

[0277] Clause 37. The sensing node of any of clauses 25 to 36, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration: a measuring periodicity for obtaining the one or more measurements; a reporting periodicity for sending the measurement report; or any combination thereof.

[0278] Clause 38. The sensing node of any of clauses 25 to 37, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

[0279] Clause 39. The sensing node of clause 38, wherein the one or more conditions for formatting, or not formating, according to the data representation type comprise: a signal- to-noise ratio (SNR), reference signal received pow er (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensingQC2406282WOQualcomm Ref. No. 2406282WOurnnode; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof,

[0280] Clause 40. The sensing node of any of clauses 25 to 39, wherein the sensing node is a user equipment (UE), a transmission-reception point (TRP), or any combination thereof.

[0281] Clause 41. The sensing node of any of clauses 25 to 40, wherein the one or more processors, either alone or in combination, are further configured to send to the network entity, receive from the network entity, or any combination thereof, via a base station, a next generation node b (gNB), a fusion entity, or any combination thereof.

[0282] Clause 42, The sensing node of any of clauses 25 to 41, wherein the network entity is a location management function (LMF), a sensing management function (SeMF), or any combination thereof.

[0283] Clause 43. 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, from a sensing node, a list of data representation types supported by the sensing node; send, via the one or more transceivers, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receive, via the one or more transceivers, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0284] Clause 44. The network entity of clause 43, wherein the one or more processors, either alone or in combination, are further configured to select, based on the list of data representation types supported by the sensing node, the one or more data representation types indicated by the configuration.

[0285] Clause 45. The network entity of any of clauses 43 to 44, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from a base station associated with the sensing node, a list of data representation types supported by the base station; receive, via the one or moreQC2406282WOQualcomm Ref. No. 2406282WO73 / 94transceivers, from a fusion entity associated with the sensing node, a list of data representation types supported by the fusion entity; or any combination thereof.

[0286] Clause 46. The network entity of clause 45, wherein the one or more processors, either alone or in combination, are further configured to select, based on the list of data representation types supported by the base station, the list of data representation types supported by the fusion entity, or any combination thereof, the one or more data representation types indicated by the configuration.

[0287] Clause 47. The network entity of any of clauses 43 to 46, wherein the one or more processors, either alone or in combination, are further configured to determine the one or more data representation types based on a backhaul capacity of a network, a computation capability of the sensing node, a computation capability of a fusion centre, a service requirement, or any combination thereof.

[0288] Clause 48. The network entity of any of clauses 43 to 47, wherein the one or more processors, either alone or in combination, are further configured to: determine, based on the one or more measurements formatted according to the at least one data representation type, to send a reconfiguration to the sensing node; and send, via the one or more transceivers, to the sensing node, a reconfiguration indicating one or more second data representation types from the list of data representation types.

[0289] Clause 49, A sensing node, comprising: means for sending, to a network entity, a list of data representation types supported by the sensing node; means for receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; means for obtaining one or more measurements of one or more reference signals; and means for sending, to the network entity', a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types,

[0290] Clause 50. The sensing node of clause 49, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

[0291] Clause 51. The sensing node of clause 50, wherein the data representation type identifier is assigned by the network entity', assigned by the sensing node, or preconfigured to the sensing node.QC2406282WOQualcomm Ref. No. 2406282WO74 / 94

[0292] Clause 52, The sensing node of any of clauses 49 to 51, wherein the list of data representation types supported by the sensing node comprises: a data quantization (DQ) data representation type, wherein the measurement report comprises one or more samples of the one or more measurements; a range-angle-doppler (RAD) tensor data representation type, wherein the measurement report comprises a range bin, an azimuth angle, a velocity, or any combination thereof, based on the one or more measurements; a point cloud data representation type, wherein the measurement report comprises a range, a velocity, an azimuth angle, an elevation angle, or any combination thereof, for one or more discrete points in a three-dimensional space, based on the one or more measurements; a voxel grid data representation type, wherein the measurement report comprises information associated with one or more voxels, based on the one or more measurements; a deep learning-based data representation type, wherein the measurement report comprises one or more features, one or more classifications, or any combination thereof, for one or more detected objects, based on the one or more measurements; a parametric object-based data representation type, wherein the measurement report comprises one or more geometric parameters of one or more shapes of one or more detected objects, based on the one or more measurements; or any combination thereof.

[0293] Clause 53. The sensing node of any of clauses 49 to 52, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, one or more support indications comprising: a data width supported by the sensing node, indicating that the sensing node supports reporting a data amount associated with the data representation type that is less than or equal to a threshold data amount; an information-level data fusion capability supported by the sensing node, indicating that the sensing node supports information-level data fusion associated with the data representation type; a signal-level data fusion capability supported by the sensing node, indicating that the sensing node supports signal-level data fusion associated with the data representation type; a reporting period supported by the sensing node, indicating that the sensing node can transmit the measurement report formatted according to the data representation type with a periodicity less than or equal to a threshold reporting periodicity; a measurement period supported by the sensing node, indicating that the sensing node can obtain the one or more measurements to be formated according to the data representation type with a periodicity less than or equal to a threshold measuringQC2406282WOQualcomm Ref. No. 2406282WOiperiodicity; a response time supported by the sensing node, indicating that the sensing node can format tire one or more measurements according to the data representation type with a response time less than or equal to a threshold response time; or any combination thereof.

[0294] Clause 54. The sensing node of any of clauses 49 to 53, further comprising: means for receiving, from the network entity, a request for a sensing node order of preference; and means for sending, to the network entity, the sensing node order of preference, wherein the sensing node order of preference indicates that the sensing node prefers a first data representation type in the list of data representation types over a second data representation type in the list of data representation types.

[0295] Clause 55. The sensing node of any of clauses 49 to 54, further comprising means for sending, to the network entity’, a maximum number of data representation type identifiers supported by the sensing node.

[0296] Clause 56. The sensing node of any of clauses 49 to 55, wherein the configuration is associated with a session of the sensing node, and the session comprises a positioning session, a data session, a sensing session, or any combination thereof.

[0297] Clause 57. The sensing node of any of clauses 49 to 56, wherein the configuration is:received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof; activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; or any combination thereof.

[0298] Clause 58. The sensing node of any of clauses 49 to 57, wherein the configuration comprises a network entity order of preference, wherein tire network entity' order of preference indicates that the network entity prefers a first data representation type of the one or more data representation types over a second data representation type of the one or more data representation types.

[0299] Clause 59. The sensing node of clause 58, further comprising means for determining to format the one or more measurements based on: a first data representation type, based on the first data representation type being first in the network entity' order of preference; or a second data representation type that is not the first in the network entity order of preference, based on one or more conditions detected by the sensing node.QC2406282WOQualcomm Ref. No. 2406282WO76 / 94

[0300] Clause 60. The sensing node of clause 59, wherein the one or more conditions comprise:a signal -to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof.

[0301] Clause 61. The sensing node of any of clauses 49 to 60, w herein the configuration of the one or more data representation types comprises, for each data representation ty pe in the configuration: a measuring periodicity’ for obtaining the one or more measurements; a reporting periodicity for sending the measurement report; or any combination thereof.

[0302] Clause 62. The sensing node of any of clauses 49 to 61, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

[0303] Clause 63. The sensing node of clause 62, wherein the one or more conditions for formatting, or not formatting, according to the data representation type comprise: a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof,

[0304] Clause 64. The sensing node of any of clauses 49 to 63, wherein the sensing node is a user equipment (UE), a transmission-reception point (TRP), or any combination thereof.

[0305] Clause 65. The sensing node of any' of clauses 49 to 64, wherein the sending to the network entity’, the receiving from the network entity', or any’ combination thereof, is via a base station, a next generation node b (gNB), a fusion entity, or any combination thereof.QC2406282WOQualcomm Ref. No. 2406282WOn

[0306] Clause 66. The sensing node of any of clauses 49 to 65, wherein the network entity is a location management function (LMF), a sensing management function (SeMF), or any combination thereof.

[0307] Clause 67. A network entity, comprising: means for receiving, from a sensing node, a list of data representation types supported by the sensing node; means for sending, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; means for receiving, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0308] Clause 68. The network entity of clause 67, further comprising means for selecting, based on the list of data representation types supported by the sensing node, the one or more data representation types indicated by the configuration.

[0309] Clause 69. The network entity of any of clauses 67 to 68, further comprising: means for receiving, from a base station associated with the sensing node, a list of data representation types supported by the base station; means for receiving, from a fusion entity associated with the sensing node, a list of data representation types supported by the fusion entity; or any combination thereof.

[0310] Clause 70. The network entity of clause 69, further comprising means for selecting, based on the list of data representation types supported by the base station, the list of data representation types supported by the fusion entity, or any combination thereof, the one or more data representation types indicated by the configuration.

[0311] Clause 71. The network entity of any of clauses 67 to 70, further comprising means for determining the one or more data representation types based on a backhaul capacity of a network, a computation capability of the sensing node, a computation capability of a fusion centre, a service requirement, or any combination thereof,

[0312] Clause 72. The network entity of any of clauses 67 to 71, further comprising: means for determining, based on the one or more measurements formatted according to the at least one data representation type, to send a reconfiguration to the sensing node; and means for sending, to the sensing node, a reconfiguration indicating one or more second data representation types from the list of data represen tation types.QC2406282WOQualcomm Ref. No. 2406282WO78 / 94

[0313] Clause 73. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sensing node, cause the sensing node to: send, to a network entity, a list of data representation types supported by the sensing node; receive, from the network entity, a configuration indicating one or more data representation types from the list of data representation types; obtain one or more measurements of one or more reference signals; and send, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

[0314] Clause 74. The non-transitory computer-readable medium of clause 73, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

[0315] Clause 75. The non-transitory computer-readable medium of clause 74, wherein the data representation type identifier is assigned by the network entity, assigned by the sensing node, or preconfigured to the sensing node.

[0316] Clause 76. The non-transitory' computer-readable medium of any of clauses 73 to 75, wherein the list of data representation types supported by the sensing node comprises: a data quantization (DQ) data representation type, wherein the measurement report comprises one or more samples of the one or more measurements; a range-angle-doppler (RAD) tensor data representation type, wherein the measurement report comprises a range bin, an azimuth angle, a velocity, or any combination thereof, based on the one or more measurements; a point cloud data representation type, wherein the measurement report comprises a range, a velocity, an azimuth angle, an elevation angle, or any combination thereof, for one or more discrete points in a three-dimensional space, based on the one or more measurements; a voxel grid data representation type, wherein tire measurement report comprises information associated with one or more voxels, based on the one or more measurements; a deep learning-based data representation type, wherein the measurement report comprises one or more features, one or more classifications, or any combination thereof, for one or more detected objects, based on the one or more measurements; a parametric object-based data representation type, wherein the measurement report comprises one or more geometric parameters of one or more shapesQC2406282WOQualcomm Ref. No. 2406282WO79 / 94of one or more detected objects, based on the one or more measurements; or any combination thereof.

[0317] Clause 77. The non-transitory computer-readable medium of any of clauses 73 to 76, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, one or more support indications comprising: a data width supported by the sensing node, indicating that the sensing node supports reporting a data amount associated with the data representation type that is less than or equal to a threshold data amount; an information-level data fusion capability supported by the sensing node, indicating that the sensing node supports information-level data fusion associated with the data representation type; a signal-level data fusion capability supported by the sensing node, indicating that the sensing node supports signal-level data fusion associated with the data representation type; a reporting period supported by the sensing node, indicating that the sensing node can transmit the measurement report formatted according to the data representation type with a periodicity less than or equal to a threshold reporting periodicity; a measurement period supported by the sensing node, indicating that the sensing node can obtain the one or more measurements to be formatted according to the data representation type with a periodicity less than or equal to a threshold measuring periodicity; a response time supported by the sensing node, indicating that the sensing node can format the one or more measurements according to the data representation type with a response time less than or equal to a threshold response time; or any combination thereof.

[0318] Clause 78. The non-transitory computer-readable medium of any of clauses 73 to 77, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to: receive, from the network entity, a request for a sensing node order of preference; and send, to the network entity, the sensing node order of preference, wherein the sensing node order of preference indicates that the sensing node prefers a first data representation type in the list of data representation types over a second data representation type in the list of data representation types.

[0319] Clause 79. The non-transitory computer-readable medium of any of clauses 73 to 78, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to send, to the network entity, a maximum number of data representation type identifiers supported by the sensing node.QC2406282WOQualcomm Ref. No. 2406282WO80 / 94

[0320] Clause 80, The non-transitory computer-readable medium of any of clauses 73 to 79, wherein the configuration is associated with a session of the sensing node, and the session comprises a positioning session, a data session, a sensing session, or any combination thereof.

[0321] Clause 81. The non-transitory computer-readable medium of any of clauses 73 to 80, wherein the configuration is: received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof; activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; or any combination thereof.

[0322] Clause 82. The non-transitory computer-readable medium of any of clauses 73 to 81, wherein the configuration comprises a network entity order of preference, wherein the network entity order of preference indicates that the network entity prefers a first data representation type of the one or more data representation types over a second data representation type of the one or more data representation types.

[0323] Clause 83. The non-transitory computer-readable medium of clause 82, further comprising computer-executable instructions that, when executed by the sensing node, cause the sensing node to determine to format the one or more measurements based on: a first data representation type, based on the first data representation type being first in the network entity order of preference; or a second data representation type that is not the first in the network entity order of preference, based on one or more conditions detected by the sensing node.

[0324] Clause 84. The non-transitory' computer-readable medium of clause 83, wherein the one or more conditions comprise: a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof.QC2406282WOQualcomm Ref. No. 2406282WO81 / 94

[0325] Clause 85. The non-transitory computer-readable medium of any of clauses 73 to 84, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration: a measuring periodicity for obtaining the one or more measurements; a reporting periodicity for sending the measurement report; or any combination thereof.

[0326] Clause 86. The non-transitory computer-readable medium of any of clauses 73 to 85, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

[0327] Clause 87. The non-transitory computer-readable medium of clause 86, wherein the one or more conditions for formatting, or not formatting, according to the data representation type comprise: a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node; a triggering of an event; a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node; a radio resource control (RRC) state of the sensing node; a power level, power consumption rate, or any combination thereof, of the sensing node; one or more modem functions of the sensing node; one or more data requirements of the sensing node; or any combination thereof.

[0328] Clause 88. The non-transitory computer-readable medium of any of clauses 73 to 87, wherein the sensing node is a user equipment (UE), a transmission-reception point (TRP), or any combination thereof.

[0329] Clause 89. The non-transitory computer-readable medium of any of clauses 73 to 88, wherein the sending to the network entity, the receiving from the network entity, or any combination thereof, is via a base station, a next generation node b (gNB), a fusion entity, or any combination thereof.

[0330] Clause 90. The non-transitory computer-readable medium of any of clauses 73 to 89, wherein the network entity is a location management function (LMF), a sensing management function (SeMF), or any combination thereof.

[0331] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: receive, from a sensing node, a list of data representation types supported by the sensing node;QC2406282WOQualcomm Ref. No. 2406282WOisend, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; receive, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types,

[0332] Clause 92. The non-transitory computer-readable medium of clause 91, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity’ to select, based on the list of data representation types supported by the sensing node, the one or more data representation types indicated by the configuration.

[0333] Clause 93. The non-transitory computer-readable medium of any of clauses 91 to 92, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: receive, from a base station associated with the sensing node, a list of data representation types supported by the base station; receive, from a fusion entity associated with the sensing node, a list of data representation types supported by the fusion entity; or any combination thereof.

[0334] Clause 94. The non-transitory computer-readable medium of clause 93, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to select, based on the list of data representation types supported by the base station, the list of data representation types supported by the fusion entity, or any combination thereof, the one or more data representation types indicated by the configuration.

[0335] Clause 95, The non-transitory computer-readable medium of any of clauses 91 to 94, further comprising computer-executable instructions that, when executed by tire network entity, cause the network entity to determine the one or more data representation types based on a backhaul capacity of a network, a computation capability’ of the sensing node, a computation capability of a fusion centre, a service requirement, or any combination thereof.

[0336] Clause 96. The non-transitory computer-readable medium of any of clauses 91 to 95, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine, based on the one or more measurements formatted according to the at least one data representation type, to send a reconfigurationQC2406282WOQualcomm Ref. No. 2406282WO83 / 94to the sensing node; and send, to the sensing node, a reconfiguration indicating one or more second data representation types from the list of data representation types.

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

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

[0339] 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-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any 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.

[0340] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executedQC2406282WOQualcomm Ref. No. 2406282WO84 / 94by 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.

[0341] 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, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then tire 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.QC2406282WOQualcomm Ref. No. 2406282WO85 / 94

[0342] 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.QC2406282WO

Claims

Qualcomm Ref. No. 2406282WO86 / 94CLAIMSWhat is claimed is:

1. A sensing node, comprising:one or more memories;one or more transceivers; andone 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:send, via the one or more transceivers, to a network entity, a list of data representation types supported by the sensing node;receive, via the one or more transceivers, from the network entity, a configuration indicating one or more data representation types from the list of data representation types;obtain one or more measurements of one or more reference signals; andsend, via the one or more transceivers, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.

2. The sensing node of claim 1, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

3. The sensing node of claim 2, wherein the data representation type identifier is assigned by the network entity, assigned by the sensing node, or preconfigured to the sensing node.

4. The sensing node of claim 1, wherein the list of data representation types supported by the sensing node comprises:a data quantization (DQ) data representation type, wherein the measurement report comprises one or more samples of the one or more measurements;QC2406282WOQualcomm Ref. No. 2406282WO87 / 94a range-angle-doppler (RAD) tensor data representation type, wherein the measurement report comprises a range bin, an azimuth angle, a velocity, or any combination thereof, based on the one or more measurements;a point cloud data representation type, wherein the measurement report comprises a range, a velocity, an azimuth angle, an elevation angle, or any combination thereof, for one or more discrete points in a three-dimensional space, based on the one or more measurements;a voxel grid data representation type, wherein the measurement report comprises information associated with one or more voxels, based on the one or more measurements;a deep learning-based data representation type, wherein the measurement report comprises one or more features, one or more classifications, or any combination thereof, for one or more detected objects, based on the one or more measurements;a parametric object-based data representation type, wherein the measurement report comprises one or more geometric parameters of one or more shapes of one or more detected objects, based on the one or more measurements; or any combination thereof.

5. The sensing node of claim 1, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, one or more support indications comprising:a data width supported by the sensing node, indicating that the sensing node supports reporting a data amount associated with the data representation type that is less than or equal to a threshold data amount;an information-level data fusion capability supported by the sensing node, indicating that the sensing node supports information-level data fusion associated with the data representation type;a signal-level data fusion capability supported by the sensing node, indicating that the sensing node supports signal -level data fusion associated wi th the data representation type;a reporting period supported by the sensing node, indicating that the sensing node can transmit the measurement report formatted according to the data QC2406282WOQualcomm Ref. No. 2406282WO88 / 94representation type with a periodicity less than or equal to a threshold reporting periodicity;a measurement period supported by the sensing node, indicating that the sensing node can obtain the one or more measurements to be formatted according to the data representation type with a periodicity less than or equal to a threshold measuring periodicity;a response time supported by the sensing node, indicating that the sensing node can format the one or more measurements according to the data representation type with a response time less than or equal to a threshold response time; orany combination thereof6. The sensing node of claim 1, wherein the one or more processors, either alone or in combination, are further configured to:receive, via the one or more transceivers, from the network entity, a request for a sensing node order of preference; andsend, via the one or more transceivers, to the network entity, the sensing node order of preference, wherein the sensing node order of preference indicates that the sensing node prefers a first data representation type in the list of data representation types over a second data representation type in the list of data representation types.

7. The sensing node of claim 1, wherein the one or more processors, either alone or in combination, are further configured to send, via the one or more transceivers, to the network entity, a maximum number of data representation type identifiers supported by the sensing node.

8. The sensing node of claim 1, wherein the configuration is associated with a session of the sensing node, and the session comprises a positioning session, a data session, a sensing session, or any combination thereof.

9. The sensing node of claim 1, wherein the configuration is:received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof;QC2406282WOQualcomm Ref. No. 2406282WO89 / 94activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; orany combination thereof,10. The sensing node of claim 1, wherein the configuration comprises a network entity order of preference, wherein the network entity order of preference indicates that the network entity prefers a first data representation type of the one or more data representation types over a second data representation type of the one or more data representation types,11. The sensing node of claim 10, wherein the one or more processors, either alone or in combination, are further configured to determine to format the one or more measurements based on:a first data representation type, based on the first data representation type being first in the network entity order of preference; ora second data representation type that is not the first in the network entity order of preference, based on one or more conditions detected by the sensing node.

12. The sensing node of claim 11, wherein the one or more conditions comprise:a signal-to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node;a triggering of an event;a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node;a radio resource control (RRC) state of the sensing node;a power level, power consumption rate, or any combination thereof, of the sensing node;one or more modem functions of the sensing node;one or more data requirements of the sensing node; orany combination thereof.QC2406282WOQualcomm Ref. No. 2406282WO90 / 9413. The sensing node of claim 1, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration:a measuring periodicity for obtaining the one or more measurements; a reporting periodicity for sending the measurement report; orany combination thereof,14. The sensing node of claim 1, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

15. The sensing node of claim 14, wherein the one or more conditions for formatting, or not formating, according to the data representation type comprise:a signal -to-noise ratio (SNR), reference signal received power (RSRP), reference signal received quality (RSRQ), a bandwidth, or any combination thereof, of a serving cell of the sensing node;a triggering of an event;a millions of instructions per second (MIPS) availability, a processing availability, or any combination thereof, in the sensing node;a radio resource control (RRC) state of the sensing node;a power level, power consumption rate, or any combination thereof, of the sensing node;one or more modem functions of the sensing node;one or more data requirements of the sensing node; orany combination thereof.

16. The sensing node of claim 1, wherein the sensing node is a user equipment (UE), a transmission-reception point (TRP), or any combination thereof.

17. The sensing node of claim 1, wherein the one or more processors, either alone or in combination, are further configured to send to the network entity, receive from the network entity, or any combination thereof, via a base station, a next generation node b (gNB), a fusion entity, or any combination thereof.QC2406282WOQualcomm Ref. No. 2406282WO91 / 9418. The sensing node of claim 1, wherein the network entity is a location management function (LMF), a sensing management function (SeMF), or any combination thereof.

19. A network entity, composing:one or more memories;one or more transceivers; andone 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, from a sensing node, a list of data representation types supported by the sensing node;send, via the one or more transceivers, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types; andreceive, via the one or more transceivers, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types, 20. The network entity of claim 19, wherein the one or more processors, either alone or in combination, are further configured to select, based on the list of data representation types supported by the sensing node, the one or more data representation types indicated by the configuration.

21. The network entity of claim 18, wherein the one or more processors, either alone or in combination, are further configured to:receive, via the one or more transceivers, from a base station associated with the sensing node, a list of data representation types supported by the base station;receive, via the one or more transceivers, from a fusion entity associated with the sensing node, a list of data representation types supported by the fusion entity; orany combination thereof.QC2406282WOQualcomm Ref. No. 2406282WO92 / 9422. The network entity of claim 21, wherein the one or more processors, either alone or in combination, are further configured to select, based on the list of data representation types supported by the base station, the list of data representation types supported by the fusion entity, or any combination thereof, the one or more data representation types indicated by the configuration.

23. The network entity of claim 19, wherein the one or more processors, either alone or in combination, are further configured to determine the one or more data representation types based on a backhaul capacity of a network, a computation capability of the sensing node, a computation capability of a fusion centre, a service requirement, or any combination thereof.

24. The network entity of claim 19, wherein the one or more processors, either alone or in combination, are further configured to:determine, based on the one or more measurements formatted according to the at least one data representation type, to send a reconfiguration to the sensing node; andsend, via the one or more transceivers, to the sensing node, a reconfiguration indicating one or more second data representation types from the list of data representation types,25. A method of wireless communication performed by a sensing node, comprising:sending, to a network entity, a list of data representation types supported by the sensing node;receiving, from the network entity, a configuration indicating one or more data representation types from the list of data representation types;obtaining one or more measurements of one or more reference signals; and sending, to the network entity, a measurement report indicating the one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types.QC2406282WOQualcomm Ref. No. 2406282WO93 / 9426. The method of claim 25, wherein the list of data representation types comprises, for each data representation type supported by the sensing node, a data representation type identifier.

27. The method of claim 25, wherein the configuration is:received via a radio resource control (RRC) configuration message, an RRC reconfiguration message, or any combination thereof;activated or deactivated via an RRC configuration message, an RRC reconfiguration message, a medium access control control element (MAC CE), a downlink control information (DCI), a sidelink control information (SCI), or any combination thereof; orany combination thereof.

28. The method of claim 25, wherein the configuration of the one or more data representation types comprises, for each data representation type in the configuration, one or more conditions for formatting, or not formatting, according to the data representation type.

29. A method of wireless communication performed by a network entity, comprising:receiving, from a sensing node, a list of data representation types supported by the sensing node;sending, to the sensing node, a configuration indicating one or more data representation types from the list of data representation types;receiving, from the sensing node a measurement report indicating one or more measurements, wherein the one or more measurements are formatted according to at least one data representation type of the one or more data representation types,30. The method of claim 29, further comprising selecting, based on the list of data representation types supported by the sensing node, the one or more data representation types indicated by the configuration.QC2406282WO

Images