Sensor service selection and configuration

Abstract

Various aspects of this disclosure generally relate to wireless communication. Some aspects more specifically relate to the selection and configuration of sensing units (SUs) associated with sensing services. In some aspects, a network function entity can receive a sensing request. The network function entity can use information indicated by the sensing request to determine one or more sensing parameters. In some aspects, the network function entity can use one or more sensing parameters and the sensing capabilities of the corresponding SU to identify or select one or more SUs to fulfill the sensing request. In some aspects, the network function entity can communicate with one or more repositories or network nodes to identify one or more SUs. The network node can use one or more sensing parameters to determine a sensing configuration. The network node can transmit, and the SU can receive, the sensing configuration. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods associated with the selection and configuration of sensing units related to sensing services. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution.

[0004] In some examples, wireless communication networks may support sensing services such as Integrated Sensing and Communication (ISAC) services. ISAC uses the same systems and infrastructure used for wireless communication to provide sensing capabilities (e.g., RF sensing capabilities). One or more devices in the wireless communication network (which may be referred to as sensing units (SUs)) can perform RF sensing via the resources of the wireless communication network (e.g., using one or more RF signals). RF sensing enables wireless communication devices to acquire information about the characteristics of the environment and / or objects within the environment. In some examples, RF sensing can be used to determine the distance (range), angle, and / or instantaneous linear velocity of an object, etc.

[0005] Sensing services can be associated with one or more Service Units (SUs) configured to perform RF sensing to fulfill one or more sensing requests. In a given wireless communication network, a variety of different devices can be capable of acting as SUs. However, different devices can be associated with different capabilities, different locations, and / or different criteria for when a device can be configured to perform RF sensing. For example, a User Equipment (UE) can be associated with RF sensing capabilities different from those of a network node. Additionally, the introduction of RF sensing as an ISAC service introduces additional considerations for configuring a given device as an SU. For example, network load information, link quality, and / or the availability of wireless communication resources may influence the configuration decisions for SUs in a wireless communication network. Furthermore, when RF sensing technology is introduced as a new system capability, new considerations are needed regarding authorization for service and operational access, data confidentiality, data integrity, and / or user privacy to ensure these aspects are taken into account when deriving sensing service requirements.

[0006] Therefore, the discovery and configuration of Subscriber Units (SUs) within a wireless communication network can be a complex task, requiring coordination among several different network entities and / or network nodes. Currently, no process or protocol is defined for SU discovery and configuration, which can result in one or more SUs failing to register or be identified (e.g., thus not participating in the sensing services provided by the wireless communication network). Additionally, this can lead to one or more SUs being configured to perform sensing operations that the SUs themselves cannot perform. For example, the wireless communication network may currently not support coordinating RF sensing between multiple network nodes and / or UEs, obtaining RF sensing capabilities from multiple network nodes and / or UEs, coordinating configuration and authorization for RF sensing performed by multiple network nodes and / or UEs, and / or providing mechanisms for providing devices with RF sensing capabilities with information indicating which network entity or network function SU to send sensing data to, etc. Summary of the Invention

[0007] Some aspects described herein relate to a Sensing Management Function (SnMF) entity for wireless communication. The SnMF entity may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the SnMF entity to receive a sensing request indicating one or more request parameters. The processing system may also be configured to cause the SnMF entity to send to one or more network nodes an indication of one or more sensing parameters for the sensing request, the network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the request parameters.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the network node to receive from a SnMF entity an indication of one or more sensing parameters associated with a sensing request. The processing system may also be configured to cause the network node to send a sensing configuration to one or more sensing units (SUs), the sensing configuration including one or more configuration parameters associated with the sensing parameters.

[0009] Some aspects described herein relate to a receiver (SU) for wireless communication. The SU may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the SU to receive a sensing configuration via one or more Radio Resource Control (RRC) communications, the sensing configuration indicating a sensing session associated with the sensing configuration. The processing system may be configured to cause the SU to receive communications indicating one or more actions to be performed for the sensing session. The processing system may be configured to cause the SU to perform the one or more actions associated with the sensing configuration and the sensing session.

[0010] Some aspects described herein relate to a method for wireless communication by a SnMF entity. The method may include receiving a sensing request indicating one or more request parameters. The method may include sending to one or more network nodes an indication of one or more sensing parameters for the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

[0011] Some aspects described herein relate to a method for wireless communication by a network node. This method may include receiving from a SnMF entity an indication of one or more sensing parameters associated with a sensing request. The method may also include sending a sensing configuration to one or more SUs, the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters.

[0012] Some aspects described herein relate to a method for wireless communication by a SU. The method may include receiving a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration. The method may include receiving communications indicating one or more actions to be performed for the sensing session. The method may include performing the one or more actions for the sensing configuration in association with the sensing session.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a SnMF entity. When executed by one or more processors of the SnMF entity, the set of instructions enables the SnMF entity to receive a sensing request indicating one or more request parameters. When executed by one or more processors of the SnMF entity, the set of instructions enables the SnMF entity to send to one or more network nodes an indication of one or more sensing parameters for the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to receive indications from a SnMF entity for one or more sensing parameters associated with a sensing request. When executed by one or more processors of the network node, the set of instructions enables the network node to send a sensing configuration to one or more SUs, the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a Substation (SU). When executed by one or more processors of the SU, the set of instructions enables the SU to receive a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration. When executed by one or more processors of the SU, the set of instructions enables the SU to receive communications instructing one or more actions to be performed for the sensing session. When executed by one or more processors of the SU, the set of instructions enables the SU to perform the one or more actions associated with the sensing configuration and the sensing session.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a sensing request indicating one or more request parameters. The apparatus may also include components for transmitting to one or more network nodes an indication of one or more sensing parameters for the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a SnMF entity an indication of one or more sensing parameters associated with a sensing request. The apparatus may also include components for transmitting a sensing configuration to one or more SUs, the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration. The apparatus may include components for receiving communications indicating one or more actions to be performed for the sensing session. The apparatus may include components for performing the one or more actions associated with the sensing configuration in connection with the sensing session.

[0019] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0020] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0021] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

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

[0024] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0025] Figure 4A and Figure 4B This is a diagram illustrating an example of radio frequency (RF) sensing according to the present disclosure.

[0026] Figure 5 This is an example of a network function configured to provide sensing services according to this disclosure.

[0027] Figure 6 This is an example of a control plane architecture associated with sensing services according to this disclosure.

[0028] Figure 7 This is an example of a Sensing Management Function (SnMF) entity associated with a sensing service according to this disclosure.

[0029] Figure 8 This is a diagram illustrating example operations associated with sensing service selection and configuration according to this disclosure.

[0030] Figure 9 This is a diagram illustrating an example sensing configuration according to this disclosure.

[0031] Figure 10 This is a diagram illustrating an example sensing session according to this disclosure.

[0032] Figure 11 This is a flowchart illustrating an example process for supporting sensor service selection and configuration performed, for example, at a SnMF entity or a device of a SnMF entity, according to this disclosure.

[0033] Figure 12 This is a flowchart illustrating an example process for supporting sensor service selection and configuration, performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0034] Figure 13 This is a flowchart illustrating an example process for supporting sensor service selection and configuration performed, for example, at a device in a SU or sensing unit, according to this disclosure.

[0035] Figure 14 This is a diagram of an example device for wireless communication that supports sensor service selection and configuration according to this disclosure.

[0036] Figure 15 This is a diagram of an example device for wireless communication that supports sensor service selection and configuration according to this disclosure.

[0037] Figure 16 This is a diagram of an example device for wireless communication that supports sensor service selection and configuration according to this disclosure. Detailed Implementation

[0038] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0039] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0040] Because radio frequency (RF) sensing operations are performed using wireless communication network resources, it can be difficult to correctly configure a sensing unit (SU) to perform RF sensing operations in response to a sensing request. For example, a sensing request may indicate one or more sensing parameters. However, the SU can be configured using wireless communication configurations, such as Radio Resource Control (RRC) configurations. For example, a network node or network function entity can configure the SU to perform RF sensing operations via RRC configuration. However, the RRC configuration may use configuration parameters different from the sensing parameters indicated by the sensing request (e.g., there may be no RRC parameter corresponding to the sensing parameters). Therefore, the SU may be configured to perform RF sensing operations that do not meet or conform to the sensing parameters indicated by the sensing request, thereby consuming resources associated with performing RF sensing operations that do not meet or conform to the sensing parameters (e.g., processing resources, network resources, and / or power resources), and / or providing inaccurate sensing results in response to the sensing request, etc. Additionally, a network function entity configured to manage sensing operations may not have information indicating the current network condition. Therefore, the network function entity may not be able to determine the optimal RRC configuration for the SU (e.g., considering the current network condition).

[0041] The various aspects as a whole involve the selection and configuration of SUs associated with sensing services. Some aspects are more specifically related to the selection and / or configuration of SUs associated with Integrated Sensing and Communication (ISAC) services. In some aspects, network function entities (referred to herein as Sensing Management Function (SnMF) entities) may be configured to interface with one or more other network function entities (such as Access and Mobility Function (AMF) entities) to perform one or more control operations for sensing services.

[0042] In some respects, the SnMF entity can receive sensing requests. A sensing request may indicate high-level service parameters for the sensing request, such as the sensing area, the time to perform sensing, and / or one or more types of sensing to be performed. The SnMF entity may use, based on, or otherwise associate with the information indicated by the sensing request to determine one or more sensing parameters. One or more sensing parameters may indicate sensing configuration requirements for a SU to be configured to perform RF sensing operations in accordance with a sensing request. In some respects, one or more sensing parameters may include detection distance parameters, Doppler range parameters, one or more quality of service (QoS) parameters, one or more sensing reporting parameters, and / or one or more adaptive reconfiguration parameters, etc.

[0043] In some aspects, a SnMF entity may identify or select one or more SUs to fulfill a sensing request by using, based on, or otherwise associated with one or more sensing parameters and the sensing capabilities of the corresponding SU. In some aspects, a SnMF entity may communicate with one or more repositories (e.g., one or more Sensing Repositories (SRs)) to identify one or more SUs. For example, an SR may be a network function entity configured to store registration information (e.g., location and one or more sensing capabilities) of the corresponding SU. The SR may send, and the SnMF entity may receive, indications for one or more SUs capable of performing RF sensing operations based on one or more sensing parameters. In some other aspects, a SnMF entity may communicate with one or more network nodes (e.g., one or more Radio Access Network (RAN) nodes) to identify one or more SUs. For example, a network node may store the sensing capabilities of the corresponding SUs with which it has established a communication connection. The network node may use, based on, or otherwise associated with one or more sensing parameters and the sensing capabilities of the corresponding SU to select one or more SUs. In some aspects, the network node may send, and the SnMF entity may receive, indications for one or more SUs. In other respects, network nodes can configure one or more SUs based on one or more sensing parameters (for example, without sending instructions for one or more SUs to the SnMF entity).

[0044] Network nodes can determine a sensing configuration using, based on, or otherwise associated with one or more sensing parameters. For example, the sensing configuration could be an RRC configuration. A network node can translate one or more sensing parameters into one or more RRC parameters. For instance, a network node can use information indicating the current network condition to determine an optimized RRC configuration suitable for enabling one or more SUs to perform RF sensing operations based on one or more sensing parameters. The network node can send, and the SUs can receive, the sensing configuration (e.g., via RRC signaling).

[0045] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to ensure that one or more network functional entities (e.g., SnMF entities, AMF entities, and / or SR entities) and / or network nodes select one or more SUs to fulfill a sensing request, which one or more SUs are capable of operating according to one or more sensing parameters associated with a given sensing request. This ensures that the SU is configured to perform RF sensing operations supported by the SU. By providing sensing parameters to the network node, the described techniques can be used to enable the network node to configure a sensing configuration for one or more SUs that satisfies the sensing parameters and also takes into account the current network conditions. For example, enabling the network node to determine an RRC configuration suitable for conforming to or satisfying the sensing parameters and also optimized for the current network conditions (e.g., because the SnMF entity may not have access to information indicating the current network conditions).

[0046] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0047] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0048] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0049] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific radio access technology (RAT) (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RAT, 5G / NR RAT, and / or 6G RAT, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0050] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0052] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0053] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0054] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0055] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0056] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a pico cell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0057] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0058] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0059] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0060] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0061] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In such examples, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0062] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0063] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0064] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0065] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0066] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning, etc., within the wireless communication network 100. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between UEs 120 in the first category and UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0067] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0068] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0069] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0070] In some examples, wireless communication network 100 may support Integrated Sensing and Communication (ISAC) services. ISAC can refer to a system that uses the same systems and infrastructure used for communication (e.g., wireless communication network 100) to provide sensing capabilities (e.g., RF sensing capabilities). ISAC may sometimes be referred to as Joint Communications and Radar (JCR). One or more devices in wireless communication network 100 (such as UE 120, network node 110, and / or SU 160) may perform RF sensing via wireless communication network 100 (e.g., using one or more RF signals). RF sensing is a technique that enables wireless communication devices to acquire information about the characteristics of the environment and / or objects within the environment. RF sensing uses RF signals to determine the distance (range), angle, and / or instantaneous linear velocity of an object. RF sensing can provide a range of functionalities for wireless communication devices, such as object detection, object recognition (e.g., vehicles, humans, or animals), object tracking, environmental monitoring, motion detection, high-accuracy positioning, health monitoring, immersive XR applications, home monitoring, weather monitoring, vehicle operation (e.g., maneuvering, navigation, and / or parking), pedestrian and / or obstacle detection on roads and / or railways, unmanned aerial vehicle (UAV) operation (e.g., UAV intrusion detection, UAV tracking, and / or collision avoidance), industrial operation (e.g., automated guided vehicles (AGVs), automated robots, and / or pedestrian detection), tracking, and / or activity recognition.

[0071] RF sensing can include communication-assisted sensing and / or sensing-assisted communication. Communication-assisted sensing can refer to a wireless communication device (such as the SU 160) using one or more hardware components and / or radio resources associated with communication to perform RF sensing. For example, the SU 160 can use RF signals (e.g., NR RF signals or other RF signals associated with wireless communication) to obtain information indicating the characteristics of the environment and / or objects within the environment. Sensing-assisted communication can refer to a wireless communication device using the sensing results to perform one or more communication operations. For example, the sensing results can improve communication performance, such as by enabling more accurate beamforming, faster beam fault recovery, and / or reducing channel state information (CSI) tracking overhead.

[0072] For example, wireless communication network 100 may include one or more SU 160s. SU 160 may include UE 120, network node 110, TRP, IAB node, RAN node, and / or another wireless communication device capable of performing RF sensing. In some examples, SU 160 may acquire sensing data (sometimes referred to as 3GPP sensing data, 5G wireless sensing data, 6G wireless sensing data, or wireless sensing data) via radio signals. Additionally or alternatively, SU 160 may acquire sensing data via one or more sensors (such as cameras, video recorders, light detection and ranging (LiDAR) sensors, radar and / or sonar sensors, etc.). For example, SU 160 may acquire sensing data via Wi-Fi sensing, radar sensing, and / or another type of sensing. Sensing data acquired via sensors (sometimes referred to as non-3GPP sensing data) may be used by SU 160 (or another device) to determine the characteristics of objects and / or the characteristics of the environment. Non-3GPP sensing data may be used to achieve improved sensing results from wireless sensing performed by SU 160.

[0073] Wireless communication network 100 may include one or more network nodes 170. Network node 170 may include core network nodes, core network entities, and / or core network functions, etc. Network node 170 may include SnMF entities, AMF entities, gateways, network repository functions (e.g., one or more SRs), etc. The SnMF entity may perform one or more operations for configuring, managing, and / or maintaining sensor configurations for one or more sensing requests. For example, network node 170 may receive a sensing request from a client device (e.g., a server device or a sensing client) and configure one or more SU160s to perform RF sensing to obtain sensing data based on the sensing request, as described in more detail elsewhere herein. Figure 1 As shown, network node 170 can communicate with SU 160 (e.g., directly and / or via network node 110) to configure and / or manage RF sensing operations.

[0074] In some aspects, SU 160 may include a communication manager 140 or a communication manager 150. As described in more detail elsewhere herein, the communication manager 140 or the communication manager 150 may receive a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration; receive communications indicating one or more actions to be performed for the sensing session; and perform one or more actions for the sensing configuration in association with the sensing session. Additionally or alternatively, the communication manager 140 or the communication manager 150 may perform one or more other operations described herein.

[0075] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive indications from SnMF entities (e.g., network node 170) for one or more sensing parameters associated with a sensing request; and send sensing configurations to one or more SUs, the sensing configurations including one or more configuration parameters associated with the one or more sensing parameters. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0076] In some aspects, network node 170 (e.g., SnMF entity) may include communication manager 180. As described in more detail elsewhere herein, communication manager 180 may receive a sensing request indicating one or more request parameters; and send indications to one or more network nodes for one or more sensing parameters used in the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters. Additionally or alternatively, communication manager 180 may perform one or more other operations described herein.

[0077] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0078] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0079] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as referring to a combination of... Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0080] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to mean any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0081] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0082] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0083] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0084] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0085] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0086] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0087] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0088] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0089] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0090] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0091] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0092] Modems 254a to 254u can transmit uplink signal sets (e.g., via corresponding sets of antennas 252) R One uplink signal or U Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0093] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0094] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0095] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0096] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0097] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in, the one or more network nodes. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0098] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0099] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. 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 RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0100] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0101] The non-RT RIC 350 may include or implement logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0102] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0103] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with sensing service selection and configuration, or perform one or more operations associated with sensing service selection and configuration, as described in more detail elsewhere herein. For example, the controller / processor of network node 170, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, ... Figure 2 Any other component, CU 310, DU 330, or RU 340 can (alone or in combination with one or more other processors) perform or direct, for example... Figure 11 Process 1100 Figure 12 Process 1200 Figure 13The operation of process 1300 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 170, network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 The process 1300 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0104] In some aspects, network node 170 includes components for receiving a sensing request indicating one or more request parameters; and / or components for sending indications to one or more network nodes for the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters. Components enabling network node 170 to perform the operations described herein may include, for example, one or more of a communication manager 180, a transmit processor, a TX MIMO processor, a modem, an antenna, a MIMO detector, a receive processor, a controller / processor, a memory, or a scheduler.

[0105] In some aspects, network node 110 includes components for receiving indications from a SnMF entity for one or more sensing parameters for a sensing request; and / or components for sending sensing configurations to one or more SUs, the sensing configurations including one or more configuration parameters associated with the one or more sensing parameters. Components enabling network node 110 to perform the 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.

[0106] In some aspects, SU 160 includes components for receiving a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration; components for receiving communications indicating one or more actions to be performed for the sensing session; and / or components for performing one or more actions for the sensing configuration in association with the sensing session. In some aspects, components for SU 160 to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for SU 160 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0107] Figure 4A and Figure 4B This is a diagram illustrating an example of RF sensing according to this disclosure. Wireless communication signals (e.g., RF signals configured to carry OFDM symbols) transmitted between UE 120 and network node 110 can be reused for RF sensing. RF sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, enabling contactless / device-free interaction with devices / systems, etc. "RF sensing" can be radar operation performed by wireless communication devices (such as UEs, network entities, or another device (such as wireless local area network (WLAN) access points)) using wireless communication signals.

[0108] RF sensing can also be referred to as environmental sensing, radar sensing, WLAN sensing, Wi-Fi sensing, and / or wireless sensing. The wireless communication signal used to perform RF sensing can be a cellular communication signal (e.g., LTE, NR, and / or 6G signal) or a WLAN signal (e.g., a Wi-Fi signal). As an example, the wireless communication signal can be an OFDM waveform as used in wireless communication network 100. High-frequency communication signals (such as millimeter-wave signals) can be advantageous for use as RF sensing signals because higher frequencies provide more accurate range (e.g., distance) detection and / or motion detection. As another example, a WLAN signal (e.g., a WLAN or Wi-Fi signal that would otherwise be used for wireless communication) can be used to perform RF sensing (e.g., to save power compared to using a higher frequency range signal). In such examples, RF sensing can be referred to as WLAN sensing or Wi-Fi sensing.

[0109] RF sensing can be performed using various frequency bands or ranges, such as millimeter wave bands or sub-6 GHz bands. In some examples, wireless communication devices performing RF sensing may sequentially use different frequencies (e.g., first using sub-6 GHz frequencies, then using millimeter wave frequencies) to change resolution (e.g., from coarse to fine), change detection range (e.g., from large to narrow), and / or change power consumption (e.g., from low to high), etc.

[0110] like Figure 4A and Figure 4B As shown, one or more SUs can detect and / or monitor target objects by sending and / or measuring wireless communication signals. Figure 4A An example of a monocentric sensing 400 is depicted. For example, one or more units (SUs) may be included in a wireless communication system 410 (such as a wireless communication network 100). A sensing transmitter 415 and a sensing receiver 420 may transmit RF signals (e.g., wireless communication signals) to perform RF sensing. In some examples, the sensing transmitter 415 and the sensing receiver 420 may be co-located, such as within a single SU (e.g., as in...). Figure 4A (As depicted). An example in which the sensing transmitter 415 and the sensing receiver 420 are co-located can be referred to as "monobase sensing". Figure 4B An example of a bistatic sensing 405 is depicted. For example, the sensing transmitter 415 and the sensing receiver 420 may not be co-located (e.g., as shown in the image). Figure 4B (As depicted). For example, the sensing transmitter 415 and the sensing receiver 420 may be included in a separate device, such as in a separate unit. An example in which the sensing transmitter 415 and the sensing receiver 420 are not co-located (e.g., included in different entities) may be referred to as "bistatic sensing". In some examples, RF sensing may be associated with obtaining sensor data indicating characteristics of the target object 425. In other examples, RF sensing operation may include multiple sensing transmitters 415 and / or multiple sensing receivers 420 (e.g., referred to as "multistatic sensing").

[0111] like Figure 4A and Figure 4BAs shown, the sensing transmitter 415 can transmit one or more signals 430. The one or more signals 430 can be RF signals, wireless communication signals, OFDM signals, and / or sensing reference signals, etc. One or more signals can be reflected from the target object 425, resulting in a reflection 435 of the signal 430. The reflection 435 can be a reflection of the signal 430, a refraction of the signal 430, a diffraction of the signal 430, and / or a deflected version of the signal 430, etc. The sensing receiver 420 can receive and / or detect the reflection 435. The sensing receiver 420 can perform one or more measurements on the reflection 435 to obtain sensing data 440. The sensing data 440 can include information indicating one or more characteristics of the target object 425. For example, the sensing data 440 can include signal strength (e.g., RSRP), received raw signal samples, channel delay distribution, one or more Doppler measurements (e.g., Doppler per channel tap), CSI, CQI, time delay measurements, and / or angle of arrival (AoA) (e.g., AoA per channel tap), etc.

[0112] like Figure 4A and Figure 4B As shown, sensing data 440 can be used to perform sensing processing 445 to obtain sensing result 450. In some examples, a SU (e.g., a SU including sensing receiver 420) can perform sensing processing 445. In such examples, the SU can send sensing result 450 to network node 110. In other examples, another device (such as network node 110) can perform sensing processing 445. In such examples, the SU (e.g., a SU including sensing receiver 420) can send sensing data and network node 110 can receive sensing data 440. Sensing result 450 may include information about one or more characteristics of target object 425. For example, sensing result 450 may include location information, velocity information, sensing resolution, object detection information, and / or other information determined using transmitted data 440. Sensing result 450 may be provided to sensing service 455 of wireless communication system 410. Sensing service 455 may include one or more core network nodes or entities, such as one or more network nodes 170. For example, sensing service 455 may include SnMF entities as described in more detail elsewhere herein. Sensing service 455 may provide sensing result 460 to client device 465. Sensing result 460 may be sensing result 450 or may be based on sensing result 450. Client device 465 may be server device or an application running on the device. For example, client device 465 may provide a sensing request to sensing service 455. Sensing service 455 may configure, manage and / or otherwise maintain sensing operations for fulfilling sensing requests (e.g., in a manner similar to that described herein).

[0113] Potential use cases for RF sensing include health monitoring (such as heart rate detection and / or respiratory rate monitoring), gesture recognition (such as human activity recognition, keystroke detection and / or sign language recognition), contextual information acquisition (such as location detection / tracking, orientation finding and / or distance estimation), and / or automotive radar (such as intelligent cruise control and / or collision avoidance).

[0114] Similar to conventional radar (e.g., frequency modulated continuous waveform (FMCW) radar), signal 430 can be used to estimate the range (e.g., range), velocity (e.g., Doppler spread), and / or angle (e.g., AoA) of target object 425. Unlike conventional radar, RF sensing can utilize both RF sensing measurements and wireless communication using a PHY layer. Signal 430 can be transmitted within a beam (e.g., using beamforming) and can be reflected from nearby objects within the beam. A portion of the transmitted RF signal is reflected back to sensing receiver 420, reflection 435 (e.g., via reflection of the transmitted signal).

[0115] In some examples, OFDM waveforms can be used for both wireless communication (e.g., via wireless networks) and RF sensing. To use an OFDM waveform as a signal for RF sensing, a specific reference signal may be required, which will be referred to herein as a sensing reference signal. RF sensing performance (e.g., resolution and maximum values ​​of range, velocity, and / or angle) can depend on the design of the sensing reference signal. For example, for gesture recognition use cases, a coarse range / velocity estimate may be sufficient for RF sensing. That is, it may be sufficient for the wireless communication device to detect a movement pattern relative to the current location of a target object 425 (e.g., a user's hand or head). In such examples, a low-density (e.g., sparse) sensing reference signal with short wavelengths and narrow bandwidth may be sufficient to provide the necessary range and velocity resolution. For vibration detection use cases, such as for respiratory monitoring, accurate Doppler estimation may be important, while accurate range estimation may be less important. In such examples, a high-density sensing reference signal with a long duration in the time domain may be beneficial. For location detection use cases, such as for object detection, accurate distance estimation may be important, while accurate Doppler estimation may be less important. In such examples, a high-density broadband sensing reference signal in the frequency domain can be beneficial. Therefore, network entities can configure one or more sensing reference signals to improve RF sensing performance, depending on the use case of RF sensing. In some examples, the sensing reference signal may be a sounding reference signal (SRS), a wireless communication reference signal, or a WLAN signal, etc.

[0116] Figure 5This is an example of a network function 500 configured to provide sensing services according to this disclosure. Network function 500 enables communication via data network 505 and RAN 510. Network function 500 may be included in a 5G core network, a 6G core network, a next-generation (NG) core network, or another type of core network. RAN 510 may be a wireless communication network 100. Data network 505 may include one or more wired and / or wireless data networks. For example, data network 505 may include an IP Multimedia Subsystem (IMS), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a private network (such as an enterprise intranet), an ad hoc network, the Internet, a fiber-optic-based network, a cloud computing network, a third-party service network, an operator service network, and / or combinations of these or other types of networks.

[0117] Network function 500 may include example functional architectures in which the systems and / or methods described herein can be implemented. For example... Figure 5 As shown, network function 500 may include one or more functional elements (e.g., one or more functions or entities) configured to provide sensing services 515 (e.g., RF sensing services or ISAC services). For example, core network 505 may include SnMF entity 520. SnMF entity 520 may be configured to perform SU discovery, SU configuration, collection of sensing data from one or more SUs, processing of sensing data, and / or opening of sensing results, etc. Network function 500 may include one or more sensing stores (SRs) 525. SR 525 may be a store configured to store information about one or more SUs (such as SU location and / or SU capabilities). In some examples, one or more SRs 525 may include a UE sensing store configured to store information about UEs capable of operating as SUs (e.g., configured to operate in RAN 510). Additionally, one or more SRs 525 may include a TRP sensing store configured to store information about TRPs and / or network nodes capable of operating as SUs (e.g., configured to operate in RAN 510). In some examples, SR 525 may include information about both the UE and TRP capable of operating as a SU. In some examples, one or more SR 525s may be a dedicated service within SnMF 520. In other examples, one or more SR 525s may be part of another network function, such as AMF or Network Storehouse Function (NRF) 545. In other examples, SR 525 may be a standalone network function. Network function 500 may include sensor data function 530. Sensor data function 530 may be configured to perform processing of sensor data (e.g., collected via one or more SUs in RAN 510) to produce sensing results as described in more detail elsewhere herein.

[0118] Network function 500 may include one or more RF sensors 535 configured to acquire sensor data. The one or more RF sensors 535 may include cameras, LiDAR sensors, radar sensors, sonar sensors, and / or Wi-Fi sensors, etc. The one or more RF sensors 535 may be referred to as non-3GPP sensors. Network function 500 may include a service discovery function 540. Service discovery function 540 may be configured to store information about one or more services supported by network function 500 and / or RAN 510. In some examples, service discovery function 540 may be configured to (e.g., to provide indications to one or more devices in RAN 510, such as one or more network nodes 110) of one or more services supported by network function 500, such as the sensing services described herein. For example, service discovery function 540 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. Service discovery function 540 may also be referred to as a Network Opening Function (NEF).

[0119] Network function 500 may include NRF 545. NRF 545 may be configured as a centralized repository for one or more network functions supported by network function 500 and / or RAN 510. For example, other functional elements of network function 500 may access NRF 545 to obtain information on functions or services provided by network function 500, such as the sensing services described herein. Network function 500 may include topology entity 550. Topology entity 550 may be configured to store and / or manage information on network topology, such as the topology of RAN 510. Network function 500 may include capability entity 555. Capability entity 555 may store information indicating, for example, the capabilities of a corresponding node or device (e.g., in RAN 510). Network function 500 may include a network data analysis function (NWDAF) 560. NWDAF 560 may include one or more devices that collect information associated with UE 120, SU, and / or RAN 510. NWDAF 560 may perform analyses based on the collected information. Different parts of network function 500 can be subscribed to receive analysis updates from NWDAF 560. In some examples, sensor data function 530 may be a component of NWDAF 560. Network function 500 may include data function entity 565. Data function entity 565 may be configured to determine, acquire, and / or provide data for RAN 510.

[0120] Network function 500 may include Figure 5Other functional elements not described herein include Network Slice Selection Function (NSSF), Network Open Function (NEF), Authentication Server Function (AUSF), Unified Data Management (UDM) component, Policy Control Function (PCF), Application Function (AF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and / or User Plane Function (UPF), etc. Figure 5 As shown, the functional elements of network function 500 can communicate via message bus 570. Message bus 570 can be a logical communication structure and / or a physical communication structure for communication between functional elements. Therefore, message bus 570 can allow communication between two or more functional elements, whether logical (e.g., using one or more application programming interfaces (APIs) and / or physical (e.g., using one or more wired and / or wireless connections).

[0121] Figure 6 This is an example of a control plane architecture 600 associated with sensing services according to this disclosure. For example... Figure 6 As shown, the control plane architecture 600 may include a client device 605. The client device 605 may be a location service (LCS) client or a sensing service client. The client device 605 can provide sensing requests associated with the sensing service.

[0122] Control plane architecture 600 may include sensing gateway 610. Sensing gateway 610 may be configured as a gateway between client device 605 and core network (such as network function 500). Sensing gateway 610 may implement one or more network functions, such as traffic routing, policy enforcement, charging, quality of service (QoS) management, and / or security. For example, sensing gateway 610 may route sensing requests from client device 605 to AMF 615 and / or SnMF 620. In other examples, AMF 615 may route sensing requests to the appropriate SnMF 620. Sensing gateway 610 and AMF 615 may communicate via an interface (shown as an NL2 interface). AMF 615 may communicate with one or more SnMF 620s. For example, AMF 615 and SnMF 620 may communicate via an interface such as an NLx interface (e.g., defined by a wireless communication standard such as 3GPP or otherwise fixed). SnMF can be configured to operate as a trusted application service provider (ASP) entity to supply non-3GPP-RF sensors (in... Figure 6 It is shown as Application Function (AF) 640 in the middle.

[0123] The control plane architecture 600 may include one or more SR 625s. As described elsewhere herein, the SR 625 may be a logical control function configured to store the identity, location, and / or capabilities of available Units (SUs) within the wireless communication network. The SR 625 may provide indications of available SUs to one or more SnMF 620s (e.g., to enable available SUs). In some examples, the functionality of the SR may be provided by another network function (such as AMF 615, NRF, etc.). Figure 6 (not shown in the diagram) and / or SnMF 620) are used. The control plane architecture 600 may include a UDM 630. The UDM 630 may include one or more devices for storing user data and profiles in the wireless telecommunications system. In some respects, the UDM 630 may be used for fixed access and / or mobile access, etc., in the core network.

[0124] The control plane architecture may include one or more UEs 120 and / or one or more network nodes 110. As described elsewhere herein, UE 120 may be configured to operate as a SU for sensing services (e.g., by SnMF 620, AMF 615, and / or network node 110). Additionally, network node 110 may be configured to operate as a SU for sensing services (e.g., an application function (AF) SU) (e.g., by SnMF 620, AMF 615, and / or another network node 110). The control plane architecture may include a NEF 635 communicating with one or more AFs 640. AF 640 may be an RF sensor, such as a camera, LiDAR sensor, radar sensor, sonar sensor, Wi-Fi sensor, or another non-3GPP RF sensor.

[0125] Figure 7 This is an example of a SnMF entity 700 associated with a sensing service according to this disclosure. SnMF entity 700 may include one or more functional components configured to perform operations associated with the sensing service, as described herein. For example, SnMF entity 700 may be configured to perform SU discovery and / or configuration, sensing data collection, sensing data processing, and / or opening of sensing results, etc. SnMF entity 700 may include a sensing management component 705, a processing component 710, a UE sensing store 715, and / or a TRP sensing store 720, etc.

[0126] Sensing management component 705 may be configured to perform one or more operations for SU discovery and / or configuration, as described in more detail elsewhere herein. Processing component 710 may be configured to generate or determine sensing results based on, in response to, or otherwise associated with collected sensor data (e.g., collected from one or more SUs). Processing component 710 may be physically executed at different (distributed) locations depending on the computing architecture of SnMF entity 700. UE sensing store 715 may store information about one or more UEs configured to operate as SUs, such as the UE's identity, UE's location, and / or one or more of the UE's capabilities, etc. TRP sensing store 720 may store information about one or more TRPs configured to operate as SUs, such as the TRP's identity, TRP's location, and / or one or more of the TRP's capabilities, etc. UE sensing store 715 and / or TRP sensing store 720 may be dedicated services within SnMF entity 700. Alternatively, UE sensing store 715 and / or TRP sensing store 720 may be included in another network function such as AMF or NRF. In some examples, SnMF entity 700 may include an SR that stores information about one or more TRPs and one or more UEs configured to operate as SU.

[0127] In some examples, the wireless communication network may be associated with a single SnMF entity 700 for each PLMN. In such examples, the SnMF entity 700 may be configured as a single entry and exit point for sensing services. In such examples, a single logical SnMF entity 700 may exist that can be implemented via multiple (distributed) SnMF instances. In other examples, multiple SnMF entities 700 may be defined and / or accessible. For example, SnMF entities 700 may be defined for a corresponding service area and / or a corresponding service type. For example, a given SnMF entity 700 may be associated with a supported service area (e.g., the geographic area on which the SnMF manages sensing services), one or more supported service types, one or more supported QoS parameters for each supported service type, and / or one or more other capabilities. In some examples, one or more SnMF functions may be shared across multiple SnMF entities 700. For example, one or more SRs may be accessible by multiple SnMF entities 700.

[0128] As described elsewhere in this document, sensing services can be associated with configuring one or more SUs to perform RF sensing to fulfill one or more sensing requests. In a wireless communication network, different devices can be capable of acting as SUs. However, different devices can be associated with different capabilities, different locations, and / or different criteria for when a device can be configured to perform RF sensing. For example, a UE can be associated with RF sensing capabilities different from those of a network node or TRP. Additionally, introducing RF sensing as an ISAC service introduces additional considerations for configuring a given device as an SU. For example, network load information, link quality, and / or the availability of wireless communication resources can influence configuration decisions for SUs in a wireless communication network. Furthermore, when introducing RF sensing technology as a new system capability, new considerations are needed regarding authorization for service and operational access, data confidentiality, data integrity, and / or user privacy to ensure these aspects are considered when deriving sensing service requirements.

[0129] Therefore, the discovery and configuration of Subscriber Units (SUs) within a wireless communication network can be a complex task, requiring coordination among several different network entities and / or network nodes. Currently, no process or protocol is defined for SU discovery and configuration, which can result in one or more SUs failing to register or be identified (e.g., thus not participating in the sensing services provided by the wireless communication network). Additionally, this can lead to one or more SUs being configured to perform sensing operations that the SUs cannot perform. For example, the wireless communication network may currently not support coordinating RF sensing between multiple network nodes and / or UEs, obtaining RF sensing capabilities from multiple network nodes and / or UEs, coordinating configuration and authorization for RF sensing performed by multiple network nodes and / or UEs, and / or providing mechanisms for providing information to devices with RF sensing capabilities, indicating which network entity or device to send sensing data to, etc.

[0130] Furthermore, because wireless communication network resources are used to perform RF sensing operations, it can be difficult to correctly configure the SU to perform RF sensing operations in response to a sensing request. For example, a sensing request may indicate one or more sensing parameters. However, the SU can be configured using wireless communication configurations, such as RRC configuration. For example, a network node or network function entity can configure the SU to perform RF sensing operations via RRC configuration. However, the RRC configuration may use configuration parameters different from the sensing parameters indicated by the sensing request (e.g., there may be no RRC parameter corresponding to the sensing parameters). Therefore, the SU may be configured to perform RF sensing operations that do not meet or conform to the sensing parameters indicated by the sensing request, thereby consuming resources associated with performing RF sensing operations that do not meet or conform to the sensing parameters (e.g., processing resources, network resources, and / or power resources), and / or providing inaccurate sensing results in response to the sensing request, etc. Additionally, a network function entity configured to manage sensing operations may not have information indicating the current network condition. Therefore, the network function entity may not be able to determine the optimal RRC configuration for the SU (e.g., considering the current network condition).

[0131] Figure 8 This is a diagram illustrating an example operation 800 associated with sensing service selection and configuration according to this disclosure. For example... Figure 8 As shown, SU 805, network node 110, SnMF entity 810, and one or more SR 815 can communicate with each other. SnMF entity 810 and one or more SR 815 can communicate via one or more network interfaces. The one or more network interfaces may include wired connections, wireless connections, and / or logical connections. For example, SnMF entity 810 and one or more SR 815 can be network functions of the core network of a wireless communication network, such as wireless communication network 100 (e.g., as described in more detail elsewhere herein). Network node 110 can communicate with SnMF entity 810 via one or more other network function entities, such as AMF.

[0132] SU 805 and network node 110 may be included in a wireless communication network (e.g., wireless communication network 100). SU 805 may be SU 160. In some aspects, SU 805 may be UE 120, network node 110, TRP, RU, or another wireless communication device capable of performing RF sensing as described in more detail elsewhere herein.

[0133] One or more SR 815s may be independent network function entities. In other aspects, one or more SR 815s may be included in another network function entity (such as SnMF entity 810, AMF, NRF, or another network function entity). For example, operations described herein as being performed by or via an SR 815 may be performed by another network function entity (such as SnMF entity 810, AMF, NRF, or another network function entity). In some aspects, an SR 815 may be a common repository configured to store information of one or more SUs (such as SU 805). In some aspects, one or more SR 815s may include a UE repository (e.g., a UE sensing repository, such as UE sensing repository 715) and / or a network node repository (e.g., a TRP sensing repository, such as TRP sensing repository 720).

[0134] In some respects, Figure 8 Prior to the operations described herein, SU 805 may register with a sensing service supported by the network. For example, SU 805 may send registration information for a sensing service (e.g., for an ISAC service). In some aspects, SU 805 may initiate registration with a sensing service. SU 805 may send registration information to register as an SU with the sensing service. The registration information may indicate the location of the SU and / or one or more sensing capabilities of the SU. Network function entities may receive the registration information. For example, SnMF entity 810, AMF entity, or another network function entity may store the registration information. In some aspects, SR 815 may be configured to store registration information of UEs and / or network nodes that have already registered as SUs. SR 815 may be accessible by multiple network functions, such as multiple SnMF entities.

[0135] As another example, SU 805 may send a request to associate the SU with a network function configured to perform operations for sensing services. For example, SU 805 may send communications (e.g., Non-Access Stratum (NAS) transport communications) indicating the location of SU 805 and / or one or more sensing capabilities of SU 805 (e.g., indicating SU registration information). In some aspects, AMF entities may use, based on, respond to, or otherwise associate with the registration information to identify one or more SnMF entities (e.g., SnMF entity 810) to be associated with SU 805.

[0136] One or more sensing capabilities of the SU 805 may include supported service areas, the location of the SU 805 (e.g., the geographic location or cell through which the SU 805 communicates with the wireless communication network), one or more supported sensing service types, and / or one or more supported QoS parameters for one or more supported sensing service types, etc. For example, the SU 805 may transmit indications of its location via geographic coordinates, one or more cell identifiers (e.g., one or more physical cell identifiers (PCIs)), one or more tracking areas, one or more geographic areas, and / or one or more areas relative to the location of a given device.

[0137] Supported sensing service types may include object detection, object tracking, environmental monitoring, and / or another type of RF sensing. Supported QoS parameters may indicate one or more supported QoS requirements for sensing requests and / or for the sensing service types supported by SU 805. QoS parameters may include confidence level, accuracy of one or more sensing parameters (e.g., accuracy of location estimation, accuracy of velocity estimation, or accuracy of another sensing parameter), sensing resolution, sensing service latency (e.g., maximum sensing service latency), refresh rate, missed detection rate, and / or false alarm rate, etc. SnMF entity 810 and / or SR 815 may store registration information of SU 805 (and / or one or more other SUs configured to operate in a wireless communication network).

[0138] In the first operation 820, SU 805 can send and network node 110 can receive capability information for sensing services. For example, SU 805 can send and network node 110 can receive capability reports. SU 805 can send capability reports via capability signaling, uplink communication, UE Assistance Information (UAI) communication, uplink control information (UCI) communication, uplink MAC control element (MAC-CE) communication, RRC communication, physical uplink control channel (PUCCH) and / or physical uplink shared channel (PUSCH), etc. The capability report can indicate one or more parameters associated with the corresponding capability of SU 805. One or more parameters can be indicated via the corresponding information element (IE) included in the capability report.

[0139] A capability report may indicate whether SU 805 supports a feature and / or one or more parameters associated with that feature. For example, a capability report may indicate the capabilities and / or parameters for the sensing services described herein. As another example, a capability report may indicate the capabilities and / or parameters for one or more sensing capabilities described herein. One or more operations described herein may be based on the capability information in the capability report. For example, SU 805 may perform communication or RF sensing operations based on the capability information, or may receive configuration information based on the capability information. In some aspects, the capability report may indicate support for acting as an SU, as described in more detail elsewhere herein. For example, the capability report may include registration information associated with SU 805. Network node 110 may store the registration information and / or may forward the registration information to network functions such as AMF, SnMF entity 810, and / or SR 815.

[0140] In the second operation 825, SnMF entity 810 may acquire or receive a sensing request. In some aspects, the AMF or gateway may send and SnMF entity 810 may receive sensing requests. Sensing requests may originate from client devices, network functions, or application functions (e.g., sent by them). As used herein, a “sensing request” may refer to a request for a sensing service (e.g., associated with an ISAC service supported by a wireless communication network). For example, a sensing request may be a request for a given sensing result (e.g., object detection, object tracking, environmental monitoring, or another sensing type). For example, a sensing request may originate from client devices and / or application functions (e.g., via NEF).

[0141] A sensing request may include sensing area parameters. Sensing area parameters define the area (e.g., a geographic region) in which RF sensing will be performed. For example, for some use cases of RF sensing, a defined sensing area can improve the relevance and / or accuracy of the sensing results provided. For example, for the detection of objects in a region, environmental monitoring, pedestrian or animal monitoring (e.g., on a given road or railway), weather monitoring (e.g., flood detection), or AGV monitoring in an industrial environment, a sensing request may indicate the sensing area in which RF sensing will be performed. Sensing area parameters may indicate one or more cell identifiers (e.g., one or more PCIs), one or more tracking areas, one or more geographic regions, and / or one or more areas relative to the location of a given device (e.g., relative to a given UE, network node, or TRP), etc.

[0142] A sensing request may indicate sensing service type parameters. Sensing service type parameters indicate the type of service output expected in response to a sensing request. For example, sensing service type parameters may indicate one or more characteristics of an object or environment that the expected sensing output indicates, such as localization, micro-Doppler, and / or object detection. A sensing request may indicate QoS parameters. QoS parameters indicate one or more QoS requirements for the sensing request and / or the sensing service type requested by the sensing request. QoS parameters may indicate confidence level, accuracy of one or more sensing parameters (e.g., accuracy of localization estimation, accuracy of velocity estimation, or accuracy of another sensing parameter), sensing resolution, sensing service latency (e.g., maximum sensing service latency), refresh rate, missed detection rate, and / or false alarm rate, etc.

[0143] A sensing request may indicate timing parameters. Timing parameters may indicate the duration of the requested RF sensing. For example, timing parameters may indicate the amount of time for which RF sensing will be performed. In some aspects, timing parameters may indicate the start and / or end time of the RF sensing. In some aspects, timing parameters may indicate the periodicity of the RF sensing (e.g., RF sensing may indicate that RF sensing will be performed daily during certain time periods). In some aspects, timing parameters may indicate the timing of sensing result reporting. For example, timing parameters may indicate the frequency at which sensing results are reported to client devices or network functions.

[0144] In the third operation 830, SnMF entity 810 may determine one or more sensing parameters for the sensing request. The one or more sensing parameters may include parameters indicating a sensing configuration suitable for fulfilling the sensing request. For example, the one or more sensing parameters may indicate sensing configuration requirements for a SU to be configured to perform RF sensing operations according to the sensing request. In some aspects, the one or more sensing parameters may include detection distance parameters, Doppler range parameters, one or more QoS parameters, one or more sensing reporting parameters, and / or one or more adaptive reconfiguration parameters, etc. In some aspects, the one or more sensing parameters may include characteristics of the sensing signal required to satisfy one or more sensing requests in the sensing request, such as frequency band, frequency bandwidth, time and / or frequency pattern or periodicity, duration over time, as some examples.

[0145] One or more sensing report parameters may indicate the type of sensing report and / or one or more sensing outputs to be indicated on the sensing report, etc. For example, one or more sensing report parameters may indicate one or more types of sensing outputs to be reported back to SnMF entity 810. In some aspects, a type of sensing report may include channel distribution reports and / or one or more processed outputs (e.g., Doppler measurements, range estimates, velocity estimates, or other processed outputs). This allows network node 110 to determine and / or configure appropriate processing configurations for SU 805, as described in more detail elsewhere herein. One or more sensing report parameters may indicate one or more Radio Resource Management (RRM) events or one or more sensing events to be reported. For example, one or more sensing report parameters may indicate that SUs entering sensing range (e.g., as defined by RSRP measurements, distance criteria, or another criterion) will be reported to SnMF entity 810. This allows network node 110 to configure RRM measurements and / or RRM reporting events for use in sensing measurement reporting.

[0146] One or more QoS parameters may indicate the expected QoS parameters for RF sensing operations. For example, one or more QoS parameters may indicate the range or resolution of the Doppler shift to be measured or reported by the SU. This allows network node 110 to configure the reference signal with appropriate time periodicity and an appropriate measurement window. Additionally or alternatively, one or more QoS parameters may indicate the range and / or range resolution of the sensing target for the sensing request. For example, one or more QoS parameters may indicate the maximum range and / or range resolution of the expected target for RF sensing operations. This allows network node 110 to configure the reference signal with appropriate frequency periodicity and / or an appropriate bandwidth. Additionally or alternatively, one or more QoS parameters may indicate the radar cross-section or support range for the sensing request. This allows network node 110 to configure appropriate transmit power for the reference signal to be used as part of the RF sensing operations.

[0147] One or more adaptive reconfiguration parameters may indicate one or more actions to be performed in connection with a failure to meet one or more QoS parameters. For example, one or more actions may include changing the sensing configuration, suppressing the transmission of sensing reports, suppressing the execution of RF sensing operations, removing the sensing configuration, and / or deregistering with the sensing service, etc. For example, one or more adaptive reconfiguration parameters may indicate one or more adaptive reconfiguration rules.

[0148] In some aspects, one or more sensing parameters may be associated with multiple sensing requests, including a sensing request. For example, one or more sensing parameters may satisfy multiple sensing requests. Additionally or alternatively, one or more sensing parameters may include multiple sets of one or more sensing parameters. For example, a single sensing request may generate multiple sets of one or more sensing parameters. In some aspects, one or more sensing parameters may be associated with a sensing session, as described in more detail elsewhere herein.

[0149] SnMF entity 810 can determine one or more sensing parameters for a sensing request. For example, SnMF entity 810 can use, be based on, or otherwise associate with parameters indicated by the sensing request to determine one or more sensing parameters. For example, SnMF entity 810 can determine one or more sensing parameters to indicate the appropriate RF sensing operation required to fulfill the sensing request.

[0150] In some respects, SnMF entity 810 may identify and / or select one or more SUs to perform RF sensing operations in response to a sensing request. For example, SnMF entity 810 may identify and / or select one or more SUs that may cover a sensing area associated with the sensing request (e.g., be configured to operate within the sensing area) and / or be able to perform operations in accordance with or based on one or more sensing parameters.

[0151] For example, in some aspects, SnMF entity 810 may communicate with one or more SRs 815 to identify and / or select one or more SUs. For example, in a fourth operation 835, SnMF entity 810 may send, and SR 815 may receive, a request for one or more SUs. For example, the request may indicate one or more sensing parameters for the sensing request. In some aspects, SnMF entity 810 may send a request for one or more UEs capable of acting as SUs to fulfill the sensing request (e.g., sent to a UE sensing repository). For example, SnMF entity 810 may send a request for a list of SUs capable of supporting one or more sensing parameters. Additionally or alternatively, SnMF entity 810 may send a request for one or more network nodes capable of acting as SUs to fulfill the sensing request (e.g., sent to a network node or a TRP sensing repository). For example, SnMF entity 810 may request a list of TRPs satisfying one or more sensing parameters from a TRP repository, and / or a list of UEs satisfying one or more sensing parameters from a UE repository.

[0152] SR 815 can identify one or more SUs that satisfy one or more sensing parameters (e.g., are capable of performing actions based on one or more sensing parameters). For example, SR 815 can identify one or more SUs configured to operate within a sensing area indicated by a sensing request (or currently located within that sensing area). In some aspects, SR 815 and / or SnMF entity 810 can perform a positioning operation to obtain more current locations of the corresponding SUs (e.g., which may be mobile and / or moving UEs in a wireless communication network). For example, SR 815 can identify one or more SUs as candidates to be selected for a sensing request (e.g., based on the registration information of the corresponding SUs). For example, the registration information may indicate that the location of the SU is within the sensing area of ​​the sensing request, and / or that the SU is capable of performing RF sensing operations based on one or more sensing parameters. SR 815 can perform a positioning operation to obtain the updated or current location of one or more SUs. For example, SR 815 can communicate with one or more SUs and / or the network node 110 that manages one or more SUs to obtain the updated or current location of one or more SUs. This improves the SR 815's selection of SUs because the SR 815 can use more current locations of the SUs (e.g., which may be moving and / or in motion) when selecting SUs capable of serving the sensing request. In the fifth operation 840, the SR 815 may send, and the SnMF entity 810 may receive, an indication for one or more SUs (e.g., including SU 805) selected by the SR 815.

[0153] As another example, SnMF entity 810 can obtain indications of one or more SUs capable of serving a sensing request by communicating with one or more network nodes, such as network node 110. For example, SnMF entity 810 can send a request to one or more network nodes capable of acting as SUs to fulfill a sensing request in a manner similar to that described elsewhere herein (e.g., sent to a network node or TRP sensing repository). Additionally, in a sixth operation 845, SnMF entity 810 can send a request to one or more SUs (e.g., UEs) capable of serving a sensing request (e.g., capable of performing one or more RF sensing operations in accordance with a sensing request) to one or more network nodes configured to operate in a sensing area indicated by a sensing request. For example, SnMF entity 810 can send and network node 110 can receive SU discovery requests (e.g., UE discovery requests). In some aspects, as part of the sixth operation 845, SnMF entity 810 can send and network node 110 can receive indications of one or more sensing parameters.

[0154] In such examples, network node 110 may identify and / or select one or more SUs that satisfy one or more sensing parameters (e.g., are capable of performing RF sensing operations based on one or more sensing parameters). For example, network node 110 may identify one or more SUs configured to operate within a sensing area indicated by a sensing request (or currently located within that sensing area). In some aspects, network node 110 may perform a positioning operation to obtain more current locations of the corresponding SUs (e.g., in a wireless communication network, this could be a mobile and / or moving UE). For example, network node 110 may identify one or more SUs as candidates to be selected for a sensing request (e.g., based on the registration information of the corresponding SUs). For example, the registration information may indicate that the SU's location is within the sensing area of ​​the sensing request, and / or that the SU is capable of performing RF sensing operations based on one or more sensing parameters. Network node 110 may perform a positioning operation to obtain the updated or current locations of one or more SUs. For example, network node 110 may communicate with one or more SUs to obtain the updated or current locations of one or more SUs. This improves the network node 110's selection of SUs because the network node 110 can use more current locations of the SUs (e.g., which may be moving and / or in motion) when selecting SUs capable of serving the sensing request. In the seventh operation 850, the network node 110 may send, and the SnMF entity 810 may receive, an indication for one or more SUs (e.g., including SU 805) selected by the network node 110.

[0155] In some other respects, network node 110 may not send instructions to SnMF entity 810 for one or more SUs. For example, network node 110 may not perform the seventh operation 850. Instead, network node 110 may identify one or more SUs and configure one or more SUs using a sensing configuration (e.g., RRC configuration) based on one or more sensing parameters, as described in more detail elsewhere herein. In such examples, SnMF entity 810 may be unaware of the identity of the SU performing the RF sensing operation in response to the sensing request.

[0156] In the eighth operation 855, SnMF entity 810 may send and network node 110 may receive indications for one or more sensing parameters. In some aspects, the eighth operation 855 may be performed as part of the sixth operation 845. In other aspects, the sixth operation 845 and / or the seventh operation 850 may not be performed. For example, as part of the eighth operation 855, SnMF entity 810 may send and network node 110 may receive indications to configure one or more SUs using sensing configuration. For example, one or more SUs may be managed by network node 110 (e.g., one or more SUs may be UEs with a communication connection to network node 110). As another example, network node 110 may be a CU or DU, and one or more SUs (e.g., SU 805) may be RUs.

[0157] In the ninth operation 860, network node 110 may use, be based on, or otherwise associate with one or more sensing parameters to determine one or more configuration parameters. The one or more configuration parameters may be RRC parameters or other configuration parameters. For example, network node 110 may use, be based on, or otherwise associate with one or more sensing parameters to determine a sensing configuration. The sensing configuration may be an RRC configuration or another wireless communication configuration. In some aspects, the sensing configuration may be determined at least in part by SU 805 (e.g., by the UE) in a manner similar to that described herein. The sensing configuration may include a sensing configuration for network node 110 and / or a sensing configuration for one or more (SU) UEs that can be configured by such network node.

[0158] For example, network node 110 can determine reference signal resource allocation (e.g., time-domain allocation, frequency-domain allocation, and / or spatial-domain allocation). For example, network node 110 can determine one or more time slots or resource blocks to be used for reference signals that will be transmitted, received, and / or measured as part of RF sensing operations (e.g., to fulfill a sensing request). For example, network node 110 can use, based on, or otherwise correlate with sensing type, QoS parameters, Doppler range or resolution, and / or target range or range resolution, etc., indicated by one or more sensing parameters to determine the reference signal resource allocation. As another example, network node 110 can determine (e.g., for reference signals) transmit power configuration. For example, network node 110 can use, based on, or otherwise correlate with radar cross-section or minimum target range, etc., indicated by one or more sensing parameters to determine the transmit power configuration. Network node 110 can use, based on, or otherwise correlate with one or more sensing parameters to determine other RRC configuration parameters. This enables network node 110 to use local and / or current information about network conditions and SU UE conditions to determine the details of the sensing configuration while satisfying conditions set by sensing parameters (e.g., to define which time slots or resource blocks are used for reference signals, whether UE or TRP measurements are used to trigger events, and / or other details of the sensing configuration).

[0159] In some aspects, network node 110 can send and SnMF entity 810 can receive the determined sensing configuration before application configuration. For example, SnMF entity 810 can request a sensing configuration from network node 110. In such examples, SnMF entity 810 can send the sensing configuration (e.g., determined by network node 110) back to the network node or to one or more SUs (e.g., SU 805) selected to fulfill the sensing request, as described in more detail elsewhere herein. In some aspects, sensing parameters or sensing configuration can be transmitted directly from SnMF entity 810 to one or more SUs 805 without requiring determination from the network node.

[0160] In some aspects, a sensing configuration may include a transmission configuration, one or more measurement configurations, one or more processing configurations, one or more reporting configurations, and / or one or more adaptive reconfiguration configurations, etc. A sensing configuration can define how the different components of the sensing configuration relate to each other. For example, a processing configuration can indicate which measurements (e.g., which measurement configuration(s)) should be used for the processing configured by the processing configuration. As another example, an adaptive reconfiguration configuration can indicate which measurements (e.g., which measurement configurations) should be used to determine whether the sensing configuration should be dynamically adapted or modified. As yet another example, a processing configuration can indicate how processing results or sensing data should be reported (e.g., which reporting configuration(s) should be used to report data generated based on the processing configuration).

[0161] The transmission configuration may include configurations for one or more sensing reference signals. For example, the transmission configuration may configure sensing reference signals transmitted by one or more SUs (such as SU 805). The transmission configuration may include configurations for performing RF sensing operations (e.g., to combine with...). Figure 4A and Figure 4B Configuration of RF signals, wireless communication signals, OFDM signals and / or sensing reference signals, etc. (similar to the description).

[0162] One or more measurement configurations indicate one or more time-domain resources, one or more frequency-domain resources, and / or one or more spatial-domain resources for a sensing reference signal to be measured for a sensing request. For example, the measurement configuration may define a sensing reference signal to be measured by one or more SUs (such as SU 805). In some aspects, the measurement configuration may indicate one or more measurement types to be performed. One or more measurement types may include raw channel time-domain measurements, frequency-domain measurements, and / or angular distribution measurements, etc. In some aspects, the measurement configuration may include an RRM measurement configuration. For example, a measurement configuration defined for a reference signal may be configured and used for RF sensing purposes.

[0163] One or more processing configurations indicate one or more processing outputs for the sensing data used in the sensing request. For example, one or more measurement configurations may configure the SU to acquire sensing data (e.g., measurements configured via one or more measurement configurations). The sensing data may be based on or otherwise associated with wireless communication channel measurements. The processing configurations may define how to use the sensing data to determine one or more processing outputs. For example, the processing outputs may include parameters determined or calculated using the sensing data. As examples, the processing outputs may include Doppler parameters, range estimates, location estimates, velocity estimates, radar cross sections, angle maps (e.g., Doppler range maps), and / or one or more object detections (e.g., a list of one or more Doppler values ​​and ranges of detected targets), etc.

[0164] The processing configuration defines information about how to process sensed data (e.g., raw sensed measurements). For example, the processing configuration may define one or more parameters to be used in the processing, such as time / frequency averaging, windowing, and / or one or more algorithms. The processing of the sensed data can be performed by the UE or network node 110. In some aspects, SU 805 can be configured to perform processing. In other aspects, SU 805 can be configured to report sensed data, and network node 110 can perform processing according to the processing configuration. As another example, SnMF entity 810 can perform processing on the sensed data.

[0165] The same sensed data can be used to generate different processed outputs (e.g., defined by different processing configurations). In other words, the same raw measurement can be used to produce multiple different processed outputs. Additionally or alternatively, a single processed output can be generated using multiple sensed data measurements (e.g., obtained according to different measurement configurations). For example, the processing configuration may indicate at least one measurement configuration associated with the processing configuration among one or more measurement configurations. Additionally or alternatively, the processing configuration may indicate at least one reporting configuration associated with the processing configuration among one or more reporting configurations (e.g., to define how the processed output is reported).

[0166] One or more report configurations can be configured to configure one or more sensing measurement reports. For example, one or more report configurations can indicate time-domain and / or frequency-domain measurements to be used by SU 805 to send sensing measurement reports. Additionally, one or more report configurations can indicate the timing or periodicity of the sensing measurement reports. In some aspects, one or more report configurations can indicate one or more measurement events associated with sending sensing measurement reports. For example, a measurement event detected by SU 805 can trigger SU 805 to send a sensing measurement report. Sensing measurement reports can indicate sensing data (e.g., channel measurements) and / or one or more processing outputs. For example, report configurations can define the content and timing of the reported (processed) sensing measurements.

[0167] One or more adaptive reconfiguration configurations may indicate one or more adaptive reconfiguration rules. For example, one or more adaptive reconfiguration configurations may indicate rules for changing the sensing state (e.g., the sensing state may include an unconfigured state, a configured state, or an unregistered state) or changing the sensing configuration of the SU 805. For example, one or more adaptive reconfiguration configurations may indicate one or more thresholds to be used for comparison with sensing data, processing output, and / or other channel measurements so that the SU 805 (and / or network node 110 or SnMF entity 810) can determine when the sensing state and / or sensing configuration of the SU 805 should be changed. For example, an adaptive reconfiguration configuration may indicate the action to be performed when one or more thresholds are met. Actions may include enabling or disabling sensing measurement reporting, deregistering from the sensing service, and / or suspending one or more RF sensing operations, etc.

[0168] In some respects, a sensing configuration can be associated with a sensing session. A sensing session can be associated with a sensing session identifier, one or more sets of one or more sensing parameters including one or more sensing parameters, one or more modes for sensing data reporting, and / or one or more session parameters, etc. The sensing session identifier can be unique for each SnMF entity. One or more sets of one or more sensing parameters can be associated with one or more sensing requests. A sensing session can be associated with multiple sensing configurations.

[0169] Establishing a sensing session allows network node 110 and / or SnMF entity 810 to simultaneously activate, deactivate, configure, deconfigure, and / or remove multiple sensing reference signal configurations, multiple sensing report configurations, and / or multiple sensing configurations. For example, network node 110 and / or SnMF entity 810 can indicate an action and a sensing session identifier (e.g., a sensing session can be indicated by a simple message carrying the sensing session identifier and indicating the action). This can result in actions being applied to multiple sensing configurations and / or multiple SUs. This saves network resources, processing resources, and / or latency that would otherwise be associated with individually signaling actions to be performed for each sensing configuration.

[0170] Additionally, when the sensed target is moving, the sense session can facilitate mobility management and / or target tracking. For example, sense configuration handover can be simplified because only a sense session identifier needs to be indicated to network node 110 to obtain the sense configuration. For example, a UE being handed over to a new network node 110 can be enabled to maintain the sense configuration associated with the sense session via the sense session identifier indicated as part of the handover operation.

[0171] For example, SU 805 can receive communications instructing one or more actions to be performed for a sensing session. A sensing session may be associated with one or more sensing configurations. SU 805 may perform one or more actions for one or more sensing configurations in association with the sensing session. One or more actions may include transferring a sensing configuration to a different communication session (e.g., with a different network node, such as via a handover operation), terminating a sensing configuration, and / or modifying a sensing configuration, etc.

[0172] In operation 865, network node 110 can send and SU 805 can receive the sensing configuration. Network node 110 can send and SU 805 can receive the sensing configuration via one or more of system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB), etc.), RRC signaling, MAC signaling (e.g., one or more MAC Control Elements (MAC-CE)), and / or DCI, etc. For example, network node 110 can send and SU 805 can receive the sensing configuration via a downlink control channel (such as PDCCH). In one option, network node 110 can apply the determined sensing configuration to itself or to one or more SUs in SU 805 by transmitting appropriate control signaling (such as RRC signaling). In some aspects, network node 110 can send and SnMF entity 810 can receive the applied sensing configuration.

[0173] In some aspects, the sensing configuration may indicate one or more candidate configuration and / or communication parameters. In some aspects, one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, subsequent indications may select candidate configuration and / or communication parameters from one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC-CE and / or one or more DCI messages, etc.

[0174] In eleventh operation 870, SU 805 may perform one or more RF sensing operations according to a sensing configuration. For example, SU 805 may transmit and / or receive one or more reference signals (e.g., one or more sensing reference signals) configured by the sensing configuration. Additionally or alternatively, SU 805 may perform one or more measurements (e.g., wireless communication channel measurements) on one or more reference signals (e.g., one or more sensing reference signals) configured by the sensing configuration. In some aspects, SU 805 may determine one or more processing outputs configured by one or more processing configurations. In some aspects, eleventh operation 870 may include SU 805 transmitting and network node 110 receiving a sensing measurement report. SU 805 may transmit a sensing measurement report according to a reporting configuration. The sensing measurement report may indicate sensing data (e.g., one or more channel measurements of the sensing reference signals) and / or processing outputs, etc.

[0175] Network node 110 can use reported sensing data from one or more SUs (such as SU 805) to determine one or more processing outputs. In some aspects, network node 110 can send and SnMF entity 810 can receive sensing measurement reports. Sensing measurement reports may indicate sensing data (e.g., one or more channel measurements of a sensing reference signal performed by one or more SUs) and / or one or more processing outputs, etc. In some aspects, SnMF entity 810 can use the reported sensing data to determine one or more processing outputs. SnMF entity 810 can determine sensing results based on a sensing request and the reported sensing data or processing outputs. SnMF entity 810 can send sensing results in response to a sensing request (e.g., to a client device, application function, or another network function).

[0176] Figure 9 This is a diagram illustrating an example sensing configuration 900 according to this disclosure. For example... Figure 9 As shown, sensing configuration 900 may include one or more reporting configurations (e.g., reporting configuration 905, reporting configuration 910, and reporting configuration 915), one or more processing configurations (e.g., processing configuration 920 and processing configuration 925), one or more measurement configurations (e.g., measurement configuration 930 and measurement configuration 935), one or more status configurations (e.g., status configuration 940), and / or one or more other types of sensing configurations or components of sensing configurations (e.g., one or more transmission configurations). Figure 9 The number and arrangement of configurations depicted are provided as examples. Sensing configurations may include... Figure 9 The configurations described herein are compared to more configurations, fewer configurations, and / or other types of configurations.

[0177] Sensing configuration 900 can indicate one or more associations between different components or parts (or sub-configurations) of sensing configuration 900. For example, such as Figure 9 As shown, sensing configuration 900 may instruct processing configuration 920 to use measurements obtained according to measurement configuration 930 and measurement configuration 935. As another example, sensing configuration 900 may instruct processing configuration 925 to use measurements obtained according to measurement configuration 935. As another example, sensing configuration 900 may instruct processing configuration 925 and / or measurement configuration 935 to be executed according to state configuration 940. State configuration 940 may be a sensing state configuration. As another example, sensing configuration 900 may instruct processing configuration 920 to report data according to reporting configuration 905 and reporting configuration 910. As another example, sensing configuration 900 may instruct processing configuration 925 to report data according to reporting configuration 915.

[0178] Different associations between components or parts (or sub-configurations) of sensing configuration 900 can enable a single sensing configuration to be applied to multiple sets of multiple sensing requests and / or one or more sensing parameters. For example, network node 110 can be configured with different associations to meet the sensing parameters used for a given sensing request. This can save processing resources, network resources, and / or power resources that would otherwise be associated with configuring a separate sensing configuration for each set of one or more sensing parameters (e.g., for each sensing request).

[0179] Figure 10 This is a diagram illustrating an example sensing session 1000 according to the present disclosure. The example sensing session may include sensing session 1005 and sensing session 1010. (As...) Figure 10 As shown, a sensing session can be associated with one or more parts (or sub-configurations) of a sensing configuration (such as sensing configuration 900 or another sensing configuration).

[0180] For example, such as Figure 10 As shown, sensing session 1005 can be associated with reporting configuration 905, processing configuration 920, measurement configuration 930, and measurement configuration 935. Sensing session 1010 can be associated with reporting configuration 910, reporting configuration 915, processing configuration 925, and measurement configuration 935. For example, one or more portions (or sub-configurations) of a sensing configuration can be associated with multiple sensing sessions, such as... Figure 10 The measurement configuration 935 is described herein. This enables network nodes or SnMF entities to perform actions on all or sub-configurations of the sensing configuration via a single communication or a single instruction, as described in more detail elsewhere in this document.

[0181] Figure 11This is a flowchart illustrating an example process 1100 for supporting sensor service selection and configuration, performed, for example, at a SnMF entity or a device of a SnMF entity, according to this disclosure. Example process 1100 is an example in which a device or SnMF (e.g., SnMF entity 810 or network node 170) performs operations associated with sensor service selection and configuration.

[0182] like Figure 11 As shown, in some aspects, process 1100 may include receiving a sensing request indicating one or more request parameters (box 1110). For example, SnMF entities (such as those using...) Figure 14 The communication manager 1408 or receiving component 1402 depicted herein can receive a sensing request indicating one or more request parameters, as described above.

[0183] like Figure 11 Further shown, in some aspects, process 1100 may include sending indications to one or more network nodes for one or more sensing parameters used in a sensing request, the one or more network nodes being selected using one or more request parameters, and the one or more sensing parameters being associated with one or more request parameters (box 1120). For example, SnMF entities (such as those using...) Figure 14 The communication manager 1408 or transmitting component 1404 depicted herein can send instructions to one or more network nodes for one or more sensing parameters used for sensing requests, the one or more network nodes being selected using one or more request parameters, and the one or more sensing parameters being associated with one or more request parameters as described above.

[0184] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0185] In the first additional aspect, one or more request parameters include at least one of the following: sensing area parameters, timing parameters, one or more QoS parameters, or service type parameters.

[0186] In a second additional aspect, either alone or in combination with the first aspect, process 1100 includes selecting one or more SUs to fulfill a sensing request.

[0187] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, one or more network nodes are associated with managing one or more SUs.

[0188] In the fourth additional aspect, selecting one or more SUs, either alone or in combination with one or more of the first to third aspects, includes selecting one or more SUs in association with the ability of one or more SUs to support one or more sensing parameters.

[0189] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, selecting one or more SUs includes sending a request to the storage entity for a list of SUs capable of supporting one or more sensing parameters, and receiving an instruction for one or more SUs from the storage entity in response to the sending request.

[0190] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, one or more SUs include one or more TRPs, and a storage entity includes a TRP storage entity.

[0191] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, one or more SUs include one or more UEs, and the storage entity includes a UE storage entity.

[0192] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes performing one or more positioning operations with a corresponding UE from one or more SUs, including one or more UEs, the one or more positioning operations indicating the current positioning of the corresponding UE from one or more SUs.

[0193] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, selecting one or more SUs includes sending a discovery request to one or more network nodes associated with discovering a UE capable of supporting one or more sensing parameters.

[0194] In the tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, process 1100 includes receiving an indication to one or more UEs from one or more network nodes in response to sending a discovery request, the one or more UEs being included in one or more SUs.

[0195] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, process 1100 includes performing one or more positioning operations with a corresponding UE from one or more SUs, including one or more UEs, the one or more positioning operations indicating the current positioning of the corresponding UE from one or more SUs.

[0196] In the twelfth additional aspect, individually or in combination with one or more of the first to eleventh aspects, one or more sensing parameters include at least one of the following: detection distance parameter, Doppler range parameter, one or more QoS parameters, one or more sensing reporting parameters, or one or more adaptive reconfiguration parameters.

[0197] In the thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, one or more sensing report parameters indicate at least one of the following: the type of sensing report, or one or more sensing outputs to be indicated on the sensing report.

[0198] In the fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, one or more sensing reporting parameters indicate one or more radio resource management events or one or more sensing events to be reported.

[0199] In the fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, one or more QoS parameters indicate at least one of the following: the range or resolution of the Doppler shift to be measured or reported, the distance to the sensing target for the sensing request, the range resolution of the sensing target, or the radar cross-section or support range for the sensing request.

[0200] In the sixteenth additional aspect, either alone or in combination with one or more of the first to fifteenth aspects, one or more adaptive reconfiguration parameters indicate one or more actions to be performed in connection with the non-compliance of one or more QoS parameters.

[0201] In the seventeenth additional aspect, one or more sensing parameters are associated, alone or in combination with one or more of the first to sixteenth aspects, with a plurality of sensing requests including sensing requests.

[0202] In the eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, one or more sensing parameters include a plurality of sets of one or more sensing parameters.

[0203] In the nineteenth additional aspect, one or more sensing parameters are associated with a sensing session, either alone or in combination with one or more of the first to eighteenth aspects.

[0204] In the twentieth additional aspect, either alone or in combination with one or more of the first to nineteenth aspects, a sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0205] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11 Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0206] Figure 12 This is a flowchart illustrating an example process 1200 for supporting sensor service selection and configuration, performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1200 is an example in which a device or network node (e.g., network node 110) performs operations associated with sensor service selection and configuration.

[0207] like Figure 12 As shown, in some aspects, process 1200 may include receiving an indication from a SnMF entity for one or more sensing parameters associated with a sensing request (box 1210). For example, a network node (such as by using...) Figure 15 The communication manager 150 or receiving component 1502 depicted herein may receive instructions from the SnMF entity regarding one or more sensing parameters associated with a sensing request, as described above.

[0208] like Figure 12 As further shown, in some aspects, process 1200 may include sending a sensing configuration to one or more SUs, the sensing configuration including one or more configuration parameters associated with one or more sensing parameters (box 1220). For example, network nodes (such as those using...) Figure 15 The communication manager 150 or transmitting component 1504 depicted herein can transmit sensing configurations to one or more SUs, the sensing configurations including one or more configuration parameters associated with one or more sensing parameters, as described above.

[0209] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0210] In the first additional aspect, one or more configuration parameters include one or more radio RRC parameters.

[0211] In a second additional aspect, either alone or in combination with the first aspect, process 1200 includes receiving instructions for one or more SUs from the SnMF entity.

[0212] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, process 1200 includes selecting one or more SUs to fulfill a sensing request.

[0213] In the fourth additional aspect, selecting one or more SUs, either alone or in combination with one or more of the first to third aspects, includes selecting one or more SUs in association with the ability of one or more SUs to support one or more sensing parameters.

[0214] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, one or more SUs may be selected to include receiving a discovery request from the SnMF entity associated with discovering a UE capable of supporting one or more sensing parameters.

[0215] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, process 1200 includes sending an indication to a SnMF entity for one or more UEs, which are included in one or more SUs, in response to receiving a discovery request.

[0216] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, one or more sensing parameters include at least one of the following: detection distance parameter, Doppler range parameter, one or more QoS parameters, one or more sensing reporting parameters, or one or more adaptive reconfiguration parameters.

[0217] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, one or more sensing report parameters indicate at least one of the following: the type of sensing report, or one or more sensing outputs to be indicated on the sensing report.

[0218] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, one or more sensing reporting parameters indicate one or more radio resource management events or one or more sensing events to be reported.

[0219] In the tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, one or more QoS parameters indicate at least one of the following: the range or resolution of the Doppler shift to be measured or reported, the distance to the sensing target for the sensing request, the range resolution of the sensing target, or the radar cross-section or support range for the sensing request.

[0220] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, one or more adaptive reconfiguration parameters indicate one or more actions to be performed in connection with the non-compliance of one or more QoS parameters.

[0221] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, the sensing configuration includes at least one of the following: a transmission configuration, one or more measurement configurations, one or more processing configurations, one or more reporting configurations, or one or more adaptive reconfiguration configurations.

[0222] In the thirteenth additional aspect, the transmission configuration includes, alone or in combination with one or more of the first to twelfth aspects, a configuration for one or more sensing reference signals.

[0223] In the fourteenth additional aspect, individually or in combination with one or more of the first to thirteenth aspects, one or more measurement configurations indicate at least one of the following for a sensing reference signal to be measured in response to a sensing request: one or more time-domain resources, one or more frequency-domain resources, or one or more spatial-domain resources.

[0224] In the fifteenth additional aspect, either alone or in combination with one or more of the first to fourteenth aspects, one or more processing configurations indicate one or more processing outputs for sensing data of a sensing request.

[0225] In the sixteenth additional aspect, either alone or in combination with one or more of the first to fifteenth aspects, a processing configuration in one or more processing configurations indicates at least one of the following: at least one measurement configuration associated with the processing configuration in one or more measurement configurations, or at least one reporting configuration associated with the processing configuration in one or more reporting configurations.

[0226] In the seventeenth additional aspect, one or more sensing parameters are associated with a sensing session, either alone or in combination with one or more of the first to sixteenth aspects.

[0227] In the eighteenth additional aspect, either alone or in combination with one or more of the first to seventeenth aspects, a sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0228] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0229] Figure 13This is a flowchart illustrating an example process 1300 for supporting sensor service selection and configuration, performed, for example, at a device of an SU or SU according to this disclosure. Example process 1300 is an example in which a device or SU (e.g., SU 160 or SU 805) performs operations associated with sensor service selection and configuration.

[0230] like Figure 13 As shown, in some aspects, process 1300 may include receiving a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration (box 1310). For example, SU (such as by using Figure 16 The communication manager 1608 or receiving component 1602 depicted herein can receive a sensing configuration via one or more RRC communications, which indicates a sensing session associated with the sensing configuration, as described above.

[0231] like Figure 13 As further shown, in some aspects, process 1300 may include receiving communication indicating one or more actions to be performed for a sensing session (box 1320). For example, SU (such as by using Figure 16 The communication manager 1608 or receiving component 1602 depicted herein can receive communications instructing one or more actions to be performed for a sensing session, as described above.

[0232] like Figure 13 As further shown, in some aspects, process 1300 may include performing one or more actions (box 1330) in connection with the sensing configuration and associated with the sensing session. For example, SU (such as by using Figure 16 The communication manager 1608 or execution component 1610 described herein can perform one or more actions in connection with the sensing configuration and the sensing session, as described above.

[0233] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0234] In the first additional aspect, the sensing configuration includes at least one of the following: a transmission configuration, one or more measurement configurations, one or more processing configurations, one or more reporting configurations, or one or more adaptive reconfiguration configurations.

[0235] In a second additional aspect, either alone or in combination with the first aspect, the transmission configuration includes configuration for one or more sensing reference signals.

[0236] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, one or more measurement configurations indicate at least one of the following for a sensing reference signal to be measured for a sensing configuration: one or more time-domain resources, one or more frequency-domain resources, or one or more spatial-domain resources.

[0237] In the fourth additional aspect, either alone or in combination with one or more of the first to third aspects, one or more processing configurations indicate one or more processing outputs of sensing data for sensing configuration.

[0238] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the processing configuration in one or more processing configurations indicates at least one of the following: at least one measurement configuration associated with the processing configuration in one or more measurement configurations, or at least one reporting configuration associated with the processing configuration in one or more reporting configurations.

[0239] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0240] In the seventh additional aspect, performing one or more actions, either alone or in combination with one or more of the first to sixth aspects, includes performing one or more actions for each sensing configuration, including the sensing configuration, associated with the sensing session.

[0241] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, receiving communication includes receiving an indication of an identifier for a sensing session and an indication for terminating the sensing session, and one or more actions include terminating the sensing configuration.

[0242] In the ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, receiving communication includes receiving an indication of an identifier for a sensing session and an indication for transferring to a different communication session, and one or more actions include transferring the sensing configuration to a different communication session.

[0243] although Figure 13 An example box for process 1300 is shown, but in some respects, it differs from... Figure 13 Compared to the boxes depicted, process 1300 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1300 may be executed in parallel.

[0244] Figure 14This is a diagram of an example device 1400 for wireless communication that supports sensor service selection and configuration according to this disclosure. Device 1400 may be a network node (e.g., network node 170, a network function entity, or a SnMF entity), or a network node may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and a communication manager 1408 that can communicate with each other (e.g., via one or more buses). Communication manager 1408 may be, or may resemble, communication manager 180. As shown, device 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another device 1406 (such as a UE, a network node, or another wireless communication device).

[0245] In some respects, device 1400 may be configured and / or capable of operating to perform the functions described herein. Figures 8 to 10 One or more operations described herein. Additionally or alternatively, the device 1400 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 11 The process 1100. In some aspects, the apparatus 1400 may include the above-described combination. Figure 2 One or more components of the network node described.

[0246] Receiver 1402 may receive communications, such as reference signals, control information, and / or data communications, from device 1406. Receiver 1402 may provide the received communications to one or more other components of device 1400, such as communication manager 1408. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1402 may include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, and / or one or more memories.

[0247] Transmitting component 1404 can transmit communications, such as reference signals, control information, and / or data communications, to device 1406. In some aspects, communication manager 1408 can generate communications and send the generated communications to transmitting component 1404 for transmission to device 1406. In some aspects, transmitting component 1404 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 1406. In some aspects, transmitting component 1404 may include the above-described combinations. Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0248] Communication manager 1408 may receive, or may cause receiving component 1402 to receive, a sensing request indicating one or more request parameters. Communication manager 1408 may send, or may cause sending component 1404 to send, indications for one or more sensing parameters for a sensing request to one or more network nodes, wherein the one or more network nodes are selected using the one or more request parameters, and the one or more sensing parameters are associated with the one or more request parameters. In some aspects, communication manager 1408 may perform one or more operations as described elsewhere herein as being performed by one or more components of communication manager 1408.

[0249] Communication Manager 1408 may include the above-mentioned components. Figure 2 The described network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 1408 includes a set of components, such as a determining component 1410 and / or a location component 1412. Alternatively, this set of components may be separate from and distinct from the communication manager 1408. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described network node may include, or may contain, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components of this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of that component.

[0250] The receiving component 1402 can receive a sensing request indicating one or more request parameters. The sending component 1404 can send an indication of one or more sensing parameters for the sensing request to one or more network nodes, the one or more network nodes being selected using one or more request parameters, and the one or more sensing parameters being associated with one or more request parameters.

[0251] The determination component 1410 can select one or more SUs to fulfill the sensing request.

[0252] The location component 1412 can perform one or more positioning operations with a corresponding UE from one or more SUs, including one or more UEs, the one or more positioning operations indicating the current location of the corresponding UE from one or more SUs.

[0253] The receiving component 1402 can receive an indication to one or more UEs from one or more network nodes in response to sending a discovery request, wherein the one or more UEs are included in one or more SUs.

[0254] The location component 1412 can perform one or more positioning operations with a corresponding UE from one or more SUs, including one or more UEs, the one or more positioning operations indicating the current location of the corresponding UE from one or more SUs.

[0255] Figure 14 The number and arrangement of components shown are provided as an example. In reality, with... Figure 14 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The collection of (one or more) components shown is executable and described as being composed of Figure 14 Another set of components shown performs one or more functions.

[0256] Figure 15 This is a diagram of an example device 1500 for wireless communication that supports sensor service selection and configuration according to this disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and a communication manager 150 that can communicate with each other (e.g., via one or more buses). As shown, device 1500 can use the receiving component 1502 and the transmitting component 1504 to communicate with another device 1506 (such as a UE, a network node, or another wireless communication device).

[0257] In some respects, device 1500 may be configured and / or capable of operating to perform the functions described herein. Figures 8 to 10 One or more operations described herein. Additionally or alternatively, the device 1500 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 12 The process 1200. In some aspects, the apparatus 1500 may include the above-described combination. Figure 2One or more components of the network node described.

[0258] Receiver 1502 may receive communications, such as reference signals, control information, and / or data communications, from device 1506. Receiver 1502 may provide the received communications to one or more other components of device 1500, such as communication manager 150. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1502 may include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, and / or one or more memories.

[0259] The transmitting component 1504 can transmit communications, such as reference signals, control information, and / or data communications, to the device 1506. In some aspects, the communication manager 150 can generate communications and send the generated communications to the transmitting component 1504 for transmission to the device 1506. In some aspects, the transmitting component 1504 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to the device 1506. In some aspects, the transmitting component 1504 may include the elements described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1504 may co-located with the receive component 1502 in one or more transceivers.

[0260] Communication manager 150 may receive, or may cause receiving component 1502 to receive from SnMF entity, indications of one or more sensing parameters associated with a sensing request. Communication manager 150 may send, or may cause sending component 1504 to send sensing configuration to one or more SUs, the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters. In some aspects, communication manager 150 may perform one or more operations as described elsewhere herein by one or more components of communication manager 150.

[0261] Communication manager 150 may include the above-mentioned components. Figure 2The described network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 150 includes a set of components, such as determining component 1508. Alternatively, this set of components may be separate from and distinct from the communication manager 150. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described network node may include, or may contain, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components of this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of that component.

[0262] The receiving component 1502 can receive an indication of one or more sensing parameters associated with a sensing request from the SnMF entity. The transmitting component 1504 can transmit a sensing configuration to one or more SUs, which includes one or more configuration parameters associated with the one or more sensing parameters.

[0263] The receiving component 1502 can receive instructions for one or more SUs from the SnMF entity.

[0264] The determination component 1508 can select one or more SUs to fulfill the sensing request.

[0265] Component 1508 can determine one or more configuration parameters by using, based on, or otherwise associated with one or more sensing parameters.

[0266] The transmitting component 1504 may, in response to receiving a discovery request, send an indication to the SnMF entity for one or more UEs, which are included in one or more SUs.

[0267] Figure 15 The number and arrangement of components shown are provided as an example. In reality, with... Figure 15 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The collection of (one or more) components shown is executable and described as being composed of Figure 15 Another set of components shown performs one or more functions.

[0268] Figure 16 This is a diagram of an example device 1600 for wireless communication that supports sensor service selection and configuration according to this disclosure. Device 1600 may be an SU, or an SU may include device 1600. In some aspects, device 1600 includes a receiving component 1602, a transmitting component 1604, and a communication manager 1608 that can communicate with each other (e.g., via one or more buses). Communication manager 1608 may be, or may resemble, communication manager 140 or communication manager 150. As shown, device 1600 can use the receiving component 1602 and the transmitting component 1604 to communicate with another device 1606 (such as a UE, network node, or another wireless communication device).

[0269] In some respects, device 1600 may be configured and / or capable of operating to perform the functions described herein. Figures 8 to 10 One or more operations described herein. Additionally or alternatively, the device 1600 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 13 The process 1300. In some aspects, the apparatus 1600 may include the above-described combination. Figure 2 One or more components of the UE or network node described.

[0270] Receiver 1602 may receive communications from device 1606, such as reference signals, control information, and / or data communications. Receiver 1602 may provide the received communications to one or more other components of device 1600, such as communication manager 1608. In some aspects, receiver 1602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1602 may include the combinations described above. Figure 2 The described UE or network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, and / or one or more memories.

[0271] Transmitting component 1604 can transmit communications, such as reference signals, control information, and / or data communications, to device 1606. In some aspects, communication manager 1608 can generate communications and send the generated communications to transmitting component 1604 for transmission to device 1606. In some aspects, transmitting component 1604 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to device 1606. In some aspects, transmitting component 1604 may include the above-described combinations. Figure 2 The described UE or network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1604 may co-located with the receive component 1602 in one or more transceivers.

[0272] Communication manager 1608 may receive, or may cause receiving component 1602 to receive, a sensing configuration indicating a sensing session associated with the sensing configuration via one or more RRC communications. Communication manager 1608 may receive, or may cause receiving component 1602 to receive communications indicating one or more actions to be performed for the sensing session. Communication manager 1608 may perform one or more actions for the sensing configuration in association with the sensing session. In some aspects, communication manager 1608 may perform one or more operations as described elsewhere herein as being performed by one or more components of communication manager 1608.

[0273] Communication Manager 1608 may include the above-mentioned features. Figure 2 The described UE or network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 1608 includes a set of components, such as an execution component 1610 and / or an RF sensing component 1612. Alternatively, this set of components may be separate from and distinct from the communication manager 1608. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described UE or network node may include, or may include, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of that component.

[0274] The receiving component 1602 can receive a sensing configuration via one or more RRC communications, the sensing configuration indicating a sensing session associated with the sensing configuration. The receiving component 1602 can receive communications indicating one or more actions to be performed for the sensing session. The executing component 1610 can perform one or more actions for the sensing configuration in association with the sensing session.

[0275] The RF sensing component 1612 can perform one or more RF sensing operations according to the sensing configuration.

[0276] Figure 16 The number and arrangement of components shown are provided as an example. In reality, with... Figure 16 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 16 The two or more components shown can be implemented within a single component, or Figure 16 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 16 The collection of (one or more) components shown is executable and described as being composed of Figure 16 Another set of components shown performs one or more functions.

[0277] The following provides an overview of some aspects of this disclosure.

[0278] Aspect 1: A method of wireless communication performed by a Sensing Management Function (SnMF) entity, the method comprising: receiving a sensing request indicating one or more request parameters; and sending to one or more network nodes an indication of one or more sensing parameters for the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

[0279] Aspect 2: According to the method of aspect 1, the one or more request parameters include at least one of the following: sensing area parameter, timing parameter, one or more quality of service (QoS) parameters or service type parameter.

[0280] Aspect 3: The method according to any one of aspects 1 to 2, the method further includes selecting one or more sensing units (SUs) to fulfill the sensing request.

[0281] Aspect 4: According to the method of aspect 3, wherein the one or more network nodes are associated with managing the one or more SUs.

[0282] Aspect 5: The method according to any one of Aspects 3 to 4, wherein selecting the one or more SUs includes selecting the one or more SUs in association with the ability of the one or more SUs to support the one or more sensing parameters.

[0283] Aspect 6: The method according to any one of Aspects 3 to 5, wherein selecting the one or more SUs comprises: sending a request to a storage entity for a list of SUs capable of supporting the one or more sensing parameters; and receiving an indication for the one or more SUs from the storage entity in response to sending the request.

[0284] Aspect 7: According to the method of aspect 6, the one or more SUs include one or more Transmit / Receive Points (TRPs), and the storage entity includes a TRP storage entity.

[0285] Aspect 8: According to the method of aspect 7, the one or more SUs include one or more user equipment (UEs), and the storage entity includes a UE storage entity.

[0286] Aspect 9: According to the method of aspect 8, the method further includes performing one or more positioning operations with a corresponding UE from the one or more UEs in association with the one or more SUs including the one or more UEs, the one or more positioning operations indicating the current positioning of the corresponding UE from the one or more SUs.

[0287] Aspect 10: The method according to any one of Aspects 3 to 9, wherein selecting the one or more SUs includes sending a discovery request to the one or more network nodes associated with discovering a user equipment (UE) capable of supporting the one or more sensing parameters.

[0288] Aspect 11: The method according to aspect 10 further includes receiving an indication for one or more UEs from the one or more network nodes in response to sending the discovery request, the one or more UEs being included in the one or more SUs.

[0289] Aspect 12: According to the method of aspect 11, the method further includes performing one or more positioning operations with a corresponding UE from the one or more UEs in association with the one or more SUs including the one or more UEs, the one or more positioning operations indicating the current positioning of the corresponding UE from the one or more SUs.

[0290] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the one or more sensing parameters include at least one of the following: detection distance parameter, Doppler range parameter, one or more quality of service (QoS) parameters, one or more sensing report parameters, or one or more adaptive reconfiguration parameters.

[0291] Aspect 14: According to the method of aspect 13, the one or more sensing report parameters indicate at least one of the following: the type of sensing report, or one or more sensing outputs to be indicated on the sensing report.

[0292] Aspect 15: The method according to any one of Aspects 13 to 14, wherein the one or more sensing reporting parameters indicate one or more radio resource management events or one or more sensing events to be reported.

[0293] Aspect 16: The method according to any one of Aspects 13 to 15, wherein the one or more QoS parameters indicate at least one of the following: the range or resolution of the Doppler frequency shift to be measured or reported, the distance of the sensing target to the sensing request, the range resolution of the sensing target, or the radar cross-section or support range to the sensing request.

[0294] Aspect 17: The method according to any one of Aspects 13 to 16, wherein the one or more adaptive reconfiguration parameters indicate one or more actions to be performed in connection with failure to satisfy the one or more QoS parameters.

[0295] Aspect 18: The method according to any one of aspects 1 to 17, wherein the one or more sensing parameters are associated with a plurality of sensing requests including the sensing request.

[0296] Aspect 19: The method according to any one of aspects 1 to 18, wherein the one or more sensing parameters comprise a plurality of sets of one or more sensing parameters.

[0297] Aspect 20: The method according to any one of aspects 1 to 19, wherein the one or more sensing parameters are associated with a sensing session.

[0298] Aspect 21: According to the method of aspect 20, the sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including the one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0299] Aspect 22: A method of wireless communication performed by a network node, the method comprising: receiving from a sensing management function (SnMF) entity an indication of one or more sensing parameters associated with a sensing request; and sending a sensing configuration to one or more sensing units (SUs), the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters.

[0300] Aspect 23: According to the method of aspect 22, the one or more configuration parameters include one or more radio resource control (RRC) parameters.

[0301] Aspect 24: The method according to any one of aspects 22 to 23, the method further comprising receiving an instruction for the one or more SUs from the SnMF entity.

[0302] Aspect 25: The method according to any one of aspects 22 to 24, the method further comprising selecting the one or more SUs to fulfill the sensing request.

[0303] Aspect 26: According to the method of aspect 25, selecting the one or more SUs includes selecting the one or more SUs in association with the ability of the one or more SUs to support the one or more sensing parameters.

[0304] Aspect 27: The method according to any one of Aspects 25 to 26, wherein selecting the one or more SUs includes receiving from the SnMF entity a discovery request associated with discovering a user equipment (UE) capable of supporting the one or more sensing parameters.

[0305] Aspect 28: According to the method of aspect 27, the method further includes sending an indication to the SnMF entity for one or more UEs, the one or more UEs being included in the one or more SUs, in response to receiving the discovery request.

[0306] Aspect 29: The method according to any one of Aspects 22 to 28, wherein the one or more sensing parameters include at least one of the following: detection distance parameter, Doppler range parameter, one or more quality of service (QoS) parameters, one or more sensing report parameters, or one or more adaptive reconfiguration parameters.

[0307] Aspect 30: According to the method of aspect 29, the one or more sensing report parameters indicate at least one of the following: the type of sensing report, or one or more sensing outputs to be indicated on the sensing report.

[0308] Aspect 31: The method according to any one of Aspects 29 to 30, wherein the one or more sensing reporting parameters indicate one or more radio resource management events or one or more sensing events to be reported.

[0309] Aspect 32: The method according to any one of Aspects 29 to 31, wherein the one or more QoS parameters indicate at least one of the following: the range or resolution of the Doppler shift to be measured or reported, the distance of the sensing target to the sensing request, the range resolution of the sensing target, or the radar cross-section or support range to the sensing request.

[0310] Aspect 33: The method according to any one of Aspects 29 to 32, wherein the one or more adaptive reconfiguration parameters indicate one or more actions to be performed in connection with failure to satisfy the one or more QoS parameters.

[0311] Aspect 34: The method according to any one of Aspects 22 to 33, wherein the sensing configuration includes at least one of the following: a transmission configuration, one or more measurement configurations, one or more processing configurations, one or more reporting configurations, or one or more adaptive reconfiguration configurations.

[0312] Aspect 35: According to the method of aspect 34, the transmission configuration includes a configuration for one or more sensing reference signals.

[0313] Aspect 36: The method according to any one of Aspects 34 to 35, wherein the one or more measurement configurations indicate at least one of the following for the sensing reference signal to be measured for the sensing request: one or more time-domain resources, one or more frequency-domain resources, or one or more spatial-domain resources.

[0314] Aspect 37: The method according to any one of aspects 34 to 36, wherein the one or more processing configurations indicate one or more processing outputs for the sensing data of the sensing request.

[0315] Aspect 38: The method according to any one of aspects 34 to 37, wherein the processing configuration in the one or more processing configurations indicates at least one of the following: at least one measurement configuration associated with the processing configuration in the one or more measurement configurations, or at least one reporting configuration associated with the processing configuration in the one or more reporting configurations.

[0316] Aspect 39: The method according to any one of aspects 22 to 38, wherein the one or more sensing parameters are associated with a sensing session.

[0317] Aspect 40: According to the method of aspect 39, the sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including the one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0318] Aspect 41: A method of wireless communication performed by a sensing unit (SU), the method comprising: receiving a sensing configuration via one or more radio resource control (RRC) communications, the sensing configuration indicating a sensing session associated with the sensing configuration; receiving communications indicating one or more actions to be performed for the sensing session; and performing the one or more actions for the sensing configuration in association with the sensing session.

[0319] Aspect 42: According to the method of aspect 41, the sensing configuration includes at least one of the following: a transmission configuration, one or more measurement configurations, one or more processing configurations, one or more reporting configurations, or one or more adaptive reconfiguration configurations.

[0320] Aspect 43: According to the method of aspect 42, the transmission configuration includes a configuration for one or more sensing reference signals.

[0321] Aspect 44: The method according to any one of aspects 42 to 43, wherein the one or more measurement configurations indicate at least one of the following for a sensing reference signal to be measured for the sensing configuration: one or more time-domain resources, one or more frequency-domain resources, or one or more spatial-domain resources.

[0322] Aspect 45: The method according to any one of aspects 42 to 44, wherein the one or more processing configurations indicate one or more processing outputs of sensing data for the sensing configuration.

[0323] Aspect 46: The method according to any one of aspects 42 to 45, wherein the processing configuration in the one or more processing configurations indicates at least one of the following: at least one measurement configuration associated with the processing configuration in the one or more measurement configurations, or at least one reporting configuration associated with the processing configuration in the one or more reporting configurations.

[0324] Aspect 47: The method according to any one of aspects 41 to 46, wherein the sensing session is associated with at least one of the following: a sensing session identifier, one or more sets of one or more sensing parameters including the one or more sensing parameters, one or more modes for sensing data reporting, or one or more session parameters.

[0325] Aspect 48: The method according to any one of aspects 41 to 47, wherein performing the one or more actions includes performing the one or more actions for each sensing configuration that includes the sensing configuration associated with the sensing session.

[0326] Aspect 49: The method according to any one of aspects 41 to 48, wherein receiving the communication includes: receiving an indication of an identifier for the sensing session and an indication for terminating the sensing session, and wherein the one or more actions include terminating the sensing configuration.

[0327] Aspect 50: The method according to any one of aspects 41 to 49, wherein receiving the communication comprises: receiving an indication of an identifier of the sensing session and an indication for transferring to a different communication session, and wherein the one or more actions comprise transferring the sensing configuration to the different communication session.

[0328] Aspect 51: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 50.

[0329] Aspect 52: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0330] Aspect 53: 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 50.

[0331] Aspect 54: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 50.

[0332] Aspect 55: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 50.

[0333] Aspect 56: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0334] Aspect 57: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0335] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0336] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0337] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0338] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (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).

[0339] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0340] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A sensing management function (SnMF) entity for wireless communication, the sensing management function (SnMF) entity comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the SnMF to: Receive a sensing request that specifies one or more request parameters; as well as Send an indication to one or more network nodes for one or more sensing parameters used in the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

2. The SnMF entity according to claim 1, wherein the one or more request parameters include at least one of the following: Sensing area parameters, Timing parameters, One or more Quality of Service (QoS) parameters, or Service type parameter.

3. The SnMF entity of claim 1, wherein the processing system is further configured to cause the SnMF to select one or more sensing units (SUs) to fulfill the sensing request.

4. The SnMF entity of claim 3, wherein, in order for the SnMF to select the one or more SUs, the processing system is configured to enable the SnMF to select the one or more SUs in association with the one or more sensing parameters.

5. The SnMF entity of claim 3, wherein, in order for the SnMF to select the one or more SUs, the processing system is configured to cause the SnMF to: Send a request to the storage entity for a list of Units (SUs) capable of supporting the one or more sensing parameters; and In response to sending the request, an instruction for the one or more SUs is received from the repository entity.

6. The SnMF entity of claim 3, wherein, in order for the SnMF to select the one or more SUs, the processing system is configured to cause the SnMF to send a discovery request to the one or more network nodes in association with the discovery of user equipment (UE) capable of supporting the one or more sensing parameters.

7. The SnMF entity of claim 6, wherein the processing system is further configured to cause the SnMF to receive an indication to one or more UEs from the one or more network nodes in response to sending the discovery request, the one or more UEs being included in the one or more SUs.

8. The SnMF entity of claim 1, wherein the one or more sensing parameters include at least one of the following: Detect distance parameters, Doppler range parameters One or more Quality of Service (QoS) parameters, One or more sensing reporting parameters, or One or more adaptive reconfiguration parameters.

9. The SnMF entity of claim 8, wherein the one or more sensing reporting parameters indicate at least one of the following: Types of sensing reports, or One or more sensing outputs to be indicated on the sensing report.

10. The SnMF entity of claim 8, wherein the one or more QoS parameters indicate at least one of the following: To measure or report the range or resolution of the Doppler frequency shift. The distance to the sensing target in the aforementioned sensing request. The distance resolution of the sensed target, or The radar cross-section or support range for the sensing request.

11. The SnMF entity of claim 8, wherein the one or more adaptive reconfiguration parameters indicate one or more actions to be performed in connection with failure to satisfy the one or more QoS parameters.

12. The SnMF entity of claim 1, wherein the one or more sensing parameters are associated with a sensing session.

13. The SnMF entity of claim 12, wherein the sensing session is associated with at least one of the following: Sensing session identifier, One or more sets of one or more sensing parameters, including the one or more sensing parameters. One or more modes used for sensing data reporting, or One or more session parameters.

14. A network node for wireless communication, the network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the network node to: Receive indications for one or more sensing parameters associated with the sensing request from the Sensing Management Function (SnMF) entity; as well as Send a sensing configuration to one or more sensing units (SUs), the sensing configuration including one or more configuration parameters associated with the one or more sensing parameters.

15. The network node of claim 14, wherein the processing system is further configured to cause the network node to select one or more SUs to fulfill the sensing request.

16. The network node of claim 15, wherein, in order for the network node to select the one or more SUs, the processing system is configured to enable the network node to select the one or more SUs in association with the one or more sensing parameters.

17. The network node of claim 15, wherein, in order for the network node to select the one or more SUs, the processing system is configured to cause the network node to receive from the SnMF entity a discovery request associated with discovering user equipment (UE) capable of supporting the one or more sensing parameters.

18. The network node of claim 14, wherein the one or more sensing parameters include at least one of the following: Detect distance parameters, Doppler range parameters One or more Quality of Service (QoS) parameters, One or more sensing reporting parameters, or One or more adaptive reconfiguration parameters.

19. The network node of claim 14, wherein the sensing configuration comprises at least one of the following: Send configuration, One or more measurement configurations, One or more processing configurations, One or more report configurations, or One or more adaptive reconfiguration configurations.

20. The network node of claim 19, wherein the transmission configuration includes a configuration for one or more sensing reference signals.

21. The network node of claim 19, wherein the one or more measurement configurations indicate at least one of the following for the sensing reference signal to be measured in response to the sensing request: One or more time-domain resources, One or more frequency domain resources, or One or more airspace resources.

22. The network node of claim 19, wherein the one or more processing configurations indicate one or more processing outputs for the sensing data of the sensing request.

23. A sensing unit (SU) for wireless communication, the sensing unit (SU) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the SU: Receive sensing configuration via one or more Radio Resource Control (RRC) communications, the sensing configuration indicating a sensing session associated with the sensing configuration; Receive communications instructing one or more actions to be performed for the sensing session; as well as The one or more actions are performed in connection with the sensing configuration and the sensing session.

24. The SU of claim 23, wherein, in order for the SU to receive the communication, the processing system is configured to cause the SU to: Receive an indication of the identifier of the sensing session and an indication for terminating the sensing session, and One or more of the actions include terminating the sensing configuration.

25. The SU of claim 23, wherein, in order for the SU to receive the communication, the processing system is configured to cause the SU to: Receive an indication of the identifier of the sensing session and an indication for transferring to a different communication session, and One or more of the actions include transferring the sensing configuration to the different communication session.

26. A method for wireless communication by a Sensing Management Function (SnMF) entity, the method comprising: Receive a sensing request that specifies one or more request parameters; as well as Send an indication to one or more network nodes for one or more sensing parameters used in the sensing request, the one or more network nodes being selected using the one or more request parameters, and the one or more sensing parameters being associated with the one or more request parameters.

27. The method of claim 26, wherein the one or more request parameters include at least one of the following: Sensing area parameters, Timing parameters, One or more Quality of Service (QoS) parameters, or Service type parameter.

28. The method of claim 26, further comprising selecting one or more sensing units (SUs) to fulfill the sensing request.

29. The method of claim 26, wherein the one or more sensing parameters include at least one of the following: Detect distance parameters, Doppler range parameters One or more Quality of Service (QoS) parameters, One or more sensing reporting parameters, or One or more adaptive reconfiguration parameters.

30. The method of claim 26, wherein the one or more sensing parameters are associated with a plurality of sensing requests including the sensing request.

Images