Resource allocation for sensing services

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a first request associated with establishing a sensing service to a network node, the first request including information indicating sensing session parameters of one or more requests associated with the sensing service. The UE may receive, from the network node and based at least in part on the first request, a resource allocation for a virtual communication session, the resource allocation indicating one or more resources for the sensing service. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek patent application No. 20220100719, entitled “RESOURCE ALLOCATION FOR SENSING SERVICES”, filed on September 1, 2022 and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated into this patent application by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for resource allocation for sensing services. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of performing wireless communications by a user equipment (UE). The method may include sending a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The method may include receiving a resource allocation for a virtual communication session from the network node and based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The method may include sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0009] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a first request associated with establishing a sensing service to a network node. The one or more processors may be configured to receive a resource allocation for a virtual communication session from the network node and based at least in part on the first request.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first request associated with establishing a sensing service with a UE. The one or more processors may be configured to send a resource allocation for a virtual communication session with the UE based at least in part on the first request.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send a first request associated with establishing a sensing service to a network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a resource allocation for a virtual communication session from the network node and based at least in part on the first request.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive a first request associated with establishing a sensing service with a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a resource allocation for a virtual communication session with the UE based at least in part on the first request.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The apparatus may include means for receiving, from the network node and based at least in part on the first request, a resource allocation for a virtual communication session, the resource allocation indicating one or more resources for the sensing service.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The apparatus may include means for sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily 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 in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a Joint Communication and Sensing (JCS) system according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example associated with resource allocation for a sensing service according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0026] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0027] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0031] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0033] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0036] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0038] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0039] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0042] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0044] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service; and receive a resource allocation for a virtual communication session from the network node and based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service; and send a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Described differently.

[0048] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0051] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0053] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 9 ) any aspects of any of the methods described herein.

[0054] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 9 ) any aspects of any of the methods described herein.

[0055] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the may perform one or more techniques associated with resource allocation for sensing services, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0056] In some aspects, the UE includes a component for sending a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service; and / or a component for receiving a resource allocation for a virtual communication session from the network node and based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service. The components for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0057] In some aspects, the network node includes a component for receiving a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service; and / or a component for including sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0058] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0059] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Described differently.

[0060] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0061] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0062] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0063] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0064] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0065] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, 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 (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), 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.

[0066] Each 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 MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0067] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

[0070] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function 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 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0071] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Described differently.

[0072] Figure 4 4 is a diagram illustrating an example 400 of a joint communication and sensing (JCS) system according to the present disclosure. Figure 4 As shown, a UE (e.g., UE 405) may communicate with one or more other UEs (e.g., UE 410) via a sidelink and / or communicate with one or more network nodes (e.g., network node 415) via a downlink and / or uplink.

[0073] UEs such as UE 405 may use radio frequency (RF) sensing (e.g., radar sensing) for environmental sensing (e.g., to detect objects). For example, in an automotive deployment, a UE associated with a vehicle may transmit one or more sensing transmissions (also referred to as radar transmissions) and measure one or more reflections (e.g., reflections of the sensing transmissions off an object) to determine the distance of an object, the speed of an object, the direction of an object, or the acceleration of an object, etc. Reserving dedicated RF resources for radar sensing may result in inefficient use of RF resources. For example, in a situation where a small number of UEs are performing RF sensing, some RF resources may not be used while communication resources are congested with transmissions from many UEs.

[0074] Thus, some communication systems may integrate wireless communication with RF sensing using a single pool of resources for both data transmission and sensing transmission. In this case, rather than having a first set of resources dedicated to sensing and a second set of resources dedicated to communication, a single set of resources is allocated for both communication and sensing. For example, some techniques may use 3GPP (e.g., NR) waveforms for both communication and sensing, thereby enabling a 3GPP device (e.g., UE, base station, roadside unit (RSU), CU, DU, RU, network node, or network entity, etc.) to use a receive processor (such as Figure 2 A configuration in which both communication and sensing are enabled for a single set of resources may be referred to as a "joint communication and sensing" or "joint communication and radar" ("JCR") deployment.

[0075] like Figure 4 As shown, a portion of a resource pool is shown, wherein data transmission and sensing transmission occur on orthogonal resources within the resource pool. As used herein, these transmissions may originate from the same UE (e.g., UE 405), from different UEs, or a combination thereof. In some cases, the transmission may originate from a network node (e.g., network node 415) for a network node-based sensing service. As shown, sensing transmissions may typically have a relatively large bandwidth utilization (e.g., relative to data transmissions), occupy many or all available subchannels and / or resources, and typically span more than one time slot.

[0076] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Described differently.

[0077] The core network architecture can support communication-based sessions, but currently does not support non-communication-based sessions (e.g., sensing sessions). Although JCS operations can be supported by network nodes, the core network does not support coordination or management of sensing and communication sessions. Although network nodes can support different sensing operations based on the specific needs of sensing sessions, there is currently no framework for controlling resources in a coordinated manner that takes into account the different communication and sensing requirements between the two types of transmissions. This may result in some sensing and / or communication sessions being allocated insufficient resources (e.g., resources without sufficient bandwidth and / or latency, etc.), while other sensing and / or communication sessions are allocated too many resources. In addition, sensing and / or communication sessions may be established using parameters (e.g., key performance indicators) that are less efficient for the corresponding application. In the absence of a way to coordinate different service types with different priorities, different service types may not be properly prioritized. Lack of coordination in resource allocation between different communication and non-communication service types may also result in lower quality or discarded communication sessions and / or sensing sessions.

[0078] Some of the techniques and devices described herein implement resource allocation for sensing services (e.g., in the time domain, frequency domain, and spatial domain). For example, a network node may receive a request associated with establishing a sensing service with a UE, and send a resource allocation for a virtual communication session with the UE to the UE, wherein the resource allocation is used for the sensing service. In some aspects, the network node is able to map the requested sensing session parameters to the communication session parameters to determine the resource allocation. Therefore, the network node can manage the virtual communication session in a manner similar to that of other communication sessions. This also enables the sensing service to be associated with a QoS parameter that can be compared to the quality of service (QoS) parameter of the communication service, which can facilitate resource allocation for different types of services. In this way, the network can more efficiently allocate resources between communication services and non-communication services, and in a manner that appropriately prioritizes communication services and non-communication services relative to each other. Relative to a network using a framework that lacks the ability to manage non-communication sessions as virtual communication sessions, this can result in higher quality communication and non-communication sessions, as described herein.

[0079] Figure 5 is a diagram illustrating an example 500 associated with resource allocation for a sensing service according to the present disclosure. Figure 5 As shown, a network node (e.g., network node 110) may communicate with a UE (e.g., UE 120). The network node may include one or more CUs, one or more DUs, one or more RUs, etc. In some aspects, the UE and the network node may be part of a wireless network (e.g., wireless network 100). The UE and the network node may be in a Figure 5 The operations shown are performed after a wireless connection has been established.

[0080] As shown by reference numeral 505, the UE may determine information indicating one or more sensing session parameters of the requested sensing service. The sensing service may be, for example, a single-station sensing service, a dual-station sensing service, or a similar sensing service. In some aspects, the information indicating the requested sensing session parameters may include communication session parameters (e.g., QoS parameters). For example, in order to treat the sensing session as a virtual communication session, the UE and / or the core network node may use the communication session parameters (which may be based on the sensing session parameters) for resource allocation, which may be more easily coordinated with other communication sessions. For example, the UE may determine information indicating one or more requested sensing session parameters (e.g., communication sensing parameters) based at least in part on information mapping at least one of the requested sensing session parameters to one or more communication session parameters.

[0081] For example, the UE may be configured with information that enables the UE to map a sensing priority parameter and / or a sensing type parameter to a communication power parameter (e.g., a relatively high value of a priority sensing parameter may translate to a relatively high value of a transmit power communication parameter), and a range resolution sensing parameter may be mapped to a bandwidth communication parameter (e.g., a relatively low value of a range resolution sensing parameter may translate to a relatively low value of a bandwidth communication parameter), etc. In some aspects, the mapping of sensing session parameters to communication session parameters may be based at least in part on criteria that define the mapping.

[0082] In some aspects, the sensing session parameters may include a priority parameter (e.g., an absolute or relative priority value), a sensing type parameter (e.g., radar, ranging, and / or positioning, etc.), a range parameter (e.g., a range in meters, such as a 10 meter (m)-300 m range), a range resolution parameter (e.g., a resolution within a particular measurement, such as <1 m, <0.1 m, <1 centimeter (cm)), a speed parameter (e.g., a speed in meters / second (m / s), such as -75 m / s to 60 m / s), a speed ... The sensing session parameters may include, for example, a range of parameters such as a local resolution, ...

[0083] In some aspects, communication session parameters (e.g., information indicating one or more session sensing parameters) may include bandwidth parameters, subcarrier spacing parameters, guard band parameters, coherent processing interval parameters, burst duration parameters, burst interval parameters, update interval parameters, transmit start time parameters, beam direction parameters, beam width parameters, and / or transmit power parameters.

[0084] Although in some implementations, the network node rather than the UE may map and / or convert the sensing parameters into communication parameters, it may be advantageous for the UE to perform the mapping. For example, the UE may reduce the processing load on the network node by performing the mapping. In addition, when the UE is aware of the impact that various parameter changes will have on each other (e.g., aware of how changes in sensing parameters affect communication parameters and / or how changes in communication parameters affect sensing parameters), the UE is better able to adjust parameters when negotiating resource allocation with the network node.

[0085] As indicated by reference numeral 510, the UE may send a first request associated with establishing a sensing service, and the network node may receive the first request. The first request may include information indicating one or more requested sensing session parameters associated with the sensing service. As described herein, in some aspects, the information indicating the one or more requested sensing session parameters may specify sensing session parameters and corresponding values ​​(e.g., leaving the mapping of values ​​to the network node). In some aspects, the information indicating the one or more requested sensing session parameters may be communication session parameters previously converted (e.g., by the UE, as described herein) from the requested sensing session parameters.

[0086] As indicated by reference numeral 515, the network node may receive policy information of the UE and / or the network, and the core network entity may send the policy information. For example, the network node may communicate with one or more core network entities, such as a network slice selection function (NSSF), a network open function (NEF), a unified data repository (UDR), a unified data management (UDM) component, a policy control function (PCF), an application function (AF), an access and mobility management function (AMF), a session management function (SMF), and / or a user plane function (UPF), a non-communication SMF (N-SMF) (e.g., for sensing services) and a non-communication PCF (N-PCF) (e.g., for sensing services), etc. The policy information may enable the network node to determine the quality of service available for the UE and other information that enables the network node to treat a first request for a sensing service as a request for a virtual communication session, so that the network node can allocate resources to the sensing service as if it were another communication session with separate communication session parameters.

[0087] As indicated by reference numeral 520, the network entity may determine resource allocation based at least in part on information mapping the requested sensing session parameters to the communication session parameters. As described herein, the UE may have mapped the requested sensing session parameters to the communication session parameters. In some aspects, the network node may perform the mapping to obtain the communication session parameters for the virtual communication session.

[0088] In some aspects, the network node may determine resource allocation based at least in part on available resources and / or network policy information received from a core network entity. For example, available resources may depend on other communications and non-communication sessions with the UE and other devices. Available resources may also depend on network policy information that indicates which resources may be available for the UE, the network, and / or a specific communication type, etc. In some aspects, resource allocation may not meet the requirements of the sensing service. For example, based on available resources and / or policy information, the network node may not be able to allocate resources that meet the requirements indicated by the communication session parameters. In this case, the network node can still generate resource allocations, but for one or more reduced communication session parameters (e.g., reduced bandwidth and / or reduced latency, etc.).

[0089] As shown by reference numeral 525, the network node may send a resource allocation, and the UE may receive the resource allocation. For example, the network node may send the resource allocation to the UE based at least in part on the first request. The resource allocation may be used for a virtual communication session between the network node and the UE, and the resource allocation may generally indicate one or more resources (e.g., time resources, frequency resources, space resources, and / or power resources, etc.) for a sensing service.

[0090] As shown by reference numeral 530, the UE may determine that one or more resources are insufficient for the sensing service. For example, the UE may determine that the resource allocation will not meet the requirements of a particular sensing service (such as a high detection rate sensing application). In some aspects, the UE may use one or more resources of the resource allocation. In some aspects, the UE may negotiate with the network node to obtain a more favorable resource allocation (for the sensing service).

[0091] As indicated by reference numeral 535, the UE may send a second request associated with establishing a sensing service, and the network node may receive the second request, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service. The adjusted sensing session parameters may have lower requirements (e.g., lower bandwidth and / or increased latency, etc.) than the sensing session parameters included in the first request. The adjusted request is part of a round-trip negotiation between the UE and the network node to obtain resource allocation that works for both the network node and the UE's sensing service. As described herein, the network node or the UE may map the adjusted sensing session parameters to communication sensing parameters.

[0092] As indicated by reference numeral 540, the network node may determine an adjusted resource allocation. For example, the network node may determine the adjusted resource allocation based at least in part on information indicating the adjusted sensing session parameters. As described herein, the resource allocation may be determined in a manner similar to determining an initial resource allocation.

[0093] The network node may send the adjusted resource allocation, and the UE may receive the adjusted resource allocation, as indicated by reference numeral 545. For example, the adjusted resource allocation may be sent and received in a manner similar to that described herein for the initial resource allocation.

[0094] In some aspects, the UE and the network node may communicate back and forth regarding resource allocations to negotiate a virtual communication session with parameters that function for both the network node and the UE's sensing services.

[0095] As shown in reference numeral 550, the UE may determine one or more granted sensing session parameters based at least in part on the one or more resources. In some aspects, the one or more granted sensing session parameters match the one or more requested sensing session parameters. In some aspects, the one or more granted sensing session parameters are different from the one or more requested sensing session parameters. For example, depending on whether the network node is allocated sufficient resources, the UE may or may not have granted sensing session parameters that match the requested sensing session parameters. The granted sensing session parameters may have values ​​that enable the UE's sensing service to operate with a specific sensing range, resolution, accuracy, and / or latency, etc.

[0096] As shown by reference numeral 555, the UE may send one or more sensing signals using one or more resources. For example, the UE may use one or more resources to use a sensing service. In this case, the network node and the UE may view the resources as virtual communication resources, but may send actual signals for the sensing service instead of communication. This enables the UE to use communication-based resource allocation for the sensing service and enables the network node to allocate resources to the sensing service as if it were a communication session.

[0097] As shown by reference numeral 560, the network node may determine that the time period that the UE has attempted to establish the sensing service has satisfied a time threshold, or that the number of attempts to establish the sensing service has satisfied an attempt threshold. For example, after negotiating back and forth for a particular time period or for a threshold number of attempts, the network node may determine that the virtual communication session may not be established using sensing and / or communication parameters that are acceptable to the UE for the sensing service. In this case, the network node may send information indicating a rejection of the sensing service, and the UE may receive the information. This may enable the UE to obtain resources or take another action from another network node, rather than continuing to negotiate with the network node what may be a time-sensitive sensing service.

[0098] In some aspects, the network node may manage the virtual communication session by changing parameters of the virtual communication session over time. For example, based on changing network conditions and / or the need for sensing services communicated by the UE to the network node, the virtual communication session may be adjusted by increasing and / or decreasing various parameter values. This may enable the network node to manage the virtual communication session in a manner coordinated with the UE and other communication and non-communication sessions handled by the network node or other network nodes included in the network.

[0099] In some aspects, the core network entity may provide the first request to the network node. For example, in addition to or as an alternative to the UE providing the first request to the network node, the UE may provide the first request (or a similar request) to a core network entity (such as an AMF and / or N-SMF, etc.). The core network entity or another core network entity may then provide the first request to the network node on behalf of the UE. For example, the UE may transmit a request to establish a sensing session to the N-SMF, and the N-SMF may cause the SMF to provide the first request to the network node for establishing a virtual communication session.

[0100] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Described differently.

[0101] As a result of the operations described herein, a network node may manage a sensing service as a virtual communication session in a manner similar to that of other communication sessions. This also enables the sensing service to be associated with QoS parameters comparable to those of the communication service, which may facilitate resource allocation for different types of services. In this manner, the network may more efficiently allocate resources between communication services and non-communication services, and in a manner that appropriately prioritizes the communication services and non-communication services relative to each other. This may result in higher quality communication and non-communication sessions relative to a network using a framework that lacks the ability to manage non-communication sessions as virtual communication sessions, as described herein.

[0102] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example in which a UE (eg, UE 120) performs operations associated with resource allocation for a sensing service.

[0103] like Figure 6 As shown, in some aspects, process 600 may include sending a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service (block 610). Figure 8The communication manager 140 and / or the sending component 804 depicted in FIG. 8 may send a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service, as described above.

[0104] like Figure 6 As further shown, in some aspects, process 600 may include receiving, from a network node and based at least in part on the first request, a resource allocation for the virtual communication session, the resource allocation indicating one or more resources for the sensing service (block 620). Figure 8 The communication manager 140 and / or receiving component 802 depicted in FIG. 8 may receive a resource allocation for a virtual communication session from a network node and based at least in part on the first request, the resource allocation indicating one or more resources for a sensing service, as described above.

[0105] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0106] In a first aspect, the requested sensing session parameters include at least one of a priority parameter, a sensing type parameter, a range parameter, a range resolution parameter, a speed parameter, a speed resolution parameter, an azimuth field of view parameter, an angular resolution parameter, a maximum number of detected targets, an update rate parameter, a data rate parameter, or a latency parameter.

[0107] In a second aspect, either alone or in combination with the first aspect, process 600 includes determining that one or more resources are insufficient for a sensing service; and sending a second request associated with establishing a sensing service to a network node, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0108] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 600 includes receiving, from a network node and based at least in part on a second request, an adjusted resource allocation for a virtual communication session, the adjusted resource allocation indicating one or more other resources for a sensing service.

[0109] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 600 includes receiving information indicating a denial of a sensing service from a network node.

[0110] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 600 includes determining one or more granted sensing session parameters based at least in part on one or more resources, and sending one or more sensing signals using the one or more resources.

[0111] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, one or more granted sensing session parameters match one or more requested sensing session parameters.

[0112] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more granted sensing session parameters are different from one or more requested sensing session parameters.

[0113] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, process 600 includes determining information indicating one or more requested sensing session parameters based at least in part on information mapping at least one of the requested sensing session parameters to one or more communication session parameters.

[0114] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the information indicating one or more requested sensing session parameters includes at least one of a bandwidth parameter, a subcarrier spacing parameter, a guard band parameter, a coherent processing interval parameter, a burst duration parameter, a burst interval parameter, an update interval parameter, a transmit start time parameter, a beam direction parameter, a beam width parameter, or a transmit power parameter.

[0115] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the sensing service is a single-station sensing service.

[0116] although Figure 6 Example blocks of process 600 are shown, but in some aspects, process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more of the blocks in the process 600 may be performed in parallel.

[0117] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a network node in accordance with the present disclosure. The example process 700 is an example in which a network node (eg, the network node 110) performs operations associated with resource allocation for a sensing service.

[0118] like Figure 7As shown, in some aspects, process 700 may include receiving a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service (block 710). For example, a network node (e.g., using Fig. 9 The communication manager 150 and / or receiving component 902 depicted in FIG. 1 may receive a first request associated with establishing a sensing service with a UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service, as described above.

[0119] like Figure 7 As further shown, in some aspects, process 700 may include sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service (block 720). Fig. 9 The communication manager 150 and / or sending component 904 depicted in the figure may send a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service, as described above.

[0120] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0121] In a first aspect, one or more requested sensing session parameters include at least one of a priority parameter, a sensing type parameter, a range parameter, a range resolution parameter, a speed parameter, a speed resolution parameter, an azimuth field of view parameter, an angular resolution parameter, a maximum number of detected targets, an update rate parameter, a data rate parameter, or a latency parameter.

[0122] In a second aspect, alone or in combination with the first aspect, process 700 includes determining a resource allocation based at least in part on information mapping at least one of the one or more requested sensing session parameters to a communication session parameter.

[0123] In a third aspect, either alone or in combination with one or more of the first and second aspects, the communication session parameters include at least one of a bandwidth parameter, a subcarrier spacing parameter, a guard band parameter, a coherent processing interval parameter, a burst duration parameter, a burst interval parameter, an update interval parameter, a transmission start time parameter, a beam direction parameter, a beam width parameter, or a transmission power parameter.

[0124] In a fourth aspect, alone or in combination with one or more of the first to third aspects, determining resource allocation further comprises determining resource allocation based at least in part on at least one of available resources or network policy information received from a core network entity.

[0125] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 700 includes determining a resource allocation based at least in part on at least one of the requested sensing session parameters.

[0126] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 700 includes receiving, from a UE, a second request associated with establishing a sensing service, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0127] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 700 includes sending an adjusted resource allocation for a virtual communication session to the UE and based at least in part on a second request, the adjusted resource allocation indicating one or more other resources for the sensing service.

[0128] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 700 includes determining that a time period during which the UE has attempted to establish a sensing service has satisfied a time threshold, or a number of attempts to establish a sensing service has satisfied an attempt threshold, and sending information to the UE indicating rejection of the sensing service.

[0129] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the sensing service is a single-station sensing service.

[0130] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first request is received from a UE.

[0131] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the first request is received from a core network entity.

[0132] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of process 700 may be performed in parallel.

[0133] Figure 8800 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802 and a sending component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the receiving component 802 and the sending component 804. As further shown, the apparatus 800 may include a communication manager 140. The communication manager 140 may include a determination component 808, etc.

[0134] In some aspects, the apparatus 800 may be configured to perform Figures 4 to 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 800 and / or Figure 8 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0135] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0136] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0137] The sending component 804 can send a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The receiving component 802 can receive a resource allocation for a virtual communication session from the network node and based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0138] Determining component 808 can determine that one or more resources are insufficient for the sensing service.

[0139] The sending component 804 can send, to the network node, a second request associated with establishing a sensing service, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0140] Receiving component 802 can receive, from the network node and based at least in part on the second request, an adjusted resource allocation for the virtual communication session, the adjusted resource allocation indicating one or more other resources for the sensing service.

[0141] Receiving component 802 can receive information from a network node indicating a denial of sensing service.

[0142] Determining component 808 can determine one or more granted sensing session parameters based at least in part on the one or more resources.

[0143] The transmitting component 804 can transmit one or more sensing signals using one or more resources.

[0144] Determining component 808 can determine information indicative of one or more requested sensing session parameters based at least in part on information mapping at least one of the requested sensing session parameters to one or more communication session parameters.

[0145] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set of component(s) may be described as being executable by Figure 8 Another collection of components shown performs one or more functions.

[0146] Fig. 9 900 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a sending component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and sending component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include a determining component 908, etc.

[0147] In some aspects, the apparatus 900 may be configured to perform Figures 4 to 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0148] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0149] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0150] The receiving component 902 may receive a first request associated with establishing a sensing service with the UE, the first request including information indicating one or more requested sensing session parameters associated with the sensing service. The sending component 904 may send a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0151] Determining component 908 can determine a resource allocation based at least in part on information mapping at least one of the one or more requested sensing session parameters to a communication session parameter.

[0152] Determining component 908 can determine a resource allocation based at least in part on at least one of the requested sensing session parameters.

[0153] Receiving component 902 can receive, from a UE, a second request associated with establishing a sensing service, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0154] The sending component 904 can send, to the UE and based at least in part on the second request, an adjusted resource allocation for the virtual communication session, the adjusted resource allocation indicating one or more other resources for the sensing service.

[0155] Determining component 908 can determine that a time period for which the UE has attempted to establish sensing service has satisfied a time threshold, or a number of attempts to establish sensing service has satisfied an attempt threshold.

[0156] The sending component 904 can send information indicating the denial of the sensing service to the UE.

[0157] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set of component(s) may be described as being executable by Fig. 9 Another collection of components shown performs one or more functions.

[0158] The following provides an overview of some aspects of the disclosure:

[0159] Aspect 1: A method of wireless communication performed by a UE, comprising: sending a first request associated with establishing a sensing service to a network node, the first request including information indicating one or more requested sensing session parameters associated with the sensing service; and receiving a resource allocation for a virtual communication session from the network node and based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0160] Aspect 2: A method according to Aspect 1, wherein the requested sensing session parameters include at least one of the following: a priority parameter, a sensing type parameter, a range parameter, a range resolution parameter, a speed parameter, a speed resolution parameter, an azimuth field of view parameter, an angular resolution parameter, a maximum number of detected targets, an update rate parameter, a data rate parameter, or a latency parameter.

[0161] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: determining that the one or more resources are insufficient for the sensing service; and sending a second request associated with establishing the sensing service to the network node, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0162] Aspect 4: The method according to aspect 3 also includes: receiving an adjusted resource allocation for the virtual communication session from the network node and at least partly based on the second request, the adjusted resource allocation indicating one or more other resources for the sensing service.

[0163] Aspect 5: The method according to aspect 3, further comprising: receiving information indicating rejection of the sensing service from the network node.

[0164] Aspect 6: The method according to any one of aspects 1 to 5 further includes: determining one or more granted sensing session parameters based at least in part on the one or more resources; and sending one or more sensing signals using the one or more resources.

[0165] Aspect 7: The method according to aspect 6, wherein the one or more granted sensing session parameters match the one or more requested sensing session parameters.

[0166] Aspect 8: The method according to aspect 6, wherein the one or more granted sensing session parameters are different from the one or more requested sensing session parameters.

[0167] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: determining the information indicating the one or more requested sensing session parameters based at least in part on information mapping at least one of the requested sensing session parameters to one or more communication session parameters.

[0168] Aspect 10: A method according to Aspect 9, wherein the information indicating the sensing session parameters of the one or more requests includes at least one of the following: bandwidth parameters, subcarrier spacing parameters, guard band parameters, coherent processing interval parameters, burst duration parameters, burst interval parameters, update interval parameters, transmission start time parameters, beam direction parameters, beam width parameters, or transmission power parameters.

[0169] Aspect 11: The method according to any one of aspects 1 to 10, wherein the sensing service is a single-station sensing service.

[0170] Aspect 12: A method of wireless communication performed by a network node, comprising: receiving a first request associated with establishing a sensing service with a UE, the first request comprising information indicating one or more requested sensing session parameters associated with the sensing service; and sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

[0171] Aspect 13: A method according to Aspect 12, wherein the one or more requested sensing session parameters include at least one of the following: a priority parameter, a sensing type parameter, a range parameter, a range resolution parameter, a speed parameter, a speed resolution parameter, an azimuth field of view parameter, an angular resolution parameter, a maximum number of detected targets, an update rate parameter, a data rate parameter, or a latency parameter.

[0172] Aspect 14: The method according to any one of aspects 12 to 13, further comprising: determining the resource allocation based at least in part on information mapping at least one of the one or more requested sensing session parameters to communication session parameters.

[0173] Aspect 15: A method according to Aspect 14, wherein the communication session parameters include at least one of the following: bandwidth parameters, subcarrier spacing parameters, guard band parameters, coherent processing interval parameters, burst duration parameters, burst interval parameters, update interval parameters, transmission start time parameters, beam direction parameters, beam width parameters, or transmission power parameters.

[0174] Aspect 16: The method according to aspect 14, wherein determining the resource allocation further comprises: further determining the resource allocation based at least in part on at least one of: available resources or network policy information received from a core network entity.

[0175] Aspect 17: The method according to any one of aspects 12 to 16, further comprising: determining the resource allocation based at least in part on at least one of the requested sensing session parameters.

[0176] Aspect 18: The method according to any one of Aspects 12 to 17 further includes: receiving a second request associated with establishing the sensing service from the UE, the second request including information indicating one or more adjusted sensing session parameters associated with the sensing service.

[0177] Aspect 19: The method according to aspect 18 also includes: sending an adjusted resource allocation for the virtual communication session to the UE and at least partly based on the second request, the adjusted resource allocation indicating one or more other resources for the sensing service.

[0178] Aspect 20: The method according to Aspect 18 also includes: determining that the time period during which the UE has attempted to establish the sensing service has met a time threshold, or the number of attempts to establish the sensing service has met an attempt threshold; and sending information to the UE indicating rejection of the sensing service.

[0179] Aspect 21: The method according to any one of aspects 12 to 20, wherein the sensing service is a single-station sensing service.

[0180] Aspect 22: The method according to any one of aspects 12 to 21, wherein the first request is received from the UE.

[0181] Aspect 23: The method according to any one of aspects 12 to 22, wherein the first request is received from a core network entity.

[0182] Aspect 24: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0183] Aspect 25: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 23.

[0184] Aspect 26: An apparatus for wireless communication, comprising a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 11.

[0185] Aspect 27: An apparatus for wireless communication, comprising a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 12 to 23.

[0186] Aspect 28: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 11.

[0187] Aspect 29: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 12 to 23.

[0188] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0189] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 23.

[0190] Aspect 32: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.

[0191] Aspect 33: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 12 to 23.

[0192] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0193] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0194] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0195] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0196] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: sending a first request associated with establishing a sensing service to a network node, The first request includes information indicative of one or more requested sensing session parameters associated with the sensing service; as well as receiving, from the network node and based at least in part on the first request, a resource allocation for a virtual communication session, The resource allocation indicates one or more resources for the sensing service.

2. The UE of claim 1 , wherein the one or more requested sensing session parameters include at least one of: The priority parameter, Sensing type parameters, Range parameters, Range resolution parameter, Speed ​​parameters, Speed ​​resolution parameter, Azimuth field of view parameters, Angular resolution parameter, The maximum number of detected targets, Update rate parameters, Data rate parameters, or Delay parameter.

3. The UE of claim 1 , wherein the one or more processors are further configured to: determining that the one or more resources are insufficient for the sensing service; and sending a second request associated with establishing the sensing service to the network node, The second request includes information indicative of one or more adjusted sensing session parameters associated with the sensing service.

4. The UE of claim 3, wherein the one or more processors are further configured to: receiving, from the network node and based at least in part on the second request, an adjusted resource allocation for the virtual communication session, The adjusted resource allocation indicates one or more additional resources for the sensing service.

5. The UE of claim 3, wherein the one or more processors are further configured to: Information indicating a denial of the sensing service is received from the network node.

6. The UE of claim 1, wherein the one or more processors are further configured to: determining one or more granted sensing session parameters based at least in part on the one or more resources; and One or more sensing signals are sent using the one or more resources. 7 . The UE of claim 6 , wherein the one or more granted sensing session parameters match the one or more requested sensing session parameters. 8 . The UE of claim 6 , wherein the one or more granted sensing session parameters are different from the one or more requested sensing session parameters.

9. The UE of claim 1, wherein the one or more processors are further configured to: The information indicative of the one or more requested sensing session parameters is determined based at least in part on information mapping at least one of the one or more requested sensing session parameters to one or more communication session parameters.

10. The UE of claim 9, wherein the information indicative of the one or more requested sensing session parameters comprises at least one of: Bandwidth parameters, Subcarrier spacing parameter, Guard band parameters, Coherent processing interval parameter, Burst duration parameter, Burst interval parameter, Update interval parameters, Send the start time parameter, Beam direction parameters, The beamwidth parameter, or Transmit power parameter. The UE according to claim 1 , wherein the sensing service is a single-station sensing service.

12. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving a first request associated with establishing a sensing service with a user equipment (UE), The first request includes information indicative of one or more requested sensing session parameters associated with the sensing service; as well as A resource allocation for a virtual communication session with the UE is sent based at least in part on the first request, the resource allocation indicating one or more resources for the sensing service.

13. The network node of claim 12, wherein the one or more requested sensing session parameters include at least one of: The priority parameter, Sensing type parameters, Range parameters, Range resolution parameter, Speed ​​parameters, Velocity resolution parameter, Azimuth field of view parameters, Angular resolution parameter, The maximum number of detected targets, Update rate parameters, Data rate parameters, or Delay parameter.

14. The network node of claim 12, wherein the one or more processors are further configured to: The resource allocation is determined based at least in part on information mapping at least one of the one or more requested sensing session parameters to a communication session parameter.

15. The network node of claim 14, wherein the communication session parameters include at least one of: Bandwidth parameters, Subcarrier spacing parameter, Guard band parameters, Coherent processing interval parameter, Burst duration parameter, Burst interval parameter, Update interval parameters, Send the start time parameter, Beam direction parameters, The beamwidth parameter, or Transmit power parameter.

16. The network node of claim 14, wherein to determine the resource allocation, the one or more processors are configured to: The resource allocation is further determined based at least in part on at least one of: Available resources, or Network policy information received from core network entities.

17. The network node of claim 12, wherein the one or more processors are further configured to: The resource allocation is determined based at least in part on at least one of the one or more requested sensing session parameters.

18. The network node of claim 12, wherein the one or more processors are further configured to: receiving, from the UE, a second request associated with establishing the sensing service, The second request includes information indicative of one or more adjusted sensing session parameters associated with the sensing service.

19. The network node of claim 18, wherein the one or more processors are further configured to: sending, to the UE and based at least in part on the second request, an adjusted resource allocation for the virtual communication session, The adjusted resource allocation indicates one or more additional resources for the sensing service.

20. The network node of claim 18, wherein the one or more processors are further configured to: determining that a time period during which the UE has attempted to establish the sensing service has satisfied a time threshold, or a number of attempts to establish the sensing service has satisfied an attempt threshold; and Sending information indicating rejection of the sensing service to the UE.

21. The network node of claim 12, wherein the sensing service is a single-station sensing service.

22. The network node of claim 12, wherein the first request is received from the UE.

23. The network node of claim 12, wherein the first request is received from a core network entity.

24. A method of wireless communication performed by a user equipment (UE), comprising: sending a first request associated with establishing a sensing service to a network node, The first request includes information indicative of one or more requested sensing session parameters associated with the sensing service; as well as receiving, from the network node and based at least in part on the first request, a resource allocation for a virtual communication session, The resource allocation indicates one or more resources for the sensing service.

25. The method according to claim 24, further comprising: determining that the one or more resources are insufficient for the sensing service; sending a second request associated with establishing the sensing service to the network node, the second request comprising information indicative of one or more adjusted sensing session parameters associated with the sensing service; as well as receiving, from the network node and based at least in part on the second request, an adjusted resource allocation for the virtual communication session, The adjusted resource allocation indicates one or more additional resources for the sensing service.

26. The method of claim 24, further comprising: determining one or more granted sensing session parameters based at least in part on the one or more resources; as well as One or more sensing signals are sent using the one or more resources.

27. The method of claim 24, further comprising: The information indicative of the one or more requested sensing session parameters is determined based at least in part on information mapping at least one of the one or more requested sensing session parameters to one or more communication session parameters.

28. A method of wireless communication performed by a network node, comprising: receiving a first request associated with establishing a sensing service with a user equipment (UE), The first request includes information indicative of one or more requested sensing session parameters associated with the sensing service; as well as sending a resource allocation for a virtual communication session with the UE based at least in part on the first request, The resource allocation indicates one or more resources for the sensing service.

29. The method according to claim 28, further comprising: The resource allocation is determined based at least in part on information mapping at least one of the one or more requested sensing session parameters to a communication session parameter.

30. The method of claim 28, wherein determining the resource allocation further comprises: The resource allocation is further determined based at least in part on at least one of: Available resources, or Network policy information received from core network entities.

Images