Dual station sensing billing subscription

Abstract

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

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 18 / 163,044, filed on February 1, 2023, entitled “BI-STATIC SENSING CHARGING SUBSCRIPTION,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication systems, and more particularly, to sensing billing subscriptions, such as sensing billing subscriptions associated with dual-station sensing operations. Features may enable and provide sensing operation management and control, reduced overhead signaling, efficient spectrum usage, reduced device hardware, or a combination thereof. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] 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 multiple user equipment (UEs). UEs may communicate with base stations via downlinks and uplinks. A downlink (or forward link) refers to the communication link from a base station to a UE, and an uplink (or reverse link) refers to the communication link from a UE to a base station.

[0006] A base station may transmit data and control information to a UE on the downlink, or receive data and control information from a UE on the uplink. On the downlink, transmissions from a base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continue to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications.

[0008] Conventional 3GPP systems are configured to manage communication-based subscription charging, such as for NR communications. For example, 3GPP systems may use or implement online charging, a mechanism whereby charging information can affect the provided services in real time. Online charging for communication-based subscriptions can be event-based or session-based. To implement online charging, direct interaction between the charging mechanism and the control of network resource usage is required. While 3GPP systems are configured to manage communication-based subscription charging, they are not configured to manage and charge for sensing services that may be provided via 5G, such as long-range or short-range sensing. Summary of the Invention

[0009] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all anticipated features of the present disclosure and is neither intended to identify key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to provide some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to the more detailed description that will be presented later.

[0010] In one aspect of the present disclosure, a method for wireless communication is performed by a user equipment (UE). The method includes sending a request to a network entity to participate in a dual-station sensing operation. The method also includes performing the dual-station sensing operation with the network entity. The method also includes sending sent sensing information associated with the dual-station sensing operation. The sent sensing information is associated with sensing billing subscription information.

[0011] In an additional aspect of the present 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 send a request to a network entity to participate in a dual-station sensing operation. The at least one processor is further configured to perform the dual-station sensing operation with the network entity. The at least one processor is further configured to send sent sensing information associated with the dual-station sensing operation. The sent sensing information is associated with sensing billing subscription information.

[0012] In an additional aspect of the present disclosure, an apparatus includes means for sending a request to a network entity to participate in a dual-station sensing operation. The apparatus also includes means for performing the dual-station sensing operation with the network entity. The apparatus also includes means for sending sent sensing information associated with the dual-station sensing operation. The sent sensing information is associated with sensing billing subscription information.

[0013] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include sending a request to a network entity to participate in a dual-station sensing operation. The operations also include performing the dual-station sensing operation with the network entity. The operations also include sending sent sensing information associated with the dual-station sensing operation. The sent sensing information is associated with sensing billing subscription information.

[0014] In one aspect of the present disclosure, a method for wireless communication is performed by a network entity. The method includes receiving a request from a UE to assist the UE in performing a dual-station sensing operation. The method also includes performing the dual-station sensing operation with the UE. The method also includes transmitting received sensing information associated with the dual-station sensing operation.

[0015] In an additional aspect of the present 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 a request from a UE to assist the UE in performing a dual-station sensing operation. The at least one processor is further configured to perform the dual-station sensing operation with the UE. The at least one processor is further configured to transmit received sensing information associated with the dual-station sensing operation.

[0016] In an additional aspect of the present disclosure, an apparatus includes means for receiving, from a UE, a request to assist the UE in performing a dual-station sensing operation. The apparatus also includes means for performing the dual-station sensing operation with the UE. The apparatus also includes means for transmitting received sensing information associated with the dual-station sensing operation.

[0017] In an additional aspect of the present 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 a request from a UE to assist the UE in performing a dual-station sensing operation. The operations also include performing the dual-station sensing operation with the UE. The operations also include transmitting received sensing information associated with the dual-station sensing operation.

[0018] In one aspect of the present disclosure, a method for wireless communication is performed by a network. The method includes sending a request to a network entity for capability information associated with the network entity's availability to participate in one or more dual-station sensing operations. The method also includes receiving a request from a UE to assist the UE in performing the dual-station sensing operation. The method also includes sending network entity information to the UE. The network entity information indicates a network entity selected from one or more network entities available to participate in the dual-station sensing operation.

[0019] In an additional aspect of the present 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 send a request to a network entity for capability information associated with the network entity's availability to participate in one or more dual-station sensing operations. The at least one processor is further configured to receive a request from a UE to assist the UE in performing the dual-station sensing operation. The at least one processor is further configured to send network entity information to the UE. The network entity information indicates a network entity selected from one or more network entities available to participate in the dual-station sensing operation.

[0020] In an additional aspect of the present disclosure, an apparatus includes means for sending a request to a network entity for capability information associated with the network entity's availability to participate in one or more dual-station sensing operations. The apparatus also includes means for receiving a request from a UE to assist the UE in performing the dual-station sensing operation. The apparatus also includes means for sending network entity information to the UE. The network entity information indicates a network entity selected from one or more network entities available to participate in the dual-station sensing operation.

[0021] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include sending a request to a network entity for capability information associated with the network entity's availability to participate in one or more dual-station sensing operations. The operations also include receiving a request from a UE to assist the UE in performing the dual-station sensing operation. The operations also include sending network entity information to the UE. The network entity information indicates a network entity selected from one or more network entities available to participate in the dual-station sensing operation.

[0022] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description below may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the figures in the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0023] Although various aspects and specific implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses may be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations may range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the devices in conjunction with the described various aspects and features may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] A further understanding of the nature and advantages of the present disclosure may be achieved by referring to the following drawings. In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second reference number.

[0025] Figure 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects.

[0026] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0027] Figure 3 A diagram illustrating an example decomposed base station architecture in accordance with one or more aspects is shown.

[0028] Figure 4is a block diagram illustrating an example wireless communication system that supports sensing billing subscriptions in accordance with one or more aspects.

[0029] Figure 5 is a ladder diagram illustrating an example of operations supporting sensing billing subscriptions in accordance with one or more aspects.

[0030] Figure 6 is a flow diagram illustrating an example process for supporting sensory billing subscriptions in accordance with one or more aspects.

[0031] Figure 7 is a block diagram of an example UE supporting sensing charging subscriptions according to one or more aspects.

[0032] Figure 8 is a flow diagram illustrating an example process for supporting sensory billing subscriptions in accordance with one or more aspects.

[0033] Figure 9 is a flow diagram illustrating an example process for supporting sensory billing subscriptions in accordance with one or more aspects.

[0034] Figure 10 is a block diagram of an example base station supporting sensing charging subscriptions according to one or more aspects.

[0035] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0036] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details to provide a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0037] The present disclosure provides systems, apparatuses, methods, and computer-readable media that support sensing billing subscriptions or dual-station sensing operations. For example, the present disclosure describes sensing billing subscription information associated with a sensing billing subscription for a user equipment (UE) configured to perform a sensing operation (such as dual-station sensing). For example, the UE may initiate a sensing operation (such as a dual-station sensing operation) performed with the assistance of a network entity (such as a base station, another UE, a roadside unit (RSU), or another device). In some specific implementations, a network (e.g., a centralized controller or a core network) is configured to determine a cost for a sensing service or sensing operation and assist the UE in performing the sensing operation. For example, the network may be configured to determine the cost based on the following: dual-station sensing measurement information, resources available at the network entity for the dual-station sensing operation, resources required by the UE for the dual-station sensing operation, the location of the UE, the mobility of the UE, the location of the network entity, the mobility of the network entity, the distance between the UE and the network entity, an operating 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 for performing sensing operations with the UE. For example, the network may identify one or more network entities based on the location of the network entity, the location of the UE, capability information received from the network entity, usage charges of the network entity, sensing charging subscription information associated with the UE, quality of service requested by the UE, 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 sensing resources, sensing transmission parameters, sensing charges, or a combination thereof. In some implementations, the UE may perform pre-sensing operations with one or more network entities to select a network entity with which to perform dual-station sensing operations. In some implementations, the network entity, the network, or both may perform a handover to further assist (or continue to assist) the UE in performing sensing operations, such as dual-station sensing operations.

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

[0039] The present disclosure as a whole relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, the techniques and apparatuses may be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0040] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0041] For example, a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). The Third Generation Partnership Project (3GPP) defined the standard for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN), also known as GERAN. GERAN is the radio component of GSM / EDGE, along with the network connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of a GSM network through which phone calls and packet data are routed from the public switched telephone network (PSTN) and the internet to subscriber handsets (also known as user terminals or user equipment (UE)), and vice versa. A mobile phone operator's network may include one or more GERANs, which, in the case of UMTS / GSM networks, may be coupled to the UTRAN. Additionally, the operator's network may also include one or more LTE networks, or one or more other networks. Different network types may use different radio access technologies (RATs) and RANs.

[0042] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are either known or under development. For example, 3GPP is a collaboration between a group of telecommunications associations to define globally applicable third generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP can define specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may describe certain aspects with reference to LTE, 4G, or 5G NR technologies; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0043] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km) 2 (1) ultra-low complexity (e.g., about 10s of bits / sec), ultra-low power consumption (e.g., about 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) includes mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) provides services with enhanced mobile broadband (including very high capacity (e.g., about 10Tbps / km 2 ), coverage of very high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0044] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises for FR2, which is often (interchangeably) referred to as the "millimeter wave" (mmWave) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "mmWave" band by the International Telecommunication Union (ITU).

[0045] In view of the above aspects, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like, if used herein, can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the term "mmWave" and the like, if used herein, can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0046] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features may include scalable numerologies and transmit time intervals (TTIs); a common, flexible framework for efficiently multiplexing services and features using dynamic, low-latency time division duplex (TDD) or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input, multiple-output (MIMO), robust mmWave transmission, advanced channel coding, and device-centric mobility. The scalability of numerologies and subcarrier spacing in 5G NR efficiently addresses the operation of various services across different spectrums and deployments. For example, in various outdoor and macro coverage deployments with less than 3 GHz FDD or TDD implementations, subcarrier spacing may occur as 15 kHz, for example, over bandwidths of 1 MHz, 5 MHz, 10 MHz, or 20 MHz. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, subcarrier spacing may occur as 30 kHz over 80 MHz / 100 MHz bandwidths. For various other indoor broadband implementations, using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting over mmWave components using TDD at 28 GHz, the subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0047] 5G NR's scalable parameter set facilitates scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design, where uplink or downlink scheduling information, data, and acknowledgments are located in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0048] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0049] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0050] Although various aspects and specific implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementations or use can be implemented via integrated chip specific implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems comprising one or more described aspects. In some practical environments, the devices in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0051] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements, including, for example, cellular-style network arrangements as well as non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.).

[0052] Figure 1The illustrated wireless network 100 includes a number of base stations 105 and other network entities. A base station can be a station that communicates with a UE and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In specific implementations of the wireless network 100 herein, the base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 can include multiple operator wireless networks). Additionally, in specific implementations of the wireless network 100 herein, the base stations 105 can provide wireless communications using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, an individual base station 105 or UE 115 can be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0053] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or femto cell) or other type of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (such as a femto cell) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3D, full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0054] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some cases, the network may be enabled or configured to handle dynamic switching between synchronous and asynchronous operation.

[0055] UEs 115 are dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in the standards and specifications promulgated by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile stations (MSs), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices, or vehicle modules, or some other suitable terminology. In this document, a "mobile" device or UE does not necessarily have the ability to be mobile and may be stationary. Some non-limiting examples of mobile devices, for example, may include one or more implementations of UE 115, including mobile phones, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quadcopter, smart energy or security equipment, solar panels or solar arrays, urban lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d of the specific implementation illustrated in FIG are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 UEs 115e to 115k illustrated in FIG. 1 are examples of various machines configured for communication that access wireless network 100 .

[0056] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication links (represented as lightning balls) indicate wireless transmissions between a UE and a serving base station (which is a base station designated to serve the UE on the downlink or uplink), or desired transmissions between base stations, as well as backhaul transmissions between base stations. A UE may operate as a base station or other network node in some scenarios. Backhaul communications between base stations of wireless network 100 may be performed using wired or wireless communication links.

[0057] In operation, at wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Gray Alerts.

[0058] The wireless network 100 of the embodiment supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e, which is a drone. The redundant communication links with UE 115e include links from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine-type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as small cell base station 105f and macro base station 105e via the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network via small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications (eg, in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e).

[0059] The base stations 105 can communicate with the core network 130 and with each other. For example, the base stations 105 can interface with the core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) via the backhaul link (e.g., via X2, Xn, or other interfaces).

[0060] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to network operator IP services. The operator IP services may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet switched (PS) streaming services.

[0061] In some implementations, the core network 130 includes or is coupled to a location management function (LMF) 131, which is an entity in the 5G core network (5GC) that supports various functionalities, such as managing support for different location services for one or more UEs. For example, the LMF 131 may include one or more servers, such as multiple distributed servers. The base station 105 may forward location messages to the LMF 131 and may communicate with the LMF via the NR Positioning Protocol A (NRPPa). The LMF 131 is configured to control positioning parameters of the UE 115, and the LMF 131 may provide information to the base station 105 and the UE 115 so that actions can be taken at the UE 115. In some implementations, the UE 115 and the base station 105 are configured to communicate with the LMF 131 via an access and mobility management function (AMF).

[0062] Figure 2 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For the restricted association scenario (as described above), the base station 105 can be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the base station 105f, and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0063] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for the physical broadcast channel (PBCH), the physical control format indicator channel (PCFICH), the physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), the physical downlink control channel (PDCCH), the enhanced physical downlink control channel (EPDCCH), the MTC physical downlink control channel (MPDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process (e.g., encode and symbol map) the data and control information separately to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., by analog-converting, amplifying, filtering, and frequency upconverting it) to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0064] At UE 115, antennas 252a through 252r may receive downlink signals from base station 105 and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols as needed, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 115 to a data sink 260, and provide decoded control information to a controller 280, such as a processor.

[0065] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, if necessary, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if necessary, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0066] The controllers 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing Figures 1 to 10 Other processes illustrated or described with reference to these figures may be performed or used for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0067] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band that may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may conventionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-transmit (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some implementations, the CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. In particular, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence that indicates the use of the channel. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as an indication of a collision).

[0068] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The core network 320 may include or correspond to the core network 130. The CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RUs 340 may communicate with corresponding UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 may be served simultaneously by multiple RUs 340.

[0069] Each of these units (i.e., CU 310, DU 330, RU 340, as well as near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals, or both, to one or more of the other units via the wireless transmission medium.

[0070] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

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

[0072] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 115. In some implementations, both real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0074] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0075] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0076] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a transmit / receive point (TRP), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), a core network, an LFM, and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station or a 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 network node, the second network node, and the third network node may be different from these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc., may include disclosure of the UE, base station, apparatus, device, computing system, etc. as a network node. For example, a 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 the present disclosure, once a specific example is expanded upon in accordance with the present 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), a broader example of the narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example 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, etc., configured to receive 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, etc.

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

[0078] Figure 4 is a block diagram of an example wireless communication system 400 that supports sensing billing subscriptions according to one or more aspects. In some examples, the wireless communication system 400 can implement aspects of the wireless network 100. The wireless communication system 400 includes a UE 115, a base station 105, a core network 130, and a network entity 470. In some implementations, the base station 105 and the core network 130 can be individually or collectively referred to as a network, a network device, or a network system. Although one UE 115, one base station 105, and one network entity 470 are illustrated, in some other implementations, the wireless communication system 400 can generally include multiple UEs 115, multiple base stations 105, multiple network entities 470, or a combination thereof.

[0079] In some implementations, the wireless communication system 400 includes an object 490, such as a stationary object or a mobile object. The object 490 can be sensed by a device (such as a UE 115, a network entity 470, a base station 105, or a combination thereof) based on one or more sensing operations. As illustrative, non-limiting examples, the one or more sensing operations can include single-station sensing operations or dual-station sensing operations. In some implementations, the one or more sensing operations can be performed to detect the object 490, determine the location of the object 490, or a combination thereof.

[0080] UE 115 may include a device such as a mobile device or a vehicle. UE 115 may be configured to use one or more uplink (UL) resources to perform sensing. For example, sensing may include dual-station sensing or single-station sensing. When UE 115 is a vehicle, UE 115 may perform one or more sensing operations to sense an environment, such as an indoor environment of a vehicle or an outdoor environment of a vehicle. For example, UE 115 may sense surrounding objects for automotive applications such as collision avoidance. To implement UE-side sensing, such as joint communication and radar (JCR) sensing, UL resources (e.g., communication resources) may be reused for sensing. For example, UL resources may be shared between communication mode and radar mode. For example, in some implementations, there may be separate resources for communication or radar based on TDM mode use. In some such implementations, SRS may be used as a sensing waveform. Alternatively, the same resources for communication and radar may be used with a joint co-designed waveform.

[0081] The UE 115 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as "processor 402"), one or more memory devices 404 (hereinafter collectively referred to as "memory 404"), and one or more sensing devices 415 (hereinafter collectively referred to as "sensing device 415"). The sensing device 415 may include or correspond to a dual-station sensing device. In some implementations, the UE 115 may include an interface (e.g., a communication interface) that includes a transmitter 416, a receiver 418, or a combination thereof. The processor 402 may be configured to execute instructions 405 stored in the memory 404 to perform the operations described herein. In some implementations, the processor 402 includes or corresponds to one or more of the receive processor 258, the transmit processor 264, and the controller 280, and the memory 404 includes or corresponds to the memory 282.

[0082] Memory 404 includes or is configured to store instructions 405 and information 406. Information 406 may include capability information 408, sensing billing subscription information 409, and measurement information 410. Capability information 408 may include or indicate one or more capabilities of UE 115 associated with performing dual-station sensing operations. For example, capability information 408 may include or indicate whether UE 115 is configured to function as a transmit (Tx) device or a receive (Rx) device for dual-station sensing operations. Additionally or alternatively, capability information 408 may include or indicate time domain parameters, frequency domain parameters, beam direction, beam bandwidth, transmit power, quality of service, or a combination thereof associated with dual-station sensing operations. Sensing billing subscription information 409 may include or indicate sensing subscriptions associated with one or more sensing operations or one or more sensing services. A sensing subscription may include or indicate functionality, rules, profiles, models, billing charges, or a combination thereof. In some implementations, a sensing subscription is associated with or based on an agreement (such as a contract) that identifies or defines a sensing subscription from among a plurality of available sensing subscriptions.

[0083] The measurement information 410 may include or indicate information based on a pre-sensing operation, a bi-station sensing operation, or a combination thereof. The measurement information 410 may include information generated by the UE 115, the network entity 470, another network entity, or a combination thereof. In some implementations, the measurement information 410 includes a pre-sensing measurement report, transmit sensing information (associated with a Tx device of the bi-station sensing operation), receive sensing information (associated with a Rx device of the bi-station sensing operation), one or more parameters associated with the pre-sensing operation or the bi-station sensing operation, or a combination thereof. The transmit sensing report may include or indicate completion of the bi-station sensing operation, receive sensing information, a network entity, time domain parameters, frequency domain parameters, beam direction, beam width, transmit power, quality of service, or a combination thereof. The receive sensing information may include or indicate received signal strength, time domain parameters, time travel time, beam direction, beam width, quality of service, the location of an object, or a combination thereof.

[0084] The sensing device 415 may be configured to be used in a dual-station sensing operation. The sensing device 415 includes one or more transmitters 416 (hereinafter collectively referred to as "transmitters 416") and one or more receivers 418 (hereinafter collectively referred to as "receivers 418"). The transmitter 416 is configured to send reference signals, control information, and data to one or more other devices, and the receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 416 may send signaling, control information, and data to the base station 105, and the receiver 418 may receive signaling, control information, and data from the base station. In some implementations, the transmitter 416 and the receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 416 or the receiver 418 may include or correspond to a reference signal. Figure 2 4. In some implementations, the sensing device 415 is associated with a joint communication and radar (JCR) system. The JCR system can be categorized as a collaborative JCR system, or a co-design of a communication and radar system. For example, the sensing device 415 can be associated with a co-design of a communication and radar system. Although described as including both a transmitter 416 and a receiver 418, in other implementations, the sensing device 415 can include the transmitter 416 but not the receiver 418, or can include the receiver 418 but not the transmitter 416.

[0085] In some implementations, the UE 115 may include one or more antenna arrays. The one or more antenna arrays may be coupled to the transmitter 416, the receiver 418, or the communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with the base station 105). 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 a TX beam and an RX beam. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding 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 UE 115. Each separate 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 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 corresponding beam.

[0086] UE 115 may include one or more components as described herein with reference to UE 115. In some implementations, UE 115 is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

[0087] The network entity 470 may include a device such as a base station, a roadside unit, a node, or another UE. The network entity 470 may be a mobile device or a stationary device. The network entity 470 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 472 (hereinafter collectively referred to as "processors 472"), one or more memory devices 474 (hereinafter collectively referred to as "memory 474"), and one or more sensing devices 475 (hereinafter collectively referred to as "sensing devices 475"). The sensing device 475 may include or correspond to a dual-station sensing device. In some implementations, the network entity 470 may include an interface (e.g., a communication interface) that includes a transmitter 476, a receiver 478, or a combination thereof. The processor 472 may be configured to execute instructions 480 stored in the memory 474 to perform the operations described herein. In some implementations, the processor 472 includes or corresponds to one or more of the receive processor 258, the transmit processor 264, and the controller 280, and the memory 474 includes or corresponds to the memory 282.

[0088] Memory 474 includes or is configured to store instructions 480 and information 484. Information 484 may include or correspond to information 406.

[0089] The sensing device 475 may include or correspond to the sensing device 415. The sensing device 475 may be configured to be used in a dual-station sensing operation. The sensing device 475 includes one or more transmitters 476 (hereinafter collectively referred to as "transmitters 476") and one or more receivers 478 (hereinafter collectively referred to as "receivers 478"). The transmitter 476 is configured to send reference signals, control information, and data to one or more other devices, and the receiver 478 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 476 may send signaling, control information, and data to the base station 105 or the UE 115, and the receiver 478 may receive signaling, control information, and data from the base station or the UE. In some specific implementations, the transmitter 476 and the receiver 478 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 476 or the receiver 478 may include or correspond to a reference Figure 24. One or more components of the UE 115 described herein. In some implementations, the sensing device 475 is associated with a joint communication and radar (JCR) system. The JCR system can be classified as a collaborative JCR system, or a co-design of a communication and radar system. For example, the sensing device 475 can be associated with a co-design of a communication and radar system. Although described as including both a transmitter 476 and a receiver 478, in other implementations, the sensing device 475 can include the transmitter 476 but not the receiver 478, or can include the receiver 478 but not the transmitter 476.

[0090] In some implementations, the network entity 470 may include one or more antenna arrays. The one or more antenna arrays may be coupled to a transmitter 476, a receiver 478, or a communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices, such as a UE 115 or a base station 105. 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 a TX beam and an RX beam. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding 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 network entity 470. Each separate 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 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 corresponding beam.

[0091] The network entity 470 may include one or more components as described herein with reference to the UE 115. In some implementations, the network entity 470 is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

[0092] The base station 105 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 452 (hereinafter collectively referred to as "processor 452"), one or more memory devices 454 (hereinafter collectively referred to as "memory 454"), and one or more sensing devices 455 (hereinafter collectively referred to as "sensing device 455"). In some implementations, the base station 105 may include an interface (e.g., a communication interface) including a transmitter 456, a receiver 458, or a combination thereof. The processor 452 may be configured to execute instructions 460 stored in the memory 454 to perform the operations described herein. In some implementations, the processor 452 includes or corresponds to one or more of the receive processor 238, the transmit processor 220, and the controller 240, and the memory 454 includes or corresponds to the memory 242.

[0093] Memory 354 includes or is configured to store instructions 460 and information 464. In some implementations, information 464 may include or correspond to information 406 or 484. Information 464 may include capability information 465, sensing charging subscription information 466, and sensing charges 467. Capability information 465 may include or correspond to capability information 408. Capability information 465 may include or indicate the capabilities of UE 115, network entity 470, base station 105, or a combination thereof. Sensing charging subscription information 466 may include or correspond to sensing charging subscription information 409. Sensing charging subscription information 466 may include or correspond to subscriptions associated with UE 115 or network entity 470, such as subscriptions for sensing services. Sensing charges 467 may include or correspond to charges for sensing services associated with or used by UE 115, network entity 470, or a combination thereof, such as fees or costs.

[0094] The sensing device 455 includes one or more transmitters 456 (hereinafter collectively referred to as "transmitters 456") and one or more receivers 458 (hereinafter collectively referred to as "receivers 458"). The transmitter 456 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 458 is configured to receive reference signals, control information, and data from one or more other devices. For example, the transmitter 456 may transmit signaling, control information, and data to the UE 115 or the network entity 470, and the receiver 458 may receive signaling, control information, and data from the UE and the network entity. In some implementations, the transmitter 456 and the receiver 458 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 456 or the receiver 458 may include or correspond to a reference signal. Figure 2 One or more components of a base station 105 are described.

[0095] In some implementations, the base station 105 may include one or more antenna arrays. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices, such as the UE 115. 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 a TX beam and an RX beam. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding 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 generate multiple beams concurrently, for example using multiple RF chains of the base station 105. 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 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 corresponding beam.

[0096] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include a plurality of 5G-capable UEs 115 and a plurality of 5G-capable base stations 105, such as UEs and base stations configured to operate according to 5G NR network protocols, such as those defined by 3GPP. In some other implementations, the wireless communication system 400 implements a 6G network.

[0097] In some specific implementations, the UE 115 or the sensing device 415 may be associated with a JCR system. The JCR system provides advantages and benefits of at least assisting radar or radar assisting communication, spectrum reuse, hardware reuse, or a combination thereof. The JCR system can be classified as a collaborative JCR system, or a collaborative design of communication and radar systems. In a collaborative JCR system, information can be shared between the communication system and the radar system to improve performance without significantly changing the core operations of the radar and communication systems. The collaborative JCR system provides advantages and benefits of at least spectrum reuse and ease of implementation. In the collaborative design of the communication and radar systems, a common transmitter or receiver can be used for both communication functionality and radar functionality. The collaborative design of the communication and radar systems may require modifications in the transmit waveform generation or receiver processing of both or either of the communication and radar systems. The collaborative design of the communication and radar systems provides advantages and benefits of at least reducing hardware and spectrum reuse.

[0098] For NR communications, a charging system that implements online charging may be used. Online charging is a mechanism in which charging information can affect the services provided in real time, thus requiring direct interaction of the charging mechanism with the control of network resource usage. Online charging may include the process of collecting charging information for network resource usage concurrently with that resource usage in the same manner as offline charging. In some implementations, authorization for network resource usage must be obtained by or from the network before actual resource usage occurs by the UE 115. This authorization may be granted by an online charging system (OCS) or a converged charging system (CCS) upon network request. In some implementations, the OCS or CCS may be located at the network, such as at the base station 105 or the core network 130.

[0099] The network may receive a network resource usage request and, based on the network resource usage request, aggregate relevant billing information and generate billing events for the OCS or CCS. For example, the billing events may be generated in real time. The OCS or CCS may then return an appropriate resource usage authorization. The resource usage authorization may be limited in scope (e.g., data volume or duration), so the authorization may need to be renewed from time to time as long as the user's network resource usage persists.

[0100] In some implementations, the billing system may include or use an event-based charging function (EBCF). The EBCF may run within the OCS and may be used to charge events based on their occurrence rather than the duration or amount used in the event. Examples of events include SMS, MMS, or the purchase of content (applications, games, music, video on demand, etc.). The EBCF may be configured to perform event-based charging and credit control (e.g., content charging) at the bearer level, the subsystem level, or the service level. For example, at the bearer level, the EBCF may perform event-based charging based on bearer usage requests received from the network, such that the EBCF controls bearer usage in the network, such as SMS. As another example, at the subsystem level, the EBCF may perform event-based charging based on session resource usage requests received from the network (e.g., IMS MRFC), such that the EBCF controls resource availability in the network, such as having the ability to authorize or deny resource usage. As another example, at the service level, the EBCF can perform event-based charging based on application server requests received from the network (e.g., an IMS application server or an MMS relay server), so that the EBCF controls application service availability in the network, for example, it has the ability to authorize or deny service usage in the network. The EBCF can communicate with the rating function to determine the value of the requested service usage, and can communicate with the account balance management function (ABMF) to query and update the subscriber's account and counter status.

[0101] In some implementations, the charging system may include or utilize a session-based charging function (SBCF). The SBCF may be configured to run within the OCS. The SBCF may be responsible for online charging of network / user sessions (such as voice calls, IP CAN bearers, IP CAN sessions, or IMS sessions). Note that utility services such as electricity or water may be charged based on overall usage over a specific time period. The SBCF may be configured to perform session-based charging and credit control at the bearer level, subsystem level, or service level. For example, at the bearer level, the SBCF may perform session-based charging based on bearer usage requests received from the network, enabling the SBCF to control bearer usage in the network, e.g., in terms of the time or amount of grants. As another example, at the subsystem level, the SBCF may perform session-based charging based on session resource usage requests received from the network (e.g., an IMS CSCF), enabling the SBCF to control sessions in the network, e.g., having the ability to authorize or deny session establishment requests and terminate existing sessions. As another example, at the service level, the SBCF can perform session-based charging based on service usage requests received from the network. This allows the SBCF to control service availability in the network, for example, by enabling it to authorize or deny service usage. The SBCF can communicate with the rating function to determine the value of the requested bearer resources or requested session. Additionally or alternatively, the SBCF can communicate with the ABMF to query and update the subscriber's account and counter status.

[0102] In some implementations, the sensing charging subscription information 409 or 466 is associated with a sensing charging subscription for a UE 115 or a network entity 470 configured to perform dual-station sensing. For example, the sensing charging subscription information 409 may include or define a sensing charging subscription, such as a sensing charging subscription model, for the UE 115. Additionally or alternatively, the sensing charging subscription information 466 may include or define a sensing charging subscription, such as a sensing charging subscription model, for the network entity 470.

[0103] In some implementations, the network entity 470 is associated with sensing billing subscription information for the network entity 470, such as a dual-station sensing billing subscription model. The network entity 470 can be a mobile device or a fixed device. Additionally or alternatively, the network entity 470 is configured to receive a request for assistance in dual-station sensing operations from another device, such as the UE 115. In such a scenario—for example, when the network entity 470 receives the request for assistance—the other device can be referred to as an initiating device, and the network entity 470 can be referred to as a helping device.

[0104] In some implementations, a controller, such as a centralized controller, may be configured to assist the UE 115 in identifying or selecting an assisting device. The controller may include or correspond to the base station 105, the core network 130, the LMF 131, the network, or a combination thereof. The controller (such as the base station 105) may be configured to request (e.g., ping) information associated with the assisted dual-station sensing operation from one or more devices (such as one or more base stations, one or more UEs, one or more network entities, or a combination thereof). In some implementations, the controller may request capability information, such as capability information 408 or 465, from the one or more devices. Additionally or alternatively, the controller may request the location of the one or more devices, the mobility of the one or more devices, the types of sensing operations or modes supported by the one or more devices, or a combination thereof. In some implementations, the controller may select at least one of the one or more devices (the assisting device) as a candidate for assisting the initiating device (e.g., the UE 115) in initiating the dual-station sensing operation. The controller may select the at least one device as a candidate based on the location of the at least one device, the mobility or direction of travel of the initiating device, the 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 send network entity information indicating the selected at least one device to the UE 115 based on sensing billing subscription information 409 or 466, a fee charged to the UE 115, or a combination thereof. Additionally or alternatively, based on the selection of the at least one device, the controller may signal the at least one device (e.g., the network entity 470) to indicate that the at least one device is selected to participate in a dual-station sensing operation with the initiating device (e.g., the UE 115). The controller may also indicate a fee to be charged for participating in the dual-station sensing operation based on the sensing billing subscription information for the UE 115 or the network entity 470.

[0105] In some implementations, the UE 115 and the network entity 470 may perform a pre-sensing operation before performing a dual-station sensing operation. For example, the controller may be configured to indicate that the pre-sensing operation is available between the UE 115 and the network entity 470 so that the UE 115 can determine whether the network entity 4708 is suitable for dual-station sensing. For example, the controller may indicate that the pre-sensing operation is available for charging.

[0106] In some implementations, the UE 115 can perform a dual-station sensing operation with at least one device selected by the controller, such as the network entity 470. For example, the controller can send network entity information to the UE 115 indicating that the network entity 470 is participating in the dual-station sensing operation. In some implementations, the UE 115 and the controller can communicate to determine (or negotiate) sensing resources, sensing transmission parameters, sensing billing charges, or a combination thereof associated with performing the dual-station sensing operation using the network entity or a combination thereof.

[0107] In some implementations, the controller may support an initiating device (e.g., UE 115) in selecting the at least one device 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 billing subscription information 409 or 466). 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. For example, the pre-sensing mode may be used for coarse sensing estimation performance with low resource usage overhead. As another example, the pre-sensing mode may be used for fine sensing estimation performance over a short duration. In some implementations, the at least one device may generate a pre-sensing measurement report based on the pre-sensing operation. A fee may be charged to the initiating device, the at least one device, or both based on Tx parameters or resources required 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 a Rx node). Additionally or alternatively, the pre-sensing measurement report may be generated or communicated to the initiating device, the controller, or another device for fee collection. For example, the at least one device may generate a pre-sensing measurement report and transmit it to the controller. As illustrative, non-limiting examples, the pre-sensing measurement report may include or indicate channel quality, amount of interference, signal strength, or a combination thereof. The controller may transmit the pre-sensing measurement report to one or more other devices, or may use the pre-sensing measurement report to select a device for the initiating device to use in the dual-station sensing operation. As another example, the at least one device may generate a pre-sensing measurement report and transmit it to the initiating device. Based on the measurement report, the initiating device may determine whether modifications to resources, transmission parameters, or different devices are needed for the dual-station sensing operation. In some implementations, the controller may not provide or enable pre-sensing measurement reports.

[0108] In some implementations, the controller is configured to determine a fee (for the initiating device or the secondary device) based on the resources available at the secondary device, the resources required for the bistatic sensing operation performed by the initiating device, or a combination thereof. For example, the fee may be a fixed sensing fee for performing or supporting the bistatic sensing operation. As another example, if a portion (e.g., a fraction) of the resources required by the initiating device (relative to the total available resources) approaches 100%, the controller may deny sensing service or charge an additional fee (in addition to the standard fee for sensing service). Additionally or alternatively, the controller may be configured to determine a fee (for the initiating device or the secondary device) based on the location or mobility of the initiating device, the secondary device, or a combination thereof. For example, if the initiating device is greater than or equal to a threshold distance from the secondary device, or if the devices are traveling in different directions, the controller may deny sensing service. Additionally or alternatively, the controller may be configured to determine a fee (for the initiating device or the secondary device) based on the secondary device's mode (e.g., Tx mode or Rx mode). For example, a secondary device operating in Tx mode may incur a higher fee than a secondary device operating in Rx mode, such as due to the secondary device's required active transmission. In some embodiments, the controller may be further configured to determine the fee (for the initiating device or the auxiliary device) based on additional service requests, such as the pre-sensing mode, the type of measurement report (e.g., a pre-sensing measurement report in which the auxiliary device acts as an Rx node, a pre-sensing measurement report in which the auxiliary device acts as a Tx node, the frequency of the pre-sensing measurement report), or a combination thereof.

[0109] In some implementations, the controller enables selection of a secondary device, such as for a given sensing subscription fee. The selection can be based on subscription billing fees for different Tx and Rx modes for the secondary device, a subscription package for the initiating device, a sensing QoS request from the initiating device, a predicted sensing QoS provided by the secondary device, or a combination thereof.

[0110] In some implementations, the initiating device is configured to perform dual-station sensing with a secondary device selected and agreed upon by the controller. Additionally, the initiating device can communicate with the controller to determine or negotiate sensing resources, sensing transmission parameters, sensing billing charges, or a combination thereof. Additionally or alternatively, the initiating device and the secondary device can communicate to determine whether the initiating device's sensing QoS requirements and the secondary device's sensing billing charges are consistent, or whether sensing service is denied.

[0111] In some implementations, a handover of a secondary device is performed to assist an initiating device with improved sensing performance. For example, a controller may enable a handover of a secondary device for additional charging to an initiating device or a secondary device. As another example, a controller or a serving base station (e.g., 105) may transmit a sensing measurement report (such as a pre-sensing measurement report) or a Tx / Rx configuration to another base station for additional charges. As another example, a controller or a serving base station (e.g., 150) may transmit a sensing measurement report (such as a pre-sensing measurement report) or a Tx / Rx configuration to a future secondary device within the coverage area of ​​the base station for charges. In some implementations, the handover of a secondary 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.

[0112] The exemplary operation of the wireless communication system 400 is at least with reference to Figure 5 Described. Figure 5 is a ladder diagram illustrating an example of operations supporting sensing billing subscriptions according to one or more aspects. Figure 5 As shown, the ladder diagram system includes UE 115, network entity 470 and network 430. Network 506 may include or correspond to base station 105 or core network 130. Although shown and described as a single entity, in some specific implementations, network 506 may be a distributed server system. UE 115, network entity 470 and network 506 may include one or more components and be configured to perform one or more operations, as described in reference Figures 1 to 4 described.

[0113] During operation, at 510, the network 506 can send a capability request. The capability request can include a request for capability information associated with the availability of a device (such as the UE 115 or the network entity 470) to participate in one or dual-station sensing operations. The capability request can be received by the network entity 470. In some implementations, the capability request can additionally or alternatively be received by the UE 115.

[0114] At 512, in response to the request, the network entity sends a capability response to the network 506. The capability response may include or indicate information 406, capability information 408, information 464, capability information 465, or information 484. The capability response may include capability information of the network entity 470, the UE 115, or a combination thereof. In some implementations, the UE 115 may send the capability response to the network 506. The network 506 may identify one or more network entities that may be used to participate in the dual-station sensing operation based on the one or more capability responses received by the network 506 from the one or more network entities.

[0115] At 514, UE 115 (such as an initiating device) sends a dual-station sensing request. For example, UE 115 may send a dual-station sensing request to network 506. The dual-station sensing request may include or indicate a request to perform a dual-station sensing operation, such as a request for UE 115 to perform or initiate a dual-station sensing operation.

[0116] At 516, the network 506 may send network entity information. For illustration, the network 506 may send a network entity information response to the dual-station sensing request. The UE 115, the network entity 470, or both may receive the network entity information. The network entity information may indicate at least one network entity selected from one or more network entities available for participating in the dual-station sensing operation, such as the network entity 470. In some implementations, the network 506 selects the network entity 470 from the one or more entities available for participating in the dual-station sensing operation (for inclusion in the network entity information). For example, the network entity 470 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, usage charges for the network entity, sensing billing subscription information associated with the UE, quality of service requested by the UE, available quality of service associated with the network entity, or a combination thereof.

[0117] At 518, UE 115 sends a network entity request to network entity 470. The network entity request may include a request for network entity 470 to participate in a dual-station sensing operation. In some implementations, UE 115 may identify network entity 470, transmit the network entity request, or both based on network entity information received from network 506. At 520, network entity 470 may send a network entity reply to UE 115. The network entity reply may be a response to the network entity request and may indicate whether network entity 470 can or will participate in a dual-station sensing operation. The network entity information may indicate sensing resources (e.g., channels), sensing transmission parameters (e.g., transmit power, beam width, beam direction, quality of service), sensing billing charges (e.g., for pre-sensing operations, dual-station sensing operations, use of network entity 470), or a combination thereof.

[0118] At 522, the UE sends a pre-sensing waveform. The pre-sensing waveform may be sent as part of a pre-sensing operation preceding the dual-station sensing operation. UE 115 may determine to perform the pre-sensing operation based on network entity information, a network entity reply, or a combination thereof. In some implementations, the pre-sensing operation is associated with a coarse sensing estimate or a fine sensing estimate, or a combination thereof, performed via an UL channel. At 524, network entity 470 sends (and UE 115 receives) a pre-sensing measurement report. In some implementations, network 506 may additionally or alternatively receive the pre-sensing measurement report from network entity 470. UE 115 may determine whether to perform the dual-station sensing operation with network entity 470 based on the pre-sensing measurement report, the quality of service of UE 115, sensing charging charges associated with network entity 470, or a combination thereof. In some implementations, UE 115 may perform pre-sensing operations with one or more network entities and select one of the one or more network entities for the dual-station sensing operation based on one or more pre-sensing operation results.

[0119] At 526, UE 115 transmits a sensing waveform. For example, UE 115 can initiate or perform a dual-station sensing operation with network entity 470, and the dual-station sensing operation includes UE 115 transmitting a sensing waveform that is received by network entity 470. In some implementations, the sensing waveform received by network entity 470 can include a reflection of the sensing waveform from an object, such as object 490.

[0120] At 528, the network entity 470 may transmit the received sensing information. For example, the network entity 470 may generate the received sensing information based on the reception of the sensing waveform—e.g., the received sensing information is associated with a dual-station sensing operation. The received sensing information may include, indicate, or correspond to the information 406, the measurement information 410, or the information 484. Although the received sensing information is shown as being transmitted to the UE 115, in other implementations, the received sensing information may additionally or alternatively be transmitted to the network 506.

[0121] At 530, the UE 115 transmits transmit sensing information. For example, the UE 115 can generate the transmit sensing information based on the transmission of the sensing waveform—for example, the transmit sensing information can be associated with a bistatic sensing operation. Although the transmit sensing information is shown as being transmitted to the network 506, in other implementations, the receive sensing information can additionally or alternatively be transmitted to the network entity 470. In some implementations, the transmit sensing information can indicate completion of the bistatic sensing operation, receive sensing information, a network entity, time domain parameters, frequency domain parameters, beam direction, beam width, transmit power, quality of service, or a combination thereof.

[0122] In some implementations, after receiving the receive sensing information, the transmit sensing information, or a combination thereof, the network 506 can determine a charge associated with the dual-station sensing request, the pre-sensing operation, the dual-station sensing operation, or a combination thereof. The charge can include or correspond to sensing charging 467. Additionally or alternatively, the charge can be determined based on sensing charging subscription information associated with the UE 115, the network entity 470, or a combination thereof. For example, the sensing charging subscription information can include or correspond to information 406, sensing charging subscription information 409, information 484, information 464, or sensing charging subscription information 466. Additionally or alternatively, the network 506 may determine a cost for the dual-station sensing operation based on the sending of the sensing information, the receiving of the sensing information, the resources available at the network entity 470 for the dual-station sensing operation, the resources required by the UE 115 for the dual-station sensing operation, the location of the UE 115, the mobility of the UE 115, the location of the network entity 470, the mobility of the network entity 470, the distance between the UE 115 and the network entity 470, the operation mode at the network entity 470, the pre-sensing operation, the pre-sensing measurement report, or a combination thereof. In some implementations, the network 506 may determine the cost as a fixed sensing fee for the dual-station sensing operation performed by the UE 115. The sensing charging subscription information indicates functionality, rules, profiles, or a combination thereof.

[0123] In some implementations, the network 506 can determine a first charge for the network entity 470 as a receiving (Rx) device, a second charge for the UE 115 as a transmitting (Tx) device, or a combination thereof. For example, the network 506 can determine that the first charge or the second charge is based on pre-sensing operations, Tx parameters, resources, quality of service, or a combination thereof.

[0124] At 530, the network entity 470 sends a handover request 532 to the network 506. The handover request may be associated with assisting the UE 115 in performing a dual-station sensing operation. Based on the handover request, the network 506 may transmit a pre-sensing message report or configuration information (e.g., network entity information) to a base station (e.g., 105), transmit a pre-sensing message report or configuration information (e.g., network entity information) to another network entity, or perform a handover operation based on the predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof. The transmitted sensing information may indicate completion of the dual-station sensing operation, received sensing information, a network entity, time domain parameters, frequency domain parameters, beam direction, beam bandwidth, transmit power, quality of service, or a combination thereof.

[0125] Note that although Figure 5 The operations of are described in a particular order, but this order is not intended to be limiting. Figure 5 One or more operations described may differ from those described in the reference Figure 5The instructions are executed in the order shown and described.

[0126] As reference Figure 4 and Figure 5 As described, the present disclosure provides techniques for supporting sensing billing subscriptions. The described techniques provide processes, information, and signaling for UE 115 to perform sensing operations (such as dual-station sensing operations) in accordance with sensing subscriptions. The wireless network 100 can advantageously manage sensing-based subscription billing for sensing operations or services (such as 5G or NR sensing services) associated with UE 115. Additionally, the techniques described herein enable management or control of sensing operations performed by UE 115 in accordance with sensing subscriptions. By managing and controlling sensing operations performed by UE 115, the techniques described herein achieve reduced overhead, efficient spectrum usage, improved spectrum reuse, reduced device hardware, improved hardware reuse, or a combination thereof.

[0127] Figure 6 is a flow chart illustrating an example process 600 for supporting sensing charging subscriptions according to one or more aspects. The operations of process 600 may be performed by a UE (such as the one described above with reference to FIG. Figures 1 to 5 UE 115 described or referenced Figure 7 For example, the example operations (also referred to as "blocks") of process 600 may enable UE 115 to support sensing charging subscriptions.

[0128] In block 602, the UE sends a request to a network entity to participate in a dual-station sensing operation. For example, the network entity may include or correspond to the network entity 470. The request may include or correspond to Figure 5 The dual-station sensing request sent by UE 115 is described at 514.

[0129] In block 604, the UE performs a dual-station sensing operation with a network entity. The dual-station sensing operation may include or correspond to the following: Figure 5 The sensing waveform sent by UE 115 is described at 526.

[0130] In block 606, the UE transmits transmit sensing information associated with the dual-station sensing operation. For example, the transmit sensing information may include or correspond to information 406, measurement information 410, information 464, or information 484. As another example, the transmit sensing information may include or correspond to Figure 5 530 of the present invention is a transmission sensing information sent by UE 115. The transmission sensing information may be associated with sensing charging subscription information. The sensing charging subscription information may include or correspond to information 406, sensing charging subscription information 409, information 464, sensing charging subscription information 466, or information 484. The sensing charging subscription information may include or indicate functionality, rules, profiles, or a combination thereof.

[0131] In some implementations, the UE receives received sensing information associated with the dual-station sensing operation from the network entity. The received sensing information may include or correspond to information 406, measurement information 410, information 484, or information 464. Additionally or alternatively, the received sensing information may include or correspond to Figure 5 The received sensing information at 528 is sent by the network entity 470. The sent sensing information may indicate completion of the dual-station sensing operation, received sensing information, a network entity, time domain parameters, frequency domain parameters, beam direction, beam bandwidth, transmit power, quality of service, or a combination thereof.

[0132] In some implementations, the UE sends a request to the network to perform a dual-station sensing operation. The network may include or correspond to the base station 105, the core network 130, or the network 506. The request to perform a dual-station sensing operation may include or correspond to Figure 5 In addition or alternatively, the UE may receive network entity information from the network. For example, the network entity information may include or correspond to Figure 5 At 516 , network entity information is received by UE 115. The network entity information may indicate a network entity selected from one or more network entities available for participating in the dual-station sensing operation. Additionally or alternatively, the network entity information indicates sensing resources, sensing transmission parameters, sensing charging charges, or a combination thereof. The network entity may include a base station, a roadside unit, or another UE; the network entity may be a mobile device or a stationary device; the network may include a core network, or a combination thereof.

[0133] In some implementations, the UE performs a pre-sensing operation with the network entity before performing the dual-station sensing operation. For example, the pre-sensing operation may include or correspond to Figure 5 The pre-sensing waveform sent by the UE 115 at 522 of FIG. The pre-sensing operation is associated with a coarse sensing estimate or a fine sensing estimate or a combination thereof performed via an uplink (UL) channel. Additionally or alternatively, the UE may receive a pre-sensing measurement report from the network entity. For example, the pre-sensing measurement report may include or correspond to Figure 5 The pre-sensing measurement report sent by the network entity 470 at 524. In some implementations, the UE can determine whether to perform dual-station sensing operation based on the pre-sensing measurement report, the UE's quality of service, sensing charging charges associated with the network entity, or a combination thereof.

[0134] In some implementations, the UE receives a request from the network for capability information associated with the UE's availability to participate in one or dual-station sensing operations. The request may include or correspond to Figure 5The capability request sent by the network 506 at 510. In response to the request, the UE may send UE capability information to the network. The UE capability information may include or correspond to information 406, capability information 408, information 484, information 464, or capability information 465. As another example, the UE capability information may include or correspond to Figure 5 At 512 , a capability response is received by the network 506 .

[0135] Figure 7 is a block diagram of an example UE 700 supporting sensing charging subscription according to one or more aspects. The UE 700 may be configured to perform operations including referring to Figure 6 In some implementations, the UE 700 includes a block diagram of the process described. Figures 1 to 5 1 and 115. For example, the UE 700 includes a controller 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 700 that provide the features and functionality of the UE 700. The UE 700 transmits and receives signals via wireless radio components 701a-r and antennas 252a-r under the control of the controller 280. The wireless radio components 701a-r include various components and hardware, such as Figure 2 As illustrated for UE 115 , modulators and demodulators 254 a - r , a MIMO detector 256 , a receive processor 258 , a transmit processor 264 , and a TX MIMO processor 266 are included.

[0136] As shown, the memory 282 may include dual-station sensing logic 702 and communication logic 703. The dual-station sensing logic 702 may be configured to enable one or more dual-station sensing operations. The communication logic 703 may be configured to enable communication between the UE 700 and one or more other devices. The UE 700 may receive information from one or more network entities (such as, Figures 1 to 4 Base station 105, Figures 4 and 5 The network entity 470 or Figure 10 The exemplary network entity) receives a signal or sends a signal to the one or more network entities.

[0137] Figure 8 is a flow chart illustrating an example process 800 for supporting sensing billing subscriptions according to one or more aspects. The operations of process 800 may be performed by a network entity (such as the one referenced above). Figures 1 to 5 UE 115 described above with reference to Figures 1 to 5 The network entity 470 described above, or Figures 1 to 4 The base station 105 described above Figure 7 UE 700 described above, or Figure 10For example, the example operations of process 800 may enable a network entity to support sensing charging subscriptions.

[0138] At block 802, a network entity receives a request from a UE to assist the UE in performing dual-station sensing operations. For example, the request may include or correspond to: Figure 5 The dual-station sensing request received by the network entity 470 is depicted at 514 .

[0139] In some implementations, the network entity sends a response indicating the availability of participating in the dual-station sensing operation in response to the request. For example, the response may include or correspond to Figure 5 At 520 , the network entity 470 sends a network entity reply.

[0140] At block 804, the network entity performs a dual-station sensing operation with the UE. The dual-station sensing operation may include or correspond to the following: Figure 5 526 depicts a sensing waveform transmitted by the UE 115 and received by the network entity 470 .

[0141] At block 806, the network entity sends received sensing information associated with the dual-station sensing operation. For example, the received sensing information may include or correspond to information 406, measurement information 410, information 464, or information 484. As another example, the received sensing information may include or correspond to Figure 5 The received sensing information sent by the network entity 470 at 528 may be associated with the sensing billing subscription information. The sensing billing subscription information may include or correspond to the information 406, the sensing billing subscription information 409, the information 464, the sensing billing subscription information 466, or the information 484.

[0142] In some implementations, the network entity receives a request from the network for capability information associated with the availability of the network entity to participate in one or dual-station sensing operations. The network may include or correspond to the base station 105, the core network 130, or the network 506. The request may include or correspond to Figure 5 510 of the capability request sent by the network 506. Additionally or alternatively, the network entity may send capability information to the network. The capability information may include or correspond to information 406, capability information 408, information 484, information 464, or capability information 465. As another example, the capability information may include or correspond to Figure 5 At 512 , a capability response is received by the network 506 .

[0143] 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 Figure 5The pre-sensing waveform sent by UE 115 at 522 of FIG. The pre-sensing operation may be associated with a coarse sensing estimate and a fine sensing estimate, and the pre-sensing operation is performed using the UL channel of the UE. Additionally or alternatively, the network entity may send a pre-sensing measurement report to the network or the UE based on the pre-sensing operation. The pre-sensing measurement report may include or correspond to Figure 5 At 524 , the pre-sensing measurement report, information 406 , measurement information 410 , information 484 , or information 464 is sent by the network entity 470 .

[0144] In some implementations, the network entity initiates a handover operation associated with the dual-station sensing operation performed by the network-assisted UE. For example, to initiate the handover operation, the network entity 470 Figure 5 The transfer request is sent at 532.

[0145] Figure 9 is a flow chart illustrating an example process 900 for supporting sensing billing subscriptions according to one or more aspects. The operations of process 900 may be performed by a network (such as the one referenced above). Figures 1 to 5 The network entity 470 described above refers to Figures 1 to 4 The base station 105 or core network 130 described above Figure 5 Network 506 described above, or reference Figure 10 For example, the example operations of process 900 may enable a network entity to support sensing charging subscriptions.

[0146] At block 902, the network sends a request to a network entity for capability information associated with the network entity's availability to participate in one or more dual-station sensing operations. For example, the network entity may include or correspond to UE 115 or network entity 470. The request for capability information may include or correspond to Figure 5 The capability information may include or correspond to information 406, capability information 408, information 464, capability information 465, or information 484. Additionally, the capability information may include or correspond to Figure 5 At 512 , the network entity 470 sends a capability response.

[0147] At block 904, the network receives a request from a UE to assist the UE in performing dual-station sensing operations. For example, the UE may include or correspond to UE 115. The assistance request may include or correspond to Figure 5 At 514 , a bistatic sensing request is received by the network 506 .

[0148] At block 906, the network sends network entity information to the UE. For example, the network entity information may include or correspond to Figure 5The network entity information is sent by the network 506 at 516. The network entity information may indicate a network entity selected from one or more network entities available for participating in the dual-station sensing operation. In some implementations, the network entity information indicates sensing resources, sensing transmission parameters, sensing charging charges, or a combination thereof. The network entity information is sent to the UE, the network entity, or a combination thereof.

[0149] In some implementations, the network selects a network entity from among one or more network entities that can be used to participate in the dual-station sensing operation. The network entity can be selected from among 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, usage charges of the network entity, sensing billing subscription information associated with the UE, quality of service requested by the UE, available quality of service associated with the network entity, or a combination thereof.

[0150] In some implementations, the network receives transmit sensing information based on a dual-station sensing operation from the UE. For example, the transmit sensing information may include or correspond to information 406, measurement information 410, information 464, or information 484. As another example, the transmit sensing information may include or correspond to Figure 5 530 of the UE 115. Additionally or alternatively, the network may receive received sensing information based on the dual-station sensing operation from the network entity. For example, the received sensing information may include or correspond to information 406, measurement information 410, information 464, or information 484. As another example, the received sensing information may include or correspond to Figure 5 4 or 5. In some implementations, the network determines a fee for the dual-station sensing operation for the UE. For example, the fee may include or correspond to sensing charging 467. The fee may be determined based on sensing charging subscription information associated with the UE (e.g., 409 or 466) and based on sending sensing information, receiving sensing information, or a combination thereof. Additionally or alternatively, the fee for the dual-station sensing operation may be determined based on sending sensing information, receiving sensing information, resources available at the network entity for the dual-station sensing operation, resources required by the UE for the dual-station sensing operation, the location of the UE, the mobility of the UE, the location of the network entity, the mobility of the network entity, the distance between the UE and the network entity, the operation mode at the network entity, pre-sensing operations, pre-sensing measurement reports, or a combination thereof. In some implementations, the network determines a fixed sensing fee for the UE for the dual-station sensing operation performed by the UE.

[0151] In some implementations, the network receives a pre-sensing measurement report from a network entity. The pre-sensing measurement report may include or correspond to Figure 5The pre-sensing measurement report, information 406, measurement information 410, information 484, or information 464 sent by the network entity 470 at 524. 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 Figure 5 522 of FIG. The pre-sensing waveform sent by UE 115 is shown. Additionally or alternatively, it should be noted that the network entity information may indicate a network entity available for pre-sensing operations prior to the dual-station sensing operation. In some implementations, the network determines a first fee for the network entity as a 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 the pre-sensing operation, Tx parameters, resources, quality of service, or a combination thereof.

[0152] In some implementations, the network receives a request for a handover operation from a network entity. Figure 5 At 532, the network entity 470 sends a handover request to the network 506. Based on the request for the handover operation, the network may transmit a pre-sensing message report or configuration information to a base station, transmit a pre-sensing message report or configuration information to another network entity, or perform a handover operation based on the predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof.

[0153] Figure 10 is a block diagram of an example network entity 1000 that supports sensing billing subscriptions according to one or more aspects. The network entity 1000 may be configured to perform operations including referring to Figure 8 and Figure 9 In some implementations, the network entity 1000 includes a reference to Figures 1 to 4 Base station 105, Figures 1 to 5 Network entity 470, Figures 1 to 4 Core network 130, Figure 5 The structure, hardware, and components shown and described for the network 506 of FIG. For example, the network entity 1000 may include a controller 240 that operates to execute logic or computer instructions stored in a memory 242 and controls components of the network entity 1000 that provide features and functionality of the network entity 1000. The network entity 1000 transmits and receives signals via wireless radio components 1001a-t and antennas 234a-t under the control of the controller 240. The wireless radio components 1001a-t include the following: Figure 2 Various components and hardware are illustrated for base station 105 in FIG, including modulators and demodulators 232a-t, transmit processor 220, TX MIMO processor 230, MIMO detector 236, and receive processor 238.

[0154] As shown, memory 242 may include capability information 1002, dual-station sensing logic 1003, and communication logic 1004. Capability information 1002 may include or correspond to information 406, capability information 408, information 484, information 464, or capability information 465. Dual-station sensing logic 1003 may be configured to enable one or more dual-station sensing operations. Communication logic 1004 may be configured to enable communication between network entity 1000 and one or more other devices. Network entity 1000 may receive information from one or more UEs (e.g., Figures 1 to 5 UE 115, Figures 4 and 5 network entity 470 or Figure 6 UE 700) receives a signal or sends a signal to the one or more UEs.

[0155] Please note that reference Figure 6 、 Figure 8 ,or Figure 9 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) described with reference to another figure. Figure 6 One or more boxes (or operations) of Figure 8 As another example, with Figure 6 One or more boxes associated with Figure 9 As another example, one or more box combinations associated with Figure 8 One or more boxes associated with Figure 9 As another example, one or more box combinations associated with Figure 6 、 Figure 8 or Figure 9 One or more boxes associated with Figures 1 to 5 One or more associated boxes (or operations) are combined. Additionally or alternatively, the above reference Figures 1 to 5 One or more of the operations described may be combined with reference to Figure 7 or Figure 10 Describes a combination of one or more operations.

[0156] In one or more aspects, techniques for supporting the reception of sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for supporting the reception of sensing information may include sending a request to a network entity to participate in a dual-station sensing operation. These techniques may also include performing the dual-station sensing operation with the network entity. These techniques may also include sending sensing information associated with the dual-station sensing operation. The sent sensing information may be associated with sensing billing subscription information. In some examples, the techniques of 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 component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the 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, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, a wireless communication device may include an interface (eg, a wireless communication interface) including a transmitter, a receiver, or a combination thereof. Additionally or alternatively, a wireless communication device may include one or more components configured to perform the operations described herein.

[0157] In a second aspect, in combination with the first aspect, the techniques further include receiving, from a network entity, received sensing information associated with the bistatic sensing operation.

[0158] In a third aspect, in combination with the second aspect, sending sensing information indicates completion of a dual-station sensing operation, receiving sensing information, a network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmit power, a quality of service, or a combination thereof.

[0159] In a fourth aspect, in combination with one or more of the first to third aspects, the sensing charging subscription information indicates functionality, rules, profiles, or a combination thereof.

[0160] In a fifth aspect, in combination with one or more of the first to fourth aspects, the techniques further include sending a request to a network to perform a bistatic sensing operation.

[0161] In a sixth aspect, in combination with one or more of the first to fifth aspects, the techniques further include receiving network entity information from a network. The network entity information of the sixth aspect may indicate a network entity selected from one or more network entities available for participating in the dual-station sensing operation.

[0162] In a seventh aspect, in combination with one or more of the first to sixth aspects, the network entity information indicates sensing resources, sensing transmission parameters, sensing charging charges, or a combination thereof.

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

[0164] In a ninth aspect, in combination with one or more of the first to eighth aspects, the network entity is a mobile device or a stationary device.

[0165] In a tenth aspect, in combination with one or more of the first to ninth aspects, the network includes a core network.

[0166] In an eleventh aspect, in combination with one or more of the first to tenth aspects, the techniques further include performing a pre-sensing operation with a network entity before performing the dual-station sensing operation.

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

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

[0169] In a fourteenth aspect, in combination with the thirteenth aspect, the techniques further include determining whether to perform dual-station sensing operations based on a pre-sensing measurement report, quality of service of the UE, sensing charging charges associated with a network entity, or a combination thereof.

[0170] In a fifteenth aspect, in combination with one or more of the first to fourteenth aspects, the techniques further include receiving a request from the network for capability information associated with availability of the UE to participate in one or dual-station sensing operations.

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

[0172] In one or more aspects, techniques for supporting receiving sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or devices described elsewhere herein. In a seventeenth aspect, techniques for supporting receiving sensing information may include receiving a request from a UE to assist the UE in performing a dual-station sensing operation. These techniques may also include performing the dual-station sensing operation with the UE. These techniques may also include sending received sensing information associated with the dual-station 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 in the seventeenth aspect may be implemented in a wireless communication device (such as a 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 component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the 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, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, a wireless communication device may include an interface (eg, a wireless communication interface) including a transmitter, a receiver, or a combination thereof. Additionally or alternatively, a wireless communication device may include one or more components configured to perform the operations described herein.

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

[0174] In a nineteenth aspect, in combination with one or more of the seventeenth or eighteenth aspects, the techniques further include sending capability information to a network.

[0175] In a twentieth aspect, in combination with one or more of aspects seventeen to nineteen, the techniques further comprise sending a response in response to the request indicating availability to engage in bistatic sensing operations.

[0176] In a twenty-first aspect, in combination with one or more of aspects seventeen to twentieth, the techniques further include performing pre-sensing operations with the UE.

[0177] In a twenty-second aspect, in combination with the twenty-first aspect, a pre-sensing operation is associated with a coarse sensing estimation and a fine sensing estimation, and the pre-sensing operation is performed using a UL channel of the UE.

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

[0179] In a twenty-fourth aspect, in combination with one or more of aspects seventeen to twenty-third, the techniques further include handover operations associated with network-initiated and assisted UE dual-station sensing operations.

[0180] In one or more aspects, techniques for supporting receiving sensing information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a twenty-fifth aspect, techniques for supporting receiving sensing information may include sending a request to a network entity for capability information associated with the network entity's availability to participate in one or dual-station sensing operations. These techniques may also include receiving a request from a UE to assist the UE in performing dual-station sensing operations. These techniques may also include sending network entity information to the UE. The network entity information indicates a network entity selected from one or more network entities available to participate in the dual-station sensing operations. In some examples, the techniques of 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 a 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 component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the 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, which, 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) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.

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

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

[0183] In a twenty-eighth aspect, in combination with one or more of aspects twenty-fifth to twenty-seventh, the techniques further include receiving, from a UE, transmitted sensing information based on a dual-station sensing operation.

[0184] In a twenty-ninth aspect, in combination with one or more of aspects twenty-fifth to twenty-eighth, the techniques further comprise receiving sensing information based on a bistatic sensing operation from a network entity.

[0185] In a thirtieth aspect, in combination with one or more of aspects twenty-fifth to twenty-ninth, the techniques further include determining, for a UE, a cost for dual-station sensing operations.

[0186] 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 based on sending sensing information, receiving sensing information, or a combination thereof.

[0187] In a thirty-second aspect, in combination with one or more of aspects twenty-fifth to thirty-first, the network entity information indicates sensing resources, sensing transmission parameters, sensing billing charges, or a combination thereof.

[0188] In a thirty-third aspect, in combination with one or more of aspects twenty-fifth to thirty-second, network entity information is sent to a UE, a network entity, or a combination thereof.

[0189] In a thirty-fourth aspect, in combination with one or more of aspects twenty-fifth to thirty-third, the techniques further comprise receiving a pre-sensing measurement report from a network entity.

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

[0191] 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 a pre-sensing operation prior to the dual-station sensing operation.

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

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

[0194] In a thirty-ninth aspect, in combination with one or more of aspects twenty-fifth to thirty-eighth, the techniques further include receiving transmitted sensing information from a UE, received sensing information from a network entity, or a combination thereof based on a dual-station sensing operation.

[0195] In the 40th aspect, in combination with the 39th aspect, these technologies also include determining the cost for the dual-station sensing operation for the UE based on sending sensing information, receiving sensing information, resources available for dual-station sensing operations at the network entity, resources required by the UE for the dual-station sensing operation, the UE's location, the UE's mobility, the location of the network entity, the mobility of the network entity, the distance between the UE and the network entity, the operation mode at the network entity, pre-sensing operations, pre-sensing measurement reports, or a combination thereof.

[0196] In a forty-first aspect, in combination with one or more of aspects twenty-fifth to thirty-eighth, the techniques further include determining, for a UE, a fixed sensing fee for dual-station sensing operations performed by the UE.

[0197] In a 42nd aspect, in combination with one or more of aspects 25-41, the techniques further include receiving a request for a handover operation from a network entity.

[0198] In a 43rd aspect, in combination with the 42nd aspect, the techniques further comprise performing a handover operation based on a request for the handover operation, based on a predicted location or mobility of one or more base stations, one or more UEs, or a combination thereof.

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

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

[0201] It will be understood by those skilled in the art that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0202] This article is about Figures 1 to 10The components, functional blocks and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. In addition, the features discussed herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0203] It will be further understood by those skilled in the art that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, frames, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed for the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. It will also be readily appreciated that the order or combination of components, methods, or interactions described herein are merely examples, and that the components, methods, or interactions of various aspects of the present disclosure can be combined or performed in a manner other than that illustrated and described herein.

[0204] The various illustrative logical components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0205] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general-purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuits specific to a given function.

[0206] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by, or for controlling the operation of, data processing apparatus.

[0207] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that can be implemented to transfer a computer program from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and blue-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically with lasers. The above combination should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0208] Various modifications to the specific implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and novel features disclosed herein.

[0209] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page and may not reflect the correct orientation of any device as implemented.

[0210] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be omitted from that combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0211] Similarly, although operations are depicted in a particular order in the figures, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of flow charts. However, other operations not depicted may be combined in the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously, or between any illustrated operations. In certain environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementations described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in different orders and still achieve the desired result.

[0212] As used herein, including in the claims, the term "or" used in a list of two or more items means that any one of the listed items can be employed alone, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing component A, B, or C, the composition can include A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined. Furthermore, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one of" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as largely, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed embodiment, the term "substantially" may be replaced with "within [percentage] of" that specified, where percentages include 0.1%, 1%, 5%, or 10%.

[0213] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: sending a request to a network entity to participate in a dual-station sensing operation; performing the dual-station sensing operation with the network entity; as well as Sending sensing information associated with the dual-station sensing operation, wherein the sending sensing information is associated with sensing billing subscription information.

2. The method according to claim 1, further comprising: receiving received sensing information associated with the bistatic sensing operation from the network entity, and wherein the transmitted sensing information indicates the completion of the dual-station sensing operation, the received sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmit power, a quality of service, or a combination thereof, and The sensing charging subscription information indicates functionality, rules, profiles or a combination thereof.

3. The method according to claim 1, further comprising: sending a request to the network to perform the bistatic sensing operation; as well as Network entity information is received from the network, the network entity information indicating the network entity selected from one or more network entities available for participating in the dual-station sensing operation.

4. The method according to claim 3, wherein: The network entity information indicates sensing resources, sensing transmission parameters, sensing billing charges, 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 of them.

5. The method according to claim 1, further comprising: performing a pre-sensing operation with the network entity before performing the dual-station sensing operation, and The pre-sensing operation is associated with a coarse sensing estimation or a fine sensing estimation or a combination thereof performed via an uplink (UL) channel.

6. The method according to claim 5, further comprising: receiving, from the network entity, a pre-sensing measurement report from the network entity; as well as Whether to perform the dual-station sensing operation is determined based on the pre-sensing measurement report, quality of service of the UE, sensing charging charges associated with the network entity, or a combination thereof.

7. The method according to claim 1, further comprising: receiving a request from a network for capability information associated with availability of the UE to participate in one or dual-station sensing operations; as well as In response to the request, UE capability information is sent to the network.

8. A user equipment (UE), comprising: a sensing device configured for use in a bistatic sensing operation; a memory storing processor-readable code; and at least one processor coupled to the memory, the at least one processor configured to execute the processor-readable code to cause the at least one processor to: sending a request to a network entity to participate in the dual-station sensing operation; performing the dual-station sensing operation with the network entity; as well as Sending sensing information associated with the dual-station sensing operation, wherein the sending sensing information is associated with sensing billing subscription information.

9. The UE of claim 8, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: receiving received sensing information associated with the bistatic sensing operation from the network entity, and wherein the sensing billing subscription information indicates functionality, rules, profiles, or a combination thereof, and The transmitted sensing information indicates the completion of the dual-station sensing operation, the received sensing information, the network entity, a time domain parameter, a frequency domain parameter, a beam direction, a beam bandwidth, a transmit power, a quality of service, or a combination thereof.

10. The UE of claim 8, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: sending a request to the network to perform the bistatic sensing operation; and Network entity information is received from the network, the network entity information indicating the network entity selected from one or more network entities available for participating in the dual-station sensing operation.

11. The UE according to claim 10, wherein: The network entity information indicates sensing resources, sensing transmission parameters, sensing billing charges, 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 of them.

12. The UE according to claim 8, wherein: the at least one processor being configured to execute the processor-readable code to cause the at least one processor to perform a pre-sensing operation with the network entity before performing the dual-station sensing operation; and The pre-sensing operation is associated with a coarse sensing estimation or a fine sensing estimation or a combination thereof performed via an uplink (UL) channel.

13. The UE of claim 12, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: receiving, from the network entity, a pre-sensing measurement report from the network entity; and Whether to perform the dual-station sensing operation is determined based on the pre-sensing measurement report, quality of service of the UE, sensing charging charges associated with the network entity, or a combination thereof.

14. The UE of claim 8, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: receiving a request from the network for capability information associated with availability of the UE to participate in one or dual-station sensing operations; and In response to the request, UE capability information is sent to the network.

15. A method of wireless communication performed by a network entity, the method comprising: receiving a request from a user equipment (UE) to assist the UE in performing a dual-station sensing operation; performing the dual-station sensing operation with the UE; as well as Received sensing information associated with the bistatic sensing operation is transmitted.

16. The method according to claim 15, further comprising: receiving a request from the network for capability information associated with availability of the network entity to participate in one or dual-station sensing operations; as well as Capability information is sent to the network.

17. The method according to claim 15, further comprising: In response to the request, a response is sent indicating availability to participate in the bistatic sensing operation.

18. The method according to claim 15, further comprising: performing a pre-sensing operation with the UE, and The pre-sensing operation is associated with a coarse sensing estimation and a fine sensing estimation, and the pre-sensing operation is performed using a UL channel of the UE.

19. The method according to claim 18, further comprising: A pre-sensing measurement report is sent to a network or the UE based on the pre-sensing operation.

20. The method of claim 15, further comprising: The network initiates a handover operation associated with assisting the UE in performing the dual-station sensing operation.

21. A method of wireless communication performed by a network, the method comprising: sending a request to a network entity for capability information associated with availability of the network entity to participate in one or more dual-station sensing operations; receiving a request from a user equipment (UE) to assist the UE in performing a dual-station sensing operation; as well as Network entity information is sent to the UE, where the network entity information indicates the network entity selected from one or more network entities that can be used to participate in the dual-station sensing operation.

22. The method according to claim 21, further comprising: The network entity of the one or more network entities available to participate in the bistatic sensing operation is selected.

23. The method of claim 22, wherein 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, usage charges of the network entity, sensing charging subscription information associated with the UE, quality of service requested by the UE, available quality of service associated with the network entity, or a combination thereof.

24. The method of claim 21, further comprising: receiving, from the UE, transmitted sensing information based on the dual-station sensing operation, receiving, from the network entity, received sensing information based on the dual-station sensing operation, or a combination thereof; and A charge for the dual-station sensing operation is determined for the UE, the charge being determined based on sensing charging subscription information associated with the UE and based on the transmitted sensing information, the received sensing information, or a combination thereof.

25. The method of claim 21, wherein: The network entity information indicates sensing resources, sensing transmission parameters, sensing billing charges, or a combination thereof; and The network entity information is sent to the UE, the network entity, or a combination thereof.

26. The method of claim 21, further comprising: receiving a pre-sensing measurement report from the network entity, the pre-sensing measurement report being based on a pre-sensing operation between the UE and the network entity, and The network entity information indicates that the network entity is capable of performing the pre-sensing operation before the dual-station sensing operation.

27. The method of claim 21, further comprising: determining a first charge for the network entity as a receiving (Rx) device, a second charge for the UE as a transmitting (Tx) device, or a combination thereof, and The first fee or the second fee is determined based on a pre-sensing operation, Tx parameters, resources, quality of service, or a combination thereof.

28. The method of claim 21, further comprising: receiving, based on the dual-station sensing operation, transmitted sensing information from the UE, received sensing information from the network entity, or a combination thereof; as well as A cost for the dual-station sensing operation is determined for the UE based on the transmitted sensing information, the received sensing information, resources at the network entity that can be used for the dual-station sensing operation, resources required by the UE for the dual-station sensing operation, a location of the UE, mobility of the UE, a location of the network entity, mobility of the network entity, a distance between the UE and the network entity, an operation mode at the network entity, a pre-sensing operation, a pre-sensing measurement report, or a combination thereof.

29. The method of claim 21, further comprising: A fixed sensing fee is determined for the UE for the dual-station sensing operation performed by the UE.

30. The method of claim 21, further comprising: receiving a request for a handover operation from the network entity; as well as 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; Transmitting a pre-sensing message report or configuration information to a base station; or Transmitting a pre-sensing message report or configuration information to another network entity.

Images