Network power saving and RF sensing

Abstract

A method of wireless communication at a network entity is disclosed. The network entity obtains an indication of an NES mode, wherein the NES mode is supported by at least one of a set of network nodes or a UE. The network entity transmits, for at least one of the set of network nodes or the UE, a configuration for at least one of an RF sensing session, a set of sensing measurements, or a set of sensing signals based on the indication of the NES mode.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 306,125, entitled “NETWORK POWER SAVING AND RF SENSING”, filed April 24, 2023, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to network power saving and radio frequency (RF) sensing. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus includes: a memory; and at least one processor coupled to the memory, and configured, at least in part based on information stored in the memory, to: obtain an indication of a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of a set of network nodes or a user equipment (UE); and, based on the indication of the NES mode, transmit configuration for at least one of the set of network nodes or the UE for an RF sensing session, a sensing measurement set, or a sensing signal transmission set.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network node are provided. The apparatus includes: a memory; and at least one processor coupled to the memory, and configured, at least in part based on information stored in the memory, to: transmit an indication of a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of the network node or user equipment (UE); and to obtain a configuration for at least one of an RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions based on the indication of the NES mode.

[0009] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0012] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figure 4 This is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0017] Figure 5 This is a diagram illustrating an example of a wireless communication system.

[0018] Figure 6 This is a diagram illustrating an example positioning procedure.

[0019] Figure 7 This is a diagram illustrating an example aspect of Network Energy Saving (NES) mode.

[0020] Figure 8 This is a diagram illustrating examples of different types of NES modes.

[0021] Figure 9 This is a diagram illustrating an example aspect of discontinuous transmission (DTX) behavior in a cell.

[0022] Figure 10 This is a diagram illustrating an example of sharing supported NES modes and supported radio frequency (RF) sensing modes with a sensing entity.

[0023] Figure 11 This is a diagram illustrating examples of supported RF sensing measurements or transmissions shared with the sensing entity for each supported NES mode.

[0024] Figure 12 This is a diagram illustrating an example of RF sensing measurements and / or transmissions performed independently of NES mode.

[0025] Figure 13 This is a diagram illustrating an example aspect of the overlapping NES mode characteristics.

[0026] Figure 14 This is a diagram illustrating an example communication flow between network entities and network nodes.

[0027] Figure 15 This is a flowchart of a wireless communication method.

[0028] Figure 16 This is a flowchart of a wireless communication method.

[0029] Figure 17 This is a flowchart of a wireless communication method.

[0030] Figure 18 This is a flowchart of a wireless communication method.

[0031] Figure 19These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0032] Figure 20 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0033] Figure 21 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0034] The network can implement Network Energy Saving (NES) modes to reduce the energy / power consumption of UEs and / or network nodes in the network. For example, the network can reduce the number of antenna ports used by the UE for wireless communication to reduce the UE's power consumption. UEs and / or network nodes in the network can also be configured to perform RF sensing measurements and / or transmissions, which can be used for positioning, navigation, and timing purposes. In one example, RF sensing measurements and / or transmissions can be used to determine the location of the UE. Some networks may not consider the impact of NES modes on RF sensing measurements and / or transmissions, and vice versa. For example, some NES modes may be incompatible with certain types of RF sensing measurements and / or transmissions.

[0035] This document describes various aspects generally involving network power saving and RF sensing. Some aspects relate more specifically to NES mode and RF sensing. In some examples, a network entity receives an indication of an NES mode, where the NES mode is supported by at least one of a set of network nodes or a UE. Based on the indication of the NES mode, the network entity sends a configuration for at least one of the set of network nodes or UEs for an RF sensing session, a sensing measurement set, or a sensing signal transmission set.

[0036] 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, by sending configurations for at least one of an RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions, a network entity can enable the realization of the benefits of RF sensing measurements and / or transmissions (e.g., UE location determination) while saving power / energy in the network via NES mode. Therefore, what is described above enables RF sensing measurements and / or transmissions to be performed in a manner consistent with NES mode.

[0037] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0038] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0039] As an example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0040] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0041] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0042] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0043] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0044] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0045] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0046] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0047] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 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 110 can be implemented to communicate with the DU 130 for network control and signaling purposes, as needed.

[0048] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0049] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in cloud-based RAN architectures such as vRAN architectures.

[0050] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support 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, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0051] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

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

[0053] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carrier can be referred to as the secondary cell (SCell).

[0054] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0055] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether a channel is available before communication.

[0056] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0057] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125GHz–24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher bands falls within the EHF band.

[0058] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0059] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0060] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0061] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0062] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0063] Refer again Figure 1 In some aspects, the core network 120 may have an NES mode component 198, which is configured to: obtain an indication of an NES mode, wherein the NES mode is supported by at least one of a set of network nodes or a UE; and, based on the indication of the NES mode, transmit configuration for at least one of the set of network nodes or the UE for an RF sensing session, a sensing measurement set, or a sensing signal transmission set. In some aspects, the base station 102 may have an NES mode component 199, which is configured to: transmit an indication of an NES mode, wherein the NES mode is supported by at least one of the network nodes or a UE; and, based on the indication of the NES mode, obtain configuration for at least one of the RF sensing session, a sensing measurement set, or a sensing signal transmission set. Although the following description focuses on 5G NR, the concepts presented herein are also applicable to other types of wireless communication systems.

[0064] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0065] Figures 2A-2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0066]

[0067] Table 1: Parameter Set, SCS, and CP

[0068] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A-2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0069] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0070] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0071] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0072] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0073] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0074] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0075] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine decoding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel state feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can utilize the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0076] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0077] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0078] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0079] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0080] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0081] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0082] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupled operations. Figure 1 The NES mode component 199 in various aspects.

[0083] Figure 4 Figure 400 illustrates an example of UE positioning based on reference signal measurements. UE 404 can be positioned at time T. SRS_TX Send UL-SRS 412 and at time T PRS_RX Receives the DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 can be used at time T. SRS_RX Receive UL-SRS 412 and at time T PRS_TX Send DL-PRS 410. UE 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168) or UE 404 may base its response on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UE Rx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple TRPs 402, 406 and measured by UE 404. SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (i.e., |T) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. SRS_RX – T PRS_TX |) and UL-SRS-RSRP. UE 404 uses auxiliary data received from the location server to measure the UE Rx-Tx time difference (and optionally the DL-PRS-RSRP of the received signal), and TRPs 402 and 406 use auxiliary data received from the location server to measure the gNB Rx-Tx time difference (and optionally the UL-SRS-RSRP of the received signal). These measurements can be used at the location server or at UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0084] DL-AoD positioning utilizes the measured DL-PRS-RSRP of downlink signals received at UE 404 from multiple TRPs 402 and 406. UE 404 uses auxiliary data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information, is used to position UE 404 relative to adjacent TRPs 402 and 406.

[0085] DL-TDOA positioning utilizes the DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0086] UL-TDOA positioning utilizes the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from the positioning server to measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the location of UE 404.

[0087] UL-AoA positioning utilizes the measured azimuth (A-AoA) and zenith (Z-AoA) of the uplink signal transmitted from UE 404 at multiple TRPs 402 and 406. TRPs 402 and 406 use auxiliary data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the position of UE 404.

[0088] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0089] Figure 5Figure 500 illustrates an example of estimating the location of a UE based on multi-RTT measurements from multiple TRPs according to various aspects of this disclosure. The UE 502 may be configured by the serving base station to decode DL-PRS resources 512 corresponding to and transmitted from the first TRP 504 (TRP-1), the second TRP 506 (TRP-2), the third TRP 508 (TRP-3), and the fourth TRP 510 (TRP-4). UE 502 can also be configured to transmit UL-SRS on a UL-SRS resource set, which may include a first SRS resource 514, a second SRS resource 516, a third SRS resource 518, and a fourth SRS resource 520, such that the serving cell (e.g., a first TRP 504, a second TRP 506, a third TRP 508, and a fourth TRP 510) and other neighboring cells can measure the UL-SRS resource set transmitted from UE 502. For multi-RTT measurements based on DL-PRS and UL-SRS, since there may be a correlation between the UE's DL-PRS measurement and the TRP's UL-SRS measurement, the smaller the gap between the UE's DL-PRS measurement and the UE's UL-SRS transmission, the better the accuracy of estimating the UE's location and / or the UE's distance to each TRP.

[0090] In some aspects of wireless communication, the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. In some aspects, downlink positioning reference signals may be referred to as "DL-PRS," while uplink positioning reference signals (e.g., positioning SRS, PTRS) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS."

[0091] Figure 6This is a communication flow 600 illustrating an example multi-RTT positioning procedure according to various aspects of this disclosure. The numbering associated with communication flow 600 does not specify a particular time order and is used only as a reference for communication flow 600. Furthermore, one or more subsets of this multi-RTT positioning procedure may be used for DL-only and / or UL-only positioning.

[0092] At 610, LMF 606 may request one or more positioning capabilities from UE 602 (e.g., from the target device). In some examples, the request for one or more positioning capabilities from UE 602 may be associated with the LTE Positioning Protocol (LPP). For example, LMF 606 may use the LPP capability delivery procedure to request positioning capabilities from UE 602. At 612, LMF 606 may request UL SRS configuration information from UE 602. LMF 606 may also provide auxiliary data (e.g., path loss reference, spatial relationships, and / or SSB configuration, etc.) specified by the serving base station 604. For example, LMF 606 may transmit an NR Positioning Protocol A (NRPPa) positioning information request message to the serving base station 604 to request UL information from UE 602.

[0093] At 614, the serving base station 604 may determine the resources available for UL SRS, and at 616, the serving base station 604 may configure one or more UL SRS resource sets for UE 602 based on the available resources. At 618, the serving base station 604 may provide UL SRS configuration information to LMF 606, such as via an NRPPa location information response message. At 620, LMF 606 may select one or more candidate neighbor BS / TRP 608, and LMF 606 may provide UL SRS configuration to one or more candidate neighbor BS / TRP 608 and / or the serving base station 604, such as via an NRPPa measurement request message. The message may include information to enable one or more candidate neighbor BS / TRP 608 and / or the serving base station to perform UL measurements.

[0094] At 622, LMF 606 may transmit an LPP (Local Power Request) auxiliary data message to UE 602. The message may include specified auxiliary data for UE 602 to perform DL (Low-Distance) measurements. At 624, LMF 606 may transmit an LPP request location information message to UE 602 to request multi-RTT (Multi-Round-Trip) measurements. At 626, for semi-persistent or aperiodic UL SRS, LMF 606 may request serving base station 604 to activate / trigger UL SRS in UE 602. For example, LMF 606 may request activation of UE SRS transmission by transmitting an NRPPa (Location Activation Request) message to serving base station 604.

[0095] At 628, the serving base station 604 can activate UE SRS transmission and transmit an NRPPa location activation response message. In response, UE 602 can begin UL-SRS transmission according to the temporal behavior configured for UL SRS resources. At 630, UE 602 can perform DL measurements from one or more candidate neighbor BS / TRP 608 and / or serving base station 604, as provided in the auxiliary data. At 632, each of the one or more configured candidate neighbor BS / TRP 608 and / or serving base station 604 can perform UL measurements. At 634, UE 602 can report the DL measurements to LMF 606, such as via an LPP location information message. At 636, each of the one or more candidate neighbor BS / TRP 608 and / or serving base station 604 can report the UL measurements to LMF 606, such as via an NRPPa measurement response message. At 638, LMF 606 can determine the RTT from UE 602 and the BS / TRP Rx-Tx time difference measurement of each of one or more candidate neighbor BS / TRP 608 and / or serving base station 604 that provides corresponding UL and DL measurements at 634 and 636, and LMF 606 can calculate the location of UE 602.

[0096] Some aspects of wireless communication can utilize different types of Positioning Reference Signals (PRS), such as downlink (DL) PRS. PRS is utilized by different wireless communications (e.g., New Radio (NR)) and positioning methods to enable devices (e.g., UEs) to detect and measure different objects. For example, a PRS can enable a UE to detect and measure the increase of neighboring TRPs or base stations. Several different types of positioning configurations are supported in wireless communications to enable various deployments or environments (e.g., indoor environments, outdoor environments, sub-6 environments, mmW environments) for devices or UEs. Different types of wireless communications (e.g., NR) support both UE-assisted positioning methods (e.g., computational) and UE-based positioning methods. Furthermore, specific types of wireless communications (e.g., NR) can support several types of positioning methods. For example, NR positioning methods can support at least one of the following: NR multiple round-trip time (multiple RTT) positioning, NR downlink (DL) time difference of arrival (DL-TDOA) positioning, or NR DL departure angle (DL-AoD) positioning.

[0097] In some aspects, different types of reference signals (e.g., downlink (DL) or uplink (UL) reference signals) and UE measurements can be used to facilitate support for different positioning technologies. For example, DL PRS and DL reference signal time difference (RSTD) UE measurements can facilitate support for DL-TDOA positioning. Additionally, DL PRS and DL PRS reference signal received power (RSRP) UE measurements can facilitate support for DL-TDOA positioning, DL-AoD positioning, and / or multi-RTT positioning. Furthermore, DL PRS and probe reference signals (SRS) used for positioning and UE receive (Rx)-transmit (Tx) time difference UE measurements can facilitate support for multi-RTT positioning. Furthermore, synchronization signal blocks (SSBs) and channel state information (CSI)-reference signals (CSI-RS) used for radio resource management (RRM), as well as synchronization signal (SS)-RSRP (e.g., RSRP for RRM), SS-reference signal reception quality (SS-RSRQ) (e.g., for RRM), CSI-RSRP (e.g., for RRM) and CSI-RSRP (e.g., for RRM) can facilitate support for enhanced cell identifier (ID) (E-CID) location.

[0098] Different aspects of positioning can also utilize pre-configured DL PRS auxiliary data (AD). Pre-configured DL PRS AD can refer to DL-PRS auxiliary data (with associated validity criteria) that can be provided to the UE (e.g., before or during an ongoing LTE Location Protocol (LPP) positioning session) and then used at a later time for potential positioning measurements (e.g., for a delayed Mobile Termination Location Request (MT-LR)). In some aspects, pre-configured DL-PRS auxiliary data can include multiple instances, each applicable to a different area within the network. Additionally, each DL-PRS auxiliary data instance can be associated with an area ID. In some instances, the area ID can include a list of cells the UE can camp on / connect to. Furthermore, the applicable area ID for the UE's location can be selected based on the cells the UE camps on / connects to. If the UE camps on / connects to one of the cells indicated in the cell list within the area ID, the instance of auxiliary data can be valid / selected.

[0099] Figure 7Figure 700 illustrates an example aspect of Network Energy Saving (NES) modes. A network can utilize different NES modes and / or operations to save energy / power and maintain network operation. An NES mode can refer to a specific energy / power saving operation performed by the network. An NES mode can also be called a network energy-saving state. NES modes can be semi-static or dynamic. Semi-static NES modes can be applied in a regular or semi-regular manner. Dynamic NES modes can be activated by receiving and / or transmitting signals and / or data. The network can switch NES modes (i.e., power modes) based on network input. In one example, an NES mode may include bandwidth adaptation, antenna adaptation, and / or transmit power adaptation. NES modes can be signaled to the UE and / or network nodes so that the UE and / or network nodes can apply configurations / behaviors associated with the NES mode.

[0100] In one example, a network node and / or UE may be configured with a first NES mode 702, a flexible NES mode 704, and a second NES mode 706. The first NES mode 702, flexible NES mode 704, and second NES mode 706 may be periodically repeated 708. In one example, the first NES mode 702 may be associated with a first set of energy / power saving characteristics, and the second NES mode 706 may be associated with a second set of energy / power saving characteristics. The flexible NES mode 704 may be a flexible mode dynamically indicated by the network based on current network service conditions. For example, the flexible NES mode 704 may be the first NES mode 702, the second NES mode 706, another NES mode, or a mode not associated with network energy / power saving (e.g., normal network operation). In addition to the first NES mode 702, flexible NES mode 704, and second NES mode 706, the network node and / or UE may also be configured for periods of normal network operation.

[0101] Figure 8 Figure 800 illustrates examples of different types of NES modes. In a first example 802, a first NES mode 702 could be an operating mode in which the network (e.g., a network node, such as a base station) serves the UE through 64 antenna ports, and a second NES mode 706 could be an operating mode in which the network serves the UE through 32 antenna ports. Serving the UE through 32 antenna ports can be associated with reduced energy / power consumption compared to serving the UE through 64 antenna ports.

[0102] In the second example 804, the first NES mode 702 can be an operating mode in which the UE utilizes a light sleep mode while sleeping, and the second NES mode 706 can be an operating mode in which the UE utilizes a deep sleep mode while sleeping. Compared to a light sleep mode, a deep sleep mode can be associated with reduced energy / power consumption. For example, the UE can execute fewer background processes when in a deep sleep mode compared to the number of background processes executed when in a light sleep mode.

[0103] In the third example 806, the first NES mode 702 can be an operating mode applied to DL communication, and the second NES mode 706 can be an operating mode applied to both DL communication and UL communication. For example, the UE (and / or network node) can implement power-saving features for DL ​​communication (but not UL communication) in the first NES mode 702, and the UE (and / or network node) can implement power-saving features for both DL communication and UL communication in the second NES mode 706.

[0104] In the fourth example 808, the first NES mode 702 can be an operating mode associated with periodic cell discontinuous transmission (DTX), and the second NES mode 706 can be an operating mode associated with dynamic cell DTX. Cell DTX will be discussed in more detail below.

[0105] Figure 9 Figure 900 illustrates an example aspect of cell discontinuous transmission (DTX) behavior. DTX behavior can refer to the behavior in which a network node (e.g., a base station, gNB) has the opportunity to be inactive. During the inactive period, the network node may not transmit some periodic signals / channels, such as common signals / channels or UE-specific signals / channels. During the inactive period, the network node may not transmit signals / channels or the network node may transmit a limited set of signals / channels. In one aspect, the base station may not skip the transmission of SSBs during the inactive period associated with cell DTX. In one aspect, the inactive period (i.e., the DTX period) may be shorter than the period associated with the transmission of SSBs. In one aspect, when entering the inactive period associated with cell DTX, the network node may send an indication to the UE, instructing the UE to stop monitoring the PDCCH and the UE to terminate the measurement of CSI-RS. Cell DTX may also be referred to as DTX.

[0106] Cell DTX can be associated with Discontinuous Reception (DRX). During DRX, network nodes (e.g., base stations, gNBs) may have opportunities to be inactive. During the inactive period, network nodes may not receive some periodic signals / channels, such as common signals / channels or UE-specific signals / channels. During the inactive period, network nodes may not receive any signals / channels or may receive a limited set of signals / channels. In Connected Mode DRX (C-DRX), the DRX cycle or offset configured for a UE in connected mode or idle / inactive mode can be aligned, potentially providing a longer inactive period at the network node and thus reducing the number of activities performed by the network node outside of the UE's DRX active time (e.g., transmission of SSB, Configuration Grant (CG)PUSCH, RACH Timing (RO), etc.).

[0107] In one aspect, network nodes may enter an inactive state during a time period associated with network adaptation to DTX / DRX. For example, in DTX / DRX, network nodes (e.g., base stations) may enter an inactive state at different time granularities. In some instances, C-DRX can be configured on a per-UE basis, and depending on the scheduler, a DTX period for one UE may be an active period for another UE. In such instances, base stations may schedule different UEs in different time periods, and the remaining inactive time for network nodes may be finite. Alignment of DRX cycles and / or offsets can be performed via RRC reconfiguration. DTX / DRX can be configured to increase inactive periods (i.e., increase inactive duration). In another aspect, UEs may monitor certain channels / signals outside of active DRX times, which may result in a corresponding reduction in the active time of network nodes.

[0108] In the first example 902, DTX can be configured with a periodic pattern (e.g., a predefined periodic pattern). For example, a Tx active mode 904 can be followed by a Tx inactive mode 906, where Tx active mode 904 and Tx inactive mode 906 can be repeated periodically 908. In the first example 902, each instance of Tx active mode 904 can have the same duration, and each instance of Tx inactive mode 906 can have the same duration.

[0109] In the second example 910, DTX can be configured dynamically, that is, the inactive state of a network node Tx (e.g., the inactive state of a base station Tx) can be dynamically activated via triggering DCI 912. For example, if Tx activity mode 904 is currently active, then Tx inactivity mode 906 can be activated by triggering DCI 912. In the second example 910, based on the time of sending (or receiving) triggering DCI 912, each instance of Tx activity mode 904 can have the same or different durations, and each instance of Tx inactivity mode 906 can have the same or different durations.

[0110] The network can implement Network Energy Saving (NES) modes to reduce the energy / power consumption of UEs and / or network nodes in the network. For example, the network can reduce the number of antenna ports used by the UE for wireless communication to reduce the UE's power consumption. UEs and / or network nodes in the network can also be configured to perform RF sensing measurements and / or transmissions, which can be used for positioning, navigation, and timing purposes. In one example, RF sensing measurements and / or transmissions can be used to determine the location of the UE. Some networks may not consider the impact of NES modes on RF sensing measurements and / or transmissions, and vice versa. For example, some NES modes may be incompatible with certain types of RF sensing measurements and / or transmissions.

[0111] This document describes various techniques related to network power saving and RF sensing. In one example, a network entity receives an indication of an NES mode, where the NES mode is supported by at least one of a set of network nodes or a UE. Based on the indication of the NES mode, the network entity sends a configuration for at least one of the set of network nodes or UEs for an RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions. RF sensing measurements and / or transmissions can be performed in a manner consistent with the NES mode as described above. For example, by sending a configuration for at least one of the RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions, the network entity can enable the realization of the benefits of RF sensing measurements and / or transmissions (e.g., UE location determination) while saving power / energy in the network via the NES mode.

[0112] NES modes can enable different operations to save power while maintaining network operation. In one aspect, NES modes can be shared with sensing modes to configure adapted RF sensing sessions, measurements, and / or transmissions. Certain RF sensing measurements may be supported in some NES modes, while these measurements may not be supported in others. For example, Doppler processing may be associated with a TRP that transmits and / or receives a reference signal over a long duration that can span multiple NES cycles. In another example, in some NES modes with antenna adaptation / reduction, angle maps may not be reliably obtained due to the limited number of antennas, and therefore angle maps may not be supported in such NES modes.

[0113] Figure 10 Figure 1000 illustrates an example of a sensing entity sharing supported NES modes and supported radio frequency (RF) sensing modes. Understanding the NES mode configuration (e.g., a semi-static NES mode configuration) allows the sensing entity to configure adapted RF sensing sessions, sensing measurements, and / or sensing transmissions. For example, certain RF sensing measurements may be supported in some NES modes but not in others. To enable the sensing entity to configure adapted RF sensing sessions, sensing measurements, and / or sensing transmissions, the sensing entity can be informed of the RF sensing measurements (or sensing transmissions) supported for each NES mode. In one example, to support Doppler processing, the TRP may transmit or receive reference signals over a time span across multiple NES cycles (e.g., multiple instances of different NES modes are active). In another example, for NES modes associated with antenna adaptation / reduction (e.g., as in the first example 802), angle maps may not be reliably obtained due to the limited number of antennas supported by a particular NES mode, and therefore, the particular NES mode may not support angle maps.

[0114] In the first example 1002, the core network 1004 (e.g., core network 120) may include a sensing entity 1006. Sensing entity 1006 may be a core network entity responsible for managing and coordinating sensing sessions. A sensing session may refer to a period of time in which sensing measurements are performed and / or in which sensing signals are transmitted. A network node 1008 (e.g., a gNB) may send indications to sensing entity 1006 regarding supported NES modes 1010 and / or supported RF sensing modes 1012. Supported NES modes 1010 may also be referred to as NES configurations. In one aspect, supported NES modes 1010 may refer to a semi-static configuration supported and implemented by the network (e.g., network node 1008) for the purpose of saving network energy / power. For example, supported NES modes 1010 may be in the form of NES mode changing and / or DTX cycling. The supported NES mode 1010 and / or the supported RF sensing mode 1012 may be supported by network node 1008 and / or UE 1014. In one example, the supported NES mode 1010 may be or may be included in Figure 8 The aspects described in one or more of the first example 802, the second example 804, the third example 806, and / or the fourth example 808. In one example, the supported RF sensing mode 1012 may include Doppler-correlated sensing and / or angle-map-correlated sensing. In one aspect, network node 1008 may send an indication of supported NES mode 1010 and / or an indication of supported RF sensing mode 1012 based on receiving a request from sensing entity 1006. In another aspect, network node 1008 may send an indication of supported NES mode 1010 and / or an indication of supported RF sensing mode 1012 without receiving a request from sensing entity 1006.

[0115] Sensing entity 1006 may generate configuration 1016 for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets based on indications of supported NES modes 1010 and / or supported RF sensing modes 1012. Configuration 1016 may be used by network node 1008 and / or UE 1014. Sensing entity 1006 may send configuration 1016 to network node 1008. Sensing entity 1006 may send configuration 1016 to UE 1014.

[0116] In the second example 1018, network node 1008 may send an indication of a supported NES mode 1010 and / or an indication of a supported RF sensing mode 1012 to an LMF 1020 (e.g., LMF 166, LMF 606) of core network 1004. In one aspect, network node 1008 may send the indication of a supported NES mode 1010 and / or an indication of a supported RF sensing mode 1012 upon receiving a request from LMF 1020. In another aspect, network node 1008 may send the indication of a supported NES mode 1010 and / or an indication of a supported RF sensing mode 1012 without receiving a request from LMF 1020. LMF 1020 may send the indication of a supported NES mode 1010 and / or an indication of a supported RF sensing mode 1012 to sensing entity 1006. For example, LMF 1020 may transmit indications of supported NES mode 1010 and / or supported RF sensing mode 1012 via a signaling protocol defined between LMF 1020 and sensing entity 1006, wherein auxiliary data may be shared via the signaling protocol. The auxiliary data may be or include indications of supported NES mode 1010 and / or supported RF sensing mode 1012. Sensing entity 1006 may generate configuration 1016 as described above, and sensing entity 1006 may send configuration 1016 to network node 1008. Network node 1008 may send configuration 1016 to UE 1014.

[0117] In both the first example 1002 and the second example 1018, network node 1008 and / or UE 1014 may perform an RF sensing session, a set of sensed measurements, and / or a set of sensed signal transmissions based on configuration 1016. Subsequently, network node 1008 may send an update request to sensing entity 1006, wherein the update request may be associated with an NES mode different from the NES mode associated with supported NES mode 1010 and / or a different RF sensing mode associated with supported RF sensing mode 1012. Sensing entity 1006 may generate a second configuration based on the update request, wherein the second configuration is used for network node 1008 and / or UE 1014. Sensing entity 1006 may send the second configuration to network node 1008. Network node 1008 may send the second configuration to UE 1014. Network node 1008 and / or UE 1014 may perform a second RF sensing session, a second set of sensed measurements, and / or a second set of sensed signal transmissions based on the second configuration.

[0118] Figure 11Figure 1100 illustrates an example of sharing supported RF sensing measurements or transmissions for each supported NES mode with a sensing entity. In some scenarios, RF sensing (e.g., RF sensing sessions, performing sets of sensing measurements, and / or transmitting sensing signals) may be a higher priority than saving network power. For example, RF sensing sessions may be aperiodic (i.e., RF sensing sessions may not occur frequently), while network power saving may be beneficial over relatively long periods of time but not beneficial over relatively short periods of time. Therefore, the network (e.g., network nodes) may signal to the sensing entity the RF sensing measurements and / or transmissions supported for each NES mode.

[0119] In one aspect, network node 1008 may send an indication of a first supported NES mode 1102, wherein the first supported NES mode 1102 is determined by network node 1008 and / or UE 1014. Figure 11 (Not depicted in the text) is supported. Network node 1008 can also send an indication for a first supported RF sensing measurement or transmission 1104 and an indication for an Nth supported RF sensing measurement or transmission 1106, where N is a positive integer greater than one, and where the first supported NES mode 1102 supports the first supported RF sensing measurement or transmission 1104 and the Nth supported RF sensing measurement or transmission 1106. Network node 1008 can send an indication for a Pth supported NES mode 1108, where P is a positive integer greater than one, and where the Pth supported NES mode 1108 is supported by network node 1008 and / or UE 1014 ( Figure 11 (Not depicted in the text) Support. Network node 1008 may also send an indication for a first supported RF sensing measurement or transmission 1110 and an indication for an R-th supported RF sensing measurement or transmission 1112, where R is a positive integer greater than one, and where the P-th supported NES mode 1108 supports both the first supported RF sensing measurement or transmission 1110 and the R-th supported RF sensing measurement or transmission 1112. Sensing entity 1006 may generate configuration 1016 based on a first supported NES mode 1102, a first supported RF sensing measurement or transmission 1104 supported by the first supported NES mode 1102, an Nth supported RF sensing measurement or transmission 1106 supported by the first supported NES mode 1102, a Pth supported NES mode 1108, a first supported RF sensing measurement or transmission 1110, and / or an Rth supported RF sensing measurement or transmission 1112 supported by the Pth supported NES mode 1108. Sensing entity 1006 may transmit configuration 1016 for network node 1008 and / or UE 1014.

[0120] Figure 12Figure 1200 illustrates an example of RF sensing measurements and / or transmissions performed independently of the NES mode. In one aspect, the configuration for RF sensing measurements and / or transmissions may indicate that certain RF sensing measurements and / or transmissions should be performed regardless of the NES mode (i.e., certain RF sensing measurements and / or transmissions are unaffected by the NES mode). In such an aspect, the TRP may perform RF sensing measurements and / or transmissions regardless of the ongoing NES mode. This can be applied to semi-statically configured or dynamic NES modes. Such an aspect may be based on whether a network node (e.g., a gNB) supports performing RF sensing measurements and / or transmissions regardless of the ongoing NES mode. The network node may indicate this support to the sensing entity. In another aspect, whether the NES mode affects RF sensing measurements and / or transmissions may be based on the type of RF sensing measurements and / or transmissions. In one example, non-periodic RF sensing measurements and / or transmissions may be unaffected by NES mode (i.e., non-periodic RF sensing measurements and / or transmissions can be performed regardless of NES mode), while periodic and semi-persistent RF sensing measurements and / or transmissions may be affected by NES mode (i.e., periodic and semi-persistent RF sensing measurements and / or transmissions may not be performed if NES mode does not support them).

[0121] In Example 1202, network node 1008 may send an indication 1204 of support for independent RF sensing measurements and / or transmissions, wherein the indication indicates that network node 1008 supports performing RF sensing measurements and / or transmissions regardless of the ongoing NES mode. Sensing entity 1006 may receive the indication of support for independent RF sensing measurements and / or transmissions 1204, and the sensing entity may generate configuration 1016 based on the indication of support for independent RF sensing measurements and / or transmissions 1204. Sensing entity 1006 may send configuration 1014 for network node 1008 and / or UE. Figure 12 Configuration 1016 (not described in the text).

[0122] At 1206, network node 1008 can operate in NES mode based on configuration 1016, where NES mode does not support a certain type of RF sensing or measurement. At 1208, even if NES mode does not support RF sensing measurements and / or transmission, network node 1008 can still perform RF sensing measurements and / or transmission.

[0123] Figure 13Figure 1300 illustrates an example aspect of overlapping NES mode characteristics. For dynamic NES mode changes, the network node and / or UE may not signal the dynamic change in operating NES mode to the sensing entity. Simultaneously, the sensing mode may be configured with certain TRPs to perform RF sensing measurements, which may sometimes fail to be performed due to NES mode characteristics. In such instances, an error reason can be provided to the sensing entity.

[0124] In Example 1302, network node 1008 can operate in NES mode associated with a first NES mode feature 1304 and a second NES mode feature 1306. The first NES mode feature 1304 and the second NES mode feature 1306 may overlap with a specific type of RF sensing measurement and / or transmission; that is, the first NES mode feature 1304 and the second NES mode feature 1306 may be incompatible with each other with respect to a specific type of RF sensing measurement and / or transmission. Network node 1008 may attempt to perform the specific type of RF sensing measurement and / or transmission. Network node 1008 may generate a network power saving mode error 1308, indicating that network node 1008 cannot perform the specific RF sensing measurement and / or transmission due to the overlapping NES mode features (i.e., because the first NES mode feature 1304 overlaps with the second NES mode feature 1306). Network node 1008 may send the network power saving mode error 1308 to sensing entity 1006.

[0125] Figure 14 This is a diagram 1400 illustrating example communication between network entity 1402 and network node 1404. In one example, network entity 1402 may be sensing entity 1006. In one example, network node 1404 may be network node 1008.

[0126] At 1406, network entity 1402 may obtain an indication of the NES mode and / or RF sensing mode supported by network node 1404 and / or the UE. For example, in one aspect, at 1408, network entity 1402 may receive an indication of the NES mode and / or RF sensing mode from network node 1404, wherein the indication is sent by network node 1404. In another aspect, at 1410, network entity 1402 may send a request for an indication of the NES mode and / or RF sensing mode. In such an aspect, network node 1404 may send an indication of the NES mode and / or RF sensing mode based on receiving the request. At 1412, network entity 1402 may send a configuration for the RF sensing session, sensing measurement set, and / or sensing signal transmission set based on the indication obtained at 1406. At 1414, network node 1404 may execute the sensing signal measurement set and / or sensing signal transmission set based on the configuration. In one aspect, the sensing signal measurement set and / or sensing signal transmission set may be executed by network node 1404 during an RF sensing session, wherein the RF sensing session is executed based on configuration. At 1415, network node 1404 may send configuration for the RF sensing session, sensing measurement set, and / or sensing signal transmission set to the UE. In one aspect, the UE may execute the sensing signal measurement set and / or sensing signal transmission set based on configuration. In another aspect, the sensing signal measurement set and / or sensing signal transmission set may be executed by the UE during an RF sensing session, wherein the RF sensing session is executed based on configuration. The UE may send the sensing signal measurement set and / or sensing signal transmission set to network node 1404, and network node 1404 may receive the sensing signal measurement set and / or sensing signal transmission set.

[0127] In one aspect, due to overlapping NES mode characteristics, network node 1404 may be unable to perform a set of sense signal measurements and / or a set of sense signal transmissions. In such an aspect, at 1416, network node 1404 may send an error message to network entity 1402 indicating that network node 1404 is unable to perform a set of sense signal measurements and / or a set of sense signal transmissions due to overlapping NES mode characteristics. At 1418, network entity 1402 may receive the error message.

[0128] In one aspect, at 1420, network node 1404 may send an update request associated with the configuration to network entity 1402. At 1422, network entity 1402 may receive the update request. At 1424, network entity 1402 may send the updated configuration for the RF sensing session, sensing measurement set, and / or sensing signal transmission set based on the update request.

[0129] Figure 15This is a flowchart 1500 of a wireless communication method. The method can be performed by network entities (e.g., core network 120, core network 1004, sensing entity 1006, network entity 1402, network entity 2160). The method can be associated with reduced power consumption in the network. In one example, the method can be performed by NES mode component 198.

[0130] At point 1502, the network entity receives an indication of the NES mode, wherein the NES mode is supported by at least one of the network node set or the UE. For example, Figure 14 At 1406, it is shown that network entity 1402 can obtain an indication of the NES modes supported by network node 1404 and / or UE. In one example, the NES modes may include the above-described combination of... Figures 7-9 The aspects described. In another example, the indication of NES mode may include an indication of the supported NES mode 1010. In one example, the network node set may be or may include network node 1008 and the UE may be or may include UE 1014. In one example, 1502 may be performed by NES mode component 198.

[0131] At 1504, the network entity sends a configuration for at least one of the following: an RF sensing session, a sensing measurement set, or a sensing signal transmission set, based on an indication of the NES mode. For example, Figure 14 At 1412, it is shown that network entity 1402 may send configurations for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets to network node 1404 or UE based on the instructions obtained at 1406. In one example, the configuration may be or include configuration 1016. In one example, RF sensing measurements may be or include distance maps, angle maps, and / or point clouds. In one example, sensing signal transmission in the sensing signal transmission set may be similar to SRS for positioning, where SRS is a signal transmitted by the UE for positioning purposes. In one example, 1504 may be performed by NES mode component 198.

[0132] Figure 16 This is a flowchart 1600 of a wireless communication method. The method can be performed by network entities (e.g., core network 120, core network 1004, sensing entity 1006, network entity 1402, network entity 2160). The method can be associated with reduced power consumption in the network. In one example, the method (including various aspects detailed below) can be performed by NES mode component 198.

[0133] At point 1604, the network entity receives an indication of the NES mode, wherein the NES mode is supported by at least one of the network node set or the UE. For example, Figure 14At 1406, it is shown that network entity 1402 can obtain an indication of the NES modes supported by network node 1404 and / or UE. In one example, the NES modes may include the above-described combination of... Figures 7-9 The aspects described. In another example, the indication of NES mode may include an indication of the supported NES mode 1010. In one example, the network node set may be or may include network node 1008 and the UE may be or may include UE 1014. In one example, 1604 may be performed by NES mode component 198.

[0134] At point 1606, the network entity sends a configuration for at least one of the following: an RF sensing session, a sensing measurement set, or a sensing signal transmission set, based on an indication of the NES mode. For example, Figure 14 At 1412, it is shown that network entity 1402 may send configurations for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets to network node 1404 or UE based on the instructions obtained at 1406. In one example, the configuration may be or include configuration 1016. In one example, 1606 may be performed by NES mode component 198.

[0135] In one aspect, obtaining an indication of the NES mode may include receiving an indication from at least one of the following: one or more network nodes in a set of network nodes, or a second network entity. For example, Figure 14 At 1408, it is shown that network entity 1402 can receive instructions from network node 1404. In another example, Figure 10 The first example 1002 shows that the sensing entity 1006 can receive an indication of the supported NES mode 1010 from the network node 1008. In yet another example, the second example 1018 shows that the network entity can receive an indication of the supported NES mode 1010 from the LMF 1020 (i.e., the second network entity).

[0136] In one aspect, at 1602, a network entity may send a request for an indication of the NES mode to a set of network nodes, wherein obtaining the indication of the NES mode may include obtaining the indication of the NES mode based on the request. For example, Figure 14 At 1410, it is shown that network entity 1402 can send a request for an indication of NES mode to network node 1404. Furthermore, at 1406, the indication can be obtained based on the request sent at 1410. In one example, 1602 can be performed by NES mode component 198.

[0137] In one aspect, the NES mode may be associated with at least one of the following: the number of antenna ports used for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set; the sleep mode type; the cell DTX; the UL state; or the DL state. The UL state may refer to a state in which the network is performing UL-related operations (rather than DL-related operations). The DL state may refer to a state in which the network is performing DL-related operations (rather than UL-related operations). For example, the foregoing aspects may be combined with the above. Figures 7-9 The described aspects are related.

[0138] In one aspect, at point 1608, network entities can receive update requests associated with the configuration based on the sent configuration. For example, Figure 14 At 1422, it is shown that network entity 1402 can receive an update request associated with the configuration based on the configuration sent at 1412. In one example, 1608 can be performed by NES mode component 198.

[0139] In one aspect, at 1610, the network entity may, based on an update request, send an updated configuration for at least one of the network node set or UE, for an RF sensing session, a sensing measurement set, or a sensing signal transmission set. For example, Figure 14 At 1424, it is shown that network entity 1402 can send an updated configuration for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets to network node 1404 or UE. In one example, 1610 can be performed by NES mode component 198.

[0140] In one aspect, the configuration may indicate one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal transmission in the set of sensing signal transmissions. For example, configuration 1016 may indicate one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal transmission in the set of sensing signal transmissions. The foregoing aspect may correspond to the above combination. Figure 11 The aspects described.

[0141] In one aspect, the configuration may instruct at least one of the network node set or UE to perform at least one of the sensing measurement set or sensing signal transmission set independently of at least one of the NES mode-supported sensing measurement set or sensing signal transmission set. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0142] In one aspect, the indication of the NES mode can instruct the network node set to support performing at least one of the sensing measurement set or sensing signal transmission set independently of the NES mode. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0143] In one aspect, the configuration may instruct one or more of the following: at least one of the network node set or the UE will perform the aperiodic sensing measurement or the aperiodic sensing signal transmission independently of at least one of the NES mode supporting aperiodic sensing measurement or aperiodic sensing signal transmission; or at least one of the network node set or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on at least one of the NES mode supporting periodic sensing measurement (i.e., periodic sensing), semi-persistent sensing measurement (i.e., semi-persistent sensing), periodic sensing signal transmission, or semi-persistent sensing signal transmission. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0144] In one respect, NES mode can be either semi-statically configured or dynamically configured. For example, Figure 14 The NES mode in the configuration can be either a semi-static or dynamically configured NES mode. A semi-static NES mode refers to a configuration where the prior knowledge is known and the NES mode does not change dynamically. A semi-static NES mode can be similar to a TDD semi-static configuration. A semi-static NES mode can be updated via RRC signaling and / or system information signaling. A dynamically configured NES mode refers to a configuration where the NES mode can change with dynamic signaling (such as DCI or MAC control elements (MAC-CE)).

[0145] In one aspect, at 1612, a network entity may obtain an error message based on the fact that at least one of the sets of sensing measurements or the sets of sensing signal transmissions was not performed due to overlapping NES mode limitations. For example, Figure 14 At 1418, it is shown that network entity 1402 may obtain an error message based on the fact that at least one of the sets of sense measurements or the sets of sense signal transmissions has not been performed due to overlapping NES mode limitations. In one example, the foregoing aspect may correspond to the combination above. Figure 13The aspects described. Overlapping NES mode limitations can refer to RF sensing measurements and / or RF sensing transmissions that overlap with the NES mode window in time. In one example, if RF sensing transmission is configured at time slot 10 and NES mode is configured from time slot 8 to time slot 12 (e.g., NES mode 1), then RF sensing transmission can overlap with NES mode 1. In one example, 1612 can be performed by NES mode component 198.

[0146] Figure 17 This is a flowchart 1700 of a wireless communication method. The method can be performed by network nodes (e.g., base station 102, base station 310, TRP 402, first TRP 504, second TRP 506, third TRP 508, fourth TRP 510, serving base station 604, candidate neighboring BS / TRP 608, network node 1008, network node 1404, network entity 2002, CU 2010, DU 2030, RU 2040). In one example, the method can be performed by NES mode component 199.

[0147] At 1702, the network node sends an indication of NES mode, where NES mode is supported by at least one of the network node or the UE. For example, Figure 14 At 1408, it is shown that network node 1404 can send indications of the NES modes supported by network node 1404 and / or the UE. In one example, the NES mode may include the above-described combination of... Figures 7-9 The aspects described. In another example, the indication of NES mode may include an indication of the supported NES mode 1010. In one example, the UE may be or include UE 1014. In one example, 1702 may be performed by NES mode component 199.

[0148] At 1704, the network node obtains a configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set based on an indication of the NES mode. For example, Figure 14 At 1412, it is shown that network node 1404 can obtain configuration for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets based on an instruction sent at 1408. In one example, the configuration may be or include configuration 1016. In one example, 1704 may be performed by NES mode component 199.

[0149] Figure 18This is a flowchart 1800 of a wireless communication method. The method can be performed by network nodes (e.g., base station 102, base station 310, TRP 402, first TRP 504, second TRP 506, third TRP 508, fourth TRP 510, serving base station 604, candidate neighboring BS / TRP 608, network node 1008, network node 1404, network entity 2002, CU 2010, DU 2030, RU 2040). In one example, the method (including the various aspects detailed below) can be performed by NES mode component 199.

[0150] At 1804, the network node sends an indication of NES mode, where NES mode is supported by at least one of the network node or the UE. For example, Figure 14 At 1408, it is shown that network node 1404 can send indications of the NES modes supported by network node 1404 and / or the UE. In one example, the NES mode may include the above-described combination of... Figures 7-9 The aspects described. In another example, the indication of NES mode may include an indication of the supported NES mode 1010. In one example, the UE may be or include UE 1014. In one example, 1804 may be performed by NES mode component 198.

[0151] At 1806, the network node obtains a configuration for at least one of the following: an RF sensing session, a sensing measurement set, or a sensing signal transmission set, based on an indication of the NES mode. For example, Figure 14 At 1412, it is shown that network node 1404 can obtain configuration for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets based on an instruction sent at 1408. In one example, the configuration may be or include configuration 1016. In one example, 1806 may be performed by NES mode component 199.

[0152] In one aspect, obtaining configuration may include receiving configuration from at least one of the UE or a network entity. For example, Figure 14 At 1412, it is shown that network node 1404 can receive configuration from network entity 1402. In another example, network node 1404 can receive configuration from UE (e.g., UE 1014).

[0153] In one aspect, at 1802, a network node may receive a request for an indication of NES mode, wherein sending the indication of NES mode may include sending the indication of NES mode based on the request. For example, Figure 14At 1410, it is shown that network node 1404 can receive a request for an indication of NES mode. Furthermore, at 1408, the indication can be sent based on the request received at 1410. In one example, 1802 can be performed by NES mode component 199.

[0154] In one aspect, the NES mode may be associated with at least one of the following: the number of antenna ports used for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set; the sleep mode type; the cell DTX; the UL state; or the DL state. For example, the foregoing aspect may be combined with the above. Figures 7-9 The described aspects are related.

[0155] In one aspect, at point 1812, network nodes can send update requests associated with the configuration based on the availability of the configuration. For example, Figure 14 At 1420, it is shown that network node 1404 can send an update request associated with the configuration based on the configuration obtained at 1412. In one example, 1812 can be performed by NES mode component 199.

[0156] In one aspect, at 1814, a network node can obtain an updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set based on an update request. For example, Figure 14 At 1424, it is shown that network node 1404 can obtain an updated configuration for RF sensing sessions, sensing measurement sets, and / or sensing signal transmission sets. In one example, 1814 can be performed by NES mode component 199.

[0157] In one aspect, the configuration may indicate one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal transmission in the set of sensing signal transmissions. For example, configuration 1016 may indicate one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal transmission in the set of sensing signal transmissions. The foregoing aspect may correspond to the above combination. Figure 11 The aspects described.

[0158] In one aspect, the configuration may instruct at least one of the network node or UE to perform at least one of the sensing measurement set or sensing signal transmission set independently of at least one of the NES mode-supported sensing measurement set or sensing signal transmission set. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0159] In one aspect, the indication of NES mode can instruct network nodes to support performing at least one of the sensing measurement set or sensing signal transmission set independently of the NES mode. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0160] In one aspect, the configuration may instruct one or more of the following: at least one of the network node or the UE will perform the aperiodic sensing measurement or the aperiodic sensing signal transmission independently of at least one of the NES mode supporting aperiodic sensing measurement or aperiodic sensing signal transmission; or at least one of the network node or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on at least one of the NES mode supporting periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission. For example, the foregoing aspect may correspond to Figure 12 Example 1202 in the example.

[0161] In one respect, NES mode can be either semi-statically configured or dynamically configured. For example, Figure 14 The NES mode can be either a semi-statically configured NES mode or a dynamically configured NES mode.

[0162] In one aspect, at 1816, a network node may send an error message based on the fact that at least one of the sets of sensing measurements or the sets of sensing signal transmissions has not been performed due to overlapping NES mode limitations. For example, Figure 14 At 1416, it is shown that network node 1404 may send an error message based on the fact that at least one of the sets of sense measurements or the sets of sense signal transmissions has not been performed due to overlapping NES mode limitations. In one example, the foregoing aspect may correspond to the combination above. Figure 13 The aspects described. In one example, 1816 can be executed by NES mode component 199.

[0163] In one aspect, at 1808, the network node can send configuration for the UE for at least one of the following: an RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions. For example, Figure 14 At 1415, it is shown that network node 1404 can send configurations to the UE for at least one of an RF sensing session, a sensing measurement set, or a sensing signal transmission set. In one example, 1808 can be performed by NES mode component 199.

[0164] In one aspect, at 1810, the network node can perform at least one of a set of sensing measurements or a set of sensing signal transmissions based on its configuration. For example, Figure 14 At 1414, it is shown that network node 1404 can perform a set of sense signal measurements and / or a set of sense signal transmissions based on the configuration obtained at 1412. In one example, 1810 can be performed by NES mode component 199.

[0165] Figure 19Figure 1900 illustrates an example of a hardware implementation for device 1904. Device 1904 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., cellular RF transceivers). Cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, device 1904 may also include one or more Subscriber Identity Module (SIM) cards 1920 and an application processor 1906 coupled to a Secure Digital Card (SD) card 1908 and a screen 1910. Application processor 1906 may include on-chip memory 1906'. In some aspects, device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1926, a power source 1930, and / or a camera 1932. Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include their own dedicated antennas and / or communicate using antenna 1980. Cellular baseband processor 1924 communicates with UE 104 and / or RU associated with network entity 1902 via transceiver 1922 through one or more antennas 1980. Cellular baseband processor 1924 and application processor 1906 may each include computer-readable media / memory 1924', 1906' respectively. Additional memory module 1926 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1924', 1906', 1926 may be non-transitory. Cellular baseband processor 1924 and application processor 1906 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1924 / application processor 1906, the software causes cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by cellular baseband processor 1924 / application processor 1906 during software execution.Cellular baseband processor 1924 / application processor 1906 may be a component of UE 350 and may include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1904 may be a processor chip (modem and / or application) and may only include cellular baseband processor 1924 and / or application processor 1906, and in another configuration, device 1904 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module for device 1904.

[0166] Figure 20Figure 2000 illustrates an example of a hardware implementation for network entity 2002. Network entity 2002 may be a BS, a component of a BS, or implement BS functionality. Network entity 2002 may include at least one of CU 2010, DU 2030, or RU 2040. For example, depending on the layer functionality handled by NES mode component 199, network entity 2002 may include CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 may include CU processor 2012. CU processor 2012 may include on-chip memory 2012'. In some aspects, CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU2010 communicates with DU 2030 via a midhaul link, such as an F1 interface. DU 2030 may include a DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include an additional memory module 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include an RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2012, 2032, and 2042 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0167] As discussed above, NES mode component 199 can be configured to send an indication of an NES mode, wherein the NES mode is supported by at least one of the network node or the UE. NES mode component 199 can be configured to obtain a configuration for at least one of an RF sensing session, a sensing measurement set, or a sensing signal transmission set based on the indication of the NES mode. NES mode component 199 can be configured to obtain a request for the indication of the NES mode, wherein sending the indication of the NES mode includes sending the indication of the NES mode based on the request. NES mode component 199 can be configured to send an update request associated with the configuration based on the acquisition of the configuration. NES mode component 199 can be configured to obtain an updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set based on the update request. NES mode component 199 can be configured to send an error message based on the failure to execute at least one of the sensing measurement set or the sensing signal transmission set due to overlapping NES mode limitations. NES mode component 199 may be configured to transmit, for the UE, the configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set. NES mode component 199 may be configured to perform at least one of the sensing measurement set or the sensing signal transmission set based on the configuration. NES mode component 199 may be located within one or more processors of one or more of CU 2010, DU 2030, and RU 2040. NES mode component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof. Network entity 2002 may include various components configured for various functions. In one configuration, network entity 2002 may include components for transmitting an indication of at least one of Network Energy Saving (NES) mode or Radio Frequency (RF) sensing mode, wherein the NES mode is supported by at least one of the network node or user equipment (UE). In one configuration, network entity 2002 may include components for obtaining a configuration for at least one of an RF sensing session, a sensing measurement set, or a sensing signal transmission set based on the indication of the NES mode. In one configuration, network entity 2002 may include components for obtaining a request for the indication of the NES mode, wherein sending the indication of the NES mode includes sending the indication of the NES mode based on the request. In one configuration, network entity 2002 may include components for sending an update request associated with the configuration based on the acquisition of the configuration.In one configuration, network entity 2002 may include components for obtaining an updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set based on the update request. In one configuration, network entity 2002 may include components for sending an error message based on the failure to execute at least one of the sensing measurement set or the sensing signal transmission set due to overlapping NES mode limitations. In one configuration, network entity 2002 may include components for sending the configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set to the UE. In one configuration, network entity 2002 may include components for executing at least one of the sensing measurement set or the sensing signal transmission set based on the configuration. The components may be NES mode components 199 of network entity 2002 configured to perform the functions described by the components. As described above, network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the components may be TX processor 316, RX processor 370 and / or controller / processor 375 configured to perform the functions described by the components.

[0168] Figure 21 Figure 2100 illustrates an example of a hardware implementation for network entity 2160. In one example, network entity 2160 may be within core network 120. Network entity 2160 may include network processor 2112. Network processor 2112 may include on-chip memory 2112'. In some aspects, network entity 2160 may also include additional memory module 2114. Network entity 2160 communicates with CU 2102 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2180. On-chip memory 2112' and additional memory module 2114 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Processor 2112 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0169] As discussed above, NES mode component 198 can be configured to obtain an indication of an NES mode, wherein the NES mode is supported by at least one of the network node set or the UE. NES mode component 198 can be configured to send a configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set to the network node set or the UE based on the indication of the NES mode. NES mode component 198 can be configured to send a request for the indication of the NES mode to the network node set, wherein obtaining the indication of the NES mode includes obtaining the indication of the NES mode based on the request. NES mode component 198 can be configured to obtain an update request associated with the configuration based on the sending of the configuration. NES mode component 198 can be configured to send an updated configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set to the network node set or the UE based on the update request. NES mode component 198 may be configured to receive an error message based on the failure to execute at least one of the sensing measurement set or the sensing signal transmission set due to overlapping NES mode limitations. NES mode component 198 may reside within processor 2112. NES mode component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2160 may include various components configured for various functions. In one configuration, network entity 2160 may include components for obtaining an indication of a Network Power Saving (NES) mode, wherein the NES mode is supported by at least one of the network node set or user equipment (UE). In one configuration, network entity 2160 may include components for transmitting a configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set for at least one of the network node set or the UE based on the indication of the NES mode. In one configuration, network entity 2160 may include components for sending a request for the indication of the NES mode to the set of network nodes, wherein obtaining the indication of the NES mode includes obtaining the indication of the NES mode based on the request. In one configuration, network entity 2160 may include components for obtaining an update request associated with the configuration based on the sending of the configuration. In one configuration, network entity 2160 may include components for sending an updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set to at least one of the network node set or the UE based on the update request.In one configuration, network entity 2160 may include a component for obtaining an error message based on the fact that at least one of the set of sense measurements or the set of sense signal transmissions was not performed due to overlapping NES mode limitations. The component may be an NES mode component 198 of network entity 2160 configured to perform the functions described therein.

[0170] The network can implement Network Energy Saving (NES) modes to reduce the energy / power consumption of UEs and / or network nodes in the network. For example, the network can reduce the number of antenna ports used by the UE for wireless communication to reduce the UE's power consumption. UEs and / or network nodes in the network can also be configured to perform RF sensing measurements and / or transmissions, which can be used for positioning, navigation, and timing purposes. In one example, RF sensing measurements and / or transmissions can be used to determine the location of the UE. Some networks may not consider the impact of NES modes on RF sensing measurements and / or transmissions, and vice versa. For example, some NES modes may be incompatible with certain types of RF sensing measurements and / or transmissions.

[0171] This document describes various techniques related to network power saving and RF sensing. In one example, a network entity receives an indication of an NES mode, where the NES mode is supported by at least one of a set of network nodes or a UE. Based on this indication of the NES mode, the network entity sends a configuration for at least one of the set of network nodes or the UE for an RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions. RF sensing measurements and / or transmissions can be performed in a manner consistent with the NES mode as described above. For example, by sending a configuration for at least one of the RF sensing session, a set of sensing measurements, or a set of sensing signal transmissions, the network entity can enable the realization of the benefits of RF sensing measurements and / or transmissions (e.g., UE location determination) while saving power / energy in the network via the NES mode.

[0172] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0173] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that an action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to "output" data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "receive" data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims.Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be interpreted as a functional component unless the element is explicitly stated using the phrase “component for…”.

[0174] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0175] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0176] Aspect 1 is a method for wireless communication at a network entity, the method comprising: obtaining an indication of a network power saving (NES) mode, wherein the NES mode is supported by at least one of a set of network nodes or a user equipment (UE); and transmitting, based on the indication of the NES mode, a configuration for at least one of the set of network nodes or the UE for an RF sensing session, a sensing measurement set, or a sensing signal transmission set.

[0177] Aspect 2 is the method according to aspect 1, wherein obtaining the indication for the NES mode includes receiving the indication from at least one of: one or more network nodes or a second network entity in the set of network nodes.

[0178] Aspect 3 is the method according to any one of Aspects 1 to 2, the method further comprising: sending a request for the indication of the NES mode to the set of network nodes, wherein obtaining the indication of the NES mode includes obtaining the indication of the NES mode based on the request.

[0179] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the NES mode is associated with at least one of the number of antenna ports for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set, the sleep mode type, discontinuous cell transmission (DTX), uplink (UL) state, or downlink (DL) state.

[0180] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: obtaining an update request associated with the configuration based on the transmission of the configuration; and transmitting an updated configuration for at least one of the network node set or the UE based on the update request.

[0181] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the configuration indicates that one or more types of NES modes are supported for each sensing measurement in the set of sensing measurements or for each sensing signal in the set of sensing signal transmissions.

[0182] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the configuration instructs at least one of the network node set or the UE to perform the sensing measurement set or the sensing signal transmission set independently of the NES mode.

[0183] Aspect 8 is the method according to aspect 7, wherein the indication of the NES mode instructs the network node set to support performing at least one of the sensing measurement set or the sensing signal transmission set independently of the NES mode.

[0184] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein the configuration indicates one or more of the following: at least one of the network node set or the UE will perform the aperiodic sensing measurement or the aperiodic sensing signal transmission independently of at least one of the NES mode supporting aperiodic sensing measurement or aperiodic sensing signal transmission, or at least one of the network node set or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on at least one of the NES mode supporting periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission.

[0185] Aspect 10 is the method according to aspect 9, wherein the NES mode is a semi-statically configured NES mode or a dynamically configured NES mode.

[0186] Aspect 11 is the method according to any one of aspects 1 to 10, the method further comprising: obtaining an error message based on the failure to perform at least one of the set of sensing measurements or the set of sensing signal transmissions due to overlapping NES mode limitations.

[0187] Aspect 12 is an apparatus for wireless communication at a network entity, the apparatus including a memory and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 11.

[0188] Aspect 13 is an apparatus for wireless communication, the apparatus including components for performing the method according to any one of aspects 1 to 11.

[0189] Aspect 14 is an apparatus according to aspect 12 or 13, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to transmit the configuration via the at least one of the transceiver or the antenna.

[0190] Aspect 15 is a computer-readable medium (e.g., a non-transitory computer-readable medium) including instructions, said computer-executable code causing said at least one processor to perform the method according to any one of aspects 1 to 11 when executed by said at least one processor.

[0191] Aspect 16 is a method for wireless communication at a network node, the method comprising: transmitting an indication of a network power saving (NES) mode, wherein the NES mode is supported by at least one of the network node or user equipment (UE); and obtaining a configuration for at least one of an RF sensing session, a sensing measurement set, or a sensing signal transmission set based on the indication of the NES mode.

[0192] Aspect 17 is the method according to aspect 16, wherein obtaining the configuration includes receiving the configuration from at least one of the UE or network entity.

[0193] Aspect 18 is a method according to any one of aspects 16 to 17, the method further comprising: obtaining a request for the indication to the NES mode, wherein sending the indication to the NES mode includes sending the indication to the NES mode based on the request.

[0194] Aspect 19 is a method according to any one of Aspects 16 to 18, wherein the NES mode is associated with at least one of the number of antenna ports for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set, the sleep mode type, discontinuous cell transmission (DTX), uplink (UL) state, or downlink (DL) state.

[0195] Aspect 20 is a method according to any one of aspects 16 to 19, the method further comprising: sending an update request associated with the configuration based on the acquisition of the configuration; and obtaining an updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set based on the update request.

[0196] Aspect 21 is a method according to any one of aspects 16 to 20, wherein the configuration indicates that one or more types of NES modes are supported for each sensing measurement in the set of sensing measurements or for each sensing signal in the set of sensing signal transmissions.

[0197] Aspect 22 is a method according to any one of aspects 16 to 21, wherein the configuration instructs at least one of the network node or the UE to perform the sensing measurement set or the sensing signal transmission set independently of the NES mode.

[0198] Aspect 23 is the method according to aspect 22, wherein the indication of the NES mode instructs the network node to support performing at least one of the sensing measurement set or the sensing signal transmission set independently of the NES mode.

[0199] Aspect 24 is a method according to any one of aspects 16 to 23, wherein the configuration indicates one or more of the following: at least one of the network node or the UE will perform the aperiodic sensing measurement or the aperiodic sensing signal transmission independently of at least one of the NES mode supporting aperiodic sensing measurement or aperiodic sensing signal transmission, or at least one of the network node or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on at least one of the NES mode supporting periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission.

[0200] Aspect 25 is the method according to aspect 24, wherein the NES mode is a semi-statically configured NES mode or a dynamically configured NES mode.

[0201] Aspect 26 is the method according to any one of aspects 16 to 25, the method further comprising: sending an error message based on the failure to perform at least one of the set of sensing measurements or the set of sensing signal transmissions due to overlapping NES mode limitations.

[0202] Aspect 27 is a method according to any one of aspects 16 to 26, the method further comprising: transmitting to the UE the configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set.

[0203] Aspect 28 is a method according to any one of aspects 16 to 25 or 27, the method further comprising: performing at least one of the set of sensing measurements or the set of sensing signal transmissions based on the configuration.

[0204] Aspect 29 is an apparatus for wireless communication at a network node, the apparatus including a memory and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 16 to 28.

[0205] Aspect 30 is an apparatus for wireless communication, the apparatus including components for performing the method according to any one of aspects 16 to 28.

[0206] Aspect 31 is an apparatus according to aspect 29 or 30, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to transmit the indication of the NES mode via the at least one of the transceiver or the antenna.

[0207] Aspect 32 is a computer-readable medium (e.g., a non-transitory computer-readable medium) including instructions, said computer-executable code causing said at least one processor to perform the method according to any one of aspects 16 to 28 when executed by said at least one processor.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; as well as At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Obtain an indication of a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of a set of network nodes or a User Equipment (UE); and Based on the indication of the NES mode, configuration for at least one of the network node set or the UE is sent for the RF sensing session, sensing measurement set, or sensing signal transmission set.

2. The apparatus of claim 1, wherein, in order to obtain the indication of the NES mode, the at least one processor is configured to receive the indication of the NES mode from at least one of: one or more network nodes or a second network entity in the set of network nodes.

3. The apparatus of claim 1, wherein the at least one processor is further configured to: A request for an indication of the NES mode is sent to the set of network nodes, wherein, in order to obtain the indication of the NES mode, the at least one processor is configured to obtain the indication of the NES mode based on the request.

4. The apparatus of claim 1, wherein the NES mode is associated with at least one of the following: the number of antenna ports for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set; the sleep mode type; discontinuous cell transmission (DTX); uplink (UL) state; or downlink (DL) state.

5. The apparatus of claim 1, wherein the at least one processor is further configured to: Based on the configuration, the sending is used to obtain an update request associated with the configuration; and Based on the update request, an updated configuration for at least one of the network node set or the UE is sent to the network node set or the UE.

6. The apparatus of claim 1, wherein the configuration indicates one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal in the set of sensing signal transmissions.

7. The apparatus of claim 1, wherein the configuration instructs at least one of the network node set or the UE to perform the sensing measurement set or the sensing signal transmission set independently of the NES mode.

8. The apparatus of claim 7, wherein the indication of the NES mode instructs the network node set to support performing at least one of the sensing measurement set or the sensing signal transmission set independently of the NES mode.

9. The apparatus of claim 1, wherein the configuration indicates one or more of the following: At least one of the network node set or the UE will independently perform at least one of the aperiodic sensing measurement or aperiodic sensing signal transmission, independent of the NES mode supporting at least one of aperiodic sensing measurement or aperiodic sensing signal transmission. At least one of the network node set or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on the NES mode supporting at least one of periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission.

10. The apparatus of claim 9, wherein the NES mode is a semi-statically configured NES mode or a dynamically configured NES mode.

11. The apparatus of claim 1, wherein the at least one processor is further configured to: An error message is obtained based on the fact that at least one of the set of sensing measurements or the set of sensing signal transmissions was not performed due to overlapping NES mode limitations.

12. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the configuration, the at least one processor is configured to transmit the configuration via at least one of the transceiver or the antenna.

13. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; as well as At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Sending an instruction for a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of the network node or user equipment (UE); and The configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set is obtained based on the indication of the NES mode.

14. The apparatus of claim 13, wherein, in order to obtain the configuration, the at least one processor is configured to receive the configuration from at least one of the UE or network entity.

15. The apparatus of claim 13, wherein the at least one processor is further configured to: A request is received for the indication of the NES mode, wherein, in order to send the indication of the NES mode, the at least one processor is configured to send the indication of the NES mode based on the request.

16. The apparatus of claim 13, wherein the NES mode is associated with at least one of the following: the number of antenna ports for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set; the sleep mode type; discontinuous cell transmission (DTX); uplink (UL) state; or downlink (DL) state.

17. The apparatus of claim 13, wherein the at least one processor is further configured to: Based on the acquisition of the configuration, an update request associated with the configuration is sent; and Based on the update request, obtain the updated configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set.

18. The apparatus of claim 13, wherein the configuration indicates one or more types of NES modes supported for each sensing measurement in the set of sensing measurements or for each sensing signal in the set of sensing signal transmissions.

19. The apparatus of claim 13, wherein the configuration instructs at least one of the network node or the UE to perform the sensing measurement set or the sensing signal transmission set independently of the NES mode.

20. The apparatus of claim 19, wherein the indication of the NES mode instructs the network node to support performing at least one of the sensing measurement set or the sensing signal transmission set independently of the NES mode.

21. The apparatus of claim 13, wherein the configuration indicates one or more of the following: At least one of the network node or the UE will perform the aperiodic sensing measurement or the aperiodic sensing signal transmission independently of at least one of the NES mode supporting aperiodic sensing measurement or aperiodic sensing signal transmission, or At least one of the network node or the UE will perform the periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission based on the NES mode supporting at least one of periodic sensing measurement, the semi-persistent sensing measurement, the periodic sensing signal transmission, or the semi-persistent sensing signal transmission.

22. The apparatus of claim 21, wherein the NES mode is a semi-statically configured NES mode or a dynamically configured NES mode.

23. The apparatus of claim 13, wherein the at least one processor is further configured to: An error message is sent based on the fact that at least one of the set of sensing measurements or the set of sensing signal transmissions was not performed due to overlapping NES mode limitations.

24. The apparatus of claim 13, wherein the at least one processor is further configured to: The configuration for at least one of the RF sensing session, the sensing measurement set, or the sensing signal transmission set is transmitted to the UE.

25. The apparatus of claim 13, wherein the at least one processor is further configured to: Based on the configuration, at least one of the set of sensing measurements or the set of sensing signal transmissions is performed.

26. The apparatus of claim 13, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the indication of the NES mode, the at least one processor is configured to transmit the indication of the NES mode via at least one of the transceiver or the antenna.

27. A method for wireless communication at a network entity, the method comprising: Obtain an indication of a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of a set of network nodes or a user equipment (UE); as well as Based on the indication of the NES mode, configuration for at least one of the network node set or the UE is sent for the RF sensing session, sensing measurement set, or sensing signal transmission set.

28. The method of claim 27, wherein obtaining the indication for the NES mode comprises receiving the indication from at least one of: one or more network nodes or a second network entity in the set of network nodes.

29. A method for wireless communication at a network node, the method comprising: Send an instruction for a Network Energy Saving (NES) mode, wherein the NES mode is supported by at least one of the network node or user equipment (UE); as well as The configuration for at least one of the RF sensing session, sensing measurement set, or sensing signal transmission set is obtained based on the indication of the NES mode.

30. The method of claim 29, wherein obtaining the configuration includes receiving the configuration from at least one of the UE or a network entity.

Images