Resource management for communication and sensing services

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first core network entity may receive a first request associated with initiation of a sensing service associated with a user equipment (UE). The first core network entity may receive one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The first core network entity may provide, to a second core network entity and based at least in part on the sensed session parameters, a second request to establish a virtual communication session with the UE, the request including one or more communication session parameters. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek patent application No. 20220100718, entitled “RESOURCE MANAGEMENT FOR COMMUNICATION AND 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 apparatuses for resource management for communication and 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 wireless communication performed by a first core network entity. The method may include receiving a first request associated with initiation of a sensing service associated with a user equipment (UE). The method may include receiving one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The method may include providing a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters.

[0008] Some aspects described herein relate to a method of wireless communication performed by a first core network entity. The method may include receiving a first request associated with a communication session associated with a UE, wherein the first request is associated with one or more first communication session parameters. The method may include receiving a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service. The method may include providing information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to a network node.

[0009] 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 initiation of a sensing service associated with a UE from a first core network entity, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service. The method may include determining one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node. The method may include sending information identifying one or more resources for the sensing service to the UE.

[0010] Some aspects described herein relate to a first core network entity. The first core network entity 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 initiation of a sensing service associated with a UE. The one or more processors may be configured to receive one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The one or more processors may be configured to provide a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters.

[0011] Some aspects described herein relate to a first core network entity. The first core network entity 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 a communication session associated with a UE. The one or more processors may be configured to receive a second request from a second core network entity to establish a virtual communication session associated with the UE. The one or more processors may be configured to provide information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to a network node.

[0012] Some aspects described herein relate to a network node. 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 initiation of a sensing service associated with a UE from a first core network entity. The one or more processors may be configured to determine one or more resources for the sensing service based at least in part on one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node. The one or more processors may be configured to send information identifying one or more resources for the sensing service to the UE.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set by a first core network entity. The instruction set, when executed by one or more processors of the first core network entity, can cause the first core network entity to receive a first request associated with the initiation of a sensing service associated with a UE. The instruction set, when executed by one or more processors of the first core network entity, can cause the first core network entity to receive one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The instruction set, when executed by one or more processors of the first core network entity, can cause the first core network entity to provide a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including one or more communication session parameters.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set by a first core network entity. The instruction set, when executed by one or more processors of the first core network entity, may cause the first core network entity to receive a first request associated with a communication session associated with a UE. The instruction set, when executed by one or more processors of the first core network entity, may cause the first core network entity to receive a second request from a second core network entity to establish a virtual communication session associated with the UE. The instruction set, when executed by one or more processors of the first core network entity, may cause the first core network entity to provide information indicating one or more first communication session parameters for a communication session and one or more second communication session parameters for a virtual communication session to a network node.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set 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 initiation of a sensing service associated with a UE from a first core network entity. The instruction set, when executed by one or more processors of the network node, may cause the network node to determine one or more resources for the sensing service based at least in part on one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send information identifying one or more resources for the sensing service to the UE.

[0016] Some aspects described herein relate to an apparatus. The apparatus may include components for receiving a first request associated with initiation of a sensing service associated with a UE. The apparatus may include components for receiving one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The apparatus may include components for providing a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters.

[0017] Some aspects described herein relate to an apparatus. The apparatus may include components for receiving a first request associated with a communication session associated with a UE, wherein the first request is associated with one or more first communication session parameters. The apparatus may include components for receiving a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service. The apparatus may include components for providing information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to a network node.

[0018] Some aspects described herein relate to an apparatus. The apparatus may include components for receiving, from a first core network entity, a first request associated with initiation of a sensing service associated with a UE, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service. The apparatus may include components for determining one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and a network node. The apparatus may include components for sending, to the UE, information identifying the one or more resources for the sensing service.

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

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

[0021] 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

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

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

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

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

[0026] Figure 4 is a diagram of an example of a core network configured to facilitate wireless communications in accordance with the present disclosure.

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

[0028] Figure 6 is a diagram of an example of a core network configured to facilitate resource management for communication and sensing services.

[0029] Figure 7 is a diagram of an example associated with resource management for communication and sensing services performed by one or more core network entities according to the present disclosure.

[0030] Figure 8 is a diagram of an example associated with resource management for communication and sensing services performed by a network node according to the present disclosure.

[0031] Fig. 9 is a diagram illustrating an example process performed, for example, by a first core network entity according to the present disclosure.

[0032] Fig.10 is a diagram illustrating an example process performed, for example, by a first core network entity according to the present disclosure.

[0033] Fig.11 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0034] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure.

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

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

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

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

[0039] Figure 11 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)).

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

[0041] 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 1 In 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).

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

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

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

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

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

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

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

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

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

[0051] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, 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.

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

[0053] 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 initiation of a sensing service associated with a UE from a first core network entity, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service; determine one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node; and send information identifying the one or more resources for the sensing service to the UE. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0054] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The content described is different.

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

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

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

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

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

[0060] 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 aspects of any of the methods described herein (eg, with reference to Figures 4 to 13 ).

[0061] 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 aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). Figures 4 to 13 ).

[0062] 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 may perform one or more techniques associated with resource management for communication and sensing services, as described in more detail elsewhere herein. In some aspects, the core network entity described herein is implemented as a network node 110, or includes Figure 2 One or more components of the network node 110 shown. 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 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 1100 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, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), the one or more instructions may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0063] In some aspects, the first core network entity includes a component for receiving a first request associated with initiation of a sensing service associated with the UE; a component for receiving one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request; and / or a component for providing a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters. In some aspects, the component for the first core network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 1250, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0064] In some aspects, the first core network entity includes a component for receiving a first request associated with a communication session associated with a UE, wherein the first request is associated with one or more first communication session parameters; a component for receiving a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service; and / or a component for providing information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to a network node. In some aspects, the component for the first core network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 1250, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0065] In some aspects, the network node includes means for receiving a first request associated with initiation of a sensing service associated with a UE from a first core network entity, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service; means for determining one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node; and / or means for sending information identifying one or more resources for the sensing service to the UE. In some aspects, means for the network node to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

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

[0067] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The content described is different.

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

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

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

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

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

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

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

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

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

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

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

[0079] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The content described is different.

[0080] Figure 4 4 is a diagram of an example of a core network 405 configured to facilitate wireless communications. Figure 4 As shown in , example 400 may include UE 120, wireless communication network 100, and core network 405. Devices (core network entities) and / or networks of example 400 may be interconnected via wired connections, wireless connections, or a combination thereof.

[0081] For example, the wireless communication network 100 may support a cellular RAT. The network 100 may include one or more network nodes (e.g., a base station, a base transceiver station, a radio base station, a Node B, an eNodeB (eNB), a gNodeB (gNB), a base station subsystem, a cellular site, a cellular tower, an access point, a TRP, a radio access node, a macrocell base station, a microcell base station, a picocell base station, a femtocell base station, or similar types of devices) and other network entities that may support wireless communication of the UE 120. The network 100 may communicate traffic between the UE 120 (e.g., using a cellular RAT), one or more network nodes (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and / or a core network 405. The wireless communication network 100 may provide one or more cells covering a geographic area.

[0082] In some aspects, the wireless communication network 100 may perform scheduling and / or resource management for UEs 120 covered by the network 100 (e.g., UEs 120 covered by a cell provided by the wireless communication network 100). In some aspects, the wireless communication network 100 may be managed by a network controller (e.g., Figure 1 The network controller 130) controls or coordinates, and the network controller can perform load balancing and / or network level configuration, etc. Figure 1 As described, the network controller may communicate with the network 100 via wireless or wired backhaul. In some aspects, the network 100 may include a network controller, a self-organizing network (SON) module or component, or a similar core network entity, module or component. Thus, the network 100 may perform network control, scheduling and / or network management functions (e.g., for uplink, downlink and / or sidelink communications of UE 120 covered by the network 100).

[0083] In some aspects, the core network 405 may include an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 405 may include an example architecture of a 5G next generation (NG) core network included in a fifth generation (5G) wireless telecommunications system. Figure 4 The example architecture of the core network 405 shown may be an example of a service-based architecture, but in some aspects the core network 405 may be implemented as a reference point architecture and / or a 4G core network, among others.

[0084] like Figure 4As shown, the core network 405 may include a plurality of core network entities identified as functional elements. The core network entities may include, for example, a network slice selection function (NSSF) 410, a network open function (NEF) 415, a unified data repository (UDR) 420, a unified data management (UDM) component 425, a policy control function (PCF) 430, an application function (AF) 435, an access and mobility management function (AMF) 440, a session management function (SMF) 445 and / or a user plane function (UPF) 450, etc. These core network entities may be communicatively connected via a message bus 455. Figure 4 Each of the illustrated core network entities may be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of these core network entities may be implemented on a physical device such as an access point, a base station, and / or a gateway, etc. In some implementations, one or more of these core network entities may be implemented on a computing device in a cloud computing environment.

[0085] NSSF 410 may include one or more devices that select a network slice instance for UE 120. Network slicing is a network architecture model in which logically different network slices operate using a common network infrastructure. For example, several network slices may operate as isolated end-to-end networks that are customized to meet different target service standards for different types of applications executed at least in part by UE 120 and / or communications to and from UE 120. Network slices may effectively provide communications for different types of services with different service standards.

[0086] NEF 415 may include one or more devices that support the opening of capabilities and / or events in a wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. UDR 420 may include one or more devices that act as a repository for subscriber information and other information, which may support various core network entities in a wireless telecommunications system.

[0087] The UDM 425 may include one or more devices that store user data and profiles in a wireless telecommunications system. In some aspects, the UDM 425 may be used for fixed access and / or mobile access in the core network 405, among other things.

[0088] PCF 430 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing and / or mobility management, among other things.

[0089] AF 435 may include one or more devices that support application impact on traffic routing, access and / or policy control to NEF 415, etc. AMF 440 may include one or more devices that act as a termination point for non-access stratum (NAS) signaling and / or mobility management, etc.

[0090] SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, SMF 445 may configure service steering policies at UPF 450 and / or enforce user equipment Internet Protocol (IP) address allocation and policies, etc.

[0091] UPF 450 may include one or more devices that act as anchor points for intra-RAT and / or inter-RAT mobility. In some aspects, UPF 450 may apply rules to packets, such as rules related to packet routing, service reporting, and / or handling user plane QoS, etc.

[0092] The message bus 455 can be a logical and / or physical communication structure for communicating between functional elements. Thus, the message bus 455 can allow communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs), etc.) and / or physically (e.g., using one or more wired and / or wireless connections).

[0093] Figure 4 The number and arrangement of devices and networks shown are provided as examples. In practice, there may be Figure 4 The devices and / or networks shown may include additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged in a different manner than those shown. Figure 4 Two or more of the devices shown may be implemented in a single device, or Figure 4 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, a collection of devices (eg, one or more devices) of example environment 400 may perform one or more functions described as being performed by another collection of devices of example environment 400.

[0094] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The content described is different.

[0095] Figure 5 is a diagram illustrating an example 500 of a joint communication and sensing (JCS) system according to the present disclosure. Figure 5As shown, a UE (e.g., UE 505) may communicate with one or more other UEs (e.g., UE 510) via a sidelink and / or communicate with one or more network nodes (e.g., network node 515) via a downlink and / or uplink.

[0096] UEs such as UE 505 may use 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 send 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 the object, the speed of the object, the direction of the object, or the acceleration of the 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.

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

[0098] like Figure 5 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 505), from different UEs, or a combination thereof. In some cases, the transmission may originate from a network node (e.g., network node 515) 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.

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

[0100] The core network architecture may support communication-based sessions, but currently does not support non-communication-based sessions (e.g., sensing sessions). Although JCS operations may be supported by network nodes, the core network does not support coordination or management of sensing and communication sessions. Although network nodes do support JCS operations that use communication waveforms to perform sensing, JCS is typically accompanied by tradeoffs for communication sessions, such as reduced communication data rates, lower communication spectrum availability (e.g., when sensing is performed in a frequency band). Although network nodes may support different sensing operations based on the specific needs of a sensing session, 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. Different service types may not be properly prioritized without a way to coordinate different service types with different priorities. Lack of coordination for resource allocation between different communication and non-communication service types may also result in lower quality or dropped communication sessions and / or sensing sessions.

[0101] Some of the techniques and devices described herein implement resource management for communication and sensing services that implement JCS operations with support from a core network. For example, a core network entity may receive a request associated with the initiation of a sensing service for a UE, obtain sensing session parameters and policy information from another core network entity, and use the sensing session parameters to establish a virtual communication session with the UE, wherein the virtual communication session is associated with the communication session parameters. Therefore, the core network can manage virtual communication sessions in a manner similar to that of other communication sessions. This enables sensing services to be associated with quality of service (QoS) parameters that are comparable to those of communication services, which can facilitate coordination and management of 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. This can result in higher quality communication and non-communication sessions, as described herein, relative to networks using a framework that lacks the ability to manage non-communication sessions as virtual communication sessions.

[0102] Figure 6 6 is a diagram of an example 600 of a core network 605 configured to facilitate resource management for communication and sensing services. Figure 6 As shown in , example 600 may include UE 120, wireless communication network 100, and core network 605. As shown, core network 605 may include many core network entities described herein (e.g., reference Figure 4 ), such as NSSF 410, NEF 415, UDR 420, UDM component 425, PCF 430, AF 435, AMF 440, SMF 445 and / or UPF 450, etc. The core network 605 also includes a non-communication SMF (N-SMF) 610 and a non-communication PCF (N-PCF) 615. The devices (core network entities) and / or networks of example 600 can be interconnected via wired connections, wireless connections, or a combination thereof.

[0103] The N-SMF 610 may include one or more devices that support the establishment, modification, and release of non-communication sessions (e.g., sensing sessions for radar services and / or positioning services, etc.) in a wireless telecommunications system. In some aspects, the N-SMF 610 may coordinate with the SMF 445, the UDM 425, the AMF 440, and / or the N-PCF 615 to establish a virtual communication session for non-communication services. For example, the AMF 440 may receive a request corresponding to a sensing service (e.g., identified at least in part based on a dedicated DNN or access point name (APN) associated with the sensing service) and forward the request to the N-SMF 610. In some aspects, a dedicated slice may be used to indicate the sensing service, such as a single network slice selection assistance information (S-NSSAI) specific to the sensing service. The N-SMF 610 may obtain subscription information and / or policy information from the UDM 425 and / or the N-PCF 615. In some aspects, the N-SMF 610 may obtain communication session parameters corresponding to the sensing service and coordinate with the SMF 445 and / or AMF 440 to have the sensing service treated as a virtual communication session (e.g., treated as a session for a communication service).

[0104] The N-PCF 615 may include one or more devices that provide a policy framework that may incorporate network slicing, roaming, packet processing, and / or mobility management, among other things. In some aspects, the N-PCF 615 may coordinate with the N-SMF 610, the UDR 420, and / or the NEF 415 to establish a virtual communication session for non-communication services. In some aspects, the N-PCF 615 may obtain policy information associated with the network 100 and / or a UE requesting a sensing service and provide the policy information to the N-SMF 610 for establishing the sensing service and otherwise managing the sensing service as a virtual communication session.

[0105] The operations of N-SMF 610 and N-PCF 615 are further described herein as they relate to managing non-communication sessions as virtual communication sessions. Figure 6 The number and arrangement of devices and networks shown are provided as examples. In practice, there may be Figure 6 The devices and / or networks shown may include additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged in a different manner than those shown. Figure 6 Two or more of the devices shown may be implemented in a single device, or Figure 6 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, a collection of devices (eg, one or more devices) of example environment 600 may perform one or more functions described as being performed by another collection of devices of example environment 600.

[0106] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The content described is different.

[0107] Figure 7 is a diagram of an example 700 associated with resource management for communication and sensing services performed by one or more core network entities according to the present disclosure. Figure 7 As shown, multiple core network entities can communicate with each other (e.g., AMF440, N-SMF 610, N-PCF 615, SMF 445, and UDM 425). In some aspects, the core network entity can be part of a wireless network (e.g., wireless network 100). Figure 7 Prior to the operations shown, one or more network nodes and / or UEs (not shown) may have been connected to the portion (e.g., via AMF 440).

[0108] As shown by reference numeral 705, the AMF may send a first request associated with a communication session associated with the UE, and the SMF may receive the first request. For example, when establishing a communication session, the AMF may communicate with the SMF and other core network entities to establish QoS flows and / or QoS rules, etc., for the communication session. In some aspects, the first request may be associated with one or more first communication session parameters. For example, the first communication session parameters may include quality of service parameters, signal to interference plus noise ratio (SINR) parameters, data rate parameters, and / or latency parameters, etc.

[0109] As indicated by reference numeral 710, the AMF may send a second request associated with initiation of a sensing service associated with the UE, and the N-SMF may receive the second request. For example, in addition to the request for the communication session, the UE may also request resources for the sensing service. By way of example, a UE requesting resources for a V2X communication session may also request resources for the sensing service for positioning and / or collision avoidance, etc.

[0110] In some aspects, the second request may be associated with a sensing network slice indicating that the second request is for a sensing service. For example, separate network slices may be used for sensing services and communication services. In some aspects, the second request may be associated with a dynamic network name (DNN) or APN indicating that the second request is for a sensing service.

[0111] As indicated by reference numeral 715, the N-PCF and / or the UDM may provide one or more sensing session parameters associated with the sensing service, and the N-SMF may obtain the one or more sensing session parameters. In some aspects, the sensing session parameters are based at least in part on subscription information associated with the UE and the sensing service and / or policy information associated with the sensing service, among other things. The subscription information and the policy information may indicate which types of sensing services are available to the UE as well as various QoS parameters and / or restrictions on the sensing service (e.g., restrictions based on a subscriber or a network).

[0112] In some aspects, the N-SMF may receive information indicating one or more policies for managing sensing services, and the N-PCF may provide the information, which may be based at least in part on information identifying the location of the UE. For example, the AMF (or network node) may provide information indicating the location of the UE, and the SMF may be configured to determine sensing session parameters based at least in part on the location of the UE, thereby enabling the N-SMF to adjust various parameters in situations where resources are expected to be more or less limited than other locations.

[0113] In some aspects, the one or more sensing session parameters may include at least one of the following: 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)-300m range), a range resolution parameter (e.g., a resolution within a particular measurement, such as <1m, <0.1m, <1 centimeter (cm)), a speed parameter (e.g., a speed in meters / second (m / s), such as -75m / s to 60m / s), a speed resolution parameter (e.g., a resolution within a particular measurement, such as <1m / s, <0.1m, <1cm ... s or <0.5m / s), azimuth field of view parameters (e.g., azimuth field of view from -15 degrees to +15 degrees), angular resolution parameters (e.g., resolution within a particular measurement, such as <4 degrees, <1 degree, or <0.5 degrees), maximum number of detected targets (e.g., absolute number of detected targets / objects, such as 12, 20, 32, or 64), data rate parameters (e.g., rate in megabits per second (Mbps) or gigabits per second (Gbps)), and / or latency parameters (e.g., measured in milliseconds (ms), such as 100ms). The foregoing sensing session parameters are examples, and the type and range of the parameters may depend on the type of sensing service, UE capabilities, and / or network capabilities, etc.

[0114] In some aspects, the sensing session parameters may be based at least in part on the second request. For example, the second request may include requested sensing parameters (e.g., collision avoidance, ranging, and / or positioning, etc.) that the UE is requesting for a particular sensing application. In some aspects, the sensing session parameters may be based on a combination of parameters requested by the UE and subscription and / or policy information from other core network entities. For example, the N-SMF may use the requested sensing parameters as long as they meet any restrictions identified by the subscription and / or policy information. For requested sensing parameters that do not meet the restrictions, the N-SMF may select the best available sensing session parameters indicated by the subscription and / or policy information.

[0115] As shown by reference numeral 720, the N-SMF may map one or more sensing session parameters to one or more communication session parameters. In some aspects, the N-SMF may use information mapping sensing session parameters to communication sensing parameters to obtain communication session parameters that may be used to treat the sensing service as a virtual communication session. For example, sensing parameters such as sensing type parameters, range parameters, range resolution parameters, speed parameters, speed resolution parameters, azimuth field of view parameters, angular resolution parameters, maximum number of detected targets, data rate parameters, and / or latency parameters may be mapped to communication parameters such as QoS parameters, SINR parameters, data rate parameters, and / or latency parameters, etc. By mapping or converting the sensing parameters to communication parameters, the N-SMF may treat the sensing session as a communication session (e.g., a virtual communication session) in order to schedule, coordinate, and manage the sensing service with other communication sessions and / or services.

[0116] As shown by reference numeral 725, the N-SMF may determine a communication service type for a virtual communication session based at least in part on the sensing session parameters. For example, the N-SMF may determine that a ranging service for supporting a remote driving application may be processed together with or as a V2X and / or unmanned autonomous vehicle (UAV) communication session. In some aspects, the sensing session parameters may indicate and / or map to a corresponding communication service type.

[0117] As shown by reference numeral 730, the N-SMF may provide a third request to establish a virtual communication session with the UE, and the SMF may receive the third request. The request may include second communication session parameters, such as communication session parameters derived from the sensing session parameters (e.g., as described herein). The SMF may already have first communication session parameters for the communication session. The first communication session parameters and the second communication session parameters may enable the SMF, which has already processed the communication session of the UE, to process the virtual communication session side by side with the communication session. In some aspects, the SMF may determine QoS parameters of the communication session and the virtual communication session based on their corresponding parameters.

[0118] As shown by reference numeral 735, the SMF may provide information indicating a first communication session parameter for the communication session and a second communication session parameter for the virtual communication session. For example, the parameters may be provided to the network node via the AMF. In some aspects, based on the communication session parameters, the actual resource allocation may be left to the network node to determine. This may enable the network node to manage both communication-based sessions (e.g., V2X / UAV communication sessions) and non-communication-based sessions (e.g., sensing services such as ranging services), for example, using communication session parameters such as QoS parameters.

[0119] In some aspects, the SMF and / or N-SMF may provide embedded radio level operational configuration information in a sensing session specific container to a network node associated with the UE. For example, the SMF and / or N-SMF may provide configuration information associated with communication session parameters and / or sensing session parameters for a communication session and / or a virtual communication session via the AMF to the network node.

[0120] In some aspects, the N-SMF may provide embedded radio level operational configuration information to the SMF, which in turn may provide the embedded radio level operational configuration information to the network node (e.g., via the AMF).

[0121] In some aspects, the SMF may provide, to the network node (eg, via the AMF), sensing information indicating a virtual communication session for a sensing service to be established between the network node and the UE.

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

[0123] Figure 8 8 is a diagram of an example 800 associated with resource management for communication and sensing services performed by a network node according to the present disclosure. Figure 8As shown, multiple core network entities can communicate with each other (e.g., AMF 440, N-SMF 610, and SMF 445), with network nodes (e.g., network node 110), and / or with UEs (e.g., UE 120). In some aspects, the UE, network nodes, and core network entities can be part of a wireless network (e.g., wireless network 100). Figure 8 Prior to the operations shown, the network node and the UE may have been connected to this part (e.g., via AMF 440).

[0124] As shown in reference numeral 805, the N-SMF and / or SMF may provide a first request associated with the initiation of a sensing service associated with the UE, and the network node may receive the first request. For example, the N-SMF may have previously received information indicating a request for a sensing service, and provide the first request to the network node based at least in part on subscription and / or policy information related to the UE, the network and / or the sensing service. In some aspects, the first request may include information identifying one or more sensing session parameters associated with the sensing service. For example, the N-SMF may provide sensing session parameters to the network node so that the network node can treat the sensing service as a virtual communication session, rather than providing communication session parameters to the network node (e.g., as a virtual communication session). In some aspects, the N-SMF may provide the first request to the network node via the AMF and / or SMF (e.g., as a virtual communication session).

[0125] In some aspects, the first request may include information indicating whether the sensing service is for a radar service, a positioning service, or another type of sensing service. The first request may also include information indicating whether the sensing service is for UE-based sensing or network node-based sensing. UE-based sensing may include a service in which a UE sends a sensing signal, and a network node-based sensing service may include a service in which a network node sends a sensing signal. In some aspects, the first request includes information indicating a priority associated with the sensing service.

[0126] As indicated by reference numeral 810, the SMF may provide (e.g., via the AMF) a second request including one or more communication session parameters, and the network node may receive the second request. The communication session parameters may include any of the communication session parameters described herein for managing the communication session (e.g., QoS parameters).

[0127] As indicated by reference numeral 815, the network node may determine one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with the communication session between the UE and the network node. The one or more resources for the sensing service may be JCS resources associated with the communication session.

[0128] In some aspects, the network node may determine one or more resources based at least in part on other resources associated with at least one other sensing service associated with at least one other UE or network node. For example, the other UE and / or network node may have an active sensing session, and the network node may determine one or more resources around the active sensing session. In some aspects, the one or more resources for the sensing service are associated with a first frequency range (e.g., FR 2), and wherein the one or more other resources for the communication session are associated with a second frequency range (e.g., FR 1).

[0129] In some aspects, a network node may determine a first portion of JCS resources for a sensing service, determine a second portion of JCS resources for a communication session, and determine the first portion of JCS resources (e.g., for the sensing service) as one or more resources. For example, if 100 Mbps can be achieved for a given resource, an 80 Mbps equivalent resource may be allocated to the communication session, and 20 Mbps may be allocated to the virtual communication session, where some waveform parameters are optimized for sensing. For example, a lower data rate waveform may have higher sensing performance due to a large cyclic prefix or guard interval and / or low digital-to-analog converter and / or analog-to-digital converter requirements, etc.

[0130] In some aspects, hybrid bearers may be used to achieve separation of resources for both communication and sensing needs. For example, in situations where only one service needs to be met urgently, separate bearers may be used for communication and sensing. For example, if 100 Mbps is achievable for a given resource, a network node may communicate at 100 Mbps or perform sensing with highly accurate object detection and tracking. The priority of a bearer may depend on the latency parameters of a sensing service or a communication service. For example, a pre-collision radar application may have a higher priority than a communication for a virtual reality game and be scheduled before that communication.

[0131] As shown by reference numeral 820, the network node may send information identifying one or more resources for the sensing service to the UE. For example, after allocating resources between the communication service and the sensing service, the network node may send information indicating the resource allocation for each service to the UE to enable the UE to transmit and / or receive using the resource allocation. In some aspects, the network node may send one or more beam parameters to be used for the sensing service to the UE and based at least in part on the one or more sensing session parameters. For example, different beam parameters such as beam width may be preferred for certain sensing services.

[0132] As shown by reference numeral 825, the network node may adjust one or more sensing parameters. For example, depending on resource requirements for the communication session or for other communication and / or sensing sessions, the priority of a sensing session (e.g., a virtual communication session) may change relative to other sessions. In this case, the network node may adjust resource allocation for the sensing session and / or adjust one or more sensing parameters associated with the sensing session.

[0133] As shown in reference numeral 830, the network node may send information indicating adjustments to one or more sensing session parameters to the SMF or N-SMF. For example, in the event that the sensing session parameters have changed, the SMF and / or N-SMF may be notified so that the SMF and / or N-SMF can coordinate future communications and sensing sessions.

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

[0135] As described herein, a core network can manage virtual communication sessions in a manner similar to that of other communication sessions. This enables sensing services to be associated with QoS parameters that are comparable to QoS parameters for communication services, which can facilitate coordination and management of different types of services. In this manner, 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. This can result in higher quality communication and non-communication sessions relative to networks using a framework that lacks the ability to manage non-communication sessions as virtual communication sessions, as described herein.

[0136] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a first core network entity according to the present disclosure. The example process 900 is an example in which a first core network entity (eg, N-SMF 610) performs operations associated with resource management for communication and sensing services.

[0137] like Fig. 9 As shown, in some aspects, process 900 may include receiving a first request associated with initiation of a sensing service associated with a UE (block 910). For example, a first core network entity (e.g., using Fig.12 The communication manager 1250 and / or receiving component 1202 depicted in FIG. 12 may receive a first request associated with initiation of a sensing service associated with a UE, as described above.

[0138] like Fig. 9As further shown, in some aspects, process 900 may include receiving one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request (block 920). Fig.12 The communication manager 1250 and / or receiving component 1202 depicted in FIG. 1 may receive one or more sensing session parameters associated with a sensing service from at least one other core network entity and based at least in part on the first request, as described above.

[0139] like Fig. 9 As further shown, in some aspects, process 900 may include providing, to a second core network entity and based at least in part on the sensed session parameters, a second request to establish a virtual communication session with the UE, the request including one or more communication session parameters (block 930). Fig.12 The communication manager 1250 and / or sending component 1204 depicted in the figure can provide a second request to establish a virtual communication session with the UE to a second core network entity and at least in part based on the sensed session parameters, the request including one or more communication session parameters, as described above.

[0140] Process 900 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.

[0141] In a first aspect, process 900 includes mapping one or more sensing session parameters to one or more communication session parameters.

[0142] In a second aspect, either alone or in combination with the first aspect, the one or more sensing session parameters include at least one of 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, a data rate parameter, or a latency parameter.

[0143] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more communication session parameters include at least one of a quality of service parameter, a SINR parameter, a data rate parameter, or a latency parameter.

[0144] In a fourth aspect, alone or in combination with one or more of the first to third aspects, one or more sensing session parameters are based at least in part on at least one of information associated with the UE and the sensing service or policy information associated with the sensing service.

[0145] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first core network entity includes an N-SMF, and the second core network entity includes an SMF.

[0146] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, at least one other core network entity includes at least one of an N-PCF or a UDM.

[0147] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, a first request is received from an AMF.

[0148] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first request is associated with a sensing network slice indicating that the first request is for a sensing service.

[0149] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the first request is associated with a DNN or APN indicating that the first request is for a sensing service.

[0150] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving one or more sensing session parameters includes receiving information indicative of one or more policies for managing the sensing service.

[0151] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the information indicative of one or more policies is based at least in part on information identifying a location of the UE.

[0152] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, information indicative of one or more policies is received from an N-PCF entity.

[0153] In a twelfth aspect, either alone or in combination with one or more of aspects one to eleven, process 900 includes determining a communication service type for a virtual communication session based at least in part on a sensed session parameter, and indicating to a second core network entity that the virtual communication session is associated with the communication service type.

[0154] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the communication service type is associated with at least one of V2X communication or UAV communication.

[0155] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 900 includes providing embedded radio level operational configuration information in a sensing session specific container for a network node associated with the UE.

[0156] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the process 900 includes providing a third request to the network node to establish a sensing service between the network node and the UE.

[0157] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the third request includes information indicating whether the sensing service is for a radar service or a positioning service.

[0158] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the third request includes information indicative of one or more sensing session parameters.

[0159] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the third request includes information indicating whether the sensing service is for UE-based sensing or network node-based sensing.

[0160] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the third request includes information indicating a priority associated with the sensing service.

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

[0162] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a first core network entity in accordance with the present disclosure. The example process 1000 is an example in which a first core network entity (eg, SMF 445) performs operations associated with resource management for communication and sensing services.

[0163] like Fig.10 As shown, in some aspects, process 1000 may include receiving a first request associated with a communication session associated with a UE, wherein the first request is associated with one or more first communication session parameters (block 1010). For example, a first core network entity (e.g., using Fig.12 The communication manager 1250 and / or receiving component 1202 depicted in the figure can receive a first request associated with a communication session associated with the UE, wherein the first request is associated with one or more first communication session parameters, as described above. In some aspects, the first request is associated with one or more first communication session parameters.

[0164] like Fig.10As further shown, in some aspects, process 1000 may include receiving, from a second core network entity, a second request to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service (block 1020). Fig.12 In some aspects, the second request is associated with the one or more second communication session parameters. In some aspects, the virtual communication session corresponds to a sensing service.

[0165] like Fig.10 As further shown, in some aspects, process 1000 may include providing information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to a network node (block 1030). Fig.12 The communication manager 1250 and / or the sending component 1204 depicted in FIG. 12 may provide information to the network node indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session, as described above.

[0166] Process 1000 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.

[0167] In a first aspect, process 1000 includes receiving, from a second core network entity, radio level operational configuration information for a network node embedded in a sensing session specific container, and providing the radio level operational configuration information to the network node.

[0168] In a second aspect, either alone or in combination with the first aspect, the radio level operational configuration information is associated with at least one sensing session parameter, the at least one sensing session parameter comprising at least one of 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, a data rate parameter, or a latency parameter.

[0169] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more second communication session parameters include at least one of a quality of service parameter, a SINR parameter, a data rate parameter, or a latency parameter.

[0170] In a fourth aspect, alone or in combination with one or more of the first to third aspects, one or more second communication session parameters are based at least in part on at least one of information associated with the UE and the sensing service or policy information associated with the sensing service.

[0171] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first core network entity includes an SMF, and the second core network entity includes an N-SMF entity.

[0172] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, a first request is received from an AMF entity.

[0173] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the second request is associated with a sensing network slice indicating that the second request is for a sensing service.

[0174] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the second request is associated with a DNN or APN indicating that the second request is for a sensing service.

[0175] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 1000 includes receiving information indicative of one or more policies for managing a virtual communication session as a sensing service.

[0176] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the second request is associated with information indicating that the virtual communication session is associated with a communication service type.

[0177] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the communication service type is associated with at least one of V2X communication or UAV communication.

[0178] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 1000 includes providing, to a network node, sensing information indicating a virtual communication session for a sensing service to be established between the network node and the UE.

[0179] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the sensing information includes information indicating whether the sensing service is for a radar service or a positioning service.

[0180] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the sensing information includes information indicative of one or more sensing session parameters.

[0181] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the sensing information includes information indicating whether the sensing service is for UE-based sensing or network node-based sensing.

[0182] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the sensing information includes information indicating a priority associated with the sensing service.

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

[0184] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network node, in accordance with the present disclosure. The example process 1100 is an example in which a network node (eg, network node 110) performs operations associated with resource management for communication and sensing services.

[0185] like Fig.11 As shown, in some aspects, process 1100 may include receiving, from a first core network entity, a first request associated with initiation of a sensing service associated with a UE, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service (block 1110). For example, a network node (e.g., using Fig.13 The communication manager 150 and / or receiving component 1302 depicted in the figure can receive a first request associated with initiation of a sensing service associated with the UE from a first core network entity, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service, as described above. In some aspects, the first request includes information identifying one or more sensing session parameters associated with the sensing service.

[0186] like Fig.11 As further shown, in some aspects, process 1100 may include determining one or more resources for a sensing service based at least in part on one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node (block 1120). Fig.13 The communication manager 150 and / or determination component 1308 depicted in FIG. 1 may determine one or more resources for a sensing service based at least in part on one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node, as described above.

[0187] like Fig.11 As further shown, in some aspects, process 1100 may include sending information identifying one or more resources for sensing services to the UE (block 1130). Fig.13 The communication manager 150 and / or the sending component 1304 depicted in FIG. 1 may send information identifying one or more resources for the sensing service to the UE, as described above.

[0188] Process 1100 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.

[0189] In a first aspect, process 1100 includes receiving a second request including one or more communication session parameters from a second core network entity.

[0190] In a second aspect, alone or in combination with the first aspect, the first core network entity is an N-SMF, and the second core network entity is an SMF entity.

[0191] In a third aspect, alone or in combination with one or more of the first and second aspects, one or more resources for sensing services are associated with a first frequency range, and wherein one or more other resources for communication sessions are associated with a second frequency range.

[0192] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, determining one or more resources for a sensing service comprises determining one or more resources based at least in part on other resources associated with at least one other sensing service associated with at least one other UE.

[0193] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending one or more beam parameters to be used for a sensing service to a UE and based at least in part on one or more sensing session parameters.

[0194] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more resources used for the sensing service are joint communication and sensing resources associated with the communication session.

[0195] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1100 includes adjusting one or more sensing session parameters, and sending information indicating the adjustment of one or more sensing session parameters to at least one of the first core network entity or the second core network entity.

[0196] In an eighth aspect, alone or in combination with one or more of aspects one to seven, determining one or more resources comprises determining a first portion of joint communication and sensing resources for a sensing service; determining a second portion of joint communication and sensing resources for a communication session; and determining the first portion of the joint communication and sensing resources as one or more resources.

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

[0198] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a core network entity, or a core network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 1250. Communication manager 1250 may include one or more of mapping component 1208 or determining component 1210, etc.

[0199] In some aspects, the communication manager 1250 may receive a first request associated with initiation of a sensing service associated with the UE; receive one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request; and provide a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters. In some aspects, the communication manager 1250 may receive a first request associated with a communication session associated with the UE, wherein the first request is associated with one or more first communication session parameters; receive a second request to establish a virtual communication session associated with the UE from a second core network entity, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to the sensing service; and provide information indicating one or more first communication session parameters for the communication session and one or more second communication session parameters for the virtual communication session to the network node. Additionally or alternatively, the communication manager 1250 may perform one or more other operations described herein.

[0200] In some aspects, the apparatus 1200 may be configured to perform Figures 4 to 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig. 9 The process of 900 Fig.10 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the core network entity. Additionally or alternatively, Fig.12 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.

[0201] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 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 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the core network entity.

[0202] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 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 1206. In some aspects, the transmitting component 1204 may include combining Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the core network entity. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0203] The receiving component 1202 may receive a first request associated with initiation of a sensing service associated with the UE. The receiving component 1202 may receive one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request. The sending component 1204 may provide a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request including the one or more communication session parameters.

[0204] A mapping component 1208 can map one or more sensing session parameters to one or more communication session parameters.

[0205] The determining component 1210 can determine a communication service type for the virtual communication session based at least in part on the sensed session parameters.

[0206] The sending component 1204 can indicate to the second core network entity that the virtual communication session is associated with the communication service type.

[0207] The transmitting component 1204 can provide embedded radio level operational configuration information in a sensing session specific container to a network node associated with the UE.

[0208] The sending component 1204 can provide, to the network node, a third request to establish a sensing service between the network node and the UE.

[0209] The receiving component 1202 may receive a first request associated with a communication session associated with the UE, wherein the first request is associated with one or more first communication session parameters. The receiving component 1202 may receive a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service. The sending component 1204 may provide information indicating the one or more first communication session parameters for the communication session and the one or more second communication session parameters for the virtual communication session to the network node.

[0210] The receiving component 1202 can receive, from a second core network entity, radio level operational configuration information for a network node embedded in a sensing session specific container.

[0211] Transmitting component 1204 can provide radio level operational configuration information to a network node.

[0212] The receiving component 1202 can receive information indicative of one or more policies for managing the virtual communication session as a sensing service.

[0213] The sending component 1204 can provide, to the network node, sensing information indicating that the virtual communication session is for a sensing service to be established between the network node and the UE.

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

[0215] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include one or more of determining component 1308 or adjusting component 1310, as well as other examples.

[0216] In some aspects, the apparatus 1300 may be configured to perform Figures 4 to 8 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2Additionally 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.

[0217] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 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 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0218] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 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 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0219] The receiving component 1302 may receive, from a first core network entity, a first request associated with initiation of a sensing service associated with the UE, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service. The determining component 1308 may determine one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node. The sending component 1304 may send information identifying one or more resources for the sensing service to the UE.

[0220] Receiving component 1302 can receive a second request including one or more communication session parameters from a second core network entity.

[0221] Transmitting component 1304 can transmit, to the UE and based at least in part on the one or more sensing session parameters, one or more beam parameters to be used for the sensing service.

[0222] An adjustment component 1310 can adjust one or more sensing session parameters.

[0223] The sending component 1304 can send information indicating an adjustment to one or more sensing session parameters to at least one of the first core network entity or the second core network entity.

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

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

[0226] Aspect 1: A method of wireless communication performed by a first core network entity, the method comprising: receiving a first request associated with the initiation of a sensing service associated with a UE; receiving one or more sensing session parameters associated with the sensing service from at least one other core network entity and based at least in part on the first request; and providing a second request to establish a virtual communication session with the UE to a second core network entity and based at least in part on the sensing session parameters, the request comprising one or more communication session parameters.

[0227] Aspect 2: The method according to aspect 1, further comprising: mapping the one or more sensing session parameters to the one or more communication session parameters.

[0228] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the one or more sensing session parameters include at least one of the following: 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, a data rate parameter, or a latency parameter.

[0229] Aspect 4: The method according to any one of aspects 1 to 3, wherein the one or more communication session parameters include at least one of the following: a quality of service parameter, a SINR parameter, a data rate parameter or a latency parameter.

[0230] Aspect 5: The method according to any one of aspects 1 to 4, wherein the one or more sensing session parameters are based at least in part on at least one of: subscription information associated with the UE and the sensing service or policy information associated with the sensing service.

[0231] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first core network entity includes an N-SMF, and the second core network entity includes an SMF.

[0232] Aspect 7: The method according to any one of aspects 1 to 6, wherein the at least one other core network entity comprises at least one of the following: N-PCF or UDM.

[0233] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the first request is received from an AMF.

[0234] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the first request is associated with a sensing network slice indicating that the first request is for the sensing service.

[0235] Aspect 10: The method according to any one of aspects 1 to 9, wherein the first request is associated with a DNN or an APN indicating that the first request is for the sensing service.

[0236] Aspect 11: The method according to any one of aspects 1 to 10, wherein receiving the one or more sensing session parameters comprises: receiving information indicating one or more policies for managing the sensing service.

[0237] Aspect 12: The method according to aspect 11, wherein the information indicative of the one or more policies is based at least in part on information identifying the location of the UE.

[0238] Aspect 13: The method according to aspect 11, wherein the information indicative of the one or more policies is received from an N-PCF entity.

[0239] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method also includes: determining the communication service type of the virtual communication session based at least in part on the sensing session parameters; and indicating to the second core network entity that the virtual communication session is associated with the communication service type.

[0240] Aspect 15: The method according to Aspect 14, wherein the communication service type is associated with at least one of the following: V2X communication or UAV communication.

[0241] Aspect 16: The method according to any one of aspects 1 to 15, the method further comprising: providing a network node associated with the UE with embedded radio level operation configuration information in a sensing session specific container.

[0242] Aspect 17: The method according to any one of aspects 1 to 16, the method further comprising: providing a third request to a network node to establish the sensing service between the network node and the UE.

[0243] Aspect 18: The method according to aspect 17, wherein the third request includes information indicating whether the sensing service is for a radar service or a positioning service.

[0244] Aspect 19: The method according to aspect 17, wherein the third request includes information indicative of the one or more sensing session parameters.

[0245] Aspect 20: The method according to aspect 17, wherein the third request includes information indicating whether the sensing service is for UE-based sensing or network node-based sensing.

[0246] Aspect 21: The method according to aspect 17, wherein the third request includes information indicating a priority associated with the sensing service.

[0247] Aspect 22: A method of wireless communication performed by a first core network entity, the method comprising: receiving a first request associated with a communication session associated with a UE, wherein the first request is associated with one or more first communication session parameters; receiving a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service; and providing information indicating the one or more first communication session parameters for the communication session and the one or more second communication session parameters for the virtual communication session to a network node.

[0248] Aspect 23: According to the method according to Aspect 22, the method also includes: receiving radio level operation configuration information for the network node embedded in a sensing session specific container from the second core network entity; and providing the radio level operation configuration information to the network node.

[0249] Aspect 24: A method according to Aspect 23, wherein the radio level operation configuration information is associated with at least one sensing session parameter, and the at least one sensing session parameter includes at least one of the following: 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, a data rate parameter, or a latency parameter.

[0250] Aspect 25: The method according to any one of aspects 22 to 24, wherein the one or more second communication session parameters include at least one of the following: a quality of service parameter, a SINR parameter, a data rate parameter or a latency parameter.

[0251] Aspect 26: A method according to any one of Aspects 22 to 25, wherein the one or more second communication session parameters are based at least in part on at least one of: subscription information associated with the UE and the sensing service or policy information associated with the sensing service.

[0252] Aspect 27: The method according to any one of Aspects 22 to 26, wherein the first core network entity comprises an SMF, and the second core network entity comprises an N-SMF.

[0253] Aspect 28: A method according to any one of Aspects 22 to 27, wherein the first request is received from an AMF.

[0254] Aspect 29: A method according to any one of Aspects 22 to 28, wherein the second request is associated with a sensing network slice indicating that the second request is for the sensing service.

[0255] Aspect 30: The method according to any one of Aspects 22 to 29, wherein the second request is associated with a DNN or APN indicating that the second request is for the sensing service.

[0256] Aspect 31: The method according to any one of Aspects 22 to 30, further comprising: receiving information indicating one or more policies for managing the virtual communication session as the sensing service.

[0257] Aspect 32: The method according to any one of Aspects 22 to 31, wherein the second request is associated with information indicating that the virtual communication session is associated with a communication service type.

[0258] Aspect 33: The method according to Aspect 32, wherein the communication service type is associated with at least one of the following: V2X communication or UAV communication.

[0259] Aspect 34: The method according to any one of aspects 22 to 33, the method further comprising: providing, to the network node, sensing information indicating that the virtual communication session is for the sensing service to be established between the network node and the UE.

[0260] Aspect 35: The method according to Aspect 34, wherein the sensing information includes information indicating whether the sensing service is for a radar service or a positioning service.

[0261] Aspect 36: The method according to aspect 34, wherein the sensing information includes information indicative of one or more sensing session parameters.

[0262] Aspect 37: The method according to aspect 34, wherein the sensing information includes information indicating whether the sensing service is for UE-based sensing or network node-based sensing.

[0263] Aspect 38: The method according to aspect 34, wherein the sensing information includes information indicating a priority associated with the sensing service.

[0264] Aspect 39: A method of wireless communication performed by a network node, the method comprising: receiving a first request associated with initiating a sensing service associated with a UE from a first core network entity, wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service; determining one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node; and sending information identifying the one or more resources for the sensing service to the UE.

[0265] Aspect 40: The method according to aspect 39, the method further comprising: receiving a second request including the one or more communication session parameters from a second core network entity.

[0266] Aspect 41: The method according to aspect 40, wherein the first core network entity is an N-SMF and the second core network entity is an SMF.

[0267] Aspect 42: A method according to any one of Aspects 39 to 41, wherein the one or more resources used for the sensing service are associated with a first frequency range, and wherein the one or more other resources used for the communication session are associated with a second frequency range.

[0268] Aspect 43: A method according to any one of Aspects 39 to 42, wherein determining the one or more resources for the sensing service comprises determining the one or more resources based at least in part on other resources associated with at least one other sensing service associated with at least one other UE.

[0269] Aspect 44: The method according to any one of aspects 39 to 43, the method also includes: sending one or more beam parameters to be used for the sensing service to the UE and based at least in part on the one or more sensing session parameters.

[0270] Aspect 45: The method according to any one of aspects 39 to 44, wherein the one or more resources used for the sensing service are joint communication and sensing resources associated with the communication session.

[0271] Aspect 46: According to the method described in any one of Aspects 39 to 45, the method also includes: adjusting the one or more sensing session parameters; and sending information indicating the adjustment of the one or more sensing session parameters to at least one of the first core network entity or the second core network entity.

[0272] Aspect 47: A method according to any one of Aspects 39 to 46, wherein determining the one or more resources includes: determining a first part of the joint communication and sensing resources for the sensing service; determining a second part of the joint communication and sensing resources for the communication session; and determining the first part of the joint communication and sensing resources as the one or more resources.

[0273] Aspect 48: An apparatus for wireless communication at a device, the apparatus 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 21.

[0274] Aspect 49: An apparatus for wireless communication at a device, the apparatus 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 22 to 38.

[0275] Aspect 50: An apparatus for wireless communication at a device, the apparatus 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 39 to 47.

[0276] Aspect 51: A device for wireless communication, the device 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 1 to 21.

[0277] Aspect 52: An apparatus for wireless communication, the apparatus 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 22 to 38.

[0278] Aspect 53: A device for wireless communication, the device 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 39 to 47.

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

[0280] Aspect 55: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 22 to 38.

[0281] Aspect 56: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 39 to 47.

[0282] Aspect 57: 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 21.

[0283] Aspect 58: 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 22 to 38.

[0284] Aspect 59: 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 39 to 47.

[0285] Aspect 60: 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 21.

[0286] Aspect 61: 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 22 to 38.

[0287] Aspect 62: 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 39 to 47.

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

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

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

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

[0292] 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 want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", 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 first core network entity, the first core network entity comprising: one or more memories; as well as one or more processors coupled to the one or more memories, the one or more processors configured to: receiving a first request associated with initiation of a sensing service associated with a user equipment (UE); receiving, from at least one other core network entity and based at least in part on the first request, one or more sensing session parameters associated with the sensing service; as well as A second request to establish a virtual communication session with the UE is provided to a second core network entity and based at least in part on the sensed session parameters, the request including one or more communication session parameters.

2. The first core network entity according to claim 1, wherein the one or more processors are further configured to: The one or more sensing session parameters are mapped to the one or more communication session parameters.

3. The first core network entity of claim 1 , wherein the one or more sensing session parameters include at least one of: 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, Data rate parameters, or Delay parameter.

4. The first core network entity of claim 1 , wherein the one or more communication session parameters include at least one of: Quality of service parameters, Signal to Interference and Noise Ratio (SINR) parameter, Data rate parameters, or Delay parameter.

5. The first core network entity of claim 1 , wherein the one or more sensing session parameters are based at least in part on at least one of: subscription information associated with the UE and the sensing service, or Policy information associated with the sensing service.

6. The first core network entity of claim 1, wherein the first core network entity comprises a non-communication session management function (N-SMF) entity, and the second core network entity comprises a session management function (SMF) entity.

7. The first core network entity of claim 1 , wherein the at least one other core network entity comprises at least one of: A non-communication policy control function (N-PCF) entity, or Unified Data Management (UDM) entity.

8. The first core network entity of claim 1, wherein the first request is received from an Access and Mobility Management Function (AMF) entity.

9. The first core network entity of claim 1, wherein the first request is associated with a sensing network slice indicating that the first request is for the sensing service.

10. The first core network entity of claim 1, wherein the first request is associated with a dynamic network name (DNN) or an access point name (APN) indicating that the first request is for the sensing service.

11. The first core network entity of claim 1 , wherein to receive the one or more sensing session parameters, the one or more processors are configured to: Information indicative of one or more policies for managing the sensing service is received.

12. The first core network entity of claim 11, wherein the information indicative of the one or more policies is based at least in part on information identifying a location of the UE.

13. The first core network entity of claim 11, wherein the information indicative of the one or more policies is received from a non-communication policy control function (N-PCF) entity.

14. The first core network entity of claim 1, wherein the one or more processors are further configured to: determining a communication service type for the virtual communication session based at least in part on the sensed session parameters; and Indicating to the second core network entity that the virtual communication session is associated with the communication service type.

15. The first core network entity of claim 14, wherein the communication service type is associated with at least one of: Vehicle-to-everything (V2X) communications, or Unmanned Autonomous Vehicle (UAV) Communications.

16. The first core network entity of claim 1, wherein the one or more processors are further configured to: Embedded radio level operational configuration information in a sensing session specific container is provided to a network node associated with the UE.

17. The first core network entity of claim 1, wherein the one or more processors are further configured to: A third request is provided to a network node to establish the sensing service between the network node and the UE. 18 . The first core network entity according to claim 17 , wherein the third request comprises information indicating whether the sensing service is for a radar service or a positioning service.

19. The first core network entity of claim 17, wherein the third request comprises information indicative of the one or more sensing session parameters.

20. The first core network entity of claim 17, wherein the third request comprises information indicating whether the sensing service is for UE-based sensing or network node-based sensing.

21. The first core network entity of claim 17, wherein the third request comprises information indicating a priority associated with the sensing service.

22. A first core network entity, the first core network entity comprising: one or more memories; as well as one or more processors coupled to the one or more memories, the one or more processors configured to: receiving a first request associated with a communication session associated with a user equipment (UE), wherein the first request is associated with one or more first communication session parameters; receiving a second request from a second core network entity to establish a virtual communication session associated with the UE, wherein the second request is associated with one or more second communication session parameters, and wherein the virtual communication session corresponds to a sensing service; as well as Information indicative of the one or more first communication session parameters for the communication session and the one or more second communication session parameters for the virtual communication session is provided to a network node.

23. The first core network entity of claim 22, wherein the one or more processors are further configured to: receiving, from the second core network entity, radio level operational configuration information for the network node embedded in a sensing session specific container; and The radio level operational configuration information is provided to the network node.

24. The first core network entity of claim 22, wherein the first core network entity comprises a session management function (SMF) entity, and the second core network entity comprises a non-communication session management function (N-SMF) entity.

25. The first core network entity of claim 22, wherein the one or more processors are further configured to: Sensing information indicating that the virtual communication session is for the sensing service to be established between the network node and the UE is provided to the network node.

26. The first core network entity of claim 25, wherein the sensing information comprises information indicative of one or more sensing session parameters.

27. A network node, the network node comprising: one or more memories; as well as one or more processors coupled to the one or more memories, the one or more processors configured to: receiving, from a first core network entity, a first request associated with initiation of a sensing service associated with a user equipment (UE), wherein the first request includes information identifying one or more sensing session parameters associated with the sensing service; determining one or more resources for the sensing service based at least in part on the one or more sensing session parameters and one or more communication session parameters associated with a communication session between the UE and the network node; as well as Information identifying the one or more resources for the sensing service is sent to the UE.

28. The network node of claim 27, wherein the one or more processors are further configured to: A second request including the one or more communication session parameters is received from a second core network entity.

29. The network node of claim 27, wherein to determine the one or more resources, the one or more processors are configured to: determining a first portion of joint communication and sensing resources for the sensing service; determining a second portion of the joint communication and sensing resources for the communication session; as well as The first portion of the joint communication and sensing resources is determined as the one or more resources.

30. A method of wireless communication performed by a first core network entity, the method comprising: receiving a first request associated with initiation of a sensing service associated with a user equipment (UE); receiving, from at least one other core network entity and based at least in part on the first request, one or more sensing session parameters associated with the sensing service; as well as A second request to establish a virtual communication session with the UE is provided to a second core network entity and based at least in part on the sensed session parameters, the second request including one or more communication session parameters.

Images