BI-STATIC SENSING CHARGING SUBSCRIPTION

This disclosure provides systems, methods, and devices for wireless communication that support a sensing charging subscription. In a first aspect, a method of wireless communication includes transmitting a request to a network entity to participate in a bi-static sensing operation. The method also includes performing the bi-static sensing operation with the network entity. The method further includes transmitting transmit sensing information associated with the bi-static sensing operation. The charging information is associated with sensing charging subscription information. Other aspects and features are also claimed and described.

TECHNICAL FIELD

Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to a sensing charging subscription, such as a sensing charging subscription associated with a bi-static sensing operation. Some features may enable and provide sensing operation management and control, reduced overhead signaling, efficient spectrum usage, reduced device hardware, or a combination thereof.

INTRODUCTION

Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, and the like. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple access networks that support communications for multiple users by sharing the available network resources.

A wireless communication network may include several components. These components may include wireless communication devices, such as base stations (or node Bs) that may support communication for a number of user equipments (UEs). A UE may communicate with a base station via downlink and uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.

A base station may transmit data and control information on a downlink to a UE or may receive data and control information on an uplink from the UE. On the downlink, a transmission from the base station may encounter interference due to transmissions from neighbor base stations or from other wireless radio frequency (RF) transmitters. On the uplink, a transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with the neighbor base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

Conventional 3GPP systems are configured to manage communication-based subscription charges, such as communication charges for NR communication. To illustrate, a 3GPP system may use or implement online charging, which is a mechanism where charging information can affect, in real-time, the service rendered. The online charging for communication-based subscriptions may be event-based or session-based. To implement the online charging, a direct interaction between the charging mechanism and control of network resource usage. Although the 3GPP systems are configured to manage the communication-based subscription charges, the 3GPP systems are not configured to manage and charge for sensing services, such as long range or short-range sensing, that may be offered over 5G.

BRIEF SUMMARY OF SOME EXAMPLES

In one aspect of the disclosure, a method for wireless communication is performed by a user equipment (UE). The method includes transmitting a request to a network entity to participate in a bi-static sensing operation. The method further includes performing the bi-static sensing operation with the network entity. The method also includes transmitting transmit sensing information associated with the bi-static sensing operation. The transmit sensing information is associated with sensing charging subscription information.

In an additional aspect of the disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to transmit a request to a network entity to participate in a bi-static sensing operation. The at least one processor is further configured to perform the bi-static sensing operation with the network entity. The at least one processor is also configured to transmit transmit sensing information associated with the bi-static sensing operation. The transmit sensing information is associated with sensing charging subscription information.

In an additional aspect of the disclosure, an apparatus includes means transmitting a request to a network entity to participate in a bi-static sensing operation. The apparatus further includes means for performing the bi-static sensing operation with the network entity. The apparatus also includes means for transmitting transmit sensing information associated with the bi-static sensing operation. The transmit sensing information is associated with sensing charging subscription information.

In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include transmitting a request to a network entity to participate in a bi-static sensing operation. The operations further include performing the bi-static sensing operation with the network entity. The operations also include transmitting transmit sensing information associated with the bi-static sensing operation. The transmit sensing information is associated with sensing charging subscription information.

In one aspect of the disclosure, a method for wireless communication is performed by a network entity. The method includes receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The method further includes performing the bi-static sensing operation with the U. The method also includes transmitting receive sensing information associated with the bi-static sensing operation.

In an additional aspect of the disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive, from a UE, a request to assist the UE in a bi-static sensing operation. The at least one processor is further configured to perform the bi-static sensing operation with the U. The at least one processor is also configured to transmit receive sensing information associated with the bi-static sensing operation.

In an additional aspect of the disclosure, an apparatus includes means for receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The apparatus further includes means for performing the bi-static sensing operation with the U. The apparatus also includes means for transmitting receive sensing information associated with the bi-static sensing operation.

In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The operations further include performing the bi-static sensing operation with the U. The operations also include transmitting receive sensing information associated with the bi-static sensing operation.

In one aspect of the disclosure, a method for wireless communication is performed by a network. The method includes transmitting, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or more bistatic sensing operations. The method further includes receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The method also includes transmitting network entity information to the UE. The network entity information indicates the network entity selected from one or more network entities available to participate in the bi-static sensing operation.

In an additional aspect of the disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to transmit, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or more bistatic sensing operations. The at least one processor is further configured to receive, from a UE, a request to assist the UE in a bi-static sensing operation. The at least one processor is also configured to transmit network entity information to the UE. The network entity information indicates the network entity selected from one or more network entities available to participate in the bi-static sensing operation.

In an additional aspect of the disclosure, an apparatus includes means for transmitting, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or more bistatic sensing operations. The apparatus further includes means for receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The apparatus also includes means for transmitting network entity information to the UE. The network entity information indicates the network entity selected from one or more network entities available to participate in the bi-static sensing operation.

In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include transmitting, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or more bistatic sensing operations. The operations further include receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The operations also include transmitting network entity information to the UE. The network entity information indicates the network entity selected from one or more network entities available to participate in the bi-static sensing operation.

DETAILED DESCRIPTION

The present disclosure provides systems, apparatus, methods, and computer-readable media that support a sensing charging subscription or a bi-static sensing operation. For example, the present disclosure describes sensing charging subscription information that is associated with a sensing charging subscription for a user equipment (UE) configured to perform a sensing operation, such as bi-static sensing. To illustrate, the UE may initiate a sensing operation, such as a bi-static sensing operation, that is performed with the assistance of a network entity, such as a base station, another UE, a roadside unit (RSU), or another device. In some implementations, a network (e.g., a centralized controller or core network) is configured to determine a fee for a sensing service or a sensing operations, and to assist the UE to perform the sensing operation. To illustrate, the network may be configured to determine the fee based on a bi-static sensing measurement information, a resource available at the network entity for the bi-static sensing operation, a resource needed by the UE for the bi-static sensing operation, a location of the UE, a mobility of the UE, a location of the network entity, a mobility of the network entity, a distance between the UE and the network entity, an operational mode at the network entity, a pre-sensing operation, a pre-sensing measurement report, or a combination thereof. Additionally, the network may be configured to identify one or more network entities that are suitable or available to perform the sensing operation with the UE. For example, the network may identify the one or more network entities based on a location of the network entity, a location of the UE, capability information received from the network entity, a fee for use of the network entity, sensing charging subscription information associated with the UE, a quality of service requested by the UE, an available quality of service associated with the network entity, or a combination thereof. As another example, the network may communicate or negotiate with the UE to determine a sensing resource, a sensing transmission parameter, a sensing fee, or a combination thereof. In some implementations, the UE may perform a pre-sensing operation with one or more network entities to select the network entity to perform the bi-static sensing operation with. In some implementations, the network entity, the network, or both, may perform a handover to further assist (or to continue to assist) the UE with performing the sensing operation, such as the bi-static sensing operation.

Particular implementations of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for supporting a sensing charging subscription. For example, the techniques described provide techniques, information, and signaling for the UE to perform sensing operations according to a sensing subscription. A system, such as a 3GPP system may advantageously manage sensing based subscription charges for the sensing operations or services, such as 5G or NR sensing services, associated with the UE. The techniques described herein enable reduced overhead, efficient spectrum usage, improved spectrum reuse, reduced device hardware, improved hardware reuse, or a combination thereof.

Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is often subdivided, based on frequency or wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” (mmWave) band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “mmWave” band.

While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, implementations or uses may come about via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail devices or purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described aspects. It is intended that innovations described herein may be practiced in a wide variety of implementations, including both large devices or small devices, chip-level components, multi-component systems (e.g., radio frequency (RF)-chain, communication interface, processor), distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

FIG.1is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include wireless network100. Wireless network100may for example, include a 5G wireless network. As appreciated by those skilled in the art, components appearing inFIG.1are likely to have related counterparts in other network arrangements including, for example, cellular-style network arrangements and non-cellular-style-network arrangements (e.g., device to device or peer to peer or ad hoc network arrangements, etc.).

Base stations105may communicate with a core network130and with one another. For example, base stations105may interface with the core network130through backhaul links132(e.g., via an S1, N2, N3, or other interface). Base stations105may communicate with one another over backhaul links (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105) or indirectly (e.g., via core network130).

In some implementations, core network130includes or is coupled to a Location Management Function (LMF)131, which is an entity in the 5G Core Network (5GC) supporting various functionality, such as managing support for different location services for one or more UEs. For example the LMF131may include one or more servers, such as multiple distributed servers. Base stations105may forward location messages to the LMF131and may communicate with the LMF via a NR Positioning Protocol A (NRPPa). The LMF131is configured to control the positioning parameters for UEs115and the LMF131can provide information to the base stations105and UE115so that action can be taken at UE115. In some implementations, UE115and base station105are configured to communicate with the LMF131via an Access and Mobility Management Function (AMF).

FIG.2is a block diagram illustrating examples of base station105and UE115according to one or more aspects. Base station105and UE115may be any of the base stations and one of the UEs inFIG.1. For a restricted association scenario (as mentioned above), base station105may be small cell base station105finFIG.1, and UE115may be UE115cor115doperating in a service area of base station105f, which in order to access small cell base station105f, would be included in a list of accessible UEs for small cell base station105f. Base station105may also be a base station of some other type. As shown inFIG.2, base station105may be equipped with antennas234athrough234t, and UE115may be equipped with antennas252athrough252rfor facilitating wireless communications.

At base station105, transmit processor220may receive data from data source212and control information from controller240, such as a processor. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, transmit processor220may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor220may also generate reference symbols, e.g., for the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and cell-specific reference signal. Transmit (TX) MIMO processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs)232athrough232t. For example, spatial processing performed on the data symbols, the control symbols, or the reference symbols may include precoding. Each modulator232may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator232may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators232athrough232tmay be transmitted via antennas234athrough234t, respectively.

Controllers240and280may direct the operation at base station105and UE115, respectively. Controller240or other processors and modules at base station105or controller280or other processors and modules at UE115may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated in or described with reference toFIGS.1-10, or other processes for the techniques described herein. Memories242and282may store data and program codes for base station105and UE115, respectively. Scheduler244may schedule UEs for data transmission on the downlink or the uplink.

FIG.3shows a diagram illustrating an example disaggregated base station300architecture. The disaggregated base station300architecture may include one or more central units (CUs)310that can communicate directly with a core network320via a backhaul link, or indirectly with the core network320through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC)325via an E2 link, or a Non-Real Time (Non-RT) RIC315associated with a Service Management and Orchestration (SMO) Framework305, or both). Core network320may include or correspond to core network130. A CU310may communicate with one or more distributed units (DUs)330via respective midhaul links, such as an F1 interface. The DUs330may communicate with one or more radio units (RUs)340via respective fronthaul links. The RUs340may communicate with respective UEs115via one or more radio frequency (RF) access links. In some implementations, the UE115may be simultaneously served by multiple RUs340.

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

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a transmission and reception point (TRP), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), a core network, a LFM, and/or a another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.

FIG.4is a block diagram of an example wireless communications system400that supports a sensing charging subscription according to one or more aspects. In some examples, wireless communications system400may implement aspects of wireless network100. Wireless communications system400includes UE115, base station105, core network130, and a network entity470. In some implementations, base station105and core network130may be individually or collectively referred to as a network, a network device, or a network system. Although one UE115, one base station105, and one network entity470are illustrated, in some other implementations, wireless communications system400may generally include multiple UEs115, multiple base station105, multiple network entities470, or a combination thereof.

In some implementations, wireless communications system400includes an object490, such as a stationary object or a mobile object. Object490may be sensed by a device, such as UE115, network entity470, base station105, or a combination thereof, based on one or more sensing operations. The one or more sensing operations may include a monostatic sensing operation or a bi-static sensing operation, as illustrative, non-limiting examples. In some implementations, the one or more sensing operations may be performed to detect object490, determine a location of object490, or a combination thereof.

UE115may include a device, such as a mobile device or a vehicle. UE115may be configured to performing sensing using one or more uplink (UL) resources. For example, sensing may include bi-static sensing or monostatic sensing. When UE115is a vehicle, UE115may perform one or more sensing operations to sense an environment, such as an indoor environment of the vehicle or an outdoor environment of the vehicle. To illustrate, UE115may sense for surrounding objects for automotive applications, such as collision avoidance. To enable UE side sensing, such as a joint communication and radar (JCR) sensing, the UL resources (e.g., communication resources) can be reused for sensing. For example, the UL resources may be shared between communication and radar modes. To illustrate, in some implementations, there could be separate resources for communication or radar that are used based on a TDM mode. In some such implementations, an SRS can be utilized as a sensing waveform. Alternatively, the same resource for communication and radar may be used that has a join co-design waveform.

UE115may include a variety of components (such as structural, hardware components) used for carrying out one or more functions described herein. For example, these components may include one or more processors402(hereinafter referred to collectively as “processor402”), one or more memory devices404(hereinafter referred to collectively as “memory404”), and one or more sensing devices415(hereinafter referred to collectively as “sensing device415”). Sensing device415may include or correspond to a bi-static sensing device. In some implementations, UE115may include an interface (e.g., a communication interface) that includes transmitter416, receiver418, or a combination thereof. Processor402may be configured to execute instructions405stored in memory404to perform the operations described herein. In some implementations, processor402includes or corresponds to one or more of receive processor258, transmit processor264, and controller280, and memory404includes or corresponds to memory282.

Memory404includes or is configured to store instructions405and information406. Information406may include capability information408, sensing charging subscription information409, and measurement information410. Capability information408may include or indicate one or more capabilities of UE115associated with performing a bi-static sensing operation. For example, capability information408may include or indicate whether UE115is configured to function as a transmit (Tx) device or a receive (Rx) device for the bi-static sensing operation. Additionally, or alternatively, capability information408may include or indicate a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof, associated with the bi-static sensing operation. Sensing charging subscription information409may include or indicate a sensing subscription associated with one or more sensing operations or one or more sensing services. The sensing subscription may include or indicate a functionality, a rule, a profile, a model, a charge fee, or a combination thereof. In some implementations, the sensing subscription is associated with or based on an agreement, such as a contract, that identifies or defines the sensing subscription of multiple available sensing subscriptions.

Measurement information410may include or indicate information based on a pre-sensing operation, the bi-static sensing operation, or a combination thereof. Measurement information410may include information generated by UE115, network entity470, another network entity, or a combination thereof. In some implementations, measurement information410includes a pre-sensing measurement report, a transmit sensing information (associated with a Tx device of a bi-static sensing operation), a receive sensing information (associated with an Rx device of a bi-static sensing operation), one or more parameters associated with a pre-sensing operation or a bi-static sensing operation, or a combination thereof. The transmit sensing report may include or indicate completion of the bi-static sensing operation, the receive sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof. The receive sensing information may include or indicate a received signal strength, a time domain parameter, a time travel time, a beam direction, a beam bandwidth, a quality of service, a location of an objection, or a combination thereof.

Sensing device415may be configured to be used in a bi-static sensing operation. Sensing device415includes one or more transmitters416(hereinafter referred to collectively as “transmitter416”), and one or more receivers418(hereinafter referred to collectively as “receiver418”). Transmitter416is configured to transmit reference signals, control information and data to one or more other devices, and receiver418is configured to receive references signals, synchronization signals, control information and data from one or more other devices. For example, transmitter416may transmit signaling, control information and data to, and receiver418may receive signaling, control information and data from, base station105. In some implementations, transmitter416and receiver418may be integrated in one or more transceivers. Additionally or alternatively, transmitter416or receiver418may include or correspond to one or more components of UE115described with reference toFIG.2. In some implementations, sensing device415is associated with a joint communication and radar (JCR) system. The JCR system may be categorized as a cooperative JCR system or a co-design of communication and radar systems. For example, sensing device415may be associated with the co-design of communication and radar systems. Although described as including both transmitter416and receiver418, in other implementations, sensing device415may include transmitter416but not receiver418, or may include receiver418but not transmitter416.

In some implementations, UE115may include one or more antenna arrays. The one or more antenna arrays may be coupled to transmitter416, receiver418, or a communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices, such as with the base station105. In some implementations, the antenna array may be configured to perform wireless communications using different beams, also referred to as antenna beams. The beams may include TX beams and RX beams. To illustrate, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple individual antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different respective beam that may have a different respective direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example using multiple RF chains of the UE115. Each individual set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different respective beam.

UE115may include one or more components as described herein with reference to UE115. In some implementations, UE115is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

Network entity470may include a device, such as a base station, a roadside unit, a node, or another UE. Network entity470may be a mobile device or a stationary device. Network entity470may include a variety of components (such as structural, hardware components) used for carrying out one or more functions described herein. For example, these components may include one or more processors472(hereinafter referred to collectively as “processor472”), one or more memory devices474(hereinafter referred to collectively as “memory474”), and one or more sensing devices475(hereinafter referred to collectively as “sensing device475”). Sensing device475may include or correspond to a bi-static sensing device. In some implementations, network entity470may include an interface (e.g., a communication interface) that includes transmitter476, receiver478, or a combination thereof. Processor472may be configured to execute instructions480stored in memory474to perform the operations described herein. In some implementations, processor472includes or corresponds to one or more of receive processor258, transmit processor264, and controller280, and memory474includes or corresponds to memory282.

Memory474includes or is configured to store instructions480and information484. Information484may include or correspond to information406.

Sensing device475may include or correspond to sending device415. Sensing device475may be configured to be used in a bi-static sensing operation. Sensing device475includes one or more transmitters476(hereinafter referred to collectively as “transmitter476”), and one or more receivers478(hereinafter referred to collectively as “receiver478”). Transmitter476is configured to transmit reference signals, control information and data to one or more other devices, and receiver478is configured to receive references signals, synchronization signals, control information and data from one or more other devices. For example, transmitter476may transmit signaling, control information and data to, and receiver478may receive signaling, control information and data from, base station105or UE115. In some implementations, transmitter476and receiver478may be integrated in one or more transceivers. Additionally or alternatively, transmitter476or receiver478may include or correspond to one or more components of UE115described with reference toFIG.2. In some implementations, sensing device475is associated with a joint communication and radar (JCR) system. The JCR system may be categorized as a cooperative JCR system or a co-design of communication and radar systems. For example, sensing device475may be associated with the co-design of communication and radar systems. Although described as including both transmitter476and receiver478, in other implementations, sensing device475may include transmitter476but not receiver478, or may include receiver478but not transmitter476.

In some implementations, network entity470may include one or more antenna arrays. The one or more antenna arrays may be coupled to transmitter476, receiver478, or a communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices, such as with UE115or base station105. In some implementations, the antenna array may be configured to perform wireless communications using different beams, also referred to as antenna beams. The beams may include TX beams and RX beams. To illustrate, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple individual antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different respective beam that may have a different respective direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example using multiple RF chains of network entity470. Each individual set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different respective beam.

Network entity470may include one or more components as described herein with reference to UE115. In some implementations, network entity470is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

Base station105may include a variety of components (such as structural, hardware components) used for carrying out one or more functions described herein. For example, these components may include one or more processors452(hereinafter referred to collectively as “processor452”), one or more memory devices454(hereinafter referred to collectively as “memory454”), and one or more sensing devices455(hereinafter referred to collectively as “sensing device455”). In some implementations, base station105may include an interface (e.g., a communication interface) that includes transmitter456, receiver458, or a combination thereof. Processor452may be configured to execute instructions460stored in memory454to perform the operations described herein. In some implementations, processor452includes or corresponds to one or more of receive processor238, transmit processor220, and controller240, and memory454includes or corresponds to memory242.

Memory354includes or is configured to store instructions460and information464. In some implementations, information464may include or correspond to information406or484. Information464may include capability information465, sensing charging subscription information466, and sensing charge467. Capability information465may include or correspond to capability information408. Capability information465may include or indicate a capability of UE115, network entity470, base station105, or a combination thereof. Sensing charging subscription information466may include or correspond sensing charging subscription information409. Sensing charge subscription information466may include or correspond to a subscription, such as a subscription for a sensing service, that is associated with UE115or network entity470. Sensing charge467may include or correspond to a charge, such as a fee or a cost, of a sensing service associated with or used by UE115, network entity470, or a combination thereof.

Sensing device455includes one or more transmitters456(hereinafter referred to collectively as “transmitter456”), and one or more receivers458(hereinafter referred to collectively as “receiver458”). Transmitter456is configured to transmit reference signals, synchronization signals, control information and data to one or more other devices, and receiver458is configured to receive reference signals, control information and data from one or more other devices. For example, transmitter456may transmit signaling, control information and data to, and receiver458may receive signaling, control information and data from, UE115or network entity470. In some implementations, transmitter456and receiver458may be integrated in one or more transceivers. Additionally, or alternatively, transmitter456or receiver458may include or correspond to one or more components of base station105described with reference toFIG.2.

In some implementations, base station105may include one or more antenna arrays. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices, such as with the UE115. In some implementations, the antenna array may be configured to perform wireless communications using different beams, also referred to as antenna beams. The beams may include TX beams and RX beams. To illustrate, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple individual antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different respective beam that may have a different respective direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example using multiple RF chains of the base station105. Each individual set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different respective beam.

In some implementations, wireless communications system400implements a 5G NR network. For example, wireless communications system400may include multiple 5G-capable UEs115and multiple 5G-capable base stations105, such as UEs and base stations configured to operate in accordance with a 5G NR network protocol such as that defined by the 3GPP. In some other implementations, wireless communications system400implements a 6G network.

In some implementations, UE115or sensing device415may be associated with a JCR system. The JCR system provide advantages and benefits of at least helping radar or radar helping communication, spectrum reuse, hardware reuse, or a combination thereof. The JCR system may be categorized as a cooperative JCR system or a co-design of communication and radar systems. In the cooperative JCR system, information may be shared between the communication and radar systems to improve performance, without much altering core operation of radar and communication systems. The cooperative JCR system provides advantages and benefits of at least spectrum reuse and ease of implementation. In the co-design of communication and radar systems, a common transmitter or receiver is used for both communication and radar functionalities. The co-design of communication and radar systems may require modification in the transmit waveform generation or the receiver processing of both or either of the systems. The co-design of communication and radar systems provide advantages and benefits of at least reduced hardware and spectrum reuse.

For NR communications, a charging system may be used that enables online charging. Online charging is a mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with the control of network resource usage is required. Online charging may include a process where charging information for network resource usage is collected concurrently with that resource usage in the same fashion as in offline charging. In some implementations, authorization for the network resource usage must be obtained by or from the network prior to the actual resource usage to occur by UE115. This authorization may be granted by an online charging system (OCS) or a converged charging system (CCS) upon request from the network. In some implementations, the OCS or the CCS may be located at the network, such as base station105or core network130.

The network may receive a network resource usage request and, based on the network resource usage request, assemble the relevant charging information and generate a charging event towards the OCS or CCS. For example, the charging event may be generated in real-time. The OCS or the CCS may then return an appropriate resource usage authorization. The resource usage authorization may be limited in its scope (e.g., volume of data or duration), therefore the authorization may have to be renewed from time to time as long as the user's network resource usage persists.

In some implementations, the charging system may include or use an event-based charging function (EBCF). The EBCF may function within the OCS and may be used to charge events based on an occurrence of an event rather than a duration or a volume used in the event. Examples, of an event include are SMS, MMS, or purchase of content (application, game, music, video on demand, etc.). The EBCF may be configured to perform event-based charging and credit-control (e.g. content charging) on a bearer level, on a subsystem level, or on a service level. For example, on the bearer level, the EBCF may perform the event-base charging based on bearer usage requests received from the network such that the EBCF controls the bearer usage in the network, e.g. SMS. As another example, on a subsystem level, the EBCF may perform the event-base charging based on session resource usage requests received from the network (e.g. the IMS MRFC) such that the EBCF controls the resource availability in network, e.g. it has the ability to grant or deny the resource usage. As another example, on service level, the EBCF may perform the event-base charging based on application server requests received from the network (e.g. an IMS application server or MMS relay server) such that the EBCF controls the application service availability in the network, e.g. it has the ability to grant or deny the service usage in the network. The EBCF may communicate with a rating function in order to determine the value of the requested service usage and may communicate with an account balance management function (ABMF) to query and update an account and counters status of a subscriber.

In some implementations, the charging system may include or use a session-based charging function (SBCF). The SBCF may be configured to functions within the OCS. The SBCF may be responsible for online charging of network/user sessions, such as voice calls, IP CAN bearers, IP CAN session or IMS sessions. It is noted that utility services, such as electricity or water, may be charged based on overall usage, for a certain time duration. The SBCF may be configured to perform session based charging and Credit-Control on the bearer level, on the subsystem level, or on the service level. For example, on the bearer level, the SBCF may perform the session-base charging based on bearer usage requests received from the network such that the SBCF controls the bearer usage in the network, e.g. in terms of time or volume granted. As another example, on the subsystem level, the SBCF may perform the session-base charging based on session resource usage requests received from the network (e.g. the IMS CSCF) such that the SBCF controls sessions in the network, e.g. it has the ability to grant or deny a session setup request and to terminate an existing session. As another example, on the service level, the SBCF may perform the session-base charging based on service usage requests received from the network such that the SBCF controls service availability in the network, e.g. it has the ability to grant or deny a usage of a service. The SBCF may communicate with a rating function in order to determine the value of the requested bearer resources or the requested session. Additionally, or alternatively, the SBCF may communicate with an ABMF to query and update an account and counters status of a subscriber.

In some implementations, sensing charging subscription information409or466is associated with sensing charging subscription for UE115or network entity470configured to perform bi-static sensing. For example, sensing charging subscription information409may include or define the sensing charging subscription, such as a sensing charging subscription model, for UE115. Additionally, or alternatively, sensing charging subscription information466may include or define the sensing charging subscription, such as a sensing charging subscription model, for network entity470.

In some implementations, network entity470is associated with sensing charging subscription information, such as a bi-static sensing charging subscription model for network entity470. Network entity470may be a mobile device or a fixed device. Additionally, or alternatively, network entity470is configured to receive a request from another device, such as UE115, to assist in a bi-static sensing operation. In such situations—e.g., when network entity470receives the request to assist, the other device may be referred to as an initiating device and the network entity470may be referred to as a helping device.

In some implementations, a controller, such as a centralized controller, may be configured to assist UE115to identify or select a helping device. The controller may include or correspond to base station105, core network130, LMF131, a network, or a combination thereof. The controller, such as base station105, may be configured to request (e.g., ping) one or more devices, such as one or more base station, one or more UEs, one or more network entities, or a combination thereof, for information associated with assisting a bi-static sensing operation. In some implementations, the controller may request capability information, such as capability information408or,465from the one or more devices. Additionally, or alternative, the controller may request a location of the one or more devices, a mobility of the one or more devices, a type of sensing operation or modes supported by the one or more devices, or a combination thereof. In some implementations, the controller may select at least one device (an assisting device) of the one or more devices as a candidate to assist an initiating device (e.g., UE115) initiating with the bi-static sensing operation. The controller may select the at least one device as the candidate based on the location of the at least one device, a mobility or direction of travel of the initiating device, a type of sensing request (e.g., a scanning mode request or a tracking mode request), or a combination thereof. In some implementations, the controller may select the at least one device or transmit network entity information that indicates the selected at least one device to UE115based on sensing charging subscription information409or466, for a fee charged to UE115, or a combination thereof. Additionally, or alternatively, based on selection of the at least one device, the controller may signal to the at least one device (e.g. network entity470) to indicate that the at least one device is selected to participate in a bi-static sensing operation with the initiating device (e.g., UE115). The controller may also indicate a fee, based on sensing charging subscription information for UE115or network entity470, to be charged for participating in the bi-static sensing operation.

In some implementations, UE115and network entity470may perform a pre-sensing operation prior to preforming a bi-static sensing operation. To illustrate, the controller may be configured to indicate that a pre-sensing operation is available between UE115and network entity470to enable UE115to determine whether or not network entity4708is suitable for bi-static sensing. For example, the controller may indicate that the pre-sensing operation is available for a fee.

In some implementations, UE115may perform the bi-static sensing operation with the at least one device (e.g., network entity470) selected by the controller. For example, the controller may transmit, to UE115, network entity information that indicates network entity470to participate in the bi-static sensing operation. In some implementations, UE115and the controller may communicate to determine (or negotiate) a sensing resource, a sensing transmission parameter, a sensing charge fee, or a combination thereof, associated with performing the bi-static sensing operation, using network entity, or a combination thereof.

In some implementations, the controller may support selection of the at least one device by the initiating device (e.g., UE115) by enabling a pre-sensing mode. The pre-sensing mode may be enabled at the initiating device, the at least one device, or a combination thereof, based on a fee, such as a fee determined based on sensing charging subscription information409or466. Additionally, or alternatively, the pre-sensing mode may enable the initiating device to understand one or more channel conditions between the at least one device and the at least one device. To illustrate, the pre-sensing mode can be for a coarse sensing estimation performance with low resource usage overhead. As another example, the pre-sensing mode can be for a fine sensing estimation performance within a short duration. In some implementations, the at least one device may generate a pre-sensing measurement report based on a pre-sensing operation. A fee may be charged to the initiating device, the at least one device, or both, based on a Tx parameter or a resource needed for the pre-sensing mode. For example, a first fee may be charged to the initiating device (as a Tx node) and a second fee may be charged to the at least one device (as an Rx node). Additionally, or alternatively, the pre-sensing measurement report may be generated or communicated to the initiating device, the controller, or to another device, for a fee. For example, the at least one device may generate and send the pre-sensing measurement report to the controller. The pre-sensing measurement report may include or indicate a channel quality, an amount of interference, a signal strength, or a combination thereof, as illustrative, non-limiting examples. The controller may send the pre-sensing measurement report tot one or more other device or may use the pre-sensing measurement report to select a device for the initiating device to use in the bi-static sensing operation. As another example, the at least one device may generate and send the pre-sensing measurement report to the initiating device. The initiating wireless may decide, based on the measurement report, if modification of resources, transmission parameters, or a different device is needed for the bi-static sensing operation. In some implementations, no pre-sensing measurement report will be offered or enabled by the controller.

In some implementations, the controller is configured to determine a fee (for the initiating device or the assisting device) based on a resource available at the assisting device, a resource needed for the bi-static sensing operation by the initiating device, or a combination thereof. For example, the fee may be a fixed sensing fee to perform or support a bi-static sensing operation. As another example, if a fraction (e.g., a portion) of a resource needed by the initiating device (with respect to a total available resource) is close to 100%, the controller may deny the sensing service or charge an additional fee (in addition to a standard fee for the sensing service). Additionally, or alternatively, the controller may be configured to determine a fee (for the initiating device or the assisting device) based on a location or mobility of the initiating device, the assisting device, or a combination thereof. For example, if the initiating device is greater than or equal to a threshold distance from the assisting device, or the devices are traveling in different direction, the controller may deny the sensing service. Additionally, or alternatively, the controller may be configured to determine a fee (for the initiating device or the assisting device) based on a mode (e.g., a Tx mode or an Rx mode) of the assisting device. For example, the assigning device operating in the Tx mode can incur a higher fee than the assisting device operating in the Rx mode, such as due to active transmission required by the assisting device. In some implementations, the controller may also be configured to determine a fee (for the initiating device or the assisting device) based on an additional service request, such as a pre-sensing mode, a type of measurement report (e.g., a pre-sensing measurement report with the assisting device as a Rx node, a pre-sensing measurement report with the assisting device as a Tx node, a frequency of a pre-sensing measurement report), or a combination thereof.

In some implementations, the controller enables the selection of an assisting device, such as for a given sensing subscription fee. The selection may be based on a subscription charge fee for different Tx and Rx modes of the assisting device, a subscription package of the initiating device, a sensing QoS request from the initiating device, a predicted sensing QoS offered by assisting device, or a combination thereof.

In some implementations, the initiating device is configured to perform the bi-static sensing with the assisting device selected and agreed upon with the controller. Additionally, the initiating device may communicate with the controller to determine or negotiate a sensing resource, a sensing transmission parameter, sensing charge fee, or a combination thereof. Additionally, or alternatively, the initiating device and the assisting device may communicate to determine whether or not a sensing QoS need of the initiating device and the sensing charge fee of the assisting device are agreed, or if the sensing service is denied.

In some implementations, a handover of the assisting device is performed for assisting the initiating device with improved sensing performance. For example, the controller may enable a handover of the assisting device for an additional charge to the initiating device or the assisting device. As another example, the controller or a service base station (e.g.,105) may send a sensing measurement report, such as a pre-sensing measurement report, or a Tx/Rx configuration to another base station for an additional fee. As another example, the controller or a serving base station (e.g.,150) may send a sensing measurement report, such as a pre-sensing measurement report, or a Tx/Rx configuration to the future assisting device within a coverage area of the base station for a fee. In some implementations, a handover of the assisting device may be based on a predicted location or mobility of one or more surrounding base stations, one or more surrounding UEs or network entities, or a combination thereof.

An illustrative operation of wireless communications system400is described at least with reference toFIG.5.FIG.5is a ladder diagram illustrating an example of operations that supports a sensing charging subscription according to one or more aspects. As shown inFIG.5, a system of the ladder diagram includes UE115, a network entity470, and a network430. Network506may include or correspond to base station105or core network130. Although shown and described as being a single entity, in some implementations, network506may be a distributed server system. UE115, network entity470, and network506may include one or more components and be configured to perform one or more operations, as described with reference toFIGS.1-4.

During operation, at510, network506may transmit a capability request. The capability request may include a request for capability information associated with an availability of a device, such as UE115or network entity470, to participate in one or bistatic sensing operations. The capability request may be received by network entity470. In some implementations, the capability request may additionally or alternatively be received by UE115.

At512, in response to the request, network entity transmits a capability response to network506. The capability response may include or indicate information406, capability information408, information464, capability information465, or information484. The capability response may include capability information of network entity470, UE115, or a combination thereof. In some implementations, UE115may transmit a capability response to network506. Network506may identify one or more network entities available to participate in bi-static sensing operations based on one or more capability responses received by network506from one or more network entities.

At514, UE115, such as an initiating device, transmits a bi-static sensing request. For example, UE115may transmit the bi-static sensing request to network506. The bi-static sensing request may include or indicate a request to perform the bi-static sensing operation, such as a request for UE115to perform or initiate the bi-static sensing operation.

At516, network506may transmit network entity information. To illustrate, network506may transmit the network entity information response to the bi-static sensing request. UE115, network entity470, or both may receive the network entity information. The network entity information may indicate at least one network entity, such as network entity470, selected from one or more network entities available to participate in the bi-static sensing operation. In some implementations, network506selects (for inclusion in the network entity information) network entity470from one or more entities available to participate in the bi-static sensing operation. For example, network entity470may be selected from the one or more network entities based on a location of the network entity, a location of the UE, capability information received from the network entity, a fee for use of the network entity, sensing charging subscription information associated with the UE, a quality of service requested by the UE, an available quality of service associated with the network entity, or a combination thereof.

At518, UE115transmits a network entity request to network entity470. The network entity request may include a request for network entity470to participate in a bi-static sensing operation. In some implementations, UE115may identify network entity470, send the network entity request, or both, based on the network entity information received from network506. At520, network entity470may transmit a network entity reply to UE115. The network entity reply may be response to the network entity request and may indicate whether or not network entity470is able to or will participate in the bi-static sensing operation. The network entity information may indicate a sensing resource (e.g., a channel), a sensing transmission parameter (e.g., a transmit power, a beam bandwidth, a beam direction, a quality of service), a sensing charge fee (e.g., for a pre-sensing operation, the bi-static sensing operation, use of network entity470), or a combination thereof.

At522, UE transmits a pre-sensing waveform. The pre-sensing waveform may be transmitted as part of a pre-sensing operation prior to the bi-static sensing operation. UE115may determine to perform the pre-sensing operation based on the network entity information, the network entity reply, or a combination thereof. In some implementations, the pre-sensing operation is associated with a course sensing estimation or a fine sensing estimation, performed via a UL channel, or a combination thereof. At524, network entity470transmits (and UE115receives) a pre-sensing measurement report. In some implementations, network506may additionally, or alternatively, receive the pre-sensing measurement report from network entity470. UE115may determine whether or not to perform the bi-static sensing operation with network entity470based on the pre-sensing measurement report, a quality of service of UE115, a sensing charge fee associated with network entity470, or a combination thereof. In some implementations, UE115may perform a pre-sensing operation with one or more network entities and select one network entity (of the one or more network entities) for the bi-static sensing operation based on one or more pre-sensing operation results.

At526, UE115transmits a sensing waveform. For example, UE115may initiate or perform the bi-static sensing operation with network entity470, and the bi-static sensing operation includes UE115transmitting the sensing waveform that is receive by network entity470. In some implementations, the sensing waveform received by network entity470may include a reflection of the sensing waveform off of an object, such as object490.

At528, network entity470may transmit receive sensing information. For example, network entity470may generate the receive sensing information based on receipt of the sensing waveform—e.g., the receive sensing information is associated with the bi-static sensing operation. The receive sensing information may include, indicate, or correspond to information406, measurement information410, or information484. Although the receive sensing information is shown as being transmitted to UE115, in other implementation, the receive sensing information may additionally or alternatively be transmitted to network506.

At530, UE115transmits transmit sensing information. For example, UE115may generate the transmit sensing information based on transmission of the sensing waveform —e.g., the transmit sensing information may be associated with the bi-static sensing operation. Although the transmit sensing information is shown as being transmitted to network506, in other implementation, the receive sensing information may additionally or alternatively be transmitted to network entity470. In some implementations, the transmit sensing information may indicate completion of the bi-static sensing operation, the receive sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof.

In some implementations, after receiving the receive sensing information, the transmit sensing information, or a combination thereof, network506may determine a fee associated with the bi-static sensing request, the pre-sensing operation, the bi-static sensing operation, or a combination thereof. The fee may include or correspond to sensing charge467. Additionally, or alternatively, the fee may be determined based on sensing charging subscription information associated with UE115, network entity470, or a combination thereof. For example, the sensing charging subscription information may include or correspond to information406, sensing charging subscription information409, information484, information464, or sensing charging subscription information466. Additionally, or alternatively, network506may determine the fee for the bi-static sensing operation based on the transmit sensing information, the receive sensing information, a resource available at network entity470for the bi-static sensing operation, a resource needed by UE115for the bi-static sensing operation, a location of UE115, a mobility of UE115, a location of network entity470, a mobility of network entity470, a distance between UE115and network entity470, an operational mode at network entity470, a pre-sensing operation, a pre-sensing measurement report, or a combination thereof. In some implementations, network506may determine the fee as a fixed sensing fee for the bi-static sensing operation performed by UE115. The sensing charging subscription information indicates a functionality, a rule, a profile, or a combination thereof.

In some implementations, network506may determine a first fee for network entity470as a receive (Rx) device, a second fee for UE115as a transmit (Tx) device, or a combination thereof. For example, network506may determine the first fee or the second fee is determined based on a pre-sensing operation, a Tx parameter, a resource, a quality of service, or a combination thereof.

At530, network entity470transmits a handover request532to network506. The handover request may be associated with assisting UE115with the bi-static sensing operation. Based on the handover request, network506may send a pre-sensing message report or configuration information (e.g., network entity information) to a base station (e.g.,105), send a pre-sensing message report or configuration information (e.g., network entity information) to another network entity, or perform the handover operation based on a predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof. The transmit sensing information may indicate completion of the bi-static sensing operation, the receive sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof.

It is noted that although operations ofFIG.5are described in a particular order, such order is not intended to be limited. Accordingly, one or more operations described with reference toFIG.5may be performed in an order other than what is shown and described with reference toFIG.5.

As described with reference toFIGS.4and5, the present disclosure provides techniques for supporting a sensing charging subscription. The techniques described provide processes, information, and signaling for UE115to perform sensing operations, such as a bi-static sensing operation, according to a sensing subscription. Wireless network100may advantageously manage sensing-based subscription charges for the sensing operations or services, such as 5G or NR sensing services, associated with UE115. Additionally, the techniques described herein enable sensing operations performed by UE115may be managed or controlled according to the sensing subscriptions. By managing and controlling the sensing operations performed by UE115, the techniques described herein enable reduced overhead, efficient spectrum usage, improved spectrum reuse, reduced device hardware, improved hardware reuse, or a combination thereof.

FIG.6is a flow diagram illustrating an example process600that supports a sensing charging subscription according to one or more aspects. Operations of process600may be performed by a UE, such as UE115described above with reference toFIGS.1-5or a UE described with reference toFIG.7. For example, example operations (also referred to as “blocks”) of process600may enable UE115to support a sensing charging subscription.

In block602, the UE transmits a request to a network entity to participate in a bi-static sensing operation. For example, the network entity may include or correspond to network entity470. The request may include or correspond to the bi-static sensing request transmitted by UE115as described at514ofFIG.5.

In block604, the UE performs the bi-static sensing operation with the network entity. The bi-static sensing operation may include or correspond to the sensing waveform transmitted by UE115as described at526ofFIG.5.

In block606, the UE transmits transmit sensing information associated with the bi-static sensing operation. For example, the transmit sensing information may include or correspond to information406, measurement information410, information464, or information484. As another example, the transmit sensing information may include or correspond to the transmit sensing information transmitted by UE115at530ofFIG.5. The transmit sensing information may be associated with sensing charging subscription information. The sensing charging subscription information may include or correspond to information406, sensing charging subscription information409, information464, sensing charging subscription information466, or information484. The sensing charging subscription information may include or indicate a functionality, a rule, a profile, or a combination thereof.

In some implementations, the UE receives receive sensing information associated with the bi-static sensing operation from the network entity. The receive sensing information may include or correspond to information406, measurement information410, information484, or information464. Additionally, or alternatively, the receiving sensing information may include or correspond to the receive sensing information transmitted by network entity470at528ofFIG.5. The transmit sensing information may indicate completion of the bi-static sensing operation, the receive sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof.

In some implementations, the UE transmits, to a network, a request to perform the bi-static sensing operation. The network may include or correspond to base station105, core network130, or network506. The request to perform the bi-static sensing operation may include or correspond to bi-static sensing request transmitted by UE115at514ofFIG.5. Additionally, or alternatively, the UE may receive network entity information from the network. For example, the network entity information may include or correspond to network entity information received by UE115at516ofFIG.5. The network entity information may indicate the network entity selected from one or more network entities available to participate in the bi-static sensing operation. Additionally, or alternatively, the network entity information indicates a sensing resource, a sensing transmission parameter, a sensing charge fee, or a combination thereof. the network entity includes a base station, a roadside unit, or another UE, the network entity is a mobile device or a stationary device, the network includes a core network, or a combination thereof.

In some implementations, the UE performs a pre-sensing operation with the network entity prior to performing the bi-static sensing operation. For example, the pre-sensing operation may include or correspond to the pre-sensing waveform transmitted by UE115at522ofFIG.5. The pre-sensing operation is associated with a course sensing estimation or a fine sensing estimation, performed via an uplink (UL) channel, or a combination thereof. Additionally, or alternatively, the UE may receive, from the network entity, a pre-sensing measurement report from the network entity. For example, the pre-sensing measurement report may include or correspond to the pre-sensing measurement report transmitted by network entity470524ofFIG.5. In some implementations, the UE may determine whether or not to perform the bi-static sensing operation based on the pre-sensing measurement report, a quality of service of the UE, a sensing charge fee associated with the network entity, or a combination thereof.

In some implementations, the UE receives, from a network, a request for capability information associated with an availability of the UE to participate in one or bistatic sensing operations. The request may include or correspond to the capability request transmitted by network506at510ofFIG.5. In response to the request, the UE may transmit UE capability information to the network. The UE capability information may include or correspond to information406, capability information408, information484, information464, or capability information465. As another example, the UE capability information may include or correspond to the capability response received by network506at512ofFIG.5.

FIG.7is a block diagram of an example UE700that supports a sensing charging subscription according to one or more aspects. UE700may be configured to perform operations, including the blocks of a process described with reference toFIG.6. In some implementations, UE700includes the structure, hardware, and components shown and described with reference to UE115ofFIGS.1-5. For example, UE700includes controller280, which operates to execute logic or computer instructions stored in memory282, as well as controlling the components of UE700that provide the features and functionality of UE700. UE700, under control of controller280, transmits and receives signals via wireless radios701a-rand antennas252a-r. Wireless radios701a-rinclude various components and hardware, as illustrated inFIG.2for UE115, including modulator and demodulators254a-r, MIMO detector256, receive processor258, transmit processor264, and TX MIMO processor266.

As shown, memory282may include bi-static sensing logic702and communication logic703. Bi-static sensing logic702may be configured to enable one or more bi-static sensing operations. Communication logic703may be configured to enable communication between UE700and one or more other devices. UE700may receive signals from or transmit signals to one or more network entities, such as base station105ofFIGS.1-4, network entity470ofFIGS.4-5, or a network entity as illustrated inFIG.10.

FIG.8is a flow diagram illustrating an example process800that supports a sensing charging subscription according to one or more aspects. Operations of process800may be performed by a network entity, such as UE115described above with reference toFIGS.1-5, network entity470described above with reference toFIGS.1-5or base station105described above with reference toFIGS.1-4, UE700described above with reference toFIG.7, or a network entity as described above with reference toFIG.10. For example, example operations of process800may enable the network entity to support a sensing charging subscription.

At block802, the network entity receives, from a UE, a request to assist the UE in a bi-static sensing operation. For example, the request may include or correspond to the bi-static sensing request received by network entity470as described at514ofFIG.5.

In some implementations, the network entity transmits, responsive to the request, a response that indicates an availability to participate in the bi-static sensing operation. For example, the response may include or correspond to the network entity reply transmitted by network entity470at520ofFIG.5.

At block804, the network entity performs the bi-static sensing operation with the UE. The bi-static sensing operation may include or correspond to the sensing waveform transmitted by UE115and received by network entity470as described at526ofFIG.5.

At block806, the network entity transmits receive sensing information associated with the bi-static sensing operation. For example, the receive sensing information may include or correspond to information406, measurement information410, information464, or information484. As another example, the receive sensing information may include or correspond to the receive sensing information transmitted by network entity470at528ofFIG.5. The receive sensing information may be associated with sensing charging subscription information. The sensing charging subscription information may include or correspond to information406, sensing charging subscription information409, information464, sensing charging subscription information466, or information484.

In some implementations, the network entity receives, from a network, a request for capability information associated with an availability of the network entity to participate in one or bistatic sensing operations. The network may include or correspond to base station105, core network130, or network506. The request may include or correspond to the capability request transmitted by network506at510ofFIG.5. Additionally, or alternatively, the network entity may transmit capability information to the network. The capability information may include or correspond to information406, capability information408, information484, information464, or capability information465. As another example, the capability information may include or correspond to the capability response received by network506at512ofFIG.5.

In some implementations, the network entity performs a pre-sensing operation with the UE. For example, the pre-sensing operation may include or correspond to the pre-sensing waveform transmitted by UE115at522ofFIG.5. The pre-sensing operation may be associated with a course sensing estimation, a fine sensing estimation, a pre-sensing operation is performed using an UL channel of the UE. Additionally, or alternatively, the network entity may transmit a pre-sensing measurement report based on the pre-sensing operation to a network or the UE. The pre-sensing measurement report may include or correspond to the pre-sensing measurement report transmitted by network entity470at524ofFIG.5, information406, measurement information410, information484, or information464.

In some implementations, the network entity initiates, with a network, a handover operation associated with assisting the UE with the bi-static sensing operation. To illustrate, to initiate the handover operation, network entity470transmits the handover request at532ofFIG.5.

FIG.9is a flow diagram illustrating an example process900that supports a sensing charging subscription according to one or more aspects. Operations of process900may be performed by a network, such as network entity470described above with reference toFIGS.1-5, base station105or core network130described above with reference toFIGS.1-4, network506described above with reference toFIG.5, or a network entity as described above with reference toFIG.10. For example, example operations of process900may enable the network entity to support a sensing charging subscription

At block902, the network transmits, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or more bistatic sensing operations. For example, the network entity may include or correspond to UE115or network entity470. The request for the capability information may include or correspond to the capability request transmitted by network506at510ofFIG.5. The capability information may include or correspond to information406, capability information408, information464, capability information465, or information484. Additionally, the capability information may include or correspond to capability response transmitted by network entity470at512ofFIG.5.

At block904, the network receives, from a UE, a request to assist the UE in a bi-static sensing operation. For example, the UE may include or correspond to UE115. The request to assist may include or correspond to the bi-static sensing request received by network506at514ofFIG.5.

At block906, the network transmits network entity information to the UE. For example, the network entity information may include or correspond to the network entity information transmitted by network506at516ofFIG.5. The network entity information may indicate the network entity selected from one or more network entities available to participate in the bi-static sensing operation. In some implementations, the network entity information indicates a sensing resource, a sensing transmission parameter, a sensing charge fee, or a combination thereof. the network entity information is transmitted to the UE, the network entity, or a combination thereof.

In some implementations, the network selects the network entity of the one or more network entities available to participate in the bi-static sensing operation. The network entity may be selected from the one or more network entities based on a location of the network entity, a location of the UE, capability information received from the network entity, a fee for use of the network entity, sensing charging subscription information associated with the UE, a quality of service requested by the UE, an available quality of service associated with the network entity, or a combination thereof.

In some implementations, the network receives transmit sensing information based on the bi-static sensing operation from the UE. For example, the transmit sensing information may include or correspond to information406, measurement information410, information464, or information484. As another example, the transmit sensing information may include or correspond to the transmit sensing information transmitted by UE115at530ofFIG.5. Additionally, or alternatively, the network may receive receive sensing information based on the bi-static sensing operation from the network entity. For example, the receive sensing information may include or correspond to information406, measurement information410, information464, or information484. As another example, the receive sensing information may include or correspond to the receive sensing information transmitted by network entity470at528ofFIG.5. In some implementations, the network determines, for the UE, a fee for the bi-static sensing operation. For example, the fee may include or correspond to sensing charge467. The fee may be determined based on sensing charging subscription information (e.g.,409or466) associated with the UE and the transmit sensing information, the receive sending information, or a combination thereof. Additionally, or alternatively, the fee for the bi-static sensing operation may be determined based on the transmit sensing information, the receive sensing information, a resource available at the network entity for the bi-static sensing operation, a resource needed by the UE for the bi-static sensing operation, a location of the UE, a mobility of the UE, a location of the network entity, a mobility of the network entity, a distance between the UE and the network entity, an operational mode at the network entity, a pre-sensing operation, a pre-sensing measurement report, or a combination thereof. In some implementations, the network determines, for the UE, a fixed sensing fee for the bi-static sensing operation performed by the UE.

In some implementations, the network receives a pre-sensing measurement report from the network entity. The pre-sensing measurement report may include or correspond to the pre-sensing measurement report transmitted by network entity470at524ofFIG.5, information406, measurement information410, information484, or information464. The pre-sensing measurement report may be based on a pre-sensing operation between the UE and the network entity. For example, the pre-sensing operation may include or correspond to the pre-sensing waveform transmitted by UE115at522ofFIG.5. Additionally, or alternatively, it is noted that the network entity information may indicate that the network entity is available for the pre-sensing operation prior to the bi-static sensing operation. In some implementations, the network determines a first fee for the network entity as an Rx device, a second fee for the UE as a Tx device, or a combination thereof. The first fee or the second fee may be determined based on a pre-sensing operation, a Tx parameter, a resource, a quality of service, or a combination thereof.

In some implementations, the network receives, from the network entity, a request for a handover operation. To illustrate, network entity470transmits the handover request to network506at532ofFIG.5. Based on the request for the handover operation, the network may send a pre-sensing message report or configuration information to a base station, send a pre-sensing message report or configuration information to another network entity, or perform the handover operation based on a predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof.

FIG.10is a block diagram of an example network entity1000that supports a sensing charging subscription according to one or more aspects. Network entity1000may be configured to perform operations, including the blocks of processes described with reference toFIG.8or9. In some implementations, network entity1000includes the structure, hardware, and components shown and described with reference to base station105ofFIGS.1-4, network entity470ofFIGS.1-5, core network130ofFIGS.1-4, network506ofFIG.5. For example, network entity1000may include controller240, which operates to execute logic or computer instructions stored in memory242, as well as controlling the components of network entity1000that provide the features and functionality of network entity1000. Network entity1000, under control of controller240, transmits and receives signals via wireless radios1001a-tand antennas234a-t. Wireless radios1001a-tinclude various components and hardware, as illustrated inFIG.2for base station105, including modulator and demodulators232a-t, transmit processor220, TX MIMO processor230, MIMO detector236, and receive processor238.

As shown, the memory242may include capability information1002, bi-static sensing logic1003, and communication logic1004. Capability information1002may include or correspond to information406, capability information408, information484, information464, or capability information465. Bi-static sensing logic1003may be configured to enable one or more bi-static sensing operations. Communication logic1004may be configured to enable communication between network entity1000and one or more other devices. Network entity1000may receive signals from or transmit signals to one or more UEs, such as UE115ofFIGS.1-5, network entity470ofFIGS.4-5, or UE700ofFIG.6.

It is noted that one or more blocks (or operations) described with reference toFIG.6,8, or9may be combined with one or more blocks (or operations) described with reference to another of the figures. For example, one or more blocks (or operations) ofFIG.6may be combined with one or more blocks (or operations) ofFIG.8. As another example, one or more blocks associated withFIG.6may be combined with one or more blocks associated withFIG.9. As another example, one or more blocks associated withFIG.8may be combined with one or more blocks associated withFIG.9. As another example, one or more blocks associated withFIG.6,8, or9may be combined with one or more blocks (or operations) associated withFIGS.1-5. Additionally, or alternatively, one or more operations described above with reference toFIGS.1-5may be combined with one or more operations described with reference toFIG.7or10.

In one or more aspects, techniques for supporting receive sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for supporting receive sensing information may include transmitting a request to a network entity to participate in a bi-static sensing operation. The techniques may further include performing the bi-static sensing operation with the network entity. The techniques may also include transmitting transmit sensing information associated with the bi-static sensing operation. The transmit sensing information may be associated with sensing charging subscription information. In some examples, the techniques in the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device, which may include a UE or a component of a UE. In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem or other components) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon that, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally, or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) that includes a transmitter, a receiver, or a combination thereof. Additionally, or alternatively, the wireless communication device may include one or more means configured to perform operations described herein.

In a second aspect, in combination with the first aspect, the techniques further include receiving receive sensing information associated with the bi-static sensing operation from the network entity.

In a third aspect, in combination with the second aspect, the transmit sensing information indicates completion of the bi-static sensing operation, the receive sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmission power, a quality of service, or a combination thereof.

In a fourth aspect, in combination with one or more of the first aspect through the third aspect, the sensing charging subscription information indicates a functionality, a rule, a profile, or a combination thereof.

In a fifth aspect, in combination with one or more of the first aspect through the fourth aspect, the techniques further include transmitting, to a network, a request to perform the bi-static sensing operation.

In a sixth aspect, in combination with one or more of the first aspect through the fifth aspect. the techniques further include receiving network entity information from the network. The network entity information of the sixth aspect may indicate the network entity selected from one or more network entities available to participate in the bi-static sensing operation.

In a seventh aspect, in combination with one or more of the first aspect through the sixth aspect, the network entity information indicates a sensing resource, a sensing transmission parameter, a sensing charge fee, or a combination thereof.

In an eighth aspect, in combination with one or more of the first aspect through the seventh aspect, the network entity includes a base station, a roadside unit, or another UE.

In a ninth aspect, in combination with one or more of the first aspect through the eighth aspect, the network entity is a mobile device or a stationary device.

In a tenth aspect, in combination with one or more of the first aspect through the ninth aspect, the network includes a core network.

In an eleventh aspect, in combination with one or more of the first aspect through the tenth aspect, the techniques further include performing a pre-sensing operation with the network entity prior to performing the bi-static sensing operation.

In a twelfth aspect, in combination with the eleventh aspect, the pre-sensing operation is associated with a course sensing estimation or a fine sensing estimation, performed via a UL channel, or a combination thereof.

In a thirteenth aspect, in combination with the eleventh aspect or the twelfth aspect, the techniques further include receiving, from the network entity, a pre-sensing measurement report from the network entity.

In a fourteenth aspect, in combination with the thirteenth aspect, the techniques further include determining whether to perform the bi-static sensing operation based on the pre-sensing measurement report, a quality of service of the UE, a sensing charge fee associated with the network entity, or a combination thereof.

In a fifteenth aspect, in combination with one or more of the first aspect through the fourteenth aspect, the techniques further include receiving, from a network, a request for capability information associated with an availability of the UE to participate in one or bistatic sensing operations.

In a sixteenth aspect, in combination with the sixteenth aspect, the techniques further include, in response to the request, transmitting UE capability information to the network.

In one or more aspects, techniques for supporting receive sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes or devices described elsewhere herein. In a seventeenth aspect, techniques for supporting receive sensing information may include receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The techniques may further include performing the bi-static sensing operation with the UE. The techniques may also include transmitting receive sensing information associated with the bi-static sensing operation. In some examples, the techniques in the seventeenth aspect may be implemented in a method or process. In some other examples, the techniques of the seventeenth aspect may be implemented in a wireless communication device, such as network entity, which may include a base station or a component of a base station, a UE or a component of a UE, a roadside unit or a component of a roadside unit. In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem or other components) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon that, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally, or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) that includes a transmitter, a receiver, or a combination thereof. Additionally, or alternatively, the wireless communication device may include one or more means configured to perform operations described herein.

In an eighteenth aspect, in combination with the seventeenth aspect, the techniques further include receiving, from a network, a request for capability information associated with an availability of the network entity to participate in one or bistatic sensing operations.

In a nineteenth aspect, in combination with one or more of the seventeenth aspect or the eighteenth aspect, the techniques further include transmitting capability information to the network.

In a twentieth aspect, in combination with one or more of the seventeenth aspect through the nineteenth aspect, the techniques further include transmitting, responsive to the request, a response that indicates an availability to participate in the bi-static sensing operation.

In a twenty-first aspect, in combination with one or more of the seventeenth aspect through the twentieth aspect, the techniques further include performing a pre-sensing operation with the UE.

In a twenty-second aspect, in combination with the twenty-first aspect, the pre-sensing operation is associated with a course sensing estimation, a fine sensing estimation, a pre-sensing operation is performed using an UL channel of the UE.

In a twenty-third aspect, in combination with the twenty-first aspect or the twenty-second aspect, the techniques further include transmitting a pre-sensing measurement report based on the pre-sensing operation to a network or the UE.

In a twenty-fourth aspect, in combination with one or more of the seventeenth aspect through the twenty-third aspect, the techniques further include initiating, with a network, a handover operation associated with assisting the UE with the bi-static sensing operation.

In one or more aspects, techniques for supporting receive sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes or devices described elsewhere herein. In a twenty-fifth aspect, techniques for supporting receive sensing information may include transmitting, to a network entity, a request for capability information associated with an availability of the network entity to participate in one or bistatic sensing operations. The techniques may further include receiving, from a UE, a request to assist the UE in a bi-static sensing operation. The techniques may also include transmitting network entity information to the UE. The network entity information indicates the network entity selected from one or more network entities available to participate in the bi-static sensing operation. In some examples, the techniques in the twenty-fifth aspect may be implemented in a method or process. In some other examples, the techniques of the twenty-fifth aspect may be implemented in a wireless communication device, such as network entity, which may include a base station or a component of a base station, a network or core network, or a component of a network or core network. In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem or other components) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon that, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally, or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) that includes a transmitter, a receiver, or a combination thereof. Additionally, or alternatively, the wireless communication device may include one or more means configured to perform operations described herein.

In a twenty-sixth aspect, in combination with the twenty-fifth aspect, the techniques further include selecting the network entity of the one or more network entities available to participate in the bi-static sensing operation.

In a twenty-seventh aspect, in combination with the twenty-sixth aspect, the network entity is selected from the one or more network entities based on a location of the network entity, a location of the UE, capability information received from the network entity, a fee for use of the network entity, sensing charging subscription information associated with the UE, a quality of service requested by the UE, an available quality of service associated with the network entity, or a combination thereof.

In a twenty-eighth aspect, in combination with one or more of the twenty-fifth aspect through the twenty-seventh aspect, the techniques further include receiving transmit sensing information based on the bi-static sensing operation from the UE.

In a twenty-ninth aspect, in combination with one or more of the twenty-fifth aspect through the twenty-eighth aspect, the techniques further include receive, from the network entity, sensing information based on the bi-static sensing operation.

In a thirtieth aspect, in combination with one or more of the twenty-fifth aspect through the twenty-ninth aspect, the techniques further include determining, for the UE, a fee for the bi-static sensing operation.

In a thirty-first aspect, in combination with the thirtieth aspect, the fee is determined based on sensing charging subscription information associated with the UE and the transmit sensing information, the receive sending information, or a combination thereof.

In a thirty-second aspect, in combination with one or more of the twenty-fifth aspect through the thirty-first aspect, the network entity information indicates a sensing resource, a sensing transmission parameter, a sensing charge fee, or a combination thereof.

In a thirty-third aspect, in combination with one or more of the twenty-fifth aspect through the thirty-second aspect, the network entity information is transmitted to the UE, the network entity, or a combination thereof.

In a thirty-fourth aspect, in combination with one or more of the twenty-fifth aspect through the thirty-third aspect, the techniques further include receiving a pre-sensing measurement report from the network entity.

In a thirty-fifth aspect, in combination with the thirty-fourth aspect, the pre-sensing measurement report based on a pre-sensing operation between the UE and the network entity.

In a thirty-sixth aspect, in combination with the thirty-fourth aspect or the thirty-fifth aspect, the network entity information indicates that the network entity is available for the pre-sensing operation prior to the bi-static sensing operation.

In a thirty-seventh aspect, in combination with one or more of the twenty-fifth aspect through the thirty-sixth aspect, the techniques further include determining a first fee for the network entity as an Rx device, a second fee for the UE as a Tx device, or a combination thereof.

In a thirty-eighth aspect, in combination with the thirty-seventh aspect, the first fee or the second fee is determined based on a pre-sensing operation, a Tx parameter, a resource, a quality of service, or a combination thereof.

In a thirty-ninth aspect, in combination with one or more of the twenty-fifth aspect through the thirty-eighth aspect, the techniques further include receiving, based on the bi-static sensing operation, transmit sensing information from the UE, receive sensing information from the network entity, or a combination thereof.

In a fortieth aspect, in combination with the thirty-ninth aspect, the techniques further include determining, for the UE, a fee for the bi-static sensing operation based on the transmit sensing information, the receive sensing information, a resource available at the network entity for the bi-static sensing operation, a resource needed by the UE for the bi-static sensing operation, a location of the UE, a mobility of the UE, a location of the network entity, a mobility of the network entity, a distance between the UE and the network entity, an operational mode at the network entity, a pre-sensing operation, a pre-sensing measurement report, or a combination thereof.

In a forty-first aspect, in combination with one or more of the twenty-fifth aspect through the thirty-eighth aspect, the techniques further include determining, for the UE, a fixed sensing fee for the bi-static sensing operation performed by the UE.

In a forty-second aspect, in combination with one or more of the twenty-fifth aspect through the forty-first aspect, the techniques further include receiving, from the network entity, a request for a handover operation.

In a forty-third aspect, in combination with the forty-second aspect, the techniques further include, based on the request for the handover operation, performing the handover operation based on a predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof.

In a forty-fourth aspect, in combination with the forty-third aspect, the techniques further include, based on the request for the handover operation, sending a pre-sensing message report or configuration information to a base station.

In a forty-fifth aspect, in combination with the forty-fourth aspect, the techniques further include, based on the request for the handover operation, sending a pre-sensing message report or configuration information to another network entity.