Sensing processing capability reporting in user equipment (UE) assisted bistatic or multistatic sensing

Abstract

Techniques for sensing processing capability reporting in user equipment (UE) assisted bistatic or multistatic sensing are disclosed. In an aspect, a sense signal transmitter is capable of transmitting first information specifying a set of one or more sensing types to a sense signal receiver. The sensing signal transmitter is capable of receiving, from the sensing signal receiver, second information specifying a sensing processing capability of the sensing signal receiver. The sensing signal transmitter can determine, based at least in part on the sensing processing capability of the sensing signal receiver, whether to select or not select the sensing signal receiver to perform a sensing task, the sensing task including bistatic sensing or multistatic sensing.

Description

Background Art 1. Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications.

[0002] 2. Description of related technologies

[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems 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), Global System for Mobile Communications (GSM), and the like.

[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G enable high-precision positioning based on 5G. Summary of the invention

[0005] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0006] In one aspect, a method of wireless sensing performed by a sensing signal transmitter includes: transmitting first information specifying a set of one or more sensing types to a sensing signal receiver; receiving second information specifying a sensing processing capability of the sensing signal receiver from the sensing signal receiver; and determining, at least in part based on the sensing processing capability of the sensing signal receiver, to select or not select the sensing signal receiver to perform a sensing task, the sensing task including dual-base sensing or multi-base sensing.

[0007] In one aspect, a method of wireless sensing performed by a sensing signal receiver includes: receiving first information specifying a set of one or more sensing types from a sensing signal transmitter; and transmitting second information specifying a sensing processing capability of the sensing signal receiver to the sensing signal transmitter.

[0008] In one aspect, a sensing signal transmitter includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit first information specifying a set of one or more sensing types to a sensing signal receiver via at least one transceiver; receive second information specifying a sensing processing capability of the sensing signal receiver from the sensing signal receiver via at least one transceiver; and determine, at least in part based on the sensing processing capability of the sensing signal receiver, to select or not select the sensing signal receiver to perform a sensing task, the sensing task including dual-base sensing or multi-base sensing.

[0009] In one aspect, a sensing signal receiver includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive first information specifying a set of one or more sensing types from a sensing signal transmitter via at least one transceiver; and transmit second information specifying a sensing processing capability of the sensing signal receiver to the sensing signal transmitter via at least one transceiver.

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

[0011] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0012] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0013] Figure 2A , Figure 2B and Figure 2CExample wireless network structures according to aspects of the present disclosure are illustrated.

[0014] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram 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.

[0015] Figure 4A An example monostatic radar system is illustrated.

[0016] Figure 4B An example bistatic radar system is illustrated.

[0017] Figure 5 Typical circuits in a telecommunication device that can perform RF communication and RF sensing according to aspects of the present disclosure are illustrated.

[0018] Figure 6 An example of a single-base ISAC according to aspects of the present disclosure is illustrated.

[0019] Figure 7 An example of a multi-base ISAC in accordance with aspects of the present disclosure is illustrated.

[0020] Figure 8 Examples of UE-assisted bistatic sensing according to aspects of the present disclosure are illustrated.

[0021] Fig. 9 Examples of UE-assisted multistatic sensing according to aspects of the present disclosure are illustrated.

[0022] Fig.10 is a signaling and event diagram illustrating procedures associated with sensing processing capability reporting in UE-assisted dual-static or multi-static sensing according to aspects of the present disclosure.

[0023] Fig.11 An example is illustrated in which the Sensing Rx reports how many Sensing Processing Units (SPUs) it supports according to aspects of the present disclosure.

[0024] Fig. 12A and Fig. 12B Two different calculations for SPU occupancy are shown in accordance with aspects of the present disclosure.

[0025] Fig.13 and Fig.14 is a flow chart of portions of example processes associated with sensing processing capability reporting in UE-assisted bistatic sensing in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0026] Disclosed are technologies for sensing processing capability reporting in user equipment (UE) assisted dual-base or multi-base sensing. In one aspect, a sensing signal transmitter may transmit first information specifying a set of one or more sensing types to a sensing signal receiver. The sensing signal transmitter may receive second information specifying the sensing processing capability of the sensing signal receiver from the sensing signal receiver. The sensing signal transmitter may determine, at least in part based on the sensing processing capability of the sensing signal receiver, to select or not select the sensing signal receiver to perform a sensing task, the sensing task comprising dual-base sensing or multi-base sensing. In another aspect, the sensing signal receiver may receive first information specifying a set of one or more sensing types from the sensing signal transmitter. The sensing signal receiver may transmit second information specifying the sensing processing capability of the sensing signal receiver to the sensing signal transmitter.

[0027] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

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

[0029] Those skilled in the art will appreciate that any of a variety of different techniques and technologies may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0030] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the subject matter claimed. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".

[0031] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0032] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (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 primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as 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)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0033] The term "base station" may refer to a single physical transmit-receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. As used herein, since a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0034] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0035] An "RF signal" includes an electromagnetic wave of a given frequency that transmits 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, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a 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.

[0036] Figure 1 An example wireless communication system 100 is illustrated in accordance with various aspects of the present disclosure. The wireless communication 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 macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femtocells, picocells, microcells, and the like.

[0037] 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 a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via 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 the like. For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0038] Among other functions, the base station 102 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, 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 EPC / 5GC) via a backhaul link 134, which may be wired or wireless.

[0039] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), 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.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may refer to either or both of a logical communication entity and a base station supporting the logical communication entity, depending on the context. In addition, since the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0040] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the 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 areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG).

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

[0042] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0043] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.

[0044] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180, which can operate in mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30GHz to 300GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended downward to a frequency of 3GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3GHz and 30GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and UE 182 can compensate for extremely high path loss and short range by using beamforming (sending and / or receiving) through the mmW communication link 184. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0045] 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 (omnidirectionally). 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 to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.

[0046] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, 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 the second reference RF signal sent 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 the second reference RF signal sent 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 the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0047] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that 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 signal received from that direction.

[0048] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on 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 specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.

[0049] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, while if the UE is forming an uplink beam, it is an uplink transmit beam.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. 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 portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0051] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this document, the term "below 6 GHz" and the like can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this document, they can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0053] 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 a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once an RRC connection is established between the UE 104 and the anchor carrier, and which can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. 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. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.

[0054] For example, still refer to Figure 1, one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0055] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell 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.

[0056] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, each group of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, where each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for the sidelink communications. In other cases, the sidelink communications are performed between the SL-UEs without involving the base station 102.

[0057] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those that employ small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0058] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. In the case where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 may utilize beamforming via side link 160.

[0059] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal of a repeating pseudo-random noise (PN) code marked with a set number of chips. Although typically located in the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0060] In a satellite positioning system, the use of signal 124 may be enhanced 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, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), etc. 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.

[0061] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, 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 an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from a SV 112.

[0062] The wireless communication system 100 may further include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.

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

[0064] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0065] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally viewed as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a 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 an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0066] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection 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, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 may also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0067] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0068] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0069] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.

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

[0071] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and the like. More specifically, the gNB-CU 226 generally hosts the RRC, Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may 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 one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0072] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. 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) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as a standalone base station or a single-chip base station) or a decomposed base station.

[0073] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between 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 in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0074] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0075] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may 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. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0076] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0077] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 280. CU280 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 specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

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

[0079] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, a 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, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the DU 285 and the CU 280 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0080] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized network elements 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 operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via an O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via an O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .

[0081] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, 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 the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.

[0082] In some implementations, in order to generate the AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. 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 via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0083] Figure 3A , Figure 3B and Figure 3C The examples may be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the present invention (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0084] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. 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.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.

[0085] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver, UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0086] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 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), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the positions of UE 302 and base station 304, respectively.

[0087] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0088] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations may include separate transmitter circuits and separate receiver circuits, or in other implementations may be implemented in other ways. The transmitter circuit and the receiver circuit 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. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0089] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired transceiver or a wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0090] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 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 circuits, or various combinations thereof.

[0091] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include sensing processors 342, 388, and 398, respectively. Sensing processors 342, 388, and 398 may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the sensing processors 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the sensing processors 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 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. Figure 3A Possible locations for the sensing processor 342 are illustrated, and the sensing processor may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for the sensing processor 388 are illustrated, and the sensing processor may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for the sensing processor 398 are illustrated, and the sensing processor may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0092] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0093] In addition, the UE 302 includes a user interface 346, which provides means for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0094] Referring to the one or more processors 384 in more detail, in a 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. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), 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 (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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.

[0095] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a 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 pre-decoded to generate multiple spatial streams. The channel estimate from the channel estimator can be used to determine the coding and modulation scheme and for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate the RF carrier with the corresponding spatial stream for transmission.

[0096] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can 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 can be combined into a single OFDM symbol stream by the receiver 312. 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 includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0097] In the downlink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0098] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission 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.

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

[0100] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

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

[0102] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of a wearable device or a tablet or a PC or a laptop computer, a specific implementation of the UE 302 may omit the WWAN transceiver 310 (e.g., a wearable device or a tablet or a PC or a laptop computer may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), may omit the short-range wireless transceiver 320 (e.g., only cellular, etc.), may omit the satellite signal receiver 330, may omit the sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0103] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces for the UE 302, base station 304, and 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 334, 382, ​​and 392 may provide for communication between the different logical entities.

[0104] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of 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 be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it will be appreciated that such operations, actions 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 processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, sensing processors 342, 388 and 398, etc.

[0105] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated differently from a network operator or 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 dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0106] Wireless communication signals (e.g., RF signals configured to carry OFDM symbols) sent between a UE and a base station can be reused for environmental sensing (also known as "RF sensing" or "radar"). Integrated sensing and communication (ISAC) is a form of RF sensing that can be performed by 5G networks and is seen as an important feature for enhanced 5G (5G+) and sixth generation (6G) networks. ISAC is attractive because it is cost-effective due to the shared RF, and possibly baseband, hardware for sensing and communication, and spectrum-efficient due to the always-on availability of spectrum for both sensing and communication.

[0107] Environmental sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, which enables contactless / device-free interaction with devices / systems, etc. The wireless communication signal can be a cellular communication signal, such as an LTE or NR signal, a WLAN signal, etc. As a specific example, the wireless communication signal can be an OFDM waveform as utilized in LTE and NR. High-frequency communication signals such as mmW RF signals are particularly beneficial for use as radar signals because the higher frequency at least provides more accurate range (distance) detection.

[0108] Use cases for macro sensing include weather monitoring, autonomous driving, dynamic mapping, low altitude airspace management (such as unmanned ariel vehicles (UAVs)), and intruder detection. Use cases for micro sensing include gesture recognition, vital signs detection, and high resolution imaging using THz signals. Other use cases include sensor-assisted communications, such as sensor-assisted beam management.

[0109] Radar sensing can be categorized into monostatic sensing and bistatic / multistatic sensing. In monostatic sensing, one entity both sends and receives the sensing signal, and in bistatic or multistatic sensing, one entity sends the sensing signal and the other entity (bistatic) or more than one other entity (multistatic) receives the sensing signal reflected by the target object.

[0110] Figure 4A and Figure 4B Two of these various types of radar are illustrated. Specifically, Figure 4A is a diagram 400 illustrating a monostatic radar scenario, and Figure 4B 4 is a diagram illustrating a bistatic radar scenario. A monostatic radar has the advantage of not needing to pair or group the Tx entity and the Rx entity (because they are the same entity), and has the disadvantage of needing to mitigate self-interference. A bistatic or multistatic radar has the advantage of not needing to mitigate self-interference, and has the disadvantage of needing to pair or group the Tx entity and the Rx entity.

[0111] exist Figure 4A 4, the base station 402 may be configured for full duplex operation and thus the transmitter (Tx) and receiver (Rx) are co-located. For example, the transmitted radio signal 406 may be reflected by a target object (such as a building 404), and the receiver on the base station 402 is configured to receive and measure the reflected beam 408. This is a typical use case for traditional or conventional radar.

[0112] exist Figure 4B, a base station 412 may be configured as a transmitter (Tx) and a UE 414 may be configured as a receiver (Rx). In this example, the transmitter and the receiver are not co-located, i.e., they are separated by a distance comparable to, for example, the intended target distance. The base station 412 may be configured to transmit a beam, such as an omni-directional downlink RF signal 406, which may be received by the UE 414. A portion of the RF signal 406 may be reflected or refracted by the building 404, and the UE 414 may receive this reflected signal 416. This is a typical use case for RF sensing based on wireless communications (e.g., WiFi-based, LTE-based, NR-based). Note that although Figure 4B The use of downlink RF signals 406 as RF sensing signals is illustrated, but uplink RF signals may also be used as RF sensing signals. In the downlink scenario, as shown, the transmitter is a base station 412 and the receiver is a UE 414, while in the uplink scenario, the transmitter is a UE and the receiver is a base station. A multi-base radar system is a generalization of a bi-base radar system, which includes at least three components, such as one receiver and two transmitters, two receivers and one transmitter, or multiple receivers and multiple transmitters.

[0113] For more details, refer to Figure 4B , the base station 412 transmits RF sensing signals (e.g., PRS) to the UE 414, but some of the RF sensing signals are reflected from the target object (such as the building 404). The UE 414 can measure the ToA of the RF signal 406 directly received from the base station and the ToA of the reflected signal 416 reflected from the target object (e.g., the building 404).

[0114] The base station 412 may be configured to transmit a single RF signal 406 or multiple RF signals to a receiver (e.g., UE 414). However, due to the propagation characteristics of RF signals through multipath channels, the UE 414 may receive multiple RF signals corresponding to each transmitted RF signal. Each path may be associated with a cluster of one or more channel taps. Typically, the time at which the receiver detects the first cluster of channel taps is considered to be the ToA of the RF signal on a 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 been reflected by objects between the transmitter and the receiver, and therefore have followed a non-LOS (NLOS) path between the transmitter and the receiver.

[0115] Therefore, returning to the reference Figure 4B, RF signal 406 follows the LOS path between base station 412 and UE 414, and reflected signal 416 represents the RF sensing signal that follows the NLOS path between base station 412 and UE 414 due to reflection from building 404 (or another target object). Base station 412 may have sent multiple RF sensing signals ( Figure 4B ), some of the multiple RF sensing signals follow the LOS path, and other of the multiple RF sensing signals follow the NLOS path. Alternatively, the base station 412 may have sent a single RF sensing signal in a sufficiently wide beam, wherein a portion of the RF sensing signal follows the LOS path, and a portion of the RF sensing signal follows the NLOS path.

[0116] Based on the difference between the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, the UE 414 can determine the distance to the building 404. In addition, if the UE 414 is capable of receiving beamforming, the UE 414 can be able to determine the general direction to the building 404 as the direction of the reflected signal 416, which is the RF sensing signal following the NLOS path as received. The UE 414 can then optionally report this information to the sending base station 412, an application server associated with the core network, an external client, a third-party application, or some other entity. Alternatively, the UE 414 can report the ToA measurement to the base station 412 or another entity, and the base station 412 can determine the distance to the target object and optionally determine the direction to the target object.

[0117] Note that if the RF sensing signal is an uplink RF signal sent by UE 414 to base station 412, base station 412 will perform object detection based on the uplink RF signal just as UE 414 performs object detection based on downlink RF signals.

[0118] Integrated sensing and communication (ISAC) is a term that describes the convergence of RF communications and RF sensing, such as radar. The trend toward digitalization in commercial radars is converging the architecture of their RF front ends (i.e., all components in the receiver that process the signal at the raw incoming radio frequency and then convert it to a lower intermediate frequency) and their waveforms to become increasingly similar to those used for communications. For example, waveforms used for vehicular radars are evolving from analog frequency-modulated carriers (FMCW) to orthogonal frequency-division multiplexing (OFDM) symbols such as those used in telecommunications. Furthermore, carrier frequencies used for telecommunications are gradually shifting to higher frequency bands (24 GHz, 60 GHz, 77 GHz, and potentially even higher) that include frequencies used for radar.

[0119] Figure 51 illustrates typical circuits in a telecommunications device 500 that can perform RF communication and RF sensing according to various aspects of the present disclosure. Figure 5 , device 500 includes a transmitter circuit 502 that provides unified radar and communication transmit processing, and a receiver circuit 504 that provides unified radar and communication receive processing. A data source 506 provides communication data and sensed data (e.g., radar signals) to the transmitter circuit 502. The receiver circuit 504 provides the received data to a radar Rx processing circuit 508 and a communication Rx processing circuit 510. The device 500 operates within an environment 512 (which may also be referred to as a radio channel 512). The data source 506 may also provide sensed data to the radar Rx processor circuit 508. As shown in FIG. Figure 5 As can be seen in FIG. 1 , using OFDM symbols for RF sensing provides the following benefit: the same RF front end can be used for both RF communication and RF sensing, ie both functions can use shared components.

[0120] Thus, ISACs can provide benefits such as cost effectiveness (e.g., there can be a joint RF hardware platform for communications and radar) and spectrum effectiveness (e.g., constant availability of spectrum for both communications and radar functions). Another benefit is that RF sensing is an additional motivation for the market introduction of vehicle-to-everything (V2X) communications.

[0121] In some aspects, the general processing of the steps of the OFDM radar at the receiver side can include fast Fourier transform (FFT) processing, followed by one or more of the following operations: (1) removal of modulation symbols (data content), which eliminates the per-resource element (RE) modulation symbols by dividing the transmitted value of each per-resource element (RE) modulation symbol at the associated RE; (2) time domain (symbol-by-symbol) FFT for target velocity (Doppler) estimation; and (3) frequency domain (subcarrier-by-subcarrier) IFFT for target range estimation. Steps (2) and (3) are similar to the 2D-FFT processing of the FMCW radar, and the performance of the OFDM radar is similar to that of the FMCW radar.

[0122] It should be noted that OFDM signals can be used for radar purposes if the modulation symbols (data content) of the transmitted OFDM signal are known at the receiver. For a monostatic radar where the transmitter and receiver are the same node, the receiver naturally knows the exact transmitted signal. For a bistatic radar where the transmitter and receiver are different nodes, the receiver may still know the exact transmitted signal, for example, when a known or predefined transmitted signal sequence is used, or if the data is correctly decoded, such as by a received communication signal with a cyclic redundancy check (CRC). It should also be noted that, unlike radars based on phase modulated carrier (PMCW) where the autocorrelation properties of the sequence may be necessary, for OFDM radars, a specific sequence is not mandatory (except that the peak-to-average power ratio (PAPR) should be considered). For example, an OFDM signal based on a Zadoff-Chu sequence has a constant amplitude and will therefore have a higher signal-to-noise ratio (SNR) at the receiver side.

[0123] Here are some considerations for New Radio (NR) based ISACs: For range resolution, wideband signals should be considered; for stable availability during the observation time, broadcast signals should be considered instead of demand-triggered data channels. Therefore, the following signals or channels are considered together as radar signals for sensing:

[0124] • For the downlink (DL): Synchronization Signal Block (SSB), which is wideband from the system's point of view; Channel State Information Reference Signal (CSI-RS); and Downlink Positioning Reference Signal (DL-PRS).

[0125] • For the uplink (UL): Sounding Reference Signal (SRS); and Sidelink Positioning Reference Signal (SL-PRS).

[0126] The following table lists various reference signals and their potential uses for NR-based ISAC.

[0127]

[0128] Techniques associated with dual-base / multi-base sensing performed by a wireless network are provided herein. These techniques are exemplified for unmanned ariel aerial vehicle (UAV) sensing performed over a cellular network, but the present invention may also be applied to sensing of other kinds of objects, such as aircraft, vehicles, ships, people, animals, or any object. Due to the irregular shape of the target object, the reflected signals may be unevenly distributed in all directions. In order to increase the possibility of receiving reflected sensing signals, some UEs are involved in receiving reflected signals and are therefore referred to herein as sensing UEs. Using UEs to receive and report sensing signals is referred to herein as UE-assisted sensing. One benefit of using sensing UEs is that the number of gNBs in a cellular network is much smaller than the number of UEs, so using sensing UEs allows a larger amount of sensing information to be collected.

[0129] Sensing UEs may include legacy UEs and / or sensing-dedicated UEs. Examples of legacy UEs are ordinary UEs, such as mobile phones or vehicle UEs (VUEs). Legacy UEs tend to be highly mobile and have low antenna gain. Sensing-dedicated UEs include sensing roadside units (RSUs) with fixed locations but with high antenna gain. There are often many more legacy UEs than sensing UEs. Regardless of the type, the location of each sensing UE is known to the network and is determined by a global positioning signal (GPS) or calculated using other positioning methods such as round trip time (RTT) calculations, time delay of arrival (TDOA), etc.

[0130] Figure 6 An example 600 of a single-base ISAC in accordance with aspects of the present disclosure is illustrated. A single-base ISAC has the advantage of not requiring the Tx entity and the Rx entity to be paired or grouped since they are the same entity, and the ISAC's reuse of OFDM symbols allows the same hardware chain to be used for both sensing and communication. Figure 6 In the example shown in , a single gNB transmits a sensing signal using a TX antenna panel and receives a reflected sensing signal via an RX antenna panel. Figure 6 In the example shown in , the sensing signal is reflected from the UAV, but this technique can be used to sense other types of objects. Information about the reflected sensing signal is typically processed by a location server, which may be integrated with the gNB or may be separate from the gNB.

[0131] In order to accurately estimate the distance and speed of the target object, the sensing UE may need to sense for a certain duration, for example, to measure micro-Doppler frequency characteristics. In order to accurately estimate the location of the target object, multi-base sensing may be required. Figure 7 An example of this operation is shown in .

[0132] Figure 7An example 700 of a multi-base ISAC in accordance with aspects of the present disclosure is illustrated. Dual-base and multi-base ISACs have the advantage that self-interference mitigation is not required, and the reuse of OFDM symbols by the ISAC allows the same hardware chain to be used for both sensing and communication. Figure 7 In the example shown in , the first gNB transmits a sensing signal using a TX antenna panel. The sensing signal is reflected from a UAV or other object. The reflected signal is received by a second gNB, which receives the reflected sensing signal via an RX antenna panel. The reflected sensing signal is received by a sensing UE. Both the second gNB and the sensing UE will typically report the received reflected sensing signal to a location server, which may be integrated with the first gNB or the second gNB or may be separate from the first gNB or the second gNB. Although Figure 7 The use of a mobile phone as a sensing UE is shown, but other types of UEs may be sensing UEs, such as a connected vehicle, a roadside unit (RSU), or Figure 7 Other types of sensing UEs not shown.

[0133] Figure 8 An example 800 of UE-assisted dual-base sensing in accordance with aspects of the present disclosure is illustrated. In UE-assisted dual-base sensing, a sensing UE may be required to perform multiple sensing-based measurements. Figure 8 In the example 800 shown in FIG. 8 , the gNB may scan for different sensing signals (in Figure 8 The gNB may include multiple beams (shown as beam 1, beam 2, and beam 3 in FIG), and a sensing UE may be configured to perform sensing for each beam. For each beam, the gNB transmits a reference signal, and the sensing UE measures the signal that propagates directly to the UE (e.g., beam 3) or is reflected by a background object or a target object (e.g., beam 1 and beam 2). Based on the measured signal, the sensing UE attempts to sense the distance and velocity of the target object and identify the type of the target object. In some aspects, the measurement may be continued for a certain duration in order to identify the target object. For example, the measurement of a micro-Doppler frequency signature may be used to distinguish a bird from a UAV, and the measurement of the micro-Doppler frequency signature may require continuous measurement for tens of milliseconds.

[0134] Fig. 9 An example 900 of UE-assisted multistatic sensing according to various aspects of the present disclosure is illustrated. Multistatic sensing can be used to estimate the location of a target object, and in this example 900, a sensing UE is configured to measure and report the location of the target object from (at Fig. 9 The sensing signals of two different gNBs (shown as gNB 1 and gNB 2) are shown in FIG.

[0135] One problem that conventional approaches for dual-base or multi-base sensing do not address is that because each sensing-based measurement consumes certain computational and memory resources, a UE can only perform at most a limited number of sensing tasks simultaneously. The computational complexity may depend on the sensing type, for example, distance estimation, velocity estimation, and micro-Doppler signature estimation may each have different computational and memory resource requirements. For example, the computation of the micro-Doppler frequency signature requires storing the channel state for a relatively long duration. Furthermore, the computational requirements increase in proportion to the bandwidth, and the sensing signals are typically large bandwidth signals. Therefore, the gNB or other transmitter of the sensing signal may request the sensing UE to perform a sensing operation that the sensing UE cannot support, either because the UE does not have sufficient computational and / or memory resources to perform that type of sensing in any case, or because the UE's computational and / or memory resources are currently occupied by too many other sensing operations to perform the additional sensing operations requested by the gNB.

[0136] This is further complicated by the fact that, in order to reduce signaling latency, sensing-based measurements are triggered by layer 1 signaling (e.g., DCI), so the UE has no chance to feedback its acceptance or rejection of the measurement configuration. High-layer signaling may take tens of milliseconds, which may lead to sensing failures when the target is moving quickly.

[0137] Therefore, it is necessary for the UE to be able to indicate to the gNB in ​​advance the processing capability of the UE for sensing-based measurements. Knowing this sensing processing capability, the gNB can configure an appropriate number of sensing-based measurements to each sensing UE. For example, if the sensing processing capability of one sensing UE is exhausted, the gNB can select another sensing UE. In this way, the gNB or other entity can avoid invalid configuration of the sensing UE, for example, the gNB or other entity can avoid making sensing requests that the sensing UE cannot handle, thereby improving sensing performance and reducing sensing latency.

[0138] Fig.10 1 is a signaling and event diagram illustrating a process 1000 associated with sensing processing capability reporting in UE-assisted dual-base or multi-base sensing according to aspects of the present disclosure. Fig.10 In the example illustrated in , process 1000 involves a sensing transmitter (TX) 1002 (e.g., a gNB) and a sensing receiver (RX) 1004 (e.g., a sensing UE).

[0139] exist Fig.10In the example shown, at box 1006, the sensing Tx 1002 transmits a configuration of a set of possible sensing types to the sensing Rx 1004. This configuration can be transmitted via an RRC message, a medium access control (MAC) control element (MAC CE), a downlink control information (DCI), or other means. In some aspects, the configuration can describe different types of sensing, such as distance estimation, speed estimation, micro-Doppler characteristic estimation, etc. In some aspects, the configuration can associate time and / or frequency requirements with one or more sensing types in different sensing types. In some aspects, the configuration can associate priorities, latency requirements, or other constraints with one or more sensing types in different sensing types. In some aspects, the sensing Tx 1002 can also configure the maximum number of frequency domain samples (subcarriers) and the maximum number of time domain samples (symbols) of the sensing reference signal resources.

[0140] exist Fig.10 In the example shown in FIG. 1004 , at block 1008, sensing Rx 1004 reports sensing processing capabilities of sensing Rx 1004 to sensing Tx 1002. This report may be transmitted via a radio resource control (RRC) message or other means. In some aspects, the sensing processing capabilities of sensing Rx 1004 may be described in terms of the number of processing resources, processing latency, power constraints, time and / or frequency constraints, and the like.

[0141] exist Fig.10 In the example shown in FIG. 10 , at block 1010, the sensing Tx 1002 determines that a sensing task is needed, such as a sensing task arriving for processing by the sensing Tx 1002. The sensing task may be performed periodically or aperiodically and may be generated by the sensing Tx 1002 or by some entity other than the sensing Tx 1002.

[0142] exist Fig.10 In the example shown in FIG. 1004 , the sensing Tx 1002 determines whether the sensing Rx 1004 has sufficient processing resources to perform the sensing task, for example, based on the sensing processing capability report received from the sensing Rx 1004 at block 1008. In some aspects, if the sensing Rx 1004 receives a request to perform a sensing task that the sensing Rx 1004 cannot support, the sensing Rx 1004 simply ignores the request. Since this may result in sensing inefficiencies, if the sensing Tx 1002 determines that the sensing Rx 1004 does not have sufficient resources to perform the sensing task, the sensing Rx 1004 may instead decide to recruit a different sensing UE to perform the sensing task.

[0143] exist Fig.10In the illustrated example, at block 1012, the sensing Tx 1002 determines that the sensing Rx 1004 has sufficient sensing processing resources to perform the sensing task. In some aspects, the sensing Tx 1002 may maintain a running list of all sensing tasks that it has assigned to a particular sensing Rx, and before assigning a sensing task to a particular sensing Rx, the sensing Tx 1002 may first determine whether the amount of unused sensing processing resources within the sensing Rx is sufficient to handle the particular type of sensing task required.

[0144] exist Fig.10 In the example shown in, at box 1014, sensing Tx 1002 configures sensing Rx 1004 to perform a sensing task. In some aspects, the configuration may be part of downlink control information (DCI) transmitted from sensing Tx 1002 to sensing Rx 1004. In some aspects, sensing Tx 1002 may configure sensing Rx 1004 with the priority of each sensing measurement, for example, via RRC, MAC CE or SCI. In some aspects, if the measurement is performed via DCI, one or more bits are used to indicate the priority level. In some embodiments, if sensing Rx 1004 receives a sensing measurement configuration in which the total processing resource consumption exceeds its capability, sensing Rx 1004 may select sensing measurement from high priority to low priority.

[0145] exist Fig.10 In the example shown in FIG. 1 , the sensing Tx 1002 transmits one or more sensing signals at block 1016. Depending on the sensing type, the sensing Tx 1002 may transmit the one or more signals one or more groups of times.

[0146] exist Fig.10 In the example shown in , at block 1018 , if sufficient sensing processing resources are still available on the sensing Rx 1004 , the sensing Rx 1004 performs sensing processing according to the configuration of the sensing measurement in block 1014 .

[0147] For some types of sensing UEs, processing resources used for sensing are dynamically shared with other applications, for example for baseband or higher layer communication processing or for video processing. Fig.10 In the example shown in FIG, at block 1020, the sensing Rx 1004 may transmit a message to the sensing Tx 1002 to indicate an updated sensing processing capability (i.e., an updated number of SPUs) and / or processing latency for each sensing type. In some aspects, this update may be transmitted via RRC signaling, MAC CE, uplink control information (UCI), or other means.

[0148] Sensing Processing Unit (SPU). In some aspects, in order to simplify the steps of reporting the sensing processing resources possessed by a particular sensing UE and determining whether a particular sensing UE has a sufficient amount of sensing processing resources remaining to handle a sensing task, the concept of a sensing processing unit (SPU) may be adopted. An SPU is a logical construct that represents a certain amount of computing resources and storage capacity that may be required for a sensing task and that a sensing UE may possess. In some aspects, each SPU represents a predefined amount of computing resources and storage capacity.

[0149] In some aspects, the sensing Rx 1004 may report the sensing processing capability of the Rx to the sensing Tx 1002, for example, through RRC signaling, based on the total number of SPUs. In some aspects, the sensing Rx 1004 may indicate to the sensing Tx 1002 how many SPUs each type of sensing task consumes. For example, the sensing Rx 1004 may indicate that the distance calculation requires an X number of SPUs, the speed estimation requires a Y number of SPUs, and the micro-Doppler calculation requires a Z number of SPUs. In some aspects, the values ​​of X, Y, and Z are based on the preconfigured "maximum number of frequency domain samples (subcarriers) and maximum number of time domain samples (symbols) of the sensing reference signal resources". In some aspects, the definition of SPU may be specified by an industry standard.

[0150] In a specific implementation using SPUs, in some aspects, before the sensing Tx 1002 allocates a sensing measurement to the sensing Rx 1004 via a DCI, the sensing Tx 1002 should ensure that the processing resource consumption of this sensing measurement can be supported by the remaining (unused) SPUs of the sensing Rx 1004. In some aspects, if the sensing Rx 1004 receives a DCI containing a measurement configuration whose processing resource consumption exceeds that of its spare SPUs, the sensing Rx 1004 can ignore the DCI. When sensing tasks arrive periodically or aperiodically, unused SPUs are assigned to perform new sensing tasks. During the time when all SPUs in the SPUs of the Rx 1004 are occupied by sensing tasks, the sensing Tx 1002 should expect that the sensing Rx 1004 will ignore any newly received sensing tasks.

[0151] In some aspects, in order to assist the sensing Tx 1002 in determining whether the sensing Rx 1004 can handle the new sensing task, the sensing Rx 1004 may report the processing delay of each sensing type to the sensing Tx 1002, for example, through RRC signaling. For example, the sensing Rx 1004 may report to the sensing Tx 1002 that the distance estimation consumes an X number of SPUs for an L number of symbols; the speed estimation consumes a Y number of SPUs for an M number of symbols; and the micro-Doppler calculation consumes a Z number of SPUs for an N number of symbols. In some aspects, the numbers L, M, and N may be calculated based on a preconfigured maximum number of frequency domain samples (subcarriers) and a maximum number of time domain samples (symbols) of the sensing reference signal resources. Therefore, in some embodiments, each sensing type occupies a known number of SPUs with a duration from receiving the sensing signal to transmitting the measurement result.

[0152] Fig.11 An example 1100 is illustrated in which a sensing Rx reports how many sensing processing units (SPUs) it supports in accordance with aspects of the present disclosure. Fig.11 In the example illustrated in FIG. , the sensing Rx 1004 has reported that it has Fig.11 In FIG. 1 , there are four SPUs identified as SPU1, SPU2, SPU3, and SPU4, which in this case means that the sensing Rx 1004 can only perform the sensing tasks equivalent to 4 SPUs at a time. Fig.11 In the example shown in FIG. 1 , the sensing Rx 1004 is assigned a first sensing task which starts at time t1 and occupies Fig.11 , shown as consuming two SPUs, SPU1 and SPU2.

[0153] exist Fig.11 In the example shown in FIG. 1 , the sensing Rx 1004 is assigned the second sensing task, which starts at time t2 and occupies Fig.11 At time t3, the first sensing task ends, thereby releasing SPU1 and SPU2.

[0154] exist Fig.11 In the example shown in FIG. 1 , the sensing Rx 1004 is assigned the third sensing task, which starts at time t4 and occupies Fig.11 In FIG, three SPUs are shown as consuming SPU1, SPU2 and SPU4. Fig.11In the example shown in , from time t4 to time t5, all available SPUs in the available SPUs are occupied, so the sensing Tx 1002 knows not to configure the sensing Rx 1004 to perform any other sensing tasks. At time t5, the third sensing task is completed, freeing SPU1, SPU2, and SPU4 for more sensing tasks. At time t6, the second sensing task is completed, freeing SPU3 for another sensing task.

[0155] Some sensing tasks, such as for Doppler frequency or micro-Doppler signature estimation, involve measurements at multiple occasions. In these scenarios, the time that an SPU is considered occupied by a sensing task may be different, depending on the specific implementation.

[0156] Fig. 12A and Fig. 12B Two different calculations for SPU occupancy are shown. Fig. 12A In the example, the SPU is considered to be a sensor signal (in Fig. 12A and Fig. 12B The SPU is occupied during the time period during which the SPU (shown as a box labeled "TX") is received and stores the measurements of the plurality of sensing signals. After the last sensing signal is received (or after a sufficient number of sensing signals have been received), the SPU is occupied to process the received data and generate a report, which is transmitted at the end of the Rx sensing processing step. This specific implementation does not require additional storage external to the SPU.

[0157] exist Fig. 12B In the example, multiple sensing signals are measured and the data is stored in some form of storage external to the sensing SPU, and the SPU is not considered occupied until after the last sensing signal is received, during which time the SPU processes the received data and generates a report.

[0158] Fig.13 is a flow chart of an example process 1300 associated with sensing processing capability reporting in UE-assisted dual-base sensing. In some implementations, Fig.13 One or more process blocks of may be performed by a sensing signal transmitter (eg, BS304, sensing signal Tx 1002). In some specific implementations, Fig.13 One or more process blocks of may be performed by another device or a group of devices separate from or including the sensing signal transmitter. Additionally or alternatively, Fig.13 One or more process blocks of process 1300 may be performed by one or more components of a device (such as a processor, memory, transceiver), any or all of which may be means for performing the operations of process 1300.

[0159] like Fig.13 As shown in , process 1300 may include: at block 1310, transmitting first information specifying a set of one or more sensing types to a sensing signal receiver. The means for performing the operation of block 1310 may include a processor, a memory, or a transceiver of any of the devices described herein. For example, BS 304 may use transmitter 354 to transmit the first information.

[0160] like Fig.13 As further shown in FIG. 1 , process 1300 may include, at block 1320, receiving second information specifying the sensing processing capability of the sensing signal receiver from the sensing signal receiver. The means for performing the operations of block 1320 may include a processor, a memory, or a transceiver of any of the devices described herein. For example, BS 304 may use receiver 350 to receive the second information specifying the sensing processing capability of the sensing signal receiver from the sensing signal receiver.

[0161] like Fig.13 As further shown in FIG. 1 , process 1300 may include, at block 1330, determining to select or not select a sensing signal receiver to perform a sensing task, the sensing task including bistatic sensing or multistatic sensing, based at least in part on the sensing processing capability of the sensing signal receiver. The means for performing the operations of block 1330 may include a processor, a memory, or a transceiver of any of the devices described herein. For example, BS 304 may determine to select or not select a sensing signal receiver to perform a sensing task using processor 384 and memory 386.

[0162] In some aspects, determining whether to select or not select a sensing signal receiver to perform a sensing task based at least in part on the second information includes: determining to perform the sensing task; determining whether the sensing signal receiver has sufficient sensing processing capabilities to perform the sensing task based on the second information; configuring the sensing signal receiver to perform the sensing task; and sending at least one sensing signal; and in response to determining that the sensing signal receiver does not have sufficient sensing processing capabilities to perform the sensing task, not configuring the sensing signal receiver to perform the sensing task.

[0163] In some aspects, in response to determining that the sensing signal receiver does not have sufficient sensing processing capabilities to perform the sensing task, the sensing signal transmitter configures a second sensing signal receiver different from the sensing signal receiver to perform the sensing task.

[0164] In some aspects, process 1300 includes receiving third information from a sensing signal receiver that updates a sensing processing capability of the sensing signal receiver, and determining to select or not select the sensing signal receiver to perform a second sensing task based at least in part on the updated sensing processing capability of the sensing signal receiver.

[0165] In some aspects, receiving second information specifying sensing processing capabilities of the sensing signal receiver includes receiving information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, where each SPU represents a predefined amount of computing resources.

[0166] In some aspects, each SPU further represents a predefined data storage capacity for each sensing task.

[0167] In some aspects, each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols on which each sensing task may be performed.

[0168] In some aspects, each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols in which each type of sensing task may be performed.

[0169] Process 1300 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Fig.13 An example block diagram of process 1300 is shown, but in some implementations, process 1300 may include Fig.13 The blocks depicted in the process 1300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1300. Additionally or alternatively, two or more blocks in the blocks of the process 1300 may be performed in parallel.

[0170] Fig.14 1400 is a flow chart of an example process 1400 associated with sensing processing capability reporting in UE-assisted dual-base or multi-base sensing. In some implementations, Fig.14 One or more process blocks of may be performed by a sensing signal receiver (eg, UE 302, sensing signal Rx 1004). In some implementations, Fig.14 One or more process blocks of may be performed by another device or a group of devices separate from or including the sensing signal receiver. Additionally or alternatively, Fig.14 One or more process blocks of process 1400 may be performed by one or more components of a device (such as a processor, memory, transceiver), any or all of which may be means for performing the operations of process 1400.

[0171] like Fig.14As shown in , process 1400 may include: at block 1410, receiving first information specifying a set of one or more sensing types from a sensing signal transmitter. The means for performing the operation of block 1410 may include a processor, a memory, or a transceiver of any of the devices described herein. For example, UE 302 may receive the first information via receiver 312.

[0172] like Fig.14 As further shown in FIG. 1 , process 1400 may include: at block 1420, transmitting second information specifying the sensing processing capability of the sensing signal receiver to the sensing signal transmitter. The means for performing the operation of block 1420 may include a processor, a memory, or a transceiver of any of the devices described herein. For example, UE 302 may transmit the second information via transmitter 314.

[0173] In some aspects, process 1400 includes receiving third information from the sensing signal transmitter that configures the sensing signal receiver to perform the sensing task, and performing the sensing task according to the third information.

[0174] In some aspects, performing the sensing task based on the third information includes measuring at least one sensing signal, and reporting a result of measuring the at least one sensing signal to the network entity.

[0175] In some aspects, process 1400 includes detecting a change in a sensing processing capability of the sensing signal receiver, and transmitting fourth information indicating the change in the sensing processing capability of the sensing signal receiver to the sensing signal transmitter.

[0176] In some aspects, transmitting the second information specifying the sensing processing capability of the sensing signal receiver includes transmitting information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, where each SPU represents a predefined amount of computing resources.

[0177] In some aspects, each SPU further represents a predefined data storage capacity for each sensing task.

[0178] In some aspects, each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols on which each sensing task may be performed.

[0179] In some aspects, each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols in which each type of sensing task may be performed.

[0180] Process 1400 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Fig.14 An example block diagram of process 1400 is shown, but in some implementations, process 1400 may include Fig.14 The blocks depicted in the process 1400 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1400. Additionally or alternatively, two or more blocks in the blocks of the process 1400 may be performed in parallel.

[0181] As will be appreciated, the technical advantage of the technology for providing sensing processing capability reporting in UE-assisted dual-base or multi-base sensing is that by making the sensing signal transmitter aware of the sensing processing capability of the UE, it is possible to avoid selecting a sensing UE that does not have the capability to perform a sensing task. This makes the network more efficient and allows for faster response times for sensing tasks.

[0182] In the above detailed description, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each dependent clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the dependent clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the dependent clause aspect with any other dependent clause or independent clause or any feature with other dependent clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is clearly expressed or can be easily inferred that a specific combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0183] Specific implementation examples are described in the following numbered clauses:

[0184] Item 1. A method of wireless sensing performed by a sensing signal transmitter, the method comprising: transmitting first information specifying a set of one or more sensing types to a sensing signal receiver; receiving second information specifying a sensing processing capability of the sensing signal receiver from the sensing signal receiver; and determining, at least in part based on the sensing processing capability of the sensing signal receiver, to select or not select the sensing signal receiver to perform a sensing task, the sensing task comprising dual-base sensing or multi-base sensing.

[0185] Clause 2. A method according to clause 1, wherein determining whether to select or not select the sensing signal receiver to perform the sensing task based at least in part on the second information includes: determining to perform the sensing task; determining whether the sensing signal receiver has sufficient sensing processing capabilities to perform the sensing task based on the second information; in response to determining that the sensing signal receiver has sufficient sensing processing capabilities to perform the sensing task, configuring the sensing signal receiver to perform the sensing task and sending at least one sensing signal; and in response to determining that the sensing signal receiver does not have sufficient sensing processing capabilities to perform the sensing task, not configuring the sensing signal receiver to perform the sensing task.

[0186] Clause 3. The method of clause 2, wherein in response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal transmitter configures a second sensing signal receiver different from the sensing signal receiver to perform the sensing task.

[0187] Clause 4. The method according to any one of clauses 1 to 3 further includes: receiving third information from the sensing signal receiver to update the sensing processing capability of the sensing signal receiver; and determining whether to select or not select the sensing signal receiver to perform a second sensing task based at least in part on the updated sensing processing capability of the sensing signal receiver.

[0188] Clause 5. A method according to any one of clauses 1 to 4, wherein receiving the second information specifying the sensing processing capability of the sensing signal receiver includes receiving information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

[0189] Clause 6. The method of clause 5, wherein each SPU further represents a predefined data storage capacity for each sensing task.

[0190] Clause 7. A method according to any of clauses 5 to 6, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols capable of performing each sensing task.

[0191] Clause 8. A method according to any one of clauses 5 to 7, wherein each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

[0192] Clause 9. A method of wireless sensing performed by a sensing signal receiver, the method comprising: receiving first information specifying a set of one or more sensing types from a sensing signal transmitter; and transmitting second information specifying a sensing processing capability of the sensing signal receiver to the sensing signal transmitter.

[0193] Clause 10. The method according to clause 9, further comprising: receiving third information from the sensing signal transmitter to configure the sensing signal receiver to perform a sensing task; and performing the sensing task according to the third information.

[0194] Clause 11. The method of clause 10, wherein performing the sensing task according to the third information comprises: measuring at least one sensing signal; and reporting a result of measuring the at least one sensing signal to a network entity.

[0195] Clause 12. The method according to any one of clauses 9 to 11 further includes: detecting a change in the sensing processing capability of the sensing signal receiver; and transmitting fourth information indicating the change in the sensing processing capability of the sensing signal receiver to the sensing signal transmitter.

[0196] Clause 13. A method according to any one of clauses 9 to 12, wherein transmitting the second information specifying the sensing processing capabilities of the sensing signal receiver includes transmitting information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

[0197] Clause 14. The method of clause 13, wherein each SPU further represents a predefined data storage capacity for each sensing task.

[0198] Clause 15. A method according to any of clauses 13 to 14, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols capable of performing each sensing task.

[0199] Clause 16. A method according to any one of clauses 13 to 15, wherein each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

[0200] Item 17. A sensing signal transmitter, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit first information specifying a set of one or more sensing types to a sensing signal receiver via the at least one transceiver; receive second information specifying a sensing processing capability of the sensing signal receiver from the sensing signal receiver via the at least one transceiver; and determine, at least in part based on the sensing processing capability of the sensing signal receiver, to select or not select the sensing signal receiver to perform a sensing task, the sensing task comprising dual-base sensing or multi-base sensing.

[0201] Clause 18. A sensing signal transmitter according to Clause 17, wherein in order to determine whether to select or not select the sensing signal receiver to perform the sensing task based at least in part on the second information, the at least one processor is configured to: determine to perform the sensing task; determine whether the sensing signal receiver has sufficient sensing processing capabilities to perform the sensing task based on the second information; in response to determining that the sensing signal receiver has sufficient sensing processing capabilities to perform the sensing task, the sensing signal receiver performs the sensing task and sends at least one sensing signal; and in response to determining that the sensing signal receiver does not have sufficient sensing processing capabilities to perform the sensing task, not configure the sensing signal receiver to perform the sensing task.

[0202] Clause 19. The sensing signal transmitter of Clause 18, wherein in response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal transmitter configures a second sensing signal receiver different from the sensing signal receiver to perform the sensing task.

[0203] Clause 20. A sensing signal transmitter according to any one of clauses 17 to 19, wherein the at least one processor is further configured to: receive third information that updates the sensing processing capability of the sensing signal receiver from the sensing signal receiver via the at least one transceiver; and determine whether to select or not select the sensing signal receiver to perform a second sensing task based at least in part on the updated sensing processing capability of the sensing signal receiver.

[0204] Clause 21. A sensing signal transmitter according to any one of clauses 17 to 20, wherein receiving the second information specifying the sensing processing capability of the sensing signal receiver includes receiving information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

[0205] Clause 22. The sensing signal transmitter of Clause 21, wherein each SPU further represents a predefined data storage capacity for each sensing task.

[0206] Clause 23. A sensing signal transmitter according to any one of clauses 21 to 22, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

[0207] Item 24. A sensing signal receiver, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive first information specifying a set of one or more sensing types from a sensing signal transmitter via the at least one transceiver; and transmit second information specifying a sensing processing capability of the sensing signal receiver to the sensing signal transmitter via the at least one transceiver.

[0208] Clause 25. A sensing signal receiver according to Clause 24, wherein the at least one processor is further configured to: receive third information configuring the sensing signal receiver to perform a sensing task from the sensing signal transmitter via the at least one transceiver; and perform the sensing task according to the third information.

[0209] Clause 26. The sensing signal receiver according to clause 25, wherein in order to perform the sensing task according to the third information, the at least one processor is configured to: measure at least one sensing signal; and report a result of measuring the at least one sensing signal to a network entity.

[0210] Clause 27. A sensing signal receiver according to any one of clauses 24 to 26, wherein the at least one processor is further configured to: detect a change in the sensing processing capability of the sensing signal receiver; and transmit fourth information indicating the change in the sensing processing capability of the sensing signal receiver to the sensing signal transmitter via the at least one transceiver.

[0211] Clause 28. A sensing signal receiver according to any one of clauses 24 to 27, wherein transmitting the second information specifying the sensing processing capability of the sensing signal receiver includes transmitting information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

[0212] Clause 29. The sensing signal receiver of clause 28, wherein each SPU further represents a predefined data storage capacity for each sensing task.

[0213] Clause 30. A sensing signal receiver according to any one of clauses 28 to 29, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

[0214] Clause 31. An apparatus comprising: a memory; a transceiver; and a processor communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor configured to perform the method of any one of clauses 1 to 16.

[0215] Clause 32. An apparatus comprising means for performing the method of any one of clauses 1 to 16.

[0216] Clause 33. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising at least one instruction for causing a computer or a processor to perform the method according to any one of clauses 1 to 16.

[0217] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0218] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0219] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or performed using 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 an 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, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0220] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a 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 so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with 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 an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0221] In one or more example aspects, the function may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function may be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. Exemplarily and not restrictively, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or may also be used to carry or store desired program codes in the form of instructions or data structures and any other medium that can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server, or other remote sources using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc, as used herein, include 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.

[0222] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method for wireless sensing performed by a sensing signal transmitter, the method comprising: transmitting first information specifying a set of one or more sensing types to a sensing signal receiver; receiving, from the sensing signal receiver, second information specifying a sensing processing capability of the sensing signal receiver; as well as Based at least in part on the sensing processing capability of the sensing signal receiver, it is determined whether to select or not select the sensing signal receiver to perform a sensing task, the sensing task comprising bistatic sensing or multistatic sensing.

2. The method of claim 1 , wherein determining whether to select or not to select the sensing signal receiver to perform the sensing task based at least in part on the second information comprises: Determining to execute the sensing task; determining whether the sensing signal receiver has sufficient sensing processing capability to perform the sensing task based on the second information; In response to determining that the sensing signal receiver has sufficient sensing processing capability to perform the sensing task, configuring the sensing signal receiver to perform the sensing task and transmit at least one sensing signal; as well as In response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal receiver is not configured to perform the sensing task.

3. The method of claim 2, wherein in response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal transmitter configures a second sensing signal receiver different from the sensing signal receiver to perform the sensing task.

4. The method according to claim 1, further comprising: receiving, from the sensing signal receiver, third information for updating the sensing processing capability of the sensing signal receiver; as well as Based at least in part on the updated sensing processing capability of the sensing signal receiver, it is determined whether to select or not select the sensing signal receiver to perform a second sensing task.

5. The method of claim 1 , wherein receiving the second information specifying the sensing processing capabilities of the sensing signal receiver comprises receiving information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources. The method of claim 5 , wherein each SPU further represents a predefined data storage capacity for each sensing task.

7. The method of claim 5, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols capable of performing each sensing task.

8. The method of claim 5, wherein each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

9. A method of wireless sensing performed by a sensing signal receiver, the method comprising: receiving first information specifying a set of one or more sensing types from a sensing signal transmitter; as well as Second information specifying a sensing processing capability of the sensing signal receiver is transmitted to the sensing signal transmitter.

10. The method according to claim 9, further comprising: receiving, from the sensing signal transmitter, third information for configuring the sensing signal receiver to perform a sensing task; as well as The sensing task is performed according to the third information.

11. The method according to claim 10, wherein performing the sensing task according to the third information comprises: measuring at least one sensed signal; as well as A result of measuring the at least one sensing signal is reported to a network entity.

12. The method according to claim 9, further comprising: detecting a change in the sensing processing capability of the sensing signal receiver; as well as Fourth information indicating the change in the sensing processing capability of the sensing signal receiver is transmitted to the sensing signal transmitter.

13. The method of claim 9, wherein transmitting the second information specifying the sensing processing capability of the sensing signal receiver comprises transmitting information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

14. The method of claim 13, wherein each SPU further represents a predefined data storage capacity for each sensing task.

15. The method of claim 13, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each sensing task and a maximum number of time domain symbols capable of performing each sensing task.

16. The method of claim 13, wherein each sensing task comprises a type of sensing task from a plurality of types of sensing tasks, and wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

17. A sensing signal transmitter, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmitting, via the at least one transceiver, to a sensing signal receiver, first information specifying a set of one or more sensing types; receiving, from the sensing signal receiver via the at least one transceiver, second information specifying a sensing processing capability of the sensing signal receiver; as well as Based at least in part on the sensing processing capability of the sensing signal receiver, it is determined whether to select or not select the sensing signal receiver to perform a sensing task, the sensing task comprising bistatic sensing or multistatic sensing.

18. The sensing signal transmitter according to claim 17, wherein in order to determine whether to select or not to select the sensing signal receiver to perform the sensing task based at least in part on the second information, the at least one processor is configured to: Determining to execute the sensing task; determining whether the sensing signal receiver has sufficient sensing processing capability to perform the sensing task based on the second information; In response to determining that the sensing signal receiver has sufficient sensing processing capability to perform the sensing task, the sensing signal receiver performs the sensing task and transmits at least one sensing signal; as well as In response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal receiver is not configured to perform the sensing task.

19. The sensing signal transmitter of claim 18, wherein in response to determining that the sensing signal receiver does not have sufficient sensing processing capability to perform the sensing task, the sensing signal transmitter configures a second sensing signal receiver different from the sensing signal receiver to perform the sensing task.

20. The sensing signal transmitter according to claim 17, wherein the at least one processor is further configured to: receiving, from the sensing signal receiver via the at least one transceiver, third information that updates the sensing processing capability of the sensing signal receiver; and Based at least in part on the updated sensing processing capability of the sensing signal receiver, it is determined whether to select or not select the sensing signal receiver to perform a second sensing task.

21. The sensing signal transmitter of claim 17, wherein receiving the second information specifying the sensing processing capability of the sensing signal receiver comprises receiving information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

22. The sensing signal transmitter of claim 21, wherein each SPU further represents a predefined data storage capacity for each sensing task.

23. The sensing signal transmitter of claim 21, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

24. A sensing signal receiver, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, first information from a sensing signal transmitter specifying a set of one or more sensing types; as well as Second information specifying a sensing processing capability of the sensing signal receiver is transmitted to the sensing signal transmitter via the at least one transceiver.

25. The sensing signal receiver of claim 24, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, from the sensing signal transmitter third information that configures the sensing signal receiver to perform a sensing task; and The sensing task is performed according to the third information.

26. The sensing signal receiver according to claim 25, wherein in order to perform the sensing task according to the third information, the at least one processor is configured to: measuring at least one sensed signal; and A result of measuring the at least one sensing signal is reported to a network entity.

27. The sensing signal receiver of claim 24, wherein the at least one processor is further configured to: detecting a change in the sensing processing capability of the sensing signal receiver; and Fourth information indicating the change in the sensing processing capability of the sensing signal receiver is transmitted to the sensing signal transmitter via the at least one transceiver.

28. The sensing signal receiver of claim 24, wherein transmitting the second information specifying the sensing processing capability of the sensing signal receiver comprises transmitting information indicating how many sensor processing units (SPUs) the sensing signal receiver supports, wherein each SPU represents a predefined amount of computing resources.

29. The sensing signal receiver of claim 28, wherein each SPU further represents a predefined data storage capacity for each sensing task.

30. The sensing signal receiver of claim 28, wherein each SPU is further associated with at least one of a maximum number of frequency subcarriers supported for each type of sensing task and a maximum number of time domain symbols capable of performing each type of sensing task.

Images